For
LAN, ATM LAN emulation, or Enterprise Extender connections: |
.-CAPACITY--=--4M-------------.
>>-+-----------------------------+-----------------------------><
'-CAPACITY--=--number_of_bits-'
|
statements: |
PORT, GROUP (TGs to Enterprise Extender
connection networks) |
dependency: |
TGs to connection networks For
GROUP; MEDIUM=HPRIP
|
range: |
1 - 1000Kb 1 - 1000Mb
1 - 100Gb
|
For
ATM native connections: |
.-CAPACITY--=--25M------------.
>>-+-----------------------------+-----------------------------><
'-CAPACITY--=--number_of_bits-'
|
statements: |
GROUP (TGs to connection networks)
PU (TGs over PVCs)
|
dependency: |
DIAL=YES (TGs to connection networks)
DIAL=NO (TGs over PVCs)
|
range: |
1 - 1000Kb 1 - 100Mb
1 - 100Gb
|
Specifies the effective capacity of the link that comprises
the transmission group (TG). Specify the value in Kb per second (for
example, 100K), Mb per second (for example, 100M), or Gb per second
(for example, 10G). This number approximates the bits per second that
the link can transmit (the transmission rate of the link, times the
maximum load factor expressed as a percentage).
Note: - Because the value for capacity is represented as a single byte,
the precision of the specified number of bits might be lost. For example,
numbers that are close (such as 100K and 101K) can be interpreted
by VTAM®, and displayed, as
the same value. See Table 1 for
a list of CAPACITY values you can specify and their corresponding
values when displayed.
- The capacity specified for ATM native connections defined as reserved
bandwidth should be related to the forward sustainable cell rate (DLCADDR
subfield 7). To calculate the data throughput required for a reserved
bandwidth connection, multiply the sustainable cell rate by the payload
per cell (48 bytes). If the defined CAPACITY is greater than ten
times the ATM reserved bandwidth connection capacity, excess storage
might be used and the weighting of this TG with others might cause
undesirable results.
Recommendations: - When specified on the PORT statement, VNGROUP and VNNAME (or VNTYPE=GLOBAL)
must also be specified on the PORT statement and the value applies
to the TG to the connection network specified in VNNAME (or IP.IP
if VNNAME is defaulted for VNTYPE=GLOBAL).
- When specified on the GROUP statement, VNNAME or VNTYPE=GLOBAL
must also be specified on the GROUP statement. If the GROUP is not
defined as a connection network, the TG characteristics cannot be
specified on the GROUP definition statement. They must be specified
on the PU definition statement in the switched major node (or for
dynamically created dial-in EE PUs on the DYNTYPE=EE model major node)
for the PU being dialed to establish the connection.
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.