Please login or register. October 18, 2017, 08:27:28 PM

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

0 Members and 1 Guest are viewing this topic.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Lost Connection to IVM/VIO
« on: December 10, 2013, 11:36:35 PM »
Hello to all.

I am a new member and this is my first issue.
I hoppe i can count with sugestions of all.

Hello to all. This is my first post.
I have a ibm p520 9131 with virtualization with 03 Logical partitions or Virtual Machines (aix 5.3,linux redhat 3.x,linux-test).
For some mistake the en0 of the vio server was missed (delete/reseted), so i cant reach vio/ivm to administrative purposes.

In control panel i can see that 192.168.2.147 e 192.168.3.147 are enable
I have Browser access to ASMi but there are no options to change VIO.
Is there a way to connect to vio from the lpars and setup a ip for vio?

My network is not using standard or best practice ip structure:

1) IP address of VIOS:
Production IP : 100.0.0.241 that was deleted/reseted

2) IP Address of your VIOS Client - AIX:
Prod IP : 100.0.0.240 - still working - Hera i have a Cache intersystems database running

3) IP Address of your VIOS Client - Linux:
Prod IP : 100.0.0.237 - still working - Here i have a Oracle database running

4) IP Address of your VIOS Client - Linux:
Prod IP : 100.0.0.243 - still working - Here we use to test some network management tools, etc.

The system was configured to use IVM.

I have installed HMC on a laptop (google:Installing HMC in VirtualBox or vmware) I am still confused about what I should do using hmc.
My readings about hcm says that the connection will neutralize ivm.
I just want to connect and make ivm live again given it a static ip.

I thank every kind of help.


Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #1 on: December 11, 2013, 07:22:50 AM »
You should still be able to connect using a serial cable. The BAUD rate is probably 19200. Then you login to IVM/VIOS on the console.

If you can connect to your client partitions this means your SEA is still functioning - so the interface you are missing is probably en6 or en7.

Working as root (use oem_setup_env to switch to root) using the following command should show whether your IP address is still in ODM or not. If it is, use lsdev -Cc adapter to see if it is available or not. Or just run cfgmgr.

The command to peek in ODM for IP addresses is:

Code: [Select]
michael@x054:[/home/michael]odmget -q "name like en? and attribute=netaddr"

CuAt:
        name = "en1"
        attribute = "netaddr"
        value = "192.168.129.54"
        type = "R"
        generic = "DU"
        rep = "s"
        nls_index = 4

CuAt:
        name = "en0"
        attribute = "netaddr"
        value = "192.168.2.1"
        type = "R"
        generic = "DU"
        rep = "s"
        nls_index = 4

And you are correct: you do not want to use the HMC or you will lose IVM features.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #2 on: December 11, 2013, 01:28:38 PM »
Hy Michael,
Thanks for reply.

I found two serial ports on the p520.
I have tested bolt ports but none work.
I have checked some IBM information from manual and to get these resourse to work i have to boot the machine with the serial cable
atached to my p520 and to a notebook with terminal emulator and then, after the p520 panel diplay a green light blinking i have to hit
enter on notebook to get access to ascii terminal.

Since this is a production machine, i will have to try at the end of the day.

I will report here soon.

Thanks

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #3 on: December 11, 2013, 06:31:23 PM »
Really boring - have an answer typed in, then it gets deleted because of cookie timeouts. Sigh: Security.

Short version:
verify serial port configuration - if you can - using the WEB ASMI interface (see attachment).

Since tty is not active NOW, I suspect a USB keyboard and a VGA screen was used to set the system up initially. If you have a graphics card, and a USB keyboard handy you might try that before you reboot. Just remember to either redefine the console to the serial port - OR - configure the serial port as login enabled.

re: WEB ASMI - remember to keep a version of FF 17.* around as that is the last version that support 40-bit https:// SSL connection encryption.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #4 on: December 12, 2013, 08:26:02 AM »
btw - welcome to rootvg. I see you have been having this problem (I googled the subject line to see if it had been spotted and saw the same question elsewhere - ittoolbox.com - so let me double the welcome.

as an aside - never change your forums without having an excellent rewriting rules setup first. Went from being in the top 10 regularly, to not very often, - but I diverge.

Another article I wrote earlier might be useful to you in the future - depending on how your system is setup to run. As I mentioned before I have another system (a 43P-140 actually, from 1996 or thereabouts, with a serial port out connecting to my power5 system I use for self-study. Very similar to your setup I expect.

http://www.rootvg.net/content/view/507/88/

As I have time I will login and show the commands/setup you will see from the command line.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #5 on: December 12, 2013, 01:04:57 PM »
Ok. I am sorry for any inconvenience I will policy attitudes in future.
i would like to apologise for my english (i have learned from myself)
I have access to asmi (web access using ethernet port) like i sai befere.
Serial ports are configured ok.
If i understand right, i will have to use/enable an option in asmi (serial snoop), enable the login at S1 an then reboot and wait for prompt.
I have read your script and i will give a try if the above dont lead me to the solution.

Due to the period of month (too much work) i cant make this befere next weekend.

Thanks for assist me.

Michael

  • Administrator
  • Hero Member
  • *****
  • Posts: 1052
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #6 on: December 12, 2013, 06:16:05 PM »
No need to apologize - "WELCOME to ROOTVG!" The more the merrier.

I shall look at the need to set "snoop". I never did that with my systems. I installed using the serial port, and then the serial port was automatically configured as console and login is possible.

So, check if there is a graphics card installed. If yes, you might be able to login using a USB keyboard and any VGA capable monitor.

Once you get logged in you need to do something like:
Code: [Select]
padmin@x091:[/home/padmin]r oem
oem_setup_env
# lsdev -Cc adapter | egrep ^ent
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

On my system there is only one SEA defined, and IVM, by default, puts the IP address on the SEA interface.

Regardless of whether you see an ent6 or ent7 interface you can check what is in the ODM using:
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.91 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
#

Here you see the netaddr is set, so once the device shows up it will work. If en6 does not have an IP address, but en7 does, then you should ALSO have a SEA on ent7.

So, the assumption is:
A. I see en6 values including a netaddr, but do not see an ent6 - This cannot be IF your client partitions were working before UNLESS you also have an ent7 defined - and that continued to work.

So, since there is an ent7 defined as SEA, and no IP address for en7 the basic assumption is that the second SEA (rather first) existed for IVM management only.

Code: [Select]
[li]The the command is (as padmin)
$ mkvdev -sea ent0 -vadapter ent2 -default ent2 -default_id 1

Then as root run:
# mkdev -l en6
# mkdev -l inet0[/li]
[li][/li]

You should now have regular communication.

If ent6 exists, and ent7 does not - ALSO en6 has no IP address and clients are working then perhaps you put your IVM management address on the  physical port (ent1) but were trying to activate a second SEA.

Since the clients are working (using ent6 as SEA) I would now put the IP address on the physical port and use the browser interface to "later" create a second SEA if needed.

Code: [Select]
As root:
# rmdev -dl en7 # Just to be sure
# rmdev -dl et7
# rmdev -dl ent7
Code: [Select]
# rmdev -dl ent1 # clean up anything that might not be as I want it
# rmdev -dl en1
# rmdev -dl et1

Code: [Select]
# cfgmgr # restore devices in default config
Code: [Select]
# chdev -l en1 -a netaddr=1.2.3.4 -a netaddr =255.25.255.0 -a state=up
# mkdev -l inet0 # restore default route, if any

At this point you should be able to ping/browse the VIOS using IVM browser.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #7 on: December 14, 2013, 05:46:14 PM »
Hy Michael...

The result of lsslot -c pci issued from a aix lpar show that : There are no PCI hot plug slots on this system.

I am here today waiting that the others workers finish your jobs to try a serial connection...

I will return soon as possible..

Thank you.

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #8 on: December 14, 2013, 05:54:11 PM »
and lsconf show:

System Model: IBM,9131-52A
Machine Serial Number: xxxxxxxxx
Processor Type: PowerPC_POWER5
Processor Implementation Mode: POWER 5
Processor Version: PV_5_3
Number Of Processors: 2
Processor Clock Speed: 2097 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 2 xxxxxxxxxxxxx_aix
Memory Size: 1024 MB
Good Memory Size: 1024 MB
Platform Firmware level: SF240_338
Firmware Version: IBM,SF240_338
Console Login: enable
Auto Restart: true
Full Core: false
 
Network Information
        Host Name: xxxxxxxxxxxxx-aix
        IP Address: 100.0.0.240
        Sub Netmask: 255.0.0.0
        Gateway: 100.0.0.230
        Name Server: 100.0.0.230
        Domain Name: xxxxxxxxxxxx.com.br
 
Paging Space Information
        Total Paging Space: 8192MB
        Percent Used: 15%
 
Volume Groups Information
==============================================================================
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            removed           799         273         113..00..00..00..160 (this will object of my next issue - how to synchronize this - raid 1)
hdisk1            active            799         281         121..00..00..00..160
==============================================================================
 
INSTALLED RESOURCE LIST
 
The following resources are installed on the machine.
+/- = Added or deleted from Resource List.
*   = Diagnostic support not available.
 
  Model Architecture: chrp
  Model Implementation: Multiple Processor, PCI bus
 
+ sys0                                                       System Object
+ sysplanar0                                                 System Planar
* vio0                                                       Virtual I/O Bus
* ent0             U9131.52A.10D36BG-V2-C4-T1                Virtual I/O Ethernet Adapter(l-lan)
* vscsi0           U9131.52A.10D36BG-V2-C2-T1                Virtual SCSI Client Adapter
* hdisk1           U9131.52A.10D36BG-V2-C2-T1-L820000000000  Virtual SCSI Disk Drive
* vsa0             U9131.52A.10D36BG-V2-C0                   LPAR Virtual Serial Adapter
* vty0             U9131.52A.10D36BG-V2-C0-L0                Asynchronous Terminal
+ L2cache0                                                   L2 Cache
+ mem0                                                       Memory
+ proc0                                                      Processor
+ proc2                                                      Processor

sistemas

  • Jr. Member
  • **
  • Posts: 8
  • Karma: +0/-0
Re: Lost Connection to IVM/VIO
« Reply #9 on: December 14, 2013, 05:55:54 PM »
and lsdisp show
lsdisp: 0468-006 No default display for LFT was found in the ODM.
lsdisp: 0468-030 No displays found for the LFT

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!