Table Of Contents
Mobile Router DHCP Support for Dynamic CCoA and Foreign Agent Processing
Prerequisites for Mobile Router DHCP Support for DCCoA and FA Processing
Restrictions for Mobile Router DHCP Support for DCCoA and FA Processing
Information About Mobile Router DHCP Support for DCCoA and FA Processing
Mobile Router Support for SNMP Traps
Mobile Router Processing of linkUp Traps
Mobile Router Processing of linkDown Traps
Benefits of Mobile Router DHCP Support for DCCoA and FA Processing
How to Configure Mobile Router DHCP Support for DCCoA
Enabling DHCP Support for DCCoA Processing on a Mobile Router Interface
Configuring SNMP on the Mobile Router
Verifying the Dynamic CCoA Configuration
Configuration Examples for Mobile Router DHCP Support for DCCoA
Mobile Router DCCoA Acquired Through DHCP: Example
show ip mobile router interface
Mobile Router DHCP Support for Dynamic CCoA and Foreign Agent Processing
The Mobile Router DHCP Support for Dynamic Collocated Care-of Address (DCCoA) and Foreign Agent (FA) Processing feature adds support for mobile router roaming on Ethernet interfaces that acquire an IP address dynamically via the Dynamic Host Configuration Protocol (DHCP). The interface can register using this acquired IP address as a DCCoA or register using a CoA acquired from a foreign agent. This behavior is true for all platforms that support Mobile IP beginning with Cisco IOS Release 12.3(14)T.
This feature adds support for FA processing of advertisements and registrations on DHCP roaming interfaces.
A Simple Network Management Protocol (SNMP) signaling capability is also added to support this feature on the Cisco 3200 Series Mobile Access Router with a Wireless Mobile Interface Card (WMIC). The WMIC uses SNMP trap messages to signal the mobile router that the Layer 2 wireless local-area network (WLAN) is either up or down.
Feature History for the Mobile Router DHCP Support for Dynamic CCoA and Foreign Agent Processing Feature
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for Mobile Router DHCP Support for DCCoA and FA Processing
•
Restrictions for Mobile Router DHCP Support for DCCoA and FA Processing
•
Information About Mobile Router DHCP Support for DCCoA and FA Processing
•
How to Configure Mobile Router DHCP Support for DCCoA
•
Configuration Examples for Mobile Router DHCP Support for DCCoA
Prerequisites for Mobile Router DHCP Support for DCCoA and FA Processing
There are no prerequisites for DHCP support. However, if a Cisco 3200 Series Mobile Access Router is using a WMIC, the WMIC should be configured for SNMP traps. The 802.11 Layer 2 transitions (associations and disassociations) that take place on the WMIC are signaled to the mobile router via SNMP. Specifically, the Interface MIB linkUp and linkDown traps are sent to the mobile router Ethernet or VLAN interface.
See the Configuration Guide for the Cisco 3200 Series Mobile Access Router for more information on how to configure SNMP traps on the Cisco 3200 Series router.
Restrictions for Mobile Router DHCP Support for DCCoA and FA Processing
The Mobile IP process will only process SNMP signals from a WMIC. The SNMP signaling functionality for DCCoA is supported on the Cisco 3200 Series Mobile Access Router.
The linkDown and linkUp trap events will not trigger mobile router redundancy.
Information About Mobile Router DHCP Support for DCCoA and FA Processing
Before you configure this feature, you should understand the following concepts:
•
Mobile Router Support for SNMP Traps
•
Benefits of Mobile Router DHCP Support for DCCoA and FA Processing
Care-of Addresses
If a mobile router determines that it is connected to a foreign network, it acquires a CoA. This CoA is the exit point of the tunnel from the home agent toward the mobile router. The CoA is included in the mobile router's registration request and is used by the home agent to forward packets to the mobile router in its current location. There are two types of CoAs:
•
CoA acquired from a foreign agent
•
Collocated care-of address (CCoA)
A foreign agent CoA is an IP address on a foreign agent that is advertised on the foreign network being visited by a mobile router. A foreign agent CoA can be shared by other mobile routers.
A CCoA is an IP address assigned to the interface of the mobile router itself. A CCoA represents the current position of the mobile router on the foreign network and can be used by only one mobile router at a time. A CCoA can be static or dynamic. A static CCoA is a fixed IP address configured on an interface. A dynamic CCoA is an IP address dynamically acquired via DHCP on an Ethernet interface or Point-to-Point Protocol (PPP)/IP Control Protocol (IPCP) on a point-to-point serial interface.
An interface enabled for both foreign agent CoA and CCoA registration will always register a foreign agent CoA instead of a CCoA if a foreign agent CoA is available.
Mobile Router DHCP Support
This feature introduces DCCoA and foreign agent CoA support when IP addresses are obtained via DHCP on a roaming interface. Prior to the introduction of this feature, the mobile router could only support foreign agent CoA registration, static CCoA registration, and DCCoA registration through PPP/IPCP.
For both static and dynamic CCoA, the interface can be configured to exclusively use the CCoA for registration or to use a foreign agent CoA if one is available. An interface enabled for both foreign agent CoA and CCoA registration will always register a foreign agent CoA instead of a CCoA if a foreign agent CoA is available.
In the foreign agent case, when an interface first comes up, it will attempt to discover foreign agents on the link by soliciting and listening for agent advertisements. If a foreign agent is found, the mobile router will register using the advertised CoA. The interface will continue to register using a CoA as long as a foreign agent is heard. When foreign agents are not heard, CCoA processing is enabled and the interface registers its CCoA. The CCoA is the interface's statically configured or dynamically acquired primary IP address. If a foreign agent is heard again, the interface will again register using the foreign agent CoA.
In previous releases of CCoA support, the CCoA registration would begin only after a number of solicits were sent or no advertisements were heard. For faster roaming, this delay is now eliminated. Now the interface registers a foreign agent CoA if an agent advertisement is heard or it registers a CCoA if an address is acquired, depending on which event occurs first. In the case where the interface registers a CCoA first, a subsequent receipt of an agent advertisement will then cause the interface to register with the foreign agent.
To support CCoA on Ethernet interfaces, a default gateway address is required. This gateway address is used as the default gateway for CCoA registration and as a default route after the interface is registered. For static CCoA on an Ethernet interface, a default gateway address must be provided through the roaming interface CCoA configuration. See the Cisco IOS Release 12.2(15)T Mobile Networks Static Collocated Care-of Address feature documentation for configuration details.
When an interface is configured for DCCoA via DHCP, a configured gateway address is not required and the option to configure a gateway address is not offered through the command line interface (CLI). For DHCP interfaces, DCCoA registration uses the DHCP default router address and, once the interface is registered, the address is also used for the mobile router default route and gateway.
Mobile Router Support for SNMP Traps
On a Cisco 3200 Series Mobile Access Router with a WMIC, SNMP traps allow the roaming interface to determine when the connected WLAN link status changes. Without this signaling, a CCoA-registered interface would not be aware of link status changes. The mobile router must be configured to receive SNMP linkUp and linkDown traps from the WMIC and can then make roaming decisions based on the type of trap received.
Mobile Router Processing of linkUp Traps
When a linkUp trap is received on a DHCP roaming interface, the mobile router interface will either renew the current IP address or acquire a new IP address as quickly as possible. If the interface already has a DHCP-acquired IP address, the mobile router will attempt to renew it first. If renewal fails, the interface will attempt to acquire a new IP address.
If a DHCP interface is without an IP address, DHCP address acquisition begins. Address "discovery" attempts are repeated at increasing intervals (up to 60 seconds) and continue until an address is acquired. During address discovery, the interface is "IP-enabled" and IP packets can be processed. This means that foreign agent CoA advertisements can be heard and Mobile IP registration can take place, even though the interface does not have an IP address.
The new ip dhcp client mobile renew command allows you to configure the number of renewal attempts and the interval between attempts for renewing the current IP address that was acquired through DHCP. The configured values override any default values.
For roaming purposes, the roaming interface treats a linkUp trap event the same as if the roaming interface just came up. For example, solicits are sent, if foreign agent CoA-enabled, and the mobile router determines if this interface, compared to other roaming interfaces, should register. Dynamic address acquisition can trigger a DCCoA registration.
If the interface is already registered when the linkUp trap arrives and nothing else has changed that affects the registration decision, the mobile router will retain the existing registration.
Mobile Router Processing of linkDown Traps
Receipt of a valid linkDown trap starts a new, configurable reassociation hold-down timer. The purpose of this timer is to delay the mobile router's response to the trap, which is typically an attempt to register on the next best interface, for a period of time long enough for the WMIC to reassociate with another bridge or access point (AP). The mobile router remains registered during this hold-down period, foreign agent data is retained, and the mobile router interface keeps any DHCP-acquired IP address. The hold-down timer should be set to the maximum time it should take the WMIC to re-establish wireless connectivity while roaming between adjacent bridges or APs.
If a linkUp trap arrives before the hold-down timer expires, the mobile router remains registered and foreign agent data is retained. Solicits are sent to find foreign agents and the DHCP IP address renewal and discovery process begins. If the WMIC has roamed to an AP on the same subnet, address renewal should succeed.
If the hold-down timer expires or the hold-down delay was set to 0, mobile router processing proceeds as if the interface just went down. Any foreign agents heard on this interface are deleted from the foreign agent list and, if registered on the interface, the mobile router deletes the current registration and tries to register by using the next best roaming interface. Solicits are sent to find foreign agents and the DHCP IP address renewal and discovery process begins.
Benefits of Mobile Router DHCP Support for DCCoA and FA Processing
This feature allows a mobile router to roam to foreign networks where foreign agents may or may not be deployed and where IP addresses are obtained dynamically via DHCP. The SNMP trap capability permits the Cisco 3200 Series Mobile Access Router with a WMIC to respond to changes in the WLAN link status.
How to Configure Mobile Router DHCP Support for DCCoA
This section contains the following procedures:
•
Enabling DHCP Support for DCCoA Processing on a Mobile Router Interface (required)
•
Configuring SNMP on the Mobile Router (optional)
•
Verifying the Dynamic CCoA Configuration (optional)
Enabling DHCP Support for DCCoA Processing on a Mobile Router Interface
Perform this task to enable dynamic CCoA processing on a mobile router interface through DHCP.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type number
4.
ip address dhcp
5.
ip dhcp client mobile renew count number interval msec
6.
ip mobile router-service roam
7.
ip mobile router-service collocated [ccoa-only]
8.
ip mobile router-service hold-down reassociate msec
DETAILED STEPS
Configuring SNMP on the Mobile Router
If a Cisco 3200 Series Mobile Access Router is using a WMIC, the router must be configured for SNMP. The WMIC uses SNMP trap messages to signal the mobile router that the WLAN is either up or down. See the Configuration Guide for the Cisco 3200 Series Mobile Access Router for additional information on how to configure SNMP traps.
Perform this task to configure SNMP on the mobile router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
snmp-server engineID remote remote-ip-address remote-engineID-string
4.
snmp-server user username group-name remote remote-ip-address v3
DETAILED STEPS
Verifying the Dynamic CCoA Configuration
To verify the dynamic CCoA configuration, perform the following steps.
SUMMARY STEPS
1.
show ip mobile router interface
2.
show ip mobile router agent
3.
show ip mobile router registration
4.
show ip mobile router
5.
show ip mobile binding
DETAILED STEPS
Configuration Examples for Mobile Router DHCP Support for DCCoA
This section provides the following configuration example:
•
Mobile Router DCCoA Acquired Through DHCP: Example
Mobile Router DCCoA Acquired Through DHCP: Example
The following example shows a mobile router configured to obtain a CCoA dynamically through DHCP:
Mobile Router
! This is the roaming interface using DCCoAinterface FastEthernet0ip address dhcpip dhcp client mobile renew count 3 interval 20ip mobile router-service roamip mobile router-service collocatedip mobile router-service hold-down reassociate 2000!! Receive v1 or v2 trapssnmp-server community public ROsnmp-server enable traps tty!! Receive v3 trapssnmp-server engineID remote 85.85.85.3 1234snmp-server user labusr labgrp remote 85.85.85.2 v3 auth md5 <SNMP user password on WGB>snmp-server group labgrp v3 authAdditional References
The following sections provide references related to the Mobile Router DHCP Support for DCCoA and FA Processing feature.
Related Documents
Related Topic Document TitleCisco 3200 Series Mobile Access Router documentation
Configuration Guide for the Cisco 3200 Series Mobile Access Router
Mobile IP commands: complete command syntax, command mode, defaults, usage guidelines, and examples
Cisco IOS IP Command Reference, Volume 4 of 4: IP Mobility, Release 12.3T
Mobile IP commands and configuration tasks related to mobile networks
Cisco Mobile Networks feature document, Release 12.2(4)T and 12.2(13)T
Static CCoA documentation
Mobile Networks Static Collocated Care-of Address feature document, Release 12.2(15)T
Dynamic CCoA documentation
Mobile Networks Dynamic Collocated Care-of Address feature document, Release 12.3(4)T
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Command Reference
This section documents new and modified commands.
•
show ip mobile router interface
ip dhcp client mobile renew
To configure the number of renewal attempts and the interval between attempts for renewing the current IP address acquired by DHCP, use the ip dhcp client mobile renew command in interface configuration mode. To disable this functionality, use the no form of this command.
ip dhcp client mobile renew count number interval msec
no ip dhcp client mobile renew count number interval msec
Syntax Description
Defaults
count number: 2
interval msec: 50Command Modes
Interface configuration
Command History
Usage Guidelines
Mobile DHCP clients automatically attempt to renew an existing IP address in response to certain events, such as moving between wireless access points. The number of renewal attempts, and the interval between those attempts, depending on network conditions, can be modified by using the ip dhcp client mobile renew command.
Examples
In the following example, the DHCP client will make four attempts to renew its current IP address with an interval of 30 milliseconds between attempts :
interface FastEthernet0ip dhcp client mobile renew count 4 interval 30Related Commands
ip mobile router-service
To enable mobile router service on an interface, use the ip mobile router-service command in interface configuration mode. To disable this service, use the no form of this command.
ip mobile router-service {hold-down [foreign-agent seconds | reassociate msec] | roam [priority value] | solicit [interval seconds] [retransmit initial minimum maximum seconds retry number]}
no ip mobile router-service {hold-down [foreign-agent seconds | reassociate msec] | roam [priority value] | solicit [interval seconds] [retransmit initial minimum maximum seconds retry number]}
Syntax Description
Defaults
hold-down foreign agent seconds: zero
hold-down reassociate msec: 1000
priority value: 100
interval seconds: 600 seconds
retransmit initial minimum maximum seconds: 1000 milliseconds (1 second)
retry number : Three retriesCommand Modes
Interface configuration
Command History
Release Modification12.2(4)T
This command was introduced.
12.3(14)T
The foreign-agent seconds and reassociate msec keywords and arguments were added.
Usage Guidelines
The mobile router discovers home agents and foreign agents by receiving agent advertisements.
Note
In release 12.3(14)T, the ip mobile router-service hold-down command was changed to the ip mobile router-service hold-down foreign-agent command. The previous version of the command is still accepted but the new command will appear in the running configuration.
When a wireless link connected to an interface is lossy, the mobile router must not immediately register with the foreign agent even when heard on a preferred interface. The ip mobile router-service hold-down foreign-agent seconds command allows existing communications to continue with mobile networks while the mobile router gauges the quality of the link to the new foreign agent.
The ip mobile router-service solicit command instructs the mobile router to send agent solicitation messages periodically. Some networks only send out agent advertisements periodically or when solicited. For networks on which agents do not advertise periodically, this function must be enabled to detect agents. The mobile router always sends solicitation messages when roaming interfaces come up.
If a mobile router interface is configured for solicitations, you should set both ip irdp maxadvertinterval seconds and ip irdp holdtime seconds to 0 seconds on the foreign agent. These settings ensure that the foreign agent will not send out any IRDP advertisements unless solicited. If a foreign agent or home agent are sending IRDP advertisements periodically, then a solicitation will trigger the agent to send an advertisement immediately instead of at the next time interval.
The solicit timer for the ip mobile router-service solicit command is reset and no solicitation is sent out on the roaming interface if the mobile router receives an advertisement from a foreign agent before the solicit timer expires. For example, if the mobile router is configured to solicit every 10 seconds and the foreign agent advertises every 3 seconds, the mobile router will never solicit.
Use the ip mobile router-service hold-down reassociate msec command to specify the interval of time that the mobile router will wait, after receiving an SNMP linkDown trap, for a linkUp trap from the Wireless Mobile Interface Card (WMIC) indicating that the wireless link is available for use. This hold-down delay should be long enough for the WMIC to establish connectivity with a new AP or bridge when roaming.
Use the show ip mobile router agent command to display agents learned from advertisements and the mobile router's available CCoAs. Use the show ip mobile router interface command to display the configuration of the interfaces used for roaming.
Examples
The following example configures roaming interfaces, solicitation services, and hold-down timers on serial interface 0 and roaming interfaces and hold-down timers on Ethernet interface 0 of the mobile router.
In this example, the mobile router has two interfaces. The serial interface is connected to a serial interface of a foreign agent and the Ethernet interface is connected to an Ethernet interface of a foreign agent. The mobile router will prefer to register on the Ethernet interface if possible because it has a higher priority than the serial interface. If the mobile router does not receive any agent advertisements on the Ethernet interface, it will use the serial interface to solicit foreign agents.
If the Ethernet interface hears a new foreign agent advertisement after the mobile router has already registered using the serial interface, it will wait the duration of the hold-down timer (20 seconds) before registering with the foreign agent on the Ethernet interface. The ip mobile router-service hold-down foreign-agent seconds command allows communications to continue with mobile networks while the mobile router gauges the quality of the link to the new foreign agent. The Ethernet interface is configured with a higher priority so the mobile router prefers to register with this interface.
Once it receives an agent advertisement on the Ethernet interface, it will use the Ethernet interface to register to its home agent.
interface s0ip mobile router-service roam! s0 solicits every 5 seconds after last advertisement received on the interfaceip mobile router-service solicit interval 5ip mobile router-service hold-down foreign-agent 20interface e0ip mobile router-service roam priority 101ip mobile router-service hold-down foreign-agent 20In the following example, the mobile router is configured to receive dynamic CCoA from DHCP. The mobile router will wait 2000 milliseconds for the SNMP linkUp trap from the WMIC indicating that layer 2 has reassociated. This interval of time allows the mobile router to roam and still maintain wireless connectivity.
interface FastEthernet0ip address dhcpip dhcp client mobile renew count 3 interval 20ip mobile router-service roamip mobile router-service collocatedip mobile router-service hold-down reassociate 2000Related Commands
show ip mobile router agent
To display information about the agents for the mobile router, use the show ip mobile router agent command in privileged EXEC mode.
show ip mobile router agent
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays a list containing information on all foreign agents currently discovered on the mobile router. This list also displays information about each interface configured for static or dynamic CCoA. An interface must be "up" to be displayed on the list and a dynamic CCoA must have acquired an IP address.
You can use the clear ip mobile router agent command to clear foreign agent care-of addresses (CoAs) but not static or dynamic CCoAs. CCoAs cannot be cleared.
Examples
The following is sample output from the show ip mobile router agent command when a CCoA is configured on a mobile router interface:
Router# show ip mobile router agentMobile Router Agents:Foreign agent 45.0.0.2:Care-of address 42.0.0.2Interface Ethernet1, MAC 0030.9492.6627Agent advertisement seq 56649, Flags rbhFmGvt, Lifetime 36000IRDP advertisement lifetime 30, Remaining 29Last received 02/13/02 17:55:48First heard 02/13/02 11:21:46Collocated Care-of address 48.0.0.1 (static):Interface Ethernet2Default gateway 48.0.0.2Registration retry interval 60Next CCoA reg attempt in 00:00:55 secondsCollocated Care-of address 11.0.0.7 (dynamic):Interface Serial0Registration retry interval 60Table 1 describes the significant fields shown in the display.
Related Commands
Command Descriptionclear ip mobile router agent
Deletes learned agents and the corresponding care-of address of the foreign agent from the mobile router agent table.
show ip mobile router interface
To display information about the interfaces configured for roaming, use the show ip mobile router interface command in privileged EXEC mode.
show ip mobile router interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The mobile router uses the interfaces for roaming, discovering foreign agents, and registering its location on the foreign network.
Use this command to display information about roaming interfaces. If the interface is configured for a collocated care-of address (CCoA), the CCoA IP address is displayed. If it is not configured for a CCoA, "disabled" is displayed. The interface can be up or down.
Examples
The following is sample output from the show ip mobile router interface command. Fast Ethernet interface 0/0 and Fast Ethernet interface 2/0 have no CCoA configuration, serial interface 1/0 has a static CCoA configuration, and serial interface 1/1 has a dynamic CCoA address with CCoA only. GRE encapsulation is configured on Fast Ethernet interface 2/0.
Router# show ip mobile router interfaceMobile Router Interfaces:Listed in order of preference.FastEthernet0/0:Priority 102, Bandwidth 10000, Address 10.0.0.9Periodic solicitation disabled, Interval 600 secRetransmit Init 1000, Max 5000 msec, Limit 3Current 0, Remaining 0 msec, Count 0Hold down 0 secRouting disallowedCollocated CoA disabledSerial1/0:Priority 100, Bandwidth 1544, Address 10.0.0.7Periodic solicitation disabled, Interval 600 secRetransmit Init 1000, Max 5000 msec, Limit 3Current 1000, Remaining 0 msec, Count 1Hold down 0 secRouting disallowedCollocated CoA 10.0.0.7 (static)Serial1/1Priority 100, Bandwidth 1544, Address 10.0.0.5Periodic solicitation disabled, Interval 600 secRetransmit Init 1000, Max 5000 msec, Limit 3Current 0, Remaining 0 msec, Count 0Hold down 0 secRouting disallowedCollocated CoA 10.0.0.5 - Solicit FA firstFastEthernet2/0Priority 110, Bandwidth 16000, Address 10.52.52.2Periodic solicitation disabled, Interval 600 secRetransmit Init 1000, Max 5000 msec, Limit 3Current 2000, Remaining 0 msec, Count 2Hold down 0 secRouting disallowedCollocated CoA disabledRequest GRE tunnelThe following sample output shows that the mobile router is configured to support signaling on roaming interfaces via SNMP interface MIB traps.
Router# show ip mobile router interfaceMobile Router Interfaces:Listed in order of preference.Ethernet1:Priority 110, Bandwidth 10000, Address 55.0.0.8Periodic solicitation disabled, Interval 600 secRetransmit Init 1000, Max 5000 msec, Limit 3Current 5000, Remaining 0 msec, Count 4Foreign agent hold down 0 secLayer 2 reassociation hold down 5000 msecLast layer 2 link-state trap: linkDownRouting disallowedCollocated CoA 55.0.0.8 - Solicit FAsTable 2 describes the significant fields shown in the display.
Related Commands
Glossary
care-of address—The termination point of the tunnel to a mobile node or mobile router. This can be a collocated care-of address, by which the mobile node or mobile router acquires a local address and detunnels its own packets, or a foreign agent care-of address, by which a foreign agent detunnels packets and forwards them to the mobile node or mobile router.
collocated care-of address—The termination point of a tunnel toward a mobile node or mobile router. A CCoA is a local address that the mobile node or mobile router associated with one of its own network interfaces.
DHCP—Dynamic Host Configuration Protocol. Provides a mechanism for allocating IP addresses and other configuration parameters dynamically so that addresses can be reused when hosts no longer need them.
foreign agent—A router on the visited network of a foreign network that provides routing services to the mobile node or mobile router while registered. The foreign agent detunnels and delivers packets to the mobile node or mobile router that were tunneled by the home agent of the mobile node. For packets sent by a mobile node, the foreign agent may serve as a default router for registered mobile nodes.
home agent—A router on a home network of the mobile node or that tunnels packets to the mobile node or mobile router while they are away from home. It keeps current location information for registered mobile nodes called a mobility binding.
IPCP—IP Control Protocol. The protocol used to establish and configure IP over PPP.
PPP—Point-to-Point Protocol. Provides router-to-router and host-to-network connections over synchronous and asynchronous circuits. PPP is most commonly used for dial-up Internet access. Its features include address notification, authentication via CHAP or PAP, support for multiple protocols, and link monitoring.
trap—Message sent by an SNMP agent to an NMS console, or terminal to indicate the occurrence of a significant event, such as a specifically defined condition or a threshold that was reached.
Note
Refer to Internetworking Terms and Acronyms for terms not included in this glossary.
Copyright © 2005 Cisco Systems, Inc. All rights reserved.


