03-02-2016 08:33 AM - edited 03-08-2019 04:47 AM
Hi All,
I'm not new to Cisco and but I've got this shiny new 4506 chassis with a Supervisor 8E and single (for now) 48port UPoE line card.
The config I have set up seems to be working, but some of the items we plug in for PoE don't seem to come up.
(They're all Creston PoE powered devices like touch panels and gateways.)
They've been running great on a 2960-S PoE switch and are being moved to this.
They are statically assigned IP addresses.
When plugged into the 4506 setup, they get power but can't contact the master Creston controller. (no traffic)
Here's what I see:
sh mac address-table shows me the MAC of the device on the port its plugged into.
sh ip arp doesn't show the IP address of the device.
sh power inline shows the power being supplied by the device. (and the panel powers up)
I can't ping the device at it's configured address from anywhere (even a login to the switch)
So here's what I've done:
added spanning-tree portfast to all the line ports since they all terminate to devices directly. (no loop potential)
toggled power to port using "shutdown/no shutdown" commands.
rechecked things like the MAC address table and ping. Same results.
If I reboot the switch, the device is now up on the network and works fine.
I don't see any "MS Windows Ver. XXX" in the software (lol) -- so I'm at a loss as to what I'm missing from this config and why it needs a reboot to bring a device online.
Any thoughts?
Thanks,
-Ben
03-02-2016 10:56 AM
Hi Ben,
I am not sure what is the issue but you should not need to reboot the device to bring up the module.
I have many 48 port UPoE modules connecting to Crestron switches and other end devices and they all work fine. Maybe you have a bad module or an IOS bug.
HTH
03-02-2016 12:00 PM
Thanks for the extra info. I wouldn't think these things should be having issues either.
Bad line card? Yeesh, I hope not.
This unit is < 90days old. We've had it powered up - but just started moving things over to it.
For anyone else reading: Here's the current unit information from sh version
c4500>sh ver
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500es8-UNIVERSAL-M), Version 03.03.00.XO RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Wed 14-Aug-13 09:51 by prod_rel_team
Cisco IOS-XE software, Copyright (c) 2005-2013 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: 15.1(1r)SG5
c4500 uptime is 5 hours, 29 minutes
System returned to ROM by reload
System restarted at 14:28:23 UTC Wed Mar 2 2016
Running default software
Jawa Revision 3, RadTrooper Revision 0x0.0x41, Conan Revision 0x1449
Last reload reason: Reload command
License Information for 'WS-X45-SUP8-E'
License Level: lanbase Type: Default. No valid license found.
Next reboot license Level: lanbase
cisco WS-C4506-E (P5040) processor (revision 2) with 4194304K bytes of physical memory.
Processor board ID FXS1926Q2N3
P5040 CPU at 2.2GHz, Supervisor 8-E
Last reset from Reload
1 Virtual Ethernet interface
48 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.
Configuration register is 0x2101
c4500>
03-02-2016 12:19 PM
Not that this is related to the POE/module issue, but your configuration register should be 0x2102 not 2101. You need to reboot after making the change and saving the config.
Configuration register is 0x2102
HTH
03-02-2016 02:49 PM
As it turns out -- that version firmware is from 2013.
There's an update from last Nov. (2015) of 03.06.04 -- which I've installed to the system....
And now the config register is 0x2101
so -- hopefully all will be well now.
Thanks for the sanity check.
(I've been using Cisco on and off for clients since like 1995 -- boy I've see some weird things. Rebooting to allow a newly attached device to work is definitely up there on the list.)
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