SYS-MIB

MIB Reference — IPNetwork Monitor

All MIBsSYS-MIB

Category: Server and Hardware Management

Description:

Defines core system management objects for device identification, uptime, and operational state.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
Gauge
IpAddress
TimeTicks
enterprises

From RFC1213-MIB

DisplayString

From RS232-MIB

rs232PortIndexOBJECT-TYPE

From SNMPv2-SMI

Gauge32

From SNMPv2-TC

TruthValue

What Is SYS-MIB?

SYS-MIB is a Northrop Grumman-Canada, Ltd. (enterprise OID 1978, 'Tiger' system) proprietary MIB reporting the standard RFC 1213 MIB-II system/interface group (sysDescr, sysObjectID, sysUpTime, sysContact, sysName, sysLocation, sysServices, ifTable) tailored for the Tiger platform, whose unit description originates from the system's configuration tool. As a baseline status MIB it lets an administrator confirm basic system identity and per-interface traffic/status on a Northrop Grumman-Canada Tiger system. It is deployed on Northrop Grumman-Canada, Ltd. Tiger system equipment. Engineers can download the SYS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in SYS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • baseline system identity and interface status

Supported Devices

  • Northrop Grumman-Canada, Ltd. Tiger system equipment

Monitoring Examples

An administrator checks sysDescr and ifTable to confirm system identity and interface status on a Northrop Grumman-Canada Tiger system.

OIDs
OID symbolicOID numericTypeAccessDescription
ngcan1.3.6.1.4.1.1978
tiger1.3.6.1.4.1.1978.2
sysMIB1.3.6.1.4.1.1978.2.18
system1.3.6.1.4.1.1978.2.18.1
STR sysDescr1.3.6.1.4.1.1978.2.18.1.1DisplayStringread-writeA textual description of the Tiger. This value corresponds to the description of the unit obtained from the configuration tool. This object should only contain printable ASCII characters.
OID sysObjectID1.3.6.1.4.1.1978.2.18.1.2OBJECT IDENTIFIERread-onlyThe vendor's authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determining `what kind of box' is being managed. Tiger is identified by the subtree (1.3.6.1.4.1.1978.2.18.1.2.0)
TIK sysUpTime1.3.6.1.4.1.1978.2.18.1.3TimeTicksread-onlyThe time (in hundredths of a second) since the system was last re-initialized.
STR sysContact1.3.6.1.4.1.1978.2.18.1.4DisplayStringread-writeThe textual identification of the contact person for this managed node, together with information on how to contact this person. This will normally be filled in via the .cfg file as generated by the configuration tool.
STR sysName1.3.6.1.4.1.1978.2.18.1.5DisplayStringread-writeAn administratively-assigned name for this managed node as identified from the .cfg file that was filled in by the configuration tool. By convention, this is the node's fully-qualified domain name. This parameter is also used as the prompt for TELNET sessions to help identify the Tiger.
STR sysLocation1.3.6.1.4.1.1978.2.18.1.6DisplayStringread-writeThe physical location of this node as identified from the .cfg file that was filled in by the configuration tool. (e.g., `telephone closet, 3rd floor').
INT sysServices1.3.6.1.4.1.1978.2.18.1.7INTEGERread-onlyA value which indicates the set of services that this entity primarily offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs primarily routing functions would have a value of 4 (2^(3-1)). In contrast, a node which is a host offering application services would have a value of 72 (2^(4-1) + 2^(7-1)). Note that in the context of the Internet suite of protocols, values should be calculated accordingly: layer functionality 1 physical (e.g., repeaters) 2 datalink/subnetwork (e.g., bridges) 3 internet (e.g., IP gateways) 4 end-to-end (e.g., IP hosts) 7 applications (e.g., mail relays) For systems including OSI protocols, layers 5 and 6 may also be counted.
interfaces1.3.6.1.4.1.1978.2.18.2
INT ifNumber1.3.6.1.4.1.1978.2.18.2.1INTEGERread-onlyThe number of network interfaces (regardless of their current state) present on this system.
ifTable1.3.6.1.4.1.1978.2.18.2.2not-accessibleA list of interface entries. The number of entries is given by the value of ifNumber.
ifEntry1.3.6.1.4.1.1978.2.18.2.2.1not-accessibleAn interface entry containing objects at the subnetwork layer and below for a particular interface.
INT ifIndex1.3.6.1.4.1.1978.2.18.2.2.1.1INTEGERread-writeA unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
STR ifDescr1.3.6.1.4.1.1978.2.18.2.2.1.2DisplayStringread-writeA textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the hardware interface.
INT ifType1.3.6.1.4.1.1978.2.18.2.2.1.3INTEGERread-writeThe type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack.
INT ifMtu1.3.6.1.4.1.1978.2.18.2.2.1.4INTEGERread-writeThe size of the largest datagram which can be sent/received on the interface, specified in octets. For interfaces that are used for transmitting network datagrams, this is the size of the largest network datagram that can be sent on the interface.
G32 ifSpeed1.3.6.1.4.1.1978.2.18.2.2.1.5Gauge32read-onlyAn estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth.
PHY ifPhysAddress1.3.6.1.4.1.1978.2.18.2.2.1.6PhysAddressread-writeThis information is required for configuration only when BOOTP support is enabled in the TIGER configuration tool in order to properly create a bootptab record. The interface's address at the protocol layer immediately `below' the network layer in the protocol stack. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length. Although it is defined as a writable variable, TIGER may silently discard that information. If the physical address given does not match the actual address, an error message may be shown. For Ethernet interfaces on TIGER, the leading 3 bytes should be: 004003. For Token Ring Interfaces, the leading 3 bytes should be: 0000F6. If you enter only the last 3 bytes of the MAC address, the configuration tool will automatically add the leading 3 bytes.
INT ifAdminStatus1.3.6.1.4.1.1978.2.18.2.2.1.7INTEGERread-writeThe desired state of the interface. The testing(3) state indicates that no operational packets can be passed.
INT ifOperStatus1.3.6.1.4.1.1978.2.18.2.2.1.8INTEGERread-onlyThe current operational state of the interface. testing - indicates that no operational packets can be passed. up - normal operation down-L2 - down due to a level 2 failure dowm-modem - down due to modem control signals - (Token Ring - transmitting beacon frames or rx beaconing, signal loss) down-other - down for some other reason - (Token Ring - no status yet received, i.e. unknown status) up-blocktx - normal; but Tiger received a flow control signal preventing it from sending data up-preventrx - normal; but Tiger sent a flow control signal to stop the other end from sending data up-bothflow - normal; but Tiger received a flow control signal preventing it from sending data AND sent a flow control signal to stop the other end from sending data cts-failure - RTS was requested, but CTS never came (probably detected via poll timeout) dcd-failure - DCD dropped while receiving data, OR - unable to poll because other ends is still transmitting (polled protocols only). hardware-failure - missing FPGA (Token Ring: PCMCIA card missing) up-isolated - (Token Ring: Single station on the ring)
TIK ifLastChange1.3.6.1.4.1.1978.2.18.2.2.1.9TimeTicksread-onlyThe value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value.
CTR ifInOctets1.3.6.1.4.1.1978.2.18.2.2.1.10Counterread-onlyThe total number of octets received on the interface, including framing characters.
CTR ifInUcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.11Counterread-onlyThe number of subnetwork-unicast packets delivered to a higher-layer protocol.
CTR ifInNUcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.12Counterread-onlyThe number of non-unicast (i.e., subnetwork-broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
CTR ifInDiscards1.3.6.1.4.1.1978.2.18.2.2.1.13Counterread-onlyThe number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space.
CTR ifInErrors1.3.6.1.4.1.1978.2.18.2.2.1.14Counterread-onlyThe number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
CTR ifInUnknownProtos1.3.6.1.4.1.1978.2.18.2.2.1.15Counterread-onlyThe number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
CTR ifOutOctets1.3.6.1.4.1.1978.2.18.2.2.1.16Counterread-onlyThe total number of octets transmitted out of the interface, including framing characters.
CTR ifOutUcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.17Counterread-onlyThe total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.
CTR ifOutNUcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.18Counterread-onlyThe total number of packets that higher-level protocols requested be transmitted to a non-unicast (i.e., a subnetwork-broadcast or subnetwork-multicast) address, including those that were discarded or not sent.
CTR ifOutDiscards1.3.6.1.4.1.1978.2.18.2.2.1.19Counterread-onlyThe number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space.
CTR ifOutErrors1.3.6.1.4.1.1978.2.18.2.2.1.20Counterread-onlyThe number of outbound packets that could not be transmitted because of errors.
G32 ifOutQLen1.3.6.1.4.1.1978.2.18.2.2.1.21Gauge32read-onlyThe length of the output packet queue (in packets).
OID ifSpecific1.3.6.1.4.1.1978.2.18.2.2.1.22OBJECT IDENTIFIERread-onlyA reference to MIB definitions specific to the particular media being used to realize the interface. For example, if the interface is realized by an ethernet, then the value of this object refers to a document defining objects specific to ethernet. If this information is not present, its value should be set to the OBJECT IDENTIFIER { 0 0 }, which is a syntatically valid object identifier, and any conformant implementation of ASN.1 and BER must be able to generate and recognize this value.
CTR ifInMulticastPkts1.3.6.1.4.1.1978.2.18.2.2.1.23Counterread-onlyThe number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this sub-layer. For a MAC layer protocol, this includes both Group and Functional addresses.
CTR ifInBroadcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.24Counterread-onlyThe number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this sub-layer.
CTR ifOutMulticastPkts1.3.6.1.4.1.1978.2.18.2.2.1.25Counterread-onlyThe total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC layer protocol, this includes both Group and Functional addresses.
CTR ifOutBroadcastPkts1.3.6.1.4.1.1978.2.18.2.2.1.26Counterread-onlyThe total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent.
INT ifStateChangeTrapEnable1.3.6.1.4.1.1978.2.18.2.2.1.27INTEGERread-writeIndicates whether ifStateChange traps should be generated for this interface. By default, this object should have the value enabled for interfaces which do not operate on 'top' of any other interface (as defined in the ifStackTable), and disabled otherwise.
T/F ifConnectorPresent1.3.6.1.4.1.1978.2.18.2.2.1.28TruthValueread-onlyThis object has the value 'true(1)' if the interface sublayer has a physical connector and the value 'false(2)' otherwise.
INT ifClearStats1.3.6.1.4.1.1978.2.18.2.2.1.29INTEGERread-writeWhen set to 'clear' all of the interface statistics are cleared to zero. It will also force a clearing of all protocol, and 'user' statistics that are related to this interface. Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8) When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as: 1/ all of the statistics have actually been zeroed, and 2/ ifClearStatsTime has been updated with the correct time. Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request. Normal operation would be: NMS Agent set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' . 'cleared' . 'cleared-confirmed' <-- . Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'.
TIK ifClearStatsTime1.3.6.1.4.1.1978.2.18.2.2.1.30TimeTicksread-onlyThe number of ticks when the Tiger last received a ifClearStats command.
INT ifErrorRateTrapEnable1.3.6.1.4.1.1978.2.18.2.2.1.31INTEGERread-writeIndicates whether ifErrorRate traps should be generated for this interface. In addition to enabling the trap via this object, thresholds must also be set.
INT ifErrorRateInterval1.3.6.1.4.1.1978.2.18.2.2.1.32INTEGERread-writeThe amount of time over which any error rate is calculated.
INT ifErrorInLowThreshold1.3.6.1.4.1.1978.2.18.2.2.1.33INTEGERread-writeIf the number of input errors drops below the low water mark (threshold) over the interval defined by 'ifErrorRateInterval' then a trap may be generated if enabled by 'ifErrorRateTrapEnable'. What errors constitute as input errors is dependant on the interface being monitored.
INT ifErrorInHighThreshold1.3.6.1.4.1.1978.2.18.2.2.1.34INTEGERread-writeIf the Low water mark (threshold) has been reached, this defines the other end of the hysterisis curve, when more than 'ifErrorInHighThreshold' number of errors have occured over the measurement interval of 'ifErrorRateInterval' If this value is reached, then a trap may be generated if enabled by 'ifErrorRateTrapEnable'. ifErrorInLowThreshold <= ifErrorInHighThreshold What errors constitute as input errors is dependant on the interface being monitored.
INT ifErrorOutLowThreshold1.3.6.1.4.1.1978.2.18.2.2.1.35INTEGERread-writeIf the number of output errors drops below the low water mark (threshold) over the interval defined by 'ifErrorRateInterval' then a trap may be generated if enabled by 'ifErrorRateTrapEnable'. ifErrorOutLowThreshold <= ifErrorOutHighThreshold What errors constitute as output errors is dependant on the interface being monitored.
INT ifErrorOutHighThreshold1.3.6.1.4.1.1978.2.18.2.2.1.36INTEGERread-writeIf the Low water mark (threshold) has been reached, this defines the other end of the hysterisis curve, when more than 'ifErrorOutHighThreshold' number of errors have occured over the measurement interval of 'ifErrorRateInterval' If this value is reached, then a trap may be generated if enabled by 'ifErrorRateTrapEnable'. ifErrorOutLowThreshold <= ifErrorOutHighThreshold What errors constitute as output errors is dependant on the interface being monitored.
INT ifErrType1.3.6.1.4.1.1978.2.18.2.2.1.37INTEGERread-onlyInforms the NMS of the reason for the ifErrorRate trap that was received. When read asynchronously, it also indicates the last known state of this interface entry.
ip1.3.6.1.4.1.1978.2.18.3
INT ipForwarding1.3.6.1.4.1.1978.2.18.3.1INTEGERread-writeThe indication of whether this entity is acting as an IP gateway in respect to the forwarding of datagrams received by, but not addressed to, this entity. IP gateways forward datagrams. IP hosts do not (except those source-routed via the host). Note that for some managed nodes, this object may take on only a subset of the values possible. Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to change this object to an inappropriate value.
INT ipDefaultTTL1.3.6.1.4.1.1978.2.18.3.2INTEGERread-writeThe default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entity, whenever a TTL value is not supplied by the transport layer protocol.
CTR ipInReceives1.3.6.1.4.1.1978.2.18.3.3Counterread-onlyThe total number of input datagrams received from interfaces, including those received in error.
CTR ipInHdrErrors1.3.6.1.4.1.1978.2.18.3.4Counterread-onlyThe number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
CTR ipInAddrErrors1.3.6.1.4.1.1978.2.18.3.5Counterread-onlyThe number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (e.g., 0.0.0.0) and addresses of unsupported Classes (e.g., Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
CTR ipForwDatagrams1.3.6.1.4.1.1978.2.18.3.6Counterread-onlyThe number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter will include only those packets which were Source-Routed via this entity, and the Source- Route option processing was successful.
CTR ipInUnknownProtos1.3.6.1.4.1.1978.2.18.3.7Counterread-onlyThe number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
CTR ipInDiscards1.3.6.1.4.1.1978.2.18.3.8Counterread-onlyThe number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (e.g., for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
CTR ipInDelivers1.3.6.1.4.1.1978.2.18.3.9Counterread-onlyThe total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
CTR ipOutRequests1.3.6.1.4.1.1978.2.18.3.10Counterread-onlyThe total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
CTR ipOutDiscards1.3.6.1.4.1.1978.2.18.3.11Counterread-onlyThe number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (e.g., for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
CTR ipOutNoRoutes1.3.6.1.4.1.1978.2.18.3.12Counterread-onlyThe number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion. Note that this includes any datagarms which a host cannot route because all of its default gateways are down.
INT ipReasmTimeout1.3.6.1.4.1.1978.2.18.3.13INTEGERread-writeThe maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
CTR ipReasmReqds1.3.6.1.4.1.1978.2.18.3.14Counterread-onlyThe number of IP fragments received which needed to be reassembled at this entity.
CTR ipReasmOKs1.3.6.1.4.1.1978.2.18.3.15Counterread-onlyThe number of IP datagrams successfully re-assembled.
CTR ipReasmFails1.3.6.1.4.1.1978.2.18.3.16Counterread-onlyThe number of failures detected by the IP re- assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.
CTR ipFragOKs1.3.6.1.4.1.1978.2.18.3.17Counterread-onlyThe number of IP datagrams that have been successfully fragmented at this entity.
CTR ipFragFails1.3.6.1.4.1.1978.2.18.3.18Counterread-onlyThe number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, e.g., because their Don't Fragment flag was set.
CTR ipFragCreates1.3.6.1.4.1.1978.2.18.3.19Counterread-onlyThe number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
ipAddrTable1.3.6.1.4.1.1978.2.18.3.20not-accessibleThe table of addressing information relevant to this entity's IP addresses.
ipAddrEntry1.3.6.1.4.1.1978.2.18.3.20.1not-accessibleThe addressing information for one of this entity's IP addresses.
IP ipAdEntAddr1.3.6.1.4.1.1978.2.18.3.20.1.1IpAddressread-writeThe IP address to which this entry's addressing information pertains. If this is a PPP port, an IP address of 0.0.0.0 signifies that IP address negotiation will occur on this link. If negotiation is enabled, the net mask will be forced to a correct value that is appropriate for that class of address.
INT ipAdEntIfIndex1.3.6.1.4.1.1978.2.18.3.20.1.2INTEGERread-writeThe index value which uniquely identifies the interface to which this entry is applicable. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
IP ipAdEntNetMask1.3.6.1.4.1.1978.2.18.3.20.1.3IpAddressread-writeThe subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.
INT ipAdEntBcastAddr1.3.6.1.4.1.1978.2.18.3.20.1.4INTEGERread-writeThe value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this entry. For example, when the Internet standard all-ones broadcast address is used, the value will be 1. This value applies to both the subnet and network broadcasts addresses used by the entity on this (logical) interface.
INT ipAdEntReasmMaxSize1.3.6.1.4.1.1978.2.18.3.20.1.5INTEGERread-writeThe size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.
ipNetToMediaTable1.3.6.1.4.1.1978.2.18.3.22not-accessibleThe IP Address Translation table used for mapping from IP addresses to physical addresses.
ipNetToMediaEntry1.3.6.1.4.1.1978.2.18.3.22.1not-accessibleEach entry contains one IpAddress to `physical' address equivalence.
INT ipNetToMediaIfIndex1.3.6.1.4.1.1978.2.18.3.22.1.1INTEGERread-writeThe interface on which this entry's equivalence is effective. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
PHY ipNetToMediaPhysAddress1.3.6.1.4.1.1978.2.18.3.22.1.2PhysAddressread-writeThe media-dependent `physical' address.
IP ipNetToMediaNetAddress1.3.6.1.4.1.1978.2.18.3.22.1.3IpAddressread-writeThe IpAddress corresponding to the media-dependent `physical' address.
INT ipNetToMediaType1.3.6.1.4.1.1978.2.18.3.22.1.4INTEGERread-writeThe type of mapping. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipNetToMediaTable. That is, it effectively dissasociates the interface identified with said entry from the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant ipNetToMediaType object.
CTR ipRoutingDiscards1.3.6.1.4.1.1978.2.18.3.23Counterread-onlyThe number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
INT ipClearStats1.3.6.1.4.1.1978.2.18.3.24INTEGERread-writeWhen set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics are cleared to zero. When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as: 1/ all of the statistics have actually been zeroed, and 2/ ipClearStatsTime has been updated with the correct time. Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request. Normal operation would be: NMS Agent set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' . 'cleared' . 'cleared-confirmed' <-- . Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'.
TIK ipClearStatsTime1.3.6.1.4.1.1978.2.18.3.25TimeTicksread-onlyThe number of ticks when the Tiger last received a ipClearStats command.
ipForward1.3.6.1.4.1.1978.2.18.3.26
GAU ipForwardNumber1.3.6.1.4.1.1978.2.18.3.26.1Gaugeread-onlyThe number of current ipForwardTable entries that are not invalid.
ipForwardTable1.3.6.1.4.1.1978.2.18.3.26.2not-accessibleThis entity's IP Routing table.
ipForwardEntry1.3.6.1.4.1.1978.2.18.3.26.2.1not-accessibleA particular route to a particular destination, under a particular policy.
IP ipForwardDest1.3.6.1.4.1.1978.2.18.3.26.2.1.1IpAddressread-writeThe destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. This object may not take a Multicast (Class D) address value. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardMask object is not equal to x.
IP ipForwardMask1.3.6.1.4.1.1978.2.18.3.26.2.1.2IpAddressread-writeIndicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipForwardDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipForwardMask by reference to the IP Address Class. Any assignment (implicit or otherwise) of an instance of this object to a value x must be rejected if the bitwise logical-AND of x with the value of the corresponding instance of the ipForwardDest object is not equal to ipForwardDest.
IP ipForwardNextHop1.3.6.1.4.1.1978.2.18.3.26.2.1.4IpAddressread-writeOn remote routes, the address of the next system en route; Otherwise, 0.0.0.0.
INT ipForwardIfIndex1.3.6.1.4.1.1978.2.18.3.26.2.1.5INTEGERread-writeThe ifIndex value which identifies the local interface through which the next hop of this route should be reached.
INT ipForwardMetric11.3.6.1.4.1.1978.2.18.3.26.2.1.11INTEGERread-writeThe primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipForwardProto value. For static routing tables, Metric1 is the default 'cost' (1-15) of the route when it is in the up condition. This is compared to other possible routes for the same destination, to state the preferred path. If this metric is not used, its value should be set to -1.
INT ipForwardMetric21.3.6.1.4.1.1978.2.18.3.26.2.1.12INTEGERread-writeAn alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipForwardProto value. For static routing tables, Metric1 is the default 'cost' (1-15) of the route when it is in the up condition. This is compared to other possible routes for the same destination, to state the preferred path. If this metric is not used, its value should be set to -1.
INT ipForwardMetric31.3.6.1.4.1.1978.2.18.3.26.2.1.13INTEGERread-writeAn alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipForwardProto value. For static routing tables, Metric1 is the default 'cost' (1-15) of the route when it is in the up condition. This is compared to other possible routes for the same destination, to state the preferred path. If this metric is not used, its value should be set to -1.
INT ipForwardMetric41.3.6.1.4.1.1978.2.18.3.26.2.1.14INTEGERread-writeAn alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipForwardProto value. For static routing tables, Metric1 is the default 'cost' (1-15) of the route when it is in the up condition. This is compared to other possible routes for the same destination, to state the preferred path. If this metric is not used, its value should be set to -1.
INT ipForwardMetric51.3.6.1.4.1.1978.2.18.3.26.2.1.15INTEGERread-writeAn alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipForwardProto value. For static routing tables, Metric1 is the default 'cost' (1-15) of the route when it is in the up condition. This is compared to other possible routes for the same destination, to state the preferred path. If this metric is not used, its value should be set to -1.
INT ipForwardTrapControl1.3.6.1.4.1.1978.2.18.3.26.3INTEGERread-writeIf enabled, it allows the system to generate ipForward traps, when the routing table changes.
INT ipForwardTrapReason1.3.6.1.4.1.1978.2.18.3.26.4INTEGERread-onlyThe reason that the ipRouteChange trap was generated. add - the entry was added. delete - the entry was removed. modified - the entry was modified. The metric probably changed value due to a link going up or down).
icmp1.3.6.1.4.1.1978.2.18.4
CTR icmpInMsgs1.3.6.1.4.1.1978.2.18.4.1Counterread-onlyThe total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
CTR icmpInErrors1.3.6.1.4.1.1978.2.18.4.2Counterread-onlyThe number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
CTR icmpInDestUnreachs1.3.6.1.4.1.1978.2.18.4.3Counterread-onlyThe number of ICMP Destination Unreachable messages received.
CTR icmpInTimeExcds1.3.6.1.4.1.1978.2.18.4.4Counterread-onlyThe number of ICMP Time Exceeded messages received.
CTR icmpInParmProbs1.3.6.1.4.1.1978.2.18.4.5Counterread-onlyThe number of ICMP Parameter Problem messages received.
CTR icmpInSrcQuenchs1.3.6.1.4.1.1978.2.18.4.6Counterread-onlyThe number of ICMP Source Quench messages received.
CTR icmpInRedirects1.3.6.1.4.1.1978.2.18.4.7Counterread-onlyThe number of ICMP Redirect messages received.
CTR icmpInEchos1.3.6.1.4.1.1978.2.18.4.8Counterread-onlyThe number of ICMP Echo (request) messages received.
CTR icmpInEchoReps1.3.6.1.4.1.1978.2.18.4.9Counterread-onlyThe number of ICMP Echo Reply messages received.
CTR icmpInTimestamps1.3.6.1.4.1.1978.2.18.4.10Counterread-onlyThe number of ICMP Timestamp (request) messages received.
CTR icmpInTimestampReps1.3.6.1.4.1.1978.2.18.4.11Counterread-onlyThe number of ICMP Timestamp Reply messages received.
CTR icmpInAddrMasks1.3.6.1.4.1.1978.2.18.4.12Counterread-onlyThe number of ICMP Address Mask Request messages received.
CTR icmpInAddrMaskReps1.3.6.1.4.1.1978.2.18.4.13Counterread-onlyThe number of ICMP Address Mask Reply messages received.
CTR icmpOutMsgs1.3.6.1.4.1.1978.2.18.4.14Counterread-onlyThe total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
CTR icmpOutErrors1.3.6.1.4.1.1978.2.18.4.15Counterread-onlyThe number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
CTR icmpOutDestUnreachs1.3.6.1.4.1.1978.2.18.4.16Counterread-onlyThe number of ICMP Destination Unreachable messages sent.
CTR icmpOutTimeExcds1.3.6.1.4.1.1978.2.18.4.17Counterread-onlyThe number of ICMP Time Exceeded messages sent.
CTR icmpOutParmProbs1.3.6.1.4.1.1978.2.18.4.18Counterread-onlyThe number of ICMP Parameter Problem messages sent.
CTR icmpOutSrcQuenchs1.3.6.1.4.1.1978.2.18.4.19Counterread-onlyThe number of ICMP Source Quench messages sent.
CTR icmpOutRedirects1.3.6.1.4.1.1978.2.18.4.20Counterread-onlyThe number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.
CTR icmpOutEchos1.3.6.1.4.1.1978.2.18.4.21Counterread-onlyThe number of ICMP Echo (request) messages sent.
CTR icmpOutEchoReps1.3.6.1.4.1.1978.2.18.4.22Counterread-onlyThe number of ICMP Echo Reply messages sent.
CTR icmpOutTimestamps1.3.6.1.4.1.1978.2.18.4.23Counterread-onlyThe number of ICMP Timestamp (request) messages sent.
CTR icmpOutTimestampReps1.3.6.1.4.1.1978.2.18.4.24Counterread-onlyThe number of ICMP Timestamp Reply messages sent.
CTR icmpOutAddrMasks1.3.6.1.4.1.1978.2.18.4.25Counterread-onlyThe number of ICMP Address Mask Request messages sent.
CTR icmpOutAddrMaskReps1.3.6.1.4.1.1978.2.18.4.26Counterread-onlyThe number of ICMP Address Mask Reply messages sent.
tcp1.3.6.1.4.1.1978.2.18.5
INT tcpRtoAlgorithm1.3.6.1.4.1.1978.2.18.5.1INTEGERread-onlyThe algorithm used to determine the timeout value used for retransmitting unacknowledged octets.
INT tcpRtoMin1.3.6.1.4.1.1978.2.18.5.2INTEGERread-onlyThe minimum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the LBOUND quantity described in RFC 793. UNITS: milliseconds
INT tcpRtoMax1.3.6.1.4.1.1978.2.18.5.3INTEGERread-onlyThe maximum value permitted by a TCP implementation for the retransmission timeout, measured in milliseconds. More refined semantics for objects of this type depend upon the algorithm used to determine the retransmission timeout. In particular, when the timeout algorithm is rsre(3), an object of this type has the semantics of the UBOUND quantity described in RFC 793. UNITS: milliseconds
INT tcpMaxConn1.3.6.1.4.1.1978.2.18.5.4INTEGERread-onlyThe limit on the total number of TCP connections the entity can support. In entities where the maximum number of connections is dynamic, this object should contain the value -1.
CTR tcpActiveOpens1.3.6.1.4.1.1978.2.18.5.5Counterread-onlyThe number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
CTR tcpPassiveOpens1.3.6.1.4.1.1978.2.18.5.6Counterread-onlyThe number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
CTR tcpAttemptFails1.3.6.1.4.1.1978.2.18.5.7Counterread-onlyThe number of times TCP connections have made a direct transition to the CLOSED state from either the SYN-SENT state or the SYN-RCVD state, plus the number of times TCP connections have made a direct transition to the LISTEN state from the SYN-RCVD state.
CTR tcpEstabResets1.3.6.1.4.1.1978.2.18.5.8Counterread-onlyThe number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.
G32 tcpCurrEstab1.3.6.1.4.1.1978.2.18.5.9Gauge32read-onlyThe number of TCP connections for which the current state is either ESTABLISHED or CLOSE-WAIT.
CTR tcpInSegs1.3.6.1.4.1.1978.2.18.5.10Counterread-onlyThe total number of segments received, including those received in error. This count includes segments received on currently established connections.
CTR tcpOutSegs1.3.6.1.4.1.1978.2.18.5.11Counterread-onlyThe total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
CTR tcpRetransSegs1.3.6.1.4.1.1978.2.18.5.12Counterread-onlyThe total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
tcpConnTable1.3.6.1.4.1.1978.2.18.5.13not-accessibleA table containing TCP connection-specific information.
tcpConnEntry1.3.6.1.4.1.1978.2.18.5.13.1not-accessibleInformation about a particular current TCP connection. An object of this type is transient, in that it ceases to exist when (or soon after) the connection makes the transition to the CLOSED state.
INT tcpConnState1.3.6.1.4.1.1978.2.18.5.13.1.1INTEGERread-writeThe state of this TCP connection. NOTE: The following paragraphs are from rfc1213 and Tiger does not currently support this. The only value which may be set by a management station is deleteTCB(12). Accordingly, it is appropriate for an agent to return a `badValue' response if a management station attempts to set this object to any other value. If a management station sets this object to the value deleteTCB(12), then this has the effect of deleting the TCB (as defined in RFC 793) of the corresponding connection on the managed node, resulting in immediate termination of the connection. As an implementation-specific option, a RST segment may be sent from the managed node to the other TCP endpoint (note however that RST segments are not sent reliably).
IP tcpConnLocalAddress1.3.6.1.4.1.1978.2.18.5.13.1.2IpAddressread-onlyThe local IP address for this TCP connection. In the case of a connection in the listen state which is willing to accept connections for any IP interface associated with the node, the value 0.0.0.0 is used.
INT tcpConnLocalPort1.3.6.1.4.1.1978.2.18.5.13.1.3INTEGERread-onlyThe local port number for this TCP connection.
IP tcpConnRemAddress1.3.6.1.4.1.1978.2.18.5.13.1.4IpAddressread-onlyThe remote IP address for this TCP connection.
INT tcpConnRemPort1.3.6.1.4.1.1978.2.18.5.13.1.5INTEGERread-onlyThe remote port number for this TCP connection.
CTR tcpInErrs1.3.6.1.4.1.1978.2.18.5.14Counterread-onlyThe total number of segments received in error (e.g., bad TCP checksums).
CTR tcpOutRsts1.3.6.1.4.1.1978.2.18.5.15Counterread-onlyThe number of TCP segments sent containing the RST flag.
INT tcpRetransAttempts1.3.6.1.4.1.1978.2.18.5.16INTEGERread-writeThe number of TCP retransmision attempts before the socket connection is declared down. The interval between attempts is fixed at approximately 7 seconds. This parameter is global for all TCP applications. (default=6)
INT tcpKAInterval1.3.6.1.4.1.1978.2.18.5.17INTEGERread-writeThe interval of time, expressed in seconds between keepalive packets. Keepalive packets are generated when there is no other socket traffic. Although the operation of keepalive is defined on a per socket basis (see autif.mib), this parameter is global for all TCP applications. (default=30)
INT tcpKAAttempts1.3.6.1.4.1.1978.2.18.5.18INTEGERread-writeThe number of successive TCP keepalive packets sent with no reply at tcpKAIntervals before the socket connection is declared down. Although the operation of keepalive is defined on a per socket basis (see autif.mib), this parameter is global for all TCP applications. (default=3)
udp1.3.6.1.4.1.1978.2.18.6
CTR udpInDatagrams1.3.6.1.4.1.1978.2.18.6.1Counterread-onlyThe total number of UDP datagrams delivered to UDP users.
CTR udpNoPorts1.3.6.1.4.1.1978.2.18.6.2Counterread-onlyThe total number of received UDP datagrams for which there was no application at the destination port.
CTR udpInErrors1.3.6.1.4.1.1978.2.18.6.3Counterread-onlyThe number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.
CTR udpOutDatagrams1.3.6.1.4.1.1978.2.18.6.4Counterread-onlyThe total number of UDP datagrams sent from this entity.
udpTable1.3.6.1.4.1.1978.2.18.6.5not-accessibleA table containing UDP listener information.
udpEntry1.3.6.1.4.1.1978.2.18.6.5.1not-accessibleInformation about a particular current UDP listener.
IP udpLocalAddress1.3.6.1.4.1.1978.2.18.6.5.1.1IpAddressread-onlyThe local IP address for this UDP listener. In the case of a UDP listener which is willing to accept datagrams for any IP interface associated with the node, the value 0.0.0.0 is used.
INT udpLocalPort1.3.6.1.4.1.1978.2.18.6.5.1.2INTEGERread-onlyThe local port number for this UDP listener.
snmp1.3.6.1.4.1.1978.2.18.7
CTR snmpInPkts1.3.6.1.4.1.1978.2.18.7.1Counterread-onlyThe total number of Messages delivered to the SNMP entity from the transport service.
CTR snmpOutPkts1.3.6.1.4.1.1978.2.18.7.2Counterread-onlyThe total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.
CTR snmpInBadVersions1.3.6.1.4.1.1978.2.18.7.3Counterread-onlyThe total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.
CTR snmpInBadCommunityNames1.3.6.1.4.1.1978.2.18.7.4Counterread-onlyThe total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.
CTR snmpInBadCommunityUses1.3.6.1.4.1.1978.2.18.7.5Counterread-onlyThe total number of SNMP Messages delivered to the SNMP protocol entity which represented an SNMP operation which was not allowed by the SNMP community named in the Message.
CTR snmpInASNParseErrs1.3.6.1.4.1.1978.2.18.7.6Counterread-onlyThe total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.
CTR snmpInTooBigs1.3.6.1.4.1.1978.2.18.7.8Counterread-onlyThe total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `tooBig'.
CTR snmpInNoSuchNames1.3.6.1.4.1.1978.2.18.7.9Counterread-onlyThe total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `noSuchName'.
CTR snmpInBadValues1.3.6.1.4.1.1978.2.18.7.10Counterread-onlyThe total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `badValue'.
CTR snmpInReadOnlys1.3.6.1.4.1.1978.2.18.7.11Counterread-onlyThe total number valid SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.
CTR snmpInGenErrs1.3.6.1.4.1.1978.2.18.7.12Counterread-onlyThe total number of SNMP PDUs which were delivered to the SNMP protocol entity and for which the value of the error-status field is `genErr'.
CTR snmpInTotalReqVars1.3.6.1.4.1.1978.2.18.7.13Counterread-onlyThe total number of MIB objects which have been retrieved successfully by the SNMP protocol entity as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
CTR snmpInTotalSetVars1.3.6.1.4.1.1978.2.18.7.14Counterread-onlyThe total number of MIB objects which have been altered successfully by the SNMP protocol entity as the result of receiving valid SNMP Set-Request PDUs.
CTR snmpInGetRequests1.3.6.1.4.1.1978.2.18.7.15Counterread-onlyThe total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInGetNexts1.3.6.1.4.1.1978.2.18.7.16Counterread-onlyThe total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInSetRequests1.3.6.1.4.1.1978.2.18.7.17Counterread-onlyThe total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInGetResponses1.3.6.1.4.1.1978.2.18.7.18Counterread-onlyThe total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpInTraps1.3.6.1.4.1.1978.2.18.7.19Counterread-onlyThe total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.
CTR snmpOutTooBigs1.3.6.1.4.1.1978.2.18.7.20Counterread-onlyThe total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `tooBig.'
CTR snmpOutNoSuchNames1.3.6.1.4.1.1978.2.18.7.21Counterread-onlyThe total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.
CTR snmpOutBadValues1.3.6.1.4.1.1978.2.18.7.22Counterread-onlyThe total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `badValue'.
CTR snmpOutGenErrs1.3.6.1.4.1.1978.2.18.7.24Counterread-onlyThe total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `genErr'.
CTR snmpOutGetRequests1.3.6.1.4.1.1978.2.18.7.25Counterread-onlyThe total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutGetNexts1.3.6.1.4.1.1978.2.18.7.26Counterread-onlyThe total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutSetRequests1.3.6.1.4.1.1978.2.18.7.27Counterread-onlyThe total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutGetResponses1.3.6.1.4.1.1978.2.18.7.28Counterread-onlyThe total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.
CTR snmpOutTraps1.3.6.1.4.1.1978.2.18.7.29Counterread-onlyThe total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.
INT snmpEnableAuthenTraps1.3.6.1.4.1.1978.2.18.7.30INTEGERread-writeIndicates whether the SNMP agent process is permitted to generate authentication-failure traps. The value of this object overrides any configuration information; as such, it provides a means whereby all authentication-failure traps may be disabled. Note that it is strongly recommended that this object be stored in non-volatile memory so that it remains constant between re-initializations of the network management system.
sysTraps1.3.6.1.4.1.1978.2.18.8
NTF ifStateChange1.3.6.1.4.1.1978.2.18.8.0.1A linkStateChange trap signifies that the sending protocol entity recognizes a change in one of the communication links represented in the agent's configuration. Currently this trap is only applicable to: lapb frame_relay sdlc token ring u100 ethernet alc ppp Other interfaces that may be supported in the future are: apath pad x2x cap mux frip autif
NTF ifErrorRate1.3.6.1.4.1.1978.2.18.8.0.2A linkErrorRate trap signifies that the sending protocol entity discovered an error rate that in one of the communication links represented in the agent's configuration. Currently this trap is only applicable to: lapb frame_relay sdlc token ring u100 ethernet alc ppp Other interfaces that may be supported in the future are: apath pad x2x cap mux frip autif
NTF ipRouteChange1.3.6.1.4.1.1978.2.18.8.0.3An ipRouteChange trap signifies that the IP Forwarding table has been changed. An entry was added, deleted or modified.
partyMIB1.3.6.1.4.1.1978.2.18.9
partyCommTable1.3.6.1.4.1.1978.2.18.9.1not-accessibleThe SNMP community database.
partyCommEntry1.3.6.1.4.1.1978.2.18.9.1.1not-accessibleLocally held information about a particular SNMP community.
INT partyCommIndex1.3.6.1.4.1.1978.2.18.9.1.1.1INTEGERread-writeA unique value for each SNMPv2 party. The value for each SNMPv2 party must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization.
STR partyCommunity1.3.6.1.4.1.1978.2.18.9.1.1.2DisplayStringread-writeThe SNMP community associated with this entry.
INT partyAccess1.3.6.1.4.1.1978.2.18.9.1.1.3INTEGERread-writeIndicates the access rights of this community.
partyTrapTable1.3.6.1.4.1.1978.2.18.9.2not-accessibleThe SNMP trap destination database.
partyTrapEntry1.3.6.1.4.1.1978.2.18.9.2.1not-accessibleLocally held information about a particular SNMP trap destination.
INT partyTrapIndex1.3.6.1.4.1.1978.2.18.9.2.1.1INTEGERread-writeA unique value for each SNMP trap destination entry.
IP partyTAddress1.3.6.1.4.1.1978.2.18.9.2.1.2IpAddressread-writeThe IP address by which the party receives network management traffic.
INT partyTPort1.3.6.1.4.1.1978.2.18.9.2.1.3INTEGERread-writeThe port address by which the party receives network management traffic.
INT partyTDomain1.3.6.1.4.1.1978.2.18.9.2.1.4INTEGERread-writeIndicates the kind of transport service by which the party receives network management traffic.
STR partyTCommunity1.3.6.1.4.1.1978.2.18.9.2.1.5DisplayStringread-writeThe SNMP community used in the trap response to this entries address.

RFC description

Provides generic system management objects similar to MIB-II for Northrop Grumman TIGER network devices.

Start monitoring Northrop Grumman-Canada, Ltd. Tiger system equipment (system identity/interface status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download SYS-MIB