Specifying a traffic processing slot for a Layer 3 aggregate interface
By default, traffic on a Layer 3 aggregate interface is processed on the slot at which the traffic arrives. You can specify a traffic processing slot for all traffic on a Layer 3 aggregate interface to be processed on the same slot. If the aggregate interface contains subinterfaces, traffic on the subinterfaces is not processed on the specified slot.
You must specify a traffic processing slot for a Layer 3 aggregate interface in any of the following situations:
NAT is configured on the Layer 3 aggregate interface. For information about NAT, see Layer 3—IP Services Configuration Guide.
The member ports belong to one or multiple FIP-240 (JH137A)/FIP-300 (JG671A)/FIP-310 (JG672A) modules. The module in the specified traffic processing slot must be a FIP-240 (JH137A), FIP-300 (JG671A), or FIP-310 (JG672A) module.
The member ports belong to one or multiple FIP-600 (JG360A) modules. The module in the specified traffic processing slot must be a FIP-600 (JG360A) module.
The member ports belong to one or multiple SAP-4EXP (JG366A) modules. The module in the specified traffic processing slot must be a SAP-4EXP (JG366A) module.
To specify a traffic processing slot for a Layer 3 aggregate interface:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter Layer 3 aggregate interface view. | interface route-aggregation interface-number | N/A |
3. Specify a primary traffic processing slot for the interface. | In standalone mode:service slot slot-number In IRF mode:service chassis chassis-number slot slot-number | By default, no primary traffic processing slot is specified for an interface. |
4. Specify a backup traffic processing slot for the interface. | In standalone mode:service standby slot slot-number In IRF mode:service standby chassis chassis-number slot slot-number | By default, no backup traffic processing slot is specified for an interface. |