The manner in which a dynamic VIPA IP address should
be moved to another stack. A value of none(1) indicates
that moveable status does not apply to this DVIPA.
This value would be set for entries where backup is set
as the value for the ibmMvsDVIPAOrigin and
ibmMvsDVIPAStatus objects. For DVIPA IP addresses
activated as the result of a VIPADEFINE configuration
statement, a value of immediate(2) means that this dynamic
VIPA can be moved to another stack as soon as the other
stack requests ownership of the DVIPA by executing a
VIPADEFINE for the same dynamic VIPA. Any existing
connections on this stack will be maintained by the new
owning stack until the connections are closed. All new
connection requests will be directed to the new owning
stack. A value of whenIdle(3) means that this dynamic
VIPA can be moved to another stack when there are no
connections for this dynamic VIPA on this stack. While
there are existing connections, any new connection requests
will continue to be directed to this stack.
For DVIPA IP addresses activated as the result of a
VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL
or BIND, a value of nonDisruptive(4) means that this
DVIPA can be moved to another stack as soon as the other
stack requests ownership of the DVIPA by creating the
same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL.
Any existing connections on this stack will be maintained
by the new owning stack until the connections are closed.
All new connection requests will be directed to the new
stack. A value of disruptive(5) means that one of two
different behaviors will occur:
- In the case of a subsequent BIND by an application on
another stack, no movement of the DVIPA will occur
the second application will presumably be disrupted
because the BIND fails. (The first application is
unaware that another BIND occurred.)
- In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA
will move to another stack but connections to the DVIPA
on this stack will be broken.
Parsed from file mvstcpip.mi2.txt
Company: None
Module: IBMTCPIPMVS-MIB
The manner in which a dynamic VIPA IP address should
be moved to another stack. A value of none(1) indicates
that moveable status does not apply to this DVIPA.
This value would be set for entries where backup is set
as the value for the ibmMvsDVIPAOrigin and
ibmMvsDVIPAStatus objects. For DVIPA IP addresses
activated as the result of a VIPADEFINE configuration
statement, a value of immediate(2) means that this dynamic
VIPA can be moved to another stack as soon as the other
stack requests ownership of the DVIPA by executing a
VIPADEFINE for the same dynamic VIPA. Any existing
connections on this stack will be maintained by the new
owning stack until the connections are closed. All new
connection requests will be directed to the new owning
stack. A value of whenIdle(3) means that this dynamic
VIPA can be moved to another stack when there are no
connections for this dynamic VIPA on this stack. While
there are existing connections, any new connection requests
will continue to be directed to this stack.
For DVIPA IP addresses activated as the result of a
VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL
or BIND, a value of nonDisruptive(4) means that this
DVIPA can be moved to another stack as soon as the other
stack requests ownership of the DVIPA by creating the
same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL.
Any existing connections on this stack will be maintained
by the new owning stack until the connections are closed.
All new connection requests will be directed to the new
stack. A value of disruptive(5) means that one of two
different behaviors will occur:
- In the case of a subsequent BIND by an application on
another stack, no movement of the DVIPA will occur
the second application will presumably be disrupted
because the BIND fails. (The first application is
unaware that another BIND occurred.)
- In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA
will move to another stack but connections to the DVIPA
on this stack will be broken.
Parsed from file IBMTCPIPMVS-MIB.mib
Module: IBMTCPIPMVS-MIB
Vendor: IBM
Module: IBMTCPIPMVS-MIB
[Automatically extracted from oidview.com]
ibmMvsDVIPAMoveable OBJECT-TYPE SYNTAX INTEGER { none(1), immediate(2), whenIdle(3), nonDisruptive(4), disruptive(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The manner in which a dynamic VIPA IP address should be moved to another stack. A value of none(1) indicates that moveable status does not apply to this DVIPA. This value would be set for entries where backup is set as the value for the ibmMvsDVIPAOrigin and ibmMvsDVIPAStatus objects. For DVIPA IP addresses activated as the result of a VIPADEFINE configuration statement, a value of immediate(2) means that this dynamic VIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by executing a VIPADEFINE for the same dynamic VIPA. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new owning stack. A value of whenIdle(3) means that this dynamic VIPA can be moved to another stack when there are no connections for this dynamic VIPA on this stack. While there are existing connections, any new connection requests will continue to be directed to this stack. For DVIPA IP addresses activated as the result of a VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL or BIND, a value of nonDisruptive(4) means that this DVIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by creating the same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new stack. A value of disruptive(5) means that one of two different behaviors will occur: - In the case of a subsequent BIND by an application on another stack, no movement of the DVIPA will occur the second application will presumably be disrupted because the BIND fails. (The first application is unaware that another BIND occurred.) - In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA will move to another stack but connections to the DVIPA on this stack will be broken." ::= { ibmMvsDVIPAEntry 9 }
ibmMvsDVIPAMoveable OBJECT-TYPE SYNTAX INTEGER { none(1), immediate(2), whenIdle(3), nonDisruptive(4), disruptive(5) } MAX-ACCESS read-only STATUS current DESCRIPTION "The manner in which a dynamic VIPA IP address should be moved to another stack. A value of none(1) indicates that moveable status does not apply to this DVIPA. This value would be set for entries where backup is set as the value for the ibmMvsDVIPAOrigin and ibmMvsDVIPAStatus objects. For DVIPA IP addresses activated as the result of a VIPADEFINE configuration statement, a value of immediate(2) means that this dynamic VIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by executing a VIPADEFINE for the same dynamic VIPA. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new owning stack. A value of whenIdle(3) means that this dynamic VIPA can be moved to another stack when there are no connections for this dynamic VIPA on this stack. While there are existing connections, any new connection requests will continue to be directed to this stack. For DVIPA IP addresses activated as the result of a VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL or BIND, a value of nonDisruptive(4) means that this DVIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by creating the same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new stack. A value of disruptive(5) means that one of two different behaviors will occur: - In the case of a subsequent BIND by an application on another stack, no movement of the DVIPA will occur the second application will presumably be disrupted because the BIND fails. (The first application is unaware that another BIND occurred.) - In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA will move to another stack but connections to the DVIPA on this stack will be broken." ::= { ibmMvsDVIPAEntry 9 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.1 | ibmMvsDVIPAIpAddrType | 0 | 0 | The IP address type of the ibmMvsDVIPAIpAddr object. |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.2 | ibmMvsDVIPAIpAddr | 0 | 0 | The dynamic VIPA IP address. |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.3 | ibmMvsDVIPAMaskType | 0 | 0 | The IP address type of the ibmMvsDVIPAMaskAddr object This object will be set to unknown(0) for entries whose ibmMvsDVIPAOrigin v… |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.4 | ibmMvsDVIPAMaskAddr | 0 | 0 | The address mask. This object will be set to a zero-length string for entries whose ibmMvsDVIPAOrigin value is backup(2). |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.5 | ibmMvsDVIPAStatus | 0 | 0 | The status of this DVIPA on the stack. A status of unknown(1) should not occur and represents an error. |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.6 | ibmMvsDVIPAOrigin | 0 | 0 | The origin of how this DVIPA came to be configured to the stack. A value of backup(2) or define(3) indicates which VIPADYNAMIC P… |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.7 | ibmMvsDVIPARank | 0 | 0 | This stack's rank in the chain of backup stacks for a given dynamic VIPA. For entries whose ibmMvsDVIPAOrigin value is not backu… |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.8 | ibmMvsDVIPADistributeStatus | 0 | 0 | The status of this DVIPA on the stack in relation to the Sysplex Distributor function. A value of none(1) indicates that the DVI… |
| 1.3.6.1.4.1.2.6.19.2.2.11.1.1.10 | ibmMvsDVIPAServMgrEnabled | 0 | 0 | The status of this DVIPA on the stack in relation to the Service Manager function. A value of true(1) indicates that the DVIPA i… |