Match Metric Type for IS-IS Routes

About this task

Use this procedure to match the external metric-type by using a route-map for any of the following cases:
  • accepting a remote IS-IS route with the help of IS-IS accept policies.

  • redistributing IS-IS routes into other protocols.

Before you begin

  • You must configure the required SPBM and IS-IS infrastructure.

  • You must log on to the route-map configuration mode in the CLI.

Procedure

  1. Enter Route-Map Configuration mode:

    enable

    configure terminal

    route-map WORD<1-64> <1-65535>

  2. Match IS-IS metric type:

    match metric-type-isis {any|internal|external}

  3. Permit the route policy action:

    permit

  4. Enable the route policy

    enable

Example

Match metric type for IS-IS routes:
Switch:1> enable
Switch:1# configure terminal
Switch:1(config)# route-map ro1 10
Switch:1(route-map)# match metric-type-isis internal
Switch:1(route-map)# permit
Switch:1(route-map)# enable
Match metric type for IS-IS routes in accept policies:
Switch:1> enable
Switch:1# configure terminal
Switch:1(config)# route-map ro1 10
Switch:1(route-map)# match metric-type-isis internal
Switch:1(route-map)# permit
Switch:1(route-map)# enable
Switch:1(route-map)# exit
Switch:1(config)# router isis
Switch:1(config-isis)# accept route-map ro1
Switch:1(config-isis)# exit
Switch:1(config)# isis apply accept
Match metric type to redistribute IS-IS routes into some other protocol (OSPF,RIP,BGP)
Switch:1> enable
Switch:1# configure terminal
Switch:1(config)# route-map ro1 10
Switch:1(route-map)# match metric-type-isis internal
Switch:1(route-map)# permit
Switch:1(route-map)# enable
Switch:1(route-map)# exit
Switch:1(config)# router bgp
Switch:1(router-bgp)# redistribute isis route-map ro1
Switch:1(router-bgp)# exit
Switch:1(config)# ip bgp apply redistribute

Variable Definitions

The following table defines parameters for the match metric-type-isis command.

Variable

Value

metric-type-isis {any|internal|external}

Specifies the IS-IS metric type:

  • internal – permits or denies routes that are internal to the IS-IS domain.

  • external – permits or denies routes that originate from an external routing protocol domain.

  • any – permits or denies both internal routes as well as external routes.