Peer – Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 626
![background image](/manuals/361696/626/background.png)
Brocade Mobility RFS Controller CLI Reference Guide
613
53-1003098-01
7
Parameters
modeconfig [pull|push]
Example
Remote VPN client:
rfs4000-229D58(config-device-00-23-68-22-9D-58-cryptomap-test#2)#modeconfig
push
peer
crypto-map auto-vpn-tunnel/remote-vpn-client instance
Configures the IKEv1 or IKEv2 peer for the auto site-to-site VPN tunnel or remote VPN client. The
peer device can be specified either by its hostname or by its IP address. A maximum of three peers
can be configured.
Supported in the following platforms:
•
Access Points — Brocade Mobility 650 Access Point, Brocade Mobility 6511 Access Point,
Brocade Mobility 1220 Access Point, Brocade Mobility 71XX Access Point, Brocade
Mobility 1240 Access Point
•
Wireless Controllers — Brocade Mobility RFS4000, Brocade Mobility RFS6000, Brocade
Mobility RFS7000
•
Service Platforms — Brocade Mobility RFS9510
Syntax:
peer <1-3> [ikev1|ikev2]
Parameters
peer <1-3> [ikev1|ikev2]
Example
Site-to-site tunnel:
rfs4000-229D58(config-device-00-23-68-22-9D-58-cryptomap-test#1)#peer 1 ikev2
ikev2Peer1
rfs4000-229D58(config-device-00-23-68-22-9D-58-cryptomap-test#1)#show context
crypto map test 1 ipsec-isakmp
peer 1 ikev2 ikev2Peer1
local-endpoint-ip 192.168.13.10
ip nat crypto
rfs4000-229D58(config-device-00-23-68-22-9D-58-cryptomap-test#1)#
modeconfig [pull|push]
Configures the mode config method associated with a remote VPN client. The options are: pull and push.
The mode (pull or push) defines the method used to assign a virtual IP. This setting is relevant for IKEv1 only,
since IKEv2 always uses the configuration payload in pull mode. The default setting is push.
peer <1-3>
Creates a new peer and configures the peer’s priority level. Peer ‘1’ is the primary peer, and peer ‘3’ is
redundant.
ikev1
Configures an IKEv1 peer
•
ikev2
Configures an IKEv2 peer
•