VRF On HP Switch
VRF On HP Switch
3
Configuring VRF on HP Switches: in a single site deployment
Conf igure
First we will configure the core switch since this is really the bulk of the configuration steps. If HP’s IRF
technology is to be used, the switches should already be configured with IRF before continuing.
Core Device Conf igurat ion
4
Configuring VRF on HP Switches: in a single site deployment
• Create the VLANs that will be used to transport port information between VRFs. You can also at this
point create any VLANs that are going to be associated with each VRF or are to be configured on the
core device itself.
• Create and bind the vlan-interface to each vpn-instance. It is recommended that you configure the IP
address after binding the interface since this command removes any previously configured information.
• Create the bridge aggregation groups that you will be using to connect the IDF, server farm and
distribution switches to the core
• Create the remaining bridge aggregation groups and add the corresponding ports to the groups (CLI
commands omitted)
Conf igure Core Device Rout ing
To be able to route between VRFs the following steps must be taken. Once configured, all VLANs in all
VRFs will be able to communicate. If certain VLANs are to be restricted, route policies must be configured
to prevent routing information from being exchanged.
[VRF-Core]bgp 65000
[VRF-Core-bgp]router-id 1.1.1.1
[VRF-Core-bgp]ipv4-family vpn-instance idf
[VRF-Core-bgp-idf]peer 172.16.100.252 as-number 65001
[VRF-Core-bgp-idf]peer 172.16.100.253 as-number 65001
[VRF-Core-bgp-idf]import-route direct
5
Configuring VRF on HP Switches: in a single site deployment
[VRF-Core-bgp-idf]quit
[VRF-Core-bgp]ipv4-family vpn-instance server
[VRF-Core-bgp-server]peer 172.16.101.253 as-number 65002
[VRF-Core-bgp- server]import-route direct
[VRF-Core-bgp- server]quit
[VRF-Core-bgp]ipv4-family vpn-instance disti
[VRF-Core-bgp-disti]peer 172.16.102.253 as-number 65003
[VRF-Core-bgp- disti]import-route direct
[VRF-Core-bgp- disti]quit
• The following commands are what allow the exchange of routing information between VRFs. Note that
the RD used is that of the vpn-instance you are trying to reach not of the originating vpn-instance.
[vrf-idf01]vlan 10
[vrf-idf01]vlan 20
[vrf-idf01]vlan 100
• Create the Bridge Aggregation group and add the corresponding ports to the group
6
Configuring VRF on HP Switches: in a single site deployment
[VRF-idf01]bgp 65001
[VRF-idf01-bgp]peer 172.16.100.254 as-number 65000
[VRF-idf01-bgp]quit
[VRF-idf01]ip route-static 0.0.0.0 0.0.0.0 172.16.100.254
Introduce a broadcast storm in a VRF to show that it stays localized. Creating a STP Loop is
another effective demo as well.
If you have access to Ixia test gear, this equipment can generate a broadcast storm at line rate
10G.
To prove that only the local VRF is affected, streaming video and ICMP requests were monitored in
the other VRFs. A physical server in the server VRF can share a folder and laptops in the other
VRFs (IDF and Disti) can play the same video. When there is no broadcast storm, the videos are in
sync and play smoothly and there are no ICMP timeouts. When the Ixia test port was enabled and
introduced a broadcast storm into a VRF, video degradation was seen only on the laptop in the
same VRF as the Ixia and there were multiple ICMP timeouts. Once the broadcast was eliminated
the video resumed playing normally with no ICMP timeouts.
If test equipment or a traffic generator isn’t available you could use hacking tools like Metasploit
and launch a DOS attack or ping of death to achieve similar results.
7
Configuring VRF on HP Switches: in a single site deployment
9
Configuring VRF on HP Switches: in a single site deployment
interface Ten-GigabitEthernet1/2/0/4
port link-type trunk
port trunk permit vlan 1 101
port link-aggregation group 101
#
interface Ten-GigabitEthernet1/2/0/5
port link-type trunk
port trunk permit vlan 1 10 20 100
port link-aggregation group 100
#
interface Ten-GigabitEthernet1/2/0/6
port link-type trunk
port trunk permit vlan 1 10 20 100
port link-aggregation group 110
#
interface Ten-GigabitEthernet2/2/0/1
port link-type trunk
port trunk permit vlan 1 102
port link-aggregation group 102
#
interface Ten-GigabitEthernet2/2/0/2
port link-type trunk
port trunk permit vlan 1 102
port link-aggregation group 102
#
interface Ten-GigabitEthernet2/2/0/3
port link-type trunk
port trunk permit vlan 1 101
port link-aggregation group 101
#
interface Ten-GigabitEthernet2/2/0/4
port link-type trunk
port trunk permit vlan 1 101
port link-aggregation group 101
#
interface Ten-GigabitEthernet2/2/0/5
port link-type trunk
port trunk permit vlan 1 10 20 100
port link-aggregation group 100
#
interface Ten-GigabitEthernet2/2/0/6
port link-type trunk
port trunk permit vlan 1 10 20 100
port link-aggregation group 110
#
bgp 65000
router-id 1.1.1.1 undo synchronization
#
ipv4-family vpn-instance edge
peer 172.16.100.252 as-number 65001
10
Configuring VRF on HP Switches: in a single site deployment
12
Configuring VRF on HP Switches: in a single site deployment
14
Configuring VRF on HP Switches: in a single site deployment
15
Configuring VRF on HP Switches: in a single site deployment
#
interface GigabitEthernet1/0/4
port link-mode bridge
port access vlan 10
#
interface GigabitEthernet1/0/5
port link-mode bridge
port access vlan 10
#
interface GigabitEthernet1/0/6
port link-mode bridge
port access vlan 10
#
interface Ten-GigabitEthernet1/0/25
port link-mode bridge
port access vlan 100
#
Configuration omitted for brevity
ospf 1
area 0.0.0.0
network 172.16.100.0 0.0.0.255
network 192.168.10.0 0.0.0.255
#
ip route-static 0.0.0.0 0.0.0.0 172.16.100.254
#
load xml-configuration
#
user-interface aux 0
user-interface vty 0 15
#
return
16
Configuring VRF on HP Switches: in a single site deployment
Sign up f or updat es
hp.com/go/getupdated Share with colleagues Rate this document
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties f or
HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
17