RFC 4295
Mobile IPv6 Management Information Base
mip6HCNodeInPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams received from the
mobile node by the MIPv6 entity. This will include
datagrams with the Mobility Header or the Home
Address option in the Destination Option extension
header (Next Header value = 60). It will also
include the IPv6 datagrams that are reverse tunneled
to a home agent from the mobile node's home address.
This object is a 64-bit version of mip6NodeInPkts.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 4 }
mip6NodeOutOctets OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
sent to the mobile node by the MIPv6 entity. This
will include datagrams with the Mobility Header
or the type 2 Routing Header. It will also include
the IPv6 datagrams that are tunneled by a home agent
to the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 5 }
mip6HCNodeOutOctets OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of octets in the MIPv6 datagrams
sent to the mobile node by the MIPv6 entity. This
will include datagrams with the Mobility Header
or the type 2 Routing Header. It will also include
the IPv6 datagrams that are tunneled by a home agent
to the mobile node.
This object is a 64-bit version of mip6NodeOutOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 6 }
mip6NodeOutPkts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent to the mobile
node by the MIPv6 entity. This will include
datagrams with the Mobility Header or the type 2
Routing Header. It will also include the IPv6
datagrams that are tunneled by a home agent to the
mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 7 }
mip6HCNodeOutPkts OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of MIPv6 datagrams sent to the mobile
node by the MIPv6 entity. This will include
datagrams with the Mobility Header or the type 2
Routing Header. It will also include the IPv6
datagrams that are tunneled by a home agent to the
mobile node.
This object is a 64-bit version of mip6NodeOutOctets.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6NodeCtrDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1, 6.3, 6.4, 10.4.5"
::= { mip6NodeTrafficEntry 8 }
mip6NodeCtrDiscontinuityTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime on the most recent occasion
at which any one or more of the counters in this row
suffered a discontinuity. The relevant counters are
the specific instances of any Counter32 or Counter64
objects in this row.
If no such discontinuities have occurred since the
last re-initialization of the local management
subsystem, then this object contains a zero value.
"
::= { mip6NodeTrafficEntry 9 }
-- mip6MnSystem Group
mip6MnHomeAddressTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6MnHomeAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing registration status for all the
home addresses pertaining to the mobile node.
"
::= { mip6MnSystem 1 }
mip6MnHomeAddressEntry OBJECT-TYPE
SYNTAX Mip6MnHomeAddressEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The registration status for a home address.
Implementors need to be aware that if the total
number of octets in mip6MnHomeAddress
exceeds 113, then OIDs of column instances in
this row will have more than 128 sub-identifiers and
cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6MnHomeAddressType, mip6MnHomeAddress }
::= { mip6MnHomeAddressTable 1 }
Mip6MnHomeAddressEntry ::=
SEQUENCE {
mip6MnHomeAddressType InetAddressType,
mip6MnHomeAddress InetAddress,
mip6MnHomeAddressState INTEGER
}
mip6MnHomeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnHomeAddress that
follows.
"
::= { mip6MnHomeAddressEntry 1 }
mip6MnHomeAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A unicast routable address assigned to the mobile
node. This is used as the 'permanent address' of the
mobile node in the sense that it remains unchanged
regardless of the mobile node's current point of
attachment. If mobile node doesn't have a home
address assigned yet, then this object will take the
default 'unspecified' value ::0.
The type of the address represented by this object
is specified by the corresponding
mip6MnHomeAddressType object.
"
REFERENCE
"RFC 3775 : Section 3.2"
::= { mip6MnHomeAddressEntry 2 }
mip6MnHomeAddressState OBJECT-TYPE
SYNTAX INTEGER {
unknown(1),
home(2),
registered(3),
pending(4),
isolated(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the state of the mobile node:
unknown -- The state of the mobile node
cannot be determined.
home -- mobile node is on the home network.
registered -- mobile node is on a foreign network
and is registered with the home
agent.
pending -- mobile node has sent registration
request to the home agent and is
waiting for the reply.
isolated -- mobile node is isolated from network,
i.e., it is not in its home network,
it is not registered, and no
registration ack is pending.
"
::= { mip6MnHomeAddressEntry 3 }
-- Mobile Node Discovery and Advertisement Group Counters
mip6MnDiscoveryRequests OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Dynamic Home Agent Address
Discovery Requests sent by the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1"
::= { mip6MnConf 1 }
mip6MnDiscoveryReplies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Dynamic Home Agent Address
Discovery Replies received by the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1"
::= { mip6MnConf 2 }
mip6MnDiscoveryTimeouts OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Dynamic Home Agent Address
Discovery Requests that timed out.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.1, 12"
::= { mip6MnConf 3 }
mip6MnPrefixSolicitationsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Mobile Prefix Solicitations
sent by the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.5, 11.4.2"
::= { mip6MnConf 4 }
mip6MnPrefixAdvsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Mobile Prefix Advertisements
received by the mobile node. This will include the
ICMP Mobile Prefix Advertisements that failed the
validity checks.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.6, 11.4.3"
::= { mip6MnConf 5 }
mip6MnPrefixAdvsIgnored OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Mobile Prefix Advertisements
discarded by the validity check.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.6, 11.4.3"
::= { mip6MnConf 6 }
mip6MnMovedToFN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile node has detected
movement to a foreign network from another
foreign network or from the home network, has
reconstructed its care-of address and has initiated
the care-of address registration process.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.5.1"
::= { mip6MnConf 7 }
mip6MnMovedToHN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of times the mobile node has detected
movement from a foreign network to its home
network.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.5.4"
::= { mip6MnConf 8 }
-- Mobile Node Registration Group
-- Registration table of mobile node
mip6MnBLTable OBJECT-TYPE
SYNTAX SEQUENCE OF Mip6MnBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table corresponds to the Binding Update List
(BL) that is maintained by the mobile node. The list
holds an item for every binding that the mobile node
has established or is trying to establish. Both
correspondent and home registrations are included in
this table. Entries from the table are deleted as
the lifetime of the binding expires.
"
REFERENCE
"RFC 3775 : Section 4.5, 11.1"
::= { mip6MnRegistration 1 }
mip6MnBLEntry OBJECT-TYPE
SYNTAX Mip6MnBLEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about a Binding Update sent by the
mobile node either to its home agent or to one of
its correspondent nodes.
Implementors need to be aware that if the total
number of octets in mip6MnHomeAddress and
mip6MnBLNodeAddress exceeds 111, then OIDs of column
instances in this row will have more than 128
sub-identifiers and cannot be accessed using
SNMPv1, SNMPv2c, or SNMPv3.
"
INDEX { mip6MnHomeAddressType,
mip6MnHomeAddress,
mip6MnBLNodeAddressType,
mip6MnBLNodeAddress
}
::= { mip6MnBLTable 1 }
Mip6MnBLEntry ::= SEQUENCE {
mip6MnBLNodeAddressType InetAddressType,
mip6MnBLNodeAddress InetAddress,
mip6MnBLCOAType InetAddressType,
mip6MnBLCOA InetAddress,
mip6MnBLLifeTimeRequested Unsigned32,
mip6MnBLLifeTimeGranted Unsigned32,
mip6MnBLMaxSeq Unsigned32,
mip6MnBLTimeSent DateAndTime,
mip6MnBLAccepted TruthValue,
mip6MnBLAcceptedTime DateAndTime,
mip6MnBLRetransmissions Gauge32,
mip6MnBLDontSendBUFlag TruthValue
}
mip6MnBLNodeAddressType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnBLNodeAddress
that follows.
"
::= { mip6MnBLEntry 1 }
mip6MnBLNodeAddress OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The address of the agent as used in the destination
address of the Binding Update. The agent
may be a home agent or a correspondent node.
The type of the address represented by this object
is specified by the corresponding
mip6MnBLNodeAddressType object.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 2 }
mip6MnBLCOAType OBJECT-TYPE
SYNTAX InetAddressType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The InetAddressType of the mip6MnBLCOA that follows.
"
::= { mip6MnBLEntry 3 }
mip6MnBLCOA OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Care-of address that the mobile node intends to
register in the Binding Update request.
The type of the address represented by this object
is specified by the corresponding mip6MnBLCOAType
object.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 4 }
mip6MnBLLifeTimeRequested OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime requested by the mobile node (in
seconds) in the Binding Update.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 5 }
mip6MnBLLifeTimeGranted OBJECT-TYPE
SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The lifetime granted to the mobile node for this
binding. This field will be inaccessible if the
Binding Update request has not been accepted.
The lifetime remaining (lR) can be calculated using
the current time (cT), mip6MnBLAcceptedTime (aT) and
mip6MnBLLifeTimeGranted (lG) as follows:
lR = lG - (cT - aT).
When lR is zero, this entry will be deleted from the
Binding Update List and consequently from this
table.
"
::= { mip6MnBLEntry 6 }
mip6MnBLMaxSeq OBJECT-TYPE
SYNTAX Unsigned32 (0..65536)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The maximum value of the Sequence Number field sent
in previous Binding Updates to this destination.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 7 }
mip6MnBLTimeSent OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time when the last (re-)transmission occurred."
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 8 }
mip6MnBLAccepted OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) if the mobile node has received a
binding acknowledgment indicating that service has
been accepted (status code 0 or 1); false(2)
otherwise. false(2) implies that the registration
is still pending.
"
::= { mip6MnBLEntry 9 }
mip6MnBLAcceptedTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time at which the mobile node receives a binding
acknowledgment indicating that Binding Update has
been accepted (status code 0 or 1);
This object will be inaccessible if the Binding
Update request is still pending.
"
::= { mip6MnBLEntry 10 }
mip6MnBLRetransmissions OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of Binding Update retransmissions.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 11 }
mip6MnBLDontSendBUFlag OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"true(1) indicates that future binding updates
will not be sent to mip6MnBLNodeAddress.
false(2) implies that binding updates will be
sent to mip6MnBLNodeAddress.
The mobile node sets this flag in the when it
receives an ICMP Parameter Problem, Code 1,
error message in response to a return
routability message or Binding Update sent to
mip6MnBLNodeAddress.
"
REFERENCE
"RFC 3775 : Section 11.1"
::= { mip6MnBLEntry 12 }
-- Mobile Node Registration Group Counters
mip6MnRegnCounters OBJECT IDENTIFIER ::= { mip6MnRegistration 2 }
mip6MnMobilityMessagesSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of mobility messages, i.e., IPv6
datagrams with Mobility Header, sent by the mobile
node. There are 3 types of mobility messages, viz.,
Home Test Init, Care-of Test Init, and Binding
Updates, that are sent by mobile nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 4.2, 6.1"
::= { mip6MnRegnCounters 1 }
mip6MnMobilityMessagesRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of mobility messages, i.e., IPv6
datagrams with Mobility Header, received by the
mobile node. There are 5 types of mobility
messages, viz., Home Test, Care-of Test, Binding
Acknowledgment, Binding Refresh Request, and Binding
Error, that are sent to mobile nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 4.2, 6.1"
::= { mip6MnRegnCounters 2 }
mip6MnBUsToHA OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates sent to the mobile
node's home agent(s).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.1"
::= { mip6MnRegnCounters 3 }
mip6MnBUAcksFromHA OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of valid binding acknowledgments
received from the mobile node's home agent(s).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.3"
::= { mip6MnRegnCounters 4 }
mip6MnBUsToCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates sent to
correspondent nodes by the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.2"
::= { mip6MnRegnCounters 5 }
mip6MnBUAcksFromCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of valid Binding Update acks
received from all the correspondent nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.3"
::= { mip6MnRegnCounters 6 }
mip6MnBindingErrorsFromCN OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Error messages received
by mobile node from CN.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
::= { mip6MnRegnCounters 7 }
mip6MnICMPErrorsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of ICMP Error messages of type ICMP
Parameter Problem, Code 1 or Code 2, received by
the mobile node from a correspondent node in
response to a return routability procedure, a
Binding Update, or a packet with the Home Address
option.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.3.5"
::= { mip6MnRegnCounters 8 }
mip6MnBRRequestsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Refresh requests
received by the mobile node from correspondent
nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 11.7.4"
::= { mip6MnRegnCounters 9 }
-- Registration Group counters used for Correspondent Node
mip6CnGlobalStats OBJECT IDENTIFIER ::= { mip6CnStats 1 }
mip6CnHomeTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Home Test Init messages received.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.1"
::= { mip6CnGlobalStats 1 }
mip6CnHomeTestsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Home Test messages sent. If a Home
Test Init message is found to be valid, a Home Test
message will be generated and sent. Otherwise the
Home Test message is silently discarded.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.3"
::= { mip6CnGlobalStats 2 }
mip6CnCareOfTestInitsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Care-of Test Init messages received.
"
REFERENCE
"RFC 3775 : Section 9.4.2"
::= { mip6CnGlobalStats 3 }
mip6CnCareOfTestsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Care-of Test messages sent. If a
Care-of Test Init message is found to be valid, a
Care-of Test message will be generated and sent.
Otherwise the Care-of Test message is silently
discarded.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.4.4"
::= { mip6CnGlobalStats 4 }
mip6CnBUsRecd OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates received by the
correspondent node from mobile nodes.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1"
::= { mip6CnGlobalStats 5 }
mip6CnBUAcksSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of acknowledgments sent by the
correspondent node for the Binding Updates received.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.4"
::= { mip6CnGlobalStats 6 }
mip6CnBRsSent OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Refresh Request messages
sent by the correspondent node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.5"
::= { mip6CnGlobalStats 7 }
mip6CnBindingErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Error messages sent by the
correspondent node to the mobile node.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.3.3"
::= { mip6CnGlobalStats 8 }
mip6CnBUsAccepted OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates accepted by the
correspondent node. If a Binding Acknowledgment
message is sent for the Binding Update request,
the Status code field in the message will have
a value less than 128.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, 9.5.4"
::= { mip6CnGlobalStats 9 }
mip6CnBUsRejected OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected
by the correspondent node. If a Binding
Acknowledgment message has been sent for the Binding
Update request, the Status code field in the
message will have a value greater than or equal to
128. Otherwise the Binding Update request will be
silently discarded.
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 9.5.1, 9.5.4"
::= { mip6CnGlobalStats 10 }
mip6CnReasonUnspecified OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the correspondent node with status code in the
Binding Acknowledgment message indicating 'reason
unspecified' (Code 128).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
::= { mip6CnGlobalStats 11 }
mip6CnInsufficientResource OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
the correspondent node with status code in the
Binding Acknowledgment message indicating
'insufficient resources' (Code 130).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8"
::= { mip6CnGlobalStats 12 }
mip6CnHomeRegnNotSupported OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Update requests rejected by
correspondent node with status code in the Binding
Acknowledgment message indicating 'home registration
not supported' (Code 131).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 10.3.1"
::= { mip6CnGlobalStats 13 }
mip6CnSeqNumberOutOfWindow OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgment message indicating 'sequence number
out of window' (Code 135).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 14 }
mip6CnExpiredHomeNonceIndex OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of Binding Updates rejected by
correspondent node with status code in the Binding
Acknowledgment message indicating 'expired home
nonce index' (Code 136).
Discontinuities in the value of this counter can
occur at re-initialization of the management system,
and at other times as indicated by the value of
mip6CounterDiscontinuityTime.
"
REFERENCE
"RFC 3775 : Section 6.1.8, 9.5.1"
::= { mip6CnGlobalStats 15 }