NIC 16: PROPIEDADES PLANTA Y EQUIPO

Check that your terminal or terminal emulator is correctly conÞgured.

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

Check the settings on your terminal or terminal emulator. The settings are 9600 baud, 8 data bits, 1 stop bit, no parity, XON/OFF ßow control enabled.

The SNMP Network Manager cannot access the device:

Check that the device's IP address, subnet mask, and default router are correctly conÞgured, and that the device has been reset.

Check that the device's IP address is correctly recorded by the SNMP Network Manager (refer to the user documentation for the Network Manager).

Check that the community strings conÞgured for the Switch and Network Manager are the same.

Check that SNMP access was not disabled for the Switch.

The Telnet workstation cannot access the device:

Check that the device's IP address, subnet mask and default router are correctly conÞgured, and that the device has been reset. Ensure that you enter the IP address of the Switch correctly when invoking the Telnet facility. Check that Telnet access was not disabled 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.

USINGTHE COMMAND-LINE INTERFACE

Traps are not received by the SNMP Network Manager:

Check that the SNMP Network Manager's IP address and community string are

correctly conÞgured, and that the IP address of the Trap Receiver is conÞgured properly on the Switch.

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

Check that Telnet access or SNMP access is enabled.

Check that 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. Check that the port through which you are trying to access the device is in a correctly conÞgured VLAN.

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 accessing the device over the network. Try accessing the device through the console port.

Check that the community strings conÞgured for the Switch and the Network Manager are the same.

Check that SNMP access was not disabled for the Switch.

Permanent entries remain in the FDB

If you have made a permanent entry in the FDB (which requires you to specify the VLAN to which it belongs and then delete the VLAN) the FDB entry will remain. Though causing no harm, you must manually delete the entry from the FDB if you want to remove it.

Default and Static Routes

If you have deÞned static or default routes, those routes will remain in the

conÞguration 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

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 conÞguration information (including passwords) to the initial values.

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

VLAN

You cannot add a port to a VLAN:

If you attempt to add a port to a VLAN and get an error message similar to localhost:7 # config vlan marketing add port 1,2

ERROR: Protocol conflict.

you already have a VLAN using untagged trafÞc on a port. Only one VLAN using untagged trafÞc can be conÞgured on a single physical port. VLAN conÞguration can be veriÞed by using the command

show vlan <name>

The solution for this error is to remove ports 1 and 2 from the VLAN currently using untagged trafÞc on those ports. If this were the ÒdefaultÓ VLAN, the command would be

localhost:23 # config vlan default del port 1,2

which should now allow you to re-enter the previous command without error as follows:

USINGTHE COMMAND-LINE INTERFACE

VLAN names:

There are restrictions on VLAN names. They cannot contain white spaces and cannot start with a numeric value unless you use quotation marks around the name. If a name contains white spaces or starts with a numeric, you must use quotation marks

whenever referring to the VLAN name.

802.1Q links do not work correctly:

Remember that VLAN names are only locally signiÞcant through the command-line interface. In order for two Switches to communicate across a 802.1Q link, the VLAN ID for the VLAN on one Switch should have a corresponding VLAN ID for the VLAN on the other Switch.

If you are connecting to a third-party device and have checked that the VLAN IDs are the same, the Ethertype Þeld used to identify packets as 802.1Q packets may differ between the devices. The default value used by the Switch is 8100. If the third-party device differs from this and cannot be changed, you may change the 802.1Q Ethertype used by the Switch with the following command:

config dot1p ethertype <ethertype>

Changing this parameter changes how the Switch recognizes all tagged frames received, as well as the value it inserts in all tagged frames it transmits.

VLANs, IP Addresses and default routes:

Recall that the Switch can have an IP address for each conÞgured VLAN. It is only necessary to have an IP address associated with a VLAN if you intend to manage (telnet, SNMP, ping) through that VLAN. You can also conÞgure multiple default routes for the Switch. The Switch Þrst tries the default route with the lowest cost metric.

STP

You have connected an endstation directly to the Switch and the endstation fails to boot correctly:

The Switch keeps aging out endstation entries in the Switch Forwarding Database (FDB):

Reduce the number of topology changes by disabling STP on those Switches that do not use redundant paths.