You can apply a tag for IPv4 routes that BGP or OSPF redistribute into IS-IS. This configuration ensures that if one BEB redistributes a route into IS-IS from either protocol, other BEBs do not redistribute tagged IS-IS routes back into BGP or OSPF.
After you configure a route tag and then configure the protocol to automatically filter tagged routes, when BGP or OSPF receive a route with the matching tag, the switch blocks redistribution for that route. You can also create route-map policies to match the IS-IS route tag. For information about route policies, see Route Filtering and IP Policies.
The switch sends an administrative tag using TLV 135 for the GRT and TLV 184 for VRFs. The switch also transmits the tags into Multi-area SPB. If an area includes platforms that cannot calculate the TLV length in TLV 135, you can disable tag transmission.
Caution
To use IS-IS Route Tagging on GRT IS-IS routes, you must also configure the metric-type as external. If you want to use IS-IS tags on GRT as internal routes, all Fabric nodes must be above a minimum software version. Any switch in the SPB Fabric that runs earlier software versions triggers an exception if you use metric type internal. To ensure this does not occur, if you attempt to configure a tag and the metric-type is not external, the switch reminds you to upgrade the software on all devices. You must ensure all devices in the network run the minimum required software.
For more information about the metric type, see Configure the Metric Type for IS-IS Routes.
| NOS | Minimum software versions |
|---|---|
| Fabric Engine |
(Future release) 8.10.6 and later (Future release) 9.0.5 and later 9.1 and later |
| VOSS |
(Future release) 8.10.6 and later (Future release) 9.0.5 and later 9.1 and later |
| VSP 8600 Series | (Future release) 8.1.7 and later |
For CLI configuration, see the following tasks:
For EDM configuration, see the following tasks: