Table Of Contents

Group Configuration Mode Commands

(config-group) active

(config-group) add destination service

(config-group) add service

(config-group) ip address

(config-group) no

(config-group) portmap

(config-group) redundancy-l4-stateless

(config-group) remove destination service

(config-group) remove service

(config-group) suspend

(config-group) vip address

Group Configuration Mode Commands

Group configuration mode allows you to configure a group. A group is a collection of local servers that initiate flows from within the local web farm. For example, after processing a group of real audio transmitters, they all appear on the same source IP address. The CSS lets you treat a group as a virtual server with its own source IP address.

To access group configuration mode, use the group command from any mode except ACL, boot, and header-field-group configuration modes. The prompt changes to (config-group [name]). You can also use this command from group mode to access another group. For information about commands available in this mode, refer to the following commands.

Use the no form of this command to delete an existing group.

group group_name
no group existing_group_name

Syntax Description

group_name

The name of a new group you want to create or of an existing group. Enter an unquoted text string with no spaces and a maximum length of 31 characters. To see a list of existing group names, enter: group ?

(config-group) active

To activate the specified group, use the active command.

active

Related Commands

(config-group) suspend

(config-group) add destination service

To add a destination service to a source group, use the add destination command.

add destination service service_name

Syntax Description

service_name

The name of the service to add to the group. Enter an unquoted text string. To see a list of services, enter: show service ?

Usage Guidelines

You cannot use a service with the same name in other source groups or the source service list within the same source group. You can use services with duplicate addresses among destination services since the actual service is chosen through content rule selection.

If the group is active and the same service is hit through a content rule, ACL preferred service, or sorry service, the source group is used to NAT the source address.

If your topology consists of a CSS 11800 using ECMP to the servers and server port NAT configured on the services, to ensure the correct processing of packets either:

•Create source groups for the services in the content rule with the add destination service command.

•Enable Service Remapping with the persistence reset remap command.

Related Commands

show group
show service
(config-group) remove destination service

(config-group) add service

To add a source service to a source group, use the add service command.

add service service_name

Syntax Description

service_name

The name of the service to add to the group. Enter an unquoted text string. To see a list of services, enter: show service ?

Usage Guidelines

You cannot use a service with:

•The same name in other source groups or the destination service list within the same source group

•The same address as a source service on another source group

If the service matches the client, the source group is used.

Before you can add a service, you must suspend the group.

Related Commands

show group
show service
(config-group) remove service

(config-group) ip address

To specify the source IP address for the group, use the ip address command. This address is substituted for the source address in flows originating from one of the group's sources. This command's function is identical to the (config-group) vip address command.

ip address ip_address

Syntax Description

ip_address

The IP address for the group. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1).

Related Commands

show group

(config-group) no

To negate a command or set it to its default, use the no command. For information on general no commands you can use in this mode, refer to the general no command. The following options are available in group mode.

Syntax Description

no acl index	Deletes an ACL
no portmap base-port	Resets the starting SFP port number to its default value of 8192
no portmap number-of-ports	Resets the number of ports per SFP to its default value
no redundancy-l4-stateless	Disables stateless redundancy failover
no rmon-event index	Deletes an RMON event
no rmon-history index	Deletes an RMON history

(config-group) portmap

To define the starting Switch Fabric Processor (SFP) port number in a Cisco CSS chassis and the number of ports per SFP on an SFM for port mapping, use the portmap command. There are two SFPs on each SFM. A Cisco CSS 11800 can contain up to two SFMs, for a maximum of four SFPs.

Use the no form of this command to reset the starting SFP port number to its default value of 8192 or number of ports to its default value of 57216 for a CSS 11050 or 11150, or 14304 for a CSS 11800.

portmap [base-port base_number|number-of-ports number]
no portmap [base-port|number-of-ports]

Syntax Description

base-port	Defines the starting SFP port number in the Cisco CSS chassis.
base_number	The base port number. Enter a number from 8192 to 65530. The default is 8192.
number-of-ports	Defines the number of ports allowed on each Switch Fabric Processor (SFP).
number	The number of ports per SFP. Enter a number from 1 to 57216. The default for a CSS 11800 is 14304. The default for a CSS 11050 or 11150 is 57216. If you enter a number that is not a multiple of 32, the CSS rounds up the number to the next multiple of 32. Note Do not define the number of ports per SFP to exceed the number of available ports. To determine the number of available ports, subtract the base port number from 65531. For example, if the base port number is 65530, the number of available ports is 1.

Usage Guidelines

Before you can change the port mapping, you must suspend the group.

Examples

If the starting SFP port number is 8192 and the number of ports per SFP is 2016, the first SFP has a range of port numbers from 8192 to 10207, and the next SFP has a port number range from 10198 to 12207.

(config-group) redundancy-l4-stateless

To enable the Stateless Redundancy Failover feature for a source group on a redundant CSS, use the redundancy-l4-stateless command. The CSS can set up a connection for a mid-stream TCP flow, allowing TCP traffic to continue when a failure occurs at the load-balancing CSS. By default, the CSS rejects TCP sessions that do not begin with a TCP/SYN frame. Use the no form of this command to reset the default behavior of the CSS.

redundancy-l4-stateless
no redundancy-l4-stateless

Command Modes

Group configuration mode

Usage Guidelines

The Stateless Redundancy Failover feature has specific environment and configuration requirements. The environment requirements are as follows:

•Layer 3 and Layer 4 content rules with a VIP address. This feature is not supported in Layer 5 configurations.

•Source IP address load balance method only.

•CSS-to-CSS identical server and content rule configuration including:

–Content VIP address.

–Content balance method.

–Failover method.

–Service IP address, number, and order. The CSS orders services alphabetically. Apply identical service names on the master and backup CSSs.

•Visibility of identical servers to keepalive traffic from CSS to CSS. This ensures that the redistribution of the balance method does not occur in a failover event.

Redundant routes in a high availability topology surrounding the CSS are supported. However, the topology must not balance packets in a TCP/IP socket connection across more than one Ethernet port on the CSS.

IP and VIP redundant configurations are supported. The configuration requirement for each server farm is synchronization across all CSSs of:

•Membership and IP addresses of the server farms.

•Content rule VIP address. Each CSS must share the content VIP address that is used as a balance point for the server farm.

•Source group VIP address. Define each CSS with a source group VIP address as the content VIP address to NAT source addresses for packets returning from the server. In case of a failover, the source group handles connection setups for TCP/IP retransmissions that arrive at the CSS from a server. All servers on the farm must be a member of the source group.

Do not configure source groups for outbound traffic from the servers because the backup CSS does not know which ports were mapped by the source group on the master CSS.

For more detailed information on Stateless Redundancy Failover, refer to the Cisco Content Services Switch Advanced Configuration Guide.

Related Commands

show redundancy
(config) ip redundancy
(config) group
(config) interface
(config) service
(config-owner) content
(config-owner-content) redundancy-l4-stateless

(config-group) remove destination service

To remove a previously configured destination service from a source group, use the remove command.

remove destination service service_name

Syntax Description

service_name

The name of an existing service you want to remove from the group. Enter a case-sensitive unquoted text string. To see a list of services for this group, enter: show group

Related Commands

show group
show service
(config-group) add destination service

(config-group) remove service

To remove a previously configure source service from a source group, use the remove command.

remove service service_name

Syntax Description

service_name

The name of an existing service you want to remove from the group. Enter a case-sensitive unquoted text string. To see a list of services for this group, enter: show group

Usage Guidelines

Before you can remove a service, you must suspend the group.

Related Commands

show group
show service
(config-group) add service

(config-group) suspend

To suspend the specified group, use the suspend command. The group and its attributes remain the same but it no longer has an effect on flow creation.

suspend

Usage Guidelines

To reactivate the group, use the (config-group) active command.

Related Commands

show group
(config-group) active

(config-group) vip address

To specify the source virtual IP address or a range of IP addresses for the group, use the vip address command. The address is substituted for the source address in flows originating from one of the group's sources. This command's function is identical to the (config-group) ip address command. Use the no form of this command to remove the VIP address for the group.

vip address ip_or_host {range number}
no vip address

Syntax Description

ip_or_host	The IP address or name for the group. Enter the address in either dotted-decimal IP notation (for example, 192.168.11.1) or mnemonic host-name format (for example, myhost.mydomain.com).
range number	The option and variable that defines the range of IP addresses for the group. Enter a number from 1 to 65353. The default is 1. The ip_or_host variable is the first address in the range.

Usage Guidelines

Before you can change the address to 0 or use the no vip address command, you must suspend the group.

Related Commands

show group