HPE FlexNetwork MSR Router Series

HPE FlexNetwork MSR Router Series
HPE FlexNetwork MSR Router Series
Comware 7 NEMO Configuration Guides
Part number: 5998-8787
Software version: CMW710-E0407
Document version: 6W100-20160526
© Copyright 2016 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for Hewlett Packard
Enterprise products and services are set forth in the express warranty statements accompanying such
products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett
Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or
copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software
Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s
standard commercial license.
Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard
Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise
website.
Acknowledgments
Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the
United States and other countries.
Microsoft® and Windows® are trademarks of the Microsoft group of companies.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Java and Oracle are registered trademarks of Oracle and/or its affiliates.
UNIX® is a registered trademark of The Open Group.
Contents
Configuring NEMO ···········································································1 Overview ·································································································································· 1 Basic concepts ··················································································································· 1 Mobile router operation ········································································································· 1 NEMO application scenarios ·································································································· 2 Registration message format ································································································· 3 Protocols and standards ······································································································· 6 NEMO configuration task list ········································································································ 6 Configuring NEMO ····················································································································· 7 Configuring mobile IP ··········································································································· 7 Configuring the mobile router feature ······················································································· 7 Configuring a roaming interface ······························································································ 8 Configuring a mobility security association ················································································ 8 Displaying and maintaining NEMO································································································· 9 NEMO configuration example ······································································································· 9 Document conventions and icons ······················································ 12 Conventions ··························································································································· 12 Network topology icons ············································································································· 13 Support and other resources ···························································· 14 Accessing Hewlett Packard Enterprise Support ·············································································· 14 Accessing updates ··················································································································· 14 Websites ························································································································· 15 Customer self repair··········································································································· 15 Remote support ················································································································ 15 Documentation feedback ···································································································· 15 Index ··························································································· 17 i
Configuring NEMO
Overview
Network mobility (NEMO) enables a node to retain the same IP address and maintain application
connectivity when the node travels across networks. It allows location-independent routing of IP
datagrams on the Internet.
Basic concepts
The NEMO feature includes the following concepts.
Home address
A home address is an IP address that is allocated to a mobile node. The mobile node uses this IP
address for all communications.
Home network
A home network is the network where the home address of a mobile node resides. The network is
attached to a home agent.
Mobile node
A mobile node (MN) is a mobile host or a router capable of reporting its current visiting network to the
home agent.
Home agent
A home agent (HA) is a host or a router acting as the home network for a mobile node. It saves the
current location of the mobile node and forwards traffic to the mobile node.
Care-of address
A care-of address (CoA) identifies the location of a mobile node when the node is away from its home
network. This CoA address is the local endpoint of the tunnel to the home agent.
Collocated care-of address
A collocated care-of address (CCoA) is a care-of address that a mobile node obtains through manual
configuration or DHCP.
Mobile router
A mobile router (MR) is a router that operates as a mobile node.
Mobile router operation
After the mobile router sends a registration request to the home agent, the mobile router operates as
follows:
•
•
If it receives a registration reply within the registration lifetime requested, the router performs
the following operations:
{
Creates a mobile IP tunnel automatically.
{
Adds a default route destined for the home agent.
If it does not receive any replies within the registration lifetime requested, the router performs
the following operations:
{
Removes the registration information.
1
{
Initiates a registration request after the interval set by using the ip mobile router-service
collocated registration retry command.
NEMO application scenarios
NEMO provides the following applications for connecting the mobile network to the home network:
•
3G or 4G wireless access.
•
Wired access with the 3G or 4G wireless link as the backup link.
Connecting the mobile network to the home network through the 3G or 4G wireless link
As shown in Figure 1, a tunnel is established between the 3G or 4G wireless modem interfaces of the
mobile router and the home agent. The mobile router and nodes on the mobile network can use the
tunnel to access the home network.
When the mobile router moves from its home network, only the IP address of the 3G or 4G wireless
modem interface of the mobile router changes.
The mobile router sends a registration request to the home agent and reestablishes a tunnel with the
home agent. Hosts attaching to the mobile router are unaware of the IP address change. Services
are not interrupted.
Figure 1 Connecting the mobile network and the home network through the wireless link
Data Center/Internet
HA
Device
Device
MR
Wireless
Terminal
PC
PC
Connecting the mobile network to the home network through the wired link
As shown in Figure 2, the 3G or 4G wireless link is the backup link for the wired link between the
mobile network and the home network.
2
When the mobile router moves from its home network, the wired link is disconnected. The mobile
network is connected to the home network through the 3G or 4G wireless link. After the move is
completed, the wired link is recovered, and the wireless link becomes the backup link.
Figure 2 Connecting the mobile network and the home network through the wired link
Registration message format
A registration message contains the fixed portion and extensions. The authentication extension must
be added. The mobile network extension and NVSE extension can be added as required.
3
Registration request
Figure 3 Registration request message format
A registration request contains the following fields:
•
Type—Type of the message. The value 1 represents a registration request, and the value 3
represents a registration reply.
•
S—Simultaneous bindings.
•
B—Broadcast datagrams.
•
D—Decapsulation by mobile node.
•
M—Minimal encapsulation.
•
G—GRE encapsulation.
•
r—Sent as zero. It is ignored on reception.
•
T—Reverse tunneling requested.
•
x—Sent as zero. It is ignored on reception.
•
Lifetime—Lifetime of the registration. The value 0 represents a request for deregistration. The
value 0xFFFF (65535) indicates infinity.
•
Home Address—Home address of the mobile node.
•
Home Agent—IP address of the mobile node's home agent.
•
Care-of Address—IP address for the end of the tunnel.
•
Identification—It is used to match registration requests and registration replies. The value is
formatted as specified by the NTP.
•
Extensions—Authentication extension. The mobile network extension and NVSE extension
can be added as required.
4
Registration reply
Figure 4 Registration reply message format
A registration reply contains the following different fields than a registration request:
•
Code—A value indicating the result of the registration request. The values 0 through 8 indicate
that the registration request is accepted. For more information, see RFC 5944.
•
Identification—It is used to match registration requests and registration replies. If the
registration request is accepted, this field copies the value of the Identification field in the
registration request.
Authentication extension
Figure 5 Authentication extension format
An authentication extension contains the following fields:
•
Type—Type of the extension. The value is 32.
•
Length—Length of the extension. The value is the total number of bytes in the SPI and
Authenticator fields.
•
SPI—Security parameter index.
•
Authenticator—Authentication data in cipher text.
Mobile network extension
Figure 6 Mobile network extension format
A mobile network extension contains the following fields:
•
Type—Type of the extension. The value is 148.
•
Length—Length of the extension, excluding the Type filed. The value is 6.
•
Sub-Type—Sub-type of the extension. The value is 0.
•
Prefix Length—Prefix length of the mobile network.
•
Prefix—Prefix of the mobile network.
5
Normal Vendor/Organization Specific Extension (NVSE)
Figure 7 NVSE format
An NVSE extension contains the following fields:
•
Type—Type of the extension. The value is 134.
•
Length—Length of the extension, excluding the Type field.
•
Reserved—Reserved for future use.
•
Vendor/Org-ID—Vendor ID. The value 9 represents Cisco.
•
Vendor-NVSE-Type—Type of the vendor NVSE extension. The value 9 represents the explicit
mode, and the value 13 represents the implicit mode.
•
Vendor-NVSE-Value—Value of the vendor NVSE extension.
NVSE prefix extension
Figure 8 NVSE prefix extension format
An NVSE prefix extension contains the following fields:
•
Sub-Type—Sub-type of the extension. The value 1 represents a registration request, and the
value 2 represents a registration reply.
•
Length—Length of the extension. The value is 6.
•
Prefix Length—Prefix length of the mobile network.
•
Code—A value indicating the result of the registration request. The value 0 indicates that the
registration request is accepted.
•
Prefix—Prefix of the mobile network.
Protocols and standards
•
RFC 5177, Network Mobility (NEMO) Extensions for Mobile IPv4
•
RFC 5944, IP Mobility Support for IPv4, Revised
NEMO configuration task list
Tasks at a glance
(Required.) Configuring mobile IP
(Required.) Configuring the mobile router feature
(Required.) Configuring a roaming interface
(Required.) Configuring a mobility security association
6
Configuring NEMO
Enable mobile IP before you perform other tasks for NEMO configuration.
Configuring mobile IP
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable mobile IP and enter
its view.
router mobile
By default, mobile IP is disabled.
3.
(Optional.) Set a preference
for mobile IP routes.
preference preference
By default, the preference for
mobile IP routers is 65.
4.
(Optional.) Set the interface
number range for the
automatically created tunnel.
tunnel-number min min-number
max max-number
For information about the default
tunnel interface number range,
see NEMO Command Reference.
Configuring the mobile router feature
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable the mobile router
feature and enter mobile
router view.
ip mobile router
By default, this feature is disabled.
3.
Assign a home address to the
mobile router.
address ip-address
By default, the mobile router does
not have any home addresses.
4.
Specify the IP address of the
home agent for the mobile
router.
home-agent ip-address
By default, no home agent is
specified for the mobile router.
5.
6.
7.
(Optional.) Specify the mobile
router interface that is
connected to the mobile
network.
By default, no mobile router
interface is specified.
mobile-network interface-type
{ interface-number |
interface-number.subnumber }
The primary IP address of a
mobile router interface is
contained in the registration
request to inform the home agent
of the mobile network.
(Optional.) Configure
registration extending
parameters for the mobile
router to be kept alive.
register extend expire seconds
retry retries interval interval
By default:
•
The mobile router sends a
registration request 60
seconds before the
registration expires.
•
The mobile router makes 3
retries at an interval of 10
seconds if no reply is
received.
(Optional.) Set the
registration lifetime
requested by the mobile
router.
register lifetime seconds
The default registration lifetime is
65534 seconds.
7
Step
Command
Remarks
(Optional.) Set
retransmission parameters
for the mobile router's
registration with the home
agent.
register retransmit initial
milliseconds maximum
milliseconds retry retries
By default:
•
The initial waiting time is
1000 milliseconds.
•
The maximum waiting time is
5000 milliseconds.
•
The maximum number of
retries is 3.
(Optional.) Enable the
interoperability mode.
interop
By default, the interoperability
mode is disabled.
10. (Optional.) Set the MTU for
the tunnel interface of the
automatically created tunnel.
tunnel mtu size
By default, the MTU for the tunnel
interface is 64000 bytes.
11. (Optional.) Set the DF bit to 0
for outgoing tunneled
packets.
ip df-bit zero
By default, the DF bit of outgoing
tunneled packets is not set.
12. (Optional.) Apply an IPsec
policy to the tunnel interface
of the automatically created
tunnel.
ipsec policy policy-name
By default, no IPsec policy is
applied to the tunnel interface of
an automatically created tunnel.
13. (Optional.) Set the TCP MSS
for the tunnel interface of the
automatically created tunnel.
tcp mss value
By default, no TCP MSS is set.
8.
9.
Configuring a roaming interface
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter Layer 3 interface
view.
interface interface-type
interface-number
N/A
3.
Configure the interface as a
roaming interface.
ip mobile router-service roam
By default, the roaming function is
disabled on an interface.
4.
(Optional.) Specify the
gateway address for the
roaming interface.
ip mobile router-service
collocated gateway ip-address
By default, no gateway address is
specified for a roaming interface.
5.
(Optional.) Set the
registration retry interval.
ip mobile router-service
collocated registration retry
interval
By default, the interval is 60
seconds.
Configuring a mobility security association
For successful authentication, configure the same authentication mode and password on the mobile
router and the home agent.
To configure a security association for authentication:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure a security
association for authentication
ip mobile secure home-agent
ip-address spi hex-value key
By default, no security association
is specified on the router for
8
Step
to the home agent.
Command
Remarks
ascii { cipher | simple } string
authentication.
For information about security
associations, see Security
Configuration Guide.
Displaying and maintaining NEMO
Execute display commands in any view.
Task
Command
Display registration information for the mobile router.
display ip mobile router registration
NEMO configuration example
Network requirements
As shown in Figure 9, the HA is a Cisco device. The MR uses a USB 3G modem to access the 3G
network through Dial-on-Demand Routing (DDR) and register with the HA.
Configure NEMO on the MR to meet the following requirements when the mobile network moves:
•
The hosts on the mobile network use their home addresses for communication.
•
Application connectivity is maintained on the hosts.
9
Figure 9 Network diagram
Data Center/Internet
HA
Loop0
1.1.1.2/32
Device
Device
MR
GE1/0/1
20.1.1.1/24
Wireless
Terminal
PC
PC
Configuration procedure
1.
Configure the MR:
# Assign the IP address 20.1.1.1 to GigabitEthernet 1/0/1.
<MR> system-view
[MR] interface gigabitethernet 1/0/1
[MR-GigabitEthernet1/0/1] ip address 20.1.1.1 255.255.255.0
[MR-GigabitEthernet1/0/1] quit
# Enable mobile IP.
[MR] router mobile
[MR-MIP] quit
# Enable the mobile router feature.
[MR] ip mobile router
# Assign a home address to the MR.
[MR-mobile-router] address 1.1.1.3
# Specify the IP address of the home agent 1.1.1.2 (IP address of interface Loopback 0 on HA)
on the MR.
[MR-mobile-router] home-agent 1.1.1.2
# Specify GigabitEthernet 1/0/1 as the mobile router interface.
[MR-mobile-router] mobile-network gigabitethernet 1/0/1
[MR-mobile-router] quit
# Channelize Cellular 2/4/0 into a synchronous/asynchronous serial interface.
10
[MR] controller cellular 2/4/0
[MR-Cellular2/4/0] serial-set 0
[MR-Cellular2/4/0] quit
# Configure Serial 2/4/0:0 as the roaming interface. (The IP address of the roaming interface is
assigned by the service provider. For more information, see Layer 2—WAN Access
Configuration Guide.)
[MR] interface serial 2/4/0:0
[MR-Serial2/4/0:0] ip mobile router-service roam
[MR-Serial2/4/0:0] quit
# Configure a security association that contains the home agent address 1.1.1.2, SPI 100, and
the plaintext key abc. (For successful authentication, configure the same SA on the HA.)
[MR] ip mobile secure home-agent 1.1.1.2 spi 100 key ascii simple abc
2.
Configure the HA. (Details not shown. For more information, see the HA user documentation.)
Verifying the configuration
# Display the registration information for the MR.
[MR] display ip mobile router registration
Registration accepted on 12/04/13 at 10:43:52, On Serial2/4/0:0
Care-of addr: 208.122.148.233, HA addr: 1.1.1.2, Home addr: 1.1.1.3
Lifetime requested: 65534, Granted: 36000
Remaining: 9 hours 58 minutes 36 seconds
Flags sbDmG-TIdentification d64985e8.bd34f00e
Next registration: 9 hours 56 minutes 36 seconds
Extensions:
Mobile Network 20.1.1.0/24
Authentication SPI: 100
# Display the registration information for the MR after it moves to another network.
[MR] display ip mobile router registration
Registration accepted on 12/04/13 at 11:35:45, On Serial2/4/0:0
Care-of addr: 212.48.124.187, HA addr: 1.1.1.2, Home addr: 1.1.1.3
Lifetime requested: 65534, Granted: 36000
Remaining: 9 hours 58 minutes 36 seconds
Flags sbDmG-TIdentification d6499211.bc35e11d
Next registration: 9 hours 56 minutes 36 seconds
Extensions:
Mobile Network 20.1.1.0/24
Authentication SPI: 100
The output shows that the MR retains the home address and maintains the application connectivity
when it moves.
11
Document conventions and icons
Conventions
This section describes the conventions used in the documentation.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
Command conventions
Convention
Description
Boldface
Bold text represents commands and keywords that you enter literally as shown.
Italic
Italic text represents arguments that you replace with actual values.
[]
Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n>
The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
#
A line that starts with a pound (#) sign is comments.
GUI conventions
Convention
Description
Boldface
Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
>
Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.
Convention
Description
Symbols
WARNING!
An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION:
An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT:
An alert that calls attention to essential information.
NOTE:
TIP:
An alert that contains additional or supplementary information.
An alert that provides helpful information.
12
Network topology icons
Convention
Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
T
Represents a wireless terminator unit.
T
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security card, such as a firewall, load balancing, NetStream, SSL VPN,
IPS, or ACG card.
13
Support and other resources
Accessing Hewlett Packard Enterprise Support
•
For live assistance, go to the Contact Hewlett Packard Enterprise Worldwide website:
www.hpe.com/assistance
•
To access documentation and support services, go to the Hewlett Packard Enterprise Support
Center website:
www.hpe.com/support/hpesc
Information to collect
•
Technical support registration number (if applicable)
•
Product name, model or version, and serial number
•
Operating system name and version
•
Firmware version
•
Error messages
•
Product-specific reports and logs
•
Add-on products or components
•
Third-party products or components
Accessing updates
•
Some software products provide a mechanism for accessing software updates through the
product interface. Review your product documentation to identify the recommended software
update method.
•
To download product updates, go to either of the following:
{
Hewlett Packard Enterprise Support Center Get connected with updates page:
www.hpe.com/support/e-updates
{
Software Depot website:
www.hpe.com/support/softwaredepot
•
To view and update your entitlements, and to link your contracts, Care Packs, and warranties
with your profile, go to the Hewlett Packard Enterprise Support Center More Information on
Access to Support Materials page:
www.hpe.com/support/AccessToSupportMaterials
IMPORTANT:
Access to some updates might require product entitlement when accessed through the Hewlett
Packard Enterprise Support Center. You must have an HP Passport set up with relevant
entitlements.
14
Websites
Website
Link
Networking websites
Hewlett Packard Enterprise Information Library for
Networking
www.hpe.com/networking/resourcefinder
Hewlett Packard Enterprise Networking website
www.hpe.com/info/networking
Hewlett Packard Enterprise My Networking website
www.hpe.com/networking/support
Hewlett Packard Enterprise My Networking Portal
www.hpe.com/networking/mynetworking
Hewlett Packard Enterprise Networking Warranty
www.hpe.com/networking/warranty
General websites
Hewlett Packard Enterprise Information Library
www.hpe.com/info/enterprise/docs
Hewlett Packard Enterprise Support Center
www.hpe.com/support/hpesc
Hewlett Packard Enterprise Support Services Central
ssc.hpe.com/portal/site/ssc/
Contact Hewlett Packard Enterprise Worldwide
www.hpe.com/assistance
Subscription Service/Support Alerts
www.hpe.com/support/e-updates
Software Depot
www.hpe.com/support/softwaredepot
Customer Self Repair (not applicable to all devices)
www.hpe.com/support/selfrepair
Insight Remote Support (not applicable to all devices)
www.hpe.com/info/insightremotesupport/docs
Customer self repair
Hewlett Packard Enterprise customer self repair (CSR) programs allow you to repair your product. If
a CSR part needs to be replaced, it will be shipped directly to you so that you can install it at your
convenience. Some parts do not qualify for CSR. Your Hewlett Packard Enterprise authorized
service provider will determine whether a repair can be accomplished by CSR.
For more information about CSR, contact your local service provider or go to the CSR website:
www.hpe.com/support/selfrepair
Remote support
Remote support is available with supported devices as part of your warranty, Care Pack Service, or
contractual support agreement. It provides intelligent event diagnosis, and automatic, secure
submission of hardware event notifications to Hewlett Packard Enterprise, which will initiate a fast
and accurate resolution based on your product’s service level. Hewlett Packard Enterprise strongly
recommends that you register your device for remote support.
For more information and device support details, go to the following website:
www.hpe.com/info/insightremotesupport/docs
Documentation feedback
Hewlett Packard Enterprise is committed to providing documentation that meets your needs. To help
us improve the documentation, send any errors, suggestions, or comments to Documentation
Feedback (docsfeedback@hpe.com). When submitting your feedback, include the document title,
15
part number, edition, and publication date located on the front cover of the document. For online help
content, include the product name, product version, help edition, and publication date located on the
legal notices page.
16
Index
NEMO configuration, 1, 6, 7, 9
A
address
NEMO care-of address (CoA), 1
M
message
NEMO collocated care-of address (CCoA), 1
NEMO configuration, 6, 7, 9
NEMO home address, 1
NEMO registration format, 3
agent
mobile router
NEMO home agent, 1
NEMO mobile router feature configuration, 7
application
NEMO scenarios, 2
NEMO operation, 1
mobility
C
NEMO configuration, 6, 7, 9
care-of address (CoA), 1
NEMO mobile IP configuration, 7
collocated care-of address (CCoA), 1
NEMO mobility security association
configuration, 8
configuring
NEMO roaming interface configuration, 8
NEMO, 1, 6, 7, 9
NEMO mobile IP, 7
N
NEMO mobile router feature, 7
NEMO
NEMO mobility security association, 8
application scenarios, 2
NEMO roaming interface, 8
basic concepts, 1
configuration, 1, 6, 7, 9
D
display, 9
displaying
mobile IP configuration, 7
NEMO, 9
mobile router feature configuration, 7
F
mobile router operation, 1
format
mobility security association configuration, 8
NEMO registration message, 3
NVSE, 6
H
NVSE prefix extension, 6
home
protocols and standards, 6
NEMO home address, 1
registration message format, 3
NEMO home agent, 1
roaming interface configuration, 8
NEMO home network, 1
network
mobility. See NEMO
I
NEMO application scenarios, 2
IP
NEMO configuration, 7
NEMO mobile IP configuration, 7
NEMO home network, 1
IP addressing
NEMO mobile IP configuration, 7
17
NEMO mobile router, 1
routing
NEMO configuration, 1
NEMO mobile router feature configuration, 7
NEMO mobile router operation, 1
NEMO mobility security association
configuration, 8
S
security association
NEMO mobility security association
NEMO registration message format, 3
configuration, 8
NEMO roaming interface configuration, 8
network management
NEMO configuration, 1, 6, 9
V
VXLAN
NEMO application scenarios, 2
node
NEMO configuration, 1
NEMO configuration, 1
NEMO mobile node, 1
NEMO protocols and standards, 6
Normal Vendor/Organization Specific Extension.
See NVSE
NVSE
NEMO, 6
NEMO prefix extension, 6
P
procedure
configuring NEMO, 6, 7, 9
configuring NEMO mobile IP, 7
configuring NEMO mobile router feature, 7
configuring NEMO mobility security
association, 8
configuring NEMO roaming interface, 8
displaying NEMO, 9
protocols and standards
NEMO, 6
R
registering
NEMO configuration, 6, 7, 9
NEMO registration message format, 3
roaming
NEMO roaming interface configuration, 8
router
NEMO mobile IP configuration, 7
NEMO mobile router, 1
NEMO mobile router operation, 1
18
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising