The description command associates a text string with a configuration context to help identify the context in the configuration file.
The no form of this command removes any description string from the context.
The no form of the command is used to enable ingress multicast path management on the MDA or forwarding plane.
The no form of the command removes the specified bandwidth policy from the system. The bandwidth policy associations must be removed from MDA configurations before it can be removed.
The no form of the command restores the default number of secondary paths.
The no form of the command returns the default path bandwidth limit for the ingress multicast path. The command has no effect for MDAs with a path override in effect for the given path.
When forwarding through the queues, each packets forwarding class is ignored. However, the forwarding class is retained for proper egress processing. The packets expressed or implied profile is also ignored within the ingress path queues. A packets congestion priority is derived from the records cong-priority-theshold evaluation result as indicated by the multicast-info-policy. The cong-priority-theshold sets the high or low congestion priority of a record based on the records preference value. Within each multicast information policy bundle the cong-priority-theshold is set with a value from 0 to 7 and defines the threshold at which all records with a preference equal to or higher than the defined preference will be treated as congestion priority high. Multicast records with a preference lower than the defined class threshold will be treated as congestion priority low. Low priority packets use the low priority MBS threshold of the queue while high priority packets use the standard MBS value. In the event of path congestion, low priority packets are discarded first, leaving room for the higher priority packets.
The cbs percent-of-resv-cbs parameter is defined as a percentage of the reserved portion of the pool. The system allows the sum of all CBS values to equal more than 100% allowing for oversubscription of the reserved portion of the pool. If the reserved portion is oversubscribed and the queues are currently using more reserved space than provisioned in the pool, the pool automatically starts using the shared portion of the pool for within-CBS buffer allocation. On the shared early detection slopes could assume more buffers exist within the shared portion than actually do which may cause the early detection function to fail.
For the primary-path and secondary-path queues, the percentage is applied to a single queue for each path. For the ancillary-path, multiple queues are required. The cbs percent-of-resv-cbs is divided between all ancillary path queues. For example, if primary is given 10 percent, the primary path queues CBS is set to 10% of the reserved portion of the buffer pool. If ancillary is given 50 percent and 10 ancillary path queues exist, each ancillary queue gets 5%. The number of path queues required depends on the available chassis slots and the provisioned IOM types. 7450 ESS-6 chassis have 4 slots, 7450 ESS-7 and 7750 SR-7 have 5 and the 7450 ESS-12 and 7750 SR-12 have 10. An IOM-1 or IOM-2 on a slot has two switch fabric destinations.
The no form of the command restore the path queues default CBS value.
The no form of this command restores the default value.
The mbs percent-of-pool parameter is defined as a percentage of the total pool size. The system allows the sum of all MBS values to equal more than 100% allowing for oversubscription of the pool.
The no form of the command is used to restore the path queues default MBS value.
The no form of the command restores the default value of 50%.
The no form of the command returns the managed multicast path pool to its default settings.
Each multicast information policy contains a bundle named default. The default bundle cannot be deleted. Any multicast channel that fails to match a channel range within an explicit bundle is automatically associated with the default bundle.
The no form of the command removes a bundle from the multicast information policy. The default bundle cannot be removed from the policy.
The no form of the command removes the specified multicast channel from the containing bundle.
The admin-bw value is closely tied to the bw-activity command. When the bw-activity command is set to use-admin-bw, the multicast ingress path manager uses the configured administrative bandwidth value as the managed ingress bandwidth. The admin-bw value must be defined for the bw-activity use-admin-bw command to succeed. Once the bw-activity command is set to use the admin-bw value, the value cannot be set to 0 and the no admin-bw command will fail. Setting the bw-activity command to dynamic (the default setting), breaks the association between the commands.
The no form of the command restores the default value for admin-bw. If the command is executed in the
channel context, the channels administrative bandwidth value is set to null. If the command is executed in the
source-override context, the source override administrative bandwidth value is set to null.
The use-admin-bw setting requires that the channel be configured with an admin-bw value that is not equal to 0 in the same context as the
bw-activity command using the setting. Once a context has use-admin-bw configured, the contextís admin-bw value cannot be set to 0 and the no admin-bw command will fail.
This command also supports an optional black-hole-rate kbps command that defnes at which current rate a channel should be placed in the black-hole state. This is intended to provide a protection mechanism against multicast channels that exceed a reasonable rate and cause outages in other channels.
The no form of the command restores the default bandwidth activity monitoring setting (dynamic or null depending on the context).
The use-admin-bw and
dynamic keywords are mutually exclusive and one must be specified when executing the
bw-activity command. The
use-admin-bw keyword indicates the channels current ingress bandwidth should be derived from the
admin-bw setting. The
admin-bw setting must not currently be set to 0 for the
use-admin-bw setting to succeed.
The
dynamic keyword indicates that the multicast ingress path manager should use the dynamic rate table (as defined in the bandwidth-policy) to derive the channels current ingress rate.
This command defines the channels multicast CAC channel type, either mandatory or
optional. The cac-type command is supported for future interaction with the egress multicast CAC manager policy. The multicast CAC manager always reserves egress bandwidth for mandatory channels within a bundle, while optional channels are only given bandwidth when a join is received.
The explicit-sf-path command in the bundle context defines the initial path for all channels associated with the bundle unless the channel has an overriding explicit-sw-path defined in the channel context. The channel context may also be overridden by the explicit-sf-path command in the source-override context. The channel and source-override explicit-sf-path settings default to null (undefined) and have no effect unless explicitly set.
The no form of the command restores default path association behavior (dynamic or null depending on the context).
The no form of the command restores the default preference value (0 or null depending on the context).
The no form of the command removes the static RPF check.
The no form of the command removes the specifed sender override context from the channel range.
The cong-priority-threshold value is also used by the multicast CAC manager to derive the class of a channel matched by the multicast information policy. Channels with a preference less than the configured threshold will be treated as ëlowí class and channels with a preference equal to or greater than the threshold will be treated as ëhighí class.
Changing the cong-priority-threshold value causes all channels congestion priority to be reevaluated. Both the ingress multicast path managers and multicast CAC managers must be updated.
The no form of the command restores the default congestion priority preference threshold value.
The no form of the command restores the default ECMP optimization preference threshold value.
If mc-ecmp-balance is enabled, a redistribution may be triggered whenever a interface is added to an ECMP link.
If mc-ecmp-balance is enabled, a period re-balance may be configured that re-optimizes the distribution as some multicast streams may have been removed from the ECMP link.
The no form of the command removes the re-balancing capability from the configuration.
The no form of the command reverts to default.
The no form of the command disables the IMPM monitoring.
The no form of the command reverts to the default values.
The no form of the command reverts to the default values.
The no form of the command reverts to the default.
Any route policy entry without the action command will be considered incomplete and will be inactive.
The no form of the command deletes the action context from the entry.
The no form of the command removes an explicit bandwidth policy from a forwarding plane or MDA and restores the default bandwidth policy.
