Table Of Contents
Setting Up Your GSS from the CLI
Logging in to the CLI and Enabling Privileged EXEC Mode
Setting User-Defined Time Zones
Setting User-Defined Daylight Saving Time
Setting Daylight Saving Time to Another Predefined Summer Time
Synchronizing the GSS System Clock with an NTP Server
Showing the Date, Time, and Timezone
Configuring a Hostname for the GSS Device
Configuring an Ethernet Interface on a GSS Device
Configuring Interface Duplex Operation
Configuring GSS Interdevice Communication
Configuring an Interface for TCP and HTTP HEAD Keepalive Communication
Setting the IP Address and Subnet Mask of the Ethernet Interface
Outputting a Record of TCP Traffic
Configuring an IP Route for the GSS
Resolving a Host or Domain Name to an IP Address
Configuring a Global Site Selector
Setting Up Your GSS from the CLI
This chapter describes how to configure your GSS devices from the CLI and connect it to the GSS network. This process describes how to configure the GSS as a primary GSSM, a standby GSSM, or as a GSS device.
This chapter contains the following sections:
•
Logging in to the CLI and Enabling Privileged EXEC Mode
•
•
•
•
•
Initial Setup Quick Start
Table 4-1 is a quick start configuration table designed to help you configure your GSS quickly from the CLI. This table provides information and examples on the following basic steps to perform the following:
•
•
•
•
•
•
Table 4-1 Initial Setup Quick Start
1.
2.
3.
localhost.localdomain> enableBy default, the hostname for GSS devices is localhost.localdomain. This name changes once you configure the hostname for the device.
4.
localhost.localdomain> enable5.
localhost.localdomain# clock set 12:10:05 Feb 15 20066.
localhost.localdomain# configlocalhost.localdomain(config)# ntp-server 172.16.1.2 172.16.1.3localhost.localdomain(config)# ntp enable7.
localhost.localdomain(config)# hostname gssm1.example.com8.
gssm1.cisco.com(config)# interface ethernet 0gssm1.cisco.com(config-eth0)# speed 100gssm1.cisco.com(config-eth0)# duplex fullYou cannot execute interface commands while the GSS software is running (for example, serving DNS requests). You must enter the gss stop command to stop the GSS software before executing the interface ethernet command.
9.
gssm1.cisco.com(config-eth0)# gss-communicationsgssm1.cisco.com(config-eth0)# exitgssm1.cisco.com(config)#10.
gssm1.cisco.com(config-eth0)# ip address 192.168.3.24 255.255.255.011.
gssm1.cisco.com(config)# interface eth1gssm1.cisco.com(config-eth1)# gss-tcp-keepalives12.
gssm1.cisco.com(config-eth1)# exitgssm1.cisco.coml(config)#13.
gssm1.cisco.com(config)# ip default-gateway 172.16.7.1814.
gssm1.cisco.com(config)# ip name-server 192.168.12.1, 192.168.12.5, 192.168.12.715.
gssm1.cisco.com(config)#exit16.
gssm1.cisco.com# gss enable gssm-primary17.
gssm2.example.com# gss enable gssm-standby gssm1.example.com18.
gss1.example.com# gss enable gss gssm1.example.com19.
gssm1.example.com# copy running-config startup-config
Logging in to the CLI and Enabling Privileged EXEC Mode
To log in to a GSS device and enable privileged EXEC mode at the CLI, perform the following steps:
1.
2.
Otherwise, if you are using a direct serial connection between your terminal and the GSS device, use a terminal emulation program to access the GSS CLI. For details about making a direct connection to the GSS device using a dedicated terminal and about establishing a remote connection using SSH or Telnet, see Chapter 3, Accessing the GSS CLI.
3.
localhost.localdomain>4.
localhost.localdomain> enablelocalhost.localdomain#The prompt changes from the user-level EXEC right angle bracket (>) prompt to the privileged-level EXEC pound sign (#).
Setting the System Clock
To set the date, time, or time zone for a GSS device, use the clock command. When you enter this command, the GSS device displays the current date and time.
This section contains the following topics:
•
•
•
•
Setting the Time and Date
Use the clock set command to set the time and the date for a GSS device. Enter the time and date:
•
•
The syntax for the clock set command is as follows:
clock set hh:mm:ss MONTH DD YYYY
The keywords and arguments are as follows:
•
•
•
For example, to specify a time of 12:10 and a date of February 15, 2006, enter:
localhost.localdomain# clock set 12:10:05 February 15 2006
Note
Setting the Time Zone
The time stored in the GSS is the local time. Use the clock timezone command to specify a time zone for the GSS, synchronizing the log timestamps to a new timezone. The name of the timezone. Enter ? to list all supported time zones, countries, continents, and cities.
There are a number of options available to set the local time zone for your GSS:
•
•
•
The syntax for this command is as follows:
clock timezone timezonename
The timezonename is the name of the time zone you specify for the GSS. Enter ? to list all supported time zone names.
For example, to specify the Greenwich Mean Time (GMT) time zone, enter:
localhost.localdomain# clock timezone GMTFor example, to specify the time zone to the local time in Paris, enter:
localhost.localdomain# clock timezone europe parisSetting User-Defined Time Zones
The clock user-timezone command allows you to set user-defined time zones.
The syntax for this command is as follows:
clock user-timezone timezonename | hour_offset <-23,+24> | minute_offset <0-59>
The keywords and arguments are as follows:
•
•
•
Setting User-Defined Daylight Saving Time
The clock user-summer-time command allows you to set a user-defined daylight saving time.
The syntax for this command 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>The keywords and arguments are as follows:
•
•
•
•
•
•
•
•
•
•
Setting Daylight Saving Time to Another Predefined Summer Time
The clock summer-time command allows you to set daylight saving time to another predefined summer time.
The syntax for this command is as follows:
clock 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 keywords and arguments are as follows:
•
•
For example, if you wish to set up standard time and daylight saving time in the Eastern Time Zone (that is, Eastern Standard Time (EST) Universal Time Coordinated (UTC -5)) and its daylight saving time (that is, Eastern Daylight Time (EDT) (UTC -4), use the clock user-timezone, summer-time, and user-summer-time commands as shown in Table 4-2.
EDT begins at 2:00 a.m. local time on the first Sunday in April and ends at 2:00 a.m. local time on the last Sunday of October.
Note
I
If you reside in one of the following timezones, ADT, AKDT, CDT, EDT, MDT, or PDT, you use the clock summer-time command as shown in step 3a to set the summer-time on the GSS. If you need to configure a custom summer-time, use the clock user-summer-time command and follow step 3b instead.
In this example, the summer-times are predefined summer times. After it is finished, the clock will be set back to the user-timezone after the daylight saving time duration is covered. In this particular instance, the time zone will be set back to EST after 2:00 a.m. on the last Sunday in October.
Note
Setting the Hardware Clock
The hardware clock is powered by a Lithium battery on the motherboard of the GSS. The system clock is a software concept, rather than an actual physical entity. It is updated by the Network Time Protocol (NTP) or by the clock set command. For more information on NTP, see the "Synchronizing the GSS System Clock with an NTP Server" section, while the "Setting the Time and Date"section contains more information on the clock set command.
The clock update-calendar and clock read-calendar commands provide a way for you to synchronize the hardware clock and the system clock without having to reload the GSS. You use clock update-calendar to update the hardware calendar from the system clock and clock read-calendar to read the hardware calendar into the system clock.
Specifically, you use clock update-calendar when the system clock is set via NTP and you wish to synchronize the system time with the hardware clock. You then use clock read-calendar when the system clock is set via NTP and you wish to revert back to using the hardware clock.
The syntax for these commands is as follows:
clock update-calendar
clock read-calendar
For example, to update the hardware calendar from the system clock, enter:
localhost.localdomain# clock update-calendarFor example, to read the hardware calendar into the system clock, enter:
localhost.localdomain# clock read-calendarSynchronizing the GSS System Clock with an NTP Server
NTP enables you to synchronize the GSS system clock to a time server. NTP is a protocol designed to synchronize the clocks of computers over a network. NTP assures accurate local time-keeping with references to radio and atomic clocks. The NTP protocol is capable of synchronizing distributed clocks within milliseconds over long time periods. You can specify a maximum of four NTP servers.
Note
Use the ntp-server global configuration mode command to specify one or more NTP servers for GSS clock synchronization. To disable an NTP time server, use the no form of this command.The syntax for this command is as follows:
ntp-server ip_or_host
The ip_or_host argument specifies the IP address or hostname of the NTP public time server that provides the clock synchronization. You can specify a maximum of four IP addresses or hostnames. Enter the IP address in dotted-decimal notation (for example, 192.168.11.1) or a mnemonic hostname (for example, myhost.mydomain.com).
Use the ntp enable global configuration mode command to enable the NTP service. To disable NTP, use the no form of this command. The syntax of this command is:
ntp enable
For example, to specify the IP addresses of two NTP time servers, enter:
localhost.localdomain# configlocalhost.localdomain(config)# ntp-server 172.16.1.2 172.16.1.3localhost.localdomain(config)# ntp enableTo view if NTP is enabled for the GSS device, enter:
localhost.localdomain# show ntpNtp is enabledntp-server 172.16.1.2ntp-server 172.16.1.3To remove a specified NTP server, enter:
localhost.localdomain(config)# no ntp-server 172.16.1.3To disable NTP, enter:
localhost.localdomain(config)# no ntp enableShowing the Date, Time, and Timezone
Use the show clock command to display the current date, time, and timezone name.
localhost.localdomain# show clockSystem time: Wed February 15 20:55:36 UTC 2006Table 4-3 describes the fields in the show clock command output.
Configuring a Hostname for the GSS Device
By default, the hostname for GSS devices is localhost.localdomain. The hostname is used for the command prompts and default configuration filenames. To configure a qualified hostname for the GSS device, use the hostname command. This name changes once you configure the hostname for the device.
The hostname command requires a fully qualified hostname, which requires at least one period (.) in the name (for example, hostname.foo.com). The no form of this command erases the configured hostname and restores the default value.
When you specify a hostname for a GSS (primary GSSM, standby GSSM, or GSS device) that is operating in a lab network environment, the top-level domain of the hostname cannot begin with a numerical value. For example, you cannot name a primary GSSM as gssm.1lab. If you attempt to create or change a hostname for a top-level domain to a name that begins with a number, the following message appears:
Top level domains of hostnames cannot begin with a numberFor the purposes of GSS interdevice communications, configure the hostname on the same interface (eth0 or eth1) that is being used for GSS communications, as set using the gss-communications command.
The syntax for this global configuration mode command is:
hostname host_name
Specify the new hostname for the GSS device as a case sensitive text string that contains from 1 to 22 alphanumeric characters.
For example, to change the hostname to gssm1.cisco.com, enter:
localhost.localdomain(config)# hostname gssm1.cisco.comgssm1.cisco.com(config)#To remove the hostname and set it to the default localhost.localdomain, enter:
gssm1.cisco.com(config)# no hostname gssm1.cisco.comlocalhost.localdomain(config)#Configuring an Ethernet Interface on a GSS Device
Your GSS comes with one integrated dual-port Ethernet controller. This controller provides an interface for connecting to 10-Mbps, 100-Mbps, or 1000-Mbps networks and supports autonegotitate, full-duplex, or half-duplex operations on an Ethernet LAN.
To configure a GSS Ethernet interface, access global configuration mode and use the interface ethernet command. The syntax for this command is as follows:
interface ethernet {0 | 1}{autosense | duplex {auto | full | half} | gss-communications | gss-tcp-keepalives | ip address {ip-address netmask} | no | shutdown | speed {mbits | auto}
If desired, you can use the following CLI commands to configure specific Ethernet interface settings:
•
•
•
•
•
•
•
The following sections provide detailed information on:
•
•
•
•
•
•
Configuring an Interface
Use the interface ethernet command to configure an Ethernet interface on a GSS device. The syntax for entering an Ethernet interface is as follows:
interface ethernet {0 | 1}
The options are:
•
•
For example, to configure Ethernet interface port 0 on a GSS and access the interface mode, enter:
gssm1.cisco.com(config)# interface ethernet 0The GSS changes from configuration mode to the specific interface mode.
gssm1.cisco.com(config-eth0)#Configuring Autosense
The autosense command enables the current GSS interface to select the proper duplex mode (for example, full duplex, half duplex) for communicating with other network devices. The GSS automatically detects the network line speed (Fast Ethernet only) and duplex of incoming signals, and it synchronizes those parameters during data transfer. Autonegotiation enables the GSS and the other devices on the link to achieve the maximum common level of operation. Autosense is enabled by default.
Note
To configure autosense for interface Ethernet 0, enter:
gssm1.cisco.com(config)# interface eth0or
gssm1.cisco.com(config)# interface eth0gssm1.cisco.com(config-eth0)# autosenseWhen autosense is on, manual configurations are overridden. To prevent your configuration from being overwritten, disable autosense before configuring an Ethernet interface.
To disable autosense, use the no form of this command. For example, enter:
gssm1.cisco.com(config-eth0)# no autosenseConfiguring Interface Duplex Operation
The duplex command enables you to configure an Ethernet interface for full- or half- duplex operation. Full duplex allows data to travel in both directions at the same time through an Ethernet interface. A half-duplex setting ensures that data travels only in one direction at any given time. Although full duplex is faster, the Ethernet interfaces sometimes cannot operate effectively in this mode. If you encounter excessive collisions or network errors, configure the interface for half duplex rather than full duplex. To disable duplex operation, use the no form of the command.
Note
The syntax is as follows:
interface ethernet {0 | 1} duplex {auto | full | half}
The options are:
•
•
•
•
•
Note
Specify an interface bandwidth (Mbps) using the speed command before you configure full- or half-duplex. If you enter the duplex full or duplex half command without specifying an interface bandwidth, the following error message appears:
Duplex will not be set until speed is set to a non-auto valueTo configure full duplex for interface Ethernet 0, enter:
gssm1.cisco.com(config)# interface eth0 duplex fullor
gssm1.cisco.com(config)# interface eth0gssm1.cisco.com(config-eth0)# duplex fullTo disable duplex operation for interface Ethernet 0, enter:
gssm1.cisco.com(config-eth0)# no duplexConfiguring Interface Speed
The speed option sets the bandwidth on Fast Ethernet interfaces only. Gigabit Ethernet interfaces run at 1000 Mbps only and are not user-configurable. To restore default values, use the no form of this command.
Note
The syntax is:
interface ethernet {0 | 1} speed mbits
Specify the bandwidth size in megabits per second (Mbps). The default speed for a GSS interface is autonegotiate. The available ranges are as follows:
•
•
•
•
Note
To set the bandwidth on Ethernet 0, enter:
gssm1.cisco.com(config)# interface eth0 speed 100or
gssm1.cisco.com(config)# interface eth0gssm1.cisco.com(config-eth0)# speed 100To restore the default setting of autonegotiate for interface Ethernet 0, enter:
gssm1.cisco.com(config-eth0)# no speedConfiguring GSS Interdevice Communication
During inter-GSS communication, all GSS devices listen for configuration and status updates on only one interface. The default inter-GSS communication interface is Ethernet 0. To designate Ethernet interface 1 for inter-GSS communication, use the gss-communications option.
Note
To designate Ethernet 1 for GSS interdevice communication, enter:
gssm1.cisco.com(config)# interface eth1 gss-communicationsor
gssm1.cisco.com(config)# interface eth1gssm1.cisco.com(config-eth1)# gss-communicationsConfiguring an Interface for TCP and HTTP HEAD Keepalive Communication
To designate one of the two GSS Ethernet interface s as the source for TCP and HTTP HEAD keepalive communication, use the gss-tcp-keepalives option. Only one Ethernet interface (0 or 1) can be designated for TCP and HTTP HEAD keepalive communication.
Note
For example, to designate Ethernet 1 for TCP and HTTP HEAD keepalive communication, enter:
gssm1.cisco.com(config)# interface eth1 gss-tcp-keepalivesor
gssm1.cisco.com(config)# interface eth1gssm1.cisco.com(config-eth1)# gss-tcp-keepalivesSetting the IP Address and Subnet Mask of the Ethernet Interface
Use the ip address command to assign an IP address and subnet mask to an Ethernet interface. You cannot assign the same IP address to more than one interface. To disable a specific IP address, use the no form of the command.
The syntax is:
ip address ip-address ip-subnet
The variables are:
•
•
Note
To assign an IP address to Ethernet 0, enter:
gssm1.cisco.com(config)# interface eth0 ip address 192.168.10.2 255.255.255.0or
gssm1.cisco.com(config)# interface eth0gssm1.cisco.com(config-eth0)# ip address 192.168.10.2 255.255.255.0To remove an IP address and subnet mask for interface Ethernet 0, enter:
gssm1.cisco.com(config)# interface eth0gssm1.cisco.com(config-eth0)# no ip addressShutting Down an Interface
Use the shutdown command in interface configuration mode to shut down a particular Ethernet interface on the GSS device.
To shut down interface Ethernet 1, enter:
gssm1.cisco.com(config)# interface eth1 shutdownor
gssm1.cisco.com(config)# interface eth1gssm1.cisco.com(config-eth1)# shutdownShowing Interface Information
To display GSS hardware interface information for Ethernet interface 0 or 1, including interface statistics, use the show interface command.
show interface {eth0 | eth1}
For example, to display information for Ethernet interface 0, enter:
gssm1.cisco.com# show interface eth0Interface eth0ip address 10.86.209.167 255.255.254.0gss-communicationsInterface StateLink is upnegotiated, 100 mbps, full duplexSupported modes: 10-half, 10-full, 100-half, 100-full, 1000-fullAdvertised modes: 10-half, 10-full, 100-half, 100-full, 1000-fullInterface statisticseth0 Link encap:Ethernet HWaddr 00:C0:9F:35:D1:64inet addr:10.86.209.167 Bcast:10.86.209.255 Mask:255.255.254.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:583003 errors:0 dropped:0 overruns:0 frame:0TX packets:114048 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:45735671 (43.6 Mb) TX bytes:9810113 (9.3 Mb)Base address:0xbc00 Memory:fc9e0000-fca00000Outputting a Record of TCP Traffic
Use the tcpdump interface command to display a record at the CLI of all TCP traffic transmitted from and received by an Ethernet interface. GSS traffic information continuously displays on screen until you press Ctrl-C to cancel the operation. The protocol, port, network, and file options of the tcpdump command allow you to filter traffic and capture only the traffic of certain protocols, going to or coming from certain hosts or certain ports.
The syntax for this command is as follows:
tcpdump interface {any | eth0 | eth1} | protocol {any| icmp|tcp|udp} | host {any | ip_or_host} | port {any | port} | network {any | ip-address ip-subnet} | file {filename}
The keywords and arguments are as follows:
•
•
•
•
–
–
–
•
•
•
•
If the file parameter is not specified, captured data is dumped to the screen. In that case, only header data is displayed and there is no limit to number of packets captured.
If you execute the tcpdump command without any specified options, no filtering is performed. If you want to use the defaults for the remaining tcpdump command parameters, press Enter at each option. No further filtering is performed by the GSS, other than what has been specified. For example, if you enter tcpdump interface eth0 protocol tcp, the GSS performs only IP protocol filtering and does not perform host, port, or network filtering.
The following is an example of the tcpdump interface command and its output:
gssm1.cisco.com# tcpdump interface eth0Kernel filter, protocol ALL, datagram packet sockettcpdump: listening on eth019:20:45.678641 > gssm.cisco.com.ssh > 10.1.2.3.1178: P 2126255246:2126255346(100) ack 4828790 win 32680 (DF) [tos 0x10]19:20:45.680534 > gssm.cisco.com.49165 > gss.cisco.com.domain: 9217+ PTR? 187.0.1.2.in-addr.arpa. (43)19:20:45.681090 < gss.cisco.com.domain > gssm.cisco.com.49165: 9217 NXDomain* 0/1/0 (111)...Specifying Name Servers
The GSS can communicate with a maximum of eight name servers for name and address resolution. Use the ip name server command to specify the IP address of one or more name servers, to a maximum of eight name servers. To disable one or more name servers, use the no form of this command.
The syntax for this command is as follows:
ip name-server ip-addresses
The ip-addresses variable identifies the IP addresses for the name servers. You can enter a maximum of eight name servers, separated by spaces. Enter each IP address in dotted-decimal notation.
To configure the IP address of a single name server, enter:
gssm1.cisco.com(config)# ip name-server 172.16.17.18To configure the IP addresses of multiple name servers, enter:
gssm1.cisco.com(config)# ip name-server 172.16.17.18 192.168.2.22 172.16.1.2The GSS requires a functioning nameserver to operate properly and perform DNS resolutions. If the nameserver is not properly configured using the ip name-server command, or if the configured nameservers are not reachable for any reason (down, network loss, or a firewall), the GSS will not be able to perform DNS resolutions when you attempt to log in. In this case, the timeout may take several minutes. This behavior occurs when you attempt to log in through a Telnet, SSH, or FTP connection.
To enable the GSS to perform DNS resolution, always configure more than one nameserver. For example:
gss.example.com(config)#ip name-server 192.168.1.1gss.example.com(config)#ip name-server 192.168.2.2gss.example.com(config)#ip name-server 192.168.3.3This behavior may also occur if you configure access lists for the GSS. In this case, create access lists that allow the DNS responses from a nameserver. For example:
gss.example.com(config)#access-list acl1 permit udp any eq 53Another solution is to limit incoming DNS response packets only from your configured nameservers (more secure). For example:
gss.example.com(config)#access-list acl1 permit udp 192.168.1.1 255.255.255.255 eq 53gss.example.com(config)#access-list acl2 permit udp 192.168.1.2 255.255.255.255 eq 53gss.example.com(config)#access-list acl3 permit udp 192.168.1.3 255.255.255.255 eq 53Configuring an IP Route for the GSS
To establish IP connectivity to the GSS, configure a static IP route to connect the GSS to next hop router. A static route consists of a destination network address and mask and the next hop to reach the destination. You can also specify a default static route (using 0.0.0.0 as the destination network address and a valid next hop address) to direct IP packets for which no other destination is listed in the routing table. Default static routes are useful for forwarding otherwise unrouteable packets by the GSS.
Use the following ip command options to configure a static IP route:
•
•
The syntax for the ip command is:
ip {default-gateway ip-address | route destination_address netmask gateway}
no ip {default-gateway ip-address | route destination_address netmask gateway}
The keywords and arguments are as follows:
•
•
•
•
•
•
For example, to configure a default gateway, enter:
gssm1.cisco.com(config)# ip default-gateway 192.168.7.18For example, to configure a static IP network route, enter:
gssm1.cisco.com(config)# ip route 172.16.227.128 172.16.227.250To display the IP routing table for the GSS, use the show ip routes command.
gssm1.cisco.com# show ip routesTable 4-4 describes the fields in the show ip routes output.
