OBJECT: routeProto
Type: Octet
Definition: The routing protocol from which this route was learned.
The value is taken from the list of values for routingProtocols
above.
Object Status: Encouraged.
OBJECT: routeTime
Type: TimeStamp
Definition: When this route was first received.
Object Status: Encouraged.
OBJECT: routeTOS
Type: INTEGER
Definition: The IP Type of Service which this routing entry serves.
Object Status: Required if type of service routing is supported.
OBJECT: valid
Type: BOOLEAN
Definition: Whether the route is active. (Some machines retain
routes which are no longer valid for various reasons.)
The IpTransportLayer Dictionary
The IpTransportLayer Dictionary contains any information which
pertains to transport protocols which use the IP protocol as the
network protocol. For ease of reference, the ASN.1 tag of each
transport protocol's dictionary is the same as the assigned IP
Protocol number. The definition of the IpTransportLayer
dictionary is shown below. Note that dictionaries for many
protocols are not yet defined.
IpTransportLayer ::= [APPLICATION 38] IMPLICIT SET {
[0] IMPLICIT ProtocolsSupported,
[1] IMPLICIT IcmpValues,
[2] IMPLICIT IgmpValues OPTIONAL,
[3] IMPLICIT GgpValues OPTIONAL,
[7] IMPLICIT TcpValues OPTIONAL,
[8] IMPLICIT EgpValues OPTIONAL,
[17] IMPLICIT UdpValues OPTIONAL,
[20] IMPLICIT HmpValues OPTIONAL,
[27] IMPLICIT RdpValues OPTIONAL,
[30] IMPLICIT NetbltValues OPTIONAL,
}
OBJECT: IpTransportLayer
Type: SET
Definition: see above.
The objects in the dictionary are defined below.
The IpTransportLayer Dictionary: ProtocolsSupported
OBJECT: protocolsSupported
Type: OCTETSTRING
Definition: Sparse list of transport protocols supported. Each
octet in the OCTETSTRING contains the IP protocol number of a
supported protocol. For the purposes of this definition, an
entity supports a protocol if it both contains software to
makes it possible for the protocol to be used in
communications with the entity, AND the entity keeps the
required values (if any) defined in this memo for that protocol.
The IpTransportLayer Dictionary: IcmpValues
The IcmpValues dictionary is a subdictionary of the IpTransportLayer
dictionary which tracks the workings of the Internet Control Message
Protocol, defined in RFC-792. The form of the dictionary is shown
below.
IcmpValues ::= SET {
inputPktCount [0] IMPLICIT Counter,
inputPktErrors [1] IMPLICIT Counter,
inputPktDeliver [2] IMPLICIT Counter,
inputPktTypes [3] IMPLICIT Histogram OPTIONAL,
outputPktCount [4] IMPLICIT Counter,
outputPktErrors [5] IMPLICIT Counter,
outputPktTypes [6] IMPLICIT Histogram OPTIONAL,
icmpTraffic [7] IMPLICIT TrafficMatrix OPTIONAL,
ipID [8] IMPLICIT Counter OPTIONAL
}
OBJECT: IcmpValues
Type: SET
Definition: see above.
The objects in the dictionary are defined below.
OBJECT: inputPktCount
Type: Counter
Definition: The total number of ICMP packets received (including
those in error).
OBJECT: inputPktErrors
Type: Counter
Definition: The number of ICMP packets received which proved to
have errors (bad checksums, bad length etc). Subtracting this
value from the inputPktCount field should give the number of
valid ICMP packets received.
OBJECT: inputPktDeliver
Type: Counter
Definition: The number of valid ICMP packets which were
successfully processed (e.g., delivered to the higher
protocol).
OBJECT: inputPktTypes
Type: Histogram
Definition: A histogram of ICMP messages types and codes received,
not including those messages that proved to contain errors.
The histogram histValue field contains a 16-bit value which is
the the (ICMP type * 256) + ICMP code, and the histCount field
contains the number of valid messages containing this
type/code pair which have been received.
The message type and code values are those defined in RFC-792
(e.g., the Time Exceeded Message with a code of "fragment
reassembly time exceeded" is (11 * 256) + 1 = 2817).
Object Status: Useful.
Operations on Object: The defaults except as listed below:
GET-MATCH: Match is defined on the value of the histValue
field.
OBJECT: outputPktCount
Type: Counter
Definition: The total number of ICMP packets that the entity
attempted to send (including those that failed due to lack of
buffers, a missing route or other transient transmission
problems).
OBJECT: outputPktErrors
Type: Counter
Definition: The number of ICMP packets which the entity could not
send due to transmission problems such as the lack of buffers, a
missing route or other transient transmission problems. This
value is not required to include errors which the ICMP layer
could not reasonably be expected to detect such as damage to the
packet in transit. Subtracting this value from the PktCount
field should give the number of ICMP packets the entity believes
it successfully sent.
OBJECT: outputPktTypes
Type: Histogram
Definition: A histogram of ICMP messages types and codes sent,
including those messages that later failed to be transmitted.
The histogram histValue field contains a 16-bit value which is
the the (ICMP type * 256) + ICMP code, and the histCount field
contains the number of valid messages containing this type/code
pair which have been sent.
The message type and code values are those defined in RFC-792
(e.g., the Time Exceeded Message with a code of "fragment
reassembly time exceeded" is (11 * 256) + 1 = 2817).
Object Status: Useful.
Operations on Object: The defaults except as listed below:
GET-MATCH: Match is defined on the value of the histValue
field.
OBJECT: icmpTraffic
Type: TrafficMatrix
Definition: All ICMP traffic which has originated on this machine.
The source address in the traffic matrix should be the interface
from which the packet was sent. The destination is the address
to which the packet is to finally be delivered (not an
intermediate hop).
Object Status: Useful.
OBJECT: ipID
Type: Counter
Definition: The next IP packet ID identifier to be used by the ICMP
code.
Object Status: Required if the ICMP code generates its own IP
identifiers.
The IpTransportLayer Dictionary: IgmpValues
IgmpValues ::= SET {
conformance [0] IMPLICIT INTEGER,
inputPktCount [1] IMPLICIT Counter,
inputPktErrors [2] IMPLICIT Counter,
inputPktTypes [3] IMPLICIT Histogram OPTIONAL,
outputPktCount [4] IMPLICIT Counter,
outputPktErrors [5] IMPLICIT Counter,
outputPktTypes [6] IMPLICIT Histogram OPTIONAL,
igmpTraffic [7] IMPLICIT TrafficMatrix OPTIONAL
igmpGroups [8] IMPLICIT SET of IgmpGroupEntry,
ipID [9] IMPLICIT Counter OPTIONAL,
}
OBJECT: IgmpValues
Type: SET
Definition: The dictionary of information on the Internet Group
Management Protocol (RFC-988).
Object Status: Required in hosts which support IGMP.
The objects stored in this dictionary are defined below.
OBJECT: conformance
Type: INTEGER
Definition: The level of conformance with RFC-988. The conformance
levels are:
0 -- Level 0. No support for IP multicasting
1 -- Level 1. Support for sending but not receiving
multicast datagrams.
2 -- Level 2. Full support for IP multicasting.
These values are taken directly from RFC-988.
OBJECT: inputPktCount
Type: Counter
Definition: The number of IGMP packets received including those
that proved to be in error.
OBJECT: inputPktErrors
Type: Counter
Definition: The number of IGMP packets received which proved to
be in error. This value subtracted from inputPktCount should
give the number of valid IGMP packets received.
OBJECT: inputPktTypes
Type: Histogram
Definition: A histogram of IGMP messages types and codes sent,
including those messages that later failed to be transmitted.
The histogram histValue field contains a 16-bit value which
is the the (IGMP type * 256) + IGMP code, and the histCount
field contains the number of valid messages containing this
type/code pair which have been sent.
The type and code values are taken from RFC-988.
OBJECT: outputPktCount
Type: Counter
Definition: The total number of IGMP packets that the entity
attempted to send (including those that failed due to lack
of buffers, a missing route or other transient transmission
problems).
OBJECT: outputPktErrors
Type: Counter
Definition: The number of IGMP packets which the entity could not
send due to transmission problems such as the lack of buffers,
a missing route or other transient transmission problems.
This value is not required to include errors which the IGMP
layer could not reasonably be expected to detect such as damage
to the packet in transit. Subtracting this value from the
outputPktCount field should give the number of IGMP packets
the entity believes it successfully sent.
OBJECT: outputPktTypes
Type: Histogram
Definition: A histogram of IGMP messages types and codes sent,
including those messages that later failed to be transmitted.
The histogram histValue field contains a 16-bit value which is
the the (IGMP type * 256) + IGMP code, and the histCount field
contains the number of valid messages containing this type/code
pair which have been sent.
The type and code values are taken from RFC-988.
OBJECT: igmpTraffic
Type: TrafficMatrix
Definition: All IGMP traffic which has originated on this machine.
The source address in the traffic matrix should be the interface
from which the packet was sent. The destination is the address
to which the packet is to finally be delivered (not an
intermediate hop).
Object Status: Useful.
OBJECT: igmpGroups
Type: SET
Definition: The various igmpGroups of which this host is aware.
This is stored as a set of IgmpGroupEntry. The format of an
IgmpGroupEntry is shown below.
IgmpGroupEntry ::= [0] SET {
groupAddress [0] IMPLICIT IpAddress,
groupAccessKey [1] IMPLICIT OCTETSTRING,
groupAgent [2] IMPLICIT BOOLEAN,
}
The groupAddress is the multicast IP address. The
groupAccessKey is the 8 octet key -- this key may be
confidential and should only be available to authorized querying
entities. The groupAgent field is true if this entity is an
agent for the multicast group.
OBJECT: ipID
Type: Counter
Definition: The next IP packet ID identifier to be used by the IGMP
code.
Object Status: Required if the IGMP code generates its own IP
identifiers.
The IpTransportLayer Dictionary: GgpValues
The definition of the GgpValues dictionary is left for further
study.
The IpTransportLayer Dictionary: TcpValues
The TcpValues dictionary is a subdictionary of the IpTransportLayer
dictionary which tracks the workings of the Transmission Control
Protocol, defined in RFC-793. The definitions of several objects in
this dictionary refer to definitions in RFC-793. The form of the
dictionary is shown below.
TcpValues ::= SET {
[0] IMPLICIT TcpParam
[1] IMPLICIT TcpStats OPTIONAL,
tcpConnData [2] IMPLICIT SET of TcpConn,
}
OBJECT: TcpValues
Type: IMPLICIT SET
Definition: see above.
Object Status: Required if the entity supports TCP.
The objects in the dictionary are defined in the next few sections.
The IpTransportLayer Dictionary: TcpValues/TcpParam
The TcpParam dictionary contains information about certain
parameters such as round-trip timer estimation constants which are
managed on a per-machine basis. The form of the dictionary is shown
below.
TcpParam ::= SET {
tcpRtoA [0] IMPLICIT IA5String,
tcpRtoParam [1] IMPLICIT SET of RtoParam,
ipID [2] IMPLICIT Counter,
tcpRtoMin [3] IMPLICIT INTEGER OPTIONAL,
tcpRtoMax [4] IMPLICIT INTEGER OPTIONAL,
tcpMaxSegSiz [5] IMPLICIT INTEGER,
tcpMaxConn [6] IMPLICIT INTEGER OPTIONAL,
tcpMaxWindow [7] IMPLICIT INTEGER OPTIONAL,
}
OBJECT: tcpParam
Type: SET
Definition: see above.
The definition of the objects in the tcpParam dictionary are given
below.
OBJECT: tcpRtoA
Type: IA5String
Definition: The TCP retransmission timeout algorithm used. The
algorithm is expressed as one or more equations to generate
a target value, "RTO[N]", which is the retransmission timeout
for packet "N". Expressions should use well understood
symbols such as * for multiplication and / for division, and
parentheses to indicate precedence. Variables should begin
with an upper case character. Multiple equations should be
separated by semi-colons. Comments should be in braces (i.e.,
{}). Constants should begin with a lower case character. In
addition to "RTO[N]" the symbol "S[N]" is defined to mean the
round-trip sample for packet N. Using this syntax, the
algorithm in RFC-793 would be expressed as:
RTO[N] = SRTT[N] * beta ;
SRTT[N] = ( S[N-1] * alpha) + (SRTT[N-1] * (1 - alpha))
Note: The syntax probably needs to be refined so that it can be
parsed and interpreted by a program. This is left for future
study.
OBJECT: tcpRtoParam
Type: SET of RtoParam
Definition: The list of the values of the constants used by the
retransmission timeout algorithm. The format of the RtoParam
structure is shown below.
RtoParam ::= SEQUENCE {
name IA5String,
value Fraction
}
The name is the name of the constant as expressed in the
tcpRtoA (e.g., "beta").
OBJECT: ipID
Type: Counter
Definition: The next IP packet ID identifier to be used by the TCP
code.
Object Status: Required if the TCP code generates its own IP
identifiers.
OBJECT: tcpRtoMin
Type: INTEGER
Definition: The minimum value the TCP implementation permits for
the retransmission timeout (RTO), measured in milliseconds.
Note: If the SET operation is optionally defined, access control
must be exercised.
Object Status: Required if the implementation uses the suggested
algorithm in RFC-793 or if the implementation sets any limits
on the minimum RTO.
Operations on Object: The defaults except as listed below:
SET: Optionally defined to change the value. Implementations
should confirm that the new value is less than tcpRtoMax.
OBJECT: tcpRtoMax
Type: INTEGER
Definition: The maximum value the TCP implementation permits for
the retransmission timeout (RTO), measured in milliseconds.
Note: If the SET operation is optionally defined, access control
must be exercised.
Object Status: Required if the implementation uses the suggested
algorithm in RFC-793 or if the implementation sets any limits
on the maximum RTO.
Operations on Object: The defaults except as listed below:
SET: Optionally defined to change the value. Implementations
should confirm that the new value is greater than tcpRtoMax,
and that the value is large (i.e., several seconds).
OBJECT: tcpMaxSegSiz
Type: INTEGER
Definition: The maximum segment size used by this implementation.
Object Status: Required if the entity sets an upper limit on the
MTU. (Some implementations have no constraints, but chose an
MTU from external constraints such as the maximum MTU of the
network interface in use.)
OBJECT: tcpMaxConn
Type: INTEGER
Definition: An optional value, which must be present if the entity
has a limit on the total number of TCP connections it can support.
Object Status: Required if the entity sets limits.
Note: If the SET operation is defined, access control must be
exercised.
Operations on Object: The defaults except as listed below:
SET: Optionally defined to change the value. If the
new value is less than the number of currently
open connections, implementations are *not* required
to close existing connections, but may not open
any additional ones.
OBJECT: tcpMaxWindow
Type: INTEGER
Definition: An optional value, which must be present if the entity
places a fixed upper limit on the size of any connection's TCP
window (i.e., if the maximum window size is not per connection
configurable).
Object Status: Required if the entity sets limits.
Note: If the SET operation is defined, access control must be
exercised.
Operations on Object: The defaults except as listed below:
SET: Optionally defined to change the value. The new
value must be at least the size of one maximum
TCP segment.
The IpTransportLayer Dictionary: TcpValues/TcpStats
The TcpStats dictionary stores general information about the
workings of the TCP layer. The form of the dictionary is shown
below.
TcpStats ::= SET {
connAttempts [0] IMPLICIT Counter OPTIONAL,
connOpened [1] IMPLICIT Counter OPTIONAL,
connAccepted [2] IMPLICIT Counter OPTIONAL,
connClosed [3] IMPLICIT Counter OPTIONAL,
connAborted [4] IMPLICIT Counter OPTIONAL,
connAbortedInfo [5] IMPLICIT Histogram OPTIONAL,
octetsIn [6] IMPLICIT Counter OPTIONAL,
octetsOut [7] IMPLICIT Counter OPTIONAL,
octetsInDup [8] IMPLICIT Counter OPTIONAL,
octetsRetrans [9] IMPLICIT Counter OPTIONAL,
inputPkts [10] IMPLICIT Counter OPTIONAL,
retransPkts [11] IMPLICIT Counter OPTIONAL,
outputPkts [12] IMPLICIT Counter OPTIONAL,
dupPkts [13] IMPLICIT Counter OPTIONAL,
}
OBJECT: TcpStats
Type: SET
Definition: See above.
Object Status: Encouraged.
The definition of the fields in the dictionary are given below.
OBJECT: connAttempts
Type: Counter
Definition: The number of connection attempts that have been made
from this host. This includes pending attempts.
Object Status: Encouraged.
OBJECT: connOpened
Type: Counter
Definition: The number of connection attempts from this host which
successfully generated an open connection. This includes
currently open connections.
Object Status: Encouraged.
OBJECT: connAccepted
Type: Counter
Definition: The number of connections accepted by listening peers
on this entity. This includes currently open connections.
Object Status: Encouraged.
OBJECT: connClosed
Type: Counter
Definition: The number of connections which were properly closed.
Object Status: Encouraged.
OBJECT: connAborted
Type: Counter
Definition: The number of connections which were aborted. Note
that if implementations trace how the connection was aborted,
they are encouraged to use the connAbortedInfo histogram.
Object Status: Encouraged.
OBJECT: connAbortedInfo
Type: Histogram
Definition: The number of connections which were aborted by type of
abort. The histValue is one of the codes listed below. The
histCount is the number of connections aborted for this reason.
The histValues codes are:
0 -- an abort condition not specified below
1 -- remote abort
2 -- local application abort
3 -- local protocol level abort
Object Status: Useful
OBJECT: octetsIn
Type: Counter
Definition: The total number of TCP octets (not including
duplicates) received at this entity.
Object Status: Required if TcpStats is implemented.
OBJECT: octetsOut
Type: Counter
Definition: The total number of TCP octets (not including
retransmissions) sent from this entity.
Object Status: Required if TcpStats is implemented.
OBJECT: octetsInDup
Type: Counter
Definition: The total number of TCP octets received which were
duplicates.
Object Status: Required if TcpStats is implemented.
OBJECT: octetsReTrans
Type: Counter
Definition: The total number of TCP octets which have been
retransmitted.
Object Status: Required if TcpStats is implemented.
OBJECT: inputPkts
Type: Counter
Definition: The total number of valid packets received, including
those on current connections.
Object Status: Useful.
OBJECT: retransPkts
Type: Counter
Definition: The total number of packets retransmitted.
Object Status: Useful.
OBJECT: outputPkts
Type: Counter
Definition: The total number of packets sent.
Object Status: Useful.
OBJECT: dupPkts
Type: Counter
Definition: The number of packets received which contained only
data already received.
Object Status: Useful.
The IpTransportLayer Dictionary: TcpValues/TcpConn
The tcpConnData field in the TcpValues dictionary is a set of
TcpConn, where each TcpConn contains information on a particular TCP
connection. The definition of TcpConn is shown below.
TcpConn ::= SET {
localPort [0] IMPLICIT INTEGER,
localAddress [1] IMPLICIT IpAddress,
foreignPort [2] IMPLICIT INTEGER,
foreignAddress [3] IMPLICIT IpAddress,
state [4] IMPLICIT INTEGER,
snduna [5] IMPLICIT INTEGER,
sndnxt [6] IMPLICIT INTEGER,
sndwnd [7] IMPLICIT INTEGER,
congwnd [8] IMPLICIT INTEGER,
rcvnxt [9] IMPLICIT INTEGER,
rcvwnd [10] IMPLICIT INTEGER,
srtt [11] IMPLICIT INTEGER OPTIONAL,
lastrtt [12] IMPLICIT INTEGER OPTIONAL,
maxSegSize [13] IMPLICIT INTEGER,
octetsSent [14] IMPLICIT Counter OPTIONAL,
octetsRXmit [15] IMPLICIT Counter OPTIONAL,
octetsRcvd [16] IMPLICIT Counter OPTIONAL,
octetDups [17] IMPLICIT Counter OPTIONAL,
octetPastWin [18] IMPLICIT Counter OPTIONAL,
segSizes [19] IMPLICIT Histogram OPTIONAL,
}
The set of TCP connections can be searched in a number of ways based
on the local and foreign addresses (including the port number).
Individual values of a connection cannot be retrieved without a
search.
OBJECT: TcpConn
Type: SET
Definition: The per TCP connection data.
Operations on Object: The defaults except as listed below:
GET-MATCH: Defined on any combination of values of
localAddress, localPort, foreignAddress and
foreignPort. Returns all connections which match
the template. (For example, GET-MATCH on a
particular foreignAddress returns all connections
to that address.)
The definitions of the fields of the tcpConn structure are given
below.
OBJECT: localPort
Type: INTEGER
Definition: The local port number of this connection.
Operations on Object: Defaults. Note that MATCH operators may be
applied to this object to locate information on a particular TCP
connection.
OBJECT: localAddress
Type: IpAddress
Definition: The local IP address of this connection. May be the
default IP address defined above. This value may not be valid
in certain states.
Operations on Object: Defaults. Note that MATCH operators may be
applied to this object to locate information on a particular
TCP connection.
OBJECT: foreignPort
Type: INTEGER
Definition: The foreign port number of this connection. This value
may be meaningless if the local peer is in certain states (e.g.,
LISTEN).
Operations on Object: Defaults. Note that MATCH operators may be
applied to this object to locate information on a particular TCP
connection.
OBJECT: foreignAddress
Type: IpAddress
Definition: The foreign IP address of this connection. This value
may be meaningless if the local peer is in certain states (e.g.,
LISTEN).
Operations on Object: Defaults. Note that MATCH operators may be
applied to this object to locate information on a particular
TCP connection.
OBJECT: state
Type: INTEGER
Definition: The current state of the local peer. The values
corresponding to the different states are: close(0), listen(1),
syn-sent(2), syn-received(3), established(4), close-wait(5),
fin-wait-1(6), closing(7), last-ack(8), fin-wait-2(9),
time-wait(10). Implementations must map internal
representations of the state into these values.
OBJECT: snduna
Type: INTEGER
Definition: The SND.UNA value as defined in RFC-793.
OBJECT: sndnxt
Type: INTEGER
Definition: The SND.NXT value as defined in RFC-793.
OBJECT: sndwnd
Type: INTEGER
Definition: The SND.WND value as defined in RFC-793.
OBJECT: congwnd
Type: INTEGER
Definition: The congestion window. This value is less than or
equal to sndwnd. If less than sndwnd, then congestion
control is in effect and congwnd is the reduced send window
size in use.
OBJECT: rcvnxt
Type: INTEGER
Definition: The RCV.NXT value as defined in RFC-793.
OBJECT: rcvwnd
Type: INTEGER
Definition: The RCV.WND value as defined in RFC-793.
OBJECT: srtt
Type: INTEGER
Definition: The smoothed round-trip time in milliseconds.
Object Status: Required if the implementation maintains a smoothed
round-trip time.
OBJECT: lastrtt
Type: INTEGER
Definition: The last round-trip time sample taken in milliseconds.
Object Status: Encouraged.
OBJECT: maxSegSize
Type: INTEGER
Definition: The maximum segment size that can be used on this
connection.
OBJECT: octetsSent
Type: Counter
Definition: The total number of octets transmitted since the
connection was opened, not including retransmissions. Can
alternatively be thought of as the current length of the
stream.
Object Status: Encouraged.
OBJECT: octetsRXmit
Type: Counter
Definition: The total number of octets retransmitted since the
connection was opened. This plus octetsSent should give the
total number of octets sent.
Object Status: Encouraged.
OBJECT: octetsRcvd
Type: Counter
Definition: The number of octets received since the connection was
opened, not including duplicates received. The receiver's
version of octetsSent.
Object Status: Encouraged.
OBJECT: octetDups
Type: Counter
Definition: The total number of octets received since the
connection was opened which were redundant (i.e., they had been
previously received).
Object Status: Encouraged.
OBJECT: octetPastWin
Type: Counter
Definition: The number of segments which contained data beyond
the upper edge of the receive window.
Object Status: Encouraged
OBJECT: segSizes
Type: Histogram
Definition: A histogram of the sizes of the packets sent on the
connection (useful for catching cases of silly-window syndrome).
This histogram is an range histogram, measuring the number of
segments whose size fell into a give range. The histogram
histValue field contains a segment size, and the histCount
field contains the number of segments between this size and
the next largest size.
Object Status: Useful.
The IpTransportLayer Dictionary: EgpValues
The EgpValues dictionary stores information about the workings of
the Exterior Gateway Protocol, defined in RFC-904. The format of
the dictionary is shown below.
EgpValues ::= SET {
egpState [0] IMPLICIT INTEGER,
[1] IMPLICIT EgpParam,
[2] IMPLICIT EgpStats OPTIONAL,
egpPeerData [3] IMPLICIT SET of EgpPeer
}
OBJECT: EgpValues
Type: SET
Definition: See above.
Object Status: Required in entities which support EGP.
The definitions of the subdictionaries of this dictionary are given
below.
OBJECT: egpState
Type: INTEGER
Definition: The state of the EGP system. The state values are:
0 -- Idle
1 -- Acquisition
2 -- Down
3 -- Up
4 -- Cease
These values are taken directly from RFC-904.
The IpTransportLayer Dictionary: EgpValues/EgpParam
The EgpParam dictionary stores the various EGP parameters. The
format of the dictionary is shown below.
EgpParam ::= SET {
p1 [0] IMPLICIT INTEGER,
p2 [1] IMPLICIT INTEGER,
p3 [2] IMPLICIT INTEGER,
p4 [3] IMPLICIT INTEGER,
p5 [4] IMPLICIT INTEGER,
ipID [5] IMPLICIT Counter OPTIONAL
}
OBJECT: EgpParam
Type: SET
Definition: See above.
The definition of the fields of the dictionary are given below. All
the definitions are taken from RFC-904.
OBJECT: p1
Type: INTEGER
Definition: Minimum interval acceptable between successive Hello
commands received.
Operations on Object: The defaults except as noted below.
SET: The set command is optionally defined on this object.
OBJECT: p2
Type: INTEGER
Definition: Minimum interval acceptable between successive Poll
commands received.
Operations on Object: The defaults except as noted below.
SET: The set command is optionally defined on this object.
OBJECT: p3
Type: INTEGER
Definition: Interval between Request or Cease command
retransmissions.
Operations on Object: The defaults except as noted below.
SET: The set command is optionally defined on this object.
OBJECT: p4
Type: INTEGER
Definition: Interval during which state variables are maintained in
the absence of commands or response in the Down and Up states.
Operations on Object: The defaults except as noted below.
SET: The set command is optionally defined on this object.
OBJECT: p5
Type: INTEGER
Definition: Interval during which state variables are maintained in
the absence of commands or response in the Acquisition and Cease
states.
Operations on Object: The defaults except as noted below.
SET: The set command is optionally defined on this object.
OBJECT: ipID
Type: Counter
Definition: The next IP packet ID identifier to be used by the EGP
code.
Object Status: Required if the EGP code generates its own IP
identifiers.
The IpTransportLayer Dictionary: EgpValues/EgpStats
The EgpStats dictionary keeps statistics about the use of EGP on
this entity. The form of the dictionary is shown below.
EgpStats ::= SET {
inputPktCount [1] IMPLICIT Counter,
inputPktErrors [2] IMPLICIT Counter,
inputPktTypes [3] IMPLICIT Histogram OPTIONAL,
outputPktCount [4] IMPLICIT Counter,
outputPktErrors [5] IMPLICIT Counter,
outputPktTypes [6] IMPLICIT Histogram OPTIONAL,
egpTraffic [7] IMPLICIT TrafficMatrix OPTIONAL
}
OBJECT: EgpStats
Type: SET
Definition: See above.
The definitions of the objects in this dictionary are given below.
OBJECT: inputPktCount
Type: Counter
Definition: The number of EGP packets received including those that
proved to be in error.
OBJECT: inputPktErrors
Type: Counter
Definition: The number of EGP packets received which proved to be
in error. This value subtracted from inputPktCount should give
the number of valid EGP packets received.
OBJECT: inputPktTypes
Type: Histogram
Definition: A histogram of types of valid EGP messages received.
The histogram histValue field contains the message type number,
and the histCount field contains the number of messages of
this type which have been received.
Object Status: Useful.
OBJECT: outputPktCount
Type: Counter
Definition: The total number of EGP packets that the entity
attempted to send (including those that failed due to lack of
buffers, a missing route or other transient transmission
problems).
OBJECT: outputPktErrors
Type: Counter
Definition: The number of EGP packets which the entity could not
send due to transmission problems such as the lack of buffers,
a missing route or other transient transmission problems.
This value is not required to include errors which the EGP
layer could not reasonably be expected to detect such as
damage to the packet in transit. Subtracting this value from
the outputPktCount field should give the number of EGP packets
the entity believes it successfully sent.
OBJECT: outputPktTypes
Type: Histogram
Definition: A histogram of EGP messages types sent, including those
that later failed to be transmitted. The histogram histValue
field contains the message type number, and the histCount field
contains the number of messages of this type which have been sent.
Object Status: Useful.
OBJECT: egpTraffic
Type: TrafficMatrix
Definition: All EGP traffic which has originated on this machine.
The source address in the traffic matrix should be the interface
from which the packet was sent. The destination is the address
to which the packet is to finally be delivered (not an
intermediate hop).
Object Status: Useful.
The IpTransportLayer Dictionary: EgpValues/EgpPeer
The egpPeerData field of the EgpValues dictionary is a set of
EgpPeer structures which contain the state variables for a
particular EGP neighbor. The form of the EgpPeer structure is shown
below.
EgpPeer ::= SET {
r [0] IMPLICIT Counter,
s [1] IMPLICIT Counter,
t1 [2] IMPLICIT INTEGER,
t2 [3] IMPLICIT INTEGER,
t3 [4] IMPLICIT INTEGER,
m [5] IMPLICIT BOOLEAN,
timer1 [6] IMPLICIT INTEGER,
timer2 [7] IMPLICIT INTEGER,
timer3 [8] IMPLICIT INTEGER,
addr [9] IMPLICIT IpAddress
}
OBJECT: EgpPeer
Type: SET
Definition: The state information for a given EGP neighbor.
The definition of each field is given below.
OBJECT: r
Type: Counter
Definition: The receive sequence number as defined in RFC-904.
OBJECT: s
Type: Counter
Definition: The send sequence number as defined in RFC-904.
OBJECT: t1
Type: INTEGER
Definition: The interval between Hello command retransmissions as
defined in RFC-904.
OBJECT: t2
Type: INTEGER
Definition: The interval between Poll command retransmissions as
defined in RFC-904.
OBJECT: t3
Type: INTEGER
Definition: The interval during which neighbor-reachability
indications are counted, as defined in RFC-904.
OBJECT: m
Type: BOOLEAN
Definition: The Hello Polling mode. True if in active mode, false
if in passive mode.
Operations on Object: The defaults except as noted below.
SET: Optionally defined to change the Hello Polling mode.
OBJECT: timer1
Type: INTEGER
Definition: The value of timer 1 as defined in RFC-904.
OBJECT: timer2
Type: INTEGER
Definition: The value of timer 2 as defined in RFC-904.
OBJECT: timer3
Type: INTEGER
Definition: The value of timer 3 as defined in RFC-904.
OBJECT: addr
Type: IpAddress
Definition: The IP address of the neighbor.
The IpTransportLayer Dictionary: UdpValues
The UdpValues dictionary stores all information on the User Datagram
Protocol, defined in RFC-768. The format of the dictionary is shown
below.
UdpValues ::= [17] IMPLICIT SET OPTIONAL {
ipID [0] IMPLICIT Counter OPTIONAL,
[1] IMPLICIT UdpStats,
udpPortData [2] IMPLICIT SET of udpPort
}
OBJECT: UdpValues
Type: SET
Definition: See above.
Object Status: Implementation of this dictionary is required if
the entity supports UDP.
The fields of this dictionary are given below.
OBJECT: ipID
Type: Counter
Definition: The next IP packet ID identifier to be used by the UDP
code.
Object Status: Required if the UDP code generates its own IP
identifiers.
The IpTransportLayer Dictionary: UdpValues/UdpStats
The UdpStats dictionary stores general information about the
behavior of the UDP protocol on the entity. The format of the
dictionary is shown below.
UdpStats ::= SET {
inputPkts [0] IMPLICIT Counter,
inputPktErrors [1] IMPLICIT Counter,
outputPkts [2] IMPLICIT Counter,
}
OBJECT: UdpStats
Type: SET
Definition: See above.
Object Status: Encouraged.
The fields in this dictionary are defined below.
OBJECT: inputPkts
Type: Counter
Definition: The total number of UDP packets received at this entity
including any errors.
Object Status: Required if the UdpStats dictionary is implemented.
OBJECT: inputPktsErrors
Type: Counter
Definition: The number of UDP packets which could not be delivered
because of format errors, data corruption or because there was no
application at the destination port.
Object Status: Required if the UdpStats dictionary is implemented.
OBJECT: outputPkts
Type: Counter
Definition: The total number of UDP segments sent from this entity.
Object Status: Required if the UdpStats dictionary is implemented.
The IpTransportLayer Dictionary: UdpValues/udpPortData
The udpPortData structure stores information about individual UDP
applications. The udpPortData is represented as a set of records,
udpPorts, which track the behavior of individual ports. The format
of both structures are shown below.
udpPortData [1] IMPLICIT SET of UdpPort
UdpPort ::= [0] IMPLICIT SET {
localAddress [0] IMPLICIT IpAddress,
localPort [1] IMPLICIT INTEGER,
foreignAddress [2] IMPLICIT IpAddress OPTIONAL,
foreignPort [3] IMPLICIT INTEGER OPTIONAL,
maxPktSize [4] IMPLICIT INTEGER,
pktsRcvd [5] IMPLICIT Counter,
octetRcvd [6] IMPLICIT Counter OPTIONAL,
pktsSent [7] IMPLICIT Counter,
octetSent [8] IMPLICIT Counter OPTIONAL,
}
OBJECT: udpPortData
Type: SET of udpPort
Definition: See above.
OBJECT: UdpPort
Type: SET
Definition: See above.
Operations on Object: The defaults except as noted below.
GET-MATCH. Defined on any combination of the values of
localAddress, localPort, foreignAddress and foreignPort.
Returns all ports which match the template.
The meaning of the individual fields of the udpPort record are given
below.
OBJECT: localAddress
Type: IpAddress
Definition: The local IP address of the port. May be the default
IP address if records are accepted from any interface.
OBJECT: localPort
Type: INTEGER
Definition: The local port number.
OBJECT: foreignAddress
Type: IpAddress
Definition: Some UDP implementations permit applications to specify
the remote address from which packets will be accepted. In such
implementations, this field may be used to return the remote IP
address. If this value is set to the default IP address, then
packets from any host are accepted. The default IP address
indicates that the application has not specified the remote
address (but could if it chose).
Object Status: Required in entities which permit applications to
specify the remote address.
OBJECT: foreignPort
Type: INTEGER
Definition: Some UDP implementations permit applications to specify
the remote address from which packets will be accepted. In such
implementations, this field may be used to return the remote
port. If this value is set to 0, packets from any remote port
are accepted.
Object Status: Required in entities which permit applications to
specify the remote port.
OBJECT: maxPktSize
Type: INTEGER
Definition: The maximum UDP packet size, if any, supported by this
host.
Object Status: Required if there is a limit on the UDP packet size.
OBJECT: pktsRcvd
Type: Counter
Definition: The total number of packets received on this port during
the lifetime of this application (i.e., application which opened
this port).
OBJECT: octetsRcvd
Type: Counter
Definition: The total number of octets received at this port.
OBJECT: pktsSent
Type: Counter
Definition: The total number of packets sent on this port during the
lifetime of this application (i.e., the application which opened
this port).
OBJECT: octetsSent
Type: Counter
Definition: The total number of octets sent on this port during the
lifetime of this application (i.e., the application which opened
this port).
The IpTransportLayer Dictionary: HmpValues
The HmpValues dictionary stores all information on the Host
Monitoring Protocol, defined in RFC-869. Since HEMS is designed to
replace HMP, the definition of this dictionary has been deferred
until a clear need for it is demonstrated.
The IpTransportLayer Dictionary: RdpValues
The RdpValues dictionary stores all information on the Reliable
Data Protocol (RDP). Since RDP is currently being tested and
revised, the definition of this dictionary is left for further
study.
The IpTransportLayer Dictionary: NetbltValues
The NetbltValues dictionary stores all information on the Network
Block Transfer protocol. Since Netblt is currently being tested
and revised, the definition of this dictionary is left for further
study.
The IpApplications Dictionary
The IpApplications dictionary stores information about networking
applications whose operations may affect the proper operation of
the network. Examples of such applications might be domain
nameservers or distributed routing agents (such as gated or
routed). The definition of this dictionary is left for further
study.
NOTES ON RETRIEVAL OF OBJECTS
It is assumed in this system that the query processor is only one
of many concurrently running processes on an entity, and that the
operations of the other processes may affect the values of the
objects managed by the query processor. To permit this
concurrency, the query processor is not required to keep the values
frozen during the execution of a query. As a result, related
values may change during the course of the query's execution.
Applications should be prepared for this possibility.
In several places, specific mathematical relations between objects
have been specified, for example, that object X minus object Y
should yield some well-defined value. Note that in many cases,
objects X and Y are roll-over counters, in which case these
relations are only valid modulo the precision of the counter. This
is acceptable. The relationships are only intended to clarify the
association between objects.
EVENTS
In the remainder of this memo we present the format and definition
of event messages which are unsolicited updates sent from entities
to management centers.
This section needs much further work. The authors provide this
section to illustrate how the trap mechanism works. However, much
more research must be done into the questions of what events need
to be reported, and what information they must carry with them
before this section can be completed. The authors welcome any
advice from the community on this subject.
Format of Event Messages
Event messages have the same format as replies; they are a sequence
of objects. The only difference between a event message and a
regular reply to a query is that the event message is labelled as a
event in the HEMP message header and the first object in the event
message is a special event leader describing the event. All
objects after the event message are standard objects stored by the
entity which might be useful to a monitoring center in
understanding the machine state which caused the event. Each event
has a certain number of objects that it must return. Additional
objects may be returned by loading instructions into the
eventExecution buffer of the relevant eventEntry.
The format of the event leader is shown below:
EventLeader ::= [APPLICATION 1024] IMPLICIT SEQUENCE {
eventCode INTEGER,
eventIndex INTEGER,
eventThreshold INTEGER,
eventTime TimeStamp,
eventDescr IA5STRING
}
The eventCode is a number which indicates the type of event. The
eventCodes are defined below.
The eventIndex is an implementation specific value. It is
considered good practice to make sure that a particular event is
only generated in one place. It may be the case that certain HEMS
generic events (for example, "no buffer space") may be generated by
more than one place in an entity's code. To allow implementors and
network managers to determine where the event is actually being
generated, implementors should make sure that a distinct eventIndex
is assigned to each location in the code that generates a
particular event.
The eventThreshold is the value of the event threshold when the
event was sent.
The eventTime indicates when the trap was generated.
The eventDescr is a text string which describes the event. This
description should explain the general problem (e.g., "no buffer
space") and may also, optionally, include additional information
about why this particular event was generated (e.g., "could not
send ICMP redirect").
Event Definitions
The remainder of this memo presents a few generic events, which are
presented for illustration only. Implementors interested in
supporting events should contact the authors to help work out a
more comprehensive set of definitions.
The format of the event definitions is:
EVENT CODE: The event code number.
Definition: Defines the event.
Related Objects: The list of related objects which *must* be
returned following the event header. All objects should be
returned as fully qualified objects (with ASN.1 codes tracing
a complete path from the root object dictionary). If no
objects are specified, then no related objects are required.
Event Status: Events are either required of all conforming
implementations, required if the entity supports a
particular feature (e.g., TCP events) or optional.
Notes: Any additional notes about the event.
List of Events
The next few event codes are for system (as opposed to more
network oriented) events.
EVENT CODE: 0
Definition: Unused
EVENT CODE: 1
Definition: The entity has rebooted.
Related Objects: An INTEGER which is the highest HEMP
messageID reached by the trap system before the system