GigaVUE‑TA25 Rules and Notes
Keep in mind the following notes and rules when using the GigaVUE‑TA25:
|
GigaVUE-TA25 Rules and Notes |
|||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Transceivers |
All Gigamon labeled 1Gb, 10Gb, 25Gb, 40Gb and 100Gb optics are supported. For details about the supported transceiver, cable type, and connectivity specifications, refer to “GigaVUE-OS Compatibility and Interoperability Matrix”. |
||||||||||||
|
Network, Tool, Hybrid, or Stack Port |
The GigaVUE‑TA25 ports can be used as network, tool, hybrid, circuit or stack-link ports. The 4x10Gb and 4x25Gb ports also support all port types. Note: On GigaVUE-TA25 all port types are supported with break-out subports. Only C1, C5 ports support 4x10G, 4x25G break-out modes. Note: For 1Gb fiber ports, auto-negotiation is not supported on GigaVUE-TA25. Stack port type is also not supported on 1Gb ports. Note: Advanced feature license is required for stack and circuit port types. |
||||||||||||
|
Map Rules and Port Filters |
The GigaVUE‑TA25 supports 256 map rules per chassis and 20 egress port filters per chassis, without advanced feature license. For details about the maximum map rule with advanced feature license, refer to the "Maximum Map Rules" table in the GigaVUE Fabric Management Guide. |
||||||||||||
|
Port Licensing |
On GigaVUE‑TA25 all ports are enabled. For GigaVUE‑TA25A upgrading with port license will enable the additional ports. Refer to Port Licensing. |
||||||||||||
|
Cluster Licensing |
Connecting a GigaVUE‑TA25 to a cluster requires the Advanced Features License. |
||||||||||||
|
Legacy Cluster/ Stacking |
The GigaVUE-TA25 ports cannot be part of destination ports of first level maps if source leader in a bidirectional clock relationship (formerly master) port is on non GigaVUE-TA25 node (i.e. “to” ports list cannot contain combination of VPort and GigaVUE-TA25 destination port if any of the from ports are non GigaVUE-TA25 ports) in legacy cluster. Note: This is not applicable when the source port is on another GigaVUE-TA25 node. Workarounds include:
|
||||||||||||
