This chapter contains all the CLI commands available on the SCE platform. Each command description is broken down into the following sub-sections:

Transcription

1 CHAPTER 2 This chapter contains all the CLI commands available on the SCE platform. Each command description is broken down into the following sub-sections: Command syntax Description Default Authorization Mode Parameters Usage guidelines The general format of the command. Description of what the command does. If relevant, the default setting for the command. The level of user authorization required for using the command. The mode (command line) from which the command can be invoked. Description of parameters and switches for the command. Information about when to invoke the command and additional details Syntax and Conventions The CLI commands are written in the following format: command required-parameter [optional-parameter] [no] is an optional parameter that may appear before the command name. When typing commands, you may enclose parameters in double-quote marks, and you must do so when there is a space within a parameter name. 2-1

2 debug aaa Chapter 2 debug aaa Displays debug information regarding Authentication, Authorization and Accounting functions. debug aaa show accounting methods debug aaa show counters debug aaa show enable methods debug aaa show login This command has no arguments or keywords. Displays the following debug information regarding Authentication, Authorization and Accounting functions: accounting methods list aaa counters enable methods list login methods list 2-2

3 Chapter 2 debug app debug app Extracts the xml section from the application file (SLI) to a specified file. debug app application-filename extract-to-file out-filename debug app-loader directory-name application-filename out-filename Name of the application file Name of the output xml file 2-3

4 debug app-loader Chapter 2 debug app-loader Recursively loads all the files in the specified directory. This can be useful in order to verify the load of certain applications in an automated manner on the SCE itself. debug boot-params-to-defaults directory-name The name of the directory from which to load the application files 2-4

5 Chapter 2 debug boot-params-to-defaults debug boot-params-to-defaults Resets the boot parameters to their default values. debug boot-params-to-defaults This command has no arguments or keywords. Changes the boot parameters to their default values, performing the following operations: Loads the default image from the SCE disk Verifies that the system is not in recovery mode Enables the management port This command can be useful in many cases, such as: Taking the system out of recovery mode Verifying that a non-standard configuration exists for running a regression 2-5

6 debug cli Chapter 2 debug cli Manipulates dynamic CLI commands. debug cli add level level# tableid tableid# numtokens num-of-tokens token1 [token2 [token3... [token6]]] debug cli remove handle handle# debug cli text sessionid session# (more no-more) outtext text-string level# Authorization level ID (0, 5, 10, or 15) tableid# ID number of the specified table num-of-tokens Number of tokens (maximum of 6) token1, token2, Up to six tokens token3,... token6 handle# Command handle number session# Session ID number text-string Text to be supplied to command This command can be used to perform the following actions on dynamic CLI commands: Add a dynamic CLI command Remove a dynamic CLI command Supply text for an invoked dynamic CLI command Note the following: add : text : : Make sure that the value specified for numtokens matches the actual number of tokens that are defined in the command. A maximum of six tokens can be defined in a single command. Use the more keyword to instruct the system to wait for more text. Use the no-more keyword to instruct the system not to wait for more text. 2-6

7 Chapter 2 debug cpa-client debug cpa-client Provides debug information related to the SurfControl URL filtering feature. debug cpa-client check-setup debug cpa-client get-category host-name host-name The name of the URL in the CPA server There are two options: check-setup Checks various SCE configuration parameters (for example, that URL filtering RDRs are sent to the mgmt-agent) to make sure that the system is properly configured for URL filtering. get-category Looks up the category ID of a URL in the CPA server. This is useful when troubleshooting connectivity problems between the SCE and the CPA server. 2-7

8 debug db Chapter 2 debug db The db is a database that holds a large number of configuration variables that affect the SCE operation. debug db get variable-name index-number debug db set variable-name index-number new-value debug db how-many debug db name-by-index variable-index debug db show variable-name debug db show-all variable-name index-number new-value variable-index Name of the variable Specifies which member of the variable array to set or get Value to which to set the specified member of the variable ID number of the variable The following debug commands allow you to view the values of variables in the db and in certain cases to change them. get Displays the value of a specified DB variable set Sets the value of a specified DB variable how-many Displays the total number of currently defined DB variables name-by-index Displays the name of a DB variable specified by ID number show Displays information about a DB variable specified by name show-all Displays all existing DB variables 2-8

9 Chapter 2 debug dbg interpret debug dbg interpret The debug log in the SCE is maintained in binary format and should be interpreted on demand. There are a number of flavors for the interpretation process as described below. debug dbg interpret [input-file in-filename last-failure] output-file out-filename [no-dumps] debug dbg interpret [input-file in-filename last-failure] output-file out-filename fatality-level error-level debug dbg interpret [input-file in-filename last-failure] output-file out-filename fatality-level error-level cpu-list (all cpu1#,cpu2#, ) message-list message1#,message2#,message3# debug dbg interpret [input-file in-filename last-failure] output-file out-filename fatality-level error-level cpu-list (all cpu1#,cpu2#, ) module-list module1#,module2#,module3# debug dbg interpret [input-file in-filename last-failure] output-file out-filename fatality-level error-level cpu-list (all cpu1#,cpu2#, ) no-dumps debug dbg interpret [input-file in-filename last-failure] output-file out-filename fatality-level error-level segment start-string start-marker end-string end-marker debug dbg interpret non-volatile-hitogram in-filename Name of the input debug file out-filename Name of the output text file error-level Fatality level for interpretation (Error, Fatal, Info, or Warning) cpu1#,cpu2#, List of cpu numbers separated by commas (e.g. 0,2,3 ) message1#,message2#, message3# module1#,module2#,m odule3# start-marker end-marker List of module names and message number separated by commas (e.g. logger::5,formatter::7,rdb_gen::11) List of module names separated by commas (e.g. logger,formatter,rdb_gen) The segment Start-Marker (exact message string) The segment End-Marker (exact message string) Available modifiers: output-file The name of the output file after interpretation (it is recommended to use the.txt suffix) input-file The name of an external binary file to be interpreted on the SCE platform instead of the original dbglog that resides on the SCE 2-9

10 debug dbg interpret Chapter 2 last-failure Interprets the dbglog, which is a file copied by the SCE each time there is a failure non-volatile-hitogram Shows the histogram of all message types that were written to the log since the last time the counters were reset (not since the system was reset) 2-10

11 Chapter 2 debug dbg module debug dbg module Allows the user to control the tracing level of the various debug modules that are capable of writing debug messages to the log. debug dbg module module-id fatality-level error-level debug dbg module module-id message message# rate-control (on off) debug dbg module module-id message message# set-period num-of-messages debug dbg module module-id message message# set-status (on off) debug dbg module module-id message message# show-fatality debug dbg module module-id message message# show-period debug dbg module module-id message message# show-string debug dbg module module-id show-messages error-level module-id message# Fatality level for interpretation (Error, Fatal, Info, Warning) Module ID, in a format starting with '0x' Number of the message Use this command to set the following options for the specified module: fatality-level Set fatality level of the module message Manage debug messages rate-control Change rate control mode for this message set-period Set the message period set-status Set the message status to all processors show-fatality Show the message fatality show-period Show the message period show-string Show the message string show-messages Show the module messages information 2-11

12 debug dbg output-format Chapter 2 debug dbg output-format Allow the user to determine whether some of the fields that are generated during log interpretation should be suppressed. debug dbg output-format date (off on) time (off on) cpu (off on) sequence (off on) This command has no arguments or keywords. The following options are available: date time cpu sequence 2-12

13 Chapter 2 debug dbg ruc-debugging debug dbg ruc-debugging Enables RuC logging. debug dbg ruc-debugging (enable disable show) This command has no arguments or keywords. Since there is an additional performance cost for dbg messages in the data plane (the Traffic Processor or the RuC), you must enable RuC logging in order to debug the RuC. Therefore, in order to optimize performance, there is a global enabler for all RuC logging. The following options are available: disable Disable RUC Info messages (including vertical debugging) enable Enable RUC Info messages (including vertical debugging) show Display the status of RUC Info messages 2-13

14 debug dbg show-modules Chapter 2 debug dbg show-modules Displays all the supported dbg modules in order to determine the exact syntax of the modules before using the debug dbg module command. debug dbg show-modules This command has no arguments or keywords. 2-14

15 Chapter 2 debug dbg slot debug dbg slot Allows the dbg commands to be localized to a certain slot or traffic processor. The functionality of the modifiers is similar to the other debug dbg commands. debug dbg slot slot# module module-name fatality-level error-level debug dbg slot slot# module module-name message message# rate-control (on off) debug dbg slot slot# module module-name message message# set-period num-of-messages debug dbg slot slot# module module-name message message# set-status (on off) debug dbg slot slot# ppc ppc# module module-name fatality-level error-level debug dbg slot slot# ppc ppc# module module-name message message# rate-control (on off) debug dbg slot slot# ppc ppc# module module-name message message# set-period num-of-messages debug dbg slot slot# ppc ppc# module module-name message message# set-status (on off) debug dbg slot slot# ppc ppc# module module-name message message# show-rate-control debug dbg slot slot# ppc ppc# module module-name message message# show-status debug dbg slot slot# ppc ppc# ruc-debugging (enable disable show) error-level Fatality level for interpretation (Error, Fatal, Info, Warning) module-name Module name message# Number of the message num-of-messages Number of messages after which a message will be issued slot# The number of the identified slot. Enter a value of 0. ppc# The number of the PPC on the specified slot The following options are available: module fatality-level Set fatality level of the module message Manage debug messages rate-control Change rate control mode for this message set-period Set the message period 2-15

16 debug dbg slot Chapter 2 set-status Set the message status to all processors ppc module fatality-level Set fatality level of the module message Manage debug messages rate-control Change rate control mode for this message set-period Set the message period set-status Set the message status to all processors show-rate-control Show the rate control mode for this message show-status Show the message status for all processors ruc-debugging disable Disable RUC Info messages (including vertical debugging) enable Enable RUC Info messages (including vertical debugging) show Display the status of RUC Info messages 2-16

17 Chapter 2 debug engage debug engage Debugs the SCA BB application. debug engage run-after-apply-handler This command has no arguments or keywords. Note This command is relevant only when the SCA BB application is installed on the SCE platform. 2-17

18 debug ffs Chapter 2 debug ffs Debugs the flash file system. Shows the number of available file descriptors. debug ffs show used-fds This command has no arguments or keywords. 2-18

19 Chapter 2 debug flow-capture debug flow-capture Executes flow capture operations. debug flow-capture { start stop create-cap file-destination } file-destination Destination where the cap file should be created (may also be an FTP site path). If no absolute path is given, the file is saved in the root directory. The flow capture is a useful debugging capability that captures packets from the traffic stream in real time and stores them for later analysis using a standard cap format. The classification of the traffic portion to be captured is based on L4 attributes. The following operations are available: start Start recording stop Stop recording create-cap Creates a cap file in the given destination Note that traffic can be captured only when an application is loaded. To perform a flow capture, complete the following steps: 1. (Optional) Configure limits to the flow capture operation using the flow-capture controllers command, to prevent a negative impact on traffic processing. You may skip this step and use the default controller values. 2. Configure an appropriate recording rule using the traffic-rule command. Assign the flow-capture action to the rule (see traffic-rule (ROOT level options)). Note the following limitations: You must use the traffic-rule command to define the recording rule. Only one recording traffic rule can be defined in the system at a time. You cannot use the flow-filter command. 3. Start the actual capture. The capture will not start unless a valid recording rule has been defined. Use the debug flow-capture start command. 4. Stop the capture. Use the debug flow-capture stop command. 5. Create the cap file. The captured data is saved as a CAP file in Snoop v4 format. The cap file will not be created until both a start and stop command have been executed. Use the debug flow-capture create-cap command. 2-19

20 debug flow-capture Chapter 2 At any point, you can use the show interface linecard flow-capture command to display the flow capture status, including whether flow capture is currently recording or is stopped, the capacity already used and the number of packets recorded. 2-20

21 Chapter 2 debug ftp debug ftp Debugs the ftp client. By generating FTP get and put requests to a specified server, this command provides the ability to spawn a number of tasks that perform the same FTP operation in parallel. This allows you to test the system behavior under these conditions. debug ftp get filename [tasks num-tasks ] debug ftp put filename [tasks num-tasks ] filename num-tasks The name of the file to get from or upload to the FTP site. Number of tasks. If this option is not included, the operation is performed in the context of the CLI task. The following options are available: get Get a file from ftp put Put a file from ftp 2-21

22 debug get-recover-support-file Chapter 2 debug get-recover-support-file Generates a recover mode support file. debug get-recover-support-file filename filename The name of the file to get. This command is equivalent to running the "logger get support-file" command when the system is in recovery mode; however, this command can be performed even when not in recovery mode. In recovery mode, the support file is generated by the SCOS itself rather than the EM agent. Therefore, it only contains the debug, user, and stats logs. 2-22

23 Chapter 2 debug jvm debug jvm Performs jvm debug operations. debug jvm {free-memory get-max-memory run kill set-max-memory (mem-in-bytes ) shell (port# ) threads up-time user-thread-count} mem-in-bytes port# The amount of memory to allocate to the JVM The TCP port number on which the shell is to be opened. Use this command to perform the following jvm debug operations: display the amount of free jvm memory display the maximum amount of jvm memory run jvm kill jvm set the maximum amount of jvm memory start an interactive Perc shell on the specified TCP port display the jvm threads display the number of jvm threads display the jvm up time in milliseconds Use the run keyword to run jvm. Use the kill keyword to kill jvm. 2-23

24 debug logout Chapter 2 debug logout Terminates current console CLI task. This command is equivalent to the 'logout' command but is implemented in a different way. debug logout This command has no arguments or keywords. 2-24

25 Chapter 2 debug loop-forever debug loop-forever Runs an endless loop at the current CLI task. debug loop-forever This command has no arguments or keywords. Note After executing this command, no other command can be executed, including the logout command. Therefore the only way to terminate the loop is to close the Telnet/SSH session and wait until the SCE platform detects the timeout. 2-25

26 debug management-agent Chapter 2 debug management-agent Loads a support module to the management agent, providing developers access to various support methods. debug management-agent load support-mbean This command has no arguments or keywords. This command also adds the following support CLIs: debug management-agent gc Run garbage collection debug management-agent jdmk-agent [enable disable] Enable or disable the logging of JDMK calls 2-26

27 Chapter 2 debug memory-traps debug memory-traps Performs a large number of memory allocations, fills the memory locations with known contents, and later verifies whether the content has been changed. If it has, it indicates a memory corruption. This command runs forever and never returns. debug memory-traps {basic system} max-mem mem-in-bytes mem-in-bytes Maximum amount of memory to take for the trap (in bytes) 2-27

28 debug new_rpc Chapter 2 debug new_rpc Runs a simple internal RPC operation to each processor, using the "new RPC" mechanism, in order to debug the mechanism. debug new_rpc This command has no arguments or keywords. If no error is printed, the operation was successful. 2-28

29 Chapter 2 debug package debug package Performs package debug operations. debug package compare package-file-name basedir base-directory debug package extract {management-agent system} package-file-name package-file-name base-directory Name of the package file. The filename should end with the.pkg extension. Directory in which the file is to be found. (The currently installed package is always located at /tffs0/system ) Use this command to perform the following package debug operations: compare Compares the contents of a specified package file with the file currently found on disk. This option can be used to verify that the installed package is not corrupt (and of the same version), after it has been successfully installed. extract Opens the specified package file. This option can be used to perform a SCOS package installation. A reload is needed for the new SCOS to be used. The following file options are available for the extract operation: management-agent Extracts the management agent package file (as specified in the management-agent system command) system Extracts the system package file (as specified in the boot system command) 2-29

30 debug party Chapter 2 debug party Gets or sets the value of a variable in a specific party context in the control card cache (not on a specific traffic processor). debug party name party-name variable var-name {get set value } party-name var-name value Name of party Name of the variable to get or set Value to set the variable to Use this command to perform either of the following actions for the specified party: get Gets a variable from the control cache set sets the value of a variable in the control cache 2-30

31 Chapter 2 debug performance aging-tuning debug performance aging-tuning Tunes the system aging time for each protocol. debug performance aging-tuning start original-aging-time aging-time aging-factor factor dormant-time dormant-time debug performance aging-tuning start signature-id hex-id signature-mask hex-mask aging-factor factor dormant-time dormant-time debug performance aging-tuning stop debug performance aging-tuning show aging-time hex-id The current aging time of the protocol to be tuned The 32 bit HEX signature ID of the tested protocol or protocol family. (Use with SCOS v and later only.) hex-mask The 32 bit HEX mask to use for the given signature. (Use with SCOS v and later only.) factor The factor by which the aging time would be reduced. dormant-time The aging time (in seconds) to assume for treating the flow as dormant. This feature is available for SCOS versions or later only. This feature allows you to tune the system aging time for each protocol, to find the best tradeoff of capacity vs performance vs classification accuracy. The main advantage of this feature versus testing on a live setup, is that this tool provides an immediate estimation of the percentage of zombie flows on each protocol on a global scope. This information indicates where to invest your time, making the process of aging tuning very efficient. The tool has a slight impact on performance while it is running. General instructions for SCOS versions before Decide on the protocol to be investigated for aging tuning. 2. Display the PL aging tunables. These reflect the protocols that can be tuned for aging. show applications slot 0 all-tunables include PL_AGING 3. Set the desired tunables to a unique value that is a multiple of 10. The values in the tunables are in 100mili units, while the aging actually works with seconds, therefore the value must be divisible by 10. For example, assume that the value of the tunable is set to 610 (which means 61 seconds of aging). 4. Run the command with the original aging time set to the tunable/10: 2-31

32 debug performance aging-tuning Chapter 2 debug performance aging-tuning start original-aging-time 61 aging-factor XX dormant-aging-time YY Where XX and YY are the values to be tested. 5. To view the current state of the measurement: debug performance aging-tuning show 6. To stop the current measurement: debug performance aging-tuning stop Note that the measurement should be run in a situation where there is enough traffic, and that the traffic is relatively constant (no variance in the number of active flows). General instructions for SCOS version or later 1. Decide on the protocol (or protocol family) to be investigated for aging tuning. 2. Find the signature of that protocol/family in //depot/app/libraries/pl/dev/src/com/pcube/libs/pl/common/common_protocol_type.san 3. Run the command with the signature ID and mask to specify the desired signature/family (replace the signature numbers with the relevant ones): debug performance aging-tuning start signature-id 0x signature-mask 0xff aging-factor XX dormant-aging-time YY Where XX and YY are the values to be tested. 4. To view the current state of the measurement: debug performance aging-tuning show 5. To stop the current measurement: debug performance aging-tuning stop Note that the measurement should be run in a situation where there is enough traffic, and that the traffic is relatively constant (no variance in the number of active flows). 2-32

33 Chapter 2 debug performance traversed-packets-histogram debug performance traversed-packets-histogram Produces data that can be converted to a histogram illustrating the percentage of flows at each number of packets. debug performance traversed-packets-histogram {create filename reset} filename Name of the csv output file. This feature is available for SCOS versions or later only. One of the most important aspects affecting the performance of the Service Control solution is the number of packets traversed per flow. This histogram provides a measure of how many flows require many packets and how many require less. General instructions for SCOS versions before Close all flows in the system, and disable flow handling: Configure >Interface linecard 0 >shutdown 2. Enable the feature: debug slot 0 for-each ppc func debugperftuningtphenable 1 3. Restart flow handling: Configure >Interface linecard 0 >no shutdown 4. Create the CSV file: debug performance traversed-packets-histogram create csv-filename 5. Disable the feature, to avoid impacting performance on a production system: debug slot 0 for-each ppc func debugperftuningtphenable 0 6. Use this Excel file to quickly create the bar graph from the CSV file, TraversedPacketsHistogram. General instructions for SCOS version or later 1. Close all flows in the system, and disable flow handling using: Configure >Interface linecard 0 >shutdown 2. Set the desired packets-type to count: debug slot 0 for-each ppc func debugperftuningtphsetpacketstype type type can be one of the following: 0 Traversed (default) 1 Handled 2-33

34 debug performance traversed-packets-histogram Chapter 2 2 Total 3. Set the desired transport type of flows to count: debug slot 0 for-each ppc func debugperftuningtphsettransporttype type type can be one of the following: 0 TCP 1 UDP 2 Non-TCP/UDP 3 ALL 4. Enable the feature: debug slot 0 for-each ppc func debugperftuningtphenable 1 5. Restart flow handling: Configure >Interface linecard 0 >no shutdown 6. Create the CSV file: debug performance traversed-packets-histogram create csv-filename 7. Disable the feature, to avoid impacting performance on a production system: debug slot 0 for-each ppc func debugperftuningtphenable 0 8. Use this Excel file to quickly create the bar graph from the CSV file, TraversedPacketsHistogram. 2-34

35 Chapter 2 debug rdr-formatter send-dummy-event debug rdr-formatter send-dummy-event Causes the RDR formatter to send a dummy event. debug rdr-formatter send-dummy-event [category category# ] category# The number of the category on which to send the dummy event. 2-35

36 debug reload-shutdown Chapter 2 debug reload-shutdown Performs 'reload shutdown '. debug reload-shutdown This command has no arguments or keywords. Do not shut down an SCE platform from a remote location. This command shuts down the SCE platform in an orderly manner, before turning it off. After issuing this command, the only way to revive the SCE platform from its power-down state is to turn it off, then back on. Because of this, the basic command reload shutdown command can only be issued from the serial CLI console port. This is done to prevent the possibility of shutting it down from a remote location, from which it is not possible to power back up. However, this debug command can be executed via a Telnet connection. If this is done, the SCE platform cannot be revived until and unless a technician is available at the physical location of the SCE platform to turn it off and then back on. 2-36

37 Chapter 2 debug rpc-adapter debug rpc-adapter Performs the specified debug operation on the PRPC adapter functions. debug rpc-adapter debug-mode {off on} debug rpc-adapter kill-session session-name message message-text debug rpc-adapter reload-cfg debug rpc-adapter reset-statistics debug rpc-adapter show {configuration debug-mode sessions statistics} session-name message-text Name of the PRPC session to kill Text of the message for the peer when killing a session Use this command to perform the following debug operations on the PRPC adapter functions: debug-mode Sets the PRPC debug mode kill-session Kills the specified session reload-cfg Reloads the configuration from configuration file reset-statistics Resets the PRPC adapter statistics show Shows the following PRPC information: configuration PRPC adapter configuration parameter debug mode Enabled (true) or disabled (false) sessions PRPC adapter session information statistics PRPC adapter statistics 2-37

38 debug scmp Chapter 2 debug scmp Performs the specified SCMP debug operation. debug scmp close name peer-name debug scmp query-by-id subscriber-id name peer-name debug scmp query-by-ip ip-address name peer-name peer-name subscriber-id ip-address Name of the SCMP peer to close of to query Subscriber ID or GUID IP address in dotted notation Use this command to perform the following SCMP debug operations: close Closes an SCMP connection query-by-id Sends a query-session by subscriber ID or GUID query-by-ip Sends a query-session by IP address 2-38

39 Chapter 2 debug simulation debug simulation debug simulation get-bw-records filename debug simulation reset debug simulation resume debug simulation run debug simulation stop debug simulation suspend filename Name of the file containing the bandwidth records Use this command to perform the following simulation operations: get-bw-records Gets the bandwidth records reset Resets the simulation resume Resumes the simulation run Runs the simulation stop Stops the simulation suspend Suspends the simulation 2-39

40 debug slot control-func Chapter 2 debug slot control-func Runs a control card debug function on the CLI context for the specified slot. debug slot slot-number control-func function-name [argument1 [argument2... [argument12]]] slot-number The number of the identified slot. Enter a value of 0. function-name The name of the control card function to run. Any exported control card function may be specified. argument1, argument2,... argument12 Up to twelve optional arguments required for the function in either decimal or HEX format. 2-40

41 Chapter 2 debug slot diagnostics debug slot diagnostics Switches to Diagnostics software after reload command. debug slot slot-number diagnostics slot-number The number of the identified slot. Enter a value of

42 debug slot for-each ppc clear Chapter 2 debug slot for-each ppc clear Clears the relevant counters on each ppc in the specified slot. debug slot slot-number for-each ppc clear counters slot-number The number of the identified slot. Enter a value of 0. To perform this debug task only on a specified PPC, see debug slot ppc clear. 2-42

43 Chapter 2 debug slot for-each ppc func debug slot for-each ppc func Executes a function on each ppc in the specified slot. debug slot slot-number for-each ppc func function-name [argument1 [argument2... argument12]]] slot-number The number of the identified slot. Enter a value of 0. function-name The function to execute. Any exported function may be specified (see "Functions" section of "" for a subset list of specific functions displayed explicitly in the CLI). argument1, argument2,... argument12 Up to twelve optional arguments required for the function in either decimal or HEX format. To perform this debug task only on a specified PPC, see debug slot ppc func. Functions The following is a listing of the subset of available functions that are displayed explicitly (and therefore also for which autocomplete is available) in the CLI: CLS_CAM_DumpTuples Dump all Tuples of the Classifier CAM CLS_SDRAM_DumpTuples Dump all Tuples of the Classifier SDRAM CLS_ShowCounter Display Classifier counters cps Clear RuC party statistics d Display memory da Disable Aging devs List devices drv List system drivers ea Enable Aging FCRate_getRate Display the Flow Context rate measured in the system fd List file descriptor names FF_ShowCounter Display Flow Filter counters for a given port i Tasks tcbs summary ir Initialize the general RuC statistics irdp Initialize the RuC dropped packets statistics 2-43

44 debug slot for-each ppc func Chapter 2 memshow System memory information paa Update aging time to immediate for all parties PARTY_debugShowDynamicStuf Dynamic party info PARTY_debugShowStaticStuff Static party info printerrno Print definition of error status RUC_DumpAllSubtasks Show the RuC subtasks running on this cpu. Argument = DumpLevel (0/1/2) RUC_HWCNTR_PrintMasterCntrs Display DP and Gmac counters for a given port RUC_HWCNTR_ResetMasterCntrs Reset DP and Gmac counters for a given port RUC_LUT_DumpCacheLutsInfo Dump all the Cache LUTs' info RUC_LUT_DumpLutEntries Dump a specific LUT's (ID) Entries RUC_LUT_DumpLutStats Dump a specific LUT's (ID) Stats RUC_LUT_Help Display the RUC_LUT (and cache LUT) debug help RUC_LUT_ResetLutEntries Reset a specific LUT's entries RUC_ResetAllSubtasks Reset all the RuC subtasks running on this cpu RUC_ShowSubtaskTables Show the names of the subtasks tables currently registered on this cpu. sd Display the test-end and Line Card state output sps Display RuC party statistics sr Display the general RuC statistics srdp Display RuC dropped packets statistics sysupdateflash Update the bootrom EXECUTE THIS COMMAND ONLY IF YOU ARE SURE. td Delete task telnetshell Start a Telnet daemon for remote target shell (SCE2000 only) ti Task TCB complete information tr Resume task ts Suspend task tt Task trace uaa Update Aging t.o/immed. of all FCs (*100 mili) wsr Display the RuC WAP traffic statistics As mentioned above, you may name any other exported function that does not appear on the above list Specify up to twelve arguments necessary for running the function in either decimal or HEX format. 2-44

45 Chapter 2 debug slot for-each ppc probe debug slot for-each ppc probe Performs the specified debug task for each ppc in the specified slot. debug slot slot-number for-each ppc probe clear flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe clear flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each ppc probe clear (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe clear path path debug slot slot-number for-each ppc probe list flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe list flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each ppc probe list (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe list path path debug slot slot-number for-each ppc probe show flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe show flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each ppc probe show (limits max-depth depth-value max-elements max-elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each ppc probe show path path slot-number The number of the identified slot. Enter a value of 0. depth-value The maximum number of levels to probe (traversing depth) max-elements-value The maximum total number of elements node-elements-value The maximum number of single node elements path See "Path" section of "" 2-45

46 debug slot for-each ppc probe Chapter 2 Use this command to perform the specified debug task for each ppc in the specified slot. The following options are available: probe Manipulate probe processor data for each ppc clear Clear probe data list List probe elements show Display probe content To perform this debug task only on a specified PPC, see debug slot ppc probe. For each option (clear, list, show), specify one, two, or all of the following options (in the order listed; flags/limits/path or flags/path or limits/path or just path): flags Set command flags limits Set action limits path Path to starting node Flags The following is a description of the flag settings: log no-log Indicates whether or not to log the action details no-details Indicates whether or not to provide more details no Reserved for future flag 1 no Reserved for future flag 2 If you use the flags option, you must specify a setting for all four flags. Limits The following is a description of the action limits: max-depth Limits the traversing depth (number of levels) max-elements Limits the total number of elements max-node-elements Limit the number of elements per single node The default value for all limits is 0. Path The following is a listing of the explicitly specified available paths, which is a subset of all available paths: RUCMasterCntrs.DpVASCnt.* DP VAS counters [port][vas#].pkts/bytes RUCMasterCntrs.TxFromVASCnt.* TX transmitted from VAS(VLAN removed)[port][vas#] in bytes RUCMasterCntrs.TxToVASCnt.* TX transmitted to VAS (VLAN added) [port][vas#] in bytes RUCMasterCntrs.TxVQCnt.* TX GC counters [port][gc] in bytes traverser.* Traverser stats VAS.agent.counters.* VAS agent counters VAS.agent.data.* VAS agent data VAS.controlCard.counters.* VAS control card counters VAS.controlCard.data.* VAS control card data 2-46

47 Chapter 2 debug slot for-each ppc probe VAS.HCMonitor.data.* VAS HC monitor data VAS.lineCard.counters.* VAS line card counters VAS.lineCard.data.* VAS line card data You may specify any other custom path to a node. 2-47

48 debug slot for-each ppc set Chapter 2 debug slot for-each ppc set Set a value for a specified party variable for each ppc in the specified slot. debug slot slot-number for-each ppc set party party-name variable var-name value var-value slot-number The number of the identified slot. Enter a value of 0. party-name The name of the party (subscriber) to set the variable value for. var-name The name of the variable. var-value The value to set for the specified party variable. To perform this debug task only on a specified PPC, see debug slot ppc set. 2-48

49 Chapter 2 debug slot for-each ppc show debug slot for-each ppc show Displays the sr counters or the specified variable value for each ppc in the specified slot. debug slot slot-number for-each ppc show counters debug slot slot-number for-each ppc show variable var-name slot-number The number of the identified slot. Enter a value of 0. var-name The name of the variable. The following options are available: Display the values of the sr () counters Display the values of a specified global variable Make sure you use a global variable. To perform this debug task only on a specified PPC, see debug slot ppc show. 2-49

50 debug slot for-each ppc show-component Chapter 2 debug slot for-each ppc show-component Displays the dump for the specified component for each ppc in the specified slot. debug slot slot-number for-each ppc show-component component-name slot-number The number of the identified slot. Enter a value of 0. component-name The name of the component to display. To perform this debug task only on a specified PPC, see debug slot ppc show-component. 2-50

51 Chapter 2 debug slot for-each ppc show-counters debug slot for-each ppc show-counters Shows sr() counters for each ppc in the specified slot. debug slot slot-number for-each ppc show-counters slot-number The number of the identified slot. Enter a value of 0. To perform this debug task only on a specified PPC, see debug slot ppc show-counters. 2-51

52 debug slot for-each ppc spawn Chapter 2 debug slot for-each ppc spawn Executes a function on each ppc in the specified slot in a separate task. debug slot slot-number for-each ppc spawn prior priority# func func-name [argument1 [argument2... [argument12]]] slot-number The number of the identified slot. Enter a value of 0. priority# The priority to assign to the task. function-name The name of the function to execute (see "Functions" section of "Usage Guidelines"). argument1, argument2,... argument12 Up to twelve optional arguments required for the function in either decimal or HEX format. To perform this debug task only on a specified PPC, see debug slot ppc spawn. Functions The following is a listing of all the available functions: CLS_CAM_DumpTuples Dump all Tuples of the Classifier CAM CLS_SDRAM_DumpTuples Dump all Tuples of the Classifier SDRAM CLS_ShowCounter Display Classifier counters cps Clear RuC party statistics d Display memory da Disable Aging devs List devices drv List system drivers ea Enable Aging FCRate_getRate Display the Flow Context rate measured in the system fd List file descriptor names FF_ShowCounter Display Flow Filter counters for a given port i Tasks tcbs summary ir Initialize the general RuC statistics irdp Initialize the RuC dropped packets statistics memshow System memory information 2-52

53 Chapter 2 debug slot for-each ppc spawn paa Update aging time to immidiate for all parties PARTY_debugShowDynamicStuf Dynamic party info PARTY_debugShowStaticStuff Static party info printerrno Print definition of error status RUC_DumpAllSubtasks Show the RuC subtasks running on this cpu. Argument = DumpLevel (0/1/2) RUC_HWCNTR_PrintMasterCntrs Display DP and Gmac counters for a given port RUC_HWCNTR_ResetMasterCntrs Reset DP and Gmac counters for a given port RUC_LUT_DumpCacheLutsInfo Dump all the Cache LUTs' info RUC_LUT_DumpLutEntries Dump a specific LUT's (ID) Entries RUC_LUT_DumpLutStats Dump a specific LUT's (ID) Stats RUC_LUT_Help Display the RUC_LUT (and cache LUT) debug help RUC_LUT_ResetLutEntries Reset a specific LUT's entries RUC_ResetAllSubtasks Reset all the RuC subtasks running on this cpu RUC_ShowSubtaskTables Show the names of the subtasks tables currently registered on this cpu sd Display the test-end and Line Card state output sps Display RuC party statistics sr Display the general RuC statistics srdp Display RuC dropped packets statistics sysupdateflash Update the bootrom EXECUTE THIS COMMAND ONLY IF YOU ARE SURE. td Delete task telnetshell Start a Telnet daemon for remote target shell (SCE2000 only) ti Task TCB complete information tr Resume task ts Suspend task tt Task trace uaa Update Aging t.o/immed. of all FCs (*100 mili) wsr Display the RuC WAP traffic statistics STRING Name of any other function that does not appear on the above list 2-53

54 debug slot for-each traffic-processor clear counters Chapter 2 debug slot for-each traffic-processor clear counters Clears the relevant counters on each traffic-processor in the specified slot. debug slot slot-number for-each traffic-processor clear counters slot-number The number of the identified slot. Enter a value of

55 Chapter 2 debug slot for-each traffic-processor func debug slot for-each traffic-processor func Executes a function on for each traffic-processor in the specified slot. debug slot slot-number for-each traffic-processor func function-name [argument1 [argument2... [argument12]]] slot-number The number of the identified slot. Enter a value of 0. function-name The function to execute. Any exported function may be specified (see "Functions" section of "" for a subset list of specific functions displayed explicitly in the CLI). argument1, argument2,... argument12 Up to twelve optional arguments required for the function in either decimal or HEX format. Functions The following is a listing of the subset of available functions that are displayed explicitly (and therefore also for which autocomplete is available) in the CLI: CLS_CAM_DumpTuples Dump all Tuples of the Classifier CAM CLS_SDRAM_DumpTuples Dump all Tuples of the Classifier SDRAM CLS_ShowCounter Display Classifier counters cps Clear RuC party statistics d Display memory da Disable Aging devs List devices drv List system drivers ea Enable Aging FCRate_getRate Display the Flow Context rate measured in the system fd List file descriptor names FF_ShowCounter Display Flow Filter counters for a given port i Tasks tcbs summary ir Initialize the general RuC statistics irdp Initialize the RuC dropped packets statistics memshow System memory information 2-55

56 debug slot for-each traffic-processor func Chapter 2 paa Update aging time to immediate for all parties PARTY_debugShowDynamicStuf Dynamic party info PARTY_debugShowStaticStuff Static party info printerrno Print definition of error status RUC_DumpAllSubtasks Show the RuC subtasks running on this cpu. Argument = DumpLevel (0/1/2) RUC_HWCNTR_PrintMasterCntrs Display DP and Gmac counters for a given port RUC_HWCNTR_ResetMasterCntrs Reset DP and Gmac counters for a given port RUC_LUT_DumpCacheLutsInfo Dump all the Cache LUTs' info RUC_LUT_DumpLutEntries Dump a specific LUT's (ID) Entries RUC_LUT_DumpLutStats Dump a specific LUT's (ID) Stats RUC_LUT_Help Display the RUC_LUT (and cache LUT) debug help RUC_LUT_ResetLutEntries Reset a specific LUT's entries RUC_ResetAllSubtasks Reset all the RuC subtasks running on this cpu RUC_ShowSubtaskTables Show the names of the subtasks tables currently registered on this cpu sd Display the test-end and Line Card state output sps Display RuC party statistics sr Display the general RuC statistics srdp Display RuC dropped packets statistics sysupdateflash Update the bootrom EXECUTE THIS COMMAND ONLY IF YOU ARE SURE. td Delete task telnetshell Start a Telnet daemon for remote target shell (SCE2000 only) ti Task TCB complete information tr Resume task ts Suspend task tt Task trace uaa Update Aging t.o/immed. of all FCs (*100 mili) wsr Display the RuC WAP traffic statistics As mentioned above, you may name any other exported function that does not appear on the above list. Specify up to twelve arguments necessary for running the function in either decimal or HEX format. 2-56

57 Chapter 2 debug slot for-each traffic-processor probe debug slot for-each traffic-processor probe Manipulates the probe processor data for each traffic-processor in the specified slot. debug slot slot-number for-each traffic-processor probe clear flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe clear flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each traffic-processor probe clear (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe clear path path debug slot slot-number for-each traffic-processor probe list flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe list flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each traffic-processor probe list (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe list path path debug slot slot-number for-each traffic-processor probe show flags (log no-log) (details no-details) no no (limits max-depth depth-value max-elements elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe show flags (log no-log) (details no-details) no no (path path ) debug slot slot-number for-each traffic-processor probe show (limits max-depth depth-value max-elements max-elements-value max-node-elements node-elements-value ) (path path ) debug slot slot-number for-each traffic-processor probe show path path slot-number The number of the identified slot. Enter a value of 0. depth-value The maximum number of levels to probe (traversing depth) max-elements-value The maximum total number of elements. node-elements-value The maximum number of single node elements. path See "Path" section of "". 2-57

58 debug slot for-each traffic-processor probe Chapter 2 The following main options are available: clear Clear probe data list List probe elements show Display probe content For each main option (clear, list, show), specify one, two, or all of the following options (in the order listed; flags/limits/path or flags/path or limits/path or just path): flags Set command flags limits Set action limits path Path to starting node Flags The following is a description of the flag settings: log no-log Indicates whether or not to log the action details no-details Indicates whether or not to provide more details no Reserved for future flag 1 no Reserved for future flag 2 If you use the flags option, you must specify a setting for all four flags. Limits The following is a description of the action limits: max-depth Limits the traversing depth (number of levels) max-elements Limits the total number of elements max-node-elements Limit the number of elements per single node The default value for all limits is 0. Path The following is a listing of the explicitly specified available paths, which is a subset of all available paths: RUCMasterCntrs.DpVASCnt.* DP VAS counters [port][vas#].pkts/bytes RUCMasterCntrs.TxFromVASCnt.* TX transmitted from VAS(VLAN removed)[port][vas#] in bytes RUCMasterCntrs.TxToVASCnt.* TX transmitted to VAS (VLAN added) [port][vas#] in bytes RUCMasterCntrs.TxVQCnt.* TX GC counters [port][gc] in bytes traverser.* Traverser stats VAS.agent.counters.* VAS agent counters VAS.agent.data.* VAS agent data VAS.controlCard.counters.* VAS control card counters VAS.controlCard.data.* VAS control card data VAS.HCMonitor.data.* VAS HC monitor data VAS.lineCard.counters.* VAS line card counters VAS.lineCard.data.* VAS line card data 2-58

59 Chapter 2 debug slot for-each traffic-processor probe You may specify any other custom path to a node. 2-59

60 debug slot for-each traffic-processor set Chapter 2 debug slot for-each traffic-processor set Sets a value for a specified party variable for each traffic-processor in the specified slot. debug slot slot-number for-each traffic-processor set party party-name variable var-name value var-value slot-number The number of the identified slot. Enter a value of 0. party-name The name of the party (subscriber) to set the variable value for. var-name The name of the variable. var-value The value to set for the specified party variable. 2-60