Skip to main content

Verifying port LEDs during switch POST

Verifying port LEDs during switch POST 
6.1.3 There are many ideas to present here. The following could help in answering some of the questions students might ask about POST LEDs during switch POST:
  • At the start all port LEDs are green
  • Each LED turns off after its test completes
  • If a test fails, its LED turns amber
  • System LED turns amber if any test fails
  • If no test fails, POST completes
  • On POST completion, LEDs blink 
Port LED Display Mode
Description
Port status (STAT LED on)
Off: No link present
Green: Link present, no activity
Flashing green: Link present with traffic activity
Alternating green and amber: Link fault. Error frames can affect connectivity. Excessive collisions and cyclic redundancy check (CRC), alignment, and jabber errors are monitored for a link-fault indication.
Amber: Port not forwarding because management disabled the port, suspended because of an address violation, or suspended by Spanning-Tree Protocol (STP) because of network loops.
Bandwidth utilization (UTL LED on)
Green: Current bandwidth utilization displayed over the amber LED background on a logarithmic scale
Amber: Maximum backplane utilization since the switch was powered on Green and amber: Depends on model as follows:
If all LEDs on Catalyst 2950-12, 2950-24, 2950C-24, and 2950T-24 switches are green, the switch is using 50 percent or more of the total bandwidth. If the far-right LED is off, the switch is using more than 25 but less than 50 percent of the total bandwidth, and so on. If only the far-left LED is green, the switch is using less than 0.0488 percent of the total bandwidth.
If all LEDs on Catalyst 2950G-12-EI switches are green, the switch is using 50 percent or more of the total bandwidth. If the LED for GBIC module slot 2 is off, the switch is using more than 25 but less than 50 percent of the total bandwidth. If LEDs for both GBIC module slots are off, the switch is using less than 25 percent of the total bandwidth, and so on.
If all LEDs on Catalyst 2950G-24-EI and 2950G-24-EI-DC switches are green, the switch is using 50 percent or more of the total bandwidth.
If the LED for GBIC module slot 2 is off, the switch is using more than 25 but less than 50 percent of the total bandwidth. If LEDs for both GBIC module slots are off, the switch is using less than 25 percent of the total bandwidth, and so on.
If all LEDs on Catalyst 2950G-48-EI switches are green, the switch is using 50 percent or more of the total bandwidth. If the LED for the upper GBIC module slot is off, the switch is using more than 25 but less than 50 percent of the total bandwidth. If LEDs for both GBIC module slots are off, the switch is using less than 25 percent of the total bandwidth, and so on.
Full duplex (FDUP LED on)
Green: Ports configured in full-duplex mode
Off: Ports using half-duplex mode

This page will explain how LEDs can be used to determine if a switch works properly and has established a link with its target.
Once the power cable is connected, the switch initiates a series of tests called the power-on self test (POST). POST runs automatically to verify that the switch functions correctly. The System LED indicates the success or failure of POST. If the System LED is off but the switch is plugged in, then POST is running. If the System LED is green, then POST was successful. If the System LED is amber, then POST failed. POST failure is considered to be a fatal error. Reliable operation of the switch should not be expected if POST fails.
The Port Status LEDs also change during POST. The Port Status LEDs turn amber for about 30 seconds as the switch discovers the network topology and searches for loops. If the Port Status LEDs turn green, the switch has established a link between the port and a target, such as a computer. If the Port Status LEDs turn off, the switch has determined that nothing is plugged into the port.
The next page will teach students how to establish a communication session with a switch.




Comments

Popular posts from this blog

OSI layers / Peer-to-peer communications / TCP/IP model

OSI layers 2.3.4 This page discusses the seven layers of the OSI model. The OSI reference model is a framework that is used to understand how information travels throughout a network. The OSI reference model explains how packets travel through the various layers to another device on a network, even if the sender and destination have different types of network media. In the OSI reference model, there are seven numbered layers, each of which illustrates a particular network function. - Dividing the network into seven layers provides the following advantages: • It breaks network communication into smaller, more manageable parts. • It standardizes network components to allow multiple vendor development and support. • It allows different types of network hardware and software to communicate with each other. • It prevents changes in one layer from affecting other layers. • It divides network communication into smaller parts to make learning it easier to understand. In the foll...

Advantages and disadvantages of link-state routing

Advantages and disadvantages of link-state routing 2.1.5  This page lists the advantages and disadvantages of link-state routing protocols. The following are advantages of link-state routing protocols:  Link-state protocols use cost metrics to choose paths through the network. The cost metric reflects the capacity of the links on those paths. Link-state protocols use triggered updates and LSA floods to immediately report changes in the network topology to all routers in the network. This leads to fast convergence times. Each router has a complete and synchronized picture of the network. Therefore, it is very difficult for routing loops to occur. Routers use the latest information to make the best routing decisions. The link-state database sizes can be minimized with careful network design. This leads to smaller Dijkstra calculations and faster convergence. Every router, at the very least, maps the topology of it...

Ports for services

Ports for services 10.2.2  Services running on hosts must have a port number assigned to them so communication can occur. A remote host attempting to connect to a service expects that service to use specific transport layer protocols and ports. Some ports, which are defined in RFC 1700, are known as the well-known ports. These ports are reserved in both TCP and UDP.  These well-known ports define applications that run above the transport layer protocols. For example, a server that runs FTP will use ports 20 and 21 to forward TCP connections from clients to its FTP application. This allows the server to determine which service a client requests. TCP and UDP use port numbers to determine the correct service to which requests are forwarded. The next page will discuss ports in greater detail.