TIMETRA-SAS-BGP-MIB

All MIBs › TIMETRA-SAS-BGP-MIB

Organization: Alcatel-Lucent

Last Updated: 2011-02-01

Description: TIMETRA-SAS-BGP-MIB module

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 TIMETRA-SAS-BGP-MIB?

TIMETRA-SAS-BGP-MIB is an Alcatel-Lucent (SAS = Service Aggregation Switch, 7210/7250 series) proprietary MIB extending the standard BGP4-MIB with a service-routes option. Its peer-parameters extension table, keyed by peer, records a use-service-routes flag, and a path-attribute extension table records the equivalent use-service-routes option at the path-attribute level. As a configuration MIB it lets an administrator confirm whether a BGP peer is configured to use service routes (routes bound to a specific service context) on an Alcatel-Lucent SAS platform. It is deployed on Alcatel-Lucent SAS (Service Aggregation Switch) platforms. Engineers can download the TIMETRA-SAS-BGP-MIB file directly to load it into their MIB browser.

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

Alcatel-Lucent SAS (Service Aggregation Switch) platforms

Monitoring Examples

An administrator checks tBgpPeerNgUseSvcRoutes to confirm a BGP peer is configured to use service routes on an Alcatel-Lucent SAS platform.

What Can Be Monitored

BGP peer service-routes configuration

Imported Objects

From BGP4-MIB

bgp4PathAttrEntry

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Gauge32
Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TestAndIncr
TimeStamp
TruthValue

From TIMETRA-BGP-MIB

tBgpPeerNgParamsEntry

OBJECT-TYPE

From TIMETRA-SAS-GLOBAL-MIB

timetraSASConfs	OBJECT-IDENTITY
timetraSASModules	OBJECT-IDENTITY
timetraSASNotifyPrefix	OBJECT-IDENTITY
timetraSASObjs	OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
timetraSASBgpMIBModule	1.3.6.1.4.1.6527.6.2.1.1.15			This document is the SNMP MIB module for Alcatel-Lucent's implementation of BGP. Copyright 2003-2014 Alcatel-Lucent. All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies Alcatel-Lucent's proprietary intellectual property. Alcatel-Lucent retains all title and ownership in the Specification, including any revisions. Alcatel-Lucent grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel-Lucent products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel-Lucent makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification. There is one BGP instance per virtual router. Each BGP instance can have a number of peer groups. The MIB objects here are organized in to four groups: - global objects (nothing there for now) - per-instance objects - per-peer-group objects - per-peer objects The value of most BGP configuration objects can be defaulted at three levels: at the per-peer level, at the peer group level, and at the BGP instance level. The per-peer object values are set: - first by the peer object value, if set; - second, if not set then by the peer-group object value, if that is set; - third, if not set, by the instance object value.
tmnxSASBgpConformance	1.3.6.1.4.1.6527.6.2.2.1.14
tmnxSASBgpGroups	1.3.6.1.4.1.6527.6.2.2.1.14.1
tmnxSASBgpGlobalV7v0Group	1.3.6.1.4.1.6527.6.2.2.1.14.1.1			The group of objects supporting management of extended BGP on Alcatel-Lucent 7210 series systems release 7.0.
tmnxSASBgpObjects	1.3.6.1.4.1.6527.6.2.2.2.18
tBgpSASPeerObjects	1.3.6.1.4.1.6527.6.2.2.2.18.1
tBgpPeerNgParamsExtnTable	1.3.6.1.4.1.6527.6.2.2.2.18.1.10		not-accessible	tBgpPeerNgParamsExtnTable provides information about the attributes configured for the BGP instance.
tBgpPeerNgParamsExtnEntry	1.3.6.1.4.1.6527.6.2.2.2.18.1.10.1		not-accessible	An entry in the tBgpPeerNgParamsExtnTable. Each entry maintains the attributes configured for BGP instance that are supported in addition to objects in tBgpPeerNgParamsTable.
T/F tBgpPeerNgUseSvcRoutes	1.3.6.1.4.1.6527.6.2.2.2.18.1.10.1.1	TruthValue	read-create	The value of tBgpPeerNgUseSvcRoutes specifies whether to use service routers for this neighbor
bgp4PathAttrExtnTable	1.3.6.1.4.1.6527.6.2.2.2.18.1.11		not-accessible	The BGP-4 Received Path Attribute Table contains information about paths to destination networks received from all BGP4 peers in addition to bgp4PathAttrTable.
bgp4PathAttrExtnEntry	1.3.6.1.4.1.6527.6.2.2.2.18.1.11.1		not-accessible	Information about a path to a network.
T/F bgp4PathUseSvcRoutesOpt	1.3.6.1.4.1.6527.6.2.2.2.18.1.11.1.1	TruthValue	read-only	The value of bgp4PathUseSvcRoutesOpt specifies whether 3107 optimisation has been done or not.

RFC description

BGP routing configuration and management for Alcatel-Lucent Service Aggregation System routers.

Start monitoring Alcatel-Lucent SAS (Service Aggregation Switch) platforms (BGP service-routes peer config 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 TIMETRA-SAS-BGP-MIB

What Is TIMETRA-SAS-BGP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description