[Top] [Table Of Contents] [Prev] [Next] [Index]
6 out of 8 total pages
 

ComOS 4.2 Commands   3

  This chapter describes the commands introduced in ComOS 4.2 for the PortMaster 4. Command descriptions appear in the following sections:
  The complete set of commands used to configure, monitor, and debug the PortMaster 4 is described in the PortMaster 4 Command Line Reference.  
  For detailed information on how to use these commands, see the PortMaster 4 Configuration Guide , the PortMaster Routing Guide , and the PortMaster Troubleshooting Guide .
  You can also configure the PortMaster 4 with the PMVision graphical user interface (GUI) for Microsoft Windows, UNIX, and other platforms supporting the Java Virtual Machine (JVM). Access PMVision online help for more information or see the PMVision User's Guide  for additional information.
  The See Also section in each command description refers to related commands in the PortMaster 4 Command Line Reference .
 

       Redundant Manager Module Commands

  ComOS 4.2 introduces the following commands to configure and manage the redundant system manager module. ComOS 4.2 also includes existing commands that have been modified to support the redundant manager module.
  Chapter 1, "Installing and Working with the Redundant Manager Module," describes in detail how to use these commands to configure the redundant manager module for the PortMaster 4.
 

       copy peer

  This command copies a file between the system manager modules.

  copy /Subdirectory/Filename(source)  peer:[/Subdirectory/Filename(destination) ]

 
 /Subdirectory  Path to the file.
 /Filename(source)  Name of the file to be copied. Filenames and directory names cannot exceed 16 characters.
 peer:  Manager module to copy the file to.
 /Filename
(destination) 		 Optional name to assign to the copied file in the new directory. If no name is specified, the PortMaster assigns the original filename.  Leave no space between peer:  and the path to the file and filename.
 

  ComOS 4.2 supports an enhanced copy  command that allows a specific file to be copied from one manager module to another manager module using the peer  keyword.
  Each manager module has is own file system. Use the show files  command before and after using the copy  command. See the copy  command description in the PortMaster 4 Command Line Reference  for additional information.
 

       reboot me|system|secondary

  This command restarts the software on a module of the PortMaster 4 or on the entire PortMaster 4, using the currently saved configuration.

  reboot [me|system|secondary]

 
 me  Reboots the manager module receiving the command.

  Caution ¯ Using the reboot me  command on the primary manager module drops all calls and shifts primary responsibility to the secondary manager module.

 system  Reboots the entire PortMaster 4 when issued from either manager module.
 secondary  Reboots the secondary manager when issued from either manager module.

  Note ¯ Use the save all  command to copy the current system configuration to the secondary manager module before rebooting it.

  ComOS 4.2 supports the enhanced reboot  commands on the PortMaster 4 to support a redundant manager module. Entering the reboot  command without any arguments on the primary manager module reboots the entire PortMaster 4. Entering reboot  from the secondary manager module reboots only the secondary manager module.
  For additional information on redundant manager module failover, see "Primary Manager Module Failover" on page 1-22.
 

       rename

  This command saves a copy of a file under another name to the local module's nonvolatile RAM.

  rename /Subdirectory  /Filename(original)  /Filename(copy)

 
 /Subdirectory  Path to the file.
 /Filename(original)  Name of the file to be copied.
 /Filename(copy)  Name of the file to save.
 

 

       reset secondary

  This command shuts down and immediately restarts the secondary manager module.

  reset secondary|slotSlotnumber 

 
 secondary  Resets the secondary manager module when issued from either manager module. This command performs the same function as the reboot secondary  command.

  Note ¯ Use the save all  command to copy the current system configuration to the secondary manager module before resetting it.

 slotSlotnumber   Resets a board in the specified slot--physical or virtual.

  ComOS 4.2 supports the enhanced reset  command to support the secondary manager module using the secondary  keyword. Entering reset slot Slotnumber  from the secondary manager using the slot number of the primary manger is the only way to reboot the primary manager from the secondary.
  For additional information about the reset command, see the PortMaster 4 Command Line Reference .
  No output is generated from this command.
  reset
 

       save [peer-also|local-only]

  This command saves configuration information to the nonvolatile memory of the primary manager module or of both the primary and secondary manager modules.

  save Keyword  [local-only|peer-also]

 
 Keyword  all , global , console , filter , host , location , netmask , ports , route , snmp , user , ospf , bgp .  For a complete description of these keywords, see the PortMaster 4  Command Line Reference .
 local-only  Saves to the nonvolatile memory of the manager module from which you enter the command.
 peer-also  Saves to nonvolatile memory of both the primary and secondary manager modules. This is the default.  The save peer-also  command cannot be issued from the secondary manager module.

  ComOS 4.2 supports the enhanced save  command with the new keywords peer-also  and local-only  to allow the PortMaster 4 to save to the primary manager module or to both the primary and secondary manager modules. See the save  command description in the PortMaster 4 Command Line Reference  for additional information. 
 

       set altname

  This command sets the prompt for the system manager module occupying slot 5 in the PortMaster 4.

  set altname Hostname

 
 Hostname  Alternate hostname of up to 39 characters for the manager module occupying slot 5.
 

 

       set debug m2m

  This command debugs the manager-to-manager protocol that runs between the primary and secondary manager modules.

  set debug m2m

  Use this command to see if the universal asynchronous receiver transmitter (UART) is functioning properly between the manager modules.
 

       show bootlog

  This command shows the reboot information and stack traces of the boards and modules that are stored in a boot log file.

  show bootlog

  ComOS 4.2 supports the enhanced show bootlog command, which now displays register and software version information in the output.
  Use this command to capture reboot information without using a console. The PortMaster 4 reserves a portion of its memory to store stack traces and the last process ID. The boot log is stored in the nonvolatile RAM file system in a file named bootlog , a circular buffer up to 64KB in length.
  When a board in the PortMaster 4 reboots, it checks for information in the reserved area and sends it to the boot log and the console, if configured. This portion of memory is not overwritten at boot time so this information can be preserved. To erase boot log information, use the erase file bootlog command.
  To translate the last process and stack trace data, send the information to Lucent Netcare Technical support.
  The information that is stored in the boot log consists of the following:
 
 
 Time Stamp  Time elapsed since the board was last rebooted.
 Slot  Slot where the reboot occurred.
 Description  Indicates if the unit was powered on, soft booted, or crashed.  If a crash occurred, the stack trace is displayed.  If a softboot and crash occurred, the last process is displayed.
  In the following example, the software version is ComOS 4.2b6. The register values are displayed after Regs.
 

  Command> show bootlog 
000:00:01:21:65] Slot0 - Crash Boot @ 0:19 pm4qt1OS: [[4.2b6]]
Crash type 3 - Last Proc 0x0 - IP 0x167768
Regs: 00167760 001E7120 00245488 00000000 00210D68 001E7154 00000000 00210D4C
1c4aa7 (8 216 1e7154 0 0 31 206 0)
167768 (245488 210d94 1e7120 1e7154 0 210dac 15b90b 2)
15b4a2 (245488 12df8 ffff000 0 0 0 0 0)
15b8dc (2 1fff28 800 210ddc 210dd8 12df8 ffff000 1)
11ea15 (1bee 14e574 202498 0 0 0 0 0)
11ed5d (1022b9 1bee 0 40 ffff000 ff540 ffff000 a)
10272f (0 0 0 0 0 0 0 0)
-- Press Return for More --
10f0f4 (0 0 0 0 0 0 0 0)
ff1e1 (0 0 0 0 0 0 0 0)
0 (0 0 0 0 0 0 0 0) }}}

 

       show smm-backup

  This command displays information about the primary and secondary manager modules if a redundant manager module is installed and operating in the PortMaster 4.

  show smm-backup

 

       tftp get peer-also|local-only

  This command retrieves a file and saves to the nonvolatile memory on one system manager module or on both the primary and secondary manager modules.

  tftp get Ipaddress  Filename  peer-also|local-only

 
 Ipaddress  IP address of the TFTP server.
 Filename  Name of a file.
 peer-also  Saves a file to the nonvolatile RAM on both the primary and secondary manager modules.
 local-only  Saves a file to the nonvolatile RAM on the manager module from which you enter the command.
 

  ComOS 4.2 supports this modified tftp  command to enable a system manager on the PortMaster 4 to save a file to the other manager module in addition to its own nonvolatile RAM.
 

       RADIUS Commands

  ComOS 4.2 introduces the following RADIUS commands to configure the PortMaster 4 to use a RADIUS server. For a complete list of RADIUS commands, see Chapter 3 of the PortMaster 4 Command Line Reference .
 

       set accounting count

  This command sets the number of times the PortMaster attempts to send a RADIUS accounting packet to a RADIUS accounting server.

  set accounting count Number

 
 Number  Number of times the PortMaster attempts to send a RADIUS accounting packet to a RADIUS accounting server if it does not receive an acknowledgment from the server.  Integer between 1 and 99. The default is 5.
 

  When the PortMaster attempts to send a RADIUS accounting packet to the RADIUS accounting server and it does not receive an acknowledgment, it retransmits the packet the number of times set with this command.
  If no acknowledgment is sent from the primary accounting server in response to the last retry packet, the PortMaster sends the packet to both the primary and alternate RADIUS accounting servers.
  If an acknowledgment is received from the RADIUS accounting server, the PortMaster no longer tries to resend the accounting packet.
  To view the accounting count setting, use the show global  command.
  set accounting interval - page 3-9
 

       set accounting interval

  This command sets the interval between accounting packet retransmissions to a RADIUS accounting server.

  set accounting interval Seconds

 
 Seconds  Number of seconds that elapse between RADIUS accounting packet retransmissions that are not acknowledged by an accounting server.  Integer between 1 and 255. The default is 30 seconds.
 

  When the PortMaster attempts to send a RADIUS accounting packet to the RADIUS accounting server and it does not receive an acknowledgment, it retransmits the packet the number of times set with the set accounting count  command. Use the set accounting interval  command to set the time interval between attempts to resend the RADIUS accounting packet.
  If no acknowledgment is sent from the primary accounting server in response to the last retry packet, the PortMaster sends the packet to both the primary and alternate RADIUS accounting servers.
  To view the accounting count and the accounting interval settings, use the show global  command.
 

       set authentication failover

  This command enables the PortMaster to dynamically switch primary and alternate RADIUS authentication servers based on their response to authentication requests.

  set authentication failover on|off

 
 on  If the primary authentication server fails to respond to three consecutive requests, the PortMaster sends seven requests to both the primary and secondary servers.  If the secondary server replies before the primary server, it becomes the primary server.
 off  The PortMaster always tries the primary server first. This is the default.

  This command enables the RADIUS authentication failover feature on the PortMaster. When RADIUS authentication failover is enabled, the PortMaster does the following:

  1. Sends three access-request packets to the primary authentication server and awaits a response.

  2. Sends seven requests to both the primary and secondary authentication servers and awaits a response.

  3. If the secondary server responds first and failover is set to on, designates it as the primary authentication server and sends it the authentication request from the next login attempt.

  4. If the designated primary server does not respond after three attempts, starts the failover process again.

  The server currently designated as primary is marked with an asterisk (*) in the output of the show global  command.
  To set the request interval, use the set authentication interval  command.
  set authentication interval - page 3-9
 

       set authentication interval

  This command sets the number of seconds that a PortMaster waits for a response from a RADIUS authentication server.

  set authentication interval Seconds 

 
 Seconds  Value between 1 and 255. The number of seconds that must elapse between RADIUS access-request retransmissions if the PortMaster receives no response from a RADIUS authentication server. The default is 3 seconds, and 0 resets the value to the default.

  The Seconds  value determines how long the PortMaster waits before sending a subsequent request to the authentication server. In addition, the PortMaster waits two times this value to initiate failover. For example, if set authentication interval 6  is used, failover occurs in 12 seconds.
  set authentication failover - page 3-10
 

       L2TP Command

  ComOS 4.2 introduces the following Layer 2 Tunneling Protocol (L2TP) command for the PortMaster 4. For a complete description of L2TP commands, see Chapter 17, of the PortMaster 4 Command Line Reference .
 

       set l2tp id-for-host

  This command sets an L2TP access concentrator (LAC) host to report itself using the RADIUS Tunnel-Assignment-ID value instead of its IP address or hostname during tunnel negotiations.

  set l2tp id-for-host on|off

 
 on  Sets a LAC host to identify itself by its RADIUS Tunnel-Assignment-ID during L2TP negotiations.
 off  Sets a LAC host to identify itself using its IP address or hostname during L2TP negotiations. This is the default.

  To use this command on a line board designated as a LAC, you must first select a slot for configuration using the set view command.
  By default, a host identifies itself with an IP address during L2TP negotiations. You can use this command to enable a host to identify itself with the Tunnel-Assignment-ID that you assign in RADIUS.
 

       Global Command

 

       set chapname

  This command sets a name that the entire PortMaster 4 uses to identify itself during Challenge Handshake Authentication Protocol (CHAP)negotiations.

  set chapname Name

 
 Name  Name of up to 39 characters that the PortMaster 4 uses to identify itself during CHAP negotiations.
 

  This command enables multiple PortMaster 4 units to act like one system for CHAP operations if you set the same CHAP name on all of them.
  No output is generated from this command.

  Command> set chapname building1 

 

       SS7 Commands

  ComOS 4.2 introduces the following commands used to configure Signaling System 7 (SS7) on the PortMaster 4. For a description of other commands related to SS7 configuration, see Chapter 15 of the PortMaster 4 Command Line Reference .
 

       set imt-reject-cause

  The command sets the cause code used when incoming calls are rejected by RADIUS when call-checking is enabled for SS7.

  set imt-reject-cause Cause_code

 
 Cause_code  Value of the reject code, an integer between 1 and 63. The default value is 1.
 

  To use this command, you must first select a slot for configuration using the set view  command.
  Use this command for telecommunications service providers that require a specific action to be taken when a RADIUS rejection occurs.
 

       set imt-alt

  This command sets one or more alternate SS7 gateways for the line boards of the PortMaster 4.

  set imt-alt 1|2|3 Ipaddress

 
 1  First alternate gateway.
 2  Second alternate gateway.
 3  Third alternate gateway.
 Ipaddress  IP address of the alternate gateway.
 

  To use this command, you must first select a slot for configuration using the set view  command.
  Use this command to configure the alternate gateways for each card. To remove an alternate gateway, set the IP address to 0.0.0.0.
  Each slot card first attempts to connect to the primary gateway. If the attempt is unsuccessful, the card retries in the following order:

  1. First alternate gateway

  2. Second alternate gateway

  3. Third alternate gateway

  4. Primary gateway

  Only one SS7 gateway must be active at any given time. When an alternate gateway is enabled after a line board detects that the primary gateway is unavailable, a failover is accomplished within 30 seconds or less. The PortMaster 4 retains calls between failovers, and informs the new gateway about existing calls.

  Note ¯ If multiple gateways are running at the same time, a situation can occur in which the first connection attempt might succeed for an alternate gateway, and the different slots become connected to different gateways. When the primary gateway comes back online, the alternate gateways must be shut down to allow the PortMaster 4 to switch back to the primary gateway.

[Top] [Table Of Contents] [Prev] [Next] [Index]
6 out of 8 total pages
spider@livingston.com
Copyright © 2000, Lucent Technologies. All rights reserved.