Beruflich Dokumente
Kultur Dokumente
Introduction........................................................................................ 3
Discovery protocols: LLDP & CDP ........................................................... 4
VLAN configuration .............................................................................. 7
Introduction ..................................................................................... 7
VLAN configuration on Cisco Catalyst ................................................... 8
VLAN configuration on HP ProCurve ....................................................10
Checking VLANs status and connectivity ..............................................11
Additional info about VLANs...............................................................14
Link aggregation ................................................................................19
Introduction ....................................................................................19
A Static Trunk/Channel .....................................................................21
LACP Trunk/Channel.........................................................................24
Spanning-Tree ...................................................................................29
Introduction ....................................................................................29
MSTP Configuration ..........................................................................31
Cisco as Core running PVST+, HP ProCurve as Edge running RSTP ..........41
HP ProCurve as Core running RSTP, Cisco as Edge running PVST+ ..........47
IP routing Interoperability....................................................................55
Sample topology ..............................................................................55
RIP configuration .............................................................................55
Other RIP features ...........................................................................58
OSPF Single Area .............................................................................60
Redistribution into OSPF ...................................................................64
Configuration of Multiple OSPF areas ..................................................70
Other OSPF features.........................................................................77
IP Multicast interoperability..................................................................80
Introduction ....................................................................................80
PIM DENSE Mode .............................................................................80
PIM SPARSE Mode............................................................................86
Introduction
The intent of this document isn’t to describe why you should do these
things, nor does it argue what the benefits are. It merely goes
through how to accomplish the necessary configurations to get the
Cisco and ProCurve switches configured so that they will work
together.
Thank you
Discovery protocols: LLDP & CDP
ProCurve is committed to standards. And it is logically that the proprietary
discovery protocol CDP (Cisco Discovery protocol) has been replaced by the
IEEE 802.1AB standard LLDP (Link Layer Discovery protocol) when this one
was released.
If LLDP is enabled by default, CDP remains in Read-only mode (receive-only).
Then ProCurve switches can discover LLDP neighbors as well as Cisco device
neighbors.
Note: Cisco does not support yet LLDP in its equipments.
Cisco IP Phone could in a close future supports LLDP-MED (Media End-Point
Discovery) which will then allow automatic discovery and configuration of IP
Phones.
Some IP Phone vendors such as Avaya and Mitel are already committed to
LLDP-MED.
The network scheme used here is the same as in the MSTP example.
e1 e2
Gi1/1 Procurve-Edge-1 Gi1/1
Gi1/3 Gi1/3
Gi1/2 Gi1/2
Cisco-Core-2
Cisco-Core-1
e1 e2
Procurve-Edge-2
Discovery configuration
The following command lists CDP neighbors. As expected, it displays the two
Catalyst 6500.
LLDP neighbors: the ProCurve switch displays the two Catalyst 6500 as well
because the LLDP display includes the CDP neighbors.
Local Port : 1
ChassisType : local
ChassisId : Core-Cisco-1
PortType : local
PortId : GigabitEthernet0/1
SysName :
System Descr : Cisco IOS Software, C6500 Software (C6500-IPSERVICESK9-
M)...
PortDescr :
-------------------------------------------------------------------------
Local Port : 2
ChassisType : local
ChassisId : Core-Cisco-2
PortType : local
PortId : GigabitEthernet0/1
SysName :
System Descr : Cisco IOS Software, C6500 Software (C6500-IPSERVICESK9-
M)...
PortDescr :
As ProCurve switches do not send anymore CDP frames, a Cisco switch will
not recognize ProCurve neighbors.
Let’s hope for a Cisco commitment to the IEEE LLDP standard.
11- Introduction
12- VLAN Configuration on Cisco Catalyst
13- VLAN configuration on HP ProCurve
14- Checking VLANs status and connectivity
15- Additional info about VLANs
a. Native VLAN
b. Configuring a “management” VLAN other than VLAN 1
c. Changing maximum number of VLANs
d. Configuring ports for IP Phones
e. VTP – GVRP
f. Cisco Extended Range of VLANs
Introduction
Glossary
This chapter deals with port based VLANs that Cisco and HP ProCurve both
support. Different names are used to describe similar concepts on both
platforms.
Vlan 40
Vlan 30
Vlan 20 10.1.40.1/24
Vlan 10 10.1.30.1/24
Vlan 1 10.1.20.1/24
10.1.10.1/24
10.1.1.1/24
Procurve-1
Vlan 40
Vlan 30
Vlan 20 10.1.40.2/24
Vlan 10 10.1.30.2/24
Vlan 1 10.1.20.2/24
10.1.10.2/24
10.1.1.2/24
Conf t
vlan 10, 20, 30, 40
interface FastEthernet1/0/1
The “encapsulation” method defines how multiple VLANs are carried on Cisco
Ethernet links. Cisco supports a proprietary method, ISL, and the IEEE
standard 802.1q (noted “dot1q”).
Cisco also supports a proprietary negotiation protocol for the trunk named
DTP (Dynamic Trunk Protocol). When defined in “trunk” mode the port
generates DTP frames. The following command disables generation of DTP
frames. This is the recommended configuration when connected to ProCurve
switches.
switchport nonegotiate
Step 4: IP configuration
interface vlan1
ip address 10.1.1.2 255.255.255.0
no shutdown
ip default-gateway 10.1.1.1
In this sample, for testing connectivity, one IP address has been defined in
each VLAN.
interface vlan10
ip address 10.1.10.2 255.255.255.0
no shutdown
interface vlan20
ip address 10.1.20.2 255.255.255.0
no shutdown
interface vlan30
ip address 10.1.30.2 255.255.255.0
no shutdown
interface vlan40
ip address 10.1.40.2 255.255.255.0
no shutdown
VLAN configuration on HP ProCurve
VLAN creation
Conf
vlan 20
untagged 10-19
tagged 45
exit
vlan 30
untagged 20-29
tagged 45
exit
vlan 40
untagged 30-44
tagged 45
exit
Step2: IP address
vlan 1
ip address 10.1.1.1 255.255.255.0
exit
vlan 10
ip address 10.1.10.1 255.255.255.0
exit
vlan 20
ip address 10.1.20.1 255.255.255.0
exit
vlan 30
ip address 10.1.30.1 255.255.255.0
exit
vlan 40
ip address 10.1.40.1 255.255.255.0
exit
The following display shows the “access” ports and does not include the Cisco
“trunk” (802.1q links) ports.
Cisco-1#show vlan
Note the operational mode, the encapsulation mode dot1q (802.1q), the
Native VLAN (the untagged VLAN on the 802.1q link) and the allowed VLANs
on port.
Testing connectivity
The connectivity is tested in the various VLANs defined on the 802.1q link
Cisco-1#ping 10.1.1.1
Cisco-1#ping 10.1.10.1
Cisco-1#ping 10.1.20.1
Cisco-1#ping 10.1.30.1
Cisco-1#ping 10.1.40.1
802.1Q vlan ID : 10
Name : Test10
Status : Port-based
Voice : No
Jumbo : No
List of VLANs defined for a given port. Although it is not explicitly shown in
this display, port 45 is tagged in VLAN 10, 20, 30 and 40 and untagged in 1.
Procurve-1(config)# show vlan port 45
Checking IP interfaces
Procurve-1(config)# sh ip
IP Routing : Disabled
Default-gateway : 10.1.1.1
Default TTL : 64
Arp Age : 20
interface FastEthernet1/0/1
switchport trunk native vlan 99
Which native VLAN is defined on a port can be checked with:
vlan 99
Untagged 45
Show vlan 99
A switch, with its default configuration, have all ports untagged. If connected
to a tagged port, this switch will still be able to send and receive frames
through the “untagged’ (native) VLAN. It will then be able to receive an IP
address automatically via DHCP. This IP address can be discovered by LLDP
(show lldp info remote) or found at the DHCP server. The switch can then be
managed and configured remotely via Telnet.
It is very common to use VLAN 1 as the management VLAN. But any created
VLAN can be used to manage switches. As explained in the previous
paragraph, it is common to use the Native/Untagged VLAN to be the
management VLAN. Again this is not mandatory and one can choose the
VLAN to be carried as tagged on uplinks. Choosing a VLAN other than VLAN
1 for management, we make a clear distinction between Default VLAN and
Management VLAN.
vlan 99
Untagged 45
Ip address 10.1.99.1/24
exit
Ip default-gateway 10.1.99.1
vlan 10
Tagged 45
exit
vlan 20
Tagged 45
exit
vlan 30
Tagged 45
exit
vlan 40
Tagged 45
Exit
Checking VLAN
802.1Q vlan ID : 99
Name : vlan99
Status : Port-based
Voice : No
Jumbo : No
interface FastEthernet1/0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 99
switchport trunk allowed vlan 1,10,20,30,40,99
switchport mode trunk
int vlan 99
ip address 10.199.2 255.255.255.0
no shutdown
Checking VLAN
Cisco-1#sh vlan 99
Checking connectivity
Cisco-1#ping 10.1.99.1
Conf
Max-vlans 48
Write memory
reload
To support both an IP Phone and a PC, a port is configured with one tagged
VLAN (for example 200) to carry voice and one untagged VLAN (for example
10) to transport the data
On ProCurve:
VTP – GVRP
Cisco supports the proprietary protocol VTP (VLAN Trunking Protocol) that
allows propagation of created, deleted or modified VLANs through multiple
Cisco switches. ProCurve switches do not support it.
On the other hand, HP supports the IEEE GVRP standard (GARP VLAN
Registration Protocol) which combines automatic creation of VLANs and
automatic tagging of uplinks. GVRP is supported on some Cisco switches
running the CatOS software and interacts properly with ProCurve switches.
But it’s that GVRP support as been removed in the IOS for Catalyst switches
Previously to 802.1q mode, Cisco “trunk” ports supported the proprietary ISL
mode to carry multiple VLANs on a port. The VLAN-id in ISL is based on 10
Bits and then supports VLANs ranging from 1 to 1023.
With 802.1q support, VLAN Id is on 12 bits and Cisco has defined an
“extended range” to support VLANs from 1024 to 4095.
To create a VLAN in the “extended range”, vtp must be defined in
“transparent mode” with the following global config mode command:
21- Introduction
22- Static Link Aggregation
23- LACP Link Aggregation
HP Active and Cisco passive
Cisco Active and HP passive
HP static LACP and Cisco passive
Introduction
Glossary
Cisco HP ProCurve What is it?
“Dynamic” trunks will be created if both sides agree to it. To do so, they
exchange messages, either PAgP or LACP, to negotiate their status. One side
is said “active” (LACP) or “desirable” (PAgP), meaning that it initiates the
negotiation. The other side is said ”passive” (LACP) or “auto” (PAgP) and
forms a link aggregation automatically.
Static trunks “always” work and can be used to create link aggregation with
switches of many brands and with servers equipped with the right NIC and
driver. Because of its simplicity, it is the preferred method.
When one manages a large number of trunks and doesn’t know in advance
what will be connected to the ports of a switch, dynamic trunks can reduce
the configuration burden.
If the remote side supports LACP in passive mode (default on Cisco and HP),
one side only has to be configured in “active” mode for the trunk to be
formed automatically.
Legend N=No, one side at least will not create a trunk; Y=yes trunk is
created on both sides, Y= yes and preferred setup.
(*): requires older version of firmware of ProCurve switches
Ports in the channel or trunk group must share same characteristics: speed,
duplex, vlan assignment. The media type, such as 1000BT or 1000SX, can
be mixed on HP ProCurve. The same holds true for Cisco.
1
Refer to ProCurve switch owner’s manual to determine if FEC is supported on a particular model.
“Logical” port defined by the Link aggregation
A Static Trunk/Channel
Sample Topology
Cisco
Channel Fa1/0/1 - 4
Trunk 45 - 48
Procurve
Configuration
conf
trunk 45-48 Trk1 Trunk
Trk1 is a “logical” port and can be assigned to a Vlan as any other physical
port. An IP address is assigned to Vlan 10 to test connectivity
vlan 10
untagged Trk1
ip address 10.1.10.1 255.255.255.0
exit
Checking trunk status
Load Balancing
Configuration
conf t
interface range FastEthernet1/0/1 – 4
Interfaces are put in the same channel group. “On” mode means static.
channel-group 1 mode ?
active Enable LACP unconditionally
auto Enable PAgP only if a PAgP device is detected
desirable Enable PAgP unconditionally
on Enable Etherchannel only
passive Enable LACP only if a LACP device is detected
channel-group 1 mode on
interface Vlan 10
ip address 10.1.10.2 255.255.255.0
no shutdown
end
Checking Channel status
… (skip)
Info is repeated for all ports that are members of the channel
LACP Trunk/Channel
With LACP, one side must be “active” (send LACP frames) and the other
“passive”.
conf t
int range fa1/0/1 - 4
channel-group 1 mode active
exit
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number State
Fa1/0/1 SA bndl 32768 0x1 0x1 0x3 0x3D
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Fa1/0/1 SP 0 0011.0a50.0d80 8s 0x0 0x2D 0x3C
(skip info..)
Test connectivity
Cisco#ping 10.1.1.1
Load Balancing
Note: the trunk group defined on ProCurve is a Dynamic trunk “Dyn1” and
belongs to Vlan1.
It cannot be assigned to any other vlans except via GVRP.
To allocate trunk port to Vlans, one should prefer the “static” trunk, with or
without LACP or FEC protocols.
Conf t
interface range FastEthernet1/0/1 - 4
switchport mode access
channel-group 1 mode passive
exit
hostname "ProCurve"
interface 45-48
lacp Active
exit
The trunk group defined on ProCurve is a Dynamic trunk “Dyn1” and belongs
to Vlan1.
It cannot be assigned to any other vlans except via GVRP.
To allocate trunk port to Vlans, one should prefer the “static” trunk, with or
without LACP or FEC protocols.
Sample topology
Cisco-2
Procurve-2
In the following example, the trunk is defined with 6 Ports and as a Layer 3
trunk.
The following defines a trunk as static LACP. The trunk group “trk1” is then assigned to
Vlan 10 in which an IP address is defined.
Conf t
trunk a1-a6 trk1 lacp
vlan 10
untagged trk1
ip address 10.1.10.1/24
exit
Load Balancing
LACP
conf t
interface range FastEthernet1/0/1 - 6
no switchport
channel-group 1 mode passive
exit
interface Port-channel1
no switchport
ip address 10.1.10.2 255.255.255.0
end
Local information:
LACP port Admin Oper Port Port
Port Flags State Priority Key Key Number
State
Fa1/0/1 SP bndl 32768 0x1 0x1 0x3FB 0x3C
Partner's information:
LACP port Oper Port Port
Port Flags Priority Dev ID Age Key Number State
Fa1/0/1 SA 0 000e.7f06.0100 12s 0xD2 0x1 0x3D
(skip info…)
Introduction
Glossary
MSTP 802.1s
It is supported on most manageable switches except 2500 and 4100 switches
Please refer to switch documentation.
PVST+
By default, Cisco switches run PVST+. PVST is the implementation of STP on
ISL links (Cisco proprietary multi-VLAN encapsulation) while PVST+ runs on
802.1q links .
In PVST+, there is one instance of STP per VLAN and BPDUs use a
proprietary Multicast Mac Address. They are not “understood” by HP
ProCurve switches (except by ProCurve 9300M and 9400M) and are then
flooded as a regular multicast. So, regarding PVST+ BPDUs, HP ProCurve
switches appear as a hub.
However, Native VLAN (untagged VLAN of a tagged link equal to VLAN 1 be
default) is an exception. In Native VLAN, the Cisco switches send standard
STP BPDUs, which are “understood” by HP ProCurve switches. This is how
both platform interact.
Cisco has also introduced Rapid PVST+, a PVST+ implementation that
integrates Rapid STP principles.
Prestandard MSTP
MSTP should not be confused with the prestandard version of MSTP.
MSTP (802.1s)
You must run the latest versions of IOS to get support of MSTP (check on
Cisco web site).
Caution
Support for the IEEE 802.1s standard has been introduced around September
2005 by Cisco in the IOS. One should refer to Cisco web site for IOS support
of compliant MSTP (*). Caution should be taken on not confusing the
prestandard MST and the compliant IEEE 802.1s MST. If configuration of
both modes looks exactly the same, the prestandard does NOT
interoperate with the MSTP on ProCurve as this one complies with IEEE
802.1s standard.
(*) Versions of IOS implementing the Compliant IEEE 802.1s starts with:
12.2(18) for Catalyst 6500, 12.2(25)SG for Catalyst 4500 and 12.2(25)SEC
on Catalyst 35xx, 37xx, and 2970.
If not all your devices support MSTP yet, a progressive migration to MSTP
can be put in place as it interoperates with Standard, Rapid Spanning Tree
modes and with PVST via the Native Vlan.
Note that all STP modes interoperate via the standard spanning-tree mode
also named the Common Spanning-Tree (CST). So whatever is your choice,
you should always carefully define the root and secondary root of the
CST. On Cisco look after priority of STP in the Native Vlan (vlan 1 by
default), on ProCurve look after the “global” priority of STP.
MSTP Configuration
e1 e2
Gi1/1 Procurve-Edge-1
Gi1/1
Gi1/3 Gi1/3
Gi1/2 Gi1/2
Cisco-Core-2
Cisco-Core-1
e1 e2
Procurve-Edge-2
The parameters for the MSTP domain has been defined as followed:
Configuration Name = procurve-cisco (case sensitive)
Configuration Number = 1
Instance 1 = vlans 1, 10, 20
Instance 2 = vlans 30, 40
Configuration of Cisco-Core-1
hostname Core-Cisco-1
All parameters of the MSTP configuration must match on all switches of the
MSTP domain.
spanning-tree mst configuration
name procurve-cisco
revision 1
instance 1 vlan 1, 10, 20
instance 2 vlan 30, 40
VLAN Creation
VLAN 1 exists by default
vlan 10,20,30,40
Uplinks are defined as 802.1q links. They are named “trunks” in Cisco
terminology and “tagged links” in ProCurve terminology. The “nonegogiate”
feature means that we do no use the Dynamic Trunk Protocol to negotiate
the status of the uplink.
IP configuration.
ip routing
The Virtual IP used as Default Gateway for the various VLANs are set using
HSRP (Hot Standby Router Protocol), the Cisco proprietary protocol.
As Cisco-Core-1 is the Root of MST instance 1, we also set it as Master of the
Virtual IP of Vlans 1, 10 & 20. And as it is secondary root for MST instance 2,
we define it as the Backup of Virtual IP in Vlans 30 & 40.
interface Vlan1
ip address 10.1.1.1 255.255.255.0
standby 1 ip 10.1.1.254
standby 1 timers 1 3
standby 1 priority 255
standby 1 preempt
!
interface Vlan10
ip address 10.1.10.1 255.255.255.0
standby 10 ip 10.1.10.254
standby 10 timers 1 3
standby 10 priority 255
standby 10 preempt
!
interface Vlan20
ip address 10.1.20.1 255.255.255.0
standby 20 ip 10.1.20.254
standby 20 timers 1 3
standby 20 priority 255
standby 20 preempt
!
interface Vlan30
ip address 10.1.30.1 255.255.255.0
standby 30 ip 10.1.30.254
standby 30 timers 1 3
!
interface Vlan40
ip address 10.1.40.1 255.255.255.0
standby 40 ip 10.1.40.254
standby 40 timers 1 3
!
end
Core-cisco-2 configuration
hostname Core-Cisco-2
!
Global Configuration is similar to the configuration of Cisco-Core-1
end
ProCurve-Edge-1 Configuration
ProCurve-Edge-1 is a 3500yl.
hostname "ProCurve-Edge-1"
VLAN configuration
MSTP Configuration: Name, Revision and instances match the one of other
switches in MSTP domain
ProCurve-Edge-2 Configuration
hostname "ProCurve-Edge-2"
max-vlans 16
vlan 1
name "DEFAULT_VLAN"
untagged 1-9,18-24
ip address 10.1.1.4 255.255.255.0
no untagged 10-17
exit
vlan 10
name "VLAN10"
untagged 10-11
tagged 1-2
exit
vlan 20
name "VLAN20"
untagged 12-13
no ip address
tagged 1-2
exit
vlan 30
name "VLAN30"
untagged 14-15
no ip address
tagged 1-2
exit
vlan 40
name "VLAN40"
untagged 16-17
no ip address
tagged 1-2
exit
spanning-tree
On Cisco-Core-2
Parameters of MSTP configuration.
Core-Cisco-2#show spanning-tree mst configuration
Name [procurve-cisco]
Revision 1 Instances configured 3
Instance Vlans mapped
-------- -------------------------------------------------------
0 2-9,11-19,21-29,31-39,41-4094
1 1,10,20
2 30,40
-----------------------------------------------------------------
On ProCurve-Edge-1
Parameters of MSTP configuration.
Note that display shows IST instance without any Vlans. In fact the vlans,
including those not yet created, that are not associated with an existing
instance are mapped to the IST instance.
| Prio BPDU
Port Type | Cost rity Edge Pnt-to-Pnt MCheck Hello Time Filter
---- --------- + --------- ----- ---- ----------- ------ ------
1 100/1000T | Auto 128 No Force-True Yes Use Global No
2 100/1000T | Auto 128 No Force-True Yes Use Global No
3 100/1000T | Auto 128 No Force-True Yes Use Global No
4 100/1000T | Auto 128 Yes Force-True Yes Use Global No
5 100/1000T | Auto 128 Yes Force-True Yes Use Global No
Instance ID : 0
Mapped VLANs :
Instance ID : 1
Mapped VLANs : 1,10,20
Switch Priority : 32768
Instance ID : 2
Mapped VLANs : 30,40
Filtered Ports :
Switch MAC Address : 001635-b487c0
Switch Priority : 32768
Max Age : 20
Max Hops : 20
Forward Delay : 15
Procurve-Edge-1
Cisco-1 Cisco-2
In this topology, uplinks are tagged with VLANs 10, 20, 30 and 40 and
untagged for VLAN 1. On Cisco, it is named the Native VLAN.
In PVST+ Cisco-1 is the primary Root for VLANs 1, 10 and 20 and Cisco-2 the
secondary Root.
Cisco-2 is the primary Root for VLANs 30 and 40 and Cisco-1 the secondary
Root.
ProCurve-Edge-1 is an access switch.
Following define PVST+ Spanning-Tree mode, allows PVST+ to run for VLANs
above 1023 an up to 4095.
Conf t
hostname Cisco-1
Spanning-Tree mode pvst
Spanning-Tree extend system-id
Cisco-1 is the primary Root for VLAN 1, 10, 20 and the secondary Root for
VLAN 30,40
Although it is not mandatory, the STP timers have been lowered to speed
convergence time. One should pay attention in using those values as it may
create instability if not applied properly. The following values are acceptable
in a network with a “diameter” of 3, which means that BPDUs will not cross
more than 3 switches before returning to originator Root switch.
Spanning-Tree vlan 1,10,20,30,40 hello-time 1
Spanning-Tree vlan 1,10,20,30,40 forward-time 4
Spanning-Tree vlan 1,10,20,30,40 max-age 6
!
Access ports are configured in PortFast mode
Conf t
hostname Cisco-2
Cisco-2 is the secondary Root for VLANs 1, 10, 20 and primary Root for
VLANs 30,40
Conf
hostname "ProCurve-Edge-1"
Spanning-Tree
Default mode is RSTP (802.1w), other modes are Standard STP (802.1D) and
MSTP (802.1s). Changing mode requires a reboot.
VLANs configuration
vlan 1
ip address 10.1.1.10 255.255.255.0
vlan 10
untagged B1-B4
tagged A15-A16
vlan 20
untagged B5-B9
tagged A15-A16
vlan 30
untagged B10-B14
tagged A15-A16
vlan 40
untagged B15-B19
tagged A15-A16
Display confirms Cisco-1 as the primary Root for VLANs 1, 10, 20 and
secondary Root for VLANs 30 and 40 and all ports are in forwarding mode.
Cisco-1#sh Spanning-Tree
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 1
Address 0013.c382.a900 (Cisco-1)
This bridge is the root
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0010
Spanning-Tree enabled protocol ieee
Root ID Priority 10
Address 0013.c382.a900 (Cisco-1)
This bridge is the root
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0020
(skip…)
VLAN0030
Spanning-Tree enabled protocol ieee
Root ID Priority 30
Address 0013.c392.d200 (Cisco-2)
Cost 4
Port 6 (GigabitEthernet1/0/4)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0040
(skip…)
Display confirms Cisco-2 as the primary Root for VLANs 30 and 40 and
secondary Root for VLANs 1, 10 and 20 and all ports are in forwarding mode.
Cisco-2#sh span
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 1
Address 0013.c382.a900 (Cisco-1)
Cost 4
Port 6 (GigabitEthernet1/0/4)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0010
Spanning-Tree enabled protocol ieee
Root ID Priority 10
Address 0013.c382.a900 (Cisco-1)
Cost 4
Port 6 (GigabitEthernet1/0/4)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0020
(skip…)
VLAN0030
Spanning-Tree enabled protocol ieee
Root ID Priority 30
Address 0013.c392.d200 (Cisco-2)
This bridge is the root
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0040
(skip…)
Conclusion
The same test has been run implementing the Rapid PVST mode on the Cisco
cores.
Regarding finale topology, same results have been obtained. However no
significant improvement in speed convergence has resulted.
In other words, HP ProCurve RSTP and Cisco Rapid PVST interacts in Vlan 1
as RSTP or standard STP interacts with PVST, but Rapid STP mechanisms are
not functioning.
In its Rapid PVST mode implementation, Cisco does not use the standard
costs of Rapid STP but rather the cost of standard STP. For example Fast
Ethernet cost is 19 and not 200000.
Sample topology
In this topology, uplinks are tagged for VLANs 10, 20, 30 and 40 and
untagged for VLAN 1.
ProCurve-Core-1 and 2 are defined as Root and secondary Root of RSTP.
Cisco-1 and Cisco-2 use standard PVST+ configuration.
Conf
hostname "ProCurve-Core-1/2"
Uplink ports are defined as Non Edge. Default is Edge and Point-to-Point.
Spanning-Tree priority 0
hostname Cisco-1/2
Spanning-Tree mode pvst
Spanning-Tree extend system-id
On ProCurve-Core-1
On ProCurve-Core-2
Cisco-1#show Spanning-Tree
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 0
Address 000e.7f06.0100
Cost 4
Port 3 (GigabitEthernet1/0/1)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 0
Address 000e.7f06.0100 (ProCurve-Core-1)
Cost 4
Port 3 (GigabitEthernet1/0/1)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
In VLANs 10, 20, 30 and 40, ProCurve-Core-1 and 2 forward Cisco PVST
BPDUs as any other frames. They are “transparent” to the Cisco switches.
Cisco-1 is the Root switch because of its Mac address.
From Cisco switches, STP Topology in VLANs 10, 20, 30 and 40 appears as
follows:
ProCurve-Core-1# conf
We define the value of path-cost of uplinks as 3.
Status on ProCurve-Core-2
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 0
Address 000e.7f06.0100 (ProCurve-Core-1)
Cost 4
Port 3 (GigabitEthernet1/0/1)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
VLAN0010
Spanning-Tree enabled protocol ieee
Root ID Priority 32778
Cost 4
Address 0013.c382.a900 (cisco-1)
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
On Cisco-2
Cisco-2#sh span
VLAN0001
Spanning-Tree enabled protocol ieee
Root ID Priority 0
Address 000e.7f06.0100
Cost 4
Port 3 (GigabitEthernet1/0/1)
Hello Time 1 sec Max Age 6 sec Forward Delay 4 sec
Sample topology
RIP configuration
conf
hostname ProCurve
ip routing
Vlan 110
untagged 1-10
ip address 10.1.10.1 255.255.255.0
exit
Vlan 120
untagged 11-20
ip address 10.1.20.1 255.255.255.0
exit
Vlan 130
untagged 21-30
ip address 10.1.30.1 255.255.255.0
exit
Vlan 140
untagged 31-40
ip address 10.1.40.1 255.255.255.0
exit
vlan 100
untagged 48
ip address 10.1.100.1 255.255.255.0
exit
router rip
exit
RIP requires to be defined in the Vlan in which there are one or more RIP
Neighbors. It is not necessary to enable RIP in the other VLANs. When RIP is
enabled, “connected networks” are automatically redistributed into RIP.
vlan 100
ip rip
exit
Conf t
hostname Cisco
IP addresses
interface Vlan100
ip address 10.1.100.2 255.255.255.0
no shutdown
interface Vlan210
ip address 10.2.10.1 255.255.255.0
no shutdown
interface Vlan220
ip address 10.2.20.1 255.255.255.0
no shutdown
interface Vlan230
ip address 10.2.30.1 255.255.255.0
no shutdown
interface Vlan240
ip address 10.2.40.1 255.255.255.0
router rip
network 10.0.0.0
version 2
passive-interface Vlan210
passive-interface Vlan220
passive-interface Vlan230
passive-interface Vlan240
Checking RIP
IP Route Entries
IP Route Entries
IP Route Entries
Auto-summary
By default, RIP summarizes IP subnets announcement to a classfull
network on a network boundary. For example the subnet 10.1.1.0/24
is announced as 10.0.0.0/8 on the IP interface 192.168.1.1. To disable
this behavior:
ProCurve1(config)#router rip
ProCurve1(rip)#no auto-summary
Cisco1(config)#router rip
Cisco1(config-router)#No auto-summary
RIP Version
On HP ProCurve switches, RIP is in version 2 on all interfaces. On Cisco
RIP is sent in Version 1 and can be received in version 1 and 2.
On HP ProCurve, changing version is done is the IP interface (vlan)
level:
ProCurve1(config)#Vlan 110
ProCurve1(vlan-10)#ip rip v1-only
ProCurve1(vlan-10)#ip rip v2-only
ProCurve1(vlan-10)#ip rip v1-compatible-v2
Cisco1(config)#router rip
Cisco1(config-router)#version 2
Cisco1(config-if)#int vlan 100
Cisco1(config-if)#ip rip send version 2
Cisco1(config-if)#ip rip receive version 1 2
ProCurve1(config)#router rip
ProCurve1(rip)#redistribute static
ProCurve1(rip)#redistribute connected
ProCurve1(rip)#default-metric 4
Cisco1(config)#router rip
Cisco1(config-router)#redistribute static
Cisco1(config-router)#default-metric 4
Cisco1(config-router)#distribute-list 1 out
Cisco1(config-router)#access-list 1 permit 10.1.10.0 0.0.0.255
hostname "ProCurve"
ip routing
vlan 100
untagged 48
ip address 10.1.100.1 255.255.255.0
exit
Vlan 110
untagged 1-9
ip address 10.1.10.1 255.255.255.0
exit
Vlan 120
untagged 10-19
ip address 10.1.20.1 255.255.255.0
exit
Vlan 130
untagged 20-29
ip address 10.1.30.1 255.255.255.0
exit
Vlan 140
untagged 30-44
ip address 10.1.40.1 255.255.255.0
exit
ip router-id 1.1.1.1
router ospf
area backbone
exit
vlan 100
ip ospf area 0
exit
Vlan 110
ip ospf area 0
exit
Vlan 120
ip ospf area 0
exit
Vlan 130
ip ospf area 0
exit
Vlan 140
ip ospf area 0
exit
ip routing
interface Vlan100
ip address 10.1.100.2 255.255.255.0
no shutdown
interface Vlan210
ip address 10.2.10.2 255.255.255.0
no shutdown
interface Vlan220
ip address 10.2.20.2 255.255.255.0
no shutdown
interface Vlan230
ip address 10.2.30.2 255.255.255.0
no shutdown
interface Vlan240
ip address 10.2.40.2 255.255.255.0
no shutdown
router ospf 1
router-id 2.2.2.2
network 10.0.0.0 0.255.255.255 area 0
List IP Interfaces:
ProCurve# show ip
Internet (IP) Service
IP Routing : Enabled
Default TTL : 64
Arp Age : 20
IP Route Entries
An other way for announcing networks via OSPF is to use the “redistribute
connected” option. OSPF is enabled on the interfaces with an OSPF neighbor,
other networks are simply redistributed into OSPF.
Conf t
router ospf 1
router-id 2.2.2.2
redistribute connected metric 100 metric-type 1 subnets
conf
ip router-id 1.1.1.1
router ospf
area backbone
default-metric 200
metric-type type1
redistribute connected
exit
vlan 100
ip ospf area backbone
exit
IP Route Entries
conf t
ip route 0.0.0.0 0.0.0.0 10.1.30.2
router ospf
redistribute static
default-metric 300
metric-type type1
exit
… and checking on Cisco
router ospf 1
default-information originate metric 400 metric-type 1
default-metric 400
IP Route Entries
HP ProCurve supports OSPF and RIP, two standard for Interior Gateway
Protocols (IGP). Cisco, support standards as well as proprietary IGP such as
IGRP and EIGRP. When mixing both environments one may have to support
both proprietary and standard routing protocols.
In this case, the solution is to mutually redistribute routing protocols on the
Cisco platform such as in the following example
Cisco-2 configuration: internal router in EIGRP autonomous system
router eigrp 65
network 10.0.0.0
passive-interface vlan 310
Check EIGRP
IP Configuration.
router eigrp 65
network 10.0.0.0
passive-interface vlan100
OSPF configuration.
Conf t
router ospf 1
router-id 2.2.2.2
network 10.1.100.2 0.0.0.0 area 0
router ospf 1
redistribute eigrp 65 metric 100 metric-type 1 subnets
router eigrp 65
redistribute ospf 1 metric 10000 100 255 1 1500
router eigrp 65
no auto-summary
Checking redistribution.
To check the redistribution effects, status should be displayed on the routers
that are neighbors of the “redistributing” router. In our example these are
Cisco-2 and ProCurve-1.
Cisco-2#show ip route
10.0.0.0/24 is subnetted, 6 subnets
D*EX 10.1.10.0 [170/19768] via 10.1.200.1, 00:04:29, vlan200
D*EX 10.1.20.0 [170/19768] via 10.1.200.1, 00:04:29, vlan200
D*EX 10.1.30.0 [170/19768] via 10.1.200.1, 00:04:29, vlan200
D*EX 10.1.100.0 [170/19768] via 10.1.200.1, 00:04:29, vlan200
C 10.1.200.0 is directly connected, Vlan200
C 10.3.10.0 is directly connected, Vlan310
Sample topology
Conf t
hostname ProCurve-0
ip routing
vlan 110
ip address 10.1.10.1 255.255.255.0
ip address 10.1.11.1 255.255.255.0
exit
vlan 120
ip address 10.1.20.1 255.255.255.0
exit
vlan 130
ip address 10.1.30.1 255.255.255.0
exit
vlan 100
ip address 10.1.100.1 255.255.255.0
exit
ip router-id 1.1.1.1
router ospf
area backbone
Area 1 is standard
area 1
Area 2 is stub (filters External LSA). 22 defines the default metric of default
route generated in area 2
area 2 stub 22
Area 3 is totally stubby (filters External LSA and Summary LSA). 33 defines
the default metric of default route generated in area 3
vlan 100
ip ospf area 0
exit
vlan 110
ip ospf area 1
exit
vlan 120
ip ospf area 2
exit
vlan 130
ip ospf area 3
exit
Checking status of OSPF neighbors
Conf t
hostname Cisco-1
ip routing
Interface Vlan 110
ip address 10.1.10.2 255.255.255.0
router ospf 1
router-id 1.0.0.1
log-adjacency-changes
network 10.1.0.0 0.0.255.255 area 1
Checking OSPF routes: networks from other areas appear as “O IA” or OSPF
Inter-Area networks.
hostname Cisco-2
ip routing
Interface Vlan120
ip address 10.1.20.2 255.255.255.0
router ospf 1
router-id 1.0.0.2
log-adjacency-changes
area 2 stub
network 10.1.0.0 0.0.255.255 area 2
end
Checking OSPF routes: OSPF networks from other areas appear as “O IA” or
OSPF Inter-Area networks. A default route is also generated in area 2 to
“hide” or “summarize” External networks (networks resulting of a
redistribute).
Note network 10.1.10.0/23 that results from summarization of Area 1.
hostname Cisco-3
Interface Vlan130
ip address 10.1.30.2 255.255.255.0
router ospf 1
router-id 1.0.0.3
log-adjacency-changes
area 3 stub no-summary
network 10.1.0.0 0.0.255.255 area 3
end
Conf t
hostname Cisco1
ip routing
Interface Vlan100
ip address 10.1.100.2 255.255.255.0
Interface Vlan210
ip address 10.2.10.1 255.255.255.0
Interface Vlan220
ip address 10.2.20.1 255.255.255.0
Interface Vlan230
ip address 10.2.30.1 255.255.255.0
Enabling OSPF
router ospf 1
router-id 2.2.2.2
hostname "ProCurve-4"
ip routing
vlan 210
ip address 10.2.10.2 255.255.255.0
exit
ip router-id 2.0.0.4
router ospf
area 4
exit
vlan 210
ip ospf area 4
exit
IP Route Entries
hostname "ProCurve-5"
ip routing
vlan 220
untagged 1-26
ip address 10.2.20.2 255.255.255.0
exit
ip router-id 2.0.0.5
router ospf
area 5 stub 55
exit
vlan 220
ip ospf area 5
exit
Checking OSPF routes: all routes are seen as Inter-Area routes and a default
route is generated by ABR to “hide” external networks.
IP Route Entries
IP Route Entries
OSPF cost
ProCurve# conf
ProCurve(config)# vlan 100
ProCurve(vlan-10)# ip ospf cost 10
Check with:
Cisco# conf
Cisco(config)# int vlan 100
Cisco(config-if)# ip ospf cost 10
conf
hostname "ProCurve"
key-chain "ospf-key"
key-chain "ospf-key" key 1 key-string "hp-cisco"
ip router-id 1.1.1.1
router ospf
area backbone
exit
vlan 100
ip ospf area backbone
ip ospf authentication-key "ospf-key"
exit
key-chain "ospf-key"
key-chain "ospf-key" key 1 key-string "hp-cisco"
vlan 100
ip ospf area backbone
ip ospf md5-auth-key-chain "ospf-key"
exit
10.1.200.0/24
10.1.1.0/24 e1 10.1.2.0/24
e2
Procurve-1 Gi1/1
Gi1/1
Gi1/3 Gi1/3
Cisco-1 Cisco-2
Gi1/4
10.1.100.0/24
hostname "ProCurve-1"
First let’s enable ip routing and define VLANs, port assignment and IP
addresses.
ip routing
vlan 10
untagged 1
ip address 10.1.1.2 255.255.255.252
exit
vlan 20
untagged 2
ip address 10.1.2.2 255.255.255.252
exit
On IP subnet/VLAN where there is potential receiver or source, we activate
IGMP. As VLANs 10 and 20 are defined on uplinks, there is no need to define
IGMP.
vlan 200
untagged 19
ip address 10.1.200.1 255.255.255.0
ip igmp
exit
For Multicast routing, the initial step is to enable globally IP multicast routing
ip multicast-routing
When a router receives a multicast flow, it checks the flow is received via the
interface that leads to the source via the shortest path. This is called the
“reverse path forwarding” process for which PIM uses the IP unicast routing
table.
This is why we enable OSPF as well as PIM.
ip router-id 1.0.0.0
router ospf
area backbone
exit
router pim
exit
vlan 20
ip ospf 10.1.2.2 area backbone
ip pim-dense
ip-addr any
exit
exit
vlan 200
ip ospf 10.1.200.1 area backbone
ip pim-dense
ip-addr any
exit
exit
Configuration of Cisco-1
hostname Cisco-1
ip routing
ip multicast-routing
interface GigabitEthernet1/3
no switchport
ip address 10.1.5.1 255.255.255.252
ip PIM state-refresh origination-interval 60
ip PIM dense-mode
interface GigabitEthernet1/4
no switchport
ip address 10.1.100.1 255.255.255.0
ip PIM state-refresh origination-interval 60
ip PIM dense-mode
Configuration of Cisco-2
Configuration of Cisco-2 is identical to configuration of Cisco-1.
hostname Cisco-2
ip routing
ip multicast-routing
interface GigabitEthernet1/1
no switchport
ip address 10.1.2.1 255.255.255.252
ip PIM state-refresh origination-interval 60
ip PIM dense-mode
interface GigabitEthernet1/3
no switchport
ip address 10.1.5.2 255.255.255.252
ip PIM state-refresh origination-interval 60
ip PIM dense-mode
router ospf 1
router-id 0.0.0.2
log-adjacency-changes
network 10.0.0.0 0.255.255.255 area 0
PIM Interfaces
PIM Neighbors
IP Address VLAN Up Time (sec) Expire Time (sec)
--------------- ---- ------------------ ------------------
10.1.1.1 10 2686 76
10.1.2.1 20 2113 89
If multicast sources are active on the network, the “show ip mroute” or the
“show ip pim mroute” should show entries:
ProCurve-1# show ip pim mroute
VLAN ID : 10
VLAN Name : VLAN10
IGMP is not enabled
VLAN ID : 20
VLAN Name : VLAN20
IGMP is not enabled
VLAN ID : 200
VLAN Name : VLAN200
Querier Address : This switch is Querier
Cisco-1#show ip mroute
Cisco-2#show ip mroute
IP Multicast Routing Table
Flags: D- Dense, S- Sparse, B- Bidir Group, s- SSM Group, C- Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
List IGMP Groups. Except “Auto-rp” entry, no other IGMP entry can be seen
as no receiver is present.
Vlan and IP configuration. Vlan 200 contain receivers and IGMP is enabled.
hostname "ProCurve-1"
ip routing
vlan 10
name "VLAN10"
untagged 1
ip address 10.1.1.2 255.255.255.252
exit
vlan 20
name "VLAN20"
untagged 2
ip address 10.1.2.2 255.255.255.252
exit
vlan 200
name "VLAN200"
untagged 19
ip address 10.1.200.1 255.255.255.0
ip igmp
exit
IP interfaces are defined in PIM Sparse mode and by default accept all flows
(ip-addr any)
vlan 10
ip ospf 10.1.1.2 area backbone
ip pim-sparse
ip-addr any
exit
exit
vlan 20
ip ospf 10.1.2.2 area backbone
ip pim-sparse
ip-addr any
exit
exit
vlan 200
ip igmp
ip ospf 10.1.200.1 area backbone
ip pim-sparse
ip-addr any
exit
exit
Interfaces are defined as sparse-dense mode which means that router can
run in both modes depending on the environment. “Sparse-mode” could also
be used in this example.
interface GigabitEthernet0/1
no switchport
ip address 10.1.1.1 255.255.255.252
ip pim sparse-dense-mode
interface GigabitEthernet0/3
no switchport
ip address 10.1.5.1 255.255.255.252
ip pim sparse-dense-mode
interface GigabitEthernet0/4
no switchport
ip address 10.1.100.1 255.255.255.0
ip pim sparse-dense-mode
OSPF is enabled.
router ospf 1
router-id 0.0.0.1
log-adjacency-changes
network 10.0.0.0 0.255.255.255 area 0
end
hostname Cisco-2
ip routing
ip multicast-routing
interface GigabitEthernet0/1
no switchport
ip address 10.1.2.1 255.255.255.252
ip pim sparse-dense-mode
interface GigabitEthernet0/2
no switchport
ip address 10.1.4.1 255.255.255.252
ip pim sparse-dense-mode
interface GigabitEthernet0/3
no switchport
ip address 10.1.5.2 255.255.255.252
ip pim sparse-dense-mode
router ospf 1
router-id 0.0.0.2
log-adjacency-changes
network 10.0.0.0 0.255.255.255 area 0
end
PIM Interfaces
PIM Neighbors
PIM Neighbors
Cisco-1#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
Cisco-1#sh ip pim rp
Group: 225.1.1.1, RP: 10.1.200.1, v2, uptime 02:28:15, expires 00:01:07
Cisco-2#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
Cisco-2#sh ip pim rp
Group: 225.1.1.1, RP: 10.1.200.1, v2, uptime 02:22:22, expires 00:02:06