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.

• Once <strong>the</strong> virtual IP address is removed, <strong>the</strong> system is accessible through <strong>the</strong> native IP address of <strong>the</strong><br />

primary RPM’s management interface.<br />

• Primary and secondary management interface IP and virtual IP must be in <strong>the</strong> same subnet.<br />

Management Interface on <strong>the</strong> S-<strong>Series</strong><br />

You can manage <strong>the</strong> S-<strong>Series</strong> from any port. Configure an IP address <strong>for</strong> <strong>the</strong> port using <strong>the</strong> ip address<br />

command, and enable it using <strong>the</strong> command no shutdown. You may use <strong>the</strong> command description from<br />

INTERFACE mode to note that <strong>the</strong> interface as <strong>the</strong> management interface. There is no separate<br />

management routing table, so you must configure all routes in <strong>the</strong> IP routing table (<strong>the</strong> ip route command).<br />

As shown in Figure 160, from EXEC Privilege mode, display <strong>the</strong> configuration <strong>for</strong> <strong>the</strong> port you are using<br />

to manage <strong>the</strong> system with <strong>the</strong> command show interface, and <strong>the</strong> routing table with <strong>the</strong> show ip route<br />

command.<br />

Figure 160 Viewing Management Routes on <strong>the</strong> S-<strong>Series</strong><br />

R1#show int gig 0/48<br />

GigabitE<strong>the</strong>rnet 0/48 is up, line protocol is up<br />

Description: This is <strong>the</strong> Managment Interface<br />

Hardware is <strong>Force10</strong>Eth, address is 00:01:e8:cc:cc:ce<br />

Current address is 00:01:e8:cc:cc:ce<br />

Pluggable media not present<br />

Interface index is 46449666<br />

Internet address is 10.11.131.240/23<br />

[output omitted]<br />

R1#show ip route<br />

Codes: C - connected, S - static, R - RIP,<br />

B - BGP, IN - internal BGP, EX - external BGP,LO - Locally Originated,<br />

O - OSPF, IA - OSPF inter area, N1 - OSPF NSSA external type 1,<br />

N2 - OSPF NSSA external type 2, E1 - OSPF external type 1,<br />

E2 - OSPF external type 2, i - IS-IS, L1 - IS-IS level-1,<br />

L2 - IS-IS level-2, IA - IS-IS inter area, * - candidate default,<br />

> - non-active route, + - summary route<br />

Gateway of last resort is 10.11.131.254 to network 0.0.0.0<br />

Destination Gateway Dist/Metric Last Change<br />

----------- ------- ----------- -----------<br />

*S 0.0.0.0/0 via 10.11.131.254, Gi 0/48 1/0 1d2h<br />

C 10.11.130.0/23 Direct, Gi 0/48 0/0 1d2h<br />

R1#<br />

Loopback Interfaces<br />

A Loopback interface is a virtual interface in which <strong>the</strong> software emulates an interface. Packets routed to it<br />

are processed locally. Since this interface is not a physical interface, you can configure routing protocols<br />

on this interface to provide protocol stability. You can place Loopback interfaces in default Layer 3 mode.<br />

254 Interfaces

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

Saved successfully!

Ooh no, something went wrong!