MRVINREACH: 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.

The number of EGP messages received without error.

The number of EGP messages received that proved to be in error.

The total number of locally generated EGP messages.

The number of locally generated EGP messages not sent due to resource limitations within an EGP entity.

The EGP neighbor table.

Information about this entity's relationship with a particular EGP neighbor.

The EGP state of the local system with respect to this entry's EGP neighbor. Each EGP state is represented by a value that is one greater than the numerical value associated with said state in RFC 904. Enumeration: 'down': 3, 'idle': 1, 'cease': 5, 'up': 4, 'acquisition': 2.

The IP address of this entry's EGP neighbor.

The autonomous system of this EGP peer. Zero should be specified if the autonomous system number of the neighbor is not yet known.

The number of EGP messages received without error from this EGP peer.

The number of EGP messages received from this EGP peer that proved to be in error (e.g., bad EGP checksum).

The number of locally generated EGP messages to this EGP peer.

The number of locally generated EGP messages not sent to this EGP peer due to resource limitations within an EGP entity.

The number of EGP-defined error messages received from this EGP peer.

The number of EGP-defined error messages sent to this EGP peer.

The number of EGP state transitions to the UP state with this EGP peer.

The number of EGP state transitions from the UP state to any other state with this EGP peer.

The interval between EGP Hello command retransmissions (in hundredths of a second). This represents the t1 timer as defined in RFC 904.

The interval between EGP poll command retransmissions (in hundredths of a second). This represents the t3 timer as defined in RFC 904.

The polling mode of this EGP entity, either passive or active. Enumeration: 'active': 1, 'passive': 2.

A control variable used to trigger operator- initiated Start and Stop events. When read, this variable always returns the most recent value that egpNeighEventTrigger was set to. If it has not been set since the last initialization of the network management subsystem on the node, it returns a value of `stop'. When set, this variable causes a Start or Stop event on the specified neighbor, as specified on pages 8-10 of RFC 904. Briefly, a Start event causes an Idle peer to begin neighbor acquisition and a non-Idle peer to reinitiate neighbor acquisition. A stop event causes a non-Idle peer to return to the Idle state until a Start event occurs, either via egpNeighEventTrigger or otherwise. Enumeration: 'start': 1, 'stop': 2.

The autonomous system number of this EGP entity.

A table containing PPP-link specific variables for this PPP implementation.

Management information about a particular PPP Link.

The value of ifIndex that identifies the lower-level interface over which this PPP Link is operating. This interface would usually be an HDLC or RS-232 type of interface. If there is no lower-layer interface element, or there is no ifEntry for the element, or the element can not be identified, then the value of this object is 0. For example, suppose that PPP is operating over a serial port. This would use two entries in the ifTable. The PPP could be running over `interface' number 123 and the serial port could be running over `interface' number 987. Therefore, ifSpecific.123 would contain the OBJECT IDENTIFIER ppp pppLinkStatusPhysicalIndex.123 would contain 987, and ifSpecific.987 would contain the OBJECT IDENTIFIER for the serial-port's media- specific MIB.

The number of packets received with an incorrect Address Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

The number of packets received on this link with an incorrect Control Field. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

The number of received packets that have been discarded because their length exceeded the MRU. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link. NOTE, packets which are longer than the MRU but which are successfully received and processed are NOT included in this count.

The number of received packets that have been discarded due to having an incorrect FCS. This counter is a component of the ifInErrors variable that is associated with the interface that represents this PPP Link.

The current value of the MRU for the local PPP Entity. This value is the MRU that the remote entity is using when sending packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

The current value of the MRU for the remote PPP Entity. This value is the MRU that the local entity is using when sending packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

The current value of the ACC Map used for sending packets from the local PPP entity to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

The ACC Map used by the remote PPP entity when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

Indicates whether the local PPP entity will use Protocol Compression when transmitting packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). Enumeration: 'disabled': 2, 'enabled': 1.

Indicates whether the remote PPP entity will use Protocol Compression when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). Enumeration: 'disabled': 2, 'enabled': 1.

Indicates whether the local PPP entity will use Address and Control Compression when transmitting packets to the remote PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). Enumeration: 'disabled': 2, 'enabled': 1.

Indicates whether the remote PPP entity will use Address and Control Compression when transmitting packets to the local PPP entity. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up). Enumeration: 'disabled': 2, 'enabled': 1.

The size of the Frame Check Sequence (FCS) in bits that the local node will generate when sending packets to the remote node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

The size of the Frame Check Sequence (FCS) in bits that the remote node will generate when sending packets to the local node. The value of this object is meaningful only when the link has reached the open state (ifOperStatus is up).

A table containing the LCP configuration parameters for this PPP Link. These variables represent the initial configuration of the PPP Link. The actual values of the parameters may be changed when the link is brought up via the LCP options negotiation mechanism.

Configuration information about a particular PPP Link.

The initial Maximum Receive Unit (MRU) that the local PPP entity will advertise to the remote entity. If the value of this variable is 0 then the local PPP entity will not advertise any MRU to the remote entity and the default MRU will be assumed. Changing this object will have effect when the link is next restarted. Agent variations: DESCRIPTION writing not supported

The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its receive side. In effect, this is the ACC Map that is required in order to ensure that the local modem will successfully receive all characters. The actual ACC map used on the receive side of the link will be a combination of the local node's pppLinkConfigReceiveACCMap and the remote node's pppLinkConfigTransmitACCMap. Changing this object will have effect when the link is next restarted.

The Asynchronous-Control-Character-Map (ACC) that the local PPP entity requires for use on its transmit side. In effect, this is the ACC Map that is required in order to ensure that all characters can be successfully transmitted through the local modem. The actual ACC map used on the transmit side of the link will be a combination of the local node's pppLinkConfigTransmitACCMap and the remote node's pppLinkConfigReceiveACCMap. Changing this object will have effect when the link is next restarted. Agent variations: DESCRIPTION writing not supported

If true(2) then the local node will attempt to perform Magic Number negotiation with the remote node. If false(1) then this negotiation is not performed. In any event, the local node will comply with any magic number negotiations attempted by the remote node, per the PPP specification. Changing this object will have effect when the link is next restarted. Agent variations: DESCRIPTION writing not supported Enumeration: 'true': 2, 'false': 1.

The size of the FCS, in bits, the local node will attempt to negotiate for use with the remote node. Regardless of the value of this object, the local node will comply with any FCS size negotiations initiated by the remote node, per the PPP specification. Changing this object will have effect when the link is next restarted. Agent variations: DESCRIPTION writing not supported

Table containing the IP parameters and statistics for the local PPP entity.

IPCP status information for a particular PPP link.

The operational status of the IP network protocol. If the value of this object is up then the finite state machine for the IP network protocol has reached the Opened state. Enumeration: 'opened': 1, 'not-opened': 2.

The IP compression protocol that the local PPP-IP entity uses when sending packets to the remote PPP-IP entity. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened). Enumeration: 'vj-tcp': 2, 'none': 1.

The IP compression protocol that the remote PPP-IP entity uses when sending packets to the local PPP-IP entity. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened). Enumeration: 'vj-tcp': 2, 'none': 1.

The Max-Slot-Id parameter that the remote node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).

The Max-Slot-Id parameter that the local node has advertised and that is in use on the link. If vj-tcp header compression is not in use on the link then the value of this object shall be 0. The value of this object is meaningful only when the link has reached the open state (pppIpOperStatus is opened).

Table containing configuration variables for the IPCP for the local PPP entity.

IPCP information for a particular PPP link.

The immediate desired status of the IP network protocol. Setting this object to open will inject an administrative open event into the IP network protocol's finite state machine. Setting this object to close will inject an administrative close event into the IP network protocol's finite state machine. Agent variations: DESCRIPTION writing not supported Enumeration: 'close': 2, 'open': 1.

If none(1) then the local node will not attempt to negotiate any IP Compression option. Otherwise, the local node will attempt to negotiate compression mode indicated by the enumerated value. Changing this object will have effect when the link is next restarted. Enumeration: 'vj-tcp': 2, 'none': 1.

The number of ports (regardless of their current state) in the RS-232-like general port table.

A list of port entries. The number of entries is given by the value of rs232Number.

Status and parameter values for a port.

A unique value for each port. Its value ranges between 1 and the value of rs232Number. By convention and if possible, hardware port numbers map directly to external connectors. The value for each port must remain constant at least from one re-initialization of the network management agent to the next.

The port's hardware type. Enumeration: 'v35': 5, 'other': 1, 'rs422': 3, 'rs232': 2, 'rs423': 4.

The number of input signals for the port in the input signal table (rs232PortInSigTable). The table contains entries only for those signals the software can detect.

The number of output signals for the port in the output signal table (rs232PortOutSigTable). The table contains entries only for those signals the software can assert.

The port's input speed in bits per second.

The port's output speed in bits per second.

A list of asynchronous port entries. The maximum entry number is given by the value of rs232Number. Entries need not exist for synchronous ports.

Status and parameter values for an asynchronous port.

A unique value for each port. Its value is the same as rs232PortIndex for the port.

The port's number of bits in a character.

The port's number of stop bits. Enumeration: 'dynamic': 4, 'two': 2, 'one-and-half': 3, 'one': 1.

The port's sense of a character parity bit. Enumeration: 'even': 3, 'none': 1, 'space': 5, 'odd': 2, 'mark': 4.

A control for the port's ability to automatically sense input speed. When rs232PortAutoBaud is 'enabled', a port may autobaud to values different from the set values for speed, parity, and character size. As a result a network management system may temporarily observe values different from what was previously set. Enumeration: 'disabled': 2, 'enabled': 1.

Total number of characters with a parity error, input from the port since system re-initialization and while the port state was 'up' or 'test'.

Total number of characters with a framing error, input from the port since system re-initialization and while the port state was 'up' or 'test'.

Total number of characters with an overrun error, input from the port since system re-initialization and while the port state was 'up' or 'test'.

A list of synchronous port entries. The maximum entry number is given by the value of rs232Number. Entries need not exist for asynchronous ports.

Status and parameter values for a synchronous port.

A unique value for each port. Its value is the same as rs232PortIndex for the port.

Source of the port's bit rate clock. 'split' means the tranmit clock is internal and the receive clock is external. Enumeration: 'internal': 1, 'external': 2, 'split': 3.

Total number of frames with an invalid frame check sequence, input from the port since system re-initialization and while the port state was 'up' or 'test'.

Total number of frames that failed to be transmitted on the port since system re-initialization and while the port state was 'up' or 'test' because data was not available to the transmitter in time.

Total number of frames that failed to be received on the port since system re-initialization and while the port state was 'up' or 'test' because the receiver did not accept the data in time.

Total number of frames that failed to be received or transmitted on the port due to loss of modem signals since system re-initialization and while the port state was 'up' or 'test'.

Number of frames aborted on the port due to receiving an abort sequence since system re-initialization and while the port state was 'up' or 'test'.

A list of port input control signal entries.

Input control signal status for a hardware port.

The value of rs232PortIndex for the port to which this entry belongs.

Identification of a hardware signal, as follows: rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector Enumeration: 'sq': 7, 'cts': 2, 'srts': 9, 'dcd': 6, 'dsr': 3, 'srs': 8, 'rts': 1, 'scts': 10, 'dtr': 4, 'sdcd': 11, 'ri': 5.

The current signal state. Enumeration: 'on': 2, 'none': 1, 'off': 3.

The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.

A list of port output control signal entries.

Output control signal status for a hardware port.

The value of rs232PortIndex for the port to which this entry belongs.

Identification of a hardware signal, as follows: rts Request to Send cts Clear to Send dsr Data Set Ready dtr Data Terminal Ready ri Ring Indicator dcd Received Line Signal Detector sq Signal Quality Detector srs Data Signaling Rate Selector srts Secondary Request to Send scts Secondary Clear to Send sdcd Secondary Received Line Signal Detector Enumeration: 'sq': 7, 'cts': 2, 'srts': 9, 'dcd': 6, 'dsr': 3, 'srs': 8, 'rts': 1, 'scts': 10, 'dtr': 4, 'sdcd': 11, 'ri': 5.

The current signal state. Enumeration: 'on': 2, 'none': 1, 'off': 3.

The number of times the signal has changed from 'on' to 'off' or from 'off' to 'on'.

The total number of Messages delivered to the SNMP entity from the transport service.

The total number of SNMP Messages which were passed from the SNMP protocol entity to the transport service.

The total number of SNMP Messages which were delivered to the SNMP protocol entity and were for an unsupported SNMP version.

The total number of SNMP Messages delivered to the SNMP protocol entity which used a SNMP community name not known to said entity.

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

The total number of ASN.1 or BER errors encountered by the SNMP protocol entity when decoding received SNMP Messages.

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

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

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

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

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

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

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

The total number of SNMP Get-Request PDUs which have been accepted and processed by the SNMP protocol entity.

The total number of SNMP Get-Next PDUs which have been accepted and processed by the SNMP protocol entity.

The total number of SNMP Set-Request PDUs which have been accepted and processed by the SNMP protocol entity.

The total number of SNMP Get-Response PDUs which have been accepted and processed by the SNMP protocol entity.

The total number of SNMP Trap PDUs which have been accepted and processed by the SNMP protocol entity.

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

The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status is `noSuchName'.

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

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

The total number of SNMP Get-Request PDUs which have been generated by the SNMP protocol entity.

The total number of SNMP Get-Next PDUs which have been generated by the SNMP protocol entity.

The total number of SNMP Set-Request PDUs which have been generated by the SNMP protocol entity.

The total number of SNMP Get-Response PDUs which have been generated by the SNMP protocol entity.

The total number of SNMP Trap PDUs which have been generated by the SNMP protocol entity.

Indicates 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. Enumeration: 'disabled': 2, 'enabled': 1.

The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be the numerically smallest MAC address of all ports that belong to this bridge. However it is only required to be unique. When concatenated with dot1dStpPriority a unique BridgeIdentifier is formed which is used in the Spanning Tree Protocol.

The number of ports controlled by this bridging entity.

Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging this will be indicated by entries in the port table for the given type. Enumeration: 'unknown': 1, 'transparent-only': 2, 'srt': 4, 'sourceroute-only': 3.

A table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.

A list of information for each port of the bridge.

The port number of the port for which this entry contains bridge management information.

The value of the instance of the ifIndex object, defined in MIB-II, for the interface corresponding to this port.

For a port which (potentially) has the same value of dot1dBasePortIfIndex as another port on the same bridge, this object contains the name of an object instance unique to this port. For example, in the case where multiple ports correspond one- to-one with multiple X.25 virtual circuits, this value might identify an (e.g., the first) object instance associated with the X.25 virtual circuit corresponding to this port. For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value { 0 0 }.

The number of frames discarded by this port due to excessive transit delay through the bridge. It is incremented by both transparent and source route bridges.

The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source route bridges.

An indication of what version of the Spanning Tree Protocol is being run. The value 'decLb100(2)' indicates the DEC LANbridge 100 Spanning Tree protocol. IEEE 802.1d implementations will return 'ieee8021d(3)'. If future versions of the IEEE Spanning Tree Protocol are released that are incompatible with the current version a new value will be defined. Enumeration: 'ieee8021d': 3, 'unknown': 1, 'decLb100': 2.

The value of the write-able portion of the Bridge ID, i.e., the first two octets of the (8 octet long) Bridge ID. The other (last) 6 octets of the Bridge ID are given by the value of dot1dBaseBridgeAddress.

The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity.

The total number of topology changes detected by this bridge since the management entity was last reset or initialized.

The bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol as executed by this node. This value is used as the Root Identifier parameter in all Configuration Bridge PDUs originated by this node.

The cost of the path to the root as seen from this bridge.

The port number of the port which offers the lowest cost path from this bridge to the root bridge.

The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded, in units of hundredths of a second. This is the actual value that this bridge is currently using.

The amount of time between the transmission of Configuration bridge PDUs by this node on any port when it is the root of the spanning tree or trying to become so, in units of hundredths of a second. This is the actual value that this bridge is currently using.

This time value determines the interval length during which no more than two Configuration bridge PDUs shall be transmitted by this node, in units of hundredths of a second.

This time value, measured in units of hundredths of a second, controls how fast a port changes its spanning state when moving towards the Forwarding state. The value determines how long the port stays in each of the Listening and Learning states, which precede the Forwarding state. This value is also used, when a topology change has been detected and is underway, to age all dynamic entries in the Forwarding Database. [Note that this value is the one that this bridge is currently using, in contrast to dot1dStpBridgeForwardDelay which is the value that this bridge and all others would start using if/when this bridge were to become the root.]

The value that all bridges use for MaxAge when this bridge is acting as the root. Note that 802.1D-1990 specifies that the range for this parameter is related to the value of dot1dStpBridgeHelloTime. The granularity of this timer is specified by 802.1D-1990 to be 1 second. An agent may return a badValue error if a set is attempted to a value which is not a whole number of seconds.

The value that all bridges use for HelloTime when this bridge is acting as the root. The granularity of this timer is specified by 802.1D- 1990 to be 1 second. An agent may return a badValue error if a set is attempted to a value which is not a whole number of seconds.

The value that all bridges use for ForwardDelay when this bridge is acting as the root. Note that 802.1D-1990 specifies that the range for this parameter is related to the value of dot1dStpBridgeMaxAge. The granularity of this timer is specified by 802.1D-1990 to be 1 second. An agent may return a badValue error if a set is attempted to a value which is not a whole number of seconds.

A table that contains port-specific information for the Spanning Tree Protocol.

A list of information maintained by every port about the Spanning Tree Protocol state for that port.

The port number of the port for which this entry contains Spanning Tree Protocol management information.

The value of the priority field which is contained in the first (in network byte order) octet of the (2 octet long) Port ID. The other octet of the Port ID is given by the value of dot1dStpPort.

The port's current state as defined by application of the Spanning Tree Protocol. This state controls what action a port takes on reception of a frame. If the bridge has detected a port that is malfunctioning it will place that port into the broken(6) state. For ports which are disabled (see dot1dStpPortEnable), this object will have a value of disabled(1). Enumeration: 'listening': 3, 'disabled': 1, 'broken': 6, 'learning': 4, 'forwarding': 5, 'blocking': 2.

The enabled/disabled status of the port. Enumeration: 'disabled': 2, 'enabled': 1.

The contribution of this port to the path cost of paths towards the spanning tree root which include this port. 802.1D-1990 recommends that the default value of this parameter be in inverse proportion to the speed of the attached LAN.

The unique Bridge Identifier of the Bridge recorded as the Root in the Configuration BPDUs transmitted by the Designated Bridge for the segment to which the port is attached.

The path cost of the Designated Port of the segment connected to this port. This value is compared to the Root Path Cost field in received bridge PDUs.

The Bridge Identifier of the bridge which this port considers to be the Designated Bridge for this port's segment.

The Port Identifier of the port on the Designated Bridge for this port's segment.

The number of times this port has transitioned from the Learning state to the Forwarding state.

The total number of Forwarding Database entries, which have been or would have been learnt, but have been discarded due to a lack of space to store them in the Forwarding Database. If this counter is increasing, it indicates that the Forwarding Database is regularly becoming full (a condition which has unpleasant performance effects on the subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has been occurring but is not persistent.

The timeout period in seconds for aging out dynamically learned forwarding information. 802.1D-1990 recommends a default of 300 seconds.

A table that contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.

Information about a specific unicast MAC address for which the bridge has some forwarding and/or filtering information.

A unicast MAC address for which the bridge has forwarding and/or filtering information.

Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1dTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the bridge does have some forwarding/filtering information about this address (e.g. in the dot1dStaticTable). Implementors are encouraged to assign the port value to this object whenever it is learned even for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).

The status of this entry. The meanings of the values are: other(1) : none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1dTpFdbAddress are being forwarded. invalid(2) : this entry is not longer valid (e.g., it was learned but has since aged-out), but has not yet been flushed from the table. learned(3) : the value of the corresponding instance of dot1dTpFdbPort was learned, and is being used. self(4) : the value of the corresponding instance of dot1dTpFdbAddress represents one of the bridge's addresses. The corresponding instance of dot1dTpFdbPort indicates which of the bridge's ports has this address. mgmt(5) : the value of the corresponding instance of dot1dTpFdbAddress is also the value of an existing instance of dot1dStaticAddress. Enumeration: 'learned': 3, 'other': 1, 'self': 4, 'invalid': 2, 'mgmt': 5.

A table that contains information about every port that is associated with this transparent bridge.

A list of information for each port of a transparent bridge.

The port number of the port for which this entry contains Transparent bridging management information.

The maximum size of the INFO (non-MAC) field that this port will receive or transmit.

The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.

The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function, including bridge management frames.

Count of valid frames received which were discarded (i.e., filtered) by the Forwarding Process.

A table containing filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from specific ports and containing specific destination addresses are allowed to be forwarded. The value of zero in this table as the port number from which frames with a specific destination address are received, is used to specify all ports for which there is no specific entry in this table for that particular destination address. Entries are valid for unicast and for group/broadcast addresses.

Filtering information configured into the bridge by (local or network) management specifying the set of ports to which frames received from a specific port and containing a specific destination address are allowed to be forwarded.

The destination MAC address in a frame to which this entry's filtering information applies. This object can take the value of a unicast address, a group address or the broadcast address.

Either the value '0', or the port number of the port from which a frame must be received in order for this entry's filtering information to apply. A value of zero indicates that this entry applies on all ports of the bridge for which there is no other applicable entry.

The set of ports to which frames received from a specific port and destined for a specific MAC address, are allowed to be forwarded. Each octet within the value of this object specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the bridge is represented by a single bit within the value of this object. If that bit has a value of '1' then that port is included in the set of ports; the port is not included if its bit has a value of '0'. (Note that the setting of the bit corresponding to the port from which a frame is received is irrelevant.) The default value of this object is a string of ones of appropriate length.

This object indicates the status of this entry. The default value is permanent(3). other(1) - this entry is currently in use but the conditions under which it will remain so are different from each of the following values. invalid(2) - writing this value to the object removes the corresponding entry. permanent(3) - this entry is currently in use and will remain so after the next reset of the bridge. deleteOnReset(4) - this entry is currently in use and will remain so until the next reset of the bridge. deleteOnTimeout(5) - this entry is currently in use and will remain so until it is aged out. Enumeration: 'permanent': 3, 'other': 1, 'deleteOnTimeout': 5, 'deleteOnReset': 4, 'invalid': 2.

Information about the parameters associated with all circuits currently known.

Parameters information about all circuits currently known.

A unique index value for each known circuit.

The line on which this circuit is active. This is the same as the IfIndex.

This value represents the circuit's Network Management operational state. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155. Enumeration: 'on': 1, 'cleared': 4, 'off': 2, 'service': 3.

This value represents the circuit's Network Management operational and service substate. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155. Enumeration: 'loading': 4, 'autoservice': 7, 'failed': 12, 'dumping': 5, 'synchronizing': 11, 'looping': 3, 'running': 13, 'reflecting': 2, 'autodumping': 9, 'autotriggering': 10, 'autoloading': 8, 'starting': 1, 'triggering': 6.

The name of the circuit entry in the table, for example, SVA-0 or in a level 2 router ASYNC-8 or ETHER-1).

This parameter represents the minimum number of seconds to wait before restarting the circuit. A value of 0 indicates not timer is running.

Represents the type of the circuit. For X.25 circuits, the value must be set to X25. For DDCMP and Ethernet circuits it is read only and is the same value as the protocol of the associated line. NOTE: Values 1 - 5 are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155. Enumeration: 'ddcmp-control': 2, 'ddcmp-dmc': 5, 'ddcmp-tributary': 3, 'ci': 7, 'bisync': 9, 'ddcmp-point': 1, 'other': 14, 'x25': 4, 'ethernet': 6, 'qp2-dte20': 8, 'fddi': 15.

This value indicates whether or not Network Management allows service operations on a circuit. The values for service-control are as follows: ENABLED SERVICE state and/or service functions are allowed. DISABLED SERVICE state and/or service functions are not allowed. NOTE: These values are incremented by one compared to the standard DECnet values in order to maintain compliance with RFC 1155. Enumeration: 'disabled': 2, 'enabled': 1.

This value represents the routing cost of the circuit. Routing sends messages along the path between two nodes having the smallest cost.

This value determines the frequency of Routing Hello messages sent to the adjacent node on the circuit.

Information about the counters associated with all circuits currently known.

Counter information about all circuits currently known

Number of seconds since the circuit counters for this circuit were last zeroed.

Number of terminating packets received on this circuit.

Number of originating packets sent on this circuit.

Number of terminating congestion losses on this circuit.

Number of corruption losses on this circuit.

Number of Transit packets received on this circuit.

Number of transit packets sent on this circuit.

Number of transit congestion losses on this circuit.

Number of circuit downs on this circuit.

Number of Initialization failures on this circuit.

This counter indicates the number of adjacency losses that result from any of the following: Node listener timeout Invalid data received at node listener Unexpected control (initialization or verification) message received Routing message received with a checksum error Node identification from a routing message or a Hello message that is not the one expected Hello message received indicating that connectivity became one-way Adjacency idled.

This counter indicates the maximum number of nodes that are up on the circuit.

Number of bytes received on this circuit.

Number of bytes sent on this circuit.

Number of data blocks received on this circuit.

Number of data blocks sent on this circuit.

Number of user buffer unavailable errors.

This parameter indicates the maximum number of originating packets that may be outstanding on this circuit. This does not include route-thru traffic.

When this value is set to 2, all of the counters in the Circuit Counter Table are set to zero. Enumeration: 'reset': 2, 'other': 1.

The number of entries in charPortTable, regardless of their current state.

A list of port entries. The number of entries is given by the value of charNumber.

Status and parameter values for a character port.

A unique value for each character port. Its value ranges between 1 and the value of charNumber. By convention and if possible, hardware port numbers come first, with a simple, direct mapping. The value for each port must remain constant at least from one re-initialization of the network management agent to the next.

An administratively assigned name for the port, typically with some local significance.

The port's type, 'physical' if the port represents an external hardware connector, 'virtual' if it does not. Enumeration: 'virtual': 2, 'physical': 1.

A reference to hardware MIB definitions specific to a physical port's external connector. For example, if the connector is RS-232, then the value of this object refers to a MIB sub-tree defining objects specific to RS-232. If an agent is not configured to have such values, the agent returns the object identifier: nullHardware OBJECT IDENTIFIER ::= { 0 0 }

A control to force the port into a clean, initial state, both hardware and software, disconnecting all the port's existing sessions. In response to a get-request or get-next-request, the agent always returns 'ready' as the value. Setting the value to 'execute' causes a reset. Enumeration: 'ready': 1, 'execute': 2.

The port's desired state, independent of flow control. 'enabled' indicates that the port is allowed to pass characters and form new sessions. 'disabled' indicates that the port is allowed to pass characters but not form new sessions. 'off' indicates that the port is not allowed to pass characters or have any sessions. 'maintenance' indicates a maintenance mode, exclusive of normal operation, such as running a test. Enumeration: 'disabled': 2, 'off': 3, 'enabled': 1, 'maintenance': 4.

The port's actual, operational state, independent of flow control. 'up' indicates able to function normally. 'down' indicates inability to function for administrative or operational reasons. 'maintenance' indicates a maintenance mode, exclusive of normal operation, such as running a test. 'absent' indicates that port hardware is not present. 'active' indicates up with a user present (e.g. logged in). Enumeration: 'down': 2, 'absent': 4, 'active': 5, 'up': 1, 'maintenance': 3.

The value of sysUpTime at the time the port 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.

The port's type of input flow control. 'none' indicates no flow control at this level or below. 'xonXoff' indicates software flow control by recognizing XON and XOFF characters. 'hardware' indicates flow control delegated to the lower level, for example a parallel port. 'ctsRts' and 'dsrDtr' are specific to RS-232-like ports. Although not architecturally pure, they are included here for simplicity's sake. Enumeration: 'hardware': 3, 'dsrDtr': 5, 'none': 1, 'ctsRts': 4, 'xonXoff': 2.

The port's type of output flow control. 'none' indicates no flow control at this level or below. 'xonXoff' indicates software flow control by recognizing XON and XOFF characters. 'hardware' indicates flow control delegated to the lower level, for example a parallel port. 'ctsRts' and 'dsrDtr' are specific to RS-232-like ports. Although not architecturally pure, they are included here for simplicy's sake. Enumeration: 'hardware': 3, 'dsrDtr': 5, 'none': 1, 'ctsRts': 4, 'xonXoff': 2.

The current operational state of input flow control on the port. 'none' indicates not applicable. 'unknown' indicates this level does not know. 'stop' indicates flow not allowed. 'go' indicates flow allowed. Enumeration: 'go': 4, 'unknown': 2, 'none': 1, 'stop': 3.

The current operational state of output flow control on the port. 'none' indicates not applicable. 'unknown' indicates this level does not know. 'stop' indicates flow not allowed. 'go' indicates flow allowed. Enumeration: 'go': 4, 'unknown': 2, 'none': 1, 'stop': 3.

Total number of characters detected as input from the port since system re-initialization and while the port operational state was 'up', 'active', or 'maintenance', including, for example, framing, flow control (i.e. XON and XOFF), each occurrence of a BREAK condition, locally-processed input, and input sent to all sessions.

Total number of characters detected as output to the port since system re-initialization and while the port operational state was 'up', 'active', or 'maintenance', including, for example, framing, flow control (i.e. XON and XOFF), each occurrence of a BREAK condition, locally-created output, and output received from all sessions.

The administratively allowed origin for establishing session on the port. 'dynamic' allows 'network' or 'local' session establishment. 'none' disallows session establishment. Enumeration: 'local': 3, 'none': 4, 'dynamic': 1, 'network': 2.

The maximum number of concurrent sessions allowed on the port. A value of -1 indicates no maximum. Setting the maximum to less than the current number of sessions has unspecified results.

The number of open sessions on the port that are in the connecting, connected, or disconnecting state.

The value of charSessIndex for the port's first or only active session. If the port has no active session, the agent returns the value zero.

A list of port session entries.

Status and parameter values for a character port session.

The value of charPortIndex for the port to which this session belongs.

The session index in the context of the port, a non-zero positive integer. Session indexes within a port need not be sequential. Session indexes may be reused for different ports. For example, port 1 and port 3 may both have a session 2 at the same time. Session indexes may have any valid integer value, with any meaning convenient to the agent implementation.

A control to terminate the session. In response to a get-request or get-next-request, the agent always returns 'ready' as the value. Setting the value to 'execute' causes termination. Enumeration: 'ready': 1, 'execute': 2.

The current operational state of the session, disregarding flow control. 'connected' indicates that character data could flow on the network side of session. 'connecting' indicates moving from nonexistent toward 'connected'. 'disconnecting' indicates moving from 'connected' or 'connecting' to nonexistent. Enumeration: 'connected': 2, 'connecting': 1, 'disconnecting': 3.

The network protocol over which the session is running. Other OBJECT IDENTIFIER values may be defined elsewhere, in association with specific protocols. However, this document assigns those of known interest as of this writing.

The session's source of establishment. Enumeration: 'unknown': 1, 'local': 3, 'network': 2.

This session's subset of charPortInCharacters.

This session's subset of charPortOutCharacters.

A reference to additional local MIB information. This should be the highest available related MIB, corresponding to charSessProtocol, such as Telnet. For example, the value for a TCP connection (in the absence of a Telnet MIB) is the object identifier of tcpConnState. If an agent is not configured to have such values, the agent returns the object identifier: nullConnectionId OBJECT IDENTIFIER ::= { 0 0 }

The value of sysUpTime in MIB-2 when the session entered connecting state.

The newRoot trap indicates that the sending agent has become the new root of the Spanning Tree; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer immediately subsequent to its election. Implementation of this trap is optional.

A topologyChange trap is sent by a bridge when any of its configured ports transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a newRoot trap is sent for the same transition. Implementation of this trap is optional.

An identification string for local and remote displays. Corresponds directly to SERVER IDENTIFICATION and the value labeled 'Identification:' on the SERVER CHARACTERISTICS display.

The system's operation with regard to DEFINE commands. 'permOnly' indicates that DEFINE commands modify only the permanent data base. 'operAndPerm' indicates that DEFINE commands modify both operational and permanent data bases, unless specifically documented to the contrary. Corresponds to SERVER CHANGE and the presence of the label CHANGE in the SERVER CHARACTERISTICS display. Enumeration: 'permOnly': 1, 'operAndPerm': 2.

The system's current local date and time. Corresponds directly to SERVER DATE and SERVER TIME and the value in various displays.

The adjustment to apply to a universal (Greenwich) time received when down-line loaded, comprising two octets. The first octet is the number of hours west of universal, the second is the number of minutes. Corresponds directly to SERVER TIMEZONE and the value labeled 'Timezone:' in the SERVER CHARACTERISTICS display.

The software file name to request for down-line load of the server. Corresponds directly to SERVER SOFTWARE, and the value labeled 'Software:' in the SERVER CHARACTERISTICS display.

Control for dumping the system's memory when the system crashes. Corresponds directly to SERVER DUMP and the presence of 'Dump' under the label 'Enabled Characteristics' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The password a management system must supply to force the system to reboot or use the system's remote console via the Maintenance Operation Protocol (MOP). Corresponds directly to SERVER MAINTENANCE PASSWORD. When setting this value, the management system must supply eight octets, filling with zeros from the first octet. That is, the value '1ab42' would be expressed as '0.0.0.0.0.1.ab.42'. Setting the value to zero disables the password check. When returning this value, the agent always returns a zero length OCTET STRING.

The system's local name. Corresponds directly to SERVER NAME and the value labeled 'Name:' in the SERVER CHARACTERISTICS display.

The software version variant running in the system. Corresponds to the letter in the software version in the SERVER CHARACTERISTICS display. alpha 'A': alpha test beta 'B': beta test production null: normal, production software special 'S': special, custom software Enumeration: 'alpha': 1, 'beta': 2, 'production': 3, 'special': 4.

The software version running in the system. In order, the octets contain major version, minor version, ECO, and pre-release number. Corresponds to the numbers in the software version in the SERVER CHARACTERISTICS display. For example, the version display for sysSoftwareVersionType 'production' and sysSoftwareVersion '2.2.0.0' is 'V2.2'. The version display for sysSoftwareVersionType 'beta' and sysSoftwareVersion '3.1.0.4' is 'V3.1B4'.

The firmware version of the bootstrap ROM installed in the system. Corresponds directly to the value labeled 'Rom' in the SERVER CHARACTERISTICS display.

The type of hardware on which the system is running. Corresponds directly to the value labeled 'Hardware Type:' in the UNIT display.

This version of hardware on which the system is running. Corresponds directly to part of the value labeled 'HW' in the SERVER CHARACTERISTICS display.

The type of chassis in which the system is running. Corresponds directly to part of the value labeled 'HW' in the SERVER CHARACTERISTICS display.

This version of chassis in which the system is running. Corresponds directly to part of the value labeled 'HW' in the SERVER CHARACTERISTICS display.

Control to cause this system to crash. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes an immediate crash. Corresponds to the CRASH command. Enumeration: 'ready': 1, 'execute': 2.

Control to cause this system to reset its software to initial load values, typically by reloading. When executing an initialize command, the system observes the value of sysInitializeDelay as supplied anywhere in the same set request with sysInitialize. If this value is not included in the set request, the system uses its default value. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'conditionalExecute' causes initialization if the overall system state is acceptible (such as not needing to store permanent parameters). Setting it to 'unconditionalExecute' causes initialization regardless of the overall system state. Setting it to 'cancel' aborts an initialization that has not yet started. According to standard SNMP operation, if the system is not in a proper state to accept a given set request for this value, it returns the standard SNMP error 'badValue'. Corresponds to the INITIALIZE command. Enumeration: 'ready': 1, 'unconditionalExecute': 3, 'cancel': 4, 'conditionalExecute': 2.

The number of minutes to delay before beginning the system initialization process as executed with sysInitialize. This value cannot be set outside a set-request that contains the value 'execute' for sysInitialize. If not included in such a set, the default value is 1. Corresponds to the INITIALIZE command's DELAY parameter and to the value labeled 'Minutes to shutdown:' in the SYSTEM STATUS display.

Control to zero all counters. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes all the system's counters to be zeroed. Corresponds to the ZERO ALL command. Enumeration: 'ready': 1, 'execute': 2.

Control to zero all base counters. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes all the system's base counters to be zeroed. Examples of counters that are zeroed are the SNMP counters or the counters from the SYSTEM COUNTERS display. Examples of counters that are not zeroed are Ethernet interface counters or port counters. Corresponds to the ZERO SYSTEM command. Enumeration: 'ready': 1, 'execute': 2.

The number hundredths of a second since the most recent zeroing of the base counters, such as through execution of sysZeroAll or sysZeroBase. Corresponds directly to the value labeled 'Seconds Since Zeroed:' in the SERVER COUNTERS display.

The name of the system that provided this system's running software. Corresponds directly to the value labeled 'Primary Host:' in the SERVER STATUS display.

The type of network address contained in sysLoaderAddress. 'unknown' means no address has been defined. 'other' means no other type value applies. 'local' means there is no address and this system's software was loaded from local storage. 'ip' is an Internet IP address. 'ethernet' is an 802.3 MAC address. Corresponds indirectly to the value labeled 'Load Address:' in the SERVER STATUS display.

The network address of the system that provided this system's running software. Corresponds directly to the value labeled 'Load Address:' in the SERVER STATUS display.

The type of network address contained in sysDumperAddress. 'unknown' means no address has been defined. 'other' means no other type value applies. 'local' means there is no address and this system's was dumped to local storage. 'ip' is an Internet IP address. 'ethernet' is an 802.3 MAC address. Corresponds indirectly to the value labeled 'Dump Address:' in the SERVER STATUS display.

The network address of the system that most recently accepted a crash dump from this system. Corresponds directly to the value labeled 'Dump Address:' in the SERVER STATUS display.

The number of times a local resource allocation failed, for example due to lack of dynamic memory. Corresponds directly to the value labeled 'Resource Errors:' in the SERVER STATUS display.

For chassis-based systems, the state of the overall chassis. 'notApplicable' indicates the system is not chassis based. 'noFault' indicates no current chassis problem. 'fault' indicates a current chassis problem such as a card or power supply failure. Corresponds directly to the value labeled 'Crate Current State: in the SERVER ALTERNATE STATUS display. Enumeration: 'notApplicable': 1, 'noFault': 2, 'loop': 4, 'fault': 3.

The number of times this system has seen sysChassisState switch from 'noFault' to 'fault' or from 'fault' to 'noFault'. Corresponds directly to the value labeled 'Crate Transition Count: in the SERVER ALTERNATE STATUS display.

The number of resource entries in the Resource table.

The number of feature entries in the Feature table.

A list of resource entries. The number of entries is given by the value of sysResourceNumber.

Status values for a system resource.

Identification of a resource type. Typically corresponds directly to a label such as 'Processes:' in the SERVER ALTERNATE STATUS display. Enumeration: 'process': 3, 'freeMemory': 8, 'ipxSapTable': 23, 'bridgeProtocolFilters': 30, 'appleFilterTable': 19, 'bridgeStaticFilters': 26, 'interfaces': 37, 'bridgeLearnedFilters': 28, 'packetBuffer': 5, 'cpuPercent': 1, 'repeaterRedundancyTable': 34, 'bridgeSourceFilters': 27, 'memoryPercent': 2, 'ipFragmentTable': 33, 'ipRouteTable': 41, 'ipFilterCache': 11, 'globalMemoryPercent': 9, 'packetHeaders': 36, 'packetCompressionTable': 32, 'phivDecnetRouteCache': 10, 'ipRouteCache': 12, 'ipcMessage': 6, 'appleRouteCache': 18, 'ipxRipFilterTable': 42, 'ipPolicyTable': 14, 'ipxSapFilterTable': 43, 'ipxRipTable': 22, 'repeaterPortAccessTable': 20, 'textPool': 7, 'latAnnouncementCompressionTable': 31, 'repeaterPortNameTable': 21, 'repeaterGlobalSecurityTable': 35, 'ipIgmpTable': 39, 'repeaterPortSecurityTable': 24, 'ipFilterTable': 15, 'bridgeInactiveFilters': 29, 'ipMulticastTable': 40, 'circuits': 38, 'ipxRouteCache': 13, 'timer': 4, 'bridgeFilterTable': 25, 'phivDecnetFilterTable': 17, 'phivDecnetPolicyTable': 16.

The number of resources currently in use on the system. Typically corresponds directly to a value labeled 'Cur' in the SERVER ALTERNATE STATUS display.

The highest or lowest value of resCurrent since system initialization. Typically corresponds directly to a value labeled 'High' or 'Low' in the SERVER ALTERNATE STATUS display.

The desired maximum possible number of resources in the system. In many cases, ACCESS to this object for a particular resType is read-only. Typically corresponds directly to a value labeled 'Max' in the SERVER ALTERNATE STATUS display for desired, administrative values. When the desired change takes effect is implementation specific, ranging from immediately to the next system initialization.

The number of times since system initialization that the system could not obtain the resource because none were available. Typically corresponds directly to a value labeled 'Failure' in the SERVER ALTERNATE STATUS display. If such failures do not apply to the particular resource, such as 'cpuPercent', the agent returns zero for this object.

The local system date and time when resLack last increased. Typically corresponds directly to a value labeled 'Last Occurred' in the SERVER ALTERNATE STATUS display. If such failures do not apply to the particular resource, such as 'cpuPercent', the agent returns all zeroes (unknown) for this object.

The current maximum possible number of resources in the system. Typically corresponds directly to a value labeled 'Max' in the SERVER ALTERNATE STATUS display for current operational values. This value is based on current or previous value of resAdminMaximum.

A list of feature entries. The number of entries is given by the value of sysFeatureNumber.

Status values for a system feature.

Identification of a feature type. Corresponds to a SERVER feature keyword. Enumeration: 'internetSecurity': 9, 'help': 1, 'changeEthernetAddress': 20, 'securID': 29, 'ppp': 23, 'frameRelay': 18, 'slip': 10, 'routeDaemon': 27, 'apd': 30, 'rwhoDaemon': 28, 'tl1': 39, 'eventLog': 8, 'men': 5, 'snmp': 2, 'ipxFiltering': 32, 'x25': 17, 'multisessions': 6, 'kerberos5': 34, 'arap': 25, 'xprinter': 16, 'enviromentalManager': 36, 'kerberos': 12, 'telnet': 13, 'ssh': 38, 'tn3270': 4, 'allPorts': 15, 'lat': 7, 'ipxRouting': 31, 'scriptServer': 11, 'rlogin': 14, 'ipMulticastSpecial': 19, 'unixCommands': 24, 'terminalServer': 37, 'expanded800': 21, 'fingerDaemon': 26, 'lpDaemon': 22, 'radius': 35, 'ipFiltering': 33, 'xremote': 3.

The status of the feature as of the next system initialization. Corresponds to the presence of the feature's lable following the label 'Enabled Feature(s): in the UNIT display. Enumeration: 'disabled': 1, 'locked': 3, 'enabled': 2.

The key a management system must supply to make a locked feature available. When unlocking a feature and the management system does not supply a value for featStatus, that object's value is implementation dependent. When returning this value, the agent always returns a zero length DisplayString.

The filename to request when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD FILE and the value labeled 'Internet Load File:' in the SERVER BOOT CHARACTERISTICS display.

The internet address of the server to use when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD HOST and the value labeled 'Internet Load Host:' in the SERVER BOOT CHARACTERISTICS display.

The internet address of the gateway to use when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD GATEWAY and the value labeled 'Internet Load Gateway:' in the SERVER BOOT CHARACTERISTICS display.

Control for loading via the combination of BOOTP and TFTP. Corresponds to SERVER LOAD PROTOCOL BOOTPTFTP and the presence of 'BOOTP/TFTP/' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via directed TFTP. Corresponds to SERVER LOAD PROTOCOL TFTPDIRECT and the presence of 'TFTPDIRECT' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading from a local medium. Corresponds to SERVER LOAD PROTOCOL LOCAL and the presence of 'LOCAL' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via DEC MOP. Corresponds to SERVER LOAD PROTOCOL MOP and the presence of 'MOP' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via MRV In-Reach-proprietary extended MOP. Corresponds to SERVER LOAD PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via the combination of RARP and TFTP. Corresponds to SERVER LOAD PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via the combination of BOOTP and TFTP. Corresponds to SERVER DUMP PROTOCOL BOOTPTFTP and the presence of 'BOOTP/TFTP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping to a local medium. Corresponds to SERVER DUMP PROTOCOL LOCAL and the presence of 'Local' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via DEC MOP. Corresponds to SERVER DUMP PROTOCOL MOP and the presence of 'MOP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via MRV In-Reach-proprietary extended MOP. Corresponds to SERVER DUMP PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via the combination of RARP and TFTP. Corresponds to SERVER DUMP PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via the combination of BOOTP and TFTP. Corresponds to SERVER PARAMETER PROTOCOL MOP and the presence of 'BOOTP/TFTP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters from a local medium. Corresponds to SERVER PARAMETER PROTOCOL LOCAL and the presence of 'LOCAL' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via DEC MOP. Corresponds to SERVER PARAMETER PROTOCOL MOP and the presence of 'MOP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via MRV In-Reach-proprietary extended MOP. Corresponds to SERVER PARAMETER PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via the combination of RARP and TFTP. Corresponds to SERVER PARAMETER PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The total number of bytes of main memory installed in the system. Corresponds directly to the value labeled 'Installed' on the SERVER ALTERNATE STATUS display. A value of 0 indicates standard memory for the particular hardware.

The temperature level of the system. 'unknown' indicates the system does not support a temperature sensor. 'normal' indicates a normal temperature level. 'high' indicates an excessive temperature level. Corresponds directly to the value labeled 'Temperature Level:' in the SERVER ALTERNATE STATUS display. Enumeration: 'high': 3, 'unknown': 1, 'normal': 2.

A list of boot control records.

Values for a boot record.

An index value that uniquely identifies a boot control record entry, from 1 to the number of entries for the system.

The filename to request when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD FILE and the value labeled 'Internet Load File:' in the SERVER BOOT CHARACTERISTICS display.

The internet address of the server to use when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD HOST and the value labeled 'Internet Load Host:' in the SERVER BOOT CHARACTERISTICS display.

The internet address of the gateway to use when loading an image via TFTP. Corresponds directly to SERVER INTERNET LOAD GATEWAY and the value labeled 'Internet Load Gateway:' in the SERVER BOOT CHARACTERISTICS display.

Control for loading via the combination of BOOTP and TFTP. Corresponds to SERVER LOAD PROTOCOL BOOTPTFTP and the presence of 'BOOTP/TFTP/' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via directed TFTP. Corresponds to SERVER LOAD PROTOCOL TFTPDIRECT and the presence of 'TFTPDIRECT' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading from a local medium. Corresponds to SERVER LOAD PROTOCOL LOCAL and the presence of 'LOCAL' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via DEC MOP. Corresponds to SERVER LOAD PROTOCOL MOP and the presence of 'MOP' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via MRV In-Reach-proprietary extended MOP. Corresponds to SERVER LOAD PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading via the combination of RARP and TFTP. Corresponds to SERVER LOAD PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Load Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via the combination of BOOTP and TFTP. Corresponds to SERVER DUMP PROTOCOL BOOTPTFTP and the presence of 'BOOTP/TFTP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping to a local medium. Corresponds to SERVER DUMP PROTOCOL LOCAL and the presence of 'Local' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via DEC MOP. Corresponds to SERVER DUMP PROTOCOL MOP and the presence of 'MOP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via MRV In-Reach-proprietary extended MOP. Corresponds to SERVER DUMP PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for dumping via the combination of RARP and TFTP. Corresponds to SERVER DUMP PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Dump Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via the combination of BOOTP and TFTP. Corresponds to SERVER PARAMETER PROTOCOL MOP and the presence of 'BOOTP/TFTP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters from a local medium. Corresponds to SERVER PARAMETER PROTOCOL LOCAL and the presence of 'LOCAL' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via DEC MOP. Corresponds to SERVER PARAMETER PROTOCOL MOP and the presence of 'MOP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via MRV In-Reach proprietary extended MOP. Corresponds to SERVER PARAMETER PROTOCOL PROPRIETARY and the presence of 'Proprietary' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for loading parameters via the combination of RARP and TFTP. Corresponds to SERVER PARAMETER PROTOCOL RARPTFTP and the presence of 'RARP/TFTP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The status of the entry. Set to 'disabled' to disable the entry. Enumeration: 'disabled': 1, 'enabled': 2.

The software file name to request for down-line load of the server via MOP or XMOP.

The internet address of the system is to use for itself when loading via TFTP. The value 0.0.0.0 indicates default action.

Control for loading parameters via the protocol DTFTP. Corresponds to SERVER PARAMETER PROTOCOL DTFTP and the presence of 'DTFTP' following the label 'Parameter Protocols Enabled:' in the SERVER BOOT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The character separating the load file directory name from the file name.

The most recent error the agent encountered in attempting to satisfy an SNMP request. Reading this value has the side effect of resetting it to 'noError'. Enumeration: 'badCommunity': 7, 'noSuchName': 3, 'badVersion': 8, 'readOnly': 5, 'noError': 1, 'badClient': 10, 'badValue': 4, 'genErr': 6, 'tooBig': 2, 'badType': 9.

Control for sending of the MOP RCP system identifier message. Corresponds directly to the presence of 'RCP Multicast' under the label 'Enabled Characteristics' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The address of the time server, either an IpAddr or an ethernet address.

The address of a configured time server (, either an IpAddr or an ethernet address).

Control whether the sysTimeServerConfiguredAddress is the only time server used to obtain the time (REQUIRED), the first time server used to obtain the time (ENABLED), or not used to obtain the time (DISABLED). Enumeration: 'disabled': 1, 'required': 3, 'enabled': 2.

Control to override the internally defined Internet address with that obtained from the bootp loading protocol. Enumeration: 'disabled': 2, 'enabled': 1.

Control to display load status messages during reboot. Corresponds directly to the value labeled 'Status Message:' in the SERVER LOADDUMP display. Enumeration: 'disabled': 2, 'enabled': 1.

Control to use default parameters upon the next reboot after which time this control reverts to disabled. This control only applies to stand-alone devices. Corresponds directly to the value labeled 'Default Parameters:' in the SERVER LOADDUMP display. Enumeration: 'disabled': 2, 'enabled': 1.

Indicates the type of authentication failure which last occurred. Enumeration: 'pap': 3, 'none': 1, 'privilegedPassword': 8, 'kerberos': 5, 'securId': 6, 'limitedPrivilegedPassword': 9, 'chap': 4, 'radius': 7, 'loginPassword': 2.

An identification string for the circuit or port where an authentication failure last occurred.

Control to allow script serving for this system from a script residing in a local flash card. Enumeration: 'disabled': 1, 'enabled': 2.

Indicates whether per port authentication is in use. This includes username, password, privilege level, and list of power outlets controlled by that user, or console connections allowed from that port. Enumeration: 'disabled': 1, 'enabled': 2.

Displays the product name of this system.

Indicates whether this system has a built-in modem. Enumeration: 'noModem': 1, 'modem': 2.

A control for toggling the cause action feature. Corresponds directly to the presence of 'Trigger/Action' under the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. The desired change will not take effect until the next system initialization. Enumeration: 'disabled': 1, 'enabled': 2.

A control for bring the web server up or down. Corresponds directly to the presence of 'Web Server' under the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The source identifier (SID) is the server name used by TL1 to identify the server.

Control to begin the system initialization process providing that at least one parameter server is current. Corresponds directly to the INITIALIZE DELAY PARAMETER command. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Enumeration: 'ready': 1, 'execute': 2.

Indicates whether the SNTP protocol is used to obtain the time at startup. If disabled, the older TIMED protocol is used. Both protocols run over UDP. Enumeration: 'disabled': 1, 'enabled': 2.

Indicates whether the unit will broadcast for the time at startup. Enumeration: 'disabled': 1, 'enabled': 2.

Control for automatic, periodic announcement of local services to the network. Corresponds directly to SERVER ANNOUNCEMENTS and the presence of the label 'Announcements' following the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Number of milleseconds to collect port input data before sending it to the host. Corresponds directly to SERVER CIRCUIT TIMER and the value labeled 'Circuit Timer:' in the SERVER CHARACTERISTICS display.

Maximum number of characters to store in the instances of latVisibleServiceIdentification. Corresponds directly to SERVER IDENTIFICATION SIZE and the value labeled 'Identification Size:' in the SERVER CHARACTERISTICS display.

Number of seconds of inactivity before sending a null message to the host. Corresponds directly to SERVER KEEPALIVE TIMER and the value labeled 'Keepalive Timer:' in the SERVER CHARACTERISTICS display.

Number of seconds between transmission of local service announcements. Corresponds directly to SERVER MULTICAST TIMER and the value labeled 'Multicast Timer:' in the SERVER CHARACTERISTICS display.

Maximum number of service nodes to keep in the node table. Corresponds directly to SERVER NODE LIMIT and the value labeled 'Node Limit:' in the SERVER CHARACTERISTICS display.

An arbitrary number assigned and used for administrative purposes. Corresponds directly to SERVER NUMBER and the value labeled 'Number:' in the SERVER CHARACTERISTICS display.

Maximum number of times to retransmit an unacknowledged message. Corresponds directly to SERVER RETRANSMIT LIMIT and the value labeled 'Retransmit Limit:' in the SERVER CHARACTERISTICS display.

The list of group numbers allowed to use local services, where a group number is in the range 0-255. The OCTET STRING contains a bitmap, with one bit for each group. Corresponding bit numbers start with 0 as the high-order bit of the first octet. Corresponds directly to SERVER SERVICE GROUPS and the value labeled 'Service Groups:' in the SERVER CHARACTERISTICS display.

Control for automatic deletion of all node table entries when latServiceGroups or latPortCurrentGroups is changed. Corresponds directly to SERVER PURGE GROUP and the presence of the label 'Purge Group' following the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for automatic deletion of all node table entries with status 'reachable' when the number of entries exceeds latNodeLimit. Corresponds directly to SERVER PURGE NODE and the presence of the label 'Purge Node' following the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Number of nodes not added to the node table because there was no room. Corresponds directly to the value labeled 'Discarded Nodes:' in the SERVER STATUS display.

Number of LAT messages received. Corresponds directly to the value labeled 'Messages Received:' in the SERVER COUNTERS display.

Number of LAT messages sent. Corresponds directly to the value labeled 'Messages Transmitted:' in the SERVER COUNTERS display.

Number of incoming LAT session connection attempts accepted. Corresponds directly to the value labeled 'Solicitations Accepted:' in the SERVER COUNTERS display.

Number of incoming LAT session connection attempts rejected. Corresponds directly to the value labeled 'Solicitations Rejected:' in the SERVER COUNTERS display.

Number of times a service announcement contained a node name already in the visible service table but with a different address. Corresponds directly to the value labeled 'Multiple Node Addresses:' in the SERVER COUNTERS display.

Number of duplicate LAT messages received. Corresponds directly to the value labeled 'Duplicates Received:' in the SERVER COUNTERS display.

Number of LAT messages retransmitted due to no acknowledgement. Corresponds directly to the value labeled 'Messages Re-transmitted:' in the SERVER COUNTERS display.

Number of LAT messages received with invalid format. Corresponds directly to the value labeled 'Illegal Messages Rcv'd:' in the SERVER COUNTERS display.

Number of LAT messages received with invalid slot format. Corresponds directly to the value labeled 'Illegal Slots Rcv'd:' in the SERVER COUNTERS display.

Number of multicast LAT messages received with invalid format. Corresponds directly to the value labeled 'Illegal Multicasts Rcv'd:' in the SERVER COUNTERS display.

A list of LAT character port entries.

LAT parameter values for a port.

An index value that uniquely identifies a port. The port identified by a particular value of this index is the same port as identified by charPortIndex in the Character MIB [11].

The list of group numbers to which the port is allowed to set access, where a group number is in the range 0-255. The OCTET STRING contains a bitmap, with one bit for each group. Corresponding bit numbers start with 0 as the high-order bit of the first octet. Corresponds directly to PORT AUTHORIZED GROUPS and the value labeled 'Authorized Groups:' in the PORT CHARACTERISTICS display.

Control for automatic stimulation of a host prompt upon forming a new session. Corresponds directly to PORT AUTOPROMPT and the presence of the label 'Autoprompt' following the label 'Enabled Characteristics:' in the PORT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The list of group numbers to which the port currently has set access, where a group number is in the range 0-255. The OCTET STRING contains a bitmap, with one bit for each group. Corresponding bit numbers start with 0 as the high-order bit of the first octet. Corresponds directly to PORT GROUPS and the value labeled 'Groups:' in the PORT CHARACTERISTICS display.

Control to allow the remote system to modify certain physical port characteristics. Corresponds directly to PORT REMOTE MODIFICATION and the presence of the label 'Remote Modification' following the label 'Enabled Characteristics:' in the PORT CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

A list of offered service entries.

Parameter values for an offered service entry.

The name of an offered service. Corresponds directly to the name in a SERVICE command and the value labeled 'Service:' in the SERVICE CHARACTERISTICS display.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the CLEAR SERVICE command. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

Control for allowing incoming connections to the service. Corresponds directly to SERVICE CONNECTIONS and the presence of the label 'Connections' following the label 'Enabled Characteristics:' in the SERVICE CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Text to identify a service. Corresponds directly to SERVICE IDENTIFICATION and the value labeled 'Identification:' in the SERVICE CHARACTERISTICS display.

The password a user must supply to use the service. Corresponds directly to SERVICE PASSWORD and the presence of the label 'Password' following the label 'Enabled Characteristics:' in the SERVICE CHARACTERISTICS display. When setting this value, the management system must supply eight octets, filling with zeros from the first octet. That is, the value '1ab42' would be expressed as '0.0.0.0.0.1.ab.42'. Setting the value to zero disables the password check. When returning this value, the agent always returns a zero length OCTET STRING.

The list of character ports offer the service. The OCTET STRING contains a bitmap, with one bit for each port, and enough octets for all the ports on the system. Port numbers are as defined for charPortIndex in the Character MIB [11]. Corresponding bit numbers start with 1 as the high-order bit of the first octet. Corresponds directly to port-list portion of SERVICE PORTS and the value labeled 'Ports:' in the SERVICE CHARACTERISTICS display.

Control for allowing queuing of incoming connections to the service when the service is busy. Corresponds directly to SERVICE QUEUE and the presence of the label 'Queuing' following the label 'Enabled Characteristics:' in the SERVICE CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control indicating whether Environmental Management services are offered. Enumeration: 'disabled': 2, 'enabled': 1.

A list of visible service entries.

Parameter values for a visible service entry.

The name of a visible service. Corresponds directly to the name in a SERVICE command and the value labeled 'Service Name' in the SERVICE SUMMARY display.

Status of communication with the service. Corresponds directly to the value labeled 'Status' in the SERVICE SUMMARY display. Enumeration: 'available': 1, 'unavailable': 2, 'unknown': 3, 'connected': 6, 'unreachable': 4, 'reachable': 5.

Name of a node offering the service. Corresponds directly to the value labeled Node Name in the SERVICE STATUS display.

Number of connected sessions to the service. Corresponds directly to the number with the value 'Connected', labeled 'Status' in the SERVICE SUMMARY display.

Text to identify a service. The length is subject to limitation by latIdentificationLengthLimit. Corresponds directly to the value labeled 'Identification:' in the SERVICE SUMMARY display.

Relative capacity of the service to accept additional sessions. Corresponds directly to value labeled Rating in the SERVICE STATUS display.

A list of node entries.

Parameter values for a node entry.

The name of a node. Corresponds directly to the value labeled 'Node:' in the NODE STATUS display.

Status of communication with the node. Corresponds directly to the value labeled 'Status' in the NODE STATUS display. Enumeration: 'available': 1, 'unavailable': 2, 'unknown': 3, 'connected': 6, 'unreachable': 4, 'reachable': 5.

Number of connected sessions to the node. Corresponds directly to the number with the value 'Connected', labeled 'Status' in the NODE STATUS display.

Ethernet address of the node. Corresponds directly to the value labeled 'Address:' in the NODE STATUS display.

Maximum Ethernet frame used by the node. Corresponds directly to the value labeled 'Data Link Frame Size:' in the NODE STATUS display.

Text that identifies the node. The size is subject to limitation by latIdentificationLengtLimit. Corresponds directly to the value labeled 'Identification' in the NODE STATUS display.

The list of group numbers to which the node belongs, where a group number is in the range 0-255. The OCTET STRING contains a bitmap, with one bit for each group. Corresponding bit numbers start with 0 as the high-order bit of the first octet. Corresponds directly to the value labeled 'Node Groups:' in the NODE STATUS display.

Number of entries for the node in the node service table. Corresponds indirectly to the list of services in the NODE STATUS display.

Control to zero counters kept for the node. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes all the system's counters to be zeroed. Corresponds to the ZERO NODE command. Enumeration: 'ready': 1, 'execute': 2.

The number of hundredths of a second since the most recent zeroing of the counters kept for the node, such as through execution of sysZeroAll or latNodeZero. Corresponds directly to the value labeled 'Seconds Since Zeroed:' in the NODE COUNTERS display.

The number of LAT messages received from the node. Corresponds directly to the value labeled 'Messages Received:' in the NODE COUNTERS display.

The number of LAT messages sent to the node. Corresponds directly to the value labeled 'Messages Transmitted:' in the NODE COUNTERS display.

The number of LAT slots received from the node. Corresponds directly to the value labeled 'Slots Received:' in the NODE COUNTERS display.

The number of LAT slots sent to the node. Corresponds directly to the value labeled 'Slots Transmitted:' in the NODE COUNTERS display.

The total number of bytes received from the node, including Ethernet overhead. Corresponds directly to the value labeled 'Bytes Received:' in the NODE COUNTERS display.

The total number of bytes sent to the node, including Ethernet overhead. Corresponds directly to the value labeled 'Bytes Transmitted:' in the NODE COUNTERS display.

The number of times a LAT message multicast by the node had a different Ethernet address from the previous time. Corresponds directly to the value labeled 'Multiple Node Addresses:' in the NODE COUNTERS display.

The number of duplicate LAT message received from the node. Corresponds directly to the value labeled 'Duplicates Received:' in the NODE COUNTERS display.

The number of LAT message retransmitted to the node due to lack of acknowledgement. Corresponds directly to the value labeled 'Messages Re-transmitted:' in the NODE COUNTERS display.

The number of LAT message received from the node with invalid format. Corresponds directly to the value labeled 'Illegal Messages Received:' in the NODE COUNTERS display.

The number of LAT slots received from the node with invalid format. Corresponds directly to the value labeled 'Illegal Slots Received:' in the NODE COUNTERS display.

The number of LAT session connection attempts received from the node and accepted. Corresponds directly to the value labeled 'Solicitations Accepted:' in the NODE COUNTERS display.

The number of LAT session connection attempts received from the node and rejected. Corresponds directly to the value labeled 'Solicitations Rejected:' in the NODE COUNTERS display.

Control for multicast solicitation of LAT services. Corresponds directly to SERVER LAT SOLICITAIONS and the presence of the label 'LAT SOLICITATIONS' following the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for LAT to provide an immediate ACK, and not to wait for the timer to expire. Corresponds directly to SERVER LAT IMMEDIATE ACK and the presence of the label 'LAT Immediate Ack following the label 'Enabled Characteristics:' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Maximum allowed number of kilobytes for recording events. Corresponds directly to MANAGER LOG FILE SIZE and the value labeled 'Log File Size:' in the MANAGER CHARACTERISTICS display.

Maximum allowed number of simultaneous service dialogs. Corresponds directly to MANAGER SIMULTANEOUS and the value labeled 'Maximum simultaneous requests:' in the MANAGER CHARACTERISTICS display.

Number of active service dialogs. Corresponds indirectly to the list of active clients in the MANAGER STATUS display.

Number of defined clients. Corresponds indirectly to the list of defined clients in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.

Total number of service offers sent in response to client requests. Corresponds directly to the value labeled 'Total service offers sent:' in the MANAGER STATUS display.

Total number of events that have been written to the event log since it was last purged. This may be less than the number currently in the log. Corresponds directly to the value labeled 'Total Messages Logged:' in the MANAGER EVENTS display.

Control to cause emptying the event log. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the event log to immediately become empty. Corresponds directly to the PURGE MANAGER LOG FILE command. Enumeration: 'ready': 1, 'execute': 2.

A list of active client dialog entries. The number of entries is given by basicActiveNumber.

Parameter values for an active client dialog entry.

The type of identification value in activeIdentification. Corresponds indirectly to the value labeled 'EthernetAddress' in the MANAGER STATUS display.

Identification of the active partner. Corresponds directly to the value labeled 'EthernetAddress' in the MANAGER STATUS display.

The function the server is performing with the partner. Corresponds directly to the value labeled 'Function' in the MANAGER STATUS display. Enumeration: 'load': 2, 'dump': 3, 'parameterStore': 1, 'imageUpdate': 4.

If activeFunction is 'load', the software version being sent to the client, otherwise 'notApplicable'. Corresponds to the letter in the software version labeled 'Version' in the MANAGER STATUS display. alpha 'A': alpha test beta 'B': beta test production null: normal, production software special 'S': special, custom software diagnostic 'D': diagnostic, debug software Enumeration: 'diagnostic': 5, 'notApplicable': 6, 'beta': 2, 'production': 3, 'alpha': 1, 'special': 4.

If activeFunction is 'load', the 4-byte software version being sent to the client, otherwise zero length. In order, the octets contain major version, minor version, ECO, and pre-release number. Corresponds to the numbers in the software version labeled 'Version' in the MANAGER STATUS display. For example, the version display for activeSoftwareVersionType 'production' and activeSoftwareVersion '2.2.0.0' is 'V2.2'. The version display for activeSoftwareVersionType 'beta' and activeSoftwareVersion '3.1.0.4' is 'V3.1B4'.

If activeFunction is 'parameterStore', the parameter version being stored by the client, otherwise zero. Corresponds directly to the value labeled 'Version' in the MANAGER STATUS display.

The current dialog sequence number. Corresponds directly to the value labeled 'Seq' in the MANAGER STATUS display.

The number of bytes remaining to be transferred in the dialog. Corresponds directly to the value labeled 'Left' in the MANAGER STATUS display.

The name of the file being used in the dialog. Corresponds directly to the value labeled 'File' in the MANAGER STATUS display.

The final status of the most recent attempt to get an image. Corresponds directly to the value labeled 'Get Status:' in the DEVICE STATUS display.

The dynamic state of an active attempt to get an image. Corresponds directly to the value labeled 'Get State:' in the DEVICE STATUS display. Enumeration: 'openFile': 5, 'closePartner': 8, 'internal1': 2, 'internal2': 3, 'writeFile': 7, 'idle': 1, 'cleanup': 10, 'done': 11, 'receivePartner': 6, 'error': 12, 'openPartner': 4, 'closeFile': 9.

A list of client data base entries. The number of entries is given by basicClientNumber.

Parameter values for a client data base entry.

The type of identification value in clientIdentification. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.

Identification of the client, either a hardware type or an Ethernet address, depending on clientIdentificationType. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the PURGE LOCAL, PURGE GLOBAL, and PURGE NODE commands. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

A name that may be used to identify the client. Corresponds directly to the value labeled 'Name' in the MANAGER NODE display.

The file with the client's load image. Corresponds directly to the value labeled 'Load File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.

The file with the client's diagnostic test image. Corresponds directly to the value labeled 'Diag File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.

Control for allowing load service for the client. Corresponds directly to the value labeled 'Load' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays. Enumeration: 'disabled': 1, 'enabled': 2.

Control for allowing dump service for the client. Corresponds directly to the value labeled 'Dump' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays. Enumeration: 'disabled': 1, 'enabled': 2.

A list of named client data base entries. The number of entries is given by basicClientNumber.

Parameter values for a named client data base entry.

The type of identification value in namedIdentification. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.

Identification of the client, either a hardware type or an Ethernet address, depending on namedIdentificationType. Corresponds directly to MANAGER NODE, MANAGER GLOBAL, and MANAGER LOCAL, and the value labeled 'Ethernet Address' in the MANAGER NODE display or 'Ethernet Address', 'Device', and 'Global Devices' or 'Local Devices' in the MANAGER GLOBAL and LOCAL displays.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the PURGE LOCAL, PURGE GLOBAL, and PURGE NODE commands. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

A name that may be used to identify the client. Corresponds directly to the value labeled 'Name' in the MANAGER NODE display.

The file with the client's load image. Corresponds directly to the value labeled 'Load File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.

The file with the client's diagnostic test image. Corresponds directly to the value labeled 'Diag File' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays.

Control for allowing load service for the client. Corresponds directly to the value labeled 'Load' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays. Enumeration: 'disabled': 1, 'enabled': 2.

Control for allowing dump service for the client. Corresponds directly to the value labeled 'Dump' in the MANAGER LOCAL, MANAGER GLOBAL, and MANAGER NODE displays. Enumeration: 'disabled': 1, 'enabled': 2.

A list of event entries. The number of entries is given by basicEventNumber.

Parameter values for a event entry.

In identification number for an event. The value 1 indicates the oldest event in the file, with subsequent numbers indicating sequential events. The event text for a given number may change as a circular event log wraps over its beginning. Corresponds directly to the relative position of an event in the MANAGER EVENTS display.

The text of the event, including date, time and other information. Corresponds directly to the individual event text in the MANAGER EVENTS display.

The system's number of mass-storage devices.

A list of device entries. The number of entries is given by basicDeviceNumber.

Parameter values for a device entry.

In identification number for a device, in the range 1 to basicDeviceNumber

A name by which the device is known in other displays, such as 'C1' or 'D2'.

Details of the device type, including, for example, size, manufacturer, Flash versus RAM, and such. Corresponds directly to the value labeled 'Device Type: in the MANAGER DEVICE STATUS display.

Current operational state of the device. Corresponds directly the value labeled 'Device Operation:' in the MANAGER DEVICE STATUS display. Enumeration: 'loadingClient': 8, 'format': 3, 'read': 1, 'write': 2, 'idle': 4, 'erase': 5, 'paramStore': 6, 'unpack': 7.

Formatting status of the device. Corresponds directly the presence of one of the value labels under the label 'Device Status:' in the MANAGER DEVICE STATUS display. Enumeration: 'unformatted': 1, 'unknown': 3, 'formatted': 2.

Write-protect status of the device. Corresponds directly the presence of one of the value labels under the label 'Device Status:' in the MANAGER DEVICE STATUS display. Enumeration: 'unknown': 3, 'write-protected': 2, 'write-enabled': 1.

Control to cause formatting of the medium in the device. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the device to be formatted. Corresponds directly to the FORMAT DEVICE command. Enumeration: 'ready': 1, 'execute': 2.

Control to cause getting a file to the device from a remote host system. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes the get to be attempted. Corresponds directly to the GET DEVICE command. When set to 'execute', the objects deviceGetFileHostIdentificationType, deviceGetFileHostIdentification, deviceGetFileName and deviceGetFileArea must be somewhere in the same set request message. Enumeration: 'ready': 1, 'execute': 2, 'abort': 3.

The type of identification value in deviceIdentification. Corresponds indirectly to ADDRESS in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is 'undefined'.

Identification of the host to get the file from, with type depending on deviceIdentificationType. Corresponds directly to ADDRESS in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero length.

The name of the file to get. Corresponds directly to LOAD FILE in the GET DEVICE command. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero length.

The area number in which to put the file. Corresponds directly to AREA in the GET DEVICE command. If it is not relevant to the particular device, it is ignored. This object may not be set outside the context of setting deviceGetFile to 'execute'. In response to a get-request or get-next-request, the value of this object is zero.

Formatting option to apply. Corresponds directly to the OPTION in the FORMAT DEVICE command. This object may not be set outside the context of setting deviceFormatMedium to 'execute'. In response to a get-request or get-next-request, the value of this object is zero.

Control for creating redundant parameter storage areas when formatting. Corresponds directly to NONREDUNDANT in the FORMAT DEVICE command. This object may not be set outside the context of setting deviceFormatMedium to 'execute'. In response to a get-request or get-next-request, the value of this object is zero. Enumeration: 'nonredundant': 1, 'redundant': 2.

Result of the immediately previous concluded boot dialog. Corresponds directly to the value labeled 'Get File Previous Status:' in the SHOW CARD STATUS display.

Control for allowing dump service for any client. Corresponds directly to DUMP and the value labeled 'Dump:' in the MANAGER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Identification number of the disk drive where dumps are stored. Corresponds directly to DUMP DRIVE and the value labeled 'Dump Drive:' in the MANAGER CHARACTERISTICS display.

Relative preference for this dump server over others. Corresponds directly to DUMP MERIT and the value labeled 'Dump Merit:' in the MANAGER CHARACTERISTICS display.

Type of dump file to keep. Corresponds directly to DUMP SIZE and the value labeled 'Dump Size:' in the MANAGER CHARACTERISTICS display. Enumeration: 'small': 1, 'full': 2.

The number of dumps completed since system initialization. Corresponds directly to the value labeled 'Dump Operations Completed:' in the MANAGER STATUS display.

The number of dumps in progress. Corresponds directly to the value labeled 'Currently Dumping:' in the MANAGER STATUS display.

The number of dump files currently stored. Corresponds directly to the value labeled 'Network dump files' and 'files' in the MANAGER FILES display.

A list of dump file entries. The number of entries is given by dumpFileNumber.

Parameter values for a dump file entry.

The type of identification value in dumpFileIdentification. Corresponds indirectly to a file name part in the section labeled 'Network dump files' in the MANAGER FILES display.

Identification of the dump file, an Ethernet address, as indicated by dumpFileIdentificationType. Corresponds indirectly to a file name part in the section labeled 'Network dump files' in the MANAGER FILES display.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds indirectly to the PURGE MANAGER DUMP FILES command. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

The time the dump file was created. Corresponds directly to a date and time in the section labeled 'Network dump files' in the MANAGER FILES display.

The number of bytes stored in the dump file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Network dump files' in the MANAGER FILES display.

Control for allowing load service for any client. Corresponds directly to LOAD and the value labeled 'Load:' in the MANAGER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Relative preference for this load server over others. Corresponds directly to LOAD MERIT and the value labeled 'Load Merit:' in the MANAGER CHARACTERISTICS display.

The number of loads completed since system initialization. Corresponds directly to the value labeled 'Load Operations Completed:' in the MANAGER STATUS display.

The number of loads in progress. Corresponds directly to the value labeled 'Currently Loading:' in the MANAGER STATUS display.

The number of load files currently stored. Corresponds directly to the value labeled 'Load image files' and 'files' in the MANAGER FILES display.

A list of load file entries. The number of entries is given by loadFileNumber.

Parameter values for a load file entry.

The name of a load file. Corresponds directly to a file name part in the section labeled 'Load image files' in the MANAGER FILES display.

The time the load file was created. Corresponds directly to a date and time in the section labeled 'Load image files' in the MANAGER FILES display.

The number of bytes stored in the load file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Load image files' in the MANAGER FILES display.

The software version type of the image in the load file. Corresponds directly to a software version in the section labeled 'Load image files' in the MANAGER FILES display. alpha 'A': alpha test beta 'B': beta test production null: normal, production software special 'S': special, custom software Enumeration: 'alpha': 1, 'beta': 2, 'production': 3, 'special': 4.

The software version of the image in the load file. Corresponds directly to a software version in the section labeled 'Load image files' in the MANAGER FILES display. For example, the version display for loadFileSoftwareVersionType 'production' and loadFileSoftwareVersion '2.2.0.0' is 'V2.2'. The version display for loadFileSoftwareVersionType 'beta' and loadFileSoftwareVersion '3.1.0.4' is 'V3.1B4'.

Control for allowing parameter storage service for any client. Corresponds directly to PARAMETER SERVICE and the value labeled 'Parameter Service:' in the MANAGER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control for allowing default parameter loading service for any client. Corresponds directly to PARAMETER DEFAULT SERVICE and the value labeled 'Parameter Default Service:' in the MANAGER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Identification number of the disk drive where parameters are stored. Corresponds directly to PARAMETER DRIVE and the value labeled 'Parameter Drive:' in the MANAGER CHARACTERISTICS display.

The number of params in progress. Corresponds directly to the value labeled 'Currently Paraming:' in the MANAGER STATUS display.

The number of parameter storage operations in progress. Corresponds directly to the value labeled 'Currently saving parameters:' in the MANAGER STATUS display.

The number of parameter files currently stored. Corresponds directly to the value labeled 'Parameter files' and 'files' in the MANAGER FILES display.

A list of param file entries. The number of entries is given by paramFileNumber.

Parameter values for a param file entry.

The type of identification value in paramFileIdentification. Corresponds indirectly to a file name part in the section labeled 'Parameter files' in the MANAGER FILES display.

Identification of the param file, an Ethernet address, as indicated by paramFileIdentificationType. Corresponds indirectly to a file name part in the section labeled 'Parameter files' in the MANAGER FILES display.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds indirectly to the PURGE MANAGER PARAMETER FILES command. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

The time the parameter file was last written. Corresponds directly to a date and time in the section labeled 'Parameter files' in the MANAGER FILES display.

The number of bytes stored in the param file. Corresponds directly to the value labeled 'bytes' in the section labeled 'Parameter files' in the MANAGER FILES display.

The version number of the parameter data in the file. Corresponds directly to the value labeled 'ver' in the section labeled 'Parameter files' in the MANAGER FILES display.

The name of the system that most recently provided this system's stored parameters. Corresponds directly to the name value labeled 'Loaded From:' in the PARAMETER SERVER display.

The type of network address contained in paramClientLoaderAddress. 'unknown' means no address has been defined. 'other' means no other type value applies. 'local' means there is no address and parameters were loaded from local storage. 'ip' is an Internet IP address. 'ethernet' is an 802.3 MAC address. Corresponds indirectly to the address value labeled 'Loaded From:' in the PARAMETER SERVER display.

The network address of the system that most recently provided this system's stored parameters. Corresponds directly to the address value labeled 'Loaded From:' in the PARAMETER SERVER display.

The version number of the parameters as stored in this system's local memory. Corresponds directly to SERVER PARAMETER VERSION and the value labeled 'Last Update Version:' in the PARAMETER SERVER display.

This system's local date and time when it last attempted to store parameters with a parameter server. Corresponds directly to the values labeled 'Last Update Date:' and 'Last Update Time:' in the PARAMETER SERVER display.

Control over whether or not this system is allowed to check for additional parameter servers. 'enabled' allows checking. Corresponds directly to PARAMETER SERVER CHECK and the presence of PARAMETER POLLING under the label 'Enabled Characteristics' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

The number of minutes between checks for additional parameter servers. Corresponds directly to PARAMETER SERVER CHECK TIMER and the value labeled 'Check Timer:' in the PARAMETER SERVER display.

Control to cause this system to immediately check for additional parameter servers. The agent always returns 'ready' for this value. Setting the value to 'ready' has no effect. Setting it to 'execute' causes a check to be started. Corresponds to the CHECK PARAMETER SERVER command. Enumeration: 'ready': 1, 'execute': 2.

The maximum number of parameter servers this system is allowed to remember at the same time. Corresponds directly to PARAMETER SERVER LIMIT and the value labeled 'Parameter Server Limit:' in the PARAMETER SERVER display.

The number of minutes between this system's attempts to store new parameters with a server that has not acknowledged previous attempts. Corresponds directly to PARAMETER SERVER RETRANSMIT TIMER and the value labeled 'Retransmit Timer: in the PARAMETER SERVER display.

The maximum number of attempts by this system to store new parameters with a server that has not acknowledged previous attempts. Corresponds directly to PARAMETER SERVER RETRANSMIT LIMIT and the value labeled 'Retransmit Limit:' in the PARAMETER SERVER display.

This system's state with regard to update attempts. The value meanings are: other none of the following idle no update in progress internal internal state of no meaning to manager hold holding to keep from updating too often retry waiting to retry after failure Corresponds directly to the value labeled 'Storage State:' in the PARAMETER SERVER display. Enumeration: 'internal8': 10, 'retry': 12, 'internal1': 3, 'internal2': 4, 'internal3': 5, 'internal4': 6, 'internal5': 7, 'internal6': 8, 'internal7': 9, 'idle': 2, 'other': 1, 'hold': 11.

The number of invalid parameter service protocol messages received by this system. Corresponds directly to the value labeled 'Bad Parameter Messages:' in the PARAMETER SERVER display.

The number of parameter servers this system rejected due to exceeding paramClientServerLimit. Corresponds directly to the value labeled 'Rejected Servers:' in the PARAMETER SERVER display.

The number of parameter servers known to this system, indicating the number of entries in serverTable. Corresponds directly to the value labeled 'Parameter Servers:' in the PARAMETER SERVER display.

A list of parameter server entries. The number of entries is given by the value of paramClientServerNumber.

Status and parameter values for a parameter server.

The server's name, unique within this system. Always 16 characters, null padded on the end. Corresponds directly to the name used to create the entry and the value labeled 'Name' in the PARAMETER SERVER display.

The status of the entry. Set to 'invalid' to remove the entry, which corresponds directly to the CLEAR/PURGE PARAMETER SERVER command. Actual removal of the entry is implementation specific. Enumeration: 'valid': 2, 'invalid': 1.

The type of network address contained in paramServerAddress. 'unknown' means no address has been defined. 'other' means no other type value applies. 'local' means there is no address and parameters were loaded from local storage. 'ip' is an Internet IP address. 'ethernet' is an 802.3 MAC address. Corresponds indirectly to the value labeled 'Address' in the PARAMETER SERVER display.

The server's network address. Corresponds directly to the value labeled 'Address' in the PARAMETER SERVER display.

Parameter version number currently stored at the server. Corresponds directly to the value labeled 'Version' in the PARAMETER SERVER display.

The server's date and time when it stored the parameters of version paramServerStoredVersion. Corresponds directly to the value labeled 'Date' in the PARAMETER SERVER display.

Status of this system's parameters with respect to the server. Corresponds directly to the value labeled 'Status' in the PARAMETER SERVER display. The value meanings are: ahead server version newer than system's behind server version older than system's current up to date failed system no longer attempting update failing system trying to update but failing query attempting to determine version noMemCard no memory card in card drive unknown version not known Enumeration: 'ahead': 3, 'unknown': 1, 'failing': 5, 'noMemCard': 8, 'current': 2, 'failed': 6, 'behind': 4, 'query': 7.

When paramServerStoredStatus is 'failed' or 'failing', the reason for the most recent failure. Corresponds directly to the value labeled 'Reason' in the PARAMETER SERVER display. The value meanings are: other none of the following none no failure protocolOut invalid protocol message to server open file open error at server read file read error at server write file write error at server resource resource lack at server (e.g. disk) protocolIn invalid protocol message from server response no response from server close file close error at server delete file delete error at server rename file rename error at server fileData bad parameter data stored at server Enumeration: 'rename': 12, 'none': 2, 'protocolOut': 3, 'resource': 7, 'read': 5, 'protocolIn': 8, 'write': 6, 'other': 1, 'close': 10, 'fileData': 13, 'open': 4, 'response': 9, 'delete': 11.

The directory path to the parameter file on all servers. Corresponds directly to PARAMETER SERVER PATH and the value labeled 'Path:' in the PARAMETER SERVER display.

The status of the current attempt to update parameters in local chassis storage. Corresponds directly to the value labeled 'Chassis Configuration:'. Enumeration: 'verifying': 4, 'unknown': 2, 'failing': 7, 'behind': 8, 'busBusy': 5, 'current': 3, 'notApplicable': 1, 'retrying': 6.

Control over whether or not this system is allowed to send out a TFTP read broadcast after sending a BOOTP broadcast during the Parameter Check Function. 'enabled' allows TFTP broadcast. Corresponds directly to the presence of PARAMETER TFTP BROADCAST under the label 'Enabled Characteristics' in the SERVER CHARACTERISTICS display. Enumeration: 'disabled': 1, 'enabled': 2.

Control to start saving parameters immediately in response to an execute. Corresponds directly to the WRITE PARAMETERS command. In response to a get-request or get-next-request, the agent always returns 'ready' for this value. Enumeration: 'ready': 1, 'execute': 2.