11-13-2007 10:10 PM - edited 03-05-2019 07:24 PM
Team,
We have configured port-channel but when we checked the interface utilization one interface is utilizing 100% where as other is only 10%. Below is the configuration and show intface outputs from both interfaces. Please review and suggest us some valuable recommendation to overcome this issue.
11-13-2007 10:18 PM
Can you post the "show interface Port-channel167" status, that would help to identify whether the port channel has been formed or not.
11-13-2007 10:23 PM
Here you go:-
ECC2DS1#show interfaces port-channel 167
Port-channel167 is up, line protocol is up (connected)
Hardware is EtherChannel, address is 000f.35e3.8c00 (bia 000f.35e3.8c00)
Description: Seismic clusters main switch connection
Internet address is 10.4.167.251/24
MTU 1500 bytes, BW 2000000 Kbit, DLY 10 usec,
reliability 255/255, txload 14/255, rxload 52/255
Encapsulation ARPA, loopback not set
Full-duplex, 1000Mb/s
input flow-control is off, output flow-control is unsupported
Members in this channel: Gi9/19 Gi9/20
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output 00:00:07, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 411533000 bits/sec, 35539 packets/sec
5 minute output rate 114001000 bits/sec, 51058 packets/sec
L2 Switched: ucast: 90761 pkt, 12135018 bytes - mcast: 2319365 pkt, 329672961 bytes
L3 in Switched: ucast: 257253669357 pkt, 361338645892673 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 179903974962 pkt, 57161721819623 bytes mcast: 0 pkt, 0 bytes
256930279756 packets input, 360850038698399 bytes, 0 no buffer
Received 6595162 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
179752237751 packets output, 57126569116323 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
ECC2DS1#
11-13-2007 10:35 PM
hi
if u c the interface 9/20, the rx load is 252/255 that should not be like that normally. do one thing shut the port and noshut again then c the load, may be this can solve ur problem or else change the port.
11-13-2007 11:20 PM
The following reponse I got from Cisco TAC:- Please review and suggst your recommendations.
Here is the documentation that you requested.
http://www.cisco.com/en/US/tech/tk389/tk213/technologies_tech_note09186a0080094714.shtml#cat6k
If one link within the bundle is favored by the load-distribution algorithm, that link will carry a disproportionate amount of traffic. In other words, the load isn't always distributed equally among the individual links.
In an Etherchannel, load balancing is present but it does not necessarily mean that they will be 50-50. EtherChannel load balancing can use MAC addresses, IP addresses, or Layer 4 port numbers with a Policy Feature Card 2 (PFC2) and either source mode, destination mode, or both. The mode you select applies to all EtherChannels that you configure on the switch. Use the option that provides the greatest variety in your configuration. For example, if the traffic on a channel only goes to a single MAC address, use of the destination MAC address results in the choice of the same link in the channel each time. Use of source addresses or IP addresses can result in a better load balance. Issue the port-channel load-balance {src-mac | dst-mac | src-dst-mac | src-ip | dst-ip | src-dst-ip | src-port | dst-port | src-dst-port} global configuration command in order to configure the load balancing.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide