Hi Denny,
Since I didn't see any other responses to you, I'll respond with my newly
gained perspective on VLAN-aware VSWITCHs. You may want to read my thread
"VSWITCH VLAN-aware not connecting" starting in May 2008, and continuing into
June. I think the definitions you've given us look correct, based on what I
know. But as you see from the other thread, my connections still aren't
working either. I wonder if you are experiencing the same thing I am.
Do this. Take some VM TRSOURCE traces. Here's the commands I'm using:
trso id trc1 type lan owner system lanname vsw20x vlan 304 (define the
trace)
trso disp (just to see that it is there)
trso en id trc1 (enable the trace)
Do a simple PING from your PC
trso disa id trc1 ("stop" the trace)
Then, the trace records should be in a TRF file in the spool.
q trf * (to get the spoolid number)
tracered -spoolid- cms trc1 trace (all
Then,
acc 592 t (TCPAMAINTs 592 disk)
ipformat trc1 trace
Look at the records in the IPFORMAT trace. Mine show that the "ping" (i.e. an
ECHO) are actually coming from my PC into VM, into my Linux guest, and the ECHO
REPLY is coming all the way back out. But, similar to you, it's not getting
out to the real network switch somehow. IBM hasn't been able to tell me why
it's not getting out, yet.
Cleanup:
trso drop id trc1
q trf *
I'll be eager to hear of your progress.
Dick Clapper
Systems Programmer
FirstBank Data Corporation
>>> "Burch, Aubrey Dennis CIV DISA GS4B" <[EMAIL PROTECTED]> 6/24/2008 1:44 PM
>>> >>>
Hello All
I'm attempting to connect a TCPIP stack and some LINUX guests to a
VSWITCH using 802.1Q trunking, and the network administrator sent me the
following VLAN info as he configured it on the real switch:
"Attached are the IP addresses you requested. I will put the trunk in
place on core switch 2 tonight. I will trunk VLANs 390, 391, 393 and
389(new vlan for this project). I will use a native vlan of 499. Will
that work for you?"
I tentatively told him I thought it was OK, but I have not found a way
to successfully configure the NATIVE VLAN (I *think* that's the
problem). It appears there is a way to do this with the NATIVE option on
the DEF VSWITCH command on z/VM 5.3, but I am at 5.2.
If I issue the following:
DEF VSWITCH VSW1 RDEV 9160 VLAN 499
SET VSWITCH VSW1 GRANT TCPIP VLAN 389
That combination allows me to ping the gateway on his switch, but I can
go no further out. I cannot get to my TCPIP stack from outside the
network either, as I expected. I have tried several permutations of
VLAN identifiers on the DEF VSWITCH command, and the only way to reach
the gateway is to use VLAN 499 or VLAN 1.
I have left VLAN 389 on the SET VSWITCH VSW1 GRANT command for TCPIP for
each attempt, as they requested the hosts go on VLAN 389.
Before I go back to the network guys, does anyone know of a way to
accommodate (on 5.2) the NATIVE VLAN configuration the network guy
specified above?
Thanks,
Denny Burch
z/VM and z/LINUX Systems
DISA DECC Mechanicsburg
717 605-1181
(dsn) 430-1181
>>>
The information contained in this electronic communication and any document
attached hereto or transmitted herewith is confidential and intended for the
exclusive use of the individual or entity named above. If the reader of this
message is not the intended recipient or the employee or agent responsible for
delivering it to the intended recipient, you are hereby notified that any
examination, use, dissemination, distribution or copying of this communication
or any part thereof is strictly prohibited. If you have received this
communication in error, please immediately notify the sender by reply e-mail
and destroy this communication. Thank you.
