Hi Gary,

We used both methods on a 515 (LAN) and 270 (cable and LAN) and it works fine.

For lan console we use a separated lan adapter (which can be used if primary fails) because when Console is active it will not allow TCP/IP to work on the same adapter so you can't have the Console and yours 5250 emulations working together . For Cable Attached Console you need the special cable and a PC with serial port and it's very simple to configure.

Regards,
Wilson

Gary,

I have used both as well and e found that the performance from cable attched console thru a serial interface was a dog.



Gary,

Be aware that the cable attached serial interface could be a dog on performance although it states its connecting at 115K, it still left a lot to be desired.

Regards,

Mark

Hi Gary,

I've setup new servers with LAN Console a whole bunch of times so I've been through the best and worst (Minutes to hours to get a session up). The best way to do it the first time is with a regular patch cable straight from the PC to the "FIRST" Ethernet port on the E4A. Leave the server powered down until you're ready. You will need to manually configure an IP, subnet and gateway for the network adapter on your PC. The IP can just be anything in the same subnet as you want the console to be on. Use your main networks subnet and gateway values. Now set up the Operations Console session. Give it a name, Partition 1,, IP, Subnet, Gateway, Server serial number,, The Device ID can stay QCONSOLE,, Set the password for this Console session,, click Finished.
Highlight your new setup from the Operations Console screen and Connect. Now fire up the server.
Watch the passwords! Sometimes it's asking for the Console sessions password (Whatever you made it) and sometimes it's asking for the Service Tools password (QSECOFR / QSECOFR). The service tools password will be expired so you'll need to key in a new one.
If you get a message that says - Authority has not been granted to the partition 1 remote control panel.
Remove it from the selected list? - say No. It will come up again later and work if you say No.
If this all works and you get in your half way there. At this point I disable most of the security around the LAN Console setup or you will not be able to get back in to fix it if you screw it up somehow accept from the front panel (Big Pain). You’ll want to do this right at this point to avoid problems.

Change the panel to “M” Manual.
Select function 21
Sign into DST

Use Dedicated Service Tools (DST)

13. Work with system security
Allow a service tools user ID with a
default and expired password to change
its own password . . . . . . . . . . . . . . 1 1=Yes


Use Dedicated Service Tools (DST)

5. Work with DST environment

2. System devices

6. Select console

Allow console recovery and console can be taken
over by another console . . . . . . . . . 1


Use Dedicated Service Tools (DST)

5. Work with DST environment

5. Service tools device IDs

1=Create
Create QCONSOLE1, QCONSOLE2 and QCONSOLE3


Use Dedicated Service Tools (DST)

5. Work with DST environment
6. Service tools security data

Selection
7

7. Work with lock for device IDs from SST Enabled

Notice: When you use the Selection 7 and press Enter 7 will cycle from Enabled to Disabled


Use Dedicated Service Tools (DST)

5. Work with DST environment
6. Service tools security data

8. Password expiration interval in days 0 <== Change to Zero

Selection
8

Notice: When you use the Selection 8 you are “Setting” the value you typed to the right of option 8


Use Dedicated Service Tools (DST)

5. Work with DST environment
6. Service tools security data

9. Maximum sign-on attempts allowed 15 <== Change to 15

Selection
9

Notice: When you use the Selection 9 you are “Setting” the value you typed to the right of option 9


Use Dedicated Service Tools (DST)

5. Work with DST environment
6. Service tools security data

10. Duplicate password control 0 <== Change to Zero

Selection
10

Notice: When you use the Selection 10 you are “Setting” the value you typed to the right of option 10

Change front panel back to 01 B N or whatever it was.

Wait until you have the server up on your network and you can open up a regular session before you try to move the LAN Console connection onto the network (If that is what you’re going to do).
This way you can use a regular session to help troubleshoot if you are having trouble with the Console connection. We usually do move the Console to the network so that we can access it from multiple PCs. It’s just a matter of plugging that first Ethernet port into your switch.

Note: When you create an Operations Console session on your PC an entry will be added to the HOSTS file on that PC. If you want to change the IP address of the session or want to delete and reuse the same name you will need to delete the HOSTS file entry.
This is the path to the HOSTS file on your PC: C:\Windows\System32\drivers\etc\hosts
The entry looks something like this: 192.168.1.100 POWER6
You should use NotePad to open and edit this file.

Voodoo

Please complete the following information:

REGISTER / LOG-IN TO DISCUSS

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Submit your e-mail address below to continue

E-mail: 

E-mail: 

Handle:   

Password: 

Forgot Password?

Create Handle: 

Your handle identifies you in ITKnowledgeExchange. Max 30 char.

Create Password: 

Confirm Password: 

Yes, I agree to the IT Knowledge Exchange  Terms and Conditions.

hidden modal window