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

Configuring OSPF between an MCE and a VPN site, Command, Remarks

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 11 highlights

Step 5. (Optional.) Configure the default cost value for the redistributed routes. Command default cost value Remarks If you do not specify a default cost value, the default cost value is 0. For more information about RIP, see Layer 3-IP Routing Configuration Guide. Configuring OSPF between an MCE and a VPN site An OSPF process can belong to a single VPN instance. If you create an OSPF process without binding it to a VPN instance, the process belongs to the public network. Binding OSPF processes to VPN instances can isolate routes of different VPNs. An OSPF process can belong to only one VPN instance, but one VPN instance can use multiple OSPF processes to advertise the VPN routes. An OSPF process that is bound with a VPN instance does not use the public network router ID configured in system view. Therefore, you must configure a router ID when starting the OSPF process. For more information about OSPF, see Layer 3-IP Routing Configuration Guide. To configure OSPF between an MCE and a VPN site: Step Command Remarks 1. Enter system view. system-view N/A 2. Create an OSPF process for a ospf [ process-id | router-id VPN instance and enter OSPF router-id | vpn-instance view. vpn-instance-name ] * Perform this configuration on the MCE. On the VPN site, create a normal OSPF process. 3. (Optional.) Configure the OSPF domain ID. domain-id domain-id [ secondary ] The default domain ID is 0. Perform this configuration only on the MCE. The domain ID of an OSPF process is included in the routes generated by the process. When an OSPF route is redistributed into BGP, the OSPF domain ID is included in the BGP VPN route and delivered as a BGP extended community attribute. An OSPF process can be configured with only one domain ID. Domain IDs of different OSPF processes are independent of each other. All OSPF processes of a VPN must be configured with the same domain ID for routes to be correctly advertised. OSPF processes on PEs in different VPNs can be configured with domain IDs as desired. 8

  • 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
8
Step
Command
Remarks
5.
(Optional.) Configure the
default cost value for the
redistributed routes.
default cost
value
If you do not specify a default cost
value, the default cost value is 0.
For more information about RIP, see
Layer 3—IP Routing Configuration Guide
.
Configuring OSPF between an MCE and a VPN site
An OSPF process can belong to a single VPN instance. If you create an OSPF process without binding
it to a VPN instance, the process belongs to the public network.
Binding OSPF processes to VPN instances can isolate routes of different VPNs. An OSPF process can
belong to only one VPN instance, but one VPN instance can use multiple OSPF processes to advertise the
VPN routes.
An OSPF process that is bound with a VPN instance does not use the public network router ID configured
in system view. Therefore, you must configure a router ID when starting the OSPF process.
For more information about OSPF, see
Layer 3—IP Routing Configuration Guide
.
To configure OSPF between an MCE and a VPN site:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create an OSPF process for a
VPN instance and enter OSPF
view.
ospf
[
process-id
|
router-id
router-id
|
vpn-instance
vpn-instance-name
] *
Perform this configuration on the
MCE. On the VPN site, create a
normal OSPF process.
3.
(Optional.) Configure the
OSPF domain ID.
domain-id
domain-id
[
secondary
]
The default domain ID is 0.
Perform this configuration only on
the MCE.
The domain ID of an OSPF process
is included in the routes generated
by the process. When an OSPF
route is redistributed into BGP, the
OSPF domain ID is included in the
BGP VPN route and delivered as a
BGP extended community
attribute.
An OSPF process can be
configured with only one domain
ID. Domain IDs of different OSPF
processes are independent of each
other.
All OSPF processes of a VPN must
be configured with the same
domain ID for routes to be correctly
advertised. OSPF processes on PEs
in different VPNs can be
configured with domain IDs as
desired.