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

Configuring EBGP between an MCE and a VPN site

Page 13 highlights

Step 4. (Optional.) Redistribute remote site routes advertised by the PE. 5. Return to system view. 6. Enter interface view. 7. Enable the IS-IS process on the interface. Command Remarks import-route { isis [ process-id ] | ospf [ process-id ] | rip [ process-id ] | bgp [ allow-ibgp ] | direct | static } [ cost cost | cost-type { external | internal } | [ level-1 | level-1-2 | level-2 ] | route-policy route-policy-name | tag tag ] * By default, IS-IS does not redistribute routes of any other routing protocol. If you do not specify the route level in the command, the command redistributes routes to the level-2 routing table by default. quit N/A interface interface-type interface-number N/A isis enable [ process-id ] By default, IS-IS is disabled. For more information about IS-IS, see Layer 3-IP Routing Configuration Guide. Configuring EBGP between an MCE and a VPN site To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on the VPN sites. 1. Configure the MCE: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter BGP view. bgp as-number N/A 3. Enter BGP-VPN instance view. ip vpn-instance vpn-instance-name N/A 4. Specify an EBGP peer or peer group. peer { group-name | ip-address } By default, no BGP peer or peer [ as-number as-number ] group is specified. 5. Create and enter BGP-VPN IPv4 unicast instance view. ipv4-family [ unicast ] N/A 6. Enable exchange of IPv4 unicast routes with the specified peer or peer group. peer { group-name | ip-address } enable BGP cannot exchange IPv4 unicast routes with any peer or peer group. 7. Allow routing loops: allow the local AS number to appear in the AS_PATH attribute of routes received from the peer or peer group and specify the maximum peer { group-name | ip-address } allow-as-loop [ number ] By default, the local AS number is not allowed to appear in the AS_PATH attribute of routes from a peer or peer group. appearance times. 8. Redistribute remote site import-route protocol routes advertised by the PE. [ process-id | all-processes ] By default, BGP does not redistribute routes from any other routing protocol. 10

  • 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

10
Step
Command
Remarks
4.
(Optional.) Redistribute
remote site routes advertised
by the PE.
import-route
{
isis
[
process-id
]
|
ospf
[
process-id
] |
rip
[
process-id
]
|
bgp
[
allow-ibgp
] |
direct
|
static
} [
cost
cost
|
cost-type
{
external
|
internal
} |
[
level-1
|
level-1-2
|
level-2
] |
route-policy
route-policy-name
|
tag
tag
] *
By default, IS-IS does not
redistribute routes of any other
routing protocol.
If you do not specify the route level
in the command, the command
redistributes routes to the level-2
routing table by default.
5.
Return to system view.
quit
N/A
6.
Enter interface view.
interface
interface-type
interface-number
N/A
7.
Enable the IS-IS process on
the interface.
isis enable
[
process-id
]
By default, IS-IS is disabled.
For more information about IS-IS, see
Layer 3—IP Routing Configuration Guide
.
Configuring EBGP between an MCE and a VPN site
To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a
BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on
the VPN sites.
1.
Configure the MCE:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter BGP-VPN instance
view.
ip vpn-instance
vpn-instance-name
N/A
4.
Specify an EBGP peer or
peer group.
peer
{
group-name
|
ip-address
}
[
as-number
as-number
]
By default, no BGP peer or peer
group is specified.
5.
Create and enter BGP-VPN
IPv4 unicast instance view.
ipv4-family
[
unicast
]
N/A
6.
Enable exchange of IPv4
unicast routes with the
specified peer or peer
group.
peer
{
group-name
|
ip-address
}
enable
BGP cannot exchange IPv4
unicast routes with any peer or
peer group.
7.
Allow routing loops: allow
the local AS number to
appear in the AS_PATH
attribute of routes received
from the peer or peer group
and specify the maximum
appearance times.
peer
{
group-name
|
ip-address
}
allow-as-loop
[
number
]
By default, the local AS number
is not allowed to appear in the
AS_PATH attribute of routes from
a peer or peer group.
8.
Redistribute remote site
routes advertised by the PE.
import-route
protocol
[
process-id
|
all-processes
]
By default, BGP does not
redistribute routes from any other
routing protocol.