Searching: serial connection - 10 Results Found

VTrak Other Using WebPAM for firmware updates on the VTrak Mx10 products may cause some issues.
Ken Chou posted this 16 April 2008

Summary:

Due to some issues seen with updating the firmware for VTrak Mx10 products via WebPAM, Promise Technology recommends performing all firmware updates on the VTrak Mx10 family via the CLU/CLI and TFTP server. This issue only effects the M210, M310 and M610 VTrak products.

Note - It is recommended to stop all I/O and Disk activity on the VTrak before updating the firmware. In the event of an error after the firmware flash, please contact Promise Technical Support for additional assistance: https://support.promise.com

 

Updating the firmware from the CLU

  1. Download the Free TFTP server from solarwinds.net site. A link is given below for download location.
     
  2. Install the Solar Winds TFTP server software. Reboot server after installation
     
  3. Download the latest VTrak MClass firmware update
     
  4. Launch the TFTP server
     
  5. Copy the firmware image file (*.img) to the C:\TFTP-Root Folder
     
  6. From the TFTP server, go to File and click on Configure. Click on the Security tab and make sure you enable Transmit and Receive.
    • You need to keep the TFTP server running to upgrade the firmware.
       
  7. Setup a serial connection to the VTrak controller and use HyperTerminal to log in
    • Check that the terminal settings are 115200, 8 bit, 1 stop bit, no parity, no flow control.
    • When the HyperTerminal window opens, press ENTER to start the CLU 
    • For more information on making the serial connection, please see your VTrak user manual.
       
  8. From the CLU's Main Menu, select Additional Info and Management, and then press Enter 
     
  9. Select Flash Through TFTP and then press Enter. Verify TFTP server IP address is the same IP address as the host PC. If TFTP server IP address is incorrect, you will be unable to download the firmware image from TFTP server.
     
  10. Select TFTP Server
    • Type the IP of TFTP server. This should be the same IP address as your host computer.
    • Port number: 69.  This is the default for TFTP server
    • File Name: Enter the filename of the firmware image to upload.
       
  11. Then select [start] and then press Enter. After pressig Enter, firmware download from the tftp server will begin. You should see the file being extracted from the host system.
     
  12. Once the firmware is complete, please be sure to reboot the VTrak.

 

Updating the firmware from the CLI

Steps 1 though 6 are same as above.

  1. Connect to the VTrak controller via serial or telnet connection and use HyperTerminal to log in
    • For serial: Check the following settings: 115200, 8 bit, 1 stop bit, no parity, no flow control.
    • For telnet: Telnet to the VTrak's IP address; port 2300
       
  2. When the HyperTerminal window opens, press ENTER and log in,
    • If the session opens into the CLU menu, type CTRL-X or choose Return to CLI from the main menu.
       
  3. At the CLI, type ptiflash -t -s -f
    • example: ptiflash -t -s 192.168.1.1 -f fw_multi_20031010.img
       
  4. Once the firmware update is complete, please be sure to reboot the VTrak.
     

 

Legacy Other How do I enable debug prints for Vtrak E-Class series products?
Ken Chou posted this 27 November 2007

The Vtrak E-Class (VTE) series product starting in Service Release 2.3 will offer the ability to enable debug prints. Debug prints allow the support engineers to further diagnose problems encountered with the Promise Vtrak. How do you capture the debug prints? How do you enable debug prints? What other information is useful to help support better support you?

1. You can capture the debug prints by doing the following: Make sure you are connected to the RJ11 to RS232 connector on each IO RAID Controller of the VTE unit. For each serial connection open a hyperterminal session (see Vtrak Promise user manual for proper baud rate). Once you have Hyperterminal configured make sure to capture the output to a file. Do the same for the remaining controller if running dual controllers.

2. You can enable the debug prints from CLI: "debug -a enable -n fw" (do the same for the remaining controller). See example below:

administrator@cli> ? debug

debug

Usage:

debug [-a <action>] [...]

debug -a list [-c <count>]

debug -a mod -s "<list of settings>"

debug -a export [-t <log type>] -s <TFTP server> [-p <port num>]

Summary:

Debug is used to process special debug functions, such as to view to change

the controller debug level, and to export debug log.

-a <action> Which action to perform.

list list debug info of the controller

mod modify debug settings of the controller

export export debug log(s) of the current controller.

This action is not applicable for in-band.

enable enalbe debug of component. For embedded only.

disable disable debug of component. For embedded only.

dump dump debug information of component. For embedded only.

-c <count> The count of the controller.

The default is maximum number of controller(s) supported

by the subsystem.

-n <component name> Specifies the component name to enable or disable debug.

fw firmware.

-s "<option>=<value>"

Used to specify which settings to change.

level= The debug level of the controller.

silent no debug message will be logged

fatal only fatal error message will be logged

error error and fatal error message will be logged

warning warning, error and fatal error messages will be logged

info all messages will be logged

-t <log type> Which type of debug log to export

iscsi (Default) export iSCSI crash log. This option is valid

only for iSCSI host interface product.

-s <TFTP server> The ip address or host name of the TFTP server,

the debug log on to

-p <port num> The port number of the TFTP server. Default is 69.

Examples:

debug

debug -a mod -s "level=warning"

debug -a export -t iscsi -s 192.168.10.79 # not applicable for in-band

Type " | more" at the end of each command, to display info page by page.

3. It is also extremely helpful if you provide the "subsysteminfo" file via Web Pam or CLI. You can retrieve the subsysteminfo via WebPam by clicking on the left hand side on the tree menu on the IP link. Once you click on the IP Link on the left hand side you will be able to save the subsysteminfo file by clicking on the "Save" button.

Via CLI you will have to use the "export" command. Make sure you specify your tftp IP address when issuing export command. See example below:


-------------------------------------------------------------
Promise Command Line Interface (CLI) Utility
-------------------------------------------------------------

Login: administrator
Password: ********
-------------------------------------------------------------
Type help or ? to display all the available commands
Type menu to enter Menu Driven Configuration Utility
-------------------------------------------------------------

administrator@cli> ? export
export

Usage: export -t <fileType> [-s <tftpServer>] [-p <port>] -f <fileName>

Summary:
   export certain type of configuration files to remote or local host.

Options:

-t <file type>       Specifies what type of file to export.

   userdb            User database file. This file type is not applicable for
                     in-band and can only be exported to remote host.
   servicereport     System service report file. This file is exported to
                     remote host for embedded and local host for in-band.

-f <file name>       Specifies the name of the file to be exported.

-s <TFTP server>     Specifies tftp server's IP or host name. Do not specify
                     TFTP server for in-band.

-p <port num>        The port number of the TFTP server. Default is 69. Do
                     not specify port number for in-band.

Examples:
   export -t userdb -s 192.168.1.1 -f userdb.bin
   export -t servicereport -s 192.168.1.1 -f servicereport.txt # for embedded
   export -t servicereport -f servicereport.txt  # for in-band

Type " | more" at the end of each command, to display info page by page.

administrator@cli>

 

Search
Popular Tags
Categories
Close