General Tips and Recommendations

The initial welcome prompt does not appear:

Check that:

Your terminal or terminal emulator is correctly configured
Your terminal or terminal emulator has the correct settings:
- 115200 baud for ExtremeSwitching X690 and X870 switches; or 9600 baud for all other switches
- 8 data bits
- 1 stop bit
- no parity
- XON/OFF flow control enabled

For console port access, you may need to press [Return] several times before the welcome prompt appears.

The SNMP Network Manager cannot access the device:

Check that:

The SNMP (Simple Network Management Protocol) access is enabled for the system.
The device IP address, subnet mask, and default router are correctly configured, and that the device has been reset.
The device IP address is correctly recorded by the SNMP Network Manager (refer to the user documentation for the Network Manager).
The community strings configured for the system and Network Manager are the same.
The SNMPv3 USM, Auth, and VACM configured for the system and Network Manager are the same.

The Telnet workstation cannot access the device:

Check that:

The device IP address, subnet mask, and default router are correctly configured, and that the device has been reset.
You entered the IP address of the switch correctly when invoking the Telnet facility.
Telnet access is enabled for the switch.

If you attempt to log in and the maximum number of Telnet sessions are being used, you should receive an error message indicating so.

Traps are not received by the SNMP Network Manager:

Check that the SNMP Network Manager's IP address and community string are correctly configured, and that the IP address of the Trap Receiver is configured properly on the system.

The SNMP Network Manager or Telnet workstation can no longer access the device:

Check that:

Telnet access or SNMP access is enabled for the system.
The port through which you are trying to access the device has not been disabled. If it is enabled, check the connections and network cabling at the port.
The port through which you are trying to access the device is in a correctly configured VLAN (Virtual LAN).
The community strings configured for the device and the Network Manager are the same.

Try accessing the device through a different port. If you can now access the device, a problem with the original port is indicated. Re-examine the connections and cabling.

A network problem may be preventing you from accessing the device over the network. Try accessing the device through the console port.

Permanent entries remain in the FDB:

If you have made a permanent entry in the FDB (forwarding database) that requires you to specify the VLAN to which the entry belongs and then deleted the VLAN, the FDB entry remains. Although this does not harm the system, if you want to removed the entry, you must manually delete it from the FDB.

Default and static routes:

If you have defined static or default routes, those routes remain in the configuration independent of whether the VLAN and VLAN IP address that used them remains. You should manually delete the routes if no VLAN IP address is capable of using them.

You forget your password and cannot log in:

If you are not an administrator, another user having administrator access level can log in, delete your user name, and create a new user name for you, with a new password.

Alternatively, another user having administrator access level can log in and initialize the device. This will return all configuration information (including passwords) to the initial values.

In the case where no one knows a password for an administrator level user, contact your supplier.

Published March 2020prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback