24.12.3 Extranet
The following two methods are available for implementing an extranet:
-
Route exchange between VRFs
-
Static routing across VRFs
The following describes the exchange of routes between VRFs that uses a routing table and static routing across VRFs. Routes that can be imported between VRFs are also described.
- <Structure of this section>
(1) Exchanging routes between VRF
An extranet can be implemented by exchanging routing information held by VRFs with other VRFs.
The following figure shows an example of exchanging routes between VRFs.
|
|
![[Figure Data]](./GRAPHICS/ZU319060.GIF)
(2) Static routing across VRF
An extranet can be implemented by creating a static route that uses a gateway for another VRF as the next hop.
The following figure shows static routing across VRFs.
|
|
![[Figure Data]](./GRAPHICS/ZU319070.GIF)
(3) Routes that can be imported between VRF
The following table describes the types of routes that can be imported from another VRF or the global network.
|
Route type |
Importable? |
|---|---|
|
Inactive path |
NG |
|
Route whose deletion is pending |
NG |
|
Route imported for an extranet |
NG |
|
Summarized route |
OK |
|
Route of an IPv6 device address specified for a loopback interface |
OK |
|
Route directly connected to a VLAN interface (global address) |
OK |
|
Route directly connected to a VLAN interface (link-local address) |
NG |
|
Direct connection route of management port |
NG |
|
Route whose output interface is a VLAN interface |
OK |
|
Route whose output interface is a loopback interface |
OK |
|
Route where the output interface becomes the management port |
NG |
|
Route whose output interface is a null interface |
OK |
Legend: Y: Imported, N: Not imported
If the routes to be imported match multiple route types, import is possible only when all the matching route types can be imported.