Server Availability Management Processor (SAMP): Avaya ...

Server Availability ManagementProcessor (SAMP): Avaya S8510 Server

03-602923Issue 1

June 2008

© 2008 Avaya Inc.

All Rights Reserved.

Notices

While reasonable efforts were made to ensure that the information inthis document was complete and accurate at the time of printing,Avaya Inc. can assume no liability for any errors. Changes andcorrections to the information in this document might be incorporatedin future releases.

For full support, please see the complete document, Avaya SupportNotices for Hardware Documentation, document number 03–600759.

To locate this document on our Web site, simply go to http://www.avaya.com/support and search for the document number in thesearch box.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, additions, ordeletions to the original published version of this documentationunless such modifications, additions, or deletions were performed byAvaya. Customer and/or End User agree to indemnify and holdharmless Avaya, Avaya's agents, servants and employees against allclaims, lawsuits, demands and judgments arising out of, or inconnection with, subsequent modifications, additions or deletions tothis documentation to the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of anylinked Web sites referenced elsewhere within this documentation,and Avaya does not necessarily endorse the products, services, orinformation described or offered within them. We cannot guaranteethat these links will work all the time and we have no control over theavailability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to yoursales agreement to establish the terms of the limited warranty. Inaddition, Avaya’s standard warranty language, as well as informationregarding support for this product, while under warranty, is availablethrough the Avaya Support Web site: http://www.avaya.com/support

Copyright

Except where expressly stated otherwise, the Product is protected bycopyright and other laws respecting proprietary rights. Unauthorizedreproduction, transfer, and or use can be a criminal, as well as a civil,offense under the applicable law.

Contact Avaya Support

Avaya Inc. provides a telephone number for you to use to reportproblems or to ask questions about your product. The supporttelephone number is 1-800-242-2121 in the United States. Foradditional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support

2 Server Availability Management Processor (SAMP): Avaya S8510 Server June 2008

http://www.avaya.com/support



Contents

Chapter 1: SAMP Overview......................................................................................................5SAMP overview................................................................................................................................................5SAMP connections............................................................................................................................................5SAMP connectivity............................................................................................................................................6SAMP software................................................................................................................................................6Modem..............................................................................................................................................................7Modem back view............................................................................................................................................8

Chapter 2: SAMP Web pages....................................................................................................9SAMP Web interface........................................................................................................................................9Login field descriptions......................................................................................................................................9Server Status field descriptions......................................................................................................................10System Board field descriptions......................................................................................................................12Cooling system field descriptions....................................................................................................................13Storage Array field descriptions......................................................................................................................14Power Supply field descriptions......................................................................................................................15SAMP field descriptions..................................................................................................................................16System field descriptions................................................................................................................................19Power/Reset field descriptions........................................................................................................................21System Inventory Data field descriptions........................................................................................................22System Inventory as Shipped field descriptions..............................................................................................24Active Alarms field descriptions......................................................................................................................25Event Log field descriptions............................................................................................................................26

Chapter 3: SAMP commands................................................................................................29SAMP commands..........................................................................................................................................29almcall............................................................................................................................................................30almclear..........................................................................................................................................................31almdisplay......................................................................................................................................................31almenable........................................................................................................................................................33almsuppress....................................................................................................................................................33environment....................................................................................................................................................34inventory..........................................................................................................................................................35loadpwd..........................................................................................................................................................36productid........................................................................................................................................................36rmbpasswd......................................................................................................................................................37rmbuseradd....................................................................................................................................................37rmbuserdel......................................................................................................................................................38rmbusermod....................................................................................................................................................38sampcmd........................................................................................................................................................39sampdiag........................................................................................................................................................39sampupdate....................................................................................................................................................41serverctrl........................................................................................................................................................41testinads..........................................................................................................................................................42testmodem......................................................................................................................................................43

Chapter 4: SAMP Procedures................................................................................................45SAMP procedures..........................................................................................................................................45Connecting to SAMP remotely using the Web................................................................................................45

Server Availability Management Processor (SAMP): Avaya S8510 Server June 2008 3

Setting Web browser options..........................................................................................................................45Connecting to SAMP directly using the Web..................................................................................................46Connecting directly to the server....................................................................................................................46Connecting remotely to the SAMP using a modem........................................................................................47Using the Web interface through the modem..................................................................................................48Using SSH through the modem......................................................................................................................48Disabling boot timer using CLI........................................................................................................................49Disabling boot timer using Web interface........................................................................................................49Copying files to server....................................................................................................................................50Determining SAMP firmware version..............................................................................................................51Downloading SAMP firmware from Avaya Support........................................................................................51Upgrading SAMP firmware..............................................................................................................................52

Index.........................................................................................................................................55

Contents


Chapter 1: SAMP Overview

SAMP overviewThe Server Availability Management Processor (SAMP) is a remote maintenance board thatmonitors and reports alerts from components within the server. The SAMP is optional andcomes preinstalled on the server for products that use it.

The SAMP board:

• Monitors the health of the server hardware, including server boot process, theCommunication Manager watch dog, the fans, the voltages, and the temperature.

• Reports server failure alarms and other alarms to Avaya INADS or other servicesgroup.

- Server by the server

- Server by the SAMP, such as server reboots.

- SAMP by the SAMP

The SAMP presents a virtual TTY that the server uses when the server must send outalarms through the modem. The modem is connected to the USB port on the SAMP boardand provides

• The capability to turn on power and to reset the server remotely.

• A secure dial-in connection to the SAMP and the server.

• Access to the SAMP and subsequently access to the server.

Note:Modem contention is resolved on a first-come, first-serve basis. For example, AvayaServices dials into the SAMP, and the server must send out an alarm through the modeminterface. Although the modem is busy, the server continues to try to send the alarm.

SAMP connectionsThe Server Availability Management Processor (SAMP) remote maintenance board isinstalled in a PCI-e expansion slot on the Avaya S8510 Server. The SAMP comes in a half-card PCI form factor and is powered externally. The SAMP supports two 10/100 Ethernet


ports and one USB port. The Ethernet port labeled 1 (Eth1) is not used. The Ethernet portlabeled 2 (Eth2) is the Services port, allowing services personnel to access the SAMP directly.

The USB port is used to connect the USB modem for remote dial-in access. For remote dial-in, the user first establishes a Point-to-Point Protocol (PPP) session that terminates at theSAMP. The user then establishes an SSH (Secure Shell) or an HTTPS (Secure Web)session to the SAMP or the server itself.

The SAMP also communicates with the host in-band by way of an on-board industry-standard Ethernet controller on the PCI bus of the host with an internal link to the SAMP.

SAMP connectivity

1 External power connector

2 USB connector for modem

3 SAMP port (Eth1 — unused)

4 SAMP services port (Eth2)

SAMP softwareThe SAMP is shipped with the software installed and with some default settings. However,you might need to install an updated version of the software and configure the SAMP beforeyou can use it.

The SAMP software update file is available on the Avaya Support Web site. See AvayaServer Availability Management Processor (SAMP): Avaya S8510 Server (03-602923) forinformation on installing software on the SAMP and changing the default settings.

SAMP Overview


ModemThe modem is used to provide remote access to the server either through the remotemaintenance board or direct connection to the server when the customer has a maintenancecontract with Avaya. Operating system and environmental alarms are sent through themodem to INADS or other service provider. Maintenance technicians can dial into the serverthrough the modem.

For a server equipped with the Server Availability Management Processor (SAMP) remotemaintenance board, the modem connects to the USB port on the SAMP. For a serverwithout the SAMP, the modem connects to one of the USB ports on the back of the server.

Important:The modem must connect to a touch tone line, not a rotary-dial line.

A telephone line connects the modem to a dedicated outside line.

Avaya supports the MultiTech MultiModem ZBA modem for use with the server. This modemprovides:

• V.92/56K download speeds and 48K upload speeds when connecting with V.92servers.

• Linux compatable.

• Globally approved for use in many countries worldwide.

• Flash memory

• Included USB cable.

Modem


Modem back view

1 Modem

2 USB cable between modem and SAMP

3 Cable from modem to outside telephone line

SAMP Overview


Chapter 2: SAMP Web pages

SAMP Web interfaceOne method to access the Server Availability Maintenance Processor (SAMP) is to use theWeb interface. You use a Web browser to access the Web interface on the SAMP. Forprocedures on accessing the SAMP using a Web browser, see

• Connecting to SAMP remotely using the Web on page 45

• Setting Web browser options on page 45

• Connecting to SAMP directly using the Web on page 46

The Web interface used with the SAMP board installed on the S8510 Server differs from theone used on the S8500 Server. It offers

• Simpler-to-use controls, with some of the controls on the SAMP and System pageshidden until you click an Advanced button.

• Enhanced log display where you can change the view of the logs from HPI eventlog to A+SAMP System Log. You also can control the number of lines displayed,search the logs using keywords, and download the entire log as a text file.

• Enhanced inventory data display where you can display the As Shipped inventorydata when the A+SAMP is first installed in a server.

The Web interface pages have a navigation pane on the left and a display pane on the right.There are also menu items across the top.

The alarms described in the Web pages are not alarmed by the SAMP board itself. Anyservice affecting alarms are logged into the syslog on the host server. The host serverdecides whether to alarm or not.

Login field descriptionsThe Login page is the first page you see when you access the Web interface through yourWeb browser and the last page you see when you log out.

The following table provides a description of the fields.


Field DescriptionUser Name: The login name you are using to log into the SAMP.

Password: The password you are using to log into the SAMP.

The following table provides a description of the buttons.

Button DescriptionLog In Logs you into the SAMP.

Cancel Cancels the action.

Server Status field descriptionsThe Server Status page is the first (Home page you see when you log into the SAMP. Itdisplays the name of the server and its physical location.

The following table provides a description of the fields.

Field DescriptionServer power Provides status of the server power.

• Normal: Component is operating in normal powerrange.

• Minor: A minor power alarm is present.• Major: A major power alarm is present.• Critical: A critical power alarm is present.

Servertemperature

Provides status of the server temperature.• Normal: Component is operating in normal

temperature range.• Minor: A minor temperature alarm is present.• Major: A major temperature alarm is present.• Critical: A critical temperature alarm is present.

Server status Provides status of the overall server.• Operational: Server is operational.• Non-Operational: Server is not operational.

System board Provides information on the system board sensors andcontrols.

• Present: Component exists in server.• Unknown: The status of the component could not

be determined.

SAMP Web pages


Field Description

• Absent: Component does not exist in server.• Normal: Component is operating in normal range.• Minor: A minor component alarm is present.• Major: A major component alarm is present.• Critical: A critical component alarm is present.

Cooling System Provides information on the fan sensors.• Present: Component exists in server.• Unknown: The status of the component could not

be determined.• Absent: Component does not exist in server.• Normal: Component is operating in normal range.• Minor: A minor component alarm is present.• Major: A major component alarm is present.• Critical: A critical component alarm is present.

Storage Array Provides information on the storage array• Present: Component exists in server.• Unknown: The status of the component could not


Power Supply 1 Provides information on the power supply.• Present: Component exists in server.• Unknown: The status of the component could not


Server Status field descriptions


Field DescriptionSAMP Provides information on SAMP alarms, sensors, and controls.



System Board field descriptionsYou access the System Board page from the main menu on the left under Components.

The top of the page provides information about the system board. The other sectionsprovide information on active component alarms and component sensors

Active alarms are present only when an active alarm is present for the component; that is, afault condition exists. Active alarms are usually triggered by sensors, for example, an overtemperature condition. Alarms have a

• Severity: Informational, Minor, Major, Critical.• Timestamp: An absolute time state, indicating the year, month, day, hour, minute,

and second when the alarm condition occurred.• Sensor that resulted in the alarm and the specific sensor condition that generated

the alarm.

Component sensors are sensors associated with the specific component. These sensorsmonitor the health of the component.

The following tables provide descriptions of the fields.

System board information

Field DescriptionSystem boardstatus

Provides information on the system board sensors andcontrols.


be determined.• Absent: Component does not exist in server.

SAMP Web pages


Field Description

• Normal: Operating in normal range.• Minor: A minor component alarm is present.• Major: A major component alarm is present.• Critical: A critical component alarm is present.

Manufacturer Name of the manufacturer of the server.

Product Version Product version of the server.

Part Number Part number of the server.

Serial Number Serial number of the server.

Active Component Alarms

Field DescriptionSeverity Provides the severity of the alarm.

• Minor: The severity of the alarm is minor.• Major: The severity of the alarm is major.• Critical: The severity of the alarm is critical.

Timestamp The timestamp when the alarm occurred.

Device Name of the device

Detail Description of the alarm, usually the name of the sensor thattriggered the alarm.

Component Sensors

Field DescriptionDescription Provides a short description of the component sensors.

Enabled Indicates if the component is enabled or not.

Event State Indicates whether the component exists or not.

Reading Provides a short description of what the sensor is displaying.

Entity Provides the name of the component.

Cooling system field descriptionsYou access the Cooling System page from the main menu on the left.

The top of the page provides information about the cooling system. The other sectionprovides information on component sensors.

Cooling system field descriptions




Cooling System Information

Field DescriptionCoolingsystemstatus

Provides information on the fan sensors.• Present: Component exists in server.• Unknown: The status of the component could not be

determined.• Absent: Component does not exist in server.• Normal: Component is operating in normal range.• Minor: A minor temperature alarm is present.• Major: A major temperature alarm is present.• Critical: A critical temperature alarm is present.

Component Sensors






Storage Array field descriptionsYou access the Storage Array page from the main menu on the left.

The top of the page provides information about the storage array. The other section providesinformation on component sensors.


SAMP Web pages



Storage array information

Field DescriptionDisk drive baystatus

Provides information on the system board sensors andcontrols.



Manufacturer Name of the manufacturer of the RAID controller.

Product Version Product version of the RAID controller.

Part Number Part number of the RAID controller.

Serial Number Serial number of the RAID controller.

Component Sensors






Power Supply field descriptionsYou access the Power Supply 1 page from the main menu on the left.

The top of the page provides information about the power supply. The other section providesinformation on component sensors


Power Supply field descriptions



Power supply information

Field DescriptionPower supplystatus

Provides information on the power supply sensors andcontrols.



Manufacturer Name of the manufacturer of the power supply.

Product Version Part number of the power supply.

Mfg Datetime Date when power supply was manufactured.

Part Number Part number of the power supply.

Serial Number Serial number of the power supply.

Component Sensors






SAMP field descriptionsYou access the SAMP page from the main menu on the left under Components.

The top of the page provides information about the SAMP. The other sections provideinformation on active component alarms and component sensors

SAMP Web pages


Active alarms are present only when an active alarm is present for the component; that is, afault condition exists. Active alarms are usually triggered by sensors, for example, an overtemperature condition. Alarms have a

• Severity: Informational, Minor, Major, Critical.• Timestamp: An absolute time state, indicating the year, month, day, hour, minute,

and second when the alarm condition occurred.• Sensor that resulted in the alarm and the specific sensor condition that generated

the alarm.


Component controls are controls associated with the specific component. Not allcomponents have controls.


SAMP information

Field DescriptionA + SAMP status Provides information on the SAMP sensors and controls.

• Present: Component exists in server.• Unknown: The status of the component could not be

determined.• Absent: Component does not exist in server.• Normal: Operating in normal range.• Minor: A minor component alarm is present.• Major: A major component alarm is present.• Critical: A critical component alarm is present.

Manufacturer Name of the manufacturer of the SAMP.

Serial Number Serial number of the SAMP.

Active Component Alarms





SAMP field descriptions


Field DescriptionDetail Description of the alarm, usually the name of the sensor that

triggered the alarm.

Component Sensors






INADS Alarm Suppression

Field DescriptionCurrent Status Indicates whether alarms to INADS are enabled or disabled.

New Setting The drop down menu provides choices from 15 minutes to 7 days.

Modem Dial-in

Field DescriptionCurrent Status Indicates whether the modem is enabled or disabled.

New Setting The drop down menu provides the following choices:• Disable Modem Dial-in• Enable Dial-in for one call• Enable Dial-in for unlimited calls

Component ControlsAvailable after clicking Advanced.

Field DescriptionDescription Provides a short description of the component controls.

Type Indicates whether analog, digital, or stream.• Analog—Can be set to a particular value• Digital—Turns on and off• Stream—Sets each individual bit

Mode–ModemAnswer

Indicates mode of operation for the modem.

SAMP Web pages


Field Description

• Auto—Auto answer is enabled (The modem isenabled for unlimited incoming calls)

• Manual—Auto answer is disabled (the modem isdisabled)

Mode–AlarmSuppression

Indicates mode of operation for alarming to INADS.• Auto—Alarms are enabled.• Manual—Alarm suppression is manually set to a value

(in minutes) that is shown in the state column.

State The state information is control type specific. In normal mode,the control states have descriptive states. In advanced mode,the states are in their raw, numeric form.

The following table provides a description of the buttons.

Button DescriptionSet Effects the New Settings changes.

Advanced Takes you to more data on sensors and controls.

Refresh Refreshes the page.

System field descriptionsYou access the System page from the main menu on the left under Components.

The top of the page provides information about the server. The other sections provideinformation on active system alarms and system sensors.


Server information

Field DescriptionServer power Provides information on the server power sensors and controls.

• Normal: Operating in normal range.• Minor: A minor power alarm is present.• Major: A major power alarm is present.• Critical: A critical power alarm is present.

System field descriptions


Field DescriptionServertemperature

Provides information on the server temperature sensors andcontrols.

• Normal: Operating in normal range.• Minor: A minor temperature alarm is present.• Major: A major temperature alarm is present.• Critical: A critical temperature alarm is present.

Server status Provides information on the server sensors and controls.• Operational: Server is operational.• Non-Operational: Server is not operational.

Asset Tag Asset tag number of the server.

Active System Alarms




Device Name of the component.

Detail Details about the failure.

System Sensors






System ControlsAvailable when you click Advanced.

Field DescriptionDescription Provides a short description of the component controls.

Type Indicates whether analog, digital, or stream.

SAMP Web pages


Field Description

• Analog—Can be set to a particular value• Digital—Turns on and off• Stream—Sets each individual bit

Mode Indicates mode of operation of a component.• Auto—The server and SAMP control the component. This

is the standard mode.• Manual—The values are manually overwritten

State The state information is control type specific (analog, digital,discrete, OEM). In normal mode, the control states havedescriptive states. In advanced mode, the states are in their raw,numeric form.

The following table provide descriptions of the buttons.

Button DescriptionAdvanced Takes you to more data on sensors and controls.


Power/Reset field descriptionsYou access the Power/Reset page from the main menu on the left under Resource Functions.

The top of the page provides information about the server. The other sections provideinformation on reset and shutdown actions, power actions, and system boot control.


Reset/Shutdown Actions

Field DescriptionWarm Reset Executes reboot on the host

Graceful Shutdown Executes halt on the host

Cold Reset Activates the server hardware reset signal

Power Actions

Field DescriptionPower Off Turns server power off

Power/Reset field descriptions


Field DescriptionPower Cycle Power cycles (off/on) the server power

System Boot Control

Field DescriptionDisable BootTimer

Disables the boot timer. Select this option when the boot timeris to be disabled. For example, when repopulating the disk for afull software installation or remaster of the hard drive.

The following table provides descriptions of the buttons.

Button DescriptionRequest Power Action Powers down or power cycles the system.

Request Boot Timer Action Disables the boot timer.

System Inventory Data field descriptionsYou access the System Inventory Data page from the main menu on the left under ResourceFunctions.

The page provides information about the server and all its components. The following tablesprovide descriptions of the fields. The expanded menu on the left allows you to view theinventory data as shipped.

Chassis Info

Field DescriptionAsset Tag Asset tag number of the server.

Product information: Avaya S8510

Field DescriptionManufacturer Name of the manufacturer of the server.


Board information: Augmentix A+ SAMP

Field DescriptionManufacturer Name of the manufacturer of the SAMP.

Product Version Product version of the SAMP.

Part Number Part number of the SAMP.

SAMP Web pages


Field DescriptionSerial Number Serial number of the SAMP.

Custom Information on memory and Avaya material code.

Custom MAC addresses for the host and Ethernet ports and IPaddresses for the Ethernet ports.

Board information: Motherboard

Field DescriptionManufacturer Name of the manufacturer of the motherboard.

Product Version Product version of the motherboard.

Part Number Part number of the motherboard.

Serial Number Serial number of the motherboard.

Custom BIOS version.

Custom MAC addresses for the first and second Ethernet interfaces(eth0 and eth1) of the motherboard on the server.

Board information: I/O Riser

Field DescriptionManufacturer Name of the manufacturer of the riser.

Product Version Product version of the riser.

Part Number Part number of the riser.

Serial Number Serial number of the riser.

Board information: Power Supply 1

Field DescriptionManufacturer Name of the manufacturer of the power supply.

Product Version Product version of the power supply.

Mfg Datetime Date when power supply was manufactured.



System Inventory Data field descriptions


System Inventory as Shipped field descriptionsYou access the System Inventory as Shipped page from the main menu on the left underOther Inventory Data.

The page provides information about the server and all its components as shipped. Thefollowing tables provide descriptions of the fields..

Product Info: Avaya S8510

Field DescriptionManufacturer Name of the manufacturer of the server


Board Info: Augmentix A+ SAMP

Field DescriptionManufacturer Name of the manufacturer of the SAMP board.

Product Version Product version of the SAMP board.

Mfg Datetime Date when SAMP board was manufactured

Part Number Part number of the SAMP board.

Serial Number Serial number of the SAMP board.

Product Version Version of the SAMP board.

Product Version Version of the firmware.

Custom MAC addresses for the host and Ethernet ports and IPaddresses for the Ethernet ports.

Board Info: Motherboard

Field DescriptionManufacturer Name of the manufacturer of the motherboard.

Product Version Version of the motherboard.

Part Number Part number of the motherboard.

Serial Number Serial number of the motherboard.

Custom BIOS version.

SAMP Web pages


Field DescriptionCustom MAC addresses for the motherboard

Board Info: I/O Riser

Field DescriptionManufacturer Name of the manufacturer of the riser.

Product Version Version of the riser.

Part Number Part number of the riser.

Serial Number Serial number of the riser.

Board information: Power Supply 1

Field DescriptionManufacturer Name of the manufacturer of the power supply.

Product Version Product version of the power supply.



Active Alarms field descriptionsYou access the Active Alarms page from the menu across the top.

The top of the page provides information about the server. The other section providesinformation on active alarms. The expanded menu on the left allows you to choose how tosort the information, display the information, and acknowledge the information.


Server information

Field DescriptionServer power Provides information on the server sensors and controls.

• Normal: Operating in normal range.• Minor: A minor power alarm is present.• Major: A major power alarm is present.• Critical: A critical power alarm is present.

Active Alarms field descriptions


Field DescriptionServer temperature Provides information on the server sensors and controls.

• Normal: Operating in normal range.• Minor: A minor temperature alarm is present.• Major: A major temperature alarm is present.• Critical: A critical temperature alarm is present.

Server status Provides information on the server sensors and controls.• Operational: Server is operational.• Non-Operational: Server is not operational.

Active Alarms

Field DescriptionTimestamp The timestamp when the alarm occurred.

Severity Provides the severity of the alarm.• Minor: The severity of the alarm is minor.• Major: The severity of the alarm is major.• Critical: The severity of the alarm is critical.


Detail Provides details about the failure.

The following table provides descriptions of the buttons

Button DescriptionAdvanced Takes you to more data on alarms.


Event Log field descriptionsYou access the Event Log page from the menu across the top.

The top of the page provides information about log types. The other section providesinformation about log entries. Clicking Advance at the bottom expands the menu on the left,allowing you to choose how to show the information, clear the log, reset the overflow.

SAMP Web pages



Select log type

Field DescriptionHardware EventLog

Where sensor events and failure conditions are logged.Entries in this log are related to the server hardware andthe various components monitored by the SAMP.

A+ SAMP SystemLog

The operating system log for the SAMP. Entries containedin this log are specific to the SAMP operating system andapplication software.

Log entries

Field DescriptionTimestamp The timestamp when the alarm occurred.

Severity Provides the severity of the alarm.• Minor: The severity of the alarm is minor.• Major: The severity of the alarm is major.• Critical: The severity of the alarm is critical.


Detail Provides details on the failure.

The following table provides descriptions of the buttons.

Button DescriptionDownload Allows you to download the contents of the log as a text file. You can

use it to save a copy of the Hardware Event Log or the SAMPSystem Log.

Advanced Takes you to more log entries.


Event Log field descriptions


SAMP Web pages


Chapter 3: SAMP commands

SAMP commandsSAMP commands are Linux commands that are used to administer the Server AvailabilityMaintenance Processor (SAMP) remote maintenance board. These commands provideserver information and help troubleshoot problems in the server and other components.Some of the commands may be run on either the server or the SAMP board itself or both.The commands are run using a Secure Shell (ssh) command line interface (CLI) applicationsuch as PuTTY.

The following table provides a list of commands that are used for SAMP administration andfrom which component they can be run.

Server and SAMP Server only SAMP only

almcall environment serverctrl

almclear inventory

almdisplay loadpwd

almenable rmbpasswd

almsuppress rmbuseradd

productid rmbuserdel

testinads rmbusermod

sampcmd

sampdiag

sampupdate

testmodem


almcallSyntax

almcall [-f first-number] [-a [y|n] ] [-s second-number] [-b [y|n] ] [-t [timer]][-i [interval]][-?]

almcall Display the administered information-f first-number Set the first number to dial out to first-number. The number can have

up to 30 digits (0-9), and "," for pause. Dashes are allowed but areignored.

-a [ y|n] Set alarm abbreviation on (y) or off (n) for the first telephone number.The default is y (almcall -a)

-s second-number

Set the second number to dial out to second-number. The number canhave up to 30 digits (0-9), and "," for pause. Dashes are allowed butare ignored.

-b [y|n] Set alarm abbreviation on (y) or off (n) for the second telephonenumber. The default is y (almcall -b).

-t [timer] Set the alarm abbreviation timer between 1 and 24 hours. The defaultvalue is 4 (almcall -t)

-i [interval] Set the interval between retries in minutes. The interval can bebetween 1 and 20 minutes. The default value is 7 minutes (almcall -i). The value 0 is ignored.

-? Display the command usage.

DescriptionUse almcall to display and set the telephone numbers to services, enable or disable alarmabbreviation on those numbers, and set the interval between retries.

ExampleTo run almcall directly on the remote maintenance board, enter

/opt/alarming/bin/almcall

SAMP commands


almclearSyntax

almclear [ -a ] [ -n [ id | id1, ids1,...idn | idn1-idn ]] [ -? ]

almclear Display the command usage. Arguments show when thecommand is executed on the server only.

-a Clear all outstanding server alarms.

-n id Clear a single server alarm with Alarm ID id

-n id1, id2, . . .idn

Clear a set of server alarms with Alarm ID numbers id1,id2,..idn. almclear -n 1, 2, 3, is valid. almclear -n 1 2 3 is not.

-n id1- idn Clear a range of server alarms from id number id1 to id numberidn.


DescriptionUse almclear to clear specific server alarms, a list of server alarms, or all server alarmswithin a range. An alarm is referenced by a positive integer, called its Alarm ID, which canbe found using the almdisplay command. almclear does not clear CommunicationManager alarms.

ExampleTo run almclear directly on the remote maintenance board, enter

/opt/alarming/bin/almclear

almdisplaySyntax

almdisplay [-v] [-? ]

almdisplay With no argument, displays the outstanding alarms.-v Display the outstanding alarms with an additional Description field. The

Description field displays the description contained in the original alarm string.This argument shows when the command is executed on the server only.

almclear



DescriptionUse almdisplay to display the list of outstanding messaging, Communication Manager,and server alarms.

ExampleTo run almdisplay directly on the remote maintenance board, enter

/opt/alarming/bin/almdisplayExample of the output for almdisplay

[root@]# almdisplayCommunicaMgr ALARMS====================ID MO Source On Brd Lvl Ack Date1 H323-SGRP 627 n MIN Y Wed Oct 31 08:18:49 MDT 20072 H323-SGRP 629 n MIN Y Wed Oct 31 08:18:45 MDT 20073 H323-SGRP 631 n MIN Y Wed Oct 31 08:18:39 MDT 20074 H323-SGRP 633 n MIN Y Wed Oct 31 08:18:35 MDT 20075 H323-SGRP 662 n MIN Y Wed Oct 31 08:18:29 MDT 20076 H323-SGRP 664 n MIN Y Wed Oct 31 08:14:13 MDT 20077 H323-SGRP 291 n MIN Y Wed Oct 31 08:14:09 MDT 20078 H323-SGRP 295 n MIN Y Wed Oct 31 08:14:05 MDT 20079 USD1-BD 06E15 n MIN Y Wed Oct 31 06:54:34 MDT 2007SERVER ALARMS=============ID Source EvtID Lvl Ack Date1839 CMG 46 MIN Y Wed Oct 31 08:35:58 MDT 20071838 CMG 46 MIN Y Wed Oct 31 08:28:51 MDT 20071837 CMG 46 MIN Y Wed Oct 31 08:05:11 MDT 20071836 CMG 46 MIN Y Wed Oct 31 07:58:04 MDT 20071835 CMG 46 MIN Y Wed Oct 31 07:34:24 MDT 20071834 CMG 46 MIN Y Wed Oct 31 07:27:22 MDT 20071834 CMG 46 MIN Y Wed Oct 31 07:25:50 MDT 2007

Field Description

ID Lists the unique Alarm ID assigned to each alarm

MO Name of the Maintenance Object that was alarmed

Source Displays the abbreviated name of the source which generatedthe alarm

On Brd Displays y if the problem is on-board, n if the problem is off-board

EvtID Displays the Event ID of the alarm. The Event ID identifies aparticular event that occurred on a given source that generatedthe alarm.

SAMP commands


Field Description

Lvl The severity level of the alarm: Warning (WRN), Minor (MIN), orMajor (MAJ)

Ack Displays Y or N, indicating if the alarm has been acknowledgedby INADS or not.

Date The time stamp assigned when the alarm was created.

almenableSyntax

almenable [-d [n|f|b]] [-s [y|n]] [-?]

almenable With no argument, display the administered information.-d n Set dial out alarm origination to neither (default). Disable alarming dialout.

Alarm origination does not occur, reports are not sent to either OSS number.

-d f First number only: use only the first dial out number for alarming.

-d b Both numbers: use both dial out phone numbers for alarming.

-s[ y|n] Enable (y) or disable (n) alarming through SNMP When executed on the SAMP,the default is n. When executed on the server, the default is y.


DescriptionUse almenable to enable or disable dial-out and SNMP alarm origination.

ExampleTo run almenable directly on the remote maintenance board (MPC), enter

/opt/alarming/bin/almenable.

almsuppressSyntax

almsuppress [-s [y|n]] [-t [minutes]] [-?]

almenable


almsuppress With no argument, display the status of current alarm suppression.-s [y|n] Suppress (y) or unsuppress (n) alarm origination for 30 minutes. The default

is y.

-t [minutes] Number of minutes to suppress alarm origination, where minutes is in therange of 30-120. The default is 30 minutes.

-? Display command option descriptions.

DescriptionUse almsuppress to suppress or unsuppress alarm origination or to check the state ofalarm suppression. Used by the craft login to stop alarms during troubleshooting operations.

ExampleTo run almsuppress directly on the remote maintenance board, enter

/opt/alarming/bin/almsuppress.

environmentSyntax

environment [-v] [-?]

environment With no argument, display the environment information.-v Turn on verbose output.

-? Display the help message.

DescriptionUse environment to see reports for environmental sensors such as temperature, fan speed,and voltage.

Example of the output for environment

*** Hardware Health ***Feature Value StatusMB Processor VTT PresentMB +1.5V PG PresentMB +1.8V PG PresentMB +3.3V PG PresentMB +5V PG PresentCMOS Battery NormalROMB Battery DisabledSys Exp +1.5V PXH PG PresentSys Exp +5V Riser PG PresentMB Backplane PG PresentMB Linear PG Present

SAMP commands


MB +0.9V PG PresentCPU 1 Present PresentCPU 1 VCORE PG PresentCPU 1 Thermal Trip NormalCPU 1 Throttled Normal...

inventorySyntax

inventory [-v]

inventory With no argument, display inventory of components.-v Use -v to see the detailed (verbose) information.

DescriptionUse inventory to

• see the remote maintenance board (SAMP) manufacturing information• verify that the remote maintenance board (SAMP) is connected and working correctly

Example of output for inventory

> inventory306 Avaya S8510 Chassis Information Asset Tag is 5000000000306 Avaya S8510 Product Information Product is Avaya S8510306 Avaya S8510 Product Information Manufactured by Avaya306 Avaya S8510 Product Information Serial Number is Service Tag JXSNPQ1306 Avaya S8510 Board Information Product is Augmentix A+SAMP306 Avaya S8510 Board Information Manufactured by DELL306 Avaya S8510 Board Information Product Version is FRU18Z.DELL P/N306 Avaya S8510 Board Information Part Number is OTT740A00306 Avaya S8510 Board Information Serial Number is CN687026CC00131306 Avaya S8510 Board Information File ID is 0

inventory


loadpwdSyntax

loadpwd [-c directory] [-o file] [ -l file] [-i] [-f] [-?]

-c directory The path to the directory that contains the passwd.conf and group.conffiles. These files have the same format as /etc/group and /etc/passwd. Theydescribe the attributes logins added by this command will have. Default is /etc/asg

-o file Path to the output file. Default is /etc/asg/asgfile.

-l file Path to the authentication file to be loaded. Default is the newest file in /var/home/ftp/pub.

-i Ignore the config file if the login already exists. By default, logins in theauthentication file that already exist on the system are changed so theymatch what is in the passwd. conf and group.conf files. This optionoverrides this behavior.

-f Force the new authentication file to load even if product IDs do not match.-? Display this help message.

DescriptionUse loadpwd to run a command-line version of the utility to load the Avaya authenticationfile (password file) onto the host server, standby server, LSP, or remote maintenance board(SAMP).

productidSyntax

productid [-p productid] [-m productid] [-r productid] [-?]

productid With no arguments, display Product ID of this server.-p productid Set this server’s Product ID to productid. The productid is a 10-digit

number that starts with "1". This is the only argument that shows when thecommand is executed on the SAMP.

-m productid Set the Messaging identification number to productid. The productid is a 10-digit number that starts with "2". This argument shows when the commandis executed on the server only.

SAMP commands


-r productid Set the Remote Maintenance Board (SAMP) identification number toproductid. The productid is a 10-digit number that starts with "5". Thisargument shows when the command is executed on the server only.

-? Display the command option descriptions.

DescriptionUse productid to view or set the Product ID for Communication Manager, Messagingproducts, or the Remote Maintenance Board for alarms.

ExampleTo run productid directly on the remote maintenance board, enter

sudo /opt/alarming/bin/productid

rmbpasswdSyntax

rmbpasswd [ -f passwd] name

-f passwd name Force encryption of the password. name is the login name for which thepassword is being changed.

DescriptionUse rmbpasswd to change passwords for remote maintenance board (SAMP) logins.

rmbuseraddSyntax

rmbuseradd [-d home][-p passwd ][-P [y|n]][-s shell][-u uid [-o]] name

-d home Identify a home directory for a particular login on the remote maintenanceboard. Default is home/login where login is the unique user name.

-p passwd Set the login password to passwd. Use this only on automated scripts. Thismust be an encrypted password as returned by the crypt system call.

-P [y|n] Specify that the login is used for establishing a PPP session through themodem. Default is n (nonmodem access).

rmbpasswd


-s shell Identify the login shell to use. If not used, the system uses the /bin/sh default.

-u uid name Specify a unique user login ID. If not used, the system assigns the nextavailable user ID. name is the login name for which the password is beingadded.

-o Create a duplicate User ID.

DescriptionUse rmbuseradd to add remote and local modem and user logins on the remotemaintenance board.

rmbuserdelSyntax

rmbuserdel nameDescriptionUse rmbuserdel name to delete existing customer-created logins on the remotemaintenance board. Craft and rasaccess logins cannot be deleted with rmbuserdel.

rmbusermodSyntax

rmbusermod [-d home][-p passwd ] [-P [y|n]][-s shell][-u uid [-o]][-l new_name] name

-d home Identify a home directory for a particular login on the remote maintenanceboard. Default is home/login where login is the unique user name.

-p passwd Set the login password to passwd. Use this only on automated scripts. Thismust be an encrypted password as returned by the crypt system call.

-P [ y|n] Specify that the login is used for establishing a PPP session through themodem. Default is n (nonmodem access).

-s shell Identify the login shell to use. If not used, the system uses the /bin/sh default.

-u uid Specify a unique user login ID. If not used, the system assigns the nextavailable user ID. name is the login name for which the password is beingmodified.

SAMP commands


-o Create a duplicate User ID.

-l new_name Change login name to a new name.

DescriptionUse rmbusermod to modify existing logins on the remote maintenance board.

sampcmdSyntax

sampcmd [cmd]

sampcmd Logs you into the remote maintenance board.

cmd Executes the command on the remote maintenance board without logging you in.

DescriptionUse sampcmd to

• log into the remote maintenance board• run a command on the remote maintenance board from the host.

ExampleTo run a command on the remote maintenance board from the host, enter sampcmd andanother command. For example, enter sampcmd date to see the date reported by theremote maintenance board.

sampdiagSyntax

sampdiag [-v]

sampcmd


-v Turn on verbose mode.

DescriptionUse sampdiag to

• test the communication path to the remote maintenance board (SAMP)• perform simple repairs on the server-to-rmb internal connection.

Example of the output for sampdiag

chintan-8500: sampdiag -vThe SAMP is using the Avaya IP address.SAMP HW address: 00:0F:29:00:01:5CSAMP IPaddress: 192.11.13.2HOST IPaddress: 192.11.13.1SSH port: 10022SSH OKHPI OKSAMP OKThe following fields appear on the sampdiag screen:

Field Description

SAMP HW address Shows if a remote maintenance board (rmb) wasdetected. If not HWaddress was detected, either theecs.conf file is incorrect or the rmb is not working.

SAMP IPaddress • If the IP address cannot be determined, check forproblems with the remote maintenance board.

• If the IP address is similar to 10.221.248.1(or .2),then an administration step was skipped or failedwhen the host software was installed. Verify thatthe remote maintenance board software is themost current.

HOST IPaddress If the IP addresses are similar to 10.221.248.1(or .2),then an administration step was skipped or failed whenthe host software was installed. Verify that the remotemaintenance board software is the most current.

SSHHPI

Shows the configuration of HPI and SSH. If both fail andthe IP address is reported, the host software may havebeen administered incorrectly.

SAMP commands


sampupdateSyntax

sampupdate [FWfile]

sampupdate Update the SAMP software with the update file in the FTP directory specifiedin ecs.conf

sampupdate FWfile Update the SAMP software with the specified file FWfile.

DescriptionUse sampupdate FWfile to update the firmware on the remote maintenance board(SAMP, MPC). The FWfile is the firmware image located in the /var/home/ftp/pub directory.No FWfile is needed if there is only one file in the directory.

serverctrlSyntax

serverctrl [-f][-r resourceID]

serverctrl power [on|off|cycle]

serverctrl reset [warm|cold]

serverctrl shutdown

serverctrl boot timer [enable|disable|stop]

serverctrl boot load [default|loadname]

serverctrl [-?]

serverctrl Display status information-f Force operation, stopping boot timer if it is running.-r resourceIDpower [on|off|cycle] Power on/off/cycle the server.reset [warm|cold] Reset the server (warm or cold).shutdown Shutdown the server.

sampupdate


boot timer [enable|disable|stop] Enable/disable/stop the boot timer.

boot load [default|loadname] Boot using the default or specified load.-? Display command option descriptions.

DescriptionUse serverctrl to see the status of the boot timer on the SAMP.

Use serverctrl boot timer disable to disable the boot timer on the SAMP whenthe server is shut down. Disable the boot timer to prevent the SAMP from rebooting theserver during server installation or remastering the hard drive.

Example of the output for serverctrl

craft@STA04310083:~$ serverctrlPower OnServer OperationalReset DeassertedBoot Timer Disabledcraft@STA04310083:~$Example of the output for serverctrl boot timer disable

craft@STA04310083:~$ serverctrl boot timer disableOK

testinadsSyntax

testinadsDescriptionUse testinads to test the connectivity between the system and INADS. testinadsgenerates a test alarm, sends it to INADS, and waits for a response. No command optionsare required.

ExampleTo run testinads directly on the remote maintenance board (SAMP), enter

sudo /opt/alarming/bin/testinads

SAMP commands


testmodemSyntax

testmodem [-s] [-l][-t reset_[usb|handshake|offhook|looparound]] [-?]

testmodem Perform the handshake and offhook tests.

-s Perform the handshake and offhook tests.

-l Perform the handshake, offhook, and looparound test to INADS.

-t reset_usb Reset the modem.

-t handshake Run the handshake test.

-t offhook Run the offhook test.

-t looparound Run only the looparound test.

-? Display command option descriptions.

DescriptionThe testmodem command provides the ability to reset the modem and perform offhook,handshake, and looparound tests. The looparound test dials out to INADS and waits for aresponse.

Example of the output for testmodem

craft> testmodemTEST RESULT DESCRIPTION---- ------ ------------handshake PASSoffhook PASS

Field Description

Test Lists the test being performed.

Result Lists the results of the test. Options are PASS or FAIL or ABORT.

Description If the test fails, displays a description of the failure.

testmodem


SAMP commands


Chapter 4: SAMP Procedures

SAMP proceduresThis section describes common procedures that you might use when working with theServer Availability Management Processor (SAMP). Procedures include:

• Connecting to SAMP remotely using the Web

• Connecting directly to the server

• Disabling boot timer using CLI

• Copying files to the server

• Upgrading SAMP firmware

Connecting to SAMP remotely using the WebYou can use any computer to connect to the SAMP through the network. The securitysettings on the LAN must allow remote access.

1. Open the Internet Explorer Web browser.

2. In the address field, enter https://IPaddress:10443, where IPaddress is the IPaddress of the SAMP you want to access.

3. Log in as craft or dadmin.

Setting Web browser optionsYou can use any Web browser that supports cascading style sheets and Javascript toremotely access the SAMP.

A connection session to a server might time out when connected through a proxy server. Toavoid having the server time out during a session, add the server host names or IP


addresses to the list of host names and IP addresses in your browser. Here are instructionswhen using Internet Explorer 6.0. Your browser or version may differ slightly.

1. In Internet Explorer 6.0, click Tools > Internet Options.

2. Select the Connection tab.

3. Click on LAN settings, then Advanced.

4. In the Do not use proxy server for addresses beginning with field, type the IPaddress for each server you intend to access remotely.If the IP addresses have the first or first and second octets the same, you canshorten the addresses to xxx.xxx.* (example, 135.9.*).

5. Click OK to close each dialog box.

Connecting to SAMP directly using the WebPrerequisitesOn the computer used to access the SAMP board directly, you must set your Web browseroptions to disable the proxy settings.

You use a laptop to connect to the SAMP board directly.

1. Plug one end of a CAT5 crossover cable into the Services access port on theSAMP board and plug the other end of the cable into the NIC on the laptop.


3. In the address field, enter https://192.11.13.6:10443.


Connecting directly to the serverPrerequisitesMake sure that you have a Secure Shell (SSH) application such as PuTTY installed on yourcomputer.

SAMP Procedures


1. Connect a crossover cable from the laptop to the Services port on either theSAMP or the server.

2. Start an SSH session.

3. In the Host Name (or IP Address) field, type 192.11.13.64. In the Protocol area, click SSH.

5. In the Port field, type 100226. Click Open.

Note:The system displays the PutTTY Security Alert window the first time youconnect to the SAMP with this version of PuTTY.

7. Click Yes to accept the server's host key and display the PuTTY window.


9. When done, type Exit and press Enter to close PuTTY.

Connecting remotely to the SAMP using a modemPrerequisitesMake sure that your modem is configured correctly and that you are using a computer with aLinux operating system.

1. Open a shell command within Linux.

2. Type connect2 -p modem telephone number -1 login -c loginpassword -t product type -R RAS access password and press Enter.For example, connect2 -p 3035557142 -1 craft -c mycraft -t850SMP -R rasaccessThe system dials into the modem, establishes a PPP connection, and respondswith the following message.

Note extra lines at the topAttempting to connect via Existing IP Connection...NOTE: SAMP browser is https:10.29.10.21:10443Open another window on this machine and connect the desired tool to

Connecting remotely to the SAMP using a modem


Address 10.29.10.21When you are finished with your connection, come back to this window and press Enter to manually shut it down.

Next stepsSee Using the Web interface through the modem on page 48 for using the Web interfaceand Using SSH through the modem on page 48 for using SSH for Linux commands.

Using the Web interface through the modemPrerequisitesMake sure you are connected through the modem. See Connecting remotely to the SAMPusing a modem on page 47.


2. In the Address field, type https://10.29.10.21:10443.

3. When done, log off to end the session.

Using SSH through the modemPrerequisitesMake sure you are connected through the modem. See Connecting remotely to the SAMPusing a modem on page 47.

If using the Linux OS shell, use the following procedures. If you want to use PuTTY, see Connecting directly to the server on page 46 but use the actual IP address of the SAMP.

1. Create a shell window.

2. At the shell prompt, type ssh –p 10022 [email protected].

3. At prompt for the password, type in the password.

4. When done, type Exit to end the session.

SAMP Procedures


Disabling boot timer using CLIPrerequisitesYou must connect to the services port on the Server Availability Management Processor(SAMP). Use a Secure Shell (SSH) application to access the SAMP.

The boot timer must be disabled if booting from the CD or DVD as part of an installation orupgrade. Otherwise, the SAMP could reboot the server and interrupt the installation orupgrade. For an initial installation, the server is shipped with the boot timer disabled. But foran upgrade, you must disable it manually.

1. Connect a crossover cable from the Services laptop to the Services port on theSAMP.

2. Log into the SAMP from the SSH application.

3. Type serverctrl boot timer disable and press Enter.The server responds with OK.

4. Type serverctrl and press Enter.The server responds with the following message:

Power OnServer Not Operational (or Server Operational depending on the state of the server)Reset DeassertedBoot Timer Disabled

You do not need to enable the boot timer after the installation or upgrade as the serversoftware enables the boot timer automatically when it reboots.

Disabling boot timer using Web interfacePrerequisitesYou must connect to the services port on the Server Availability Management Processor(SAMP). Use a Web browser to access the SAMP Web interface.

The boot timer must be disabled if booting from the CD or DVD as part of an installation orupgrade. Otherwise, the SAMP could reboot the server and interrupt the installation orupgrade. For an initial installation, the server is shipped with the boot timer disabled. But foran upgrade, you must disable it manually.

Disabling boot timer using CLI


1. Connect a crossover cable from the Services laptop to the Services port on theSAMP.

2. Log into the SAMP from the Web Interface.

3. On the menu on the left, under Resource Functions, click Power/Reset.

4. Scroll down to the Boot Timer Actions section, and select Disable Boot Timer.

5. Click Request Boot Timer Action.

You do not need to enable the boot timer after the installation or upgrade as the serversoftware enables the boot timer automatically when it reboots.

Copying files to serverPrerequisitesYou must download the files from Avaya Support before copying them to the server. Youmust be logged into the server using the Maintenance Web Interface.

1. Under Miscellaneous, click Download Files.

2. Select File(s) to download from the machine I’m using to connect to theserver.

3. Click Browse next to the top field to open the Choose File dialog box and find thefirmware that you downloaded and saved to a local directory.

4. Click Download to copy the file(s) to the server.The files are automatically copied to the correct directory.

Next stepsYou must install the SAMP firmware on the server.

SAMP Procedures


Determining SAMP firmware versionPrerequisitesYou must use Secure Shell (SSH) to access the server.

Note:Perform this procedure from the server.

1. Connect a crossover cable from the laptop to the Services port on the server.

2. Start an SSH session

3. Type sampcmd samp-update status and press Enter.

4. Check the Version ID: field for the firmware version. See the following example:

craft@dellV3_dlw> sampcmd samp-update statusSerial Number: SMI07373523Version ID: AVAYA_S8510_2_2_3Boot type: committedActive Kernel/Root: 1/5Committed Kernel/Root: 1/5U-Boot boot command: run k1r5;run netboot

Next stepsCheck the Avaya Support Web site to locate the current firmware version available.

Downloading SAMP firmware from Avaya SupportYou must first download the firmware image files to a staging area before copying them tothe server.

1. In a Web browser Location or Address field, type http://support.avaya.com toaccess the Avaya Support Web site.

2. Select Downloads then select S from Download by Product Name and selectS8500–Series Server. Alternatively, type SAMP firmware in the Search box to geta list of firmware versions. Scroll down until you see the latest SAMP firmwareversion listed for your server.

Determining SAMP firmware version


3. Find the firmware version that you want. Unless otherwise instructed, select thelatest version.Be sure to read the ReadMe file for the firmware version before downloading theimage file.

4. Click the image filename.

5. Select Save this file to disk in a convenient directory on your computer.

6. Write down the full path to the file's location; you need this information later.

Next stepsYou must copy the firmware image file from your computer to the server before installing it.

Upgrading SAMP firmwarePrerequisitesYou must copy the firmware files to the server before upgrading the SAMP firmware. Youmust use Secure Shell (SSH) and a command line interface to access the server.

1. Start an SSH session.


3. Type sampupdate filename where filename is the firmware image and pressEnter.If the upgrade is run while connected directly to the server, the system displaysthe following message:

Upgrade of the SAMP has begun. This may take several minutes. Please be patient.If the upgrade is run while connected through the SAMP (modem or SAMPservices port), the system displays the following message:

Upgrade of the SAMP has begun. Because you are logged in via the SAMP, your connection will be lost during the upgrade. Do not interact with the SAMP during the upgrade process (about 15-20 minutes). If you experience any problems, you may check the status of the upgrade by viewing the log file in the /var/log/ecs directory.For example, sampupdate_2005-12-05-155106.log where 2005 is the year, 12 isthe month, 05 is the day, and 155106 is the hour, minute, and second.

4. Type sampdiag -v and press Enter to verify the SAMP is performing properly.

SAMP Procedures


5. Type sampcmd samp-update status and press Enter to verify that the newfirmware load installed successfully.

6. If you experienced problems in the last two steps, review the log file in the /var/log/ecs directory.

Upgrading SAMP firmware


SAMP Procedures


Index

A

active alarms Web page .............................................25almcall ........................................................................30almclear ......................................................................31almdisplay ..................................................................31almenable ...................................................................33almsuppress ...............................................................33

C

connect directly to SAMP ...........................................46connect remotely to SAMP .........................................45cooling system Web page ..........................................13copying files to server .................................................50

D

determine SAMP firmware version .............................51direct connection ........................................................46disabling boot timer

CLI .......................................................................49Web Interface .......................................................49

disk drive ....................................................................14downloading SAMP firmware .....................................51

E

environment ................................................................34event log Web page ...................................................26

I

inventory .....................................................................35

L

legal notices .................................................................2loadpwd ......................................................................36login ..............................................................................9logout ...........................................................................9

M

modem .........................................................................7modem connection ...............................................47, 48

SSH ......................................................................48

Web interface .......................................................48

N

notices, legal ................................................................2

P

power supply Web page .............................................15power/reset Web page ...............................................21productid .....................................................................36

R

remote connection ......................................................47rmbpasswd .................................................................37rmbuseradd ................................................................37rmbuserdel .................................................................38rmbusermod ...............................................................38

S

SAMP commands .......................................................29SAMP connections .......................................................5SAMP connectivity .......................................................6SAMP overview ............................................................5SAMP software ............................................................6SAMP Web interface ....................................................9SAMP Web page ........................................................16sampcmd ....................................................................39sampdiag ....................................................................39sampupdate ................................................................41Server Availability Management Processor .................5server status ...............................................................10serverctrl .....................................................................41status

overall system health ...........................................10component ...........................................................10

storage array Web page .............................................14system board Web page ............................................12system inventory data as shipped Web page .............24system inventory data Web page ...............................22system Web page .......................................................19

T

testinads .....................................................................42testmodem ..................................................................43


Uupgrading SAMP firmware .........................................52

W

Web browser settings .................................................45

Index


Server Availability Management Processor (SAMP): Avaya ...

Documents

Transcript of Server Availability Management Processor (SAMP): Avaya ...