Wake on LAN configuration on 4507R switch

Trying to configure Wake on LAN on a 4507R switch. I thought I would just get it working with devices directly attached to this switch before trying to expand the configuration to the rest of the network.
Followed this document:
http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a008084b55c.shtml
Between this and other web articles I’ve read, it seems fairly simple to configure. However, I haven’t gotten it to work yet. I can’t identify the correct udp socket(s) to try, even when using the same Solarwinds Wake On LAN software mentioned in the article. Am also using Wyse Device Manager to attempt to wake thin clients.
I’ve tried to use debug ip udp, but never see any entries listed for the transmission(s) by the host machine to the intended subnets(s).
Also tried using Wireshark, but I still don’t see the host transmissions from any device that I’ve tried sending the WOL packets from.
Does anyone know the socket(s) used by either of those two pieces of software for WOL packets?
TIA
Rick

Hi DMatt7176,
I would provide a reference for you:
Wake-on-Lan (WOL) for Windows 7 Made Easy!
http://windows7-issues.blogspot.com/2011/03/wake-on-lan-wol-for-windows-7-made-easy.html
Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Regards,
Alex Zhao
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

MSI G70 Dragon Edition 2 and wake on lan

Hi everybody.
Does G70 laptop support wake on lan feature ?
Or how i can get wake on lan feature for this laptop.

Here I reply to myself : I think this will be useful to other people, whatever the motherboard model.
So, I just SUCCESSFULLY have been able to wake up my PC from the LAN
Here are my conclusions :
1- There's nothing in the motherboard documentation that explicitly indicates that it's supported. But it is !
2 - I didn't need to connect the LAN card to the motherboard (didn't need any WOL connection)
3 - I have a patched Windows XP. But its standard drivers for my network card weren't enough. I had to install the updated drivers from the manufacturer (admtek).
4 - With these drivers, I could then access, from Windows devices setup tool, to the network adapter APM properties, and I could "Allow Device to Bring Computer Out of Standby".
5. Inside the BIOS, a few things to setup :
Power Management Features
-> IPCA Function : Enabled
-> Power Management / APM : Enabled
-> Set Wake Up Events ... Wake Up On PME# : Enabled
Actually, this means that there is no explicit need for a "Wake On LAN" configuration. It all goes through PME# (i.e. direct PCI) wakeup events.
6. Then it works :-)
The excellent free tool available at
http://www.depicus.com/wake-on-lan/
does the job at the remote computer side (when fed with the valid MAC and IP addresses).
I'm very pleased... but I wish MSI had somehow indicated that the motherboard is WOL capable !
Guillaume

MSI 645 Ultra and "Wake On LAN" ???

Hello,
This question is aimed at the following people :
- Someone who owns a MSI 645-Ultra motherboard, and who has some experience about it's "Wake On LAN" capabilities,
or,
- Someone at MSI who knows the detailed specifications of this motherboard (related to its "Wake On LAN" capabilities).
I own a "MSI 645 Ultra" motherboard for some time now (more than a year). It's based on SIS 645 chipset.
Currently, I'm trying to make the computer boot on demand, through the LAN.
So, I have an appropriate network card : its based on Admtek AN983, it supports "Wake On LAN" (WOL), and a WOL cable was included.
About the MSI 645 Ultra motherboard, I looked at the documentation, and, surprisingly, I didn't find any mention of the WOL feature.
Too sad, this "modern" motherboard doesn't support WOL feature ??
The doc says there is support for WOR (Wake on modem Ring), and there is a WOR connector. But no WOL connector.
So, what's the status of this motherboard, regarding WOL support ??
- Is it internally supported, without the need of a WOL connection, directly through PCI and PME signaling ?
- Can I use the motherboard WOR input connector, and plug the network card's WOL into it ?
- Is all of this non sense ??
Thanks in advance for your clarifications and tips.
Technical replies are welcome (I have a solid networking background)
Guillaume

Here I reply to myself : I think this will be useful to other people, whatever the motherboard model.
So, I just SUCCESSFULLY have been able to wake up my PC from the LAN
Here are my conclusions :
1- There's nothing in the motherboard documentation that explicitly indicates that it's supported. But it is !
2 - I didn't need to connect the LAN card to the motherboard (didn't need any WOL connection)
3 - I have a patched Windows XP. But its standard drivers for my network card weren't enough. I had to install the updated drivers from the manufacturer (admtek).
4 - With these drivers, I could then access, from Windows devices setup tool, to the network adapter APM properties, and I could "Allow Device to Bring Computer Out of Standby".
5. Inside the BIOS, a few things to setup :
Power Management Features
-> IPCA Function : Enabled
-> Power Management / APM : Enabled
-> Set Wake Up Events ... Wake Up On PME# : Enabled
Actually, this means that there is no explicit need for a "Wake On LAN" configuration. It all goes through PME# (i.e. direct PCI) wakeup events.
6. Then it works :-)
The excellent free tool available at
http://www.depicus.com/wake-on-lan/
does the job at the remote computer side (when fed with the valid MAC and IP addresses).
I'm very pleased... but I wish MSI had somehow indicated that the motherboard is WOL capable !
Guillaume

SG200 how to configure Wake on LAN across subnets

How can I configure to support WOL on a SG200 (8 Ports) to support Wake On Lan (Magic Packets) from a different IP Subnet or other SG200 Switch. It seems not to support Directed-Broadcasts.

I checked out the link and tested the changes. Unfortunately, the WOL still won't work. In the link you attached, it states that you cannot turn on a computer that is off. Does that mean one that is off such as unplugged or in shutdown? Also, one of the steps to configure the firewall access rules says to block all outbound connections for all services. That doesn't make any sense to me, but I might be wrong. I also noticed that the link was for another router. I don't know if that makes a difference. I also read somewhere in the forums that someone else is having a similar problem, saying that Port Forwarding still isn't working in the latest firmware. This whole problem is strange because it used to work all the time on my old router with Port Forwarding, but on this one it won't work at all.
Sent from Cisco Technical Support iPad App

How to configure Wake On LAN to work through the Internet?

I'm using an iOS app to wake my desktop computer. It works perfectly fine when I'm within my WiFi range. However, when I'm out of my Linksys E3000 access point, it no longer works over the Internet. So, if anyone can point me to documentation that have step by step instruction on how to configure this through the Linksys E3000 access point, I'll be grateful.

Hi ohgosh,
I believe your computer is already configured and has all the requirements for Wake on Lan since it works locally. To do it remotely you need to open the regular port numbers used for WOL like UDP ports 9 and 32767. Your desktop IP address must be set to static because that's what you need to enter on the port forwarding page of your router. You may use this link below for instructions on how to do port forwarding on your router.
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=d9b27a0c1bb9496d8c22d0d55f875ddf_17241.xml&pid=80&...
Another option is to set up DynDNS on your router. With this, you need to subscribe to DynDNS.com. I found some online links that could help you enable WOL remotely:
http://kb.linksys.com/Linksys/ukp.aspx?vw=1&docid=3ff9013e9f4f4a0b9d9805b0697407b7_4578.xml&pid=80&r...
http://lifehacker.com/5786791/rule-your-computer-from-afar-by-setting-up-wake+on+lan
http://www.dslreports.com/faq/9389
http://www.teamviewer.com/en/res/pdf/TeamViewer-Manual-Wake-on-LAN-en.pdf
Hope this helps!

Dot1x + wake on lan

hi,
i found some datasheet about dot1x and WOL, but no ones gave me satisfaction this day.
I try to have the WOL with dot1x, but is it possible ?
i have switch 2960X (SW version :15.0(2)EX4) )
the initial port's configuration below (for dot1x of course) :
authentication port-control auto
authentication violation protect
dot1x pae authenticator
with the value "authentication port-control auto" the magic packet cannot access to the computer. When i remove the value, the compoter boot correctly but, i dont have any authentication, the port keeps the old authentication and i dont see my computer on the ACS when he reboots. (i see the computer for each reboots on ACS).
but, i can log on the network domain, i have an IP, but i dont know if the computer is legit or not
i want to see the computer's registration with "sh authenti session int xxxx"
without the value "port control auto" i just see :
MAC Address: Unknown
IP Address: Unknown
Status: Authz Success
and with the value :
MAC Address: b4b5.2fae.xxxx
IP Address: 10.45.66.54
User-Name: ps01826
so, how do I do ? is it possible or not ?
thank for the reply

i found the answer this morning :
"IEEE 802.1X Authentication with Wake on LAN
The IEEE 802.1X authentication with wake on LAN (WoL) feature allows dormant PCs to be powered when the switch receives a specific Ethernet frame, known as the “magic packet.” You can use this feature in environments where administrators need to connect to systems that have been powered off.
When a host that uses WoL is attached through an 802.1X port and the host powers off, the 802.1X port becomes unauthorized. The port can only receive and send EAPOL packets, and WoL magic packets cannot reach the host. When the PC is powered off, it is not authorized, and the switch port is not opened.
When the switch uses 802.1X authentication with WoL, the switch forwards traffic to unauthorized 802.1x ports, including magic packets. While the port is unauthorized, the switch continues to block ingress traffic other than EAPOL packets. The host can receive packets but cannot send packets to other devices in the network."
describes exactly the problem i have, and i cant fix it because if i remove the "authentication port-control auto" the computer does not authenticate anymore :/

Nexus 7K Wake on Lan

I am running 6.2(2) on 7K. My woke on lan server is svi901 and physically on the 5K down stream. I am trying to setup wake on lan to sent direct broadcast from 7K out to the clients remote subnets. From other router WoL example it requires ip forward-protocol udp 7 in global config. I don't see that command availabe in 7K. Is this command available or is there other way to config WoL on 7K?
Thanks

Here is a good doc on WOL:
http://www.cisco.com/en/US/partner/products/hw/switches/ps5023/products_configuration_example09186a008084b55c.shtml
https://www.ciscotaccc.com/kaidara-advisor/lanswitching/showcase?case=K74260926
Remember to configure ip forward-protocol udp 7 and ip directed-broadcast on the last hop router (nexus in this case).
WOL does not require directed-broadcasts unless you've got a host on a different subnet attempting to do it. if that is the case then you need to allow directed-broadcasts.
I have seen issues on access ports if ports were not set to auto auto.
Nothing special about the Nexus I am aware of.
In regards to possible conflict with the DHCP, make sure WOL is not using UDP/67 or you might run into some issues with DHCP snoop. I see the hosts using WOL and DHCP are on the same subnet but are the WOL and DHCP servers on the same subnet?
Fabienne.

WRT160N wake-on-lan

Hi all,
I'm having real problems getting wake-on-lan to work with my WRT160N. My NIC (a realtek 8110) certainly supports the WOL function and I'm pretty sure I have Vista set up correctly but I think I need to set the router to forward UDP packets on port 9 to the LAN broadcast address - 192.168.1.255 - but the router firmware won't allow values higher than .254!
Does anyone know of a way around this?
Many thanks,
Dan

I'm experiencing this exact issue with a WRT160Nv2. I was able to get WOL from the Internet working by creating a DHCP reservation and forwarding the port, but it only works for about 15 minutes after the PC goes to sleep. It works from the LAN reliably at any time. I upgraded to the latest firmware, which made me very nervous since I had previously been through the build 11 DNS drop fiasco and had to RMA the first one of these I had, but that's another story. No change there. I previously had the PC configured with a static IP, but I switched it to automatic so that it actually gets the reserved address from the DHCP. This made it actually appear in the DHCP clients table, which gave me a little hope, but it didn't change the behavior either. The router still seems to drop it from the ARP cache, even though it's been told to permanently associate the given IP and MAC address. I tried putting the PC in the DMZ, which I really don't want to do anyway, and that didn't change anything. I'm guessing this is just the latest in the long list of problems with this router that Linksys can't replicate and isn't especially bothered about. I'm definitely going to make sure I get a router that's supported by alternative firmware the next time. Anyone have any other ideas about this other than replacing the router?

Wake on LAN - ip directed broadcast

We're looking at deploying a Wake-on-LAN solution for software distribution. The first alternative to distribute the 'magic packet' is enabling 'ip directed-broadcast' in each router, which presents a security risk (man in the middle attack, ARP table poisoning), the second alternative is to extend ARP aging time in the routers which presents the same security risk.
My question is, how can be this security risk reduced or minimized (options I've heard of: 'dynamic ARP inspection' in the switches, ACL on the router associated with the ip directed-broadcast command allowing only software distribution servers to convert directed-broadcast packets into unicast packets). I have a concern extending ARP aging time and its impact with current or future application.
I'll appreciated any comment. Thanks.

IP directed broadcasts are used in the popular "smurf" denial-of-service attack and derivatives thereof. An IP directed broadcast is a datagram that is sent to the broadcast address of a subnet to which the sending machine is not directly attached. The directed broadcast is routed through the network as a unicast packet until it arrives at the target subnet, where it is converted into a link-layer broadcast. Because of the nature of the IP addressing architecture, only the last router in the chain, the one that is connected directly to the target subnet, can conclusively identify a directed broadcast. Directed broadcasts are occasionally used for legitimate purposes, but such use is not common outside the financial services industry. In a "smurf" attack, the attacker sends Internet Control Message Protocol (ICMP) echo requests from a falsified source address to a directed broadcast address, causing all the hosts on the target subnet to send replies to the falsified source. By sending a continuous stream of such requests, the attacker can create a much larger stream of replies, which can completely inundate the host whose
address is being falsified. If a Cisco interface is configured with the no ip directed-broadcast command, directed broadcasts
that would otherwise expand into link-layer broadcasts at that interface are dropped instead.
If you are behind a firewall and are confident in your security policy, then I don't see this as being a problem.

Wake on Lan works on my MacBook Pro, not on my iMac...

Hello everyone, with all these threads about the problem, I wanted to start a new one to make it clear, with all information you may need in order to help me out.
I've got a MacBook Pro '15 and an iMac 21.5', both are running (clean install) OS X Mountain Lion 10.8.2, both are up to date with the latest updates, both have the same apps, both have the same settings in "system preferences", and of course the same settings in "sharing" options.
My iMac is connected to my 5GHz network from my Time Capsule while my MacBook Pro use the 2.4GHz network.
Before going to bed, I leave both my Macs turned on, after 10min they go to sleep automatically. In the morning I can wake up my MacBook Pro from my iPhone or iPad with a screen sharing app.
The iMac doesn't respond at all. It stays in sleep mode. I can leave my MacBook Pro asleep for a week, it always responds. The iMac responds after a few hours but after 6 or 8 hours it seems to be completely asleep and doesn't respond to anything. If you think it's about the iPhone/iPad's app, when I try to wake the iMac from my MacBook Pro with "Back to my Mac" I have the same results.
I tried to connect my iMac to the 2.4GHz network: same problem.
OF COURSE "WAKE ON LAN" is activated in my system preferences.
I made a reset of the PRAM, the cache and the SMC on my iMac: same problem.
I type sudo periodic daily weekly monthly in the terminal and sudo dscacheutil -flushcache: same problem.
I tried everything I may have found in the forums or on this Support from people having the same issue: same problem.
I even tried to set the iMac with the same sleep mode as my MacBook Pro: same problem.
PLEASE HELP ME!

loïcfernandezcastrillon wrote:
I'm connected with the WiFi of my Time Capsule (bridge mode). I have this configuration since Snow Leopard, and no troubles...
I understand that, but if your router is not an Apple AirPort Base Station then it introduces an element of uncertainty. Apple has implemented many changes related to wireless networking recently.
You are complicating matters by changing networkoversleep:
networkoversleep - this setting affects how OS X networking presents shared network services during system sleep. This setting is not used by all platforms; changing its value is unsupported.
Solving problems like this requires that you simplify your network environment and eliminate its unknowns. Using third party routers and making unsupported changes runs counter to simplification.
The iMac stays connected to the Time Capsule about 6 hours during sleep. Then it dissapears...
The iMac wakes periodically (every few hours) to inform your router of its network presence for Wake on LAN demands. Try changing your router's DHCP lease period to something longer than a few hours. For a home environment, a few days is more appropriate. This may not solve the problem, but it is better than making unsupported changes to your system.

T500 Wake on Lan (wireless) does not work.

Hi,
I set up T500 (Windows 7 Ultimate 64bit) for wake on lan,
1) Enable Bios WOL
2) Enable WOL in power manegement tab of Intel WiFi Link 5300 AGN property in device manager.
But WOL does not work. Sending magic packet from a PC in the same WiFi segment does not wake up sleeped T500.
Are there any setting for WOL in lenovo tools ?
Does anybody use WOL(WiFI) on T500?
Thanks,

Is the T500:
Associated with an access point at the time it is put into standby/sleep mode?
Connected to AC power for the whole time it is in standby/sleep mode (in otherwords the whole time it is in a low power state) when you are attempting to use WoWLAN?
If not, that may be at least part of your problem, as it is a known limitation on WoWLAN operation.
You also need to have the laptop "set up" to the master workstation, and the WLAN configured to handle braodcast wireless frame, but I am presuming you have already done that side of things.
Cheers,
Bill
I don't work for Lenovo

Wake on LAN across subnets

Is there a way to get Zenwork's wake-on-lan feature to work across subnets?
I am not a LAN administrator so pardon any ignorance you see in my
question.
Zenwork's wake-on-lan function won't work on our LAN because our switches
are set to not allow forwarding of subnet-oriented broadcasts, which is a
generic requirment for zenworks wake-on-lan function to work. Our security
folks say enabling this on the switches is not an option because it
introduce a security vulnerbility. I find it strange that there wouldn't
be a solution for this by Novell/Zenworks considering that multiple
subnets, switches, and security considerations are usually a component of
all networks which zenworks is specifically targeted for in the first
place.
Thanks

Originally Posted by Marcus Breiden
On Thu, 07 Sep 2006 22:52:59 GMT, [email protected] wrote:
[color=blue]
it is the only way though.. that's how any WOL software works.. they can
limit the packets comming from either your c1 wks or the zenworks server
though.. otherwise you would require one server per subnet
Marcus Breiden
If you are asked to email me information please change -- to - in my e-mail
address.
The content of this mail is my private and personal opinion.
Edu-Magic.net, deceased
Exactly, and this is the best choice. Make "Replication Servers" in each subnet, is very simple. U can use a Windows machine or SuSE, both without installing zenworks. Only registering them as servers satellites. You must install the agent (logically, hehe).

Wake on lan - I can't get it to work

Sorry for the nubie here.
I am unable to wake my new iMac from my Macbook using WakeOnLand. The MB is using wifi and the others are using ethernet.
Also, I am unable to see a G4 running 10.4.11.
The MB and iMac are running 10.6.2. No firewalls.
I have a Dlink router and know how to get into its admin page but really am afraid to change its configurations due to lack of knowledge.
Any help appreciated.
Lewis

no. wake on lan works over ethernet only. it does not matter what router you use. but SNow leopard has a new feature "wake on demand" that does work over wireless. but for that you need a very recent apple router (TC or AEBS) and and a very recent computer.
http://support.apple.com/kb/HT3774

Erasing a config and vlan.dat file in Catalyst 4507R Switch

Hi,
I am unable to erase the configuration from Catalyst 4507R Switch.When i do "write erase" and reload the switch,the configuration still remains on the switch.
Switch1#write erase
Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]
[OK]
Erase of nvram: complete
mp024-dc-nr00#sh start
startup-config is not present
After this i did reload and configuration still didn't get removed.
I tried
erase /all nvram:
reload
This also didn't help.
I also tried:
erase /all non-default
reload
This also didn't help.
Can anyone suggest how to erase the config on Catalyst 4507R Switch.
Thanks,

Hi Saroj,
do you see the below symtoms:
Cat4500# write erase
Erasing the nvram filesystem will remove all files! Continue? [confirm]y[OK]
Erase of nvram: complete
Cat4500# reload
System configuration has been modified. Save? [yes/no]: n
!--- Do not save the configuration at this prompt. Otherwise, the switch
!--- reloads with the current running configuration and does not reset to default.
Proceed with reload? [confirm]y
2w0d: %SYS-5-RELOAD: Reload requested
To erase the vlan.dat file on the 6500/6000 switches, issue the erase const_nvram: command. On the 4500/4000 switches, issue the erase cat4000_flash: command. On the fixed configuration switches, issue the delete flash:vlan.dat command.
HTH
Regards
Inayath

Wake-on-LAN Breaks After Several Reboots, 3.18 Kernel

Greetings all,
I'm leaving town for a month and I dont' want keep my machine turned on so I set up Wake-on-LAN on my desktop machine running 3.18 kernel. Got the wol command working but the problem is that something breaks and won't work beyond a few reboots. If I phisycally power up and shutdown the machine and then try it again, it magically works again.
I set up port forwarding on my router then followed the wiki and tried every single method mentioned there, udev, cron, systemd and wol-systemd as a last resort. Strangely enough they all give me the same result, for whatever configuration, it doesn't last beyond a few reboots.
As it stands, this is my current configuration after installing the wol-systemd package from AUR:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/enable-wol %i
Type=oneshot
[Install]
WantedBy=multi-user.target
My alternative is to leave my machine running, I can ssh into it just fine. but I'm hoping someone can shed some light. Feel free to ask any questions. Thanks!
***EDIT***
No takers yet? Super quiet around the forums lately,
I'm no networking guru, but I read up on some additional material regarding this subject. Apparently my problem is related to my router's ARP cache releasing the IP address after an initial period. Since the cache expires the magic packets never reach the destination IP, which coincides with the problem I'm having.
An option is to use the broadcast address in place of the IP, however, that's beyond my router's capabilities, at least I think. My router is a Linksys EA6500. I've tried just about everything. I also tried messing around with AMT but that's even a bigger headache on linux. If anyone has a workaround it would surely be a great help. Thanks!
Last edited by w201 (2015-02-24 22:32:39)

Greetings all,
I'm leaving town for a month and I dont' want keep my machine turned on so I set up Wake-on-LAN on my desktop machine running 3.18 kernel. Got the wol command working but the problem is that something breaks and won't work beyond a few reboots. If I phisycally power up and shutdown the machine and then try it again, it magically works again.
I set up port forwarding on my router then followed the wiki and tried every single method mentioned there, udev, cron, systemd and wol-systemd as a last resort. Strangely enough they all give me the same result, for whatever configuration, it doesn't last beyond a few reboots.
As it stands, this is my current configuration after installing the wol-systemd package from AUR:
[Unit]
Description=Wake-on-LAN for %i
Requires=network.target
After=network.target
[Service]
ExecStart=/usr/sbin/enable-wol %i
Type=oneshot
[Install]
WantedBy=multi-user.target
My alternative is to leave my machine running, I can ssh into it just fine. but I'm hoping someone can shed some light. Feel free to ask any questions. Thanks!
***EDIT***
No takers yet? Super quiet around the forums lately,
I'm no networking guru, but I read up on some additional material regarding this subject. Apparently my problem is related to my router's ARP cache releasing the IP address after an initial period. Since the cache expires the magic packets never reach the destination IP, which coincides with the problem I'm having.
An option is to use the broadcast address in place of the IP, however, that's beyond my router's capabilities, at least I think. My router is a Linksys EA6500. I've tried just about everything. I also tried messing around with AMT but that's even a bigger headache on linux. If anyone has a workaround it would surely be a great help. Thanks!
Last edited by w201 (2015-02-24 22:32:39)

Wake on LAN configuration on 4507R switch

Similar Messages

Maybe you are looking for