Avaya Server Available Management Processor

8/7/2019 Avaya Server Available Management Processor

http://slidepdf.com/reader/full/avaya-server-available-management-processor 1/62

Using the Avaya Server AvailabilityManagement Processor (SAMP)

03-300322Issue 4

February 2007



© 2007 Avaya Inc.All Rights Reserved.

Notice

While reasonable efforts were made to ensure that the information in thisdocument was complete and accurate at the time of printing, Avaya Inc. canassume no liability for any errors. Changes and corrections to the informationin this document may be incorporated in future releases.

For full suport information, please see the complete document,Avaya Support Notices for Software Documentation , document number03-600758.

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

the search box.

Documentation disclaimer

Avaya Inc. is not responsible for any modifications, additions, or deletions tothe original published version of this documentation unless such modifications,additions, or deletions were performed by Avaya. Customer and/or End Useragree to indemnify and hold harmless Avaya, Avaya's agents, servants andemployees against all claims, lawsuits, demands and judgments arising out of,or in connection with, subsequent modifications, additions or deletions to thisdocumentation to the extent made by the Customer or End User.

Link disclaimer

Avaya Inc. is not responsible for the contents or reliability of any linked Websites referenced elsewhere within this documentation, and Avaya does notnecessarily endorse the products, services, or information described or offeredwithin them. We cannot guarantee that these links will work all of the time andwe have no control over the availability of the linked pages.

Warranty

Avaya Inc. provides a limited warranty on this product. Refer to your salesagreement to establish the terms of the limited warranty. In addition, Avaya’sstandard warranty language, as well as information regarding support for thisproduct, while under warranty, is available through the following Web site:http://www.avaya.com/support.

Copyright

Except where expressly stated otherwise, the Product is protected by copyrightand other laws respecting proprietary rights. Unauthorized reproduction,transfer, and or use can be a criminal, as well as a civil, offense under theapplicable law.

Avaya support

Avaya provides a telephone number for you to use to report problems or to askquestions about your product. The support telephone numberis 1-800-242-2121 in the United States. For additional support telephonenumbers, see the Avaya Web site: http://www.avaya.com/support.

http://www.avaya.com/support


http://www.avaya.com/support/

http://www.avaya.com/support/





Issue 4 February 2007 3

Chapter 1: Using the Avaya Server Availability Management Processor . . . . . . . 5

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Web browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Determining the latest firmware version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Upgrading the SAMP firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Downloading new firmware from the support website to the staging area . . . . . . . . . . 7

Accessing the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Copying and installing SAMP firmware to the server . . . . . . . . . . . . . . . . . . . . . 9

Verifying the internal link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Password protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Login commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Login administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Common options for login commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SAMP commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

SAMP commands run on the host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

sampdiag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Detecting the SAMP card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Testing the internal LAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Testing the SAMP through ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Testing HPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Testing NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Rebooting the SAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Connecting and logging in to the SAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Local connections through a web browser . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Local connections through ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Remote connections through ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Remote connections through a web browser . . . . . . . . . . . . . . . . . . . . . . . . . 25

Connecting and logging in remotely to the server . . . . . . . . . . . . . . . . . . . . . . . . . 26

Navigating on the SAMP web pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Home window layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Viewing system health summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Inventory data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Logging off the SAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents



Contents

4 Using the Avaya Server Availability Management Processor (SAMP)

Chapter 2: Server Availability Management Processor tasks . . . . . . . . . . . . . 33

SAMP control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Server power and restart activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Power off enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Power/Reset Control window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Performing SAMP tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Disabling the boot timeout using Linux commands . . . . . . . . . . . . . . . . . . . . . . 40

Disabling the boot timeout using the SAMP Web page . . . . . . . . . . . . . . . . . . . 41

Monitoring the server using the SAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 3: Alarms, Event Log, and Sensors. . . . . . . . . . . . . . . . . . . . . . . 49

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Viewing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Clearing alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Alarm suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Viewing the event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61




Chapter 1: Using the Avaya Server AvailabilityManagement Processor

Overview

The Avaya Server Availability Management Processor (SAMP) card is installed in PCI-X slot 1of the server. Administration of the SAMP is accomplished through the SAMP Web interfaceusing a browser or through server administration commands.

The following are highlights of the features of the SAMP:

● Monitors the health of the server hardware including fan speed, voltages, and temperature

● Reports server hardware failure and other alarms to INADS by modem

● Provides remote server power-on and reset (soft and hard) capability

● Provides remote access dial-in connection to the SAMP and the server

● Provides local laptop access to the SAMP (and subsequently to the server)

The SAMP is powered externally. This ensures continued working of the SAMP even when theserver looses its power.

Web browser requirementsYou can use any Web browser that supports cascading style sheets and Javascript to remotelyaccess the SAMP:

Note:

Note: The values in all windows shown in this book are examples. Your settings will bedifferent.

Note:

Note: If a Web browser does not work, try a different browser.



Using the Avaya Server Availability Management Processor


Determining the latest firmware version

Note:

Note: Perform this procedure from the server.

To determine the firmload load on your server:

1. From the server, open a command line (for example, ssh).

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

The system displays a window similar to the following.

Serial Number: STA04310079

Version ID: AVAYA_S8500_2_1_SP2

Boot type: committed

Active Kernel/Root: 1/5Committed Kernel/Root: 1/5

U-Boot boot command: run k1r5;run netboot

3. Check the Version ID line for the latest firmware load on the server.

4. On a Web browser, go to http://support.avaya.com.

The system displays the Avaya Support window.

5. Go to the Avaya Support Website (http://support.avaya.com). Follow the Software &Firmware Downloads link and subsequent links.

6. Locate the SAMP firmware update and check the version number against what is on yourSAMP.

Upgrading the SAMP firmware

Note:

Note: Perform this procedure from the server.

On occasion new firmware becomes available for the SAMP. These firmware upgrades can

include:● security patches

● bug fixes

● new features

http://support.avaya.com/

http://support.avaya%2C.com/

http://support.avaya.com/






New firmware is available at the Avaya Support Website where you can copy the files to thecomputer used to access the server (for example, the Services laptop).

Downloading new firmware from the support website to the

staging area

! CAUTION:

CAUTION: Make sure that you want to upgrade the SAMP firmware before you initiate theupgrade. Once you have successfully installed the new firmware onto yourSAMP, you cannot cancel the upgrade.

To upgrade the SAMP firmware you first must download the firmware image files to a stagingarea, then copy them to the server.

1. Go to the Avaya Support Website (http://support.avaya.com). Follow the Software &Firmware Downloads link and subsequent links.

2. Find the section for the firmware vintage you want. Unless otherwise instructed, choose thehighest vintage.

3. Be sure to read that vintage’s ReadMe file before downloading the image file(s).

4. For each image file to be downloaded:

a. Click on the image filename.

b. Save this file to disk in a convenient directory.

c. Write down the full path to the firmware image. You need this information later.

5. Go to Copying and installing SAMP firmware to the server on page 9 to copy and install the

firmware.







Accessing the server

To access the server using a Web browser:

1. If on site, connect to the Services port on the server.

If off site, log into the server using the IP address of the server or the modem (PPP).

2. Open a Web browser.

3. If connected to the Services port on the media server, type http://192.11.13.6 in theAddress field. Press Enter to bring up the logon Web page.

If connected through the network, type in the server name or IP address of the server.

4. Log in as craft.

5. When asked whether to suppress alarms, click Yes.

The system displays the Home window.

6. Click Launch Maintenance Web Interface to get to the Main Menu.





Copying and installing SAMP firmware to the server

! CAUTION:

CAUTION: Make sure that you want to upgrade the SAMP firmware before you initiate the

upgrade. Once you have successfully upgraded the SAMP, you cannot reversethe upgrade.

To copy the firmware to the server:

1. On the Web browser, under Miscellaneous, click Download Files.

The system displays the Download Files window.

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

3. Click Browse next to the top field to open the Choose File screen on your computer. Findthe firmware that you downloaded from the Avaya Support Website and was saved to yourlocal staging area directory in Downloading new firmware from the support website to the

staging area on page 7.4. Click Download to copy the file(s) to the server.

5. Ssh to the server and log in as craft.

6. Type sampupdate filename where filename is the firmware image located in the /var/ home/ftp/pub directory and press Enter. If there is only one file in the directory, the filenameis not necessary.

If the upgrade is run while connected directly to the server, the system displays the followingmessage:

Upgrade of the SAMP has begun. This may take several minutes. Pleasebe patient.

If the upgrade is run while connected through the SAMP (modem or SAMP services port),the system displays the following message:

Upgrade of the SAMP has begun. Because you are logged in via theSAMP, your connection will be lost during the upgrade. Do notinteract with the SAMP during the upgrade process (about 15-20minutes). If you experience any problems, you may check the statusof the upgrade by viewing the log file in the /var/log/ecsdirectory.

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.

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

8. Type sampcmd samp-update status and press Enter verify that the new firmware loadinstalled successfully.

9. If you experience problems in steps 7 or 8, review the log file in the /var/log/ecs directory.





Verifying the internal link

It is possible to verify the address of the SAMP by pinging the suspected address. However, ifthat address is not the same as what the internal Ethernet port is configured as, the ping will fail.

For example, if the internal Ethernet of the server is configured as 192.11.13.1 and the SAMP isconfigured as 10.221.248.1, the command will fail because the server and SAMP are not on thesame network. Consequently, the server network firmware will not attempt to send the pingdown the internal interface.

To verify the internal link between the SAMP and the server:

1. Open a Telnet or ssh session to the server.

2. Log in as craft.

3. Type sampdiag -v where v means verbose (more information will be printed on thescreen) and press Enter.

4. Look at the system response to determine if the SAMP is communicating.

Password protection

The SAMP’s default configuration includes two logins - craft and rasaccess. Prior to loadingRemote Feature Access’ (RFAs) authentication file; these may be used by either AvayaServices or BusinessPartners. The remote access (rasaccess) password is used whenaccessing the SAMP via the modem to establish a PPP session.

Upon installing the RFA authentication file, the S8500B’s default static passwords are changedautomatically for security reasons. Services personnel should be aware that the rasaccesspassword changes every time an authentication file is loaded. Since the process relies on theAutomatic Registration Tool (ART) to manually train Avaya’s connect tool when the rasaccesspassword has been changed, it is imperative that the technician rerun ART whenever a newauthentication is loaded.

BusinessPartners must create an alternate system login. The recommended system login isdadmin, with a password of the BusinessPartner’s choice. The BusinessPartner may choose tocreate a PPP login for themselves. They must be cautious about utilizing modem access,however, as doing so blocks product alarming and also blocks Avaya Services from remotelyfixing problems. If the BusinessPartner forgets to create logins or loses their login/password,

they will not be able to access the SAMP nor remotely access the S8500B. Upon request, theBusinessPartner’s login/password can be reset for a fee by Avaya’s Technical Consulting -System Support team (U.S.-based BusinessPartners at 1-800-225-7585) or Regional ServiceCenters (non-U.S.).



Login commands


Login commands

This section discusses only the login commands.

All commands are entered from the host (the S8500B Media Server), not the SAMP.

The SAMP login name can contain upper or lower case letters, numbers, or a combination ofupper or lower case letters and numbers. However, the length of the password cannot exceed12 characters and the first character cannot be a number.

! CAUTION:

CAUTION: Be careful when changing passwords.

! CAUTION:

CAUTION: Do not change the craft or rasaccess passwords. If these are changed, a servicecall is necessary to reset the passwords.

Note:Note: You can use the -? option to display a command syntax for each command.

The remote maintenance board (RMB) commands

● loadpwd - loads the new authentication file onto the host server and the SAMP.

● rmbuseradd - adds modem and SAMP user logins on the SAMP (creates remote/locallogins).

● rmbusermod - changes existing logins on the SAMP (modifies existing logins).

● rmbuserdel - deletes logins from the SAMP (craft and rasaccess cannot be deleted by thiscommand).

● rmbpasswd - changes (modifies) passwords for SAMP logins.

Login administration

The SAMP login name can contain upper or lower case letters, numbers, or a combination ofupper or lower case letters and numbers. However, the length of the password cannot exceed12 characters and the first character cannot be a number.

You can use the following SAMP commands.

Remote (modem) logins

To create a remote login for use over a modem:

1. On the host, type rmbuseradd -P y login where login is the unique login name andpress Enter.





2. Type rmbpasswd login where login is the unique login name and press Enter.

The system responds with Enter password.

3. Type the new password and press Enter.

The system responds with Re-enter the password.

4. Type the new password again and press Enter.

Local logins (SAMP login)

To create a local login for use on the SAMP:

1. On the host, type rmbuseradd login where login is the unique login name and pressEnter.

2. Type rmbpasswd login where login is the unique login name and press Enter.

The system responds with Enter password.


The system responds with Re-enter the password.


Changing a local login to a remote login

To change a local login to a remote login:

1. On the host, type rmbusermod -P y login where login is the unique login name andpress Enter.

Changing a remote login to a local login

To change a remote login to a local login:

1. On the host, type rmbusermod -P n login where login is the unique login name andpress Enter.

Removing a login from the SAMP

To remove a login from the SAMP:

1. On the host, type rmbuserdel login where login is the unique login name and press

Enter.



SAMP commands


Common options for login commands

All commands to administer logins on the SAMP have options. These options include:

● [-u uid] - specifies a unique user ID (login ID). This option can be used on rmbuseradd or

rmbusermod commands. If this option is not used, the system assigns the next availableUID.

● [-o] - creates a user ID that is already in the system (for example, two users with the sameUID). This option can be used on rmbuseradd or rmbusermod commands.

● [-d home] - this is the home directory for a particular login on the SAMP. The default is / home/ login where login is the unique user name. This option can be used onrmbuseradd or rmbusermod commands.

● [-s shell] - this is the login shell you want to use. This option can be used on rmbuseradd and rmbusermod commands. If this option is not used, the system default of /bin/sh isused.

Note:

Note: The next option must be an encrypted password as returned by the crypt systemcall and should only be used by automated scripts. To manually add/change apassword, use the rmbpasswd command.

● [-p passwd] - This option sets the login password to passwd . This option can be used onrmbuseradd and rmbusermod commands.

● [-P y/n] - specifies that the login is used for establishing a PPP session through themodem. This option can be used on rmbuseradd and rmbusermod commands. If thisoption is not used, the system assigns the default of n (non-modem access).

For example, to add a login to the SAMP that lets you log in to the host through the modem

on the SAMP, type rmbuseradd -P y login where login is the unique user name, y isconnect through the modem. Press Enter.

SAMP commands

SAMP commands affect alarms, environment, product ID, and so forth. There are twocategories of SAMP commands. Some are run from the server and some are run by logging intothe SAMP. The ones that have the same names do similar things with similar syntax.

To get assistance on the host for a particular command:

● Type info command where command is one of the below listed commands and pressEnter.





SAMP commands run on the host

These commands are run on the host. They affect both how the host is administered and alsohow the SAMP is administered (assuming the server can communicate with the SAMP).

● almcall - This command displays and sets the dial-up numbers on the modem for placingalarms.

● testinads - This command generates a test alarm and sends it to INADS so the phonenumber administration can be exercised.

● testmodem - This command tests the connection to the SAMP modem and exercises thecommunication path to the modem.

● almenable - This command turns alarming on and off.

● almsuppress - This command disables alarms while the user is logged in.

● almdisplay - This command displays outstanding host alarms.

● productid - This command sets the product ID for alarms.

● environment - This command displays the environment sensors such as temperature, fanspeed, and voltage values.

● date - This command displays or changes the clock. For more information on this option,type man date.

● sampcmd - This command logs into the SAMP or runs a command on the SAMP. If thiscommand is followed by an argument (a command) on the host, it elicits a response fromthe SAMP. For example, sampcmd date. Press Enter requests the time from the SAMPto display.

● sampdiag - This command tests the communication path to the SAMP and performs

simple repairs on the ’host to samp’ internal connection.

● sampupdate - This command updates the firmware on the SAMP.

● inventory - This command displays the manufacturing information on the SAMP andverifies the SAMP is connected and working correctly.



Troubleshooting


Configuration

The alarm service relies on configuration information to determine dial-out properties and alarmencoding of events. The configuration information is stored in the local configuration databaseon the SAMP.

Upon initial loading, the alarm service reads the configuration information from the localconfiguration database. The alarm service supports the following configuration parameters:

● Product ID

● Alarm prefix for SAMP

● Dial-out Enable state

● Time interval between retries

● Dial-out properties for OSS including phone number, alarm abbreviations, and enablestate

● Alarm notification states● Event encoding entries

Any configuration changes such as disabling dial-out support, takes effect immediately after theSAMP receives the new configuration information. If a call is in process when the configurationis updated, the in-process call completes before the new configuration is applied.

Troubleshooting

All communication between host and the SAMP are via an internal, dedicated LAN. Three majorchannels (ports) are used in that LAN for host to SAMP firmware communications. The SAMPforwards traffic on all other channels between its Services port or modem connection and thehost. The three channels are for:

● ssh sessions (logging into the SAMP)

● HPI traffic (environment and control traffic)

● NTP (time updates)

The way to determine if the SAMP is working is to see if any of these channels is working. If anyone is and another is not, the problem is with the channel that is not working. If none is working,

the problem is with the SAMP or the internal LAN.





sampdiag

The place to start is to test the internal LAN. As user craft in a command line shell on thehost, run the sampdiag -v command. If you see the following example

server1>: sampdiag -vThe SAMP is using the Avaya IP address.

SAMP HWaddress: 00:0F:29:00:01:5C

SAMP IPaddress: 192.11.13.2

HOST IPaddress: 192.11.13.1

SSH port: 10022

SSH OK

HPI OK

SAMP OK

then everything is configured correctly and working.The sampdiag command tries to fix the internal LAN configuration. If there was a problem inhow the host internal LAN was configured, sampdiag may have fixed the problem. After amoment. You can run sampdiag –v again and see if the SAMP is fully operational.

There are several things to look for in the response from sampdiag.

● The HWaddress line tells you if a SAMP was detected where the host configuration saysthat it is (eth2 or eth4). If no HWaddress was detected, either the ecs.conf file is incorrector the SAMP is not working.

● If the IPaddresses are similar to 10.221.248.1 (or .2), the host was not configured properlywhen host software was installed or the SAMP firmware needs to be updated.

● This command will test HPI and ssh configuration for you. If both are failing, but the IPaddress is reported, the host firmware is probably not set up correctly.

● If sampdiag cannot determine the IP address, there could be a problem with the SAMP,itself.

● HPI failing indicates the SAMP firmware probably is not up to date.

The next sections are tests targeted at specific components in the SAMP communication path.



Troubleshooting


Detecting the SAMP card

To determine if SAMP card is present:

1. Type grep SampEth /etc/opt/ecs/ecs.conf and press Enter.

The system responds with

SampEth eth4

SampEth is a ecs.conf variable entry that is set to eth2 or eth4 if the system detects theSAMP card. If the system does not detect SAMP card, the entry shows:

SampEth none

Testing the internal LAN

Run the ifconfig eth2 command (without the dual NIC) or ifconfig eth4 (with the dualNIC). The results should look something like:

eth2 Link encap:Ethernet HWaddr 00:0F:29:00:01:5C

inet addr:192.11.13.1 Bcast:192.11.13.3 Mask:255.255.255.252

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:86930 errors:0 dropped:0 overruns:0 frame:0

TX packets:89315 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:100

RX bytes:10273485 (9.7 Mb) TX bytes:15627789 (14.9 Mb)

Interrupt:11 Base address:0x3000 Memory:d0220000-d0220038

The things to look for are:

● The inet addr should be 192.11.13.1.

If it is 10.221.248.2, the host was not configured properly when software was installed or theSAMP firmware needs to be updated.

● Both RX packets and TX packets should be non-zero. If RX packets is 0, the SAMP is notsending anything to the host. This is may indicate that the SAMP should be replaced.





Testing the SAMP through ssh

As user craft, enter the sampcmd command from a command line. If the SAMP is working, thefirst time this is done, you will be asked to add a security key. Answer yes. After the SAMP andhost exchange keys and if everything is working, you will see something like the following:

.

.M

.MM _ _

.MM M | (_)

.MM M | |_ _ __ _ ___ __

MMM MMMMMMM | | | '_ \| | | \ \/ /

MMM M | | | | | | |_| |> <

MMMM M |_|_|_| |_|\__,_/_/\_\

BusyBox v1.00-pre10 (2005.03.09-16:48+0000) Built-in shell (ash)

Enter 'help' for a list of built-in commands.

craft@STA04310083:~$

This is a Linux banner and prompt from the SAMP.

Enter exit to log out of the SAMP.

If you do not see the above, run the sampdiag -v command to diagnose the SAMP.

Testing HPI

There are several ways to test if the HPI (Hardware Platform Interface) is working, select theone most convenient for your situation:

● As user craft, from a command line, enter the inventory command. If everything isworking, you will see something like

server1>: inventory

306 Avaya S8500B Chassis information Asset Tag is 5000000000

306 Avaya S8500B Board Information Product is Server AvailabilityManagement Card

306 Avaya S8500B Board Information Manufactured by AugmentixCorporation

306 Avaya S8500B Board Information Product Version is Avaya 2.1



Troubleshooting


306 Avaya S8500B Board Information Manufactured on2004-08-10T11:30:50-06:00

306 Avaya S8500B Board Information Part Number is 10321 REV.B00

306 Avaya S8500B Board Information Serial Number is STA04310079

306 Avaya S8500B Board Information Product Version is AVAYA_S8500_2_1_SP2

306 Avaya S8500B Board Information Product Version is INP Firmware AVAYA11.20 Jul 11 2006

306 Avaya S8500B Board Information Custom is MAC host00:0F:29:00:01:74

306 Avaya S8500B Board Information Custom is MAC eth000:0F:29:00:01:75



● From the Maintenance Web pages, select Temperature/Voltage. If everything is working,

you will see a page like





● If you do not see anything like the above, log in with administrator privileges to a commandline. Enter the /opt/desahpi/bin/hpisensorscommand. If everything is working,you should see something like

server1>: /opt/desahpi/bin/hpisensors

Opened Session to Domain 1

Resource 306 Avaya S8500B

Sens Num EvtState Reading IdString

-------- -------- -------------------- --------

1 0x0001 PCI Reset

2 0x0000 3.344 PCI +3.3V

3 0x0007 2.672 PCI +3.3V Aux

4 0x0000 5.073 PCI +5V

5 0x0000 11.776 PCI +12V

6 0x0000 -11.992 PCI -12V

7 0x0000 12.096 Ext A 12V

9 0x0000 35 Samp Temp

10 0x0001 Samp +3.3V Fail

50 0x0002 Server Power On51 0x0001 System Reset

101 0x0000 2.59098 MB +2.5V

102 0x0000 3.33486 MB +3.3V

103 0x0000 5.0778 MB +5V

104 0x0000 1.52295 MB +1.5V

105 0x0000 11.875 MB +12V

106 0x0000 34 PCI Area Temp

107 0x0000 32 Memory Area Temp

108 0x0000 45 CPU Diode Temp

110 0x0000 10306 Fan Tach 1

111 0x0000 8655 Fan Tach 2

112 0x0000 8767 Fan Tach 3

113 0x0000 8941 Fan Tach 4

201 0x0000 0 Alarm Total

202 0x0000 0 Alarm Retries

203 0x0000 0 Alarms Active

204 0x0000 Modem Status

258 0x0000 Aggregate Temp

257 0x0000 Aggregate Power

256 0x0000 Operational Status

● Finally, from a command line, run the ps –C bridgeip command. You should see aresponse like

server1>: ps -C bridgeipPID TTY TIME CMD

317 ? 00:00:00 bridgeip



Connecting and logging in to the SAMP


Testing NTP

The SAMP tries to get the date and time from the host once an hour. The date may be offimmediately after installation is complete, but should be synchronized after the next SAMPreboot or within the hour.

It is difficult to directly test that NTP is working. If the first test (testing ssh) worked, then as usercraft, run the sampcmd date command. You should see something like

server1>: sampcmd date

Fri Apr 8 08:19:34 MDT 2005

Where the response is the same time and date as the host. If this is not working, NTP is not setup correctly.

Rebooting the SAMP

To reboot the SAMP as craft login:

● On the server, type sampcmd sudo reboot and press Enter.

The SAMP then reboots and is unavailable for about a minute.


Note:

Note: To access the SAMP using ssh or the SAMP Web interface, you must log into theSAMP.





Local connections through a web browser

To use the Web interface to locally connect and log in to the SAMP:

1. Connect the services laptop to the Ethernet port 2 on the SAMP using a crossover cable.

2. Open an Web browser window.

Note:

Note: For the following step, the command syntax starts with https:, not http:

3. In the Address field, type https://192.11.13.6:10443 and press Enter.

The system displays the Log In window.

4. In the User Name field, type craft or another login with Web permissions.





5. In the Password field, type the server password for craft (or the password the user uses tolog in) and click Log In.

The system displays the Home window. This is an example from the S8500B Media Server.

From the Web pages, you can:

● Look at the state of the server environment (temperature, voltage, fans)

● Look at any alarms that have been generated by the SAMP

● Control the server’s power





● Reboot the server

● Determine the health of the server

● (These can be done even if the server is powered down, as long as the SAMP has itsindependent power.)

Local connections through ssh

To use the ssh command to locally connect and log in to the SAMP:

1. Connect a crossover cable from the Services laptop into the Services port on the SAMP.

2. From a command window, type arp -d 192.11.13.6 and press Enter.

3. On the Services laptop, click on the Putty desktop link or select Start > Programs > PuTTY > PuTTY.

The system displays the PuTTY Configuration window.

4. In the Host Name (or IP address) field, type 192.11.13.6.

5. In the Protocol area, click SSH.

6. In the Port field, type 10022.

7. Click Open.

Note:

Note: The system displays the PuTTY Security Alert window the first time you connectto the SAMP with this version of PuTTY.

8. If this is the first time you that connect to the SAMP, click Yes to accept the server’s hostkey. Otherwise, go to step 9.

The system displays the PuTTY window.

9. Log in as craft.

The system prompt displays. For example, craft@STA04410179:~$

10. When done, type exit and press Enter.

Remote connections through ssh

Note:Note: Remote connections work the same as if the modem was connected to the

server.





To use ssh to remotely connect and log in to the SAMP:

1. On a command line interface (CLI), type connect2 -p modem telephone number -l login -c login password -t product type -R RAS access password and pressEnter.

For example, connect2 -p 3035557142 -1 craft -c mycraft -t 850SMP -R rasaccess

The system dials into the modem and establishes a PPP connection.

The system responds with:

Open another window on this machine, and connect the desired tool to

Address 10.7.9.2

When you are finished with your connection, come back to thiswindow, and press Enter to manually shut it down.

2. Open another CLI window.

3. Type ssh -p 10022 craft@address provided above and press Enter.

For example, ssh -p 10022 [email protected]. In the password, type the server password for craft and press Enter.



6. Go back to the first screen. Press Enter to close it.

Remote connections through a web browser

To use the Web interface to remotely connect and log in to the SAMP:1. On a command line interface (CLI), type connect2 -p modem telephone number -l login -c login password -t product type -R RAS access password and pressEnter.

For example, connect2 -p 3035557142 -1 craft -c mycraft -t 850SMP -R rasaccess

The system dials into the modem and establishes a PPP connection.


Open another window on this machine, and connect the desired tool to

Address 10.7.9.2

When you are finished with your connection, come back to thiswindow, and press Enter to manually shut it down.

2. Open a Web browser window.








5. In the Password field, type the server password for craft (or the password the user uses tolog in) and click Log In.


From the Web pages, you can:

● Look at the state of the server environment (temperature, voltage, fans)

● Look at any alarms that have been generated by the SAMP

● Control the server’s power

● Reboot the server

● Determine the health of the server

● (These can be done even if the server is powered down, as long as the SAMP has itsindependent power.)

Connecting and logging in remotely to the server

To remotely connect and log in to the server:

1. On a command line interface (CLI), type connect2 -p modem telephone number -l login -c login password -t product type -R RAS access password and pressEnter.

For example, connect2 -p 3035557142 -1 craft -c mycraft -t 850IPA -R rasaccess

The system dials into the modem and establishes a PPP connection and automatically logsyou in to the server.


Suppress alarm origination (y/n)?

2. Press Enter to suppress alarm origination.

The system responds with a Linux command line prompt containing the name of the server.For example, craft@server>




Navigating on the SAMP web pages


Navigating on the SAMP web pages

Home window layout

The Home window is divided into a navigation pane (on the left) and a display pane (in themiddle). This is an example from the S8500B Media Server.





Note:

Note: The above page may be different depending on what program the SAMP issupporting. The above page is supporting the Avaya S8500B server.

Note:

Note: The Overall System Health section probably is the most important area on this

window. This area tells you the status of the server when you log in.

Note:

Note: These pages do not refresh automatically. To refresh this window, use theRefresh functionality of your Web browser.

Table 1: Available resources on page 28 outlines the resource functions available in thenavigation pane.

Table 1: Available resources

Link Description

Components

System Board Provides information on system board sensors and controls.

Fans Provides information fan sensors.

Front Panel Provides information on front panel controls.

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

System Provides information on system alarms, sensors, and controls.

Resource Functions

Power/Reset Provides the remote power on, power cycle, and reset (warmand cold) capability on the server.

Inventory Data Data identifying this particular SAMP.When the server starts, the SAMP collects system data, andstores it in non-volatile memory.

Across the top

Home Home window

Alarms Shows information on the last active alarms.

Log Shows information on the last 100 events.

Log Out Use to terminate your SAMP session.



Viewing system health summary


Viewing system health summary

To view the system health of the server, select Home in the navigation pane. The followinginformation appears under the Overall System Health:

● temperature

● power

● operational status

The SAMP provides basic information on component performance when you logged on.





Inventory data

To see the inventory data:

1. On the Home window (if you are not on the Home window, click Home), click InventoryData.

The system displays the Inventory Data window.

The middle Product Version field contains the most important information on this window -the firmware version being run on the SAMP.



Logging off the SAMP


Logging off the SAMP

Use this option to log off the SAMP.

To log off the SAMP:

1. Click Log Out.

The system displays the Log In window because you have been logged out.








Chapter 2: Server Availability ManagementProcessor tasks

SAMP control

This section outlines the procedures needed to configure the SAMP.

Server power and restart activity

Use the Power / Reset option on the SAMP Web interface to:

● power-off the server

● restart the server

● enable and disable the boot timer option

Power off enabled

The Power Off Enabled window enables or disables the power controls. It provides a lock onthe power controls and can be used to prevent inadvertent power operations from occurring.



Server Availability Management Processor tasks


To set power off enabled:

1. On the Home window (if you are not on the Home window, click Home), click System.

The system displays the System Controls section.



SAMP control


The column headings for System Controls are:

a. Description - The components on the server

b. Type -

● Analog - can be set to a particular value

● Digital - turns on and off● Stream - sets each individual bit

c. Mode - The type of operation of the component

● Auto - standard

● Manual - overrides set values

d. State - The condition of the component at the time you are looking at this page

● On

● Off

2. Under System Controls, click Power Off Enabled.The system displays the Power Off Enabled window.

Table 2: Power Off Enabled window selections on page 35 outlines the selectioninformation available on this window.

Table 2: Power Off Enabled window selections

Description

Set Off Makes the Power Off control non-functional.

1 of 2





3. Click the appropriate selection.

Power/Reset Control window

The Power/Reset Control window:

● Turns the power off

● Resets the power

● Resets the boot timer

Set Auto Mode Returns the control to the default setting (which is On; itre-enables the power off control).

Refresh Provides an updated screen. The screen may changedepending on what has taken place in the last few minutes.

Table 2: Power Off Enabled window selections

Description

2 of 2





To reset power:

1. On the Home window (if you are not on the Home window, click Home), under ResourceFunctions, click Power/Reset.

The system displays the Power/Reset Control window.





Note:

Note: The buttons on this window appear depending on whether their associatedactions currently are usable. For example, if the power already is turned on,Power On does not appear. If the power is turned off, the Reset selections do notappear. If the power or reset controls are disabled, Power Off or Reset does notappear.

Table 3: Power/Reset Control window selections on page 38 outlines the selectioninformation available on this window.

2. Click the appropriate selection.

Resetting power

Use the Power/Reset Control window to reset power.

To reset power:

1. On the Home window (if you are not on the Home window, click Home), under ResourceFunctions, click Power/Reset.

Table 3: Power/Reset Control window selections

Description

Warm Reset Performs a graceful shutdown and restarts the operatingsystem.

Cold Reset Tells the server hardware to perform a not so graceful shutdownand restarts the operating system.

Power Off Performs a graceful shutdown and turns the power off.

Power On Turns the server power on.

Power Cycle Performs a graceful power off followed by a power on.

Disable Boot Timer Disables the operating system watchdog. Click if there areproblems booting the system.






2. Scroll down to the Power/Reset Control window.

For a description of the fields and selections in the Reset/Shutdown Actions section, seePower/Reset Control window on page 36.

3. In the Reset/Shutdown Actions section, click Warm Reset to reset the power.





Performing SAMP tasks

The Tasks section allows you to view the server power and restart activity, and to directlycontrol the server. Using the Server Power / Restart Control option, you can perform the

following functions:

● Disable the boot timeout using Linux commands

● Power on server immediately

● Power on server at a specified time

● Power off server immediately

● Shutdown O/S and then power off server

● Shutdown O/S and then power restart server

● Restart the server immediately

Disabling the boot timeout using Linux commands

If installing or upgrading server software from a CD or DVD requires booting from the CD orDVD, you must disable the boot timeout after booting into the CD or DVD. The SAMP couldreboot the media server, thereby interrupting the installation or upgrade.

It is not necessary to enable the boot timeout when you complete the install or upgrade. Theserver software enables the boot timeout when it boots.

To disable the boot timeout using Linux commands:

Note:Note: To use Linux commands, you must log in to the SAMP. For more information on

Web access, see Disabling the boot timeout using the SAMP Web page onpage 41.


2. From a command window, type arp -d 192.11.13.6 and press Enter.

3. On the Services laptop, click on the Putty desktop link or select Start > Programs > PuTTY > PuTTY.

The system displays the PuTTY Configuration window.

4. In the Host Name (or IP address) field, type 192.11.13.6.5. In the Protocol area, click SSH.





6. In the Port field, type 10022.

7. Click Open.

Note:

Note: The system displays the PuTTY Security Alert window the first time you connectto the SAMP with this version of PuTTY.

8. If this is the first time that you connect to the SAMP, click Yes to accept the server’s hostkey. Otherwise, go to step 9.

The system displays the PuTTY window.

9. Log in as craft.


10. At the prompt, type serverctrl boot timer disable and press Enter.

The system responds with an OK message.

11. Type serverctrl and press Enter.

Note:

Note: The system message should indicate that the boot timer is disabled.

The system responds with the following messages.

Power On

Server Not Operational (or Server Operational depending on the state of theserver)

Reset Deasserted

Boot Timer Disabled

Disabling the boot timeout using the SAMP Web page

If installing or upgrading server software from a CD or DVD requires booting from the CD orDVD, you must disable the boot timeout after booting into the CD or DVD. The SAMP couldreboot the media server thereby interrupting the installation or upgrade.

Note:

Note: Use this procedure if the S8500B or S8500C has Communication ManagerRelease 3.1 or later.





To disable the boot timeout using the SAMP Web pages:

Note:

Note: To access the SAMP using the Web interface, you must log in to the SAMP card.


2. From a command window, type arp -d 192.11.13.6 and press Enter.3. Start a Web browser.








6. In the Password field, type the appropriate password for the user and click Log In.






7. On the left, under Resource Functions, click Power/Reset.

The system displays the Power/Reset Control window.

8. Scroll down to the Boot Timer Actions section.



Monitoring the server using the SAMP


9. Select Disable Boot Timer.

10. Click Request Boot Timer Action.

It is not necessary to enable the boot timeout when the install or upgrade completes. Theserver software enables the boot timeout when it boots.


The following information can be found under various headings:

● In the navigation pane, under Components:

- Fans monitors the fan speed

- System Board and SAMP monitor voltages

- SAMP and System monitor temperature

● Event Logs:

- View the events recorded in the logs

- View the severity of the events

To view the information on the Component Sensors heading:

Note:

Note: For this procedure, the example is displaying the PCI +3.3V.





1. Click System Board.

The system displays the Component Sensors window.





2. In the Description column, click PCI +3.3V.

The system displays the PCI +3.3V window. This screen is very long; you need to scrolldown on the SAMP window to see the entire screen.





Note:

Note: In the above window, checking Enabled enables the reporting of this sensor byerror messages.




Chapter 3: Alarms, Event Log, and Sensors

Overview

This chapter cover alarms, the event log, and the Server Availability Management Processor(SAMP) sensors.

Alarms

Use this section to look at alarms and clear them.

Any sensor in an abnormal state may generate alarms. In some cases, these alarms generateINADS alarms.

The SAMP reports the following events as alarms to INADS:

● Host power loss

● Host unable to boot

● Host exhibiting rolling reboots. In this case, the host notifies the SAMP about its state andthe SAMP sends out an alarm

● If it detects boot failure after the following sequence:

●

Host fails to boot, SAMP initiates a hard reset● Host fails to boot, SAMP initiates a power cycle

● Host fails to boot, SAMP sends out an alarm

● Loss of external power to the SAMP

● Loss of heartbeat to the host



Alarms, Event Log, and Sensors


Viewing alarms

To view active alarms:

1. Click Alarms.

The system displays the Active Alarms window.

Table 4: Active Alarms window field descriptions on page 50 outlines the informationavailable on this window.

2. Click the entry under Detail for further information.

Table 4: Active Alarms window field descriptions

Description

Timestamp The day, hour, minute, and second when the event occurred.

Severity Critical, Major, Minor, or Informational

Device The host (for instance, SAMP)

Detail The component that created the event alarm. Click for furtherdetails.



Alarms


Clearing alarms

To clear alarms:

1. Click Alarms.

The system displays the Active Alarms window. In this example the bottom alarm has beenacknowledged, while the top alarm is New (this alarm has not been acknowledged at thistime). Notice the menu listing on the left has changed.

Table 5: Active Alarms window field descriptions on page 51 outlines the informationavailable on this window.


Description


Severity Indicates the level of the alarm

● Critical - indicates that the component being monitoredis no longer functioning well enough to do what it issupposed to do. Typically, this would mean that thesystem itself may not be able to continue to run unlessthe problem is fixed. However, that does not mean thatthe system is shutting down immediately. For example, afan that is not turning fast enough to move a usefulamount of air would have a critical alarm. But, until thesystem overheats, it will keep on running.

● Major - indicates a condition that needs attention but it isnot keeping the system from continuing to run.

● Minor - indicates a condition that may need attention.

1 of 2





2. To acknowledge this alarm, click New.

The system displays the Active Alarms window.

The word New means the alarm has not been acknowledged on the SAMP.

Note:

Note: After this alarm has been clicked, the word New disappears. However, this doesnot resolve the alarm.

Device The host (for instance SAMP).

Detail Shows the current state of the sensor that caused the alarm.


Description

2 of 2



Alarms


3. On the Active Alarms window, under Detail, click PCI +3.3V Aux.

The system displays the Avaya S8500B Sensor Details window and shows the currentstate of the sensor that caused the alarm. Notice the menu on the left now lists all sensors.This figure shows the upper portion of the details window.





This figure shows the lower portion of the details window.

4. Go back to the Active Alarms window.

5. Under Acknowledge, click All Alarms.

The alarm clears only if the condition is resolved.

However, this is not a permanent change. When the SAMP reboots, the settings revert totheir default values. There is no way to make changes permanent.



Alarms


Alarm suppression

Use this selection to turn off alarms while resolving system problems.

To set the alarm suppression:

1. On the Home window (if you are not on the Home window, click Home), click SAMP.

The system displays the A+SAMP window.





2. Under Component Controls, click Alarm Suppression.

The system displays the Alarm Suppression window.

Table 6: Alarm Suppression window selections on page 56 outlines the selectioninformation available on this window.

3. Make the appropriate selections and click Set Control.

Table 6: Alarm Suppression window selections

Description

Setting Changes the value in minutes for your system to suppressalarms during problem resolution.

Set Control Makes the Alarm Suppression control active.




Event Log


Event Log

Use this section to see what is happening in the system.

Viewing the event log

The sensors are the components being monitored. Any sensors reporting a reading outsidetheir threshold (out of their permissible range) creates an entry on the event log. The SAMPdoes not generate an alarm for these events. The events are sent to the host and the hostgenerates an alarm.

To view the Event Log:

1. On the Home window (if you are not on the Home window, click Home), click Log.

The system displays the Event Log window.

This window provides a list of the last 100 generated alarms.





Table 7: Event Log Entries window field descriptions on page 58 outlines the informationavailable on this window.

2. To see the details of a specific event, click on the icon to the left.

The system displays an Event Log Detail window.

Table 7: Event Log Entries window field descriptions

Description

Severity Indicates if the event is critical, major, minor, or informational.


Type Shows if a sensor has been enabled, disabled, or is a changedevent state.

Detail A more detailed description of the type of event.



Event Log


Table 8: Event Log Detail window field descriptions on page 59 outlines the informationavailable on this window.

Sensors

The SAMP monitors current temperature readings and threshold levels for various componentsof the host.

Table 8: Event Log Detail window field descriptions

Description

Severity Indicates if the event is critical, major, minor, or informational.

Event Type Shows if a sensor has been enabled, disabled, or is a changedevent state.

Event Id The number of the event.


Type A more detailed description of the type of event.






Index

Index

Aaccessing the server . . . . . . . . . . . . . . . . . 8adding

local logins . . . . . . . . . . . . . . . . . . . 12remote (modem) logins . . . . . . . . . . . . . .11

alarm service configuration . . . . . . . . . . . . . 15alarms . . . . . . . . . . . . . . . . . . . . . . 49

clearing . . . . . . . . . . . . . . . . . . . . 51suppression . . . . . . . . . . . . . . . . . . 55viewing. . . . . . . . . . . . . . . . . . . . . 50

B

boot timeoutdisabling with Linux commands . . . . . . . . . 40disabling with the Web page . . . . . . . . . . . 41

Cchanging

local login to remote login . . . . . . . . . . . . 12remote login to local login . . . . . . . . . . . . 12

clearingalarms . . . . . . . . . . . . . . . . . . . . . 51

commandscommon options for login . . . . . . . . . . . . 13login . . . . . . . . . . . . . . . . . . . . . . .11

run on the host . . . . . . . . . . . . . . . . . 14SAMP . . . . . . . . . . . . . . . . . . . . . 13

common options for login commands . . . . . . . . 13configuring the SAMP . . . . . . . . . . . . . . . 33connecting to the SAMP . . . . . . . . . . . . . . 21

Ddetecting SAMP card. . . . . . . . . . . . . . . . 17disable

boot timeout with Linux commands. . . . . . . . 40boot timeout with the Web page . . . . . . . . . 41

disablingpower . . . . . . . . . . . . . . . . . . . . . 33

Downloading new firmware from the support websiteto the staging area . . . . . . . . . . . . . . . . . 7

Eenabling

power . . . . . . . . . . . . . . . . . . . . . 33event log

viewing . . . . . . . . . . . . . . . . . . . . . 57

Ffirmware

copying and installing . . . . . . . . . . . . . . . 9upgrading . . . . . . . . . . . . . . . . . . . . . 6

firmware versiondetermining latest . . . . . . . . . . . . . . . . . 6

Hhome pane layout . . . . . . . . . . . . . . . . . 27

Iinternal link

verifying . . . . . . . . . . . . . . . . . . . . 10inventory data . . . . . . . . . . . . . . . . . . . 30

L

local connections to the SAMP through a web browser 22local connections to the SAMP through ssh . . . . . 24local connections to the SAMP using PuTTY . . . . . 24logging in to the SAMP . . . . . . . . . . . . . . . 21logging in to the SAMP locally through a web browser 22logging in to the SAMP locally through ssh . . . . . . 24logging in to the SAMP locally using PuTTY . . . . . 24logging in to the SAMP remotely through ssh . . . . . 24logging in to the SAMP remotely through the browser . 25Logging off . . . . . . . . . . . . . . . . . . . . . 31logging off the SAMP . . . . . . . . . . . . . . . . 31login administration . . . . . . . . . . . . . . . . . 11login commands . . . . . . . . . . . . . . . . . . 11logins

changing local login to remote login. . . . . . . . 12changing remote login to local login. . . . . . . . 12local . . . . . . . . . . . . . . . . . . . . . . 12remote (modem) . . . . . . . . . . . . . . . . 11removing from SAMP . . . . . . . . . . . . . . 12



Index

MMonitoring the server using the SAMP. . . . . . . . 45

N

navigation pane layout . . . . . . . . . . . . . . . 27

Ppassword protection . . . . . . . . . . . . . . . . 10power

disabling . . . . . . . . . . . . . . . . . . . . 33enabling . . . . . . . . . . . . . . . . . . . . 33resetting . . . . . . . . . . . . . . . . . . . 36, 38turning off . . . . . . . . . . . . . . . . . . . 36turning on . . . . . . . . . . . . . . . . . . . 36

Power Off Enabled window . . . . . . . . . . . . . 33Power/Reset Control window . . . . . . . . . . . . 36PuTTY

using to log in to the SAMP locally . . . . . . . . 24

Rrebooting the SAMP . . . . . . . . . . . . . . . . 21remote connections to the SAMP through ssh . . . . 24remote connections to the SAMP through the browser 25removing

login from SAMP . . . . . . . . . . . . . . . . 12resetting power . . . . . . . . . . . . . . . . . 36, 38restart activity . . . . . . . . . . . . . . . . . . . 33RSA tasks

performing . . . . . . . . . . . . . . . . . . . 40

SSAMP

configuring . . . . . . . . . . . . . . . . . . . 33connecting to . . . . . . . . . . . . . . . . . . 21logging in . . . . . . . . . . . . . . . . . . . 21logging of . . . . . . . . . . . . . . . . . . . 31monitoring the server . . . . . . . . . . . . . . 45rebooting. . . . . . . . . . . . . . . . . . . . 21

SAMP commands . . . . . . . . . . . . . . . . . 13SAMP commands run on the host . . . . . . . . . . 14sensors . . . . . . . . . . . . . . . . . . . . . . 59server

connecting to remotely . . . . . . . . . . . . . 26logging in to remotely . . . . . . . . . . . . . . 26

server power . . . . . . . . . . . . . . . . . . . 33

Ttesting HPI . . . . . . . . . . . . . . . . . . . . . 18testing internal LAN . . . . . . . . . . . . . . . . . 17testing NTP . . . . . . . . . . . . . . . . . . . . 21testing SAMP through ssh. . . . . . . . . . . . . . 18

testing the internal LAN . . . . . . . . . . . . . . . 16troubleshooting. . . . . . . . . . . . . . . . . . . 15

detecting SAMP card . . . . . . . . . . . . . . 17testing HPI . . . . . . . . . . . . . . . . . . . 18testing internal LAN . . . . . . . . . . . . . 16, 17testing NTP . . . . . . . . . . . . . . . . . . . 21testing SAMP through ssh . . . . . . . . . . . . 18

Vviewing

event log . . . . . . . . . . . . . . . . . . . . 57viewing alarms . . . . . . . . . . . . . . . . . . . 50vital product data

performing RSA tasks . . . . . . . . . . . . . . 40

WWeb browser requirements . . . . . . . . . . . . . . 5window

Power Off Enabled . . . . . . . . . . . . . . . 33Power/Reset Control . . . . . . . . . . . . . . 36

Documents

Avaya Server Available Management Processor