02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Command Syntax Command Mode Purpose<br />

match interface interface CONFIG-ROUTE-MAP Match routes whose next hop is a specific<br />

interface. The parameters are:<br />

• For a Fast E<strong>the</strong>rnet interface, enter <strong>the</strong><br />

keyword FastE<strong>the</strong>rnet followed by <strong>the</strong><br />

slot/port in<strong>for</strong>mation.<br />

• For a 1-Gigabit E<strong>the</strong>rnet interface, enter<br />

<strong>the</strong> keyword gigabitE<strong>the</strong>rnet followed<br />

by <strong>the</strong> slot/port in<strong>for</strong>mation.<br />

• For a loopback interface, enter <strong>the</strong><br />

keyword loopback followed by a number<br />

between zero (0) and 16383.<br />

• For a port channel interface, enter <strong>the</strong><br />

keyword port-channel followed by a<br />

number from 1 to 255 <strong>for</strong> TeraScale, 1 to<br />

32 <strong>for</strong> E<strong>the</strong>rScale.<br />

• For a SONET interface, enter <strong>the</strong> keyword<br />

sonet followed by <strong>the</strong> slot/port<br />

in<strong>for</strong>mation.<br />

• For a 10-Gigabit E<strong>the</strong>rnet interface, enter<br />

<strong>the</strong> keyword tengigabitE<strong>the</strong>rnet<br />

followed by <strong>the</strong> slot/port in<strong>for</strong>mation.<br />

• For a VLAN, enter <strong>the</strong> keyword vlan<br />

followed by a number from 1 to 4094.<br />

match ip address<br />

prefix-list-name<br />

match ipv6 address<br />

prefix-list-name<br />

match ip next-hop<br />

{access-list-name | prefix-list<br />

prefix-list-name}<br />

match ipv6 next-hop<br />

{access-list-name | prefix-list<br />

prefix-list-name}<br />

match ip route-source<br />

{access-list-name | prefix-list<br />

prefix-list-name}<br />

match ipv6 route-source<br />

{access-list-name | prefix-list<br />

prefix-list-name}<br />

CONFIG-ROUTE-MAP Match destination routes specified in a prefix<br />

list (IPv4).<br />

CONFIG-ROUTE-MAP Match destination routes specified in a prefix<br />

list (IPv6).<br />

CONFIG-ROUTE-MAP Match next-hop routes specified in a prefix list<br />

(IPv4).<br />

CONFIG-ROUTE-MAP Match next-hop routes specified in a prefix list<br />

(IPv6).<br />

CONFIG-ROUTE-MAP Match source routes specified in a prefix list<br />

(IPv4).<br />

CONFIG-ROUTE-MAP Match source routes specified in a prefix list<br />

(IPv6).<br />

match metric metric-value CONFIG-ROUTE-MAP Match routes with a specific value.<br />

match origin {egp | igp |<br />

incomplete}<br />

match route-type {external<br />

[type-1 | type-2] | internal |<br />

level-1 | level-2 | local }<br />

CONFIG-ROUTE-MAP Match BGP routes based on <strong>the</strong> ORIGIN<br />

attribute.<br />

CONFIG-ROUTE-MAP Match routes specified as internal or external<br />

to OSPF, ISIS level-1, ISIS level-2, or locally<br />

generated.<br />

match tag tag-value CONFIG-ROUTE-MAP Match routes with a specific tag.<br />

362 IP Access Control Lists, Prefix Lists, and Route-maps

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!