Problem with Cisco C3550 Switch (Inline Power)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2011 04:08 AM - edited 03-07-2019 12:48 AM
Hi Everyone,
I have got an interesting problem with some Samsung POE IP Phones (ITP-5114D). If I plug one of them into the C3550 switch, the port comes up for about 2/3 seconds and then goes down, and the switch does this until I either shutdown the port or un-plug it. On the interface I have manually set the speed to be 100 and Duplex to be full (as stated for the IP Phone) and I still get the same results. I even took this a stage further and tried it with different speed settings and duplex, with no luck.
The kicker is, if I plug the Samsung POE IP Phones into a standard Netgear POE switch it works fine.
Any ideas??
Thanks
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2011 07:09 AM
Hi Kevin,
'show log' should give some relevant information, no?
Cheers,
Rajiv
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2011 08:21 AM
I'm off site at the moment but will post log information tomorrow morning. Thanks for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2011 07:11 AM
debug ilpower port
debug ilpower powerman
debug ilpower event
may also help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2011 08:21 AM
I am currently off site at the moment but will post the debug information tomorrow morning. Thank you for the suggestion.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2011 12:16 AM
Hi,
Ok, I have pasted the debug information below:
EXHXSW2#
Jun 15 08:06:57.366: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:06:57.366: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:06:57.366: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:06:57.366: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:00.174: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
EXHXSW2#
Jun 15 08:07:02.174: %LINK-3-UPDOWN: Interface FastEthernet0/13, changed state to up
EXHXSW2#
Jun 15 08:07:02.218: ILP uses Link Disconnect(Fa0/13): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
Jun 15 08:07:02.218: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:02.218: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:04.218: %LINK-3-UPDOWN: Interface FastEthernet0/13, changed state to down
EXHXSW2#
Jun 15 08:07:05.690: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:07:05.690: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:07:05.690: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:07:05.690: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:08.458: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
EXHXSW2#
Jun 15 08:07:10.458: %LINK-3-UPDOWN: Interface FastEthernet0/13, changed state to up
EXHXSW2#
Jun 15 08:07:10.538: ILP uses Link Disconnect(Fa0/13): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
Jun 15 08:07:10.538: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:10.538: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:12.538: %LINK-3-UPDOWN: Interface FastEthernet0/13, changed state to down
EXHXSW2#
Jun 15 08:07:14.014: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:07:14.014: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:07:14.014: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:07:14.014: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:16.822: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
EXHXSW2#
Jun 15 08:07:18.822: ILP uses Link Disconnect(Fa0/13): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
Jun 15 08:07:18.822: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:18.822: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:22.338: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:07:22.338: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:07:22.338: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:07:22.338: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:25.146: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
EXHXSW2#
Jun 15 08:07:27.146: ILP uses Link Disconnect(Fa0/13): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
Jun 15 08:07:27.146: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:27.146: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:30.662: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:07:30.662: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:07:30.662: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:07:30.662: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:33.470: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= PHY_LINK_UP_EV
EXHXSW2#
Jun 15 08:07:35.470: ILP uses Link Disconnect(Fa0/13): state= ILP_LINK_UP_S, event= PHY_LINK_DOWN_EV
Jun 15 08:07:35.470: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:35.470: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:38.986: ILP uses Link Disconnect(Fa0/13): state= ILP_DETECTING_S, event= TWTI_PWR_GOOD_EV
Jun 15 08:07:38.986: Ilpower PD device 2 class 9 from interface (Fa0/13)
Jun 15 08:07:38.986: ilpower new power from pd discovery Fa0/13, power_status ok
Jun 15 08:07:38.986: Ilpower interface (Fa0/13) power status change, allocated power 15400
EXHXSW2#
Jun 15 08:07:43.986: ILP uses Link Disconnect(Fa0/13): state= ILP_PWR_GOOD_USE_LINK_DISC_S, event= BAD_LINK_TIMER_EV
Jun 15 08:07:43.986: ilpower delete power from pd linkdown Fa0/13
Jun 15 08:07:43.986: Ilpower interface (Fa0/13), delete allocated power 15400
EXHXSW2#
Jun 15 08:07:43.986: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Fa0/13: Power given, but link is not up
I also managed to do a show power inline:
Fa0/13 auto on 15.4 Ieee PD 15.4
Fa0/14 auto off 0.0 n/a n/a 15.4
Fa0/15 auto off 0.0 n/a n/a 15.4
Fa0/16 auto off 0.0 n/a n/a 15.4
Fa0/17 auto off 0.0 n/a n/a 15.4
Fa0/18 auto off 0.0 n/a n/a 15.4
Fa0/19 auto off 0.0 n/a n/a 15.4
Show ver information below:
Cisco IOS Software, C3550 Software (C3550-IPSERVICESK9-M), Version 12.2(44)SE6, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Mon 09-Mar-09 20:28 by gereddy
Image text-base: 0x00003000, data-base: 0x012A99FCROM: Bootstrap program is C3550 boot loader
EXHXSW2 uptime is 23 hours, 10 minutes
System returned to ROM by power-on
System restarted at 09:03:39 GMT Tue Jun 14 2011
System image file is "flash:c3550-ipservicesk9-mz.122-44.SE6/c3550-ipservicesk9-mz.122-44.SE6.bin"Cisco WS-C3550-24-PWR (PowerPC) processor (revision D0) with 65526K/8192K bytes of memory.
Processor board ID CAT0739X0Y8
Last reset from warm-reset
Running Layer2/3 Switching ImageEthernet-controller 1 has 12 Fast Ethernet/IEEE 802.3 interfaces
Ethernet-controller 2 has 12 Fast Ethernet/IEEE 802.3 interfaces
Ethernet-controller 3 has 1 Gigabit Ethernet/IEEE 802.3 interface
Ethernet-controller 4 has 1 Gigabit Ethernet/IEEE 802.3 interface
24 FastEthernet interfaces
2 Gigabit Ethernet interfacesThe password-recovery mechanism is enabled.
384K bytes of flash-simulated NVRAM.
Base ethernet MAC Address: 00:0D:BC:E4:C8:80
Motherboard assembly number: 73-8100-07
Power supply part number: 341-0029-02
Motherboard serial number: CAT07370AD9
Power supply serial number: DTH07351W4R
Model revision number: D0
Motherboard revision number: A0
Model number: WS-C3550-24PWR-SMIConfiguration register is 0x10F
Any help would be much appreicated.
Thankyou
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2011 01:41 AM
Just for some further information. I have managed to get the POE Status from the current 3COM switch which they are plugged into.
Unit: 1
Compatible mode : Enabled
Interface Admin Oper Power(mWatt) Power(used) Priority High Power
---------- ------- ---- ------------ ------------ --------- ----------
Eth 1/ 1 enable off 30000 0 Auto disable
Eth 1/ 2 enable off 30000 0 Auto disable
Eth 1/ 3 enable on 30000 3300 Auto disable
Eth 1/ 4 enable on 30000 3100 Auto disable
Eth 1/ 5 enable on 30000 3400 Auto disable
Eth 1/ 6 enable on 30000 3100 Auto disable
Eth 1/ 7 enable on 30000 4800 Auto disable
Eth 1/ 8 enable on 30000 3200 Auto disable
Port State Mode Power Max (watts) Power Used (watts) Voltage (v) Current (mA)
6 Enabled Auto 30.0 3.1 50 62
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2011 04:49 AM
Interesting issue you have.
Changing speed/duplex settings will have little influence here but what you can try is to turn CDP off on the interface.
Looking at the above, I think this may not be the solution though.
The 3550 is one of the older devices which was initially providing pre-standard power and I'm unsure whether an IOS upgrade will make it 100% 802.3af compliant. This kind of issue seems the most likely culprit. We have solved similar issues by using a PD-PS401/Cisco balun.
If you have one of those lying around I would certainly try to connect it between the switch and the phone.
Otherwise, use Google to find one.
Finally, the link below provides intersting info on PoE 802.3af and pre-standard:
http://www.cisco.com/en/US/products/hw/phones/ps379/products_qanda_item09186a00808996f3.shtml#qa2
Hope this helps.
regards,
Leo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2011 06:09 AM
As far as I am aware the switch is running the latest version of the IOS. If someone could confirm that it would be great.
I will see if I can find these in the UK although it might start to get a little costly as we will have 20 of these shortly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2011 06:44 AM
Yes, this is indeed the latest (i.e.the last) IOS version for the 3550.
Thnx for the points.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2011 02:38 AM
As all member of the 3550 family is already EndofLife since approx 2-3 months, I didnt care and made a test.
12.2(55)SE3 was the last IOS released for "3550 24 DC" model in May 2011, all other members of the 3550 family is officially stuck at the prehistoric 12.2(44)SE6. Theoritically, all 3550's share very similar hardware, so I gave it a shot: install 12.2(55)SE3 on my 3550 24 PWR (PoE version).
It turned out, my 3550 24 PWR SMI can boot the new 12.2(55)SE3 successfully, BUT there is at least 1 caveat:
as my model name suggests, mine is a PoE model, the supported (now even already deprecated) 3550 24 DC is not PoE capable!
As a result, the “power inline ….” commands have problems: they are basically working, both the config commands and the show power.. commands, but they never become part of the running-config. As an indirect result, not become part of the startup-config either.
As a workaround, I exported the startup-config via TFTP to my PC, edited the power commands into the startup-config, imported back the edited file, and restarted the device. It successfully recognized my “hacked” values. But! (yeah, always these Butts) If you make any Write memory command in the future, it will screw up your hack, and you will lose your manually edited “power” commands. As a result, you have to repeat this painful process.
Bottom line: to give some answers to the original subjecto of this topic:
3550 has never and (obviously as it is EOL since ages) will never support 802.3af, it supports only "inline power" which is different from 802.3af
did you try the universal magic command: "power inline delay shutdown 20 initial 300" on the interface which connects to the PoE IP phone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2013 11:54 PM
Dear Kevin,
Have you resolved this issue? What is the solutions for this issue? Even me too having the same problem.. plz post if you have the solutions for this case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2013 11:57 PM
Have you resolved this issue? What is the solutions for this issue? Even me too having the same problem.. plz post if you have the solutions for this case.
Create a different thread (Hey, it's FREE!). Your situation is different.
Include relevant information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2013 07:56 PM
Dear Leo,
I've posted but didn't get solutions so far. that's why asked. Even, for me also the Non-Cisco POE device keep on flapping on 3560X. Need to fix this issue as early as possible. plz help :-(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-14-2013 08:02 PM
I've posted but didn't get solutions so far. that's why asked.
muru amir wrote:
Dear Leo,
I've posted but didn't get solutions so far. that's why asked. Even, for me also the Non-Cisco POE device keep on flapping on 3560X. Need to fix this issue as early as possible. plz help :-(
This is an old post. An old post that's very much differnet to your scenario and situation. I've responded to your post and I am awaiting for your response.
To minimize confusion, I'm going to stop responding to your post in this thread.
