7210 SAS-M, T, R6, R12, Mxp, Sx, S Basic System
Configuration Guide
System Management
Edition: 01 3HE 16132 AAAB TQZZA 563
max-ip-subnets
Syntax max-ip-subnets number
no max-ip-subnets
Context configure>system>resource-profile>router
configure>system>global-res-profile>router
Supported
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures the number of directly connected IP interfaces and subnets (both
IPv4 and IPv6) the user plans to use on the node, so that only the requisite number of entries
in the L3 forwarding table are allocated. On the 7210 SAS platforms, the hardware L3
forwarding table (that is, the IP IFB) stores the IP routes (both IPv4 and IPv6) received from
routing peers and also stores the IP address prefix for the directly connected interfaces. The
rest are available for use by IP routes received from peers.
This command provides the flexibility to earmark resources based on the number of directly
connected interfaces required on the node, allowing the user to decrease the number of
resources for directly connected subnets and consequently increase the number of entries
available for IP routes received from peers. See the description of the max-ipv6-routes
command for detailed information about IP route allocation.
Default no max-ip-subnets (Software allocates a fixed number of entries towards this to maintain
backward compatibility with releases prior to release 7.0.R3).
Note: The configure>system>resource-profile>router context is supported on the
7210 SAS-M, 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE: standalone, and
7210 SAS-Sx 10/100GE.
The configure>system>global-res-profile>router context is supported on the
7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-Sx/S 1/10GE: standalone-VC.
Note:
• Each IPv4 subnet configured on the node requires 1 entry and each IPv6 subnet
configured on the node requires 2 entries. Each IPv6 /64-bit address prefix requires
twice the amount of space needed for an IPv4 address prefix. Additionally, the user
must account for resources required for IPv6 primary and secondary addresses
assigned to an IPv6 interface.
• The number of entries available for IP routes received from a peer is equal to the total
number of L3 forwarding entries supported for the platform subtracted by the number
of entries specified by this command.
• The software allocates entries from this pool on a FCFS (first come first serve) model
based on the order of configuration of IP interfaces. An error is generated when the
maximum limit is reached.