Abstract. Avaya Solution & Interoperability Test Lab

Transcription

1 Avaya Solution & Interoperability Test Lab Configuring Routing Protocol Redistribution Between Avaya P882 Gigabit Ethernet Switch, Enterasys Vertical Horizon, and HP Procurve Routers - Issue 1.0 Abstract Route redistribution is required when two systems running different routing protocols need to be interconnected. These Application Notes describe how to configure routing protocol redistribution between an Avaya P882 Gigabit Ethernet Switch and other third party vendors. The example configuration described specifically addresses redistribution of local, RIPv2 and OSPF routes between Avaya P882, HP Procurve 5304XL and Enterasys Networks Vertical Horizon VH-2402-L3 Routers. 1 of 26

2 1. Introduction The Route Redistribution feature introduced in Avaya 80 Series Switch Supervisor Module Version 6.0 enhances the existing routing policy implementation by giving the user added control over the exchange of routing information between different routing protocols. Redistribution filters can be defined per protocol, and can be configured based on standard access-lists or without the use of access-lists. If route redistribution is used without access-lists, all routes from the source protocol will be redistributed into the destination protocol. If route redistribution is used with access-lists, the user can control the distribution of specific routes using standard permit and deny access-list indices. The sample configuration depicted in Figure 1 demonstrates how routing redistribution can be used to permit or deny specific route exchanges between differing protocols. The diagram shows the P882 switch acting as an Autonomous System Border Router (ASBR) since it is handing area ID , which requires interconnection with a backbone in order to interconnect with other autonomous systems. Avaya (TM) 4624 IP Telephone x44004 DHCP Avaya(TM) S8300 Server with a G700 Gateway VLAN /24 HP Interfaces: VLAN /24 VLAN /30 A1 1/2 VLAN /24 1/1 VLAN /24 3/7 D2 5/3 Avaya (TM) 4612 IP Telephone x44003 DHCP HP Procurve Switch 5304XL OSPF Area ID /2 Avaya(TM) P882 Gigabit Ethernet Switch ASBR RIP v2 Networks 25 P882 Interfaces and Routes: VLAN /24 - OSPF VLAN /30 - OSPF VLAN /30 - RIP v2 VLAN /24 - Local Route VLAN /24 - Local Route VLAN /24 1 VLAN /24 Target PC Local Route 3/9 Local Route 3/8 VLAN /24 Target PC VLAN 54 Enterasys /24 Vertical Horizon VH-2402-L3 OSPF Backbone DHCP/TFTP Server Enterasys Interfaces: VLAN /30 VLAN / BaseT 1000BaseSX 100BaseTX Figure 1: Route Redistribution Sample Configuration 2 of 26

3 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya S8300 Media Server with a G700 Media Gateway Communication Manager 1.3 Avaya P882 Gigabit Ethernet Switch Version 6.0 Enterasys Vertical Horizon VH-2402-L3 Switch 1.0 HP Procurve Switch 5304XL E Avaya P882 Switch Configuration via the Web Agent The following procedures depict the core steps involved in configuring the Avaya P882 Gigabit Ethernet Switch via the Web Agent (or web interface). For brevity, only excerpts of the overall configuration are shown. For additional details on configuring the P882 switch, please reference the Avaya P882/P580 Version 6.0 User Guide Create All Required VLANs To create a VLAN, navigate to MultiService Switch L2 Switching VLANs Configuration CREATE. The Create VLAN window opens (Figure 2). Enter a unique name and ID for the new VLAN to be created (e.g. Name=vlan10, ID=10) in the highlighted fields and click APPLY. Figure 2: Create VLAN Window 3 of 26

4 3.2. Bind All VLANs to Their Corresponding Physical Ports To associate a VLAN to a physical port, navigate to MultiService Switch Modules & Ports Configuration. The Module Information window opens (Figure 3). Click on the switch ports link under the Switch Ports column corresponding to the module whose port is to be modified. For example, to modify a port on the M8024R-100TX in Module 3, click on the 24 in that row for that module. The Switch Ports window opens (Figure 4). Figure 3: Module Information Window Under the Name column, click on the specific port to be modified on the module. For example, to modify Port 8 on Module 3, the administrator would scroll down to port 3.8 under the Port column and click on Port 3.8 under the Name column. The Switch Port Configuration window for the chosen port opens (Figure 5) Figure 4: Switch Ports Window (Abbreviated) 4 of 26

5 Select the VLAN to be bound to the port from the Port VLAN drop-down menu. For example, to bind VLAN 56 to Port 3/8, the user would select the name for VLAN 56 (e.g. vlan56) and click APPLY. Figure 5: Switch Port Configuration 5 of 26

6 3.3. Create the Necessary Layer 3 Interfaces for Each VLAN To create a Layer 3 router interface for a particular VLAN, navigate to MultiService Switch Routing IP Configuration Interfaces CREATE. The Add IP Interface window opens (Figure 6). Enter a unique interface name, VLAN, Network Address and Mask for the new interface to be created (e.g. Name=vlan53, VLAN=53, Network Address= , MASK= ) in the highlighted fields and click APPLY. Note: If the interface will be using RIP, this can enabled from the RIP drop-down menu. See Figure 6. The procedure for enabling OSPF is slightly different. Figure 6: Add IP Interface Window 6 of 26

7 3.4. Enable OSPF Routing on Required Interfaces Note: Interfaces being assigned to OSPF must be disabled or shut down first. If the backbone area is not used, the correct area ID must be assigned to the interface before enabling OSPF. Navigate to MultiService Switch Routing IP Configuration Interfaces. The IP Interfaces window opens (Figure 7). Under the Select column, select the interface on which OSPF will be enabled. Select DOWN under the Admin. State column and click APPLY. Figure 7: IP Interfaces Window 7 of 26

8 Administer OSPF on the DOWN interfaces (Figure 8). Under the Select column, select the interface on which OSPF will be enabled. Select Enable under the OSPF column and click APPLY. Figure 8: IP Interfaces (Abbreviated) 8 of 26

9 Navigate to MultiService Switch Routing IP OSPF Global Configuration. The OSPF Global Configuration window opens (Figure 9). Select Enable from the OSPF dropdown menu. Enter a unique Router ID for the switch (e.g ) and click APPLY. Figure 9: OSPF Global Configuration Window Create Area required for the sample configuration. Navigate to MultiService Switch Routing IP OSPF Areas CREATE. The Add OSPF Area window opens (Figure 10). Enter a unique Area ID for the switch interfaces (e.g ). Select Not-so-stubby from the Area Type drop-down menu and click APPLY. Figure 10: Add OSPF Area Window 9 of 26

10 Assign area to the required OSPF enabled interfaces. Navigate to MultiService Switch Routing IP OSPF Interfaces. The OSPF Interfaces window opens (Figure 11). Select the interfaces to be modified under the Select column. Change the Area drop-down menus for the interfaces to indicate the area of choice (e.g ) and click APPLY. The OSPF interfaces are now members of area Figure 11: OSPF Interfaces Window After OSPF has been enabled and all areas have been assigned to OSPF interfaces, they must be enabled. Navigate to MultiService Switch Routing IP Configuration Interfaces. The IP Interfaces window opens (Figure 12). Under the Select column, select the interface on which OSPF will be enabled. Select UP under the Admin. State column and click APPLY. Figure 12: IP Interfaces Window 10 of 26

11 3.5. Enable RIPv2 Routing on Required Interfaces Note: RIP is enabled globally by default, so the administrator only needs to apply the service to select router interfaces. Navigate to MultiService Switch Routing IP Configuration Interfaces. The IP Interfaces window opens (Figure 13). Under the Select column, select the interface on which RIP will be enabled. Select Enable under the RIP column and click APPLY. Figure 13: IP Interfaces Window (Abbreviated) Force all RIP enabled interfaces to send and receive RIPv2. Navigate to MultiService Switch Routing IP RIP Interfaces. The RIP Interfaces window opens (Figure 14). Under the Select column, select the RIP interface to be modified. Select V2 under the Send Version and Receive Version columns and click APPLY. Figure 14: RIP Interfaces Window 11 of 26

12 3.6. Configure Route Redistribution The standard access-lists used for routing redistribution should not be enabled via the accessgroup command because they will impact packet forwarding. They should be reserved for use in the IP redistribute list only. The standard access lists used for route redistribution, like the standard access lists applied for packet forwarding, use an implicit permit all statement at the end of every list. This is why only deny statements are used in these Application Notes for specific routes. However, it should be noted that administrators may choose the opposite approach by creating a deny all statement in the last index position of the list, which would block all routes from being redistributed. It would then be the responsibility of the system administrator to create individual permit statements for each route to be redistributed based on the applied filter. These Application Notes demonstrate two ways to apply route redistribution filters. The first way is redistribution without the use of access lists and the second is redistribution with the use of access lists. Example #1 Route Redistribution without access lists Create filters without using access lists to redistribute routing information between all available routing protocols. Navigate to MultiService Switch Routing IP Configuration IP Redistribute List CREATE. The Add IP Redistribute List Entry window opens (Figure 15). Create a rule allowing all OSPF learned routes to be redistributed into RIP. Change the Source Protocol drop-down menu to Ospf and the Dest Protocol drop-down menu to Rip and click CREATE. Figure 15: Add IP Redistribute List Entry Window Repeat the procedure for the remaining 5 combinations: Source Protocol=Local, Dest Protocol=Rip Source Protocol=Static, Dest Protocol=Rip Source Protocol=Rip, Dest Protocol=Ospf Source Protocol=Local, Dest Protocol=Ospf Source Protocol=Static, Dest Protocol=Ospf 12 of 26

13 Once complete, the following Redistribute filters will allow exchange of routing information between all protocols. See Figure 16. Figure 16: IP Redistribute List Entries Example #2 Route Redistribution with access lists Create two access lists. The first access list will be used to deny the local route from being redistributed into OSPF. Navigate to MultiService Switch Routing IP Configuration Access Lists Create Standard. The IP Standard Access Rule Creation window opens (Figure 17). Enter a unique Access List Name for the list (e.g. Blk56toOSPF). Enter 1 in the Access Rule Index field because this is the first entry for the new list. Select Deny/Filter from the Access Type drop-down menu. Enter the subnet route to be blocked from redistribution in the Source Address field (e.g ) and the corresponding Source Network Wildcard (e.g ) and click APPLY. Figure 17: IP Standard Access Rule Creation Window 13 of 26

14 The second access list will be used to deny the local route from being redistributed into RIP. Navigate to MultiService Switch Routing IP Configuration Access Lists Create Standard. The IP Standard Access Rule Creation window opens (Figure 18). Enter a unique Access List Name for the list (e.g. Blk55toRIP). Enter 1 in the Access Rule Index field because this is the first entry for the new list. Select Deny/Filter from the Access Type drop-down menu. Enter the subnet route to be blocked from redistribution in the Source Address field (e.g ) and the corresponding Source Network Wildcard (e.g ) and click APPLY. Figure 18: IP Standard Access Rule Creation Window Apply the newly created access lists to the IP Redistribute List. Navigate to MultiService Switch Routing IP Configuration IP Redistribute List. The IP Redistribute List Entries window opens (Figure 19). Select the filters to be modified under the Select column. Select the applicable access lists (Blk55toRIP for Local to Rip and Blk56toOSPF for Local to Ospf) to use for each filter under the Access List column and click APPLY. Figure 19: IP Redistribute List Entries 14 of 26

15 3.7. Create a DHCP Server for DHCP Relay Agent Requests Navigate to MultiService Switch Routing IP Configuration BOOTP/DHCP Servers CREATE. The Add BOOTP/DHCP Server Entry window opens (Figure 20). Enter the IP Address of the DHCP server (e.g ) and click APPLY. Figure 20: Add BOOTP/DHCP Server Entry Window 4. Enterasys VH-2402-L3 Switch Configuration 4.1. Create All Required VLANs Log into the VH-2402-L3 switch via the console port. Use <Tab> to navigate to the VLANs option and press <Enter> (Figure 21). VH-2402-L3 Local Management Main Menu Basic Setup: Switch Information IP Setup Remote Management Setup Switch Settings Configure Ports Setup User Accounts Serial Port Settings Utilities Network Monitoring Save Changes Reboot Logout Advanced Setup: Spanning Tree Forwarding Filtering Priority Mirroring Multicasting VLANs Port Trunking Layer 3 IP Networking ******************************************************************************* Figure 21: Main Menu 15 of 26

16 Use <Tab> to navigate to the Edit 802.1Q VLANs option and press <Enter> (Figure 22). VLAN Menu Edit 802.1Q VLANs Configure 802.1Q Port Settings ******************************************************************************* Figure 22: VLAN Menu Add VLAN 54 to port 25 untagged as depicted (Figure 23). Select APPLY and press <Enter>. Edit 802.1Q VLANs Action: <Add/Modify> VID:[54 ] VLAN Name:[vlan54 ] Total Entries:7 Port 1 to 8 9 to to Membership (E/F/-): [ ][ ][ ] [E] [-] Tagging (U/T) : [TTTTTTTT][TTTTTTTT][TTTTTTTT] [U] [T] APPLY VID VLAN Name 1 to 8 9 to to DEFAULT_VLAN FFFFFFFF FFFFFFFF FFFFFFFF F F TTTTTTTT TTTTTTTT TTTTTTTT T T 44 DHCP_Server TTTTTTTT TTTTTTTT TTTTTTTT T T 208 Management TTTTTTTT TTTTTTTT TTTTTTTT T T 209 Data_Main EEEEEEEE EEEEEEEE EEEE-E-E - - UUUUUUUU UUUUUUUU UUUUTUTU T T 210 Voice_Main EEEEEEEE EEEEEEEE EEEEE-EE - - TTTTTTTT TTTTTTTT TTTTUTUT T T ******************************************************************************* Figure 23: Edit 802.1Q VLANs Menu 16 of 26

17 Add VLAN 100 to port 1 untagged as depicted (Figure 24). Select APPLY and press <Enter>. Edit 802.1Q VLANs Action: <Add/Modify> VID:[100 ] VLAN Name:[vlan100 ] Total Entries:8 Port 1 to 8 9 to to Membership (E/F/-): [E ][ ][ ] [-] [-] Tagging (U/T) : [UTTTTTTT][TTTTTTTT][TTTTTTTT] [T] [T] APPLY VID VLAN Name 1 to 8 9 to to DEFAULT_VLAN FFFFFFFF FFFFFFFF FFFFFFFF F F TTTTTTTT TTTTTTTT TTTTTTTT T T 44 DHCP_Server TTTTTTTT TTTTTTTT TTTTTTTT T T 54 vlan E - TTTTTTTT TTTTTTTT TTTTTTTT U T 208 Management TTTTTTTT TTTTTTTT TTTTTTTT T T 209 Data_Main EEEEEEEE EEEEEEEE EEEE-E-E - - UUUUUUUU UUUUUUUU UUUUTUTU T T ******************************************************************************* Figure 24: Edit 802.1Q VLANs Menu 4.2. Bind All VLANs to Their Corresponding Physical Ports Enter the Configure 802.1Q Port Settings menu from the VLAN menu (Figure 25). VLAN Menu Edit 802.1Q VLANs Configure 802.1Q Port Settings ******************************************************************************* Figure 25: VLAN Menu 17 of 26

18 Configure the port 1 PVID to be 100 (Figure 26). Select APPLY and press <Enter>. Configure 802.1Q Port Settings Configure Port from [1 ] to [1 ] PVID [100 ] Ingress Filter<Disabled> GVRP<Disabled> GMRP Disabled APPLY Port PVID Ingress DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GVRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GMRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS Port PVID Ingress DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GVRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GMRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS ******************************************************************************* Figure 26: Configure 802.1Q Port Settings Menu Configure the port 25 PVID to be 54 (Figure 27). Select APPLY and press <Enter>. Configure 802.1Q Port Settings Configure Port from [25] to [25] PVID [54 ] Ingress Filter<Disabled> GVRP<Disabled> GMRP Disabled APPLY Port PVID Ingress DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GVRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GMRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS Port PVID Ingress DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GVRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS GMRP DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS DIS ******************************************************************************* Figure 27: Configure 802.1Q Port Settings Menu 18 of 26

19 4.3. Create the Necessary Layer 3 Interfaces for Each VLAN From the Main Menu, navigate to Layer 3 IP Networking (Figure 28). Press <Enter>. VH-2402-L3 Local Management Main Menu Basic Setup: Switch Information IP Setup Remote Management Setup Switch Settings Configure Ports Setup User Accounts Serial Port Settings Utilities Network Monitoring Save Changes Reboot Logout Advanced Setup: Spanning Tree Forwarding Filtering Priority Mirroring Multicasting VLANs Port Trunking Layer 3 IP Networking ******************************************************************************* Figure 28: Main Menu Enter Setup IP Interface from the IP Networking screen (Figure 29). Press <Enter>. Setup Layer 3 - IP Networking IP Interface: Setup IP Interface Routing Protocols: Setup RIP Configuration ******************************************************************************* Figure 29: Setup Layer 3 IP Networking Menu 19 of 26

20 Enter the IP address information for VLAN 54 (Figure 30). Select APPLY then press <Enter>. Setup IP Interface Action:<Add/Modify> Interface Name:[vlan54 ] VID:[54 ] IP Address :[ ] Active:<Yes> Subnet Mask:[ ] Total IP Interface: 6 APPLY Interface Name: System 1 to 8 9 to to IP Address : Subnet Mask: VID : 208 Active : Yes Interface Name: Data_Main 1 to 8 9 to to IP Address : MMMMMMMM MMMMMMMM MMMM-M-M - - Subnet Mask: VID : 209 Active : Yes ******************************************************************************* Figure 30: Setup IP Interface Menu Enter the IP address information for VLAN 100 (Figure 31). Select APPLY and press <Enter>. Setup IP Interface Action:<Add/Modify> Interface Name:[vlan100 ] VID:[100 ] IP Address :[ ] Active:<Yes> Subnet Mask:[ ] Total IP Interface: 7 APPLY Interface Name: System 1 to 8 9 to to IP Address : Subnet Mask: VID : 208 Active : Yes Interface Name: Data_Main 1 to 8 9 to to IP Address : MMMMMMMM MMMMMMMM MMMM-M-M - - Subnet Mask: VID : 209 Active : Yes Figure 31: Setup IP Interface Menu 20 of 26

21 4.4. Enable RIPv2 Routing on Required Interfaces Enter Setup IP Interface from the IP Networking screen (Figure 32). Press <Enter>. Setup Layer 3 - IP Networking IP Interface: Setup IP Interface Routing Protocols: Setup RIP Configuration ******************************************************************************* Figure 32: Setup Layer 3 IP Networking Menu Configure RIPv2 for the vlan54 interface (Figure 33). Select APPLY and press <Enter>. Setup RIP Configuration Interface name: [vlan54 ] TX Mode< V2 Only > RX Mode:< V2 Only > Authentication:<Disabled> Password:[ ] APPLY Interface IP Address TX Mode RX Mode Authentication System Disabled Disabled Disabled Data_Main Disabled Disabled Disabled Voice_Main Disabled Disabled Disabled DataLSPsite Disabled Disabled Disabled VoiceLSPsite Disabled Disabled Disabled DHCP_Server Disabled Disabled Disabled vlan Disabled Disabled Disabled vlan Disabled Disabled Disabled ******************************************************************************* Figure 33: Setup RIP Configuration 21 of 26

22 Configure RIPv2 for the vlan100 interface (Figure 34). Select APPLY and press <Enter>. Setup RIP Configuration Interface name: [vlan100 ] TX Mode< V2 Only > RX Mode:< V2 Only > Authentication:<Disabled> Password:[ ] APPLY Interface IP Address TX Mode RX Mode Authentication System Disabled Disabled Disabled Data_Main Disabled Disabled Disabled Voice_Main Disabled Disabled Disabled DataLSPsite Disabled Disabled Disabled VoiceLSPsite Disabled Disabled Disabled DHCP_Server Disabled Disabled Disabled vlan Disabled Disabled Disabled vlan Disabled Disabled Disabled ******************************************************************************* Figure 34: Setup RIP Configuration 5. HP 5304XL Configuration 5.1. Create All Required VLANs, Interfaces and Port Assignments HP ProCurve Switch 5304XL (config)# vlan 53 HP ProCurve Switch 5304XL (vlan-53)# name vlan53 HP ProCurve Switch 5304XL (vlan-53)# untagged D2 HP ProCurve Switch 5304XL (vlan-53)# ip address HP ProCurve Switch 5304XL (config)# vlan 92 HP ProCurve Switch 5304XL (vlan-53)# name vlan92 HP ProCurve Switch 5304XL (vlan-53)# tagged A2 HP ProCurve Switch 5304XL (vlan-53)# ip address HP ProCurve Switch 5304XL (vlan-53)# ip helper-address !Enable a DHCP-Relay Agent to the server Enable OSPF Routing and Assign Area to All Interfaces HP ProCurve Switch 5304XL (config)# ip routing!enable routing HP ProCurve Switch 5304XL (config)# router ospf HP ProCurve Switch 5304XL (ospf)# area !Create area HP ProCurve Switch 5304XL (ospf)# vlan 53 HP ProCurve Switch 5304XL (vlan-53)# ip ospf area !assign area to 53 HP ProCurve Switch 5304XL (vlan-53)# vlan 54 HP ProCurve Switch 5304XL (vlan-54)# ip ospf area !assign area to of 26

23 6. Verification Steps How to verify Example #1 Route Redistribution without access lists From the HP Procurve command line: Verify that all routes from the P882 and Enterasys switches appear in the HP route table. HP ProCurve Switch 5304XL# show ip route IP Route Entries Destination Network Mask Gateway Type Sub-Type Metric ospf External ospf IntraArea vlan53 connected ospf External ospf External ospf External vlan92 connected ospf External reject static lo0 connected 0 Figure 35: HP Procurve Route Table From the Enterasys Main Menu, navigate to Network Monitoring Menu Routing Table. Verify that all routes from the P882 and HP switches appear in the Enterasys route table. Browse Routing Table Jump to Destination Address:[ ] Mask:[ ] Gateway:[ ] GO CLEAR TABLE Total Entries:8 IP Address Netmask Gateway Interface Name Hops Protocol Voice_Main 1 Local vlan54 2 RIP vlan54 2 RIP vlan54 1 Local vlan54 2 RIP vlan54 2 RIP vlan54 9 RIP vlan100 1 Local Figure 36: Enterasys Vertical Horizon Route Table 23 of 26

24 How to verify Example #2 Route Redistribution with access lists From the HP Procurve command line: Verify that the route no longer appears in the HP routing table. HP ProCurve Switch 5304XL# show ip route IP Route Entries Destination Network Mask Gateway Type Sub-Type Metric ospf External ospf IntraArea vlan53 connected ospf External ospf External vlan92 connected ospf External reject static lo0 connected 0 Figure 37: HP Procurve Route Table From the Enterasys Main Menu, navigate to Network Monitoring Menu Routing Table Verify that the route no longer appears in the Enterasys routing table. Browse Routing Table Jump to Destination Address:[ ] Mask:[ ] Gateway:[ ] GO CLEAR TABLE Total Entries:8 IP Address Netmask Gateway Interface Name Hops Protocol Voice_Main 1 Local vlan54 2 RIP vlan54 2 RIP vlan54 1 Local vlan54 2 RIP vlan54 9 RIP vlan100 1 Local Figure 38: Enterasys Vertical Horizon Route Table 7. Conclusion Connectivity between all of the vendors using the Route Redistribute feature was demonstrated in these Application Notes. The procedures described can be generalized to most configurations. Support for route redistribution with and without the use of access lists was also demonstrated. 24 of 26

25 8. Additional References The following reference document can be obtained online at the Avaya Support website: Avaya P580/P882 Gigabit Ethernet Switch User Guide 25 of 26

26 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 26 of 26