Sponsored Content
Full Discussion: LPAR Networking: Can't ping
Operating Systems AIX LPAR Networking: Can't ping Post 302673231 by zaxxon on Tuesday 17th of July 2012 05:11:47 PM
Old 07-17-2012
I would suggest you compare via HMC the settings of the virtual ethernet adapter of one of your working LPARs with the non-working one.
Both have to be in a VLAN that is set on the SEA on the VIO. Your SEA can have more than 1 Virtual Lan ID. It needs to match at least one VLAN-ID between your LPAR's vAdapter and the VIO/SEA. It could also be, that all your client LPAR vAdapters are in the same VLAN which makes things a tad easier when comparing settings.
Maybe you have accidentally hooked a box for trunking or priority, whatever.
Have no HMC at hand, but here is a link, that shows exactly how things are set up:

http://www.ibm.com/developerworks/sy...5-virtualvlan/

Last edited by zaxxon; 07-18-2012 at 05:45 AM.. Reason: Rephrasing the whole post to a more proper english
 

10 More Discussions You Might Find Interesting

1. AIX

LPAR and CFGMGR

I have a P570 that for some reason is not allowing the P1-T6 NIC to be recognized. I have confirmed from the HMC that it is set for the LPAR, but when I do a cfgmgr, it won't recognize it. It though is recognizing the slot cards just fine which are P1-C3 for one shelf and P1-C3 of another shelf.... (1 Reply)
Discussion started by: LegendMan
1 Replies

2. IP Networking

ping and networking

Dear friends, Please explain the functionality of the ping command and explain the network details, and IP layers. I want some more clarification about following things i) switch ii) hub iii) routers iv) proxy (3 Replies)
Discussion started by: thangappan
3 Replies

3. AIX

LPAR

I am planning for System P with 2 number of 2-core processor (4 core in total). Can I make 3 LPARS with this processor configuration without the support of micropartitioning, that means with simple LPAR only. (3 Replies)
Discussion started by: pchangba
3 Replies

4. AIX

LPAR creation

can i get a step b syep explanation in creating LPAR... i have searched for tutorials i couldn't find the right one.... (2 Replies)
Discussion started by: udtyuvaraj
2 Replies

5. AIX

LPAR freezes after switching of storage (lpar is mirrored)

Hi all, I have the following configuration 2 ds3524 storage disk systems located over 2 locations 2 P720 server located over 2 locations DS3524 are connected to san switch. Each vio server has 1 fc adapter attached to a san switch. per p720 server 2 virtual io servers. Vio 1 has 1 lun... (2 Replies)
Discussion started by: markiemark
2 Replies

6. Shell Programming and Scripting

Animation Ping on Solaris Like Cisco Ping

Hi, I develop simple animation ping script on Solaris Platform. It is like Cisco ping. Examples and source code are below. bash-3.00$ gokcell 152.155.180.8 30 Sending 30 Ping Packets to 152.155.180.8 !!!!!!!!!!!!!.!!!!!!!!!!!!!!!. % 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies

7. AIX

Networking Issue (Cant Ping the gateway)

Hi, I installed AIX 7.1 on a blade though (hmc with vio). I can ping the IP address, but not the gateway. Is there anything that I should configure? Is there anything that I have to check with vio setting or Am I missing any configuration? Please let me know further. Thank you (5 Replies)
Discussion started by: pjeedu2247
5 Replies

8. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies

9. AIX

How to differentiate between a standalone LPAR and a VIOC (which again is a lpar)?

There can be configurations in IBM Server wherein a standalone partition is created on some supported IBM Server Or A VIOS - VIOC LPARs created. Now in both cases they are lpars. But if I want to differentiate b/w a standalone LPAR vs an VIOC LPAR how can I do..? On a... (2 Replies)
Discussion started by: Manish00712
2 Replies

10. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
ovs-vlan-test(1)						Open vSwitch Manual						  ovs-vlan-test(1)

NAME
ovs-vlan-test - check Linux drivers for problems with vlan traffic SYNOPSIS
ovs-vlan-test [-s | --server] control_ip vlan_ip Common options: [-h | --help] [-V | --version] DESCRIPTION
The ovs-vlan-test utility has some limitations, for example, it does not use TCP in its tests. Also it does not take into account MTU to detect potential edge cases. To overcome those limitations a new tool was developed - ovs-test. ovs-test is currently supported only on Debian so, if possible try to use that on instead of ovs-vlan-test. The ovs-vlan-test program may be used to check for problems sending 802.1Q traffic which may occur when running Open vSwitch. These prob- lems can occur when Open vSwitch is used to send 802.1Q traffic through physical interfaces running certain drivers of certain Linux kernel versions. To run a test, configure Open vSwitch to tag traffic originating from vlan_ip and forward it out the target interface. Then run the ovs-vlan-test in client mode connecting to an ovs-vlan-test server. ovs-vlan-test will display "OK" if it did not detect problems. Some examples of the types of problems that may be encountered are: o When NICs use VLAN stripping on receive they must pass a pointer to a vlan_group when reporting the stripped tag to the networking core. If no vlan_group is in use then some drivers just drop the extracted tag. Drivers are supposed to only enable stripping if a vlan_group is registered but not all of them do that. o On receive, some drivers handle priority tagged packets specially and don't pass the tag onto the network stack at all, so Open vSwitch never has a chance to see it. o Some drivers size their receive buffers based on whether a vlan_group is enabled, meaning that a maximum size packet with a VLAN tag will not fit if no vlan_group is configured. o On transmit, some drivers expect that VLAN acceleration will be used if it is available, which can only be done if a vlan_group is configured. In these cases, the driver may fail to parse the packet and correctly setup checksum offloading or TSO. Client Mode An ovs-vlan-test client may be run on a host to check for VLAN connectivity problems. The client must be able to establish HTTP connec- tions with an ovs-vlan-test server located at the specified control_ip address. UDP traffic sourced at vlan_ip should be tagged and directed out the interface whose connectivity is being tested. Server Mode To conduct tests, an ovs-vlan-test server must be running on a host known not to have VLAN connectivity problems. The server must have a control_ip on a non-VLAN network which clients can establish connectivity with. It must also have a vlan_ip address on a VLAN network which clients will use to test their VLAN connectivity. Multiple clients may test against a single ovs-vlan-test server concurrently. OPTIONS
-s, --server Run in server mode. -h, --help Prints a brief help message to the console. -V, --version Prints version information to the console. EXAMPLES
Display the Linux kernel version and driver of eth1. uname -r ethtool -i eth1 Set up a bridge which forwards traffic originating from 1.2.3.4 out eth1 with VLAN tag 10. ovs-vsctl -- add-br vlan-br -- add-port vlan-br eth1 -- add-port vlan-br vlan-br-tag tag=10 -- set Interface vlan-br-tag type=internal ifconfig vlan-br-tag up 1.2.3.4 Run an ovs-vlan-test server listening for client control traffic on 172.16.0.142 port 8080 and VLAN traffic on the default port of 1.2.3.3. ovs-vlan-test -s 172.16.0.142:8080 1.2.3.3 Run an ovs-vlan-test client with a control server located at 172.16.0.142 port 8080 and a local VLAN ip of 1.2.3.4. ovs-vlan-test 172.16.0.142:8080 1.2.3.4 SEE ALSO ovs-vswitchd(8), ovs-ofctl(8), ovs-vsctl(8), ovs-test(8), ethtool(8), uname(1) Open vSwitch December 2010 ovs-vlan-test(1)
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy