Configure Fabric Extend

Use the following procedure to configure Fabric Extend (FE) between a Main office to a Branch office. This is a typical deployment. However, if your deployment creates tunnels between two switches that support Fabric Extend natively, then repeat those steps and ignore the steps for switches that require an ONA.

Note

VRF is an optional parameter. If a VRF is not configured, then FE uses the GRT.

Before you begin

The tunnel source IP address can be a brouter port IP, a CLIP IP, or a VLAN IP.

Note

Product Notice: Except VSP 8600 Series, all product series support a VLAN IP as the Fabric Extend tunnel source IP address.

For information about product support, see Fabric Extend Considerations.

If using the tunnel originating address on the GRT, Fabric Extend has the following requirements:

• The tunnel source IP address must be on the GRT, not on a VRF.

  

  Note

  A best practice is to use separate IP addresses for the SPBM IP Shortcuts ip-source-address command and the Fabric Extend ip-tunnel-source-address command. However, if you want these IP addresses to be the same, you MUST exclude the ip-source-address address with an IS-IS accept policy. You cannot use the redistribute command with a route map exclusion.

  Specify a CLIP interface to use as the source address for SPBM IP shortcuts.

• If IP Shortcuts is enabled, you must configure an IS-IS accept policy or exclude route-map to ensure that tunnel destination IP addresses are not learned through IS-IS.

If you are using the tunnel originating address on a VRF, Fabric Extend has the following requirements:

• Configure a CLIP and tunnel source IP address on the VRF.

• Remote management of the VSP 4450 Series is only possible after establishing IP Shortcut over IS-IS. (Alternatively, you can enable GRT-VRF redistribution locally.)

The following steps are for platforms that support FE natively:

1. Enter IS-IS Router Configuration mode:

   enable

   configure terminal

   router isis

2. Configure the IP tunnel source address:

   ip-tunnel-source-address <A.B.C.D> [vrf WORD<1–16>]

3. Enter Global Configuration mode:

   exit

4. Use one of the following commands to create a logical IS-IS interface:

   • In a network with a Layer 3 Core, enter logical-intf isis <1–255> dest-ip <A.B.C.D> [name WORD<1–64>] [mtu <750-9000>]

   • In a network with a Layer 2 Core, enter logical-intf isis <1–255> vid <list of vids> primary-vid <2–4059> port <slot/port> mlt <mltId> [name WORD<1–64>] [mtu <750-9000>]

     

     Note

     The primary VLAN ID (primary-vid must be one of the VIDs in the vid <list of vids>.

The following steps are for platforms that require an ONA to support FE:

Note

The interface VLAN connecting to the ONA network port is always in the GRT and the member port that the VLAN is part of is always an access port.

5. Enter IS-IS Router Configuration mode:

   enable

   configure terminal

   router isis

6. Configure the IP tunnel source address on the port that connects to the Device side of the ONA:

   ip-tunnel-source-address <A.B.C.D> port <slot/port> [mtu <mtu_value>] [vrf WORD<1–16>]

7. Exit back into Global Configuration mode:

   exit

8. Use one of the following commands to create a logical IS-IS interface:

   • In a network with a Layer 3 Core, enter:

     logical-intf isis <1–255> dest-ip <A.B.C.D> [name WORD<1–64>]

   • In a network with a Layer 2 Core, enter:

     logical-intf isis <1–255> vid <list of vids> primary-vid <2–4059> port <slot/port> mlt <mltId> [name WORD<1–64>]

     

     Note

     The primary VLAN ID (primary-vid) must be one of the VIDs in the vid <list of vids>.