(1) (2) >>-+------------------------+---------------------------------->< '-VNGROUP--=--group_name-'
- Code VNGROUP if you code VNNAME (or VNTYPE=GLOBAL if you default the name to IP.IP)
- VNNAME and VNTYPE can not be specified on the GROUP definition statement when that GROUP is specified on the VNGROUP operand on the PORT definition statement.
| statements: | PORT, GROUP |
| dependencies: | LAN, ATM LAN emulation and Enterprise
Extender connections only; VNNAME; DIAL=YES on GROUP statement On GROUP, MEDIUM=HPRIP is required on the PORT statement |
Specifies the name of the GROUP containing dial-out links available for use on the connection network named on the VNNAME operand.
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. The name specified on the VNGROUP operand provides the name of the group for the dynamic PU that is allocated.
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.