Avaya G430, Manual

Page: 512 / 696

Gxxx-001(config-ACL 302/ip rule 25)# exit
Gxxx-001(config-ACL 302)# exit
!
! Activate the Ingress and Egress ACLs on the FastEthernet Interface
!
Gxxx-001(config)# interface fastethernet 10/3
Gxxx-001(config-if:FastEthernet 10/3)# ip access-group 301 in
Done!
Gxxx-001(config-if:FastEthernet 10/3)# ip access-group 302 out
Done!
2. Specify
no ip address
and then
ip address dhcp
in the context of the
FastEthernet Interface.
For example:
Gxxx-001(config-if:FastEthernet 10/3)# no ip address
no ip address defined on this interface
Gxxx-001(config-if:FastEthernet 10/3)# ip address dhcp
Done!
3. Exit the context of the interface, and set the interface name as the next hop.
For example:
Gxxx-001(config-if:FastEthernet 10/3)#exit
Gxxx-001(config)# ip route 5.0.0.0 255.0.0.0 FastEthernet 10/3
Done!
Note:
For more information on DHCP client in the Branch Gateway, see DHCP client
configuration on page 204.
Continuous channel
An IPSec VPN connection exists as long as traffic is traversing the connection, or the timeouts
have not expired. However, there are advantages to keeping the connection continuously alive,
such as eliminating the waiting time necessary to construct a new IPSec VPN connection.
The Branch Gateway IPSec VPN feature supports continuous channel, which maintains a
continuous IPSec VPN connection. That means that when you activate the
ip crypto-
group
command on the defined interface, the IPSec VPN tunnel is immediately started, even
if no traffic is traversing the interface and the timeouts have expired.
Enabling continuous channel
About this task
You can set continuous channel for either or both IKE phase 1 and IKE phase 2, as follows:
Procedure
1. To set continuous channel for IKE phase 1, enter
continuous-channel
when
configuring the crypto ISAKMP peer information (see Configuring ISAKMP peer
information on page 489).
IPSec VPN
512 Administering Avaya G430 Branch Gateway October 2013
Comments? infodev@avaya.com