ProCurve - Cisco Interoperability Guide

  • View
    625

  • Download
    5

Embed Size (px)

Text of ProCurve - Cisco Interoperability Guide

ProCurve Networking

ProCurve / Cisco Interoperability Guide

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

IntroductionTodays multi-vendor environments present many challenges to administrators trying to configure dissimilar (proprietary vs. standard) protocols. In an effort to accommodate the needs for many of our partners and customers, ProCurve networking has written this guide to assist in the configuration and deployment of ProCurve and Cisco environments. The intent of this document isnt 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.

While the testing conducted was extensive, it is impossible that all possible configurations and scenarios were captured. This document therefore, can not be assumed to be perfect as it applies to every environment. Please consider carefully the implications of some of these changes before instituting them.

The recommendation is to test the new configurations in a controlled environment prior to rolling out changes that could impact your production environment. Additionally, saving current configuration files for switches is a good practice for backup.

Thank you

Discovery protocols: LLDP & CDPProCurve 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.

Gi1/1

e2 Procurve-Edge-1

e1

Gi1/1

Gi1/3 Gi1/2

Gi1/3 Gi1/2

Cisco-Core-1 e1 e2

Cisco-Core-2

Procurve-Edge-2

Discovery configurationWe simply use the default configuration regarding Discovery protocols. On ProCurve switches: LLDP is enabled in send and receive mode. CDP is enabled in received mode. On Cisco: CDP is enabled by default.

Checking Discovery info on a ProCurve switchThe following command lists CDP neighbors. As expected, it displays the two Catalyst 6500.ProCurve-Edge-1# show cdp neighbors CDP neighbors information Port ---1 2 Device ID ---------------------Core-Cisco-1 Core-Cisco-2 | + | | Platform Capability ---------------------------- ----Cisco IOS Software, C6500... R S Cisco IOS Software, C6500... R S

LLDP neighbors: the ProCurve switch displays the two Catalyst 6500 as well because the LLDP display includes the CDP neighbors.ProCurve-Edge-1# show lldp info remote-device LLDP Remote Devices Information LocalPort --------1 2 | + | | ChassisId ------------------------Core-Cisco-1 Core-Cisco-2 PortId PortDescr SysName ------ --------- --------------Gig... Gig...

We display the LLDP neighbors attached to given ports. It shows details about neighbors.ProCurve-Edge-1# show lldp info remote-device 1-2 LLDP Remote Device Information Detail Local Port ChassisType ChassisId PortType PortId SysName System Descr M)... PortDescr : : : : : : : : : bridge, router : bridge, router 1 local Core-Cisco-1 local GigabitEthernet0/1 Cisco IOS Software, C6500 Software (C6500-IPSERVICESK9-

System Capabilities Supported System Capabilities Enabled Remote Management Address Type : ipv4 Address : 10.1.1.1

------------------------------------------------------------------------Local Port : ChassisType ChassisId PortType PortId SysName System Descr M)... PortDescr 2 : : : : : : : : bridge, router : bridge, router

local Core-Cisco-2 local GigabitEthernet0/1 Cisco IOS Software, C6500 Software (C6500-IPSERVICESK9-

System Capabilities Supported System Capabilities Enabled

Remote Management Address Type : ipv4 Address : 10.1.1.2

Checking Discovery info on a Cisco switchAs ProCurve switches do not send anymore CDP frames, a Cisco switch will not recognize ProCurve neighbors. Lets hope for a Cisco commitment to the IEEE LLDP standard.Core-Cisco-1#show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID Core-Cisco-2 Local Intrfce Gig 0/3 Holdtme 171 Capability R S I Platform Port ID WS-C6500-4 Gig0/3

VLAN configuration11- 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

IntroductionGlossaryThis chapter deals with port based VLANs that Cisco and HP ProCurve both support. Different names are used to describe similar concepts on both platforms. Cisco Trunk HP ProCurve Tagged What is it? A port that carries multiple VLANs using the 802.1q tag, for example an uplink, an IP phone port. A port that belongs to a unique VLAN and is untagged Defines the untagged VLAN of a 802.1q tagged port. Defaults to VLAN 1 on HP and Cisco

Access Native VLAN

Untagged -

Sample topology Edge/Access ports untagged in VLANs 10,20, 30 & 40Vlan 20 Vlan 30 Vlan 40

10.1.40.1/24 10.1.30.1/24 10.1.20.1/24 10.1.10.1/24 10.1.1.1/24 Vlan 1 Vlan 10

Cisco-1

Uplink 802.1q port tagged in VLANs 10,20, 30 & 40 and untagged in vlan 1

Procurve-1Vlan 20 Vlan 30 Vlan 40

10.1.40.2/24 10.1.30.2/24 10.1.20.2/24 Vlan 1 10.1.10.2/24 10.1.1.2/24 Vlan 10

VLAN configuration on Cisco CatalystStep 1: VLAN Creation Conf t vlan 10, 20, 30, 40 Step 2: Assignment of Access ports to VLANs interface range FastEthernet1/0/10 - 19 switchport access vlan 10 switchport mode access interface range FastEthernet1/0/20 - 29 switchport access vlan 20 switchport mode access interface range FastEthernet1/0/30 - 39 switchport access vlan 30 switchport mode access interface range FastEthernet1/0/40 - 48 switchport access vlan 40 switchport mode access

Step 3: Creation of 802.1q links (Cisco Trunk) 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). switchport trunk encapsulation dot1q By default, a Cisco trunk carries all VLANs. The allowed VLAN restricts transport of VLANs to the specified VLANs. switchport trunk allowed vlan 1,10,20,30,40 By default, a port is in access mode, i.e. it belongs to one VLAN only. switchport mode trunk Cisco also supports a proprietary negotiation protocol for the trunk named DTP (Dynamic Trunk Protoco