This attribute specifies whether the interface is on an OAM segment
boundary.
When yes is selected, the interface is on an OAM segment boundary
and all connections passing through the interface terminate OAM
segment cells.
When no is selected, the interface is not on an OAM segment
boundary and the interface permits the segment cells to be passed
transparently.
Parsed from file nortelPC-atmCoreV1.mib.txt
Company: None
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
This attribute specifies whether the interface is on an OAM segment
boundary.
When yes is selected, the interface is on an OAM segment boundary
and all connections passing through the interface terminate OAM
segment cells.
When no is selected, the interface is not on an OAM segment
boundary and the interface permits the segment cells to be passed
transparently.
Parsed from file Nortel-MsCarrier-MscPassport-AtmCoreMIB.mib
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
Vendor: Northern Telecom, Ltd.
Module: Nortel-MsCarrier-MscPassport-AtmCoreMIB
[Automatically extracted from oidview.com]
mscAtmIfOamSegmentBoundary OBJECT-TYPE SYNTAX INTEGER { no(0), yes(1) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute specifies whether the interface is on an OAM segment boundary. When yes is selected, the interface is on an OAM segment boundary and all connections passing through the interface terminate OAM segment cells. When no is selected, the interface is not on an OAM segment boundary and the interface permits the segment cells to be passed transparently." DEFVAL { yes } ::= { mscAtmIfProvEntry 30 }
mscAtmIfOamSegmentBoundary OBJECT-TYPE SYNTAX INTEGER { no(0), yes(1) } ACCESS read-write STATUS mandatory DESCRIPTION "This attribute specifies whether the interface is on an OAM segment boundary. When yes is selected, the interface is on an OAM segment boundary and all connections passing through the interface terminate OAM segment cells. When no is selected, the interface is not on an OAM segment boundary and the interface permits the segment cells to be passed transparently." DEFVAL { yes } ::= { mscAtmIfProvEntry 30 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.562.36.2.1.114.110.1.10 | mscAtmIfInterfaceName | 0 | 0 | This attribute associates the AtmIf component with a specific interface on a Function Processorfor example, Lp/1 Ds3/0. This impl… |
1.3.6.1.4.1.562.36.2.1.114.110.1.20 | mscAtmIfType | 0 | 0 | mscAtmIftype |
1.3.6.1.4.1.562.36.2.1.114.110.1.40 | mscAtmIfMaxVpcs | 0 | 0 | This attribute specifies the maximum number of VPCs that can be configured on this AtmIf. The value must not exceed the total num… |
1.3.6.1.4.1.562.36.2.1.114.110.1.50 | mscAtmIfMaxVccs | 0 | 0 | This attribute specifies the maximum number of usable VCCs that can be configured on this AtmIf. The value must not exceed the nu… |
1.3.6.1.4.1.562.36.2.1.114.110.1.60 | mscAtmIfTrafficShaping | 0 | 0 | mscAtmIftrafficShaping |
1.3.6.1.4.1.562.36.2.1.114.110.1.70 | mscAtmIfUnshapedTransmitQueueing | 0 | 0 | It is migrated in P6.0 to the attributes of the same name under each ATM service category component of the AtmIf CA. This attrib… |
1.3.6.1.4.1.562.36.2.1.114.110.1.80 | mscAtmIfUsageParameterControl | 0 | 0 | It is migrated in P6.0 to the attributes of the same name under each ATM service category component of the AtmIf CA. This attrib… |
1.3.6.1.4.1.562.36.2.1.114.110.1.85 | mscAtmIfMaxVpiBits | 0 | 0 | This attribute specifies the maximum number of VPI bits that may be active for this AtmIf. These bits start at the least signifi… |
1.3.6.1.4.1.562.36.2.1.114.110.1.90 | mscAtmIfRemoteAtmInterfaceLabel | 0 | 0 | This attribute specifies a unique indication of the remote ATM service or interface component connected to this one. The value o… |
1.3.6.1.4.1.562.36.2.1.114.110.1.91 | mscAtmIfTxCellMemory | 0 | 0 | mscAtmIftxCellMemory |
1.3.6.1.4.1.562.36.2.1.114.110.1.100 | mscAtmIfFaultHoldOffTime | 0 | 0 | mscAtmIfFaultHoldOfftime |
1.3.6.1.4.1.562.36.2.1.114.110.1.110 | mscAtmIfCtdCalculation | 0 | 0 | This attribute specifies whether cell transfer delay calculation should be performed on loopback cells for each SPVC and SPVP con… |