A single precision floating-point number. The semantics
and encoding are identical for type 'single' defined in
IEEE Standard for Binary Floating-Point,
ANSI/IEEE Std 754-1985.
The value is restricted to the BER serialization of
the following ASN.1 type:
FLOATTYPE ::= [120] IMPLICIT FloatType
(note: the value 120 is the sum of '30'h and '48'h)
The BER serialization of the length for values of
this type must use the definite length, short
encoding form.
For example, the BER serialization of value 123
of type FLOATTYPE is '9f780442f60000'h. (The tag
is '9f78'h; the length is '04'h; and the value is
'42f60000'h.) The BER serialization of value
'9f780442f60000'h of data type Opaque is
'44079f780442f60000'h. (The tag is '44'h; the length
is '07'h; and the value is '9f780442f60000'h.
We got an IMS header in the request. We validated the
timestamp and decided that the client's copy of this object is
fresh. So we generated a 304 response and sent it out to the
client.
The requested object was found in the cache. However, the
request required revalidation (due to client generated
revalidate, proxy generated revalidate or proxy generated forced
miss).
The request does not result in a cache table search.
Something in the request made us deem it non-cacheable (eg.
very long URL, a 'Cache-Control: no-store' header etc.
Count of times the cache table was searched, no matching entry
was found and a new entry was created. However, note
that sometimes, an entry is created temporarily (eg. for an IMS
request resulting in a 304) and is deleted after sending it
out to the client (delayed delete).
Current maximum possible number of entries in the vrrpTable,
which is 255 * (number of interfaces for which a cluster is
defined). 255 is the max number of VIPs in a cluster.
An entry in the vrrpTable. Each entry represents a cluster VIP
and not the cluster itself. If a cluster has n VIPs, then there
will be n entries for the cluster in the vrrpTable (0 <= n <= 255).
All the entries in the vrrpTable belonging to a single cluster
will have the same values for all the fields except
clusterVirIndex and clusterVirAddr
The number of syslog notifications that
have been sent. This number may include notifications
that were prevented from being transmitted due to
reasons such as resource limitations and/or
non-connectivity. If one is receiving notifications,
one can periodically poll this object to determine if
any notifications were missed. If so, a poll of the
logHistoryTable might be appropriate.
Indicates whether logMessageGenerated notifications
will or will not be sent when a syslog message is
generated by the device. Disabling notifications
does not prevent syslog messages from being added
to the logHistoryTable.
Indicates which syslog severity levels will be
processed. Any syslog message with a severity value
greater than this value will be ignored by the agent.
note: severity numeric values increase as their
severity decreases, e.g. error(3) is more severe than
debug(7).
The upper limit on the number of entries that the
logHistoryTable may contain. A value of 0 will
prevent any history from being retained. When this
table is full, the oldest entry will be deleted and
a new one will be created.
A monotonically increasing integer for the sole
purpose of indexing messages. When it reaches the
maximum value the agent flushes the table and wraps
the value back to 1.
The text of the message. If the text of the message
exceeds 255 bytes, the message will be truncated to
254 bytes and a '*' character will be appended,
indicating that the message has been truncated.
When a syslogTrap message is generated by the device a
syslogTrap notification is sent. The
sending of these notifications can be enabled/disabled
via the logNotificationsEnabled object.
A unique value for each interface. Its value
ranges between 1 and the value of infNumber. 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.
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, which were not addressed to a multicast
or broadcast address at this sub-layer.
The number of packets, delivered by this sub-layer to a
higher (sub-)layer, which were addressed to a multicast or
broadcast address at this sub-layer.
The number of inbound packets which were chosen to be
discarded even though no errors had been detected to prevent
their being deliverable to a higher-layer protocol. One
possible reason for discarding such a packet could be to
free up buffer space.
For packet-oriented interfaces, the number of inbound
packets that contained errors preventing them from being
deliverable to a higher-layer protocol. For character-
oriented or fixed-length interfaces, the number of inbound
transmission units that contained errors preventing them
from being deliverable to a higher-layer protocol.
For packet-oriented interfaces, the number of packets
received via the interface which were discarded because of
an unknown or unsupported protocol. For character-oriented
or fixed-length interfaces that support protocol
multiplexing the number of transmission units received via
the interface which were discarded because of an unknown or
unsupported protocol. For any interface that does not
support protocol multiplexing, this counter will always be
0.
The total number of packets that higher-level protocols
requested be transmitted, and which were not addressed to a
multicast or broadcast address at this sub-layer, including
those that were discarded or not sent.
The total number of packets that higher-level protocols
requested be transmitted, and which were addressed to a
multicast or broadcast address at this sub-layer, including
those that were discarded or not sent.
For packet-oriented interfaces, the number of outbound
packets that could not be transmitted because of errors.
For character-oriented or fixed-length interfaces, the
number of outbound transmission units that could not be
transmitted because of errors.
The 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.
The 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.
The number of times ClickTCP connections have made a direct
transition to the CLOSED state from either the SYN-SENT
state or the SYN-RCVD state, plus the number of times TCP
connections have made a direct transition to the LISTEN
state from the SYN-RCVD state.
The total number of ClickTCP segments received, including those
received in error. This count includes segments received on
currently established connections.
The total number of segments retransmitted - that is, the
number of ClickTCP segments transmitted containing one or more
previously transmitted octets.
A conceptual row of the ctcpConnTable containing information
about a particular current TCP connection. Each row of this
table is transient, in that it ceases to exist when (or soon
after) the connection makes the transition to the CLOSED
state.
The local IP address for this TCP connection. In the case
of a connection in the listen state which is willing to
accept connections for any IP interface associated with the
node, the value 0.0.0.0 is used.
The local 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.
