First off when troubleshooting system "lock ups" it can be tedious, tricky and exhausting. When the system freezes first find out
1. Do any phones have dialtone (no)
2. Can you access the v3000 admin Gui (no)
3. Can you ping the v3000? (no)
4. Check the v3000 ethernet cable, is it connected? does it have a link light with activity?
5. Move the v3000 to a different ethernet switch port, does that help?
6. do an "i" command from the console and take note of suspended tasks
7. See my notes on running nbxSaveCore command, if 1-5 does not help 3com support will need to be involved to decipher some of the logs. Also, start keeping good records of the time (exact) that the system fails.
8. Sometimes its a good idea to plug the nbx into a hub and plug that hub into the network switch. This will allow you to connect your pc to that hub and use a program like wireshark, to sniff the line to see whats coming thorugh. sometimes there can be other apps on the network using certain ports like 1025 and 1026 that can interfere with the nbx...not as likely though
when the system is locked up, before doing a ctrl+R, type nbxSaveCore and rpess enter. this will take a few minutes but it will dump the current logs into a certain directory
nbxSaveCore will do asynchronous writes to the disk and does not tar up all the files, saving precious minutes when you need to get the system operational. This new command means less downtime for your customers and we even created two different ways to enter the command so a novice technician or customer that might be taking instructions on the phone (cell phone if they are entering this command...) will not be tripped up by the traditional bumpy case commands of a CLI.
A typical NBX100 with 64mb of memory can run a savecore in less than three minutes !!!
Savecore writes a new directory to the disk based on the time of your savecore. For example, you would see a new directory in /htfs0/Core_Jan09_03_35pm. In this directory, you will need to copy all the files for development to analyze.
Files in this directory are:
nboss.inf
nboss.cor
adminlog.txt
NBossLog.txt
upglog.txt
All OldNBossLog's