Access denied | www.archivum.info used Cloudflare to restrict access
Please enable cookies.
What happened?
The owner of this website (www.archivum.info) has banned your access based on your browser's signature (3ff4e56dc3b4989b-ua98).1472人阅读
【Android之WIFI】（2）
【Android之USB】（3）
we need to run
the script
to switch USB modem
mode for Ubuntu
#!/bin/bash
#VERSION=22.001.03.01.03
install_exit()
echo "Preass any key to exit. "
read COMMAND
WHEREWHOAMI="`which whoami`"
ROOTORNOT="`$WHEREWHOAMI`"
#echo "$ROOTORNOT"
if [ "$ROOTORNOT" != "root" ]
echo "You must run the install process by root."
install_exit
CURRENTPATH="$(dirname "$0")"
#echo "$CURRENTPATH"
TMP_FILE_PATH="/tmp/MobileBrServ_AutoRun"
INSTALL_FILE="/linux_mbb_install"
SYSCONFIG_PATH="/ArConfig.dat"
INSTALL_SHELL="/install"
DATACARD_VERIFY="/DataCard_Verify"
MBB_BIN_FILE="/mbbservice.bin"
MBB_FILE="/mbbservice"
SYSCONFIG_VALUE="VALUE"
INSTALL_PATH="/usr/local/MobileBrServ"
LOG_PATH="/tmp/MobileBrServ_autoinstall_log"
#define the install variable
FIRST_INSTALL="NO"
INSTALL_OR_NOT="NO"
echo "Current path = ${CURRENTPATH}" & ${LOG_PATH}
check_ISO()
echo "begin to verify ISO ..." | tee -a ${LOG_PATH} #& /dev/null 2&&1
#TESTFILE="${CURRENTPATH}"
#echo "$TESTFILE"
#read COMMAND
if [ ! -f "${CURRENTPATH}${INSTALL_FILE}${MBB_BIN_FILE}" ]
echo "${CURRENTPATH}${INSTALL_FILE}${MBB_BIN_FILE}"
echo "the .bin file is not exist! " | tee -a ${LOG_PATH}
install_exit
if [ ! -f "${CURRENTPATH}${INSTALL_FILE}${SYSCONFIG_PATH}" ]
echo "the ArConfig.dat file is not exist! " | tee -a ${LOG_PATH}
install_exit
echo "verify the ISO succeed !" | tee -a ${LOG_PATH}
backup_ISO()
echo "begin to copy install file..." | tee -a ${LOG_PATH}
if [ -d "${TMP_FILE_PATH}" ]
rm -f -R "${TMP_FILE_PATH}"
mkdir -p "${TMP_FILE_PATH}"
cp -f -R "${CURRENTPATH}${INSTALL_FILE}" "${TMP_FILE_PATH}${INSTALL_FILE}"
chmod a+wrx -R "${TMP_FILE_PATH}${INSTALL_FILE}"
x_install_mbbservice()
echo "now begin to install... " | tee -a ${LOG_PATH}
export DISPLAY=":0"
echo "Run xterm and begin to install" | tee -a ${LOG_PATH}
TERMINAL=`which xterm`
${TERMINAL} '-e' "${TMP_FILE_PATH}${INSTALL_FILE}${INSTALL_SHELL}"
echo "Exit install and remove temporary files" | tee -a ${LOG_PATH}
#install_exit
if which gnome-
echo "Run gnome-terminal and begin to install" | tee -a ${LOG_PATH}
TERMINAL=`which gnome-terminal`
${TERMINAL} '-e' "${TMP_FILE_PATH}${INSTALL_FILE}${INSTALL_SHELL}"
echo "Exit install and remove temporary files" | tee -a ${LOG_PATH}
#install_exit
echo "Run konsole and begin to install" | tee -a ${LOG_PATH}
TERMINAL=`which konsole`
${TERMINAL} '-e' "${TMP_FILE_PATH}${INSTALL_FILE}${INSTALL_SHELL}"
echo "Exit install and remove temporary files" | tee -a ${LOG_PATH}
#install_exit
echo "Run shell and begin to install" | tee -a ${LOG_PATH}
"${TMP_FILE_PATH}${INSTALL_FILE}${INSTALL_SHELL}"
echo "Exit install and remove temporary files" | tee -a ${LOG_PATH}
#install_exit
#check_first_install
#if [ "${FIRST_INSTALL}" = "YES" ]
backup_ISO
x_install_mbbservice
#verify_version
16.250003] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
16.252812] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
16.252830] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
18.225129] NET: Registered protocol family 40
20.031863] init: plymouth-upstart-bridge main process ended, respawning
20.038509] init: plymouth-upstart-bridge main process (1714) terminated with status 1
20.038524] init: plymouth-upstart-bridge main process ended, respawning[ ] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ ] usb 1-1: New USB device found, idVendor=12d1, idProduct=1f01
[ ] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ ] usb 1-1: Product: HUAWEI_MOBILE
[ ] usb 1-1: Manufacturer: HUAWEI_MOBILE
[ ] usb 1-1: SerialNumber: ABCDEF
[ ] usb-storage 1-1:1.0: USB Mass Storage device detected
[ ] scsi host33: usb-storage 1-1:1.0
[ ] usbcore: registered new interface driver usb-storage
[ ] usbcore: registered new interface driver uas
[ ] scsi 33:0:0:0: CD-ROM
Mass Storage
2.31 PQ: 0 ANSI: 2
[ ] scsi 33:0:0:1: Direct-Access
TF CARD Storage
2.31 PQ: 0 ANSI: 2
[ ] sr 33:0:0:0: [sr1] scsi-1 drive
[ ] sr 33:0:0:0: Attached scsi CD-ROM sr1
[ ] sr 33:0:0:0: Attached scsi generic sg2 type 5
[ ] sd 33:0:0:1: Attached scsi generic sg3 type 0
[ ] sd 33:0:0:1: [sdb] Attached SCSI removable disk
[ ] ISO 9660 Extensions: Microsoft Joliet Level 1
[ ] ISOFS: changing to secondary root[ ] usb 1-1: USB disconnect, device number 2
[ ] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ ] usb 1-1: New USB device found, idVendor=12d1, idProduct=14dc
[ ] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ ] usb 1-1: Product: HUAWEI_MOBILE
[ ] usb 1-1: Manufacturer: HUAWEI_MOBILE
[ ] usb-storage 1-1:1.2: USB Mass Storage device detected
[ ] scsi host34: usb-storage 1-1:1.2
[ ] cdc_ether 1-1:1.0 eth1: register 'cdc_ether' at usb-.0-1, CDC Ethernet Device, 0c:5b:8f:27:9a:64
[ ] usbcore: registered new interface driver cdc_ether
[ ] cdc_ether 1-1:1.0 eth1: kevent 11 may have been dropped
[ ] scsi 34:0:0:0: Direct-Access
TF CARD Storage
2.31 PQ: 0 ANSI: 2
[ ] sd 34:0:0:0: Attached scsi generic sg2 type 0
[ ] sd 34:0:0:0: [sdb] Attached SCSI removable disk
[ ] cdc_ether 1-1:1.0 eth1: kevent 12 may have been dropped
[ ] cdc_ether 1-1:1.0 eth1: kevent 12 may have been dropped
[ ] cdc_ether 1-1:1.0 eth1: kevent 12 may have been dropped
then open the ip address http://192.168.81.
we can get
hardware infomation as below :
IMEI： 875
IMSI： 486
本机号码： 未知
硬件版本号： CL2E3372HM
软件版本号： 22.180.05.00.00
Web UI 版本： 17.100.06.00.03
LAN MAC 地址： 00:0D:87:8E:4B:AC
WAN IP 地址： 10.200.104.175Cisco GSS Command Reference (Software Version 3.1) - Cisco Global Site Selector CLI Commands [Cisco ACE GSS 4400 Series Global Site Selector Appliances] - Cisco
Cisco GSS Command Reference (Software Version 3.1)
Book Contents
Book Contents
Available Languages
Download Options
Book Title
Cisco GSS Command Reference (Software Version 3.1)
Chapter Title
Cisco Global Site Selector CLI Commands
View with Adobe Reader on a variety of devices
Chapter: Cisco Global Site Selector CLI Commands
Chapter Contents
Cisco Global Site Selector CLI Commands
This chapter provides detailed information for the following types of Global Site Selector (GSS) CLI commands:
oGeneral commands that you can enter after you log in to the GSS in user EXEC and privileged EXEC modes.
oGlobal configuration commands that you enter after you log in to the GSS in privileged EXEC mode.
oInterface configuration commands that you enter after logging in to the GSS in privileged EXEC mode.
oGlobal server load-balancing configuration commands that you enter after logging in to the GSS in privileged EXEC mode.
oDomain and source address list commands that you enter after you access the global server load-balancing configuration mode.
oAnswer and answer group commands that you enter after you access the global server load-balancing configuration mode.
oDomain Name System (DNS) rule configuration commands that you enter after you access the global server load-balancing configuration mode.
oDNS sticky configuration commands that you enter after you access the global server load-balancing configuration mode.
oProximity configuration commands that you enter after you access the global server load-balancing configuration mode.
The documentation of each command contains the following information:
oCommand Syntax—Information about the correct structure and syntax for the command
oUsage Guidelines—Detailed information that describes the purpose of the command and its proper application
oExamples—Command syntax as it appears in a CLI session
oRelated Commands—Other CLI commands with a purpose that is closely related to or dependent on the current command
For more information about accessing a CLI session and using CLI commands, see .
The following general commands are available to you immediately after you log in to a GSS. The commands that you can access depend on your permission level.
oUser EXEC permission level provides access to the following commands and any associated no forms:
–dnslookup
oPrivileged EXEC permission level provides access to all general commands. You can also access commands in the following modes: global configuration, interface configuration, global server load-balancing configuration, and subordinate global server load-balancing configuration modes.
To display a list of the available commands and syntax options, use the ? command.
Syntax Description
This command has no keywords or arguments.
Command Modes
All command modes
Usage Guidelines
This command displays the commands and syntax options available to you at the point at which you enter the command. For additional background on the use of GSS help, see .
The following example shows how to display a list of the available commands and syntax options:
gss1.example.com& ?
Change directory
CNR Related commands
Directory list
DDoS exec commands
dnslookup Resolve hostname (DNS)
Turn on privileged commands
Exit from the EXEC
Open FTP session to host
Description of the interactive help system
list files in long info
Directory list
Ping a remote host
Show present working directory
SecureCopy files [scp from to]
Show running system information
Display last 10 lines of a file
Open telnet session to host
View a file
host(config)# show ?
access-group
Configure access lists
access-list
Configure access lists
Display system ARP cache
boot-config
Display bootable GSS software images
Display system clock
DDoS exec commands
Display disk information
Display ftp status
gslb-config
Show configuration for gslb objects
gslb-errors
Show errors during most recent script-play
Configure interface
Show inventory information
Display IP information
Show license information
Configure system logging
Display GSS system log
Display memory information
NTP service control
Display processes on system
properties
Display system properties
Display Proximity subsystem information
running-config
Show running configuration
Display status of basic services
Display SNMP information
Display SSH status
startup-config
Show startup configuration
statistics
Display statistics
Display Sticky Database information
system-status
Report status of GSS
Display TACACS+ configuration
tech-support
Display information useful to Cisco TAC
Display telnet status
terminal-length Display terminal-length
Display system uptime
Display user information
Display configured users
Display system version
Related Commands
To change the directory, use the cd command.
cd directoryname
Syntax Description
directoryname
Name of the directory.
Command Modes
User and privileged EXEC
Usage Guidelines
Use this command to maneuver between directories and for file management. The directory name becomes the default prefix for all relative paths. Relative paths do not begin with a slash (/). Absolute paths begin with a slash (/).
Enter cd .. to move to the directory that is one level higher than the one that you are in.
The following example shows the relative path:
gss1.example.com& cd local1
The following example shows the absolute path:
gss1.example.com& cd /local1
Related Commands
To reset GSS statistics for a specific subsystem, use the clear command.
clear statistics {boomerang | ddos [all | attacks | drops | global ] | dns | drpagent | keepalive {all | cra | http-head | icmp | kalap | ns | tcp} | proximity | sticky {mesh} | tacacs}
Syntax Description
statistics
Resets load-balancing statistics on the GSS.
Resets statistics that relate to the boomerang server component of the GSS.
Resets statistics that relate to the Distributed Denial of Service (DDoS) detection and mitigation component of the GSS.
(Optional) Resets global statistics that relate to the GSS DDoS detection and mitigation component.
(Optional) Resets attack statistics that relate to the GSS DDoS detection and mitigation component.
Resets statistics that relate to the Domain Name System (DNS) server component of the GSS, including proximity and sticky DNS rule statistics.
Resets statistics that relate to the DRP agent component of the GSS.
Resets statistics that relate to the keepalive function of the GSS software.
Resets statistics for all keepalive types maintained by the GSS.
Resets statistics for only content routing agent (CRA)-type keepalives maintained by the GSS.
Resets statistics for only the VIP HTTP-HEAD type keepalive maintained by the GSS.
Resets statistics for only the VIP ICMP-type keepalive maintained by the GSS
Resets statistics for only the VIP KAL-AP-type keepalive maintained by the GSS.
Resets statistics for the Name Server-type keepalive maintained by the GSS.
scripted-kal
Resets statistics for the Scripted-Kal-type keepalive maintained by the GSS.
Resets statistics for the IP and port TCP-type keepalive maintained by the GSS.
Resets statistics for the network proximity function.
Resets statistics for the DNS sticky function.
Resets mesh and session statistics for the local GSS node of the global sticky mesh.
Resets TACACS+GSSM statistics.
Command Modes
Privileged EXEC
Usage Guidelines
Use the clear command to reset global server load-balancing statistics for one or more of your GSS components. Clearing the statistics for a GSS component will erase all record of routing activity and performance for that device.
The following example shows how to use the clear command:
gss1.example.com# clear statistics boomerang
Are you sure? (yes/no) yes
gss1.example.com# clear statistics dns
Are you sure? (yes/no) yes
cra keepalive statistics cleared
gss1.example.com# clear statistics keepalive kalap
Are you sure? (yes/no) yes
kal-ap keepalive statistics cleared
gss1.example.com# clear statistics proximity
Are you sure? (yes/no) yes
proximity statistics cleared
To clear the configuration from the Distributed Denial of Service (DDoS) detection and mitigation subsystem, use the clear ddos-config command.
clear ddos-config
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
The following example shows how to clear the configuration from the DDoS detection and mitigation subsystem:
gss1.example.com# clear ddos-config
gss1.example.com#
To perform the following actions, use the clock command:
oRead the hardware calendar into the system clock
oSet the current time or time zone for a GSS device
oSet daylight saving time to some predefined summer time
oReset the GSS to synchronize log time stamps to a new time zone
oUpdate the hardware calendar from the system clock
oSet a user-defined daylight saving time
oSpecify a user-defined time zone
clock {read-calendar | set hh:mm:ss MONTH DD YYYY | summer-time timezone | timezone timezonename | update-calendar | user-summer-time summer-time name | start time | start day |
start week | start month | end time | end day | end week | end month | offset | user-timezone timezone name | hour_offset | minute_offset}
Syntax Description
read-calendar
Reads the hardware calendar into the system clock. You can use this command when the system clock is reset through NTP and you want to revert back to using the hardware clock.
Sets the device clock to the date and time provided.
Current time to which the GSS device clock is being reset. Specify one or two digits for the hours, minutes, and seconds.
MONTH DD YYYY
Current date to which the GSS device clock is being reset. Specify the full name of the month, one or two digits for the day, and four digits for the year. The following month names are recognized:
oSeptember
summer-time
Sets daylight saving time to some predefined summer times.
Name of the predefined time zone. The following time zones are recognized:
oADT (Atlantic Daylight Time)
oAKDT (Alaska Standard Daylight Time)
oCDT (Central Daylight Time)
oEDT (Eastern Daylight Time)
oMDT (Mountain Daylight Time)
oPDT (Pacific Daylight Time)
Resets the GSS to synchronize log time stamps to a new time zone.
timezonename
Name of the timezone. Enter ? to list all supported time zones, countries, continents, and cities. The following options are available to set the local time zone for your GSS:
oStandard time zone (for example, GMT, EST, UTC)
oCountry or part of a continent (for example, America, Europe, Egypt)
oSpecific city (for example, New York, Paris)
update-calendar
Updates the hardware calendar from the system clock. You can use this command when the system clock is reset through NTP and you want to synchronize the system time with the hardware clock.
user-summer-time
Sets a user-defined daylight saving time.
summer-time name
Name of the user-defined summer time.
start time
Start time for the user-defined summer time in hours and minutes. Values from 0-23 are recognized.
Start day for the user-defined summer time.The following days are recognized:
oWednesday
start week
Start week for the user-defined summer time. Values from 1-5 are recognized.
start month
Start month for the user-defined summer time. The following month names are recognized:
oSeptember
End time for the user-defined summer time in hours and minutes. Values from 0-23 are recognized.
End day for the user-defined summer time. The following days are recognized:
oWednesday
End week for the user-defined summer time. Values from 1-5 are recognized.
End month for the user-defined summer time. The following month names are recognized:
oSeptember
Offset (in minutes) for the user-defined time zone. Values from 0-1440 are recognized.
user-timezone
Specifies a user-defined time zone.
timezone name
Name of the user-defined time zone.
hour_offset
Hour offset for the user-defined time zone. Values from -23 to +24 are recognized.
minute_offset
Minute offset for the user-defined time zone. Values from 0-59 are recognized.
Note The clock update-calendar and read-calendar commands allow you to synchronize the hardware clock and system clock without reloading the GSS.
Command Modes
Privileged EXEC, global configuration, and interface configuration.
Usage Guidelines
If you previously enabled NTP on a GSS using the ntp enable command, the GSS prevents you from using the clock set command and displays an error message. If you want to manually set the clock for the GSS, first disable NTP using the no ntp enable command before setting the clock.
The following example shows how to set the GSS device time:
gss1.example.com# clock set 13:01:05 sept 15 2004
gss1.example.com# clock timezone GMT
The following example shows how to set the GSS time zone:
gss1.example.com# clock timezone europe paris
The following example shows how to set a user-defined time zone on the GSS:
gss1.example.com# clock user-timezone EST -5 0
Please restart the GSS (reload) to sync log timestamps to new timezone.
The following example shows how to set the user-defined summer time on the GSS:
gss1.example.com# clock user-summertime 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.
The following example shows how to update the hardware calendar from the system clock:
gss1.example.com# clock update-calendar
The following example shows how to read the hardware calendar into the system clock:
gss1.example.com# clock read-calendar
To enter the Cisco Network Registrar (CNR) command line interface (the nrcmd program), use the cnr command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
Note Before entering nrcmd, you must first install and enable CNR.
Upon successful execution of this command, you are prompted for a username and password.
See the Cisco Network Registrar CLI Reference Guide v6.2 for instructions about using the CNR configuration mode commands.
For information about CNR software and CNR licensing restrictions, see the Cisco Global Site Selector Administration Guide.
The following example shows how to enter CNR configuration mode:
gssm1.example.com# cnr
username: &user_name&
password: ******
cluster = localhost
current-vpn = global
default-format = user
groups = superuser
roles = superuser
scope-edit-mode = staged
user-name = admin
visibility = 5
zone-edit-mode = synchronous
Related Commands
To configure the CNR GUI access mode for HTTP, HTTPS, or both protocols, use the following command in exec mode:
cnr access-mode enable {http | https | both}
Syntax Description
HTTP access only is enabled. This is the default.
HTTPS access only is enabled.
HTTP and HTTPS access are enabled.
Command Modes
Privileged EXEC
Usage Guidelines
To enable HTTPS access on port 8443, you need to create a keystore file, copy it to the GSS, and then enable the HTTPS option on the GSS.
When you enable HTTPS access using the https or both keywords, the CLI prompts you to enter the keystore filename (including the path) and password.
When you enable a different access mode setting, the GSS automatically disables the previous setting. For example, if you change the access mode from HTTP to HTTPS, the GSS disables HTTP access.
You must disable CNR before configuring the access mode and then enable CNR when you have completed the configuration process.
For information about CNR, including configuring the CNR GUI access mode and CNR licensing restrictions, see the Cisco Global Site Selector Administration Guide.
The following example shows how to configure the CNR GUI access mode for both HTTP and HTTPS:
gss.example.com# config
gss.example.com(config)# no cnr enable
gss.example.com(config)# exit
gss.example.com# cnr access-mode enable both
gss.example.com# config
gss.example.com(config)# cnr enable
Related Commands
CNR regularly backs up its database once a day automatically. You can modify the time at which CNR performs the backup by using the following command in privileged EXEC mode:
cnr backup-time edit time
Syntax Description
Specifies the time of day. Use the hh:mm format to specify the time as follows:
ohh—Specifies the hour of the day. Enter a value from 0 to 23. The default is 23.
omm—Specifies the minute. Enter a value from 0 to 59. The default is 45.
Command Modes
Privileged EXEC
Usage Guidelines
If you configure the time for 0:0, CNR backs up the database during the first minute of each day.
You must disable CNR before configuring the backup time and then enable CNR when you have completed the configuration process.
For information about CNR, including configuring the CNR database backup time and CNR licensing restrictions, see the Cisco Global Site Selector Administration Guide.
The following example show how to configure the backup time to 5:45&AM:
gss.example.com# config
gss.example.com(config)# no cnr enable
gss.example.com(config)# exit
gss.example.com# cnr backup-time edit 5:45
gss.example.com# config
gss.example.com(config)# cnr enable
gss.example.com(config)#
Related Commands
To install Cisco Network Registrar (CNR) on your GSS, use the cnr install command. To uninstall CNR, use the cnr uninstall command.
cnr install cnr-package
cnr uninstall
Syntax Description
cnr-package
Name of the CNR package.
Command Modes
Privileged EXEC
Usage Guidelines
You can install CNR without first obtaining the GSS license for the CNR module. It is not mandatory to have both the license file for installing CNR on the GSS and the CNR software package itself.
The CNR software package contains the response file for silent installation, config_cnr, which configures the CNR ports that listen to the GSS.
The cnr uninstall command also removes the CNR Security Kit if the kit is loaded on the GSS. Before you can uninstall CNR, you must disable it by using the no cnr enable command in configuration mode.
Note Prior to the release of GSS software version 3.1, Cisco announced the end-of-sale and end-of-life dates for the integrated version of CNR. As a result of this announcement, new SF-GSS-DNSLIC software licenses that enable the integrated CNR are no longer available. This guide provides CNR information for use by existing CNR license holders only. To request more information regarding this change, including guidance for migration options from the integrated version of CNR running on the GSS, send your request to ask-.
For information about installing and activating the CNR software, see the Cisco Global Site Selector Administration Guide.
The following example shows how to install the CNR package on the GSS:
gssm1.example.com# cnr install cnr_pak.tar
The following example shows how to disable CNR and then uninstall it:
gssm1.example.com# configure
gssm1.example.com(config)# no cnr enable
gssm1.example.com(config)# exit
gssm1.example.com# cnr uninstall
Related Commands
To install and manage the Cisco Network Registrar (CNR) Security Kit on your GSS, use the cnr security-kit command.
cnr security-kit {install filename mode {disable | optional | required} | mode {required | optional | disable} | uninstall}
Syntax Description
install filename
Specifies the name of the security kit file.
Specifies the security kit operating mode. Enter one of the following options:
odisable—Specifies that CNR does not use the installed security kit to establish secure connections with other CNR components on the GSS network.
ooptional—Specifies that CNR uses an unsecure connection if it cannot create a secure connection.
orequired—Specifies that CNR must use the security kit to create secure connections with with other CNR components on the GSS network. If a secure connection cannot created, then the servers will fail.
Uninstalls the CNR Security Kit software.
Command Modes
Privileged EXEC
Usage Guidelines
You can install the optional CNR Security Kit that uses secure sockets layer (SSL) to enable secure communication channels between the various CNR components running on a GSS mesh. For example, if a GSS network consists of four GSS devices with CNR running on each of them, the CNR components communicate with each other to perform such functions a s configuration synchronization or other data synchronization. Without the CNR Security Kit installed, the CNR components communicate with each other over an unsecure channel. Installing the security kit on each of the GSS devices installs the SSL library which enables secure communication channels between the four CNR components.
You must have Cisco Network Registrar Release 6.1.4 or later installed on your GSS devices to use the CNR Security kit.
You must disable CNR before using the cnr security-kit command.
For information about CNR, including the CNR security kit and CNR licensing restrictions, see the Cisco Global Site Selector Administration Guide.
The following examples show how to install the CNR Security Kit:
gss.example.com# config
gss.example.com(config)# no cnr enable
gss.example.com(config)# exit
gss.example.com# cnr security-kit install cnrsec_2_0_1-linux4.gtar.gz mode required
Successfully installed CNR security kit
gss.example.com# config
gss.example.com# cnr enable
Related Commandsgss.example.com#
To enter the restricted Cisco Network Registrar (CNR) shell and execute the available CNR utilities, use the cnr shell command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
Upon successful execution of this command, you can press the Tab key to see the available utilities in the CNR shell. You can then execute any of these utilities by entering the utility name. See the Cisco CNS Network Registrar User's Guide for more information about the available utilities.
For information about using CNR with the GSS, including CNR licensing restrictions, see the Cisco Global Site Selector Administration Guide.
The following example shows how to enter the CNR shell, display the utilities, and then execute the cnr_tactool utility:
gssm1.example.com# cnr shell
cnr shell& cnr &Tab&
cnr_tactool.orig
cnrdb_load
cnrdb_verify
cnr_exim.orig
cnrdb_archive
cnrdb_printlog
cnrservagt
cnr_keygen
cnrdb_checkpoint cnrdb_recover
cnr_keygen.orig cnrdb_deadlock
cnrdb_stat
cnr_tactool
cnrdb_dump
cnrdb_upgrade
cnr shell &
cnr shell&
cnr shell& cnr_tactool
Related Commands
To enter global configuration mode, use the configure command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
To exit global configuration mode, use the
commands, or by pressing the Ctrl-Z key sequence.
The following example shows how to enter global configuration mode:
gss1.example.com# configure
gss1.example.com(config)#
Related Commands
To copy configuration settings to or from the GSS device, use the copy command.
copy {ddos-config disk filename | disk startup-config filename | gslb-config disk filename | startup-config disk filename | running-config [disk&filename&|&startup-config]}
Syntax Description
ddos-config disk
Copies the Distributed Denial of Service (DDoS) configuration file to a named file on disk.
Name of the output file containing the GSLB-configuration, startup-configuration or running-configuration information.
disk startup-config
Loads the GSS device startup configuration settings from a named file located on the GSS.
gslb-config disk
Copies the global server load-balancing configuration to a named file on the GSS.
startup-config disk
Copies the GSS device startup configuration to a named file on the GSS.
running-config disk
Copies the GSS device current running configuration to a named file on the GSS.
running-config startup-config
Copies the GSS device current running configuration as the new startup configuration.
Command Modes
Privileged EXEC
Usage Guidelines
When supplying an output filename enter the name only. Do not include path information with the filename.
The following examples show that the copy command is used to load a new startup configuration to the device from a file and to copy the current running configuration to a file:
gss1.example.com# copy disk startup-config configfile
gss1.example.com# copy running config disk runconfigfile
Related Commands
Different Domain Name System (DNS) zones may exhibit different behavior. A high traffic rate on one D-proxy may be perfectly normal for another. A peacetime learning process is required on the GSS.
To configure peacetime learning in the GSS, use the ddos peacetime command and its related commands.
ddos peacetime [apply {increment | overwrite} | database erase | save filename | show [filename | status] | start | stop]
apply {increment | overwrite}
command for a detailed syntax description.
database erase
command for a detailed syntax description.
save filename
command for a detailed syntax description.
show [filename | status]
command for a detailed syntax description.
command for a detailed syntax description.
command for a detailed syntax description.
To apply values learned during the peacetime learning process to the rate-limit database, use the ddos peacetime apply command.
ddos peacetime apply {increment | overwrite}
Syntax Description
Specifies that you want to apply the peacetime learned values incrementally to the database.
Specifies that you want to restore all the values in the rate-limit database to their defaults and then update them with the values learned during peacetime.
Command Modes
Privileged EXEC
Usage Guidelines
This command updates the rate-limit database with the peacetime learned values.
The peacetime database location is specified in the
command. If you do not specify this command, the in-memory database is used instead.
The following example shows how to apply values learned during the peacetime learning process to the rate-limit database:
gssm1.example.com# ddos peacetime apply increment
gssm1.example.com#
Related Commands
To erase peacetime learning, use the ddos peacetime database erase command.
ddos peacetime database erase
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
The following example shows how to erase peacetime learning:
gssm1.example.com# ddos peacetime database erase
gssm1.example.com#
Related Commands
To save peacetime learning to the memory or to a file on a disk, use the ddos peacetime save command in privileged EXEC mode.
ddos peacetime save filename
Syntax Description
Name of the file on the disk to which you want to save peacetime learning.
Command Modes
Privileged EXEC
The following example shows how to save peacetime learning:
gssm1.example.com# ddos peacetime save samplefile
gssm1.example.com#
Related Commands
To show values learned during the peacetime learning process or show the peacetime learning status, use the ddos peacetime show command.
ddos peacetime show [filename | status]
Syntax Description
(Optional) Filename of the peacetime learning process that you want do display values.
(Optional) Specifies that you want to display the current peacetime learning status.
Command Modes
Privileged EXEC
The following example shows how to display the peacetime status:
gssm1.example.com# ddos peacetime show status
DDoS Peacetime Learning is running.
gssm1.example.com#
Related Commands
To start the peacetime learning process, use the ddos peacetime start command.
ddos peacetime start
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
This command incrementally updates the values in the peacetime database.
The following example shows how to start peacetime learning:
gssm1.example.com# ddos peacetime start
gssm1.example.com#
Related Commands
To stop peacetime learning, use the ddos peacetime stop command.
ddos peacetime stop
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
The following example shows how to stop peacetime learning:
gssm1.example.com# ddos peacetime stop
gssm1.example.com#
Related Commands
To restore the default rate-limit values in the rate-limit database, use the ddos restore-defaults command.
ddos restore-defaults ipaddress
Syntax Description
D-proxy IP address. Indicates that you want to restore the rate limit of the designated D-proxy to the default rate and the state to Unknown.
Command Modes
Privileged EXEC
The following example shows how to restore the defaults in the rate-limit database:
gssm1.example.com# ddos restore-defaults 1.1.1.2
gssm1.example.com#
Related Commands
To delete files from your GSS device, use the del command.
del filename
Syntax Description
Name of the file to be deleted.
Command Modes
Privileged EXEC
The following example shows how to delete files from your GSS device:
gss1.example.com& enable
gss1.example.com# del oldtechrept.tgz
gss1.example.com#
Related Commands
To view a long list of files in a directory, use the dir command.
dir [directory]
Syntax Description
(Optional) Name of the directory to list.
Command Modes
User and privileged EXEC
Usage Guidelines
Use this command to view a detailed list of files contained within the working directory, including names, sizes, and the time created. The equivalent command is lls.
The current directory is the default directory.
The following example shows how to view a long list of files in a directory:
gss1.example.com# dir
total 771884
drwxrwxrwx
drwxrwxrwx
8 11:13 ..
drwx------
4096 Jan 23
-rw-r--r--
2006 ACR_new.upg
-rw-r--r--
2006 ACR_new1.upg
-rw-r--r--
2006 ACR_new2.upg
-rw-r--r--
2006 gss-1.2.2.2.0-k9.upg
-rw-r--r--
2006 gss-1.3.0.3.0-k9.upg
-rw-r--r--
8 10:54 gss-1.3.0.4.1-k9.upg
-rw-r--r--
8 11:09 one
-rw-r--r--
8 11:06 proximitySchema.xsd
-rw-r--r--
8 11:07 stickySchema.xsd
gss1.example.com#
Related Commands
To turn off privileged EXEC mode, use the disable command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
The disable command places you in user EXEC mode. To turn privileged EXEC mode back on, use the
The following example shows how to turn off privileged EXEC mode:
gss1.example.com# disable
gss1.example.com&
Related Commands
To resolve a host or domain name to an IP address, use the dnslookup command.
dnslookup {hostname | domainname}
Syntax Description
Name of the host on the network.
domainname
Domain name.
Command Modes
User and privileged EXEC
The following examples show how the dnslookup command is used to resolve the hostname myhost.cisco.com to IP address 172.31.69.11, cisco.com to IP address 192.168.219.25, and the IP address 10.86.209.210 to gss.cisco.com:
gss1.example.com# dnslookup myhost.cisco.com
mydnsserver.cisco.com
172.16.69.12
myhost.cisco.com
Address: 172.16.69.11
gss1.example.com# dnslookup cisco.com
dns-bxb.cisco.com
161.44.124.122
www.cisco.com
198.168.219.25
gss1.example.com# dnslookup 10.86.209.210
dns-bxb.cisco.com
161.44.124.122
gss.cisco.com
10.86.209.210
To access privileged EXEC commands, use the enable command.
Syntax Description
This command has no keywords or arguments.
Command Modes
User and privileged EXEC
Usage Guidelines
To access privileged EXEC mode from user EXEC mode, use the enable command. The
command takes you from privileged EXEC mode to user EXEC mode.
If you are accessing the GSS remotely using Telnet or SSH, the CLI prompts you for the enable password. The default password is default. For more information about the enable password and configuring a new password, see the
The following example shows how to access privileged EXEC commands:
gss1.example.com& enable
gss1.example.com#
Related Commands
To change the enable command password, use the enable-passwd command.
enable-passwd
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
You can control user access to the privileged Exec mode for users that remotely connect to the GSS using Telnet or SSH. When connecting to the GSS remotely, the CLI prompts you for a password when you enter the enable command to access the privileged Exec mode. The default password is default.
You have to be the admin user to configure the enable password.
When you enter the enable-passwd command, the CLI prompts you for an admin password and then to define and confirm the enable password. The password is alphanumeric, can contain spaces and special characters, and can contain a maximum of 32 characters. Leave the password blank to set the password to the default value, which is default.
Note The enable password is not required when you access the GSS using a console or terminal session. If you forget the enable password, use a console or terminal session to configure a new password.
The following example shows how to configure the enable password:
localhost.localdomain# enable-passwd
Admin Password: &admin_password&
Set GSS enable Password: &enable_password&
Confirm GSS enable Password: &enable_password&
Related Commands
To exit the EXEC or global configuration command shell, use the end command.
Syntax Description
This command has no keywords or arguments.
Command Modes
EXEC and global configuration
Usage Guidelines
Use the end command in any configuration mode to return to EXEC mode. This command is equivalent to pressing Ctrl-Z or using the exit command.
The end command entered in the user-level EXEC shell terminates the console or Telnet session.
The following example shows how to exit the EXEC or global configuration command shell:
gss1.example.com(config)# end
gss1.example.com# end
gss1.example.com&
Related Commands
To access the EXEC command shell from the global or interface configuration command shells, use the exit command.
Syntax Description
This command has no keywords or arguments.
Command Modes
All command modes
Usage Guidelines
Use the exit command in any configuration mode to return to EXEC mode. This command is equivalent to the
command or pressing Ctrl-Z.
The exit command entered in the user-level EXEC shell terminates the console or Telnet session.
The following example shows how to access the EXEC command shell from the global or interface configuration command shells:
gss1.example.com(config)# exit
gss1.example.com# exit
gss1.example.com&
Related Commands
To launch an FTP session on your GSS device, use the ftp command.
ftp ip_or_host
Syntax Description
ip_or_host
IP address or hostname of the FTP server that you want to access. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1) or a mnemonic hostname (for example, myhost.mydomain.com).
Command Modes
User EXEC and privileged EXEC
Usage Guidelines
Use the ftp command in EXEC mode to launch the FTP client and transfer a file to and from remote machines.
The following example shows how to launch an FTP session on your GSS device:
gss1.example.com# ftp 192.168.0.1
Related Commands
To manage your GSS devices, use the gss command.
gss {disable | enable {gssm-primary | gssm-standby {primary_GSSM_hostname | primary_GSSM_IP_address} | gss {primary_GSSM_hostname | primary_GSSM_IP_address} | restart | start | status [verbose] | stop}
Syntax Description
Disables the selected device (GSSM or GSS) and removes any existing configuration, including deleting the Global Site Selector Manager (GSSM) database from the GSS device and removing certificate attributes specified using the certificate set-attributes command. This keyword returns the GSS device to the initial, disabled state. Disabling a GSS device is only necessary when you want to switch the role of a GSS within a network (for example, change a GSS to a GSSM or if you need to move a GSS or GSSM to a different network of GSS devices.
Enables the selected device to act as the type of device that you specify: either a GSSM or GSS. This keyword creates the embedded database on the primary GSSM that stores and manages the configuration information for the GSS network. It also performs all of the other initialization processes to enable the device in a network of GSS devices. Enabling a GSS device is a one-time initialization step that is required only when you first set up the device within a network of GSS devices.
gssm-primary
Configures the selected device to act as the primary GSSM for your GSS network, responsible for maintaining status information about GSS devices and load-balancing information that is distributed to devices on the network.
gssm-standby
Configures the selected device to act as a standby GSSM which will take over GSS network management should the primary GSSM go offline.
primary_GSSM_hostname
Domain Name System (DNS) hostname of the device currently serving as the primary GSSM.
primary_GSSM_IP_address
Network address of the device currently serving as the primary GSSM.
Indicates that the selected device should function as a GSS on the GSS network.
Stops and restarts the GSS software on the selected device.
Starts the GSS software on the selected device following the initial configuration or a software upgrade.
Displays detailed information about the current operating state of the GSS device including the online status, the software version, and the start date or time for the various components. The equivalent command is the show system-status command.
Note The status of the License Manager (LM) and the Distributed Denial of Service (DDoS) prevention module do not appear in the output of the gss status command. Instead, you enter the show ddos status command to obtain DDoS information and the show processes | grep license_manager command to obtain the LM status.
(Optional) Displays the same detailed information about the current operating state of the GSS device as with the gss status command, including the CPU utilization.
Note Calculating the CPU utilization can take additional time when using the gss status verbose command. On a busy system, the gss status verbose command can take approximately 10&seconds to complete. If you do not require calculation of the CPU Utilization operating parameter, then we recommend that you use the gss status command.
Stops the GSS software before a software upgrade, maintenance, or troubleshooting activities.
Command Modes
Privileged EXEC
Usage Guidelines
The gss command provides a variety of options for managing your GSSs and GSSMs, including:
oDesignating individual devices to act as a GSS, primary GSSM, or standby GSSM using the gss, gssm-primary, or gssm-standby keywords of the gss command.
oControlling the GSS servers on the device so that you can perform the required maintenance and software upgrades using the start, stop, and restart commands.
The following example shows how to manage your GSS devices:
gssm1.example.com# gss status
Cisco GSS - 1.2(2) GSS [Thu Mar 31 21:09:09 UTC 2005]
Registered to primary GSSM: 10.86.209.167
Normal Operation [runmode = 5]
Config Agent (crdirector)
Config Server (crm)
DNS Server
GUI Server (tomcat)
Keepalive Engine
Node Manager
Web Server (apache)
When the DNS server is ready to serve DNS requests, it generates the following subsystem log message and saves it in the system.log file:
Mar 25 10:45:26 gssm1.example.com DNS-5-SELREADYINFO[2073] Selector ready to start serving
DNS requests
Related Commands
To generate a detailed report for use by Cisco Technical Assistance Center (TAC) representatives in troubleshooting persistent GSS problems, use the gss tech-report command.
gss tech-report filename
Syntax Description
User-assigned name for the report generated by the gss tech-report command.
Command Modes
Privileged EXEC
Usage Guidelines
The file generated is a tar- format archive file with a .tgz extension.
The following example shows how to generate a detailed report for use by TAC representatives in troubleshooting persistent GSS problems:
gss1.example.com# gss stop
gss1.example.com# gss tech-report gss_techrpt1
Creating report for Cisco TAC. This may take a few minutes...
Created debug package: /home/techrpt1.tgz
Use scp/ftp to retrieve.
To manage your primary and standby Global Site Selector Manager (GSSM) (GSSM) and your GSS database, use the gssm command.
gssm backup full filename | database {invalidate | maintain | purge-log-records {count number_records | days number_days} | report | status | validate}| primary-to-standby | restore filename | standby-to-primary
Syntax Description
Performs a backup of GSSM data on the GSS device.
Performs a backup of both the database component of the GSSM and its network and device configuration information. The primary GSSM backup does not include user files that reside in the /home directory.
Name of the database backup file. This file can be the target file for a database backup action or the source file for a database restore action.
Creates, configures, or removes the embedded database on the GSSM.
invalidate
Invalidates GSSM database records.
Cleans up the GSSM database by defragmenting and optimizing the space allocation.
purge-log-records
Purges system log messages from the GSSM database for a specified number or period of time. This keyword removes the system log messages that appear on the primary GSSM GUI, the System Log list page of the Tools navigation tab.
Purges a quantity of database records up to the last n records.
number_records
Number of database system log records, starting back from the last record, that will be retained when the database is purged.
Purges records that cover a set time period up to n days before today.
number_days
Number of days back, starting from today, for which database system log records will be retained when the database is purged.
Generates and displays a report that identifies invalidated database records in the GSSM database.
Reports the current running status of the GSSM database.
Validates GSSM database records.
primary-to-standby
Changes the role of the GSSM from the primary to the standby GSSM.
Restores the GSSM from a full backup file.
Name of the GSSM backup image that will be used to restore the device.
standby-to-primary
Changes the role of the GSSM from standby to GSSM.
Command Modes
Privileged EXEC
Usage Guidelines
Use the gssm database command and keyword to manage the embedded GSS database. The various command options allow you to monitor the status of your database and perform standard maintenance tasks such as backing up and restoring the database, validating the database content, and purging records.
Use the gssm restore command and keyword to restore an earlier version of the GSSM from a full backup image.
Use the gssm standby-to-primary and primary-to-standby command and keywords to switch the role of the selected GSSM in your GSS network. You must make sure that your original primary GSSM is offline before attempting to enable the standby GSSM as the new primary GSSM. Having two primary GSSMs active at the same time may result in the inadvertent loss of configuration changes for your GSS network. If this dual primary GSSM configuration occurs, the two primary GSSMs revert to standby mode and you will need to reconfigure one of the GSSMs as the primary GSSM.
The standby GSSM can temporarily take over the role as the primary GSSM if the the primary GSSM is unavailable (for example, you need to move the primary GSSM or you want to take it offline for repair or maintenance). The switching of roles between the designated primary GSSM and the standby GSSM is intended to be a temporary GSS network configuration until the original primary GSSM is back online. The interim primary GSSM can be used to monitor GSS behavior and make configuration changes if necessary. Once the original primary GSSM is available, reassign the two GSSMs to their original roles in the GSS network as described in the Cisco Global Site Selector Administration Guide.
The following examples show that the gssm database command is used to check the running status of the GSSM embedded database, back up the database to a file, purge all database records except for the last 50, and delete the database:
gss1.example.com# gssm database report
GSSM database validation report written to validation.log
gss1.example.com# gssm database status
GSSM database is running.
gss1.example.com# gssm database validate
GSSM database passed validation.
gss1.example.com# gssm primary-to-standby
Standby GSSM enabled.
gss1.example.com# gssm standby-to-primary
Standby GSSM disabled.
Related Commands
To obtain online help for the GSS CLI, use the help command.
Syntax Description
This command has no keywords or arguments.
Command Modes
User EXEC, privileged EXEC, and global configuration
Usage Guidelines
You can get help at any point when specifying a CLI command by entering a question mark (?). If nothing matches, the help list will be empty, and you must back up until entering a ? shows the available options.
Two methods of help are provided at the CLI:
oFull help is available when you are ready to enter a command argument (for example, show ?) and describes each possible argument.
oPartial help is provided when you enter an abbreviated command and you want to know what arguments match the input (for example, show clock ?).
The following example shows how to obtain online help for the GSS CLI:
gss1.example.com# help
gss1.example.com# help copy ?
To install a new version of the GSS software on your GSS device, use the install command.
install filename
Syntax Description
Name of the software update file.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to install a new image of the GSS software on the Cisco GSS hardware. The upgrade file must be present on the Cisco GSS before you execute this command.
The install command cannot be executed while the Cisco GSS is running (for example, serving Domain Name System [DNS] requests). You must enter the gss stop command before executing the install command.
The following example shows how to install an updated version of the GSS software:
gss1.example.com# install /gss.upg
Related Commands
To install or uninstall a license file on your GSS device, use the license command.
license install filename | uninstall filename
Syntax Description
Installs a license file on the GSS.
Uninstalls a license file on the GSS.
Name of the license file.
Note A valid license file always includes the .lic extension. Otherwise, it is considered invalid and is not installed.
Command Modes
Privileged EXEC
Usage Guidelines
For information about obtaining and installing a license file, see the Cisco Global Site Selector Administration Guide.
The following example shows how to install the Distributed Denial of Service (DDoS) license on the GSS:
gssm1.example.com# license install ddos.lic
Related Commands
To view a long list of files in a directory, use the lls command.
lls [directory]
Syntax Description
(Optional) Name of the directory to list.
Command Modes
User EXEC and privileged EXEC
Usage Guidelines
Use this command to view a detailed list of files contained within the working directory, including names, sizes, and the time created. The equivalent command is .
The current directory is the default directory.
The following example shows how to view a long list of files in a directory:
gss1.example.com# lls
total 771884
drwxrwxrwx
drwxrwxrwx
8 11:13 ..
drwx------
4096 Jan 23
-rw-r--r--
2006 ACR_new.upg
-rw-r--r--
2006 ACR_new1.upg
-rw-r--r--
2006 ACR_new2.upg
-rw-r--r--
2006 gss-1.2.2.2.0-k9.upg
-rw-r--r--
2006 gss-1.3.0.3.0-k9.upg
-rw-r--r--
8 10:54 gss-1.3.0.4.1-k9.upg
-rw-r--r--
8 11:09 one
-rw-r--r--
8 11:06 proximitySchema.xsd
-rw-r--r--
8 11:07 stickySchema.xsd
gss1.example.com#
Related Commands
To view a list of files or subdirectory names within a directory, use the ls command.
ls [directory]
Syntax Description
(Optional) Name of the directory for which you want a list of files.
Command Modes
User EXEC and privileged EXEC
Usage Guidelines
To list the filenames and subdirectories within a particular directory, use the ls directory
to list the filenames and subdirectories of the current working directory, use the ls command. To view the present working directory, use the pwd command.
The current directory is the default directory.
The following example shows how to view a list of files or subdirectory names within a directory:
gss1.example.com# ls
gss-1.0.2.0.2-k9.upg id_rsa.pub megara.back.1_0.full rpms
gss-1.0.904.0.1-k9.upg gss_sample.full megara.back.1_1.full
Related Commands
To view a list of all open files on your GSS device, use the lsof command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Usage Guidelines
To list the names, file properties, and locations of all files that are currently open on your GSS device, use the lsof command.
The following example shows how to view a list of all open files on your GSS device:
gss1.example.com# lsof
492 /sbin/init
29 /lib/ld-2.1.3.so
36 /lib/libc-2.1.3.so
unix 0xf7f86f40
5851 socket
4098 /rw/dev/initctl
unix 0xf7f86f40
5851 socket
4098 /rw/dev/initctl
unix 0xf7f86f40
5851 socket
4098 /rw/dev/initctl
unix 0xf7f86f40
5851 socket
4098 /rw/dev/initctl
unix 0xf7f86f40
5851 socket
4098 /rw/dev/initctl
Related Commands
To negate a CLI command or set it to its default settings, use the no command. Some GSS CLI commands do not have a no form.
no command
Syntax Description
Disables the copying of GSS configuration information or technical support information.
Disables the File Transfer Protocol (FTP) on a GSS device.
Disables Simple Network Management Protocol (SNMP) on a GSS device.
Disables Telnet operations on the GSS device.
Command Modes
Interface configuration, global, and global server load-balancing configuration
Usage Guidelines
Use the no command to disable functions or negate a command. If you need to negate a specific command, such as the default gateway IP address, you must include the specific string in your command, such as no&ip&default-gateway&ip-address.
The following example shows how to negate a CLI command or set it to its default settings:
gss1.example.com(config)# no ip name-server 10.11.12.14
gss1.example.com(config)# no ntp-server 172.16.22.44
To send ICMP echo packets for diagnosing basic network connectivity on networks, use the ping command.
ping {hostname | ip-address}
Syntax Description
Hostname of the system to send an ICMP echo packet.
ip-address
IP address of the system to send an ICMP echo packet.
Command Modes
User and privileged EXEC
Usage Guidelines
To use this command with the hostname argument, make sure that the Domain Name System (DNS) functionality is configured on your GSS. To force the timeout of a nonresponsive host, or to eliminate a loop cycle, press the Ctrl-C key sequence.
The following example shows how to send ICMP echo packets for diagnosing basic network connectivity on networks:
gss1.example.com# ping gss.cisco.com
PING 172.16.0.0 (172.16.0.0) from 10.1.13.5 : 56(84) bytes of data.
64 bytes from gss.cisco.com (172.16.0.0): icmp_seq=0 ttl=35 time=57.3 ms
64 bytes from gss.cisco.com (172.16.0.0): icmp_seq=1 ttl=35 time=55.8 ms
64 bytes from gss.cisco.com (172.16.0.0): icmp_seq=2 ttl=35 time=55.5 ms
64 bytes from gss.cisco.com (172.16.0.0): icmp_seq=3 ttl=35 time=57.6 ms
64 bytes from gss.cisco.com (172.16.0.0): icmp_seq=4 ttl=35 time=55.3 ms
To remove entries from the proximity database (PDB), use the proximity database delete command.
proximity database delete {all | assigned | group {name} | inactive minutes | ip {ip-address} netmask {netmask} | no-rtt | probed}
proximity database delete
all command in special instances when you want to remove all entries from the PDB in order to have an empty database. Ensure that you want to permanently delete entries from the PDB before you enter this command. You cannot retrieve PDB entries once they are deleted.
Syntax Description
Removes all proximity database entries from the GSS memory.
Removes all static entries from the PBD.
group name
Removes all entries that belong to a named proximity group. Specify the exact name of a previously created proximity group.
inactive minutes
Removes all dynamic entries that have been inactive for a specified time. Valid values are 0-43200&minutes.
ip ip_address netmask netmask
Removes all proximity entries related to a D-proxy IP address and subnet mask. Specify the IP address and subnet mask of the requesting client's D-proxy in dotted-decimal notation (for example, 192.168.9.0 255.255.255.0).
Removes all entries from the PDB that do not have valid RTT values.
Removes all dynamic entries from the PDB.
Command Modes
Privileged EXEC
Usage Guidelines
You can remove all PDB entries from the GSS memory by using the proximity database delete all CLI command. This command, however, does not delete PDB entries saved as part of an automatic dump to a backup file on a disk, which the GSS loads upon a reboot or restart to initialize the PDB. To ensure that you successfully remove all PDB entries from both the GSS memory and disk, enter the proximity database delete all command followed by the proximity database periodic-backup now command to force an immediate backup of the empty PDB residing in the GSS memory.
The prompt &Are you sure?& appears to confirm the deletion of all PDB entries. Specify y to delete all entries or n to cancel the deletion operation.
The following example shows how to remove entries from the proximity database:
gss1.example.com# proximity database delete ip 192.168.8.0 255.255.255.0
Related Commands
To dump all or selected entries from the proximity database to a named file as a user-initiated backup file, use the proximity database dump command.
proximity database dump {filename} format {binary | xml} [entry-type {all | assigned | probed}] [entry-address {ip-address} netmask {netmask}]
Syntax Description
Name of the output file that contains the proximity database entries on the GSS disk. This file resides in the /home directory. The GSS displays a prompt for overwrite confirmation if the filename already exists in the current working directory.
Dumps the proximity database entries in a binary or Extensible Markup Language (XML) format. Choose binary-encoding as the format type if you intend to load the contents of the file into the proximity database of another GSS. The allowable entries are as follows:
obinary—Dumps the assigned proximity entries in a true binary format. This file can only be used with the proximity database load command.
oxml—Dumps the assigned proximity entries in an XML format. The contents of an XML file includes the data fields and the data descriptions. The contents of this file can be viewed using the type command.
Note Dumping PDB entries in an XML format can be a resource-intensive operation and may take from 2-4 minutes to complete depending on the size of the PDB and the GSS platform in use. We recommend that you do not perform a PDB dump in an XML format during the routine operation of the GSS to avoid a degradation in performance.
entry-type
(Optional) Specifies the type of entries to output from the proximity database. The allowable entries are as follows:
oall—Dumps static and dynamic entries from the proximity database. (default)
oassigned—Dumps statically assigned proximity entries.
oprobed—Dumps dynamically probed proximity entries.
entry-address ip-address
(Optional) Specifies the IP address of the proximity database entry.
netmask netmask
Specifies the subnet mask of the proximity database entry in dotted decimal notation (for example, 255.255.255.0).
Command Modes
Privileged EXEC
Usage Guidelines
The GSS automatically dumps proximity database entries to a backup file on a disk approximately every hour. The GSS uses this backup file to initialize the proximity database upon system restart or reboot to enable the GSS to recover the contents of the database.
You can use the proximity database dump command to dump all or selected entries from the proximity database to a named file as a user-initiated backup file. You can then use the ftp command in privileged EXEC mode to launch the FTP client and transfer the file to and from remote machines.
To view the entire contents of the XML proximity database output file from the GSS, use the type command.
The following example shows how to dump the dynamic proximity database entries to a file named PDB6_30_04 in binary format:
gss1.example.com# proximity database dump file PDB6_30_04 format binary entry-type probed
entry-address 172.23.5.7 netmask 255.255.255.255
Related Commands
To load and merge proximity database entries from a file into the existing proximity database in GSS memory, use the proximity database load command.
proximity database load filename format binary [override]
Syntax Description
Name of the proximity database file to load and merge with the existing proximity database on the GSS device. The file must be in a binary format to be loaded into the GSS memory (see the
command). Use the ftp command in privileged EXEC mode to launch the FTP client and transfer the proximity database file to the GSS from a remote GSS.
format binary
Loads the assigned proximity file in a true binary format. The file must be in a binary format to be loaded into the GSS memory.
(Optional) Specifies if the proximity database entries in the file are to override the same entries located in the current GSS proximity database. When you choose the override keyword, static database entries always take priority over dynamic database entries in the database. For the same database entries that exist in both the file and in GSS database memory, the GSS does the following:
oOverwrites dynamic entries with any overlapping static entries.
oOverwrites static entries with any overlapping static entries, but does not overwrite those entries with any overlapping dynamic entries.
If you do not specify the override keyword, the GSS loads all the most recent entries into the memory, which will replace the older entries of the same type (dynamic or static) in the proximity database. For example, the most recent dynamic entries replace the older dynamic entries in the proximity database.
Command Modes
Privileged EXEC
Usage Guidelines
The proximity database load function supports the migration of proximity database entries from one GSS device into the proximity database of another GSS device. The GSS validates the loaded database entries, checks the software version for compatibility, and then replaces the proximity database in the memory. The file must be in a binary format to be loaded into the GSS memory.
Proximity RTT metrics loaded from the file replace overlapping entries that exist in the database and supplement the nonoverlapping database entries.
The following example shows how to load and merge the entries from the GSS3PDB file without overriding the existing entries in the GSS proximity database:
gss1.example.com# proximity database load GSS3PDB
Related Commands
To force an immediate backup of the proximity database residing in the GSS memory, use the proximity database periodic-backup command.
proximity database periodic-backup now
Syntax Description
Instructs the GSS device to immediately initiate the periodic proximity database backup.
Command Modes
Privileged EXEC
Usage Guidelines
You may manually initiate a proximity database dump as a database recovery method to ensure that you store the latest proximity database entries before you shut down the GSS.
The GSS sends the proximity database entries to the system dump file as the proximity database file. Upon a reboot or restart, the GSS reads this file and loads the contents to initialize the proximity database at boot time.
The following example shows how to force an immediate backup of the proximity database residing in the GSS memory:
gss1.example.com# proximity database periodic backup now
Related Commands
To dump the proximity group configuration summary to a specified text file, use the proximity group-summary dump command.
proximity gro}