SYS-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
211
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
211 total| Object Name |
|---|
ngcan OBJECT IDENTIFIER .1.3.6.1.4.1.1978 |
SNMPv2-TC Unknown .1.3.6.1.4.1.1978 |
tiger OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2 |
sysMIB OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18 |
system OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.1 |
sysDescrA textual description of the Tiger. This value
corresponds to the description of the unit obtained from the
configuration tool. This object should only contain
printable ASCII characters.rw DisplayString .1.3.6.1.4.1.1978.2.18.1.1 |
sysObjectIDThe 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. Tiger is identified
by the subtree (1.3.6.1.4.1.1978.2.18.1.2.0)ro OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.1.2 |
sysUpTimeThe time (in hundredths of a second) since the
system was last re-initialized.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.1978.2.18.1.3 |
sysContactThe textual identification of the contact person
for this managed node, together with information
on how to contact this person. This will normally
be filled in via the .cfg file as generated by the
configuration tool.rw DisplayString .1.3.6.1.4.1.1978.2.18.1.4 |
sysNameAn administratively-assigned name for this managed node
as identified from the .cfg file that was filled in by
the configuration tool.
By convention, this is the node's fully-qualified domain name.
This parameter is also used as the prompt for TELNET sessions
to help identify the Tiger.rw DisplayString .1.3.6.1.4.1.1978.2.18.1.5 |
sysLocationThe physical location of this node
as identified from the .cfg file that was filled in by
the configuration tool. (e.g., `telephone closet, 3rd floor').rw DisplayString .1.3.6.1.4.1.1978.2.18.1.6 |
sysServicesA 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.ro INTEGER .1.3.6.1.4.1.1978.2.18.1.7 |
interfaces OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.2 |
ifNumberThe number of network interfaces (regardless of
their current state) present on this system.ro INTEGER .1.3.6.1.4.1.1978.2.18.2.1 |
ifTableA list of interface entries. The number of
entries is given by the value of ifNumber. SEQUENCE OF IfEntry .1.3.6.1.4.1.1978.2.18.2.2 |
ifEntryAn interface entry containing objects at the
subnetwork layer and below for a particular
interface. IfEntry .1.3.6.1.4.1.1978.2.18.2.2.1 |
ifIndexA 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.1 |
ifDescrA 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.rw DisplayString .1.3.6.1.4.1.1978.2.18.2.2.1.2 |
ifTypeThe type of interface, distinguished according to the physical/link
protocol(s) immediately `below' the network layer in the protocol stack.rw Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.3 |
ifMtuThe 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.4 |
ifSpeedAn 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.ro Gauge32 .1.3.6.1.4.1.1978.2.18.2.2.1.5 |
ifPhysAddressThis information is required for configuration only when BOOTP support is enabled
in the TIGER configuration tool in order to properly create a bootptab record.
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.
Although it is defined as a writable variable, TIGER may silently discard that
information. If the physical address given does not match the actual address,
an error message may be shown.
For Ethernet interfaces on TIGER, the leading 3 bytes should be: 004003.
For Token Ring Interfaces, the leading 3 bytes should be: 0000F6.
If you enter only the last 3 bytes of the MAC address, the configuration tool
will automatically add the leading 3 bytes.rw PhysAddress (SNMPv2-TC) .1.3.6.1.4.1.1978.2.18.2.2.1.6 |
ifAdminStatusThe desired state of the interface.
The testing(3) state indicates that no operational packets can be passed.rw Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.7 |
ifOperStatusThe current operational state of the interface.
testing - indicates that no operational packets can be passed.
up - normal operation
down-L2 - down due to a level 2 failure
dowm-modem - down due to modem control signals
- (Token Ring - transmitting beacon frames or rx beaconing, signal loss)
down-other - down for some other reason
- (Token Ring - no status yet received, i.e. unknown status)
up-blocktx - normal; but Tiger received a flow control signal preventing it from sending data
up-preventrx - normal; but Tiger sent a flow control signal to stop the other end from sending data
up-bothflow - normal; but Tiger received a flow control signal preventing it from sending data AND
sent a flow control signal to stop the other end from sending data
cts-failure - RTS was requested, but CTS never came (probably detected via poll timeout)
dcd-failure - DCD dropped while receiving data, OR
- unable to poll because other ends is still transmitting (polled protocols only).
hardware-failure - missing FPGA
(Token Ring: PCMCIA card missing)
up-isolated - (Token Ring: Single station on the ring)ro Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.8 |
ifLastChangeThe 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.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.1978.2.18.2.2.1.9 |
ifInOctetsThe total number of octets received on the interface, including framing characters.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.10 |
ifInUcastPktsThe number of subnetwork-unicast packets delivered to a higher-layer protocol.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.11 |
ifInNUcastPktsThe number of non-unicast (i.e., subnetwork-broadcast or subnetwork-multicast)
packets delivered to a higher-layer protocol.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.12 |
ifInDiscardsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.13 |
ifInErrorsThe number of inbound packets that contained errors preventing them from being
deliverable to a higher-layer protocol.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.14 |
ifInUnknownProtosThe number of packets received via the interface which were discarded because
of an unknown or unsupported protocol.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.15 |
ifOutOctetsThe total number of octets transmitted out of the interface, including framing characters.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.16 |
ifOutUcastPktsThe total number of packets that higher-level protocols requested be transmitted
to a subnetwork-unicast address, including those that were discarded or not sent.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.17 |
ifOutNUcastPktsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.18 |
ifOutDiscardsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.19 |
ifOutErrorsThe number of outbound packets that could not be transmitted because of errors.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.20 |
ifOutQLenThe length of the output packet queue (in packets).ro Gauge32 .1.3.6.1.4.1.1978.2.18.2.2.1.21 |
ifSpecificA 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.ro OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.2.2.1.22 |
ifInMulticastPktsThe number of packets, delivered by this sub-layer to a higher (sub-)layer,
which were addressed to a multicast address at this sub-layer.
For a MAC layer protocol, this includes both Group and Functional addresses.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.23 |
ifInBroadcastPktsThe number of packets, delivered by this sub-layer to a higher (sub-)layer,
which were addressed to a broadcast address at this sub-layer.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.24 |
ifOutMulticastPktsThe total number of packets that higher-level protocols requested be transmitted,
and which were addressed to a multicast address at this sub-layer, including those
that were discarded or not sent. For a MAC layer protocol, this includes both
Group and Functional addresses.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.25 |
ifOutBroadcastPktsThe total number of packets that higher-level protocols requested be transmitted,
and which were addressed to a broadcast address at this sub-layer, including those
that were discarded or not sent.ro Counter .1.3.6.1.4.1.1978.2.18.2.2.1.26 |
ifStateChangeTrapEnableIndicates whether ifStateChange traps should be generated for this interface.
By default, this object should have the value enabled for interfaces which do
not operate on 'top' of any other interface (as defined in the ifStackTable),
and disabled otherwise.rw Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.27 |
ifConnectorPresentThis object has the value 'true(1)' if the interface sublayer has a physical
connector and the value 'false(2)' otherwise.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1978.2.18.2.2.1.28 |
ifClearStatsWhen set to 'clear' all of the interface statistics are cleared to zero.
It will also force a clearing of all protocol, and 'user' statistics that
are related to this interface.
Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8)
When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:
1/ all of the statistics have actually been zeroed, and
2/ ifClearStatsTime has been updated with the correct time.
Should an NMS read the object and receive a 'cleared' indication, the SNMP agent
will set this object to 'cleared-confirmed'. This aids the NMS in determining
whether or not the agent successfully received subsequent clear request.
Normal operation would be:
NMS Agent
set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <
Rules:
1/ NMS must read 'cleared-confirmed' BEFORE attempting
to set 'clear'.
2/ After setting 'clear' the NMS must read 'cleared'.
then the NMS must read 'cleared-confirmed'.
In this manner, if a 'clear' command was missed by the agent,
the variable will still be set to either 'cleared' or 'cleared-confirmed'.rw Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.29 |
ifClearStatsTimeThe number of ticks when the Tiger last received a ifClearStats command.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.1978.2.18.2.2.1.30 |
ifErrorRateTrapEnableIndicates whether ifErrorRate traps should be generated for this interface.
In addition to enabling the trap via this object, thresholds must also be set.rw Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.31 |
ifErrorRateIntervalThe amount of time over which any error rate is calculated.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.32 |
ifErrorInLowThresholdIf the number of input errors drops below the low water mark (threshold)
over the interval defined by 'ifErrorRateInterval' then a trap may be
generated if enabled by 'ifErrorRateTrapEnable'.
What errors constitute as input errors is dependant on the interface being monitored.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.33 |
ifErrorInHighThresholdIf the Low water mark (threshold) has been reached, this defines the other
end of the hysterisis curve, when more than 'ifErrorInHighThreshold' number
of errors have occured over the measurement interval of 'ifErrorRateInterval'
If this value is reached, then a trap may be generated if enabled by
'ifErrorRateTrapEnable'.
ifErrorInLowThreshold <= ifErrorInHighThreshold
What errors constitute as input errors is dependant on the interface being monitored.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.34 |
ifErrorOutLowThresholdIf the number of output errors drops below the low water mark (threshold)
over the interval defined by 'ifErrorRateInterval' then a trap may be
generated if enabled by 'ifErrorRateTrapEnable'.
ifErrorOutLowThreshold <= ifErrorOutHighThreshold
What errors constitute as output errors is dependant on the interface being monitored.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.35 |
ifErrorOutHighThresholdIf the Low water mark (threshold) has been reached, this defines the other
end of the hysterisis curve, when more than 'ifErrorOutHighThreshold' number
of errors have occured over the measurement interval of 'ifErrorRateInterval'
If this value is reached, then a trap may be generated if enabled by
'ifErrorRateTrapEnable'.
ifErrorOutLowThreshold <= ifErrorOutHighThreshold
What errors constitute as output errors is dependant on the interface being monitored.rw INTEGER .1.3.6.1.4.1.1978.2.18.2.2.1.36 |
ifErrTypeInforms the NMS of the reason for the ifErrorRate trap that was received.
When read asynchronously, it also indicates the last known state of this interface entry.ro Enumeration .1.3.6.1.4.1.1978.2.18.2.2.1.37 |
ip OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.3 |
ipForwardingThe 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.rw Enumeration .1.3.6.1.4.1.1978.2.18.3.1 |
ipDefaultTTLThe 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.2 |
ipInReceivesThe total number of input datagrams received from
interfaces, including those received in error.ro Counter .1.3.6.1.4.1.1978.2.18.3.3 |
ipInHdrErrorsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.4 |
ipInAddrErrorsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.5 |
ipForwDatagramsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.6 |
ipInUnknownProtosThe number of locally-addressed datagrams
received successfully but discarded because of an
unknown or unsupported protocol.ro Counter .1.3.6.1.4.1.1978.2.18.3.7 |
ipInDiscardsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.8 |
ipInDeliversThe total number of input datagrams successfully
delivered to IP user-protocols (including ICMP).ro Counter .1.3.6.1.4.1.1978.2.18.3.9 |
ipOutRequestsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.10 |
ipOutDiscardsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.11 |
ipOutNoRoutesThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.12 |
ipReasmTimeoutThe maximum number of seconds which received
fragments are held while they are awaiting
reassembly at this entity.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.13 |
ipReasmReqdsThe number of IP fragments received which needed
to be reassembled at this entity.ro Counter .1.3.6.1.4.1.1978.2.18.3.14 |
ipReasmOKsThe number of IP datagrams successfully re-assembled.ro Counter .1.3.6.1.4.1.1978.2.18.3.15 |
ipReasmFailsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.16 |
ipFragOKsThe number of IP datagrams that have been
successfully fragmented at this entity.ro Counter .1.3.6.1.4.1.1978.2.18.3.17 |
ipFragFailsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.18 |
ipFragCreatesThe number of IP datagram fragments that have
been generated as a result of fragmentation at
this entity.ro Counter .1.3.6.1.4.1.1978.2.18.3.19 |
ipAddrTableThe table of addressing information relevant to
this entity's IP addresses. SEQUENCE OF IpAddrEntry .1.3.6.1.4.1.1978.2.18.3.20 |
ipAddrEntryThe addressing information for one of this
entity's IP addresses. IpAddrEntry .1.3.6.1.4.1.1978.2.18.3.20.1 |
ipAdEntAddrThe IP address to which this entry's addressing information pertains.
If this is a PPP port, an IP address of 0.0.0.0 signifies that
IP address negotiation will occur on this link. If negotiation is enabled,
the net mask will be forced to a correct value that is appropriate for that
class of address.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.20.1.1 |
ipAdEntIfIndexThe 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.20.1.2 |
ipAdEntNetMaskThe 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.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.20.1.3 |
ipAdEntBcastAddrThe 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.20.1.4 |
ipAdEntReasmMaxSizeThe size of the largest IP datagram which this
entity can re-assemble from incoming IP fragmented
datagrams received on this interface.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.20.1.5 |
ipNetToMediaTableThe IP Address Translation table used for mapping
from IP addresses to physical addresses. SEQUENCE OF IpNetToMediaEntry .1.3.6.1.4.1.1978.2.18.3.22 |
ipNetToMediaEntryEach entry contains one IpAddress to `physical' address equivalence. IpNetToMediaEntry .1.3.6.1.4.1.1978.2.18.3.22.1 |
ipNetToMediaIfIndexThe 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.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.22.1.1 |
ipNetToMediaPhysAddressThe media-dependent `physical' address.rw PhysAddress (SNMPv2-TC) .1.3.6.1.4.1.1978.2.18.3.22.1.2 |
ipNetToMediaNetAddressThe IpAddress corresponding to the media-dependent `physical' address.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.22.1.3 |
ipNetToMediaTypeThe 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.rw Enumeration .1.3.6.1.4.1.1978.2.18.3.22.1.4 |
ipRoutingDiscardsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.3.23 |
ipClearStatsWhen set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics
are cleared to zero.
When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:
1/ all of the statistics have actually been zeroed, and
2/ ipClearStatsTime has been updated with the correct time.
Should an NMS read the object and receive a 'cleared' indication, the SNMP agent
will set this object to 'cleared-confirmed'. This aids the NMS in determining
whether or not the agent successfully received subsequent clear request.
Normal operation would be:
NMS Agent
set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <
Rules:
1/ NMS must read 'cleared-confirmed' BEFORE attempting
to set 'clear'.
2/ After setting 'clear' the NMS must read 'cleared'.
then the NMS must read 'cleared-confirmed'.
In this manner, if a 'clear' command was missed by the agent,
the variable will still be set to either 'cleared' or 'cleared-confirmed'.rw Enumeration .1.3.6.1.4.1.1978.2.18.3.24 |
ipClearStatsTimeThe number of ticks when the Tiger last received a ipClearStats command.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.1978.2.18.3.25 |
ipForward OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.3.26 |
ipForwardNumberThe number of current ipForwardTable entries that are not invalid.ro Gauge .1.3.6.1.4.1.1978.2.18.3.26.1 |
ipForwardTableThis entity's IP Routing table. SEQUENCE OF IpForwardEntry .1.3.6.1.4.1.1978.2.18.3.26.2 |
ipForwardEntryA particular route to a particular destination, under a particular policy. IpForwardEntry .1.3.6.1.4.1.1978.2.18.3.26.2.1 |
ipForwardDestThe destination IP address of this route. An entry
with a value of 0.0.0.0 is considered a default route.
This object may not take a Multicast (Class D) address value.
Any assignment (implicit or otherwise) of an instance of this
object to a value x must be rejected if the bitwise logical-AND
of x with the value of the corresponding instance of the
ipForwardMask object is not equal to x.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.26.2.1.1 |
ipForwardMaskIndicate the mask to be logical-ANDed with the destination
address before being compared to the value in the ipForwardDest
field. For those systems that do not support arbitrary subnet
masks, an agent constructs the value of the ipForwardMask by
reference to the IP Address Class.
Any assignment (implicit or otherwise) of an instance of this
object to a value x must be rejected if the bitwise logical-AND
of x with the value of the corresponding instance of the
ipForwardDest object is not equal to ipForwardDest.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.26.2.1.2 |
ipForwardNextHopOn remote routes, the address of the next system
en route; Otherwise, 0.0.0.0.rw IpAddress .1.3.6.1.4.1.1978.2.18.3.26.2.1.4 |
ipForwardIfIndexThe ifIndex value which identifies the local interface through
which the next hop of this route should be reached.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.5 |
ipForwardMetric1The primary routing metric for this route.
The semantics of this metric are determined by the routing-protocol specified
in the route's ipForwardProto value. For static routing tables, Metric1 is
the default 'cost' (1-15) of the route when it is in the up condition. This
is compared to other possible routes for the same destination, to state the
preferred path. If this metric is not used, its value should be set to -1.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.11 |
ipForwardMetric2An alternate routing metric for this route.
The semantics of this metric are determined by the routing-protocol specified
in the route's ipForwardProto value. For static routing tables, Metric1 is
the default 'cost' (1-15) of the route when it is in the up condition. This
is compared to other possible routes for the same destination, to state the
preferred path. If this metric is not used, its value should be set to -1.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.12 |
ipForwardMetric3An alternate routing metric for this route.
The semantics of this metric are determined by the routing-protocol specified
in the route's ipForwardProto value. For static routing tables, Metric1 is
the default 'cost' (1-15) of the route when it is in the up condition. This
is compared to other possible routes for the same destination, to state the
preferred path. If this metric is not used, its value should be set to -1.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.13 |
ipForwardMetric4An alternate routing metric for this route.
The semantics of this metric are determined by the routing-protocol specified
in the route's ipForwardProto value. For static routing tables, Metric1 is
the default 'cost' (1-15) of the route when it is in the up condition. This
is compared to other possible routes for the same destination, to state the
preferred path. If this metric is not used, its value should be set to -1.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.14 |
ipForwardMetric5An alternate routing metric for this route.
The semantics of this metric are determined by the routing-protocol specified
in the route's ipForwardProto value. For static routing tables, Metric1 is
the default 'cost' (1-15) of the route when it is in the up condition. This
is compared to other possible routes for the same destination, to state the
preferred path. If this metric is not used, its value should be set to -1.rw INTEGER .1.3.6.1.4.1.1978.2.18.3.26.2.1.15 |
ipForwardTrapControlIf enabled, it allows the system to generate ipForward traps,
when the routing table changes.rw Enumeration .1.3.6.1.4.1.1978.2.18.3.26.3 |
ipForwardTrapReasonThe reason that the ipRouteChange trap was generated.
add - the entry was added.
delete - the entry was removed.
modified - the entry was modified. The metric probably changed value
due to a link going up or down).ro Enumeration .1.3.6.1.4.1.1978.2.18.3.26.4 |
icmp OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.4 |
icmpInMsgsThe total number of ICMP messages which the
entity received. Note that this counter includes
all those counted by icmpInErrors.ro Counter .1.3.6.1.4.1.1978.2.18.4.1 |
icmpInErrorsThe number of ICMP messages which the entity
received but determined as having ICMP-specific
errors (bad ICMP checksums, bad length, etc.).ro Counter .1.3.6.1.4.1.1978.2.18.4.2 |
icmpInDestUnreachsThe number of ICMP Destination Unreachable messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.3 |
icmpInTimeExcdsThe number of ICMP Time Exceeded messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.4 |
icmpInParmProbsThe number of ICMP Parameter Problem messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.5 |
icmpInSrcQuenchsThe number of ICMP Source Quench messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.6 |
icmpInRedirectsThe number of ICMP Redirect messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.7 |
icmpInEchosThe number of ICMP Echo (request) messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.8 |
icmpInEchoRepsThe number of ICMP Echo Reply messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.9 |
icmpInTimestampsThe number of ICMP Timestamp (request) messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.10 |
icmpInTimestampRepsThe number of ICMP Timestamp Reply messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.11 |
icmpInAddrMasksThe number of ICMP Address Mask Request messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.12 |
icmpInAddrMaskRepsThe number of ICMP Address Mask Reply messages received.ro Counter .1.3.6.1.4.1.1978.2.18.4.13 |
icmpOutMsgsThe total number of ICMP messages which this
entity attempted to send. Note that this counter
includes all those counted by icmpOutErrors.ro Counter .1.3.6.1.4.1.1978.2.18.4.14 |
icmpOutErrorsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.4.15 |
icmpOutDestUnreachsThe number of ICMP Destination Unreachable messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.16 |
icmpOutTimeExcdsThe number of ICMP Time Exceeded messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.17 |
icmpOutParmProbsThe number of ICMP Parameter Problem messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.18 |
icmpOutSrcQuenchsThe number of ICMP Source Quench messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.19 |
icmpOutRedirectsThe number of ICMP Redirect messages sent. For a
host, this object will always be zero, since hosts
do not send redirects.ro Counter .1.3.6.1.4.1.1978.2.18.4.20 |
icmpOutEchosThe number of ICMP Echo (request) messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.21 |
icmpOutEchoRepsThe number of ICMP Echo Reply messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.22 |
icmpOutTimestampsThe number of ICMP Timestamp (request) messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.23 |
icmpOutTimestampRepsThe number of ICMP Timestamp Reply messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.24 |
icmpOutAddrMasksThe number of ICMP Address Mask Request messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.25 |
icmpOutAddrMaskRepsThe number of ICMP Address Mask Reply messages sent.ro Counter .1.3.6.1.4.1.1978.2.18.4.26 |
tcp OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.5 |
tcpRtoAlgorithmThe algorithm used to determine the timeout value
used for retransmitting unacknowledged octets.ro Enumeration .1.3.6.1.4.1.1978.2.18.5.1 |
tcpRtoMinThe 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.
UNITS: millisecondsro INTEGER .1.3.6.1.4.1.1978.2.18.5.2 |
tcpRtoMaxThe 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.
UNITS: millisecondsro INTEGER .1.3.6.1.4.1.1978.2.18.5.3 |
tcpMaxConnThe 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.ro INTEGER .1.3.6.1.4.1.1978.2.18.5.4 |
tcpActiveOpensThe number of times TCP connections have made a
direct transition to the SYN-SENT state from the
CLOSED state.ro Counter .1.3.6.1.4.1.1978.2.18.5.5 |
tcpPassiveOpensThe number of times TCP connections have made a
direct transition to the SYN-RCVD state from the
LISTEN state.ro Counter .1.3.6.1.4.1.1978.2.18.5.6 |
tcpAttemptFailsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.5.7 |
tcpEstabResetsThe number of times TCP connections have made a
direct transition to the CLOSED state from either
the ESTABLISHED state or the CLOSE-WAIT state.ro Counter .1.3.6.1.4.1.1978.2.18.5.8 |
tcpCurrEstabThe number of TCP connections for which the
current state is either ESTABLISHED or CLOSE-WAIT.ro Gauge32 .1.3.6.1.4.1.1978.2.18.5.9 |
tcpInSegsThe total number of segments received, including
those received in error. This count includes
segments received on currently established
connections.ro Counter .1.3.6.1.4.1.1978.2.18.5.10 |
tcpOutSegsThe total number of segments sent, including
those on current connections but excluding those
containing only retransmitted octets.ro Counter .1.3.6.1.4.1.1978.2.18.5.11 |
tcpRetransSegsThe total number of segments retransmitted - that
is, the number of TCP segments transmitted
containing one or more previously transmitted
octets.ro Counter .1.3.6.1.4.1.1978.2.18.5.12 |
tcpConnTableA table containing TCP connection-specific information. SEQUENCE OF TcpConnEntry .1.3.6.1.4.1.1978.2.18.5.13 |
tcpConnEntryInformation 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. TcpConnEntry .1.3.6.1.4.1.1978.2.18.5.13.1 |
tcpConnStateThe state of this TCP connection.
NOTE: The following paragraphs are from rfc1213
and Tiger does not currently support this.
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).rw Enumeration .1.3.6.1.4.1.1978.2.18.5.13.1.1 |
tcpConnLocalAddressThe 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.ro IpAddress .1.3.6.1.4.1.1978.2.18.5.13.1.2 |
tcpConnLocalPortThe local port number for this TCP connection.ro INTEGER .1.3.6.1.4.1.1978.2.18.5.13.1.3 |
tcpConnRemAddressThe remote IP address for this TCP connection.ro IpAddress .1.3.6.1.4.1.1978.2.18.5.13.1.4 |
tcpConnRemPortThe remote port number for this TCP connection.ro INTEGER .1.3.6.1.4.1.1978.2.18.5.13.1.5 |
tcpInErrsThe total number of segments received in error (e.g., bad TCP checksums).ro Counter .1.3.6.1.4.1.1978.2.18.5.14 |
tcpOutRstsThe number of TCP segments sent containing the RST flag.ro Counter .1.3.6.1.4.1.1978.2.18.5.15 |
tcpRetransAttemptsThe number of TCP retransmision attempts before the socket connection is
declared down. The interval between attempts is fixed at approximately
7 seconds. This parameter is global for all TCP applications.
(default=6)rw INTEGER .1.3.6.1.4.1.1978.2.18.5.16 |
tcpKAIntervalThe interval of time, expressed in seconds between keepalive packets.
Keepalive packets are generated when there is no other socket traffic.
Although the operation of keepalive is defined on a per socket basis
(see autif.mib), this parameter is global for all TCP applications.
(default=30)rw INTEGER .1.3.6.1.4.1.1978.2.18.5.17 |
tcpKAAttemptsThe number of successive TCP keepalive packets sent with no reply at
tcpKAIntervals before the socket connection is declared down.
Although the operation of keepalive is defined on a per socket basis
(see autif.mib), this parameter is global for all TCP applications.
(default=3)rw INTEGER .1.3.6.1.4.1.1978.2.18.5.18 |
udp OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.6 |
udpInDatagramsThe total number of UDP datagrams delivered to UDP users.ro Counter .1.3.6.1.4.1.1978.2.18.6.1 |
udpNoPortsThe total number of received UDP datagrams for
which there was no application at the destination port.ro Counter .1.3.6.1.4.1.1978.2.18.6.2 |
udpInErrorsThe number of received UDP datagrams that could
not be delivered for reasons other than the lack
of an application at the destination port.ro Counter .1.3.6.1.4.1.1978.2.18.6.3 |
udpOutDatagramsThe total number of UDP datagrams sent from this entity.ro Counter .1.3.6.1.4.1.1978.2.18.6.4 |
udpTableA table containing UDP listener information. SEQUENCE OF UdpEntry .1.3.6.1.4.1.1978.2.18.6.5 |
udpEntryInformation about a particular current UDP listener. UdpEntry .1.3.6.1.4.1.1978.2.18.6.5.1 |
udpLocalAddressThe 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.ro IpAddress .1.3.6.1.4.1.1978.2.18.6.5.1.1 |
udpLocalPortThe local port number for this UDP listener.ro INTEGER .1.3.6.1.4.1.1978.2.18.6.5.1.2 |
snmp OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.7 |
snmpInPktsThe total number of Messages delivered to the
SNMP entity from the transport service.ro Counter .1.3.6.1.4.1.1978.2.18.7.1 |
snmpOutPktsThe total number of SNMP Messages which were
passed from the SNMP protocol entity to the
transport service.ro Counter .1.3.6.1.4.1.1978.2.18.7.2 |
snmpInBadVersionsThe total number of SNMP Messages which were
delivered to the SNMP protocol entity and were for
an unsupported SNMP version.ro Counter .1.3.6.1.4.1.1978.2.18.7.3 |
snmpInBadCommunityNamesThe total number of SNMP Messages delivered to
the SNMP protocol entity which used a SNMP
community name not known to said entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.4 |
snmpInBadCommunityUsesThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.7.5 |
snmpInASNParseErrsThe total number of ASN.1 or BER errors
encountered by the SNMP protocol entity when
decoding received SNMP Messages.ro Counter .1.3.6.1.4.1.1978.2.18.7.6 |
snmpInTooBigsThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.8 |
snmpInNoSuchNamesThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.9 |
snmpInBadValuesThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.10 |
snmpInReadOnlysThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.7.11 |
snmpInGenErrsThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.12 |
snmpInTotalReqVarsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.7.13 |
snmpInTotalSetVarsThe 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.ro Counter .1.3.6.1.4.1.1978.2.18.7.14 |
snmpInGetRequestsThe total number of SNMP Get-Request PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.15 |
snmpInGetNextsThe total number of SNMP Get-Next PDUs which have
been accepted and processed by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.16 |
snmpInSetRequestsThe total number of SNMP Set-Request PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.17 |
snmpInGetResponsesThe total number of SNMP Get-Response PDUs which
have been accepted and processed by the SNMP
protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.18 |
snmpInTrapsThe total number of SNMP Trap PDUs which have
been accepted and processed by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.19 |
snmpOutTooBigsThe 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.'ro Counter .1.3.6.1.4.1.1978.2.18.7.20 |
snmpOutNoSuchNamesThe total number of SNMP PDUs which were
generated by the SNMP protocol entity and for
which the value of the error-status is `noSuchName'.ro Counter .1.3.6.1.4.1.1978.2.18.7.21 |
snmpOutBadValuesThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.22 |
snmpOutGenErrsThe 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'.ro Counter .1.3.6.1.4.1.1978.2.18.7.24 |
snmpOutGetRequestsThe total number of SNMP Get-Request PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.25 |
snmpOutGetNextsThe total number of SNMP Get-Next PDUs which have
been generated by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.26 |
snmpOutSetRequestsThe total number of SNMP Set-Request PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.27 |
snmpOutGetResponsesThe total number of SNMP Get-Response PDUs which
have been generated by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.28 |
snmpOutTrapsThe total number of SNMP Trap PDUs which have
been generated by the SNMP protocol entity.ro Counter .1.3.6.1.4.1.1978.2.18.7.29 |
snmpEnableAuthenTrapsIndicates 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.rw Enumeration .1.3.6.1.4.1.1978.2.18.7.30 |
sysTraps OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.8 |
ifStateChangeA linkStateChange trap signifies that the sending protocol entity recognizes a change
in one of the communication links represented in the agent's configuration.
Currently this trap is only applicable to:
lapb frame_relay
sdlc token ring
u100 ethernet
alc
ppp
Other interfaces that may be supported in the future are:
apath pad x2x cap
mux frip autif TRAP-TYPE .1.3.6.1.4.1.1978.2.18.8.0.1 |
ifErrorRateA linkErrorRate trap signifies that the sending protocol entity discovered an
error rate that
in one of the communication links represented in the agent's configuration.
Currently this trap is only applicable to:
lapb frame_relay
sdlc token ring
u100 ethernet
alc
ppp
Other interfaces that may be supported in the future are:
apath pad x2x cap
mux frip autif TRAP-TYPE .1.3.6.1.4.1.1978.2.18.8.0.2 |
ipRouteChangeAn ipRouteChange trap signifies that the IP Forwarding table has been changed.
An entry was added, deleted or modified. TRAP-TYPE .1.3.6.1.4.1.1978.2.18.8.0.3 |
partyMIB OBJECT IDENTIFIER .1.3.6.1.4.1.1978.2.18.9 |
partyCommTableThe SNMP community database. SEQUENCE OF PartyCommEntry .1.3.6.1.4.1.1978.2.18.9.1 |
partyCommEntryLocally held information about a particular SNMP community. PartyCommEntry .1.3.6.1.4.1.1978.2.18.9.1.1 |
partyCommIndexA unique value for each SNMPv2 party. The value
for each SNMPv2 party must remain constant at
least from one re-initialization of the entity's
network management system to the next re-initialization.rw INTEGER .1.3.6.1.4.1.1978.2.18.9.1.1.1 |
partyCommunityThe SNMP community associated with this entry.rw DisplayString .1.3.6.1.4.1.1978.2.18.9.1.1.2 |
partyAccessIndicates the access rights of this community.rw Enumeration .1.3.6.1.4.1.1978.2.18.9.1.1.3 |
partyTrapTableThe SNMP trap destination database. SEQUENCE OF PartyTrapEntry .1.3.6.1.4.1.1978.2.18.9.2 |
partyTrapEntryLocally held information about a particular SNMP trap destination. PartyTrapEntry .1.3.6.1.4.1.1978.2.18.9.2.1 |
partyTrapIndexA unique value for each SNMP trap destination entry.rw INTEGER .1.3.6.1.4.1.1978.2.18.9.2.1.1 |
partyTAddressThe IP address by which the party receives network management traffic.rw IpAddress .1.3.6.1.4.1.1978.2.18.9.2.1.2 |
partyTPortThe port address by which the party receives network management
traffic.rw INTEGER .1.3.6.1.4.1.1978.2.18.9.2.1.3 |
partyTDomainIndicates the kind of transport service by which
the party receives network management traffic.rw Enumeration .1.3.6.1.4.1.1978.2.18.9.2.1.4 |
partyTCommunityThe SNMP community used in the trap response to this entries address.rw DisplayString .1.3.6.1.4.1.1978.2.18.9.2.1.5 |