VNNAME


                                            (1) (2) (3)   
>>-+--------------------------------------+--------------------><
   '-VNNAME--=--connection_network_cpname-'

Notes:

On the PORT statement for all connections other than Enterprise Extender, code VNNAME if you code VNGROUP.
On the PORT statement for Enterprise Extender connections, VNNAME is not required if VNTYPE=GLOBAL, otherwise code VNNAME if you code VNGROUP.
VNNAME is valid on the GROUP statement only if this is an Enterprise Extender XCA major node (MEDIUM=HPRIP on the PORT statement).

statements:

PORT

GROUP

dependencies:

LAN, ATM LAN emulation, or Enterprise Extender connections only; VNGROUP; DIAL=YES on GROUP statement

Enterprise Extender connections; DIAL=YES on GROUP statement

On GROUP, MEDIUM=HPRIP is required on the PORT statement

Specifies a 1–17 character network-qualified CPNAME for the connection network. VNNAME is reported to the network topology as a virtual node and is treated as an adjacent CP to this node. The NETID of the SSCP that owns the connection network (the NETID of the host) is used.

For sessions that are routed through the connection network, a dynamic PU is created to represent the destination node. In effect, DYNPU=YES is enforced automatically when a session is established through the connection network.

VNNAME operand can be specified on the GROUP definition statement for Enterprise Extender Connection Networks.

VNNAME operand will no longer be required for Enterprise Extender Connection Networks when the VNTYPE is defined as GLOBAL. If no VNNAME is specified for a Global Virtual Node (VNTYPE=GLOBAL), then a default name of IP.IP will be used. If no Network ID (NETID) is specified for the VNNAME, then the NETID of the host defining the Global Virtual Node is used. Therefore, if a user does not want to use the default VNNAME, they should define their VNNAME as fully qualified throughout their network (otherwise they risk non-matching VNNAMEs and not being able to fully use their Global Virtual Routing Node support).

If the same VNNAME is defined more than once within the Enterprise Extender XCA major node, the associated IPADDR value, HOSTNAME value, or IP address resolved from the HOSTNAME value must be unique. A general rule is the VNNAME/specified or resolved IP address pair must be unique.

If the same VNNAME is defined more than once within the Enterprise Extender XCA major node, the VNTYPE associated with this virtual routing node (VRN) must be the same.

Note: A user may define both Global and Local Virtual Nodes in the same XCA (MEDIUM=HPRIP) major node. This can be done by defining them on multiple GROUP definition statements. Alternatively, this can be done by coding one Virtual Node on the PORT and coding other Virtual Nodes on one or more GROUP statements. If a Virtual Node is being defined on the PORT statement, then it must specify a VNGROUP operand and the GROUP referenced cannot define another Virtual Node (either Local or Global). A user may define as many Local or Global Virtual Nodes as their configuration requires.

Guideline: Although an Enterprise Extender connection network, including the virtual node name, type, and all TG characteristics, can be defined on the PORT definition statement, you should define your Enterprise Extender connection network on the corresponding GROUP definition statement instead. By coding all connection network and TG characteristics operands on the GROUP statement, the VNGROUP operand is no longer needed. Also, because there can be multiple connection networks defined in an Enterprise Extender XCA major node with multiple GROUP definition statements, defining all of the operands on the GROUP statement to which they apply provides more clarity.