STN-BGP-MIB

All MIBs › STN-BGP-MIB

Organization: Spring Tide Networks

Last Updated: 2000-04-06

Category: Routing, Spring Tide Networks

Description: Manages Spring Tide Networks BGP routing peer configuration, session state, and prefix counts.

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 STN-BGP-MIB?

STN-BGP-MIB is a Spring Tide Networks private enterprise MIB describing managed objects for BGP-4 routing on Spring Tide's platforms (a company later acquired by Lucent), extending or paralleling the standard BGP4-MIB with vendor-specific peer configuration, session state, and prefix-count reporting. Although no sample objects were captured for this module, based on its description it would expose per-peer BGP session state (idle/connect/established), configured peer attributes, and counts of received/advertised route prefixes — data essential for monitoring the software health of the BGP routing process. This kind of MIB is used to detect BGP session flaps, unexpectedly low or high prefix counts (indicating route leaks or filtering problems), and peer misconfiguration, all reflecting the operational health of the router's control-plane software rather than physical hardware. It has a clear conceptual dependency on the standard BGP4-MIB (RFC 4273/1657) that it extends or mirrors for vendor-specific detail. It would have been deployed on Spring Tide Networks service routers used in carrier/ISP core and edge BGP routing roles. Network engineers evaluating or troubleshooting this functionality can download the STN-BGP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in STN-BGP-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

Spring Tide Networks service routers/switches

Monitoring Examples

No sample objects were provided for this module, so a concrete polling scenario cannot be grounded in specific object names; based on its documented purpose, an admin would typically poll a per-peer table for BGP session state and prefix counts, alerting on transitions out of the Established state as a sign of peering instability. Sudden drops or spikes in advertised/received prefix counts would similarly flag route-leak or filter misconfiguration issues on Spring Tide BGP routers.

What Can Be Monitored

BGP peer session state
BGP peer configuration
received/advertised prefix counts

Imported Objects

From BGP4-MIB

bgp4PathAttrEntry

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SPRING-TIDE-NETWORKS-SMI

stnNotification

OBJECT-IDENTITY

From STN-IPROUTING-MIB

stnIpRouting

MODULE-IDENTITY

How to Use in IPNetwork Monitor

Example using stnBgpPrefixCount OID:

Select a Spring Tide Networks (Lucent) service router (BGP-4 peer/session status) 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 stnBgpPrefixCount into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of distinct prefixes in the local RIB. 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
stnBgp	1.3.6.1.4.1.3551.2.12.5			This MIB module describes managed objects of Spring Tide Networks BGP-4.
stnBgpObjects	1.3.6.1.4.1.3551.2.12.5.1
stnBgpRouteAttrTable	1.3.6.1.4.1.3551.2.12.5.1.1		not-accessible	A table of BGP route attribute sets.
stnBgpRouteAttrEntry	1.3.6.1.4.1.3551.2.12.5.1.1.1		not-accessible	Information about a particular set of BGP attributes.
I32 stnBgpRouteAttrId	1.3.6.1.4.1.3551.2.12.5.1.1.1.1	Integer32	read-only	A unique integer identifing this row in the table.
OCT stnBgpRouteAttrASPathSegment	1.3.6.1.4.1.3551.2.12.5.1.1.1.2	OCTET STRING	read-only	The sequence of AS path segments. Each AS path segment is represented by a triple . The type is a 1-octet field which has two possible values: 1 AS_SET: unordered set of ASs a route in the UPDATE message has traversed 2 AS_SEQUENCE: ordered set of ASs a route in the UPDATE message has traversed. The length is a 1-octet field containing the number of ASs in the value field. The value field contains one or more AS numbers, each AS is represented in the octet string as a pair of octets according to the following algorithm: first-byte-of-pair = ASNumber / 256; second-byte-of-pair = ASNumber & 255;
INT stnBgpRouteAttrRefCount	1.3.6.1.4.1.3551.2.12.5.1.1.1.3	INTEGER	read-only	A number of BGP routes using this attibute set.
INT stnBgpRouteAttrLocPref	1.3.6.1.4.1.3551.2.12.5.1.1.1.4	INTEGER	read-only	The originating BGP4 speaker's degree of preference for an advertised route. A value of -1 indicates the absence of this attribute.
INT stnBgpRouteAttrMultiExitDisc	1.3.6.1.4.1.3551.2.12.5.1.1.1.5	INTEGER	read-only	This metric is used to discriminate between multiple exit points to an adjacent autonomous system. A value of -1 indicates the absence of this attribute.
INT stnBgpRouteAttrOrigin	1.3.6.1.4.1.3551.2.12.5.1.1.1.6	INTEGER	read-only	The ultimate origin of the path information.
IP stnBgpRouteAttrNextHop	1.3.6.1.4.1.3551.2.12.5.1.1.1.7	IpAddress	read-only	The address of the border router that should be used for the destination network.
INT stnBgpRouteAttrAtomicAggregate	1.3.6.1.4.1.3551.2.12.5.1.1.1.8	INTEGER	read-only	Whether or not the local system has selected a less specific route without selecting a more specific route.
INT stnBgpRouteAttrAggregatorAS	1.3.6.1.4.1.3551.2.12.5.1.1.1.9	INTEGER	read-only	The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute.
IP stnBgpRouteAttrAggregatorAddr	1.3.6.1.4.1.3551.2.12.5.1.1.1.10	IpAddress	read-only	The IP address of the last BGP4 speaker that performed route aggregation. A value of 0.0.0.0 indicates the absence of this attribute.
C32 stnBgpPrefixCountEx	1.3.6.1.4.1.3551.2.12.5.1.2	Counter32	read-only	Number of distinct prefixes in the local RIB.
C32 stnBgpPathCount	1.3.6.1.4.1.3551.2.12.5.1.3	Counter32	read-only	Number of paths in the local RIB.
C32 stnBgpSelectedPathCount	1.3.6.1.4.1.3551.2.12.5.1.4	Counter32	read-only	Number of paths selected for route table installation.
C32 stnBgpPathAttributeCount	1.3.6.1.4.1.3551.2.12.5.1.5	Counter32	read-only	Number of entries in the path attribute database.
C32 stnBgpPathAttributeTlvLength	1.3.6.1.4.1.3551.2.12.5.1.6	Counter32	read-only	Total length of all TLVs in the path attribute database.
stnBgp4PathAttrTable	1.3.6.1.4.1.3551.2.12.5.1.7		not-accessible	A table of BGP path attributes.
stnBgp4PathAttrEntry	1.3.6.1.4.1.3551.2.12.5.1.7.1		not-accessible	Additional information about a bgp path to a network.
OCT stnBgp4PathAttrCommunities	1.3.6.1.4.1.3551.2.12.5.1.7.1.1	OCTET STRING	read-only	The sequence of community numbers. Each AS community number is a 4-octet long unsigned integer
I32 stnBgp4PathAttrWeight	1.3.6.1.4.1.3551.2.12.5.1.7.1.2	Integer32	read-only	The weight of this path.
INT stnBgp4PathAttrImported	1.3.6.1.4.1.3551.2.12.5.1.7.1.3	INTEGER	read-only	Variable indicates whether this path has been imported from the other portocol on this router.

RFC description

Spring Tide Networks BGP-4 route attribute management and routing policy administration.

Start monitoring Spring Tide Networks (Lucent) service router (BGP-4 peer/session 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 STN-BGP-MIB