FlexE clients correspond to externally observed user interfaces. Each FlexE client can be flexibly allocated bandwidth from a group resource pool, and the bandwidth can be adjusted.
Context
To ensure that the FlexE clients on both ends can communicate with each other, you need to configure the same ID and bandwidth for them.
Table 1 Numbers of physical ports that can be added to the same group and port-id value ranges for different subcard modelsNumbers of Physical Ports that Can Be Added to the Same Group
|
port-id Value Range
|
|---|
8,9,12,20
|
1000-3000
|
10,11,14,21
|
1000-3000
|
13,16,17,22
|
1000-3000
|
15,18,19,23
|
1000-3000
|
24,28,29
|
1000-3000
|
25,30,31
|
1000-3000
|
Procedure
- Run system-view
The system view is displayed.
- Run flexe client-instance clientindex [ flexe-group groupIndex flexe-type { cross | full-function } [ port-id portid ] ]
A FlexE client is created and its view is displayed.
- Run flexe-clientid clientid
An ID is configured for the FlexE client.
- Configure bandwidth for the FlexE client.
- If the bandwidth mode is configured for the FlexE card, run the flexe-bandwidth { 1 | 2 | 3 | 4 | bandwidth-value } command to configure bandwidth for the FlexE client.
- If the timeslot mode is configured for the FlexE card, run the binding interface interface-type interface-number time-slot timeslot-list [ sub-time-slot subtime-slot ] command to bind one or more sub-timeslots to the FlexE client. The bound sub-timeslots constitute the bandwidth of the FlexE client.
- (Optional) Run minimal available bandwidth percent
The minimum available bandwidth percentage is configured for the FlexE client.
- Run commit
The configuration is committed.