NAME
lcell_pvcbatch - Batch command for establishing or dropping
Permanent Virtual Circuits (PVCs) in an ATM network.
SYNOPSIS
lcell_pvcbatch [ -b batchfile ] [ -i ipaddress ]
DESCRIPTION
This command provides a means to establish or terminate Per-
manent Virtual Circuits in an ATM network using a batch file
to specify the PVCs. The file format is described below,
and sample files are included in /usr/lnms/conf/*.pvc.
lcell_pvcbatch reads the batchfile specified, skips comment
lines that begin with "#", and executes any remaining lines
containing Open Call, Add Endpoint, Drop Call, or Drop End-
point commands. Execution consists of validating the
request and then sending the request to the SynOptics ATM
Connection Management System running on the station whose IP
Address is provided with the -i option. After each request
is sent to the CMS, lcell_pvcbatch suspends waiting for a
response message indicating success or failure. On failure,
a message is printed to indicate timeout or some other
detailed error situation.
Note that the two-character tokens below MUST be uppercase,
although the spacing between tokens is up to the user, in a
"free format", parsed by sscanf. Also note that the VPI and
VCI fields must be in required ranges. For virtual connec-
tions, VCI must be between 32 and 1023, inclusive. For vir-
tual paths, VPI must be between 1 and 1023, inclusive.
The first token indicates the action to be taken, with OC
indicating Open Call, AE meaning Add Endpoint, DC meaning
Drop Call, and DE meaning Drop Endpoint. The second token
indicates the accessibility of the call, with MP for point-
to-multipoint calls or PP for point-to-point calls. The
third field, vc_or_vp, tells whether to open a virtual con-
nection (VC) or a virtual path (VP). The second and third
fields are ignored for the Drop Call and Drop Endpoint
requests, but placeholders, e.g., "--" should be used for
these two tokens.
The remaining tokens are switchAtmAddress, port, vpi, vci,
plus switch2AtmAddress, port2, vpi2, and vci2, The first
four of these fields describe the access point at the owner
side. The remaining four fields describe the access point
at the other end (or at the new endpoint being added to the
call.
The switch ATM addresses can be either in MAC address for-
mat, or in ATM address format. MAC address format includes
12 hex characters (e.g., 000081abcdef) to identify the
switch. ATM address format includes the ESI (end station
identifier) followed by ":xx", where "xx" is the Selector
byte. The ESI is a 12-byte hex string representing the MAC
address of the switch. The Selector byte is a 2-byte hex
string and is normally "00". The values for port, vpi, and
vci are in decimal.
OPEN CALL -- ADDITIONAL PARAMETERS
Three additional parameters are required on the Open Call
request (only). These parameters specify the quality of
service, peak bandwidth, and sustained (or average)
bandwidth. Quality of service is specified using UBR, CBR,
VRT, or VBR. The "UBR" token indicates Unspecified Bit
Rate; "CBR" indicates Constant Bit Rate (the highest prior-
ity); "VRT" indicates Variable Bit Rate - Real Time; "VBR"
indicates Variable Bit Rate. Bandwidth values are specified
in megabits per second, and may contain a fraction (as in
2.02 for 2.02 Mbit/s). If excessively large values are
specified, Open Call requests might fail due to lack of
available bandwidth on a link, so choose these values
wisely. In particular, note that a single call specifying
10.0 Mbit/s corresponds to allocating the maximum rate of
standard Ethernet. If necessary, use the Allowed Bandwidth
capability of the Port Profile dialog to make future Open
Calls succeed or fail based on statistical multiplexing.
SUPPORT FOR VP TRUNKS
Carrier-provided VP Trunks are supported in the following
manner. To setup several calls that multiplex onto a single
VP Trunk, create virtual connections (not Virtual Paths)
that have unique VCI's at the port going to the VP Trunk,
but use the same VPI values. See the example later in the
manpage.
If multiple VP Trunks emanate from a single port, distin-
guish the VP Trunks by using the appropriate VPI for the
calls that should follow each VP Trunk.
CONVERSION OF EXISTING BATCH FILES
For backward compatibility, the ":xx" portion may be omitted
in ATM addresses. All examples herein omit the ":xx" por-
tion.
The Open Call request has changed slightly in each release,
from 1.0 to 1.1, and again to 1.2. With each change, addi-
tional capability has been provided. A single bandwidth
value was expected in 1.1, but 1.2 now requires quality of
service, as well as peak bandwidth and sustained bandwidth.
This requires editing of all existing PVC batch files to
modify Open Call requests.
Be certain to use the correct version of this utility.
Older versions of this program were provided in the 1.0 and
1.1 releases of SynOptics ATM Network Management Applica-
tion. In addition, a special version was provided with the
1.0.2 release of the SynOptics ATM Connection Management
System. When using the 1.2 CMS product, the 1.2 version of
this program must be used.
PVC/SVC Coexistence (1.0 to 1.1)
One notable difference in upgrading from 1.0 to 1.1
lcell_pvcbatch dealt with PVC/SVC coexistence. To establish
calls between an SVC client and a PVC client, 1.1 and 1.2
lcell_pvcbatch require that each client be specified using
the tuple of (switch, port). Version 1.0.2 used an interim
approach where the SVC client address itself could be speci-
fied, but this is no longer supported.
OPTIONS
-b batchfile Specifies the file to read to get the PVC
commands.
-i ipaddress Specifies the IP address of the station run-
ning SynOptics ATM Connection Management Sys-
tem.
EXAMPLES
lcell_pvcbatch -b sample.pvc -i 127.0.0.1
The above command would read pvc batch commands from
sample.pvc and send requests to the CMS running on IP sta-
tion 127.0.0.1.
Below are some sample PVC batch commands:
OC MP VC 000081000001 16 0 99 000081000001 15 0 99 UBR 6.0
1.0
AE MP VC 000081000001 16 0 99 000081000001 14 0 99
The above commands would open a multipoint virtual circult
owned by the client at port 16, but directed to clients on
ports 15 and port 14. The call will be setup with Unspeci-
fied Bit Rate quality of service.
OC PP VP 000081000001 16 100 0 000081000001 15 100 0 VRT
8.0 4.0
The above command would open a point-to-point virtual path
between the clients at ports 16 and 15. The request uses
variable bit rate real time.
OC PP VC 000081000001 16 0 101 000081000001 15 0 101 CBR
9.0 9.0
The above command would open a point-to-point virtual con-
nection between the clients at ports 16 and 15. The request
uses constant bit rate.
DC -- -- 000081000001 16 0 99 000081000001 15 0 99
DC -- -- 000081000001 16 100 0 000081000001 15 100 0
DC -- -- 000081000001 16 0 101 000081000001 15 0 101
The above commands would drop the calls from the previous
examples.
DE -- -- 000081000001 16 0 99 000081000001 15 0 99
DE -- -- 000081000001 16 100 0 000081000001 15 100 0
DE -- -- 000081000001 16 0 101 000081000001 15 0 101
The above commands would drop the endpoints on the right
from calls created in the previous examples. Dropping the
owner endpoint (by listing it on the left and right sides)
will drop the entire call. Dropping the last non-owner end-
point of a point-to-point or point-to-multipoint call will
also drop the entire call.
OC PP VC 000081000001 16 0 300 000081000001 12 50 300 UBR
5.0 1.0
OC PP VC 000081000001 16 0 301 000081000001 12 50 301 UBR
5.0 1.0
OC PP VC 000081000001 11 0 302 000081000001 12 50 302 UBR
5.0 1.0
The above commands would open three point-to-point virtual
connections that multiplex onto a single VP Trunk. Two
calls emanate from port 16, while one emanates from port 11.
All three calls end at port 12. From there the cells will
travel out with unique VCI's but with the same VPI value
(50). At the other end of the VPI Trunk, the individual
VC's can be de-multiplexed.
BUGS
Empty lines or lines with "#" as first character are
skipped. Lines with one or more blanks but no other charac-
ters cause a (useless) warning.
For Open Call, the actual bandwidths sent to CMS may be
slightly different than the bandwidth requested, due to
conversions to different units (namely chunks of 16 cells
per second). The values actually sent to CMS are converted
back to Mbit/s and printed when the Open Call request is
processed.
SEE ALSO
sscanf(3V)