z/VM: CP Commands and Utilities Reference - z/VM - IBM
27.12.2012 • Views
Share Embed Flag

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS
ePAPER READ
DOWNLOAD ePAPER
vm.ibm.com

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

START NOW

v The T<strong>CP</strong>/IP VSWITCH CONTROLLER statement is coded, <strong>and</strong> has<br />

defaulted to be ON or is explicitly set to ON in the T<strong>CP</strong>/IP configuration file<br />

or through an OBEYFILE comm<strong>and</strong>.<br />

v The stack has completed initialization.<br />

SET VSWITCH<br />

v The stack has virtual device addresses available for <strong>CP</strong> to attach the control<br />

device.<br />

The virtual address range used by <strong>CP</strong> is specified in the VSWITCH<br />

CONTROLLER T<strong>CP</strong>/IP configuration statement. If no VDEV range is<br />

specified, <strong>CP</strong> uses the virtual device address (vdev) that matches the rdev<br />

address specified on the DEFINE VSWITCH or SET VSWITCH comm<strong>and</strong>.<br />

See z/<strong>VM</strong>: T<strong>CP</strong>/IP Planning <strong>and</strong> Customization for more information about<br />

the VSWITCH CONTROLLER statement.<br />

Note: Do not code DEVICE <strong>and</strong> LINK T<strong>CP</strong>/IP configuration statements for<br />

the device. Do not attach the device to a T<strong>CP</strong>/IP controller virtual<br />

machine. These steps are h<strong>and</strong>led by DEFINE VSWITCH processing<br />

when a controller is selected.<br />

If an eligible stack is not found, or none of the rdevs are operational, you<br />

receive a message, <strong>and</strong> the virtual switch operates in a local LAN<br />

environment.<br />

2. Use the QUERY CONTROLLER comm<strong>and</strong> output to find the z/<strong>VM</strong> T<strong>CP</strong>/IP<br />

stacks that are the virtual switch controllers. Use the QUERY VSWITCH<br />

comm<strong>and</strong> to display information about virtual switches.<br />

3. <strong>CP</strong> manages the devices used to control a virtual switch’s connection to a real<br />

LAN segment through an OSA Express device. <strong>CP</strong> attaches the devices to the<br />

z/<strong>VM</strong> T<strong>CP</strong>/IP virtual machine. <strong>CP</strong> also defines a device of type VSWITCH-OSD<br />

to the z/<strong>VM</strong> T<strong>CP</strong>/IP stack, concatenating switchname with vdev <strong>and</strong> ″DEV″ to<br />

form the device name <strong>and</strong> switchname with vdev <strong>and</strong> ″LINK″ to form the link<br />

name. These names appear in the T<strong>CP</strong>/IP query <strong>and</strong> trace information. The<br />

status of a link that represents the active connection to a real LAN segment is<br />

Status: Ready. Status: Inactive is shown for any links defined for backup<br />

devices.<br />

DEVICE <strong>and</strong> LINK statements must not be included in the T<strong>CP</strong>/IP<br />

configuration file for these devices. Use the CONNECT <strong>and</strong> DISCONNECT<br />

oper<strong>and</strong>s to control whether the traffic flows through the OSA Express Adapter<br />

to a real LAN segment.<br />

If the OSA Express Adapter has been initialized, you must issue SET<br />

VSWITCH with the DISCONNECT oper<strong>and</strong> before changing PORTNAME, the<br />

currently active RDEV, or CONTROLLER. However, you can add or remove<br />

backup RDEVs while the virtual switch is connected.<br />

4. Multiple real devices <strong>and</strong> portnames can be specified on the RDEV <strong>and</strong><br />

PORTNAME parameters. If your OSA-Express device requires a portname,<br />

specify one portname for each real device number. This feature allows failover<br />

to an alternate real device in the event of a failure with the current<br />

OSA-Express device. All real devices specified must be active <strong>and</strong> connected<br />

in order to dynamically failover to an alternate device. In addition, the alternate<br />

devices must be defined on separate CHPIDs.<br />

5. When the real device identified by one of the rdevs is started, T<strong>CP</strong>/IP assigns<br />

the port name as the hardware adapter name. If an adapter name was already<br />

assigned by a previous connection, then the port name must be the same as<br />

assigned by any other connection in order to share the adapter. This includes<br />

sharing the OSA Express adapter with this logical partition or all other<br />

partitions.<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 1423

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!