In the ASE (v4.4-44 and earlier) switches, when using terminal emulation applications to manage the switch, the Backspace key does not function normally due to issues in the code. These issues are currently being addressed, but until they are resolved the backspace function can only be achieved using the Delete key or by pressing CTRL + H. This short article presents a workaround to this issue that allows you to reconfigure the keyboard settings in your SSH session so that you can use the Backspace key normally. The following instructions are specific to PuTTy, but similar reconfigurations in the terminal emulation tool of your choice can be achieved by making the same adjustments. The process for reconfiguring your PuTTy session to preserve the Backspace key functionality revolves around redefining the Backspace key keyboard settings for the PuTTy session. You can reconfigure these settings in a new PuTTy session or in an existing session by following these steps: 1. When opening a new PuTTy session, select the Keyboard setting in the PuTTy Configuration menu. If you already have an active PuTTy session open, you can right-click on the menu bar at the top of the application and select Change Settings to open the PuTTy Reconfiguration menu, and then select the Keyboard setting.   2. Next, in The Backspace key configuration, change the default setting from Control-? (127) to Control-H as shown below. This operation reassigns the CTRL + H function to the Backspace key so that the Backspace key functions normally. To apply these changes, select Apply at the bottom of the menu.   3. Once the changes have been applied, you can close the configuration menu and continue to use PuTTy as normal by using one of the following options: You can close the settings menu and use the Backspace key as normal for the session. NOTE: If you do not save these settings to a session profile on the main PuTTy screen, you will have to repeat these steps to use the Backspace key as normal each time you open a PuTTy session. Save these modified settings to a session profile and use that profile each time you are working with an ASE switch to use the Backspace key normally.

Question How do you Factory Default an ASE device? Answer There are at least 2 methods. 1.  Using the Mode/Reset button on the front of the switch, hold this button for 2 - 7 seconds.           2.  Log In and Reset Configuration to Factory Default Press Enter one or more times until the Username: prompt appears. Type admin and press Enter. At the Password: prompt type password and press Enter. This completes the login sequence and displays the prompt, ‘#’. ( Using the default login ) Username: admin Password: password #   At this point, the admin user is operating at the highest privilege level, level 15. This means full control over the device and its configuration, and it is, therefore, possible to reset the configuration to factory defaults. Type reload defaults and press Enter. When the prompt returns, the system has reverted to factory defaults as follows: # reload defaults % Reloading  

Question How do I configure auto-link on my ASE Switch? Answer Currently auto-link is configurable only in the CLI of our ASE switches. The following 2 commands are all that's needed to get it up and running from global configuration mode: ! auto-link  auto-link server primary <hostname | ip address> [port <port>] !   Considerations: Only one entry is allowed for the primary n-Command MSP server. In addition, primary servers cannot be deleted if any secondary servers are configured. Multiple entries can be configured for secondary n-Command MSP servers. Duplicate entries are not allowed. The priority of secondary servers is determined by the order in which they were configured. By default, auto-link will use port 80 for HTTP, or port 443 for HTTPS, depending on the specified communication method. By default, the unit communicates with the server using HTTPS.

Question Why are my devices that were learned on the port, showing static MAC addresses in the MAC Table? Answer MAC address learned on a port are normally shown as dynamic ( dynamically learned )  MAC addresses, but this will change with some security settings. Example; Port security is the reason for the mac addresses being static here -  With port security:   NV1560# show run interface GigabitEthernet 1/4 Building configuration... interface GigabitEthernet 1/4 no poe mode qos trust tag speed auto 10 100 1000 description Connected to Customer LAN and VoIP Phones port-security ! end NV1560# show mac address-table Type    VID  MAC Address       Ports Static  1    00:0c:29:c9:70:74 GigabitEthernet 1/4 Static  1    a4:ba:db:1d:c5:39 GigabitEthernet 1/4     Without port security:   NV1560# show run interface gig 1/4 Building configuration... interface GigabitEthernet 1/4 no poe mode qos trust tag speed auto 10 100 1000 description Connected to Customer LAN and VoIP Phones ! End   NV1560# show mac address-table Type    VID  MAC Address       Ports Dynamic 1    00:0c:29:c9:70:74 GigabitEthernet 1/4 Dynamic 1    a4:ba:db:1d:c5:39 GigabitEthernet 1/4

Question What happens when a Port is Shutdown on an ASE device? How do you drop PoE to the Port to reboot a device? Answer If a port is shutdown: Port LED continues to blink PoE continues to be supplied to connected device. “no poe mode” must be configured on the port to stop the port from supplying power To stop PoE to a device on a port from the Web interface -  Configuration / PoE / PoE Configuration - Select the pull-down next to the port of interest, and set the PoE Mode to Disabled.   

Question How would I disable Telnet on an ASE device? Answer From the CLI in enable mode  - Switch# con t Switch(config)# no aaa authentication login telnet To re-enable telnet - Switch# con t Switch(config)# aaa authentication login telnet  

Question:  How do you turn PoE power off to a PoE device connected to an ASE switch?   Answer: From the CLI ( example on Port 12 ) -  Switch# sh poe int gig 1/12 Interface PD Class Pwr Req Pwr Alloc Port Status Power Used [W] Current Used [mA] Priority ---------------------- -------- ------- -------------------------------------------------- --------------- ------------------ -------- GigabitEthernet 1/12 2 3.9 3.9 PoE turned ON 2.5 47 Low Total - 3.9 3.9 - 2.5 47 Switch# con t Switch(config)# int gig 1/12 Switch(config-if)# no poe mode Switch(config-if)# exit Switch(config)# exit Switch# sh poe int gig 1/12 Interface PD Class Pwr Req Pwr Alloc Port Status Power Used [W] Current Used [mA] Priority ---------------------- -------- ------- -------------------------------------------------- --------------- ------------------ -------- GigabitEthernet 1/12 - 0.0 0.0 PoE turned OFF - PoE disabled 0.0 0 Low Total - 0.0 0.0 - 0.0 0 To restore power, use the CLI command - " poe mode plus " on the interface. From the Web interface ( example on Port 2 ) -    Using the "disable" option will remove power after the save button is selected at the bottom of the page. And selecting one of the other options will restore PoE power after the save button is selected at the bottom of the page.  

Symptoms -  CPU of ASE switch and the network is slow or not responding   Diagnosis - LEDS show traffic is nearly constant, management access to the switch is slow to not responsive.  Interface stats show a majority of multicast traffic or is counting up faster than other traffic. Solution - IGMP Snooping   IGMP/MLD Snooping IP multicast reduces the IP broadcasting data traffic efforts by forwarding the data frames to only those network devices that expect the designated frames proposing group registration. It is commonly deployed for triple play services (data, voice, and video), such as a network conference system and video on demand (VOD). ASE IPMC, which includes IGMP and MLD protocol support, manages the IP multicast group registration.  Snooping works at the layer 2 MAC level but it handles the IP IGMP (layer 3) control messages to dedicate a layer 2 MAC forwarding table. For IPMC snooping, the system needs to be in router mode where the following two roles are defined. • Querier transmits IPMC queries and is responsible for triggering multicast address determination. • Non-querier routers not selected as querier in the same broadcast domain, such as a VLAN.   ASE IGMP Defaults  IGMP Snooping Setup Using ICLI   Execute the following steps to set up IGMP snooping using ICLI.  Enters global configuration mode.               configure terminal Example # configure terminal (config)#    Sets up unknown flooding, SSM range, or IPv4 multicast data forwarding. (Optional) ip igmp { ssm-range <ipv4_mcast> | unknown-flooding } Example (config)# ip igmp unknown-flooding (config)#    Creates and enters (IP) VLAN interface configuration mode with the specific VLAN ID or list.  This list includes all VLANs that you would like to have IGMP snooping, running. interface vlan <vlan_list> Example 1 (config)# int vlan 1-3,5 (config-if-vlan)# Example 2 (config)# interface vlan 1 (config-if-vlan)#    Enables the designated (IP) VLAN interface IGMP snooping function. ip igmp snooping Example (config-if-vlan)# ip igmp snooping (config-if-vlan)#    Sets up IGMP VLAN interface specific configurations. (Optional) ip igmp snooping { compatibility { auto | v1 | v2 | v3 } | last-member-query-interval <0-31744> | priority <0-7> | querier address <ipv4_ucast> | querier election | query-interval <1-31744> | query-max-response-time <0-31744> | robustness-variable <1-255> | unsolicitedreport- interval <0-31744> } Example (config-if-vlan)# ip igmp snooping querier election (config-if-vlan)#    Exits from interface configuration mode and returns to global configuration mode. exit Example (config-if-vlan)# exit (config)#     Enables the global IGMP snooping function. ip igmp snooping Example (config)# ip igmp snooping (config)#    Returns to privileged EXEC mode. end Example (config)# end #    Saves settings in the configuration file. (Optional) copy running-config startup-config Example # copy running-config startup-config #

Question:  How is SNMP configured on an ASE device?   Answer:  With the current ( at this time) version of firmware v4.4-41, using the default configuration with the addition of a default route to allow routing to and from the switch, the ASE device will allow a MIB browser to walk the MIB.   Example - To get the switch into default config - # reload defaults keep-ip   In the default configuration -   Switch# sh run feature snmp all Building configuration... ! ! ! ! snmp-server snmp-server engine-id local 800002980300... snmp-server contact no snmp-server location no snmp-server community public ip-range 0.0.0.0 0.0.0.0 encrypted snmp-server community private ip-range 0.0.0.0 0.0.0.0 encrypted snmp-server security-to-group model v1 name public group default_ro_group snmp-server security-to-group model v1 name private group default_rw_group snmp-server security-to-group model v2c name public group default_ro_group snmp-server security-to-group model v2c name private group default_rw_group snmp-server view default_view .1 include snmp-server access default_ro_group model any level noauth read default_view snmp-server access default_rw_group model any level noauth read default_view write default_view !   The default community strings of public and private are configured.   To troubleshoot, verify the switch can ping the SNMP browser and the browser is using the ASE device IP address , default port of 161, and the correct community strings. The MIB's for the SDX 8110 / NV1560 are again available at www.adtran.com/mibs.  They are now under the ADTRAN product line.  

Question: How do you find the serial number of a NetVanta 1560 series switch?   Answer: There are five methods for locating the serial number on your NetVanta 1560 Series switch: Method One: The sticker on the bottom of the switch will provide the serial number and much more information. Method Two: The box the switch came in, if you still have it, also has a baled with the same serial number on the top. Method Three: Access the switch's web interface and navigate to the System tab. Then, select Information.     Method Four: Connect to the NetVanta 1560 CLI (using Telnet, SSH, or Console), and follow these steps: From the Enable mode prompt, enable the platform debug feature using the platform debug allow command. NV1560-24>en NV1560-24#platform debug allow WARNING: The use of 'debug' commands may negatively impact system behavior. Do not enable unless instructed to. (Use 'platform debug deny' to disable debug commands.) NOTE: 'debug' command syntax, semantics and behavior are subject to change without notice. 2. Next, enter the debug factory command to display system information for the switch, including the serial number. NV1560-24#deb factory MAC Address: 00-24-45-xx-xx-xx Serial Number : LBADTN1914AE314 HW Version : P2A Part Number : 17108124PF2 Fan High Threshold : 300 Fan Low Threshold : 280 NV1560-24# Method Five: With firmware v4.4-44 and newer, connect to the NetVanta 1560 CLI (using Telnet, SSH, or Console), and follow this step: From the Enable mode prompt, using the show version command. NV1560-24#sh ver MAC Address: 00-24-45-xx-xx-xx Serial Number : LBADTN1914AE314 Previous Restart : Cold System Contact : System Name : NV1560-24 System Location :

Question: In the web interface of the NetVanta 1560 series switches, what does the Save button on many of the pages actually do? If I use that button, I do not see any changes in the Startup-config.   Answer:  This button only saves the changes to the current running configuration and does not save these changes to the startup configuration. When you use the Save button, any changes are saved to the running-config and the changes are applied. To save changes to the startup configuration file, in the NetVanta 1560 GUI, navigate to the Configuration tab, and select Save startup-config: When prompted, select Save Configuration.   Update - v4.4-46 has changed the button on these screens to  Apply  to reduce confusion.  

Question: How do I view the console events when connected to the NetVanta 1560 CLI?   Answer: Real-time port status changes are not seen in the ASE switch console or CLI connections. The command #sh logging will display the interface logs showing these events.   Switch# sh logging Switch logging host mode is disabled Switch logging host address is null Switch logging level is informational Number of entries on Switch 1: Error : 0 Warning : 0 Notice : 5609 Informational: 9 All : 5618 ID Level Time & Message ---------- ------------- -------------- 1 Informational 1969-12-31T18:00:37-06:00 SYS-BOOTING: Switch just made a cold boot. ... 8 Notice 1969-12-31T18:00:42-06:00 LINK-UPDOWN: Interface Vlan 1, changed state to up. 9 Notice 1969-12-31T18:00:42-06:00 LINK-UPDOWN: Interface Vlan 1, changed state to up. 10 Notice 1969-12-31T18:00:42-06:00 LINK-UPDOWN: Interface GigabitEthernet 1/1, changed s tate to up. 11 Notice 1969-12-31T18:00:42-06:00 LINK-UPDOWN: Interface GigabitEthernet 1/24, changed state to up. 12 Notice 1969-12-31T18:00:43-06:00 LINK-UPDOWN: Interface Vlan 1, changed state to down. 13 Notice 1969-12-31T18:00:46-06:00 LINK-UPDOWN: Interface Vlan 1, changed state to up. 14 Notice 1969-12-31T18:00:48-06:00 LINK-UPDOWN: Interface GigabitEthernet 1/1, changed s tate to down. 15 Notice 1969-12-31T18:00:50-06:00 LINK-UPDOWN: Interface GigabitEthernet 1/1, changed s tate to up. 16 Notice 1969-12-31T18:00:51-06:00 LINK-CHANGED: Interface GigabitEthernet 1/1, changed state to up (MEP). 17 Notice 1969-12-31T18:00:51-06:00 LINK-CHANGED: Interface GigabitEthernet 1/2, changed state to up (MEP).