Advertising the Routes of a PE in the Local AS to the Remote PE

After the routes of the loopback interface on a PE in an AS are advertised to the remote PE in another AS, the MP-EBGP peer relationship is established between PEs.

Procedure

Configure an ASBR to advertise the loopback address of a PE in the local AS to the remote ASBR.
Perform the following steps on each ASBR:
1. Run system-view
  The system view is displayed.
2. Run bgp as-number
  The BGP view is displayed.
3. Run network ip-address [ mask | mask-length ]
  The function to advertise the loopback address of a PE in the local AS to the remote ASBR is enabled.
4. Run quit
  Return to the system view.
5. Run commit
  The configuration is committed.
Configure the peer ASBR to import BGP routes to an IGP.
Perform the following steps on the peer ASBR:
- If OSPF runs between the PE and ASBR:
  1. Run system-view
    
    The system view is displayed.
  2. Run ospf process-id
    
    The OSPF view is displayed.
  3. Run import-route bgp [ cost cost ] [ route-policy route-policy-name ]
    
    BGP routes are imported to OSPF.
  4. Run quit
    
    Return to the system view.
  5. Run commit
    
    The configuration is committed.
- If IS-IS runs between the PE and ASBR:
  1. Run system-view
    
    The system view is displayed.
  2. Run isis process-id
    
    The IS-IS view is displayed.
  3. Run import-route bgp [ cost-type { external | internal } | cost cost | tag tag | route-policy route-policy-name | [ level-1 | level-2 | level-1-2 ] ] ^*
    
    BGP routes are imported to IS-IS.
    
    If the IS-IS level is not specified in the command, BGP routes will be imported into the Level-2 IS-IS routing table.
  4. Run quit
    
    Return to the system view.
  5. Run commit
    
    The configuration is committed.