Originally posted by: SystemAdmin

I set up a VIO server LPAR on my 9115-505. I used Smitty to set up TCPIP minimum configuration but I am taking packet loss when I ping my IP not sure what to check.
I am a newbie to LPAR TCPIP.
#AIX-Forum

Originally posted by: bassemir

Do you have just one ethernet interface configured? Show us the output from ifconfig -a command.

What kind of packet loss are you seeing? 50% packet loss?

I had a problem once because I had two adapters configured, only one connected to the network so every other packet was attempting to use the second adapter. I was seeing 50% packet loss.

Rich
#AIX-Forum

Originally posted by: SystemAdmin

Here is my output for ifconfig -a I included my netstat -r output also

1. ifconfig -a

en0: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT
,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
inet 192.168.1.142 netmask 0xffffff00 broadcast 192.168.1.255
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
en1: flags=5e080863,c0<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST,GROUPRT
,64BIT,CHECKSUM_OFFLOAD(ACTIVE),PSEG,LARGESEND,CHAIN>
tcp_sendspace 131072 tcp_recvspace 65536 rfc1323 0
lo0: flags=e08084b<UP,BROADCAST,LOOPBACK,RUNNING,SIMPLEX,MULTICAST,GROUPRT,64BIT
>
inet 127.0.0.1 netmask 0xff000000 broadcast 127.255.255.255
inet6 ::1/0
tcp_sendspace 131072 tcp_recvspace 131072 rfc1323 1
>
0/24 VIO1 U 0 0 en1 - - =
>
default 192.168.1.40 UG 0 0 en0 - - =
>
default VIO1 UG 0 0 en0 - - =
>
default 192.168.1.105 UG 0 0 en0 - - =
>
default 192.168.1.0 UG 0 0 en0 - - =
>
default 209.183.214.17 UG 0 0 en0 - - =
>
default 192.168.1.1 UG 0 0 en0 - -
0.0.0.255 VIO1 UHSb 0 0 en1 - -
127/8 loopback U 12 272 lo0 - -
192.168.1.0 VIO1 UHSb 0 0 en0 - - =
>
192.168.1/24 VIO1 U 2 4420 en0 - -
VIO1 loopback UGHS 1 2 lo0 - -
192.168.1.255 VIO1 UHSb 0 2 en0 - -

Route tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 48 lo0 - -
#
#AIX-Forum

Originally posted by: bassemir

Okay, this is what I would try next.

1) remove the en1 network interface (use smitty, I don't recall the CLI syntax)
or
2) configure en1 with another IP address on your network, like 192.168.1.143 (if available)

Have you created any shared ethernet adapters, any link aggregation, or are you just trying to give an IP address to one of your vio's physical ethernet adapters?

If that does not work, show us the output from the lsdev -type adapter command (from the padmin account)and the output from the command lsmap -all -net (also from the padmin account)

Rich
#AIX-Forum

Originally posted by: SystemAdmin

Yes I have already created the SEA en3.

Here is my current lsdev -type adapter ouput before I make any changes.
/home/padmin

1. exit

$ lsdev -type adapter
name status description
ent0 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)

ent1 Available 2-Port 10/100/1000 Base-TX PCI-X Adapter (14108902)

ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent3 Defined Shared Ethernet Adapter
ent4 Available Virtual I/O Ethernet Adapter (l-lan)
fcs0 Available FC Adapter
fcs1 Available FC Adapter
ide0 Available ATA/IDE Controller Device
sisscsia0 Available PCI-X Dual Channel Ultra320 SCSI Adapter
usbhc0 Available USB Host Controller (33103500)
usbhc1 Available USB Host Controller (33103500)
vhost0 Available Virtual SCSI Server Adapter
vhost1 Available Virtual SCSI Server Adapter
vhost2 Defined Virtual SCSI Server Adapter
vhost3 Defined Virtual SCSI Server Adapter
vhost4 Defined Virtual SCSI Server Adapter
vhost5 Defined Virtual SCSI Server Adapter
vsa0 Available LPAR Virtual Serial Adapter
$
#AIX-Forum

Originally posted by: Casey_B

So,

I think that this problem doesn't relate so much to LPAR/VIO, but rather the routing setup looks a bit funny to me.

I don't think having en1 up, but not configured with an IP is a problem. It certainly can be confusing...But probably not
a problem.

Now, before talking about your netstat -r, one comment...The group doesn't know what the value of "VIO1" is, so the netstat information
isn't 100% clear.

Let me make a guess, though....VIO1 appears to be your ip address for en0 == 192.168.1.142
(Reason I say that, is there are some network routes for 192.168.1/24 pointing to VIO1, these would
have been automatically configured by AIX when the address was placed on the interface)

Ok, to continue...

Now you have a default route that points to each of the following addresses:
default 192.168.1.40 UG 0 0 en0 - - =
default VIO1 UG 0 0 en0 - - =
default 192.168.1.105 UG 0 0 en0 - - =
default 192.168.1.0 UG 0 0 en0 - - =
default 209.183.214.17 UG 0 0 en0 - - =
default 192.168.1.1 UG 0 0 en0 - -
AIX will round robin outgoing connections through all of these default routes.

One of the default routes points to VIO1, which is guess is local to the machine. Does that work? In most cases it shouldn't...
One of the default routes references 209*, which shouldn't be reachable from your ifconfig output.
(This may work if you have the 209 directly connected, and specified the route correctly)
What about all of the other ones...including 192.168.1.0....That seems wrong... .0 is a network
address, not a host address.

So, I believe that AIX will round robin to all of these dubious routes for outgoing connections,
causing drops on bad routes, and success on good routes....

To check what might be happening try the following command:

route -n get 10.100.100.100
(The address doesn't need to be a real machine, I chose 10.100.100.100 because it should be routed through the default gateway)

Run it several times, and see that the "gateway" is changing on each of the calls.

There is something else that seems out of the ordinary, the route to 0.0.0/24 But, seeing as this machine might
be a VIO server...I just don't know if that is normal. I know more about AIX than anything with VIO...Certainly
does seem like an odd route, though.
So, my advice is to clean up your default routes, and see if that helps.

I can't tell you which ones are correct for your environment...

Hope this helps,
Casey
#AIX-Forum

Originally posted by: SystemAdmin

I am attempting to remove the en1 adapter as per your suggestion using smitty so when i go to "devices" and 'Communication" then 'Ethernet" and list all ethernet adapters all I get are the physical adapters, (ent0 to ent4) my en1 is virtual I guess. So if I remove my en1 I think I will have to go command line.

COMMAND STATUS

Command: OK stdout: yes stderr: no

Before command completion, additional instructions may appear below.

ent2 Available Virtual I/O Ethernet Adapter (l-lan)
ent4 Available Virtual I/O Ethernet Adapter (l-lan)
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)
ent3 Defined Shared Ethernet Adapter
Esc+1=Help Esc+2=Refresh Esc+3=Cancel F6=Command
F8=Image F9=Shell F10=Exit /=Find
n=Find Next
#AIX-Forum

Originally posted by: bassemir

The en1 is not a virtual interface, it is a real interface. The fact the SEA (ent3) is "defined" is also strange to me. But if it were me I would still remove the en1 interface and clean up the routing table as Casey suggests.

Using smitty you can remove the interface by going Communication - ethernet - further config - network interface - network interface selection - remove network interface.

Once that interface is gone, see what your routing table looks like. Maybe flush the table?

I typically assign the IP address to my SEA interface. In your case that would be ent3.

Rich
#AIX-Forum