Oam Considerations; Qinq Raps-Tag Considerations - Nokia 7302 Manual

Services Overview
no shutdown
exit
Associating eth-ring instance to a sap:
Configure service
exit
3.11.3
Ethernet CFM can be enabled on each individual path under an Ethernet ring. Only
down MEPs can be configured on each of them and CCM sessions can be enabled
to monitor the liveliness of the path using intervals of 100 msec.
Different CCM intervals can be supported on the path a and path b in an Ethernet
ring. CFM is optional if the hardware supports Loss of Signal for example.
Up MEPs on service SAPs which multicast into the service and monitor the active
path may be used to monitor services.
3.11.4
From release R5.0.0.1, its possible to configure Double tagged (QinQ) Eth-ring path
RAPS-Tag over an Dot1q encapsulated Ethernet port.
With respect to iHub's behavior, whenever a QinQ Raps-Tag is configured, it sends
out RAPS and CCM packets with double tags over the ring-ports.
Also iHub can receive double tagged RAPS and CCM packets from the peer-nodes,
but always process the corresponding packets whose outer-vlan matches the control
vlan; the inner vlan is never taken as input for validation or control plane processing.
The control vlan v-vpls configuration will remain singled tagged.
This facility is introduced in R5.0.0.1 to allow interoperation with 1830 PSS switch
which sends and receives only double tagged RAPS and CCM packets.
68
no shutdown
exit
exit
no shutdown
vpls 20 customer 1 v-vpls vlan 100 create
description "Ring Control VID 100"
sap nt-a:xfp:1:100 eth-ring 1 create //control sap for
path-a
exit
sap lag-10:100 eth-ring 1 create // control sap for path-b
exit
no shutdown
exit

OAM considerations

QinQ RAPS-Tag Considerations

3HH-11985-AAAA-TQZZA
FD 100/320Gbps NT and FX NT IHub Services Guide
Issue: 13