Not seeing traffic at the analyzer from the TAP
Chapter 8: Troubleshooting 23
Not seeing traffic at the analyzer from the TAP
If your TAP is not transmitting to the analyzer as you expect, check the following:
♦
The Link is definitely up and running.
♦
The cable connected to the analyzer functions properly. Use a different
cable to confirm this.
♦
The Ethernet/SPAN or Fiber channel is not diverted elsewhere.
♦
Try swapping the cables between the ports.
♦
The nTAP is receiving power using a VIAVI power adapter. The Link A and
Link B lights flash when there is traffic traversing through the nTAP, which
indicates the nTAP has power.
♦
If you are using a TAP with a GigaStor, ensure the driver configuration
speed is set correctly. Sometimes allowing it to auto-negotiate will enable
the connection.
♦
If the system you are monitoring is Linux or UNIX based, you may have an
issue with the Maximum Transmission Unit size. The TCP stack in the UNIX
system uses algorithms to produce an MTU based on response time from
SYN ACK. A small MTU forces a server and client to redo their handshake.
Increase the MTU on your server to alleviate this issue.
Can I “team” or bond NICs in my analyzer?
Yes, it is possible with some limitations. Sometimes it is desirable to use two
standard full-duplex capture cards to capture full-duplex TAP output for analysis.
Because a standard capture card port has only one receive channel you must
aggregate the receive channels from two ports to see both sides of the two-way
connection being monitored. Intel’s Advanced Network Services allows you to
team multiple connections at the driver level, presenting your analyzer with an
aggregated view of send and receive channels.
Because of the processing overhead and its effect on capture card performance,
this method is not recommended for monitoring moderate to highly saturated
links, such as those between switches. However, it can be an economical
alternative when monitoring more lightly used connections, such as between a
server and switch.
In addition to the bandwidth limitations, connection teaming is also less accurate
when timestamping packets, which can cause unexpected results when your
analyzer attempts to display certain charts and statistics such as Connection
Dynamics or VoIP jitter. You also will not be able to tell which side is DCE vs.
DTE. In short, if you do not have a dual-receive analysis capture card, it is always
better to analyze the SPAN or port mirror session through a standard capture
card rather than using the connection teaming method described here.
Note:
You need at least one capture card that supports Advanced Network
Services. If the card has two ports, they can be teamed, otherwise another
capture card with an unused port must be present.
Содержание 10/100 Copper nTAP
Страница 1: ...10 100 Copper TAP User Guide 7 Feb 2018 ...