LEDs and connection sequence
When turned on, the TAP performs a sequence of steps to determine whether its link ports are connected to any devices, and what speeds and other capabilities those devices have. The blinking pattern of the LEDs indicate which step of the connection process the TAP is performing. The duration of each state depends on the type of equipment attached to each port of the TAP. Here are the connection steps, listed in the order they occur:
1. Capabilities search. Both link ports/connections on the TAP are attempting to attach to their respective devices and determine a common speed and other capabilities. The LED pattern is that the Speed LEDs flash (slower) and the Link LEDs flicker (faster).
2. Connecting. The link parameters are attempting to connect using the parameters determined during the capabilities search. The LED pattern is that the TAP shows the connection speed while the Link LEDs continue to flicker.
3. Connected. Both link ports/connections are connected to the link partners at a common speed. The Speed LED shows connection speed. The Link LEDs light steadily (idle) or flicker depending on whether there is any traffic present. If a Link LED is unlit, there is no functioning device connected to that port.
When the 10/100 Copper nTAP experiences power loss, the following occurs:
If you are using a redundant power supply or the TAP is attached to an uninterruptible power supply (UPS), it provides power with no loss of network connection.
If you are not using a redundant power supply or UPS, or power to both power supplies is lost, then:
The Analyzer ports stop working and the analysis device(s) connected to the TAP will go “dark.”
The TAP continues to pass data between the network devices connected to it (firewall/router/switch to server/switch). In this sense the TAP is passive.
The network devices connected to the TAP on the Link ports must renegotiate a connection with each other because the TAP has dropped out. This may take a few seconds.
Error conditions are shown by the LEDs for approximately 10 seconds, after which the TAP resets itself (goes back to the Capabilities connection step).
LED Pattern
Error Condition
The LEDs repeat the sequence: 10> 100> 1000.
No Common Speed. There is no common speed capability between the devices attached to Link A and Link B.
Memory Failure (aggregator nTAP only). The software failed to initialize the aggregation buffer.
The 10 LED flashes. The other Speed LEDs are on and do not flash.
Timed Out. The TAP software has timed out waiting for some event.
The expected speed’s LED is on, while the actual speed’s LED flashes.
Wrong Speed. One of the links has connected at the wrong speed.
The 1000 LED flashes. The other Speed LEDs are on and do not flash.
Logic Error. This error occurs when the link partner capabilities are ambiguous.
See How do I connect my failover devices? for details about what happens when a primary device fails.