03-10-2015 10:29 PM - edited 03-07-2019 11:02 PM
Greetings!
I have a Cisco switch model WS-C3650-48TS-S and I configured in one of its interfaces flowcontrol receive on but when I check the interface using show interface I noticed that input flow-control off and output flow-control unsupported I wounder why the flow control not working even i configured it already?
Interface configuration
interface GigabitEthernet2/0/3
switchport access vlan 111
switchport mode access
flowcontrol receive on
show interface output
GigabitEthernet2/0/3 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is f8c2.8857.340d (bia f8c2.8857.340d)
Description: N5Strg iSCSI Port
MTU 9198 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 11/255, rxload 8/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:06, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 31653000 bits/sec, 3746 packets/sec
5 minute output rate 44204000 bits/sec, 4417 packets/sec
6668410425 packets input, 18568845018908 bytes, 0 no buffer
Received 8271 broadcasts (0 multicasts)
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
8040770794 packets output, 29759036783816 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 unknown protocol drops
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
Please help me if you know why it does not work
03-11-2015 02:07 AM
Hi,
Cisco Catalyst switches generally do not support output flow control - they never send PAUSE frames - so the message about the output flow control being unsupported is normal and expected.
Regarding the input flow control, this feature has to be advertised by the link partner during linkup and autonegotiation phase. In other words, the device connected to this port must itself advertise the ability to use flow control. If the input flow control is claimed to be off then it may be caused by the device connected to this port that does not advertise this capability. You should check its NIC settings and optionally try to shutdown/unshutdown the port to go over the autonegotiation again.
Please keep us informed!
Best regards,
Peter
03-29-2015 05:58 PM
Did you ever get this resolved I was seeing the same issue and bouncing the port didn't fix it.
Thanks
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