This command controls the administrative state of the ccag-id the command is executed under. Upon creation, the default state of a CCAG is to be administratively up which corresponds to the no shutdown form of the command. If the CCAG must be forced to be operationally down, the
shutdown command will place the CCAG into an administratively down state causing the operational state to also be down.
The no form of the command removes any current description string from the CCAG.
None (A description string must be explicitly defined)
The no form of the command removes an existing
ccag-id from the system. Once the specified
ccag-id is removed from the system, it may not be referenced by any cross connect objects. If the
force keyword is not specified, the
no ccag ccag-id command will fail if the specified
ccag-id has one or more
cc-ids associated with it. In the event that the specified
ccag-id does not exist, the
no ccag ccag-id command will return to the current CLI context without any change to the system.
None (each CCAG context must be explicitly created to be used)
After a ccag-id is created, a CCAG SAP may be created with an association with the
ccag-id. A CCAG SAP is identified by a concatenation of an existing
ccag-id and a
cc-id. The
cc-id must match the
cc-id of the other object the CCAG SAP is paired with on the
ccag-id. The created
ccag-id may also be associated with a network IP interface. A network IP interface is bound to the
ccag-id through the port command in the config router interface ip-interface context and references the
ccag-id and a
cc-id. Again, the
cc-id must match the other object the IP interface is paired with on the
ccag-id.
Once created, the ccag ccag-id command may be executed to enter the
ccag-id instance for the purpose of editing the CCAG parameters or operational state.
The create keyword explicitly indicates that the specified
ccag-id is being created. Handling the inclusion or exclusion state of the create keyword is dependent on the system environment variable create.
Once a ccag-id has been created, the create keyword is ignored when a ccag command is executed with that
ccag-id. The
ccag ccag-id create command will only result in a CLI context change to the specified CCAG instance for a pre-existing
ccag-id.
The force keyword removes the specified
ccag-id regardless of the presence of one or more
cc-id. If a SAP exists on the
ccag-id, the force keyword will cause the SAP to be removed from the configuration. If a network IP interface is bound to the
ccag-id, the interface will be silently unbound from the
ccag-id. The force keyword is intended as a time saving feature, preventing the need to first remove all service and network associations with the
ccag-id.
It is not required to first remove all CCAs from the CCAG prior to deleting the CCAG from the system. When the CCAG is removed, association with all member CCAs is automatically removed.
config>vsm>ccag ccag-id>access
The no form of the command returns the CCAG access QoS adaptation rule to the default setting of distribute.
The link keyword is mutually exclusive with the
distributed keyword. When
link is specified, the CCAG will create the SAP queues and virtual schedulers on each CCA with the actual parameters defined in the QoS and scheduler policies. This mode is useful when conversation hashing places all or most traffic over a single CCA.
The distribute keyword is mutually exclusive with the
link keyword. When
distribute is specified, the CCAG SAP queues and schedulers on each CCA will receive a portion of the defined parameters in the QoS and scheduler policies. The portion is decided on an IOM basis with the ratio determined by the number of active CCA members on the IOM relative to the total number of active members within the CCAG. The following equation may be used to determine the actual ratio:
[no
] member-cca
card-slot/mda-number
The a keyword is mutually exclusive to the
b keyword and defines the CLI CCA path context to be the alpha path. Either the
a or
b path must be specified. If the
a or
b keyword is not present, the path command will fail without changing the current CLI context.
The b keyword is mutually exclusive to the
a keyword and defines the CLI CCA path context to be the beta path. Either the
a or
b path must be specified. If the
a or
b keyword is not present, the path command will fail without changing the current CLI context.
rate kilobits-per-second [aggregate
| cca
]
config>vsm>ccag ccag-id>path {a | b}
The no form of the command removes path rate limiting from all CCAs in the CCAG membership list for the path.
None (rate limiting the alpha path must be explicitly defined)
The aggregate keyword is optional and mutually exclusive to the
cca keyword. When
aggregate is specified, the defined rate is divided among the CCAs in the CCAG member list based on the number of active CCAs. If three CCAs are active, the rate is divided by three and the result is applied to each active CCA. If a fourth CCA becomes active on the CCAG, the defined rate is then divided by four with the result applied to each CCA member on the CCAG. The actual rate at each CCA is implemented in 50Mbps increments. The system will adapt the specified rate to the best rate available per CCA.
The cca keyword is optional and mutually exclusive to the
aggregate keyword. When
cca is specified, the defined rate is applied to all CCAs in the CCAG member list. The actual rate at each CCA is implemented in 50Mbps increments. The system will adapt the specified rate to the best rate available per CCA.
The no form of the command returns the path-weight for the path to the default value of 50.
config>vsm>ccag ccag-id>path {a | b}
config>vsm>ccag ccag-id>path {a | b}>sap-net
config>vsm>ccag ccag-id>path {a | b}>net-sap
The no form of the command returns the in-use MAC address for the path’s context to the default MAC from the chassis MAC pool.
config>vsm>ccag ccag-id>path {a | b}>sap-sap
config>vsm>ccag ccag-id>path {a | b}>sap-net
config>vsm>ccag ccag-id>path {a | b}>net-sap
The no form of the command returns the MTU for the path’s sap-sap context to the default MTU.
|
Default
|
1518 - sap-sap
1518 - sap-net
9212 - net-sap
|
config>vsm>ccag ccag-id>path {a | b}>sap-sap
config>vsm>ccag ccag-id>path {a | b}>sap-net
config>vsm>ccag ccag-id>path {a | b}>net-sap
config>vsm>ccag ccag-id>path {a | b}>sap-sap>egress
config>vsm>ccag ccag-id>path {a | b}>sap-sap>ingress
config>vsm>ccag ccag-id>path {a | b}>sap-net>egress
config>vsm>ccag ccag-id>path {a | b}>sap-net>ingress
config>vsm>ccag ccag-id>path {a | b}>net-sap>egress
[no
] resv-cbs percentage-of-pool
config>vsm>ccag ccag-id>path {a | b}>sap-sap>egress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-sap>ingress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-net>egress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-net>ingress>pool
config>vsm>ccag ccag-id>path {a | b}>net-sap>egress>pool
The no form of the command returns the reserved portion of the buffer pool to the default percentage.
config>vsm>ccag ccag-id>path {a | b}>sap-sap>egress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-sap>ingress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-net>egress>pool
config>vsm>ccag ccag-id>path {a | b}>sap-net>ingress>pool
config>vsm>ccag ccag-id>path {a | b}>net-sap>egress>pool
The no form of the command configures the default slope policy as the managing policy for the buffer pool.
config>vsm>ccag ccag-id>path {a | b}>sap-sap
config>vsm>ccag ccag-id>path {a | b}>sap-net
config>vsm>ccag ccag-id>path {a | b}
config>vsm>ccag ccag-id>path {a | b}>sap-net>ingress>pool
The no form of the command configures the default slope policy as the managing policy for the buffer pool.
config>vsm>ccag ccag-id>path {a | b}>net-sap
config>vsm>ccag ccag-id>path {a | b}>
The no form of the command returns the MTU for the path’s net-sap context to the default MTU.
config>vsm>ccag ccag-id>path {a | b}>net-sap
The no form of the command reverts the path’s net-sap context statistics billing collection to the statistics defined in the default network accounting policy.
config>vsm>ccag ccag-id>path {a | b}>net-sap
The no form of the command disables network billing statistics collection on the net-sap context.
config>vsm>ccag ccag-id>path {a | b}>net-sap
This command defines the egress network queues used by IP interfaces bound to the path’s net-sap context. The specified queue-policy-name defines the number of queues, the rate and buffering parameters for the queues and the forwarding class mappings to the queues.
The no form of the command reverts the path’s net-sap network IP interface queues to the systems default queue policy.
config>vsm>ccag ccag-id>path {a | b}>net-sap
config>vsm>ccag ccag-id>path {a | b}>net-sap>egress
Refer to the 7750 SR OS Interface Configuration Guide for more card, MDA, and port command information. Refer to the
7750 SR OS Services Guide for details about configuring specific service parameters.
The no form of the command unprovisions an MDA from the system. For a VSM to be unprovisioned, the VSM must not be a member of a CCAG. If the VSM is a member of a CCAG, the
no cca slot-number/mda-number command must be used in the CCAG member-list context. Once a CCA is unprovisioned from the system; it cannot be made a member of a CCAG until it has been reprovisioned.
None (An MDA position number must be explicitly specified.)
This command cross connects a network IP interface to a CCAG SAP using the referenced ccag-id. A CCAG network IP interface binding is identified by four items; the
ccag-id, the CCAG path, the pairing type and the
cc-id. A network IP interface CCAG port binding supports all the available features as port binding using a Dot1Q virtual interface.
To support cross connection between services and network IP interfaces, the network interface port command allows the binding of the IP interface to a ccag cc-id. Similar to service CCAG SAPs, the network IP interface port binding command must reference the
ccag-id, the CCA path (.a or .b) and the
cc-id used by the service CCAG SAP on the other CCA path. The pairing type is optional as only .
net-sap is supported.
The no form of the command removes the CCAG binding from the network IP interface.
The ccag-id portion of the port binding is required and specifies which
ccag-id the network IP interface must be bound to. The specified
ccag-id must exist on the system or the port binding will fail. The leading dash must be included as a separator between ccag and the
ccag-id.
The :cc-id portion of the port binding is required and specifies the unique
cc-id in use by the CCAG network IP interface port binding and the cross connect SAP on the other path.
Services are provisioned onto a CCAG using a special CCAG SAP definition. CCAG SAPs must reference a ccag-id, a CCA path (a or b), a pairing type (sap-sap or sap-net) and a unique
cc-id. The
ccag-id identifies the group of CCAs that will be used for forwarding packets associated with the SAP. The path identifies the bandwidth control grouping used to manage CCA egress bandwidth. The pairing type helps the system identify which buffering resources will be used to manage egress queuing of packets. Finally, the
cc-id is used to explicitly cross connect the SAP to another SAP or network IP interface configured with the same
cc-id.
sap ccag-ccag-id.{a
| b
}[.sap-net | .sap-sap]:cc-id [create
]
This command creates a cross connect SAP on the ccag-id referenced in the Epipe service. A CCAG SAP is identified by four items; the
ccag-id, the CCAG path, the pairing type and the
cc-id. An Epipe CCAG SAP supports all the available QoS, filtering and accounting features as an Epipe Dot1Q SAP.
The no form of the command removes a SAP from a service context. Once removed, all information and resources concerning the SAP is deleted from the system including the CCAG
cc-id in use on the CCA path.
The ccag-id portion of the SAP identifier is required and specifies which
ccag-id on which the SAP must be created. The specified
ccag-id must exist on the system or the SAP creation will fail. The leading dash must be included as a separator between
ccag and the
ccag-id.
The :cc-id portion of the CCAG SAP identifier is required and specifies the unique
cc-id in use by the CCAG SAP and the cross connect object on the other path.
When the system environment variable create is enabled, the system requires the explicit use of the create keyword when creating objects such as SAPs. If the keyword is not included and the specified CCAG SAP has not already been created, an error will occur and the CLI will not change context to the specified CCAG SAP instance. This is designed to prevent the inadvertent creation of a CCAG SAP in the event where the wrong CCAG SAP identifier is specified during an attempt to edit an existing CCAG SAP. If the
create keyword is specified, the CCAG SAP will be created if it does not already exist or if it does exist, the CLI context will change to the specified CCAG SAP.
sap ccag-ccag-id.{a
| b
}[.sap-net | .sap-sap]:cc-id [create
]
This command creates a cross connect SAP on the ccag-id referenced in the VPLS service. A CCAG SAP is identified by four items; the
ccag-id, the CCAG path, the pairing type and the
cc-id. A VPLS CCAG SAP supports all the available QoS, filtering and accounting features as a VPLS Dot1Q SAP.
The no form of the command removes a SAP from a service context. Once removed, all information and resources concerning the SAP is deleted from the system including the CCAG
cc-id in use on the CCA path.
Specifies which ccag-id on which the SAP must be created. The specified
ccag-id must exist on the system or the SAP creation will fail. The leading dash must be included as a separator between
ccag and the
ccag-id.
The .a and
.b portion of the CCAG SAP identifier is required and is used to define the CCA bandwidth path with will be associated with the SAP. The path association must be specified and .a and .b are mutually exclusive. The .a designation identifies the SAP as being on the Alpha path and the .b designation identifies the SAP as being on the Beta path. The paired SAP or network IP interface using the same
cc-id as the SAP must be associated with the opposite path. The leading period must be included as a separator between the
ccag-id and the path designator.
The :cc-id portion of the CCAG SAP identifier is required and specifies the unique
cc-id in use by the CCAG SAP and the cross connect object on the other path.
When the system environment variable create is enabled, the system requires the explicit use of the create keyword when creating objects such as SAPs. If the keyword is not included and the specified CCAG SAP has not already been created, an error will occur and the CLI will not change context to the specified CCAG SAP instance. This is designed to prevent the inadvertent creation of a CCAG SAP in the event where the wrong CCAG SAP identifier is specified during an attempt to edit an existing CCAG SAP. If the
create keyword is specified, the CCAG SAP will be created if it does not already exist or if it does exist, the CLI context will change to the specified CCAG SAP.
sap ccag-ccag-id.{a
| b
}[.sap-net | .sap-sap]:cc-id [create
]
This command creates a cross connect SAP on the ccag-id referenced in the IES service. A CCAG SAP is identified by four items; the
ccag-id, the CCAG path, the pairing type and the
cc-id. A CCAG SAP on an IES IP interface supports all the available QoS, filtering and accounting features as an IES IP interface Dot1Q SAP.
The no form of the command removes a SAP from the IES service IP interface context. Once removed, all information and resources concerning the SAP is deleted from the system including the CCAG
cc-id in use on the CCA path.
The ccag portion of the SAP identifier is required and specifies that the ies SAP is of the CCAG type.
The ccag-id portion of the SAP identifier is required and specifies which
ccag-id on which the SAP must be created. The specified
ccag-id must exist on the system or the SAP creation will fail. The leading dash must be included as a separator between ccag and the
ccag-id.
The :cc-id portion of the CCAG SAP identifier is required and specifies the unique
cc-id in use by the CCAG SAP and the cross connect object on the other path.
When the system environment variable create is enabled, the system requires the explicit use of the create keyword when creating objects such as SAPs. If the keyword is not included and the specified CCAG SAP has not already been created, an error will occur and the CLI will not change context to the specified CCAG SAP instance. This is designed to prevent the inadvertent creation of a CCAG SAP in the event where the wrong CCAG SAP identifier is specified during an attempt to edit an existing CCAG SAP. If the
create keyword is specified, the CCAG SAP will be created if it does not already exist or if it does exist, the CLI context will change to the specified CCAG SAP.
sap ccag-ccag-id.{a | b}[.sap-net | .sap-sap]:cc-id [create]
This command creates a cross connect SAP on the ccag-id referenced in the VPRN service. A CCAG SAP is identified by four items; the ccag-id, the CCAG path, the pairing type and the cc-id. A CCAG SAP on a VPRN IP interface supports all the available QoS, filtering and accounting features as a VPRN IP interface Dot1Q SAP.
The no form of the command removes a SAP from the VPRN service IP interface context. Once removed, all information and resources concerning the SAP is deleted from the system including the CCAG cc-id in use on the CCA path.
Specifies which ccag-id on which the SAP must be created. The specified ccag-id must exist on the system or the SAP creation will fail. The leading dash must be included as a separator between ccag and the ccag-id.
The .a and .b portion of the CCAG SAP identifier is required and is used to define the CCA bandwidth path with will be associated with the SAP. The path association must be specified and .a and .b are mutually exclusive. The .a designation identifies the SAP as being on the alpha path and the .b designation identifies the SAP as being on the beta path. The paired SAP or network IP interface using the same cc-id as the SAP must be associated with the opposite path. The leading period must be included as a separator between the ccag-id and the path designator.
Specifies that the SAP is of the SAP-2-Net pairing type and is required when the cc-id is paired with a network IP interface. The pairing type .sap-net is mutually exclusive with pairing type .sap-sap. If .sap-net is not specified, .sap-sap is assumed and does not need to be included in the SAP identification. When specified, the leading period must be used as a separator between the path designator and the pairing type.
The .sap-sap portion of the CCAG SAP identifier is mutually exclusive to .sap-net and is used to define the pairing type as SAP-2-SAP. The .sap-sap pairing type is only used when the cross connect object sharing the same cc-id on the opposite path is a CCAG SAP. If the other cross connect object is a network IP interface, the pairing type must be defined as .sap-net. If .sap-net is not specified, .sap-sap is assumed and does not need to be included in the SAP identification. When specified, the leading period must be used as a separator between the path designator and the pairing type.
The :cc-id portion of the CCAG SAP identifier is required and specifies the unique cc-id in use by the CCAG SAP and the cross connect object on the other path.
When the system environment variable create is enabled, the system requires the explicit use of the create keyword when creating objects such as SAPs. If the keyword is not included and the specified CCAG SAP has not already been created, an error will occur and the CLI will not change context to the specified CCAG SAP instance. This is designed to prevent the inadvertent creation of a CCAG SAP in the event where the wrong CCAG SAP identifier is specified during an attempt to edit an existing CCAG SAP. If the create keyword is specified, the CCAG SAP will be created if it does not already exist or if it does exist, the CLI context will change to the specified CCAG SAP.
