Longest Prefix Match (LPM) Table and IPv6 /65 – /128 support
Two partitions are available.
• Partition I with IPv6 /65 – /128 route prefix. Doesn’t support IPv4 entries in the current release.
• Partition II with IPv6 0/0 – /64 route prefix and IPv4 0/0 -0/32 route prefix entries.
• Number of entries in Partition II will be reduced based on the number of entries configured in
Partition I.
• Partitioning will be applied well before the system initialization. This will be done using the NVRAM.
• Dell Networking OS provides CLI for enabling the partition. Configuration will be stored in NVRAM
when the operator saves the configuration.
• Partition will take effect only after the switch reboot. During the reboot Dell Networking OS reads the
partition configuration from NVRAM and uses the same for partitioning the LPM.
• A command has been introduced to partition the LPM to support provisioning of IPv6 /65 to /128
route prefixes.
To support /65 – /128 IPv6 route prefix entries, Dell Networking OS needs to be programmed with /65
- /128 bit IPv6 support. The number of entries as well needs to be explicitly programmed. This number
can be1K, 2K, or 3K granularity.
On the S6000 platform, for IPv6 /65 to /128 will consume the same storage banks which is used by the
L3_DEFIP table. Once the IPv6 128 bit is enabled, number of entries in L3_DEFIP will be reduced.
LPM partitioning will take effect after reboot of the box. This is because the SDK does the LPM
partitioning during the chip initialization.
The longest prefix match (LPM) table on the S6000 platform supports different types of prefixes for IPv6
and IPv4. The route table, also called the LPM table, is divided into the following three logical tables:
1.
IPv4 32-bit LPM table (Holds IPv4 Prefixes)
2.
IPv6 64-bit LPM table (Holds IPv6 Prefixes less than /65 Prefix Length)
3.
IPv6 128-bit LPM table (Holds IPv6 Prefixes greater than /64 Prefix Length)
The LPM table, which is 8K in size, is a dedicated table. It comprises eight ternary content addressable
memory (CAM) blocks, with each block being 1K in size. The table can contain 16KIPv4 route entries or
8K IPv6 route entries (less than /65 prefix-length) or 3K IPv6 route entries (greater than /64 prefix-length).
You can configure the LPM table with one of the following partitions to support the IPv4 and IPv6 prefix
route entries:
• Partition 1: IPv6 128-bit LPM entries can be stored in this partition. IPv4 and 64-bit IPv6 entries cannot
be saved in this partition.
• Partition 2: IPv4 LPM and 64-bit IPv6 LPM entries can be stored in this partition.
The platforms (S6000) useS presently only IPv6 /0 – 0/64 prefix route entries. Support for /0 – /128 IPv6
prefix route entries is available, although they are not utilized. A total of eight pools or regions are present
with each region containing 1024 210-bit entries (supports up to 0/64 prefix). To support up to /128
prefixes, you must use 2 banks (410-bit entries). It is necessary to partition the LPM.
IPv6 Routing
439
Содержание S6000-ON
Страница 1: ...Dell Configuration Guide for the S6000 ON System 9 9 0 0 ...
Страница 505: ...Figure 60 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 505 ...
Страница 508: ...Figure 62 Inspecting a LAG Port on BRAVO Using the show interface Command 508 Link Aggregation Control Protocol LACP ...
Страница 509: ...Figure 63 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 509 ...
Страница 552: ...mac address table static multicast mac address vlan vlan id output range interface 552 Microsoft Network Load Balancing ...
Страница 557: ...Figure 80 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 557 ...
Страница 558: ...Figure 81 Configuring PIM in Multiple Routing Domains 558 Multicast Source Discovery Protocol MSDP ...
Страница 562: ...Figure 83 MSDP Default Peer Scenario 1 562 Multicast Source Discovery Protocol MSDP ...
Страница 563: ...Figure 84 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 563 ...
Страница 564: ...Figure 85 MSDP Default Peer Scenario 3 564 Multicast Source Discovery Protocol MSDP ...
Страница 665: ...Policy based Routing PBR 665 ...
Страница 672: ...ip pim bsr border Remove candidate RP advertisements clear ip pim rp mapping 672 PIM Sparse Mode PIM SM ...
Страница 818: ...Figure 110 Single and Double Tag TPID Match 818 Service Provider Bridging ...
Страница 819: ...Figure 111 Single and Double Tag First byte TPID Match Service Provider Bridging 819 ...
Страница 995: ...Figure 140 Setup OSPF and Static Routes Virtual Routing and Forwarding VRF 995 ...