SL-XPDR-MIB

All MIBs › SL-XPDR-MIB

Organization: Smartoptics AS

Last Updated: 2005-01-25

Description: MIB for optical transponder connections and ODU cross-connections on Smartoptics SiteLight gear supporting DS3, GbE, FC, OC-n, and OTN service types

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is SL-XPDR-MIB?

SL-XPDR-MIB is a vendor MIB from Smartoptics for the SiteLight optical transport platform, covering optical transponder connections and ODU (Optical channel Data Unit) cross-connections that carry client services such as DS3, GbE, Fibre Channel, OC-n SONET/SDH, and OTN. It exposes connection configuration between transponder interfaces, service-type selection, rate control, multiplexing mode, and loss-of-signal (LOS) propagation behavior. For hardware/software status monitoring, its most relevant fields are xpdrConnConfigLosPropagation (whether a loss-of-signal condition is passed through the cross-connect) and xpdrConnConfigRateControlAdmin/Oper (administrative vs operational rate-control state), which together reveal whether an optical circuit is actually carrying traffic as configured. It operates within the broader ITU-T OTN/G.709 framework implied by its ODU cross-connect and service-type model, and likely complements a transport-layer MIB covering the physical optical interfaces themselves. It is deployed in metro/regional optical transport networks where Smartoptics transponders multiplex client signals onto DWDM links. Engineers can download the SL-XPDR-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SL-XPDR-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Smartoptics SiteLight optical transponder/transport platform

Monitoring Examples

An operator would inspect xpdrConnConfigTable/xpdrConnConfigEntry, keyed by xpdrConnConfigIf1 and xpdrConnConfigIf2, to confirm which client interface is cross-connected to which line interface and verify xpdrServiceType matches the expected client signal (e.g., GbE vs OC-n). Checking xpdrConnConfigRateControlAdmin against xpdrConnConfigRateControlOper would reveal a mismatch where a configured rate-limited circuit is not operating as intended. xpdrConnConfigLosPropagation combined with slXpdrLastChange helps an operator determine whether a recent alarm was caused by a genuine loss-of-signal condition propagating through the cross-connect versus a configuration change.

What Can Be Monitored

transponder cross-connect mapping
service type (DS3/GbE/FC/OC-n/OTN)
rate control admin vs operational state
loss-of-signal propagation
multiplexing (inband) mode
last configuration change

Imported Objects

From IF-MIB

InterfaceIndex

From PerfHist-TC-MIB

PerfCurrentCount
PerfIntervalCount
PerfTotalCount

From SL-NE-MIB

sitelight

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
RowStatus
TimeStamp
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
slXpdr	1.3.6.1.4.1.4515.1.8			This MIB module describes the optical connections.
slXpdrConn	1.3.6.1.4.1.4515.1.8.1
xpdrConnConfigTable	1.3.6.1.4.1.4515.1.8.1.1		not-accessible	The connection table contains for each transponding connection a single bi-directional entry. The index to the table is the ifIndex of both XPDR interfaces. The ifType valued used for the index is: 196.
xpdrConnConfigEntry	1.3.6.1.4.1.4515.1.8.1.1.1		not-accessible	An entry in the transponding connection table.
NUM xpdrConnConfigIf1	1.3.6.1.4.1.4515.1.8.1.1.1.1	InterfaceIndex	read-only	The first XPDR interface.
NUM xpdrConnConfigIf2	1.3.6.1.4.1.4515.1.8.1.1.1.2	InterfaceIndex	read-only	The second XPDR interface.
INT xpdrConnConfigRateControlAdmin	1.3.6.1.4.1.4515.1.8.1.1.1.3	INTEGER	read-write	This variable ask the rate of the traffic used by this interface. Frequency is in Kbp/s. The value 0-30 is used for rate control Bypass.
INT xpdrConnConfigRateControlOper	1.3.6.1.4.1.4515.1.8.1.1.1.4	INTEGER	read-only	This variable tells the rate of the traffic used by this interface. Frequency is in Kbp/s. The value 0 returned for rate control Bypass.
T/F xpdrConnConfigLosPropagation	1.3.6.1.4.1.4515.1.8.1.1.1.5	TruthValue	read-write	This object is used to detrmine if the LOS propagation should be active.
XPD xpdrServiceType	1.3.6.1.4.1.4515.1.8.1.1.1.6	XpdrServiceType	read-write	The service type of the transponder.
INT xpdrConnAddMask	1.3.6.1.4.1.4515.1.8.1.1.1.7	INTEGER	read-write	This object is a bit mask relevant only for Muxponder entry. It contains a bit for each Muxponder service. To add a service the management should set the corresponding bit to 1. To remove a service the bit should be set to 0. For ODU allocation, the value of xpdrConnAddMask should be set to reflect the odus/time-slots provisioned for the service according to the following rules: a. For ODU1 the first byte is 0; for ODU0 the first byte is 1. b. The second byte. Is equal to: i. The 4 bits of the first nibble correspond to Uplink 1 allocated odus counted from right to left ii. The 4 bits of the second nibble correspond to Uplink 2 allocated odus counted from right to left c. The Third and Forth bytes keep bit-mask of the allocated time-slots within the odu.
INT xpdrMuxInbandAdmin	1.3.6.1.4.1.4515.1.8.1.1.1.8	INTEGER	read-write	This object is relevant only for muxponder. up value means that the muxponder inband management is enabled.
INT xpdrMuxInbandOper	1.3.6.1.4.1.4515.1.8.1.1.1.9	INTEGER	read-only	The operational state of the inband interface.
INT xpdrDirection	1.3.6.1.4.1.4515.1.8.1.1.1.10	INTEGER	read-write	This object is used for unidirectional services. The upper port is the uplink as with the aps configuration. The transponder on one side should be configured as TX and the peer as RX.
T/F xpdrConnConfigCpriRateControl	1.3.6.1.4.1.4515.1.8.1.1.1.11	TruthValue	read-write	This object is used to detrmine if the CPRI rate control should be active.
INT xpdrFaultPropagationDelay	1.3.6.1.4.1.4515.1.8.1.1.1.12	INTEGER	read-write	This object is used to determine the fault propagation delay. The value 0 mean no delay, the value 1 means 100ms delay, the value 2 means 200ms delay etc. 0 is the default value.
INT xpdrFecMode	1.3.6.1.4.1.4515.1.8.1.1.1.13	INTEGER	read-write	This object is used to determine the IEEE FEC mode for 10G and 16G services: 0 - No FEC (default) 1 - FEC Monitoring 2 - FEC Generation 3 - FEC Regeneration
oduXcConnConfigTable	1.3.6.1.4.1.4515.1.8.1.2		not-accessible	Description: 1. The port numbers are: 0 unassigned 1..10 ODUs of Uplink 1 11..20 ODUs of Uplink 2 (not available without 20G or 1+1 license) 2. All connections are unidirectional 3. P1 is the Source port and P2 is the Sync port 4. Port 0 is used as P2 when P1 is dropped 5. Port 0 is used as P1 when P2 is added 6. In the case of APS the two mate ODUs will apear with oduXcConnConfigProtected=TRUE 7. The allocation of ODUs per service port is described in xpdrConnAddMask above
oduXcConnConfigEntry	1.3.6.1.4.1.4515.1.8.1.2.1		not-accessible	An entry in the ODU connection table. An entry describes uni-directional connection of traffic from P1 (Source port) to port P2 (Sync port).
INT oduXcConnConfigP1	1.3.6.1.4.1.4515.1.8.1.2.1.1	INTEGER	read-create	The Source port.
INT oduXcConnConfigP2	1.3.6.1.4.1.4515.1.8.1.2.1.2	INTEGER	read-create	The Sync port.
T/F oduXcConnConfigProtected	1.3.6.1.4.1.4515.1.8.1.2.1.3	TruthValue	read-create	Indication for entry with Protection Mates
ROW oduXcConnConfigRowStatus	1.3.6.1.4.1.4515.1.8.1.2.1.4	RowStatus	read-create	The Status of this connection entry.
INT xpdrOduMappingStatus	1.3.6.1.4.1.4515.1.8.1.3	INTEGER	read-only	A bit mask that specifies how the ODUs are configured. The first nible describes Uplink 1 and the second nibble describes Uplink 2. Examples: If bit 1 equals 1 it means that the first ODU1 of Uplink 1 is devided into two ODU0. If bit 8 equals 1 it means that the forth ODU1 of Uplink 2 is devided into two ODU0. The default value is 0, means that all ODUs are ODU1.
INT xpdrOduMappingMaskedAdmin	1.3.6.1.4.1.4515.1.8.1.4	INTEGER	read-write	The first byte is the new mapping to set. The second byte is the mask for the setting. For example to split the second ODU1 of Uplink 1 into two ODU0 First byte should be - 01000000 Second byte should be - 01000000 To change the reunite the third ODU1 of uplink 2 First byte should be - 00000000 Second byte should be - 00000010
slXpdrLastChange	1.3.6.1.4.1.4515.1.8.6
slXpdrTraps	1.3.6.1.4.1.4515.1.8.7
slXpdrTraps0	1.3.6.1.4.1.4515.1.8.7.0
NTF xpdrConnConfigTableChange0	1.3.6.1.4.1.4515.1.8.7.0.1			A xpdrConnConfigTableChange trap is sent when the content of the xpdrConnConfigTable is changed. It is defined to support browsers that don't recognize RFC 2576.
NTF xpdrConnConfigTableChange	1.3.6.1.4.1.4515.1.8.7.1			A xpdrConnConfigTableChange trap is sent when the content of the xpdrConnConfigTable is changed.

RFC description

Smartoptics optical transponder MIB managing cross-connections and performance metrics for various optical service types.

Start monitoring Smartoptics SiteLight optical transponder/transport platform (ODU cross-connect/rate-control status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SL-XPDR-MIB

What Is SL-XPDR-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description