2960-x port up/down when Vivi box in use

[aandersne]

I have a Vivi box connected to a port on a 2960-X. As soon as a client connects to the Vivi the port on the switch starts going down and coming up constantly...

001120: 02:37:07: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down

001121: 02:37:10: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up

001122: 02:37:11: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up

001123: 02:37:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down

001124: 02:37:14: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down

001125: 02:37:16: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up

001126: 02:37:17: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up

001127: 02:37:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to down

001128: 02:37:50: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to down

001129: 02:37:58: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/1, changed state to up

If I plug the Vivi into a different switch (catalyst 3560) I don't see this. Is there some configuration on the switch that might cause this? The current port status is:

#sh int gi1/0/1

GigabitEthernet1/0/1 is up, line protocol is up (connected)

  Hardware is Gigabit Ethernet, address is 003c.100e.8081 (bia 003c.100e.8081)

  Description: ***WIRELESS AV VLAN***

  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,

     reliability 255/255, txload 3/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  Keepalive set (10 sec)

  Full-duplex, 100Mb/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 never, output 00:00:01, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 23

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 8000 bits/sec, 24 packets/sec

  5 minute output rate 1260000 bits/sec, 114 packets/sec

     253099 packets input, 20011673 bytes, 0 no buffer

     Received 1069 broadcasts (1009 multicasts)

     0 runts, 0 giants, 0 throttles

     1 input errors, 1 CRC, 0 frame, 0 overrun, 0 ignored

     0 watchdog, 1009 multicast, 0 pause input

     0 input packets with dribble condition detected

     923791 packets output, 1028133936 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

Cheers

Ash

[Leo Laohoo · Accepted solution]

On the 2960X interface, use the command "10 100 auto".

[aandersne]

Thanks Leo,

Forcing the speed to 10 stopped the flap.

Cheers

Ash

[grassopj]

Speed 10 100 auto is not actually a command for Cisco IOS , do you mean enter the commands:

Speed 10

Duplex full

?

-Pete

[aandersne]

Hi Pete,

I just entered "speed 10", left duplex at auto and the link started behaving.

Cheers

Ash

[grassopj]

Thanks Ash, Going to give it a try now !

-Pete

[grassopj]

Hi Ash,

That certainly stopped the link flap, but I would like to have a faster speed than 10mbits/sec on the Vivi due to wanting to stream HD video to the device.

So I contacted Vivi support about this issue, and they pointed me to this bug: CSCus35889. Apparently its an issue with EEE (Energy Efficient Ethernet) on some 2960X switches. I did a little testing and in my environment found the problem presented on any switch later than hardware revision 2. 

The solution is very easy, you apply this command to the port that the Vivi is plugged into, and the problem goes away:  no power efficient-ethernet

This worked very nicely for me, with the port signalling up at 100mbits/sec and no more link flap but your mileage may vary.

-Pete

[aandersne]

Thanks Pete,

Thats a much better solution! It definitely felt dirty throttling the link. I must have drawn the short straw with vivi support ;)

Cheers

Ash