HP 6125XLG R2306-HP 6125XLG Blade Switch MCE Configuration Guide - Page 14

Configuring routing between an MCE and a PE, Command, Remarks, domain-id

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 14 highlights

Step 9. (Optional.) Configure a filtering policy to filter advertised routes. 10. (Optional.) Configure a filtering policy to filter received routes. Command Remarks filter-policy { acl-number | prefix-list ip-prefix-name } export [ direct | isis process-id | ospf process-id | rip process-id | static ] By default, BGP does not filter advertised routes. filter-policy { acl-number | By default, BGP does not filter prefix-list ip-prefix-name } import received routes. BGP checks routing loops by examining AS numbers. When EBGP is used, the MCE advertises routing information carrying the local AS number to the site and then receives routing updates from the site. The routing updates carry the AS number of the MCE, so the MCE discards them to avoid routing loops. To enable the MCE to receive such routes, configure the MCE to allow routing loops. Routes redistributed from OSPF to BGP on the MCE have their OSPF attributes removed. To enable BGP to distinguish routes redistributed from different OSPF domains, you must enable the redistributed routes to carry the OSPF domain ID by configuring the domain-id command in OSPF view. The domain ID is added to BGP VPN routes as an extended community attribute. BGP runs in a BGP VPN instance in the same way as it runs in a normal network. For more information about BGP, see Layer 3-IP Routing Configuration Guide. 2. Configure the VPN site: Step 1. Enter system view. 2. Enable BGP and enter BGP view. 3. Create and enter BGP-VPN IPv4 unicast instance view. 4. Enable BGP to exchange IPv4 unicast routing information with the specified peer or peer group. Command system-view bgp as-number ipv4-family [ unicast ] peer { group-name | ip-address } enable Remarks N/A By default, BGP is disabled. N/A By default, BGP does not exchange IPv4 unicast routing information with any peer or peer group. 5. Redistribute the IGP routes of the VPN. import-route protocol [ process-id ] [ med med-value | route-policy route-policy-name ] * By default, BGP does not redistribute any IGP routes. A VPN site must advertise the VPN network addresses it can reach to the connected MCE. Configuring routing between an MCE and a PE MCE-PE routing configuration includes these tasks: • Binding the MCE-PE interfaces to VPN instances. • Performing route configurations. • Redistributing VPN routes into the routing protocol running between the MCE and the PE. Configurations in this section are performed on the MCE. For information about configuring the PE, see the configuration guide for the PE. 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
11
Step
Command
Remarks
9.
(Optional.) Configure a
filtering policy to filter
advertised routes.
filter-policy
{
acl-number
|
prefix-list
ip-prefix-name
}
export
[
direct | isis
process-id
|
ospf
process-id
|
rip
process-id
|
static
]
By default, BGP does not filter
advertised routes.
10.
(Optional.) Configure a
filtering policy to filter
received routes.
filter-policy
{
acl-number
|
prefix-list
ip-prefix-name
}
import
By default, BGP does not filter
received routes.
BGP checks routing loops by examining AS numbers. When EBGP is used, the MCE advertises
routing information carrying the local AS number to the site and then receives routing updates from
the site. The routing updates carry the AS number of the MCE, so the MCE discards them to avoid
routing loops. To enable the MCE to receive such routes, configure the MCE to allow routing loops.
Routes redistributed from OSPF to BGP on the MCE have their OSPF attributes removed. To enable
BGP to distinguish routes redistributed from different OSPF domains, you must enable the
redistributed routes to carry the OSPF domain ID by configuring the
domain-id
command in OSPF
view. The domain ID is added to BGP VPN routes as an extended community attribute.
BGP runs in a BGP VPN instance in the same way as it runs in a normal network. For more
information about BGP, see
Layer 3—IP Routing Configuration Guide
.
2.
Configure the VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable BGP and enter BGP
view.
bgp
as-number
By default, BGP is disabled.
3.
Create and enter BGP-VPN
IPv4 unicast instance view.
ipv4-family
[
unicast
]
N/A
4.
Enable BGP to exchange
IPv4 unicast routing
information with the
specified peer or peer
group.
peer
{
group-name
|
ip-address
}
enable
By default, BGP does not
exchange IPv4 unicast routing
information with any peer or
peer group.
5.
Redistribute the IGP routes
of the VPN.
import-route
protocol
[
process-id
] [
med
med-value
|
route-policy
route-policy-name
]
*
By default, BGP does not
redistribute any IGP routes.
A VPN site must advertise the
VPN network addresses it can
reach to the connected MCE.
Configuring routing between an MCE and a PE
MCE-PE routing configuration includes these tasks:
•
Binding the MCE-PE interfaces to VPN instances.
•
Performing route configurations.
•
Redistributing VPN routes into the routing protocol running between the MCE and the PE.
Configurations in this section are performed on the MCE. For information about configuring the PE, see
the configuration guide for the PE.