Connecting a passive TAP: Difference between revisions
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
{{#invoke:Message box|ambox |type=content|text=Inspect and clean if necessary all optical connectors and bulk heads before making a connection.}} | {{#invoke:Message box|ambox |type=content|text=Inspect and clean if necessary all optical connectors and bulk heads before making a connection.}} | ||
{{#invoke:Message box|ambox |type=content|text=Passive TAPs are direction sensitive! | | ||
{{#invoke:Message box|ambox |type=content|text=Passive TAPs are direction sensitive! Make sure to make RX and TX connections accordingly!}} | |||
| | ||
Revision as of 17:08, 15 July 2022
Introduction
Passive Fiber Optic TAPs require little or no configuration. While cabling the network - and site ports is straight forward, the cabling between the TAP output and the NETSCOUT Accelerator NIC is somewhat special.
Solution
 | Inspect and clean if necessary all optical connectors and bulk heads before making a connection. |
| Passive TAPs are direction sensitive! Make sure to make RX and TX connections accordingly! |
LC SM/MM HD Fiber TAP
TAP internal cabling
Cables required
The two fibers of the duplex LC-LC output of the TAP - indicated with "monitor" - are both used for transmission.
To connect to the NETSCOUT Accelerator NIC, you need a LC-LC-duplex to 2x LC-simplex fan-out cable. It is very easy to make a cable like that.
Connecting the TAP to the NETSCOUT accelerator NIC
Both LC-simplex connectors need to be connected to the input of two separate SFP/SFP+ ports on the NETSCOUT Accelerator NIC on the back of the appliance.
Link aggregation
To analyze the date from the TAP correctly, you MUST create an aggregate that includes the two ports on the accelerator NIC connected to the TAP. In this example, those interfaces are if3 and if4. Ask our COMCERT Engineer to configure a aggregate for you or read the Agent Configuration Utility for CDM/ASI Administration Guide for details on how to do this.