SONUS-ISUP-SERVICE-GROUP-MIB :: sonusIsupMaintReason

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SONUS-ISUP-SERVICE-GROUP-MIB › sonusIsupMaintReason

sonusIsupMaintReason

Module: SONUS-ISUP-SERVICE-GROUP-MIB

OID (symbolic): SONUS-ISUP-SERVICE-GROUP-MIB::sonusIsupMaintReason

OID (numeric): 1.3.6.1.4.1.2879.2.6.1.2.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Maintenance reason for blocking/unblocking of the circuit.

What is sonusIsupMaintReason?

The specific reason code, e.g. trunkGroupMode(3), remoteHardware(10), ss7GwResynchronization(12), carried in circuit block/unblock traps, explaining why a circuit's maintenance state changed. Admins use this to distinguish, e.g., a deliberate local operator action from an automatic reaction to remote hardware failure, without cross-referencing other data.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2879.2.6.1.2.1.2
snmpwalk -v2c -c public <target> SONUS-ISUP-SERVICE-GROUP-MIB::sonusIsupMaintReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2879.2.6.1.2.1.2.1
snmpget -v2c -c public <target> SONUS-ISUP-SERVICE-GROUP-MIB::sonusIsupMaintReason.1

Start monitoring Sonus Networks softswitch, SS7 signaling gateway (ISUP point-code/routing configuration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SONUS-ISUP-SERVICE-GROUP-MIB::sonusIsupMaintReason OID value, configure state conditions and alerts, and monitor any Sonus Networks softswitch, SS7 signaling gateway (ISUP point-code/routing configuration) from a single console.

How to Use in IPNetwork Monitor

Select a Sonus Networks softswitch, SS7 signaling gateway (ISUP point-code/routing configuration) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type sonusIsupMaintReason into the Find box to locate it in the OID tree, then select it and click OK. It reports the maintenance reason for blocking/unblocking of the circuit. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value changes between polls, since this object only carries a meaningful reason code while the circuit is in a blocked state. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2879sonusSONUS-SMI
1.3.6.1.4.1.2879.2sonusMgmtSONUS-SMI
1.3.6.1.4.1.2879.2.6sonusSignallingMIBsSONUS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.2879.2.6.1sonusIsupServiceGroupMIBSONUS-ISUP-SERVICE-GROUP-MIB
1.3.6.1.4.1.2879.2.6.1.2sonusIsupServiceGroupMIBNotificationsSONUS-ISUP-SERVICE-GROUP-MIB
1.3.6.1.4.1.2879.2.6.1.2.1sonusIsupServiceGroupMIBNotificationsObjectsSONUS-ISUP-SERVICE-GROUP-MIB
1.3.6.1.4.1.2879.2.6.1.2.1.2sonusIsupMaintReasonSONUS-ISUP-SERVICE-GROUP-MIB