Home/Catalog/PAIRGAIN-IISP-MIB

PAIRGAIN-IISP-MIB

AI MIB Summary

The PAIRGAIN-IISP-MIB module enables SNMP-based monitoring and configuration of routing protocols and interface states on PairGain IISP (Integrated Internet Service Provider) gateway devices. It provides granular visibility into IISP-specific routing tables, session establishment metrics, and protocol state transitions for network troubleshooting and policy enforcement.

Initial version of the MIB for monitoring and controlling IISP routing.
Main OID:
pgIISP.1.3.6.1.4.1.927.1.9.13.1
25
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

25 total
Object Name
pgIISPInitial version of the MIB for monitoring and controlling IISP routing.
MODULE-IDENTITY
.1.3.6.1.4.1.927.1.9.13.1
pgIISPMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.927.1.9.13.1.1
pgIISPRouteAddrIndexNextThis 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.ro
INTEGER
.1.3.6.1.4.1.927.1.9.13.1.1.1
pgIISPRouteAddrTableA 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..
SEQUENCE OF PgIISPRouteAddrEntry
.1.3.6.1.4.1.927.1.9.13.1.1.2
pgIISPRouteAddrEntryAn entry in the table, containing information about a reachable address prefix.
PgIISPRouteAddrEntry
.1.3.6.1.4.1.927.1.9.13.1.1.2.1
pgIISPRouteAddrIndexAn index into the set of listings of connectivity to a given route.ro
Integer32
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.1
pgIISPRouteAddrRowStatusTo create, delete, activate and de-activate a reachable address prefix.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.2
pgIISPRouteAddrAddressThe value of the ATM End System Address prefix.ro
PgAtmAddrPrefix
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.3
pgIISPRouteAddrPrefixLengthThe prefix length to be applied to the ATM End System Address prefix.ro
PgAtmPrefixLength
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.4
pgIISPRouteAddrIfIndexThe local interface over which the reachable address can be reached. The value zero indicates an unknown interface or reachability through a remote node.rw
InterfaceIndex (IF-MIB)
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.5
pgIISPRouteAddrTypeThe 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.rw
Enumeration
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.6
pgIISPRouteAddrAdminStatusIndicates whether the route is configured to be used.rw
Enumeration
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.7
pgIISPRouteAddrOperStatusIndicates whether the reachable address prefix is operationally valid and whether it is being advertised by this node.rw
Enumeration
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.8
pgIISPRouteAddrTimeStampIndicates when the connectivity from the advertising node to the reachable address prefix became known to the local node.rw
TimeStamp (SNMPv2-TC)
.1.3.6.1.4.1.927.1.9.13.1.1.2.1.9
pgIISPNetPrefixIndexNextThis 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.ro
INTEGER
.1.3.6.1.4.1.927.1.9.13.1.1.3
pgIISPNetPrefixTableA table implemented by the user-side, containing the network-prefix(es) for ATM-layer addresses in effect on the user side of the UNI.
SEQUENCE OF PgIISPNetPrefixEntry
.1.3.6.1.4.1.927.1.9.13.1.1.4
pgIISPNetPrefixEntryInformation 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.
PgIISPNetPrefixEntry
.1.3.6.1.4.1.927.1.9.13.1.1.4.1
pgIISPNetPrefixIndexAn index into the set of listings of connectivity to a given address prefix.ro
Integer32
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.1
pgIISPNetPrefixRowStatusTo create, delete, activate and de-activate a net prefix entry.rw
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.2
pgIISPNetPrefixPortA 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.ro
INTEGER
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.3
pgIISPNetPrefixPrefixThe network prefix for ATM addresses which is in effect on the user side of the ATM UNI port.ro
NetPrefix
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.4
pgIISPNetPrefixFormatATM address format.rw
Enumeration
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.5
pgIISPNetPrefixLengthThe number of bits that are significant in an ATM address prefix used.rw
Integer32
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.6
pgIISPNetPrefixStatusAn 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.rw
Enumeration
.1.3.6.1.4.1.927.1.9.13.1.1.4.1.7
pgIISPAtmAddrPrefixThe identifier assigned by a service provider. This ATM address prefix is used by more than one line cards in the Avidia.rw
AtmAddr (ATM-TC-MIB)
.1.3.6.1.4.1.927.1.9.13.1.1.5
PAIRGAIN-IISP-MIB - SNMP MIB Reference | MIBs Explorer