Login
- Table of Contents
-
- 17-Network Management and Monitoring Configuration Guide
- 00-Preface
- 01-Information center configuration
- 02-Flow log configuration
- 03-Fast log output configuration
- 04-NetStream configuration
- 05-Cloud connection configuration
- 06-Mirroring configuration
- 07-Packet capture configuration
- 08-NQA configuration
- 09-Track configuration
- 10-BFD configuration
- 11-Monitor Link configuration
- 12-Smart Link configuration
- 13-Interface backup configuration
- 14-Interface collaboration configuration
- 15-System maintenance and debugging configuration
- 16-NTP configuration
- 17-EAA configuration
- 18-Process monitoring and maintenance configuration
- 19-NETCONF configuration
- 20-CWMP configuration
- 21-SNMP configuration
- 22-RMON configuration
- 23-Event MIB configuration
- 24-Process placement configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 14-Interface collaboration configuration | 83.75 KB |
Contents
Configuring interface collaboration
How interface collaboration works
Restrictions and guidelines: Interface collaboration configuration
Interface collaboration tasks at a glance
Prerequisites for interface collaboration
Creating a collaboration group
Configuring collaboration group member interfaces
Configuring a collaboration group member interface in collaboration group view
Configuring a collaboration group member interface in interface view
Configuring the delay for the member interfaces in a collaboration group to come up
Removing ineffective member interfaces from all collaboration groups
Display and maintenance commands for interface collaboration
Configuring interface collaboration
About interface collaboration
The interface collaboration feature assigns different interfaces on a device to a collaboration group and associates the states of these interfaces. All member interfaces in a collaboration group can or cannot transmit packets at the same time. This feature is typically used to associate the states of downlink and uplink interfaces.
Typical application
As shown in Figure 1, Device C accesses the core network through Device B. When Interface B1 goes down, the switchover of traffic from Device C to Device D is slow because Interface B2 is still up.
If Interface B1 and Interface B2 belong to one collaboration group, Device B brings down Interface B2 when Interface B1 goes down to achieve fast traffic switchover. Similarly, the device brings down Interface B1 when Interface B2 goes down.
Figure 1 Interface collaboration application scenario
How interface collaboration works
The interface collaboration feature works as follows:
· When any member interface in a collaboration group goes down, the device sets all other member interfaces in the collaboration group to the Collaboration-down state. The state of the collaboration group is down, and no member interfaces in the collaboration group can transmit packets.
· When any member interface in DOWN or Collaboration-down state comes up, the device attempts to bring up all other member interfaces in the collaboration group.
¡ If all other member interfaces come up in 10 seconds, the collaboration group comes up. All member interfaces in the collaboration group can transmit packets.
¡ If any member interface cannot come up in 10 seconds, the device sets that member interface to DOWN state and sets all other member interfaces to the Collaboration-down state. The collaboration group goes down, and no member interfaces in the collaboration group can transmit packets.
Restrictions and guidelines: Interface collaboration configuration
This feature cannot be used together with the external security service bypass feature. For more information about external security service bypass see Layer 2 forwarding configuration in Layer 2—LAN Switching Configuration Guide.
Interface collaboration tasks at a glance
To configure interface collaboration, perform the following tasks:
· Creating a collaboration group
· Configuring collaboration group member interfaces
· (Optional.) Configuring the delay for the member interfaces in a collaboration group
· (Optional.) Removing ineffective member interfaces from all collaboration groups
Prerequisites for interface collaboration
Before configuring interface collaboration, you must enable Monitor Link globally (see Network Monitoring and Management Configuration Guide).
Creating a collaboration group
1. Enter system view.
system-view
2. Create a collaboration group and enter collaboration group view.
collaboration-group group-id
By default, no collaboration groups exist.
Configuring collaboration group member interfaces
Restrictions and guidelines
An interface can belong to only one collaboration group.
For a collaboration group to work correctly, do not assign its member interfaces to a redundancy group.
Do not add both an aggregate interface and its member ports to the same collaboration group.
Do not add both Selected ports and Unselected ports in a dynamic aggregation group to the same collaboration group.
If you have configured a member interface as the uplink/downlink interface of a monitor link group, do not configure any other member interface in the same collaboration group as the downlink/uplink interface of any monitor link group.
You can assign only one interface of a link to a collaboration group.
You can configure member interfaces for a collaboration group in collaboration group view or interface view. Configurations made in these views have the same effect.
Configuring a collaboration group member interface in collaboration group view
1. Enter system view.
system-view
2. Enter collaboration group view.
collaboration-group group-id
3. Configure an interface as a member of the collaboration group.
port interface-type interface-number
By default, no member interfaces exist in a collaboration group.
Configuring a collaboration group member interface in interface view
1. Enter system view.
system-view
2. Enter interface view.
interface interface-type interface-number
3. Configure the interface as a member of a collaboration group.
port collaboration-group group-id
By default, an interface is not a collaboration group member.
Configuring the delay for the member interfaces in a collaboration group to come up
About this task
By default, member interfaces in a collaboration group come up and forward service traffic immediately after the device restarts. Traffic loss occurs if the service modules have not returned to normal state.
Perform this task to enable the member interfaces to come up after a configurable delay time upon a device restart.
Procedure
1. Enter system view.
system-view
2. Enter collaboration group view.
collaboration-group group-id
3. Configure the delay for the member interfaces in a collaboration group to come up.
up-delay delay
By default, the delay time is 0 seconds. The member interfaces come up as soon as the device restarts.
Removing ineffective member interfaces from all collaboration groups
About this task
A member interface in a collaboration group becomes ineffective when the card that hosts the interface is removed or changed to another slot or the ID of the IRF member device that hosts the interface changes. This task prevents an ineffective interface from causing all other member interfaces in the same collaboration group to go down.
An ineffective interface cannot be automatically assigned to the original collaboration group when its hosting card is reinstalled or changed back to the original slot or the IRF member ID is changed back to the original ID. You must assign it to the original collaboration group manually.
Procedure
1. Enter system view.
system-view
2. Enter collaboration group view.
collaboration-group clean
Display and maintenance commands for interface collaboration
Execute the display command in any view:
|
Task |
Command |
|
Display collaboration group information. |
display collaboration-group { group-id | all } [ verbose ] |
