•
Enable IPsec authentication for OSPFv3 packets on an IPv6-based interface.
INTERFACE mode
ipv6 ospf authentication {null | ipsec spi
number
{MD5 | SHA1} [
key-encryption-type
]
key
}
•
null
: causes an authentication policy configured for the area to not be inherited on the interface.
•
ipsec spi
number
: the security policy index (SPI) value. The range is from 256 to 4294967295.
•
MD5 | SHA1
: specifies the authentication type: Message Digest 5 (
MD5
) or Secure Hash Algorithm 1 (
SHA-1
).
•
key-encryption-type
: (optional) specifies if the key is encrypted. The valid values are
0
(key is not encrypted) or
7
(key is
encrypted).
•
key
: specifies the text string used in authentication. All neighboring OSPFv3 routers must share key to exchange information. For
MD5 authentication, the key must be 32 hex digits (non-encrypted) or 64 hex digits (encrypted). For SHA-1 authentication, the key
must be 40 hex digits (non-encrypted) or 80 hex digits (encrypted).
•
Remove an IPsec authentication policy from an interface.
no ipv6 ospf authentication ipsec spi
number
•
Remove null authentication on an interface to allow the interface to inherit the authentication policy configured for the OSPFv3 area.
no ipv6 ospf authentication null
•
Display the configuration of IPsec authentication policies on the router.
show crypto ipsec policy
•
Display the security associations set up for OSPFv3 interfaces in authentication policies.
show crypto ipsec sa ipv6
Configuring IPsec Encryption on an Interface
To configure, remove, or display IPsec encryption on an interface, use the following commands.
Prerequisite
: Before you enable IPsec encryption on an OSPFv3 interface, first enable IPv6 unicast routing globally, configure an IPv6
address and enable OSPFv3 on the interface, and assign it to an area (refer to
Configuration Task List for OSPFv3 (OSPF for IPv6)
).
NOTE:
When you configure encryption using the
ipv6 ospf encryption ipsec
command, you enable both IPsec
encryption and authentication. However, when you enable authentication on an interface using the
ipv6 ospf
authentication ipsec
command, you do not enable encryption at the same time.
The SPI value must be unique to one IPsec security policy (authentication or encryption) on the router. Configure the same authentication
policy (the same SPI and key) on each OSPFv3 interface in a link.
•
Enable IPsec encryption for OSPFv3 packets on an IPv6-based interface.
INTERFACE mode
ipv6 ospf encryption {null | ipsec spi
number
esp
encryption-algorithm
[
key-encryption-type
]
key authentication-algorithm
[
key-authentication-type
]
key
}
•
null
: causes an encryption policy configured for the area to not be inherited on the interface.
•
ipsec spi
number
: is the security policy index (SPI) value. The range is from 256 to 4294967295.
•
esp
encryption-algorithm
: specifies the encryption algorithm used with ESP. The valid values are
3DES
,
DES
,
AES-CBC,
and
NULL
. For
AES-CBC
, only the AES-128 and AES-192 ciphers are supported.
•
key
: specifies the text string used in the encryption. All neighboring OSPFv3 routers must share the same key to decrypt
information. Required lengths of a non-encrypted or encrypted key are: 3DES - 48 or 96 hex digits; DES - 16 or 32 hex digits; AES-
CBC - 32 or 64 hex digits for AES-128 and 48 or 96 hex digits for AES-192.
•
key-encryption-type
: (optional) specifies if the key is encrypted. The valid values are
0
(key is not encrypted) or
7
(key is
encrypted).
•
authentication-algorithm
: specifies the encryption authentication algorithm to use. The valid values are
MD5
or
SHA1
.
•
key
: specifies the text string used in authentication. All neighboring OSPFv3 routers must share key to exchange information. For
MD5 authentication, the key must be 32 hex digits (non-encrypted) or 64 hex digits (encrypted). For SHA-1 authentication, the key
must be 40 hex digits (non-encrypted) or 80 hex digits (encrypted).
Open Shortest Path First (OSPFv2 and OSPFv3)
665
Содержание S4048T-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Страница 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Страница 251: ...Dell Control Plane Policing CoPP 251 ...
Страница 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Страница 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Страница 512: ...Figure 65 Inspecting Configuration of LAG 10 on ALPHA 512 Link Aggregation Control Protocol LACP ...
Страница 515: ...Figure 67 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 515 ...
Страница 516: ...Figure 68 Inspecting LAG 10 Using the show interfaces port channel Command 516 Link Aggregation Control Protocol LACP ...
Страница 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Страница 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Страница 560: ...Figure 86 Configuring PIM in Multiple Routing Domains 560 Multicast Source Discovery Protocol MSDP ...
Страница 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Страница 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Страница 729: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 Per VLAN Spanning Tree Plus PVST 729 ...
Страница 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Страница 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...