INTRODUCED 2.0.1
The status of the phasor for this SAF.
The first octet is used to indicate transmit
phasor status. The bits are interpretted as
follows (bit 1 is the least significant bit
of the octet):
bit 1: phasor underflow
bit 2: phasor overflow
bits 3-6: unused
bit 7: software phasor (if clear,
hardware phasor)
bit 8: phasor not applicable
The second octet is used to indicate receive
phasor status. The bits are interpretted as
follows (bit 1 is the least significant bit
of the octet):
bit 1: phasor underflow
bit 2: phasor overflow
bits 3-6: unused
bit 7: software phasor (if clear,
hardware phasor)
bit 8: phasor not applicable
For both phasors (receive and transmit), if
the phasor is OK, then the octet will be
set to 0 for a hardware phasor, or x40 for
a software phasor. If there is no phasor of
that type (receive or transmit), then the
octet will be set to x80.
If the SAF does not support any phasors,
then the value returned for this attribute
will be x8080.
Parsed from file STMIB.mib.txt
Company: None
Module: STMIB
INTRODUCED 2.0.1
The status of the phasor for this SAF.
The first octet is used to indicate transmit
phasor status. The bits are interpretted as
follows (bit 1 is the least significant bit
of the octet):
bit 1: phasor underflow
bit 2: phasor overflow
bits 3-6: unused
bit 7: software phasor (if clear,
hardware phasor)
bit 8: phasor not applicable
The second octet is used to indicate receive
phasor status. The bits are interpretted as
follows (bit 1 is the least significant bit
of the octet):
bit 1: phasor underflow
bit 2: phasor overflow
bits 3-6: unused
bit 7: software phasor (if clear,
hardware phasor)
bit 8: phasor not applicable
For both phasors (receive and transmit), if
the phasor is OK, then the octet will be
set to 0 for a hardware phasor, or x40 for
a software phasor. If there is no phasor of
that type (receive or transmit), then the
octet will be set to x80.
If the SAF does not support any phasors,
then the value returned for this attribute
will be x8080.
Parsed from file STMIB.mib
Module: STMIB
Vendor: Timeplex
Module: STMIB
[Automatically extracted from oidview.com]
restSafPhasorStatus OBJECT-TYPE SYNTAX OCTET STRING (SIZE (2)) ACCESS read-only STATUS mandatory DESCRIPTION "INTRODUCED 2.0.1 The status of the phasor for this SAF. The first octet is used to indicate transmit phasor status. The bits are interpretted as follows (bit 1 is the least significant bit of the octet): bit 1: phasor underflow bit 2: phasor overflow bits 3-6: unused bit 7: software phasor (if clear, hardware phasor) bit 8: phasor not applicable The second octet is used to indicate receive phasor status. The bits are interpretted as follows (bit 1 is the least significant bit of the octet): bit 1: phasor underflow bit 2: phasor overflow bits 3-6: unused bit 7: software phasor (if clear, hardware phasor) bit 8: phasor not applicable For both phasors (receive and transmit), if the phasor is OK, then the octet will be set to 0 for a hardware phasor, or x40 for a software phasor. If there is no phasor of that type (receive or transmit), then the octet will be set to x80. If the SAF does not support any phasors, then the value returned for this attribute will be x8080." ::= { restSafEntry 19 }
restSafPhasorStatus OBJECT-TYPE SYNTAX OCTET STRING (SIZE (2)) ACCESS read-only STATUS mandatory DESCRIPTION "INTRODUCED 2.0.1 The status of the phasor for this SAF. The first octet is used to indicate transmit phasor status. The bits are interpretted as follows (bit 1 is the least significant bit of the octet): bit 1: phasor underflow bit 2: phasor overflow bits 3-6: unused bit 7: software phasor (if clear, hardware phasor) bit 8: phasor not applicable The second octet is used to indicate receive phasor status. The bits are interpretted as follows (bit 1 is the least significant bit of the octet): bit 1: phasor underflow bit 2: phasor overflow bits 3-6: unused bit 7: software phasor (if clear, hardware phasor) bit 8: phasor not applicable For both phasors (receive and transmit), if the phasor is OK, then the octet will be set to 0 for a hardware phasor, or x40 for a software phasor. If there is no phasor of that type (receive or transmit), then the octet will be set to x80. If the SAF does not support any phasors, then the value returned for this attribute will be x8080." ::= { restSafEntry 19 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.16.101.1.2.2.15.1.1.1 | restSafAddr | 0 | 0 | SAF address. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.2 | restSafStatus | 0 | 0 | Indicates whether the SAF is synchronized or not, or whether the SAF is currently in the middle of a frame switch. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.3 | restSafSubStatus | 0 | 0 | If the SAF status is out of sync, then this attribute indicates if it is due to an error or not. If the SAF is in sync or in the m… |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.4 | restSafRemoteNode | 0 | 0 | The node in which the remote side of this SAF connection resides. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.5 | restSafRemoteAddr | 0 | 0 | The address of the remote side of this SAF connection. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.6 | restSafInlNumber | 0 | 0 | The local INL number that this SAF is located on. For a local SAF, this attribute shall return 32. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.7 | restSafBandwidthAvail | 0 | 0 | The available (unused) bandwidth in this SAF according to the NCP. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.8 | restSafNumChannels | 0 | 0 | The number of subrate channels currently connected through this SAF according to the NCP. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.9 | restSafHWPhasorStatus | 0 | 0 | DEPRECATED 2.0.1 This attribute will always return x8080, which means not applicable. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.10 | restSafSWPhasorStatus | 0 | 0 | DEPRECATED 2.0.1 This attribute will always return x8080, which means not applicable. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.11 | restSafModNumChannels | 0 | 0 | INTRODUCED 2.0.1 The number of subrate channels currently connected through this SAF according to the module that this endpoint of… |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.12 | restSafModBandwidthAvail | 0 | 0 | INTRODUCED 2.0.1 The available (unused) bandwidth in this SAF according to the module that this endpoint of the SAF resides on. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.13 | restSafDiagnostics | 0 | 0 | INTRODUCED 2.0.1 clearStats will clear the counters in this MIB section. setLoopback will initiate a loopback on this SAF. This wil… |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.14 | restSafFrameSwitchLocation | 0 | 0 | INTRODUCED 2.0.1 If a frame switch is currently occurring on this SAF, then this attribute indicates the location of that frame sw… |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.15 | restSafFrameSwitchIndicator | 0 | 0 | INTRODUCED 2.0.1 Indicates if a frame switch is needed on this SAF or not. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.16 | restSafRemoteStatus | 0 | 0 | INTRODUCED 2.0.1 The view of the remote endpoint of SAF from the module that this endpoint of the SAF resides on. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.17 | restSafSyncErrors | 0 | 0 | INTRODUCED 2.0.1 The number of sync errors on this SAF. |
1.3.6.1.4.1.16.101.1.2.2.15.1.1.18 | restSafOosErrors | 0 | 0 | INTRODUCED 2.0.1 The number of OOS errors on this SAF. |