- This topic is empty.
-
Posts
-
Hey all
Has anyone had the problem where all the units in their WDM inventory have decided to turn off (red device) although the units are on and i can remote shadow to them??
Thanks
DShaunJust realised, i dont think its got to do with WDM. One of our ESX servers are down. My bad 🙁
Hi! I got WDM 4.5.3 Enterprise installed at a customer and there is an issue regarding the status of the devices, it has many V90s which are working normally but in the console are shown as red, here is a detail:
1. They are on an working
2. VNC is working
3. The agent is up to date (5.0.0.7)
4. All with the same image version (503)
5. Port 80 is open on the subnet
6. ID 186 is set to DHCP
7. WDM is working correctly, timeout is set to 1minI really dont know how to fix this issue
Hi,
Any errors in the Server Event Log? You say only some devices are red not all, are they all in the same location or spread about the place?
Cheers,
-TTYes they are all in the same subnet, some of them are green when working and they are in the same conditions as the red ones so its really strange.
The customer tried to put manually the rapport ip address on some of the red ones and after went green but DHCP is set for 186 so why he need to put it manually? is the ID 186 been saved on the device?Hi,
The 186 tag does not have any effect with XPe. WDM finds devices automatically via receiving the DHCP broadcast fro the devices. Are IP helpers in place for the remote subnets? When you changed the IP in the control panel in the problem devices I assume they had the wrong IP so I guess the WDM 4.5.3 server is a new on with a different IP so this is the issue,
Cheers,
-TTYes the IP helpers are enabled, so the issue is that the device has a wrong rapport ip address inside the control panel? but this means you have to change it manually on all red devices (about 500), why is not done automatically?
Hi Edo,
If IP helpers are set correctly and the devices have PXE first in the boot order they “should” auto discover. You can easy check if the IP helpers are OK by looking at a device that works in the subnet and see if it has PXE enabled. Right click on the device and see if the option “Get Device Image (Requires PXE)” is there.
If its not there is a problem with the IP helpers, if it is there may be an issue with WDM. You can manually discover devices from WDM but create a IP range to do the discovery as I have always found discovery by subnet a bit flaky in WDM 4.5x as compared to 4.4.1. Also be aware if a device is discovered with the write filter on and it has the wrong WDM IP it will reboot so don’t do this at 11:00am in the morning on 500 devices 🙂
The 186 tag is used for CE, Linux and WTOS – shame it has not been implemented for XP/NT
Cheers,
-TT
- You must be logged in to reply to this topic.