reakhavok Posted January 12, 2015 Share Posted January 12, 2015 So our entire block suffered a power outtage a few days ago. It took about 2 hours for power to be restored and by that time I was back at work. Last night I noticed several ISY programs were not working and started investigating. I discovered my ISY was not detected on my network. So I went over to the device and unplugged power/replugged it. The blue light came on in the front and so I went back to my laptop to try and log into it. I was not able to login or ping the device. So I went back to the ISY and noticed the link light on the NIC port was not flashing and the same on the switch. I don't know what else to do.. Is it possible the outtage fried the port?? any suggestions.. Thanks all!! Gregg Link to comment
Xathros Posted January 12, 2015 Share Posted January 12, 2015 (edited) So our entire block suffered a power outtage a few days ago. It took about 2 hours for power to be restored and by that time I was back at work. Last night I noticed several ISY programs were not working and started investigating. I discovered my ISY was not detected on my network. So I went over to the device and unplugged power/replugged it. The blue light came on in the front and so I went back to my laptop to try and log into it. I was not able to login or ping the device. So I went back to the ISY and noticed the link light on the NIC port was not flashing and the same on the switch. I don't know what else to do.. Is it possible the outtage fried the port?? any suggestions.. Thanks all!! Gregg Hi Gregg- Power down the ISY again and replug the power. Watch the link/Act light on your switch to see if there is any activity during the ISY startup. If there is, it's possible you have an IP conflict with another device on your LAN. Was your ISY assigned a static address? If so, was that done by hard coding the address in the ISY or by MAC reservation in the router? -Xathros Edited January 12, 2015 by Xathros Link to comment
reakhavok Posted January 12, 2015 Author Share Posted January 12, 2015 (edited) Xathros, thanks for the reply.. So im at work and don't have it in front of me, but from memory when repluggling the ISY only the blue power light comes up. No other lights blink or make any indication that they are working. My ISY is a static IP of 192.168.1.5 and my DHCP server only assigns dynamic IP's at 192.168.1.100 and above. I have a more complex network than the average user. I use a cisco 24 port managed POE switch and have all of my static devices set in the lower ranges.. Any guests or rarely used devices get DHCP address above 100. I feel confident that I do not have an IP address conflict. Thanks,Gregg P.S the ISY is hardcoded with the IP. I did not use Mac address reservations. Edited January 12, 2015 by reakhavok Link to comment
Xathros Posted January 12, 2015 Share Posted January 12, 2015 Hi Gregg- Thats very much the same as my setup. I agree - IP conflict is unlikely here. When you get home, unplug the PLM (From the wall) and remove power from the ISY. Plug the PLM back in, wait 5 seconds then repower the ISY and watch for activity on the switch port as well as ISY blue light activity. Post results. -Xathros Link to comment
shannong Posted January 12, 2015 Share Posted January 12, 2015 (edited) There are no Ethernet link lights on either end so the problem would be unrelated to IP address, DHCP, etc without an active Layer 2 link. Since it's statically assigned to the ISY then you must not be doing DHCP snooping and Dynamic ARP Inspection which could ErrDisable the port when it sees unauthorized traffic and shut it down. Are you using port security to map MAC addresses to specific ports that could disable the port if it was lost on boot? Did you log into your switch and see if there are any log messages associated with that port? What does "show interface" indicate for that port? What happens when you plug it into a different port on the switch that is known to work? And of course, did you swap the cable? What happens when you plug a different device into the switch port in question? A power surge could've waxed the port on the ISY, the switch, or both. Edited January 12, 2015 by shannong Link to comment
Xathros Posted January 12, 2015 Share Posted January 12, 2015 There are no Ethernet link lights on either end so the problem would be unrelated to IP address, DHCP, etc without an active Layer 2 link. Since it's statically assigned to the ISY then you must not be doing DHCP snooping and Dynamic ARP Inspection which could ErrDisable the port when it sees unauthorized traffic and shut it down. Are you using port security to map MAC addresses to specific ports that could disable the port if it was lost on boot? Did you log into your switch and see if there are any log messages associated with that port? What does "show interface" indicate for that port? What happens when you plug it into a different port on the switch that is known to work? And of course, did you swap the cable? What happens when you plug a different device into the switch port in question? A power surge could've waxed the port on the ISY, the switch, or both. The ethernet port on my 994 has both Link and Act LED's As do most switches I have seen. The OP stated that there was no blinking, I took that to mean there was a Link but no activity. If neither Link LED's are lit then, I have to agree and suspect fried port(s). -Xathros Link to comment
shannong Posted January 12, 2015 Share Posted January 12, 2015 The ethernet port on my 994 has both Link and Act LED's As do most switches I have seen. The OP stated that there was no blinking, I took that to mean there was a Link but no activity. If neither Link LED's are lit then, I have to agree and suspect fried port(s). -Xathros Reading it again it's not clear. He said the "link light was not flashing" which at first I just read as "I don't have a link". The link light should be solid green, amber, or not lit based on whether the Layer 2 connection is established. The Activity light flashes with traffic but only if the Link light is lit solid. Link to comment
reakhavok Posted January 12, 2015 Author Share Posted January 12, 2015 Sorry for the confusion. I meant to say there is no light at all. I am home now have done the following. Unplugged, removed all cables from ISY, PLM plugged everything back in. The only light the ISY emits is the really bright blue power light. None of the other ligths on the front do anything, including the NIC light on the back.. Once everything was plugged back up, i tried using a different port, then a different cable, then put a known good device onto the ISY's port and that devices still works. so all indications point to either the ISY as a whole not working or possibly just the NIC. I dont remember when the ISY is powered up if the other lights on the front should come on/blink or not.. Link to comment
Teken Posted January 12, 2015 Share Posted January 12, 2015 (edited) Sorry for the confusion. I meant to say there is no light at all. I am home now have done the following. Unplugged, removed all cables from ISY, PLM plugged everything back in. The only light the ISY emits is the really bright blue power light. None of the other ligths on the front do anything, including the NIC light on the back.. Once everything was plugged back up, i tried using a different port, then a different cable, then put a known good device onto the ISY's port and that devices still works. so all indications point to either the ISY as a whole not working or possibly just the NIC. I dont remember when the ISY is powered up if the other lights on the front should come on/blink or not.. When the ISY first powers on and initiates you will indeed see a flurry of strobing of LED's which go across from left to right. If you have a cross over cable wire it to your laptop and see if you can login. If you can't even ping the device via command line the unit may be damaged. Assuming you can ping the device enter ping XXX.XXX.XXX -t <-- This will run a continuous ping until you shut down the terminal window. I do this all the time to get an idea of the network health and that of the end devices. Assuming it replies back (not dead) an increasing ping time is also indicative of a failing NIC card. Edited January 12, 2015 by Teken Link to comment
shannong Posted January 12, 2015 Share Posted January 12, 2015 (edited) If no programs are running that are based on Insteon messaging only, then the ISY isn't working at all and it's not just a network port issue. The ISY doesn't need an active Ethernet connection to run programs related to Insteon devices and events. I recommend plugging in a USB cable to it and connecting that to your laptop. That will give you direct console access like on a Cisco switch. Some versions of Windows recognize and install the driver for the USB to UART bridge connector. If not, you need to install Silicon Labs CP210x driver. The Com port number it's using can be seen in the Device Manager. Connections setting: 115200, 8,1, none. You'll also need a terminal emulator program. Ultimately you'll probably need to open a ticket with UDI. Edited January 12, 2015 by shannong Link to comment
reakhavok Posted January 13, 2015 Author Share Posted January 13, 2015 (edited) I can not ping the device, I think it may be dead. I am going to try and connect to it via USB and a term emu as shannong just recommended. Thanks all. plugged the ISY into my laptop and the driver loaded fine, launched PuTTY but it wouldnt connect. I've sent a message into UD Edited January 13, 2015 by reakhavok Link to comment
Recommended Posts