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.

Figure 162 show interface port-channel Command Example<br />

<strong>Force10</strong>>show interface port-channel 20<br />

Port-channel 20 is up, line protocol is up<br />

Hardware address is 00:01:e8:01:46:fa<br />

Internet address is 1.1.120.1/24<br />

MTU 1554 bytes, IP MTU 1500 bytes<br />

LineSpeed 2000 Mbit<br />

Members in this channel: Gi 9/10 Gi 9/17<br />

ARP type: ARPA, ARP timeout 04:00:00<br />

Last clearing of "show interface" counters 00:00:00<br />

Queueing strategy: fifo<br />

1212627 packets input, 1539872850 bytes<br />

Input 1212448 IP Packets, 0 Vlans 0 MPLS<br />

4857 64-byte pkts, 17570 over 64-byte pkts, 35209 over 127-byte pkts<br />

69164 over 255-byte pkts, 143346 over 511-byte pkts, 942523 over 1023-byte pkts<br />

Received 0 input symbol errors, 0 runts, 0 giants, 0 throttles<br />

42 CRC, 0 IP Checksum, 0 overrun, 0 discarded<br />

2456590833 packets output, 203958235255 bytes, 0 underruns<br />

Output 1640 Multicasts, 56612 Broadcasts, 2456532581 Unicasts<br />

2456590654 IP Packets, 0 Vlans, 0 MPLS<br />

0 throttles, 0 discarded<br />

Rate info (interval 5 minutes):<br />

Input 00.01Mbits/sec, 2 packets/sec<br />

Output 81.60Mbits/sec, 133658 packets/sec<br />

Time since last interface status change: 04:31:57<br />

<strong>Force10</strong>><br />

When more than one interface is added to a Layer 2 port channel, <strong>FTOS</strong> selects one of <strong>the</strong> active interfaces<br />

in <strong>the</strong> port channel to be <strong>the</strong> Primary Port. The primary port replies to flooding and sends protocol PDUs.<br />

An asterisk in <strong>the</strong> show interfaces port-channel brief command indicates <strong>the</strong> primary port.<br />

As soon as a physical interface is added to a port channel, <strong>the</strong> properties of <strong>the</strong> port channel determine <strong>the</strong><br />

properties of <strong>the</strong> physical interface. The configuration and status of <strong>the</strong> port channel are also applied to <strong>the</strong><br />

physical interfaces within <strong>the</strong> port channel. For example, if <strong>the</strong> port channel is in Layer 2 mode, you cannot<br />

add an IP address or a static MAC address to an interface that is part of that port channel. As Figure 163<br />

illustrates, interface GigabitE<strong>the</strong>rnet 1/6 is part of port channel 5, which is in Layer 2 mode, and an error<br />

message appeared when an IP address was configured.<br />

Figure 163 Error Message<br />

<strong>Force10</strong>(conf-if-portch)#show config<br />

!<br />

interface Port-channel 5<br />

no ip address<br />

switchport<br />

channel-member GigabitE<strong>the</strong>rnet 1/6<br />

<strong>Force10</strong>(conf-if-portch)#int gi 1/6<br />

<strong>Force10</strong>(conf-if)#ip address 10.56.4.4 /24<br />

% Error: Port is part of a LAG Gi 1/6.<br />

<strong>Force10</strong>(conf-if)#<br />

Error message<br />

260 Interfaces

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

Saved successfully!

Ooh no, something went wrong!