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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT OPENSOLARIS
vlan
VLAN manipulation action in tc(8) Linux VLAN manipulation action in tc(8)
NAME
vlan - vlan manipulation module
SYNOPSIS
tc ... action vlan { pop | PUSH | MODIFY } [ CONTROL ]
PUSH := push [ protocol VLANPROTO ] [ priority VLANPRIO ] id VLANID
MODIFY := modify [ protocol VLANPROTO ] [ priority VLANPRIO ] id VLANID
CONTROL := { reclassify | pipe | drop | continue | pass | goto chain CHAIN_INDEX }
DESCRIPTION
The vlan action allows to perform 802.1Q en- or decapsulation on a packet, reflected by the operation modes POP, PUSH and MODIFY. The POP
mode is simple, as no further information is required to just drop the outer-most VLAN encapsulation. The PUSH and MODIFY modes require at
least a VLANID and allow to optionally choose the VLANPROTO to use.
OPTIONS
pop Decapsulation mode, no further arguments allowed.
push Encapsulation mode. Requires at least id option.
modify Replace mode. Existing 802.1Q tag is replaced. Requires at least id option.
id VLANID
Specify the VLAN ID to encapsulate into. VLANID is an unsigned 16bit integer, the format is detected automatically (e.g. prefix
with '0x' for hexadecimal interpretation, etc.).
protocol VLANPROTO
Choose the VLAN protocol to use. At the time of writing, the kernel accepts only 802.1Q or 802.1ad.
priority VLANPRIO
Choose the VLAN priority to use. Decimal number in range of 0-7.
CONTROL
How to continue after executing this action.
reclassify
Restarts classification by jumping back to the first filter attached to this action's parent.
pipe Continue with the next action, this is the default.
drop Packet will be dropped without running further actions.
continue
Continue classification with next filter in line.
pass Return to calling qdisc for packet processing. This ends the classification process.
EXAMPLES
The following example encapsulates incoming ICMP packets on eth0 from 10.0.0.2 into VLAN ID 123:
#tc qdisc add dev eth0 handle ffff: ingress
#tc filter add dev eth0 parent ffff: pref 11 protocol ip
u32 match ip protocol 1 0xff flowid 1:1
u32 match ip src 10.0.0.2 flowid 1:1
action vlan push id 123
Here is an example of the pop function: Incoming VLAN packets on eth0 are decapsulated and the classification process then restarted for
the plain packet:
#tc qdisc add dev eth0 handle ffff: ingress
#tc filter add dev $ETH parent ffff: pref 1 protocol 802.1Q
u32 match u32 0 0 flowid 1:1
action vlan pop reclassify
SEE ALSO
tc(8)
iproute2 12 Jan 2015 VLAN manipulation action in tc(8)