Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Application Notes for Configuring Avaya C363T RSTP to Interoperate with Extreme Networks MSTP to Support Avaya Communication Manager and Avaya G650 Media Gateway - Issue 1.0 Abstract These Application Notes describe the steps for configuring Rapid Spanning Tree Protocol (RSTP) to interoperate with Multiple Spanning Tree Protocol (MSTP 1 ) in a network environment consisting of an Avaya C363T-PWR Converged Stackable Switch and Extreme Networks switches. MSTP has the concept of regions and allows for multiple instances of Spanning Tree Protocol to be configured within a region. MSTP is backward compatible with Spanning Tree Protocol (802.1D) and Rapid Spanning Tree Protocol (802.1w) compliance bridges. 1 Multiple Spanning Tree Protocol (MSTP) is an implementation of IEEE 802.1S. 1 of 25

2 1. Introduction In an effort to construct a robust network infrastructure, both physical and logical redundancies are often introduced into the network, but resulting in the need for loop avoidance algorithms. In the realm of a Layer-2 data network, Spanning Tree Protocol (802.1D), Rapid Spanning Tree Protocol (802.1w), or Per VLAN Spanning Tree Protocol (PVSTP) is typically deployed as the mechanism to prevent such loops from cascading into a broadcast storm in a network. Each of these protocols has advantages and disadvantages. To improve resiliency and convergence time, Multiple Spanning Tree Protocol (MSTP) can be implemented in the network. MSTP is backwards compatible with network bridges supporting Spanning Tree Protocol (STP) and Rapid Spanning Tree Protocol (RSTP). These Application Notes describe a solution in implementing MSTP and RSTP to interoperate in a partially meshed 4-node network. Unlike other bridging protocols, MSTP has the concept of Regions. A common Region Name, Format Selector, and Revision Level logically group switches into a Region. This allows for greater scalability, since each region now defines the logical boundary of the spanning tree network. Therefore, each spanning tree instance converges separately and has its own root bridge. Figure 1 below illustrates the function of the MSTP Region. B2, B3, and B4 belong to a MSTP region as defined by the criteria mentioned earlier. A Common and Internal Spanning Tree (CIST) instance is run among these three bridges and a CIST Regional Root is elected. Figure 1: MSTP Region 2 of 25

3 From the perspective of bridge B1 (which is not part of a MSTP region), the whole MSTP region behaves as one virtual bridge. The B-Virtual bridge will take on the bridge priority and MAC address the CIST Regional Root Bridge for the purposes of Spanning Tree calculation with bridges outside of the MSTP region. Bridge Protocol Data Units (BPDUs) will be exchanged between B1 and the virtual bridge to calculate a Root Bridge, also known as the CIST Root for the entire network. Figure 2: CIST Regional Root Bridge In addition, one or more Multiple Spanning Tree Instance (MSTI) domains can be configured within the MSTP region to support VLANs or further partition VLAN(s) into multiple MSTI domains. Figure 3 below is an example of the upperfloor MSTI domain. This upperfloor MSTI runs a separate instance of the Spanning Tree protocol and elects its own MSTI Regional Root bridge. Figure 3: MSTI Regional Root 3 of 25

4 Figure 4 below illustrates the final state of the root bridge assignment. Note that B4 designated as both the CIST Regional Root and the MSTI Regional Root. It is also possible to have a single bridge within the MSTP region to serve as the root bridge for all three types of root bridges (CIST Root, CIST Regional Root, and MSTI Regional Root); however the opposite is not true as both the CIST Regional Root and MSTI Regional Root must be within the MSTP region. Figure 4: MSTI Regional Root The details of how CIST and MSTI communicate and construct BPDUs for interoperability with other spanning tree protocol are beyond the scope of this document. Please consult reference [6] for additional information. 4 of 25

5 2. Configuration Figure 5 illustrates the configuration used in these Application Notes. Figure 5: Sample Network Configuration 5 of 25

6 3. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration provided: Equipment Avaya S8500 Media Server with Avaya G650 Media Gateway Software/Firmware Avaya Communication Manager 3.1 (R ) Service Pack Avaya C363T-PWR Converged Stackable Switch Avaya 4620 SW IP Telephones (H.323) 2.3 Extreme Network BlackDiamond XOS Extreme Network BlackDiamond XOS Extreme Network BlackDiamond 8810 XOS of 25

7 4. Avaya Communication Manager There is no unique setup needed in Avaya Communication Manager to support MSTP interoperability or any feature(s) mentioned in this document. For detailed information on the installation, maintenance, and configuration of Avaya Communication Manager, please consult references [1] and [2]. 5. Configure the Extreme Networks Switches The following sections describe the configuration for the different Extreme Network switches in the sample configuration Configure the Extreme Networks BlackDiamond This section shows the necessary steps for configuring the BlackDiamond shown in the sample network. CIST must be configured first before MSTI can be configured. To avoid an accidental spanning tree loop, complete Steps 1-10 in Sections first and verify CIST information is as shown in Section 6 Step 4 before completing the remaining steps in each section. Step Description 1. Connect to the BlackDiamond Log in using the appropriate login and password. login: password: BD # 2. Make sure the ports are not already configured for other VLANs. Use the show port <port> info detail command to check the current configuration for the port. The following steps assume that all ports used in the sample configuration are not configured for any other VLAN. BD # show port 2:15-2:16,2:20 info detail 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional) BD # disable port 2:15-2:16,2:20 4. Create VLAN v171 for VoIP traffic, and create VLAN v173 for data traffic. BD # create vlan "V171" BD # configure vlan V171 tag 171 BD # configure vlan V171 ipaddress /24 BD # create vlan "V173" BD # configure vlan V173 tag 173 BD # configure vlan V173 ipaddress /24 BD # enable ipforwarding 7 of 25

8 Step Description 5. Assign ports to the appropriate VLAN(s). The default VLAN is used to carry BPDUs for the CIST ports for Avaya Media Server and Avaya G650 Media Gateway BD # config vlan v171 add port 2:1-4 untagged inter-switch ports BD # config vlan default add port 2:15-16,2:20 tagged BD # config vlan v171 add port 2:15-16,2:20 tagged BD # config vlan v173 add port 2:15-16,2:20 tagged 6. Assign an MSTP region name for the BlackDiamond The sample configuration uses buildinga as the MSTP region name. BD # configure mstp region buildinga 7. Configure the Common and Internal Spanning Tree (CIST) for the MSTP region. The sample configuration uses the default stpd domain s0 for the CIST. BD # disable stpd s0 auto-bind vlan Default BD # configure stpd s0 mode mstp cist 8. Assign the default VLAN ports to the CIST and configure the port connecting to Avaya 363T-PWR switch for dot1d operational mode. BD # enable stpd s0 auto-bind vlan Default BD # configure stpd s0 add vlan v171 ports 2:20 dot1d BD # configure stpd s0 add vlan v173 ports 2:20 dot1d 9. Configure the inter-switch links as point-to-point. BD # configure stpd s0 ports link-type point-to-point 2:15-16,2: Enable the CIST. BD # enable stpd s0 11. Configure a Multiple Spanning Tree Instance (MSTI) for the MSTP region. The sample configuration uses upperfloor for the MSTI. BD # create stpd upperfloor BD # configure stpd upperfloor mode mstp msti Assign ports to the upperfloor MSTI. BD # configure stpd upperfloor add vlan v171 ports 2:15-16 BD # configure stpd upperfloor add vlan v173 ports 2: of 25

9 Step Description 13. Configure the inter-switch links as point-to-point. BD # configure stpd upperfloor ports link-type point-to-point 2: Enable the upperfloor MSTI. BD # enable stpd upperfloor 15. Enable the inter-switch ports. BD # enable port 2:15-16,2: Enable diffserv examination for all ports used in the sample configuration. BD # enable diffserv examination ports 2:1-4,2:15-16,2: Save the configuration. BD # save 5.2. Configure the Extreme Network BlackDiamond This section shows the necessary steps for configuring the BlackDiamond shown in the sample network. Step Description 1. Connect to the BlackDiamond Log in using the appropriate login and password. login: password: BD # 2. Make sure the ports are not already configured for other VLANs. Use the show port <port> info detail command to check the current configuration for the port. The following steps assume that all ports used in the sample configuration are not configured for any other VLAN. BD # show port 8:1,8:5-6 info detail 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional). BD # disable port 8:1,8:5-6 9 of 25

10 Step Description 4. Create VLAN v171 for VoIP traffic, and create VLAN v173 for data traffic. BD # create vlan "V171" BD # configure vlan V171 tag 171 BD # create vlan "V173" BD # configure vlan V173 tag Assign ports to the appropriate VLAN(s). The default VLAN is used to carry BPDUs for the CIST inter-switch ports BD # config vlan default add port 8:1,8:5-6 tagged BD # config vlan v171 add port 8:1,8:5-6 tagged BD # config vlan v173 add port 8:1,8:5-6 tagged 6. Assign an MSTP region name for the BlackDiamond The sample configuration uses buildinga as the MSTP region name. BD # configure mstp region buildinga 7. Configure the Common and Internal Spanning Tree (CIST) for the MSTP region. The sample configuration uses the default stpd domain s0 for the CIST. BD # disable stpd s0 auto-bind vlan Default BD # configure stpd s0 mode mstp cist 8. Assign the default VLAN ports to the CIST and configure the port connecting to Avaya 363T-PWR switch for dot1d operational mode. BD # enable stpd s0 auto-bind vlan Default BD # configure stpd s0 add vlan v171 ports 8:1 dot1d BD # configure stpd s0 add vlan v173 ports 8:1 dot1d 9. Configure the inter-switch links as point-to-point. BD # configure stpd s0 ports link-type point-to-point 8:1,8: Enable the CIST. BD # enable stpd s0 11. Configure a Multiple Spanning Tree Instance (MSTI) for the MSTP region. The sample configuration uses upperfloor for the MSTI. BD # create stpd upperfloor BD # configure stpd upperfloor mode mstp msti 1 10 of 25

11 Step Description 12. Assign ports to the upperfloor MSTI. BD # configure stpd upperfloor add vlan v171 ports 8:5-6 BD # configure stpd upperfloor add vlan v173 ports 8: Configure the inter-switch links as point-to-point. BD # configure stpd upperfloor ports link-type point-to-point 8: Enable the MSTI. BD # enable stpd upperfloor 15. Enable the inter-switch ports. BD # enable port 8:1,8: Enable diffserv examination for all ports used in the sample configuration. BD # enable diffserv examination ports 8:1,8: Save the configuration. BD # save 5.3. Configure the Extreme Network BlackDiamond 8810 This section shows the necessary steps for configuring the BlackDiamond 8810 shown in the sample network. Step Description 1. Connect to the BlackDiamond Log in using the appropriate login and password. login: password: BD-8810 # 2. Make sure the ports are not already configured for other VLANs. Use the show port <port> info detail command to check the current configuration for the port. The following steps assume that all ports used in the sample configuration are not configured for any other VLAN. BD-8810 # show port 1:5-6 info detail 11 of 25

12 Step Description 3. Disable the uplink ports that will be used to prevent accidental broadcast storms from occurring (optional). BD-8810 # disable port 1: Create VLAN v171 for VoIP traffic, and create VLAN v173 for data traffic. BD-8810 # create vlan "V171" BD-8810 # configure vlan V171 tag 171 BD-8810 # create vlan "V173" BD-8810 # configure vlan V173 tag Assign ports to the appropriate VLAN(s). The default VLAN is used to carry BPDUs for the CIST port for Avaya IP Telephone and PC BD-8810 # config vlan v171 add port 1:1 tagged BD-8810 # config vlan v173 add port 1:1-2 untagged inter-switch ports BD-8810 # config vlan default add port 1:5-6 tagged BD-8810 # config vlan v171 add port 1:5-6 tagged BD-8810 # config vlan v173 add port 1:5-6 tagged 6. Assign an MSTP region name for the BlackDiamond The sample configuration uses buildinga as the MSTP region name. BD-8810 # configure mstp region buildinga 7. Configure the Common and Internal Spanning Tree (CIST) for the MSTP region. The sample configuration uses the default stpd domain s0 for the CIST. BD-8810 # disable stpd s0 auto-bind vlan Default BD-8810 # configure stpd s0 mode mstp cist 8. Assign the default VLAN ports to the CIST. BD-8810 # enable stpd s0 auto-bind vlan Default 9. Configure the inter-switch links as point-to-point. BD-8810 # configure stpd s0 ports link-type point-to-point 1: Enable the CIST. BD-8810 # enable stpd s0 12 of 25

13 Step Description 11. Configure a Multiple Spanning Tree Instance (MSTI) for the MSTP region. The sample configuration uses upperfloor for the MSTI. BD-8810 # create stpd upperfloor BD-8810 # configure stpd upperfloor mode mstp msti Assign ports to the upperfloor MSTI. BD-8810 # configure stpd upperfloor add vlan v171 ports 1:5-6 BD-8810 # configure stpd upperfloor add vlan v173 ports 1: Configure the inter-switch links as point-to-point. BD-8810 # configure stpd upperfloor ports link-type point-to-point 1: Enable the MSTI. BD-8810 # enable stpd upperfloor 15. Enable the inter-switch ports. BD-8810 # enable port 1: Enable diffserv examination for all ports used in the sample configuration. BD-8810 # enable diffserv examination ports 1:1-2,1: Save the configuration. BD-8810 # save 5.4. Configure the Avaya C363T-PWR Converged Stackable Switch This section shows the necessary steps for configuring the Avaya C363T-PWR Converged Stackable Switch shown in the sample network. Step Description 1. From a terminal emulation program, connect to the Avaya C363T-PWR Converged Stackable Switch via the console port with the following terminal settings. Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 13 of 25

14 Step Description 2. Create VLAN v171 for the Avaya IP Telephone, and VLAN v173 for the data traffic. Assign these VLANs to the appropriate ports. C360-1(super)# set vlan 171 name v171 C360-1(super)# set vlan 173 name v173 C360-1(super)# set port vlan 173 1/1 C360-1(super)# set port vlan 173 1/2 C360-1(super)# set trunk 1/1 dot1q C360-1(super)# set trunk 1/5 dot1q C360-1(super)# set trunk 1/7 dot1q C360-1(super)# set port vlan-binding-mode 1/1 bind-to-configured C360-1(super)# set port vlan-binding-mode 1/5 bind-to-configured C360-1(super)# set port vlan-binding-mode 1/7 bind-to-configured 3. Configure Spanning Tree Protocol. C360-1(super)# set spantree version rapid-spanning-tree C360-1(super)# set spantree enable 14 of 25

15 6. Verification Steps The following steps may be used to verify the configuration: Step Description 1. Place calls using the Avaya IP Telephones. 2. Verify the PCs can ping each other and the Avaya IP Telephones. 3. Use the show stpd command on the Extreme Network switches to display the status of all stpd domains. Verify that the MSTP Region Name is correct. Verify that the number of MSTI instances is correct. Verify that both the CIST and MSTI domains are enabled. The following is the show stpd output for the BlackDiamond BD # show stpd MSTP Global Configuration: MSTP Region Name : buildinga MSTP Format Identifier : 0 MSTP Revision Level : 3 Common and Internal Spanning Tree (CIST) : s0 Total Number of MST Instances (MSTI) : 1 Name Tag Flags Ports Bridge ID Designated Root Rt Port Rt Cost s EM d a330 2:16 4 upperfloor 0000 EI d a330 2:16 4 Total number of STPDs: 2 Flags: (C) Topology Change, (D) Disable, (E) Enable, (R) Rapid Root Failover (T) Topology Change Detected, (M) MSTP CIST, (I) MSTP MSTI 15 of 25

16 4. Use the show stpd <stpd domain> command on the Extreme Network switches to display the spanning tree domain information for the CIST domain. Verify that the spanning tree domain is enabled. Verify that the ports are correct. Verify that the participating VLANs are correct. Verify that the CIST Root is correct (all bridges in the network should have the same information). Verify that the CIST Regional Root is correct (all bridges in the same region should have the same information). Below is the show stpd s0 output from the BlackDiamond Note the following: The CIST Root is the bridge with the lowest MAC address (Avaya C363T-PWR Converged Stackable Switch) The CIST Regional Root is the bridge with the lowest MAC address (the BlackDiamond 10808) within the Region buildinga. BD # show stpd s0 Stpd: s0 Stp: ENABLED Number of Ports: 4 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: CIST 802.1Q Tag: (none) Ports: 2:15,2:16,2:20 Participating Vlans: Default,v171,v173 Auto-bind Vlans: Default Bridge Priority: BridgeID: 80:00:00:04:96:1d:65:00 Designated root: 80:00:00:04:96:10:a3:30 CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 19 Internal RootPathCost: 4 Root Port: 2:16 MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 19 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 8 Time Since Last Topology Change: 51736s The following is the show stpd s0 output from the BlackDiamond of 25

17 BD # show stpd s0 Stpd: s0 Stp: ENABLED Number of Ports: 3 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: CIST 802.1Q Tag: (none) Ports: 8:1,8:5,8:6 Participating Vlans: Default,v171,v173 Auto-bind Vlans: Default Bridge Priority: BridgeID: 80:00:00:04:96:10:a3:30 Designated root: 80:00:00:04:0d:3c:32:ff CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 19 Internal RootPathCost: 0 Root Port: 8:1 MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 20 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 25 Time Since Last Topology Change: 51941s The following is the show stpd s0 output from the BlackDiamond Aspen # show stpd s0 Stpd: s0 Stp: ENABLED Number of Ports: 2 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: CIST 802.1Q Tag: (none) Ports: 1:5,1:6 Participating Vlans: Default Auto-bind Vlans: Default Bridge Priority: BridgeID: 80:00:00:04:96:1f:a1:a0 Designated root: 80:00:00:04:96:10:a3:30 CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 19 Internal RootPathCost: 4 Root Port: 1:5 MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 19 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 7 Time Since Last Topology Change: 52062s Aspen # 5. Use the show stpd <stpd domain> ports command on the Extreme Network switches to display the state of the spanning tree ports. Verify that the port is set to 802.1D mode (default). Verify that all ports are either forwarding or blocking. Verify that the port is set to point-to-point. Verify that the port connected to another bridge outside the Region is marked as Boundary. Verify that the port connected to another bridge inside the Region is mark as Internal. The following is the show stpd s0 port output from the BlackDiamond of 25

18 BD # show stpd s0 ports Port Mode State Cost Flags Priority Port ID Designated Bridge 2: D FORWARDING 4 edbb-m--i f 80:00:00:04:96:1d:65:00 2: D FORWARDING 4 erbb-m--i :00:00:04:96:10:a3:30 2: D BLOCKING 19 eapp-m--b :00:00:04:0d:3c:32:ff Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal BD # The following is the show stpd s0 port output from the BlackDiamond BD # show stpd "s0" ports Port Mode State Cost Flags Priority Port ID Designated Bridge 8: D FORWARDING 19 erpp-m--b :00:00:04:0d:3c:32:ff 8: D FORWARDING 4 edpp-m--i :00:00:04:96:10:a3:30 8: D FORWARDING 4 edpp-m--i :00:00:04:96:10:a3:30 Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal BD # The following is the show stpd s0 port output from the BlackDiamond Aspen # show s0 ports Port Mode State Cost Flags Priority Port ID Designated Bridge 1: D FORWARDING 4 erbb-m--i :00:00:04:96:10:a3:30 1: D BLOCKING 4 eabb-m--i :00:00:04:96:1d:65:00 Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal Aspen # 18 of 25

19 6. Use the show stpd <stpd domain> command on the Extreme Networks switches to display the spanning tree domain information for the MSTI domain. Verify that the spanning tree domain is enabled. Verify that the ports are correct. Verify that the participating VLANs are correct. Verify that the CIST Root is correct. Verify that the CIST Regional Root is correct (all bridges in the same region should have the same information). Verify that the MSTI Regional Root is correct (all bridges in the same MSTI domain should have the same information). Below is the show stpd upperfloor output from the BlackDiamond Note the following: The CIST Root is the bridge with the lowest MAC address (Avaya C363T-PWR Converged Stackable Switch) The CIST Regional Root is the bridge with the lowest MAC address (the BlackDiamond 10808) within the Region buildinga. The MSTI Regional Root is the bridge with the lowest MAC address for MSTI domain in Region buildinga. BD # show stpd "upperfloor" Stpd: upperfloor Stp: ENABLED Number of Ports: 2 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: MSTI Q Tag: (none) Ports: 2:15,2:16 Participating Vlans: v171,v173 Auto-bind Vlans: (none) Bridge Priority: BridgeID: 80:00:00:04:96:1d:65:00 Designated root: 80:00:00:04:96:10:a3:30 CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 MSTI Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 0 Internal RootPathCost: 4 Root Port: 2:16 Master Port: ---- MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 19 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 7 Time Since Last Topology Change: 51790s BD # The following is the show stpd upperfloor output from the BlackDiamond of 25

20 BD # show stpd "upperfloor" Stpd: upperfloor Stp: ENABLED Number of Ports: 2 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: MSTI Q Tag: (none) Ports: 8:5,8:6 Participating Vlans: v171,v173 Auto-bind Vlans: (none) Bridge Priority: BridgeID: 80:00:00:04:96:10:a3:30 Designated root: 80:00:00:04:96:10:a3:30 CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 MSTI Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 0 Internal RootPathCost: 0 Root Port: ---- Master Port: ---- MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 20 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 6 Time Since Last Topology Change: 51981s BD # The following is the show stpd upperfloor output from the BlackDiamond Aspen # show "upperfloor" Stpd: upperfloor Stp: ENABLED Number of Ports: 2 Rapid Root Failover: Disabled Operational Mode: MSTP Default Binding Mode: 802.1D MSTI Instance: MSTI Q Tag: (none) Ports: 1:5,1:6 Participating Vlans: v171,v173 Auto-bind Vlans: (none) Bridge Priority: BridgeID: 80:00:00:04:96:1f:a1:a0 Designated root: 80:00:00:04:96:10:a3:30 CIST Root: 80:00:00:04:0d:3c:32:ff CIST Regional Root: 80:00:00:04:96:10:a3:30 MSTI Regional Root: 80:00:00:04:96:10:a3:30 External RootPathCost: 0 Internal RootPathCost: 4 Root Port: 1:5 Master Port: ---- MaxAge: 20s HelloTime: 2s ForwardDelay: 15s CfgBrMaxAge: 20s CfgBrHelloTime: 2s CfgBrForwardDelay: 15s MaxHopCount: 19 CfgMaxHopCount: 20 Topology Change Time: 35s Hold time: 1s Topology Change Detected: FALSE Topology Change: FALSE Number of Topology Changes: 3 Time Since Last Topology Change: 52135s Aspen # 7. Use the show stpd <stpd domain> ports command to display the state of the spanning tree ports. Verify that the port is set to 802.1D mode (default). Verify that all ports are either forwarding or blocking. Verify that the port is set to point-to-point. Verify that the port connected to another bridge inside the region is mark as Internal. The following is the show stpd upperfloor port output from the BlackDiamond of 25

21 BD # show stpd "upperfloor" port Port Mode State Cost Flags Priority Port ID Designated Bridge 2: D FORWARDING 4 edpp-m--i f 80:00:00:04:96:1d:65:00 2: D FORWARDING 4 erpp-m--i :00:00:04:96:10:a3:30 Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal BD # The following is the show stpd upperfloor port output from the BlackDiamond BD # show stpd "upperfloor" ports Port Mode State Cost Flags Priority Port ID Designated Bridge 8: D FORWARDING 4 edpp-m--i :00:00:04:96:10:a3:30 8: D FORWARDING 4 edpp-m--i :00:00:04:96:10:a3:30 Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal BD # The following is the show stpd upperfloor port output from the BlackDiamond 8810 Aspen # show "upperfloor" ports Port Mode State Cost Flags Priority Port ID Designated Bridge 1: D FORWARDING 4 erpp-m--i :00:00:04:96:10:a3:30 1: D BLOCKING 4 eapp-m--i :00:00:04:96:1d:65:00 Total Ports: Flags: : e=enable, d=disable 2: (Port role) R=Root, D=Designated, A=Alternate, B=Backup, M=Master 3: (Config type) b=broadcast, p=point-to-point, e=edge, a=auto 4: (Oper. type) b=broadcast, p=point-to-point, e=edge 5: p=proposing, a=agree 6: (partner mode) d = 802.1d, w = 802.1w, m = mstp 7: i = edgeport inconsistency 8: S = edgeport safe guard active s = edgeport safe guard configured but inactive 9: B = Boundary, I = Internal Aspen # 21 of 25

22 8. Use the show port <port> info detail command on the Extreme Networks switches to display the information for a port. Verify that the correct VLAN(s) is assigned to the port with the appropriate tag. Verify that the port belong to the appropriate spanning tree domain. Verify that the Ingress IPTOS Examination is enabled. Below is the show port output for port 2:15 on the BlackDiamond BD # show port 2:15 info de Port: 2:15 Virtual-router: VR-Default Type: UTP Random Early drop: Unsupported Admin state: Enabled with auto-speed sensing auto-duplex Link State: Active, 1Gbps, full-duplex Link Counter: Up 0 time(s) VLAN cfg: Name: Default, 802.1Q Tag = 1, MAC-limit = No-limit, Virtual ro uter: VR-Default Name: v171, 802.1Q Tag = 171, MAC-limit = No-limit, Virtual rou ter: VR-Default Name: v173, 802.1Q Tag = 173, MAC-limit = No-limit, Virtual rou ter: VR-Default BD # STP cfg: s0(enable), Tag=(none), Mode=802.1D, State=FORWARDING upperfloor(enable), Tag=(none), Mode=802.1D, State=FORWARDING Protocol: Trunking: Load sharing is not enabled. EDP: Enabled ELSM: Disabled Learning: Enabled Unicast Flooding: Enabled Multicast Flooding: Enabled Broadcast Flooding: Enabled Jumbo: Disabled QoS Profile: None configured Aggregate Queue: QP0 MinBw = 0% MaxBw = 100% Pri = 8 Queue: QP1 MinBw = 0% MaxBw = 100% Pri = 1 QP2 MinBw = 0% MaxBw = 100% Pri = 2 QP3 MinBw = 0% MaxBw = 100% Pri = 3 QP4 MinBw = 0% MaxBw = 100% Pri = 4 QP5 MinBw = 0% MaxBw = 100% Pri = 5 QP6 MinBw = 0% MaxBw = 100% Pri = 6 QP7 MinBw = 0% MaxBw = 100% Pri = 7 QP8 MinBw = 0% MaxBw = 100% Pri = 8 Ingress Rate Shaping : Unsupported Ingress IPTOS Examination: Enabled Egress IPTOS Replacement: Disabled Egress 802.1p Replacement: Disabled NetLogin: Disabled NetLogin port mode: Port based VLANs Smart redundancy: Enabled Software redundant port: Disabled Preferred medium: Fiber 22 of 25

23 9. Use the show spantree command on the C363T-PWR Converged Stackable Switch to display the spanning tree information. Verify that the spanning tree version is set to rapid spanning tree. Verify that all ports are either forwarding or blocking. C360-1(super)# show spantree Spanning tree state is enabled Designated Root: d-3c-32-ff Designated Root Priority: Designated Root Cost: 0 Designated Root Port: No root port, Bridge is Designated root Root Max Age: 20 Hello Time: 2 Root Forward Delay: 15 Bridge ID MAC ADDR: d-3c-32-ff Bridge ID priority: Bridge Max Age: 20 Bridge Hello Time: 2 Bridge Forward Delay: 15 Tx Hold Count 3 Spanning Tree Version is rapid spanning tree Spanning Tree Default Path Costs is according to common spanning tree Port State Cost Priority /1 Forwarding /2 Forwarding /3 not-connected /4 not-connected /5 Forwarding /6 not-connected /7 Forwarding /8 not-connected Use the show vlan command on the C363T-PWR Converged Stackable Switch to display all the configured VLANs. C360-1(super)# show vlan VLAN ID Vlan-name V1 171 v v173 Total number of VLANs: 3 C360-1(super)# 23 of 25

24 11. Use the show trunk command on the C363T-PWR Converged Stackable Switch to display Trunking information. Verify that the inter-switch links are set as dot1q trunks with the correct binding mode. C360-1(super)# show trunk Port Mode Binding mode Native vlan /1 dot1q bound to configured vlans 173 1/2 off bound to configured vlans 173 1/3 off statically bound 1 1/4 off statically bound 1 1/5 dot1q bound to configured vlans 1 1/6 off statically bound 1 1/7 dot1q bound to configured vlans 1 1/8 off statically bound 1 7. Conclusion These Application Notes have described the administration steps required to configure the Multiple Spanning Tree Protocol in Extreme Networks switches to interoperate with Rapid Spanning Tree Protocol in an Avaya C363T-PWR Converged Stackable Switch. Avaya IP Telephones using DHCP were verified to work successfully across the MSTP-RSTP environment. Quality of Service was also verified successfully using a traffic generator. The MSTP-RSTP converged successfully in a timely manner when different links were randomly disconnected and restored. 8. Additional References [1] Administrator Guide for Avaya Communication Manager, Doc # , Issue 1, February 2006 [2] Avaya Communication Manager Advanced Administration Quick Reference, Doc # , Issue 2, June 2005 Release 3.0 [3] Administration for Network Connectivity for Avaya Communication Manager, Doc # , Issue 6, May 2003 [4] Avaya Application Solutions: IP Telephony Deployment Guide, Doc# , Issue 4.3, February 2006 [5] ExtremeWare XOS Concepts Guide, Software Version 11.4, Part Number: Rev 01, March 2006 [6] ExtremeWare XOS Command Reference Guide, Software Version 11.4, Part Number: Rev 01, March 2006 [7] ExtremeWare CommandReference Guide, Software Version 7.5, Part Number: Rev. 01, October 2005 Product documentation for Avaya products may be found at Product documentation for Extreme Networks products may be found at 24 of 25

25 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at 25 of 25