Cisco Systems Cisco MGX 8850 Manuale Utente
7-24
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 7
SPVC and SVC Commands
cnfcon
cnfcon
Configure Connection
Modifies the bandwidth, policing, and routing parameters of an existing endpoint. This command applies
to only an SPVC or SPVP. For ABR-specific parameters, use the cnfabr command.
to only an SPVC or SPVP. For ABR-specific parameters, use the cnfabr command.
The command parameters consist of:
•
A logical port, VPI, and VCI to identify the connection
•
Bandwidth parameters for the local (master) end then the remote (slave) end
•
Policing parameters for the connection as a whole
After you specify the mandatory connection identifier, all other parameters are optional.
Card(s) on Which the Command Executes
AXSM
Usage Guidelines for cnfcon
The following sections discuss the application of certain cnfcon parameters.
Note
On DAX connections, using cnfcon at the slave end has no effect. For DAX connections, use cnfcon
at the master end only, and the parameters will take effect on the controller as well.
at the master end only, and the parameters will take effect on the controller as well.
Traffic Parameters
Traffic parameters such as PCR, SCR, MBS are entered at both the master and slave endpoints for both
the forward and reverse directions. Be sure that the value entered as “local” on one end is equal to the
value entered as “remote” on the other end. For example, the lpcr on the slave endpoint should be same
as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If
you modify traffic parameters after creating an SPVC, you just modify them at either the master endpoint
or the slave endpoint.
the forward and reverse directions. Be sure that the value entered as “local” on one end is equal to the
value entered as “remote” on the other end. For example, the lpcr on the slave endpoint should be same
as the rpcr on the master endpoint and vice versa when you provision the connection at the other end. If
you modify traffic parameters after creating an SPVC, you just modify them at either the master endpoint
or the slave endpoint.
Traffic parameters such as CDV, CTD are entered at both the master and slave endpoints for both the
forward and reverse directions. However, the values of these parameters entered at the slave end are
ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master
end only.
forward and reverse directions. However, the values of these parameters entered at the slave end are
ignored during call setup. Therefore, you can specify the lcdv, rcdv, lctd and rctd options at the master
end only.
Routing Parameters
The routing parameter maxcost (specified using -mc option) need to be entered at the master endpoint
only. The values of this parameters entered at the slave end is ignored and not considered during call
setup.
only. The values of this parameters entered at the slave end is ignored and not considered during call
setup.
Frame Discard
For the parameter frame discard (specified using -frame option), you need to enter it at only the master
endpoint. This parameters has no significance at the slave end.
endpoint. This parameters has no significance at the slave end.
For the MGX 8850 2.0 release, if you try to enable frame discard at the slave end point you will not get
an error message. Nothing will happen, and frame discard will not take effect. In future releases, an error
message will be displayed if you try to enable frame discard at the slave end point.
an error message. Nothing will happen, and frame discard will not take effect. In future releases, an error
message will be displayed if you try to enable frame discard at the slave end point.