Juniper-SSC-CLIENT-MIB :: juniSscClientPolicyCommandsReceived

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Juniper-SSC-CLIENT-MIB › juniSscClientPolicyCommandsReceived

juniSscClientPolicyCommandsReceived

Module: Juniper-SSC-CLIENT-MIB

OID (symbolic): Juniper-SSC-CLIENT-MIB::juniSscClientPolicyCommandsReceived

OID (numeric): 1.3.6.1.4.1.4874.2.2.36.1.3.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of policy command packets received from the SSC.

What is juniSscClientPolicyCommandsReceived?

A running count of policy command packets received from the SSC server, the basic activity counter for the subscriber-policy control channel.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.36.1.3.1.1
snmpwalk -v2c -c public <target> Juniper-SSC-CLIENT-MIB::juniSscClientPolicyCommandsReceived

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.36.1.3.1.1.1
snmpget -v2c -c public <target> Juniper-SSC-CLIENT-MIB::juniSscClientPolicyCommandsReceived.1

Start monitoring Juniper Networks E-series router running JUNOSe (Service Selection Center client) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Juniper-SSC-CLIENT-MIB::juniSscClientPolicyCommandsReceived OID value, configure state conditions and alerts, and monitor any Juniper Networks E-series router running JUNOSe (Service Selection Center client) from a single console.

How to Use in IPNetwork Monitor

Select a Juniper Networks E-series router running JUNOSe (Service Selection Center client) 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 juniSscClientPolicyCommandsReceived into the Find box to locate it in the OID tree, then select it and click OK. The number of policy command packets received from the SSC. 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 a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (10 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.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.36juniSscClientMIBJuniper-MIBs
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.36.1juniSscClientObjectsJuniper-SSC-CLIENT-MIB
1.3.6.1.4.1.4874.2.2.36.1.3juniSscClientStatisticsJuniper-SSC-CLIENT-MIB
1.3.6.1.4.1.4874.2.2.36.1.3.1juniSscClientStatisticsScalarsJuniper-SSC-CLIENT-MIB
1.3.6.1.4.1.4874.2.2.36.1.3.1.1juniSscClientPolicyCommandsReceivedJuniper-SSC-CLIENT-MIB