RFC1213-MIB
Page 14
snmpOutTooBigs
1.3.6.1.2.1.11.20
scalar
snmpOutTraps
1.3.6.1.2.1.11.29
scalar
sysContact
1.3.6.1.2.1.1.4
scalar
sysDescr
1.3.6.1.2.1.1.1
scalar
sysLocation
1.3.6.1.2.1.1.6
scalar
sysName
1.3.6.1.2.1.1.5
scalar
sysObjectID
1.3.6.1.2.1.1.2
scalar
sysServices
1.3.6.1.2.1.1.7
scalar
sysUpTime
1.3.6.1.2.1.1.3
scalar
system
1.3.6.1.2.1.1
node
tcp
1.3.6.1.2.1.6
node
tcpActiveOpens
1.3.6.1.2.1.6.5
scalar
tcpAttemptFails
1.3.6.1.2.1.6.7
scalar
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 Trap PDUs which have
been generated by the SNMP protocol entity.
The textual identification of the contact person
for this managed node, together with information
on how to contact this person.
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 physical location of this node (e.g.,
`telephone closet, 3rd floor').
An administratively-assigned name for this
managed node. By convention, this is the node's
fully-qualified domain name.
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'.
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 time (in hundredths of a second) since the
network management portion of the system was last
Re-initialized.
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 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.
147
© RACOM s.r.o. – RipEX Radio modem & Router
OID mappings
Содержание RipEX 1.4
Страница 2: ......
Страница 6: ...6...
Страница 37: ...DQ Data Quality Min 180 PER Packet Error Rate Max 5 37 RACOM s r o RipEX Radio modem Router Network planning...