Creates or removes egress-group and defines how traffic is forwarded to end devices.
Config mode
A maximum of 64 egress objects can be added to an egress-group.
A valid <egress-name> must be provided. all is a reserved name and cannot to be used for configuration.
An egress-group name must be unique. An error is thrown if you try to use the same name for an egress group as for an egress.
The following reserved keywords cannot be used as name identifiers: all, ingress-group, egress, egress-group, match, list, access-list, route-map, and listener-policy.The no egress-group name command clears all objects of the specified egress group.
| Message | Reason |
|---|---|
| Error: egress-group name identifier must start with an alphabetic character or an underscore. | Egress-group name begins with non-alphabetic character or does not begin with an underscore. |
| Error: egress-group name identifier cannot exceed 64 characters | Egress-group name is longer than 64 characters. |
| Error: egress-group name identifier must be an arbitrary sequence of alphabets, numerals, underscores, hyphens or dots. | Egress-group name contains invalid characters. |
| Error: egress-group name identifier must not be reserved keyword "egress-group". | Egress-group name includes the reserved word egress-group |
| Error: egress Group is bounded to route map. | Deletion of an egress-group is not allowed if it is mapped in a route-map. |
| Error: Egress-group and egress cannot use same name. An egress object with same name already exists | Egress-group name cannot be same as egress. |
The following example configures the egress group.
device# configure terminal device(config)# egress-group egg123 (config-egress-group)# set egress egress-one (config-egress-group)# device# show running-config egress-group egress-group egg123 egress-one