"FD 100/320Gbps NT and FX NT IHub System
Basics, Management and OAM Guide"
8.10 Y1731 PM Restrictions
The following Y1731 PM restrictions exist:
•
•
•
•
•
•
•
•
8.11 CLI Command Reference
8.11.1
configure
— eth-cfm
—
domain
md-index [format {mac | none | string}] [name md-name] level level
—
domain
md-index
—
no
domain
—
association
—
association
— no
association
—
bridge-identifier
— no
bridge-identifier
Issue: 10
Y1731 PM functionalities not supported on the following MEPs:
•
UP MEP
•
MEP over SDP
•
MEPs configured in an EPIPE service
•
IEEE MEP
•
MEP over LT SAP
•
MEP over NULL SAP or SAP *
maximum number of Y1731 PM enabled MEP is limited to 32
Y1731 PM, L2 ACL and SAP PM uses the same hardware resources. Y1731 PM
has higher precedence, so L2 ACL and SAP PM will not work along with Y1731
PM.
Y1731 PM counter maintained for loss will have the following restrictions:
•
ACL dropped egress packets will be counted
•
egress dropped packets due to buffer is full; the rate limit will be counted
•
egress CRM OAM frames on standby port will be counted
•
OAM CFM frames forwarded in data plane will be counted in egress and ingress
•
In case of LAG with active and standby port, as members ETH-CCM transmitted by
NT will not be counted
Egress and ingress counters in LMM and LMR will be updated by CPU not by
hardware. Due to this, frames would be sent or received between the actual
counter read and transmission of LMM / LMR PDU.
Egress and ingress counter will not be accurate if one or more ports are added or
removed between any two consecutive LMM PDUs in the LAG.
Timestamps in DMM and DMR will be updated by CPU not by the hardware. Due
to this delay, the calculation will be less accurate compare to the hardware
solutions.
Y1731 PM proactive current history records will not be synced to standby. Due to
this, Y.1731 PM current history records would not survive NT switchover.
CFM Commands
ma-index [{format {icc-based | integer | string | vid | vpn-id}] name ma-name
ma-index
ma-index
bridge-id
bridge-id
3HH-11982-AAAA-TQZZA
Ethernet Connection Fault Management
181