Cisco Cisco ASR 5000
HeNB-GW Access Service Configuration Mode Commands
▀ security-gateway
▄ Command Line Interface Reference, StarOS Release 18
6326
security-gateway
This command configuration defines the IPv4 address to be used as the connection point for establishing IKEv2 sessions
and specify the crypto template to use for the security gateway (SeGW) for the HeNB-GW Access service.
and specify the crypto template to use for the security gateway (SeGW) for the HeNB-GW Access service.
Product
HeNB-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > HeNBGW-Access Service Configuration
configure > context context_name > henbgw-access-service
service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-henbgw-access-service)#
Syntax
security gateway bind ipv4-address ipv4_addr crypto-template template_name [ context
ctxt_name ]
ctxt_name ]
no security gateway bind
no
Removes the security gateway related configuration associated with this HeNB-GW Access service
configuration.
configuration.
ip_addr
Identifies the security gateway address used for this HeNB-GW Access service. It must be entered in dotted
decimal notation.
decimal notation.
template_name
Identifies the crypto template name for security gateway for this HeNB-GW Access service. It must be
entered a string of size 0 to 127.
entered a string of size 0 to 127.
ctxt_name
Identifies the context name where crypto template is defined for this HeNB-GW Access service. It must be
entered a string of size 1 to 79.
entered a string of size 1 to 79.
Usage
Use this command to configure the security gateway (SeGW) related configuration for this HeNB-GW
Access service. SeGW configuration includes crypto template configuration as part of IPSec settings,
therefore if the crypto-template is defined in a different context than the current HeNB-GW Access service,
the context name has to be specified.
Access service. SeGW configuration includes crypto template configuration as part of IPSec settings,
therefore if the crypto-template is defined in a different context than the current HeNB-GW Access service,
the context name has to be specified.
Example