Aruba 6000 Series Installation And Getting Started Manual page 34

Tip
6
(missing or bad snippet)
Problem
The port or remote link
partner may be improperly
configured, or the port may
be in a "blocking" state by
the normal operation of
protocols, such as Spanning
Tree, LACP, or MVRP
features.
NOTE: If the switch port configuration is changed to one
of the fixed configuration options (for example, 100
Mbps/Full Duplex), then the port operates as MDI-X only
and you must use the correct type of cable for the
connection. In general, for connecting an end node (MDI
port) to the switch, use straight-through cable; for
connecting to MDI-X ports on hubs, other switches, and
routers, use crossover cable.
For fiber-optic connections, verify that the transmit port
o
on the switch is connected to the receive port on the
connected device, and the switch receive port is
connected to the transmit port on the connected device.
For 1000BASE-T connections, verify that the network cabling
n
complies with the IEEE 802.3ab standard. Install the cable
according to the ANSI/TIA/EIA-568-A-5 specifications.
Ensure that the cable testing complies with the stated
limitations for Attenuation, Near-End Crosstalk, Far-End
Crosstalk, Equal-Level Far-End Crosstalk (ELFEXT), Multiple
Disturber ELFEXT, and Return Loss.
The cable verification process must include all patch cables from
any end devices, including the switch, to any patch panels in the
cabling path.
Verify that the port has not been disabled through a switch
n
configuration change.
You can use the console interface, or, if you have configured an
IP address on the switch, use the web browser interface to
determine the state of the port and re-enable the port if
necessary.
Verify that the switch port configuration matches the
n
configuration of the attached device. For example, if the
switch port is configured as "Auto", the port on the attached
device also MUST be configured as "Auto". Depending on
the port type, twisted-pair or fiber-optic, if the
configurations do not match, the results could be a very
unreliable connection, or no link at all.
If the other procedures do not resolve the problem, try
n
using a different port or a different cable.
You must ensure that the device at the other end of the
n
connection indicates a good link to the switch. If it does not,
the problem may be with the cabling between the devices,
the connectors on the cable, or the configuration of the
device on the remote end of the cable.
Use the switch console to see if the port is part of a dynamic
n
trunk (through the LACP feature) or to see if Spanning Tree
is enabled on the switch, and to see if the port may have
Solution