Cable disconnected with macintosh and sg200 26 cisco router

jsoliveresr · ‎01-15-2013

I owe a SG200 26 port switch and it works fine so far.

Amacintosh computer (mountain lion) has been added to the wired net. Everything works fine t first, but there's a sudden disconnection issue.

It seems that the macintosh computer is not able to communicate to the switch, and the macintosh prompts a lack of cable connection. None of the lights on the switch are on.

If I plug the macintosh cable directly to a router ethernet port, it works properly.

I need some advise about that, please.

Does anybody know anything?

Thanks.

Tom Watts · ‎01-15-2013

Hi Juan, first thing I always do is be sure to have the latest firmware loaded to the switch.

Please verify that you are not using a wireless connection simultaneous with the wired connection.

A couple things I may recommend is to disable the Energy Efficient Ethernet options. If you navigate to port management -> Green Ethernet. Remove all the options on the properties and port settings.

You may also try to force manually negotiation on the switch port the computer connects to under port management -> port settings.

Lastly, you should ensure spanning tree port fast is enabled. It can take up to 52 seconds for a link to be recognized without portfast. I would recommend to go to Spanning Tree -> STP interface settings -> Look at the port number and see if edge port is enabled or disabled.

-Tom
Please mark answered for helpful posts

-Tom Please mark answered for helpful posts http://blogs.cisco.com/smallbusiness/

Clayton Sill · ‎01-15-2013

Hello Juan,

Just to add on to Toms notes. I've seen that model switch have issues auto negotiating to newer macs than older macs for some reason. When the speeds were manually set on the switch and mac there was a link up light. That switch was running a older firmware as well and once the firmware was upgraded to a new firmware it fixed the issue.

Thanks,
Clayton Sill

Christoph Franke · ‎01-19-2013

Hello everybody,

I encountered a similar problem with my 2011 iMac 27 and a Cisco SG300-10. Especially after coming from hibernation the Mac claims to have no ethernet connection (no physical cable attached) from time to time, although lights on the switch are on. I need to reboot the Mac in order to get the connection back.

Above that there seems to be some trouble negotiating the correct settings between those two devices. This is some typical console output from the Mac regarding its en0 interface after the wakeup:

19.01.13 09:17:13,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:17:17,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,2301,0de1,0300,c1e1,0800]

19.01.13 09:17:19,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:17:21,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,2303,0de1,0300,c1e1,0800]

19.01.13 09:17:23,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:17:25,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,2303,0de1,0300,c1e1,7800]

19.01.13 09:17:34,453 configd[16]: network changed: v6(en0+:fe80::2665:11ff:fe97:88b3) DNS+ Proxy+ SMB

19.01.13 09:17:36,275 configd[16]: network changed: v4(en0+:192.168.0.14) v6(en0:fe80::2665:11ff:fe97:88b3) DNS! Proxy SMB

19.01.13 09:17:45,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0 (wol enabled, BJP 818)

19.01.13 09:17:49,493 configd[16]: network changed: v4(en0-:192.168.0.14) v6(en0-:fe80::2665:11ff:fe97:88b3) DNS- Proxy- SMB-

19.01.13 09:18:04,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,0300,0de1,0300,c1e1,0800]

19.01.13 09:18:05,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:18:08,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,0300,0de1,0300,c1e1,0800]

19.01.13 09:18:09,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:18:12,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,0301,0de1,0300,c1e1,0800]

19.01.13 09:18:14,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0

19.01.13 09:18:17,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,0f00,0de1,0300,c1e1,7800]

19.01.13 09:18:20,111 mDNSResponder[40]: mDNS_RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:426C:8FFF:FE15:B51E)

19.01.13 09:18:21,970 configd[16]: network changed: v6(en0+:fe80::2665:11ff:fe97:88b3) DNS+ Proxy+ SMB

19.01.13 09:18:28,448 configd[16]: network changed: v4(en0+:192.168.0.14) v6(en0:fe80::2665:11ff:fe97:88b3) DNS! Proxy SMB

19.01.13 09:18:28,450 mDNSResponder[40]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.0.14)

19.01.13 09:19:04,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0 (wol enabled, BJP 826)

19.01.13 09:19:07,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [796d,0321,0181,0000,c1e1,0800]

19.01.13 09:19:08,184 configd[16]: network changed: v4(en0-:192.168.0.14) v6(en0-:fe80::2665:11ff:fe97:88b3) DNS- Proxy- SMB-

19.01.13 09:19:08,185 configd[16]: arp_client_transmit(en0) failed, Network is down (50)

19.01.13 09:19:08,185 configd[16]: bootp_session_transmit: bpf_write(en0) failed: Network is down (50)

19.01.13 09:19:08,185 configd[16]: DHCP en0: INIT-REBOOT transmit failed

19.01.13 09:19:08,186 configd[16]: DHCP en0: ARP detect ROUTER failed, arp_client_transmit(en0) failed, Network is down (50)

19.01.13 09:19:08,187 mDNSResponder[40]: DeregisterInterface: Frequent transitions for interface en0 (192.168.0.14)

As you can see, the link goes up and down like the Santa Maria on Columbus' first expedition. In addition to that there is no "EEE enabled" entry although the network chipset (BCM57765) is EEE compatible and the Cisco affirms "EEE Support on Remote" for the specific port.

I don't know if there is something wrong with the Mac OS X network driver (10.8.2) or with the switch firmware, at least I thought I let you know and maybe you can take a look or have a hint.

Regards,

Christoph

Clayton Sill · ‎01-21-2013

Hello Christoph,

Yeah I would manually set the speeds on both the port and the mac to see what would happen if you haven't already. Other than that what firmware version are you running? I remember on a 200 series switch that when I upgraded the firmware it fixed the auto nego. issue to a Mac that was going on even though when I manually set the speeds on the port and mac. Based on the logs though it does look like its something wrong with the auto nego.

Hope this helps!

Thanks,

Clayton Sill

Christoph Franke · ‎01-21-2013

Hello Clayton,

thanks for your response! Well, I use the latest firmware 1.2.7.76 on my three Cisco SG300-10 switches, so there is no upgrade to be made. I will try to alter EEE settings and disable Auto Negotiation and give feedback.

Regards,

Christoph

Clayton Sill · ‎01-21-2013

Hello Christoph,

If you are on the latest firmware then yeah I would manually set the speeds then. That should get you up and working if not let us know! I would test with 1000 full duplex and 100 full duplex if yo uhave issues with 1000.

Thanks,

Clayton Sill

Christoph Franke · ‎01-28-2013

Hello everybody,

after a week with fixed speed and duplex mode (1000 full duplex) on both ends I have not seen a single incident again. To be more precise the connection didn't drop again stating there was no cable attached to the iMac. What didn't stop was the link going up and down. From the switch log:

2147482889	2013-Jan-28 09:44:01	Warning	%STP-W-PORTSTATUS: gi2: STP status Forwarding
2147482890	2013-Jan-28 09:43:56	Informational	%LINK-I-Up: gi2
2147482891	2013-Jan-28 09:43:53	Warning	%LINK-W-Down: gi2
2147482892	2013-Jan-28 07:43:43	Warning	%STP-W-PORTSTATUS: gi2: STP status Forwarding
2147482893	2013-Jan-28 07:43:38	Informational	%LINK-I-Up: gi2
2147482894	2013-Jan-28 07:43:30	Warning	%LINK-W-Down: gi2
2147482895	2013-Jan-28 05:43:24	Warning	%STP-W-PORTSTATUS: gi2: STP status Forwarding
2147482896	2013-Jan-28 05:43:19	Informational	%LINK-I-Up: gi2
2147482897	2013-Jan-28 05:43:07	Warning	%LINK-W-Down: gi2
2147482898	2013-Jan-28 03:42:57	Warning	%STP-W-PORTSTATUS: gi2: STP status Forwarding
2147482899	2013-Jan-28 03:42:52	Informational	%LINK-I-Up: gi2
2147482900	2013-Jan-28 03:42:44	Warning	%LINK-W-Down: gi2
2147482901	2013-Jan-28 01:42:29	Warning	%STP-W-PORTSTATUS: gi2: STP status Forwarding
2147482902	2013-Jan-28 01:42:25	Informational	%LINK-I-Up: gi2
2147482903	2013-Jan-28 01:42:21	Warning	%LINK-W-Down: gi2

I have found this to occur to many people on this forum, but I have no clue where to look for a solution or how to stop this behaviour. Maybe a Cisco employee could help me out on this.

Regards,

Christoph

Clayton Sill · ‎01-28-2013

Christoph,

Yeah the only thing I could think of is maybe a bad cable? Sounds like it could be some type of Layer 1 issue going on or maybe something in STP options. Maybe try switch it to a different port just to see if you get different results.

Other than that you may want to call Cisco up and have a case open up with them if it gets to be a problem and you get no response from a Cisco employee on the fourms at this point.

Thanks!

Clayton Sill

Christoph Franke · ‎01-28-2013

Hello Clayton,

during my testing stage I already tried to change the cable, both cables I used were CAT6, but no luck. I also tried a different port which also did not help. Regarding STP I am not sure what option might cause the trouble (the switch is setup on defaults regarding that aspect). As you can see on the log I posted the link up/down entry occurs about every two hours. Maybe that helps.

Regards,

Christoph

Christoph Franke · ‎01-31-2013

Hi everybody,

doing some more research I can now happily report to have found the reason for the Link up/down symptom occuring every 2 hours. The root cause of this is a feature Apple came up with starting with Mac OS X 10.6 called "Wake on Demand" (see http://support.apple.com/kb/HT3774 for details) as a successor to "Wake on LAN".

As a part is this concept the clients registering themselves to the Bonjour Sleep Proxy Server every 2 hours cause a short interrupt of hibernation and the Link to up/down accordingly. Hope that helps somebody.

Inspite of this I have no clue why the Autonegotiation between the iMac and the Cisco switch would fail so miserably.

Regards,

Christoph

Clayton Sill · ‎01-31-2013

Hello Chris,

Thank you for the update and letting us know where the issue was at! I was at a lost on what could have been causing the issue but it makes since now since I am not familiar with Mac stuff lol. Glad everything is working fine now for you!

Thanks,

Clayton Sill