LIVINGSTON-SNMP: View SNMP OID List / Download MIB

A textual description of the entity. This value should include the full name and version identification of the system's hardware type, software operating-system, and networking software. It is mandatory that this only contain printable ASCII characters.

The 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. For example, if vendor `Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its `Fred Router'.

The time (in hundredths of a second) since the network management portion of the system was last re-initialized.

The textual identification of the contact person for this managed node, together with information on how to contact this person.

An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.

The physical location of this node (e.g., `telephone closet, 3rd floor').

A 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.

The number of network interfaces (regardless of their current state) present on this system.

A list of interface entries. The number of entries is given by the value of ifNumber.

An interface entry containing objects at the subnetwork layer and below for a particular interface.

A 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.

A 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.

The type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack. Enumeration: 'propPointToPointSerial': 22, 'frame-relay': 32, 'softwareLoopback': 24, 'rfc877-x25': 5, 'ds3': 30, 'ppp': 23, 'ddn-x25': 4, 'slip': 28, 'proteon-10Mbit': 12, 'ethernet-3Mbit': 26, 'sip': 31, 'iso88023-csmacd': 7, 'other': 1, 'sdlc': 17, 'lapb': 16, 'iso88024-tokenBus': 8, 'hyperchannel': 14, 'basicISDN': 20, 'ethernet-csmacd': 6, 'primaryISDN': 21, 'e1': 19, 'fddi': 15, 'proteon-80Mbit': 13, 'starLan': 11, 'eon': 25, 'iso88025-tokenRing': 9, 'ds1': 18, 'hdh1822': 3, 'nsip': 27, 'regular1822': 2, 'iso88026-man': 10, 'ultra': 29.

The 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.

An 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.

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.

The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

The 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.

The total number of octets received on the interface, including framing characters.

The number of subnetwork-unicast packets delivered to a higher-layer protocol.

The number of non-unicast (i.e., subnetwork- broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.

The 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.

The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.

The number of packets received via the interface which were discarded because of an unknown or unsupported protocol.

The total number of octets transmitted out of the interface, including framing characters.

The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including those that were discarded or not sent.

The 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.

The 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.

The number of outbound packets that could not be transmitted because of errors.

The length of the output packet queue (in packets).

A 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.

The Address Translation tables contain the NetworkAddress to `physical' address equivalences. Some interfaces do not use translation tables for determining address equivalences (e.g., DDN-X.25 has an algorithmic method); if all interfaces are of this type, then the Address Translation table is empty, i.e., has zero entries.

Each entry contains one NetworkAddress to `physical' address equivalence.

The 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.

The media-dependent `physical' address. Setting this object to a null string (one of zero length) has the effect of invaliding the corresponding entry in the atTable object. 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 atPhysAddress object.

The NetworkAddress (e.g., the IP address) corresponding to the media-dependent `physical' address.

The 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. Enumeration: 'forwarding': 1, 'not-forwarding': 2.

The 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.

The total number of input datagrams received from interfaces, including those received in error.

The 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.

The 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.

The 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.

The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.

The 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.

The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).

The 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.

The 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.

The 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.

The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.

The number of IP fragments received which needed to be reassembled at this entity.

The number of IP datagrams successfully re- assembled.

The 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.

The number of IP datagrams that have been successfully fragmented at this entity.

The 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.

The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.

The table of addressing information relevant to this entity's IP addresses.

The addressing information for one of this entity's IP addresses.

The IP address to which this entry's addressing information pertains.

The 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.

The 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.

The 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.

The size of the largest IP datagram which this entity can re-assemble from incoming IP fragmented datagrams received on this interface.

This entity's IP Routing table.

A route to a particular destination.

The destination IP address of this route. An entry with a value of 0.0.0.0 is considered a default route. Multiple routes to a single destination can appear in the table, but access to such multiple entries is dependent on the table- access mechanisms defined by the network management protocol in use.

The index value which uniquely identifies the local interface through which the next hop of this route should be reached. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.

The primary routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

The IP address of the next hop of this route. (In the case of a route bound to an interface which is realized via a broadcast media, the value of this field is the agent's IP address on that interface.)

The type of route. Note that the values direct(3) and indirect(4) refer to the notion of direct and indirect routing in the IP architecture. Setting this object to the value invalid(2) has the effect of invalidating the corresponding entry in the ipRouteTable object. That is, it effectively dissasociates the destination identified with said entry from the route 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 ipRouteType object. Enumeration: 'indirect': 4, 'other': 1, 'direct': 3, 'invalid': 2.

The routing mechanism via which this route was learned. Inclusion of values for gateway routing protocols is not intended to imply that hosts should support those protocols. Enumeration: 'bgp': 14, 'bbnSpfIgp': 12, 'ggp': 6, 'ospf': 13, 'egp': 5, 'rip': 8, 'es-is': 10, 'ciscoIgrp': 11, 'other': 1, 'is-is': 9, 'icmp': 4, 'local': 2, 'hello': 7, 'netmgmt': 3.

The number of seconds since this route was last updated or otherwise determined to be correct. Note that no semantics of `too old' can be implied except through knowledge of the routing protocol by which the route was learned.

Indicate the mask to be logical-ANDed with the destination address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network, and then using one of: mask network 255.0.0.0 class-A 255.255.0.0 class-B 255.255.255.0 class-C If the value of the ipRouteDest is 0.0.0.0 (a default route), then the mask value is also 0.0.0.0. It should be noted that all IP routing subsystems implicitly use this mechanism.

An alternate routing metric for this route. The semantics of this metric are determined by the routing-protocol specified in the route's ipRouteProto value. If this metric is not used, its value should be set to -1.

A reference to MIB definitions specific to the particular routing protocol which is responsible for this route, as determined by the value specified in the route's ipRouteProto value. 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.

The IP Address Translation table used for mapping from IP addresses to physical addresses.

Each entry contains one IpAddress to `physical' address equivalence.

The 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.

The media-dependent `physical' address.

The IpAddress corresponding to the media- dependent `physical' address.

The 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. Enumeration: 'static': 4, 'other': 1, 'dynamic': 3, 'invalid': 2.

The 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.

The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.

The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).

The number of ICMP Destination Unreachable messages received.

The number of ICMP Time Exceeded messages received.

The number of ICMP Parameter Problem messages received.

The number of ICMP Source Quench messages received.

The number of ICMP Redirect messages received.

The number of ICMP Echo (request) messages received.

The number of ICMP Echo Reply messages received.

The number of ICMP Timestamp (request) messages received.

The number of ICMP Timestamp Reply messages received.

The number of ICMP Address Mask Request messages received.

The number of ICMP Address Mask Reply messages received.

The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.

The 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.

The number of ICMP Destination Unreachable messages sent.

The number of ICMP Time Exceeded messages sent.

The number of ICMP Parameter Problem messages sent.

The number of ICMP Source Quench messages sent.

The number of ICMP Redirect messages sent. For a host, this object will always be zero, since hosts do not send redirects.

The number of ICMP Echo (request) messages sent.

The number of ICMP Echo Reply messages sent.

The number of ICMP Timestamp (request) messages sent.

The number of ICMP Timestamp Reply messages sent.

The number of ICMP Address Mask Request messages sent.

The number of ICMP Address Mask Reply messages sent.

The algorithm used to determine the timeout value used for retransmitting unacknowledged octets. Enumeration: 'vanj': 4, 'other': 1, 'constant': 2, 'rsre': 3.

The 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.

The 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.

The 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.

The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.

The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.

The 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.

The number of times TCP connections have made a direct transition to the CLOSED state from either the ESTABLISHED state or the CLOSE-WAIT state.

The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.

The total number of segments received, including those received in error. This count includes segments received on currently established connections.

The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.

The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.

A table containing TCP connection-specific information.

Information 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.

The state of this TCP connection. 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). Enumeration: 'synReceived': 4, 'established': 5, 'finWait2': 7, 'timeWait': 11, 'finWait1': 6, 'lastAck': 9, 'closeWait': 8, 'deleteTCB': 12, 'closed': 1, 'closing': 10, 'listen': 2, 'synSent': 3.

The 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.

The local port number for this TCP connection.

The remote IP address for this TCP connection.

The remote port number for this TCP connection.

The total number of segments received in error (e.g., bad TCP checksums).

The number of TCP segments sent containing the RST flag.

The total number of UDP datagrams delivered to UDP users.

The total number of received UDP datagrams for which there was no application at the destination port.

The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port.

The total number of UDP datagrams sent from this entity.

A table containing UDP listener information.

Information about a particular current UDP listener.

The 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.

The local port number for this UDP listener.

A text string that describes the trap being reported.

A list of serial interface entries.

A serial interface entry containing objects at the physical and session layer.

A unique value for each serial interface.

A textual string containing the name of the serial interface (ie. S0, W1, etc).

The type of physical serial interface, distinguished according to the physical/link protocol(s) being currently used on the interface. Enumeration: 'trueDigital': 5, 'isdnSync': 7, 'sync': 3, 'isdnV120': 6, 'other': 1, 'async': 2, 'isdn': 4.

Name of the active user. Blank if not active.

A unique Session Identifier which matches the RADIUS session ID. Blank when not using RADIUS.

The active type of service being provided by the serial interface. Enumeration: 'device': 3, 'login': 2, 'network': 1, 'twoway': 4.

The direction the active session was initiated. Enumeration: 'out': 2, 'inout': 3, 'in': 1.

The status of the serial interface. Enumeration: 'established': 3, 'noservice': 6, 'idle': 1, 'connecting': 2, 'command': 5, 'disconnecting': 4.

The amount of time this session has been active.

The amount of time this session has been idle.

An estimate of the serial interface's current inbound bandwidth in bits per second.

An estimate of the serial interface's current outbound bandwidth in bits per second.

A textual string containing the name of the True Digital modem being used by the serial interface.

The IP address associated with the serial interface. If being used as a network type port, this is the remote user's IP address. If being used as a device or login, this is the IP address of the host the user is connected to.

A textual string containing information about the network interface bound to the serial interface.

The total number of octets received on the serial interface.

The total number of octets transmitted on the serial interface.

The total number of octets queued on the serial interface.

The status of the modem being used by the serial interface. Enumeration: 'active': 4, 'test': 5, 'none': 1, 'connecting': 3, 'bound': 2.

The compression being used in the modem or by the serial interface. Enumeration: 'v42bis': 2, 'mnp5': 3, 'none': 1, 'stac': 4.

The error correcting protocol being used in the modem or by the serial interface. Enumeration: 'mnp': 3, 'none': 1, 'lapm': 2.

The number of retrains attempted by the modem attached to the serial interface.

The number of renegotiates attempted by the modem attached to the serial interface.

A list of T1/E1 interface entries.

A T1/E1 entry containing objects at the physical layer.

A unique value for each T1/E1 interface.

The type of interface (T1 or E1). Enumeration: 'e1': 2, 't1': 1.

The configured function of the interface. Enumeration: 'clear': 3, 'channelized': 2, 'isdn': 1, 'fractional': 4.

The current operational status of the interface. Enumeration: 'down': 2, 'up': 1, 'loopback': 3.

The configured line framing. Enumeration: 'esf': 1, 'd4': 2, 'crc4': 3, 'fas': 4.

The configured line signal encoding. Enumeration: 'ami': 1, 'hdb3': 3, 'b8zs': 2.

The configured voice modulation. Enumeration: 'ulaw': 1, 'alaw': 2.

The amount of time this interface has been up or down.

An estimate of the serial interface's current recieve signal level in DB.

The total number of Blue Alarms on the interface.

The total number of Yellow Alarms on the interface.

The total number of times the interface has lost carrier.

The total number of times the interface has lost frame synchronization.

The total number of bipolar violations detected on the interface.

The total number of frame level CRC errors detected on the interface.

The total number of frame synchronization errors detected on the interface.

A list of modem entries.

A modem entry containing objects at the session layer.

A unique value for each modem interface.

A textual string containing the name of the serial interface (ie. S0, S1, etc).

A current state of the modem. Enumeration: 'none': 1, 'halt': 8, 'admin': 9, 'ready': 7, 'bound': 2, 'down': 6, 'test': 5, 'connecting': 3, 'active': 4.

The error correcting protocol being used in the modem. Enumeration: 'none': 1, 'mnp': 3, 'bufferd': 4, 'direct': 5, 'lapm': 2, 'cellular': 6.

The compression being used in the modem interface. Enumeration: 'v42bis': 2, 'mnp5': 3, 'none': 1, 'stac': 4.

An estimate of the modem interface's current inbound bandwidth in bits per second.

An estimate of the modem interface's current outbound bandwidth in bits per second.

The total number of bytes received on the serial interface.

The total number of bytes transmitted on the serial interface.

The number of retrains attempted by the modem.

The number of renegotiates attempted by the modem.

The number of times a call received by the modem.

The number of analog calls received by the modem.

The number of successful calls received by the modem.

Call summary table containing the summary of calls on a per board basis. The rows in the table correspond to the slots and the columns specify the type of calls as V.90, V.34, ISDN etc. This object is not accessible, it is present for clarity purpose.

The entries in the call summary table. The max number of rows in this table is limited to the number of line cards. (Quad T1 or Tri E1). The slot ID will be used as an index into this table.

Board ID used as an index into the call summary table. The valid board IDs are the T1/E1 board/slot IDs which is 0 - 9.

Total calls specifies the capacity of this T1/E1 board.

Total calls specifies the current total of all ISDN calls handled by this T1/E1 board.

Total calls specifies the current total of all V.90/56KFlex/56K calls handled by this T1/E1 board.

Total calls specifies the current total of all V.34/33.6/28.8K calls handled by this T1/E1 board.

Total calls specifies the current total of all other type calls not handled by the other objects in this table.

Call summary table containing the summary of calls on a per line basis. The rows in the table correspond to the lines and the columns specify the type of calls as V.90, V.34, ISDN etc. This object is not accessible, it is present for clarity purpose.

The entries in the call summary table. The max number of rows in this table is limited to the number of lines. (Quad T1 or Tri E1). The line ID will be used as an index into this table.

Line ID used as an index into the call summary table. The valid line IDs are the T1/E1 lines which is 36 T1 or 27 E1.

Total calls specifies the sum total of all types of calls handled by this T1/E1 line.

Total calls specifies the sum total of all ISDN calls handled by this T1/E1 line.

Total calls specifies the sum total of all V.90/56KFlex/56K calls handled by this T1/E1 line.

Total calls specifies the sum total of all V.34/33.6/28.8K calls handled by this T1/E1 line.

Total calls specifies the sum total of all other type calls not handled by the other objects in this table.

This object specifies the total number of calls of all types on a per chassis basis.

This object specifies the total number of ISDN calls on a per chassis basis.

This object specifies the total number of V.90/K56Flex/56K calls on a per chassis basis.

This object specifies the total number of V.34/33.6/28.8K calls on a per chassis basis.

This object specifies the total number of other call types on a per chassis basis not specified by the above objects.

This object specifies the total number of sessions for this chassis basis.

Power supply failed trap. The variable bindings in the Trap packet provide information about the chassis name, power supply unit and the trap status. This Trap must be cleared manually.

Power supply restored trap. The variable bindings in the Trap packet provide information about the chassis name, power supply unit and the trap status. This Trap is issued when a failed power supply is restored. This must be cleared manually.

Fan failure trap. The variable bindings in the Trap packet provide information about the chassis name, fan number and the trap status. This Trap must be cleared manually.

Fan restored trap. The variable bindings in the Trap packet provide information about the chassis name, fan number and the trap status. This Trap is issued when the failed fan is restored. This trap must be cleared manually.

Board temperature warning trap. The variable bindings in the Trap packet provide information about the chassis name, unit and the trap status. This Trap is issued when the board temperature exceeds a set threshold value. This trap must be cleared manually.

Board trap. The variable bindings in the Trap packet provide information about the chassis name, board number and the trap status. This Trap must be cleared manually.

Modem failure trap. The variable bindings in the Trap packet provide information about the chassis name, modem number and the trap status. This Trap must be cleared manually.

T1/E1 Line trap. The variable bindings in the Trap packet provide all the information for the clients to display the Board ID, Line ID and the status of the line. This Trap could be generated when the line comes up or goes down once. It must be cleared manually.

This trap is issued when the power supply to the board is not enough. The variable bindings in the Trap packet provide information about the chassis name, board/board number and the trap status. This Trap must be cleared manually.

This trap is issued when the power supply to the board is not enough. The variable bindings in the Trap packet provide information about the chassis name, board/board number and the trap status. This Trap must be cleared manually.