BGP Authentication - Subnet-Level with MD5

This feature introduces support for an MD5 signature for a BGP TCP connection to a subnet (range of addresses) within the specified prefix length. This feature protects against the introduction of spoofed TCP segments into BGP session connection streams. You configure a router using the MD5 signature option with a password for each peer for which authentication is required. You also use this feature to store an encrypted password. You can create BGP hello adjacencies even when peering interfaces are configured with different security signatures. However, the BGP TCP session cannot be authenticated and is never established.Supports VRF instance along with Default Routing instance.