02-01-2002 10:25 AM
Any/all help greatly appreciated.
02-01-2002 10:40 AM
02-01-2002 10:41 AM
What version of Netscape or IE are you running? Can you click on the window that has the terminal display? Then hit return, if nothing happens, try ctrl-b, just to see if you have the web console hooked up correctly. BTW, what kind of server and web console??
Also, for debugging purposes, hook up a real console to make sure the console port is still working.
live free or die
02-01-2002 10:53 AM
I have the documents you mentioned and have throughly gone through them.
I am using either Netscape 6 or IE 5.5.
The webconsole is model J3591A. I have the emulation set to vt100.
In IE, I have the following enabled: Java Console, Java Logging, JIT.
02-01-2002 11:09 AM
Here's my settings for the web console:
term type vt100
baud rate 9600
Parity/data bits none/8
parity checking disable
Xon/Xoff not selected
Once you "Access console" does "Get history" show you anything?
Is it possible to connect a normal terminal to the console port to see if that works?
Have you verified the serial cable connection from the web console to the system's console port?
02-01-2002 11:16 AM
I never connected the serial cable.
Thanks all for your insights. Andy
02-01-2002 11:19 AM
Check and see if java plugin are installed for the browser you are using. This looks like a problem with java. Can you ping the console with the new ip.
Hope this helps.
02-01-2002 11:36 AM
Anyway, no one has to know, especially your manager. I'd let mine know how hard I worked, all the research I did, and all the effort I put into making it work!
Darrell -who's made plenty of SUEs and SAEs (Stoopid Admin Error)
02-01-2002 02:09 PM
It's not a stupid error, our operations staff does it to me ALL THE TIME!!! Then when they call with a problem saying the box is down and I access the SWC, it drives me crazy trying to figure out why even the GSP will not respond. Then I remember and have them go out to check the cable.
This happens at least once a month.
02-01-2002 08:01 PM
I would not use a PC as a dumb terminal unless you have used it successfully as a terminal in the past. When you use a PC and don't get a prompt, you now have two complex computer systems and cables to debug.
Finally, a software error may have disabled the console prompt so you won't see the login request. However, the service processor is always active on most newer servers, so CTRL-B should get you some text on the screen.
02-12-2002 04:50 AM
I do have an 8 port Arula, that I attached to the server and that seemed to work fine. That was on a different port though. I'm all kinds of confused. If the internal port were not working, would I have been able to configure it, at all?
Any help is greatly appreciated.