3Com S7902E, Руководство по настройке

Страница: 1545 / 2621

1-30
z
After configuring an IS-IS instance, you must start IS-IS by using the same method for starting a
common IS-IS process.
z
For description and detailed configuration about IS-IS, refer to IS-IS Configuration in the IP Routing
Volume .
Configuring EBGP Between PE and CE
1) On a PE
Follow these steps to configure EBGP between PE and CE on a PE:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
Required
Configure the CE as the VPN
peer
peer { group-name |
ip-address } as-number
as-number
Required
Inject the routes of the local
CEs
import-route protocol
[ process-id ] [ med med-value |
route-policy
route-policy-name
] *
Required
A PE needs to inject the routes
of the local CEs into its VPN
routing table so that it can
advertise them to the peer PE.
Configure BGP to filter routes
to be advertised
filter-policy { acl-number |
ip-prefix ip-prefix-name }
export [ direct | isis process-id
| ospf process-id | rip
process-id | static ]
Optional
By default, BGP does not filter
routes to be advertised.
Configure BGP to filter received
routes
filter-policy { acl-number |
ip-prefix ip-prefix-name }
import
Optional
By default, BGP does not filter
received routes.
Allow the local AS number to
appear in the AS_PATH
attribute of a received route and
set the maximum number of
repetitions
peer { group-name |
ip-address } allow-as-loop
[ number ]
Optional
For the hub and spoke
networking scheme