| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
Welcome to the pSeries Tech Forums,
our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software. You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments. Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community. Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
| Our Sponsors | |
| | |
| Want to advertise? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
Hi all, wondering if anyone can help here. I have a p510 which has just been issued a DHCP IP address via the HMC. The server has been propgated into the managed node list, however when trying to connect, I get the Login screen, but cannot do anything from there. It looks like the screen just hangs.? I have tried the following. # lsdev -C | grep vsa vsa0 Available LPAR Virtual Serial Adapter 2. Check the children of this device. There should be a virtual terminal device # lsdev -C -p vsa0 vty0 Available Asynchronous Terminal 3. Check to see what the console is currently set to. On a 510 we have up and working on another HMC it is set to be the vty0 device shown in step 2 # lscons -a current = /dev/vty0 console_logname = /var/adm/ras/conslog console_logsize = 32768 console_logverb = 1 console_tagverb = 0 If this is not the case can try resetting the console temporarily to see if it works # swcons /dev/vyt0 = works fine # chcons /dev/vty0 = fails because console device is not avaliable. # lsattr -El vty0 -a login # chdev -l vty0 -a login=enable and it still does'nt work? Any ideas welcome. many Thanks Martin |
|
#2
| ||||
| ||||
Martin, Something for you to try To completely remove vsa0 and vty0 from ODM and have system come up on reboot and prompt you to set this terminal as your console. If you have network access you can do this from a telnet or ssh session If you have no network access you will need to boot into Maintenance Mode # odmdelete -q name=vty0 -o CuDv 0518-307 odmdelete: 1 objects deleted. # odmdelete -q name=vsa0 -o CuDv 0518-307 odmdelete: 1 objects deleted. # odmdelete -q attribute=syscons -o CuAt 0518-307 odmdelete: 1 objects deleted. # bosboot -ad /dev/ipldevice bosboot: Boot image is 23794 512 byte blocks. # sync # reboot When system comes up it should reconfigure vsa0 and vty0 and since we removed "syscons" from ODM it should prompt you to select terminal. |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |