You can use SDM
templates to configure system resources in the
Switch
to optimize support for specific features, depending on how the
Switch
is used in the network. You can select a template to provide maximum system
usage for some functions; for example, use the default template to balance
resources, and use the access template to obtain maximum ACL usage. The
Switch
SDM templates allocate system hardware resources for different uses.
You can select SDM
templates for IP Version 4 (IPv4) to optimize these features on
Switch
running the IP Base or IP Services feature set:
Note |
When the
Switch
is running the LAN Base feature set, do not select a routing template (sdm prefer routing). The
routing values shown in the templates are not valid on the
Switch.
To configure IPv4 static routing on
Switch
running the LAN Base feature set, you must use the default template.
|
-
Routing—The
routing template maximizes system resources for unicast routing, typically
required for a router or aggregator in the center of a network.
-
VLANs—The VLAN
template disables routing and supports the maximum number of unicast MAC
addresses. It would typically be selected for a Layer 2
Switch.
-
Default—The
default template gives balance to all functions.
Note |
Use this
template when configuring IPv4 static routing on SVIs on
Switch
running the LAN Base feature set. You can configure up to 16 static routes.
|
-
Access—The access
template maximizes system resources for access control lists (ACLs) to
accommodate a large number of ACLs.
The
Switch
also supports multiple dual IPv4 and IP Version 6 (IPv6) templates for
environments with both types of traffic.
Note |
Although these
templates are visible on all
Switch,
the resources on
Switch
running the LAN Base feature do not match those shown in the templates:
-
Switch
running the LAN Base feature set support only 255 VLANs, not 1024 as shown in
all templates.
-
Although the
routing template is visible, the template is not supported. The LAN Base
feature set supports IPv4 static routing on SVIs (up to 16 static routes) and
the
Switch
must be running the default template.
|
Table 1. Approximate Number
of Feature Resources Allowed by the Templates
Resource
|
Access
|
Default
|
Routing
|
VLAN
|
Unicast MAC addresses
|
4 K
|
6 K
|
3 K
|
12 K
|
Internet Group Management Protocol (IGMP) groups and multicast
routes
|
1 K
|
1 K
|
1 K
|
1 K
|
Unicast routes
|
6 K
|
8 K
|
11 K
|
0
|
|
4 K
|
6 K
|
3 K
|
0
|
|
2 K
|
2 K
|
8 K
|
0
|
Policy-based routing access control entries (ACEs)
|
0.5 K
|
0
|
0.5 K
|
0
|
IPv4 or MAC QoS ACEs
|
0.5 K
|
1 K
|
1 K
|
0.5 K
|
IPv4 or MAC security ACEs
|
2 K
|
1 K
|
1 K
|
1 K
|
VLANs
|
1 K
|
|
|
1 K
|
Number of IPv6 security ACEs
|
52
|
60
|
58
|
60
|
The table represents
approximate hardware boundaries set when a template is selected. If a section
of a hardware resource is full, all processing overflow is sent to the CPU,
seriously impacting
Switch
performance.
In mixed stack scenarios such as lotr and pixar, the default template
will be enabled with IPv6 FHS on pixar, but not on lotr. You cannot have mixed
stack with default/vlan/routing/access templates with IPv6 FHS enabled.
You can use IPv6 FHS
features such as RA Guard, DHCP Guard and NDP snooping by using the entries
reserved for IPv6 Security Aces. Other IPv6 features such as IPv6 QoS or other
IPv6 FHS features such as Source Guard will not work with this template.