Please login or register. October 17, 2017, 08:16:01 PM

Author Topic: Lost Connection to IVM/VIO  (Read 11540 times)

0 Members and 1 Guest are viewing this topic.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #10 on: December 15, 2013, 12:39:13 AM »
Hi...

I fill a litle disapointed with myself and with a litle of shame.

i rebooted the server but it only thing that it show me are options that dont let me login as padmin

Firstly after a power off from asmi, the ascii terminal prompt only get access to admin/admin from asmi (cant do nothing)

When i restart the system it prompt me to choice sms/firmware/boot list (i have tried only sms and firmware and cant do nothing even)

I have enabled snoop serial and nothing
I have disabled snoop serial and nothing

What else can i do?
If you have patience, please give a light.

Thanks.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #11 on: December 15, 2013, 03:26:50 PM »
If this is from the client partition I would not expect to see the graphics card.

Now seeing your post about after a reboot.

Could you login as admin using the web interface before? If yes, then we are good to move forward - because you can use the ASMI serial interface to boot into maintenance mode.

I shall try to do the same on my system and capture all the text.

will update shortly.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #12 on: December 15, 2013, 04:56:46 PM »
1) I do not have snoop enabled on any of my serial ports. This is only needed if you want to be able to force some action (such as reboot) by sending a string to a serial port.

2) what is needed is figuring out a way to get the console to head to the serial port for maintenance.
Note: this is much easier if you have the VIOS DVD because then you can do a normal maintenance boot (option 3). For now I am assuming you do not have that DVD.

3) start the system in SMS mode - from the ASMI interface
a) from the PowerOn/Off Menu use option 4 to set to boot in SMS mode. Your screen should look like this:
Code: [Select]
Power On/Off System
Current system power state: Off
Current firmware boot side: Temporary
Current system server firmware state: Not running

 1. System boot speed
        Currently: Fast
 2. Firmware boot side for the next boot
        Currently: Temporary
 3. System operating mode
        Currently: Normal
 4. AIX/Linux partition mode boot
        Currently: Boot to SMS menu
 5. Boot to system server firmware
        Currently: Running
 6. System power off policy
        Currently: Power off
 7. i5/OS partition mode boot
        Currently: A
 8. Power on
98. Return to previous menu
99. Log out

Now choose option 8 to start the system, eventually you will see:

Code: [Select]
PowerPC Firmware
 Version SF240_418
 LKM 1.6 (c) Copyright IBM Corp. 2000,2005 All rights reserved.
-------------------------------------------------------------------------------
 Language Selection Menu

 Current Language :  ISO8859-1 English (United States)

 1.   Change Language
 2.   Continue to Password Entry









 -------------------------------------------------------------------------------
 
 
 
 -------------------------------------------------------------------------------
 Type menu item number and press Enter:
Choose option 2, and enter the "admin" password again.

Now the SMS menu is open.

Just to be sure, choose option 4 to specify the console. If you also have a VGA screen and a USB keyboard attached you will be able to switch between the two as console.
I am assuming you are continuing with the serial port, and press 0 to select the serial port as console.

4) Now choose option 5 - Select Boot Options -

Choose option 1, I will say option 7 to list all, for simplicity.

When the list completes: choose the VIOS DVD if you have it (then you do not need to know root password to login). Also note - you may need to press N to see the next page.

Again, assuming you do not have the DVD, choose the hardisk with VIOS on it. AND on the next screen, choose option 3 -- Service Boot

Code: [Select]
PowerPC Firmware
 Version SF240_418
 SMS 1.6 (c) Copyright IBM Corp. 2000,2005 All rights reserved.
-------------------------------------------------------------------------------
 Select Task

SCSI 73407 MB Harddisk, part=2 (VIOS 2.2.2)
    ( loc=U788C.001.AAA4403-P1-T11-L4-L0 )

 1.   Information
 2.   Normal Mode Boot
 3.   Service Mode Boot








 -------------------------------------------------------------------------------
 Navigation keys:
 M = return to Main Menu
 ESC key = return to previous screen         X = eXit System Management Services
 -------------------------------------------------------------------------------
 Type menu item number and press Enter or select Navigation key:

As it boots, the connection may disconnect - keep trying to restablish a connection. Eventually, it will say "Connected". If it does not disconnect - it will be much easier as you will not need to answer prompts in the blind.

Code: [Select]
michael@x054:[/home/michael]cu -l tty1
Connected

Lost carrier.

The connection is ended.
michael@x054:[/home/michael]cu -l tty1
Connected

Lost carrier.

The connection is ended.
michael@x054:[/home/michael]cu -l tty1
Connected

Lost carrier.

The connection is ended.
michael@x054:[/home/michael]cu -l tty1
Connected

Lost carrier.

The connection is ended.
michael@x054:[/home/michael]cu -l tty1
Connected


I am connected, but I did not get to see the prompt - so I just enter some string that is an error: aaaaaa

Now I get the prompt for the FUNCTION SELECTION (Service Boot):
Code: [Select]
michael@x054:[/home/michael]cu -l tty1
Connected
aaaaa
FUNCTION SELECTION

1. Diagnostic Routines
    This selection will test the machine hardware. Wrap plugs and
    other advanced functions will not be used.
2. Advanced Diagnostic Routines
    This selection will test the machine hardware. Wrap plugs and
    other advanced functions will be used.
3. Task Selection(Diagnostics, Advanced Diagnostics, Service Aids, etc.)
    This selection will list the tasks supported by these procedures.
    Once a task is selected, a resource menu may be presented showing
    all resources supported by the task.
4. Resource Selection
    This selection will list the resources in the system that are supported
    by the diagnostic programs. Once a resource is selected, a task menu will
    be presented showing all tasks that can be run on the resource(s).
5. Single User Mode
    The system will enter single-user mode for software maintenance.





To make a selection, type the number and press Enter [1]:

5) Choose option 5 here. Again, you may lose connection as the system starts to boot in maintenance mode - you will need to know the root password (not padmin!)

Code: [Select]
To make a selection, type the number and press Enter [1]:5

Be careful as you "reconnect" - there will come a moment that you are connected, and nothing happens. NOW the system is waiting for the root password to start maintenance mode.

Unfortunately - I do not know my root password - so I will have to boot normally, change the root password, and then proceed with the post.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #13 on: December 15, 2013, 05:29:26 PM »
Sometimes, a bit of luck can be nice. I had entered the correct password, but the screen did not move forward. Pressing "Ctrl-C", for just in case got me a lot of error messages (I am not too worried about)... because I suspect it has to do with a filesystem that is not mounted yet.
Code: [Select]
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
Unable to open file: /home/ios/logs/ioscli_global.trace for append
Error from cliCheckFile:-1
#
What is important is the # prompt - I am root in maintenance mode.

Now I want to know what my console is: the command for that is lscons

Code: [Select]
# lscons -a
 current = /dev/vty0
 console_logname = /var/adm/ras/conslog
 console_logsize = 32768
 console_logverb = 1
 console_tagverb = 0
#
Now, what this is not showing is if it is enabled for login or not - it is, but just to be sure I am going to use the "change console" chcons command.

First, the syntax:
Syntax

       chcons [ -a login { =disable | =enable} ] [ -a
       console_logname=file ] [  -a console_logsize=size ]
       [ -a console_logverb=number ] [ -a
       console_tagverb=number ] PathName


So, simply entering:

Code: [Select]
# chcons -a login=enable /dev/vty0
The login=enable should not be necessary, but in a situation like this - I want to be sure. (From man page)

       If the console path name is a character device, the
       system starts the login program on the device.
       Login is enabled on the console at all run levels.
       If no login is desired, use the -a login=disable
       flag.
            CAUTION: If the console is the only login
            terminal on the system, you cannot log in at
            the next start of the system using the -a
            login=disable flag.



So, I hope after getting through all of this - shutdown -Fr will have the console coming up, and you can login as padmin - HOWEVER - since you are already logged in as root - why not use smit or chdev to put an address on your SEA adapter.

Code: [Select]
# lsdev -Cc adapter
ent0      Available 03-08 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent1      Available 03-09 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)
ent2      Available       Virtual I/O Ethernet Adapter (l-lan)
ent3      Available       Virtual I/O Ethernet Adapter (l-lan)
ent4      Available       Virtual I/O Ethernet Adapter (l-lan)
ent5      Available       Virtual I/O Ethernet Adapter (l-lan)
ent6      Available       Shared Ethernet Adapter
ent7      Available       Shared Ethernet Adapter

Code: [Select]
# lsattr -El en6
alias4                        IPv4 Alias including Subnet Mask              True
alias6                        IPv6 Alias including Prefix Length            True
arp           on              Address Resolution Protocol (ARP)             True
authority                     Authorized Users                              True
broadcast                     Broadcast Address                             True
monitor       off             Enable/Disable monitor attribute              True
mtu           1500            Maximum IP Packet Size for This Device        True
mtu_bypass    on              Enable/Disable largesend for virtual Ethernet True
netaddr       192.168.129.101 Internet Address                              True
netaddr6                      IPv6 Internet Address                         True
netmask       255.255.255.0   Subnet Mask                                   True
prefixlen                     Prefix Length for IPv6 Internet Address       True
remmtu        576             Maximum IP Packet Size for REMOTE Networks    True
rfc1323                       Enable/Disable TCP RFC 1323 Window Scaling    True
security      none            Security Level                                True
state         up              Current Interface Status                      True
tcp_mssdflt                   Set TCP Maximum Segment Size                  True
tcp_nodelay                   Enable/Disable TCP_NODELAY Option             True
tcp_recvspace                 Set Socket Buffer Space for Receiving         True
tcp_sendspace                 Set Socket Buffer Space for Sending           True
thread        off             Enable/Disable thread attribute               True
Code: [Select]
# lsattr -El en7
alias4                       IPv4 Alias including Subnet Mask              True
alias6                       IPv6 Alias including Prefix Length            True
arp           on             Address Resolution Protocol (ARP)             True
authority                    Authorized Users                              True
broadcast                    Broadcast Address                             True
monitor       off            Enable/Disable monitor attribute              True
mtu           1500           Maximum IP Packet Size for This Device        True
mtu_bypass    off            Enable/Disable largesend for virtual Ethernet True
netaddr       192.168.90.101 Internet Address                              True
netaddr6                     IPv6 Internet Address                         True
netmask       255.255.255.0  Subnet Mask                                   True
prefixlen                    Prefix Length for IPv6 Internet Address       True
remmtu        576            Maximum IP Packet Size for REMOTE Networks    True
rfc1323                      Enable/Disable TCP RFC 1323 Window Scaling    True
security      none           Security Level                                True
state         up             Current Interface Status                      True
tcp_mssdflt                  Set TCP Maximum Segment Size                  True
tcp_nodelay                  Enable/Disable TCP_NODELAY Option             True
tcp_recvspace                Set Socket Buffer Space for Receiving         True
tcp_sendspace                Set Socket Buffer Space for Sending           True
thread        off            Enable/Disable thread attribute               True
#

What you are really looking for/verifying is:
Code: [Select]
# lsattr -El en6 -a netaddr -a netmask
netaddr 192.168.129.101 Internet Address True
netmask 255.255.255.0   Subnet Mask      True
# lsattr -El en7 -a netaddr -a netmask
netaddr 192.168.90.101 Internet Address True
netmask 255.255.255.0  Subnet Mask      True
#

So, you can use the following command to set an IP address - and then you should be good to go.

Code: [Select]
# chdev -l enX -a netaddr=A.B.C.D -a netmask=255.X.Y.Z -a state=up

I hope this has your up and running - as desired.

p.s. - while you have the chance to be rebooting the system, you may want to update your firmware to " SF240_418".

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #14 on: December 16, 2013, 01:57:59 PM »
Hi Michael,

In my past message i was a litle half away from the soluction.
I get the sms prompt, choose the right options but stop on boot choice, since i dont knew what to do i prefer stop.

With your new intructions i will check later to se what i can do.

Have a nice day

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #15 on: December 16, 2013, 06:46:24 PM »
I check in again tomorrow to read how you are doing!

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #16 on: December 23, 2013, 11:19:26 PM »
No news is good news I hope. Still curious to know how you are doing with this!