Table Of Contents
Release Note for the Cisco Global Site Selector, Release 1.3(3)
Contents
Cisco-Supported Hardware and Software Compatibility
Before Upgrading to Version 1.3(3)
Removing Double Quotes from Object or Description Names
Backing Up Your Current Primary GSSM Database
Downgrading from Version 1.3(3)
Obtaining the Recovery Image and Creating the Recovery CD
Using the Recovery CD to Downgrade GSS Devices
Downgrading 4490 GSS Devices
Downgrading 4491 GSS Devices
Restoring a Primary GSSM Database
Additional Information on GSS Front Panel Buttons and LEDs
Operating Considerations for Software Version 1.3(3)
GUI Change in Software Version 1.3(3)
Software Version 1.3(3) Open Caveats, Resolved Caveats, and Command Changes
Software Version 1.3(3) Open Caveats
Software Version 1.3(3) Resolved Caveats
CLI Command Changes in Software Version 1.3(3)
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Note for the Cisco Global Site Selector, Release 1.3(3)
June 1, 2007
Note 
The most current Cisco GSS documentation for released products is available on Cisco.com.
Contents
This release note applies to software version 1.3(3) for the Cisco Global Site Selector (GSS). It contains the following sections:
•Cisco-Supported Hardware and Software Compatibility
•Before Upgrading to Version 1.3(3)
•Downgrading from Version 1.3(3)
•Additional Information on GSS Front Panel Buttons and LEDs
•Operating Considerations for Software Version 1.3(3)
•GUI Change in Software Version 1.3(3)
•Software Version 1.3(3) Open Caveats, Resolved Caveats, and Command Changes
•Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco-Supported Hardware and Software Compatibility
GSS software version 1.3(3), installed on a GSS 4492R, GSS 4491, GSS 4490, or GSS 4480, operates with all load balancers if ICMP-, TCP-, or HTTP-HEAD-type keepalives are used. In addition, KAL-AP-type keepalives can be used with a Cisco Content Services Switch (CSS) or Catalyst 6500 Content Switching Module (CSM) to support smarter load balancing.
GSS software version 1.3(3) operates with the following Cisco hardware:
•Cisco Content Services Switch (CSS) running the following WebNS software releases:
Cisco CSS Platform
|
Recommended WebNS Versions
|
Minimum Supported WebNS Versions
|
Cisco 11500 Series CSS
|
Software releases:
•7.40.0.04 or greater
•7.30.2.03 or greater
|
Software releases:
•7.20.1.04
•7.10.3.05
|
Cisco 11000 Series CSS
|
Software releases:
•6.10.4.05 or greater
•5.00.6.05 or greater
|
Software releases:
•6.10.1.07
•5.00.3.09
|
•Cisco Catalyst 6500 Content Switching Module (CSM) running the following software releases:
Platform
|
Recommended CSM Versions 1
|
Minimum Supported CSM Versions
|
Cisco Catalyst 6500 Content Switching Module (CSM)
|
Software releases:
•3.1(10) or greater
•3.2(1)
•4.1(4) or greater
•4.2(1) or greater
|
Software releases:
•3.1(4)
•3.2(1)
•4.1(4)
•4.2(1)
|
Before Upgrading to Version 1.3(3)
You can upgrade directly to GSS software version 1.3(3) from GSS software versions: 1.3(x), 1.2(1.0.3), 1.2(1.1.2), 1.2(2.0.3), 1.2(2.1.3), and 1.2(2.2.0). To upgrade from GSS software version 1.1(x), you must first upgrade to GSS software version 1.2(2.2.0).
Note If you upgrade from GSS software version 1.1(x) to 1.2(2.2.0) to 1.3(3), do not change the role of the GSS devices in the network until you have completed the installation on each GSS device in the network.
Before you upgrade to software version 1.3(3), be sure that you:
1. Determine if you need to perform the steps to remove double quotes from names and associated description strings. GSS software versions 1.3(x) do not allow the use of double quotes for names and associated description strings. If you are upgrading from a software version earlier than version 1.3(1) and you have instances of double quotes (") in object names or associated descriptions, you must remove all double quotes before you upgrade to software version 1.3(3). Follow the steps in the "Removing Double Quotes from Object or Description Names"section.
2. Perform a full backup of your primary GSSM database using the links provided in the "Backing Up Your Current Primary GSSM Database" section.
Removing Double Quotes from Object or Description Names
GSS software versions 1.3(x) do not allow the use of double quotes for names and associated description strings. If you have any instances of double quotes (") in object names or associated descriptions (for example, "dns rule 01" or "dns rule 02), you must remove all double quotes before you upgrade to software version 1.3(3).
Perform these steps to remove double quotes:
1. If you are upgrading from:
–Version 1.1(x) to version 1.3.3, first upgrade to GSS software version 1.2(2.2.0), then proceed to step 2.
–Version 1.2(x) or 1.3(x), go to step 2.
2. Perform a full backup of your primary GSSM database. For details on performing a full backup, refer to Chapter 7, Backing Up, Restoring, and Downgrading the GSSM, the "Backing Up the Primary GSSM" section in the Cisco Global Site Selector Administration Guide. Provide a unique name for the backup file (this is the backup file that includes double quotes). If you need to downgrade in the future, you can use this file to restore your unmodified 1.2 or 1.3(x) database.
3. In GSS software version 1.2 or 1.3(x), access the GUI at the primary GSSM. Locate and remove the double quotes from any object names or associated descriptions.
4. Perform a full backup of your modified primary GSSM database. Provide a unique name for the modified backup file. If you need to downgrade in the future, you can use this file to restore your modified 1.2 or 1.3(x) database.
5. Upgrade to GSS software version 1.3(3) as described in the Cisco Global Site Selector Administration Guide, Appendix A, Upgrading the GSS Software.
Backing Up Your Current Primary GSSM Database
Before you upgrade, you must back up your current primary GSSM database in the event that you need to restore. Refer to the appropriate instructions for backing up your version of GSS software:
•For software version 1.3(3), refer to Chapter 7, Backing Up, Restoring, and Downgrading the GSSM, the "Backing Up the Primary GSSM" section in the Cisco Global Site Selector Administration Guide. Also, review the software version 1.3(3) software upgrade sequence as described in the Cisco Global Site Selector Administration Guide, Appendix A, Upgrading the GSS Software.
•For software version 1.2, refer to Chapter 7, Backing Up and Restoring the GSSM, the "Backing Up the Primary GSSM" section in the Cisco Global Site Selector Administration Guide.
•For software version 1.1, refer to Chapter 9, GSS Administration and Troubleshooting, the "Backing Up the GSSM" section in the Cisco Global Site Selector Configuration Guide.
•For software version 1.0, refer to Chapter 3, GSS Administration and Troubleshooting, the "Backing Up the GSSM" section in the Cisco Global Site Selector Configuration Guide.
Downgrading from Version 1.3(3)
Downgrading from software version 1.3(3) to 1.3(2) on GSS devices 4480, 4490, 4491, 4492 is supported.
This procedure applies to downgrading from software version 1.3.3 to versions earlier than 1.3(2) only on GSS 4490 and 4491 devices. If your GSS system uses 4480 devices, you will need to make RMA arrangements to return the devices to Cisco for the downgrade.
Follow the steps in this procedure if you need to downgrade from software version 1.3(3) to versions earlier than 1.3(2). If you have any questions about the need to downgrade your system, contact Cisco Technical Assistance Center (TAC). See "Obtaining Technical Assistance" for more information. To restore an earlier version of your software, you must have a previous backup of the primary GSSM database that corresponds to the version to which you wish to restore. For example, if you wish to downgrade to software release 1.2(2.2.0), you must have a software release 1.2(2.2.0) database backup that you can restore. A 1.3(3) database cannot run on the earlier software platforms because of changes in the database schema and kernel.
In addition to your earlier GSS software version backup, downgrading requires that you download a recovery image from cisco.com, then create a Recovery CD for the software version to which you need to downgrade.
You need the following items to complete the downgrade:
•Full backup of your primary GSSM database that corresponds to the software version to which you wish to restore. This backup is required to restore the database on the primary GSSM.
•Recovery CD.
•Keyboard, mouse, and monitor.
Downgrading the GSS devices in your system requires that you complete the following procedures:
•Obtaining the Recovery Image and Creating the Recovery CD
•Using the Recovery CD to Downgrade GSS Devices
•Restoring a Primary GSSM Database
Obtaining the Recovery Image and Creating the Recovery CD
The steps in this section describe how to obtain the recovery image from Cisco Systems and create the Recovery CD. If necessary, contact Cisco Technical Assistance Center (TAC) for more information about obtaining the recovery image.
You must have a Cisco.com username and password to download a software update from Cisco.com. To acquire a Cisco.com login, go to http://www.cisco.com and click the Register link.
Note You need a service contract number, Cisco.com registration number and verification key, Partner Initiated Customer Access (PICA) registration number and verification key, or packaged service registration number to obtain a Cisco.com username and password.
These steps describe how to obtain the recovery image and create the CD:
1. Use your preferred web browser to access the recovery image at: https://upload.cisco.com/cgi-bin/swc/fileexg/main.cgi?CONTYPES=GSS_Forum
2. Locate the "GSSRecoverySoftware.iso" file. Confirm these file properties:
–owner: rongole
–date: 9-AUG-2006
–size: 194117632 bytes
3. Click the file. If prompted by the software, reenter your username and password, then click OK.
Note The GSS Rescue Software is considered a strong encryption image. If you are not eligible to receive strong encryption images, you will be prompted to complete the Encryption Software Distribution Authorization Form. Complete the form to access and download GSS Recovery Software.
4. If prompted, complete the Encryption Software Distribution Authorization Form (see previous Note).
5. When the End User License Agreement opens, read the license agreement, then click I agree. The File Download page opens.
6. Click Save, then choose a location on your workstation to temporarily store the recovery file.
7. Use your preferred CD-creation software to burn the recovery file to a CD.
8. Before attempting to use the Recovery CD, run an md5 checksum on the file using a tool such as md5sum on Linux and confirm that the value is: b84ff87e04f7b2a95dcf2afe06b02f01
Using the Recovery CD to Downgrade GSS Devices
The procedures in this section describe how to use the Recovery CD to downgrade each 4490 and 4491 GSS device on your network. Refer to the appropriate procedure as required:
•Downgrading 4490 GSS Devices
•Downgrading 4491 GSS Devices
Downgrading 4490 GSS Devices
These steps describe how to use the Recovery CD to downgrade each 4490 GSS device on your network:
1. Verify the role of the primary GSSM in the GSS network.
2. Connect your keyboard and mouse to their corresponding ports on the GSS 4490 device. Connect the monitor to the GSS console port.
3. Follow steps 3a to 3t for each GSS 4490 device:
a. Insert the Recovery CD into the CD-ROM drive on the GSS.
b. Power cycle the GSS and press F1 during the initial startup sequence to enter BIOS Setup.
c. Select Start Options, then press Enter.
d. Select Startup Sequence, then press Enter.
e. Navigate to First Startup Device, then change the state to Disabled.
f. Navigate to Second Startup Device, then change the state to Disabled.
g. Renavigate to First Startup Device, then select CD-ROM.
h. Renavigate to Second Startup Device, then select Hard Disk 0.
i. Press ESC, ESC, ESC. When prompted, select "If yes, Save and Exit the Setup Utility," then press Enter. The GSS boots from the Recovery CD and displays the Rescue prompt.
j. Enter gss-rescue at the prompt, then press Enter.
k. When "Sleeping..." is displayed, press CTRL-ALT-DEL or power cycle by pressing the power button to reboot the GSS, then press F1 during the initial startup sequence to re-enter BIOS Setup.
l. Power cycle the GSS and press F1 during the initial startup sequence to enter BIOS Setup.
m. Select Start Options, then press Enter.
n. Press Enter again to select Startup Sequence.
o. Navigate to First Startup Device, then change the state to Disabled.
p. Navigate to Second Startup Device, then change the state to Disabled.
q. Renavigate to First Startup Device, then select Hard Disk 0.
r. Renavigate to Second Startup Device, then select CD-ROM.
s. Press ESC, ESC, ESC. When prompted, select "If yes, Save and Exit the Setup Utility," then press Enter. The GSS boots.
t. If you are downgrading a primary GSSM, go to "Restoring a Primary GSSM Database".
If you are downgrading a GSS, stop. You have completed the downgrade process.
Downgrading 4491 GSS Devices
These steps describe how to use the Recovery CD to downgrade each 4491 GSS device on your network:
1. Verify the role of the primary GSSM in the GSS network.
2. Connect your keyboard and mouse to their corresponding ports on the GSS 4491 device. Connect the monitor to the GSS console port.
3. Follow steps 3a to 3l for each GSS device:
a. Insert the Recovery CD into the CD-ROM drive on the GSS.
b. Power cycle the GSS and press F4 during the initial startup sequence to enter BIOS Setup.
c. At the BIOS Setup screen, select the Boot menu.
d. Select the Boot Device Priority menu.
e. Select ATAPI CD-ROM as the first device from which to boot.
f. Save the settings and exit from BIOS. The GSS boots from the Recovery CD and displays the Rescue prompt.
g. Enter gss-rescue at the prompt, then press Enter.
h. When "Sleeping..." is displayed, press CTRL-ALT-DEL or power cycle by pressing the power button to reboot the GSS, then press F4 during the initial startup sequence to re-enter BIOS Setup.
i. At the BIOS Setup screen, select the Boot menu, select the Boot Device Priority menu, then reselect Hard Drive as the first device from which to boot.
j. Save the settings.
k. Remove the Recovery CD, then exit from BIOS. The GSS boots.
l. If you are downgrading a primary GSSM, go to "Restoring a Primary GSSM Database".
If you are downgrading a GSS, stop. You have completed the downgrade process for the GSS 4491 device.
Restoring a Primary GSSM Database
These steps describe how to restore your primary GSSM by using the earlier GSS software version database backup:
1. Locate the earlier GSS software version backup of your primary GSSM database to which you wish to restore.
2. If you are restoring to GSS software version 1.3(1), go to step 4.
3. If you are restoring to a GSS software version earlier than version 1.3(1), obtain the software and install it as described in steps 1 to 9 in the "Upgrading Your GSS Devices" section in Appendix A of the Cisco Global Site Selector Administration Guide, then go to step 4d.
4. Restore your primary GSSM using the database backup you created in "Backing Up Your Current Primary GSSM Database". Refer to the steps described in Chapter 7, Backing Up, Restoring, and Downgrading the GSSM, the "Restoring Your Primary GSSM from a Previous Backup" section in the Cisco Global Site Selector Administration Guide.
Additional Information on GSS Front Panel Buttons and LEDs
The following information augments the material on the GSS front panel features provided in Chapter 1, Introduction, in the Cisco Global Site Selector 4491 Hardware Installation Guide.
The System ID button on the GSS front panel allows you to identify the GSS when it is installed in a single rack with multiple GSS devices. The LED illuminates on the rear panel of the active GSS.
•Press the front System ID button to activate the blue LED on the rear panel of the GSS.
•Press the rear System ID button to turn off the LED on the rear panel.
Note that the Power Spike (or Surge) indicator LED operates as the System ID button on the front of the GSS. Thus, if you press the System ID button on the front or rear of the GSS, the rear System ID button will blink as well as the Power Spike indicator LED on the front of the unit. The reason for this is that the System ID button does not activate a corresponding LED, so it uses the Power Spike indicator LED instead.
If there are several GSSs in the rack and you press the System ID button, you can locate the GSS you are working on should you need to go to the rear of the rack. After using the System ID button to identify the GSS, it is recommended that you press the button a second time to restore solid LED status and thus, re-enable the Power Spike indicator. It is also recommended that you only press the System ID button during installation or troubleshooting in order to retain the Power Spike detection and reporting feature.
Operating Considerations for Software Version 1.3(3)
The following operating considerations apply to software version 1.3(3):
•When you use a TCP keepalive with the fast detection and graceful termination methods to test a Telnet service on a server running Windows Server 2003, port 23 may fluctuate between the Up and Down state (port flapping). If port flapping occurs on TCP port 23 of Windows Server 2003, you will notice an increase in keepalive negative probe and keepalive transition counts on the Answer Keepalive Statistics list page of the primary GSSM GUI. To resolve this issue, increase the retries value for the TCP keepalive. A retry value of three or four should prevent flapping on port 23 when connecting to a server running Windows Server 2003.
Depending on the number of TCP keepalives you require to send from port 23 to servers running Windows Server 2003, specify the retries value as follows:
–If the GSS is transmitting numerous TCP keepalives using port 23, globally change the Number of Retries value for all TCP keepalives on the Configure Global KeepAlive Properties details page of the GUI. If you are using the keepalive-properties tcp fast command in the CLI to configure keepalives, change the value of the retries option.
–If TCP keepalives are being used for different devices or ports, change the Number of Retries value on a per TCP keepalive basis using the Modifying Answer detail page of the GUI. If you are using the keepalive type tcp command in the CLI to configure keepalives on a per TCP keepalive basis, change the value of the retries option.
•Cisco LocalDirector does not reply properly to TCP keepalives sent on port 23 from a GSS device. To resolve this behavior, specify a different keepalive method with LocalDirector or directly probe the servers located behind LocalDirector.
•For a GSS to successfully operate and perform DNS resolutions, a name server must be properly configured, running, and reachable by the GSS.
•When a primary GSSM has been upgraded to software version 1.3(3), but other GSS devices remain at version 1.2(1.1.2) or 1.2(2.0.3), global server load-balancing configuration settings are not propagated to the GSS devices still at version 1.2(1.1.2) or 1.2(2.0.3). To avoid this behavior, ensure that all GSS devices on the network are upgraded to software version 1.3(3) before you configure global server load balancing.
GUI Change in Software Version 1.3(3)
The GUI on the primary GSSM now displays the load for each answer, as well as the answer status, either online or offline, on the Monitoring > Answer Status details page. Previously, only the answer status was shown.
In some cases, the KAL-AP load may be less than 255, yet the answer status remains offline. If so, some other keepalive is causing the answer to be offline.
Software Version 1.3(3) Open Caveats, Resolved Caveats, and Command Changes
The following sections contain the open caveats, resolved caveats, and command changes in software version1.3(3):
•Software Version 1.3(3) Open Caveats
•Software Version 1.3(3) Resolved Caveats
•CLI Command Changes in Software Version 1.3(3)
Software Version 1.3(3) Open Caveats
This section lists the open caveats for software version 1.3(3).
•CSCse79659—DNS query processing is case sensitive, but should be not be case sensitive. For example, when a domain is configured as .*foo\.com\.au, the GSS only matches all lowercase characters. The following variations of the domain name example shows names on which the GSS will not match:
–*.FOO.COM.AU - is not matched
–*.foo.com.AU - is not matched
Workaround: Define a regular expression of the form: .*[fF][oO][oO]\.[cC][oO][mM]\.[aA][uU]
•CSCsf17052—The GSS 4492 interface link does not come up when speed/duplex are hard set. When a GSS is connected to a Catalyst 6500 and both devices are hard set to 1000/full, the Ethernet link will not come up. If you set the GSS to auto speed/duplex, the link will come up. The link stays up if you set it back to 1000/full. Workaround: Set both devices to auto-negotiate.
Software Version 1.3(3) Resolved Caveats
This section lists the resolved caveats for software version 1.3(3).
•CSCse14107—You cannot use the console when AAA accounting is enabled. When you issue aaa accounting commands on the GSS, you are logged out of the primary GSSM. If you repeat the login attempt, the login succeeds. If you execute any command, you are logged out. Workaround: Access the GSS IP address using telnet or SSH. Do not access the GSS IP address using the console port.
•CSCse78532—When doing Name Server Forwarding on the GSS, client initiated traffic to the GSS coming in as TCP (zone transfers or large requests) is incorrectly forwarded to the DNS server as a UDP request.
•CSCse41672—GSS primary and standby database timestamps are not synchronized.
•CSCsd27446—The GSS WebGUI Monitoring tab shows zero keepalive probes per second even when there are probes present. Workaround: Manually compute the keepalive probes per second based on the configuration and the show command outputs.
•CSCsc71389—A DNS rule using hash has an uneven load distribution. When you configure a DNS rule with the hashed load distribution method and the associated answer group only contains two answers, a 2:1 distribution of load occurs.
•CSCse33535—Generating a tech report results in a Java null pointer exception in CrDirector.
•CSCsf09042—The GSS becomes unusable when you to attempt to restore the startup config from the disk. Workaround: Ensure there is a database on the GSS before attempting to copy the startup config.
•CSCse94530—Changes to the GSLB configuration may not take effect after performing a role swap. During and after a role swap in a GSS network, configuration changes on the primary GSSM are displayed by the show gslb-config command, but statistics relating to the new config are not compatible with the changed configuration.
•CSCse94715—With remote SSH TACACS authentication, you no longer need to manually create a local user for a successful authentication.
CLI Command Changes in Software Version 1.3(3)
Table 1 lists the new clock command options in software version 1.3(3). Table 2 lists the command that was removed from software version 1.3(3).
Table 1 New CLI Clock Command Options in Software Version 1.3(3)
Command and Syntax
|
Description
|
clock
|
The user-summer-time, user-timezone, and summer-time options have been added to the clock command to allow you to set:
•user-defined daylight savings time
•user-defined timezones
•daylight savings time to another predefined summer time
The syntax for the new clock command options is as follows:
clock [user-summer-time summer-time name | start time (hh:mm) <0-23> |
start day <Friday, Monday, Saturday, Sunday, Thursday, Tuesday, Wednesday> |
start week <1-5> | start month <April, August, December, February, January, July, June, March, May, November, October, September>| end time (hh:mm) <0-23> |
end day <Friday, Monday, Saturday, Sunday, Thursday, Tuesday, Wednesday> | end week <1-5> | end month <April, August, December, February, January, July, June, March, May, November, October, September> | offset (in minutes) <0-1440>]
[user-timezone timezone name | hour_offset <-23,+24> | minute_offset <0-59>]
[summer-time timezone <ADT (Atlantic Daylight Time) | AKDT (Alaska Standard Daylight Time) | CDT (Central Daylight Time) | EDT (Eastern Daylight Time) | MDT (Mountain Daylight Time) | PDT (Pacific Daylight Time)]
The options and variables for this command are:
•user-summer-time —(Optional) Allows you to specify entries such as a summer-time name, start time, start day, start week, start month, end time, end day, end week, end month and an offset for daylight savings time.
•user-timezone —(Optional) Allows you to specify entries such as a timezone name and an hour and minute offset for a timezone.
•summer-time —(Optional) Allows you to directly set daylight savings time to some predefined summer times.
|
clock (continued)
|
For example, if you wish to set up standard time and daylight savings time in the Eastern Time Zone (i.e., Eastern Standard Time (EST) Universal Time Coordinated (UTC -5)) and its daylight saving time (i.e., Eastern Daylight Time (EDT) (UTC -4), you follow these instructions. EDT begins here at 2:00 am local time on the first Sunday in April and ends at 2:00 am local time on the last Sunday of October.
The following procedure shows how to set the time zones using the 3 new clock command options:
1. Set the clock based on UTC.
gss2.gss-tb6.com#clock set 7:45:00 September 7 2006
gss2.gss-tb6.com#show clock
System time: Thu Sep 7 07:45:05 UTC 2006
2. Set the clock to EST by using the user-timezone command option.
Timezone set.com#clock user-timezone EST -5 0
Please restart the GSS (reload) to sync log timestamps to new timezone.
gss2.gss-tb6.com#show clock
System time: Thu Sep 7 02:45:17 EST 2006
Note that you need to set the user-timezone before using the summer-time command option.
3. Set the summer-time on the GSS in one of two ways:
a. Enter the summer-time command option.
gss1.gss-tb6.com#clock summer-time ?
ADT Atlantic Daylight Time: 2 am 1st Sunday April - 2 am last Sunday Oct, +60
min
AKDT Alaska Standard Daylight Time: 2 am 1st Sunday April - 2 am last Sunday
CDT Central Daylight Time: 2 am 1st Sunday April - 2 am last Sunday Oct, +60 min
EDT Eastern Daylight Time: 2 am 1st Sunday April - 2 am last Sunday Oct
MDT Mountain Daylight Time: 2 am 1st Sunday April - 2 am last Sunday Oct, +60
min
PDT Pacific Daylight Time: 2 am 1st Sunday April - 2 am last Sunday Oct, +60 min
gss1.gss-tb6.com#clock summer-time EDT
Please restart the GSS (reload) to sync log timestamps to new timezone.
b. Enter the user-summer-time command option.
gss2.gss-tb6.com#clock user-summer-time EDT 2:00 Sunday 1 April 2:00 Sunday 5
October 60
Timezone set.
Please restart the GSS (reload) to sync log timestamps to new timezone.
gss2.gss-tb6.com#show clock
System time: Thu Sep 7 03:47:07 EDT 2006
If you reside in one of the following timezones, ADT, AKDT, CDT, EDT, MDT, or PDT, you use the summer-time option as shown in step 3a to set the summer-time on the GSS. If you need to configure a custom summer-time, use the user-summer-time option and follow step 3b instead. Note that in this procedure, the summer-times are predefined summer times.
After the procedure is finished, the clock will be set back to the user-timezone after the daylight savings time duration is covered. In this particular instance, the timezone will be set back to EST after 2:00 A.M on the last Sunday in October.
You set both the summer-time and user-summer-time command options with respect to UTC only, and not the user-timezone. Also, there is no relation to the clock timezone command that was used to establish a timezone on the GSS.
|
Table 2 lists command that was removed in software version 1.3(3).
Table 2 Command Removed from Software Version 1.3(3)
Command and Syntax
|
Description
|
gss-tcp-keepalives
|
The gss-tcp-keepalives command in interface mode was removed. For example:
gss1.example.com(config)# interface ethernet 0
gss1.example.com(config-eth0)# gss-tcp-keepalives
|
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Copyright © 2007, Cisco Systems, Inc.
All rights reserved.
