Juniper-SSC-CLIENT-MIB

All MIBs › Juniper-SSC-CLIENT-MIB

Organization: Juniper Networks, Inc.

Last Updated: 2003-12-18

Category: Domain: Subscriber Management, Vendor: Juniper

Description: MIB from Juniper Networks covering Service Selection Center (SSC) client configuration and subscriber portal interaction on E-series equipment.

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 Juniper-SSC-CLIENT-MIB?

Juniper-SSC-CLIENT-MIB is a Juniper Networks vendor-specific MIB for JUNOSe (E-series) routers that models the Service Selection Center (SSC) Client, the component that connects to an external SSC server to receive subscriber policy commands and web-portal/DHCP-LS/SSC session-selection instructions. It exposes configuration scalars (juniSscClientPrimaryAddress/Port, juniSscClientSecondaryAddress/Port, juniSscClientTertiaryAddress/Port, juniSscClientServerSwitchoverTimeout, juniSscClientTransportRouterName), status scalars (juniSscClientConnectionState, disconnected, trying, connected, plus juniSscClientActiveAddress/Port and juniSscClientVersion), and statistics counters (juniSscClientPolicyCommandsReceived, juniSscClientPolicyCommandsListReceived, juniSscClientBadPolicyCommandsReceived, juniSscClientErrorPolicyCommandsReceived). This data is useful for confirming the SSC client has an active connection to one of its configured servers and is successfully receiving well-formed policy commands, since a fallback to a secondary/tertiary server or a rise in bad-command counters signals a subscriber-management integration problem. It depends on Juniper-TC and Juniper-MIBs for shared textual conventions and enterprise registration, and it is deployed on Juniper E-series routers running JUNOSe subscriber-management features, where administrators can download the Juniper-SSC-CLIENT-MIB file to monitor SSC connectivity.

IPNetwork Monitor allows you to monitor SNMP objects defined in Juniper-SSC-CLIENT-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

Juniper Networks E-series routers running JUNOSe

Monitoring Examples

An operator polls juniSscClientConnectionState and juniSscClientActiveAddress to confirm the client is connected to its primary server rather than juniSscClientSecondaryAddress, then checks juniSscClientBadPolicyCommandsReceived; a connection state stuck at 'trying' combined with a growing bad-command counter would indicate the SSC server is unreachable or sending malformed policy updates, risking stale subscriber policy enforcement.

What Can Be Monitored

SSC server connection state (disconnected/trying/connected)
active server address and port in use
primary/secondary/tertiary server configuration
policy commands received and list/accounting subtypes
bad and error policy command counters

Imported Objects

From Juniper-MIBs

juniMibs

MODULE-IDENTITY

From Juniper-TC

JuniName

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using juniSscClientPolicyCommandsReceived OID:

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.

OIDs

OID symbolic	OID numeric	Type	Access	Description
juniSscClientMIB	1.3.6.1.4.1.4874.2.2.36			The Service Selection Center (SSC) Client MIB for the Juniper Networks enterprise.
juniSscClientObjects	1.3.6.1.4.1.4874.2.2.36.1
juniSscClientCfg	1.3.6.1.4.1.4874.2.2.36.1.1
juniSscClientCfgScalars	1.3.6.1.4.1.4874.2.2.36.1.1.1
I32 juniSscClientServerSwitchoverTimeout	1.3.6.1.4.1.4874.2.2.36.1.1.1.1	Integer32	read-write	The server switchover timeout in seconds. The SSC Client begins with the primary server and proceeds rotationally to secondary, tertiary, primary, etc. as timeouts occur.
IP juniSscClientPrimaryAddress	1.3.6.1.4.1.4874.2.2.36.1.1.1.2	IpAddress	read-write	The IP address of the primary SSC server. A value of 0.0.0.0 indicates the server address is unconfigured.
I32 juniSscClientPrimaryPort	1.3.6.1.4.1.4874.2.2.36.1.1.1.3	Integer32	read-write	The TCP port number for the primary SSC server. A value of zero indicates the port is unconfigured.
IP juniSscClientSecondaryAddress	1.3.6.1.4.1.4874.2.2.36.1.1.1.4	IpAddress	read-write	The IP address of the secondary SSC server. A value of 0.0.0.0 indicates the server address is unconfigured.
I32 juniSscClientSecondaryPort	1.3.6.1.4.1.4874.2.2.36.1.1.1.5	Integer32	read-write	The TCP port number of the secondary SSC server. A value of zero indicates the port is unconfigured.
IP juniSscClientTertiaryAddress	1.3.6.1.4.1.4874.2.2.36.1.1.1.6	IpAddress	read-write	The IP address of the tertiary SSC server. A value of 0.0.0.0 indicates the server address is unconfigured.
I32 juniSscClientTertiaryPort	1.3.6.1.4.1.4874.2.2.36.1.1.1.7	Integer32	read-write	The TCP port number of the tertiary SSC server. A value of zero indicates the port is unconfigured.
IP juniSscClientLocalAddress	1.3.6.1.4.1.4874.2.2.36.1.1.1.8	IpAddress	read-write	The local IP address binding of the server connection. A value of 0.0.0.0 indicates the local address is unconfigured.
JUN juniSscClientTransportRouterName	1.3.6.1.4.1.4874.2.2.36.1.1.1.9	JuniName	read-write	The name of the router to be used as the transport for the server connection.
juniSscClientStatus	1.3.6.1.4.1.4874.2.2.36.1.2
juniSscClientStatusScalars	1.3.6.1.4.1.4874.2.2.36.1.2.1
INT juniSscClientConnectionState	1.3.6.1.4.1.4874.2.2.36.1.2.1.1	INTEGER	read-only	The connection state of the SSC Client: disconnected Not connected to a SSC server. trying Attempting a connection to a server. connected Connected to a server. When this object has the value 'connected', the active server address and TCP port are reported in juniSscClientActiveAddress and juniSscClientActivePort, respectively.
IP juniSscClientActiveAddress	1.3.6.1.4.1.4874.2.2.36.1.2.1.2	IpAddress	read-only	The IP address of the SSC server currently in use. A value of 0.0.0.0 indicates no server is in use.
I32 juniSscClientActivePort	1.3.6.1.4.1.4874.2.2.36.1.2.1.3	Integer32	read-only	The TCP port number for the SSC server currently in use. A value of zero indicates no server is in use.
STR juniSscClientVersion	1.3.6.1.4.1.4874.2.2.36.1.2.1.4	DisplayString	read-only	The version number for the SSC server currently in use.
juniSscClientStatistics	1.3.6.1.4.1.4874.2.2.36.1.3
juniSscClientStatisticsScalars	1.3.6.1.4.1.4874.2.2.36.1.3.1
C32 juniSscClientPolicyCommandsReceivedEx	1.3.6.1.4.1.4874.2.2.36.1.3.1.1	Counter32	read-only	The number of policy command packets received from the SSC.
C32 juniSscClientPolicyCommandsListReceived	1.3.6.1.4.1.4874.2.2.36.1.3.1.2	Counter32	read-only	The number of policy command packets received from the SSC with subtype LIST.
C32 juniSscClientPolicyCommandsAcctReceived	1.3.6.1.4.1.4874.2.2.36.1.3.1.3	Counter32	read-only	The number of policy command packets received from the SSC with subtype ACCOUTING.
C32 juniSscClientBadPolicyCommandsReceived	1.3.6.1.4.1.4874.2.2.36.1.3.1.4	Counter32	read-only	The number of policy command packets received from the SSC that included rules that were in error.
C32 juniSscClientErrorPolicyCommandsReceived	1.3.6.1.4.1.4874.2.2.36.1.3.1.5	Counter32	read-only	The number of policy command packets received from the SSC indicating an error from the SSC.
C32 juniSscClientPolicyReportsSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.6	Counter32	read-only	The number of policy report packets sent to the SSC.
C32 juniSscClientConnectionOpenRequests	1.3.6.1.4.1.4874.2.2.36.1.3.1.7	Counter32	read-only	The number of connection open requests sent to the SSC.
C32 juniSscClientConnectionOpenCompletes	1.3.6.1.4.1.4874.2.2.36.1.3.1.8	Counter32	read-only	The number of connections to the SSC that open successfully.
C32 juniSscClientConnectionClosedSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.9	Counter32	read-only	The number of connection close indications that were sent to the SSC.
C32 juniSscClientConnectionClosedRemotely	1.3.6.1.4.1.4874.2.2.36.1.3.1.10	Counter32	read-only	The number of connection close indications that were received from the SSC.
C32 juniSscClientCreateInterfacesSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.11	Counter32	read-only	The number of interface creation indications that were sent to the SSC. This indicates the transition of an interface to an UP state.
C32 juniSscClientDeleteInterfacesSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.12	Counter32	read-only	The number of delete interface indications that were sent to the SSC. This indicates the transition of an interface to an DOWN state.
C32 juniSscClientActiveIpInterfaces	1.3.6.1.4.1.4874.2.2.36.1.3.1.13	Counter32	read-only	The number of currently active IP interfaces that the SSC Client is aware of.
C32 juniSscClientIpInterfaceTransitions	1.3.6.1.4.1.4874.2.2.36.1.3.1.14	Counter32	read-only	The number of IP interface transitions that have been tracked by the SSC Client.
C32 juniSscClientSynchronizesReceived	1.3.6.1.4.1.4874.2.2.36.1.3.1.15	Counter32	read-only	The number of synchronization requests received from the SSC.
C32 juniSscClientSynchronizeCompletesSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.16	Counter32	read-only	The number of synchronization complete packets sent to the SSC.
C32 juniSscClientInternalErrors	1.3.6.1.4.1.4874.2.2.36.1.3.1.17	Counter32	read-only	The number of internal errors tracked by the SSC Client.
C32 juniSscClientCommunicationErrors	1.3.6.1.4.1.4874.2.2.36.1.3.1.18	Counter32	read-only	The number of lower layer communication errors tracked by the SSC Client.
C32 juniSscClientTokensSeen	1.3.6.1.4.1.4874.2.2.36.1.3.1.19	Counter32	read-only	The number of tokens seen by the SSC client.
C32 juniSscClientActiveTokens	1.3.6.1.4.1.4874.2.2.36.1.3.1.20	Counter32	read-only	The number of tokens that the SSC client is currently aware of.
C32 juniSscClientTokenTransitions	1.3.6.1.4.1.4874.2.2.36.1.3.1.21	Counter32	read-only	The number of tokens transitions that have occurred.
C32 juniSscClientCreateTokensSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.22	Counter32	read-only	The number of token creation indications that were sent to the SSC. This indicates the transition of a token to an UP state.
C32 juniSscClientDeleteTokensSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.23	Counter32	read-only	The number of delete token indications that were sent to the SSC. This indicates the transition of a token to an DOWN state.
C32 juniSscClientActiveAddresses	1.3.6.1.4.1.4874.2.2.36.1.3.1.24	Counter32	read-only	The number of addresses that the SSC client is currently aware of.
C32 juniSscClientAddressTransitions	1.3.6.1.4.1.4874.2.2.36.1.3.1.25	Counter32	read-only	The number of address transitions that have occurred.
C32 juniSscClientCreateAddressesSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.26	Counter32	read-only	The number of address creation indications that were sent to the SSC. This indicates the transition of an address to an UP state.
C32 juniSscClientDeleteAddressesSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.27	Counter32	read-only	The number of delete address indications that were sent to the SSC. This indicates the transition of an address to an DOWN state.
C32 juniSscClientAuthenticationSuccesses	1.3.6.1.4.1.4874.2.2.36.1.3.1.28	Counter32	read-only	The number of tokens which were authenticated successfully.
C32 juniSscClientAuthenticationFailures	1.3.6.1.4.1.4874.2.2.36.1.3.1.29	Counter32	read-only	The number of tokens which were not authenticated successfully.
C32 juniSscClientDiscoversSeen	1.3.6.1.4.1.4874.2.2.36.1.3.1.30	Counter32	read-only	The number of discovers seen by the SSC client.
C32 juniSscClientActiveDiscovers	1.3.6.1.4.1.4874.2.2.36.1.3.1.31	Counter32	read-only	The number of discovers that the SSC client is currently aware of.
C32 juniSscClientDiscoverTransitions	1.3.6.1.4.1.4874.2.2.36.1.3.1.32	Counter32	read-only	The number of discover transitions that have occurred.
C32 juniSscClientCreateDiscoversSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.33	Counter32	read-only	The number of discover creation indications that were sent to the SSC.
C32 juniSscClientDeleteDiscoversSent	1.3.6.1.4.1.4874.2.2.36.1.3.1.34	Counter32	read-only	The number of delete discover indications that were sent to the SSC.
juniSscClientMIBConformance	1.3.6.1.4.1.4874.2.2.36.4
juniSscClientMIBCompliances	1.3.6.1.4.1.4874.2.2.36.4.1
juniSscClientAuthCompliance	1.3.6.1.4.1.4874.2.2.36.4.1.1			Obsolete compliance statement for authentication clients implementing the Juniper SSC Client MIB authentication functionality. This statement became obsolete when DHCP-LS, Web and SSC support objects were added.
juniSscClientAuthCompliance2	1.3.6.1.4.1.4874.2.2.36.4.1.2			Obsolete compliance statement for authentication clients implementing the Juniper SSC Client MIB authentication functionality. This statement became obsolete when the version number, local address and transport router name objects were added.
juniSscClientAuthCompliance3	1.3.6.1.4.1.4874.2.2.36.4.1.3			Obsolete compliance statement for clients implementing the Juniper SSC Client MIB functionality. This statement became obsolete when token scalar statistics were obsoleted and discover scalar statistics were added.
juniSscClientAuthCompliance4	1.3.6.1.4.1.4874.2.2.36.4.1.4			The compliance statement for clients implementing the Juniper SSC Client MIB functionality.
juniSscClientMIBGroups	1.3.6.1.4.1.4874.2.2.36.4.2
juniSscClientGroup	1.3.6.1.4.1.4874.2.2.36.4.2.1			Obsolete collection of objects providing management of SSC Clients. This group became obsolete when DHCP-LS, Web and SSC support objects were added.
juniSscClientGroup2	1.3.6.1.4.1.4874.2.2.36.4.2.2			Obsolete collection of objects providing management of SSC Clients. This group became obsolete when version number, local address and transport router name objects were added.
juniSscClientGroup3	1.3.6.1.4.1.4874.2.2.36.4.2.3			Obsolete collection of objects providing management of SSC Clients. This group became obsolete when token scalar statistics were obsoleted and discover scalar statistics were added.
juniSscClientGroup4	1.3.6.1.4.1.4874.2.2.36.4.2.4			The basic collection of objects providing management of SSC Clients.

RFC description

Juniper Networks MIB for Service Selection Center (SSC) client configuration and subscriber portal interaction on Juniper E-series.

Start monitoring Juniper Networks E-series router running JUNOSe (Service Selection Center client) 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 Juniper-SSC-CLIENT-MIB