NBX 3000: Can't access WEB UI or Ping - System still up.
NBX 3000: Problem: Can't ping or access WEB UI System still operational, just cannot make any changes. Tried rebooting system - stays operational for several minutes and then becomes un-pingable and WEBUI no longer accessible.
Re: NBX 3000: Can't access WEB UI or Ping - System still...
There is most likely another device on the network with the same IP as the phone system. You can check this by un plugging the link to the phone system (after hours of course) and then pinging the IP of the phone system. If you get a reply while the link is disconnected then you know there is a duplicate IP on the network. You can use your server to try to identify the device or use a IP scanner like NetScanTools to ID it. You could also try changing the IP address of the phone system and see if you have the same problem.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
This does happen occasionally but is not a typical thing. This means that you have either lost network access to the system or a service on the system has stopped. The system will have to be rebooted to get things going normally again. The preferred method (since you can do it through netset) is to connect to the console port with a DB9 straight through serial cable and open hyperterm or putty and connect to it at 9800, 8, 1 none settings. Hit ctrl r and the system will reboot. if you don't have a serial cable then you are forced to pull the power or switch it off and then back on. CAUTION: you risk a database corruption every time the system loses power without closing the database properly (netset or ctrl r through the console) so do this as a last resort. Also, the system will do a disk scan (except V3001) and will take 15 to 45 minutes to complete before the system will start to function again. DO NOT UNPLUG IT AGAIN WHILE IT IS DOING A DISK SCAN! You can tell if it is doing the scan by looking at the S1 and S2 lights on the Call Processor. During a disk scan, they will be alternating back and forth (like police lights). Wait for it to complete and try netset again. I recommend doing a fresh reboot through netset after it comes back up just to be sure it's a fresh clean boot.
As long as someone hasn't been poking around in the phone system, this is a phone company issue. I have seen this many times and it has always been a carrier issue. Typically with PRI's or integrated access analog lines.
This was a rather simple fix. When I was speaking about the NBX V3000, I was talking about our 2U NBX Chassis which holds the line card. When our phone system was installed I wasn't shown the 1U NBX V3000 "Brain". I thought everything was contained in the chassis. Long story, short, I restarted the 1U "Brain" and the system came back up with 5 minutes.
Check if you can still connect to the the camera's UI, connect it to a router or computer. Try to ping its IP address and access the camera's UI, if ur able to access it, try to do the firmware upgrade again.
The phone is in a continuous because it is trying to connect to the NBX. You need to make sure it is on the same network as the NBX. Also, within the NBX you need to make sure Auto-Discovery is enabled. You also need to check how many group 2 licenses you have, as this phone requires one to run on the NBX.