>One other thought - also make sure the VSWITCH controllers (DTCVSW1 &
; 2)
>are AUTOLOGed and given time to initialized before your Linux guests are
>AUTOLOGed.
Ok. . . . We're running z/VM on a trial basis for a proof of conncept, an
d
training has been minimal/neglected. So, I hate to ask t
>Does AUTOLOG1 GRANT authorization to your Linux guests prior to
>AUTOLOGing the Linux guests? If you have them out of order the behavior
>would be as you describe it. Obviously, the creation of the VSWITCH
>needs to be before the GRANTs, preferably in SYSTEM CONFIG rather than b
y
>AUTOLOG1
>I'm not sure what you mean here.. of course this should work regardles
s
>of how the guest is started - automatically or manually if things are
>setup correctly. Can you explain further?
I mean that when the LINUX guests start automatically when z/VM is IPL'ed
,
then they cannot connect to t
>FYI... Rule #2: Don't annoy Security People.
Clearly, at least to me NOW, I should have read the rules sooner.
In any case, we have it working. Thanks for everyone's support.
The answer(s) is/were to:
1) define the IP address we already had as the primary home address
2) define a vlink
3) add
Alan said:
>According to other parts of the query, your Linux guest has registered
>10.0.102.215 (Layer 3 VSWITCH), which looks fine based on your VM TCP/IP
>configuration (same subnet, no VLANs). I assume your Linux default
>gateway is also 10.0.102.4.
>Are you using a VIPA in Linux? I am worr
Alan said:
>When OSAs were first introduced it was true. It hasn't been true for
>many many years.
>Same goes for PORTNAME. Don't specify it in *any* Linux or z/VM
>configuration element. All that does is complicate matters.
Which all argues against relying on Redbooks as a dependable source o
>shouldn't there be a modify/grant statement in the SYSTEM CONFIG after
>the vswitch define ?
>MODIFY VSWITCH VM3SWTCH GRANT MLXESS1S
I mayt be wrong, but I believe this is covered by the commands in
AUTOLOG1's PROFILE:
'CP SET VSWITCH VSWITCH1 GRANT OZLXINIT'
'CP SET VSWITCH VSWITCH1 GRANT OZL
Hans said:
>Can you provide the LINUX IP configuration.
>Lastly, I believe this is not a problem as long as you use 3 consecutive
>addresses for your nic/OSA card but your skipped 703 OSA card address
I have to get the Linux config from the Linux guy.
Somewhere in the many documents I read abo
>You're specifying virtual 300, 301 and 302? What distro? What error are
>you getting?
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Kernel 2.6.18-92.el5 on an s390x
I am trying to get the actual error messages from the Linux guy.
>OK, that all looks good to me. What does a Linux guest report when you
>log it on; are there any CP error messages about coupling the NIC to the
>VSWITCH?
No errors that I see. The Linux admin simply says, "No connectivity to th
e
LAN. Lan is offline." - I'm trying to get the actual message tex
>What does "q vswitch details" show? Also, "q nic details" from each
guest?
q vswitch details
VSWITCH SYSTEM VSWITCH1 Type: VSWITCH Connected: 1Maxconn: INFINITE
PERSISTENT RESTRICTEDNONROUTER Accounting: OFF
We are attempting to configure a proof of concept z/VM and Linux
configuration, and I have spent several days futzing around with the
vswitch. It just plain does not work. Linux says the LAN is offline.
Maybe someone could be so kind as to point out the error of my ways?
Our real OSA address i
Can any VM systems programmers recommend a good training course for
seasoned mainframe sysprogs who are expanding into z/VM? The course I am
looking for should teach how to properly install, maintain, debug, tune,
expand, plan, etc. including network, security, operations, etc. for a
serious
>When a VM system has the PPRC secondaries online, a path group is formed
>with them. z/OS can't use them when this is the case.
So, it's the secondary volumes that cause the problem and not the primary
volumes?
>You just need to simply vary them offline from VM. Best to not include
>them in t
I am installing z/VM for the first time in many years. We currently have
a
z/OS sysplex and want to put z/VM on some of the same DASD.
I followed the initial install, creating the res, page, spool and work
volumes, then left the z/VM system up.
The next morning the storage admins complained
15 matches
Mail list logo
