3Com Switch 8800 Configuration Guide Chapter 21 BGP Configuration
21-12
IX. Configuring BGP MD5 authentification password
BGP uses TCP as its transport layer. For the sake of high security, you can configure
MD5 authentication password when setting up a TCP connection. In other words, BGP
MD5 authentication just sets password for TCP connection, but not for authenticating
BGP packets. The authentication is implemented by TCP.
Perform the following configuration in BGP view.
Table 21-17 Configure BGP MD5 authentication
Operation Command
Configure MD5 authentication
password peer { group-name | peer-address } password
{ cipher | simple } password
Cancel MD5 authentication undo peer { group-name | peer-address }
password
In BGP, no MD5 authentication is performed in setting up TCP connections by default.
Note:
The multicast extension configured in BGP view is also available in MBGP, since they
use the same TCP link.
The Switch 8800 supports filtering imported and advertised routes for peers (groups)
through Route-policy, AS path list, ACL and ip prefix list.
The route filtering policy of advertised routes configured for each member of a peer
group must be same with that of the peer group but their route filtering policies of
ingress routes may be different.
Perform the following configuration in BGP view.
I. Configuring route policy for a peer (group)
Table 21-18 Configure route policy for a peer (group)
Operation Command
Configure the ingress route policy for a
peer (group)
peer { peer-address | group-name }
route-policy route-policy-name import
Remove the ingress route policy of a
peer (group)
undo peer { peer-address | group-name }
route-policy policy-name import