| admin-name |
string |
Used to define a name that can be used to uniquely identify
an object. Historically, an arbitrary integer index
would have been used for this purpose. A string provides
greater flexibility and allows some amount of context to
be included.
The string has the following restrictions:
- Leading underscore is not allowed;
- Leading or trailing space is not allowed;
- Leading plus sign followed by a fully numeric string is not allowed;
- Leading digit is not allowed unless the full string is numeric and is within the range 1..4294967295 |
| admin-name |
string |
Used to define a name that can be used to uniquely identify
an object. Historically, an arbitrary integer index
would have been used for this purpose. A string provides
greater flexibility and allows some amount of context to
be included.
The string has the following restrictions:
- Leading underscore is not allowed;
- Leading or trailing space is not allowed;
- Leading plus sign followed by a fully numeric string is not allowed;
- Leading digit is not allowed unless the full string is numeric and is within the range 1..4294967295 |
| admin-name |
string |
Used to define a name that can be used to uniquely identify
an object. Historically, an arbitrary integer index
would have been used for this purpose. A string provides
greater flexibility and allows some amount of context to
be included. |
| bandwidth-notif-rate |
union |
Types for rate from the ETH-BN PDU. |
| bandwidth-notif-rate |
union |
Types for rate from the ETH-BN PDU. |
| bandwidth-notif-rate |
union |
Types for rate from the ETH-BN PDU. |
| ccm-interval-type |
enumeration |
The possible intervals between CCM transmissions. |
| ccm-interval-type |
enumeration |
The possible intervals between CCM transmissions. |
| ccm-interval-type |
enumeration |
The possible intervals between CCM transmissions. |
| ccm-tlv-ignore-type |
enumeration |
An enumerated value indicating whether to enable processing of received
CCM TLVs |
| ccm-tlv-ignore-type |
enumeration |
An enumerated value indicating whether to enable processing of received
CCM TLVs |
| ccm-tlv-ignore-type |
enumeration |
An enumerated value indicating whether to enable processing of received
CCM TLVs |
| chassis-id-subtype |
enumeration |
This typedef describes the source of a chassis identifier.
The enumeration 'system(1)' represents a chassis
identifier based on the value of entPhysicalAlias object
(defined in IETF RFC 2737) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').
The enumeration 'local(7)' represents a chassis identifier
based on a locally defined value. |
| chassis-id-subtype |
enumeration |
This typedef describes the source of a chassis identifier.
The enumeration 'system(1)' represents a chassis
identifier based on the value of entPhysicalAlias object
(defined in IETF RFC 2737) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').
The enumeration 'local(7)' represents a chassis identifier
based on a locally defined value. |
| chassis-id-subtype |
enumeration |
This typedef describes the source of a chassis identifier.
The enumeration 'system(1)' represents a chassis
identifier based on the value of entPhysicalAlias object
(defined in IETF RFC 2737) for a chassis component (i.e.,
an entPhysicalClass value of 'chassis(3)').
The enumeration 'local(7)' represents a chassis identifier
based on a locally defined value. |
| facility-id-permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. This is a
subset of permission-type. The valid values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent. |
| facility-id-permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. This is a
subset of permission-type. The valid values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent. |
| facility-id-permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. This is a
subset of permission-type. The valid values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent. |
| fault-propagation-type |
enumeration |
The Fault Propagation type for a MEP
When not set, no additional fault propagation will occur.
use-if-status-tlv(1) The MEP will send an interface status TLV in the next CCM indicating
fault when fault is detected, even if the MEP itself has not detected a fault.
suspend-ccm(2) Faults will be propagated by stopping the regular CCM
transmissions entirely. Once the fault is cleared, the regular
CCM transmissions will resume.
Additionally, when the value of this leaf is set, a defect detected
by the MEP will be propagated into the service. |
| fault-propagation-type |
enumeration |
The Fault Propagation type for a MEP
When not set, no additional fault propagation will occur.
use-if-status-tlv(1) The MEP will send an interface status TLV in the next CCM indicating
fault when fault is detected, even if the MEP itself has not detected a fault.
suspend-ccm(2) Faults will be propagated by stopping the regular CCM
transmissions entirely. Once the fault is cleared, the regular
CCM transmissions will resume.
Additionally, when the value of this leaf is set, a defect detected
by the MEP will be propagated into the service. |
| fault-propagation-type |
enumeration |
The Fault Propagation type for a MEP
When not set, no additional fault propagation will occur.
use-if-status-tlv(1) The MEP will send an interface status TLV in the next CCM indicating
fault when fault is detected, even if the MEP itself has not detected a fault.
suspend-ccm(2) Faults will be propagated by stopping the regular CCM
transmissions entirely. Once the fault is cleared, the regular
CCM transmissions will resume.
Additionally, when the value of this leaf is set, a defect detected
by the MEP will be propagated into the service. |
| fc-type |
enumeration |
This data type describes a set of Forwarding Classes. |
| fc-type |
enumeration |
This data type describes a set of Forwarding Classes. |
| fc-type |
enumeration |
This data type describes a set of Forwarding Classes. |
| fng-state-type |
enumeration |
Indicates the diferent states of the MEP Fault Notification
Generator State Machine.
reset(1) No defect has been present since the
fng-reset-time timer expired, or since
the state machine was last reset.
defect(2) A defect is present, but not for a
long enough time to be reported.
report-defect(3) A momentary state during which the
defect is reported by sending a
dot1agCfmFaultAlarm notification,
if that action is enabled.
defect-reported(4) A defect is present, and some defect
has been reported.
defect-clearing(5) No defect is present, but the
fng-reset-time timer has
not yet expired. |
| fng-state-type |
enumeration |
Indicates the diferent states of the MEP Fault Notification
Generator State Machine.
reset(1) No defect has been present since the
fng-reset-time timer expired, or since
the state machine was last reset.
defect(2) A defect is present, but not for a
long enough time to be reported.
report-defect(3) A momentary state during which the
defect is reported by sending a
dot1agCfmFaultAlarm notification,
if that action is enabled.
defect-reported(4) A defect is present, and some defect
has been reported.
defect-clearing(5) No defect is present, but the
fng-reset-time timer has
not yet expired. |
| fng-state-type |
enumeration |
Indicates the diferent states of the MEP Fault Notification
Generator State Machine.
reset(1) No defect has been present since the
fng-reset-time timer expired, or since
the state machine was last reset.
defect(2) A defect is present, but not for a
long enough time to be reported.
report-defect(3) A momentary state during which the
defect is reported by sending a
dot1agCfmFaultAlarm notification,
if that action is enabled.
defect-reported(4) A defect is present, and some defect
has been reported.
defect-clearing(5) No defect is present, but the
fng-reset-time timer has
not yet expired. |
| frame-priority |
uint8 |
Used to define the priority of OAM frames. |
| frame-priority |
uint8 |
Used to define the priority of OAM frames. |
| frame-priority |
uint8 |
Used to define the priority of OAM frames. |
| highest-priority-defect-type |
enumeration |
An enumerated value indicating the highest-priority defect that has been present
since the MEP Fault Noffication Generator State Machine was last in the FNG_RESET state. |
| highest-priority-defect-type |
enumeration |
An enumerated value indicating the highest-priority defect that has been present
since the MEP Fault Noffication Generator State Machine was last in the FNG_RESET state. |
| highest-priority-defect-type |
enumeration |
An enumerated value indicating the highest-priority defect that has been present
since the MEP Fault Noffication Generator State Machine was last in the FNG_RESET state. |
| interface-status |
enumeration |
An enumerated value from the Interface Status TLV from the
last CCM received from the last MEP. It indicates the status
of the Interface within which the MEP transmitting the CCM
is configured, or the next lower Interface in the Interface
Stack, if the MEP is not configured within an Interface.
is-no-interface-status-tlv(0) Indicates either that no CCM has been
received or that no interface status TLV
was present in the last CCM received.
is-up(1) The interface is ready to pass packets.
is-down(2) The interface cannot pass packets
is-testing(3) The interface is in some test mode.
is-unknown(4) The interface status cannot be determined
for some reason.
is-dormant(5) The interface is not in a state to pass
packets but is in a pending state, waiting
for some external event.
is-not-present(6) Some component of the interface is missing
is-lower-layer-down(7) The interface is down due to state of the
lower layer interfaces
NOTE: A 0 value is used for isNoInterfaceStatusTLV, so that
these code points can be kept consistent with new code
points added to ifOperStatus in the IF-MIB. |
| interface-status |
enumeration |
An enumerated value from the Interface Status TLV from the
last CCM received from the last MEP. It indicates the status
of the Interface within which the MEP transmitting the CCM
is configured, or the next lower Interface in the Interface
Stack, if the MEP is not configured within an Interface.
is-no-interface-status-tlv(0) Indicates either that no CCM has been
received or that no interface status TLV
was present in the last CCM received.
is-up(1) The interface is ready to pass packets.
is-down(2) The interface cannot pass packets
is-testing(3) The interface is in some test mode.
is-unknown(4) The interface status cannot be determined
for some reason.
is-dormant(5) The interface is not in a state to pass
packets but is in a pending state, waiting
for some external event.
is-not-present(6) Some component of the interface is missing
is-lower-layer-down(7) The interface is down due to state of the
lower layer interfaces
NOTE: A 0 value is used for isNoInterfaceStatusTLV, so that
these code points can be kept consistent with new code
points added to ifOperStatus in the IF-MIB. |
| interface-status |
enumeration |
An enumerated value from the Interface Status TLV from the
last CCM received from the last MEP. It indicates the status
of the Interface within which the MEP transmitting the CCM
is configured, or the next lower Interface in the Interface
Stack, if the MEP is not configured within an Interface.
is-no-interface-status-tlv(0) Indicates either that no CCM has been
received or that no interface status TLV
was present in the last CCM received.
is-up(1) The interface is ready to pass packets.
is-down(2) The interface cannot pass packets
is-testing(3) The interface is in some test mode.
is-unknown(4) The interface status cannot be determined
for some reason.
is-dormant(5) The interface is not in a state to pass
packets but is in a pending state, waiting
for some external event.
is-not-present(6) Some component of the interface is missing
is-lower-layer-down(7) The interface is down due to state of the
lower layer interfaces
NOTE: A 0 value is used for isNoInterfaceStatusTLV, so that
these code points can be kept consistent with new code
points added to ifOperStatus in the IF-MIB. |
| lowest-alarm-priority |
enumeration |
An enumerated value indicating the lowest priority defect that is
allowed to generate a fault alarm. |
| lowest-alarm-priority |
enumeration |
An enumerated value indicating the lowest priority defect that is
allowed to generate a fault alarm. |
| lowest-alarm-priority |
enumeration |
An enumerated value indicating the lowest priority defect that is
allowed to generate a fault alarm. |
| maintenance-association-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain association name. The value can be
one of the following:
vid(1) Primary VLAN ID.
12 bits represented in a 2-octet integer:
- 4 least significant bits of the first
byte contains the 4 most significant
bits of the 12 bits primary VID
- second byte contains the 8 least
significant bits of the primary VID
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
|0 0 0 0| (MSB) |
+-+-+-+-+-+-+-+-+
| VID LSB |
+-+-+-+-+-+-+-+-+
string(2) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used. (1..45) octets
integer(3) 2-octet integer/big endian
vpn-id(4) RFC 2685 VPN ID
3 octet VPN authority Organizationally
Unique Identifier followed by 4 octet VPN
index identifying VPN according to the OUI:
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| VPN OUI (MSB) |
+-+-+-+-+-+-+-+-+
| VPN OUI |
+-+-+-+-+-+-+-+-+
| VPN OUI (LSB) |
+-+-+-+-+-+-+-+-+
|VPN Index (MSB)|
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
|VPN Index (LSB)|
+-+-+-+-+-+-+-+-+
icc-based(32) raw ascii - between 8 and 13 characters
To support future extensions, the Dot1agCfmMaintAssocNameType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations must ensure that Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent. An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName pairs
must be changed together if the nameType changes.
The Maintenance Domain name and Maintenance Association name,
when put together into the CCM PDU, MUST total 48 octets or
less. If the Dot1agCfmMaintDomainNameType object contains
none(1), then the Dot1agCfmMaintAssocName object MUST be
45 octets or less in length. Otherwise, the length of
the Dot1agCfmMaintDomainName object plus the length of the
Dot1agCfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets. |
| maintenance-association-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain association name. The value can be
one of the following:
vid(1) Primary VLAN ID.
12 bits represented in a 2-octet integer:
- 4 least significant bits of the first
byte contains the 4 most significant
bits of the 12 bits primary VID
- second byte contains the 8 least
significant bits of the primary VID
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
|0 0 0 0| (MSB) |
+-+-+-+-+-+-+-+-+
| VID LSB |
+-+-+-+-+-+-+-+-+
string(2) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used. (1..45) octets
integer(3) 2-octet integer/big endian
vpn-id(4) RFC 2685 VPN ID
3 octet VPN authority Organizationally
Unique Identifier followed by 4 octet VPN
index identifying VPN according to the OUI:
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| VPN OUI (MSB) |
+-+-+-+-+-+-+-+-+
| VPN OUI |
+-+-+-+-+-+-+-+-+
| VPN OUI (LSB) |
+-+-+-+-+-+-+-+-+
|VPN Index (MSB)|
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
|VPN Index (LSB)|
+-+-+-+-+-+-+-+-+
icc-based(32) raw ascii - between 8 and 13 characters
To support future extensions, the Dot1agCfmMaintAssocNameType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations must ensure that Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent. An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName pairs
must be changed together if the nameType changes.
The Maintenance Domain name and Maintenance Association name,
when put together into the CCM PDU, MUST total 48 octets or
less. If the Dot1agCfmMaintDomainNameType object contains
none(1), then the Dot1agCfmMaintAssocName object MUST be
45 octets or less in length. Otherwise, the length of
the Dot1agCfmMaintDomainName object plus the length of the
Dot1agCfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets. |
| maintenance-association-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain association name. The value can be
one of the following:
vid(1) Primary VLAN ID.
12 bits represented in a 2-octet integer:
- 4 least significant bits of the first
byte contains the 4 most significant
bits of the 12 bits primary VID
- second byte contains the 8 least
significant bits of the primary VID
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
|0 0 0 0| (MSB) |
+-+-+-+-+-+-+-+-+
| VID LSB |
+-+-+-+-+-+-+-+-+
string(2) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used. (1..45) octets
integer(3) 2-octet integer/big endian
vpn-id(4) RFC 2685 VPN ID
3 octet VPN authority Organizationally
Unique Identifier followed by 4 octet VPN
index identifying VPN according to the OUI:
0 1 2 3 4 5 6 7 8
+-+-+-+-+-+-+-+-+
| VPN OUI (MSB) |
+-+-+-+-+-+-+-+-+
| VPN OUI |
+-+-+-+-+-+-+-+-+
| VPN OUI (LSB) |
+-+-+-+-+-+-+-+-+
|VPN Index (MSB)|
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
| VPN Index |
+-+-+-+-+-+-+-+-+
|VPN Index (LSB)|
+-+-+-+-+-+-+-+-+
icc-based(32) raw ascii - between 8 and 13 characters
To support future extensions, the Dot1agCfmMaintAssocNameType
textual convention SHOULD NOT be sub-typed in object type
definitions. It MAY be sub-typed in compliance statements in
order to require only a subset of these address types for a
compliant implementation.
Implementations must ensure that Dot1agCfmMaintAssocNameType
objects and any dependent objects (e.g.,
Dot1agCfmMaintAssocName objects) are consistent. An
inconsistentValue error must be generated if an attempt to
change an Dot1agCfmMaintAssocNameType object would, for
example, lead to an undefined Dot1agCfmMaintAssocName value.
In particular,
Dot1agCfmMaintAssocNameType/Dot1agCfmMaintAssocName pairs
must be changed together if the nameType changes.
The Maintenance Domain name and Maintenance Association name,
when put together into the CCM PDU, MUST total 48 octets or
less. If the Dot1agCfmMaintDomainNameType object contains
none(1), then the Dot1agCfmMaintAssocName object MUST be
45 octets or less in length. Otherwise, the length of
the Dot1agCfmMaintDomainName object plus the length of the
Dot1agCfmMaintAssocName object, added together, MUST total
less than or equal to 44 octets. |
| maintenance-domain-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain name. The value can be one of
the following:
none(1) No format specified, usually because
there is not (yet) a Maintenance
Domain Name. In this case, a zero
length string for the Domain
Name field is acceptable.
dns(2) Domain Name like string, globally unique
text string derived from a DNS name.
mac(3) MAC address + 2-octet (unsigned) integer.
string(4) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used.
Implementations must ensure that maintenance-domain-name-type
MOs and any dependent MOs (e.g., domain name) are consistent.
'domain type' and 'domain name' pairs
must be changed together if the 'domain type' changes. |
| maintenance-domain-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain name. The value can be one of
the following:
none(1) No format specified, usually because
there is not (yet) a Maintenance
Domain Name. In this case, a zero
length string for the Domain
Name field is acceptable.
dns(2) Domain Name like string, globally unique
text string derived from a DNS name.
mac(3) MAC address + 2-octet (unsigned) integer.
string(4) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used.
Implementations must ensure that maintenance-domain-name-type
MOs and any dependent MOs (e.g., domain name) are consistent.
'domain type' and 'domain name' pairs
must be changed together if the 'domain type' changes. |
| maintenance-domain-name-type |
enumeration |
A value that represents a type (and thereby the format)
of an eth-cfm domain name. The value can be one of
the following:
none(1) No format specified, usually because
there is not (yet) a Maintenance
Domain Name. In this case, a zero
length string for the Domain
Name field is acceptable.
dns(2) Domain Name like string, globally unique
text string derived from a DNS name.
mac(3) MAC address + 2-octet (unsigned) integer.
string(4) RFC2579 DisplayString, except that the
character codes 0-31 (decimal) are not
used.
Implementations must ensure that maintenance-domain-name-type
MOs and any dependent MOs (e.g., domain name) are consistent.
'domain type' and 'domain name' pairs
must be changed together if the 'domain type' changes. |
| mep-defect-flags |
bits |
A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
rdi-ccm A remote MEP is reported the RDI bit in its last CCM.
mac-status Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
remote-ccm The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
error-ccm The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
xcon-cmm The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out. |
| mep-defect-flags |
bits |
A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
rdi-ccm A remote MEP is reported the RDI bit in its last CCM.
mac-status Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
remote-ccm The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
error-ccm The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
xcon-cmm The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out. |
| mep-defect-flags |
bits |
A MEP can detect and report a number of defects, and multiple
defects can be present at the same time. These defects are:
rdi-ccm A remote MEP is reported the RDI bit in its last CCM.
mac-status Either some remote MEP is reporting its
Interface Status TLV as not isUp, or all remote
MEPs are reporting a Port Status TLV that
contains some value other than psUp.
remote-ccm The MEP is not receiving valid CCMs from at
least one of the remote MEPs.
error-ccm The MEP has received at least one invalid CCM
whose CCM Interval has not yet timed out.
xcon-cmm The MEP has received at least one CCM from
either another MAID or a lower MD Level whose
CCM Interval has not yet timed out. |
| mep-id-type |
uint16 |
The MEP Identifier which is an integer that uniquely
identifies the MEP over a given Maintenance Association. |
| mep-id-type |
uint16 |
The MEP Identifier which is an integer that uniquely
identifies the MEP over a given Maintenance Association. |
| mep-id-type |
uint16 |
The MEP Identifier which is an integer that uniquely
identifies the MEP over a given Maintenance Association. |
| mhf-creation-level-type |
union |
The Maintenance Domain Level (MD Level).
The value defer indicates that no MD Level has been assigned. |
| mhf-creation-level-type |
union |
The Maintenance Domain Level (MD Level).
The value defer indicates that no MD Level has been assigned. |
| mhf-creation-level-type |
union |
The Maintenance Domain Level (MD Level).
The value defer indicates that no MD Level has been assigned. |
| mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create
default-domain MHFs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
defer(4) The creation of MHFs is determined by the
corresponding Default Domain system's
mhf-creation value. |
| mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create
default-domain MHFs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
defer(4) The creation of MHFs is determined by the
corresponding Default Domain system's
mhf-creation value. |
| mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create
default-domain MHFs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
defer(4) The creation of MHFs is determined by the
corresponding Default Domain system's
mhf-creation value. |
| mip-authority |
enumeration |
Types of authorities to apply attributes to instantiated MIPs.
system(1) System settings.
default(2) Default domain.
association(3) Maintenance Association (MA). |
| mip-authority |
enumeration |
Types of authorities to apply attributes to instantiated MIPs.
system(1) System settings.
default(2) Default domain.
association(3) Maintenance Association (MA). |
| mip-authority |
enumeration |
Types of authorities to apply attributes to instantiated MIPs.
system(1) System settings.
default(2) Default domain.
association(3) Maintenance Association (MA). |
| mp-direction |
enumeration |
The direction the MEP faces on the Bridge port.
If 'down' the Management Point (MP) sends CFM PDUs away from the
MAC Relay Entity. If 'up' the MP sends CFM PDUs towards the MAC Relay Entity. |
| mp-direction |
enumeration |
The direction the MEP faces on the Bridge port.
If 'down' the Management Point (MP) sends CFM PDUs away from the
MAC Relay Entity. If 'up' the MP sends CFM PDUs towards the MAC Relay Entity. |
| mp-direction |
enumeration |
The direction the MEP faces on the Bridge port.
If 'down' the Management Point (MP) sends CFM PDUs away from the
MAC Relay Entity. If 'up' the MP sends CFM PDUs towards the MAC Relay Entity. |
| mp-level |
int32 |
The Management Point (MP) level.
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM packets. Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links. |
| mp-level |
int32 |
The Management Point (MP) level.
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM packets. Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links. |
| mp-level |
int32 |
The Management Point (MP) level.
Higher numbers correspond to higher Maintenance Domains,
those with the greatest physical reach, with the highest
values for customers' CFM packets. Lower numbers correspond
to lower Maintenance Domains, those with more limited
physical reach, with the lowest values for CFM PDUs
protecting single bridges or physical links. |
| permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. The valid
values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent.
manage(3) The Management Address Length and
Management Address of the Sender ID TLV
are to be sent.
chassis-manage(4) The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address
Length and Management Address fields are
all to be sent.
defer(5) The contents of the Sender ID TLV are
determined by the corresponding
Maintenance Domain permission variable |
| permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. The valid
values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent.
manage(3) The Management Address Length and
Management Address of the Sender ID TLV
are to be sent.
chassis-manage(4) The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address
Length and Management Address fields are
all to be sent.
defer(5) The contents of the Sender ID TLV are
determined by the corresponding
Maintenance Domain permission variable |
| permission-type |
enumeration |
Indicates what, if anything, is to be included in the Sender
ID TLV transmitted in CCMs, LBMs, LTMs, and LTRs. The valid
values are:
none(1) The Sender ID TLV is not to be sent.
chassis(2) The Chassis ID Length, Chassis ID
Subtype, and Chassis ID fields of the
Sender ID TLV are to be sent.
manage(3) The Management Address Length and
Management Address of the Sender ID TLV
are to be sent.
chassis-manage(4) The Chassis ID Length, Chassis ID
Subtype, Chassis ID, Management Address
Length and Management Address fields are
all to be sent.
defer(5) The contents of the Sender ID TLV are
determined by the corresponding
Maintenance Domain permission variable |
| port-status |
enumeration |
An enumerated value from the Port Status TLV from the last CCM
received from the last MEP. It indicates the ability of the
Bridge Port on which the transmitting MEP resides to pass
ordinary data, regardless of the status of the MAC.
ps-no-port-state-tlv(0) Indicates either that no CCM has been
received or that no port status TLV was
present in the last CCM received.
ps-blocked(1) Ordinary data cannot pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
false.
ps-up(2): Ordinary data can pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
true.
NOTE: A 0 value is used for ps-no-port-state-tlv, so that
additional code points can be added in a manner
consistent with the Dot1agCfmInterfaceStatus textual
convention. |
| port-status |
enumeration |
An enumerated value from the Port Status TLV from the last CCM
received from the last MEP. It indicates the ability of the
Bridge Port on which the transmitting MEP resides to pass
ordinary data, regardless of the status of the MAC.
ps-no-port-state-tlv(0) Indicates either that no CCM has been
received or that no port status TLV was
present in the last CCM received.
ps-blocked(1) Ordinary data cannot pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
false.
ps-up(2): Ordinary data can pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
true.
NOTE: A 0 value is used for ps-no-port-state-tlv, so that
additional code points can be added in a manner
consistent with the Dot1agCfmInterfaceStatus textual
convention. |
| port-status |
enumeration |
An enumerated value from the Port Status TLV from the last CCM
received from the last MEP. It indicates the ability of the
Bridge Port on which the transmitting MEP resides to pass
ordinary data, regardless of the status of the MAC.
ps-no-port-state-tlv(0) Indicates either that no CCM has been
received or that no port status TLV was
present in the last CCM received.
ps-blocked(1) Ordinary data cannot pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
false.
ps-up(2): Ordinary data can pass freely through
the port on which the remote MEP resides.
Value of enableRmepDefect is equal to
true.
NOTE: A 0 value is used for ps-no-port-state-tlv, so that
additional code points can be added in a manner
consistent with the Dot1agCfmInterfaceStatus textual
convention. |
| remote-mep-state-type |
enumeration |
Operational state of the remote MEP state machine. This
state machine monitors the reception of valid CCMs from a
remote MEP with a specific MEPID. It uses a timer that
expires in 3.5 times the length of time indicated by the
ccm-interval leaf
mep-idle(1) Momentary state during reset.
mep-start(2) The timer has not expired since the
state machine was reset, and no valid
CCM has yet been received.
mep-failed(3) The timer has expired, both since the
state machine was reset, and since a
valid CCM was received.
mep-ok(4) The timer has not expired since a
valid CCM was received. |
| remote-mep-state-type |
enumeration |
Operational state of the remote MEP state machine. This
state machine monitors the reception of valid CCMs from a
remote MEP with a specific MEPID. It uses a timer that
expires in 3.5 times the length of time indicated by the
ccm-interval leaf
mep-idle(1) Momentary state during reset.
mep-start(2) The timer has not expired since the
state machine was reset, and no valid
CCM has yet been received.
mep-failed(3) The timer has expired, both since the
state machine was reset, and since a
valid CCM was received.
mep-ok(4) The timer has not expired since a
valid CCM was received. |
| remote-mep-state-type |
enumeration |
Operational state of the remote MEP state machine. This
state machine monitors the reception of valid CCMs from a
remote MEP with a specific MEPID. It uses a timer that
expires in 3.5 times the length of time indicated by the
ccm-interval leaf
mep-idle(1) Momentary state during reset.
mep-start(2) The timer has not expired since the
state machine was reset, and no valid
CCM has yet been received.
mep-failed(3) The timer has expired, both since the
state machine was reset, and since a
valid CCM was received.
mep-ok(4) The timer has not expired since a
valid CCM was received. |
| statistics-opcode-name |
enumeration |
An enumerated value indicating the CFM PDU Opcode to which a statistic
may be associated.
total(0) The total CFM PDUs of all types below.
other(1) Indicates the CFM PDU type does not match
any other type explicitly detailed below.
ccm(2) Connectivity check messages.
lbr(3) Loopback response messages.
lbm(4) Loopback request messages.
ltr(5) Linktrace response messages.
ltm(6) Linktrace request messages.
ais(7) Alarm indication signal messages.
lck(8) Ethernet locked signal messages.
tst(9) Ethernet test signal messages.
laps(10) Linear automatic protection switching messages.
raps(11) Ring automatic protection switching messages.
mcc(12) Maintenance communications channel messages.
lmr(13) Ethernet loss measurement response messages.
lmm(14) Ethernet loss measurement messages.
1dm(15) One way delay measurement messages.
dmr(16) Delay measurement response messages.
dmm(17) Delay measurement message.
exr(18) Ethernet experimental response messages.
exm(19) Ethernet experimental messages.
csf(20) Client signal fail messages.
vsr(21) Vendor specific response messages.
vsm(22) Vendor specific messages.
1sl(23) One way synthetic loss measurement messages.
slr(24) Synthetic loss measurement response messages.
slm(25) Synthetic loss measurement messages.
gnm(26) Generic notification messages. |
| statistics-opcode-name |
enumeration |
An enumerated value indicating the CFM PDU Opcode to which a statistic
may be associated.
total(0) The total CFM PDUs of all types below.
other(1) Indicates the CFM PDU type does not match
any other type explicitly detailed below.
ccm(2) Connectivity check messages.
lbr(3) Loopback response messages.
lbm(4) Loopback request messages.
ltr(5) Linktrace response messages.
ltm(6) Linktrace request messages.
ais(7) Alarm indication signal messages.
lck(8) Ethernet locked signal messages.
tst(9) Ethernet test signal messages.
laps(10) Linear automatic protection switching messages.
raps(11) Ring automatic protection switching messages.
mcc(12) Maintenance communications channel messages.
lmr(13) Ethernet loss measurement response messages.
lmm(14) Ethernet loss measurement messages.
1dm(15) One way delay measurement messages.
dmr(16) Delay measurement response messages.
dmm(17) Delay measurement message.
exr(18) Ethernet experimental response messages.
exm(19) Ethernet experimental messages.
csf(20) Client signal fail messages.
vsr(21) Vendor specific response messages.
vsm(22) Vendor specific messages.
1sl(23) One way synthetic loss measurement messages.
slr(24) Synthetic loss measurement response messages.
slm(25) Synthetic loss measurement messages.
gnm(26) Generic notification messages. |
| statistics-opcode-name |
enumeration |
An enumerated value indicating the CFM PDU Opcode to which a statistic
may be associated.
total(0) The total CFM PDUs of all types below.
other(1) Indicates the CFM PDU type does not match
any other type explicitly detailed below.
ccm(2) Connectivity check messages.
lbr(3) Loopback response messages.
lbm(4) Loopback request messages.
ltr(5) Linktrace response messages.
ltm(6) Linktrace request messages.
ais(7) Alarm indication signal messages.
lck(8) Ethernet locked signal messages.
tst(9) Ethernet test signal messages.
laps(10) Linear automatic protection switching messages.
raps(11) Ring automatic protection switching messages.
mcc(12) Maintenance communications channel messages.
lmr(13) Ethernet loss measurement response messages.
lmm(14) Ethernet loss measurement messages.
1dm(15) One way delay measurement messages.
dmr(16) Delay measurement response messages.
dmm(17) Delay measurement message.
exr(18) Ethernet experimental response messages.
exm(19) Ethernet experimental messages.
csf(20) Client signal fail messages.
vsr(21) Vendor specific response messages.
vsm(22) Vendor specific messages.
1sl(23) One way synthetic loss measurement messages.
slr(24) Synthetic loss measurement response messages.
slm(25) Synthetic loss measurement messages.
gnm(26) Generic notification messages. |
| tmnx-mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create MHFs
used for primary-vlan MIPs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
static(32) Multiple MHFs can be created on the
primary VID on any bridge port through
which this primary VID can pass. |
| tmnx-mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create MHFs
used for primary-vlan MIPs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
static(32) Multiple MHFs can be created on the
primary VID on any bridge port through
which this primary VID can pass. |
| tmnx-mhf-creation-type |
enumeration |
Indicates whether the Management Entity can create MHFs
used for primary-vlan MIPs.
The valid values are:
none(1) No MHFs can be created for this VID.
default(2) MHFs can be created on this VID on any
Bridge port through which this VID can
pass.
explicit(3) MHFs can be created for this VID only on
Bridge ports through which this VID can
pass, and only if a MEP is created at some
lower MD Level.
static(32) Multiple MHFs can be created on the
primary VID on any bridge port through
which this primary VID can pass. |
| vlan-id-or-none |
union |
The VLAN ID that uniquely identifies a specific VLAN,
or no VLAN. The special value of none is used to
indicate that no VLAN ID is present or used. This can
be used in any situation where an object or a table entry
must refer either to a specific VLAN, or to no VLAN. |
| vlan-id-or-none |
union |
The VLAN ID that uniquely identifies a specific VLAN,
or no VLAN. The special value of none is used to
indicate that no VLAN ID is present or used. This can
be used in any situation where an object or a table entry
must refer either to a specific VLAN, or to no VLAN. |
| vlan-id-or-none |
union |
The VLAN ID that uniquely identifies a specific VLAN,
or no VLAN. The special value of none is used to
indicate that no VLAN ID is present or used. This can
be used in any situation where an object or a table entry
must refer either to a specific VLAN, or to no VLAN. |