Licensing Requirements and Limitations for IP Routing Table Management

Involved Network Elements

Other network elements are not required.

Licensing Requirements

The number of IPv4 FIB entries supported by an S5720-HI and S5730-HI depends on licenses. For the maximum number of IPv4 FIB entries, contact the equipment supplier.

For details about how to apply for a license, see Obtaining Licenses in the S1720, S5700, and S6700 Series Switches License Usage Guide.

Feature Support in V200R019C10

All models of S2720, S5700, and S6700 series switches support IP Routing Table Management.

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

When the S6720-SI, S6720S-SI, S5730-SI, S5730S-EI, S6720-LI, or S6720S-LI functions as a route forwarding device, it is recommended that they be used in the following typical route forwarding scenarios:

IPv4 routes: Among all routing entries, there are no more than 1500 types of 16-bit prefixes or no more than 200 types of 8-bit prefixes. In VPN scenarios, the same prefix is counted multiple times in different VPNs.
IPv6 routes: Among all routing entries, there are no more than 1200 types of 32-bit prefixes or no more than 3 types of 8-bit prefixes. In VPN scenarios, the same prefix is counted multiple times in different VPNs.
Routes with a mask less than 64 bits are recommended, and routes with a 128-bit mask are not recommended. It is not recommended that you use a large number of Layer 3 interfaces to configure IPv6 services. This is because two routes will be generated for an IPv6 Layer 3 interface: one is a network segment route and the other is a 128-bit local route, and this 128-bit local route occupies many hardware resources.

For example, there are four IP addresses: 10.1.1.1, 10.1.2.1, 10.2.1.1, 192.168.1.1

There are three types of 16-bit prefixes: 10.1, 10.2, and 192.168.
There are two types of 8-bit prefixes: 10 and 192.

When the preceding switches are used as route forwarding devices in scenarios other than the preceding typical scenarios, collect log information, configuration, and routing entries if route forwarding failures occur, and contact technical support personnel.