FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 181
The VPLS management VRF only supports routing packets to locally attached hosts.
That is, no next-hops can be statically specified and no routing protocols can be
activated.
To address the VPLS management VRF, the router instance vpls-management must
be specified in CLI commands.
For example:
show router vpls-management arp
ping 10.10.10.1 router vpls-management
show router vpls-management route-table
5.4.10 PM Counters per SAP
Statistics and Performance Monitoring (PM) can be enabled on a per-SAP basis for
both VPLS and v-VPLS services. This includes counting of Transmit and Receive
Frames and Octets on the SAP. By enabling statistics on the SAP, the operator can
monitor the running statistics on the SAP and also the current 15-minute interval and
current 1-day interval statistics. The PM interval table holds the history for the most
recent 32 instances of 15-minute intervals and 2 instances of 1-day intervals.
5.4.11 Per-service Configurable TPID
As per IEEE 802.1ad, S-VLANs can be tagged with 0x88a8 (or any other ethernet
type other than 0x8100) by the access provider for each v-VPLS, VPLS or EPIPE
service.
This feature allows for certain services to be configured to use one TPID (for
example, A) while other v-VPLS services can be configured to use either another
TPID (for example, B) or a system-wide default TPID.
Once a service level TPID is configured, each SAP in the service can be enabled to
use either the TPID configured at the v-VPLS, VPLS, or EPIEP service level or the
port-default TPID.
To Next Page
Loading...
