PAIRGAIN-IISP-MIB: View SNMP OID List / Download MIB

VENDOR: PAIRGAIN TECHNOLOGIES


 Home MIB: PAIRGAIN-IISP-MIB
Download as:   

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
 pgIISP 1.3.6.1.4.1.927.1.9.13.1
Initial version of the MIB for monitoring and controlling IISP routing.
     pgIISPMIBObjects 1.3.6.1.4.1.927.1.9.13.1.1
         pgIISPRouteAddrIndexNext 1.3.6.1.4.1.927.1.9.13.1.1.1 integer read-only
This object contains an appropriate value to be used for pgIISPRouteAddrIndex when creating entries in the pgIISPRouteAddrTable. The value 0 indicates that no unassigned entries are available. To obtain the atmVcCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
         pgIISPRouteAddrTable 1.3.6.1.4.1.927.1.9.13.1.1.2 no-access
A table containing all the attributes necessary to determine what the entity believes is reachable in terms of ATM End System Addresses and to determine which nodes are advertising this reachability. This table is also used to configure static routes to reachable address prefixes. The local node index that received the reachability information, reachable address, address prefix length, and an index that distinguishes between multiple listings of connectivity to a given address prefix from a given local node are combined to form an instance ID for this object..
             pgIISPRouteAddrEntry 1.3.6.1.4.1.927.1.9.13.1.1.2.1 no-access
An entry in the table, containing information about a reachable address prefix.
                 pgIISPRouteAddrIndex 1.3.6.1.4.1.927.1.9.13.1.1.2.1.1 integer32 read-only
An index into the set of listings of connectivity to a given route.
                 pgIISPRouteAddrRowStatus 1.3.6.1.4.1.927.1.9.13.1.1.2.1.2 rowstatus read-only
To create, delete, activate and de-activate a reachable address prefix.
                 pgIISPRouteAddrAddress 1.3.6.1.4.1.927.1.9.13.1.1.2.1.3 pgatmaddrprefix read-only
The value of the ATM End System Address prefix.
                 pgIISPRouteAddrPrefixLength 1.3.6.1.4.1.927.1.9.13.1.1.2.1.4 pgatmprefixlength read-only
The prefix length to be applied to the ATM End System Address prefix.
                 pgIISPRouteAddrIfIndex 1.3.6.1.4.1.927.1.9.13.1.1.2.1.5 interfaceindex read-write
The local interface over which the reachable address can be reached. The value zero indicates an unknown interface or reachability through a remote node.
                 pgIISPRouteAddrType 1.3.6.1.4.1.927.1.9.13.1.1.2.1.6 integer read-write
The type (e.g. internal or exterior) of reachability from the advertising node to the address prefix. Reject(2) refers to an address prefix which, if matched, indicates that the message should be discarded as unreachable. This is used in some protocols as a means of correctly aggregating routes. Enumeration: 'other': 1, 'internal': 3, 'exterior': 4, 'reject': 2.
                 pgIISPRouteAddrAdminStatus 1.3.6.1.4.1.927.1.9.13.1.1.2.1.7 integer read-write
Indicates whether the route is configured to be used. Enumeration: 'active': 2, 'inactive': 1.
                 pgIISPRouteAddrOperStatus 1.3.6.1.4.1.927.1.9.13.1.1.2.1.8 integer read-write
Indicates whether the reachable address prefix is operationally valid and whether it is being advertised by this node. Enumeration: 'active': 2, 'inactive': 1, 'advertised': 3.
                 pgIISPRouteAddrTimeStamp 1.3.6.1.4.1.927.1.9.13.1.1.2.1.9 timestamp read-write
Indicates when the connectivity from the advertising node to the reachable address prefix became known to the local node.
         pgIISPNetPrefixIndexNext 1.3.6.1.4.1.927.1.9.13.1.1.3 integer read-only
This object contains an appropriate value to be used for pgIISPRouteAddrIndex when creating entries in the pgIISPRouteAddrTable. The value 0 indicates that no unassigned entries are available. To obtain the atmVcCrossConnectIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.
         pgIISPNetPrefixTable 1.3.6.1.4.1.927.1.9.13.1.1.4 no-access
A table implemented by the user-side, containing the network-prefix(es) for ATM-layer addresses in effect on the user side of the UNI.
             pgIISPNetPrefixEntry 1.3.6.1.4.1.927.1.9.13.1.1.4.1 no-access
Information about a single network-prefix for ATM-layer addresses in effect on the user-side. Note that the index variable atmNetPrefixPrefix is a variable-length string, and as such the rule for variable-length strings in section 4.1.6 of RFC 1212 applies.
                 pgIISPNetPrefixIndex 1.3.6.1.4.1.927.1.9.13.1.1.4.1.1 integer32 read-only
An index into the set of listings of connectivity to a given address prefix.
                 pgIISPNetPrefixRowStatus 1.3.6.1.4.1.927.1.9.13.1.1.4.1.2 rowstatus read-only
To create, delete, activate and de-activate a net prefix entry.
                 pgIISPNetPrefixPort 1.3.6.1.4.1.927.1.9.13.1.1.4.1.3 integer read-only
A unique value which identifies the UNI port for which the network prefix for ATM addresses is in effect. The value of 0 has the special meaning of identifying the local UNI.
                 pgIISPNetPrefixPrefix 1.3.6.1.4.1.927.1.9.13.1.1.4.1.4 netprefix read-only
The network prefix for ATM addresses which is in effect on the user side of the ATM UNI port.
                 pgIISPNetPrefixFormat 1.3.6.1.4.1.927.1.9.13.1.1.4.1.5 integer read-write
ATM address format. Enumeration: 'e164': 3, 'dcc': 1, 'icd': 2.
                 pgIISPNetPrefixLength 1.3.6.1.4.1.927.1.9.13.1.1.4.1.6 integer32 read-write
The number of bits that are significant in an ATM address prefix used.
                 pgIISPNetPrefixStatus 1.3.6.1.4.1.927.1.9.13.1.1.4.1.7 integer read-write
An indication of the validity of the network prefix for ATM addresses on the user side of the UNI port. To configure a new network prefix in this table, the network-side must set the appropriate instance of this object to the value valid(1). To delete an existing network prefix in this table, the network-side must set the appropriate instance of this object to the value invalid(2). If circumstances occur on the user-side which cause a prefix to become invalid, the user-side modifies the value of the appropriate instance of this object to invalid(2). Whenever the value of this object for a particular prefix becomes invalid(2), the conceptual row for that prefix may be removed from the table at any time, either immediately or subsequently. Enumeration: 'valid': 1, 'invalid': 2.
         pgIISPAtmAddrPrefix 1.3.6.1.4.1.927.1.9.13.1.1.5 atmaddr read-write
The identifier assigned by a service provider. This ATM address prefix is used by more than one line cards in the Avidia.