LUM-OTN-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
1
Rows
1
Columns
34

otnSmTcmPmTable

table deprecated
.1.3.6.1.4.1.8708.2.34.2.2.1 · 1 row entry · 34 columns
Uses the infinera variant from /opt/observium/mibs/infinera.
Command help
Walk otnSmTcmPmTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LUM-OTN-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-OTN-MIB::otnSmTcmPmTable'
The OTN table.
otnSmTcmPmEntry row .1.3.6.1.4.1.8708.2.34.2.2.1.1
An entry in the OTN table.
Indexes
Column Syntax OID
An arbitrary index assigned to each entry.
Unsigned32
Constraints:
range: 1-2147483647
.1.3.6.1.4.1.8708.2.34.2.2.1.1.1
The name of the object, for example
'sm:1:2:1-2', where the numbers indicate the
subrack, slot and port numbers.
LUM-TCMgmtNameString
Type Constraints:
range: 0..255
Description:
An octet string containing administrative
information, in human-readable form.

More or less the same as SnmpAdminString
defined in SNMP-FRAMEWORK-MIB.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.2
The type of object, SM, TCM or PM.
LUM-TCOtnMonitorType
Type Values:
0sm
1pm
2tcm
Description:
MonitorType for an OTN object.

sm - section monitor

pm - path monitor

tcm - tandem connection monitor
.1.3.6.1.4.1.8708.2.34.2.2.1.1.3
MontorConfig tells if monitor is terminated or not.
LUM-TCOtnMonitorConfig
Type Values:
0terminated
1transparent
Description:
Monitor Configuration for an OTN object.

terminated - section is terminated in port

transparent - monitor passes the port transparent
.1.3.6.1.4.1.8708.2.34.2.2.1.1.4
Tcm that will be terminated in this node. This is none
or tcm1, tcm2, tcm3, tcm4, tcm5, tcm6. If one tcm is selected
the alarms on this tcm will also be used as protection criteria.
Enumerationr/w
Enumerated Values:
0none
1tcm1
2tcm2
3tcm3
4tcm4
5tcm5
6tcm6
.1.3.6.1.4.1.8708.2.34.2.2.1.1.5
User configurable label.
SNMPv2-TCDisplayStringr/w
Type Constraints:
range: 0..255
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.6
The subrack number for this protected
interface.
LUM-TCSubrackNumber
Type Constraints:
range: 0..15
Description:
The number of a subrack within a network element.

0 signifies an undefined subrack number.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.7
The slot number for this protected
interface.
LUM-TCSlotNumber
Type Constraints:
range: 0..22
Description:
The number of a slot within a subrack.

0 signifies an undefined slot number.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.8
The number of the port where the interface is
located.
LUM-TCPortNumber
Type Constraints:
range: 0..116
Description:
The number of a port on a board.
If an interface has two numbers, the lowest number is used.

0 signifies an undefined port number.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.9
The administrative state for the interface.

down - The interface should be inactive.

service - The object is activated but alarms
are suppressed. Intended for use during service
or re-confi…
LUM-TCBoardOrInterfaceAdminStatusr/w
Type Values:
1down
2service
3up
Description:
The administrative state for a board or
interface.

down - The board/interface should be inactive.

service - The board/interface is activated but
alarms are suppressed. Intended for use during
servi…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.10
The operational state for the interface.

notPresent - The interface is not available.

down - The interface is de-activated or there are
faults preventing it from going to the 'up'-state.
LUM-TCBoardOrInterfaceOperStatus
Type Values:
1notPresent
2down
3up
Description:
The operational state for a board or interface.

notPresent - The board/interface is not available.

down - The board/interface is de-activated or
there are faults preventing it from going to the
'up…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.11
The Source Destination Access Point Identifier to be
transmitted from this interface.

Note, it is only possible to enter 15 characters since first
character is added automatically according to standard.
SNMPv2-TCDisplayStringr/w
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.12
The received Source Access Point Identifier for this interface.
Unsigned32
Constraints:
range: 1-2147483647
.1.3.6.1.4.1.8708.2.34.2.2.1.1.13
The received Source Access Point Identifier for this interface.
SNMPv2-TCDisplayString
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.14
SAPI used for matching against the received SAPI.

Note, it is only possible to enter 15 characters since first
character is added automatically according to standard.
SNMPv2-TCDisplayStringr/w
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.15
The Destination Access Point Identifier to be transmitted from this
interface.

Note, it is only possible to enter 15 characters since first
character is added automatically according to standard.
SNMPv2-TCDisplayStringr/w
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.16
The received Destination Access Point Identifier for this interface.
Unsigned32
Constraints:
range: 1-2147483647
.1.3.6.1.4.1.8708.2.34.2.2.1.1.17
The received Destination Access Point Identifier for this interface.
SNMPv2-TCDisplayString
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.18
DAPI used for matching against the received DAPI.

Note, it is only possible to enter 15 characters since first
character is added automatically according to standard.
SNMPv2-TCDisplayStringr/w
Constraints:
range: 0-15
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.19
The operator specific trace identifier to be transmitted
from this interface.

Set to empty string for default value.

<IP address>:<subrack>:<slot>:<port>

Note that only th…
SNMPv2-TCDisplayStringr/w
Constraints:
range: 0-31
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.20
The received operator specific trace identifier for this
interface.
SNMPv2-TCDisplayString
Constraints:
range: 0-31
Description:
Represents textual information taken from the NVT ASCII

character set, as defined in pages 4, 10-11 of RFC 854.

To summarize RFC 854, the NVT ASCII repertoire specifies:

- the use of c…
.1.3.6.1.4.1.8708.2.34.2.2.1.1.21
The method to detect a TTI identifier mismatch value.
LUM-TCOtnTIMDetModer/w
Type Values:
0sapi
1dapi
2both
Description:
TTI Mismatch detection mode.

sapi - TTI MM is detected based on SAPI

dapi - TTI MM is detected based on DAPI

both - TTI MM is detected based on SAPI and DAPI
.1.3.6.1.4.1.8708.2.34.2.2.1.1.22
Controls if the trace identifier mismatch alarm
should be raised. If trace alarm mode is enabled, BDI is sent
in backward direction if received trace and expected trace
differs.

disabled - The alarm is di…
Enumerationr/w
Enumerated Values:
1disabled
2enabled
.1.3.6.1.4.1.8708.2.34.2.2.1.1.23
Property mask.
LUM-TCObjectProperty
Type Constraints:
range: 0..4294967295
Description:
A bitmask of length 32 encoding certain properties
of an object.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.24
Indicates if the expected SM/PM/TCMtrace identifier (SAPI+DAPI)
differs from the received trace identifier.

A: The received trace identifier differs from
the expected trace identifier.

D: T…
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.25
Indicates if backward defect indication (BDI) alarm
exists or not.

A: BDI is active.

D: BDI is inactive.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.26
Alarm indication signal.

A: An 'all ones' PM/TCM signal is detected.

D: PM/TCM signal recovered.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.27
Open connection Indication.

A: A 'open connection' PM/TCM signal is detected.

D: PM/TCM signal recovered.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.28
Client Maintenance Indication.

A: A 'client maintenance' PM signal is detected.

D: PM/TCM signal recovered.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.29
Locked Defect Indication.

A: A 'Locked Defect' PM/TCM signal is detected.

D: PM/TCM signal recovered.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.30
Command to change which TCM that is terminated.
LUM-TCCommandString
Description:
tbd
.1.3.6.1.4.1.8708.2.34.2.2.1.1.31
No terminated TCM.

A: The TCM is not terminated anywhere.

D: The TCM is terminated somewhere.
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.32
Indicates an incoming frame alignment error.

A: IAE is active

D: IAE is inactive
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.33
Indicates a backward incoming alignment error.

A: BIAE is active

D: BIAE is inactive
LUM-TCFaultStatus
Type Values:
1ok
2alarm
Description:
A value indicating the current state
of a potential fault condition leading to
an alarm for an object.

ok - indicates that no fault condition is present
and no alarm is active or the alarm has been cleared.
.1.3.6.1.4.1.8708.2.34.2.2.1.1.34