SET VSWITCH

Grant and Portnumber Options

Uplink Options

Bridgeport Options

IVLPort Options

Notes:

¹ You can specify a maximum of 8 user IDs.
² You can specify a maximum of 3 port names.
³ You can specify a maximum of 3 real device numbers.
⁴ defState depends on whether a previous DEFINE VSWITCH or SET VSWITCH command explicitly set the BRIDGEPORT CONNECT or BRIDGEPORT DISCONNECT option. If neither was explicitly specified, the default is CONNECT.

Authorization

Privilege Class: B

Purpose

Use the SET VSWITCH command to set the attributes of an existing virtual switch.

Operands

switchname

is the name of the virtual switch to be set. The switchname is a single token (1–8 alphanumeric characters) that identifies the virtual switch. This virtual switch was created by a DEFINE VSWITCH command or statement in the System Configuration file.

GRANT userid

specifies the userid to be either added or modified in the access list for this virtual switch. This allows userid to connect an adapter to switchname. If an External Security Manager (ESM) is in control of the virtual switch, it may override the CP access list.

If the userid is not currently in the access list, it will be added with the specified network characteristics. Any network characteristics not specified will use the defaults from the virtual switch.

If the userid already exists in the access list, then only the network characteristics specified on this command will be changed.

The SET VSWITCH command with GRANT creates a z/VM® assigned port (in the range of 2176-4095 inclusive) representing the intended configuration if a port in this range does not already exist. The port defined by this command will persist until the VSWITCH is destroyed or the GRANT is removed by the SET VSWITCH command with the REVOKE option. If any ports are already configured for this user, update each port as specified by this new GRANT specification.

PORTType

defines the type of VSwitch connection to be used. If the GRANT or PORTNUMBER operand is being used to add a new user or port to the access list, and the virtual switch has been defined as VLAN aware and no PORTTYPE is specified on the GRANT or PORTNUMBER, the porttype assigned to the guest or port will be the default porttype as specified on the DEFINE VSWITCH command or statement.

If the GRANT or PORTNUMBER operand is issued for a user or port that has already been added to the access list, and the virtual switch has been defined as VLAN aware and no PORTTYPE is specified on the GRANT or PORTNUMBER, the current setting of porttype for the guest or port will be used. PORTTYPE TRUNK is not allowed for a TYPE IVL virtual switch.

PORTType ACCESS

defines the type of connections that are established to be an access port. The guest is unaware of VLAN IDs and sends and receives only untagged traffic.

PORTType TRUNK

defines the type of connections that are established to be a trunk port. The guest is VLAN aware and sends and receives only tagged traffic for those VLANs to which the guest is authorized. If the guest is also authorized for the natvid, untagged traffic sent or received by the guest is associated with the native VLAN ID of the virtual switch.

VLAN vidset

identifies the VLAN ID (or set of VLAN IDs) to which this user is restricted while connected to switchname. If VLAN is not specified, the default VLAN for this user is the default VLAN ID as specified on the DEFINE VSWITCH command or statement. Note that when a virtual switch is defined as VLAN AWARE, a default VLAN ID is not assigned. If a default VLAN ID is not assigned when the virtual switch is defined, then all inbound or outbound frames are discarded until a VLAN ID is assigned.

If VLAN is specified, each item in the vidset must be a valid VLAN number (between 1 and 4094, inclusive). The vidset may contain ranges:

Table 1. vidset Ranges
Examples:
VLAN 100-199 VLAN 100-199 1000-1099
VLAN 1 101-199
VLAN 1 101-199 4094
VLAN 1 2 3
VLAN 1 101 201 301

If an External Security Manager (ESM) is in control of the virtual switch, it can override the CP access list for a virtual switch.

PROmiscuous

specifies that the user ID or port is authorized for PROMISCUOUS Mode.

NOPROmiscuous

specifies that the user ID or port is NOT authorized for PROMISCUOUS Mode. This is the default setting when the GRANT or PORTNUMBER operand is being used to add a new user or port to the access list.

If an External Security Manager (ESM) is in control of the virtual switch, it may override the PROMISCUOUS authority.

PQUPLINKTX

specifies the priority for all packets sent from a virtual NIC's network connection to an external network. The PQUPLINKTX value will be used when priority queuing is enabled on the virtual switch (PRIQueuing ON). If PQUPLINKTX is configured for a virtual switch that does not have priority queuing enabled, the setting will be saved and used if priority queuing is enabled at a later time. If PQUPLINKTX is not specified, the default is that all outbound traffic to the external network will be sent at Normal priority. See PRIQueuing operand for additional information.

This option is not allowed for IVL virtual switches. For an IVL virtual switch, z/VM handles the priority of outbound transmissions.

Outbound traffic from the Hipersockets Bridgeport will be sent at Normal priority.

LOW: specifies that outbound traffic to the external network will be sent at a low priority. This traffic will use the low priority queue which is serviced less frequently than the normal or high priority queues.
NORMAL: specifies that outbound traffic to the external network will be sent at a normal priority. This traffic will use the normal priority queue which is serviced less frequently than the high priority queue but more frequently than the low priority queue.
HIGH: specifies that outbound traffic to the external network will be sent at a high priority. This traffic will use the high priority queue which is serviced more frequently than the normal or low priority queues.

REVOKE userid

specifies userid is removed from the CP access list for this virtual switch. This prevents user userid from connecting an adapter to virtual switch switchname. If an External Security Manager (ESM) is in control of the virtual switch, it may override the CP access list.

The REVOKE option removes configured ports belonging to userid whether they were configured by SET VSWITCH with GRANT, PORTNUMBER, or NICDEF.

Note: If the connection was authorized by the ESM and it needs to be permanently removed, the ESM database must also be updated. If authorized by NICDEF, the user directory must also be updated (to permanently remove access).

PORTNUMber userportnum USERID userid

The PORTNUMBER operand defines a port for a virtual switch and associates the specified user userid with a virtual switch port userportnum. This operand will also be used to specify port options including porttype, promiscuous, and VLAN ids. The userid will be added to the access list for this virtual switch. This allows userid to connect an adapter to userportnum on virtual switch switchname. If an External Security Manager (ESM) is in control of the virtual switch, the userid must be authorized by the ESM, and the VLANs configured with the SET VSWITCH PORTNUMBER command must be included in the VLAN list provided by the ESM. The valid range for user-defined ports is 1-2048.

This option is not allowed for a TYPE IVL virtual switch.

PORTNUMber MODIFY portnum

This operand is used to change the port options including porttype, promiscuous, and VLAN ids. The valid range is 1-4095 because the administrator can modify user-defined ports or ports allocated by z/VM.

This option is not allowed for a TYPE IVL virtual switch.

PORTNUMber REMOVE portnum

specifies the portnum to be removed from the virtual switch. Connections to this port are not allowed unless the port is again added to the virtual switch. Existing connections to this port on the virtual switch will be uncoupled. If the userid associated with this port does not have any other ports defined on this virtual switch, this will also revoke virtual switch access for the userid. The valid range is 1-4095 because the administrator can remove user-defined ports or ports allocated by z/VM.

This option is not allowed for a TYPE IVL virtual switch.

VLANID vlanid ADD portset

The ADD operand adds the port set to the specified virtual lan segment. The vlanid must be a valid VLAN number (between 1 and 4094, inclusive). Each item in the portset must be a valid port number (between 1 and 4095, inclusive). Each port must be defined with SET VSWITCH PORTNUMBER, SET VSWITCH GRANT, or NICDEF before being added to a VLAN. The portset may contain ranges:

Table 2. portset Ranges
Examples:
1-25
1 25-50
1 25-50 2048
1 2 3
1 101 201 301

Existing connections will be updated.

This option is not allowed for a TYPE IVL virtual switch.

If an External Security Manager (ESM) is in control of the virtual switch, the VLAN ids defined with VLANID command must be included in the VLAN list provided by the ESM.

VLANID vlanid REMOVE portset

The REMOVE operand removes the ports listed from the specified virtual lan segment. The vlanid must be a valid VLAN number (between 1 and 4094, inclusive). Each item in the portset must be a valid port number (between 1 and 4095, inclusive). The portset may contain ranges. See Table 2. Existing connections will be updated. When the last port number is removed from the VLAN, the VLAN is deleted.

This option is not allowed for a TYPE IVL virtual switch.

VLANID DELETE vlanid

The DELETE operand deletes the VLAN vlanid from the specified virtual switch. The vlanid must be a valid VLAN number (between 1 and 4094, inclusive). The VLAN will be removed from all ports. Existing connections will be updated.

This option is not allowed for a TYPE IVL virtual switch.

UPLINK

enables and specifies connectivity for a virtual switch UPLINK port. The UPLINK port is a special port that typically is used to connect the virtual switch to a physical switch -- essentially bridging the virtual switch's simulated network to a physical network.

CONnect

indicates that the currently configured virtual switch UPLINK port must be activated, and traffic may flow through the devices associated with the specified UPLINK ports device(s). For the case when a virtual switch has been defined with the NOUPLINK operand, the CONNECT is not performed. If an error occurs with one of the backup devices, issue the SET VSWITCH switchname CONNECT command to refresh the backup device once the problem is corrected.

DISCONnect

indicates that the currently configured virtual switch UPLINK port must not be activated, and that no traffic is to flow through the devices associated with the specified UPLINK ports device(s).

A virtual switch can be functional without a connection to a real LAN segment, and traffic flows only between virtual machines coupled to the virtual switch.

RDEV nnnn

RDEV nnnn.Pn

is a real device number or a real device number and OSA-Express port number to be used as an UPLINK to connect the virtual switch to a OSA-Express device. The device selected must be compatible to the type of virtual switch created. Specify each real device number as a hexadecimal number between X'0001' and X'FFFD'. If specifying a real device and an OSA-Express port number, specify the real device number as a hexadecimal number between X'0001' and X'FFFD' followed by a period (.), the letter 'P' or ('p') followed by the port number as a hexadecimal number between X'0' and X'F'. For example, to specify port 1 for RDEV 300, specify 300.P1. The value of the port number depends on how many ports the OSA-Express hardware adapter supports. If the port number is not specified, it will default to port 0.

You can specify a maximum of three real device numbers. If you specify more than one device number, each must be separated from the others by at least one blank. When the virtual switch has been defined with the GROUP attribute, any devices identified by the RDEV keyword are used for failover in the event of a real switch failure of the link aggregation group. Failover in this environment will be to a single OSA-Express device connected to a second real switch.

Each real device number represents a trio of devices. For example, specifying RDEV 111 222 333 means that the first devices, 111-113, are used to provide the connection to the real hardware LAN segment. When issuing the VSWITCH command without the GROUP attribute, if there is a problem with the connection, devices 222-224 are used next to provide the connection, and if those devices fail to connect, devices 333-335 are used. This feature provides dynamic recovery for OSA-Express device failures when issuing the VSWITCH command without the GROUP attribute or for real switch failure when issuing the VSWITCH command with the GROUP attribute. (Failure of an OSA in an aggregated group is automatically handled by the virtual switch; that is, the virtual switch will transfer the data flow to the remaining OSAs in the group.)

RDEV NONE means that the virtual switch should not be connected to the real LAN segment when defined with NOGROUP. When the virtual switch has been defined with GROUP, RDEV NONE means that there is no link aggregation group failover in the event the real switch should fail.

The number of devices identified by the RDEV keyword combined with the number of devices in an associated GROUP may not exceed eight devices.

The RDEV operand may not be used to specify device numbers when the virtual switch is configured to use a shared port group. MAC address takeover is managed by the shared port group to maintain connectivity following a failure.

GROup groupname

NOGroup

GROUP indicates that the virtual switch is to be configured to use IEEE 802.3ad Link Aggregation. The groupname is a single token (1-8 alphanumeric characters) that identifies the group. Use the SET PORT GROUP command to specify the attributes of the group and the OSA-Express devices that will comprise the group. This option can be specified only when the virtual switch has been defined with the ETHERNET transport attribute. NOGROUP means that the virtual switch will not use Link Aggregation.

The GROUP or NOGROUP operands can be used only when the virtual switch is in the DISCONNECT state. If a group already has been associated with a virtual switch and you wish to change to a different group, first issue SET VSWITCH with the NOGROUP operand, followed by SET VSWITCH with a GROUP operand that specifies the new groupname. The port group must be defined using the SET PORT GROUP command before it can be associated with a GLOBAL virtual switch. For a LOCAL virtual switch, if the group specified has not been defined, it will be created with this command.

NIC

causes the UPLINK port for a virtual switch to be connected to, or disconnect from, a virtual switch guest port. The NIC operand can be specified only when a virtual switch is in the DISCONNECT state. Setting the UPLINK port to a guest port also will set RDEV NONE and NOGROUP. Changing either of the RDEV or GROUP settings causes UPLINK NIC NONE to be set.

This option is not allowed for a TYPE IVL virtual switch.

userid2 vdev (AUTO/portnum)

specifies that the UPLINK port is to be connected to a guest port, and that the virtual switch is not to be connected to a physical switch. In this configuration the virtual switch routes all broadcasts and destination MAC or IP Address unicast frames that cannot be resolved within the simulated LAN segment to the specified guest port. If your virtual switch is VLAN AWARE, the guest port should be configured as a TRUNK port.

AUTO indicates that the CP determines the virtual switch port number to be used.
If a single user port was defined for this user by the SET VSWITCH command, then that port will be automatically used by COUPLE or CONNECT, and its port settings will be used. If there are multiple user ports defined, then the CONNECT or COUPLE command will fail.
portnum
The guest portnum may be specified. When the uplink NIC is COUPLED or CONNECTED, it is connected to the specified portnum on the virtual switch. The portnumber must be a valid user-defined port number (between 1 and 2048, inclusive), and must be configured with the SET VSWITCH PORTNUMBER command. If the portnum is not a configured port, then the COUPLE or CONNECT command will fail.

NONE

disconnects the currently connected guest port from the special virtual switch UPLINK port. Until another UPLINK port is specified, all destination MAC or IP address unicast frames that cannot be resolved within the simulated LAN segment are discarded

PATHMTUDiscovery

indicates that CP will, by default, participate in the Path MTU Discovery process in order to minimize packet loss and to maximize the size of packets sent through a defined UPLINK RDEV port device. The Path MTU Discovery process performed by CP examines and discards any IP datagrams destined for the UPLINK port that are larger than the Path MTU Discovery value allowed by the UPLINK RDEV port device. CP also sends to the datagram source an appropriate notification in the form of an ICMP or ICMPv6 message.

The SET VSWITCH PATHMTUDISCOVERY option can be used to configure a user-defined Path MTU Discovery value, to indicate that CP should determine the Path MTU Discovery value (the default), or to indicate to CP that the Path MTU Discovery process is to be disabled.

These options are specified as follows:

EXTernal

indicates that CP should determine the Path MTU Discovery value to assign. The value to be assigned is determined as follows:

If the virtual switch is configured with an active UPLINK RDEV port, CP determines the Path MTU Discovery value to use from the maximum MTU value supported by the connected OSA UPLINK RDEV port device. Typically, this value is 8992 bytes.
If the virtual switch is configured with one or more UPLINK RDEV ports but none are currently active, CP disables the Path MTU Discovery process, effectively the same as specifying the SET VSWITCH PATHMTUDISCOVERY OFF option. Later, when one of the UPLINK RDEV port devices is activated, CP determines the Path MTU Discovery value to use based on the maximum MTU value supported by the active OSA UPLINK RDEV port device. Typically, this value is 8992 bytes.
If the virtual switch is configured without an UPLINK RDEV port device, CP disables the Path MTU Discovery process, effectively the same as specifying the SET VSWITCH PATHMTUDISCOVERY OFF option. Later, when the UPLINK RDEV port device is defined and activated for the virtual switch, CP determines the Path MTU Discovery value to use based on the maximum MTU value supported by the active OSA UPLINK RDEV port device. Typically, this value is 8992 bytes.

PATHMTUDISCOVERY EXTERNAL is the default setting for the virtual switch.

VALue nnnnn

configures a user-defined value of nnnnn bytes to be used by CP as the Path MTU Discovery value. Specifying this option can be useful if the PATHMTUDISCOVERY value of the physical network needs to be different from the PATHMTUDISCOVERY value used by CP when SET VSWITCH PATHMTUDISCOVERY EXTERNAL is specified. To determine the recommended PATHMTUDISCOVERY value, refer to the Maximum Transmission Unit (MTU) information in the hardware documentation associated with the OSA UPLINK RDEV port device. nnnnn is a number from 512 to 65535.

OFF

indicates that the Path MTU Discovery process for this virtual switch is to be disabled by CP. This setting is not recommended when the virtual switch is defined with a Bridge Port.

SWITCHOVER

initiate a controlled port change or failover from the currently active OSA port to another configured backup port with minimal network disruption. Although the network connection is quickly terminated, it is still possible that data in transit may be lost, causing some additional network recovery actions to occur.

This command is not valid for a link aggregation or GROUP configured uplink port. To remove a port from a link aggregation group, use the SET PORT GROUP LEAVE command.

AVAILABLE: Switch to one of the available configured backup uplink devices configured on the virtual switch. The first available port in which a new network connection can be established will become the active uplink port. If none of the configured backup ports can establish an active network connection, then a network connection will be established back on the original device.
RDEV nnnn.Pn: Attempt to switch to the specified configured backup device. The RDEV and OSA-Express port number specified must already be configured as a backup device with the SET VSWITCH UPLINK RDEV command. Specify the real device number as a hexadecimal number between X'0001' and X'FFFD' followed by a period (.), the letter 'P' or ('p') followed by the port number as a hexadecimal number between X'0' and X'F'. When a port number is not specified using (.Pn), then port number zero will be used.
If for any reason a network connection cannot be established on the specified RDEV, the network connection will be reestablished backed on the original uplink port.

PRIQueuing

enables or disables guest priority queuing support on all outbound data transmissions from the virtual switch uplink port to an external network. Priority queuing is a capability of the OSA-Express feature where multiple output queues are defined for a single network connection with each queue weighed by a priority on how often it gets serviced by the OSA-Express feature. The highest priority queue is serviced first and more often followed by the next highest priority and so on. No queue is starved and all will get serviced at some point by the OSA-Express feature. See Virtual Switch Priority Queuing Function in z/VM: Connectivity for more information on virtual switch exploitation of priority queuing.

If PRIQueuing is to be enabled on a virtual switch, then the OSA-Express features configured to the virtual switch's uplink port must be configured by IOCP to enable the feature within the adapter (PQ_ON). (See DEFINE CHPID / PATH for more information.

OFF

The virtual switch will not exploit priority queuing. A single input queue is established for inbound transmissions from the external network and a single output queue is established for outbound transmissions. All outbound data to the external network is transmitted with equal priority. This is the default for TYPE QDIO virtual switches.

The OFF option is not allowed for a TYPE IVL virtual switch.

ON

The virtual switch will exploit priority queuing. If the customer configured the OSA-Express features used by a virtual switch uplink port for priority queuing via IOCP (PQ_ON), then z/VM will establish one input queue and four output queues when activating its network connection. This will allow z/VM to transmit data to the external network at four different priorities. CP will use the highest priority queue for control and management traffic. The other three queues (low, normal and high) can be used for virtual NIC's network connections. This is the default for TYPE IVL virtual switches.

For an IVL virtual switch, z/VM will attempt to establish an active network connection with the first OSA device specified. For migration reasons, if the OSA-Express features (used by the IVL virtual switch uplink port) are configured without priority queuing (PQ_OFF), z/VM will establish an active network connection, and force priority queuing off. A warning message will be displayed to inform the customer to configure priority queuing via IOCP.

If the OSA-Express features used by a non-IVL virtual switch uplink port are configured without priority queuing (PQ_OFF), z/VM will NOT establish an active network connection, and an error message will be displayed.

The policy used to select which priority a specific datagram is transmitted to the external network is determined by the type of virtual switch.

For an IVL virtual switch, the priority of outbound transmissions is handled by z/VM. IVL management traffic will be queued and transmitted on a high priority queue, and encapsulated production data failover traffic will be sent on a lower priority queue. The default for TYPE IVL virtual switches is PRIQUEUING ON, given priority queuing of both management and encapsulated production data is required to maintain a viable IVL network. Only an OSA-Express feature configured for priority queuing should be used on an IVL virtual switch's uplink port.

For all other virtual switch types, the priority can be set to low, normal or high for all packets sent from a guest NIC's network connection to an external network via the SET VSWITCH command. See the PQUPLINKTX operand on SET VSWITCH for more information.

The PRIQueuing operand can be specified only when virtual switch's uplink port is in the DISCONNECT state.

TRACEsize nnnn

specifies the number of pages to be allocated for an internal trace table to keep track of trace events pertaining to this UPLINK port. The allowable range is 0 to 4095. The default value is 8 pages in order to increase the chance of capturing sufficient documentation in the event of a virtual switch problem. Increasing the page size allows a greater history of traces to be obtained when gathering documentation to assist IBM® in diagnosing an UPLINK related problem. Setting a value of 0 turns off this data capture function.

BRIDGEport

enables and specifies connectivity for a virtual switch Bridge Port. The Bridge Port is a special port that is used to connect the virtual switch to a HiperSockets CHPID, essentially bridging the HiperSockets CHPID to the virtual switch's simulated and physical networks.

Configuring a virtual switch Bridge Port is only supported when the Bridge facility is supported by the processor, the virtual switch transport type is ETHERNET, the virtual switch TYPE is QDIO and the ISOLATION and VEPA modes are OFF.

Only guest operating systems running in a virtual machine under z/VM and exploiting QDIO Enhanced Buffer State Management QEBSM) are eligible to be bridged from the HiperSockets CHPID to the virtual switch's simulated and physical networks.

RDEV nnnn

is a real device to be used as a Bridge Port to connect the virtual switch to a HiperSockets CHPID. Only devices that have been configured with the HiperSockets CHPID parameters EXTERNAL_BRIDGED, can be specified. The RDEV operand can be specified only when the Bridge Port is in the DISCONNECT state.

The device selected must be compatible to the type of virtual switch created; that is, EXTERNAL_BRIDGED for a QDIO type virtual switch. Connectivity to the HiperSockets CHPID will be prevented when the specified device does not match the virtual switch's type.

Specify a single real device number as a hexadecimal number between X'0001' and X'FFFD'. The real device number specified represents a trio of devices. For example, specifying BRIDGEPORT RDEV 508 means the devices 508-50A are used to provide the connection to the HiperSockets CHPID.

NONE

specifies that the virtual switch does not have a Bridge Port. If a Bridge Port was previously defined, it must be in the DISCONNECT state in order to be removed.

CONnect

indicates that the device identified by the RDEV keyword will be immediately activated, allowing the connection to be used as the active or standby Bridge Port.

DISCONnect

indicates that the device identified by the RDEV keyword will be placed in the inactive state. If this connection is the active Bridge Port connection, another virtual switch with a Bridge Port on the same CHPID in standby state will take over the active Bridge Port connection.

SECONDARY

indicates that this virtual switch should be assigned a role as a SECONDARY Bridge Port for the HiperSockets CHPID. The SECONDARY operand can be specified only when the Bridge Port is in the DISCONNECT state. See the DEFINE VSWITCH usage note 17 for more information about the SECONDARY Bridge Port role.

PRIMARY

indicates that this virtual switch must be assigned the role as the PRIMARY Bridge Port for the HiperSockets CHPID. The PRIMARY operand can be specified only when the Bridge Port is in the DISCONNECT state. See the DEFINE VSWITCH usage note 17 for more information about the PRIMARY Bridge Port role.

BUFFERS nnnnn

indicates the maximum number of asynchronous requests that are allowed to be outstanding on the Bridge Port. The allowable range is 0 to 65535. The default value is 2048.

RESET

is intended for diagnostic purposes when directed by IBM to synchronize the virtual switch and HiperSockets bridge communications. This RESET operand can be specified only when the Bridge Port is in CONNECT state and is the active Bridge Port connection.

TRACEsize nnnn

specifies the number of pages to be allocated for an internal trace table to keep track of trace events pertaining to this Bridge Port. The allowable range is 0 to 4095. The default value is 8 pages in order to increase the chance of capturing sufficient documentation in the event of a virtual switch problem. Increasing the page size allows a greater history of traces to be obtained when gathering documentation to assist IBM in diagnosing a Bridge Port related problem. Setting a value of 0 turns off this data capture function.

NICDistribution

specifies how Ethernet frames flow from HiperSockets bridge capable ports on the HiperSockets CHPID into the virtual switch uplink or other simulated guests that are coupled to the virtual switch.

OFF: The virtual switch does not examine each Ethernet frame to identify the HiperSockets guest port that sent the frame. The virtual switch distributes all Ethernet frames from the HiperSockets CHPID as a single source. OFF is the default setting if you do not specify the NICDISTRIBUTION parameter.
ON: The virtual switch examines each Ethernet frame to identify the HiperSockets guest port that sent the frame. The virtual switch uses the HiperSockets guest port information to distribute the frames among the virtual switch uplinks or other simulated guests that are coupled to the virtual switch. The information is used to balance the load, especially when links are in a link-aggregation port group configuration and when most guests are on the HiperSockets CHPID.
When NICDISTRIBUTION is ON, additional information that is related to the HiperSockets guest ports is displayed by the QUERY VSWITCH command, in monitor records, and by Diagnose x'26C'. For example, packet counters and IP addresses of the guests are displayed. For more information, see QUERY VSWITCH.

CONTroller * | userid1

identifies the z/VMz/VM user ID that controls the OSA-Express device connected to the virtual switch. You can specify a maximum of eight user IDs. If you specify more than one user ID, each must be separated from the others by a least one blank. CONTROLLER * means CP selects from any of the eligible z/VM TCP/IP stacks. See usage note 1 for more information about the function of a controller.

If you specify multiple real devices on the RDEV keyword or through the GROUP keyword, then specify CONTROLLER * or allow it to default or specify a list of user IDs. The controller functions are then spread across multiple z/VM TCP/IP stacks, providing more flexibility in case of a failure. You can also specify a pool of specific controllers to be chosen from by specifying a list of user IDs after the CONTROLLER keyword with the SET VSWITCH command or the MODIFY VSWITCH statement.

MACPRotect

turn on or off MAC address protection for devices coupled to this virtual switch. Turning MAC address protection on prevents a guest from using a MAC address that is not assigned to the user's network device. MACPROTECT is valid only for an ETHERNET virtual switch. MAC address protection is not supported for guest ports that are being bridged by this virtual switch.

There are three levels of inheritance used when determining the MAC address protection level for a MAC address assigned to a network device. The highest is the system level, followed by the virtual switch (or guest LAN) level. The lowest level is the protection set for a specific network data device.

The MAC address protection level assigned is determined first at the device, then virtual switch and lastly the system level. If MAC address protection is set at the device level using the SET NIC CP Command, then its current setting is used. When the device is set to UNSPECIFIED, it will inherit the MACPROTECT setting of the virtual switch. When the virtual switch MACPROTECT setting is set to UNSPECIFIED, the SYSTEM's MAC address protection specified by the SET VMLAN CP command or VMLAN configuration statement is assigned.

UNSPECified: allow the MAC address protection to be determined by the SYSTEM level setting. UNSPECIFIED is the default setting for a virtual switch.
If MAC address protection is set to UNSPECIFIED by the SET NIC CP command for a specific device, then the device's MAC address protection will be set to the SYSTEM level defined by the SET VMLAN CP command or the VMLAN configuration statement.
OFF: set the MAC address protection level off for coupled devices defined with a MAC address protection set to UNSPECIFIED.
If MAC address protection is set to UNSPECIFIED by the SET NIC CP command for a specific device, then the device's MAC address protection will be set off.
ON: set the MAC address protection level on for coupled devices defined with a MAC address protection set to UNSPECIFIED.
If MAC address protection is set to UNSPECIFIED by the SET NIC CP command for a specific device, then the device's MAC address protection will be set on.

MACID macid

is a unique identifier (up to six hexadecimal digits) used as part of the virtual switch MAC address. This MACID (three bytes) is appended to the system MACPREFIX (three bytes) or USERPREFIX (three bytes) to form a unique MAC address for this virtual switch. If a specified MACID is already in use, the virtual switch is not changed. You must eliminate the conflict or select a different MACID. If no MACID is set for the virtual switch, CP generates a unique identifier for this virtual switch. Also, specifying SET VSWITCH MACID without macid changes the MACID from the user-specified value to a system-generated value.

Note: The MAC address is used in LACP (Link Aggregation Control Protocol). It is necessary for proper operation of a virtual switch defined with the GROUP operand. The MAC address is also used when a z/VM TCP/IP stack is providing management services for a virtual switch, such as acting as an SNMP agent reporting bridge MIB information.

VEPA

determines the operational mode of the virtual switch with regard to forwarding guest-to-guest and guest-to-external destination communications.

OFF

allows guest ports to communicate with each other and with any hosts and/or LPARs that share the same OSA port. VEPA OFF is the default setting for a QDIO virtual switch.

ON

prohibits guests from sending traffic to other guests on the same virtual switch without going through an external entity by forwarding all traffic from the guest through the OSA uplink to an adjacent switch. In addition, no direct LPAR communications sharing the same OSA port is permitted with the guest ports of the virtual switch. All traffic from the virtual switch destined for any sharing hosts/LPARs on the same OSA port will be forwarded as well. Any traffic destined for the virtual switch guest ports from hosts/LPARs sharing the same OSA port will also be forwarded to the adjacent switch. VEPA ON requires an ETHERNET virtual switch (without a Bridge Port) with OSA uplink(s) that supports VEPA as well as the partner switch must support Reflective Relay.

VEPA ON may not be specified if ISOLATION is ON.

VEPA ON may not be specified for a GLOBAL virtual switch.

ISOLation

determines if guests on the virtual switch can communicate between themselves and other hosts and/or LPARs that share the same OSA-Express port with the virtual switch. ISOLATION OFF is set by default for all other virtual switch types to allow unrestricted network communications. ISOLATION is not supported for a virtual switch that has a Bridge Port.

OFF: allows guest ports to communicate with each other and with any hosts and/or LPARs that share the same OSA port.

ON

prohibits guests from sending traffic to other guests on the same virtual switch by discarding traffic that is destined for another guest port on the virtual switch. In addition, no direct LPAR communications sharing the same OSA port is permitted with the guest ports of the virtual switch. All traffic from the virtual switch destined for any sharing hosts/LPARs on the same OSA port will be dropped. Any traffic destined for the virtual switch guest ports from hosts/LPARs sharing the same OSA port will also be dropped.

ISOLATION ON may not be specified if VEPA is ON.

ISOLATION ON may not be specified for a GLOBAL virtual switch.

IPTimeout nnn

indicates the length of time in minutes that a remote IP address table entry remains in the IP address table for the virtual switch.

nnn is a number from 1 to 240.

VLAN_counters

indicates the level of detail that should be maintained for the virtual switch network activity.

OFF: indicates that the detailed VLAN counters are not needed. That is, the system should stop keeping counters at the VLAN level, and begin keeping transmission counters only at the port level. Packet counters are kept for each port to show the number of frames received, transmitted or discarded. VLAN_counters OFF is the default.
ON: indicates that the system should begin keeping transmission counters at the VLAN level. That is, for each port, packet counters are maintained to show the number of frames received, transmitted or discarded for each VLAN. See Virtual Switch Configuration Strategy with VLAN in z/VM: Connectivity for guidance on selecting VLAN IDs to maximize performance.

COUNTERS CLEAR [UPLINK|BRIDGEport] [ALL|DATA|DISCARDed|ERRORs]

resets counts for the virtual switch.

UPLINK: resets counts for the uplink port.
BRIDGEport: resets counts for the bridge port.
ALL: resets discarded, error and data counts for the specified port.
DATA: resets data counts for the specified port. Data counts include transmitted packets, transmitted bytes, received packets and received bytes.
DISCARDed: resets discarded counts for the specified port.
ERRORs: resets error counts for the specified port.

QUEuestorage numberM

indicates the upper limit of the amount of fixed storage CP and Queued Direct I/O Hardware Facility will use for buffers for each OSA-Express data device.

number defines the maximum number of megabytes of storage that can be consumed for QDIO queues on a single OSA port. When multiple OSA devices are defined in a link aggregation group, then each OSA port within the group will use the specified amount of storage. Fixed storage is allocated as needed based on network traffic, until the maximum of numberM are allocated.

number is a number from 1 to 8. 8M is the default value.

GVRP

specifies that the VLAN IDs in use on the virtual switch should be registered with GVRP-aware switches on the LAN. This allows offloading of VLAN filtering to the switch from the z/VM Control Program (CP).

NOGVRP

Do not register VLAN IDs with GVRP-aware switches on the LAN.

NONrouter

indicates that the OSA-Express device identified by the RDEV keyword will not act as a router to the virtual switch. If a datagram is received at this device for an unknown IP address, the datagram will be discarded. This is the default.

NONrouter is valid only for an IP virtual switch.

PRIrouter

indicates that the OA Express device identified by the RDEV keyword will act as a primary router to the virtual switch. If a datagram is received at this device for an unknown IP address, the datagram will be passed to the virtual switch.

PRIrouter is valid only for an IP virtual switch.

PORTname portname

is a 1- to 8-character name that identifies the OSA-Express adapter. You can specify a maximum of three port names. Multiple port names are used when different port names are needed for the multiple rdevs specified on the RDEV operand. See usage note 5 for more information.

Note: The PORTNAME operand is ignored when the GROUP operand is used.

IVLPORT

specifies operations that are allowed only for an IVL-type virtual switch. An IVL virtual switch is a special type of virtual switch that provides communication infrastructure to exchange control information and data necessary to manage global networking objects that can span multiple systems running z/VM.

VLAN IVL_vlanid

provides the system administrator with a way to change the VLAN ID associated with the IVL port on an IVL virtual switch that is VLAN AWARE. This changes the default VLAN ID assigned when the IVL virtual switch was created. It is a number between 1 and 4094.

PING [MAC | SYStem | ALL]

tests connectivity with another system running z/VM, to determine if it is a member of the same IVL domain.

SYStem IVLsystemnm

IVLsystemnm is the 8 byte EBCDIC z/VM system identifier of the remote system running z/VM as specified in the system configuration file.

MAC IVLsystemMAC

IVLsystemMAC can be a unicast or multicast MAC address. A MAC address can be entered using any one of the following MAC notations:

Twelve contiguous hex character: 02A000123456
Greater than twelve but no more than eighteen hex characters delineated by any non-space character. This permits both standard and even nonstandard MAC address notations to be entered as shown.
- 02-A0-00-12-34-56
- 02:A0:00:12:34:56
- 02A000-123456

ALL

use ALL to send a ping to the IVL domain multicast MAC address which will check connectivity with all members of the IVL domain.

Use QUERY VMLAN to display the members of the IVL domain along with the IVLsystemMAC for each.

HEARTbeat TIMEout seconds

changes the length of time that is allowed to expire before the local system declares a communication problem with another system in the IVL domain if heartbeat signals are missing. Every 5 seconds, each system in the IVL domain broadcasts a signal to confirm current communication with all IVL domain members.

The default HEARTBEAT TIMEOUT is 30 seconds.

The allowable range is 10 to 3600 seconds.

RESET

is intended to be used for diagnostic purposes when directed by IBM. The RESET operand:

terminates and then recreates the IVL virtual switch's connection, forcing the system to serialize itself with all other members of the IVL domain.
disconnects and immediately reconnects the IVL virtual switch UPLINK port.

Usage Notes

A virtual switch's connection to a real hardware LAN segment is not operational until an eligible z/VM TCP/IP stack is selected to be the controller for the OSA-Express device. CP selects an eligible z/VM TCP/IP stack to be the controller by either:
- It is recommended that the VSWITCH controller be at the same release level as CP, although all supported releases are allowed.
- If CONTROLLER userid1 is specified on the DEFINE or SET VSWITCH commands or the DEFINE or MODIFY VSWITCH system configuration statements, with either a single user ID or a list of user IDs, only those user IDs are selected.
- If CONTROLLER * is specified or allowed to default, CP selects from any eligible z/VM TCP/IP stacks.
A z/VM TCP/IP stack becomes eligible when:
- The TCP/IP MODULE running in the controller is at a release level that supports the function required for the virtual switch.
- An IUCV *VSWITCH statement is included in its CP directory entry.
- The TCP/IP VSWITCH CONTROLLER statement is coded, and has defaulted to be ON or is explicitly set to ON in the TCP/IP configuration file or through an OBEYFILE command.
- The stack has completed initialization.
- The stack has virtual device numbers available for CP to attach the control device.
  The virtual device range used by CP is specified in the VSWITCH CONTROLLER TCP/IP configuration statement. If no VDEV range is specified, CP uses the virtual device number (vdev) that matches the rdev number specified on the DEFINE VSWITCH or SET VSWITCH command. See z/VM: TCP/IP Planning and Customization for more information about the VSWITCH CONTROLLER Statement.
  Note: Do not code DEVICE and LINK TCP/IP configuration statements for the device. Do not attach the device to a TCP/IP controller virtual machine. These steps are handled by DEFINE VSWITCH processing when a controller is selected.
If an eligible stack is not found, or none of the rdevs are operational, you receive a message, and the virtual switch operates in a local LAN environment.
Use the QUERY CONTROLLER command output to find the z/VM TCP/IP stacks that are the virtual switch controllers. Use the QUERY VSWITCH command to display information about virtual switch.
CP manages the devices used to control a virtual switch's connection to a real LAN segment through an OSA-Express device. CP attaches the devices to the z/VM TCP/IP virtual machine. CP also defines a device of type VSWITCH-OSD to the z/VM TCP/IP stack, concatenating switchname with vdev and "DEV" to form the device name and switchname with vdev and "LINK" to form the link names. These names appear in the TCP/IP query and trace information. The status of a link that represents the active connection to a real LAN segment is Status: Ready. Status: Inactive is shown for any links defined for backup devices.
DEVICE and LINK statements must not be included in the TCP/IP configuration file for these devices. Use the CONNECT and DISCONNECT operands to control whether the traffic flows through the OSA-Express Adapter to a real LAN segment.

If the OSA-Express Adapter has been initialized, you must issue SET VSWITCH with the DISCONNECT option before the PORTNAME, CONTROLLER, NONROUTER, PRIROUTER, GVRP, VEPA, PRIQUEUING, or the currently active UPLINK port values can be changed. However, you can add or remove backup RDEVs while the virtual switch is connected.
Multiple real devices and portnames can be specified on the RDEV and PORTNAME parameters. If your OSA-Express device requires a portname, specify one portname for each real device number. This feature allows failover to an alternate real device in the event of a failure with the current OSA-Express device or link aggregation group. All real devices specified must be active and connected in order to dynamically failover to an alternate device. In addition, the alternate devices must be defined on separate CHPIDs.
When the real device identified by one of the rdevs is started on a VSWITCH command with the NOGROUP attribute, TCP/IP assigns the port name as the hardware adapter name. If an adapter name was already assigned by a previous connection, then the port name must be the same as assigned by any other connection in order to share the adapter. This includes sharing the OSA-Express adapter with this logical partition or all other partitions.
The PORTNAME operand is optional. However, some levels of the OSA-Express adapters require that the PORTNAME operand is specified. When such an adapter is in use and the PORTNAME operand is omitted, an error message is displayed during switch initialization.

If the device is already started, you must stop it by issuing the SET VSWITCH switchname DISCONNECT command before changing the port name.
VLAN configuration information can be found in Planning for Guest LANs and Virtual Switches in z/VM: Connectivity.
PRIROUTER is required only when IP forwarding (routing) nodes will be coupled to the switch. Router nodes provide connectivity for their LAN segments (remote nodes) through their switch connection. When Router nodes are deployed, their switch connection must be configured as PRIROUTER. In addition to this, the switch itself must also be configured as PRIROUTER to the OSA-E adapter. This will insure delivery of datagrams destined for LAN segments that are connected through routers coupled to a switch. Only one connection on each OSA-Express card can be designated as PRIROUTER. If the switch is successful in establishing PRIROUTER on the OSA-Express card, no other node (or switch) sharing the same OSA-Express card will be able to act as PRIROUTER. If another connection has already been established as PRIROUTER, the switch will be left with NONROUTER status (which is reflected in the QUERY VSWITCH response).
NONROUTER is the default mode for the switch. Every node is directly coupled to the switch and the associated IP destinations are registered with the OSA-Express connection. This is the most efficient way to use the virtual switch. In this mode, packets with an unrecognized IP destination are automatically sent out through the switch connection.
If the virtual switch has a guest port for the UPLINK port (UPLINK NIC userid2 vdev), the PRIROUTER and NONROUTER options are ignored.
If the virtual switch has been defined as VLAN UNAWARE, the following are not allowed:
- the PORTTYPE and VLAN option on GRANT
- the PORTTYPE and VLAN option on PORTNUMBER
- the VLANID option
If a virtual switch is defined as VLAN aware and no VLAN membership is given with the GRANT, PORTNUMBER, NICDEF or the VLANID (or provided by an external security manager), a guest is a member of the virtual switch's default VLAN ID (defvid) only if a defvid was assigned as part of the virtual switch definition.
The MACID may not be changed while a z/VM TCP/IP stack is providing management (SNMP) services for the virtual switch. That is, when a HOME TCP/IP configuration statement has established a management IP address for the virtual switch using the VSWITCH switchname keyword. Use the QUERY VSWITCH command to find the name of the stack providing management services and contact the administrator of the stack to remove the management IP address using the OBEYFILE command for the HOME configuration statement. This disables management services (including SNMP) for the virtual switch. When the MACID has been changed successfully notify SNMP clients of the MACID change and issue the OBEYFILE command to reassign the IP address and reactivate SNMP services.
The MACID may not be changed while the virtual switch connection to the hardware LAN is active. Use the SET VSWITCH switchname DISCONNECT command before changing the MACID.
Changing the RDEV list with SET VSWITCH RDEV can affect SNMP data, specifically the port number that represents the OSA-E connection to the real network. This is the Bridge MIB dot1dBasePort variable (1.3.6.1.2.1.17.1.4.1).
Using the VLAN_counters ON option on SET VSWITCH can significantly degrade throughput and increase system utilization for a virtual switch. Use this option only if there is a need to understand traffic patterns at the level of VLAN IDs. One example of when you might want VLAN_counters ON is when you are using a network management tool to analyze VLAN network traffic.
Detailed transmission counters are available only for a VLAN AWARE Virtual Switch with the VLAN_counters option set to ON. These values can be obtained by using the Diagnose x'26C' interface.
If the virtual switch is VLAN aware, the VLANs need to be configured with the GRANT, VLANID or PORTNUMBER command or via the NICDEF statement in the user directory. If an External Security Manager (ESM) is in control of the virtual switch, the VLANs configured (with GRANT, VLANID, PORTNUMBER or NICDEF) must be included in the VLAN list provided by the ESM.
When SET VSWITCH commands are used in conjunction with NICDEF statements to configure the network attributes, the following rules apply:
- No SET VSWITCH configuration is required if the NICDEF statement provides all necessary network configuration.
- NICDEF attributes override any prior SET VSWITCH configuration (and this is reflected in subsequent QUERY VSWITCH output).
- After a device is connected to the virtual switch, subsequent SET VSWITCH commands change the active configuration (but do not alter NICDEF statements in the USER DIRECT source).
- Each time the virtual NIC is created (or coupled) to the network, network attributes from the NICDEF statement are refreshed (replacing any dynamic changes made using the SET VSWITCH command).
The following notes are related to the SET VSWITCH PATHMTUDISCOVERY option:
- When a PORT GROUP is defined using the SET PORT command, the PATHMTUDISCOVERY option applies to all members of the group.
- If a virtual switch is configured with an UPLINK NIC, the SET VSWITCH PATHMTUDISCOVERY option is not applicable. However, it can be set for use later when an UPLINK RDEV port device is defined.
- If a virtual switch is configured with the NOUPLINK option, the SET VSWITCH PATHMTUDISCOVERY option is not allowed.
A Global virtual switch is a collection of virtual switches that share the same networking characteristics. This collection of virtual switches spans multiple systems running z/VM but logically operates as a single switch.
Virtual switches defined with the same name and the GLOBAL option are said to be members of the same global virtual switch when they reside in systems running z/VM that belong to the same IVL domain. (Definition and activation of an IVL virtual switch allows a system running z/VM to join an IVL domain. See usage note 19 for more information about the IVL virtual switch.)
The following conditions must be fulfilled in order to create or change a global virtual switch member:
- The system's IVL virtual switch must be defined and its UPLINK port connected. In other words, the system must be an active member of an IVL domain.
  Creation of Global virtual switches specified in the SYSTEM CONFIG file will be deferred until the IVL virtual switch UPLINK port connects the system to the IVL domain. Message HCP3178I will be displayed for each deferred Global virtual switch.
- If any other virtual switch exists in the IVL domain with the same name the following attributes must match or the DEFINE VSWITCH or SET VSWITCH will fail with message HCP3170E.
  - IP or ETHERNET
  - ISOLATION
  - VEPA
  - VLAN AWARE or UNAWARE
  - NATIVE natvid
  - USERBASED or PORTBASED
- The following additional restrictions exist if a global virtual switch is configured to use a shared port group:
  - RDEV device_addr is not allowed
SET VSWITCH COUNTERS CLEAR only affects the data displayed via the QUERY VSWITCH and QUERY NIC commands. It does not affect other data such as Virtual Switch monitor records, Diagnose x'26C' data, or SNMP BRIDGE-MIBs for a virtual switch.

Examples

The following examples apply when CP, not an ESM, is protecting the guest LAN:

To allow user VMTCPIP to connect to virtual switch BIGANG and filter any incoming traffic using VLAN 9, specify the following:
```
  set vswitch bigang grant vmtcpip vlan 9
```
To remove the authority of LINUX1 to connect to virtual switch BIGANG, specify the following:
```
  set vswitch bigang revoke linux1
```
To connect virtual switch BIGANG to a real LAN using device FD00, specify the following:
```
  set vswitch bigang rdev fd00
```
To disconnect virtual switch BIGANG from device FD00 and reconnect it to a real LAN using device FE00 and portname ableport, specify the following:
```
  set vswitch bigang disconnect
  set vswitch bigang portname ableport
  set vswitch bigang rdev fe00
  set vswitch bigang connect
```

To define a port based virtual switch VSWITCH1 with multiple access ports 10 and 20 for user1, specify the following. Port 10 will be added to VLAN 11 and port 20 will be added to VLAN 21.

  define vswitch vswitch1 portbased vlan aware
  set vswitch vswitch1 portnumber 10 userid user1
  set vswitch vswitch1 portnumber 20 userid user1
  set vswitch vswitch1 vlanid 11 add 10
  set vswitch vswitch1 vlanid 21 add 20

Given VSWITCH1 (a VLAN AWARE network), individual device connections can be configured in the user directory with no need for SET VSWITCH commands:

  USER USER1 ...
  //
  NICDEF 2100 TYPE QDIO LAN SYSTEM VSWITCH1 VLAN 11 PORTTYPE ACCESS
  NICDEF 2200 TYPE QDIO LAN SYSTEM VSWITCH1 VLAN 21 PORTTYPE ACCESS

Responses

Response 1:

    command complete

is the normal response from this command.

Messages

HCP002E Invalid operand - operand.
HCP003E Invalid option - option
HCP003E Invalid option - command contains extra option(s) starting with option
HCP007E Invalid userid - userid
HCP025E Storage missing or invalid
HCP2768E Missing switchname
HCP2783E VSWITCH SYSTEM switchname does not exist
HCP2798I User userid is already authorized
HCP2799E VSWITCH change is not allowed.
HCP2838I Device device specified for VSWITCH switchname BRIDGEPORT is not a bridge-capable HiperSockets device.
HCP2838I Device device specified for VSWITCH switchname does not exist.
HCP2838I Device device specified for VSWITCH switchname is already attached to user username.
HCP2838I Device device specified for VSWITCH switchname is not compatible with the VSWITCH type.
HCP2838I Device device specified for VSWITCH switchname is offline.
HCP2838I Port portnumber specified for device device is invalid; maximum port number is maxportnumber.
HCP2838I Device device specified for VSWITCH switchname is not configured for priority queuing.
HCP2839E Invalid operand for specified VSWITCH: operand
HCP2846E The [VLAN | PORTTYPE | GVRP | NATIVE | VLAN_COUNTERS | VLANID | IVLPORT VLAN] option is not allowed for a VLAN UNAWARE virtual switch.
HCP2847E PORTTYPE ACCESS is not allowed when the user is authorized for more than one VLAN
HCP2850E MACID is not set for switchname. SSI cluster mode not stable.
HCP2850E MACID is not set for VSWITCH vswname. [ Stack userid is providing management services | MAC address macaddr is already in use [ by user ID ] | Suffix for MAC address macaddr is not within USER MACIDRANGE | No MACID is available ].
HCP2853E SET VSWITCH not performed; device limit exceeded.
HCP2856E SET VSWITCH not performed; port group already assigned to VSWITCH SYSTEM switchname.
HCP2856E SET VSWITCH not performed; port group groupname is already in use.
HCP2858I Guest userid is authorized for too many VLAN IDs on SYSTEM switchname. VLAN-specific ARP processing is disabled.
HCP2858I userid connection to lanowner lanname has been [revoked | updated] by userid1.
HCP2858I userid connection to lanowner lanname is not affected by this update.
HCP3001E Device device is defined for both port group groupname and VSWITCH SYSTEM switchname.
HCP3002E Unable to establish ISOLATION mode at this time; VSWITCH SYSTEM switchname configuration in transition.
HCP3003E Controller controllername for VSWITCH SYSTEM switchname does not support OSA QDIO Connection Isolation.
HCP3004E Device device for VSWITCH SYSTEM switchname does not support OSA QDIO Connection Isolation.
HCP3022E SET VSWITCH not performed; virtual switch switchname is defined with NOUPLINK.
HCP3022E SET VSWITCH not performed; user userid not logged on.
HCP3022E SET VSWITCH not performed; device vdev does not exist.
HCP3022E SET VSWITCH not performed; NIC type nictype does not match VSWITCH type switchname.
HCP3022E SET VSWITCH not performed; NIC vdev is already attached to owner switchname.
HCP3022E SET VSWITCH not performed; CONNECT or DISCONNECT is already in progress on the {UPLINK | BRIDGE} port.
HCP3022E SET VSWITCH not performed; userid is not authorized to COUPLE to VSWITCH switchname.
HCP3022E SET VSWITCH not performed; VLAN configuration error.
HCP3022E SET VSWITCH not performed; NIC transport type transport1 does not match VSWITCH transport type transport2.
HCP3022E SET VSWITCH not performed; internal logic error code code.
HCP3022E SET VSWITCH not performed; vdev is not the correct device type.
HCP3022E SET VSWITCH not performed; VSWITCH does not exist.
HCP3022E SET VSWITCH not performed; ESM error.
HCP3022E SET VSWITCH not performed; Uplink port error.
HCP3022E SET VSWITCH not performed; ESM VLAN configuration error.
HCP3022E SET VSWITCH not performed; MACPROTECT is not valid for the IP transport type.
HCP3022E SET VSWITCH not performed; [BRIDGEPORT | VEPA] is not valid when the transport type is IP.
HCP3022E SET VSWITCH not performed; [BRIDGEPORT | VEPA] is not valid when the ISOLATION setting is ON.
HCP3022E SET VSWITCH not performed; ISOLATION is not valid when a Bridge Port is defined.
HCP3022E SET VSWITCH not performed; BRIDGEPORT RESET requires the virtual switch to be the active Bridge Port connection.
HCP3022E SET VSWITCH not performed; PATHMTUDISCOVERY is not valid when the virtual switch is defined with the NOUPLINK option.
HCP3022E SET VSWITCH not performed; [VEPA | ISOLATION] is not valid when [ISOLATION | VEPA] is on.
HCP3022E SET VSWITCH not performed; SWITCHOVER is not valid when the virtual switch is disconnected.
HCP3022E SET VSWITCH not performed; SWITCHOVER is not valid when the uplink port is a NIC.
HCP3022E SET VSWITCH not performed; SWITCHOVER is allowed only when there is an eligible backup device in the uplink RDEV list.
HCP3022E SET VSWITCH not performed; SWITCHOVER is allowed only when the active device is in the uplink RDEV list.
HCP3022E SET VSWITCH not performed; SWITCHOVER is allowed only when the virtual switch is not configured for link aggregation.
HCP3022E SET VSWITCH not performed; UPLINK NIC is not valid when the VEPA setting is ON.
HCP3022E SET VSWITCH not performed; VEPA is not valid when an Uplink NIC is defined.
HCP3022E SET VSWITCH not performed; [VEPA | ISOLATION] ON is not valid for a GLOBAL virtual switch.
HCP3022E SET VSWITCH not performed; UPLINK NIC is not valid for an IVL virtual switch.
HCP3022E SET VSWITCH not performed; No port is available.
HCP3022E SET VSWITCH not performed; PRIQUEUING OFF is not valid for an IVL virtual switch.
HCP3022E SET VSWITCH not performed; PQUPLINKTX is not valid for an IVL virtual switch.
HCP3031I Port portnum cannot join VLAN vlanid. The port is not defined.
HCP3031I Port portnum cannot join VLAN vlanid. Access ports cannot join more than one VLAN.
HCP3032I Port portnum cannot be removed from VLAN vlanid. The port is not defined.
HCP3032I Port portnum cannot be removed from VLAN vlanid. The port has not joined that VLAN.
HCP3033E SET VSWITCH not performed; Port portnum is already defined.
HCP3033E SET VSWITCH not performed; Port portnum is not defined.
HCP3033E SET VSWITCH not performed; VLAN vlanid is not defined.
HCP3033E SET VSWITCH not performed; Port definition conflicts with Uplink NIC port definition.
HCP3033E SET VSWITCH not performed; Uplink NIC port conflicts with existing port definition.
HCP3039I Port portnum has joined VLAN vlanid.
HCP3039I Port portnum has been removed from VLAN vlanid.
HCP3040I SET VSWITCH completed with messages.
HCP3045E The Bridge facility is not supported by this processor.
HCP3046E Port number conflicts with configured port portnum.
HCP3049E An internal error occurred; the state of the virtual switch switchname may be unstable.
HCP3160E Virtual switch switchnm cannot be configured with the RDEV operand specifying back up devices.
HCP3160E Virtual switch switchnm cannot be configured with a shared port group.
HCP3161E [DEFINE VSWITCH | SET VSWITCH] is not performed; a port group defined with the SHARED option can be used only with a virtual switch defined with the GLOBAL option.
HCP3163E SET VSWITCH is not performed; IVLPORT is valid only for an IVL virtual switch.
HCP3163E SET VSWITCH is not performed; system sysname is isolated from IVL Domain domain due to a configuration problem.
HCP3163E SET VSWITCH is not performed; the IVL virtual switch does not exist or its IVL port is not connected.
HCP3166E [DETACH VSWITCH | SET VSWITCH DISCONNECT] for IVL VSWITCH ivlswitchnm failed. Virtual switch switchname is defined on systemnm with the GLOBAL attribute.
HCP3167E [DEFINE VSWITCH switchnm | SET VSWITCH switchnm | SET PORT GROUP groupname] failed. The IVL virtual switch does not exist or its UPLINK port is not connected.
HCP3170E VSWITCH systemname.switchname [is not created | is not changed]. The virtual switch defined on systemname [ conflicts with the [ IP | ETHERNET | ISOLATION | VEPA | VLAN AWARE | VLAN UNAWARE |NATIVE VLAN | USERBASED | PORTBASED ] attribute ].
HCP3170E VSWITCH systemname.switchname [is not created | is not changed]. An internal error occurred.
HCP3170E VSWITCH systemname.switchname [is not created | is not changed]. The virtual switch defined on systemname [ is currently not responding | is currently in synchronization ].
HCP3173E Device device is reserved for system use.
HCP3174I System systemname is not a member of the local system's IVL Domain.
HCP3186E [DEFINE VSWITCH GROUP | SET PORT GROUP | SET VSWITCH GROUP] for shared port group groupname not performed; devices on OSA PCHID pchid do not exist or are not available.
HCP3195E SET [VMLAN | VSWITCH] not performed; trace table can not be allocated.
HCP3196E SET VSWITCH not performed; the port group must be defined before associating it with a GLOBAL vswitch.
HCP3199E SET VSWITCH not performed; uplink port group groupname on this system is not equivalent to other IVL members sharing the same port group.
HCP3221E SET VSWITCH GROUP not performed; usage of shared port group groupname would exceed the maximum number of virtual switches allowed by a single system sharing the same port group.
HCP6704E Missing token at end of line.
HCP6706E Invalid BUFFER value - value
HCP6706E Invalid device address - vdev
HCP6706E Invalid device address or port number - {vdev | portnumber}
HCP6706E Invalid groupname - groupname
HCP6706E Invalid HEARTBEAT value - value
HCP6706E Invalid MACID - id
HCP6706E Invalid number - number
HCP6706E Invalid PATHMTUDISCOVERY value - value
HCP6706E Invalid PING value - value
HCP6706E Invalid portname - portname
HCP6706E Invalid port number - portnumber
HCP6706E Invalid switchname - switchname
HCP6706E Invalid TRACESIZE value - value
HCP6706E Invalid VLAN id - vlanid