basic-slice

FlexE interfaces of the same main interface type or belonging to the same GroupId can construct basic interfaces and slice interfaces.

Network slicing interfaces are classified into basic interfaces and slice interfaces, which are defined as follows:

1. A basic interface is used to carry address prefixes and is used for route calculation. It can also be used as a slice interface.
2. A slice interface does not have an address prefix. Only the network slice to which the interface is assigned is specified.
   When traffic is diverted to a basic interface, the local device searches for a slice interface with the same ID on the basic interface based on the network slice ID carried in the packet and forwards the packet through the corresponding slice interface.

A basic interface and a slice interface may be constructed on a same physical main interface.

Network slicing interfaces are classified into basic interfaces and slice interfaces, which are defined as follows:

1. A basic interface is used to carry address prefixes and is used for route calculation. It can also be used as a slice interface.
2. A slice interface does not have an address prefix. Only the network slice to which the interface is assigned is specified.
   When traffic is diverted to a basic interface, the local device searches for a slice interface with the same ID on the basic interface based on the network slice ID carried in the packet and forwards the packet through the corresponding slice interface.

The rules for configuring the basic-slice command are as follows:

1. The ipv6 enable command must be run first.
2. The configured basic slice ID must exist. That is, the network-slice data-plane or network-slice flex-channel command must be run on other interfaces of the same physical interface (with the same group ID of FlexE type).
3. If the basic-slice command has been run on a FlexE interface, the IPv6 global address cannot be configured.
4. The network-slice data-plane or network-slice flex-channel command cannot be run before the basic-slice command is run on an interface.
5. The basic slice configuration on a FlexE interface is mutually exclusive with the following commands: mpls, isis enable, isis ipv6 enable, ospf enable, ospfv3 area, rip enable, ripng enable, pim sm, igmp enable, pim ipv6 sm, mld enable, mac-address, ip address, ip address unnumbered interface, ipv6 address, ipv6 address anycast, ipv6 address eui-64, dot1q termination vid, qinq termination l2, and ip binding vpn-instance.
6. When a non-FlexE interface is configured as a slice interface, the basic slice configuration and the ip binding vpn-instance command are mutually exclusive.
7. If the network-slice data-plane or network-slice flex-channel command has been configured on an interface, the basic-slice command cannot be configured.
8. Basic interfaces support IPv6 MTU configuration. The slice interface inherits the IPv6 MTU of the basic interface and does not use the IPv6 MTU configured by itself.

The rules for configuring the basic-slice command are as follows:

1. The ipv6 enable command must be run first.
2. The configured basic slice ID must exist. That is, the network-slice data-plane or network-slice flex-channel command must be run on other interfaces of the same physical interface.
3. The network-slice data-plane or network-slice flex-channel command cannot be run before the basic-slice command is run on an interface.
4. When a interface is configured as a slice interface, the basic slice configuration and the ip binding vpn-instance command are mutually exclusive.
5. If the network-slice data-plane or network-slice flex-channel command has been configured on an interface, the basic-slice command cannot be configured.
6. Basic interfaces support IPv6 MTU configuration. The slice interface inherits the IPv6 MTU of the basic interface and does not use the IPv6 MTU configured by itself.