Catalyst 3560 Switch Software Configuration Guide, Rel. 12.2(25)SEE

Configuring SDM Templates

This chapter describes how to configure the Switch Database Management (SDM) templates on the Catalyst 3560 switch.

Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release.

This chapter consists of these sections:

•Understanding the SDM Templates

•Configuring the Switch SDM Template

•Displaying the SDM Templates

Understanding the SDM Templates

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 access template to obtain maximum ACL usage.

To allocate ternary content addressable memory (TCAM) resources for different usages, the switch SDM templates prioritize system resources to optimize support for certain features. You can select SDM templates for IP Version 4 (IPv4) to optimize these features:

•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.

•Access—The access template maximizes system resources for access control lists (ACLs) to accommodate a large number of ACLs.

Table 7-1 lists the approximate numbers of each resource supported in each of the three templates for a desktop switch.

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 impacting 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

If the switch is running the advanced IP services image, you can select SDM templates to support IP Version 6 (IPv6). For more information about IPv6 and how to configure IPv6 routing, see "Configuring IPv6 Unicast Routing."

This software release does not support IPv6 multicast routing and QoS. This release does support IPv6 Multicast Listener Discovery (MLD) snooping.

This software release does not support Policy-Based Routing (PBR) when forwarding IPv6 traffic. The software supports IPv4 PBR only when the dual-ipv4-and-ipv6 routing template is configured.

Note Though visible in the command-line help strings for all switches, the dual-ipv4-and-ipv6 option is only supported in the advanced IP services image.

The dual IPv4 and IPv6 templates allow the switch to be used in dual stack environments (supporting both IPv4 and IPv6). Using the dual stack templates results in less TCAM capacity allowed for each resource. Do not use them if you plan to forward only IPv4 traffic.

These SDM templates support IPv4 and IPv6 environments:

•Dual IPv4 and IPv6 default template—supports Layer 2, multicast, routing, QoS, and ACLs for IPv4; and Layer 2, routing, and ACLs for IPv6 on the switch

•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 on the switch

•Dual IPv4 and IPv6 VLAN template—supports basic Layer 2, multicast, QoS, and ACLs for IPv4, and basic Layer 2 and ACLs for IPv6 on the switch.

Note An IPv4 route requires only one TCAM entry. Because of the hardware compression scheme used for IPv6, an IPv6 route can take more than one TCAM entry, reducing the number of entries forwarded in hardware. For example, for IPv6 directly connected IP addresses, the desktop template might allow less than two thousand entries.

Table 7-2 defines the approximate feature resources allocated by each new template. Template estimations are based on a switch with 8 routed interfaces and approximately 1000 VLANs.

Configuring the Switch SDM Template

These sections contain this configuration information:

•Default SDM Template

•SDM Template Configuration Guidelines

•Setting the SDM Template

Default SDM Template

The default template is the default desktop template.

SDM Template Configuration Guidelines

Follow these guidelines when selecting and configuring 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. The sdm prefer routing global configuration command prevents other features from using the memory allocated to unicast routing in the routing template.

•If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message is generated.

•Using the dual stack templates results in less TCAM capacity allowed for each resource, so do not use if you plan to forward only IPv4 traffic.

Setting the SDM Template

Beginning in privileged EXEC mode, follow these steps to use the SDM template to maximize feature usage:

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:

Switch# show sdm prefer 

 The current template is "desktop routing" template. 

 The selected template optimizes the resources in 

 the switch to support this level of features for 

 8 routed interfaces and 1024 VLANs. 

  number of unicast mac addresses:            3K 

  number of igmp groups + multicast routes:   1K 

  number of unicast routes:                   11K 

    number of directly connected hosts:       3K 

    number of indirect routes:                8K 

  number of qos aces:                         512 

 number of security aces:                    1K 

 On next reload, template will be "desktop vlan" template.

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.

Switch(config)# sdm prefer routing

Switch(config)# end

Switch# reload

Proceed with reload? [confirm]

This example shows how to configure the IPv4-and-IPv6 default template on a desktop switch:

Switch(config)# sdm prefer dual-ipv4-and-ipv6 default

Switch(config)# exit

Switch# reload

Proceed with reload? [confirm]

Displaying the SDM Templates

Use the show sdm prefer privileged EXEC command with no parameters to display the active template.

Use the show sdm prefer [access | default | dual-ipv4-and-ipv6 {default | vlan} |routing | vlan] privileged EXEC command 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.

Switch# show sdm prefer

 The current template is "desktop default" template.

 The selected template optimizes the resources in

 the switch to support this level of features for

 8 routed interfaces and 1024 VLANs.

  number of unicast mac addresses:             6K

  number of igmp groups + multicast routes:    1K

  number of unicast routes:                    8K

    number of directly connected hosts:        6K

    number of indirect routes:                 2K

  number of policy based routing aces:         0

  number of qos aces:                          512

  number of security aces:                     1K

This is an example of output from the show sdm prefer routing command entered on a switch:

Switch# show sdm prefer routing

"desktop routing" template:

 The selected template optimizes the resources in

 the switch to support this level of features for

 8 routed interfaces and 1024 VLANs.

  number of unicast mac addresses:             3K

  number of igmp groups + multicast routes:    1K

  number of unicast routes:                    11K

    number of directly connected hosts:        3K

    number of indirect routes:                 8K

  number of policy based routing aces:         512

  number of qos aces:                          512

  number of security aces:                     1K

This is an example of output from the show sdm prefer dual-ipv4-and-ipv6 default command entered on a switch:

Switch# show sdm prefer dual-ipv4-and-ipv6 default

 "desktop IPv4 and IPv6 default" template:

 The selected template optimizes the resources in

 the switch to support this level of features for

 8 routed interfaces and 1024 VLANs.

  number of unicast mac addresses:                  2K

  number of IPv4 IGMP groups + multicast routes:    1K

  number of IPv4 unicast routes:                    3K

    number of directly-connected IPv4 hosts:        2K

    number of indirect IPv4 routes:                 1K

  number of IPv6 multicast groups:                  1K

  number of directly-connected IPv6 addresses:      2K

  number of indirect IPv6 unicast routes:           1K

  number of IPv4 policy based routing aces:         0

  number of IPv4/MAC qos aces:                      512

  number of IPv4/MAC security aces:                 1K

  number of IPv6 policy based routing aces:         0

  number of IPv6 qos aces:                          510

  number of IPv6 security aces:                     510