TROPIC-OSPF-MIB: View SNMP OID List / Download MIB

VENDOR: NOKIA


 Home MIB: TROPIC-OSPF-MIB
Download as:   
SNMPv2-CONF, IF-MIB, TROPIC-GLOBAL-REG, OSPF-MIB, SNMPv2-SMI, 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
     tnOspfMibModule 1.3.6.1.4.1.7483.1.1.2.4.3
The Nokia DWDM OSPF MIB.
 tnOspfConf 1.3.6.1.4.1.7483.2.5.1.1
     tnOspfGroups 1.3.6.1.4.1.7483.2.5.1.1.1
         tnOspfAreaGroup 1.3.6.1.4.1.7483.2.5.1.1.1.2
         tnOspfPortGroup 1.3.6.1.4.1.7483.2.5.1.1.1.21
         tnOspfMultiAreaConfigGroup 1.3.6.1.4.1.7483.2.5.1.1.1.22
     tnOspfCompliances 1.3.6.1.4.1.7483.2.5.1.1.2
         tnOspfCompliance 1.3.6.1.4.1.7483.2.5.1.1.2.1
 tnOspfObjs 1.3.6.1.4.1.7483.2.5.1.2
     tnOspfAreaTable 1.3.6.1.4.1.7483.2.5.1.2.2 no-access
         tnOspfAreaEntry 1.3.6.1.4.1.7483.2.5.1.2.2.1 no-access
             tnOspfAreaTopologyId 1.3.6.1.4.1.7483.2.5.1.2.2.1.1 tntopologyid no-access
             tnOspfAreaId 1.3.6.1.4.1.7483.2.5.1.2.2.1.2 areaid no-access
     tnOspfPortTable 1.3.6.1.4.1.7483.2.5.1.2.21 no-access
           tnOspfPortEntry 1.3.6.1.4.1.7483.2.5.1.2.21.1 no-access
               tnOspfPortTopologyId 1.3.6.1.4.1.7483.2.5.1.2.21.1.1 tntopologyid read-only
     tnOspfMultiAreaConfigTable 1.3.6.1.4.1.7483.2.5.1.2.22 no-access
           tnOspfMultiAreaConfigEntry 1.3.6.1.4.1.7483.2.5.1.2.22.1 no-access
               tnOspfMultiAreaId 1.3.6.1.4.1.7483.2.5.1.2.22.1.1 areaid read-only
               tnOspfMultiAreaConfigType 1.3.6.1.4.1.7483.2.5.1.2.22.1.2 integer read-only
Specifies an OSPF area type: normal areas are defined as areas that can accept intra-area, inter-area and external routes. stub areas do not accept routes belonging to external autonomous systems (AS); however, these areas have inter-area and intra-area routes. This reduces the size of the routing databases for the area's internal routers. Routers in the stub area also contain a default route which is advertised to the area by the Area Border Router (ABR). totallyStub areas do not allow routes other than intra-area and the default route to be propagated within the area. This further reduces the size of the routing databases for the area's internal routers. The ABR advertises a default route into the area and all the routers belonging to this area use the default route to send any traffic outside the area. nssa (Not So Stub Areas) can import AS external routes from within the area and send them to other areas, but cannot receive AS external routes from other areas. Inter-area and intra-area routes are allowed along with a default route which is advertised to the area by the ABR. nssaTotallyStub areas are similar to nssa with the added restriction that inter-area routes are not allowed. Enumeration: 'stub': 2, 'totallyStub': 3, 'normal': 1, 'nssa': 4, 'nssaTotallyStub': 5.
               tnOspfMultiAreaConfigDnsOpaqueLsa 1.3.6.1.4.1.7483.2.5.1.2.22.1.3 integer read-only
Opaque LSA status for the DNS application. Determines whether opaque LSAs for the DNS application shall be distributed into this OSPF area, and received from this area. yes - DNS opaque LSAs are distributed to the area, and received from the area. no - DNS opaque LSAs are not distributed to the area, and not received from the area. Enumeration: 'yes': 1, 'no': 2.
               tnOspfMultiAreaConfigWavekeyOpaqueLsa 1.3.6.1.4.1.7483.2.5.1.2.22.1.4 integer read-only
Opaque LSA status for the Wave key application. Determines, whether opaque LSAs for the Wave key application shall be distributed into this OSPF area, and received from this area. Wave Key opaque LSAs can only be enabled in one OSPF Area. yes - Wave key opaque LSAs are distributed to the area, and received from the area no - Wave key opaque LSAs are not distributed to the area, and not received from the area. Enumeration: 'yes': 1, 'no': 2.
               tnOspfMultiAreaConfigNssaTranslate 1.3.6.1.4.1.7483.2.5.1.2.22.1.5 integer read-only
Applicable only if area type is nssa or nssaTotallyStub. Determines behavior of NSSA ABR router translation of internal area type 7 LSAs to type 5 LSAs which get propagated into other areas. candidate ospf elects one of candidate routers to be a translator for this area. always router will be always used as translator for this area. never router will never be used as translator for this area. notApplicable is when the type is not nssa or nssaTotallyStub. Enumeration: 'always': 2, 'never': 3, 'candidate': 1, 'notApplicable': 4.
               tnOspfMultiAreaConfigDefaultCost 1.3.6.1.4.1.7483.2.5.1.2.22.1.6 integer32 read-only
Specifies the cost in the range -1 to 16777215 for the default route originated by stub, totallyStub, nssa or nssaTotallyStub area ABR. -1 indicates that the default cost is not applicable. Current configurable range: 0 to 16777215. Note: If the cost is set to the maximum value of 16777215 this prevents the ABR from distributing a default route within the Stub or NSSA area.
               tnOspfMultiAreaConfigVirtualLinkIp 1.3.6.1.4.1.7483.2.5.1.2.22.1.7 ipaddress read-only
Applicable only for normal Areas. Allows for the creation of a virtual link for this area. OSPF requires that all areas attach directly to Area 0.0.0.0 but not that the attachment be physical. One can take any physical arrangement of areas and attach them logically through OSPF virtual links. Specifies the Loopback interface IP Address of the NE to terminate the virtual link. This NE should have an interface that is connected to Area 0.0.0.0 and a non 0.0.0.0 Area. Note: A virtual link must be configured on both NEs. Virtual links cannot be established through Area 0.0.0.0, stub, totallyStub, nssa or nssaTotallyStub type areas. The IP address of 0.0.0.0 means no virtual link.
               tnOspfMultiAreaConfigRowStatus 1.3.6.1.4.1.7483.2.5.1.2.22.1.8 rowstatus read-only
Status of this OSPF area. supported values: 1 - active 4 - createAndGo 6 - destroy. To create an OSPF area, set the value to 4. To delete an OSPF area, set the value to 6. After an OSPF area is created, upon a retrieve of this attribute, 1 is returned. That is, the active state is not set but it is transitioned after the OSPF area has been created.