Operating Console
Hi
I have operations console running on a laptop which is directly connected to my I-Series. All runs okay until the laptop powers down(for variety of reasons), when i power it on again it will not connect to the I-Series without doing an IPL of the I-Series. I get the message "Connecting Console" and it never connects. When i do the IPL i leave the laptop powered on and it connects without any problems.
Is this normal? does the laptop need to been connected and powered on permenently? If not does anybody have any ideas as to why this may be happening?
Thanks
Software/Hardware used:
Software/Hardware used:
ASKED:
June 28, 2006 2:52 AM
UPDATED:
July 5, 2006 11:05 AM
Answer Wiki:
You are correct in assuming that the Ops Console needs to be powered up all the time whilst the iSeries is on. I had this same problem with a laptop back 2003.
I tried everything - reinstalling iSeries Access & trying other versions as well; then uninstalling and reinstalling the AOC modem drivers - several times. I also disconnected another Ops Console (desktop PC) from a working iSeries - that did not connect either. However, when I connected the PC back to working iSeries it didn't reconnect! I had to IPL the working iSeries to get the connection back.
On the original iSeries, I had to schedule an IPL out of working hours to see if it cures the issue. I believed it would, because the symptoms when I disconnected and reconnected the desktop PC on the working iSeries were the same.
After the IPL, the system detected the Ops Console on the laptop and all was well.
I put a note in our company's call log:
Lesson learnt: If the system console is an Ops Console via a PC (or laptop), the connection cannot be re-established if the PC is disconnected and changes made - the system requires an IPL to re-establish communications.
I always said it was a mistake when IBM moved away from twinax, I can understand the rational, but do not understand the horrible nightmare just to get a simple connection.
You shouldn't have to IPL the box to be able to access the system console. What happens if you are in the middle of an upgrade and the Ops Console "blue screens"!? IBM have a lot to answer for, for this error of judgement!
Good luck,
Richard.
To see all answers submitted to the Answer Wiki: View Answer History.
When you Laptop drops without disconnecting the Console session properly its leaving the device DSP01 or other in a “Signon Display” state. If you still have IP connectivity just sign on to another telnet session vary off DSP01 then vary it back on. Then back on your Console session it will connect again.
In a case where you lose Ethernet connectivity and your Console session drops (extended power outage) you will have to IPL to get the Console back. Couple of ways around that. 1 – make it a habit to disconnect the Console when not in use so the device is always vary on pending. 2 – Write a monitor program to watch QSYSOPR for Ethernet connectivity messages and have it reply with a R (Retry) say every 15 minutes or so. So when the LAN/WAN does come back up you get your IP back without needing the Console.
When you Laptop drops without disconnecting the Console session properly its leaving the device DSP01 or other in a “Signon Display” state. If you still have IP connectivity just sign on to another telnet session vary off DSP01 then vary it back on. Then back on your Console session it will connect again.
In a case where you lose Ethernet connectivity and your Console session drops (extended power outage) you will have to IPL to get the Console back. Couple of ways around that. 1 – make it a habit to disconnect the Console when not in use so the device is always vary on pending. 2 – Write a monitor program to watch QSYSOPR for Ethernet connectivity messages and have it reply with a R (Retry) say every 15 minutes or so. So when the LAN/WAN does come back up you get your IP back without needing the Console.
Try deactivating then reactiviting the console line. On the AS400 control panel, select function 25, prese enter, function 26, press enter (this allows access to the upper range of function numbers), function 65, press enter to deactivite the line, wait 15 seconds, function 66, press enter to activate the line. If this doesn’t work perform the same process but between the function 65 and 66, pull the console cable and reboot the PC and plug the cable back in.