MIB2

# IP Tab

> You can view the switch IP information by choosing Edit > IP . The following table describes the IP tab fields.

> Field | Description
> DefaultTTL | The default value inserted into the Time-To-Live field of the IP header of datagrams originated at this entry, whenever a TTL value is not supplied by the transport layer protocol. The default value is 16.
> Reasm Timeout | The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity. The default value is 5.

# IP Address Tab

> The IP Address tab displays the switch IP address information. The following table describes the IP Address tab fields.

> Field | Description
> Addr | The device IP address.
> Interface | The device unit number.
> NetMask | The subnet mask address.
> BcastAddr | The IP broadcast address used.
> ReasmMaxSize | The size of the largest IP datagram that this entity can reassemble from incoming IP fragmented datagrams received on this interface.

# ARP Tab

> The Address Resolution Protocol (ARP) tab displays the MAC addresses and the associated IP addresses for the switch. The following table describes the ARP tab fields.

> Field | Description
> Interface | The device unit number.
> MacAddress | The unique hardware address of the device.
> IpAddress | The Internet Protocol address of the device used to represent a point of attachment in a TCP/IP internetwork.
> Type | The type of mapping.

# IP Route

> The following table describes the IP Route tab fields.

> Field | Description
> Dest | 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.
> Interface | 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.
> NextHop | 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.)
> Type | 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 disassociates 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.
> Proto | 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.
> Age | 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.
> Mask | 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.
> Hops | 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.

# TCP

> The following table describes the TCP tab fields.

> Field | Description
> RtoAlgorithm | The algorithm used to determine the time out value used for retransmitting unacknowledged octets.
> RtoMin | 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.
> RtoMax | 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.
> MaxConn | 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.

# TCP Connections

> The following table describes the TCP Connections tab fields.

> Field | Description
> 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).
> LocalAddress | 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.
> LocalPort | The local port number for this TCP connection.

# UDP Listener

> Field | Description
> Address | 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.
> Port | The local port number for this UDP listener.

# Edit Interface

> Field | Description
> Name | The textual name of the interface.
> Index | 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.
> Type | The type of interface.
> Mtu | The size of the largest packet which can be sent/received on the interface, specified in octets.
> Speed | An estimate of the interface's current bandwidth in bits per second.
> PhysAddress | The interface's address at its protocol sub-layer. The interface's media-specific MIB must define the bit and byte ordering and format of the value contained by this object.
> AdminStatus | The desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).
> OperStatus | The current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state.
> LastChange | The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last reinitialization of the local network management subsystem, then this object contains a zero value.
> LinkTrap | Indicates whether linkUp/linkDown traps should be generated for this interface.

# Interface Tab

> The following table describes the Port Interface Tab fields.

> Field | Description
> ifInOctets | The total number of octets received on the interface, including framing characters.
> ifOutOctets | The total number of octets transmitted out of the interface, including framing characters.
> ifInUcastPkts | The number of packets delivered by this sublayer to a higher sublayer that were not addressed to a multicast or broadcast address at this sublayer.
> ifOutUcastPkts | The number of packets that higher-level protocols requested be transmitted that were not addressed to a multicast address at this sublayer. This total number includes those packets discarded or unsent.
> ifInNUcastPkts | The number of packets delivered by this sublayer to a higher (sub)layer, which were addressed to a multicast or broadcast address at this sublayer. This object is deprecated in favor of ifInMulticastPkts and ifInBroadcastPkts.
> ifOutNUcastPkts | The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast or broadcast address at this sublayer, including those that were discarded or not sent. This object is deprecated in favor of ifOutMulticastPkts and ifOutBroadcastPkts.
> InDiscards | The number of inbound packets that 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.
> OutDiscards | 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.
> InErrors | For packet-oriented interfaces, the number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. For character-oriented or fixed-length interfaces, the number of inbound transmission units that contained errors preventing them from being deliverable to a higher-layer protocol.
> OutErrors | For packet-oriented interfaces, the number of outbound packets that could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound transmission units that could not be transmitted because of errors.
> InUnknownProtos | For packet-oriented interfaces, the number of packets received via the interface that were discarded because of an unknown or unsupported protocol. For character-oriented or fixed-length interfaces that support protocol multiplexing, the number of transmission units received via the interface that were discarded because of an unknown or unsupported protocol. For any interface that does not support protocol multiplexing, this counter will always be 0.

# SNMP Tab

> The following table describes the SNMP Tab fields.

> Field | Description
> Inpkts | The total number of messages delivered to the SNMP from the transport service.
> Outpkts | The total number of SNMP messages passed from the SNMP protocol to the transport service.
> InTotalReqVars | The total number of MIB objects retrieved successfully by the SNMP protocol as the result of receiving valid SNMP Get-Request and Get-Next PDUs.
> InTotalSetVars | The total number of MIB objects altered successfully by the SNMP protocol as the result of receiving valid SNMP Set-Request PDUs.
> InGetRequests | The total number of SNMP Get-Request PDUs that have been accepted and processed by the SNMP protocol.
> InGetNexts | The total number of SNMP Get-Next PDUs accepted and processed by the SNMP protocol.
> InSetRequests | The total number of SNMP Set-Request PDUs accepted and processed by the SNMP protocol.
> InGetResponses | The total number of SNMP Get-Response PDUs accepted and processed by the SNMP protocol.
> OutTraps | The total number of SNMP Trap PDUs generated by the SNMP protocol.
> OutTooBigs | The total number of SNMP PDUs generated by the SNMP protocol for which the value of the error-status field is tooBig.
> OutNoSuchNames | The total number of SNMP PDUs generated by the SNMP protocol for which the value of the error-status field is noSuchName.
> OutBadValues | The total number of SNMP PDUs generated by the SNMP protocol for which the value of the error-status field is badValue.
> OutGenErrs | The total number of SNMP PDUs generated by the SNMP protocol for which the value of the error-status field is genErr.
> InBadVersions | The total number of SNMP messages delivered to the SNMP protocol for an unsupported SNMP version.
> InBadCommunityNames | The total number of SNMP messages delivered to the SNMP protocol that used an unknown SNMP community name.
> InBadCommunityUses | The total number of SNMP messages delivered to the SNMP protocol that represented an SNMP operation not allowed by the SNMP community named in the message.
> InASNParseErrs | The total number of ASN.1 or BER errors encountered by the SNMP protocol when decoding received SNMP messages.
> InTooBigs | The total number of SNMP PDUs delivered to the SNMP protocol for which the value of the error-status field is tooBig.
> InNoSuchNames | The total number of SNMP PDUs delivered to the SNMP protocol for which the value of the error-status field is noSuchName.
> InBadValues | The total number of SNMP PDUs delivered to the SNMP protocol for which the value of the error-status field is badValue.
> InReadOnlys | The total number of SNMP PDUs delivered to the SNMP protocol for which the value of the error-status field is readOnly. It is a protocol error to generate an SNMP PDU containing the value ôreadOnlyö in the error-status field. This object is provided to detect incorrect implementations of the SNMP.
> InGenErrs | The total number of SNMP PDUs delivered to the SNMP protocol for which the value of the error-status field is genErr.

# IP Tab

> The following table describes the IP Tab fields.

> Field | Description
> InReceives | The total number of input datagrams received from interfaces, including those received in error.
> InHdrErrors | 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.
> InAddrErrors | The number of input datagrams discarded because the IP address in the IP header destination field was not a valid address. This count includes invalid addresses (for example, 0.0.0.0) and addresses of unsupported Classes (for example, Class E). For addresses that are not IP gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
> ForwDatagrams | 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. For addresses that do not act as IP Gateways, this counter will include only those packets that were source-routed by way of this address and had successful source-route option processing.
> InUnknownProtos | The number of locally addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
> InDiscards | The number of input IP datagrams for which no problems were encountered to prevent their continued processing but that were discarded (for example, for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting reassembly.
> InDelivers | The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
> OutRequests | The total number of IP datagrams that 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.
> OutDiscards | The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but that were discarded (for example, for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
> OutNoRoutes | 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 that meet this no-route criterion. Note that this includes any datagrams a host cannot route because all of its default gateways are down.
> FragOKs | The number of IP datagrams that have been successfully fragmented at this entity.
> FragFails | The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, for example, because their DonÆt Fragment flag was set.
> FragCreates | The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
> ReasmReqds | The number of IP fragments received that needed to be reassembled at this entity.
> ReasmOKs | The number of IP datagrams successfully reassembled.
> ReasmFails | The number of failures detected by the IP reassembly algorithm (for whatever reason: timed out, errors, etc.). Note that this is not necessarily a count of discarded IP fragments because some algorithms (notably the algorithm in RFC 815) can lose track of the number of fragments by combining them as they are received.

# ICMP In Tab

> The following table describes the ICMP In Tab fields.

> Fields | Description
> SrcQuenchs | The number of ICMP Source Quench messages received.
> Redirects | The number of ICMP Redirect messages received.
> Echos | The number of ICMP Echo (request) messages received.
> EchoReps | The number of ICMP Echo Reply messages received.
> Timestamps | The number of ICMP Timestamp (request) messages received.
> TimestampReps | The number of ICMP Timestamp Reply messages received.
> AddrMasks | The number of ICMP Address Mask Request messages received.
> AddrMaskReps | The number of ICMP Address Mask Reply messages received.
> ParmProbs | The number of ICMP Parameter Problem messages received.
> DestUnreachs | The number of ICMP Destination Unreachable messages received.
> TimeExcds | The number of ICMP Time Exceeded messages received.

# ICMP Out Tab

> The following table describes the ICMP Out Tab fields.

> Field | Description
> SrcQuenchs | The number of ICMP Source Quench messages sent.
> Redirects | The number of ICMP Redirect messages received. For a host, this object will always be zero, because hosts do not send redirects.
> Echos | The number of ICMP Echo (request) messages sent.
> EchoReps | The number of ICMP Echo Reply messages sent.
> Timestamps | The number of ICMP Timestamp (request) messages sent.
> TimestampReps | The number of ICMP Timestamp Reply messages sent.
> AddrMasks | The number of ICMP Address Mask Request messages sent.
> AddrMaskReps | The number of ICMP Address Mask Reply messages sent.
> ParmProbs | The number of ICMP Parameter Problem messages sent.
> DestUnreachs | The number of ICMP Destination Unreachable messages sent.
> TimeExcds | The number of ICMP Time Exceeded messages sent.

# Graph TCP Traffic

> Field | Description
> InSegs | The total number of segments received, including those received in error. This count includes segments received on currently established connections.
> OutSegs | The total number of segments sent, including those on current connections but excluding those containing only retransmitted octets.
> RetransSegs | The total number of segments retransmitted - that is, the number of TCP segments transmitted containing one or more previously transmitted octets.
> ActiveOpens | The number of times TCP connections have made a direct transition to the SYN-SENT state from the CLOSED state.
> PassiveOpens | The number of times TCP connections have made a direct transition to the SYN-RCVD state from the LISTEN state.
> AttemptFails | 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.
> EstabResets | 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.
> CurrEstab | The number of TCP connections for which the current state is either ESTABLISHED or CLOSE- WAIT.
> InErrs | The total number of segments received in error (e.g., bad TCP checksums)
> OutRsts | The number of TCP segments sent containing the RST flag.

# Graph UDP Traffic

> Field | Description
> InDatagrams | The total number of UDP datagrams delivered to UDP users.
> OutDatagrams | The total number of UDP datagrams sent from this entity.