Requested revision
Standard: | 802.1Q-2011 | Clause: | Clause 20.9 |
Clause title: | MEP variables |
Rationale for revision
There is administrative state defined for MEP (MEPActive), but there is no operational state for MEP in 802.1Q-2011. Operational state is important for indicating if a MEP works normally or not.
Proposed text
Clause 20.9:
Add x) MEPOperationalState (20.9.xx)
Add Clause 20.9.xx MEPOperationalState: This state indicates the operational state of the MEP. If the value is 'up', the MEP is able to provide OAM capabilities and has been set to active via the dot1agCfmMepActive object. If the value is 'down' the MEP is not able to provide OAM capabilities, for example because it has been disabled via the dot1agCfmMepActive object, has detected an operational failure condition, or has failed an internal test. If the value is 'testing' the MEP has been placed into a test mode, either a troubleshooting mode or ETH-Test 'Out-of-service' mode.If the value is 'unknown' the MEP is unable to report the operational state.
Clause 17
Add corresponding MIB objects
Impact on existing networks
None
Originator
Name: | Weiying Cheng | Email: | Weiying.Cheng@tellabs.com |
Affiliation: | Tellabs | ||
Submitted: | 2012-06-29 |