TIMETRA-SAS-BGP-MIB: View SNMP OID List / Download MIB

VENDOR: NOKIA

Home	MIB: TIMETRA-SAS-BGP-MIB
Download as:		SNMPv2-CONF, TIMETRA-BGP-MIB, SNMPv2-SMI, TIMETRA-SAS-GLOBAL-MIB, BGP4-MIB, SNMPv2-TC		Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash). Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded. The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.

Object Name	OID	Type	Access	Info
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		no-access	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		no-access	An entry in the tBgpPeerNgParamsExtnTable. Each entry maintains the attributes configured for BGP instance that are supported in addition to objects in tBgpPeerNgParamsTable.
tBgpPeerNgUseSvcRoutes	1.3.6.1.4.1.6527.6.2.2.2.18.1.10.1.1	truthvalue	read-only	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		no-access	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		no-access	Information about a path to a network.
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.