-
Network Analysis Module Command Reference Guide, 5.0
-
Preface
-
CLI
-
NAM CLI Commands: application - device waas
-
NAM CLI Commands: email - managed device community
-
NAM CLI Commands: metric export host - show certificate request
-
NAM CLI Commands: show clock details - show monitor urlfilter
-
NAM CLI Commands: show patches - web user
-
MPCLI
-
Acronyms
-
Matrix
-
Index
-
Feedback
Table Of Contents
NAM CLI Commands:
metric export host - show certificate requestmetric export non-waas traffic
monitor protocol encapsulation
NAM CLI Commands:
metric export host - show certificate request
This chapter describes the following NAM CLI commands:
•
metric export non-waas traffic
•
•
metric export host
To configure the metric export host, use the metric export host command. To disable metric export, use the no form of this command.
metric export host ip-address [port]
no metric export
Syntax Description
ip-address
Specifies the IPv4 address of the external reporting console.
port
Port the external reporting console is listening on for incoming packets (optional).
Defaults
The default port is 9995.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Use this command to export ART metrics to an external reporting console.
Examples
The following example specifies the reporting console's IP address as the source to collect ART metrics, then removes this configuration.
root@nam.cisco.com# metric export 10.0.0.1 9995root@nam.cisco.com# no metric exportmetric export non-waas traffic
To send SPAN traffic (non-WAAS traffic) to an external reporting console, use the metric export non-waas traffic command. To disable metric export, use the no form of this command.
metric export non-waas traffic
no metric export non-waas traffic
Syntax Description
This command has no arguments or keywords.
Defaults
Export is disabled.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Use this command to export non-waas (SPAN traffic) metrics to an external reporting console.
Examples
The following example shows how to send non-WAAS traffic to an external reporting console, then removes this configuration:
root@nam.cisco.com# metric export non-waas trafficroot@nam.cisco.com# no metric export non-waas trafficmonitor protocol encapsulation
To set the protocol encapsulation, use the monitor protocol encapsulation command. To disable the protocol encapsulation, use the no form of this command.
monitor protocol encapsulation
no monitor protocol encapsulation
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to set the monitor protocol encapsulation.
root@nam.cisco.com# monitor protocol encapsulationgre-ip - encapsulation typegtp - encapsulation typeip-esp - encapsulation typeip-ipv4 - encapsulation typeip-ipv6 - encapsulation typeroot@nam.cisco.com# monitor protocol encapsulationRelated Commands
show monitor protocol encapsulationmonitor rtp-stream enable
To enable RTP stream monitoring, use the monitor rtp-stream enable command. To disable RTP stream monitoring, use the no form of this command.
monitor rtp-stream enable
no monitor rtp-stream enable
Note
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
Examples
This example shows how to enable RTP stream monitoring.
root@localhost# monitor rtp-stream enableThis example shows how to disable RTP stream monitoring.
root@localhost# no monitor rtp-stream enableRelated Commands
monitor rtp-stream filter
To set a RTP stream filtering entry, use the monitor rtp-stream filter command. To remove a RTP stream filtering entry, use the no form of this command.
monitor rtp-stream filter source-address source-mask dest-address dest-mask
Syntax Description
Note
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
Examples
This example shows how to enable RTP stream filtering:
root@localhost# monitor rtp-stream filter 1.2.3.0 255.255.255.0 4.5.0.0 255.255.0.0Related Commands
monitor rtp-stream threshold
To set the alarm threshold for the different RTP stream monitoring types, use the monitor rtp-stream threshold command. To disable the alarm threshold RTP stream monitoring, use the no form of this command.
monitor rtp-stream threshold <key_word>
no monitor rtp-stream threshold <key_word>
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to set an alarm threshold of 6% for RTP stream monitoring of lost packets.
root@NAM.cisco.com# monitor rtp-stream threshold adjusted-pkt-loss 6Successfully set adjusted-pkt-loss alarm.root@NAM.cisco.com#monitor urlcollection
To enter the URL collection submode and configure URL collections, use the monitor urlcollection command. To disable the URL collection, use the no form of this command.
monitor urlcollection
no monitor urlcollection
Note
Syntax Description
This command has no keywords or arguments.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
When you enter the URL collections submode, the following commands are available:
•
•
•
•
•
–
–
–
–
•
•
•
There is only one URL collection in NAM. The collection owner is always LocalMgr. The index is always one.
Examples
This example shows how to configure URL collection:
root@localhost# monitor urlcollectionEntering into subcommand mode for this command.Type 'exit' to apply changes and come out of this mode.Type 'cancel' to discard changes and come out of this mode.root@localhost(sub-monitor-url-collection)# ?? - display helpcancel - discard changes and exit from subcommand modedata-source - specify the collection data source (*)exit - exit from the subcommand modehelp - display helpignore - set url collection data matching schemesmatch-only - match string for url collection datamax-entry - set max number data entries of url collectionrecycle - enable or disable aging of url collection data entries(*) - denotes a mandatory field for this configuration.root@localhost(sub-monitor-url-collection)#Related Commands
cdp interval
show monitor urlcollectionmonitor urlfilter
To enter the URL filter collection configuration subcommand mode, and then configure URL filters, use the monitor urlfilter command. To remove the URL filters from the configuration, use the no form of this command.
monitor urlfilter
no monitor urlfilter control-index
Note
Syntax Description
Defaults
The control index is random.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
When you enter the monitor URL filter subcommand mode, the following commands are available:
•
•
•
•
•
•
•
•
•
The clear configuration command removes the URL filters from the configuration. There is no SNMP support for configuring the URL filters.
Examples
This example shows how to configure URL filters:
root@nam# monitor urlfilterEntering into subcommand mode for this command.Type 'exit' to come out of this mode.Type 'cancel' to discard changes and to come out of this mode.root@nam(sub-monitor-url-filter)# control-index 2root@nam(sub-monitor-url-filter)# description urlfilter exampleroot@nam(sub-monitor-url-filter)# host-regexp www.example.comroot@nam(sub-monitor-url-filter)# protocol-encap ipv4root@nam(sub-monitor-url-filter)# exitSucessfully created urlfilter entry.root@nam# show monitor urlfilterDescription: urlfilter exampleControl index: 2Protocol encapsulation: IPv4URL's host string: www.example.comURL's path string: (not-set)To remove this URL filter entry, use the no form of the command:
root@nam# no monitor urlfilter 2Successfully delete urlfilter entry.Related Commands
cdp interval
show monitor urlfilternetflow input port
To set a specified value of the input NetFlow UDP port on NAM, use the netflow input port [port] command.
netflow input port [port]
Note
Syntax Description
Defaults
The default port is 3000.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to use the netflow input port command.
root@localhost# netflow input port 9101NetFlow input port 3000 changed to 9101nslookup
To configure name server queries, use the nslookup command.
nslookup hostname [server]
Syntax Description
hostname
Specifies the name server query host.
server
(Optional) Specifies the name server to query.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to configure name server queries:
root@localhost.cisco.com# nslookup www.yahoo.comServer: 127.0.0.1Address: 127.0.0.1#53Non-authoritative answer:www.yahoo.com canonical name = www.yahoo.akadns.net.Name: www.yahoo.akadns.netAddress:66.218.71.80root@localhost.cisco.com#password
To set a new password, use the password command.
password username
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
There are only two valid users, root and guest.
Examples
This example shows how to set a password:
root@localhost.cisco.com# password rootChanging password for user rootNew UNIX password:Retype new UNIX password:passwd:all authentication tokens updated successfullyroot@localhost.cisco.com#patch
To download and install a software patch, use the patch command.
patch ftp://user:passwd@host/full-path/filename
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to download and install a patch:
root@localhost.cisco.com# patch ftp://hostname/fullpath/c6nam-3.6-strong-cryptoK9-patch-1-0.binProceeding with installation. Please do not interrupt.If installation is interrupted, please try again.Downloading c6nam-3.6-strong-cryptoK9-patch-1-0.bin. Please wait...ftp://hostname/fullpath/c6nam-3.6-strong-cryptoK9-patch-1-0.bin (1K)- [########################] 1K | 1886.33K/s1891 bytes transferred in 0.00 sec (1569.00k/sec)Verifying c6nam-3.6-strong-cryptoK9-patch-1-0.bin. Please wait...Patch c6nam-3.6-strong-cryptoK9-patch-1-0.bin verified.Applying /usr/local/nam/patch/workdir/c6nam-3.6-strong-cryptoK9-patch-1-0.bin. Please wait...########################################### [100%]########################################### [100%]Patch applied successfully.root@localhost.cisco.com#Related Commands
pid-sn
To enter the Product ID and Serial number of a WAE device for node locking with a NAM Virtual Blade product license, use the pid-sn command.
pid-sn PIDnnnn SNnnnn
Syntax Description
PIDnnnn
Specifies the Product ID of the WAE device.
SNnnnn
Specifies the serial number of the WAE device.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is valid only on NAM Virtual Blade platforms.
Examples
This example shows how to ener the Product ID and serial number of a WAE device:
root@localhost# pid-sn WAE-674-K9 KXQCDHDRroot@localhost#ping
To check connectivity to a network device, use the ping command.
ping [-n | -v] [-c count] [-i wait] [-p pattern] [-s packetsize] hostname | IP address
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to check the connectivity of a network device with ping:
root@localhost# ping -n -v ralph 100.20.19.23root@localhost#preferences
To enter the preferences subcommand mode, and then configure how your screen displays information, use the preferences command.
preferences
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
When you enter the preferences subcommand mode, the following commands are available:
•
•
•
•
•
•
•
•
•
•
•
Examples
This example shows how to configure preferences for your screen display:
root@localhost.cisco.com# preferencesEntering into subcommand mode for this command.Type 'exit' to come out of this mode.Type 'cancel' to discard changes and to come out of this mode.root@localhost.cisco.com(sub-preferences)# entries-per-screen 15root@localhost.cisco.com(sub-preferences)# refresh-interval 60root@localhost.cisco.com(sub-preferences)# graph-bars 10root@localhost.cisco.com(sub-preferences)# hostname-resolution disableroot@localhost.cisco.com(sub-preferences)# data-displayed bytesroot@localhost.cisco.com(sub-preferences)# format-large-number enableroot@localhost.cisco.com(sub-preferences)# number-notation comma-dotroot@localhost.cisco.com(sub-preferences)# exitNAM web interface preferences updated successfully.dataThis example shows how to display the configured preferences:
root@localhost.cisco.com# show preferencesEntries per screen: 15Refresh interval: 60 secsNumber of graph bars: 10Hostname resolution: DisabledData displayed in: BytesFormat large number: NoNumber notation: Commas-dotroot@localhost.cisco.com#Related Commands
reboot
To shut down and then restart NAM, use the reboot command.
reboot
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to reboot the NAM:
root@localhost# rebootReboot the NAM? (Y/N) [N]:root@localhost#remote-storage nfs
To set a NFS remote storage for capturing data and enter the configuration command mode, use the remote-storage nfs command. To remove a NFS remote storage for captured data, use the no remote-storage name command.
remote-storage nfs
no remote-storage name
Syntax Description
Note
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
Usage Guidelines
When you enter the web user subcommand mode, the following commands are available:
•
•
•
•
•
•
Examples
This example shows how to configure NFS remote storage for capturing data:
root@hostname.cisco.com# remote-storage nfsEntering into subcommand mode for this command.Type 'exit' to come out of this mode.Type 'cancel' to discard changes and to come out of this mode.root@hostname.cisco.com(sub-remote-storage_nfs)# ?root@hostname.cisco.com#Related Commands
remote-storage iscsi
show remote-storageremote-storage iscsi
To set an iSCSI remote storage for capture data and enter the configuration command mode, use the remote-storage iscsi command. To remove an iSCSI remote storage entry for capture data, use the no remote-storage name command.
remote-storage iscsi
no remote-storage name
Syntax Description
Note
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NAM-1, NAM-2, NME-NAM-80S, and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
When you enter the web user subcommand mode, the following commands are available:
•
•
•
•
•
•
•
•
Examples
This example shows how to configure a remote storage for caputuring iSCSI data:
root@hostname.cisco.com# remote-storage iscsiEntering into subcommand mode for this command.Type 'exit' to come out of this mode.Type 'cancel' to discard changes and to come out of this mode.root@hostname.cisco.com(sub-remote-storage_iscsi)# ?root@hostname.cisco.com#Related Commands
remote-storage nfs
show remote-storagermwebusers
To remove all web users from the local web user database, use the rmwebusers command.
rmwebusers
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to remove web users from the local web user database:
root@localhost.cisco.com# rmwebusersWARNING:Doing this will stop the web server and removeall locally defined web users from web user database.Are you sure you want to continue (y/n) [n]? yDisabling HTTP server...Successfully disabled HTTP server.All locally defined web users have beenremoved from web user database.root@localhost.cisco.com#Related Commands
show access-log
To display the web access log, use the show access-log command.
show access-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display the web access log:
Root@localhost# show access-log11 Mar 2003, 12:23:38 152.20.27.182 - Access denied (no login session)/error.php11 Mar 2003, 12:23:39 152.20.27.182 - Access denied (no login session)/error.php11 Mar 2003, 12:23:39 152.20.27.182 - Access denied (no login session)/error.php11 Mar 2003, 12:23:39 152.20.27.182 - Access denied (no login session)/error.php
show application app-id
To display all applications, use the show application app-id command.
show application app-id
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display all applications:
root@NAM.cisco.com# show application app-idsample-l3:1 (16777217) icmpsample-l3:2 (16777218) igmpsample-l3:4 (16777220) ipsample-l3:6 (16777222) tcpsample-l3:8 (16777224) egpRelated Commands
show application eng-id
To display application information per engine ID, use the show application eng-id command.
show application eng-id
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display application information per engine ID:
root@NAM.cisco.com# show application eng-id 1sample-l3:1 (16777217) icmpsample-l3:2 (16777218) igmpsample-l3:4 (16777220) ipsample-l3:6 (16777222) tcpsample-l3:8 (16777224) egpRelated Commands
show application group
To display application groups, use the show application group command.
show application group [group-name]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display application groups:
root@namlab-kom10.cisco.com# show application groupApplication Group: File-TransferNumber of Protocols: 5- ftp16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.21.4.0.1.0.0- ftp-data16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.20.4.0.1.0.0- ftps16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.222.4.0.1.0.0- ftps-data16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.221.4.0.1.0.0- tftp16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.69.4.0.1.0.2Application Group: Peer-to-PeerNumber of Protocols: 12- gnutella(6346)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.24.202.4.0.1.0.0- gnutella(6347)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.24.203.4.0.1.0.0- fasttrack(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.4.190.4.0.1.0.0- fasttrack(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.4.190.4.0.1.0.0- winmx(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.24.113.4.0.1.0.- winmx(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.26.43.4.0.1.0.0- edonkey(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.18.57.4.0.1.0.0- edonkey(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.18.53.4.0.1.0.0- hotline16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.21.124.4.0.1.0.0- soulseek16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.8.186.4.0.1.0.0- directconnect16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.155.4.0.1.0.0- bittorrent16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.26.225.4.0.1.0.0Application Group: WebNumber of Protocols: 2- http16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.80.4.0.1.0.0- https16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.187.4.0.1.0.0Application Group: DatabaseNumber of Protocols: 9- sql*net16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.66.4.0.1.0.0- sqlserv(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.118.4.0.1.0.0- sqlserv(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.118.4.0.1.0.0- ms-sql-mon(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.5.154.4.0.1.0.0- ms-sql-mon(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.5.154.4.0.1.0.0- ms-sql-ser(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.5.153.4.0.1.0.0- ms-sql-ser(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.5.153.4.0.1.0.0- oracle-server(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.5.245.4.0.1.0.0- oracle-server(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.5.245.4.0.1.0.0Application Group: emailNumber of Protocols: 7- smtp16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.25.4.0.1.0.0- smtps16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.209.4.0.1.0.0- pop3(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.110.4.0.1.0.0- pop3(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.110.4.0.1.0.0- pop3s16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.227.4.0.1.0.0- imap216.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.143.4.0.1.0.0- imaps16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.225.4.0.1.0.0Application Group: Multi-MediaNumber of Protocols: 9- h22516.1.0.0.1.0.0.8.0.0.0.0.6.0.0.6.184.4.0.1.0.0- h24516.1.0.0.1.0.0.8.0.0.0.0.6.0.0.6.182.4.0.1.0.0- h323-gatekeeper16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.6.183.4.0.1.0.0- rtp16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.125.0.4.0.1.0.0- rtcp16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.125.1.4.0.1.0.0- sip(udp)16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.19.196.4.0.1.0.- sip(tcp)16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.19.196.4.0.1.0.0- mgcp16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.9.123.4.0.1.0.0- sccp16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.7.208.4.0.1.0.0Related Commands
show audit-trail
To display the audit trail configuration, use the show audit-trail command.
show audit-trail
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display the audit trail configuration:
root@hostname.cisco.com# show audit-trailAudit trail is enabled.root@hostname.cisco.com#Related Commands
show autocreate-data-source
To display the autocreated data-sources, use the show autocreate-data-source command.
show autocreate-data-source
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows if the autocreation of data-sources feature is enabled:
root@NAM.cisco.com# show autocreate-data-sourceNDE autocreation : ENABLEDWAAS autocreation : ENABLEDERSPAN autocreation : ENABLEDAutocreate WAAS Client data source : ENABLEDAutocreate WAAS Client WAN data source : DISABLEDAutocreate WAAS Server WAN data source : DISABLEDAutocreate WAAS Server data source : DISABLEDAutocreate WAAS Passthru data source : DISABLEDEnable Passthru export on autocreated WAAS device : NOroot@NAM.cisco.com#show cdb
To display information about a CDB file, use the show cdb command.
show cdb [filename]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all platforms.
show cdp settings
To display the current Cisco Discovery Protocol (CDP) settings, use the show cdp settings command.
show cdp settings
Note
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported only on NME-NAM-80S and NME-NAM-120S devices and Cisco NAM 2200 Series appliances.
Examples
To display the current CDP settings:
root@nam# show cdp settingsCDP is disabledMessage Interval: 60Message Hold Time: 180root@nam#Related Commands
autocreate data-source
cdp hold-time
cdp intervalshow certificate
To display the installed certificate, use the show certificate command.
show certificate
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display certificate information:
Root@localhost# show certificate-----BEGIN CERTIFICATE-----MIIDgzCCAuygAwIBAgIBADANBgkqhkiG9w0BAQQFADCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMQswCQYDVQQHEwJTSjEbMBkGA1UEChMSQ2lzY28gU3lzdGVtcywgSW5jMSswKQYDVQQLEyJDYXRhbHlzdCA2MDAwIE5BTSBUZXN0IENlcnRpZmljYXRlMRswGQYDVQQDExJDaXNjbyBTeXN0ZW1zLCBJbmMwHhcNMDExMTI3MTI0MDIwWhcNMDYxMTI2MTI0MDIwWjCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMQswCQYDVQQHEwJTSjEbMBkGA1UEChMSQ2lzY28gU3lzdGVtcywgSW5jMSswKQYDVQQLEyJDYXRhbHlzdCA2MDAwIE5BTSBUZXN0IENlcnRpZmljYXRlMRswGQYDVQQDExJDaXNjbyBTeXN0ZW1zLCBJbmMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMfdNQJunHkjduRGMc7B978Bgh4xlEixRCPQ9K74PNzmXbZlIayRUXvLHA3xCM8GamFtSlLgjO5R3q0cHWnUrluknHeI1UfZMQMiL0IqL255JxX6NbvCUzGpTxNMKywDXDc3VevqmPezWrHAFxx3hoXtgTnj6j6BMxyOkbYDwAFXAgMBAAGjge4wgeswHQYDVR0OBBYEFPNCoN6ndQG9nCmgnzP+Y3VxOSP3MIG7BgNVHSMEgbMwgbCAFPNCoN6ndQG9nCmgnzP+Y3VxOSP3oYGUpIGRMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0ExCzAJBgNVBAcTAlNKMRswGQYDVQQKExJDaXNjbyBTeXN0ZW1zLCBJbmMxKzApBgNVBAsTIkNhdGFseXN0IDYwMDAgTkFNIFRlc3QgQ2VydGlmaWNhdGUxGzAZBgNVBAMTEkNpc2NvIFN5c3RlbXMsIEluY4IBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBAUAA4GBAD95psLs1tneBsIuUWQvIdV6D7QYBfewtDzNW10lFvgDZBQdIu7QeRtLtjMNyGDUIG7tz7/9iZyA90rfrkM410qJrJysoKBZgMzTg6ilpaIzPnoJnN4DYj5CqNGuOM0OKqtpqCFMKq87UXUuvTgc3hhQKSY5LKOXhJyhtCupJ669-----END CERTIFICATE-----Related Commands
show certificate-request
To display the certificate-signing requests, use the show certificate-request command.
show certificate-request
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Command mode
Usage Guidelines
This command is supported on all NAM platforms.
Examples
This example shows how to display the certificate-signing requests:
Root@localhost# show certificate-requestRelated Commands
