- Preface
- Overview
- Using the Command-Line Interface
- Configuring the Switch Alarms
- Assigning the Switch IP Address and Default Gateway
- Configuring Cisco IOS Configuration Engine
- Clustering Switches
- Administering the Switch
- Configuring PTP
- Configuring PROFINET
- Configuring SDM Templates
- Configuring Switch-Based Authentication
- Configuring IEEE 802.1x Port-Based Authentication
- Configuring Web-Based Authentication
- Configuring SGT Exchange Protocol over TCP (SXP) and Layer 3 Transport
- Configuring Interface Characteristics
- Configuring Smartports Macros
- Configuring VLANs
- Configuring VTP
- Configuring Voice VLAN
- Configuring Private VLANs
- Configuring IEEE 802.1Q and Layer 2 Protocol Tunneling
- Configuring STP
- Configuring MSTP
- Configuring Optional Spanning-Tree Features
- Configuring Resilient Ethernet Protocol
- Configuring Flex Links and the MAC Address-Table Move Update Feature
- Configuring DHCP Features and IP Source Guard
- Configuring Dynamic ARP Inspection
- Configuring Port-Based Traffic Control
- Configuring SPAN and RSPAN
- Configuring LLDP, LLDP-MED, and Wired Location Service
- Configuring CDP
- Configuring UDLD
- Configuring RMON
- Configuring System Message Logging
- Configuring SNMP
- Configuring Embedded Event Manager
- Configuring Network Security with ACLs
- Configuring QoS
- Configuring EtherChannels and Link-State Tracking
- Configuring IP Unicast Routing
- Configuring IPv6 Unicast Routing
- Configuring IPv6 Unicast Routing
- Configuring IPv6 ACLs
- Configuring IPv6 MLD Snooping
- Configuring HSRP and VRRP
- Configuring Cisco IOS IP SLAs Operations
- Configuring Enhanced Object Tracking
- Configuring Web Cache Services By Using WCCP
- Configuring Fallback Bridging
- Troubleshooting
- Working with the Cisco IOS File System, Configuration Files, and Software Images
- Unsupported Commands in Cisco IOS Release 15.2(2)E
- Index
Understanding the SDM Templates
Switch Database Management (SDM) templates allocate system hardware resources in order to support specific features on the switch. You can select an SDM template to provide maximum system usage for specific functions; for example, you can use the default template to balance system resources and use the LAN base routing template to maximize the number of static routes on switch virtual interfaces (SVIs).
You can select SDM templates to best support these features:
- Default—Gives balance to all Layer 2 functions.
- LAN base routing—Supports IPv4 unicast routes for configuring static routing SVIs.
- Dual IPv4 and IPv6—Allows the switch to be used in dual stack environments; that is, supporting both IPv4 and IPv6 traffic. You should not use this template if you plan to forward only IPv4 traffic. See the “Dual IPv4 and IPv6 SDM Templates” section.
- QoS—Maximizes system resources for quality of service (QoS) access control entries (ACEs).
- Routing—The routing template maximizes system resources for IPv4 unicast routing, which is typically required for a router or aggregator in the center of a network. To configure the routing template, the switch must be running the IP services image.
Note The switch must be running Cisco IOS Release 12.2(52)SE or later to configure the routing template.
The first eight rows in the tables (unicast MAC addresses through security ACEs) represent 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 degrading switch performance. The last row is a guideline used to calculate hardware resource consumption related to the number of Layer 2 VLANs on the switch.
Dual IPv4 and IPv6 SDM Templates
These SDM templates support IPv4 and IPv6 environments:
- Dual IPv4 and IPv6 default template—supports Layer 2, QoS, and ACLs for IPv4 and Layer 2, IPv6 host, and ACLs for IPv6.
- Dual IPv4 and IPv6 routing template—supports Layer 2, multicast, routing (including policy-based routing), QoS, and ACLs for IPv4 and Layer 2, routing, and ACLs for IPv6.
Note The dual IPv4 and IPv6 templates are available only on switches running the IP services image.
Note This software release supports IPv4 policy-based routing (PBR) only; it does not support PBR when forwarding IPv6 traffic.
IPv6 policy-based routing ACEs2 |
||
1.Template estimates are based on a switch with 8 routed interfaces and approximately 1000 VLANs. |
Configuring the Switch SDM Template
These sections contain this configuration information:
SDM Template Configuration Guidelines
Follow these guidelines when selecting and configuring SDM templates:
- When you select and configure SDM templates, you must reload the switch for the configuration to take effect.
- Use the sdm prefer vlan global configuration command only on switches intended for Layer 2 switching with no routing. When you use the VLAN template, no system resources are reserved for routing entries, and any routing is done through software. This overloads the CPU and severely degrades routing performance.
- Do not use the routing template if you do not have routing enabled on your switch. Use the sdm prefer routing global configuration command to prevent other features from using the memory allocated to unicast routing in the routing template.
- If you download the IP services image and plan to use Layer 3 functionality, you must use the routing SDM template.
- If you try to configure IPv6 features without first selecting a dual IPv4 and IPv6 template, a warning message is generated.
- The dual IPv4 and IPv6 templates can result in less ternary content addressable memory (TCAM) being allocated to each resource, which reduces the number of entries forwarded in hardware. You should not use these templates if you plan to forward only IPv4 traffic.
Setting the SDM Template
Beginning in privileged EXEC mode, follow these steps to configure an SDM template:
After the system reboots, you can use the show sdm prefer privileged EXEC command to verify the new template configuration. If you enter the show sdm prefer command before you enter the reload privileged EXEC command, the show sdm prefer command shows the template currently in use and the template that will become active after a reload.
This is an example of an output display when you have changed the template and have not reloaded the switch:
To return to the default template, use the no sdm prefer global configuration command.
This example shows how to configure a switch with the routing template.
This example shows how to configure the IPv4-and-IPv6 default template on a switch:
Displaying the SDM Templates
Use the show sdm prefer command in privileged EXEC mode to display the active template.
Use the show sdm prefer [ default | dual-ipv4-and-ipv6 { default | routing } | qos | routing ] command in privileged EXEC mode to display the resource numbers supported by the specified template.
This is an example of output from the show sdm prefer command, displaying the template in use.
This is an example of output from the show sdm prefer routing command: