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:
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:
# 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.
[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.
As root:
# rmdev -dl en7 # Just to be sure
# rmdev -dl et7
# rmdev -dl ent7# rmdev -dl ent1 # clean up anything that might not be as I want it
# rmdev -dl en1
# rmdev -dl et1
# cfgmgr # restore devices in default config
# 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.
Topic: Lost Connection to IVM/VIO (Read 34274 times)