Network Analysis Module Command Reference Guide, 4.2
NAM CLI Commands: esp-null-heuristic - show hosts
Downloads: This chapterpdf (PDF - 608.0KB) The complete bookPDF (PDF - 4.3MB) | Feedback

NAM CLI Commands: esp-null-heuristic - show hosts

Table Of Contents

NAM CLI Commands:
esp-null-heuristic - show hosts

protocol esp-null-heuristic

reboot

remote-storage nfs

remote-storage iscsi

rmon buffer

rmon channel

rmon filter

rmwebusers

router

router community

show access-log

show alarm event

show alarm mib

show alarm voice

show application group

show audit-trail

show autostart

show bios

show cdp settings

show certificate

show certificate-request

show clock details

show configuration

show custom-filter capture

show custom-filter decode

show date

show debug log-levels

show debug messages

show diffserv aggregate

show diffserv profile

show email

show entity

show ftp

show hosts


NAM CLI Commands:
esp-null-heuristic - show hosts


This chapter describes the following NAM CLI commands:

protocol esp-null-heuristic

reboot

remote-storage nfs

remote-storage iscsi

rmon buffer

rmon channel

rmon filter

rmwebusers

router

router community

show access-log

show alarm event

show alarm mib

show alarm voice

show application group

show audit-trail

show autostart

show bios

show cdp settings

show certificate

show certificate-request

show clock details

show configuration

show custom-filter capture

show custom-filter decode

show date

show debug log-levels

show debug messages

show diffserv aggregate

show diffserv profile

show email

show entity

show ftp

show hosts

protocol esp-null-heuristic

Use the protocol esp-null-heuristic command to enable and disable the NAM to parse ESP-NULL protocol heuristically.

To enable the NAM to parse ESP-NULL protocol heuristically, use the following command:

protocol esp-null-heuristic enable

To disable the NAM to parse ESP-NULL protocol heuristically, use the following command:

no protocol esp-null-heuristic enable

Syntax Description

This command enables and disables heuristic parsing of ESP-NULL packets.

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 enable parsing heuristically:

root@localhost# protocol esp-null-heuristic enable 

root@localhost# 

This example shows how to disable parsing heuristically:

root@localhost# no protocol esp-null-heuristic enable 

root@localhost# 

Related Commands

show protocol-feature

reboot

To shut down and then restart the 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# reboot
Reboot the NAM? (Y/N) [N]:
root@localhost# 

remote-storage nfs

To set an 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

name

Specifies the name for the NFS remote storage being removed.



Note This command is not supported on the NAM Virtual Blade.


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:

? or help—Displays help; see the help command.

cancel—Discards changes and exits from the subcommand mode.

exit—Saves changes and exits from the subcommand mode; see the exit command.

server WORDNFS server dns hostname or ip address.

dir WORDAn absolute directory with read write permission at the nfs server.

name WORDName of the nfs remote storage entry.

Examples

This example shows how to configure NFS remote storage for capturing data:

root@hostname.cisco.com# remote-storage nfs
Entering 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-storage

remote-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

name

Specifies the name for the NFS remote storage being removed.



Note This command is not supported on the NAM Virtual Blade.


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:

? or help—Displays help; see the help command.

cancel—Discards changes and exits from the subcommand mode.

exit—Saves changes and exits from the subcommand mode; see the exit command.

name WORDName of the iSCSI remote storage entry.

server WORDSCSI server dns hostname or ip address.

target WORDiSCSI target name provided by the iSCSI server admin.

format none partition-numberUntouch the remote iSCSI target partition table and make the NAM use "partition-number" for storing its capture data.

format one-linuxFormat the remote iSCSI target with one linux ext2 partition before using it to store NAM capture data.

Examples

This example shows how to configure a remote storage for caputuring iSCSI data:

root@hostname.cisco.com# remote-storage iscsi
Entering 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-storage

rmon buffer

To enter the RMON buffer configuration subcommand mode, and then configure RMON buffers, use the rmon buffer command. To remove RMON buffer configurations, use the no form of this command.

rmon buffer

no rmon buffer 1-65535


Note This command is not supported on the NAM Virtual Blade.


Syntax Description

1-65535

RMON buffer OID.


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 RMON buffer configuration subcommand mode, the following commands are available:

cancel—Discards changes and exits from the subcommand mode.

capture-slice bytes—(Optional) Sets the capture slice size. Default is 500 bytes.

channel-index 1-65535—Sets the channel index. Range is from 1 to 65535.

download-offset offset-number—(Optional) Sets the download offset. Default is 0.

download-slice bytes—(Optional) Sets the download slice size. Default is 500 bytes.

exit—Saves changes and exits from the subcommand mode; see the exit command.

full-action lock | wrap(Optional) Sets full action type to lock or wrap. Default is lock when full (lock).

Index(Optional) Sets the index.

owner string—(Optional) Specifies the collection owner. Default is monitor.


Note The collections that are configured in the CLI will not be visible in the GUI. For collections that use a GUI screen, you can make them visible in the GUI by using the owner string "LocalMgr."


size bytes—(Optional) Sets the buffer size.

Examples

This example shows how to configure RMON buffers:

root@localhost.cisco.com# rmon buffer
Entering 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-rmon-buffer)# channel-index 10
root@localhost.cisco.com(sub-rmon-buffer)# full-action lock
root@localhost.cisco.com(sub-rmon-buffer)# capture-slice 500
root@localhost.cisco.com(sub-rmon-buffer)# download-slice 500
root@localhost.cisco.com(sub-rmon-buffer)# download-offset 0
root@localhost.cisco.com(sub-rmon-buffer)# size 5120000
root@localhost.cisco.com(sub-rmon-buffer)# owner monitor
root@localhost.cisco.com(sub-rmon-buffer)# exit
Successfully created the RMON buffer control entry.
root@localhost.cisco.com# 

root@localhost.cisco.com# show rmon buffer 
Index:               50485
Channel index:       10
Full action:         Lock when full
Capture slice size:  500 bytes
Download slice size: 500 bytes
Download offset:     0
Max octets requested:5120000 bytes
Owner:               monitor

root@localhost.cisco.com# 

Related Commands

show rmon buffer

rmon channel

To enter the RMON channel subcommand mode, and then configure RMON channel collections, use the rmon channel command. To remove RMON channel configurations use the no form of this command.

rmon channel

no rmon channel 1-65535


Note This command is not supported on the NAM Virtual Blade.


Syntax Description

1-65535

RMON channel OID.


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 RMON channel configuration subcommand mode, the following commands are available:

accept-type failed | matched(Optional) Sets the accept type to either failed or matched. Default is matched.

cancel—Discards changes and exits from the subcommand mode.

data-control off | on(Optional) Turns the capture channel off or on. Default is on.

data-source data-source-string—Sets the channel data source.

description string—(Optional) Sets the channel description.

event-status always | ready(Optional) Sets the event status to either always or ready.

exit—Saves changes and exits from the subcommand mode; see the exit command.

index 1-65535—(Optional) Sets the channel index. Range is from 1 to 65535.

off-event 0-65535—(Optional) Sets the off event index. Default is 0.

on-event 0-65535—(Optional) Sets the on event index. Default is 0.

owner string—(Optional) Sets the owner string. Default is monitor.


Note The collections that are configured in the CLI will not be visible in the GUI. For collections that use a GUI screen, you can make them visible in the GUI by using the owner string "LocalMgr."


Examples

This example shows how to configure RMON channels:

root@localhost.cisco.com# rmon channel
Entering 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-rmon-channel)# ?
?                         - display help
accept-type               - set accept type
cancel                    - discard changes and exit from subcommand mode
data-control              - set capture channel mode
data-source               - set data source (*)
description               - set description
event-status              - set event status
exit                      - exit from subcommand mode
help                      - display help
index                     - set index
match-event               - set match-event index
off-event                 - set off-event index
on-event                  - set on-event index
owner                     - set owner string

(*) - denotes a mandatory field for this configuration.
root@localhost.cisco.com(sub-rmon-channel)# data-source vlan1
root@localhost.cisco.com(sub-rmon-channel)# accept-type matched
root@localhost.cisco.com(sub-rmon-channel)# data-control on
root@localhost.cisco.com(sub-rmon-channel)# description test
root@localhost.cisco.com(sub-rmon-channel)# event-status ready
root@localhost.cisco.com(sub-rmon-channel)# on-event 10
root@localhost.cisco.com(sub-rmon-channel)# off-event 10
root@localhost.cisco.com(sub-rmon-channel)# match-event 10
root@localhost.cisco.com(sub-rmon-channel)# owner monitor
root@localhost.cisco.com(sub-rmon-channel)# exit
Successfully created the RMON channel.
root@localhost.cisco.com# show rmon channels
Index:               24614
Data source:         vlan1 (5)
Accept type:         Matched (Inclusive)
Data control:        ON
Turn-On event index: 10
Turn-Off event index:10
Event index:         10
Event status:        Ready
Description:         test
Owner:               monitor

root@localhost.cisco.com#

Related Commands

show rmon channels

rmon filter

To enter the RMON filter subcommand mode, and then configure RMON filters, use the rmon filter command. To remove RMON filter configurations use the no form of this command.

rmon filter

no rmon filter 1-65535


Note This command is not supported on the NAM Virtual Blade.


Syntax Description

1-65535

RMON filter OID.


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 RMON filter configuration subcommand mode, the following commands are available:

cancel—Discards changes and exits from the subcommand mode.

channel-index 1-65535—Sets the channel index. Range is from 1 to 65535.

data hex-string—(Optional) Sets data.

data-mask hex-string—(Optional) Sets the data mask.

data-not-mask hex-string—(Optional) Sets the data-not-mask.

exit—Saves changes and exits from the subcommand mode; see the exit command.

index 1-65535—(Optional) Sets the filter index. Range is from 1 to 65535.

offset number—(Optional) Sets the offset. Default is 0.

owner string—(Optional) Sets the owner string. Default is monitor.


Note The collections that are configured in the CLI will not be visible in the GUI. For collections that use a GUI screen, you can make them visible in the GUI by using the owner string "LocalMgr."


pd-data-index number—(Optional) Sets the protocol directory data local index. Default is 0.

pd-index number—(Optional) Sets the protocol directory local index. Default is 0.

status number—(Optional) Sets the packet status. Default is 0.

status-mask number—(Optional) Sets the packet status mask. Default is 0.

status-not-mask number—(Optional) Sets the packet status not mask. Default is 0.

Examples

This example shows how to configure RMON filters:

root@localhost.cisco.com# rmon filter
Entering 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-rmon-filter)# ?
?                         - display help
cancel                    - discard changes and exit from subcommand mode
channel-index             - set channel index (*)
data-mask                 - set data mask
data-not-mask             - set data not mask
data                      - set data (*)
exit                      - exit from subcommand mode
help                      - display help
index                     - set filter index
offset                    - set offset
owner                     - set owner string
pd-data-index             - set protocol directory data local index
pd-index                  - set protocol directory local index
status-mask               - set packet status mask
status-not-mask           - set packet status not mask
status                    - set packet status

(*) - denotes a mandatory field for this configuration.
root@localhost.cisco.com(sub-rmon-filter)# channel-index 10
root@localhost.cisco.com(sub-rmon-filter)# data "ab bc cd 2f"
root@localhost.cisco.com(sub-rmon-filter)# offset 0
root@localhost.cisco.com(sub-rmon-filter)# owner monitor
root@localhost.cisco.com(sub-rmon-filter)# exit
Successfully created the RMON filter.
root@localhost.cisco.com# show rmon filters
Index:          11089
Channel index:  10
Data offset:    0
Data:           ab bc cd 2f
Data mask:
Data not mask:
Status:         0
Status mask:    0
Status not mask:0
PD index:       0
PD data index:  0
Owner:          monitor

root@localhost.cisco.com# 

Related Commands

show rmon buffer

rmwebusers

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# rmwebusers
 
WARNING:Doing this will stop the web server and remove
all locally defined web users from web user database.
 
Are you sure you want to continue (y/n) [n]? y
 
Disabling HTTP server...
Successfully disabled HTTP server.
 
All locally defined web users have been
removed from web user database.
root@localhost.cisco.com#

Related Commands

show web-users

router

To be supplied.

router


Note This command is not valid for NAM-1 or NAM-2 devices or the Cisco NAM 2200 Series appliances.


router community

To be supplied.

router


Note This command is not valid for NAM-1 or NAM-2 devices or the Cisco NAM 2200 Series appliances.


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-log
11 Mar 2003, 12:23:38   152.20.27.182   -       Access denied (no login session)
 /error.php
11 Mar 2003, 12:23:39   152.20.27.182   -       Access denied (no login session)
 /error.php
11 Mar 2003, 12:23:39   152.20.27.182   -       Access denied (no login session)
 /error.php
11 Mar 2003, 12:23:39   152.20.27.182   -       Access denied (no login session)
 /error.php

show alarm event

To display NAM event alarms, use the show alarm event command.

show alarm event [control-index]

Syntax Description

control-index

(Optional) Specifies the event control index.


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 NAM system event alarms:

root@nam# show alarm event 58874
Index:       58874
Description: Capture Stop
Type:        None
Community:
Owner:       LocalMgr

root@nam# no alarm event 58874
Successfully deleted the event.
root@nam#

Related Commands

alarm event
alarm mib

show alarm mib

To display NAM MIB alarms, use the show alarm event mib command.

show alarm mib [control-index]

Syntax Description

control-index

(Optional) Specifies the event control index.


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 NAM system event alarms:

root@nam# show alarm mib 4800
Index:               4800
Polling interval:    60 secs
Variable:            nlHostInPkts.1.0.1.4.172.20.98.129
Sample type:         Absolute
Startup:             Rising & falling
Rising threshold:    50 Pkts
Falling threshold:   40 Pkts
Rising event index:  3816
Falling event index: 3816
Owner:               LocalMgr

root@nam# no alarm mib 4800
Successfully deleted the alarm.
root@nam#


Related Commands

alarm event
alarm mib

show alarm voice

To display NAM voice alarms, use the show alarm voice command.

show alarm voice

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 NAM system event alarms:

root@nam# show alarm voice
SCCP:	
        Jitter alarm:          Disabled
        Packet lost alarm:     Disabled
        Jitter threshold:      30 msecs
        Packet lost threshold: 5%

H.323:
        Jitter alarm:          Disabled
        Packet lost alarm:     Disabled
        Jitter threshold:      150 msecs
        Packet lost threshold: 5%

MGCP:
        Jitter alarm:          Disabled
        Packet lost alarm:     Disabled
        Jitter threshold:      30 msecs
        Packet lost threshold: 5%
root@nam#

Related Commands

alarm event
alarm mib

show application group

To display application groups, use the show application group command.

show application group [group-name]

Syntax Description

group-name

(Optional) Specifies the application group name.


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 group
Application Group: File-Transfer
    Number of Protocols: 5
      - ftp
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.21.4.0.1.0.0
      - ftp-data
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.20.4.0.1.0.0
      - ftps
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.222.4.0.1.0.0
      - ftps-data
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.221.4.0.1.0.0
      - tftp
        16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.0.69.4.0.1.0.2

Application Group: Peer-to-Peer
    Number 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
      - hotline
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.21.124.4.0.1.0.0
      - soulseek
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.8.186.4.0.1.0.0
      - directconnect
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.155.4.0.1.0.0
      - bittorrent
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.26.225.4.0.1.0.0

Application Group: Web
    Number of Protocols: 2
      - http
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.80.4.0.1.0.0
      - https
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.1.187.4.0.1.0.0

Application Group: Database
    Number of Protocols: 9
      - sql*net
        16.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.0

Application Group: email
    Number of Protocols: 7
      - smtp
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.25.4.0.1.0.0
      - smtps
        16.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
      - pop3s
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.227.4.0.1.0.0
      - imap2
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.0.143.4.0.1.0.0
      - imaps
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.3.225.4.0.1.0.0

Application Group: Multi-Media
    Number of Protocols: 9
      - h225
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.6.184.4.0.1.0.0
      - h245
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.6.182.4.0.1.0.0
      - h323-gatekeeper
        16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.6.183.4.0.1.0.0
      - rtp
        16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.125.0.4.0.1.0.0
      - rtcp
        16.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
      - mgcp
        16.1.0.0.1.0.0.8.0.0.0.0.17.0.0.9.123.4.0.1.0.0
      - sccp
        16.1.0.0.1.0.0.8.0.0.0.0.6.0.0.7.208.4.0.1.0.0

Related Commands

application group

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-trail
Audit trail is enabled.
root@hostname.cisco.com# 

Related Commands

audit-trail enable

show autostart

To display autostart collections, use the show autostart command.

show autostart

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 autostart collections:

Root@localhost# show autostart
etherstats disable
addressmap disable
priostats disable
vlanstats disable
art disable

Related Commands

autostart

show bios

To display BIOS information, use the show bios command.

show bios

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 module's BIOS information:

Root@localhost# show bios
BIOS Information:
    Vendor: Phoenix Technologies Ltd.
    BIOS Version: 4.0-Rel 6.0.4
    BIOS Start Addr Seg: 0xe9d2
    BIOS Release Date: 05/28/2002
    BIOS ROM Size: 512K

System Info
    Manufacturer: Cisco Systems, Inc
    Product Name: Catalyst LineCard
    Version: 2 Processors
    Serial Number: 000000000
    UUID: 00000000000000000000000000000000

System Enclosure Info
    Manufacturer: Cisco Systems, Inc.
    Version:
    Serial Number: 000000000
    Asset Tag: No Asset Tag

show cdp settings

To display the current Cisco Discovery Protocol (CDP) settings, use the show cdp settings command.

show cdp settings


Note This command is not supported on NAM-1 or NAM-2 devices or the NAM Virtual Blade.


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 settings
CDP is disabled
    Message Interval:   60
    Message Hold Time:  180

root@nam#

Related Commands

cdp enable
cdp hold-time
cef data-source

show 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-----
MIIDgzCCAuygAwIBAgIBADANBgkqhkiG9w0BAQQFADCBjjELMAkGA1UEBhMCVVMx
CzAJBgNVBAgTAkNBMQswCQYDVQQHEwJTSjEbMBkGA1UEChMSQ2lzY28gU3lzdGVt
cywgSW5jMSswKQYDVQQLEyJDYXRhbHlzdCA2MDAwIE5BTSBUZXN0IENlcnRpZmlj
YXRlMRswGQYDVQQDExJDaXNjbyBTeXN0ZW1zLCBJbmMwHhcNMDExMTI3MTI0MDIw
WhcNMDYxMTI2MTI0MDIwWjCBjjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMQsw
CQYDVQQHEwJTSjEbMBkGA1UEChMSQ2lzY28gU3lzdGVtcywgSW5jMSswKQYDVQQL
EyJDYXRhbHlzdCA2MDAwIE5BTSBUZXN0IENlcnRpZmljYXRlMRswGQYDVQQDExJD
aXNjbyBTeXN0ZW1zLCBJbmMwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMfd
NQJunHkjduRGMc7B978Bgh4xlEixRCPQ9K74PNzmXbZlIayRUXvLHA3xCM8GamFt
SlLgjO5R3q0cHWnUrluknHeI1UfZMQMiL0IqL255JxX6NbvCUzGpTxNMKywDXDc3
VevqmPezWrHAFxx3hoXtgTnj6j6BMxyOkbYDwAFXAgMBAAGjge4wgeswHQYDVR0O
BBYEFPNCoN6ndQG9nCmgnzP+Y3VxOSP3MIG7BgNVHSMEgbMwgbCAFPNCoN6ndQG9
nCmgnzP+Y3VxOSP3oYGUpIGRMIGOMQswCQYDVQQGEwJVUzELMAkGA1UECBMCQ0Ex
CzAJBgNVBAcTAlNKMRswGQYDVQQKExJDaXNjbyBTeXN0ZW1zLCBJbmMxKzApBgNV
BAsTIkNhdGFseXN0IDYwMDAgTkFNIFRlc3QgQ2VydGlmaWNhdGUxGzAZBgNVBAMT
EkNpc2NvIFN5c3RlbXMsIEluY4IBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEB
BAUAA4GBAD95psLs1tneBsIuUWQvIdV6D7QYBfewtDzNW10lFvgDZBQdIu7QeRtL
tjMNyGDUIG7tz7/9iZyA90rfrkM410qJrJysoKBZgMzTg6ilpaIzPnoJnN4DYj5C
qNGuOM0OKqtpqCFMKq87UXUuvTgc3hhQKSY5LKOXhJyhtCupJ669
-----END CERTIFICATE-----

Related Commands

show certificate-request

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-request

Related Commands

show certificate

show clock details

To show clock details on the NAM, use the show clock details command.

show clock details


Note This command is only valid for Cisco NAM 2200 series appliances.


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

The following example shows how to display clock settings.

root@nam.cisco.com# show clock details
System Time:    Fri Oct 17 06:06:24 UTC 2008

show configuration

To display the NAM running configuration, use the show configuration command.

show configuration

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.

The following configurations are not included in the generated configuration file:

Reports

CLI users

Supervisor engine community strings

Examples

This example shows how to display the NAM running configuration:

Root@localhost# show configuration
!
! NAM running configuration
!
! Date: Thu Jan  9 09:23:31 2003
!
ip http tacacs+ disable
!
custom-filter capture
  filter-name "cli_origin_capture"
  description "came from the cli"
  protocol "6 1000001 800 2f 800 6 50 0 1 0 0 0 0"
  exit
!
custom-filter decode
  filter-name "cli_origin"
  protocol http
  exit
!
web-user
  user-name admin
  account-mgmt enable
  system-config enable
  capture enable
  alarm-config enable
  collection-config enable
  en-password "YWRtaW4K"
  exit
!
preferences
  entries-per-screen 25
  refresh-interval 15
  graph-bars 10
  resolve-hostname enable
  exit
!
syslog
  mib local enable
  mib remote disable
  voice local enable
  voice remote disable
  system debug enable
  system local enable
  system remote disable
  exit
!
alarm voice
  protocol H.323
  jitter-alarm disable
  pkt-loss-alarm disable
  jitter-threshold 150
  pkt-loss-threshold 5
  exit
!
alarm event
  index 7763
  description Capture Start
  cancel
!
alarm mib
  index 63547
  variable nlHostInPkts.9939.0.1.4.10.0.0.1
  interval 60
  sample-type absolute
  startup-alarm rising
  rising-threshold 10
  falling-threshold 20
  rising-event 63547
  falling-event 63547
  owner LocalMgr
  exit
!
rmon buffer
  index 47654
  channel-index 22838
  full-action lock
  capture-slice 1500
  download-slice 1500
  download-offset 0
  size 51200000
  owner LocalMgr
  exit
!
end

Related Commands

config clear

show custom-filter capture

To display the capture filters, use the show custom-filter capture command.

show custom-filter capture [filter-name]


Note This command is not supported on the NAM Virtual Blade.


Syntax Description

filter-name

(Optional) Sets the capture filter name.


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 display the capture filters:

Root@localhost# show custom-filter capture cli_origin_capture

Related Commands

custom-filter capture

show custom-filter decode

To display the decode filters, use the show custom-filter decode command.

show custom-filter decode [filter-name]


Note This command is not supported on the NAM Virtual Blade.


Syntax Description

filter-name

(Optional) Sets the decode filter name.


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 display the decode filters:

Root@localhost# show custom-filter decode cli_origin

Related Commands

custom-filter decode


show date

To display the current date and time, use the show date command.

show date

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 current date and time:

Root@localhost# show date
Thu Jan 09 09:38:01 2003

Related Commands

show time
time

show debug log-levels

To display log level settings, use the show debug log-levels command.

show debug log-levels

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default behavior or settings.

Command Modes

Command mode

Usage Guidelines

This command is supported on all NAM platforms.

Examples

The following example shows log level settings:

root@nam.cisco.com# show debug log-levels
Debug Logging: enabled
Feature OTHER (1): error (1)
Feature CDP (2): error (1)
Feature POLLD (3): error (1)
Feature SWPOLLD (4): error (1)
Feature TREND_DAEMON (5): error (1)
Feature TREND_RPC (6): error (1)
Feature TREND_SNMP (7): error (1)
Feature MAIN (8): error (1)
Feature MISC (9): error (1)
Feature SNMP (10): error (1)
Feature SRSNMP (11): error (1)
Feature ENTITY (12): error (1)
Feature RMON (13): error (1)
Feature RPC (14): error (1)
Feature DSRC (15): error (1)
Feature WAAS (16): error (1)
Feature PARSER (17): error (1)
Feature PPROC (18): error (1)
Feature FM (19): error (1)
Feature FR (20): error (1)
Feature COLL_SHARED (21): error (1)
Feature RTP (22): error (1)
Feature METRIC_ENGINE (23): error (1)
Feature ART (24): error (1)
Feature URL_COLLECTION (25): error (1)
Feature PORT_TABLE (26): error (1)
Feature MPLS_STATS (27): error (1)
Feature ETHERSTATS (28): error (1)
Feature CAPTURE (29): error (1)
Feature RMON1_HOST (30): error (1)
Feature RMON1_MATRIX (31): error (1)
Feature RMON2_ADDRMAP (32): error (1)
Feature RMON2_PDIST (33): error (1)
Feature RMON2_HOST (34): error (1)
Feature RMON2_MATRIX (35): error (1)
Feature DSMON_STATS (36): error (1)
Feature DSMON_PDIST (37): error (1)
Feature DSMON_HOST (38): error (1)
Feature DSMON_MATRIX (39): error (1)
Feature SMON_PRIO (40): error (1)
Feature SMON_VLAN (41): error (1)
 

show debug messages

To display NAM log file contents, use the show debug messages command.

show debug messages

Syntax Description

This command has no arguments or keywords.

Defaults

This command has no default behavior or settings.

Command Modes

Command mode

Usage Guidelines

This command is supported on all NAM platforms.

Examples

The following example shows the log file contents:

root@nam.cisco.com# show debug messages
2008-10-14 00:07:11 *** FM Metric Engine 1 created (iThread 3)
2008-10-14 00:07:11 MAIN: Flow reaper starting, LWP = 1381
2008-10-14 00:07:11 Packet data and flow processing layers started successfully.
2008-10-14 00:07:11 WAAS: Load autoconfig: enables:1 client:1 cltwan:0 svrwan:0                                                                                             
server:0 passthru:0
2008-10-14 00:07:11 *** WAAS Flow Agent (FA) manager module initialized ***
2008-10-14 00:07:11 Load SA Export config SA_EXPORT_ENABLED = 0
2008-10-14 00:07:11 *** Configure SuperAgent export: export disabled
2008-10-14 00:07:11 *** ART Metric Engine post initialization done. ***
2008-10-14 00:07:11 MAIN: dbgport_init: No cfg file!
2008-10-14 00:07:11 MAIN: Offtime LWP = 1382
2008-10-14 00:07:11 RPC: RPC LWP = 1383
2008-10-14 00:16:19 mond: exiting on signal 15.
2008-10-14 00:19:21 mond starting.
2008-10-14 00:19:21 MAIN: Timer LWP = 1570
2008-10-14 00:19:21 MAIN: Timekeeping LWP = 1571

show diffserv aggregate

To display all of the differentiated services aggregate configurations for all the data sources and profiles, use the show diffserv aggregate command.

show diffserv aggregate [control-index]

Syntax Description

control-index

(Optional) Aggregate 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 the differentiated service configurations:

Root@localhost# show diffserv aggregate
Control index:                 23723
Description:                   VoIP-TEst
Owner:                         LocalMgr
Status:                        1

Control index:                 31645
Description:                   VoIP
Owner:                         LocalMgr
Status:                        1

Control index:                 41657
Description:                   DragonBallZ
Owner:                         LocalMgr
Status:                        1

Control index:                 47739
Description:                   NoAggAllTech
Owner:                         LocalMgr
Status:                        1

show diffserv profile

To display all of the differentiated services profiles and their descriptions, use the show diffserv profile command.

show diffserv profile [profile-index]

Syntax Description

profile-index

(Optional) Profile 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 the profiles and their descriptions:

Root@localhost# show diffserv profile 31645
Aggregate Profile Index: 31645
DSCP Value     Description


show email

To display email settings that are used for e-mailing alarm messages or scheduled reports, use the email command.

show email

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 email values:

root@localhost# show email
Email
  Server: example-email.domain.com
  Mail Alarm: enabled
  Alarm Recipients: admin@domain.com another_admin@domain.com
root@localhost# 

Related Commands

email

show entity

To display the serial number and the values of the entity MIB entPhysicalAlias and entPhysicalAssetID, use the show entity command.

show entity

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 entity values:

root@localhost# show entity
Serial Number : SAD061506JU
Alias         :
Asset ID      :

Related Commands

entity alias
entity assetid

show ftp

To display the FTP server and directory for storing scheduled reports configuration, use the show ftp command.

show ftp

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 FTP server configuration:

root@localhost# show ftp
FTP settings:
  Server:     my.ftp-server.com
  Directory:  /my/directory
  User:       myUserName

Related Commands

ftp

show hosts

To display the hosts entries, use the show hosts command.

show hosts

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 hosts entries:

Root@localhost# show hosts
# $Id: hosts,v 1.4 2002/04/04 01:47:51 pwildi Exp $
#
127.0.0.1               localhost localhost.localdomain

127.0.0.11              slot1
127.0.0.21              slot2
127.0.0.31              slot3
127.0.0.41              slot4
127.0.0.51              slot5
127.0.0.61              slot6
127.0.0.71              slot7
127.0.0.81              slot8

111.10.9.18 switch1 lab