TIMETRA-SAS-BGP-MIB
AI MIB Summary
The TIMETRA-SAS-BGP-MIB provides SNMP management for Alcatel-Lucent SR OS (formerly TiMOS) platforms to monitor and configure BGP instances, peer groups, and individual BGP peers within virtual routers. It exposes hierarchical configuration objects and operational states for BGP sessions, supporting a three-level inheritance model where peer settings default to peer-group or instance values if not explicitly defined.
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.
Main OID:
timetraSASBgpMIBModule.1.3.6.1.4.1.6527.6.2.1.1.15
11
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
11 total| Object Name |
|---|
timetraSASBgpMIBModuleThis 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. MODULE-IDENTITY .1.3.6.1.4.1.6527.6.2.1.1.15 |
tmnxSASBgpConformance OBJECT IDENTIFIER .1.3.6.1.4.1.6527.6.2.2.1.14 |
tmnxSASBgpGroups OBJECT IDENTIFIER .1.3.6.1.4.1.6527.6.2.2.1.14.1 |
tmnxSASBgpObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6527.6.2.2.2.18 |
tBgpSASPeerObjects OBJECT IDENTIFIER .1.3.6.1.4.1.6527.6.2.2.2.18.1 |
tBgpPeerNgParamsExtnTabletBgpPeerNgParamsExtnTable provides information about the
attributes configured for the BGP instance. SEQUENCE OF TBgpPeerNgParamsExtnEntry .1.3.6.1.4.1.6527.6.2.2.2.18.1.10 |
tBgpPeerNgParamsExtnEntryAn entry in the tBgpPeerNgParamsExtnTable. Each entry
maintains the attributes configured for BGP instance that
are supported in addition to objects in tBgpPeerNgParamsTable. TBgpPeerNgParamsExtnEntry .1.3.6.1.4.1.6527.6.2.2.2.18.1.10.1 |
tBgpPeerNgUseSvcRoutesThe value of tBgpPeerNgUseSvcRoutes specifies whether to use
service routers for this neighborrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6527.6.2.2.2.18.1.10.1.1 |
bgp4PathAttrExtnTableThe BGP-4 Received Path Attribute Table
contains information about paths to
destination networks received from all
BGP4 peers in addition to bgp4PathAttrTable. SEQUENCE OF Bgp4PathAttrExtnEntry .1.3.6.1.4.1.6527.6.2.2.2.18.1.11 |
bgp4PathAttrExtnEntryInformation about a path to a network. Bgp4PathAttrExtnEntry .1.3.6.1.4.1.6527.6.2.2.2.18.1.11.1 |
bgp4PathUseSvcRoutesOptThe value of bgp4PathUseSvcRoutesOpt specifies whether 3107 optimisation has been done or not.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.6527.6.2.2.2.18.1.11.1.1 |