cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
6015
Views
0
Helpful
27
Replies

SF-300-48P POE is power cycling

Hello,

I have a SF-300-48P that is power cycling all POE ports (in use) exactly every 30 minutes. The other older cisco POE switches we were replacing did not have this issue. We have about 40 cisco SPA942 IP phones connected to it. Power consumption is about 175 watts total.

This is my second switch, previously tried a SG500X-48P with the same result.

Any ideas how to stop it from cycling?

Thanks for the help,

David

27 Replies 27

Tom Watts
VIP Alumni
VIP Alumni

Hello David, what version firmware is the switch running?  If you remove any amount of phones does the switch stop dropping?

-Tom
Please rate helpful posts

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

Version: 1.1.2

To add to the info, I just realized, one of the old 24 port switches (still in use) is cycling its ports as well. This switch is plugged into the SF-300 via a standard 10/100 port.

I actually do recall this happening with the first new switch i tried as well. After removing the new switch and placing the other old switch back in place the power cycling stopped. Seems like less of a switch issue and maybe a power issue but I don't see why the 2 old 24 port switches play nice together.

More info: the VOIP phones register offsite at the ISPs location.

Almost forgot, removing phones does not appear to resolve the issue. Removing all phones, of course does (on the specific switch)...but there's nothing plugged into the switch at that point.

David, if you could please do the following

config t

log file debug

log console debug

Additionally, please post a

show run

Also please provide

show run interface fa10  (just a port that has a phone connecting).

-Tom
Please rate helpful posts

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

switch3bb80b#show run

voice vlan oui-table add 0001e3 Siemens_AG_phone________

voice vlan oui-table add 00036b Cisco_phone_____________

voice vlan oui-table add 00096e Avaya___________________

voice vlan oui-table add 000fe2 H3C_Aolynk______________

voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone

voice vlan oui-table add 00d01e Pingtel_phone___________

voice vlan oui-table add 00e075 Polycom/Veritel_phone___

voice vlan oui-table add 00e0bb 3Com_phone______________

interface vlan 1

ip address 10.32.1.10 255.255.255.0

exit

interface vlan 1

no ip address dhcp

exit

hostname switch3bb80b

logging console debugging

logging file debugging

username privilege 15

no snmp-server server

switch3bb80b#

show run interface shows "Empty configuration"

Okay, next time the phones reboot provide the following 2 commands

show log

show log file

Additionally, please choose 1 phone port and do the following

config t

int fa10

negotiation 100f

Choose another phone port

config t

int fa11

negotiation 10h

With these 2 changes, lets see if those 2 phones survive the reboot.

-Tom
Please rate helpful posts

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

Show Log:

04-Dec-2012 13:05:24 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 13:04:37 :%STP-W-PORTSTATUS: fa38: STP status Forwarding

04-Dec-2012 13:04:33 :%LINK-I-Up:  fa38

04-Dec-2012 13:04:24 :%LINK-W-Down:  fa38

04-Dec-2012 13:04:21 :%STP-W-PORTSTATUS: fa32: STP status Forwarding

04-Dec-2012 13:04:20 :%STP-W-PORTSTATUS: fa41: STP status Forwarding

04-Dec-2012 13:04:19 :%STP-W-PORTSTATUS: fa5: STP status Forwarding

04-Dec-2012 13:04:17 :%LINK-I-Up:  fa32

04-Dec-2012 13:04:16 :%STP-W-PORTSTATUS: fa8: STP status Forwarding

04-Dec-2012 13:04:16 :%LINK-I-Up:  fa41

04-Dec-2012 13:04:15 :%STP-W-PORTSTATUS: fa2: STP status Forwarding

04-Dec-2012 13:04:15 :%LINK-I-Up:  fa5

04-Dec-2012 13:04:15 :%STP-W-PORTSTATUS: fa42: STP status Forwarding

04-Dec-2012 13:04:14 :%STP-W-PORTSTATUS: fa22: STP status Forwarding

04-Dec-2012 13:04:12 :%LINK-I-Up:  fa8

04-Dec-2012 13:04:11 :%LINK-I-Up:  fa2

04-Dec-2012 13:04:10 :%LINK-I-Up:  fa42

04-Dec-2012 13:04:10 :%LINK-I-Up:  fa22

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa32

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa5

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa41

04-Dec-2012 13:04:06 :%STP-W-PORTSTATUS: fa7: STP status Forwarding

04-Dec-2012 13:04:03 :%LINK-W-Down:  fa8

04-Dec-2012 13:04:03 :%LINK-W-Down:  fa2

04-Dec-2012 13:04:02 :%LINK-W-Down:  fa42

04-Dec-2012 13:04:01 :%LINK-I-Up:  fa7

04-Dec-2012 13:04:01 :%LINK-W-Down:  fa22

04-Dec-2012 13:04:01 :%STP-W-PORTSTATUS: fa26: STP status Forwarding

04-Dec-2012 13:03:58 :%STP-W-PORTSTATUS: fa37: STP status Forwarding

04-Dec-2012 13:03:58 :%STP-W-PORTSTATUS: fa39: STP status Forwarding

04-Dec-2012 13:03:57 :%LINK-I-Up:  fa26

04-Dec-2012 13:03:53 :%LINK-I-Up:  fa37

04-Dec-2012 13:03:53 :%LINK-I-Up:  fa39

04-Dec-2012 13:03:53 :%LINK-W-Down:  fa7

04-Dec-2012 13:03:48 :%LINK-W-Down:  fa26

04-Dec-2012 13:03:46 :%STP-W-PORTSTATUS: fa36: STP status Forwarding

04-Dec-2012 13:03:46 :%STP-W-PORTSTATUS: fa19: STP status Forwarding

04-Dec-2012 13:03:46 :%STP-W-PORTSTATUS: fa12: STP status Forwarding

04-Dec-2012 13:03:45 :%LINK-W-Down:  fa39

04-Dec-2012 13:03:45 :%LINK-W-Down:  fa37

04-Dec-2012 13:03:43 :%STP-W-PORTSTATUS: fa21: STP status Forwarding

04-Dec-2012 13:03:42 :%LINK-I-Up:  fa36

04-Dec-2012 13:03:42 :%LINK-I-Up:  fa19

04-Dec-2012 13:03:41 :%LINK-I-Up:  fa12

04-Dec-2012 13:03:38 :%LINK-I-Up:  fa21

04-Dec-2012 13:03:34 :%LINK-W-Down:  fa36

04-Dec-2012 13:03:33 :%LINK-W-Down:  fa12

04-Dec-2012 13:03:33 :%LINK-W-Down:  fa19

04-Dec-2012 13:03:31 :%LINK-W-Down:  fa21

04-Dec-2012 13:03:27 :%STP-W-PORTSTATUS: fa35: STP status Forwarding

04-Dec-2012 13:03:23 :%LINK-I-Up:  fa35

04-Dec-2012 13:03:15 :%LINK-W-Down:  fa35

04-Dec-2012 13:00:24 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:55:24 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:50:23 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:45:23 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:40:23 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:35:23 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 12:34:23 :%STP-W-PORTSTATUS: fa38: STP status Forwarding

04-Dec-2012 12:34:19 :%LINK-I-Up:  fa38

04-Dec-2012 12:34:10 :%LINK-W-Down:  fa38

04-Dec-2012 12:34:06 :%STP-W-PORTSTATUS: fa41: STP status Forwarding

04-Dec-2012 12:34:03 :%STP-W-PORTSTATUS: fa8: STP status Forwarding

04-Dec-2012 12:34:02 :%STP-W-PORTSTATUS: fa32: STP status Forwarding

04-Dec-2012 12:34:02 :%STP-W-PORTSTATUS: fa2: STP status Forwarding

04-Dec-2012 12:34:02 :%LINK-I-Up:  fa41

04-Dec-2012 12:34:01 :%STP-W-PORTSTATUS: fa42: STP status Forwarding

04-Dec-2012 12:34:00 :%STP-W-PORTSTATUS: fa22: STP status Forwarding

04-Dec-2012 12:33:59 :%STP-W-PORTSTATUS: fa5: STP status Forwarding

04-Dec-2012 12:33:58 :%LINK-I-Up:  fa8

04-Dec-2012 12:33:58 :%LINK-I-Up:  fa32

04-Dec-2012 12:33:57 :%LINK-I-Up:  fa2

04-Dec-2012 12:33:57 :%LINK-I-Up:  fa42

04-Dec-2012 12:33:56 :%LINK-I-Up:  fa22

04-Dec-2012 12:33:54 :%LINK-I-Up:  fa5

04-Dec-2012 12:33:53 :%LINK-W-Down:  fa41

04-Dec-2012 12:33:52 :%STP-W-PORTSTATUS: fa7: STP status Forwarding

04-Dec-2012 12:33:49 :%LINK-W-Down:  fa8

04-Dec-2012 12:33:49 :%LINK-W-Down:  fa32

04-Dec-2012 12:33:49 :%LINK-W-Down:  fa2

04-Dec-2012 12:33:48 :%LINK-W-Down:  fa42

04-Dec-2012 12:33:48 :%LINK-I-Up:  fa7

04-Dec-2012 12:33:48 :%STP-W-PORTSTATUS: fa26: STP status Forwarding

04-Dec-2012 12:33:47 :%LINK-W-Down:  fa22

04-Dec-2012 12:33:44 :%STP-W-PORTSTATUS: fa37: STP status Forwarding

04-Dec-2012 12:33:43 :%LINK-I-Up:  fa26

04-Dec-2012 12:33:42 :%LINK-W-Down:  fa5

04-Dec-2012 12:33:40 :%STP-W-PORTSTATUS: fa39: STP status Forwarding

04-Dec-2012 12:33:40 :%LINK-I-Up:  fa37

04-Dec-2012 12:33:39 :%LINK-W-Down:  fa7

04-Dec-2012 12:33:36 :%LINK-I-Up:  fa39

04-Dec-2012 12:33:35 :%LINK-W-Down:  fa26

04-Dec-2012 12:33:33 :%STP-W-PORTSTATUS: fa36: STP status Forwarding

04-Dec-2012 12:33:33 :%STP-W-PORTSTATUS: fa12: STP status Forwarding

04-Dec-2012 12:33:32 :%STP-W-PORTSTATUS: fa19: STP status Forwarding

04-Dec-2012 12:33:31 :%LINK-W-Down:  fa37

04-Dec-2012 12:33:30 :%STP-W-PORTSTATUS: fa21: STP status Forwarding

04-Dec-2012 12:33:29 :%LINK-I-Up:  fa36

04-Dec-2012 12:33:28 :%LINK-I-Up:  fa12

04-Dec-2012 12:33:28 :%LINK-W-Down:  fa39

04-Dec-2012 12:33:28 :%LINK-I-Up:  fa19

04-Dec-2012 12:33:25 :%LINK-I-Up:  fa21

04-Dec-2012 12:33:21 :%LINK-W-Down:  fa36

04-Dec-2012 12:33:20 :%LINK-W-Down:  fa12

04-Dec-2012 12:33:19 :%LINK-W-Down:  fa19

04-Dec-2012 12:33:18 :%LINK-W-Down:  fa21

04-Dec-2012 12:33:14 :%STP-W-PORTSTATUS: fa35: STP status Forwarding

04-Dec-2012 12:33:10 :%LINK-I-Up:  fa35

switch3bb80b#

Show Log File:

switch3bb80b#show log file04-Dec-2012 13:10:24 %CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

Logging is enabled.

Console Logging: Level debug. Console Messages: 1 Dropped.

Buffer Logging: Level info. Buffer Messages: 200 Logged, 200 Displayed, 200 Max.

File Logging: Level debug. File Messages: 241 Logged, 2318 Dropped.

4 messages were not logged

Application filtering control

Application                 Event                       Status

--------------------        --------------------        ---------

AAA                         Login                       Enabled

File system                 Copy                        Enabled

File system                 Delete-Rename               Enabled

Management ACL              Deny                        Enabled

Aggregation: Enabled

Aggregation aging time: 300 Sec

04-Dec-2012 13:10:24 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 13:08:03 :%AAA-I-CONNECT: User CLI session for user cisco over console , source 0.0.0.0 destination  0.0.0.0 ACCEPTED

04-Dec-2012 13:07:56 :%AAA-W-REJECT: New console connection, source 0.0.0.0 destination 0.0.0.0  REJECTED

04-Dec-2012 13:05:24 :%CDP-W-DUPLEX_MISMATCH: Duplex mismatch detected on interface fa24.

04-Dec-2012 13:04:37 :%STP-W-PORTSTATUS: fa38: STP status Forwarding

04-Dec-2012 13:04:33 :%LINK-I-Up:  fa38

04-Dec-2012 13:04:24 :%LINK-W-Down:  fa38

04-Dec-2012 13:04:21 :%STP-W-PORTSTATUS: fa32: STP status Forwarding

04-Dec-2012 13:04:20 :%STP-W-PORTSTATUS: fa41: STP status Forwarding

04-Dec-2012 13:04:19 :%STP-W-PORTSTATUS: fa5: STP status Forwarding

04-Dec-2012 13:04:17 :%LINK-I-Up:  fa32

04-Dec-2012 13:04:16 :%STP-W-PORTSTATUS: fa8: STP status Forwarding

04-Dec-2012 13:04:16 :%LINK-I-Up:  fa41

04-Dec-2012 13:04:15 :%STP-W-PORTSTATUS: fa2: STP status Forwarding

04-Dec-2012 13:04:15 :%LINK-I-Up:  fa5

04-Dec-2012 13:04:15 :%STP-W-PORTSTATUS: fa42: STP status Forwarding

04-Dec-2012 13:04:14 :%STP-W-PORTSTATUS: fa22: STP status Forwarding

04-Dec-2012 13:04:12 :%LINK-I-Up:  fa8

04-Dec-2012 13:04:11 :%LINK-I-Up:  fa2

04-Dec-2012 13:04:10 :%LINK-I-Up:  fa42

04-Dec-2012 13:04:10 :%LINK-I-Up:  fa22

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa32

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa5

04-Dec-2012 13:04:07 :%LINK-W-Down:  fa41

04-Dec-2012 13:04:06 :%STP-W-PORTSTATUS: fa7: STP status Forwarding

04-Dec-2012 13:04:03 :%LINK-W-Down:  fa8

04-Dec-2012 13:04:03 :%LINK-W-Down:  fa2

04-Dec-2012 13:04:02 :%LINK-W-Down:  fa42

04-Dec-2012 13:04:01 :%LINK-I-Up:  fa7

04-Dec-2012 13:04:01 :%LINK-W-Down:  fa22

04-Dec-2012 13:04:01 :%STP-W-PORTSTATUS: fa26: STP status Forwarding

04-Dec-2012 13:03:58 :%STP-W-PORTSTATUS: fa37: STP status Forwarding

04-Dec-2012 13:03:58 :%STP-W-PORTSTATUS: fa39: STP status Forwarding

04-Dec-2012 13:03:57 :%LINK-I-Up:  fa26

switch3bb80b#

Let me know if you need more data from the files.

Unless I missed it, I don't see fa24 going up or down but there is a duplex mismatch. Was port 24 a phone connection you changed the negotiation?

What ports did you change the negotiation on?

-Tom
Please rate helpful posts

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

I believe 24 is actually a small 4 port netgear switch plugged into a copier and an analog fax line converter ATA 186

I used port # 1 for 100 and port # 2 for 10. I am waiting another 15-20 minutes to see if they reboot.

David

David, any luck with reboots?

-Tom
Please rate helpful posts

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

Sorry, was in a meeting.

Port 1 did not go down, port 2 did.

I have switched port 2 to 100f as well to confirm.

Port 2 went down

After further investigation, I noticed that some ports are drawing 2700-3000 mw and some are drawing 5300-5500mw. I suppose some of the phones might be different models (like the receptionist).

Port 1 is drawing: 2700mw

Port 2 is drawing: 5300mw

I went back through the log to see if Port 1 had actually ever went down but the log was truncated so I am unable to confirm.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Switch products supported in this community
Cisco Business Product Family
  • CBS110
  • CBS220
  • CBS250
  • CBS350
Cisco Switching Product Family
  • 110
  • 200
  • 220
  • 250
  • 300
  • 350
  • 350X
  • 550X