Abstract. Testing was conducted via the Internal Interoperability Program at the Avaya Solution and Interoperability Test Lab.

Transcription

1 Avaya Solution & Interoperability Test Lab Interoperability Application Note for Avaya 96x0, 96x1 and 1600 Series IP Telephones with Avaya Ethernet Routing Switch 2550T-PWR Data Switch with Quality of Service Issue 1.0 Abstract These Application Notes present a sample configuration for a local area network including an Avaya Ethernet Routing Switch 2550T-PWR Data Switch providing Quality of Service to Avaya handsets Series 96x0, 96x1 and Testing was conducted via the Internal Interoperability Program at the Avaya Solution and Interoperability Test Lab. 1 of 26

2 1. Introduction The purpose of this interoperability Application Notes is to validate for Quality of Service (QoS) testing performed on the Avaya Aura Communication Manager R6.0.1, Avaya Aura Session Manager R6.1 and Avaya Ethernet Routing Switch 2550T-PWR Data Switch across a local area network. The network consisted of the Avaya telephone system residing in a designated VLAN, with connection to the handsets via switches and router. Please see Figure 1 for graphical representation. Handsets consisted of a variety of Avaya devices, programmed as H.323 and SIP devices. Handsets were split across two VLAN s with a third VLAN for data connections. Voice over IP traffic may be tagged to be treated differently from other packets on the network. This tagged traffic can be segregated and using Quality of Service, the tagged traffic can be given a higher priority and dealt with differently. Commonly, traffic will be tagged by the Avaya endpoint, using Layer 2 and Layer 3 information. For layer 2, the 802.1p priority is set to 6 and Layer 3 Differentiated Services Code Point (DSCP) is set to 46. Usually the Ethernet switch is configured to give priority to the value 6 and the router is configured to give priority to value 46. Quality of Service settings were enabled on both the router and the Avaya 2550T-PWR switch which also provided VLAN settings to the handsets. Testing consisted of ensuring that handset functionality was available through the designated ports on the switch, configuring the router and the switch with appropriate VLAN and QoS settings and ensuring the handsets received the relevant settings and information was displayed correctly in Wireshark traces. Test calls were made whilst generating a load across the local area network to review the status of calls. Load was generated on the network via means of ping and large file transfer from devices on x network to devices on x via the Extreme Summit 450e router and Avaya Switches (363T and 2550T). 2 of 26

3 Figure 1: Network Diagram for Quality of Service Test Configuration Testing Assumptions The following assumptions have been made as part of this document: It is assumed that Communication Manager, System Manager and Session Manager have been installed, configured and licensed. Refer to Section 9 for documentation regarding these procedures. Throughout this section the administration of Communication Manager is performed using a System Access Terminal (SAT). The commands are entered on the system with the appropriate administrative permissions. Some administration screens have been abbreviated for clarity. The user has experience administering the Avaya system via both SAT and Web Based Management systems. Handset extensions have been programmed on Communication Manager and System Manager and programming of these devices will only be referred to with regards to the context of Quality of Service settings that may need to be altered. Some familiarity with HyperTerminal and telnet sessions for connectivity with data switches and routers. Both router and switches have been programmed with network settings and introduced to the network as working devices. 3 of 26

4 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided. Equipment Software Avaya S8800 Media Server Avaya Aura Communication Manager R6.0.1 VSP: CM_Simplex R016x Avaya S8800 Media Server Avaya Aura System Manager R6.1.0 (Build No ) Software Update Revision No: Avaya S8800 Media Server Avaya Aura Session Manager R (Build No ) VSP: Avaya G650 Media Gateway TN2312BP HW15 FW054 TN799DP HW16 FW040 TN2602AP HW08 FW061 TN2224CP HW08 FW015 TN2464CP HW02 FW024 TN793CP HW17 FW010 Avaya Handset 1608 (H.323) ha1608ual_3100.bin Avaya Handset 9601 (SIP) 2r24628_V11r1271.tar Avaya Handset 9611 (SIP) S96x1_SALBR6_0_2V470.tar Avaya Handset 9621 (SIP) S96x1_SALBR6_0_2V470.tar Avaya Handset 9640 (H.323) ha96xxua3_1_02_s.bin Avaya Handset 9641 (SIP) S96x1_SALBR6_0_2V470.tar Avaya Handset 9641 (H.323) ha96xxua3_1_02_s.bin Avaya Handset 9650 (H.323) ha96xxua3_1_02_s.bin Extreme Summit X450e-48p Switch: G Rev 7.0 BootROM: IMG: Image: ExtremeXOS version v1203b16 BootROM : Avaya 363T Data Switch Image Version Avaya Ethernet Routing Switch 2550T-PWR Data Switch HW:10 FW: SW:v of 26

5 3. Configure Avaya Ethernet Routing Switch 2550T-PWR Switch This section provides details on the configuration of Avaya Ethernet Routing Switch 2550T- PWR data switch. Configuration of the switch can be performed using either a serial connection or a telnet session to the relevant ip address of the switch. This section provides the procedures for configuring ERS 2550T PWR data switch areas for VLANs and QoS: Configure VLANs Configure DHCP Configure QoS Settings 3.1. Configure VLAN To configure the switch with two voice vlans and one data vlan, open a session to the switch. At the prompt enter any username/password that may have been set. Enter enable at the prompt. To begin configuration, enter configure terminal to obtain 2550T-PWR(config)# prompt. Configure Voice VLAN T-PWR(config)#vlan create 82 type port (create VLAN 82) 2550T-PWR(config)#vlan members add (add ports 1-12 to VLAN82) 2550T-PWR(config)#vlan members add (add uplink port 49 to VLAN 82) 2550T-PWR(config)#vlan name 82 VLAN82_Voice 2550T-PWR(config)#vlan ports 1-12 tagging tagall (tag All ports 1-12 with relevant VLAN id) 2550T-PWR(config)#interface vlan 82 (changes to a vlan interface for configuration) 2550T-PWR(config-if)#ip address (assign ip address and subnetmask to VLAN82) 2550T-PWR(config-if)#exit (to leave vlan interface configuration mode) 2550T-PWR(config)#exit (to leave configuration mode) Configure Voice VLAN T-PWR(config)#vlan create 83 type port 2550T-PWR(config)#vlan members add T-PWR(config)#vlan members add T-PWR(config)#vlan name 83 VLAN83_Voice 2550T-PWR(config)#vlan ports tagging tagall 2550T-PWR(config)#interface vlan T-PWR(config-if)#ip address T-PWR(config-if)#exit 2550T-PWR(config)#exit 5 of 26

6 As the handsets on VLAN83 will also provide NIC for a personal computer, the ports must NOT issue a Voice VLAN id / ip address to the PC. In this example, the handset plugged into Port 19 on the switch will also provide a NIC connection for a PC. To prevent the port from issuing a Voice related VLAN id to the PC, use the following. 2550T-PWR(config)#vlan ports 19 tagging untagpvidonly pvid 84 Create Data VLAN T-PWR(config)#vlan create type port 2550T-PWR(config)#vlan members add (add ports to VLAN84) 2550T-PWR(config)#vlan members add (add port 19 to VLAN 84) 2550T-PWR(config)#vlan members add (add uplink port 49 to VLAN 84) 2550T-PWR(config)#vlan name 84 VLAN84_Data 2550T-PWR(config)#interface vlan T-PWR(config-if)#ip address T-PWR(config-if)#exit 2550T-PWR(config)#exit The command show vlan will show configuration summary. 2550T-PWR(config)# show vlan Id Name Type Protocol PID Active IVL/SVL Mgmt VLAN #1 Port None 0x0000 Yes IVL No Port Members: VLAN82_Voice Port None 0x0000 Yes IVL Yes Port Members: 1-12,49 83 VLAN83_Voice Port None 0x0000 Yes IVL No Port Members: 13-24,49 84 VLAN84_Data Port None 0x0000 Yes IVL No Port Members: 15,25-36,49 Total VLANs: 4 Use show ip route to confirm the routing. 2550T-PWR(config)#show ip route ============================================================================= Ip Route ============================================================================= DST MASK NEXT COST VLAN PORT PROT TYPE PRF S IB C DB C DB C DB 0 6 of 26

7 Notes: Other useful commands for vlan information. show vlan interface info displays the vlan assigned to the port and whether the port is being tagged with the vlan information. show vlan ip id <vlan id> - displays the ip addresses of each vlan 3.2. Configure DHCP The 2550T-PWR will use DHCP to issue ip addresses to devices connecting on the ports. Devices may also use fixed IP addresses if desired. In this application note, DHCP was used to provide addresses automatically to devices connecting to the network. Set the lease time for devices to lease ip addresses. 2550T-PWR(config)#ip dhcp-server lease days 2 hours 3 Alternatively use default ip dhcp-server lease to default the lease time to 1 day. 2550T-PWR(config)#default ip dhcp-server lease Adding the DHCP Pool. 2550T-PWR(config)#ip dhcp-server pool vlan82 range Set the default router for each pool. 2550T-PWR(config)#ip dhcp-server pool vlan82 option-3 routers Set the subnet mask for each pool. 2550T-PWR(config)#$dhcp-server pool vlan82 option-1 subnet-mask Repeat the creation of the DHCP pool and add the subnet mask and router address for VLAN 83 and VLAN 84. Enable DHCP server. 2550T-PWR#ip dhcp-server enable Additional settings such as DNS server, Vendor Class ID and options may also be configured via this interface, but are not required within this document. Please refer to Section 9 for further information on programming. 7 of 26

8 3.3. Enabling QoS The switch ports are classified into three different categories trusted, untrusted or unrestricted. These classifications are applied to groups of ports known as an interface group. Trusted ports are usually connected to the core of the DiffServ network, whereas untrusted ports are usually access links to end points. Unrestricted ports can be either access links or connect to the core network. Initial out of the box configuration has all ports untrusted. For further details on QoS and the Avaya Ethernet Routing Switch, please refer to Section 9. For the purposes of this application note it was decided to set ports to unrestricted. A QoS if-group, called TRUSTED was created with the class unrestricted. 2550T-PWR(config)#qos if-group name TRUSTED class unrestricted 2550T-PWR(config)#qos if-assign port 1-24 name TRUSTED 4. Configuration on Extreme Summit 450e Router The router must be programmed to recognize the L2 / L3 info coming from the data switch in order to prioritize this traffic. Within the Extreme Summit 450e router there are two default priority queues that traffic uses. Most traffic by default is assigned to QP1, the lowest priority queue, with network control traffic assigned to QP8 (high priority). A new queue was created to assign qos traffic entering the router. In the example, QP7 was created using the command create qosprofile qp7. Priority Queues X450e-48p.2 # create qosprofile qp Assign DSCP & 802.1q values to Priority Queue 7 Assign DSCP and 802.1q values to the new priority queue. According to the display in ipnetwork-region 1 form in Communication Manager (see Section 9 Reference [1]), Avaya VoIP traffic uses DIFFSERV/TOS parameters of 46 and 802.1p/Q PARAMETERS of 6, so these values are used here and the router is configured to examine incoming packets for this information and associate the packet with QP7. To assign DSCP value 46 to qosprofile7, use the command configure diffserv examination code-point 46 qp7. To assign 802.1q value of 6 to qosprofile7, use the command configure dot1q type 6 qp7. X450e-48p.2 # configure diffserv examination code-point 46 qp7 X450e-48p.2 # configure dot1q type 6 qp7 8 of 26

9 5. Administer Avaya Aura Communication Manager This section highlights the areas for registering Avaya IP telephones as H.323 stations in the Communications Manager and administering IP network-region and IP codec forms to carry calls between Avaya IP endpoints in separate VLANs. It also highlights the important commands for defining Avaya SIP telephones as an Off-PBX Station (OPS) and administering a SIP Trunk and Signaling Group to carry calls between Avaya IP and SIP telephones Verify OPS Capacity Use the display system-parameters customer-options command to verify that Maximum Off- PBX Telephones OPS has been set to the value that has been licensed, and that this value will accommodate the addition of SIP telephones. If a required feature is not enabled or there is insufficient capacity, contact an authorized Avaya sales representative. display system-parameters customer-options Page 1 of 11 OPTIONAL FEATURES G3 Version: V16 Software Package: Enterprise Location: 2 System ID (SID): 1 Platform: 28 Module ID (MID): 1 USED Platform Maximum Ports: Maximum Stations: Maximum XMOBILE Stations: Maximum Off-PBX Telephones - EC500: Maximum Off-PBX Telephones - OPS: Maximum Off-PBX Telephones - PBFMC: Maximum Off-PBX Telephones - PVFMC: Maximum Off-PBX Telephones - SCCAN: 0 0 Maximum Survivable Processors: of 26

10 Verify that Maximum Concurrently Registered IP stations has been set to the value that has been licensed, and that this value will accommodate the addition of IP telephones. Verify that Maximum Administered SIP Trunks has been set to accommodate addition of SIP trunks. display system-parameters customer-options Page 2 of 11 OPTIONAL FEATURES IP PORT CAPACITIES USED Maximum Administered H.323 Trunks: Maximum Concurrently Registered IP Stations: Maximum Administered Remote Office Trunks: Maximum Concurrently Registered Remote Office Stations: Maximum Concurrently Registered IP econs: Max Concur Registered Unauthenticated H.323 Stations: Maximum Video Capable Stations: Maximum Video Capable IP Softphones: Maximum Administered SIP Trunks: Maximum Administered Ad-hoc Video Conferencing Ports: Maximum Number of DS1 Boards with Echo Cancellation: Maximum TN2501 VAL Boards: Maximum Media Gateway VAL Sources: Maximum TN2602 Boards with 80 VoIP Channels: Administer Dial Plan Analysis The Dial Plan Analysis screen shows how Communication Manager translates the digits dialed by the user. In the example below, there are two dialed string patterns highlighted. The dialed pattern 231 with a total length of 5 and Call Type ext was used for IP (H.323) extensions. A similar dial pattern 232 was used for IP extensions that were configured as SIP devices. display dialplan analysis Page 1 of 12 DIAL PLAN ANALYSIS TABLE Location: all Percent Full: 3 Dialed Total Call Dialed Total Call Dialed Total Call String Length Type String Length Type String Length Type 1 3 dac 2 5 aar 20 4 aar ext ext ext 10 of 26

11 5.3. Administer IP Node-Name The IP Node Names form is where Communications Manager assigns the IP address and Node Name to the system. This information is needed to administer the signaling group. In the example below, the information relating to the entry clan and the session manager (sm100b) is required. list node-names all NODE NAMES Type Name IP Address IP clan IP default IP gateway IP medpro IP procr IP procr6 :: IP sm100b of 26

12 5.4. Administer Signaling Group This section describes the Signaling Group screen. The configuration of the signaling group was set as follows:- Set the Group Type Transport Method Near-end Node Name Far-end Node Name Near-end Listen Port Set to 5060 Far-end Listen Port Set to 5060 Far-end Network Region Set to 1 Far-end Domain Direct IP-IP Audio Connections Set to sip Set either tcp (for internal use only) or as tls Set to clan node name of the available clan interface Set to sm100b - the node name of the Session Manager Leave blank to accept all domain names or set to specific domain name i.e. mmsil.local Set to y (Audio Shuffle on) display signaling-group 150 SIGNALING GROUP Group Number: 150 Group Type: sip IMS Enabled? n Transport Method: tcp Q-SIP? n SIP Enabled LSP? n IP Video? y Priority Video? y Enforce SIPS URI for SRTP? y Peer Detection Enabled? y Peer Server: SM Near-end Node Name: clan Far-end Node Name: sm100b Near-end Listen Port: 5060 Far-end Listen Port: 5060 Far-end Network Region: 1 Far-end Domain:mmsil.local Bypass If IP Threshold Exceeded? n Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n DTMF over IP: rtp-payload Direct IP-IP Audio Connections? y Session Establishment Timer(min): 3 IP Audio Hairpinning? n Enable Layer 3 Test? y Initial IP-IP Direct Media? n H.323 Station Outgoing Direct Media? n Alternate Route Timer(sec): of 26

13 5.5. Administer Trunk Group This section describers the trunk group used to carry calls to and from SIP telephones. The configuration of the trunk group was set as follows:- Group Number Set to 150 Group Type Set to sip Group Name Set to sip tg 150 Direction Set to two-way Service Type Set to tie Signaling Group Set to 150 Number of Members Set to 10 display trunk-group 150 Page 1 of 21 TRUNK GROUP Group Number: 150 Group Type: sip CDR Reports: y Group Name: sip tg 150 COR: 1 TN: 1 TAC: 150 Direction: two-way Outgoing Display? y Dial Access? n Night Service: Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: auto Signaling Group: 150 Number of Members: of 26

14 5.6. Administer IP Network Region This section describes the IP Network Region. All handsets were placed in this network region. This screen shows the values used for DIFFSERV (DSCP) and 802.1p/Q. The settings were configured as follows. Authoritative Domain Set to mmsil.local Codec Set Set to 1 Intra-region IP-IP Direct Audio Set to yes Inter-region IP-IP Direct Audio Set to yes DIFFSERV/TOS PARAMETERS o Call Control PHB Value Set to 46 o Audio PHB Value Set to P/Q PARAMETERS o Call Control 802.1p Priority Set to 6 o Audio 802.1p Priority Set to 6 display ip-network-region 1 Page 1 of 20 IP NETWORK REGION Region: 1 Location: 1 Authoritative Domain: mmsil.local Name: To ASM61 MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 2048 IP Audio Hairpinning? n UDP Port Max: DIFFSERV/TOS PARAMETERS Call Control PHB Value: 46 Audio PHB Value: 46 Video PHB Value: P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 Changing the DiffServ and 802.1p value on this screen should alter the values on the H.323 handsets, however only the DiffServ value will be updated immediately. The 802.1p value on the H.323 handset will not change. In order to change the 802.1p value on the handset, follow the instructions in Section 5.8. Once the changes have been made to both the ip-network-region and ip-server-interface screens, reboot the H.323 handset and it will display both of the new settings for DiffServ and 802.1p. To change the DiffServ and 802.1p settings on SIP devices, please see Section of 26

15 5.7. Administer IP Codec Set This section describes the IP Codec Set screen and determines the codecs the handsets will use. For the purposes of this application note, IP Codecs G.711MU, G.711A and G.729 were used. display ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n : G.711A n : G.729 n IP Server and DIFFSERV / values This section describers how to view the values on the IP Server Interface using the command display ipserver interface 1. (Please note, there may be more than one IP Server interface card present in the system, so adjust the command as required. Only one card was present in the system at the time of testing.). display ipserver-interface 1 Page 1 of 2 IP SERVER INTERFACE (IPSI) ADMINISTRATION - PORT NETWORK 1 IP Control? y Encryption? y Ignore Connectivity in Server Arbitration? n PRIMARY IPSI QoS AND ETHERNET SETTINGS Location: 1A01 Use System Level Parameter Values? y Subnet Mask: / p: 6 IP Address: DiffServ: 46 Gateway: Auto? y To change the 802.1p and DiffServ values on the ipserver interface form to different values other than 46 and 6, first set Use System level Parameter Values to n. The fields for 802.1p and DiffServ will then become available for editing Changing DiffServ and values on SIP Devices Altering the DiffServ and values on SIP devices is carried out by the 46xxsettings.txt file that each phone reads from an http source whilst booting. The fields within the 46xsettings files as follows:- For 802.1p priority SET L2QAUD 6 SET L2QSIG 6 For DiffServ SET DSCPAUD 46 SET DSCPSIG of 26

16 6. Configure Avaya Aura Session Manager The following steps describe the configuration of Session Manager for SIP devices Avaya Aura Session Manager Administration The DiffServ and 802.1p/Q (QoS Priority) may be viewed via System Manager. Connect to the System Manager Web interface using of System Manager>/SMGR/. Log in and select the following from the Home screen, Home Elements Session Manager Session Manager Administration. From the section on the right hand side of the screen, select Session Manager Instances. Select the Session Manager and then click on the Edit button. This opens the Edit Session Manager screen. In here Call Control PHB Value (Diffserv Code Point) and QOS Priority (802.1p/Q) are displayed. 16 of 26

17 7. Verification The following verification steps were used as part of testing. These steps may also be used in the field. Monitoring of the data switch was enabled by port monitoring the uplink between the switch and the router. Note: In some cases network interfaces cards on computers performing monitoring may strip VLAN identification from incoming packets. It may be necessary to enable this setting on the NIC via modification of registry relating to the NIC card. Please refer to the relevant manufacturer website for instructions relating to this. It was verified that the PC ( / VLAN84) using the NIC connection on SIP Device (ext / IP Address / VLAN83) could ping a phone assigned in VLAN 82 - SIP Device(ext / IP Address / VLAN82). Figure 2: Ping results between PC on VLAN 84 and SIP device on VLAN82 Monitoring of the data switch was enabled by port monitoring the uplink between the switch and the router. It was verified that the PC ( / VLAN84) using the NIC connection on SIP Device (ext / IP Address / VLAN83) could ping a phone assigned in VLAN 83 - SIP Device(ext / IP Address / VLAN83). Figure 3: Ping results between PC on VLAN 84 and SIP device on VLAN83 17 of 26

18 It was verified that the VLAN ID was visible from the Avaya ERS 2550T-PWR switch. This can be seen in the Wireshark trace in Figure 4. Figure 4: Wireshark Trace showing VLAN id It was also verified that the DSCP and 802.1p values were also being captured within a Wireshark trace. See Figure 5. Figure 5: Wireshark trace showing 802.1p/Q and DiffServ Value 18 of 26

19 Handsets were verified as being registered in one of two ways, dependent on the handset type (H.323 or SIP). For IP Stations registered directly with Communication Manager (H.323) use the command list registered-ip-stations. list registered-ip-stations REGISTERED IP STATIONS Station Ext Set Type/ Prod ID/ TCP Station IP Address/ or Orig Port Net Rgn Release Skt Gatekeeper IP Address IP_Phone y S IP_Phone y S IP_Phone y S For IP stations registered as SIP Devices with Session Manager use the System Manager web interface and from the Home screen, browse to Elements Session Manager System Status User Registrations. 19 of 26

20 Active H.323 calls can be viewed with Communications Manager with the command status station XXXXX, where XXXXX is an extension number. status station Page 4 of 8 CALL CONTROL SIGNALING Port: S00041 Switch-End IP Signaling Loc: 01A0217 H.245 Port: IP Address Port Node Name Rgn Switch-End: clan 1 Set End: H.245 Near: H.245 Set: Figure 6 Sample of call from H.323 to SIP station Active SIP calls can be viewed via Session Manager trace session or a Wireshark trace. 20 of 26

21 8. Conclusion As illustrated in these Application Notes, Avaya Ethernet Routing Switch 2550T-PWR can interoperate with Avaya Aura Communication Manager and Avaya Aura Session Manager to provide Quality of Service. In detail these Application notes have described the administration steps required to configure Voice and Data VLANs on Avaya ERS 2550T-PWR switch Administration of Avaya IP and SIP devices with Avaya Aura Communication Manager and Avaya Aura System Manager in relation to QoS Administration of system settings relating to QoS within Avaya Aura Communication Manager and Avaya Aura System Manager 9. Additional References Product Documentation for Avaya Products, including Ethernet Routing Switches may be found at [1] Administering Avaya Aura Communication Manager Release 6.0 Issue 6.0 [2] Administering Avaya Aura Communication Manager Server Options Release 6.0.1, Issue 2.2 [3] Administering Avaya Aura Session Manager Release 6.1 Issue 1.0 [4] Maintaining and Troubleshooting Avaya Aura Session Manager Release 6.1 Issue 4.1 [5] Avaya IP Telephony Deployment Technical Configuration Guide NN Version: 7.1 [6] ERS2500_4.4_Doc_Collection_02_ Collection of Manuals relating to Ethernet Routing Switch 2500 series, including Configuration of VLAN, IP/DHCP and QoS. Available as a zip download from Avaya. Product Documentation for Extreme Summit 450e Routers may be found at 21 of 26

22 Appendix A Sample Configuration file for Avaya 2550T-PWR Data Switch! Embedded ASCII Configuration Generator Script! Model = Ethernet Routing Switch 2550T-PWR! Software version = v !! Displaying only parameters different to default!================================================! *** CORE *** tftp-server ! *** SNMP ***! *** IP *** ip default-gateway ip address switch ! *** IP Manager ***! *** ASSET ID ***! *** System Logging ***! *** STACK ***! *** Custom Banner ***! *** STP (Phase 1) *** spanning-tree port-mode auto! *** VLAN *** vlan create type port vlan ports 1-18 tagging tagall vlan ports 19 tagging untagpvidonly vlan ports 20-24,49 tagging tagall vlan configcontrol flexible vlan members vlan members ,49 vlan members ,49 vlan members 84 19,25-36,49 vlan ports 1-12 pvid of 26

23 vlan ports pvid 83 vlan ports 19 pvid 84 vlan ports pvid 83 vlan ports pvid 84 vlan configcontrol automatic! *** IGMP ***! *** EAP ***! *** EAP Guest VLAN ***! *** EAP Fail Open VLAN ***! *** EAP Voip VLAN ***! *** Port Mirroring *** port-mirroring mode XrxOrXtx monitor-port 25 mirror-port-x 49! *** 802.1ab ***! *** 802.1ab vendor-specific Avaya TLVs config ***! *** QOS *** qos if-group name TRUSTED class unrestricted qos if-assign port 1-24 name TRUSTED! *** RMON ***! *** Interface ***! *** MLT (Phase 1) ***! *** MAC-Based Security ***! *** LACP ***! *** ADAC ***! *** STP (Phase 2) *** spanning-tree port-mode normal interface FastEthernet ALL spanning-tree port learning disable 23 of 26

24 exit! *** VLAN Phase 2*** vlan mgmt 82! *** MLT (Phase 2) ***! *** PoE ***! *** RTC ***! *** AUR ***! *** AAUR ***! *** L3 *** ip routing interface vlan 83 ip address exit interface vlan 84 ip address exit ip route ! *** IPV6 ***! *** VLACP ***! *** DHCP Relay ***! *** L3 Protocols ***! --- IP Directed Broadcast ---! --- Proxy ARP ---! --- UDP Broadcast Forwarding ---! *** DHCP SNOOPING ***! *** ARP INSPECTION ***! *** IP SOURCE GUARD *** 24 of 26

25 ! *** STACK MONITOR ***! *** DHCP 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