Monitoring the Protocol Statistics for the Mobile IP Home Agent Traffic

Purpose

Display the protocol statistics for the Mobile IP home agent traffic, including advertisements, solicitations, registrations, registration errors, and security violations. Use the optional delta keyword to display the baseline-relative statistics for the Mobile IP home agent traffic.

Action

To display the protocol statistics for the Mobile IP home agent traffic:

host1#show ip mobile traffic
Home Agent Registrations:
Registration requests:
Register: 0
Copyright © 2012, Juniper Networks, Inc. 321
Chapter 14: Configuring the Mobile IP Home Agent
Deregister: 0
Accept: 0
Registration rejects:
Denied: 0
Unspecified: 0
Unknown HA: 0
Administratively prohibited: 0
No Resources: 0
Authentication failed MN: 0
FA: 0
Bad identification: 0
Bad request form: 0
Unavailable encapsulation: 0
No reverse tunnel: 0

Meaning

Table 54 lists the output fields for the show ip mobile traffic command.

Table 54: show ip mobile traffic Output Fields

Field Name

Field Description

Registration requests

Total number of registration requests, de-registration requests, and accepted registration requests for mobile nodes:

  • Register—Number of registration requests received by the Mobile IP home agent
  • Deregister—Number of de-registration requests received by the Mobile IP home agent
  • Accept—Number of registration requests accepted by the Mobile IP home agent

Registration rejects

Total number of and reasons for unsuccessful responses to registration requests:

  • Denied—Number of registration requests denied by the Mobile IP home agent
  • Unspecified—Number of registration requests rejected for an unspecified reason, such as an internal communication failure
  • Unknown HA—Number of registration requests rejected because of an unknown Mobile IP home agent address, or because the specified Mobile IP home agent address is not serviced by this Mobile IP home agent
  • Administratively prohibited—Number of registration requests prohibited for administrative reasons, such as the broadcast or B bit being set without the corresponding D bit, or a denial by the registration filters
  • No Resources—Number of registration requests rejected due to insufficient resources, such as a full binding table, an inability to create a tunnel, or an inability of the IP subscriber management application to create a dynamic subscriber interface
  • Authentication failed MN—Number of registration requests rejected because the mobile node failed authentication
  • FA—Number of registration requests rejected because the foreign agent failed authentication
  • Bad identification—Number of registration requests rejected because the registration ID field is out of range
  • Bad request form—Number of registration requests rejected because of a malformed request
  • Unavailable encapsulation—Number of registration requests rejected because of unsupported encapsulation
  • No reverse tunnel—Number of registration requests rejected because reverse tunneling is disabled

Related Documentation