Home

Embedded Support Partner User Guide

1. ror 912 Internal controller has encount ered a firmware breakpoint 89 7 Internal controller is in the h ung state 896 A debug dump exists on this sys tem 807 A Debug Dump exists on this sys tem 806 Configuration on disk import fa iled 805 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 345 Chapter 10 Default Event Classes and Types 346 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 WWW CO CO Ww W w WWW CO CO 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 rAr 0 iO CO 108 Configuration on disk access er ror 803 Configuration invalid 802 Request Sense 702 Back end fibre dead 644 Back end SCSI bus dead 642 Channel failed 640 Automatic reboot count has chan ged 518 Lost connection to server or s erver is down 517 Size table full 513 Mirror Race on critical drive 428 Mirror Race recovery failed 4 27 Controller is using default non unique world wide name 426 Controller boot ROM image needs to be reloaded 425 Killed partner 423
2. 1 Channel initialization error x1500 Fibre channel link errors cont nue 0x1206 Fibre channel driver detect rror during initialization 2 Cu C23 C3 C 3C X ran Fibre channel driver detect rror after initialization 0x12 Fibre channel TPRLO reset recei ved 0x1203 Fibre channel TGT reset receiv d 0x1202 Fibre channel LIP reset receiv d 0x1201 Unknown interrupt 0x1104 Host bus reset received 0x1103 Host bus reset asserted 0x1102 SRC driver detected exception o n SCSI chip 0x1101 Destination driver successfully issued reassign blocks command 373 Chapter 10 Default Event Classes and Types 374 81 81 81 81 81 81 81 81 81 81 81 81 81 83 83 83 83 83 83 83 83 83 83 83 83 83 84 84 84 84 84 3352 3351 3390 3349 3348 3347 3346 3345 3344 3343 3342 3341 3340 3726 3725 3724 3723 3722 3721 3720 3719 3718 Sg 3716 3715 3677 3687 3686 3685 3684 3683 0x1014 Destination driver level 0 diag nostic failed 0x1013 Destination driver error 0x101 2 Chip error 0x1011 Bus parity error on controller 0x100F Unexpected interrupt on control ler 0x100 Timeout on drive side of cont ller 0x100 Hardware error on drive side controller 0x10 Start of day error in destin on driver 0x10 Controller memory parity err 0x10 Unsu
3. BBU out of service 418 Hard ECC error corrected 415 Soft ECC error corrected 414 BBU battery not present 410 WARM BOOT failed 406 BBU removed 405 Controller firmware mismatch 404 Controller s partner is gone c ontroller is in failover mode n ow 399 Controller is gone System is d isconnecting from this controll er 395 BBU Power OK 394 BBU Power Low 393 Controller is gone System is d isconnecting from this controll er 391 Controller is found 390 Controller has been reset 389 Controller is dead System is d Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 3107 3106 3105 3104 3103 3102 3101 3100 3099 3098 3097 3096 3095 3094 3093 3092 3091 3090 3089 3088 3087 3086 isconnecting from this controll er 388 Internal log structures getting full PLEASE SHUTDOWN AND RESE I THE SYSTEM IN THE NEAR FUTUR
4. 3202 3201 3200 199 198 197 196 WWW CO 99 195 3191 3190 3185 3184 BBU reconditioning is finished 401 BBU reconditioning is started 400 Controller is gone System is d isconnecting from this controll er 398 Controller is online 397 Controller powered on 396 BBU Present 392 Array management server softwar started successfully 384 Enclosure services ready 334 Enclosure access has been resto red 331 ormal temperature has been res tored 328 Power supply has been restored 324 Fan has been restored 321 Uninterruptible power supply no rmal 311 Storage Works enclosure reporte d normal state 306 Storage Works enclosure reporte d critical state 305 Normal temperature has been res tored 290 Power supply has been restored 273 Fan has been restored 257 Logical drive background initia lization restarted 179 Logical drive background initia lization paused 178 Attempt to read data from block that is marked in Bad Data Tab le 158 System drive type changed 155 System drive size changed 154 Expand Capacity completed l51 Expand Capacity started 150 Z uu oo0 0 z Zz Oo Zz zu 0 9 0 0 Zz zi Oo ESP for the IRIX OS 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
5. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes 333 Chapter 10 Default Event Classes and Types 334 49 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 47 48 50 50 51 51 51 51 1771 1772 1773 1774 VETS 1776 1777 1778 1779 1780 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 2100 2101 2102 2103 2104 2105 pn Sat_pn_start without existing s at_pn Allocated more memory than clea red Root device not available Bad prom swap Could not allocate nbufs Reconfigure nbufs and reboot Frame scheduler inavlid recove ry mode Frame scheduler invalid intr s ource fire Frame scheduler invalid intr s ource reset Frame scheduler invalid attr Could not allocate job for proc 0 Biophysio Failed userdma Invalid information label add Invalid label add Preemption with no valid rsa Runable no rsa 1 Runable no rsa 2 Illegal request to yield Rbid set for nid but no rsa Dyield nid bad rsa Illegal dyield call Table inconsistent with relocat ion entries 1 Table inconsistent with relocat ion entries 2 Symbol not found Paging daemon not running Swap allocation overflow M
6. 1752 1753 1754 1755 1756 1757 1758 1359 3010 1760 1761 1762 1763 1764 1765 1766 1770 mload strstub no symbol table mload strstub not ELF format mload strstub unreadable mload strstub init failed mload strstub no queue 2 Probe DMA failed SCHED hits bad color Callouts allocation failed vnode set EATTR failed kmem zone too small Select device no setting PD flush error nfs3 chunkcommit bad vop Frame scheduler slave FRS not found Frame scheduler invalid state during interrupt Frame scheduler illegal dispat ch state Frame scheduler invalid dispat ch state Frame scheduler invalid new at tr R4K badaddr for K2 impacting pe rformance Process killed errno Process killed limit exceeded Process killed lock stack Process killed grow stack Process trapped but signal hel d or ignored R4K badaddr for KO impacting pe rformance Tlbmiss 1 invalid badaddr Process core dump Trap on CPU R4K badaddr for K2 wired impact ing performance R4K badaddr for K2 impacting ke rn performance Tlbmiss 2 invalid badaddr Tlbmis User invalid badaddr Too many BADVA Process referenced bad addr Unknown branch instruction Sat_pn_start with existing sat_ Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
7. 3085 3084 3083 3082 3081 3080 3079 3078 3077 3076 3075 3074 3073 3072 3071 3070 3069 3068 3067 3066 3065 3064 3063 Temperature is above 50 degrees Celsius 289 Over temperature Temperature i s above 70 degrees Celsius 28 8 Storage cabinet power supply is not present 275 Power supply failure 274 Power supply failure 272 Storage cabinet fan is not pres ent 259 Fan failure 258 Fan failure 256 Logical drive background initia lization completed 181 Logical drive background initia lization failed 180 Logical drive background initia lization stopped 177 Logical drive background initia lization started 176 A standby rebuild has started o n logical drive 162 Temporary Offline RAIDO 1 RAID1 RAIDO JBOD array is available to the user again 161 Temporary Offline RAID5 RAID3 a rray is available to the user a gain with the possibility of da ta in the array 160 Data for Disk Block has been 1o st due to Logical Drive problem 159 System drive LUN mapping has be en written to config 157 Bad data blocks found Possible data loss 156 Bad Blocks found 153 Expand Capacity stopped with er ror 152 Logical drive initialization fa iled 147 Rebuild stopped because logical drive failed 143 Rebuild stopped with error New Yes Yes Yes Yes Yes Yes Yes Yes Yes
8. 5A lum 59 omp 58 tar 57 0 56 ied 367 Chapter 10 Default Event Classes and Types 368 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 34 34 34 34 34 34 34 34 34 34 98 97 96 95 94 93 92 91 90 89 88 87 86 85 SS 78 77 76 75 created or deleted Hot spare capacity not sufficie nt for all drives 0x2253 0x224F Wrong drive removed replaced 0 RE removed RE deleted RE failed or hot spare drive Drive marked optimal edia scan scrub resumed 0x2 edia scan scrub stopped 0x2 Unknown drive marked unassigned Unassigned drive with no DACSTO Unassigned drive with no DACSTO Unassigned drive with no DACSTO DACSTORE created for unassigned x224C 246 245 0x2244 0x2243 0x2242 0x2241 0x2240 0x223E Unassigned drive replac d 0x22 3D Failed Replaced drive marked r placed Drive marked deleted Hot spare drive assigned intern ally Drive added in previously unuse d slot 0x223B 0x223A 0x2239 0x2238 Replaced drive completed recons truction Hot spare drive copy completed Optimal Replaced drive marked r 0x2237 0x2236 emoved Reconstructing drive marked rem oved 0x2235 0x2234 removed Unassigned
9. 269 Chapter 6 Viewing Reports 270 Table 6 13 describes the contents of the report Table 6 13 Hardware Changes Report Contents System Group Manager Mode Column Heading Description No Index number in the table Part Name Name of the part Location Location of the part Serial Number Serial number of the part Part Number Part number of the part Revision Revision level of the part System Name System on which the part is located Install Date Time Date and time that the part was installed in the location Remove Date Tim Date and time the part was removed from the location Using the Command Line Interface Use the following syntax of the espreport command to view a hardware changes report usr sbin espreport hwchanges sysid system id host host name gt from mm dd yyyy to lt mm dd yyyy gt Use the fromand to options to specify a range of dates If you do not use these options the report includes all available data Software Reports Software Reports There are two types of software reports e System inventory reports e System changes reports Software Inventory Reports Software inventory reports show all software installed on a system at a specific date and time Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate a software inventory report from single system manager mode 1
10. mtr SIOC MULTI srb_ used unix mtr mtr watchdog unix mtr mtr output unix mtr POLLING SIFINT unix Filesystem on device may be corrupted unmount and fsck Yt unix Directory 0 9 is co Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No zu OoOo00 2 ESP for the IRIX OS 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 1944 1944 1944 1944 1944 1944 1944 19441 19441 19441 19441 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 26 25 24 23 22 21 20 11 10 09 05 04 03 rrupted unix NFS server increase svc maxdupreqs from 0 9 unix wid 0 9 already swapp ing buffers unix crimeError resetting gr aphics from unix crime unknown ioctl imdmonitor il8n unix Wacom failed init No t ablet unix ECC Error in side of IMM Slot 0 9 unix Nonrecoverable memory pa rity error detected unix ALERT arp host with MA C address is still using my I P address unix ALERT arp host with MA C address is using my IP addr ess unix NOTICE SCSI tape 40 3 I ncompatible media in drive
11. 82 82 82 82 82 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 3729 3728 3727 3714 3113 3712 Sul 3710 3709 3708 3707 3706 3705 H W graph cannot create vhdl H W graph cannot add to xtalk v ertex H W graph cannot create device vertex H W graph cannot add device ver tex H W graph cannot get device ver tex H W graph cannot create device vertex for port scmd timed out Cannot destroy zombie fwd vcte Unknown b2h type Cannot destroy fwd vcte Cannot destroy rvs vcte 1 Cannot destroy rvs vcte 2 No unit number H W graph ioctl cannot create v hdl 1 H W graph ioctl cannot create v hdl 2 Ecname error mode at PCI addres S Debug quadoc3 flash req cmd Could not locate DMA descriptor CMS Cannot allocate nCr handle current cells Membership lost withdrawing f rom cluster cms comb dynamic init cannot al loc memory mtcp hb watchdog expired Cannot create multicast socket invalid config cmd unexpected param type mesg xpmb count Bad paramater type unknown header type unregistered subsystem thread callback still in progre ss unregistered translation subsys tem unknown subsystem Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Ye
12. The DSO components of ESP are e Core software ESP DSO SGM DSO e Monitoring software availmon DSO syslog DSO Performance monitoring DSO The stand alone components of ESP are e Monitoring software Availability monitor availmon Configuration monitor configmon e Notification software espnotify espcall e Console software Configurable Web server esphttpd Web based interface Report generator core Report generator plugins e Command line interface Configuration tool espconfig Report tool espreport If you install the performance metrics inference engine application pmie which is included in the Performance Co Pilot Execution Only Environment pcp eoe subsystem ESP can receive notification of resource oversubscription bandwidth saturation and other adverse performance conditions 15 Chapter 1 Introduction 16 If you install the Internal Support Tools 2 0 CD or a later release ESP can receive data from the diagnostic tools included on the CD Note The Internal Support Tools CDs are available only to SGI support personnel for example System Support Engineers Figure 1 6 shows the ESP architecture when a Web based interface is used Figure 1 7 shows the ESP architecture when a command line interface is used Descriptions of the components follow the figures ESP Architecture Figure 1 6 sgi ESP Architecture Using Web Browser User Remote Event Manager
13. The interface displays the Action Reports window Refer to Figure 6 13 Mesp Embedded Support Partner ver 30 ESP pere mil Set Environment I Configuration E Reports l BE Logbook Action Reports balkan csd sgi com C Last 30 days C Last 7 days o 08 13 2003 to 08 13 2003 Generate Report Figure 6 13 Action Reports Window Single System Manager Mode 3 Specify the range of dates for the report 4 Clickonthe Generate Report button Figure 6 14 shows an example actions taken report 242 Actions Taken Reports aM esp Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Configuration Logbook Action Report balkan csd sgi com 08 13 2003 to 08 13 2003 No Class va 1 Daemon Messages Event Description va Daemon Error Lii Action Taken 08 13 2003 mail sysadm 12 35 24 08 13 2003 mail sysadm 12 36 17 08 13 2003 mail sysadm 12 36 17 2 Diagnostic Diagnostic start 3 Diagnostic Diagnostic interrupted Figure 6 14 Example Actions Taken Report Single System Manager Mode Table 6 4 describes the information that the report contains Table 6 4 Actions Taken Report Contents Single System Manager Mode Column Description No Index number in the table Class Class of the event to which the action is assigned Event Description Time Action Taken Description of the event to which the action is assigned Time and date at that the action was
14. To add a new pager click on the Add button To update the pager parameters click on the check box next to the pager name and then click on the Update button To delete the pager click on the check box next to the pager name and then click on the Delete button Using the Command Line Interface No command line interface commands are available to set up the pager parameters To modify the pager parameters you must manually edit the etc qpage cf file and use the etc init d qpageserver script to start QPage 113 Chapter 4 Setting Up the ESP Environment Setting Up the System Parameters Single System Manager Mode Only 114 The system parameters enable you to set up an alias name select the system mode full or SGM and add the system to a group Perform the following procedure to update the system parameters in single system manager mode 1 Click onthe Set Environment button 2 Clickon the System button The interface displays the Update System Information window Refer to Figure 4 12 ares p Support Partner ver 30 A ESP Administration mi Set Environment x7 Configuration Reports Logbook E Update System Information baltic csd sgi com Warning All changes take effect immediately Alias name baltic System mode C SGM Ful System group Unknown zjl Update Figure 4 12 Update System Information Window Single System Manager 3 Setthe parameters Table 4 3 describes the
15. Transport endpoint is not connected 4 4 4 Daemon Error 08 13 2003 08 13 2003 1 warning can t get 09 09 04 09 09 04 client address Transport endpoint is not connected 4 4 4 4 4 Figure 6 2 Example Report Web based Interface Printable Format If you use the Web based interface to generate and view reports there are several controls that you can use to navigate the reports Refer to Table 6 1 Table 6 1 Report Navigation Controls Control Function io records per page Select the number of report entries records to show on a page Select the software application to view in a software inventory report Activate the selected menu options Display the report in the printable format that shows an ASCII table with all report entries Expand all rows in the table to Show subcomponents of each row 227 Chapter 6 Viewing Reports 228 Table 6 1 Report Navigation Controls continued Control Function Contract all rows in the table to show only the top level components Contract the current row Expand the current row to show all subcomponents of the component shown in the row Go to the last page of report Go to the next page of the report Go to the previous page of the report Go to the first page of
16. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 337 Chapter 10 Default Event Classes and Types 338 75 75 75 75 75 75 TS 75 75 75 75 75 75 75 75 75 75 TS 75 75 75 75 75 75 75 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2976 2977 2978 2979 2980 2981 2982 2983 2984 Lost spool info on MSPEC buserr error on MSPEC access 0 error on MSPEC access 1 UCE interrupt on PIO access Lost spool info on IO buserr Uncorrectable error on uncached memory access physical addres S uncached remote partition acces S error Page with memory directory erro r could not be discarded 2 uncached partition page access error No spool info on uncached buser r at paddr Lost spool info on uncached bus err Uncached read access timed out physical address uncached remote partition timeo ut error uncached partition page timeout error Uncached remote partition acces S error physical address Uncached memory access error c ause
17. ode select for array logical p 365 Chapter 10 Default Event Classes and Types 366 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3545 3544 3543 3542 3541 3540 3539 3538 3537 3536 3535 3534 3533 3532 3531 3530 3529 3528 3527 3526 3525 3524 3523 3522 age 2B received 0x300C ode select for array physical page 2A received 0x300B ode select for control mode pa ge A received 0x300A ode for caching page 8 receive d 0x3009 ode select for page 2 received 0x3008 ode select for page 1 received 0x3007 Safe pass through issued 0x300 6 Synchronize controller cache is sued 0x3005 Release issued 0x3004 Reserve issued 0x3003 Reassign blocks issued from hos t 0x3002 Quiescence issued 0x3001 Format unit issued 0x3000 Drive by passed condition resol ved 0x2824 Incompatible mini hub canister 0x2821 Two controllers present but NVS RAM offset 0x35 bit 6 set fo r NOT reporting a missing secon d controller 0x2820 ESM Environmental card firmware mismatch resolved 0x281F Temperature changed to optimal 0x281A Tray ID mismatch resolved 0x28 19 Tray ID conflict resolved 0x28 17 GBIC changed to optimal 0x2814 ini hub canister changed to op timal 0x2812 Not Used 0x2811
18. sysid system id gt Use the following command syntax to view the current setting of the call logging parameter usr sbin espconfig show call logging sgmclient client alias gt sysid system id gt Use the following command syntax to enable call logging which sends event information to SGI to provide proactive support usr sbin espconfig enable call logging text comp encoded sgmclient client alias gt sysid system id gt Note You must set up a customer profile for call logging to work The text option specifies that ESP should send the e mail message in plain text format the comp encoded option specifies that ESP should send the message in uuencoded format The e mail address lists can contain up to 255 characters of comma separated e mail addresses Use the following command syntax to disable call logging usr sbin espconfig disable call logging sgmclient client alias sysid system id gt Use the following command syntax to view the current setting of the e mail parameter usr sbin espconfig show mail 103 Chapter 4 Setting Up the ESP Environment 104 Use the following command syntax to enable ESP to send e mail messages and specify the e mail account that sends the messages usr sbin espconfig nable mail from email address emaill email address gt email2 email address gt Use the following command syntax to disable ESP from sending e mail m
19. 17 Chapter 1 Introduction Remote Event Manager Spi Figure 1 7 ESP Architecture Using Command Line Interface User 18 ESP Architecture Core Software The core software includes the functionality that is necessary to process events to determine the action to perform and to store data about the system that ESP is monitoring The core software includes the following components e System Support Database SSDB e ESP and SGM dynamic shared objects DSOs System Support Database SSDB The SSDB is the central repository for all system support data It contains the following data types e System configuration data e System event data e System actions for system events e System availability data e Diagnostic test data e Task configuration data The SSDB includes a server that runs as a daemon espdbd which starts at boot time Note ESP includes a utility esparchive that you can use to archive the current SSDB data which reduces the amount of disk space that is used ESP and SGM DSOs There are two main consumer DSOs that ESP 3 0 uses to subscribe unsubscribe and process events e The ESP DSO e The System Group Manager SGM DSO 19 Chapter 1 Introduction 20 ESP DSO The ESP DSO is the main ESP processing module It is the consumer for all ESP events It receives events from the Event Manager converts them to the ESP specific format saves them in the SSDB and executes any
20. 2 Diagnostic interrupted 3 Diagnostic start 4 Stress end 5 Stress interrupted 6 Stress start 7 SVP end 8 SVP interrupted 9 SVP start Registration With SGI Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Figure 5 19 Event List for Updating an Event 6 Click on the description of the event that you want to update The interface displays the Update Event window with the information for the event that you selected Refer to Figure 5 20 Configuring Events aj esp Embedded Supron Partner ver 30 A ESP perm mil Set Environment Reports E Ba Logbook AA b Events Load Profile Add Update Batch Update Delete subscription i O Update Event balkan csd sgi com Class Diagnostic Event Diagnostic end Event status Registration with SGI I myaction 1 I Notify sysadmin on console Enabled Disabled Action frequency e6400 secs B6400 secs Figure 5 20 Update Event Window with Event to Update You cannot modify the parameters for single events in the availability configuration and diagnostics classes You must use the Batch Update command to update these parameters for events in those classes The Live event in the availability class is the exception you can modify all parameters for this event You cannot update the Event Status parameter for individual events in the availability system configuration or diagnostics event classes U
21. 58 57 56 55 54 53 52 51 50 49 48 Fre eing more than allocated Allocated less than freed midisyn midisyn midisyn midisyn midisyn ut midisyn midisyn unix unix unix unix unix unix unix unix unix unix unix unix stem unix client commit failure XVM hostnames dont match XVM specific messages unix TOOK ACTION unix CONFIG ISSUE unix SYS DEGRADED unix MAINT NEEDED th initial preset loa d error th resource temporari ly unavailable th unable to set up I PC pipe unable to create i nternal MIDI device th unable to set outp port rate or clock type h unable to open aud io out port ct y ct th audio interface se t failed Cannot lock process inm emory No memory to register pr otocol No space for client Cannot initialize clie nt list semaphore Could not start thread Could not create semap hore for io q Out of memory allocating common client info Client could not setup new client Client Access denied xfs iflush detected cor rupt incore inode xfs iflush ad inode Please umount the filesy and rectify the problem I O error in filesystem Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
22. Configuring Events fap esp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment Z Configuration E Reports 3 Logbook P Events P ada EJ Add Event Figure 5 10 Add Event Window with Example Parameters Adding Event to New Class 9 Click on the Add button The interface displays a verification message Refer to Figure 5 11 155 Chapter 5 Configuring ESP 156 mM esp ag Embedded Support Partner ver 30 a ESP Administration mil Set Environment Reports Logbook AA P Events Load Profile Add Update BatchUpdate Delete subscription O Add Event balkan csd sgi com Profile name Demo Event class Realtime Demo Event description Demo start Event status Enabled Occurrences prior to registration 1 Application name realtdemo Priority Not set Facility Not set Regular expression Current actions Action description Action frequency 1 Notify sysadmin on console 86400 secs Commit Figure 5 11 Verification Message for Adding an Event Adding Event to New Class 10 Click on the Commit button The interface displays information about the event that was added Refer to Figure 5 12 If you need to update the event click on the update button Be sure to note the sequence number assigned to the event located in the event description next to the event name You need this number to register the event in ESP fr
23. Enter a subject for the entry This required field can hold up to 128 characters 4 Enter a log entry This required field can hold up to 4 Kbytes of data 5 Clickonthe Submit Log button The interface displays the information that you entered Refer to Figure 7 8 Embedded Support Partner ver 30 A ESP Administration mil Set Environment Configuration Ln Logbook Create Log balkan csd sgi com User administrator Date 08 13 2003 Subject routine online testing Log entry Ran weekly runalldiags basic testing No failures were detected Commit Figure 7 8 Logbook Entry Confirmation Window Single System Manager Mode 6 Click on the Commit button to create the entry The interface displays the information that was added to the logbook Refer to Figure 7 9 299 Chapter 7 Using the ESP Logbook mM esp UM Embedded Support Partner ver 30 a ESP Administration mi Set Environment Configuration Reports Create Log balkan csd sgi com User administrator Date 08 13 2003 14 25 41 Subject routine online testing Log entry Ran weekly runalldiags basic testing No failures were detected Figure 7 9 Completed Logbook Entry Single System Manager Mode Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to add a logbook entry in system group manager mode 1 Click on the Logbook button 2 Click on the Add L
24. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 3062 3061 3060 3059 3058 3057 3056 3055 3054 3053 3052 3051 3050 3049 3048 3047 3046 3045 3044 device failed 142 Rebuild stopped with error 14 1 An automatic rebuild has starte d on logical drive 137 Logical drive is critical 135 Logical drive has been made off line 134 Consistency check failed due to physical device failure 133 Consistency check on logical dr ive failed 132 Consistency check on logical dr ive error 131 Device loop ID conflict soft a ddressing detected 96 A standby rebuild was started A hard disk failed because wri e operation of Bad Data Table failed 49 A hard disk failed because writ e operation of the Configurati on On Disk failed 48 A hard disk failed because devi ce was not found on start up 61 Temporary Dead physical drive i S automatically made online 6 0 Physical drive missing on start up 57 Physical device failed to start 54 47 A hard disk failed because devi ce is not rea
25. aA ESP Administration mil Set Environment Iv Configuration E Reports __ Logbook 8 Event Report 1 Daemon Error 08 13 2003 08 13 2003 warning can t get client 06 23 55 06 23 55 address Transport endpoint is not connected Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 03 03 09 03 03 address Transport endpoint is not connected Figure 6 1 Example Report Web based Interface 226 About Reports Event report for Daemon Messages class From 08 13 2003 to 08 13 2003 System baltic csd sgi com T 4q dqesesese 4 qose d 5 2 5 5 No Event First Last Ev Syslog message Description Occurrence Occurrence Cnt T poe mmm mm mmm mmm T 4 4 4 1 Daemon Error 08 13 2003 08 13 2003 1 warning can t get 06 23 55 06 23 55 client address Transport endpoint is not connected 4 4 4T 4 4 4 2 Daemon Error 08 13 2003 08 13 2003 1 warning can t get 06 35 31 06 35 31 client address Transport endpoint is not connected 4 4 4 4 4 3 Daemon Error 08 13 2003 08 13 2003 1 warning can t get I 09 03 03 09 03 03 client address
26. show system host host name sgmclient client alias sysid system id set system host host name sysid system id alias new alias gt group group name gid group id setnode system sgmnode fullnode check system sgmlicense updat add sgmclient alias client alias host client hostname path client reach path group group descr gt gid group id gt v2 v3 p lt password gt subscribe sgmclient host host name alias client alias gt sysid system id loadprofiles refreshprofiles lightnode fullnode force unsubscribe sgmclient host host name alias client alias gt sysid system id force update sgmclient host host name alias client alias gt sysid system id p lt password gt path new path gt lightnode fullnode delete sgmclient host host name alias client alias gt sysid system id ping sgmclient client alias sysid system id path reach path espver add sgmserver host lt SGM host name p communication password Using the Command Line Interface espconfig update sgmkey host host name p comm password pid key ID gt Refer to Chapter 3 Administering ESP Chapter 4 Setting Up the ESP Environment and Chapter 5 Configuring ESP for more information about using the espconfig command espreport has the following command line options s
27. x220F Media scan scrub started 0x2 20E Media scan scrub enabled 0x2 20D Device failed during interrupte 369 Chapter 10 Default Event Classes and Types 370 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 34 34 34 34 34 34 34 34 34 34 34 48 47 46 45 44 43 42 41 40 39 38 37 36 39 34 33 32 3675 34 34 34 34 34 31 30 29 28 2d 26 d write processing Copyback restarted Copyback started Modification reconfigur leted Modification reconfigur ted Device copy complete Reconstruction completed Source drive failed duri operation I O is resumed Volume group or volume d Volume added Volume marked optimal Cache corrected by using ate controller s cache Recoverable error in dat 0x220 0x220 0x220 e co 0x220 e st 0x220 0x220 0x2 p E C B A m 9 a 8 d 2 0 6 ng copy 0x2205 0x2204 eleted 0x2203 0x2202 0x2201 altern 0x211A a buffe r memory detected correc ted 0x 2119 Controller cache manager cleared Alternate controller cac ery failed Alternate controller cac ery nearing expiration Alternate controller cac ery is fully charged rror 0x2117 he batt 0x2116 he batt 0x2115 he batt 0x2114 nearin Controller cache battery g exp
28. 154 Perform the following procedure to use this window to add an event to a new event class 1 2 3 Choose the event profile Enter the name of the new event class in the New custom class field Enter a description of the event in the Event description field ESP displays this description on other pages of the interface to identify the event Note The description cannot include the following characters Specify a status for the event Click on Enabled to add the event to the database and to start monitoring it Click on Disabled to add the event to the database but not monitor it Specify the number of times that the event must occur before ESP registers it and performs any assigned actions in the Occurrences prior to registration field Set the following optional parameters to provide more information about the event e Application name Priority value Facility value e Regular expression to match Assign an action to the event If Event status is set to Enabled ESP performs this action when the event is registered Specify the number of seconds that ESP should pause between multiple executions of an action in the Action frequency time field A value of 0 disables the option For example if you set this parameter to 5 seconds and ESP registers an event every second ESP executes the assigned action s every 5 seconds Figure 5 10 shows the Add Event window with example parameters
29. 30 ESP prre mi Set Environment x7 RA Configuration Reports E F Logbook Add Password For A New Server Update Password For An Existing Server baltic csd sgi com Warning All changes take effect immediately Password Update Figure 4 22 Update Password for an Existing Server Window 134 Using the Command Line Interface to Configure SGM Settings 4 Enter the new password in the Password field Tip To remove a password leave the Password field empty 5 Click on the Update button Using the Command Line Interface to Configure SGM Settings You can use the espconfig command to register an SGM server Use the following command syntax to register a server usr sbin espconfig add sgmserver host lt SGM host name gt The command prompts you for a communication password You can use the espconfig command to configure SGM clients Use the following command syntax to register a client usr sbin espconfig add sgmclient client alias client hostname server alias The command prompts you for a communication password Use the following command syntax to add a client usr sbin espconfig add sgmclient alias client alias host client hostname path client reach path gt group group descr gt gid group id gt v2 v3 p lt password gt Use the following command syntax to subscribe a client usr sbin espconfig subscribe sgmclient host host name
30. 359 396 397 398 399 ror Cached read access Directory e rror Cached remote partition directo ry error Page with memory directory erro r could not be discarded 3 Cached partition page directory error Cached read access Bad error t ype Partition error handler not reg istered 5 writeback surprise WAR done 5 writeback surprise War fail Cache Error Cache Error Cache Error Cache Error Interface Error Suspect MEMORY BANK Recovered from memory error by discarding the page Unrecoverable Interfac Tror Suspect memory address CPU isolated after recovered ca che error CPU isolation failed CPU Error CPU paddr CPU Tag State CPU Cache Error recoverd by inv alidating line Cache Error on CPU Recovered by killing process Cache Error recovery failed secondary Cache SBE Cached remote partition Poison Access Violation Cached partition page Poison Ac cess Violation Cached read Poison Access Viola tion Cached remote partition Excessi Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 75 75 75 T5 75 75
31. 51 52 Chapter 2 Accessing ESP 4 Enter a username and password Refer to Figure 2 2 The default username is administrator the default password is partner Note Before you use ESP the first time enter espconfig createadmin to create the default user account administrator T EE NEET csd sgi com Username and Password Required xj Enter username for Embedded Support Partner Secured Area at deiter csd 5554 UserName administrar SS Embedded Support Partner Figure 2 8 Entering a Username and Password Using the Web based Interface The ESP main page appears Figure 2 3 shows the main page in single system manager mode Figure 2 4 shows the main page in system group manager mode The main page shows the current system and ESP configuration information and provides buttons that link to the main ESP functions mM esp Embedded aai Partner verzo rmi ESP Administration mE Set Environment Iv Configuration Repor E Logbook f System Information Figure 2 9 ESP Main Page Single System Manager Mode 53 Chapter 2 Accessing ESP T un Support Partner ver 30 rj ESP Administration mil Set Environment Iv Configuration Reports E Logbook f System Information Figure 2 10 ESP Main Page System Group Manager Mode 54 Using the Web based Interface Using the launchESPartner Command ESP for the IRIX OS Only Perform the following procedure to use the 1aunchESPartner comm
32. 80 80 80 80 80 80 80 80 80 80 3159 3152 3151 3150 3149 3146 3730 3760 3759 3758 S435 3756 3755 3754 3753 3752 3751 3750 3749 3748 3747 Warm spare found 27 Active spare found 26 Expand Capacity stopped with er ror L8 Expand Capacity Completed 17 Expand Capacity started 16 A previously configured disk is now available 15 A hard disk has been removed 14 A new hard disk has been found 13 A rebuild has started 6 A hard disk added as hot spare 2 A hard disk has been placed onl ine 1 Unknown Event Valid SANMap was not found in t he configuration on disk 809 Valid configuration on disk not Battery test failed battery ba Battery test has completed 52 Battery test has started 519 A ted to stop the surviving contr Error in mirror race table 44 found 808 d 522 Battery test cancelled 521 0 replacement controller attemp oller 441 0 Dual active negotiation failed cache memory size 439 Dual active negotiation failed memory size 438 Dual active negotiation failed host ports 437 Dual active negotiation failed disk channels 436 Dual active negotiation failed board types 435 Dual active negotiation failed IDs 434 No Yes Yes Yes Yes Yes Yes Yes Yes N
33. Notification message Execute action as Action timeout Action status r r r r r r r F Host name from which event originated Data received along with the event Event time stamp in mm dd yyy hh mm ss format Event class description Event class ID Event description Event type ID Event ID as registered by ESP Forwarder hostname in case of SGM System ID i nobody f30 second s Enabled Disabled Update Figure 5 43 Update Action Window Configuring Actions 5 Update the parameters 6 Clickon the Update button The interface displays a verification window Refer to Figure 5 44 al es p Support Partner ver 30 A ESP Administration Set Environment Reports Logbook AA P Actions Add b Update Enable Disable Update Action Notify sysadmin on console Action string dusr sbin espnotify A n 7 D l Execute action as nobody Action timeout 30seconds Action status Enabled Commit Figure 5 44 Verification Message for Updating an Action 7 Click on the Commit button The interface displays a confirmation message Refer to Figure 5 45 If you need to update the parameters again click on the description of the action 203 Chapter 5 Configuring ESP AM esp Embedded Support Partner ver 30 a ESP Administration mi Set Environment Z Configuration E Reports E Logbook AA Md P Update Enable Disable Update Current Action
34. Perform the following procedure to use the Web based interface to generate a software changes report from single system manager mode 1 Click on the Reports button 2 Click on the Software button 3 Click on the Changes button The interface displays the History of Software Changes window Refer to Figure 6 37 aM esp ag Embedded Support Partner ver 30 A ESP Administration mi Set Environment MeCN E Reports Logbook History of Software Changes balkan csd sgi com C Last days Last 30 days C ori 3 2001 to oer 3 2003 Figure 6 37 History of Software Changes Window Single System Manager Mode Software Reports 4 Specify the range of dates for the report 5 Clickonthe Generate Report button Figure 6 38 shows an example software changes report AM esp Embedded Support Partner ver 30 aA ESP Administration E Set Environment Configuration Reports Logbook D ESP Notice Software No changes for this time period ok Figure 6 38 Example Software Changes Report Single System Manager Mode Table 6 16 describes the contents of the report Table 6 16 Software Changes Report Contents Single System Manager Mode Column Heading No Software Name Software Version Installation Date Removal Date Time Description Description Index number in the table Name of the software application Version number of the software application Date that the software application was ins
35. Write back error 385 Access to fan status informatio n has been lost Switch card o r connectivity has been removed 337 Access to power supply status i nformation has been lost 336 Access to temperature sensor ha S been lost 335 Enclosure Soft Addressing Detec ted 333 Enclosure access is offline 3 32 Enclosure access critical 330 Temperature sensor is not prese nt 329 Temperature is above working li mit 327 mperature is over safe limit Failure imminent 326 Power supply is not present 3 25 Power supply failure 323 Fan is not present 322 Fan failure 320 Uninterruptible power supply fa iled 310 Uninterruptible power supply ba ttery low 309 Uninterruptible power supply AC failed 308 Uninterruptible power supply di sabled 307 Storage Works enclosure reporte d failure state 304 Storage cabinet temperature sen Sor is not present 292 Over temperature 291 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 347 Chapter 10 Default Event Classes and Types 348 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
36. Yes Yes 375 Chapter 10 Default Event Classes and Types 376 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 4194447 4194446 41944 41944 41944 41944 41944 41944 41944 41944 41944 41944 41944 41944 41944 41944 1944 1944 1944 1944 BS Qm am ae 41944 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 Z4 meta data dev block unix I O Error Detected Shu tting down filesystem unix Superblock write error detected while unmounting files ystem Filesystem may not be m arked shared readonly unix Corruption of in memory data detected Shutting down filesystem unix filesystem is corrupt unmount and run xfs repair unix corrupt inode in files ystem Unmount and run xfs repai Es unix mtr unable to alloca te buff memory unix mtr kmem_zalloc fali ed unix mtr could not alloca te pio map unix mtr bad EDT ctlr ent EY unix mtr SIOCSIFADDR AF R AW failed unix mtr possible lockup unix mtr failed to alloca te memory for TX amp RX kvpalloc unix mtr SIOC TR RESTART failed unix mtr SIFINT ADAPTER C HECK unix mtr no memory or io base register unix
37. abilized reached reached t reache d reached reached reached reached hed Temperature advisory limit reac hed Power level stabilized Fan speed stabilized Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 341 Chapter 10 Default Event Classes and Types 67 354 Temperature stabilized Yes Yes 67 355 Auto power down interrupted Yes Yes 67 356 Auto power down completed Yes Yes 67 357 Environment monitor test faul Yes Yes t condition this is a test 67 358 Environment monitor test warn Yes Yes ing condition this is a test 67 418 VRM not present Yes Yes 67 419 VRM not okay Yes Yes 67 420 48V power failure Yes Yes 67 421 System controller watchpoint co Yes Yes ndition 1 67 422 System controller watchpoint co Yes Yes ndition 2 67 428 Power Bay DPS 1 AC fail lost r Yes Yes edundancy 67 429 Power Bay DPS 2 AC fail lost r Yes Yes edundancy 67 430 Power Bay DPS 3 AC fail lost r Yes Yes edundancy 67 431 Power Bay DPS 4 AC fail lost r Yes Yes edundancy 67 432 Power Bay DPS 5 AC fail lost r Yes Yes edundancy 67 433 Power Bay DP
38. aes p Support Partner verzo A ESP Administration mil Set Environment Z Configuration E Reports Logbook AA b Events Delete User Events baltic csd sgi com No Class Event Description Status 1 my config class my config event Enabled Figure 5 26 Delete User Events Window Web based Interface 4 Click on the description of the event that you want to delete or click the name of event class to delete an entire class of events The interface displays a verification message Refer to Figure 5 27 IE mbedded Support Partner ver 30 A ESP Administration mil Set Environment Z Configuration E Reports Logbook AA Delete Custom Event baltic csd sgi com Event my config event will be deleted History for this event will be deleted Commit Figure 5 27 Verification Message for Deleting an Event 5 Click on the Commit button The interface displays a confirmation message Refer to Figure 5 28 179 Chapter 5 Configuring ESP 180 Mes p Support Partner ET aA ESP Administration Imil Set Environment Reports Logbook Ez b Events Load Profile Add Update Batch Update P Delete subscription 8 8 Delete Custom Event altic csd sgi com This was the last event in the class my config class Both event my config event and class my config class have been deleted Figure 5 28 Confirmation Message for Deleting an Event Using the Command Line Interfac
39. forbidden Please check your permissions Unable to verify that the host name matches the address This may be a transient problem or a botched nam Authorization failed Retry Forbidden Request The current request was forbidden Please check your permissions Connection was rejected since number of authorization attempts was reached Please try to connect later server setup Reverse DNS lookup failed because ESP was not able to verify that your system IP address and hostname matched Reverse DNS lookup fails if an IP address is faked or if the DNS server used by the ESP Web server is not working correctly The username and password that you entered are not valid You did not enter a valid username password combination within four attempts When this happens the ESP Web server prevents login attempts for two minutes If the DNS server on the system is not working correctly perform the following actions to disable reverse DNS lookup 1 Add the following line to the Web server configuration file etc esphttpd conf ReverseDNSLookup off 2 Enter the following command to kill the current Web server process killall esphttpd 3 Restart the esphttpd process Warning Disabling the reverse DNS lookup feature increases the possibility of security problems Enter a valid username and password If you forget your username and password enter espconfig update user name username
40. may be blank tape or wrong tape ty pe unix ALERT SCSI tape Exce Ssive write errors unix NOTICE SCSI tape Inc ompatible media when reading unix dks Alert mediad couldn t find DSO for device at SCSI ctlr mediad can t open CD ROM I O error mediad can t read sector 0 9 of device mediad sector size of 0 9 too large for HFS mediad The file system on dev ice cannot be mounted fam imon event queue overflow fam can t open dev imon unix XFS read error in file s ystem meta data block 0 9 unix XFS write error in file Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 377 Chapter 10 Default Event Classes and Types 378 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 4194401 4194400 4194399 4194397 4194396 4194395 4194394 4194393 4194392 4194391 4194390 4194389 4194388 4194387 4194386 4194385 4194384 system meta data block 0 9 unix Process ran out of d isk space unix Process ran out of con tiguous space unix Ancestor inode 0 9 is not a directory unix Process pid 0 9 kil led not enough memory to grow stack uni
41. sgmclient client alias sysid system Id espconfig save espenv global ipaddr user site customer_profile all name gt espconfig load espenv sysid lt client system id gt chk check definition file name gt from lt data definition file name gt IP Address Configuration lt IP address gt lt IP address gt espconfig enable ipaddr IP address gt espconfig disable ipaddr IP address 37 Chapter 2 Accessing ESP espconfig espconfig delete ipaddr IP address IP address list ipaddr IP address IP address enabled disabled User and User Permission Configuration espconfig add user name user name gt p lt password gt espconfig delet user name user name p lt password gt espconfig updat user name user name p new password gt espconfig list user name user name gt espconfig createadmin espconfig add permdesc perm permission name desc permission description espconfig delet permdesc perm permission name espconfig list permdesc perm permission name permission name gt espconfig add userperm name user name gt perm permission name gt espconfig delet userperm name user name perm permission name gt espconfig list userperm name user name perm permission name gt ESP Archive Management espconfig list archive lt archiv
42. 0x5012 363 Chapter 10 Default Event Classes and Types 364 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3595 3594 3993 3592 3591 3590 3589 3588 3587 3586 3585 3584 3583 3582 3581 3580 3579 3578 3577 3576 35475 3574 3573 3572 3571 Change RAID level of volume gro up 0x5011 Add free capacity to volume gro up 0x5010 Start volume group defragment 0x500F Reconstruct drive volume 0x500 e Place volume group online 0x C Place volume group offline 0 Controller NVSRAM download s ted 0x50 Download drive firmware issue 0x500 Controller firmware download arted 0x50 Initialize drive 0x50 Initialize volume group or v me 0x50 Delete volume 0x50 De assign hot spare drive 0 K CO Ch Oe oO oo O G oO o0 e x PNwWOBATP OWN pawo axo et Create volume 0x500 Assign hot spare drive 0x500 Assign volume group ownership 0x500 0 Controller reset 0x4010 Controller reset by its alterna te 0x400F Automatic volume transfer start ed 0x400E Controller placed online 0x400 D Controller placed offline 0x40 0C All channel reset detected 0x4 00B Alternate controller quiescence released 0x400A Controller quiescence released 0x4009 Controller quiescence halted 0 x40
43. 123 hrs 7 min 99 92 unknown 4 24 min 123 hrs 7 min Scheduled and Unscheduled 6 57 min 82 hrs 5 min 99 8195 Average uptime 70 hrs 13 min Least uptime 10 min Most uptime 336 hrs 53 min current epoch Average downtime 9 min Least downtime 4 min Most downtime 24 min Monitoring started at Thu Jul 24 00 22 06 2003 Last boot at Wed Jul 30 11 59 12 2003 Total time since last reboot 336 hrs 52 min Most Unsubscribed time 6 min All registered availability events Figure 6 18 Example Availability Report Single System Manager Mode Availability Reports Table 6 6 describes the contents of the report Table 6 6 Single System Availability Report Contents Single System Manager Mode Row Description Unscheduled Information about any unscheduled downtime events count downtime due to the event in minutes mean time between interrupts in minutes and availability percentage Scheduled Information about scheduled downtime events count Scheduled and Unscheduled Average uptime Least uptime Most uptime Average downtime Least downtime Most downtime Logging started at Last boot at System has been up for All registered availability events downtime caused by the service action in minutes mean time between interrupts in minutes and availability percentage Tip Click on the link to view a report of all scheduled availability events
44. 166 167 168 169 170 JE 172 173 174 175 176 178 179 180 181 182 183 184 185 Canno Canno Canno Canno Canno No heap zone No zone index Buffer overlap Invalid Size 1 Null pointer 1 Null size 1 Use count wrong Pointer already fr 1 Bad pointer Pointer already fr 2 Invalid Size 2 Null pointer 2 Null size 2 1 2 n Cannot allocate qband Cannot allocate qband t allocate space for mux ode Unknown event t allocate memory for mux edge 1 t allocate memory for mux edge 2 Cannot allocate qband 3 allocate stream event 1 allocate stream event 2 Message out of order hwgraph no vertex Bad service Invalid service Memory leak warning 1 Address out of range No memory for net proc l1 CPU not used No memory for net proc 2 Kmemory allocation error Memory leak warning 2 Receive port error Unsupported address MAC programming error Stray interrupt FDDI bad interrupt status CAMEL NP error Bad hwgraph vhandle Bad unit number No memory for frame filter ct ct Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Ye
45. 2d 52 53 54 55 56 57 58 99 60 61 62 63 64 65 66 67 68 69 70 2097920 2097921 1 Q1 WN 11 12 13 14 15 esphttpd missing library esphttpd resource path error esphttpd resource path error 1 esphttpd resource path error 2 esphttpd invalid port number esphttpd database init error esphttpd IP load error esphttpd username error esphttpd password error esphttpd database connection fa iled Eventmon cannot write amticker timestamp file Eventmon cannot find amdiag fil e NodeChange for SgmClient ESP started ESP stopped ESP set SGM node ESP unset SGM node ESP SGM client added ESP SGM client subscribed ESP SGM client unsubscribed ESP SGM client deleted Configuration Event Error Event SCSI ctrl init failed SCSI command timed out SCSI hard error SCSI bus reset SCSI ctrl h w sram parity erro JU pH r SCSI ctrl h w sram parity erro r bank0 SCSI ctrl h w sram parity erro r bankl 1 XIO bus error Keyboard error SCSI ctrl h w sram parity erro r bank1 2 SCSI bus error SCSI debug SCSI target or bus error PCI bridge error GIO bridge error Bema wee we ew 000000000 0 K oO zi zi Zz Oo Oo Z Zz 00000000 zu zu E Oo zZ no Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 2a A a a 2A D A 0000000000 z A 9 A Oo lt t2 SS a a maa a a A a M O
46. 4596 00x for more information about how tpmwatch sends events to ESP Remote Support Capability Remote support capability enables you to connect to the console software with a Web browser or directly to ESP with the command line application from a remote location This capability enables you to control ESP from the remote location and provides SGI support personnel with a virtual seat on the system or systems on which they need to work Remote support capability is built into ESP The only requirement is a communication channel for example a network connection to the site 31 Chapter 1 Introduction Security Features 32 ESP implements the following security features to prevent unauthorized access to ESP the data that ESP stores and the system that is running ESP ESP requires a login password combination to access the Web server ESP validates user permissions for the accounts that are assigned to execute actions ESP does not permit actions to run as root ESP implements ReverseDNS lookup for Web server and SGM connections ESP uses HMAC MDS digital signatures for all data transfers to an SGM server ESP disables login attempts after four unsuccessful attempts Users must wait several minutes before attempting to log in again ESP includes a command line interface to enable users to use ESP without running the Web server on their system ESP restricts database access to local transactions external systems
47. 5 Configuring ESP Table 5 4 PMIE Rules continued Rule Description Performance Issue cpu low util cpu syscall cpu system cpu util espping response espping status filesys filling memory exhausted memory swap low Low average processor utilization High aggregate system call rate Busy executing in system mode High average processor utilization System Group Manager slow service response System Group Manager service probe failure File system is filling up Severe demand for real memory Low free swap space The average processor utilization across all CPUs was below a threshold percentage This rule is effectively the opposite of cpu util and is disabled by default it is useful only in specialized environments where for example processing is batch oriented and low processor utilization is indicative of poor use of system resources In such a situation you should enable the cpu low util rule and disable the cpu util rule The average number of system calls per CPU per second exceeded a threshold value The average utilization per CPU exceeded a threshold value and the ratio of system time to busy time exceeded a threshold value The average processor utilization across all CPUs exceeded a threshold value The amount of time required for a monitored service to complete exceeded a threshold value A service that was being monitored by a group manager system fail
48. 7000134 7000135 7000136 7000137 2098176 2098177 2098178 2098179 DoF WN HE Controlled Controlled Controlled Controlled Controlled shutdown Controlled shutdown Singleuser shutdown unknow Singleuser shutdown 1 unknow Singleuser shutdown Singleuser shutdown Singleuser shutdown Singleuser shutdown Singleuser shutdown Singleuser shutdown Subscribe availability events Unsubscribe availability events Kernel Emergency Kernel Alert Kernel Critical Kernel Error Kernel Warning Kernel Notice Kernel Info Kernel Debug User Emergency User Alert User Critical User Error User Warning User Notice User Info User Debug Daemon Emergency Daemon Alert Daemon Critical Daemon Error Daemon Warning Daemon Notice Daemon Info Daemon Debug Diagnostic start Diagnostic interrupted Diagnostic end Stress start hutdown hutdown hutdown hutdown nnnnn 0 OrPWNERF DD AO 0 N FE Oo Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yos Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes KK ZBeweAeaeaeaewaeaaeaeaeyweeawaweaeaeaweeaseawao o n o 0000000000000 00000000 00 0 Z Yes 319 Chapter 10 Default Event Classes and Types 320 4005 2098180 Stress end Yes Yes 4005 2098181 SVP start Yes Yes 4005 2098182 SVP end Yes Yes 4005 2098183 SVP interrupt
49. 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 194356 194355 194353 194352 194350 194349 194348 194347 194346 194345 194344 194343 194342 194341 194340 194339 194338 194337 194336 194335 memory for ecplp driver unix attempt to disconnect no n existant IOC3 at unix out of IOC3 config struc unix ALERT SCSI controller ts 0 9 detected pci unix ALERT SCSI controller 0 9 detected bus reset by ext ernal unix ALERT SCSI controller ECOD device 0 9 detected unexpect unix ALERT SCSI controller 0 9 detected parity error unix ALERT SCSI controller d bus f ree 0 9 detected internal error unix SCSI disconnection must be enabled in order for tag que ueing to work 0 9 0 9 unix SCSI command for 0 9 0 9 rejected because its too large increase maxdmasz unix SCSI bus reset on contro ller 029 unix SCSI CDROM at 0 9 0 z91 failed unix SCSI hard error on 0 9 unix unix SCSI overfl nderf l unix SCSI command on 0 9 timed out after unix SCSI controller nitialization OS Oy low or u low on 0 9 0 9 secs 0 9 i failed unix XFS xlog recover do ino de trans bread error unix XFS xlog recov
50. C and system B to the SGM server system system A Note The SGM DSO feature does not require a license however you need a license on the SGM system to create SGM clients Chapter 1 Introduction System A SGM server xc a gt System C a j amp Ae hay gg System D SGM client Figure 1 5 Group Management Over Hierarchies 10 Distribution Simplified Group Management Configuration Under ESP 3 0 you do not need to configure group management on both the server and client sides like you did in earlier versions of ESP You only need to configure group management from the SGM server side Note No authentication is performed when you use this method to add clients to a server For increased security you can add a password that the server and client must exchange before they transfer data To do this you must configure the authentication password on the client and then on the server Enhanced Configuration for SGM Clients ESP 3 0 enables you to configure all configuration parameters including performance monitoring and system monitoring parameters for remote systems from the SGM server This enables you to set parameters for multiple systems from one location Note You cannot configure performance monitoring and system monitoring parameters for clients that are connected to a group manager through intermediate systems The group manager must have a direct connection to the c
51. Chapter 9 Logging Events from Applications and Scripts 316 e The p priority option specifies the priority for example local0 notice Refer to the syslog 3C man page for descriptions of the priority values If you do not specify a priority value esplogger sets the priority to local0 info You must use this option with the s option and the or m option e The t time option specifies the time that the event occurred You must specify the time in seconds since 00 00 00 UTC on January 1 1970 in decimal notation If you do not specify the time esplogger defaults the time to the time that it received the event You must use this option with the s option and the f or m option e The h option prints the usage information e The v option prints the esplogger version number Note You can also use 1ogger to send event information through SYSLOC Refer to the logger 1 man page for more information Example 1 emgrlogger t 200356 if FILE availmon dat esplogger s 200356 f availmon dat This example sets the sequence number to 200356 the priority to local0 info 1030 and the time to the time that esplogger received the event Then it passes this information and the data in the availmon dat file to eventmond Example 2 emgrlogger t 0x00200000 p syslog f warning is MSG Start SVP emgrlogger s 0x00200000 p syslog warning m Start SVP This example sets the sequence number to 0x00200000 the pr
52. Configuration El Reports E WE Logbook aa 2 P Modem Setup Service Provider Padng o Fl Paging gt Modem Setup boxelder peachtree sgi com Warning ESP paging subsystem is not running Paging will not be performed To restart paging subsystem please execute chkconfig quickpage on and or etc init d qpageserver start from a command line You might continue with the service provider configuration and enable paging subsystem later Administrator s e mail address nadezhda sgi com Waiting time for reply before giving up on the amp queries Modem Name Modem Device Modem Initialization Command Figure 4 9 Modem Parameters Window Web based Interface Enter a modem name in the Modem Name field do not include blank spaces 4 Enter the device name to which the modem is connected in the Modem Device field Example dev ttyd 5 Enter the modem initialization command in the Modem Initialization Command field Example ATZ Setting Up the Paging Parameters ESP for IRIX OS Only Be aware of the following information when you configure the initialization command e Theinitialization command is specific to the modem that you are using Refer to your modem user manual for specific details about the initialization command e The initialization command can vary based on requirements from your paging service provider For example many paging services require you to turn off error correction on your modem
53. E Reports E Ba Logbook AA Md P Update enable disable Update Current Actions Qu Save Action Profile Execute Description Action Timeout No va Action String As wa Enabled 1 Notify lusr bin espnotify A 96D nobody 10 Enabled sysadmin on console 2 test mail Jusr sbinfespnotify E nobody 600 Enabled nadezhda sgi com s ESP test notification n 7 m 96H 96D z 96c 96C 96e T F l Just a test Disregard please Figure 5 42 Update Current Actions Window 201 Chapter 5 Configuring ESP 202 Tip The Save Action Profile buttonin the Update Current Actions window saves all current actions in an action profile var esp init eventprofiles Actions esp You can copy this file to another system and load the profile using the same method as loading event profiles to have the same actions on that system ESP does not automatically save actions in an action profile You must click on the save Action Profile button to save the current actions in an action profile Click on the description of the action that you want to update The interface displays the Update Action window Refer to Figure 5 43 ar esp Embedded SUN Partner verzo ESP pre mil Set Environment Z Configuration E Reports E Ba Logbook AA P Actions Add b Update Enable Z Disable Update Action Notify sysadmin on console notify on console information message 3 Action type Notification priority Notification format
54. ESP will prompt you for a new password Wait for two minutes and log in with a valid username password combination 43 Chapter 2 Accessing ESP 44 Opening a URL in a Web Browser You can access the Web based interface via one of the following URLs http localhost 5554 http systemname 5554 Tips If the system that you want to use is a server without graphics capability you can e Log into the server system from another networked system that has graphics capability Then set the DISPLAY variable on the server to a display on the remote system and start a Web browser application on the server Open the http localhost 5554 URL in the Web browser window that is displayed on the remote system e Open the http server system name 5554 URL from a Web browser application running on a remote system that has graphics capability If you use this option you must use the espconfig enable ipaddr command to enable network access for the remote system before you open the URL Perform the following procedure to access ESP by opening a URL in a Web browser 1 If this is the first time that you are using ESP on the system do the following e Log into the system as root and enter espconfig createadmin to create the default user account administrator e Enter espconfig enable ipaddr 127 0 0 0 and espconfig enable ipaddr 127 0 0 1to enable access to ESP from the local system 2 Open the appropriat
55. Generate Report Figure 6 25 Hardware Inventory Report Window Single System Manager Mode 3 Specify the date and time of the hardware inventory that you want to view 4 Clickonthe Generate Report button Figure 6 26 shows an example hardware inventory report 260 Hardware Reports ales Embedded Support Partner ver 30 a ESP Administration mi Set Environment Configuration Logbook AA P inventory Changes Hardware Inventory Report T balkan csd sgi com 08 13 2003 13 21 40 Part Serial Installation Number Number RH Date NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 NA 07 24 2003 No Part Name Location 1 RACK 001 NA 2 MODULE 001c18 NA 811 NA 4 NODE 0 NA 5 CPU 0 NA 6 CPU 1 NA 7 NODE 1 NA 8 CPU 2 NA 9 CPU 3 NA 10 MODULE IXbrick NA z z Ze EN ES zZ Ea EN oo gu zt rE rE rr rr r z rrrrrr rr gt zZ z zZz zZ m zZ m Figure 6 26 Example Hardware Inventory Report Single System Manager Mode 261 Chapter 6 Viewing Reports 262 Table 6 10 describes the contents of the report Table 6 10 Hardware Inventory Report Contents Column Heading Description No Index number within the table Part Name Name of the part Location Location where the part is installed Part Number Part number for the part Serial Number Serial number of the part Revision Revision
56. Ia P Actions add Update Enable Disable Add Action Action description email me Action string fusrfbinfespnotify E me sgi com n 7 m H 96D 96z Execute action as nobody Action timeout 600 seconds Update Figure 5 37 Confirmation Message for Adding an Action Using Notification Action Option 195 Chapter 5 Configuring ESP Using the Other Action Option Figure 5 38 shows the Add An Action window when you choose the Other Action option mM esp ES Embedded Support Partner ver 3 aA ESP Administration mi aaau v Configuration Reports Logbook Actions Add An Action Action description Action string Execute action as Action timeout feoo second s Add Figure 5 38 Add an Action Window Using Other Action Option Perform the following procedure to use this window to create an action 1 Enter a description for the action ESP displays this description on other pages of the interface Enter a command to execute as a action For example you could use the espnotify command to send an e mail Refer to Chapter 8 Sending Notifications for more information about using the espnot ify command to send notifications Note If you want to create a standard notification it is easiest to use the Notification Action optionin the Add An Action window Refer to Figure 5 31 196 Configuring Actions Tip When you use the espnotify command you can include seve
57. O OO 20 O Q0 Gro OF O K oO o Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 325 Chapter 10 Default Event Classes and Types 326 co 0000000000 1 1 12 10100101010101 i 1 1 1 100000000000 01 0 SB O1000 00 00 00 CO CO O1 Oo O1 16 17 18 19 20 21 22 23 24 25 26 24 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 Panic Fatal Panic TOD batt Fatal Bus erro Pari Pari Power fail detected Parity error in SIMM Parity error in SIMM parity error in SIMM parity error in SIMM parity error in SIMM Parity error in SIMM Bus error Bus error 2 Memory copy error src Memory copy error dest TOD battery 1 TOD battery 2 TOD battery 3 TOD battery 4 TOD battery 5 ery load nvram info err or Power fail detected 2 memory parity error 2 Parity error in SIMM TOD battery 6 TOD battery 7 TOD battery 8 TOD battery 9 TOD battery 10 Fatal memory ECC error Bus error TCC Bus error 5 Bus error 6 Bus error internal r exception on IDLE st ack Parity error in SIMM 4 NMI 1 Parity error in SIMM 5 TOD battery 11 TOD battery 12 TOD battery 13 TOD battery 14 TOD battery 15 Memory ECC soft error Memory ECC hard error ty error in DIMM phy 1 ty error in DIMM phy 2 Yes Yes Yes Yes Yes Yes Ye
58. Refer to Setting Up the Network Permissions on page 68 If the system is running the Linux OS and ESP does not detect the system serial number enter the system serial number Refer to Setting Up the System Serial Number ESP for the Linux OS Only on page 92 Enter the customer profile information Refer to Setting Up the Customer Profile on page 64 Set up the global configuration parameters Refer to Setting Up the Global Configuration Parameters on page 97 10 Modify and or add actions Refer to Configuring Actions on page 187 11 Modify and or add events Refer to Configuring Events on page 139 59 Chapter 2 Accessing ESP Configuring Group Management 60 All ESP components necessary for group management are installed on your system by default however you need a nodelocked license to enable the system group management SGM functionality You must configure a system to use system group manager SGM mode to use the group management functions in ESP If you want one system to register events from other systems in a group and perform actions for those events you must subscribe to those events on the remote systems When the ESP software on a remote system registers subscribed events it logs them in its database if itis a full node light nodes do not maintain a database performs any actions assigned to the events and then forwards the events to the ESP software on the group manager system
59. Server Desktop Web Server and File Server To create a new group enter the name in the System group field Once you create one or more group names ESP displays a menu of the existing groups to select an existing group choose it from the menu Note When you enter group names the entry in the field takes precedence over the selection in the menu The proper way to create a new group is to set the menu to New Group and enter the group name in the System Group field The following three rules apply for creating group names 1 The case of characters does not matter ESP puts systems hat you enter in the groups named Web server and Web Server in the same group 2 Spacing between characters does matter ESP puts systems that you enter in the groups named Web server and Web server in different groups 3 Single and double quotes are not allowed This parameter is optional Setting Up the System Client Parameters System Group Manager Mode Only Updating an ESP 3 0 SGM Client If you select an ESP 3 0 SGM client ESP displays the Update Client Information window shown in Figure 4 18 a esp Tag Embedded Support Partner ver 30 aA ESP Administration mi Set Environment 7 Configuration Reports Logbook AA Update System Client Unsubscribe Delete Clet El Update Client Information balkan csd sgi com Warning All changes take effect immediately Client status C Subscribed Unsu
60. Setting Up the System Client Parameters System Group Manager Mode Only Unsubscribing SGM Clients If a system is subscribed you can either unsubscribe a client or unsubscribe and delete it When you unsubscribe a client the client no longer sends events to the SGM server and changes occur on the client system If a client system is a light node and subscribed to only one SGM server the client system resets to a full node once the unsubscription process completes If a client system is a full node or is subscribed to two or more SGM servers the mode for that node remains the same All information about an unsubscribed client for the period of time that the system was subscribed to the SGM server remains available on the SGM system When unsubscribe a delete a system the same actions occur and all information for the system including reports is removed from the SGM server Tip If an ESP SGM license expires and you do not plan to renew it enter the espconfig unsubscribe sgmclient command to unsubscribe the clients Perform the following procedure to unsubscribe a system 1 2 3 Click on the Set Environment button Click on the System Client button Click on the Unsubscribe Delete Client button The interface displays the Unsubscribe Delete Client window Refer to Figure 4 20 Note If more than one client is subscribed to the SGM server the interface displays a list of clients Select the client that you want
61. System Error 3 System Error 4 System Warning or5to7 System Information Specifies processing options for the message Two options are available o coMP compress and uuencode the message and o ENCO uuencode the message These options are valid only if you also use the f option Specifies the subject of the message The format of the default subject is HOSTNAME text where HOSTNAME is replaced with the name of the host and text is replaced with a priority message for example Critical System Error If you use the n and s options the s option overrides the n option Invoking espnotify from ESP For example the following command sends a message to dtg sgi com refer to Figure 8 3 usr bin espnotify E dtg sgi com m This is the text of the message n 1 Subject lobos Critical System Error Date Mon 7 Jun 1999 09 44 24 0700 PDT From root lobos csd sgi com Super User To dig sgi com This is the text of the message Figure 8 3 Sending an E mail Message Invoking espnotify from ESP Because espnot ify is a command line utility you can configure it as an ESP action To do this create a new action or update an existing action with a command string that uses the usr bin espnotify command This section shows an example of how to create ESP actions that use espnotify Note ESP automatically generates the proper espnot ify command line when you choose the Not
62. This can be done on the U S Robotics Sportster fax modem with X2 with the amp A0 amp K0 amp MO initialization command Contact your paging service provider to determine any special requirements 6 Click on the Add button The interface displays a confirmation window 7 Click on the Commit button Once you have a modem configured you have the following options to modify the modem parameters when you click on the Modem Setup button e Toadd a new modem click on the Add button e To update a modem click on the check box next to the modem and then click on the Update button e To delete a modem click on the check box next to the modem and then click on the Delete button Deleting a modem deletes all paging service providers and pagers that are assigned to it Using the Command Line Interface No command line interface commands are available to set up the modem parameters To modify the modem parameters you must manually edit the etc qpage cf file and use the etc init d qpageserver script to start QPage 109 Chapter 4 Setting Up the ESP Environment 110 Setting Up the Paging Service Provider Parameters ESP for IRIX OS Only You need to provide ESP with information about the paging service that you use so it can properly contact your pager Using the Web based Interface 1 Click onthe Set Environment button 2 Clickon the Paging button 3 Clickonthe Service Provider button The interface displays the S
63. Using the Command Line Interface 289 Site Reports System Group Manager Mode Only 290 Using the Command Line Interface 292 7 Using the ESP Logbook 293 About the ESP Logbook 293 viii Contents 10 11 Viewing Logbook Entries 293 Using the Web based Interface Single System Manager Mode 293 Using the Web based Interface System Group Manager Mode 295 Using the Command Line Interface 297 Adding a Logbook Entry 298 Using the Web based Interface Single System Manager Mode 298 Using the Web based Interface System Group Manager Mode 300 Using the Command Line Interface 303 Sending Notifications 305 About the espnotify Tool 305 Command Line Options for Displaying a Message on the Console 305 Displaying a Message on an X Window System Display 306 Sending an E mail Message 308 Invoking espnotify from ESP 309 Example Creating an Action to Send an E mail 309 Logging Events from Applications and Scripts 313 Event Classification and Sequence Numbers 313 Using the Event Manager API 314 Using the emgrlogger and esplogger Tools 314 Example1 316 Example2 316 Default Event Classes and Types 317 ESP for the Linux OS 317 Default Event Classes 317 Default Event Types 318 ESP for the IRIX OS 321 Default Event Classes 321 Default Event Types 323 ESP Error Codes 383 Generic Errors 383 Event Manager Errors 383 SGM Error Codes 384 ESP Execution Errors 385 List of Figures Figure 1 1 Figure 1 2 Figure 1 3 F
64. Web based Interface Single System Manager Mode 247 Using the Web based Interface System Group Manager Mode 250 Using the Command Line Interface 253 Diagnostic Result Reports 254 Using the Web based Interface Single System Manager Mode 254 Using the Web based Interface System Group Manager Mode 256 Using the Command Line Interface 258 vii Contents Hardware Reports 259 Hardware Inventory Reports 259 Using the Web based Interface Single System Manager Mode 259 Using the Web based Interface System Group Manager Mode 262 Using the Command Line Interface 265 Hardware Changes Reports 266 Using the Web based Interface Single System Manager Mode 266 Using the Web based Interface System Group Manager Mode 268 Using the Command Line Interface 270 Software Reports 271 Software Inventory Reports 271 Using the Web based Interface Single System Manager Mode 271 Using the Web based Interface System Group Manager Mode 275 Using the Command Line Interface 277 Software Changes Reports 278 Using the Web based Interface Single System Manager Mode 278 Using the Web based Interface System Group Manager Mode 280 Using the Command Line Interface 281 System Reports 282 System Inventory Reports 282 Using the Web based Interface 282 Using the Command Line Interface 285 System Changes Reports 286 Using the Web based Interface Single System Manager Mode 286 Using the Web based Interface System Group Manager Mode 288
65. Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 63 63 64 64 63 65 78 78 75 75 ED 75 75 75 75 75 79 75 75 75 75 75 75 75 75 75 75 75 75 2746 2747 2748 2749 2750 2751 3011 3012 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 0 Pixel DMA timeout 1 Pixel DMA timeout 2 Unrecognized flat panel display 1 Unrecognized flat panel display 2 FIFO timeout DMA error o room left in the Xthread Tab le Conflict in the Xthread Table umber of consecutive exception s exceeded limit Exception while saving hardware state Exception during show hardware state Exception during FRU analysis Invalid uncached attribute phy address Data bus error on unknown addre ss retrying Unsupported cache algorithm Process killed access to page with error User Kernel Data Instr Bus erro Access to non existent memory a ddress No write privileges to memory a ddress No read privileges to memory ad dress Write error exception on migrat ing page Unrecoverable VM migration erro r Page with memory directory erro r could not be discarded 1 Write error on poisoned page No spool info on HSPEC buserr Lost Spool info on HPEC buserr error on HSPEC access 0 error on HSPEC access 1 No spool info on MSPEC buserr P P
66. Yes Yes 4000 2097166 Interrupt Yes Yes 4000 2097167 Panic H W Yes Yes 4000 2097168 Panic Yes Yes 4000 2097169 Controlled shutdown unknown Yes Yes 4000 2097170 Controlled shutdown timeout Yes Yes 4000 2097171 Controlled shutdown 1 unknown Yes Yes 4000 2097182 Controlled shutdown 1 Yes Yes 4000 2097183 Controlled shutdown 2 Yes Yes 4000 2097184 Controlled shutdown 3 Yes Yes 4000 2097185 Controlled shutdown 4 Yes Yes 323 Chapter 10 Default Event Classes and Types 324 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 20971 20971 20971 20971 20971 20971 20971 20971 20971 20971 86 87 90 91 92 93 94 95 96 97 3761 3762 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 24 25 26 27 28 29 30 3T 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 Controlled shutdown 5 Controlled shutdown 6 Singleuser shutdown unknown Singleuser shutdown 1 unknown Singleuser shutdown 1 Singleuser shutdown 2 Singleuser shutdown 3 Singleuser shutdown 4 Singleuser shutdown 5 Singleuser shutdown 6 Subscr
67. access list If you specify the disabled option this command lists only the IP addresses that are included in the restrict access list Setting Up the User Permissions Setting Up the User Permissions User permissions provide an additional security layer by enabling you to create individual user accounts within ESP Each user account can have access to different areas of ESP for example one account could have access only to availability reports and a second account could have access to all reports ESP contains one user account by default login administrator password partner The administrator account has full access to all ESP features Note This is no direct correlation between ESP user accounts and normal user accounts on a system Viewing the Current Users You can view a list of all ESP user accounts that are currently available Using the Web based Interface 1 Click onthe ESP Administration button 2 Click onthe User Permissions button The interface shows the list of current users Refer to Figure 3 4 71 Chapter 3 Administering ESP 72 mM esp Er v Embedded Support Partner ver 30 ESP Administration mii Set Environment Configuration Reports Logbook AA User Permissions P View Users Add User Update Password Update Permissions Deleteuser H View Current Users baltic csd sgi com List of current users administrator Figure 3 4 Current User List
68. an Authorization Failed message and ESP does not perform the requested operation Caution Do not change the permissions for the administrator account The administrator account is the main ESP account and should always have full permissions Using the Web based Interface Perform the following procedure to use the Web based interface to update permissions for a user 1 Click onthe ESP Administration button 2 Clickonthe User Permissions button 3 Clickonthe Update Permissions button The interface displays the Update User s Permissions window Refer to Figure 3 8 Setting Up the User Permissions Fi esp Embedded Support Partner verzo f ESP Administration Set Environment Configuration Reports Logbook L User Permissions d P Update Permissions Kj Update User s Permissions administrator Figure 3 8 Update User s Permissions Window Web based Interface 4 Select the user whose permissions you want to update 5 Clickon the Update Permissions button The interface updates the Update User s Permissions window Refer to Figure 3 9 81 Chapter 3 Administering ESP am esp E ud Embedded Support Partner ver 30 V ESP Administration mil Set Environment Configuration Reports Logbook AA View Users Add User Update Password b Update Permissions Deleteuser Z Kj Update User s Permissions User Name administrator Warning All changes take effect immediately Res
69. and date information for archives If you specify one or more archive names this command lists information about those archives If you do not specify an archive name this command displays information about all of the archives on the system Use the following command syntax to delete a database archive usr sbin espconfig drop archive archive name gt 89 Chapter 3 Administering ESP 90 The espconfig command also enables you to initialize the ESP database on your system Warning Initializing the ESP database on a system deletes all data for that system If the system is a group manager initializing the ESP database also deletes information about events on other systems in the group Use the following command syntax to initialize the ESP database on your system to return it to the initial state usr sbin espconfig reconstructdb Use the following command syntax to clean the ESP database tables on your system usr sbin espconfig flushdb sysid system id host lt hostname gt config all Use the sysid option to select a system by system ID Use the nost option to select a system by hostname If you do not specify the sysid or host option this command cleans the database tables on the local system If you do not specify the config or all option this command cleans the ESP data tables on the selected system If you specify the config option this command cleans only the configuration t
70. and the others passed Time at which the diagnostic completed testing When multiple tests run under one diagnostic for example SVP this column indicates the time at which all tests completed Client system on which the action was taken Using the Command Line Interface Diagnostic reports are not available from the command line interface Hardware Reports Hardware Reports There are two types of hardware reports e Hardware inventory reports e Hardware changes reports Hardware Inventory Reports Hardware inventory reports show all hardware installed in a system at a specific date and time Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate a hardware inventory report in single system manager mode 1 Click on the Reports button 2 Click on the Hardware button The interface displays the Hardware Inventory Report window Refer to Figure 6 25 259 Chapter 6 Viewing Reports fap eSp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment Configuration Logbook Ia P inventory Changes Hardware Inventory Report balkan csd sgi com To generate an inventory report of installed hardware for a specific date and time enter correctly formatted date and time values in the fields provided below current date and time values entered by default PREIS 08 13 2003 Time hh mm ss 13 21 40
71. button 3 Click on the Update Password button The interface displays the Update Password for User window Refer to Figure 3 6 Smm esp Embedded Support Partner ver 30 T8 ESP Administration mil Set Environment Configuration Reports Logbook AA User Permissions View Users Add User P Update Password Update Permissions DeleteUser Z Kj Update User s Password baltic csd sgi com List of users administrator Figure 3 6 Update Password Window Web based Interface 77 Chapter 3 Administering ESP 4 Select the user whose password you want to update 5 Clickonthe Update Password button The interface displays the Add User window Refer to Figure 3 5 ap esp ag Embedded Support Partner ver 30 f ESP Administration endl Set Environment Configuration Reports Logbook AA View Users Add User P Update Password Update Permissions Deleteuser A Update Password For User administrator baltic csd sgi com Warning All changes take effect immediately Changing password for a current user will result in the authentication failure You will be asked to provide a new password immediately Old Password New Password Verify Password Commit Figure 3 7 Update Password for User Window Web based Interface 6 Enter the old password for the selected user in the Old Password field 7 Enter the new password in the New Password field Passwords have the following
72. cannot directly access the ESP database ESP limits information returned to SGI with the call logging feature to event specific information ESP does not transmit any customer proprietary information to SGI ESP can encrypt the e mail notifications that it sends System Performance Impact of ESP System Performance Impact of ESP The eventmond and espdbd daemons that ESP uses are event driven and consume CPU resources only when events occur When ESP receives an event the daemons use less than 2 milliseconds of CPU time to process the event and store it in the ESP database The eventmond daemon uses approximately 200 KB of memory to run the espdbd daemon uses approximately 500 KB of memory to run Most of this memory is used to store the system configuration data so the daemons use more memory on larger systems than they do on smaller systems ESP disk utilization depends on the size of the system larger systems require more disk space than smaller systems For example a 64 processor system with 75 to 125 boards uses less than 30 MB of disk space Once a database uses at least 10 MB of disk space you can use the esparchive utility to compress the database to 40 to 60 percent of its original size 33 Chapter 2 Accessing ESP This chapter describes how to use the command line interface and Web based interface to access ESP on your systems It also describes how to configure single system management and system gr
73. connected 5 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 50 38 09 50 38 address Transport endpoint is not connected 6 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 59 30 09 59 30 address Transport endpoint is not connected Figure 6 6 Events Registered in a Specific Class Single System Manager Mode 233 Chapter 6 Viewing Reports 234 2 Click on the i The interface displays all occurrences of the event Refer to Figure 6 7 esp Embedded Support Partner ver 30 d Event Description for the event aA ESP Administration mil Set Environment per EGO Ge Reports Logbook Specific Event Report balkan csd sgi com Class Daemon Messages Event Daemon Error First Occurrence Va 08 13 2003 06 04 20 08 13 2003 06 41 12 08 13 2003 09 06 12 08 13 2003 09 35 44 08 13 2003 09 50 38 08 13 2003 09 59 30 08 13 2003 11 20 10 Figure 6 7 All Occurrences of a Specific Event Single System Manager Mode 08 13 2003 to 08 13 2003 All Classes Last Occurrence Va 08 13 2003 06 04 20 08 13 2003 06 41 12 08 13 2003 09 06 12 08 13 2003 09 35 44 08 13 2003 09 50 38 08 13 2003 09 59 30 08 13 2003 11 20 10 Syslog Message warning can t get client address Transport endpoint is not connected warning can t get client address Transport endpoint is not connected warning can t get client address Transport endpoint is not connec
74. csd sgi com N A ESEKAN Continue Figure 5 1 Event Profile Window System Group Manager AM esp Tg Embedded Support Partner ver 30 a ESP Administration mil Set Environment Reports Logbook AA P Events b Load Profile Add Update Batch Update Delete subscription O Event Profiles balkan csd sgi com ESP Internal Storage TP8100 Storage TP9400 System controller Reload System Defaults Figure 5 2 Event Profile Window 141 Chapter 5 Configuring ESP 142 Use this window as follows To list the events that are contained in a profile click on the profile in the Current Event Profile list and then click on the List Events button To remove a set of events from the current ESP event list click on the profile in the Current Event Profile list and then click on the Remove button To save the current ESP event list in an event profile click on a profile name and then click on the Save button To refresh the list of profiles from the SGM client click on the Re resh A11 Profiles button To add a set of events from an event profile file to the ESP event list click on the profile in the Available Event Profiles list and then click on the Add button Note If the selected system is an SGM client you should click on one of the radio buttons before you click on the Add button Click on the radio button next to Subscribe to subscribe the events in the profile to the SGM serv
75. enter the group name in the System Group field The following three rules apply for creating group names 1 The case of characters does not matter ESP puts systems hat you enter in the groups named Web server and Web Server in the same group 2 Spacing between characters does matter ESP puts systems that you enter in the groups named Web server and Web server in different groups 3 Single and double quotes are not allowed This parameter is optional 115 Chapter 4 Setting Up the ESP Environment Setting Up the System Client Parameters System Group Manager Mode Only The system client parameters enable you to add a new SGM client to an SGM server update system parameters for an SGM server or one of its SGM clients and unsubscribe an SGM client from an SGM server Adding a New SGM Client 1 Click onthe Set Environment button 2 Click on the System button 3 Click on the Add New Client button The interface displays the Add New Client window Refer to Figure 4 13 a esp Embedded Support Partner verzo a ESP Administration mi Set Environment 7 Configuration Reports Logbook AA b Add New Client Update System Client Unsubscribe Delete Client Fl Add New Client Warning SGM Server must be set on the client system before proceeding with client set up Add new ESP 3 0 client C Add new ESP 2 0 client Figure 4 13 Add New Client Window System Group Manager Mo
76. failed H W graph no vertex for io4vhdl H W graph cannot create vertex Unknown input buffer Cannot clear int bit Board seen stray interrupt xcmd ne b2h cqcemd Max b2h cqcomd Cannot destroy fwd vcte 1 Cannot destroy rvc vcte xcmd xmit result warning Cannot destroy fwd vcte 2 s2d register response failed fo E IP Memory TXMT overflow 1 Memory TX overflow on TSR 1 Memory TXMT overflow 2 Memory TX overflow on TSR 2 kmem zalloc error ARP request but not server AAOP ARP request error ARP ta ble full ARP reply error ARP table ful l ARP reply but not server AAOP ARP reply error ARP tabl e full Cannot find IFATM info kmem zalloc error Booting bit not cleared LINC LCSR boot error scmd init no response scmd init failed self test scmd init failed H W graph cannot get vertex Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 343 Chapter 10 Default Event Classes and Types 344 74 74 74 74 74 74 74 74 74 74 74 74 74 74 82 82 82 82 82 82 82 82
77. for a specific event when it registers a specific number of events Example actions include sending an e mail message and sending a page Use ESP to perform the following activities to manage actions on your system View existing actions Add actions Update existing actions Disable actions Viewing the Existing Actions You can use the espconfig command to view the existing actions Use the following command syntax to list event actions It lists the action IDs and action descriptions from the event action fields usr sbin espconfig list evaction Use the following command syntax to view all parameters for an action usr sbin espconfig show evaction acid action id acd action description This command shows the fields in the following format begin eventAction actionId 4 throttle 4 action usr bin espnotify A N DN retryCount 0 timeout 10 user s root actionDescription Notify sysadmin on console disabled NO end eventAction Use the acid option to specify an action ID or use the aca option to specify an action description a string enclosed in quotes 187 Chapter 5 Configuring ESP 188 Adding Actions You can customize ESP by adding new actions Using the Web based Interface Perform the following procedure to use the Web based interface to add actions 1 Click on the Configuration button 2 Clickon the Actions button The interface displays the Add a
78. generate and view reports Note You must use the root account or an account with root privileges to execute the espconfig esplognote and espreport commands 29 Chapter 1 Introduction 30 External Tools The following external tools can generate events e Performance monitoring tools Diagnostic tools e RAID monitoring tools These tools are not part of the ESP package and must be loaded separately Performance Monitoring Tools The performance metrics inference engine application pmie which is included in the Performance Co pilot Execution Only Environment pcp eoe subsystem provides ESP with performance monitoring events pmie is an inference engine for performance metrics It evaluates a set of performance rules at specified time intervals You can use a separate utility to customize and extend the rules and their attributes Refer to the Performance Co Pilot for IA 64 Linux User s and Administrator s Guide publication number 007 4580 00x or the Performance Co Pilot for IRIX User s and Administrator s Guide publication number 007 3965 00x for more information about pmie and the pcp eoe subsystem ESP 3 0 uses a performance monitoring DSO when you configure performance monitoring settings via the ESP user interface or the espconfig command for example usr sbin espconfig on performance or usr sbin espconfig off performance The performance monitoring DSO enables you to e Enable disable PMIECON
79. gt city lt city gt state state province post postal code gt country lt country gt site id site id host host name alias client alias gt sysid lt systemid gt e Use the following command syntax to update an existing customer profile usr sbin espconfig update customer profile fname lt first name gt lname last name gt phone lt phone gt email lt email gt streetl1 street address linel gt street2 street address line2 gt street3 street address line3 gt city city state state province post postal code gt country lt country gt site id site id host host name alias client alias gt sysid lt systemid gt 67 Chapter 3 Administering ESP Setting Up the Network Permissions Network permissions enable you to specify which systems can access the Web server that ESP uses These permissions provide a layer of security to prevent unauthorized systems from accessing ESP data from your systems If you want to restrict access to ESP you must set up a restrict access list and an allow access list If you do not set up a restrict access list all IP addresses can connect to ESP regardless of the allow access list settings because the default configuration allows connections from all IP addresses if no restrict access list exists The most secure configuration is to set the restrict access lis
80. interface displays the Pager Setup window Refer to Figure 4 11 mM esp r i Evi Embedded Support Partner verzo aA ESP Administration mi Set Environment 7 Configuration Reports Logbook AA Paging Modem Setup Service Provider p Paging oo Fl Pager Setup boxelder peachtree sgi com Pager Name 2 Pager ID Service Name h PageSericel Lada Figure 4 11 Pager Parameters Window Web based Interface Setting Up the Paging Parameters ESP for IRIX OS Only 8 Enter a unique name for the pager in the Pager Name field Do not include blank spaces ESP uses this name on other interface pages to identify the pager Enter the pager identification number in the Pager ID field Your paging service provider assigns a unique pager identification number to each individual pager This number could differ from the telephone number that you dial to access the pager Contact your paging service provider to determine the pager identification number of your pager Choose the paging service provider that you want to use from the list of available paging service providers If you do not see the provider that you want to use click on the Service Provider button to add it Click on the Aaa button The interface displays a confirmation window Click on the Commit button Once you have a pager configured you have the following options to modify the parameters when you click on the Service Provider button
81. intermediate server you must log into the client and configure the performance monitoring parameters directly on the client e ESP 2 0 SGM clients are not supported by this procedure To configure performance monitoring on an ESP 2 0 SGM client you must log into the client and configure the performance monitoring parameters directly on the client 1 Click on the Configuration button 2 Click on the Performance Monitoring button Note If the system is an SGM server the interface displays a list of clients Refer to Figure 5 47 Click on the client that you want to use and click on the Cont inue button The interface displays the Performance Monitoring window Configuring Performance Monitoring AM esp ig Embedded Support Partner ver 30 A ESP Administration mil Sau rd v Configuration e Reports E Logbook Performance Monitoring Performance Monitoring System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Figure 5 47 Performance Monitoring Window with SGM Clients 209 Chapter 5 Configuring ESP mM esp E Embedded Support Partner ver 30 a ESP Administration mil Sau rd v Configuration El Reports E FE Logbook Performance Monitoring Peformance Monitoring baltic csd sgi com PMIE Enabled Disabled No PMIE Rule Description PMIE Rule Enabled 1 High aggregate context switch rate cpu context switch Iv 2 Possibl
82. level of the part Installation Date Date that the part was installed Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a hardware inventory report in system group manager mode 1 Clickon the Reports button 2 Click on the Hardware button The interface displays the Hardware Inventory Reports for System Group window Refer to Figure 6 27 Hardware Reports aj esp Embedded Support Partner ver 30 A ESP id mi Set Environment Configuration Logbook AA P inventory Changes Hardware Inventory Report Date oe 3 2003 Time 132733 Sys System Serial Current System Name Type Number IP Address Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi ccom N A 134 16 241 91 Subscribed Continue Figure 6 27 Hardware Inventory Reports for System Group Window System Group Manager Mode 3 Specify the date and time of the hardware inventory that you want to view 4 Specify the system for the hardware inventory that you want to view 5 Click on the Generate Report button Figure 6 28 shows an example hardware inventory report 263 Chapter 6 Viewing Reports Tg Embedded Support Partner ver 30 A ESP Administration Set Environment Configuration Logbook AA Hardware p inventory Changes Hardware Inventory Report baltic csd sgi com Page_1 10 records per page GO Part Serial Installatio
83. ll Q i 22 BQQDI can t get client Transport is not connected can t get client Transport is not connected can t get client Transport is not connected can t get client Transport is not connected Example Report Command Line Interface Event registered reports show all events that ESP has registered within a specific time period Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate an events registered report in single system manager mode 1 Click on the Reports button 2 Click on the 1 The interface displays the Events button Event Reports window Refer to Figure 6 4 229 Chapter 6 Viewing Reports fal nes p Support Partner verzo a ESP Administration mi Set Environment I Configuration E Reports l Logbook E Event Reports 2 C e owns to fonao Kemel Messages Performance Realtime Demo System Configuration User Messages Figure 6 4 Event Reports Window Single System Manager Mode 3 Specify the range of dates for the report 4 Select the event classes that the report should include 5 Click on the Generate Report button 230 Events Registered Reports Figure 6 5 shows an example event report esp Embedded Support Partner ver 30 ESP prec mil Set Environment Configuration E Reports l a Logbook Event Report balkan csd sgi com Class Daemon
84. lt gt 74 Setting Up the User Permissions 5 Enter the password for the user in the Password field Passwords have the following restrictions e Passwords are case sensitive for example Password is different than PAssword e Passwords cannot be more than 126 characters e Passwords cannot include the following characters amp lt gt SPACE Tab 6 Re enter the password for the user in the Verify Password field You must enter the password twice to ensure that it is entered correctly 7 Setthe permissions for the user Table 3 2 describes the permissions Table 3 2 Available User Permissions Permission Description ESP Administration and Enables the user to perform all activities in the ESP Set Environment Administration and Set Environment sections of the interface set up customer profile network permissions user permissions global configuration paging parameters archive settings and SGM settings Configuration Enables the user to perform all activities in the Configuration section of the interface configure events actions performance monitoring and system monitoring Events Actions Enables the user to view all event reports action reports Diagnostics and Site diagnostic reports and site reports Reports Availability Reports Enables the user to view availability reports HW and SW Reports Enables the user to view hardware inventory reports software invent
85. lt pmie rule description parameter to enable specific PMIE rules Use the following command syntax to disable PMIE rules usr sbin espconfig disable performance pd all lt pmie rule description gt Use the a11 option to disable all PMIE rules Use the lt pmie rule description gt parameter to disable specific PMIE rules 215 Chapter 5 Configuring ESP Configuring System Monitoring 216 You can configure ESP to monitor ICMP DNS X Window System server RPCBIND SMTP NNTP and PMCD services on the local system or on other systems in a group ESP uses Performance Co Pilot software tools to monitor the services and to register any events in the Embedded Support Partner database The events belong to the Performance class possible events include System Group Manager service prob failure and System Group Manager slow service respons System monitoring is disabled by default Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to configure system monitoring in single system manager mode 1 Click on the Configuration button 2 Click on the System Monitoring button The interface displays the System Monitoring window Refer to Figure 5 49 Configuring System Monitoring m esp Embedded Support Partner ver 30 aA ESP Administration mil Edad v Configuration Reports Logbook System Monitoring System Monitoring balkan csd sg
86. of ESP e Configuring the Web server e Configuring system groups e Configuring the behavior of tasks e Setting up monitors and associated thresholds e Setting up notifiers e Generating reports for a single system or group of systems ESP Architecture e Accessing system consoles and system controllers e Remotely controlling a system with the IRISconsole multiserver management system The ESP GUI uses the espconfig command to interact with the Event Manager Command Line Interface If you prefer to use a command line interface the Command Line Application CLA software enables you to connect to ESP without using a Web server This enables ESP to be used at a site where the Web server cannot be used for security reasons It also enables ESP to be used over slower remote connections because only text is transferred across the connection The CLA software comprises three components e espconfig e esplognote espreport The espcon ig command enables you to configure ESP espconfig is the main ESP configuration utility It maintains all ESP configuration information in the SSDB and ESP configuration files It performs ESP related operations such as database accesses and Event Manager interactions for example subscribing unsubscribing certain events and producing SGM related events based on command line interface requests The esplognote command enables you to create logbook entries The espreport command enables you to
87. omitted All systems name must be fully qualified hostnames 127 Chapter 4 Setting Up the ESP Environment 128 Table 4 6 Update Client Information Window Parameters ESP 3 0SGM Client continued Parameter Description System group Password Specifies the group to which the client belongs You can use groups to quickly access information about all systems in a group by generating a site report Example group names include Server Desktop Web Server and File Server To create a new group enter the name in the System group field Once you create one or more group names ESP displays a menu of the existing groups to select an existing group choose it from the menu Note When you enter group names the entry in the field takes precedence over the selection in the menu The proper way to create a new group is to set the menu to New Group and enter the group name in the System Group field The following three rules apply for creating group names 1 The case of characters does not matter ESP puts systems hat you enter in the groups named Web server and Web Server in the same group 2 Spacing between characters does matter ESP puts systems that you enter in the groups named Web server and Web server in different groups 3 Single and double quotes are not allowed This parameter is optional Specifies a password that the server and client must exchange before transmitting data to provi
88. parameters that are available 4 Click the Update button Setting Up the System Parameters Single System Manager Mode Only Table 4 3 Update System Information Window Parameters Single System Manager Mode Parameter Description Alias System mode System group Specifies an alias that ESP uses to identify the SGM server This parameter is optional If you do not set this parameter ESP uses the hostname of the client without the domain name This parameter can contain any non blank space character except for single or double quotes Specifies how the system is configured There are two choices SGM and Full node default The SGM option configures the system to be a system group manager system The Full node option configures the system as a single system manager The system does not have any clients Specifies the group to which the system belongs You can use groups to quickly access information about all systems in a group by generating a site report Example group names include Server Desktop Web Server and File Server To create a new group enter the name in the System group field Once you create one or more group names ESP displays a menu of the existing groups to select an existing group choose it from the menu Note When you enter group names the entry in the field takes precedence over the selection in the menu The proper way to create a new group is to set the menu to New Group and
89. root echo quit usr share pcp binitelnet probe HOST 25 4 rpcbind usr sbin rpcinfo p HOST 5oeserver DISPLAY HOST 0 usribin X1 1 xhost 6 dns nslookup HOST lt dev null 7 icmp Ibin ping c 3 f HOST Commit Figure 5 52 System Monitoring Window System Group Manager Mode Note To change the performance monitoring status click on the View by system name System Name baltic csd sgi com baltic csd sgi com baltic csd sgi com baltic csd sgi com Enabled radio button to enable performance monitoring or click on the Disabled radio button to disable performance monitoring and click on the Commit button To perform system monitoring performance monitoring must be enabled 3 Click on the name of the service that you want to monitor The interface displays the Update System Monitoring window Refer to Figure 5 53 Configuring System Monitoring fa esp Embedded Support Partner ver 30 a ESP Administration mi Egan rd v Configuration Reports Logbook System Monitoring Update System Monitoring Service name icmp baltic csd sgi com balkan csd sgi com Figure 5 53 Update System Monitoring Window System Group Manager Mode 4 Click on the systems s that you want to monitor 5 Clickon the Update button The interface displays a verification screen Refer to Figure 5 54 far esp Embedded Support Partner ver 30 ESP i mil Erga Lud v Configuration Reports i BE Log
90. set up the global configuration parameters 1 Click on the Set Environment button 2 Click on the Global Config button Note If the system is an SGM server choose the system for which you want to update the global configuration parameters and click on the Cont inue button Refer to Figure 4 6 The interface displays the Global Configuration window Refer to Figure 4 7 97 Chapter 4 Setting Up the ESP Environment far eSp Um Embedded Support Partner ver 30 a ESP Administration mi Set Environment x2 Configuration Reports Logbook Global Configuration System Name IP Type System Serial Number IP Address All subscribed systems baltic csd sgi com N A N0900155 134 16 241 92 balkan csd sgi com N A N0900156 134 16 241 91 Continue Figure 4 6 Choosing the System to Update the Global Parameters aj esp Embedded Support Partner ver 30 A ESP perm mil Set Environment 7 RA Configuration s Reports E FE Logbook Global Config E Global Configuration baltic csd sgi com Register events Enabled Disabled Throttle events R Enabled Disabled Enable actions E Enabled Disabled Shutdown reason E Enabled Disabled Registration with SGI customer profile S gt Di information is required j Ered 9 Lissie i Compressed amp 3 C E mail format Text Encrypted Warning The following parameters are applicable to all currently subscribed systems Send e mail as E mail text for
91. support personnel to proactively support systems and resolve issues before they develop into actual failures ESP integrates monitoring notifying and reporting operations It enables users to monitor one or more systems at a site from a local or remote connection ESP provides the following functions e Monitoring system configuration events performance availability and services e Providing proactive notification when specific conditions occur e Generating reports about system activity configuration changes events availability etc Sending event information to SGI for statistical interpretation e Providing usability enhancements common interface remote support and system group management Figure 1 1 provides a functional diagram of ESP Chapter 1 Introduction Diagnostic Performance RAID Events Events Events Configuration System Events Events Availability Events User Events E Spi Notifications Event Reports Information Figure 1 1 ESP Functional Diagram This document describes ESP 3 0 which began shipping in SGI ProPack 2 3 and IRIX 6 5 23 Distribution Distribution The ESP software is distributed in two levels e Base package e Extended package Base Package The base package includes the single system manager which has the functionality necessary to e Configure ESP e Monitor a single system for system and performance events configuration changes and av
92. that ESP registered during the time period Information about the total downtime for scheduled and unscheduled downtime count downtime in minutes caused by the action mean time between interrupts in minutes and availability percentage Tip Click on the link to view a report of all scheduled and unscheduled availability events that ESP registered during the time period Average uptime between availability events Shortest uptime between availability events Longest uptime between availability events Average downtime Shortest downtime Longest downtime Date and time that ESP began monitoring availability events Date and time of last system boot Length of time that system has been powered up since last system boot Link to a table of all availability events that ESP registered during the specified time period 249 Chapter 6 Viewing Reports 250 Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate availability reports in system group manager mode 1 Click on the Reports button 2 Clickonthe Availability button The interface displays the Availability Reports For System Group window Refer to Figure 6 19 aes Uu Support Partner verzo a ESP Administration Imi Set Environment OMe EE Reports Logbook Availability Availability Report Last 30 days C Last 7 days C 08 13 2003 to 08 13 2003 IP System Serial Type N
93. that ESP should dial to contact the paging service Enter only numbers in this field for example 17151234567 5 Click on the Add button The interface displays a confirmation window 6 Clickon the Commit button Once you have a paging service provider configured you have the following options to modify the parameters when you click on the Service Provider button e To add a new paging service provider click on the Add button e To update the paging service provider parameters click on the check box next to the service provider name and then click on the Update button e To delete the paging service provider click on the check box next to the service provider name and then click on the Delete button Deleting a paging service provider deletes all pagers assigned to it 111 Chapter 4 Setting Up the ESP Environment 112 Using the Command Line Interface No command line interface commands are available to set up the paging service provider parameters To modify the paging service provider parameters you must manually edit the etc qpage cf file and use the etc init d qpageserver script to start QPage Setting Up the Paging Parameters ESP for the IRIX OS Only You also need to provide information about the pager that you want to use so ESP can properly contact it Using the Web based Interface 1 Click onthe Set Environment button 2 Click on the Paging button 3 Click on the Paging button The
94. the report Sort by this column ascending b 4 pz b p K Sort by this column descending Events Registered Reports Figure 6 3 shows an example report generated by the command line interface root baltic root espreport events cid 7130 from 08 13 2003 to 08 13 2003 vent report bu class for system baltic csd sgi com lasst od poo Type re poe ee 1 Daemon Error poe MMMM 2 Daemon Error poe i i 3 Daemon Error foe ii i i 4 Daemon Error foe root baltic rootl Jj 7130 Daemon Messages First Last too to 08 13 2003 08 13 2003 06 23 55 06 23 55 4 08 13 2003 08 13 2003 06335331 06 35 31 08 13 2003 08 13 2003 09 03 03 09 03 03 to 08 13 2003 08 13 2003 09 09 04 09 09 04 Figure 6 3 Events Registered Reports 4 4 4 4 4 ee iiii i i i i i Syslog message ae iii warning address endpoint a iii iii warning address endpoint a M M M warning address endpoint warning address t endpoint EE S S i P
95. throttling event actions shutdown reason sgmclient client alias sysid system id gt enable mail from lt email address gt emaill lt email address gt email2 lt email address gt disable call_logging event_registration event_throttling event_actions shutdown_reason sgmclient client alias sysid system id gt show call logging event registration event throttling event actions shutdown reason sgmclient client alias sysid system id gt show mail flushdb sysid system id host host name gt config all 39 Chapter 2 Accessing ESP espconfig reconstructdb Performance and System Monitoring Configuration espconfig espconfig on performance off performance list performance status nable disable enable performance pd all lt pmie rule description disable performance pd all lt pmie rule description monitor list lt service name gt monitor show lt service name gt sgmclient lt client alias gt monitor nabl lt service name gt sgmclient lt client alias gt monitor disabl service name sgmclient client alias SGM Related Commands espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig espconfig 40 show systems show sgmclients show sgmservers
96. to unsubscribe and click on the Continue button 131 Chapter 4 Setting Up the ESP Environment m esp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment x4 Configuration Reports Logbook Fl Unsubscribe Delete Client balkan csd sgi com Unsubscribe Unsubscribe and delete all records about this client Commit Figure 4 20 Unsubscribe Delete Client Window 4 Specify if you want to unsubscribe the client or unsubscribe and delete the client ESP 2 0 clients are unsubscribed immediately For ESP 3 0 clients you must commit the unsubscription on a verification screen before ESP will unsubscribe them Note When you unsubscribe an ESP 2 0 client on the server side SGI recommends that you also unregister the server on the ESP 2 0 client side 5 Click on the Commit button 132 Setting Up the Authentication Password Setting Up the Authentication Password You can use authentication between the SGM server and clients to provide stronger security Authentication requires the SGM server to exchange and authenticate a password before any data transactions can occur You must configure the password on the client side and then on the server side Adding a Password for a New Server Perform the following procedure to set up a password on the client side in single system manager mode 1 Clickonthe set Environment button 2 Click onthe sGM Server button 3 Click onthe Add P
97. tout option to update the amount of time in seconds that ESP should wait for the action to execute If the action does not complete execution before the timeout period expires ESP kills the action command Use the throttle option to update the throttling value for the action which specifies the number of times an event must occur before ESP performs the action Use the enable option to enable the action or use the disable option to disable the action 205 Chapter 5 Configuring ESP 206 Disabling and Enabling Actions You can disable actions that you no longer need to use When you disable an action ESP does not execute it when the events to which it is assigned are registered Disabling an action allows you to prevent a specific action from occurring without modifying the individual event action assignments You can also re enable any actions that you disable Note ESP does not allow you to delete actions because deleting an action removes the historical data for the action from the ESP database Using the Web based Interface Perform the following procedure to use the Web based interface to disable an action 1 Click on the Configuration button 2 Click on the Actions button 3 Click on the Enable Disable button The interface displays the view Current Actions window Refer to Figure 5 46 Configuring Actions AM es un Support Partner verzo aA ESP Administration fl Set Environment Reports Logb
98. unknown Uncached Read Access Error to n ode Uncached remote partition Read Access Error to node Uncached partition page Read Ac cess Error to node Uncached read Directory Error t o node Uncached remote partition read Directory Error to node Uncached partition page read Di rectory Error to node Uncached read Poison Access Vio lation to node Uncached remote partition read Poison Access Violation to node Uncached partition page read Po Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 75 75 75 75 75 75 75 45 75 75 75 75 75 75 75 ED TD 75 75 75 75 75 75 75 2985 2986 2987 2988 2989 2990 2991 2992 2993 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 ison Access Violation to node Uncached read Excessiv ACKs t o node Uncached remote partition read Excessive NACKs to node Uncached partition page read Ex cessive NACKs to node Uncached read Response Data Err or to node Uncached remote partition read Response Data Error to node Uncached partiti
99. use the Web based interface to generate a site inventory report from system group manager mode 1 Click on the Reports button 2 Click on the site button The interface displays the Site Reports window Refer to Figure 6 47 ja eS Embedded Support Partner ver 30 ta ESP Administration mi Set Environment Configuration Logbook Site Reports A groups E Please select one or more parameters for the report Leave selection unchanged if you want all parameter s to be included Linux 2 4 20 sgi221c4jlan e tO report 200 MHz Itanium 2 J System information z Generate Report Figure 6 47 Site Reports Window System Reports 3 Select the items to include in the report Choose the groups that you want to include in the report The pulldown menu includes the names of all groups that are available When you choose a group name from the menu the report contains only the systems in the group that you select Choose A11 groups to include all systems in the report Choose the operating system that you want to include in the report The pulldown menu includes the name of all operating systems that ESP detected on the systems When you choose an operating system from the menu the report contains only systems that are running that operating system Choose a processor type The pulldown menu includes all processor types that ESP detected in the systems When you choose a processor type from the menu the report conta
100. va va 1 Performance Low average processor utilization 08 13 2003 send me mail 12 21 12 2 Daemon Messages Daemon Error 08 13 2003 send me mail 12 21 12 Figure 6 16 Example Actions Taken Report System Group Manager Mode Table 6 5 describes the information that the report contains Table 6 5 Actions Taken Report Contents System Group Manager Mode Column Description No Index number in the table Class Class of the event to which the action is assigned Event Description Description of the event to which the action is assigned Time Time and date at that the action was taken Action Taken Description of the command that the action performed Tip Click on an action to view the parameter settings for the action System Name Client system on which the event occurred a This column appears only when reports contain more than one event class b This column appears only on SGM systems when reports contain more than one system 245 Chapter 6 Viewing Reports 246 Using the Command Line Interface Use the following syntax of the espreport command to view an actions taken report usr sbin espreport action taken sysid system id host lt hostname gt from mm dd yyyy to mm dd yyyy Use the sysidor host options to select a specific system to include in the report If you do not specify a system the report contains actions from the local host Note Enter usr sbin esreport sysinfo all to dete
101. which you do not want to delete the action 6 Click on the Commit button Using the Command Line Interface Batch updating is not available from the command line interface 177 Chapter 5 Configuring ESP 178 Deleting Events You can delete custom events that you added to ESP on your system Warning Deleting an event removes all records that are associated with the event from the database After you delete an event you will not be able to retrieve information about any occurrences of the event on your system Using the Web based Interface Perform the following procedure to use the Web based interface to delete an event 1 Click on the Configuration button 2 Click on the Events button 3 Click on the Delete button Note If the system is an SGM server the interface displays a list of clients Refer to Figure 5 25 Click on the client that you want to use and click on the Cont inue button The interface displays the Delete User Events window Refer to Figure 5 26 fp yes p SUUS Partner verzo A ESP Administration mil Set Environment Reports E FE Logbook AA b Events Load Profile Add Update Batch Update P Delete subscription O Delete Event System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Continue Figure 5 25 Delete User Events Window with SGM Clients Configuring Events
102. 00A Piece failed 0x2006 Virtual disk failed interrupt ed write 0x2005 ESM miswire 0x1510 Channel miswire 0x150F Controller loop back diagnostic s failed 0x150E Unresponsive drive bad AL PA e rror 0x150A Fibre channel link errors thres hold exceeded 0x1207 Incorrect mode parameters set o n drive 0x1015 Impending drive failure PFA d etected 0x1010 Drive returned CHECK CONDITION 0x100A Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 357 Chapter 10 Default Event Classes and Types 358 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3234 3233 3232 3231 3256 3314 3313 3312 3311 3310 3309 3308 3307 3306 3305 3304 3303 3302 3301 3300 3299 3298 3297 3296 3295 Drive write failure retries e xhausted 0x1006 Drive read failure retries ex hausted 0x1005 Drive error tally exceeded thre shold 0x10 Channel failed 0x10 O O Controller cache battery failed 0x210C Sys wipe request received by al ternate controller 0x40 Sys wipe request sent to con ller
103. 08 ESP for the IRIX OS 3570 3569 3568 3567 3566 3565 3564 3563 3562 3561 3560 3559 3558 3557 3556 3555 3554 3553 3552 3551 3550 3549 3548 3547 3546 Subsystem quiescence started 0 x4007 Alternate controller quiescence started 0x4006 Controller quiescence started 0x4005 Alternate controller quiescence message received 0x400 NVSRAM clear request received b y alternate controller 0x4003 NVSRAM clear request sent to al ternate controller 0x4001 VKI commom error 0x3200 Deferred error EEL 0x3102 AEN posted for recently logged event 0x3101 Environmental card firmware dow nload completed 0x301E Environmental card firmware dow nload started 0x301C Drive firmware download complet ed 0x301B Set pass command issued 0x3018 Set pass through issued 0x3017 Alternate controller transition issued 0x3016 Drive pass through issued 0x30 15 Drive firmware download started 0x3014 Download controller firmware is sued 0x3013 Write Buffer 0x3012 Defect list received 0x3011 ode select for hot spare page 3A received 0x3010 ode select for time page 2F re ceived 0x300F ode select for vendor unique c ache page 2E received 0x300E ode select for redundant contr oller page 2C received 0x300D
104. 0x40 VKI panic 0x3201 nload failed 0x301D Drive firmware download failed 0x301A Volume ownership changed due to failover 0x3019 Drive by passed 0x2823 ESM firmware mismatch 0x281E Temperature sensor removed 0x2 81D Maximum temperatur xceeded x281C Nominal temperatur xceeded x281B Tray ID mismatch duplicate ID S in same drive tray 0x2818 Tray ID conflict duplicate ID S across drive trays 0x2816 GBIC failed 0x2815 ini hub canister failed 0x281 ESM loss of communication 28 charged 0x280 Drive tray component failed 3 0 OF Standby power source not fully OE 0 280D Controller tray component faile d 0x280B Controller tray component missi ng 0x280A OG c H O Environmental card firmware dow Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 3294 Tray ID not unique 0x2808 Yes Yes 32 93 ESM Failed 0x2807 Yes Yes 3292 UPS battery two minutes to fail Yes Yes ure 0x2803 3291 Storage Array running on UPS ba Yes Yes ttery 0x2801 3290 Recoverable erro
105. 0x560 361 Chapter 10 Default Event Classes and Types 362 81 81 81 81 81 81 81 81 81 CO OO CO CO OO CO co 81 81 81 81 81 81 81 81 81 81 81 3647 3646 3645 3644 3643 3642 3641 3640 3639 3638 3637 3636 3635 3634 3633 3632 3631 3630 3629 3628 3627 3626 3625 3624 3623 3622 3621 3620 3619 This controller s alternate pas sed diagnostics 0x5601 Controller passed diagnostics 0x5600 Premium feature disabled 0x540 1 Premium featur nabled 0x5400 Change volume to LUN mapping x5211 Delete volume to LUN mapping 0 x5210 Create volume to LUN mapping 0 x520F Move Storage Array port 0x520E Delete Storage Array port group 0x520D Create Storage Array port group 0x520C Set host port type 0x520B Move host port 0x520A Rename host port 0x5209 Delete host port 0x5208 Create host port 0x5207 Move host 0x5206 Rename host 0x5205 Delete host 0x5204 Create host 0x5203 Rename host group 0x5202 Delete host group 0x5201 Create host group 0x5200 Create mirror relationship 0x5 033 Change synchronization priority 0x5032 Deactivate remote mirroring 0x 5031 Activate remote mirroring 0x50 30 Increase volume capacity 0x502 B Assign volume ownership 0x502A Reset controller battery age 0 Bom
106. 110 111 112 113 114 115 116 Description No such subscription Address resolution error Event translation error Operation timeout No such file No administrative permissions Description System error Lower layer error Event allocation error Timeout Delivery error Invalid format Invalid parameter value Invalid response ID No response ID No subscription status Database error File access error File save error No system information No site information Tool table information missing No profile information ESP Execution Errors Code 117 118 119 120 121 122 123 124 125 126 127 128 ESP Execution Errors Code 200 201 202 203 204 205 206 207 208 209 210 Description hinv table information missing No SGM information Invalid system role No peer information System is unreachable Already subscribed New role is incompatible No such SGM No license Invalid Destination SGM no response Authorization failure Description Memory allocation error Processing error Event profile read error Event profile entry error Unknown section Incomplete definition Invalid event type definition Invalid event action definition Duplicate system Invalid system ID Duplicate event attribute 385 Chapter 11 ESP Error Codes 386 Code 211 212 213 214 215 216 217 218 219 220 221 222 223 224 Description Missing system serial number Registration event Availability clas
107. 2 Figure 3 13 Figure 4 1 Figure 4 2 Figure 4 3 Figure 4 4 Figure 4 5 Figure 4 6 Figure 4 7 Figure 4 8 Figure 4 9 Figure 4 10 Figure 4 11 Figure 4 12 Figure 4 13 Figure 4 14 Figure 4 15 Figure 4 16 Figure 4 17 Figure 4 18 Figure 4 19 Figure 4 20 Figure 4 21 Update Password for User Window Web based Interface 78 Update User s Permissions Window Web based Interface 81 Updated Update User Permissions Window Web based Interface 82 Delete User Window Web based Interface 85 Updated Delete User Window Web based Interface 86 Delete Archive Window Web based Interface 88 Delete Archive Verification Screen 89 Linux System SN Button 92 Add Linux System Serial Number Window Single System Manager Mode 93 Add Linux System Serial Number Verification Window Single System Manager Mode 94 Linux System SN Window SGM Server that has One Client without a Serial Number Entered 95 Linux System SN Window SGM Server that has Multiple Clients without Serial Numbers Entered 96 Choosing the System to Update the Global Parameters 98 Global Configuration Window Web based Interface 98 Process for Sending a Page 105 Modem Parameters Window Web based Interface 108 Paging Service Provider Pager Web based Interface 110 Pager Parameters Window Web based Interface 112 Update System Information Window Single System Manager 114 Add New Client Window System Group Manager Mode 116 Add New Client Window f
108. 3266 3265 3264 3263 3262 3261 3260 3259 3258 3257 3674 3673 3672 3671 3670 3669 3668 3667 3666 3665 47 Partially reconstructed drive m arked optimal 0x223F Drive reinserted 0x223C Drive manually failed 0x222D Drive failed by controller 0x2 229 Drive spun down 0x2226 Duplicate data structure exists for two devices 0x2223 Piece failed during uncompleted write processing 0x2218 Piece failed 0x2217 Piece taken out of service 0x2 216 Drive marked failed 0x2215 Parity repaired 0x2212 Memory parity ECC error 0x2118 Controller cache memory initial ization failed 0x2110 Controller cache memory parity error detected 0x210F Controller cache memory recover y failed after power cycle or r eset 0x210E Communication to remote volume up 0x6502 Remote volume deleted 0x6501 Remote volume created 0x6500 Mirrored pair changed to optima 1 0x6404 Mirror repository volume delete d Mirror repository volume create d Diagnostics rejected download is in progress Running diagnostics on this con troller Diagnostics initiated from this controller 0x6301 0x6300 0x561F 0x561E 0x561D Diagnostics rejected both con trollers must be in active mode 0x561C Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
109. 4Suite 0 11 2 02 26 2003 3 5b2 Xx 3 Canna libs 50 45211 06 13 2003 The runtime library for Canna 0 8 CpuMemSets processor and sgi221c1 06 19 2003 memory placement utilities CpuMemSets 0 8 The development option for 5 devel sgi221c1 06 19 2003 CpuMemSets 6 Distutils 1 0 2 2 02 26 2003 Python distribution utilities A debugger which detects memory 7 ElectricFence 2 2 2 8 02 26 2003 allocation violations Development library and header Peete files for FreeVVnn 9 FreeV nn libs 1 11 19 02 26 2003 A runtime library for FreeVVnn 10 GConf 1 0 4 3 02 26 2003 The Gnome Config System 4 CpuMemSets 8 FreeWnn devel 1 11 19 Figure 6 34 Example Software Inventory Report Single System Manager Mode 273 Chapter 6 Viewing Reports Table 6 14 describes the contents of the report Table 6 14 Software Inventory Report Contents Single System Manager Mode Column Heading Description No Index number within the table Software Name Name of the software application Version Version number of the software application Installation Date Date on which the software application was installed Software Description Brief description of the software 274 Software Reports Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a software inventory report from system group manager mode 1 Click on the Reports button 2 Cl
110. 71310142003 10 14 2003 10 14 2003 r deiter 14581710142003 10 14 2003 10 14 2003 DM deiter 15014810142003 10 14 2003 10 14 2003 r deiter 15025510142003 10 14 2003 10 14 2003 I deiter 15061710142003 10 14 2003 10 14 2003 r deiter 15435010142003 10 14 2003 10 14 2003 I deiter_15480610142003 10 14 2003 10 14 2003 r deiter 15194410022003 10 2 2003 10 2 2003 D deiter 13434310032003 10 3 2003 10 3 2003 F deiter 12243110132003 10 3 2003 10 13 2003 Delete Archive Figure 3 12 Delete Archive Window Web based Interface 3 Click on the check box next to the name of the database archive that you want to delete 4 Click onthe Delete Archive button The interface displays a verification screen Refer to Figure 3 13 88 Manipulating Database Archives P6 esp Embedded Support Partner ver 30 f ESP Administration mil Set Environment Configuration Reports E Be Logbook Fl Delete Archive deiter csd sgi com The following archive will be deleted e deiter 14261210142003 Commit Figure 3 13 Delete Archive Verification Screen 5 Click on the Commit button Using the Command Line Interface You can use the espconfig command to view information about the available database archives and to delete a specific database archive Use the following command syntax to view the available database archives usr sbin espconfig list archive archive name archive name gt This command displays the name
111. 75 75 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 67 402 404 405 338 177 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 343 344 345 346 347 348 349 350 351 352 299 Cac Cac Cac Cac Cac Cac Cac Cached read hed partition page n Excessiv ve NACKs Excessive NACKs NACKs hed read Respons hed remote partition Respons e Data Erro hed partition page Response Data Error Auto Auto Auto Auto Auto Auto Fan Fan Fan Power high fault power power power power power hed remote parti hed read Packet Environment redundancy lost Environmental redundancy lost down down down down down Data Error tion Packet ength Error hed partition page Packet Le ngth Error ength Error in 3 in 2 in 2 in 1 xn Il 0 5 0 5 0 power down in 5 1 warning 2 warning 3 warning Fan 1 fault Fan 2 fault Fan 3 fault Fan limi limi limit limit limi limi l RPM s Fan 2 RPM s Fan 3 RPM s Power low fault Power high warning lim Power low warning Fan fault Fan warning Temperature fault Temperature critical limit reac limi limi limi limi limi limit CFT seconds seconds Seconds seconds seconds seconds reached reached reached reached reached reached abilized abilized
112. 80 80 3177 3176 3175 3174 3173 3172 SLAE 3170 3169 3168 3167 3166 3165 3164 3163 3162 3161 3160 3159 3158 3157 3156 S155 A logical drive has been delet d 149 A logical drive has been found 148 Logical drive initialization ca ncelled 146 Logical drive initialization do ne 145 Logical drive initialization st arted 144 Rebuild on logical drive is can celled 140 Rebuild on logical drive is ove r 139 A manual rebuild has started on logical drive 138 Logical drive has been placed o nline 136 Consistency check is cancelled 130 Consistency check is finished 129 Consistency check is started 128 Physical drive is switching fro m a channel to the other channe l4 59 Rebuild startup failed due to 1 ower disk capacity 58 as hysical device negotiated diff erent bus width than config 5 6 Physical device negotiated diff erent offset than config 55 Physical device ID did not matc h 53 Physical device status changed to rebuild 52 Physical device status changed to Hot Spare 51 Physical device status changed to offline 50 Initialization canceled 32 Initialization completed 30 Initialization started 29 353 Chapter 10 Default Event Classes and Types 354 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
113. Changes Report Contents Single System Manager Mode 279 Table 6 17 Software Changes Report Contents System Group Manager Mode 281 Table 6 18 System Changes Report Contents Single System Manager Mode 287 Table 6 19 System Changes Report Contents System Group Manager Mode 289 Table 8 1 Example Action Parameters for Sending an E mail Notification 310 XX What s New in this Document Revision 009 makes the following changes to this document e It adds information about the version of ESP 3 0 that runs under the IRIX operating system e It updates the document to include changes from the IRIX 6 5 23 and SGI ProPack 2 4 releases e It updates the descriptions of the Web based interface throughout the document e It incorporates miscellaneous technical and editorial changes throughout the document This revision supports the IRIX and Linux operating system versions of ESP 3 0 that are included in the IRIX 6 5 23 and SGI ProPack 2 4 releases respectively xxi Chapter 1 Introduction The SGI product line ranges from desktop workstations to supercomputers which makes it one of the broadest product lines in the industry Supporting such a diverse product line creates many challenges Embedded Support Partner ESP was created to address some of these challenges by automatically detecting system conditions that indicate potential future problems and notifying the appropriate personnel This enables SGI customers and
114. Click on the Reports button 2 Click on the Software button 3 Click on the Inventory button The interface displays the Software Inventory Report window Refer to Figure 6 33 271 Chapter 6 Viewing Reports S eSp ag Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Configuration Logbook AA p inventory Changes 8 Software Inventory Report balkan csd sgi com To generate an inventory report of installed software for a specific date and time enter correctly formatted date and time values in the fields provided below current date and time values entered by default IIR UT 08 13 2003 Time hh mm ss 13 50 19 Generate Report Figure 6 33 Software Inventory Report Window Single System Manager Mode 4 Specify the date and time of the software inventory that you want to view 5 Clickonthe Generate Report button Figure 6 34 shows an example software inventory report 272 Software Reports z mM esp Um Embedded Support Partner ver 30 a ESP Administration mi Set Environment Configuration Logbook AA b Software P inventory changes Software Inventory Report balkan csd sgi com 10 records per page GO Installation Date Software Description No Software Name Version Python tools and libraries for XML processing and databases 3 5b2 Header file and library for 2 Canna devel gt 06 13 2003 developing programs which use 50 as21 1 Canna 1
115. ESM communication restored 0 x2810 Drive tray component changed to ESP for the IRIX OS 3521 3520 3519 3518 3517 3516 3515 3514 3513 3512 3511 3510 3509 3508 3507 3506 3505 3504 3503 3502 3501 3500 3499 optimal 0x28 Controller tray component ch ed to optimal 0x28 Tray component change 0x280 Controller tray component ch e detected 0x28 Not Used 0x28 UPS battery is fully charged x28 Power supply state change de ted 0x280 Start of day routine complet 0x26 Default volume created 0x26 Automatic controller firmwar ynchronization completed 0x Automatic controller firmwar ynchronization started 0x26 Controller mode switch occur 0x25 Controller mode changed to a ve 0x25 Controller mode changed to p ive 0x25 Controller icon chip error 5 Controller mode changed to a ve 0x25 Hot swap monitor detected dr insertion 0x24 Hot swap monitor detected dr removal 0x24 Immediate availability initi 05 03 es 260 1 es 00 red 05 cti 04 ass 3 x2 2 cti 01 ive 01 ive 00 ali O OO zation IAF started on volume 0x22 Initialization started on vo e 0x22 Modification reconfigure c leted on volume 0x22 Modification reconfigure s ted on volume 0x22 Copyback completed on volume x22 Volume group or volume modif
116. ESP actions that are assigned to the events All processing done is based on configuration information from the ESP database The ESP startup script starts this DSO as a task of the Event Manager daemon eventmond The DSO stores event information in the SSDB and uses the espnotify utility to generate notifications SGM DSO The SGM DSO provides distributed functionality among a group of ESP systems The Event Manager loads and executes this DSO when there are SGM specific events to handle There is no need to load and execute this DSO during the startup sequence The SGM DSO serves as a router translator for remote ESP configuration requests When an SGM server needs to configure an SGM client it sends an ESP SGM event via the Event Manager API This event has an SGM DSO as a consumer when an SGM DSO receives these events it either performs a routing forwarding producer operation if the event needs to go to a remote system or executes the specified operation and sends the result back to the SGM server SGM DSO functionality requires a license ESP Architecture Monitoring Software A key function of ESP is monitoring the system The ESP base package includes software that enables the following types of monitoring on a system e Configuration monitoring e Event monitoring e Availability monitoring Monitoring is performed by tools that run as stand alone programs or as DSOs and send events to the Event Manager The Event Manage
117. Embedded Support Partner User Guide Document Number 007 4065 009 CONTRIBUTORS Revised by Darrin Goss Production by Karen Jacobson Engineering contributions by the System and Site Support Tools Group COPYRIGHT 1999 2000 2001 2002 2003 Silicon Graphics Inc All Rights Reserved This document contains proprietary and confidential information of SGI The contents of this document may not be disclosed to third parties copied or duplicated in any form in whole or in part without the prior written permission of SGI LIMITED RIGHTS LEGEND Use duplication or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision c 1 ii of the Rights in Technical Data and Computer Software clause at DFARS 52 227 7013 and or in similar or successor clauses in the FAR or in the DOD or NASA FAR Supplement Unpublished rights reserved under the Copyright Laws of the United States Contractor manufacturer is SGI 1500 Crittenden Lane Mountain View CA 94043 TRADEMARKS AND ATTRIBUTIONS Silicon Graphics SGI Challenge InPerson IRIX O2 Octane Onyx Onyx2 Origin and the SGI logo are registered trademarks and Altix CASEVision Key O Matic Performance Co Pilot and Supportfolio are trademarks of Silicon Graphics Inc in the United States and or other countries worldwide CrayLink is a trademark of Cray Inc Linux is a registered trademark of Linus Tor
118. F at the global level performs chkconfig pmie onor chkconfig pmie off e Enable disable specific PMIE rules You can use the ESP user interface or the espconfig command to configure performance monitoring Remote Support Capability Diagnostic Tools The support tools included in the Internal Support Tools 2 0 CD and later releases can also interface with the ESP framework If you install the Internal Support Tools 2 0 CD or alater release ESP collects data from the diagnostic tools that are included on the CD Refer to the CD booklet for installation instructions for the support tools Note The Internal Support Tools CDs are available only to SGI support personnel for example System Support Engineers RAID Monitoring Tools Starting with IRIX 6 5 17 ESP receives RAID events from the TP9100 and TP9400 disk subsystems The following software enables ESP to receive these events e The tpmwatch application monitors the TP9100 disks and writes RAID events to the tpmwatch log e The tpssm7monitor for T9400 releases 3 and 4 and tpssmmonitor for TP9400 release 5 daemons monitor the TP9400 disks and write RAID events to the Major Event Log MEL e A script checks the tpmwatch log and MEL for new events and uses esplogger to send the events to ESP e The Storage_TP9100 espand Storage TP9400 esp ESP event profiles specify the RAID events that ESP should register Refer to the tp9100esptool User Guide publication number 007
119. I command abort SCSI command timeou A hard disk has Hard disk erro Rebuild stopped bec drive Rebuild stopped wit device Rebuild stopped wit because of g processor because devi ce is missing 36 because doub because SCSI because writ imed out 3 9 because of b device 38 37 occurred 3 5 failed 34 failed 33 failed 31 available 28 reset 25 found 24 23 found found 22 d on hard di Sk 21 on hard disk 20 t on hard de vice 19 failed 12 r found 3 ause logical failed 11 h error New Failed 10 h error 9 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 3020 3019 3018 3017 3230 3229 3228 3227 3226 3225 3224 3223 3222 3221 3220 3219 3218 3217 321 321 321 321 321 NU kb oO oO 321 3210 bh 3209 3208 3207 3206 3205 3204 3203 Rebuild is cancelled 8 Rebuild is over 7 An automat
120. L and O penGL at the same time 1 Process attempting IrisGL and O penGL at the same time 2 Unrecognized command Lost clip id 1 Lost clip id 2 Lost clip id 3 Process not bound to rn Swapbuffer timeout Retrac vent timeout Board manager failed to flush F IFO FCG error FIFO overflow Unrecognized interrupt FIFO timeout Deactivation timeout DMA timeout Pickfeed timeout Vcstage timeout Hardware incompatibility 1 Hardware incompatibility 2 Illegal hardware configuration RM4 1 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yos Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Tes Yes Yes Yes Yes Yes Yes Yes Yes 335 Chapter 10 Default Event Classes and Types 336 27 27 57 57 57 58 58 59 60 60 61 60 60 61 61 61 61 60 60 59 60 62 60 59 59 61 60 60 62 60 99 29 59 59 59 60 61 62 60 61 2706 2707 2708 2709 2710 271 271 271 271 Z3 271 271 271 271 2720 2721 2722 2723 2724 2725 2726 2123 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 c 10 01 WN ES Xe l
121. Messages First Last Event Occurrence Occurrence No Description va va Count Syslog message 1 Daemon Error 08 13 2003 08 13 2003 1 warning can t get client 06 04 20 06 04 20 address Transport endpoint is not connected 2 Daemon Error 08 13 2003 08 13 2003 warning can t get client 06 41 12 06 41 12 address Transport endpoint is not connected 3 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 06 12 09 06 12 address Transport endpoint is not connected 4 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 35 44 09 35 44 address Transport endpoint is not connected 5 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 50 38 09 50 38 address Transport endpoint is not connected Figure 6 5 Example Events Registered Report Single System Manager Mode 231 Chapter 6 Viewing Reports 232 Table 6 2 describes the information that the report contains Table 6 2 Events Registered Report Contents Single System Manager Mode Column Heading Description No Class Event Description First Occurrence Last Occurrence Event Count Syslog message Index number within the table The class that contains the event Tip Click on an event class to view a report of all occurrences of events in that class Brief description of the event Tip Click on an event description to view a report of all occurrences of that event Date and time at which the event was first re
122. Mode 295 View Logbook Entries Window System Group Manager Mode 296 Specified Logbook Entries System Group Manager Mode 296 Logbook Entry Information System Group Manager Mode 297 Create Log Window Single System Manager Mode 298 Logbook Entry Confirmation Window Single System Manager Mode 299 Completed Logbook Entry Single System Manager Mode 300 Create Log Window System Group Manager Mode 301 Logbook Entry Confirmation Window System Group Manager Mode 302 Completed Logbook Entry System Group Manager Mode 303 Displaying a Message in the Console Window 306 Displaying a Message on an X Window System Display 307 Sending an E mail Message 309 Example Action Parameters for Sending an E mail Message 310 Example Verification Message for Sending an E mail Message Action 311 Example Confirmation Message for Sending an E mail Message Action 311 xvii List of Tables Table 1 1 Table 2 1 Table 3 1 Table 3 2 Table 3 3 Table 4 1 Table 4 2 Table 4 3 Table 4 4 Table 4 5 Table 4 6 Table 4 7 Table 5 1 Table 5 2 Table 5 3 Table 5 4 Table 6 1 Table 6 2 Table 6 3 Table 6 4 Table 6 5 Table 6 6 ESP Benefits 12 ESP Startup Error Messages 42 Customer Profile Parameters 65 Available User Permissions 75 Command Line Interface User Permission Settings 84 Global Configuration Parameters 99 Paging Service Provider Parameters 111 Update System Information Window Parameters Single System Manag
123. Mode Select lock 0x560B This controller s alternate fai led timeout waiting for resul ts 0x5602 Feature Enable Identifier chang ed 0x5404 Premium featur xceeds limit 0x5403 Premium feature out of complian ce 0x5402 Yes Yes Yes Yes Tes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 3317 3316 3315 3255 3254 3253 3252 325i 3250 3249 3248 3247 3246 3245 3244 3243 3242 3241 3240 3239 3238 3237 3236 3235 Error writing configuration 0x 5212 Fail drive 0x5006 Place controller offline 0x500 5 Cache between controllers not s ynchronized 0x210B Controller cache not enabled cache sizes do not match 0x210 9 Data parity mismatch detected o n volume 0x2034 Parity reconstructed on volume 0x2033 Read drive error during interru pted write 0x202E Virtual disk failed during inte rrupted write 0x2021 Piece failed during interrupted write 0x2020 Uncompleted writes detected in NVSRAM at start of day 0x2015 Unwritten data parity recovered from cache 0x2013 Unrecovered deferred error on v olume 0x200B Data parity mismatch on volume 0x2
124. Notification priority S information message 3 Execute action as E nobody Action timeout eoo second s Continue Figure 5 32 Add an Action Window Using Notification Action Option 189 Chapter 5 Configuring ESP 190 Perform the following procedure to use this window to create an action 1 Enter a description for the action ESP displays this description on other pages of the interface Select the type of notification that you want to create e mail notification system console notification or GUI pop up notification Select the priority of the notification Enter the user account that will execute the command The default is the nobody account Enter the amount of time that ESP should wait for the action to execute timeout value If the action does complete within this period of time ESP kills the action Click on the Continue button e Ifyou selected e mail notification ESP displays the window shown in Figure 5 33 e Ifyou selected notify on console ESP displays the window shown in Figure 5 34 e Ifyouselected GUI pop up notification ESP displays the window shown in Figure 5 35 Configuring Actions sr esp Mod Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Z Configuration E Reports 3 Logbook P Actions EJ Add Notification Action LI LJ pC Po v v v L E E E x x r oon Figure 5 33 Add an Action Window Usin
125. Page Single System Manager Mode 47 Chapter 2 Accessing ESP esp Embedded Support Partner ve 5o rm ESP Administration mil Set Environment I Configuration z s 3 Logbook f System Information Figure 2 4 ESP Main Page System Group Manager Mode 48 Using the Web based Interface Using the Embedded Support Partner Icon ESP for the IRIX OS Only Perform the following procedure to use the Embedded Support Partner icon to start the ESP Web based graphical interface 1 Choose Find gt Support Tools in the Toolchest menu Refer to Figure 2 5 Desktop D Selected internet rj Search For Files File QuickFind Host QuickFind Datatranstators Demos DesktopTools DeveloperMagic 5 MediaTools Printing SupportTools WebTools WhatsNew Figure 2 5 Toolchest Menu 49 Chapter 2 Accessing ESP The Icon Catalog application opens to the Support Tools category Refer to Figure 2 6 Figure 2 6 Icon Catalog 2 Double click on the Embedded Support Partner icon Netscape displays the ESP opening page Refer to Figure 2 7 50 Using the Web based Interface tut deiter csd sgi com J Embedded Support Partner Figure 2 7 ESP Opening Page 3 Specify the system that you want to access e To connect to the local system click on the login button e To connect to a remote system enter the system name or IP address in the hostname box and click on the 1ogin button
126. S 6 AC fail lost r Yes Yes edundancy 67 434 Power Bay DPS 1 fail lost redu Yes Yes ndancy 67 435 Power Bay DPS 2 fail lost redu Yes Yes ndancy 67 436 Power Bay DPS 3 fail lost redu Yes Yes ndancy 67 437 Power Bay DPS 4 fail lost redu Yes Yes ndancy 67 438 Power Bay DPS 5 fail lost redu Yes Yes ndancy 67 439 Power Bay DPS 6 fail lost redu Yes Yes ndancy 67 440 Power Bay DPS 1 predictive fail Yes Yes 67 441 Power Bay DPS 2 predictive fail Yes Yes 67 442 Power Bay DPS 3 predictive fail Yes Yes 67 443 Power Bay DPS 4 predictive fail Yes Yes 67 444 Power Bay DPS 5 predictive fail Yes Yes 67 445 Power Bay DPS 6 predictive fail Yes Yes 69 2836 Cannot bring up board Yes Yes 342 ESP for the IRIX OS 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 69 70 71 Mel 71 71 72 72 72 72 72 T2 73 73 74 74 74 74 74 74 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 Timeout reached wait HCA Memory cannot post small buffs Memory cannot post medium buffs Memory cannot post large buffs ATM init had duplicate unit ID Cannot kmem zalloc Cannot kvpalloc HCA area Cannot kvpalloc CMDQ Cannot kvpalloc B2H Cannot allocate stats area dang intr conn
127. Then the ESP software on the group manager system registers the events logs the events in its database and performs any actions assigned to the events This process creates a central repository of data on the group manager system which enables you to access information about all of the systems in the group from a single interface Be aware of the following requirements as you configure group management e Although you can subscribe to any events that are recognized on group member systems the systems forward only the events that have event registration enabled Globally disabling event registration on a group member system disables event forwarding for all events on that system Disabling an individual event registration on a group member prevents the group member system from forwarding that event to the group manager system e Event forwarding is an internal ESP action so you must enable ESP actions on group member systems to forward events to the group manager system Onagroup manager system ESP stores event settings on a per host basis There are separate sets of events for each member of the group Disabling global or individual event registration on the group manager does not propagate to the group members systems if a group member attempts to deliver an event that is disabled on the group manager the event is delivered to the group manager and then the event is discarded If you no longer need an event from a member system you sh
128. Web based Interface Using the Command Line Interface Use the following syntax of the espcon ig command to view a list of current users usr sbin espconfig list user name lt username gt If you include the name option this command displays information about a specific user If you do not include the name option this command lists all users Setting Up the User Permissions Adding a User Any user with the ESP Administration and Set Environment permission can add new users and configure access permissions for them Using the Web based Interface Perform the following procedure to use the Web based interface to add a user 1 Click onthe ESP Administration button 2 Click onthe User Permissions button 3 Click on the Add User button The interface displays the Add User window Refer to Figure 3 5 73 Chapter 3 Administering ESP fa esp gt i Embedded Support Partner ver 30 u ESP Administration mil Set Environment Co tion El Reports jE Logbook P User Permissions Kj Add User D D Po D a P P E a a Figure 3 5 Add User Window Web based Interface 4 Enter the login name for the user in the User Name field User names have the following restrictions e User names are case sensitive for example User is different than USer e User names cannot be more than 126 characters e User names cannot include the following characters amp
129. Window with SGM Clients The interface displays the Event Batch Update window Refer to Figure 5 24 173 Chapter 5 Configuring ESP aM esp Mod Embedded Support Partner verzo aA ESP Administration mil Set Environment Z Configuration EI Reports 3 Logbook P Events Event Batch Update Figure 5 24 Event Batch Update Window 174 Configuring Events 5 Click on the radio button next to the batch operation you want to perform Table 5 1 describes the batch operations and the procedure to use each operation Table 5 1 Batch Update Options Option Description Update events parameters Search by class Update action frequency Search by action Update action frequency Search by class Updates the event parameters for an entire class of events Perform the following procedure 1 Click on the Continue button 2 Choose the class of events that you want to update 3 Click on the Update button 4 Update the Event Status and Registration with SGI values 5 Click on the Update button 6 Click on the Commit button Updates the action frequency for multiple events Perform the following procedure 1 Click on the Continue button 2 Click on the action that you want to update 3 Click on the Cont inue button 4 Uncheck the checkmark for any event classes that you do not want to update or click on a class description to update actions assigned to individual events i
130. Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 81 3664 3663 3662 3661 3660 3659 3658 3657 3656 3655 3654 3653 3652 3651 3650 3649 3648 Diagnostics rejected data tra nsfer on this controller s alte rnate is not disabled quiesced 0x561B Diagnostics rejected data tra nsfer on controller is not disa bled quiesced 0x561A Diagnostics rejected no cache memory on this controller s al ternate 0x5619 Diagnostics rejected no cache memory on controller 0x5618 Not Used 0x5615 A host side port link has bee n detected as down 0x5614 Diagnostics loopback test ident ified bad destination channel s 0x5613 This controller s alternate pas sed diagnostics but loopback t st identified an error on loop s 0x5612 Controller passed diagnostics but loopback test identified an error on loop s 0x5611 Diagnostics rejected access v olume UTM is not enabled 0x56 0A Diagnostics unable to select a drive for I O 0x5609 Diagnostics rejected test ID is incorrect 0x5608 Diagnostics returned unknown Re turnCode 0x5607 Diagnostics rejected ctlrDiag task unable to queue DIAG INIT MSG message 0x5606 Diagnostics rejected error oc curred when sending the Icon me ssage 0x5605 Diagnostics rejected this con troller s alternate is absent r failed 0x5604 Diagnostics rejected already 3 in progress
131. a E Reports Logbook Diagnostics Diagnostic Results balkan csd sgi com C Last 30 days C Last days e 08 13 2003 to 08 13 2003 Figure 6 21 Diagnostic Results Window Single System Manager Mode 254 Diagnostic Result Reports Specify the range of dates for the report 4 Ifyou are using system group manager mode select the systems to include in the report 5 Clickonthe Generate Report button Figure 6 22 shows an example diagnostic results report Mesp Embedded Support Partner ver 30 ESP a mil Set Environment i UMM E Reports E F Logbook Diagnostic Results fex balkan csd sgi com 08 13 2003 to 08 13 2003 All Events Report Event Report for Diagnostics class No Diagnostic Name va a 1 olcmt Passed 08 13 2003 13 10 49 2 olmem Passed 08 13 2003 13 11 15 Diagnostic Result Diagnostic Result Time Figure 6 22 Example Diagnostic Results Report Single System Manager Mode Table 6 8 describes the contents of the report Table 6 8 Diagnostic Results Report Contents Single System Manager Mode Column Heading Description No Index number within the table Diagnostic Name Name of the diagnostic When one or more tests run as a group under one program for example SVP the total number of tests run is shown in parentheses next to the diagnostic name for example SVP 86 indicates that 86 tests ran under SVP 255 Chapter 6 Viewing Reports 256 Table 6 8 Di
132. ables for the local system If you specify the a11 option this command cleans the configuration tables and the ESP data tables on the selected system Chapter 4 Setting Up the ESP Environment This chapter describes how to set up the ESP environment on your system The ESP environment includes the following components e System serial number Linux OS only e Global configuration Paging parameters e System client parameters e System Group Manager SGM password parameters Note The paging parameters are not included in the ESP 3 0 Web based interface for the Linux OS ESP 3 0 for the Linux OS does not include paging by default because SGI does not distribute the OPage application for the Linux OS Paging capabilities are disabled when ESP 3 0 runs under the Linux OS The ESP 3 0 graphical user interface for the Linux OS does not include the Paging menu If you obtain the QPage application for the Linux OS from another source you should manually install and configure it and then create an ESP action that calls the oPage application You must set up the environmental components when you first configure ESP on a system After that modify specific parameters only when the corresponding environmental component changes 91 Chapter 4 Setting Up the ESP Environment Setting Up the System Serial Number ESP for the Linux OS Only 92 The Linux System SN button refer to Figure 4 1 is available only on systems th
133. agnostic Results Report Contents Single System Manager Mode continued Column Heading Description Diagnostic Result Result of the diagnostic PASS FAIL or COMPLETE PASS indicates that the diagnostic completed successfully FAIL indicates that the diagnostic failed COMPLETE indicates that multiple tests ran and one or more of them failed and the others passed Diagnostic Result Time at which the diagnostic completed testing Time When multiple tests run under one diagnostic for example SVP this column indicates the time at which all tests completed Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a diagnostic results report in system group manager mode 1 Click on the Reports button 2 Click on the Diagnostics button The interface displays the Diagnostic Results window Refer to Figure 6 23 AM esp Embedded Support Partner 5c a ESP Administration mi Set Environment cui E Reports Logbook Diagnostics Diagnostic Reports For System Group C Last 30 days Last days C 08 13 2003 to 08 13 2003 IP System Serial Current Type Number o Status All subscribed systems F baltic csd sgi com NA 134 16 241 92 SGM C balkan csd sgi com N A 134 16 241 91 Subscribed System Name Figure 6 23 Diagnostic Results Window System Group Manager Mode Diagnostic Result Reports Specify the range of date
134. ailability e Notify support personnel when specific events occur e Generate basic reports The features in the base package are included at no extra cost They are installed by default and ESP begins monitoring the system as soon as the system is booted if ESP is chkconfig ed on You can configure the base package to specify what types of events it should monitor and whom it should notify when events occur Note ESP can also monitor events from diagnostic tests and perform actions based on these events To use these optional features install the diagnostics from the Internal Support Tools 2 0 CD or a later release The Internal Support Tools CDs are available only to SGI personnel Chapter 1 Introduction Extended Package The extended package includes the System Group Manager SGM which adds the capabilities to monitor multiple systems at a site The system selected as the group manager runs the SGM which manages all systems in the group The SGM provides functionality to uniformly manage multiple systems when more than one system is installed at a site Specifically it performs the following functions e System group event tracking e System group configuration management e System group availability monitoring e Notification based on the events that occur on systems in the group e Enhanced reporting for groups of systems Any system within a system group can be designated the group manager it is even possible to h
135. al 4 Power Supply 5 Memory Parity 6 Memory ECC 7 System Error 8 System Board 9 NMI 10 File System 11 os AS 12 OS VM 13 OS PROC 14 OS PDA 15 OS NUMA 16 OS SYSCALL 17 OS Memory 18 Kernel Module 19 Kernel XLV 20 Kernel Clock 21 Kernel Vnode 22 Kernel Fork 23 Kernel KMEM 24 Kernel File System 25 Kernel Heap 26 Kernel Stream 27 Net Kernel IFSWITCH 28 Net Kernel PS 29 Net Kernel Routing 30 Net Kernel Internal 31 Network Driver FDDI 32 Network Driver Fast Enet 33 Network Driver GIO Enet 321 Chapter 10 Default Event Classes and Types 322 34 35 36 37 38 39 40 Cn es DB am DPD GER HB DB BAW O w 00 1001 C PN rp O10 01 O1 01 O1 O1 O1 O1 O1 Ol F20 000 1001 4 N50 rn O00 Ae Ww N OO 1 1 1 E Eaa B EE o a E gt a M Ov O 0 014 C F9 e 0 WON UW co n o OO Co N Network Driver VME Fast Enet Network Driver VME FXP Enet Network Driver VME GFE Enet Network Driver GIO FDDI Network Driver VME FDDI Network Driver IP22 6 8 Token k k k k k k Network Driver PCI Fast Enet k k k k k k Network Driver Everest Enet Network Driver MACE Fast Enet Network Kernel IFNET Network Kernel MBUF Network Kernel INPCB Network Kernel BSD Init Kernel User Saudit Kona Command Kona Timeout Kona Resource Kona Val
136. alias client alias sysid system id loadprofiles refreshprofiles lightnode fullnode force Use the following command syntax to unsubscribe a client usr sbin espconfig unsubscribe sgmclient host host name alias client alias sysid system id force 135 Chapter 4 Setting Up the ESP Environment 136 Use the following command syntax to update a client usr sbin espconfig update sgmclient host host name alias client alias sysid system id p lt password gt path new path gt lightnode fullnode Use the following command syntax to delete a client usr sbin espconfig delete sgmclient host host name alias client alias sysid system id Use the following command syntax to ping a client usr sbin espconfig ping sgmclient client alias sysid system id path reach path espver You can use the espconfig to check and configure general SGM settings Use the following command syntax to show the systems that an SGM knows usr sbin espconfig show systems Use the following command syntax to show an SGM s clients usr sbin espconfig show sgmclients Use the following command syntax to show the SGM servers configured for a system usr sbin espconfig show sgmservers Use the following command syntax to show information about a system usr sbin espconfig show system host host name sgmclient client alias sysid sy
137. anager User Guide publication number 007 4661 00x for more information about the Event Manager API functions and how to use them Using the emgrlogger and esplogger Tools 314 The esplogger and emgrlogger tools provide a simple command line interface to submit events to the Event Manager emgr logger works with the new Event Manager and replaces esplogger which was used with previous versions of eventmond and ESP esplogger remains available to provide backward compatibility emgrlogger can produce any type of Event Manager event including subscription events Use the emgrlogger and esplogger tools to pass event information from your local scripts to the event monitoring component of ESP eventmond You can run esplogger from a UNIX prompt or from a UNIX shell script emgrlogger and esplogger use the following command syntax emgrlogger emgrlogger h emgrlogger S U Q UQ RS c lt class gt t lt type gt a lt appname gt s source host gt o lt origin gt p lt priority gt f lt facility gt P path to remote host gt is lt tag gt lt value gt if lt tag gt lt file path id lt tag gt lt hex data gt Note Options related to creating subscription events are not typically used and are not described in this document where e The s option makes a subscription request e The u option makes an unsubscription request Using the emgrlogger and espl
138. and its clients Previous versions of ESP used RPC protocol over TCP IP Using standard TCP IP protocol provides the following benefits e TCP IP protocol is easier to configure e TCP IP protocol uses fewer resources e TCP IP protocol enables ESP 3 0 to communicate through a firewall Group Management Over Hierarchies Under ESP 3 0 an SGM server is required to know the hostname but not the IP address of a client system ESP 3 0 allows intermediate system s to know this information This enables ESP to work through a firewall The intermediate systems must have eventmond and ESP running The intermediate systems run an SGM dynamic shared object DSO that routes events from host to host The intermediate systems do not require an SGM license unless they are configured as SGM servers For example system A is an SGM server and system D is a client but system A does not know the IP address of system D However system B knows the IP addresses of systems A and C and system C knows the IP addresses of systems B and D ESP 3 0 allows you to add system D as a client to system A by specifying the connection path as follows B gt C This means that events will be forwarded from system D to system A following the connection path through system C and system B Refer to Figure 1 5 In this example an SGM DSO that is running on the client system system D forwards the event through the eventmond daemons on the intermediate systems system
139. and to start monitoring it Click on Disabled to add the event to the database but not monitor it Specify the number of times that the event must occur before ESP registers it and performs any assigned actions in the Occurrences prior to registration field Set the following optional parameters to provide more information about the event e Application name e Priority value Facility value e Regular expression to match Assign an action to the event If Event status is set to Enabled ESP performs this action when the event is registered Specify the number of seconds that ESP should pause between multiple executions of an action in the Action frequency time field A value of 0 disables the option For example if you set this parameter to 5 seconds and ESP registers an event every second ESP executes the assigned action s every 5 seconds Figure 5 14 shows the Add Event window with example parameters 159 Chapter 5 Configuring ESP aM esp roti Embedded Support Partner verzo tion mil Set Environment Z Configuration JE Reports E Logbook EJ Add Event Demo Demol Demol Eventi Figure 5 14 Add Event Window with Example Parameters Adding an Event to a New Class in a New Profile 9 Click on the Ada button The interface displays a verification message Refer to Figure 5 15 160 Configuring Events mM esp Embedded Support Partner ver 30 aA ESP Adm
140. and to start the ESP Web based graphical interface 1 Enter the launchEsPartner command Netscape displays the ESP opening page Refer to Figure 2 11 HOSUR Ec eiter csd sgi com C Embedded Support Partner Figure 2 11 ESP Opening Page 2 Specify the system that you want to access e To connect to the local host click on the login button e To connect to a remote system enter the system name or IP address in the hostname box and click on the login button 55 56 Chapter 2 Accessing ESP 3 Entera username and password The default username is administrator the default password is partner Note Before you use ESP the first time enter espconfig createadmin to create the default user account administrator TES PTT deiter csd sgi com Username and Password Required xj Enter username for Embedded Support Partner Secured Area at deiter csd 5554 UserName administrator SSCS Embedded Support Partner Figure 2 12 Entering a Username and Password Using the Web based Interface The ESP main page appears Figure 2 13 shows the main page in single system manager mode Figure 2 14 shows the main page in system group manager mode The main page shows the current system and ESP configuration information and provides buttons that link to the main ESP functions mMm esp roti Embedded Support Partner ver 50 a ESP Administration E Set Environment Iv Configuration Reports i Logbo f Sy
141. andalone version of the Event Manager daemon named eventmond to maintain compatibility with previous versions of ESP and other tools performs all event management functions The Event Manager daemon collects event information from other applications It runs independently of all other applications and enables local or remote applications to receive event data from it on a subscription basis Any application can subscribe to receive event information from the Event Manager event information availability is not limited to ESP as it was in earlier releases of ESP and eventmond ESP 3 0 subscribes to the Event Manager daemon to receive information about events that occur on a system ESP Architecture The new Event Manager daemon provides greater flexibility for applications that submit events This flexibility provides enhanced monitoring ability for ESP and any other applications that subscribe to receive events from the Event Manager Applications that submit events can specify the following information An event class ID number An event type ID number that is unique to each application Internal flags that indicate how to handle the message An event version number that is specific to each application The time that the event occurred The user ID number of the process that generated the event The hostname including domain name of the system that generated the event The name of the application that owns the event for example Kernel o
142. art number of the part Revision level of the part Date and time that the part was installed in the location Date and time that the part was removed from the location Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a hardware changes report from system group manager mode 1 Clickon the Reports button 2 Click on the Hardware button 3 Click on the Changes button The interface displays the Hardware Changes Report For System window Refer to Figure 6 31 Hardware Reports FII esp j J Embedded Support Partner ver 30 A ESP Administration mi Set Environment Configuration Logbook E History of Hardware Changes Last 30 days C Last days E 08 13 2003 to 08 13 2003 Sys System Serial Current System Name Type Number IP Address Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi ccom N A 134 16 241 91 Subscribed Figure 6 31 Hardware Changes Reports for System Group Window System Group Manager Mode 4 Specify the range of dates for the report 5 Clickonthe Generate Report button Figure 6 32 shows an example hardware changes report lap esp ro v Embedded Support Partner ver 30 A ESP Administration mi Set Environment Configuration Logbook Inventory P Changes D ESP Notice No changes for this time period x Figure 6 32 Example Hardware Changes Report Single Group Manager Mode
143. ass Window 184 Add an Action Window 188 Add an Action Window Using Notification Action Option 189 Add an Action Window Using Notification Action and E mail Options 191 Add an Action Window Using Notification Action and System Console Options 192 Add an Action Window Using Notification Action and GUI Pop up Options 193 Verification Message for Adding an Action Using Notification Action Option 195 Confirmation Message for Adding an Action Using Notification Action Option 195 Add an Action Window Using Other Action Option 196 Example Parameters Add an Action Window Using Other Action Option 198 Verification Message for Adding an Action Using Other Action Option 198 Confirmation Message for Adding an Action Using Other Action Option 199 Update Current Actions Window 201 Update Action Window 202 Verification Message for Updating an Action 203 Confirmation Message for Updating an Action 204 View Current Actions Window 207 Performance Monitoring Window with SGM Clients 209 Performance Monitoring Window 210 System Monitoring Window Single System Manager Mode 217 System Monitoring Change Verification Screen Single System Manager Mode 218 List of Figures Figure 5 51 Figure 5 52 Figure 5 53 Figure 5 54 Figure 5 55 Figure 6 1 Figure 6 2 Figure 6 3 Figure 6 4 Figure 6 5 Figure 6 6 Figure 6 7 Figure 6 8 Figure 6 9 Figure 6 10 Figure 6 11 Figure 6 12 Figure 6 13 Figure 6 14 F
144. assword for a New Server button The interface displays the Add Password for a New Server window Refer to Figure 4 21 far esp Embedded Support Partner verzo ESP _ mil Set Environment Configuration Reports E FR Logbook AA Add Password For A New Server Update Password For An Existing Server Add Password For A New Server Warning Settings below take effect immediately Server hostname l Password Figure 4 21 Add Password for a New Server Window 133 Chapter 4 Setting Up the ESP Environment 4 Enter the fully qualified hostname of the SGM server in the Server hostname field 5 Enter the password in the Password field 6 Click on tne Add button ESP immediately adds the password Be sure to configure the same password on the SGM server when you add the client to the server Refer to Adding a New SGM Client on page 116 Updating the Password for an Existing Server Perform the following procedure to update a password that you previously assigned to a server 1 Click onthe Set Environment button 2 Click onthe sGM Server button 3 Click on the Update Password for an Existing Server button The interface displays the Update Password for an Existing Server window Refer to Figure 4 22 Note If the client has more than one SGM server select the server for which you want to update the password and click on the Cont inue button Mesp Embedded Support Partner ver
145. at run the Linux OS This button enables you to enter the serial number of a system that is running the Linux OS This button can appear if you are running ESP from SGI ProPack 2 3 or later however this button should not normally appear for ESP from SGI ProPack 2 4 and later which can automatically detect the system serial number far esp E Embedded Support Partner ver so n ESP Administration mil Set Environment x Confiquration fE Reports E Logbook KLinux System SN E Add Linux System Serial Number balkan csd sgi com System serial number Figure 4 1 Linux System SN Button The Linux System SN button appears under two conditions e A local system is running the Linux OS and ESP cannot detect the system serial number e An SGM server has a subscribed client that is running the Linux OS and the system serial number was not detected or entered on the client before you subscribed the client to the SGM server Note You cannot set the Registration with SGI global configuration parameter to Enabled until you set the system serial number On a local system the Linux System SN button disappears after you enter the system serial number On an SGM system the Linux System SN button disappears after you enter the system serial number for each client system that does not have a system serial number set Setting Up the System Serial Number ESP for the Linux OS Only Setting the System Serial Number Single System Manager M
146. ation 01 11 12 LUTEA 9 Performance Low average processor 08 13 2003 08 13 2003 utilization 01 21 12 01 21 12 10 Performance Low average processor 08 13 2003 08 13 2003 utilization 01 31 12 missed Figure 6 10 Example Events Registered Report System Group Manager Mode 237 Chapter 6 Viewing Reports 238 Table 6 3 describes the information that the report contains Table 6 3 Events Registered Report Contents System Group Manager Mode Column Heading Description No Class Event Description First Occurrence Last Occurrence Event Count System Name Index number within the table The class that contains the event Tip Click on an event class to view a report of all occurrences of events in that class Brief description of the event Tip Click on an event description to view a report of all occurrences of that event Date and time at which the event was first registered Tip Click on the occurrence date to view the logbook entry for that date Date and time at which the event was last registered Tip Click on the occurrence date to view the logbook entry for that date Number of times that the event occurred Client system on which the event occurred a This column appears only when reports contain more than one event class b This column appears only on SGM systems when reports contain more than one system Events Registered Reports To drill down a report to fi
147. ave more than one group manager A system that is designated as the group manager monitors all systems in the group including itself The features in the extended package are not enabled unless the customer acquires a license to use them A 90 day free trial license is included full licenses are included in some service contracts or may be purchased separately Figure 1 2 provides a block diagram of system group management Distribution Group System 1 Manager System 2 System 3 System 4 Figure 1 2 System Group Management Block Diagram Chapter 1 Introduction ESP 3 0 adds enhanced group management functionality in the extended package including Support for named groups Communication via TCP IP protocol Support for full and light nodes Support for group management over hierarchies A simplified group management configuration process Enhanced configuration for SGM clients Central logbook capability Named Groups ESP 3 0 enables you to categorize the systems that you monitor by group name You can use the group names to quickly access statistical information and reports about all systems in a group by generating a site report through the Reports Site menu options Example group names include Server Desktop and Web server Refer to Figure 1 3 Figure 1 3 Named Groups Distribution Full and Light Nodes ESP 3 0 enables SGM clients to be full or light nodes A full node is a client s
148. ber ESP for the Linux OS Only Setting the System Serial Number System Group Manager Mode Perform the following procedure to set the system serial number in system group manager mode 1 Click onthe Set Environment button 2 Click on the Linux System SN button The interface displays the Add Linux System Serial Number window One SGM Client without a Serial Number Set If there is only one SGM client without a serial number enter the system serial number in the System serial number field and click on the Continue button Refer to Figure 4 4 Then log into ESP on the SGM client and set the serial number on that system You must set the serial number on the SGM server and the SGM client Tip Verify that you correctly entered the serial number before you click on the Commit button You cannot change the serial number once it has been submitted EM esp Mog Embedded Support Partner ver zo aA ESP Administration mill Set Environment 7 Configuration Reports Logbook Linux System SN E Add Linux System Serial Number balkan csd sgi com System serial number Figure 4 4 Linux System SN Window SGM Server that has One Client without a Serial Number Entered 95 Chapter 4 Setting Up the ESP Environment 96 Multiple Clients without a Serial Number Set If there is more than one SGM client without a serial number choose the correct system from the pulldown menu enter the system serial number in the Syst
149. book System Monitoring Update System Monitoring icmp will be monitored on the following e baltic csd sgi com e balkan csd sgi com Commit Figure 5 54 System Monitoring Change Verification Screen System Group Manager Mode 221 Chapter 5 Configuring ESP 222 6 Clickon the Commit button The interface displays an updated System Monitoring window Refer to Figure 5 55 a esp Embedded Support Partner ver 30 a ESP m mil Set Environment v Configuration Reports E BE Logbook System Monitoring baltic csd sgi com PMIE Enabled Disabled View by system name No Service Command String Name 1 pmed Iusr share pcp bin pmcd wait h HOST 2 nntp echo listgroup comp sys sgi echo quit usr share pcp binitelnet prpbe HOST 119 3 smtp echo expn root echo quit usr share pcp binitelnet probe HOST 25 4 rpcbind usr sbin rpcinfo p HOST 5 xserver DISPLAY HOST 0 usribin X11 xhost 6 dns nslookup HOST lt dev null 7 icmp Ibin ping c 3 f HOST Commit Figure 5 55 Updated System Monitoring Window System Group Manager Mode Using the Command Line Interface System Name baltic csd sgi com baltic csd sgi com baltic csd sgi com baltic csd sgi com balkan csd sgi com baltic csd sgi com You can use the espconfig command to configure system monitoring e Use the following command syntax to list descriptions of services that are available for monitorin
150. bscribed Client alias balkan Client node Ful C Light Connection path battic ced sgi com balken csd sgi com System group 3 desktop E Password Leave itasis C Add Update Figure 4 18 Update Client Information Window ESP 3 0 SGM Client Selected 1 Setthe parameters Table 4 6 describes the parameters that are available 2 Click the Update button 125 Chapter 4 Setting Up the ESP Environment 126 Table 4 6 Update Client Information Window Parameters ESP 3 0 SGM Client Parameter Description Client alias Client node Specifies an alias that ESP uses to identify the client This parameter is optional If you do not set this parameter ESP uses the hostname of the client without the domain name This parameter can contain any non blank space character except for single or double quotes Specifies how the client is configured Fulland Light A full node is an SGM client that sends data to an SGM server and also keeps a copy of all data in its own database Full nodes require more local disk space than light nodes A light node is an SGM client that sends data to an SGM server but does not keep any data in its own database You can convert a light node to a full node at any time however only data that is generated after the conversion completes is stored in the local database Data generated before the conversion completes is stored only in the database on the SGM
151. ce cid class id gt cd class desc sgmclient client alias gt sysid client espconfig update evclass cid class id cd class desc sgmclient client alias sysid client espconfig delete evclass cid class id cd class desc sgmclient client alias sysid client espconfig list evclass espconfig add evclass Event Action Configuration system id system id system id espconfig show evaction acid action id acd action desc espconfig list evaction espconfig add evaction acd action desc act action string nable disable user lt name gt tout timeout value espconfig update evaction acd action desc acid action id gt act action string gt nable disable user name tout timeout value to file Exporting and Importing Environment espconfig add 1load merg ventprofile profile name gt allprofiles defaults dontsubscribe sgmclient client alias sysid system Id espconfig drop unload eventprofile profile name gt allprofiles sgmclient client alias sysid system Id espconfig save refresh ventprofile defaults profile name gt allprofiles sgmclient client alias sysid system Id espconfig list eventprofile sgmclient client alias sysid system Id espconfig showevents eventprofile profile name gt
152. client first refer to Adding a Password for a New Server on page 133 and then on the SGM server refer to Adding a New SGM Client on page 116 and Updating the System or a Client on page 122 Subscribe to the events that you want to receive from the SGM Clients Refer to Subscribing Events from SGM Clients on page 182 61 Chapter 3 Administering ESP This chapter describes how to administer ESP on your system ESP administration includes the following components e Customer profile e Network permissions e User permissions e Database archives You must set up the administration components when you first configure ESP on a system After that modify specific parameters as needed for example add or delete users 63 Chapter 3 Administering ESP Setting Up the Customer Profile 64 Customer profiles provide contact information for a system site If the service contract for your site includes automatic call logging ESP sends the name telephone number and e mail address of the contact person to the call logging tool at SGI Using the Web based Interface Perform the following procedure to use the Web based interface to set up the customer profile for a system 1 Clickonthe ESP Administration button Note If the system is an SGM server choose the system for which you want to set up the customer profile and click on the Continue button Refer to Figure 3 1 The interface displays th
153. cription events logger logger provides a shell command interface to the syslog system log routine It can log messages specified on the command line from a specified file or from the standard input Each line in the specified file or standard input is logged separately Event Manager API The Event Manager API provides a mechanism that enables tasks to communicate with eventmond The eventmond daemon receives information from external monitoring tasks through API function calls Each command that is sent to eventmond returns a status code that indicates successful completion or the reason that a failure occurred ESP Architecture Availability Monitoring The base package also includes an availability monitoring application availmon availmon monitors system uptime and differentiates between controlled shutdowns system panics power cycles and power failures Availability monitoring is useful for high availability systems production systems or other customer sites where monitoring availability information is important The availmon script runs at system start up to gather the availability data Do not manually run the availmon script Manually running the script creates inaccurate availability results The avaiimon DSO monitors system uptime To do this it updates the var adm avail save lasttick file every 5 minutes to indicate that the system is still running The var adm avail save lasttick file contains the current uptim
154. d Use the cid option to select the event class by class ID Use the cd option to specify a new class description a string enclosed in quotes Use the sgmclient or sysid option to select the SGM client on which you want to update the event information Configuring Events Updating Multiple Events at the Same Time Batch Updating You can update multiple events at the same time by using the batch update feature The batch update feature enables you to select more than one event at a time and apply parameter changes to all of the selected events Using the Web based Interface Perform the following procedure to use the Web based interface to update multiple events at the same time 1 Click on the Configuration button Click on the Events button 2 3 Click on the Batch Update button 4 If you are using ESP on a system group manager the interface displays the Update Event window with a list of SGM clients Refer to Figure 5 23 Select the system on which you want to update events and click on the Cont inue button fal es Uu Support Partner verzo aA ESP Administration mil Set Environment Reports Logbook AA b Events _Load Profile Add Update P Batch update Delete subscription Batch Events Update System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Continue Figure 5 23 Batch Events Update
155. d action id acd action desc gt pri priority fac facility appname app name gt regexp reg expression gt prfid profile id prfn profile name gt sgmclient client alias sysid client system id gt updat vtyp tid type id cid class id gt cd class desc gt sgmclient client alias sysid client system id gt td type desc gt throttle lt value gt nable disable log nolog acfreq action frequency value gt acid action id acd action desc gt noacid action id noacd action desc gt pri priority fac facility appname app name gt regexp reg expression gt prfid profile id prfn profile name noprfid profile id noprfn profile name gt delet vtyp tid type id gt td type desc sgmclient client alias sysid client system id gt espconfig subscribe evtype cid class id cd class desc gt tid type id td type desc gt pri priority fac facility appname application name gt sgmclient client alias sysid client system id gt espconfig unsubscribe evtype cid class id gt cd class desc gt 36 tid type id td type desc gt pri priority fac facility appname application name gt sgmclient client alias sysid client system id gt Using the Command Line Interfa
156. d system id gt Use the following command syntax to enable event throttling usr sbin espconfig enable event throttling sgmclient client alias gt sysid system id gt Use the following command syntax to disable event throttling usr sbin espconfig disable event throttling sgmclient client alias gt sysid system id gt Use the following command syntax to view the current setting of the actions parameter usr sbin espconfig show event actions sgmclient client alias sysid system id gt Use the following command syntax to enable actions usr sbin espconfig enable event actions sgmclient client alias sysid system id gt Use the following command syntax to disable actions usr sbin espconfig disable event actions sgmclient client alias gt sysid system id gt Setting Up the Global Configuration Parameters Use the following command syntax to view the current setting of the shutdown description parameter usr sbin espconfig show shutdown reason sgmclient client alias gt sysid system id gt Use the following command syntax to prompt users for a description when they shut down the system usr sbin espconfig enable shutdown reason sgmclient client alias sysid system id gt Use the following command syntax to allow users to shut down the system without providing a reason usr sbin espconfig disable shutdown reason sgmclient client alias
157. d Enabled 9 SVP start Enabled Enabled Figure 5 22 Confirmation Message for Updating an Event 170 Configuring Events Using the Command Line Interface You can use the espconfig command to update event information e Use the following command syntax to update an event usr sbin espconfig updat vtyp tid type id cid class id cd class description gt sgmclient client alias sysid client system id gt td type description gt throttle throttle value gt nabl disable log nolog acfreq action frequency value gt acid action id acd action description noacid action id noacd action description gt acid action id acd action description gt pri lt priority gt fac lt facility gt appname lt app name gt regexp lt reg expression gt prfid lt profile id gt prfn lt profile name gt noprfid profile id noprfn profile name gt Use the cid option to specify an existing event class ID or use the cd option to provide a class description a string enclosed in quotes that describes the class Use the sgmclient or sysid option to select the SGM client on which you want o update the event information se the tid option to specify the event to update You must provide a unique event type ID U Use the td option to update the event description You can only update custom event descr
158. d be omitted All systems name must be fully qualified hostnames 120 Setting Up the System Client Parameters System Group Manager Mode Only Table 4 4 Add New Client Window Parameters continued Parameter Description System group Password Specifies the group to which the client belongs You can use groups to quickly access information about all systems in a group by generating a site report Example group names include Server Desktop Web Server and File Server To create a new group enter the name in the System group field Once you create one or more group names ESP displays a menu of the existing groups to select an existing group choose it from the menu Note When you enter group names the entry in the field takes precedence over the selection in the menu The proper way to create a new group is to set the menu to New Group and enter the group name in the System Group field The following three rules apply for creating group names 1 The case of characters does not matter ESP puts systems hat you enter in the groups named Web server and Web Server in the same group 2 Spacing between characters does matter ESP puts systems that you enter in the groups named Web server and Web server in different groups 3 Single and double quotes are not allowed This parameter is optional Specifies a password that the server and client must exchange before transmitting data to provi
159. de 4 Select the type of client to add ESP 3 0 or ESP 2 0 client 5 Clickon the Continue button 116 Setting Up the System Client Parameters System Group Manager Mode Only Figure 4 14 shows the Add New Client window for an ESP 3 0 client Che esp d Embedded Support Partner ver 30 aA ESP Administration mil Set Environment W Configuration Reports i Logbook System Client Add New Client Fl Add New Client New group Figure 4 14 Add New Client Window for ESP 3 0 Client System Group Manager Mode 117 Chapter 4 Setting Up the ESP Environment Figure 4 15 shows the Add New Client window for an ESP 2 0 client mm esp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment x7 Configuration Reports Logbook Ia System Client P Add New Client Update System Client Unsubscribe Delete Client i O Fl Add New Client Warning All changes take effect immediately Client hostname EM J Client alias EM System group Do ueem A Password EM Add Client Figure 4 15 Add New Client Window for ESP 2 0 Client System Group Manager Mode 6 Set the parameters for the client Table 4 4 describes the parameters that are available 7 Click on the Add Client button 8 Click on the Continue button For ESP 3 0 clients ESP immediately subscribes the system without waiting for additional verification If ESP cannot
160. de stronger security via authentication This parameter is optional for ESP 3 0 clients This parameter is required for ESP 2 0 clients If you require a password you must configure it on the client side first a This parameter appears only for ESP 3 0 clients 121 Chapter 4 Setting Up the ESP Environment 122 Updating the System or a Client Perform the following procedure to update the SGM server system or an SGM client in system group manager mode 1 Click onthe Set Environment button 2 Click on the System Client button 3 Click on the Update System Client button The interface displays the Update System Client window Refer to Figure 4 16 AM eSp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment Configuration Reports Logbook AA Update System Client Unsubscribe Delete Client Fl Update SystemiClient Information Alias System Name IP Type Serial Number ESP Version System Status baltic baltic csd sgi com N A ESP3 0 SGM C balkan balkan csd sgi com NA ESP3 0 Unsubscribed Continue Figure 4 16 Update System Client Window System Group Manager Mode 4 Select the system to update 5 Click on the Continue button Setting Up the System Client Parameters System Group Manager Mode Only Updating the SGM Server If you select the local system the SGM server ESP displays the Update System Information window Refer to Figure 4 17 Mes
161. de stronger security via authentication This parameter is optional If you require a password you must configure it on the client side first Use the Leave it as is option to retain an existing password Use the Add option to add a new password Setting Up the System Client Parameters System Group Manager Mode Only Updating an ESP 2 0 SGM Client If you select an ESP 2 0 SGM client ESP displays the Update Client Information window shown in Figure 4 19 FIBI Embedded Support Partner ve a SEG mi Set Environment Configuration Reports Logbook AA System Client Unsubscribe 7 Delete cem OO El Update Client Information sirocco csd sgi com Warning All changes take effect immediately Client alias sirocco System group Unknown z Password Leaveitasis C Add Update Figure 4 19 Update Client Information Window ESP 2 0 SGM Client Selected 1 Setthe parameters Table 4 7 describes the parameters that are available 2 Click the Update button 129 Chapter 4 Setting Up the ESP Environment 130 Table 4 7 Update Client Information Window Parameters ESP 2 0 SGM Client Parameter Description Client alias System group Password Specifies an alias that ESP uses to identify the client This parameter is optional If you do not set this parameter ESP uses the hostname of the client without the domain name This parameter can contain any non blank space cha
162. drive marked 0x2233 Removed drive marked removed 0 Drive marked removed Drive failed by device manager x2232 0x2231 Drive marked replaced 0x2230 0x222F ESP for the IRIX OS 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 34 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 Mark drive removed 0x222E Drive marked unassigned 0x222C Drive replaced when Storage Arr ay was turned off 0x222B Hot spare drive assigned 0x222 A Drive deleted 0x2228 Drive marked optimal 0x2227 Reconstruction restarted 0x222 5 Reconstruction started 0x2224 Logical unit number for volume reassigned 0x2222 Hot spare drive removed from ho t spare list 0x2221 Hot spare drive added to hot sp are list 0x2220 Initialization immediate avail ability started or restarted 0x221F Volume group or volume initiali zed 0x221E Volume group placed online 0x2 21D Volume group placed offline 0x 221G Piece placed in service 0x221B Piece replaced 0x221A Piece removed from volume 0x22 19 One or more Sundry regions crea ted 0x2214 Volume initialized with zeros 0x2213 Restore completed 0x2211 Restore started 0x2210 0 Media scan scrub completed
163. dy 46 A hard disk failed because devi ce returned an unknown status 45 A hard disk failed because of a sequence error in the SCSI bus phase handling 44 A hard disk failed because acc ss to the device met with a sel Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 349 Chapter 10 Default Event Classes and Types 350 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 3043 3042 3041 3040 3039 3038 3037 3036 3035 3034 3033 3032 3031 3030 3029 3028 3027 3026 3025 3024 3016 3023 3022 3021 ection ti A hard disk set to b me out 43 failed state y host 42 A hard disk failed because of b usy status or parit y error 41 A hard disk failed because of t he system reset 40 A hard disk failed because comm and to the device t A hard disk failed ad tag from the A hard disk failed ross error on SCSI A hard disk failed A hard disk failed le check condition A hard disk failed bus reset A hard disk failed e recovery Initialization Request Sense Data SCSI device Misc error Soft error Parity error SCSI command retrie SCS
164. e You can use the espconfig command to delete events and event classes Use the following command syntax to delete an existing custom event usr sbin espconfig delet vtype tid type id td type description sgmclient client alias sysid client system id Use the t id option to specify an event ID or use the ta option to specify an event description a string enclosed in quotes Use the sgmclient or sysid option to specify an SGM client Note If the event description is not unique the command displays a table of matching events and event IDs When this occurs use an event ID from the table with the td option to delete an event If the event to delete is the last event in a custom class this command also deletes the event class Configuring Events Use the following command syntax to delete an entire custom event class usr sbin espconfig delete evclass cid class id cd class description sgmclient client alias sysid client system id Use the cid option to specify an event class ID or use the ca option to specify an event class description a string enclosed in quotes Use the sgmclient or sysid option to select the SGM client on which you want to update the event information Use the following command syntax to delete all event related data structures types classes actions and so on in the system support database usr bin espconfig delet
165. e in seconds since January 1 1970 Note In ESP 3 0 you cannot change the default status interval of last tick 5 minutes or the default interval for sending status reports 7 days You can use the usr sbin eventmond T command to verify that the availmon DSO is running The output from this command lists the availmon DSO when it is running SGI recommends that you do not manually run the availmon DSO 25 Chapter 1 Introduction 26 Notification Software Notification is one of the actions that can be programmed to take place when a particular system event occurs The notification software provides several types of notifiers including dialog boxes on the local system e mail paging and diagnostic reports and other types of reports The espnot ify tool provides the following notification capabilities for ESP e E mail notifications e GUI based or console text notifications with audio if the notification is on the local host e Program execution for notification e Alphanumeric and chatty paging through the Qpage application ESP 3 0 for the Linux OS does not include paging by default SGI does not distribute the QP age application for the Linux OS Paging capabilities are disabled when ESP 3 0 runs under the Linux OS The ESP 3 0 graphical user interface for the Linux OS does not include the Paging menu If you obtain the QP age application for the Linux OS from another source you should manually install and co
166. e Create Customer Profile window Refer to Figure 3 2 mM esp i Embedded Support Partner ver 30 ESP Administration ei Set Environment Configuration Reports Logbook Customer Profile Kj Customer Profile System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Continue Figure 3 1 Choosing the System to Update the Customer Profile Setting Up the Customer Profile Embedded Support Partner ver 30 ESP Administration mi Set Environment Configuration Reports Logbook Customer Profile EE Kj Create Customer Profile baltic csd sgi com Required First Name Last Name Phone Number include country and or area code s E mail Address Country Optional Site ID Street Address 1 Street Address 2 Street Address 3 City State Postal Code ZIP Code Figure 3 2 Update Customer Profile Window Web based Interface 2 Update the customer profile parameters Table 3 1 describes the parameters Table 3 1 Customer Profile Parameters Parameter Description Required Parameters First Name First name of the site contact person Last Name Last name of the site contact person Phone Number Phone number of the site contact person include only numbers and dashes for example 1 715 123 4567 65 Chapter 3 Administering ESP 66 Table 3 1 Customer Profile Parameters continued Parameter Descript
167. e URL http 10ocahost 5554 Or http systemname 5554 in a Web browser The Web browser displays the ESP opening page Refer to Figure 2 1 Using the Web based Interface hostname balticcsdsgicom O csd sgi com ttt Embedded Support Partner Figure 2 1 ESP Opening Page 45 Chapter 2 Accessing ESP 46 3 Specify the system that you want to access e To connect to the local system click on the login button e To connect to a remote system enter the system name or IP address in the hostname box and click on the 1ogin button 6 4 Enter a username and password Refer to Figure 2 2 The default username is administrator the default password is partner hostname baltic csd sgi com WE I Nu uu m I Username and Password Required xj Enter username for Embedded Support Partner Secured Area at baltic csd 5554 UserName adminisiator SSS Embedded Support Partner Figure 2 2 Entering a Username and Password Using the Web based Interface The ESP main page appears Figure 2 3 shows the main page in single system manager mode Figure 2 4 shows the main page in system group manager mode The main page shows the current system and ESP configuration information and provides buttons that link to the main ESP functions fat eS Uu Support Partner verzo rm ESP Administration mil Set Environment Iv Configuration Reports Logbook f System Information Figure 2 3 ESP Main
168. e high floating point exception rate cpu excess fpe 3 High 1 minute load average cpuload average 4 Low average processor utilization cpu low util 5 High aggregate system call rate cpu syscall 6 Busy executing in system mode cpu system 7 High average processor utilization cpu util 8 System Group Manager slow service response espping response 9 System Group Manager service probe failure espping status 10 File system is filling up filesys filling 11 Severe demand for real memory memory exhausted 12 Low free swap space memory swap low 13 High number of saturated processors per cpu many util 14 High per CPU processor utilization per cpu some util 15 High per CPU system call rate per cpu syscall 16 Some CPU busy executing in system mode per cpu system 17 High collision rate in packet sends per netif collisions 18 High network interface error rate per netif errors 19 High network interface packet transfers per netif packets Shell ping PMDA slow application or service response 21 Shell ping PMDA application or service probe failure shping status Commit Figure 5 48 Performance Monitoring Window SI SI SI SI SI MTA HAMA TAWA AA A xI shping response KI 210 Configuring Performance Monitoring Table 5 4 PMIE Rules 3 Click on the Enabled radio button to enable performance monitoring or click on the Disabled radio button to disable performance monitoring Note This setting is also available in the System Monitoring wi
169. e name archive name gt espconfig drop archive archive name ESP Customer Profile Configuration espconfig 38 create customer profile fname first name lname last name phone phon number email email address streetl street address line 1 gt street2 street address line 2 gt street3 street address line 3 gt city city name gt state state or province gt post lt postal zip code gt country country site id site id host host name alias client alias sysid system id gt Using the Command Line Interface espconfig espconfig update customer profile fname first name gt lname last name gt phone phone number gt email lt email address gt streetl street address line 1 gt street2 street address line 2 gt street3 street address line 3 city city name gt state state or province gt post lt postal zip code gt country lt country gt site id site id gt host host name alias client alias sysid system id gt show customer profile host host name alias client alias sysid system id gt Global Configuration espconfig espconfig espconfig espconfig espconfig espconfig espconfig enable call logging text comp encoded sgmclient client alias sysid system id gt nabl vent registration event
170. e time batch update 139 Chapter 5 Configuring ESP 140 e Delete events e Subscribe to events on other system system group management mode only Managing Event Profiles Event profiles provide an easy way to control which events are being monitored on your system You can use event profiles to quickly load events that pertain to your system configuration and unload events that do not Event profiles are located in the var esp init eventprofiles directory If you manually edit an event profile you must save it with a esp extension in this directory Note In the following subsections the term ESP event list refers to the events that are currently loaded in ESP on your system Using the Web based Interface Perform the following procedure to use the Web based interface to use event profiles 1 Clickonthe Configuration button 2 Clickon the Events button 3 Click on the Load Profile button Note If the system is an SGM server the interface displays a list of clients Refer to Figure 5 1 Click on the client that you want to use and click on the continue button The interface displays the Event Profile window Refer to Figure 5 2 Configuring Events fr es p Support Partner ver 30 A ESP Administration mil Set Environment Z Configuration E Reports Logbook AA b Events Event Profiles System Name IP Type Serial Number ESP Version baltic csd sgi com SGM N A ESP3 0 C balkan
171. ect the system on which you want to update the event and click on the Cont inue button Configuring Events a es Pa Support Partner ver 30 A ESP Administration mi Set Environment Reports Logbook AA b Events Load Profile Add Update Batch Update Delete subseripton 8 8 Update Event System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Continue Figure 5 17 Update Event Window with SGM Clients The interface displays the Update Event window Refer to Figure 5 18 ar esp mbedded Support Partner ver 30 A ESP Administration mil Egan ud v Configuration Reports Logbook Update Event List of event classes Daemon Messages Diagnostic ESP Event Manager ESP Internal Events Kernel Messages Generate Report Figure 5 18 Update Event Window 165 Chapter 5 Configuring ESP 166 4 Clickon the event class that contains the event that you want to update 5 Clickonthe Generate Report button The interface displays a list of all events in the event class that you selected Refer to Figure 5 19 MM es Uu Support Partner 5o a ESP Administration mi Set Environment Reports Logbook AA Events Load Profile Add Update Batch Update Delete subscription O Update Events Class Diagnostic balkan csd sgi com Event Description No va 1 Diagnostic end
172. ed 0x2027 No No 3408 Reconstruction completed 0x202 No No 6 3407 Reconstruction started 0x2025 No No 3406 Media scan scrub resumed 0x2 No No 024 3405 Media scan scrub completed 0 No No x2023 3404 Media scan scrub started 0x2 No No 022 3403 VDD repair completed 0x201F No No 371 Chapter 10 Default Event Classes and Types 372 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3402 3401 3400 3399 3398 3397 3396 3395 3394 3393 3392 3391 3390 3389 3388 3387 3386 3385 3384 3383 3382 3381 3380 3379 3378 3377 3376 3375 3374 3373 VDD repair started 0x201 VDD recover completed 0x201 VDD recover started 0x201 VDD restore completed 0x201 VDD restore started 0x201 Performance monitor 0x2019 I O suspended due to no pre all ocated resources 0x2018 Interrupted writes detected fro dwa m checkpoint logs 0x2017 Interrupted writes processed 0 x2016 VDD logged an error 0x2014 Cache flush completed 0x2012 Cache flush started 0x2011 Cache synchronization completed 0x2010 Cache synchronization started 0x200F Virtual disk driver reconfigure d 0x200E I O aborted on volume 0x200D Recovered error on volume 0x20 0C RAID 0 write failures 0x2009 Failed volume started recons
173. ed Yes Yes 4005 2098184 Stress interrupted Yes Yes 4001 2097244 High aggregate context switch r Yes Yes ate 4001 2097217 Possible high floating point ex Yes Yes ception rate 4001 2097218 High 1 minute load average Yes Yes 4001 2097246 Low average processor utilizati Yes Yes on 4001 2097219 High aggregate system call rate Yes Yes 4001 2097220 Busy executing in system mode Yes Yes 4001 2097221 High average processor utilizat Yes Yes ion 4001 2097249 System Group Manager slow servi Yes Yes ce response 4001 2097248 System Group Manager service pr Yes Yes obe failure 4001 2097226 File system is filling up Yes Yes 4001 2097227 Severe demand for real memory Yes Yes 4001 2097228 Low free swap space Yes Yes 4001 2097247 High number of saturated proces Yes Yes sors 4001 2097241 High per CPU processor utilizat Yes Yes ion 4001 2097239 High per CPU system call rate Yes Yes 4001 2097240 Some CPU busy executing in syst Yes Yes em mode 4001 2097230 High collision rate in packet s Yes Yes ends 4001 2097231 High network interface error ra Yes Yes te 4001 2097232 High network interface packet t Yes Yes ransfers ESP for the IRIX OS ESP for the IRIX OS Default Event Classes The following output from the espconfig command shows the default event classes that ESP includes on a system running the IRIX OS irix espconfig list evclass ClassId Class description T CSCSIT 2 Io 3 Peripher
174. ed or did not respond within a timeout period The amount of data in the filesystem exceeded a threshold value and the remaining space in the filesystem is filling ata rate that exceeded a threshold value The rate at which the system is swapping modified pages out of main memory to the swap partitions exceeded a threshold value The amount of swap space remaining reached a threshold value Reduce the number and size of the running programs or add more swap 1 space before it completely runs out 212 Configuring Performance Monitoring Table 5 4 PMIE Rules continued Rule Description Performance Issue per cpu many util per cpu some util per cpu syscall per cpu system per netif collisions per netif errors High number of saturated processors High per CPU processor utilization High per CPU system call rate Some CPU busy executing in system mode High collision rate in packet sends High network interface error rate The processor utilization for a minimum number of CPUs exceeded a threshold value This rule applies only to multiprocessor systems that have more than min cpu count processors For single processor systems refer to the cpu util rule For multiprocessor systems with less than min cpu count processors refer to the per cpu some util rule The processor utilization for at least one CPU exceeded a threshold value This rule applies only to multiprocess
175. egal hardware configuration RM4 2 legal hardware configuration illegal VTX config llegal hardware configuration invalid VME adapter llegal hardware configuration no map VME adapter llegal hardware configuration check DVI cable connection Write to DG2 EEPROM failed DG EEPROM contents invalid Resourc xhausted Context switch error 1 Context switch error 2 Context switch timeout Unrecognized command Graphics error Idle wait timeout FIFO timeout Texture I O DMA timeout 1 Texture I O DMA timeout 2 Texture DMA error 1 HQ4 context switch error HOA FIFO overflow HQ4 ucode error HQ4 DMA address range error HO4 FIFO privilege violation HQ4 stack overflow HQ3 FIFO overflow HQ3 FIFO timeout FIFO error HQ3 ucode error HQ3 DMA address range error HQ3 FIFO privilege violation HQ3 stack overflow Bad TRAM configuration 1 Bad TRAM configuration 2 Bad SRAM 1 2 Bad SRAM Texture DMA error 2 Video texture DMA timeout DMA boundary exceeded DMA locking enabled Swapbuffer timeout Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
176. em serial number field and click on the Continue button Refer to Figure 4 5 Then log into ESP on the SGM client and set the serial number on that system You must set the serial number on the SGM server and the SGM client Tip Verify that you correctly entered the serial number before you click on the Commit button You cannot change the serial number once it has been submitted aj esp Embedded Support Partner v5 A ESP i mil Set Environment 7 RA Configuration Reports E WE Logbook Linux System SN Fl Add Linux System Serial Number System name balken csd sgi com System serial number Figure 4 5 Linux System SN Window SGM Server that has Multiple Clients without Serial Numbers Entered Setting Up the Global Configuration Parameters Setting Up the Global Configuration Parameters The global configuration parameters define global ESP behaviors and are divided into the following categories Global event handling parameters which determine if ESP should register events throttle events and perform any actions Global availability parameter which determines if a reason must be supplied when the system is shutdown Global registration parameters which determine if event information is returned to SGI the format of the message that contains the event information and any additional recipients of the message Using the Web based Interface Perform the following procedure to use the Web based interface to
177. emory deadlock with no one to kill Process killed due to insuffici ent memory ARM interrupt error GE interrupt error FIFO timeout Swapbuffer timeout 1 Retrac vent timeout Swapbuffer timeout 2 Yes Yes Tes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 52 50 50 51 51 50 50 50 50 51 22 23 23 953 52 51 2d 51 52 51 54 54 54 55 55 55 55 56 56 57 58 57 59 56 56 56 56 56 57 57 57 2106 2107 2108 2109 211 217 211 211 211 211 211 2141 29 213 2120 2121 2122 2123 e co 10 01 CO N29 ES oO 2126 2131 2132 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 Illegal hardware configuration XG error 1 XG error 2 Memory timeout Textport timeout XG error 3 TBUS ARM error Unrecognized command Graphics error Checkpipe timeout DMA overflow 1 XG RAM parity error XG RAM invalid error XG bus parity error DMA overflow 2 Mopup timeout DMA timeout Selectfeed timeout I O space exhausted Context deactivation timeout Process attempting IrisG
178. endpoint is not connected Figure 6 11 Events Registered in a Specify Class System Group Manager Mode 239 Chapter 6 Viewing Reports 2 Clickonthe Event Description for the event The interface displays all occurrences of the event Refer to Figure 6 12 at esp mbedded Support Partner ver 30 aA ESP Administration mi Set Environment Configuration Logbook Specific Event Report baltic csd sgi com 08 13 2003 to 08 13 2003 Class Daemon Messages All Classes Event Daemon Error First Last Occurrence Occurrence Event va va Count Syslog Message 08 13 2003 08 13 2003 1 warning can t get client address 06 23 55 06 23 55 Transport endpoint is not connected 08 13 2003 08 13 2003 ql warning can t get client address 06 35 31 06 35 31 Transport endpoint is not connected 08 13 2003 08 13 2003 warning can t get client address 09 03 03 09 03 03 Transport endpoint is not connected 08 13 2003 08 13 2003 warning can t get client address 09 09 04 09 09 04 Transport endpoint is not connected 08 13 2003 08 13 2003 warning can t get client address 09 21 14 09 21 14 Transport endpoint is not connected 08 13 2003 08 13 2003 warning can t get client address 09 31 48 09 31 48 Transport endpoint is not connected 08 13 2003 08 13 2003 warning can t get client address 11 22 06 11 22 06 Transport endpoint is not connected 8 08 13 2003 08 13 2003 warning can t get client address 11 44 38 11 44 38 Transport endpoint is no
179. ent Update the Action frequency time parameter for each action Click on the Update button The interface displays a verification message that shows the changes that you selected Refer to Figure 5 21 Configuring Events aN esp mbedded Support Partner ver 30 aA ESP Administration mi Set Environment Reports Logbook AA P Events Load Profile Add P Update BatchUpdate Delete subscription 8 Update Event balkan csd sgi com Class Diagnostic Event Diagnostic end Actions 1 my action 1 86400 secs 2 Notify sysadmin on console 86400 secs Commit Figure 5 21 Verification Message for Updating an Event 13 Click on the Commit button The interface displays a confirmation message that shows the updated event in bold Refer to Figure 5 22 169 Chapter 5 Configuring ESP aM esp SD Embedded Support Partner ver 30 a ESP Administration mi Set Environment Z Configuration E Reports Logbook AA b Events Load Profile Add Update Batch Update Delete subseripton 8 8 8 0 8 Update Events Class Diagnostic balkan csd sgi com Event Description No va Status Registration With SGI 1 Diagnostic end Enabled Enabled 2 Diagnostic interrupted Enabled Enabled 3 Diagnostic start Enabled Enabled 4 Stress end Enabled Enabled 5 Stress interrupted Enabled Enabled 6 Stress start Enabled Enabled 7 SVP end Enabled Enabled 8 SVP interrupted Enable
180. er Warning All changes take effect immediately Allow Access Restrict Access Figure 3 3 Network Permissions Window Web based Interface 3 To modify the Allow Access list e To add an address enter the IP address or IP address mask using as a wild card for one or more values in the address in the box and click on the Add button e To delete an address click on the address in the Allow Access list and click on the Delete button 4 Tomodify the Restrict Access list e To add an address enter the IP address or IP address mask using as a wild card for one or more values in the address in the box and click on the Add button e To delete an address click on the address in the Restrict Access list and click on the Delete button 69 Chapter 3 Administering ESP 70 Using the Command Line Interface You can use the espconfig command to set up the network permissions from the command line interface Tip Usean asterisk as a wild card character in any of the IP addresses that you enter for the ip address gt parameter for example 123 23 2 123 255 and Use the following command syntax to enable IP addresses to access the ESP Web server usr sbin espconfig enable ipaddr ip address gt ip address gt You must specify at least one IP address If you specify an IP address that is already enabled it remains enabled If you specify an IP address that is disab
181. er Mode 115 Add New Client Window Parameters 119 Update System Information Window Parameters SGM Server 124 Update Client Information Window Parameters ESP 3 0 SGM Client 126 Update Client Information Window Parameters ESP 2 0 SGM Client 130 Batch Update Options 175 Notification Action Parameters 194 espnotify Parameters 197 PMIE Rules 211 Report Navigation Controls 227 Events Registered Report Contents Single System Manager Mode 232 Events Registered Report Contents System Group Manager Mode 238 Actions Taken Report Contents Single System Manager Mode 243 Actions Taken Report Contents System Group Manager Mode 245 Single System Availability Report Contents Single System Manager Mode 249 xix List of Tables Table 6 7 Single System Availability Report Contents System Group Manager Mode 252 Table 6 8 Diagnostic Results Report Contents Single System Manager Mode 255 Table 6 9 Diagnostic Results Report Contents System Group Manager Mode 258 Table 6 10 Hardware Inventory Report Contents 262 Table 6 11 Hardware Inventory Report Contents System Group Manager Mode 265 Table 6 12 Hardware Changes Report Contents Single System Manager Mode 268 Table 6 13 Hardware Changes Report Contents System Group Manager Mode 270 Table 6 14 Software Inventory Report Contents Single System Manager Mode 274 Table 6 15 Software Inventory Report Contents System Group Manager Mode 277 Table 6 16 Software
182. er do buf fer trans bread unix xfs log recover error unknown buffer type unix XFS error writing log b lock unix XFS error reading log b Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 B Gm Ga a 194334 194333 194332 194331 194330 194329 194328 194327 194326 194325 194324 194323 194322 194321 194320 194315 194314 194313 194310 194309 194308 194307 194306 194304 lock unix reclaim locks invalid N LM version 0 9 unix Incore quota table overf low lboot 1M with larger valu e for NDQUOT unix inode 0 illegal mode 0 unix ec 0 9 TX memory read error unix ec 0 9 RX error data FIFO overflow unix ec 0 9 phy device not found probe failed unix ec 0 9 could not set interrupt vector unix ef 0 9 link fail ch ck ethernet cabl unix ec 0 9 can t allocate Space for transmit descriptors unix ec 0 9 can t allocate space for receive descriptors unix ec 0 9 auto negotiati on fail unix ec 0 9 auto negotiati on timeout unix ec 0 9 only 10Mbit on chip PHY was fou
183. er veo aA ESP Administration mil aaau v Configuration El Reports Logbook System Monitoring System Monitoring balkan csd sgi com PMIE Enabled Disabled No Service Command String Name 1 pmed fusr share pcp bin pmed_wait h HOST 2 nntp echo listgroup comp sys sgi echo quit usr share pcp binitelnet prpbe HOST 119 3 smtp echo expn root echo quit usr share pcp bin telnet probe HOST 25 4 rpcbind lusr sbin rpcinfo p HOST 5 xserver DISPLAY HOST 0 usribin X11 xhost 6 dns nslookup HOST dev null 7 icmp Ibin ping c 3 f HOST Update Figure 5 51 Updated System Monitoring Window Single System Manager Mode ks SI TR 4 219 Chapter 5 Configuring ESP 220 Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to configure system monitoring in system group manager mode 1 Click on the Configuration button 2 Click on the System Monitoring button The interface displays the System Monitoring window Refer to Figure 5 52 aj esp Embedded Support Partner ver 30 A ESP m mil Egan v Configuration Reports E BE Logbook System Monitoring System Monitoring baltic csd sgi com PMIE Enabled Disabled No Service Command String Name 1 pmed fusr share pcp bin omed_wait h HOST 2 nntp echo listgroup comp sys sgi echo quit usr share pcp binitelnet prpbe HOST 119 3 smtp echo expn
184. er when ESP loads the event profile or click on the radio button next to Do Not Subscribe to load the event profile without subscribing the events to the SGM server To reload the system defaults click on the Reload System Defaults button Configuring Events Using the Command Line Interface You can use the espconfig command to manage event profiles Use the following command syntax to list the event profiles that are available on a system and determine which profiles are currently loaded usr sbin espconfig list eventprofile eventprofile name sgmclient client alias sysid system Id gt If you indicate a specific event profile ESP lists only information about that event profile Use the following command syntax to clear the current event list and assigned actions and to install the event profile that is stored in a file usr sbin espconfig load eventprofile profile name allprofiles defaults dontsubscribe sgmclient client alias sysid system Id gt Use the following command syntax to compare a file of event profile data with the events that are currently installed in ESP and to insert any events in the file that are not already installed usr sbin espconfig add eventprofile profile name gt allprofiles defaults dontsubscribe sgmclient client alias sysid system Id gt Use the following command to compare the events that are currently loaded in ESP with an event p
185. ervice Provider Setup window Refer to Figure 4 10 mM esp r l UM Embedded Support Partner v5 aA ESP Administration Configuration Reports Logbook AA Modem Setup P Service Provider Pagg o 0 Fl Service Provider Setup boxelder peachtree sgi com Service Provider Name Modem Name USRobotics Spartster zl Maximum Retry must be at least 6 Maximum Message Length consult your service provider Phone Number no spaces Figure 4 10 Paging Service Provider Pager Web based Interface Setting Up the Paging Parameters ESP for IRIX OS Only 4 Update the parameters Table 4 2 describes the parameters Table 4 2 Paging Service Provider Parameters Parameter Description Service Provider Name Modem Name Maximum Retry at least 6 must be Maximum Message Length consult your service provider Phone number Spaces no Specifies the name of the paging service The interface displays this name on other pages to identify the paging service Do not include blank spaces Specifies the modem to use Select the modem from the menu If the modem that you want to use is not in the menu click on the Modem Setup button to add it Specifies the number of times that ESP should attempt to contact this paging service Specifies the maximum number of characters that this service will accept Contact your paging service provider for this information Specifies the phone number
186. es usr sbin espconfig monitor disable lt service list gt sgmclient all host list gt Use the lt service list gt parameter to specify which services to stop monitoring If you do not use the lt service list gt parameter this command disables all services that are currently monitored on the system Use the sgmclient option to display services on one or more SGM clients Use the all parameter to list services on all SGM clients Use the host 1ist parameter to list services on specific SGM clients 223 About Reports Chapter 6 Viewing Reports This chapter describes how to generate and view the following reports e Events registered reports e Actions taken reports e Availability reports Diagnostic reports e Hardware reports e Software reports e System reports e Site reports ESP generates reports based on parameters that you specify through the Web based interface or command line interface In single system manager mode ESP generates reports from the data that is stored in the ESP database on the local system In system group manager mode ESP generates reports from the information that is stored in the ESP database on the group manager system Figure 6 1 shows an example report generated by the Web based interface Figure 6 2 shows an example report generated by the Web based interface in printable format 225 Chapter 6 Viewing Reports aN es Uu Support Partner ver 30
187. es Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 38 38 38 38 38 38 38 38 38 38 38 39 39 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 41 41 41 41 41 41 41 23 1 232 233 234 235 236 237 238 299 240 241 242 243 244 245 246 247 248 249 250 294 252 253 254 299 256 257 258 259 260 261 262 263 264 265 266 267 268 e filter 1 Cannot lock mutex IFNET Unknow line state Membuf has MT_FREE 1 Membuf has MT FREE 2 Membuf has MT FREE 3 DMA corruption Bad blen Bad membuf chain 1 Bad membuf chain 2 ifnet driver re ntered Memory allocation fail for fram e filter 2 Assertion Memory allocation fail Hwgraph cannot add vertex Memory allocation failure Shared memory null PIO map ioctl reset failure Memory allocation failure PGS f or geninfo PCI IO DMA map allocation faile d ioctl cannot get MAC addr hwgraph missing controller vert ex Firmware missing Memory failed to allocate gt 2 RR BS ioctl event error i
188. es the event list from the ESP 2 0 client stores the list on the SGM server and displays the list of available event classes You can use the Refresh button to verify subscribed events Note The Re resh button does not appear for ESP 3 0 clients Use the Re resh A11 Profilesbuttoninthe Event Profiles window accessible via Configuration Events gt Load to refresh event information from an ESP 3 0 client 185 Chapter 5 Configuring ESP Using the Command Line Interface You can use the espconfig command to subscribe and unsubscribe events e Use the following command syntax to subscribe events usr sbin espconfig subscribe evtype cid class id gt cd class desc gt tid lt type id gt td lt type desc gt pri lt priority gt fac lt facility gt appname lt application name gt sgmclient lt client alias gt sysid lt client system id gt e Use the following command syntax to unsubscribe events usr sbin espconfig unsubscribe evtype cid class id cd class desc gt tid type id td type desc gt pri lt priority gt fac lt facility gt appname lt application name gt sgmclient lt client alias gt sysid lt client system id gt 186 Configuring Actions Configuring Actions Actions are commands that ESP performs in response to events if you set up event action assignments An event action assignment specifies the action that ESP should perform
189. essages usr sbin espconfig disable mail Setting Up the Paging Parameters ESP for IRIX OS Only Setting Up the Paging Parameters ESP for IRIX OS Only QuickPage QPage is a third party client server application that ESP uses to send messages to an alphanumeric pager QPage uses a modem to send an IXO TAP protocol message to a telephone number that is connected to a paging service QPage is integrated in the ESP software suite and its services are accessed through the usr bin espnotify application Refer to Figure 4 8 espnotify Paging OPage Service Telephone Provider Network Figure 4 8 Process for Sending a Page QPage is installed on your system by default and is chkconfig ed off Perform the following procedure to set it up and enable it 1 Enter the following command to turn QPage on chkconfig quickpage on 2 Enter the following command to start the QPage server etc init d qpageserver start Note The QPage server automatically restarts whenever you reboot the system 105 Chapter 4 Setting Up the ESP Environment 106 3 Setup the following paging parameters e Modem parameters that specify the modem that oPage should use to connect to the paging service provider e Paging service provider parameters that provide information about the paging service provider and how to contact it e Pager parameters that provide information about the pager to use The following sections describe h
190. ession demo4 Current actions Action description Action frequency 1 Notify sysadmin on console 86400 secs Commit Figure 5 7 Verification Message for Adding an Event Adding Event to Existing Class 10 Click on the Commit button The interface displays information about the event that was added Refer to Figure 5 8 If you need to update the event click on the update button Be sure to note the sequence number assigned to the event located in the event description next to the event name You need this number to register the event in ESP from an external application Refer to Chapter 9 Logging Events from Applications and Scripts 151 Chapter 5 Configuring ESP a esp d Embedded Support Partner verzo aA ESP Administration mil Set Environment Z Configuration E Reports E Logbook P Events EJ Add Event Figure 5 8 Confirmation Message for Adding an Event Adding Event to Existing Class 152 Configuring Events Adding an Event to a New Event Class in an Existing Event Profile Figure 5 9 shows the Add Event window when you choose the Add new event to a new class in an existing profile option refer again to Figure 5 3 d Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Z Configuration Reports E Logbook P Events b ada EJ Add Event Figure 5 9 Add Event Window Adding Event to New Class 153 Chapter 5 Configuring ESP
191. establish a connection between systems ESP displays a message that indicates this For ESP 2 0 clients you must also configure SGM clients from the client side 118 Setting Up the System Client Parameters System Group Manager Mode Only Table 4 4 Add New Client Window Parameters Parameter Description Client Specifies the fully qualified hostname of a client system hostname Client alias Client node Automatic events subscription Specifies an alias that ESP uses to identify the client This parameter is optional If you do not set this parameter ESP uses the hostname of the client without the domain name This parameter can contain any non blank space character except for single or double quotes Specifies how the client is configured There are two choices Fu11 and Light default A full node is an SGM client that sends data to an SGM server and also keeps a copy of all data in its own database Full nodes require more local disk space than light nodes A light node is an SGM client that sends data to an SGM server but does not keep any data in its own database You can convert a light node to a full node at any time however only data that is generated after the conversion completes is stored in the local database Data generated before the conversion completes is stored only in the database on the SGM server Specifies whether or not ESP should automatically subscribe events with the Event Ma
192. et this parameter to Disabled to specify that ESP should not perform actions for any events if you set this parameter to Disabled it overrides any action settings for individual events Recommendation Set this parameter to Enabled and assign the desired actions for each event 99 Chapter 4 Setting Up the ESP Environment Table 4 1 Global Configuration Parameters continued Parameter Description Shutdown reason Registration with SGI E mail format Specifies whether or not users will be prompted to enter a reason when they shut down the system Set this parameter to Enabled to prompt users for a reason whenever they shut down the system Set this parameter to Disabled to allow users to shut down the system without providing a reason Recommendation Always set this parameter to Enabled to ensure that ESP generates accurate availability metrics Specifies whether or not ESP should send data system hardware and software information event information crash analysis reports and system availability reports to SGI at esp sgi com under specific service contracts SGI uses this data to open trouble tickets and respond to problems on your system before the problems affect system availability Set this parameter to Enabled to have ESP send e mail messages to SGI Set this parameter to Disabled to prevent ESP from sending e mail messages to SGI Recommendation Always set this paramete
193. et unlocked Socket zone init failed Exception count on exit Swap block error Tile cache dirty Low on kernel memory No thread MFREE map overflow Bad free size for bitmap 1 Bad free size for bitmap 2 Bitmap overflow No free slot for rmap log Bad device No interactive reboot No standalone exec mload no ksyms mload bootp kernal mload registration fail mload dynamic load module faile d mload dynamic attach module fai led mload no symbol table Object file not ELF format mload object unreadabl mload driver init failed mload stropen failed mload strload failed mload strload not ELF format mload strload unreadable mload strload init failed mload unload failed mload strstub no queue 1 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 18 18 18 18 18 47 47 47 47 47 47 47 47 47 47 47 47 47 47 48 48 48 48 48 48 48 48 47 47 48 47 47 48 48 49 CO CO CO CO CO CO CO CO CO cO 10 01 WNEF c w CO N H O o 321 322
194. events Date and time of last system boot Length of time that system has been powered up since last system boot Link to a table of all availability events that ESP registered during the specified time period Availability Reports Using the Command Line Interface Use the following syntax of the espreport command to view an availability report usr sbin espreport availability sysid system id host lt hostname gt from mm dd yyyy to mm dd yyyy Use the sysidor host options to select a specific system to include in the report If you do not specify a system the report contains availability information from the local host Use the from and to options to select the range of dates for the report If you do not specify a range of dates the report contains all information up to the current date 253 Chapter 6 Viewing Reports Diagnostic Result Reports If you use the diagnostics that are included in the Internal Support Tools 2 0 or later releases ESP generates diagnostic results reports Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate a diagnostic results report in single system manager mode 1 Click on the Reports button 2 Clickon the Diagnostics button The interface displays the Diagnostic Results window Refer to Figure 6 21 fares p Support Partner ver 30 aA ESP Administration Set Environment ic
195. events and performs actions You can archive the current database to reduce the amount of disk space used on the system Use the esparchive command at a UNIX prompt to archive the current database that ESP is using on a system The esparchive command shuts down ESP momentarily compresses the current database to save space opens a new database to receive data from ESP and restarts ESP You must use the root account to execute the esparchive command this command archives the current database only if it is 10 MB or larger You can use the Web based interface and command line interface to delete database archives that you no longer need Warning When you delete a database archive the information in the database archive is permanently lost You will not be able to view any system information that was stored in the database archive Using the Web based Interface Perform the following procedure to use the Web based interface to delete a database archive 1 Click onthe ESP Administration button 2 Clickon the archive button The interface displays the Delete Archive window Refer to Figure 3 12 87 Chapter 3 Administering ESP fr esp Embedded Support Partner ver 30 T8 ESP Administration mil Set Environment Configuration Reports Logbook Fl Delete Archive deiter csd sgi com Archive Name Start Date End Date M deiter_14261210142003 10 14 2003 10 14 2003 r deiter_14502010142003 10 14 2003 10 14 2003 D deiter 145
196. ew Users Add User Update Password Update Permissions Delete User aM Delete User baltic csd sgi com List of users administrator Delete User Figure 3 10 Delete User Window Web based Interface 85 Chapter 3 Administering ESP 86 4 Select one or more user accounts to delete 5 Clickonthe Delete User button The interface updates the Delete User window Refer to Figure 3 11 aj esp Embedded Support Partner verzo fj ESP Administration mil Set Environment Configuration Reports Logbook AA User Permissions View Users Add User Update Password Update Permissions P Deleteuser Kj Delete User baltic csd sgi com The following user s will be deleted administrator Warning Deleting current user will result in the authentication failure You will not be able to continue use ESP under this username Commit Figure 3 11 Updated Delete User Window Web based Interface 6 Click on the Commit button Using the Command Line Interface Use the following syntax of the espconfig command to delete a user espconfig delete user name user name p user password gt If you do not provide the password for the user account that you want to delete this command prompts you for the password but does not display the password on the screen Manipulating Database Archives Manipulating Database Archives ESP logs data in a database on the system as it registers
197. ey Be ae zwuwuwtutu t 0000000000000 Zz 2 A ee ee Bewwe we OQ O 0 0 0 OQ OO O10 OO 2 ESP for the IRIX OS 3618 3617 3616 3615 3614 3613 3612 3611 3610 3609 3608 3607 3606 3605 3604 3603 3602 3601 3600 35399 3598 3597 3596 Controller NVSRAM downlo leted Controller NVSRAM downlo ed Controller firmware down mpleted Controller firmware down iled Internal download checkp Controller return status on call for requested op Automatic configuration age Array Reset configuration of S Array Change media scan scrub ngs of Storage Array Change media scan scrub ngs of volume Change positions of tray ysical view Revive volume Revive drive Place controller online Change name of volume Change parameters of vol Change cache parameters me Synchronize controller c x5029 ad comp 0x5028 ad fail 0x5027 load co 0x5026 load fa 0x5025 oint 0 x5024 functi eration 0x5023 on Stor 0x5022 torage 0x5021 setti 0x5020 setti 0x501F S in ph Ox501E 0x501D 0x501C 0x501B 0x501A ume 0x 5019 of volu 0x5018 lock 0 x5017 Change name of Storage Array 0 Update cache parameters age Array Change controller to act ec Change controller to pas de Change segment size of v x5016 of Stor 0x5015 ive mod 0x5014 Sive mo 0x5013 olume
198. f SGM servers and clients are used The configmon binary tool handles both functions 21 Chapter 1 Introduction 22 The configmon producer gathers information about the hardware and software configuration Then it checks a file in the var esp directory that contains checksums from the last time that conf igmon was run If the current and old checksums are the same no actionis performed If the con igmon producer detects any differences then the data that differs is sent to the conf igmon consumer via a private conf igmon event The configmon consumer then checks the SSDB and compares the data received from the producer to the SSDB data If no differences in the data exist no action is performed If differences do exist con igmon brings the database up to date and moves the old configuration data into the archive tables Note You can use the u update and f force command line options to force producer data to go to the consumer On non SGM systems both the producer and consumer reside on the local system and the data passes through the Event Manager Event Monitoring ESP is an event driven system Events can come from various sources Examples of events are e Configuration events e Inferred performance events e Availability events e System critical events from the kernel and various device drivers Diagnostic events Starting with ESP 3 0 event management moves outside of the ESP framework A new st
199. g usr sbin espconfig monitor list lt service list gt Use the service list parameter to specify which services to show If you do not use the service list parameter this command lists all services that are available on the system Configuring System Monitoring Use the following the command syntax to show the hosts that are being monitored for selected services usr sbin espconfig monitor show lt service list sgmclient host list gt Use the lt service list gt parameter to specify which services to show If you do not use the lt service list gt parameter this command lists all services that are available on the system Use the sgmclient option to display services on one or more SGM clients Use the host list parameter to specify the SGM clients to view Use the following command syntax to enable monitoring of specific services usr sbin espconfig monitor nable lt service list gt sgmclient all host list gt Use the lt service list gt parameter to specify which services to show If you do not use the lt service list gt parameter this command lists all services that are available on the system Use the sgmclient option to display services on one or more SGM clients Use the all parameter to list services on all SGM clients Use the host 1ist parameter to list services on specific SGM clients Use the following command syntax to disable monitoring of specific servic
200. g Notification Action and E mail Options 191 Chapter 5 Configuring ESP fa esp 4 Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Z Configuration E ts E Logbook EJ Add Notification Action Po v v v x r r P x r E aE Figure 5 34 Add an Action Window Using Notification Action and System Console Options 192 Configuring Actions mM esp Mod Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Z Configuration E Reports 3 Logbook P Actions EJ Add Notification Action baltic csd sgi com 0 0 as v v v x E E E r E E TEE Figure 5 35 Add an Action Window Using Notification Action and GUI Pop up Options 7 Set the parameters for the action Table 5 2 describes the parameters that are available for each type of notification 193 Chapter 5 Configuring ESP Table 5 2 Notification Action Parameters Notification Type Parameter Description E mail notification E mail address es Specifies the e mail address es that receive an e mail notification Tip Separate multiple e mail addresses with a space a comma or a semicolon Subject Specifies the subject of the e mail notification Tip The message cannot include quotation marks single or double Notification message Specifies a message to add to the end of the notification Tip The message cannot include quotation marks single or double Notification fo
201. g espconfig command syntax to add an event usr sbin espconfig add evtyp td type description cid class id cd class description gt throttle throttle value gt nabl disable log nolog acfreq action frequency value gt acid action id acd action description gt pri lt priority gt fac lt facility gt appname app name gt regexp reg expression gt prfid profile id prfn profile name gt sgmclient client alias sysid client system id Use the td option to specify the type description a string enclosed in quotes that describes the event Use the cid option to specify an existing event class ID or use the cd option to provide an existing or new class description a string enclosed in quotes that describes the class If the class does not exist ESP creates a new class Use the throttle option to specify the throttling value which is the number of times the event must occur before ESP registers it If you do not specify this option the default value of 1 is used Use the enable or disable option to specify whether the event is enabled or disabled You can specify only one of these options at a time If you do not specify this option the event is disabled by default Use the 10g or nolog option to specify if ESP should log the event Use the acid option to assign an action to the event by specifying an existing action ID or use the acd o
202. ge for Adding an Event Adding Event to New Class 156 Confirmation Message for Adding an Event Adding Event to New Class 157 Add Event Window Adding an Event to a New Class in a New Profile 158 Add Event Window with Example Parameters Adding an Event to a New Class in a New Profile 160 Verification Message for Adding an Event Adding an Event to a New Class in a New Profile 161 Confirmation Message for Adding an Event Adding Event to a New Class in a New Profile 162 Update Event Window with SGM Clients 165 Update Event Window 165 Event List for Updating an Event 166 Update Event Window with Event to Update 167 Verification Message for Updating an Event 169 Confirmation Message for Updating an Event 170 Batch Events Update Window with SGM Clients 173 Event Batch Update Window 174 xiii List of Figures xiv Figure 5 25 Figure 5 26 Figure 5 27 Figure 5 28 Figure 5 29 Figure 5 30 Figure 5 31 Figure 5 32 Figure 5 33 Figure 5 34 Figure 5 35 Figure 5 36 Figure 5 37 Figure 5 38 Figure 5 39 Figure 5 40 Figure 5 41 Figure 5 42 Figure 5 43 Figure 5 44 Figure 5 45 Figure 5 46 Figure 5 47 Figure 5 48 Figure 5 49 Figure 5 50 Delete User Events Window with SGM Clients 178 Delete User Events Window Web based Interface 179 Verification Message for Deleting an Event 179 Confirmation Message for Deleting an Event 180 Batch Event Subscription Window 183 Events by Subscription Cl
203. gistered Tip Click on the occurrence date to view the logbook entry for that date Date and time at which the event was last registered Tip Click on the occurrence date to view the logbook entry for that date Number of times that the event occurred Message from SYSLOG that generated the event a This column appears only if a report shows events from more than one class Events Registered Reports To drill down a report that contains events from multiple classes to find specific information about an event perform the following procedure 1 Clickonthe c1ass name The interface displays information about events from the class that were registered Refer to Figure 6 6 b i ag Embedded Support Partner ver 30 m ESP Administration mil Set Environment Configuration Logbook Event Report balkan csd sgi com Class Daemon Messages First Last Event Occurrence Occurrence Event No Description va va Count Syslog message 1 Daemon Error 08 13 2003 08 13 2003 1 warning can t get client 06 04 20 06 04 20 address Transport endpoint is not connected 2 Daemon Error 08 13 2003 08 13 2003 warning can t get client 06 41 12 06 41 12 address Transport endpoint is not connected 3 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 06 12 09 06 12 address Transport endpoint is not connected 4 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 35 44 09 35 44 address Transport endpoint is not
204. guration LIE Logbook View Logbook Entries C Last 30 days C Last days 08 13 2003 to 08 13 2003 System Name IP Type System Serial Number IP Address C All subscribed systems M baltic csd sgi com N A 134 16 241 92 O balkan csd sgi com N A 134 16 241 91 Continue Figure 7 4 View Logbook Entries Window System Group Manager Mode 3 Specify the range of dates to view 4 Select the systems to view 5 Clickonthe view Log Entries button The interface displays the specified logbook entries Refer to Figure 7 5 mM es Pg un Support Partner ver 30 a ESP Administration fa Set Environment Configuration e Reports Logbook Logbook Entries fex baltic csd sgi com 08 13 2003 to 08 13 2003 No User Log Date Va 10 administrator 08 13 2003 14 12 58 ran memory tests 2T administrator 08 13 2003 14 34 53 node board swap Generate Report Subject Figure 7 5 Specified Logbook Entries System Group Manager Mode 296 Viewing Logbook Entries 6 Perform one the following actions to view a log entry e Set the check mark next to entry number and click on the Generate Report button Click on the subject link for the entry The interface displays the logbook entry information Refer to Figure 7 6 FIBI Embedded Support Partner v A ESP Administration mi Set Environment Configuration Reports E Logbook Logbook Entries 1 System name baltic csd sgi com Created by administrat
205. guration parameters user configuration parameters and IP address allow access and restrict access lists All changes are effective immediately Use the following command syntax to save an ESP environment usr sbin espconfig save espenv global ipaddr user site customer profile all to filename Use the following command syntax to load an ESP environment usr sbin espconfig load espenv sysid client system id chk check definition filename gt from data definition filename 137 Chapter 5 Configuring Events Configuring ESP This chapter describes how to configure the following components of ESP Events Actions Performance monitoring System monitoring Events are conditions that ESP monitors ESP includes many default events and you can add custom events Example events include panics high processor utilizations and nonmaskable interrupts NMI Events are organized into event classes which enables you to quickly view and update similar events Example event classes include availability system configuration and performance Note Chapter 10 Default Event Classes and Types contains lists of all event classes and event types that ESP includes by default To manage events on your system use ESP to perform the following activities Manage event profiles View existing event classes and events Add events Update existing events Update multiple events at the sam
206. gure 6 40 Example Software Changes Report System Group Manager Mode Table 6 17 describes the contents of the report Table 6 17 Software Changes Report Contents System Group Manager Mode Column Heading Description No Index number in the table Software Name Name of the software application Software Version Version number of the software application Installation Date Date that the software application was installed on the system Removal Date Time Date that the software application was removed from the system Description Description of the software application Using the Command Line Interface Use the following syntax of the espreport command to view a software changes report usr sbin espreport swchanges sysid system id host host name gt from mm dd yyyy to lt mm dd yyyy gt Use the romand to options to specify a range of dates If you do not use these options the report includes all available data 281 Chapter 6 Viewing Reports System Reports 282 There are two types of system reports e System inventory reports e System changes reports System Inventory Reports System inventory reports show the current system and ESP information Using the Web based Interface Perform the following procedure to use the Web based interface to generate a system inventory report 1 Clickon the Reports button 2 Clickon the System button 3 Clickon the Inventory button The inte
207. h SGI Yes Yes 4002 2097418 ESP package updated Yes No 4002 2097419 ESP package uninstalled Yes No 4002 2097420 ESP system information change Yes No 4002 2097421 ESP profile s update Yes No 4002 340 Customer information is updated Yes No 4000 2097152 Live event No No 4000 2097153 System ID change Yes Yes 4000 2097154 Power cycle Yes Yes 4000 2097155 System reset Yes Yes 4000 2097156 NMI Yes Yes 4000 2097157 Panic S W Yes Yes 4000 2097158 Status report Yes Yes 4000 2097159 Software error Yes Yes 4000 2097160 Hardware error Yes Yes 4000 2097161 No error Yes Yes 4000 2097162 Registration Yes Yes 4000 2097163 Deregistration Yes Yes 4000 2097164 Power failure Yes Yes 4000 2097165 System off Yes Yes 4000 2097166 Interrupt Yes Yes 4000 2097167 Panic H W Yes Yes 4000 2097168 Panic Yes Yes 4000 2097169 Controlled shutdown unknown Yes Yes 4000 2097170 Controlled shutdown timeout Yes Yes 4000 2097171 Controlled shutdown 1 unknown Yes Yes 318 ESP for the Linux OS 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 4000 Ce e o o J J J 2097182 2097183 2097184 2097185 2097186 2097187 2097190 2097191 2097192 2097193 2097194 2097195 2097196 2097197 3761 3762 7000100 7000101 7000102 7000103 7000104 7000105 7000106 7000107 7000110 700011 700011 700011 700011 700011 700011 7000117 7000130 7000131 7000132 7000133
208. h point stepover Driver locking error 1 Driver locking error 2 Unknown driver routine Cross processor interrupt 1 Cross processor interrupt 2 R10K spec dma error Process fork error NUMA service error 1 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 327 Chapter 10 Default Event Classes and Types 15 103 T5 104 15 L05 15 106 16 107 16 108 L 17 84 T 109 Fr 17 110 17 L11 C 17 112 G 17 LES C T 114 Insuffic 17 115 Insuffic 17 116 Insuffic 17 117 R10K c 17 18 R10K c 17 119 R10K c 17 120 17 121 17 122 Dequeue f 17 123 Dequeue f 17 124 Invalid 17 125 Invalid 17 126 Invalid 17 127 VCE 17 128 17 129 Duplica 17 130 I 17 131 Memory al 17 132 10 133 18 134 19 135 19 136 19 137 20 138 21 139 Vnode pas 21 40 21 141 N 22 142 328 MLD set topology error NUMA MLD error 1 NUMA MLD error 2 NUMA service error 2 Invalid vfault pages conversion error Invalid node number eeing unaligned memory Invalid virtual page annot swap in K2SEG 1 annot swap in K2SEG 2 a
209. he format specified by the E mail format parameter Each field can hold up to 255 characters you should separate multiple e mail addresses with spaces or commas Recommendation Enter e mail addresses of local personnel that are interested in this information for example system administrators a Any changes that you make to these parameters from an SGM server affect all SGM clients that are currently subscribed to that server 4 Click on the Update button The interface displays a confirmation window 5 Click on the Commit button 101 Chapter 4 Setting Up the ESP Environment 102 Using the Command Line Interface You can use the espconfig command to update the global configuration parameters Use the following command syntax to view the current setting of the event registration parameter usr sbin espconfig show event registration sgmclient client alias gt sysid system id gt Use the following command syntax to enable event registration by ESP usr sbin espconfig nabl vent registration sgmclient client alias sysid system id gt Use the following command syntax to disable event registration by ESP usr sbin espconfig disabl vent registration sgmclient client alias gt sysid system id gt Use the following command syntax to view the current setting of the event throttling parameter usr sbin espconfig show event throttling sgmclient client alias sysi
210. i com PMIE Enabled Disabled No Service Command String Name 1 pmcd lusr share pcp bin pmcd wait h HOST 2 nntp echo listgroup comp sys sgi echo quit usr share pcp bin telnet prpbe HOST 119 3 smtp echo expn root echo quit usr share pcp bin telnet probe HOST 25 4 rpcbind fusrisbin rpcinfo p HOST 5 xserver DISPLAY HOST 0 usribin X11 host 6 dns nslookup HOST dev null 7 icmp Ibin ping c 3 f HOST Update XI SI 15 S Figure 5 49 System Monitoring Window Single System Manager Mode 3 Click on the Enabled radio button to enable performance monitoring or click on the Disabled radio button to disable performance monitoring Note This setting is also available in the Performance Monitoring window If you change the PMIE setting in the System Monitoring window the setting also changes in the Performance Monitoring window Click on the Enabled checkbox for each service that you want to monitor Click on the Update button The interface displays a verification screen Refer to Figure 5 50 217 Chapter 5 Configuring ESP fal es p EE Embedded Support Partner v aA ESP Administration mi Set Environment Z Configuration E Reports l Logbook FZ Update System Monitoring Figure 5 50 System Monitoring Change Verification Screen Single System Manager Mode 6 Click on the Commit button 218 Configuring System Monitoring ases p Support Partn
211. i com NA 91 of 103 ESP3 0 C balkan balkan csd sgi com NA 407 of 898 ESRO Continue Batch Event Subscription Window Figure 5 29 183 Chapter 5 Configuring ESP Network Driver VME FDDI Oof 11 Network Driver VME GFE Enet Oof4 Network Kernel IFNET 0 of 1 SI XS S x Network Kernel MBUF O0 of 1 Newport Timeout O0 of 3 NMI Oof3 OS Memory 0 of 25 OS PDA Oof6 SIC a5 XI KI OS SYSCALL 0of2 Performance 0 of 33 Power Supply Oof2 Saudit Oof2 M M M M M M M a SES 0 of 1 Storage TP9400 0 of 445 System Configuration 110f 11 System Error 0 of 17 SI XXX XX z lt User 0 of 12 Venice Timeout Oof 7 O 2208 N O Figure 5 30 Events by Subscription Class Window k Ee a e 905 4 184 Configuring Events This window displays all event classes available on the selected client Set the check mark to select an entire class for subscription or unsubscription Click on a class description to access the individual events in a class The interface displays the current status of all events in the class Click on the Subscribe button to subscribe all events in a class ESP subscribes all events in the class that have event registration enabled on the SGM client Click on the Unsubscribe button to unsubscribe all events in a class ESP unsubscribes all events in the class If no event classes are listed for an ESP 2 0 client click on the Refresh button ESP retriev
212. ibe availability events Unsubscribe availability events EventMon Started EventMon Stopped Eventmon invalid CPU command Eventmon invalid FPE command Eventmon mutex initialization f ailure Eventmon thread init error Eventmon no input buffers Eventmon can t find string Eventmon too many strings Eventmon database table empty Eventmon condition variable fai lure Eventmon fatal API error Eventmon Non fatal API Error Eventmon cannot open amticker t imestamp file Eventmon database init failure Eventmon database library load failure esphttpd started esphttpd stopped esphttpd invalid CPU command esphttpd invalid FPE esphttpd mutex initialization f ailure esphttpd thread error esphttpd condition variable fai lure esphttpd thread allocation erro r esphttpd socket bind error esphttpd socket listen error uuuwutu zu 000000 z Oo zou ey ee 0 20 Or QUO z Oo Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ey Aea O O O 07070 uuuuu zu 000000 z Oo zuwuwuu oo00 0 zi Oo ESP for the IRIX OS 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4003 4004 4004 rw NNRPR PR 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 20974 50
213. ic rebuild has starte d 5 Hard disk PFA condition found this disk may fail soon 4 Configuration on disk converted 804 Configuration cleared 801 New configuration received 80 0 Set real time clock 703 Event log entries lost 701 Event log empty 700 Back end fibre alive 645 Back end SCSI bus alive 643 Channel online 641 Server alive 516 User logged out 515 User logged in 514 System started 512 Dual controllers entered nexus 424 Dual controllers enabled 422 Inserted partner 421 Relinquished partner 420 Updated partner s status 419 Controller s Partner Has Been R emoved 417 BBU recondition needed 416 Controller device start complet e 413 Controller entered normal cache mode 412 Controller entered Conservativ Cache Mode 411 BBU calibration cycle is cancel ed 409 BBU calibration cycle finished 408 BBU calibration cycle started 407 Installation aborted 403 BBU reconditioning is canceled 402 Yes Yes Yes Yes zu O 0 Bee ee zu Z zu Zz 0000000000 0 ry ta aA a o0o000 0 2 O Yes Yes Yes Yes zu Oo 0 zc uuu zu z uu Zz 0000000000 0 uuuuu O O OQ zZ O 351 Chapter 10 Default Event Classes and Types 352 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80
214. ick on the Software button 3 Click on the Inventory button The interface displays the Software Inventory Reports for System Group window Refer to Figure 6 35 far esp Embedded Support Partner ver 30 ESP pene mil Set Environment Configuration E Reports BB Logbook AA P inventory Changes Software Inventory Report Date 08 13 2003 Time fi3 50 03 Sys System Serial Current System Name Type Number IP Address Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi com NA 134 16 241 91 Subscribed Continue Figure 6 35 Software Inventory Reports for System Group Window System Group Manager Mode 4 Specify the date and time of the software inventory that you want to view 5 Click on the Generate Report button Figure 6 36 shows an example software inventory report 275 Chapter 6 Viewing Reports aM esp ag Embedded Support Partner verzo aA ESP Administration mi Set Environment Configuration Logbook AA b Software p inventory changes Software Inventory Report T baltic csd sgi com 08 13 2003 13 50 03 4Suite 10 records per page GO Installation Date 1 4Suite 0 11 2 02 26 2003 No Software Name Version Software Description Python tools and libraries for XML processing and databases 3 5b2 Header file and library for 2 Canna devel 50 a221 1 06 13 2003 eng programs which use 3 5b2 50 as21 1 0 8 CpuMemSets processor and sgi221c1 06 18 2003 memory
215. ides a quick insight to problems Provides an effective means of delivering service which greatly increases system availability with accurate problem diagnosis ESP Benefits ESP Benefits continued Benefit to Service Provider Benefit to Customer Extended Package Centralized event processing group management System Group Centralized support administration group management Centralized automated response and notification group management Centralized site troubleshooting Enables you to collect and display all information from one central location which helps to determine causes of problems on systems within the site Provides a single location from which all support activities can be performed for a group of systems Provides visibility to problems as they occur Provides accurate system and site data online Provides the ability to resolve problems from a central location Provides the entire set of circumstances in one place Eases administration and service tracking Provides proactive support Provides a quick insight to problems Enables extensive tracking of availability and system performance Provides an efficient mechanism to fix problems on site 13 Chapter 1 Introduction ESP Architecture 14 Table 1 1 ESP Benefits continued Component Feature Benefit to Service Provider Benefit to Customer Performance Proactive automated Assis
216. idity GFX Command GFX Validity Venice Timeout Venice Resource Venice Validity MGRAS Resource MGRAS Command MGRAS Timeout MGRAS Validity Newport Timeout Newport Command Newport Validity System Controller Net Driver ATM OC3 Everest Net Kernel ATM SVC Net Driver ATM PCI Speedracer Net Kernel ATM TCPIP Net Kernel ATM ARP Net Driver ATM Lego RAS Kernel XTCI Storage TP9100 Storage TP9400 CXFS XFS ESP for the IRIX OS 84 85 4000 4002 4003 4004 4005 7001 XVM snmp Availability System Configuration ESP Internal Events ESP Event Manager Diagnostic DE Default Event Types The following output from the espconfig command shows the default event types that ESP includes on a system running the IRIX OS irixf espconfig list evtype Event types for 351797 Class Id Type Id Type Description Enabled Log Enabled 4000 2097152 Live event No No 4000 2097153 System ID change Yes Yes 4000 2097154 Power cycle Yes Yes 4000 2097155 System reset Yes Yes 4000 2097156 NMI Yes Yes 4000 2097157 Panic S W Yes Yes 4000 2097158 Status report Yes Yes 4000 2097159 Software error Yes Yes 4000 2097160 Hardware error Yes Yes 4000 2097161 No error Yes Yes 4000 2097162 Registration Yes Yes 4000 2097163 Deregistration Yes Yes 4000 2097164 Power failure Yes Yes 4000 2097165 System off
217. if the message contains more than one word a Specifies that an audio file should be played The usr bin ssplay application plays the audio file Audio notification cannot be performed without graphical notification Audio notification can be performed only on the local host About the espnotify Tool display Specifies the display to use If you do not specify a display the window is displayed on the host specified by the DISPLAY environment variable geomet ry Specifies an optional X Window System geometry string for the window icon number title in the standard WIDTHxHEIGHTxXOFFxYOFF format For example g 120x80x50x100 specifies a window that is 120 pixels wide by 80 pixels high and is located 50 pixels from the left edge of the screen and 100 pixels from the top edge of the screen Refer to the x 1 man page for more information Specifies an optional image to display as an icon for the window Specifies an optional priority message which is determined by the value that you specify for number The number parameter can be a value from 1 to 7 espnot ify attaches a label to the message based on the value of number 1 or 2 Critical System Error 3 System Error 4 System Warning or5to7 System Information Specifies an optional title of the window Enclose lt title gt in double quotes if the title contains more than one word For example the following com
218. ification option in the Add Action window Example Creating an Action to Send an E mail The first example shows how to set up an ESP action to send notification by E mail 1 Click on the Configuration button 2 Click on the Actions button 3 Click on the Add button 4 Click on the radio button next to Other action 5 Click on the Continue button 309 Chapter 8 Sending Notifications 6 Update the parameters Table 8 1 lists the parameters for this example Table 8 1 Example Action Parameters for Sending an E mail Notification Field Setting Action description Send notification via e mail to abci238sgi com Action string usr bin espnotify E abc123 sgi com m SD s An event was just registered Execute action as nobody Action timeout 600 Figure 8 4 shows an interface page with the proper settings for this example aj esp Embedded easi Partner ver 30 a ESP em mil Set Environment Reports E Be Logbook AA Add An Action Action description Faation via e mail to abc123 sgi com Action string D D s An eventwas just registered Execute action as o mbody Action timeout feo second s Figure 8 4 Example Action Parameters for Sending an E mail Message 7 Click on the Add button Figure 8 5 shows the verification message for this example 310 Invoking espnotify from ESP Embedded Support Partner 5 A ESP Administration mil Set Environment Rep
219. igure 1 4 Figure 1 5 Figure 1 6 Figure 1 7 Figure 1 8 Figure 2 1 Figure 2 2 Figure 2 3 Figure 2 4 Figure 2 5 Figure 2 6 Figure 2 7 Figure 2 8 Figure 2 9 Figure 2 10 Figure 2 11 Figure 2 12 Figure 2 13 Figure 2 14 Figure 3 1 Figure 3 2 Figure 3 3 Figure 3 4 Figure 3 5 Figure 3 6 ESP Functional Diagram 2 System Group Management Block Diagram 5 Named Groups 6 Full and Light Nodes 8 Group Management Over Hierarchies 10 ESP Architecture Using Web Browser 17 ESP Architecture Using Command Line Interface 18 Sending Event Information to SGI 27 ESP Opening Page 45 Entering a Username and Password 46 ESP Main Page Single System Manager Mode 47 ESP Main Page System Group Manager Mode 48 Toolchest Menu 49 Icon Catalog 50 ESP Opening Page 51 Entering a Username and Password 52 ESP Main Page Single System Manager Mode 53 ESP Main Page System Group Manager Mode 54 ESP Opening Page 55 Entering a Username and Password 56 ESP Main Page Single System Manager Mode 57 ESP Main Page System Group Manager Mode 58 Choosing the System to Update the Customer Profile 64 Update Customer Profile Window Web based Interface 65 Network Permissions Window Web based Interface 69 Current User List Web based Interface 72 Add User Window Web based Interface 74 Update Password Window Web based Interface 77 xi List of Figures xii Figure 3 7 Figure 3 8 Figure 3 9 Figure 3 10 Figure 3 11 Figure 3 1
220. igure 6 15 Figure 6 16 Figure 6 17 Figure 6 18 Figure 6 19 Updated System Monitoring Window Single System Manager Mode 219 System Monitoring Window System Group Manager Mode 220 Update System Monitoring Window System Group Manager Mode 221 System Monitoring Change Verification Screen System Group Manager Mode 221 Updated System Monitoring Window System Group Manager Mode 222 Example Report Web based Interface 226 Example Report Web based Interface Printable Format 227 Example Report Command Line Interface 229 Event Reports Window Single System Manager Mode 230 Example Events Registered Report Single System Manager Mode 231 Events Registered in a Specific Class Single System Manager Mode 233 All Occurrences of a Specific Event Single System Manager Mode 234 Event Reports for System Group Window System Group Manager Mode 235 Event Reports Window with List of Classes System Group Manager Mode 236 Example Events Registered Report System Group Manager Mode 237 Events Registered in a Specify Class System Group Manager Mode 239 All Occurrences of a Specific Event System Group Manager Mode 240 Action Reports Window Single System Manager Mode 242 Example Actions Taken Report Single System Manager Mode 243 Actions Report for System Group Window System Group Manager Mode 244 Example Actions Taken Report System Group Manager Mode 245 Availability Reports Window Single System M
221. ing command syntax to add a new type of permission to a system usr sbin espconfig add permdesc perm permission name gt desc permission description Use the following command syntax to delete a specific type of permission from a system usr sbin espconfig delete permdesc perm permission name Use the following command syntax to list permissions for a user usr sbin espconfig list userperm name user name perm permission name gt If you do not specify a user name this command lists all users If you do not specify a permission name this command lists all permissions If you do not specify a user name or permission name this command lists all permissions for all users Use the following command syntax to add new permissions for a user usr sbin espconfig add userperm name user name perm permission name gt Table 3 3 lists the settings for the permission name parameter 83 Chapter 3 Administering ESP Table 3 3 Command Line Interface User Permission Settings Permission Setting ESP administration and set environment Configuration Event registered actions taken diagnostic results and site reports t SPpermission set_environment E n Ppermission configuration E n Ppermission events_actions_diag_reports Availability reports ESPpermission availability_reports Hardware and software configuration ESPpermission hw_sw_reports report
222. inistration mil Set Environment Reports Logbook AA P Events Load Profile Add Update Batch Update Delete subscription Add Event balkan csd sgi com Profile name Demo Event class Demo1 Event description Demo1 Event1 Event status Enabled Occurrences prior to registration 1 Application name demotapp Priority Not set ili Not set Regular expression Current actions Action description Action frequency 1 Notify sysadmin on console 86400 secs Commit Figure 5 15 Verification Message for Adding an Event Adding an Event to a New Class in a New Profile 10 Click on the Commit button The interface displays information about the event that was added Refer to Figure 5 16 If you need to update the event click on the update button Be sure to note the sequence number assigned to the event located in the event description next to the event name You need this number to register the event in ESP from an external application Refer to Chapter 9 Logging Events from Applications and Scripts 161 Chapter 5 Configuring ESP aj esp a Embedded Support Partner ver 30 a ESP Administration mil Set Environment Z Configuration JE Reports E Logbook EJ Add Event Figure 5 16 Confirmation Message for Adding an Event Adding Event to a New Class in a New Profile 162 Configuring Events Using the Command Line Interface Use the followin
223. ins only systems that contain that type of processor Choose the type of site report to generate The following options are available The System information option generates a site information report which includes the following information system name IP type if applicable processor type OS version the group that includes the system the system activation date the date when system was added to the group for the first time and system deactivation date the date when system was unsubscribed The All events option generates a report of all available events The Events by class generates a report of events from specific classes 4 Clickonthe Generate Report button The interface displays the report Figure 6 48 shows an example of a site information report 291 Chapter 6 Viewing Reports esp SS Embedded Support Partner ver 30 ESP perum mil Set Environment I Configuration E Reports WE Logbook Site Information Report Activation System Name IP Group Date Deactivation No va Type Processor os va va Date 1 balkan csd sgi com None 900 MHz Linux desktop 08 07 2003 Active Itanium2 2 4 20 sgi221c4jlan 2 baltic csd sgi com None 900 MHz Linux Unknown 07 23 2003 Active Itanium 2 2 4 20 sgi221c4jlan Figure 6 48 Site Information Report Using the Command Line Interface Site reports are not available from the command line interface 292 Chapter 7 Using the ESP Logbook This cha
224. interface e Opening a URL in a Web browser e Using the Embedded Support Partner icon e Entering the launchESPartner command Note The Embedded Support Partner icon and 1aunchESPartner command are available only for the IRIX OS Table 2 1 lists error messages that might appear when you attempt to start the Web based interface It also lists the cause of each message and the actions you should perform to correct the problems that caused the error messages Table 2 1 ESP Startup Error Messages Error Message There was no response The server could be down or is not responding Forbidden Request The current request was forbidden Please check your permissions Cause Solution The ESP Web server isnotrunningonthe Verify that the system is running Reboot system or the system is down the system if necessary Verify that the ESP Web server esphttpd is running on the system Restart the ESP Web server if it is not running If the esphttpd server is not running verify that ESP is chkconfig ed on Your system does not have permission to Add your system to the allow access access the ESP Web server list or remove it from the restrict access list Refer to Setting Up the Network Permissions on page 68 42 Using the Web based Interface Table 2 1 ESP Startup Error Messages continued Error Message Cause Solution Forbidden Request The current request was
225. ion E mail Address E mail address of the site contact person ESP sends a copy of any automated e mail messages to this address Country Country where the site is located Optional Parameters Site ID Identification number for the site Street Address 1 Street address for the site Street Address 2 Street Address 3 City City where the site is located State State where the site is located Postal Code Zip Code Postal code or zip code of the site location a Information in the required fields is necessary to enable automatic call logging If this information is not pro vided automatic call logging is disabled b Although these fields are optional it is recommended that you provide this information 3 Click on the Add button Setting Up the Customer Profile Using the Command Line Interface You can use the espconfig command to view set up or modify the customer profile from the command line interface e Use the following command syntax to view the current customer profile usr sbin espconfig show customer profile host host name alias client alias gt sysid lt systemid gt e Use the following command syntax to set up the initial customer profile usr sbin espconfig create customer profile fname lt first name gt lname last name gt phone lt phone gt email lt email gt streetl1 street address linel gt street2 street address line2 gt street3 street address line3
226. ion to remote volume down 0x6503 Data on mirrored pair unsynchro No Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes No No Yes Yes Yes Yes Yes Yes Yes Yes Yes 355 Chapter 10 Default Event Classes and Types 356 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3335 3334 3333 3332 3331 3330 3329 3328 3327 3326 3325 3324 3323 3322 3321 3320 3319 3318 nized 0x6402 Dual secondary volume conflict 0x6401 Dual primary volume conflict 0 x64 Snapshot volume failed 0x62 Snapshot repository volume capa city full 0x6201 Snapshot repository volume capa city threshold exceeded 0x62 Internal configuration database full 0x6101 Diagnostics rejected configur ation error on this controller S alternate 0x5617 Diagnostics rejected configur ation error on controller 0x56 16 This controller s alternate fai led diagnostics write test 0x5 610 Diagnostics write test failed o n controller 0x560F This controller s alternate fa led diagnostics read test 0x5 o o H e Diagnostics read test failed on controller 0x560D Diagnostics rejected CtlrDiag task on controller s alternate cannot obtain Mode Select lock 0x560C Diagnostics rejected CtlrDiag task cannot obtain
227. iority to syslog warning 324 and the time to the time that emgrlogger or esplogger received the event Then it passes this information and the message to eventmond Chapter 10 Default Event Classes and Types This chapter lists the default event classes and events that ESP includes ESP for the Linux OS Default Event Classes The following output from the espconfig command shows the default event classes that ESP includes on a system running the Linux OS linuxf espconfig list evclass ClassId Class description 4000 Availability 4001 Performance 4002 System Configuration 4005 Diagnostic 7100 Kernel Messages 7110 User Messages 7130 Daemon Messages 317 Chapter 10 Default Event Classes and Types Default Event Types The following output from the espconfig command shows the default event types that ESP includes on a system running the Linux OS linux espconfig list evtype Event types for 8006913E029 Class Id Type Id Type Description Enabled Log Enabled 4002 2097408 Configmon init Yes Yes 4002 2097409 Sysinfo changed Yes Yes 4002 2097410 Hardware installed Yes Yes 4002 2097411 Harwdare de installed Yes Yes 4002 2097412 Software installed Yes Yes 4002 2097413 Software de installed Yes Yes 4002 2097414 System change Yes Yes 4002 2097415 Configuration error Yes Yes 4002 2097416 ESP registered with SGI Yes Yes 4002 2097417 ESP deregistered wit
228. iptions You must provide a string enclosed in quotes U se the throttle option to update the throttling value which specifies the number of times that the event must occur before ESP registers it Use the enable option to enable registration of the event or use the disable option to disable registration of the event Use the 1log or nolog option to specify if ESP should log the event U se the acid and acd options to assign actions to the event This command can add only one action at a time if you want to assign more than one action to an event you must enter the command multiple times Specify an action ID with the acid option Specify a string enclosed in quotes with the acad option 171 Chapter 5 Configuring ESP 172 Use the noacidand noacd options to remove an action that is already assigned to the event Specify an action ID with the noacid option Specify a string enclosed in quotes with the noacd option Use the pri ac appname and regexp options to provide more information about the event priority facility application name and regular expression Use the pr idor prfn option to add the event to an event profile Use the noprfid or noprfn to remove the event from an event profile Use the following syntax to update a custom class description usr sbin espconfig update evclass cid class id cd class description sgmclient client alias sysid client system i
229. iration Controller cache battery ly charged Controller cache task fa Controller deferred erro Controller cache not enabled or 0x2113 is ful 0x2112 iled 0 x2111 r 0x21 OD was internally disabled 0x210 A Controller cache manager encing errors Clear requested on contr ache manager s DACSTORE xperi 0x2108 oller c 0x2107 ESP for the IRIX OS 3425 Update requested on controller No No cache manager s DACSTORE 0x210 6 3424 Controller cache reconfigure ev No No ent 0x2105 3423 Controller cache synchronizatio No No n purge event 0x2104 3422 UPS battery is fully charged 0 No No x2103 3421 Cache mirroring on controllers No No not synchronized 0x2102 3420 Alternate controller checked in No No late 0x2101 3419 Initialization resumed on volum No No e 0x2032 3418 Initialization started on volum No No e 0x2031 3417 Initialization completed on vol No No ume 0x2030 3416 Automatic volume transfer compl No No eted 0x202F 3415 Redundancy check resumed 0x202 No No D 3414 Redundancy check completed 0x2 No No 02C 3413 Redundancy check started 0x202 No No B 3412 Modification reconfigure resu No No med 0x202A 3411 Modification reconfigure comp No No leted 0x2029 3410 Modification reconfigure star No No ted 0x2028 3409 Reconstruction resum
230. ix Failed to add swap file error 0 9 unix Swap out failed on logic al swap 0 9 blkno for proc ess vhand unix vhand runing low on swap handle lists only 0 9 left unix rtodc preposterous time in tod chip unix I04 NVRAM time of day ch ip reports invalid RAM or time unix Environment segment inva lid Unable to program FLASH RA M unix Environment segment inva lid Unable to zero FLASH RAM unix Process 0 9 sent SI GBUS due to Bus Error unix Process 0 9 sent SI GBUS due to Memory Error in SIM M unix SCSI Bus 0 9 ID 0 9 LUN 0 9 SCSI cmd 0x 0 9 timeout after 0 9 sec unix Integral SCSI bus rese t unix BIST Fails slot 0 9 Code unix BIST Timed Out 3 seco nds slot 0 9 unix SCSI tape Uncorrectabl e media error unix SCSI tape Hardware err or Non recoverable unix SCSI tape Unrecoverabl e media error unix SCSI tape requires cl aning unix plp free context out of order unix plp memory error occure d during a DMA transation unix plp context IRQ out of order unix plp init failed out of Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 379 Chapter 10 Default Event Classes and Types 380 7001 7001 7001 7001 7001 7001 7001 7001 7001
231. l rule is more useful because it considers the reported bandwidth of each network interface However in some situations this value is zero in that case an absolute threshold based rule like this one is more useful for this reason it should be applied to some network interfaces but not others use the interfaces variable to filter this A response came from a shell ping PMDA application or service probe A failure occurred in a shell ping PMDA application or service probe 214 Configuring Performance Monitoring Using the Command Line Interface You can use the espconfig command to configure performance monitoring Use the following command syntax to enable performance monitoring usr sbin espconfig on performance Use the following command syntax to disable performance monitoring usr sbin espconfig off performance Use the following command syntax to list the current performance monitoring settings and PMIE rule settings usr sbin espconfig list performance status enable disable Use the status option to list the current status on or off of performance monitoring on a system Use the enable option to list all PMIE that are currently enabled Use the disable option to list all PMIE that are currently disabled Use the following command syntax to enable PMIE rules usr sbin espconfig enable performance pd all lt pmie rule description Use the a11 option to enable all PMIE rules Use the
232. led ESP moves it from the restrict access list to the allow access list to enable it for Web server access If you specify a new IP address ESP adds it to the allow access list to enable it for access to the Web server Use the following command syntax to restrict IP addresses from accessing the ESP Web server usr sbin espconfig disable ipaddr ip address ip address You must specify at least one IP address If you specify an IP address that is disabled it remains disabled If you specify an address that was enabled for Web server access ESP moves it from the allow access list to the restrict access list to prevent it from accessing the Web server If you specify a new IP address ESP adds it to the restrict access list to prevent it from accessing the Web server Use the following command syntax to delete IP addresses from the access lists on the system usr sbin espconfig delete ipaddr ip address gt ip address gt You must specify at least one IP address Use the following command syntax to list the IP addresses that are contained in the access lists on the system and the current state of the IP addresses usr sbin espconfig list ipaddr ip address ip address enabled disabled If you do not specify an IP address this command lists all IP addresses in the access lists on the system If you specify the enabled option this command lists only the IP addresses that are in the allow
233. lients to configure these parameters This restriction is caused by limitations of PMIE Central Logbook Capability ESP 3 0 includes a feature that enables you to create logbook entries for SGM clients on the SGM server The logbook entries are stored on the SGM server This feature enables you to store all logbook data on a common system which makes it easier to access information about multiple systems You can specify which system each logbook entry is for 11 Chapter 1 Introduction ESP Benefits 12 Table 1 1 lists the benefits that ESP provides for service personnel and customers Table 1 1 ESP Benefits Component Feature Benefit to Service Provider Benefit to Customer Base Package Single Web based Increases usability of Provides fast and Single System interface support tools onasingle effective service Manager system Broad and useful support functionality Centralized event processing single system Centralized automated response and notification single system Remote support Provides an integrated set of tools that work in a single framework while increasing support coverage Enables you to collect and display all information from one central location Provides visibility to problems as they occur Provides a virtual seat into the site remotely Provides consistent and wide coverage on systems Provides the entire set of circumstances in one place Enables proactive support Prov
234. mand displays a window on the local host refer to Figure 8 2 usr bin espnotify c This is the message to display D localhost 0 t This is the title i This is the message to display Figure 8 2 Displaying a Message on an X Window System Display 307 Chapter 8 Sending Notifications 308 Sending an E mail Message Use the following format of the espnotify command to send an e mail message usr bin espnotify E address f filename m message n lt number gt o lt options gt s lt subject gt This format of the espnot ify command has the following command line options m address Specifies the e mail addresses that should receive the message Enclose address in single quotes if the list contains more than one address filename Specifies a text file to use as content for the message message number options subject You cannot use the f and m options at the same time Specifies text to use as content for the message Enclose message in single quotes if the message contains more than one word You cannot use the f and m options at the same time Specifies an optional priority message which is determined by the value that you specify for number The number parameter can be a value from 1 to 7 espnoti y attaches a label to the message based on the value of lt number gt 1 or 2 Critical
235. mat E mail specified format Figure 4 7 Global Configuration Window Web based Interface 98 Setting Up the Global Configuration Parameters 3 Setthe parameters Table 4 1 describes the global configuration parameters Table 4 1 Global Configuration Parameters Parameter Description Register events Throttle events Enable actions Specifies whether or not ESP should register events in the ESP database Set this parameter to Enabled if you want to register event information in the ESP database on your system Set this parameter to Di sabledif you do not want to register event information in the ESP database on your system if you set this parameter to Disabled it overrides the individual event settings Recommendation Always set this parameter to Enabled to capture all event information in the ESP database on your system Specifies whether or not ESP should throttle events Set this parameter to Enabled to require that a specific number of events must occur before the event is registered in the ESP database on your system Set this parameter to Disabled to register every event in the ESP database Recommendation Set this parameter to Enabled and configure the individual throttle values for each event Specifies whether or not ESP should perform actions Set this parameter to Enabled to specify that ESP should perform any assigned actions in response to all events that occur S
236. maui System Information maui sgi com 1015961831 1015961831 1015357057 0 7 NULL NULL NULL NULL NULL NULL 0 0 NULL NULL 03 12 2002 11 37 11 Availability 4000 Status report 2097158 21 B0006011 27 Chapter 1 Introduction 28 Console Software The ESP base package includes console software that enables you to interact with it from a Web browser The console software uses the Configurable Web Server esphttpa to receive input from the user send it to the ESP software running on the system and return the results to the user inetd invokes esphttpd whenever a Web server connection is needed The console software also includes a report generator core and a set of plugins to create various types of reports These reports are based on the data that ESP tasks provide such as configmon availmon etc In the base package you can access the following types of reports e System hardware and software configuration reports current and historical e System event reports e Event action reports e Local system metrics MTBI availability etc e ESP configuration The extended package enables you to generate enhanced site level reports and reports for any system on the site Web based Interface If you use a graphical Web browser for example Netscape Communicator to access the Web server the console software provides a graphical Web based interface that supports the following functionality e Configuring the behavior
237. ministration mil Set Environment Iv Configuration E Reports l Logbook E Event Report Daemon Messages Diagnostic Kernel Messages Performance System Configuration User Messages Figure 6 9 Event Reports Window with List of Classes System Group Manager Mode 6 Select the event classes to include in the report 7 Click onthe Generate Report button 236 Events Registered Reports Figure 6 10 shows an example events registered report aN esp bedded Support Partner ver 30 aA ESP prem E Set Environment v Configuration E Reports l FE Logbook All Events Report E baltic csd sgi com 08 13 2003 to 08 13 2003 fic records per page First Last Class Event Description Occurrence Occurrence Event No va va va va Count 1 Performance Low average processor 08 13 2003 08 13 2003 1 utilization 00 01 12 00 01 12 2 Performance Low average processor 08 13 2003 08 13 2003 1 utilization 00 11 11 00 11 11 3 Performance Low average processor 08 13 2003 08 13 2003 utilization 00 21 12 00 21 12 4 Performance Low average processor 08 13 2003 08 13 2003 utilization 00 31 12 00 31 12 5 Performance Low average processor 08 13 2003 08 13 2003 utilization 00 41 12 00 41 12 6 Performance Low average processor 08 13 2003 08 13 2003 utilization 00 51 12 00 51 12 7 Performance Low average processor 08 13 2003 08 13 2003 utilization 01 01 11 01 01 11 8 Performance Low average processor 08 13 2003 08 13 2003 utiliz
238. n Number Number Ro Date NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 NA 07 23 2003 No Part Name Location zt z 1 RACK 001 NA 2 MODULE 001c05 NA 811 NA 4 NODE 0 NA 5 CPU 0 NA 6 CPU 1 NA 7 NODE 1 NA 8 CPU 2 NA 9 CPU 3 NA 10 MODULE 001c08 NA zZ ze EN zZ ze EM zZ z z rE rE rrr r z mUbBBBBPBPBPPIII z z Zz Z gt zZ m Figure 6 28 Example Hardware Inventory Report System Group Manager Mode 264 Hardware Reports Table 6 11 describes the contents of the report Table 6 11 Hardware Inventory Report Contents System Group Manager Mode Column Heading Description No Index number within the table Part Name Name of the part Location Location where the part is installed Part Number Part number for the part Serial Number Serial number of the part Revision Revision level of the part Installation Date Date that the part was installed Using the Command Line Interface Use the following command to view a hardware inventory report configmon h 265 Chapter 6 Viewing Reports 266 Hardware Changes Reports Hardware changes reports show all hardware that has been installed or deinstalled with a specified time period Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate a hardware cha
239. n Action window Refer to Figure 5 31 Mesp Embedded SUPRA Partner TS ESP prem Imi Set Environment Reports i EDS AA Actions P Add Update Enable Disable Add An Action Notification action C Other action Continue Figure 5 31 Add an Action Window 3 Specify how you want to create the action string To have ESP build a notification action string from menu options that you select click on the radio button next to Notification action Use this option if you do not know the appropriate syntax of the espnotify command for the notification that you want to create To manually enter the action string click on the radio button next to other action Use this option if you know the syntax of the espnotify command for the notification that you want to create or if you want to create an action that is not a notification 4 Click on the Continue button Configuring Actions The interface updates the Add An Action window The following subsections describe how to use this window Using the Notification Action Option Figure 5 32 shows the Add an Action window when you choose the Notification Action option S esp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment Z Configuration E Reports Logbook AA P Actions add Update Enable Disable Add Notification Action Action description El 3 h 3A 3 3 3 Type of notification e mail notification
240. n event profile usr sbin espconfig refresh eventprofile lt profile name gt sgmclient lt client alias gt sysid lt system Id gt Configuring Events Viewing Event Classes and Events You can use the espcon ig command to view all events and event classes that are available on your system Use the following command syntax to list the event classes that are loaded on your system usr sbin espconfig list evclass The output lists the event class ID and event class description Refer to Chapter 10 Default Event Classes and Types for a list of the default event classes Use the following command syntax to view the event types that are loaded on your system usr sbin espconfig list evtype cid class id cd class description enabl disable log nolog sgmclient lt alias gt Use the cid option to show events with a specific class ID value Use the ca option to show events with a specific description If you do not use the cid or cd option this command lists all event types Refer to Chapter 10 Default Event Classes and Types for a list of default events The following command syntax shows all information about an event usr sbin espconfig show evtype tid type id td type description sgmclient lt alias gt Use the t id option to show events with a specific type Use the td option to show events with a specific description If the type descripti
241. n the class 5 Update the Action Frequency values 6 Click on the Updat e button Updates the action frequency for multiple events Perform the following procedure 1 Click on the Continue button 2 Choose the class of events that you want to update 3 Click on the Cont inue button 4 Update the Action Frequency values 5 Click on the Update button 175 Chapter 5 Configuring ESP Table 5 1 Batch Update Options continued Option Description Assign action s to events Search events by class Assign action s to events Search by event keyword Replace events action Search events by action Assigns an action to an entire class of events Perform the following procedure 1 Click on the Continue button 2 Choose one or more classes of events 3 Choose one or more actions 4 Click on the Assign Action button 5 If you selected only one event class select the check box for any events for which you do not want to assign the action 6 Click on the Commit button Assigns an action to events that match a specific keyword Perform the following procedure 1 Enter the keyword in the box 2 Click on the Continue button 3 Select the events to which you want to assign the action 4 Click on the Assign Action button 5 Select one or more actions 6 Click on the Assign Action button 7 Deselect the check box for any events for which you do not want to assign the action 8 Click on the Commit but
242. nager If you set this parameter to Yes you do not need to manually subscribe the event with the Subscription button 119 Chapter 4 Setting Up the ESP Environment Table 4 4 Add New Client Window Parameters continued Parameter Description Connection Specifies the connection path between the SGM server and this client paths This parameter applies only to ESP 3 0 clients ESP 2 0 clients ignore this parameter ESP 3 0 does not require an SGM to know the hostname and IP address information for its clients ESP 3 0 allows an intermediate system to know this information about the SGM and client systems This enables ESP to work through a firewall For example system A is an SGM server and system D is a client but system A does not know the hostname or IP address of system D However system B knows about systems A and C and system C knows about systems B and D ESP 3 0 allows you to add system D as a client to system A by specifying the connection path as follows B gt C This means that events are forwarded from system D to system A following the connection path through system C and system B If only one system is intermediate enter a fully qualified hostname of that system If a direct connection can be established between SGM server and client systems leave this field blank Note A connection path must be specified in the direction from the SGM server towards a client The SGM server and client hostnames shoul
243. nd unix ec 0 9 late collision unix no carrier rexd Out of ptys satd all output paths full System shutdown in 10 seconds satd Satd recovery failure System will probably hang soon mount hfs HFS filesystem writ e error block 0 9 mount hfs HFS filesystem read error block 0 9 s mount hfs file system corrupt ed inetd server failing loopi ng service terminated vacation can t exec vacation no such user uid Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes uuu O0OoO0o00 zi 381 Chapter 11 ESP Error Codes This chapter lists the error codes that the Web based interface displays When an error occurs the interface displays more information about what you should do to recover from the error Generic Errors Code Event Manager Errors Code Oo DOAN Oo OF FPF WO Ne e me Ny E Gc Description Generic error Description Forwarding path is missing Consumer is missing Invalid consumer definition Invalid event Invalid format Invalid DSO Invalid function name Wrong value System error Network error Memory allocation failure Duplicate subscription 383 Chapter 11 ESP Error Codes SGM Error Codes 384 Code 13 14 15 16 17 18 Code 100 101 102 103 104 105 106 107 108 109
244. nd specific information about an event perform the following procedure 1 Clickonthe c1ass name The interface displays information about events from the class that were registered Refer to Figure 6 11 far esp Embedded Support Partner ver 30 ESP peer mil Set Environment Configuration E Reports Ba Logbook Event Report baltic csd sgi com Class Daemon Messages First Last Event Occurrence Occurrence Event No Description va va Count Syslog message 1 Daemon Error 08 13 2003 08 13 2003 1 warning can t get client 06 23 55 06 23 55 address Transport endpoint is not connected 2 Daemon Error 08 13 2003 08 13 2003 warning can t get client 06 35 31 06 35 31 address Transport endpoint is not connected 3 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 03 03 09 03 03 address Transport endpoint is not connected 4 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 09 04 09 09 04 address Transport endpoint is not connected 5 Daemon Error 08 13 2003 08 13 2003 warning can t get client 09 21 14 09 21 14 address Transport endpoint is not connected 6 Daemon Error 08 13 2003 08 13 2003 warning cant get client 09 31 48 09 31 48 address Transport endpoint is not connected 7 Daemon Error 08 13 2003 08 13 2003 warning can t get client 11 22 06 11 22 06 address Transport endpoint is not connected 8 Daemon Error 08 13 2003 08 13 2003 warning can t get client 11 44 38 11 44 38 address Transport
245. ndow lf you change the PMIE setting in the Performance Monitoring window the setting also changes in the System Monitoring window 4 Setthe Enabled check marks for the PMIE rules that you want to enable 5 Clickon the Update button Table 5 4 describes the PMIE rules that are available and the performance issues that they detect Refer to the Performance Co Pilot for IA 64 Linux User s and Administrator s Guide publication number 007 4580 00x or the Performance Co Pilot for IRIX User s and Administrator s Guide publication number 007 3965 00x for more information about PMIE rules Rule Description Performance Issue cpu context switch cpu excess fpe cpu load average High aggregate context switch rate Possible high floating point exception rate High 1 minute load average The average number of context switches per CPU per second exceeded a threshold value Processes generating large numbers of floating point exceptions FPEs were detected Typically this occurs when heavy system time is coupled with low system call rates Exceptions are delivered through the kernel to the process taking some system time but no system calls are serviced for the application The current 1 minute load average exceeded a threshold value The load average measures the number of processes that are running executable or soon to be executed for example processes in short term sleep 211 Chapter
246. nfigure it and then create an ESP action that calls the QPage application ESP 3 0 for the IRIX OS still includes the QPage application The ESP 3 0 graphical user interface for the IRIX OS still includes the Paging menu Typically the ESP DSO invokes the espnot i fy tool in response to some event However you can run the espnotify tool as a stand alone application if necessary The espca11 tool sends event information from a system to the main ESP database at SGI Figure 1 8 shows how this information is processed ESP Architecture Support Personnel 1 espcall sends e mail to SGI with information about the event 2 A mail parser application running at SGI receives the e mail and logs the data in the master ESP database 3 An analysis tool analyzes a set of business rules for the event and determines if a service call should be opened 4 If a call needs to be opened the call is created in the service database and the appropriate support personnel are notified Figure 1 8 Sending Event Information to SGI SGI uses the event information to provide faster and more accurate responses to potential system problems Any customer can send event information to SGI however service calls are automatically opened only for customers whose service contracts include this option The following example message which was generated by espca11 shows the type of information that is returned to SGI for an availability event Subject
247. ng a URL in a Web Browser 44 Using the Embedded_Support_Partner Icon ESP for the IRIX OS Only 49 Using the launchESPartner Command ESP for the IRIX OS Only 55 Configuring Single System Management 59 Configuring Group Management 60 3 Administering ESP 63 Setting Up the Customer Profile 64 Using the Web based Interface 64 Using the Command Line Interface 67 Setting Up the Network Permissions 68 Using the Web based Interface 68 Using the Command Line Interface 70 Setting Up the User Permissions 71 Viewing the Current Users 71 Using the Web based Interface 71 Using the Command Line Interface 72 Adding a User 73 Using the Web based Interface 73 Using the Command Line Interface 76 Updating a Password 77 Using the Web based Interface 77 Contents Using the Command Line Interface 79 Updating Permissions for a User 80 Using the Web based Interface 80 Using the Command Line Interface 83 Deleting a User 85 Using the Web based Interface 85 Using the Command Line Interface 86 Manipulating Database Archives 87 Using the Web based Interface 87 Using the Command Line Interface 89 Setting Up the ESP Environment 91 Setting Up the System Serial Number ESP for the Linux OS Only 92 Setting the System Serial Number Single System Manager Mode 93 Setting the System Serial Number System Group Manager Mode 95 Setting Up the Global Configuration Parameters 97 Using the Web based Interface 97 Using the Command Line Interface 102 Set
248. nges report from single system manager mode 1 Click on the Reports button 2 Click on the Hardware button 3 Click on the Changes button The interface displays the History of Hardware window Refer to Figure 6 29 M esp Embedded Support Partner ver 30 ESP mi mil Set Environment I Configuration E Reports BE Logbook PAA Inventory P changes History of Hardware Changes balkan csd sgi com Last days C Last 30 days C 08 13 2003 to ori 3 2003 Generate Report Figure 6 29 History of Hardware Changes Window Single System Manager Mode Hardware Reports 4 Specify the range of dates for the report 5 Clickonthe Generate Report button Figure 6 30 shows an example hardware changes report ETE Embedded Support Partner ver 30 aA ESP prerana imi Set Environment I Configuration E Reports Me Logbook Inventory P Changes D ESP Notice No changes for this time period ox Figure 6 30 Example Hardware Changes Report Single System Manager Mode 267 Chapter 6 Viewing Reports 268 Table 6 12 describes the contents of the report Table 6 12 Hardware Changes Report Contents Single System Manager Mode Column Heading Description No Part Name Location Serial Number Part Number Revision Install Date T Removal Date T ime ime Index number in the table Name of the part Location of the part Serial number of the part P
249. nment Z Configuration E Reports E BE Logbook AA Load Profile b Add Update Batch Update Delete subscription Add Event balkan csd sgi com Existing profiles EAT ted Existing classes a Demat Event description Event status Enabled Disabled Occurrences prior to registration f Application name Priority Facility Regular expression Available actions Action frequency I Notify sysadmin on console e6400 secs Figure 5 5 Add Event Window Adding Event to Existing Class Configuring Events Perform the following procedure to use this window to add an event to an existing event class 1 Choose the event profile 2 Choose the event class 3 Enter a description of the event in the Event Description field ESP displays this description on other pages of the interface to identify the event Note The description cannot include the following characters 4 Specify a status for the event Click on Enabled to add the event to the database and to start monitoring it Click on Disabled to add the event to the database but not monitor it 5 Specify the number of times that the event must occur before ESP registers it and performs any assigned actions in the Occurrences prior to registration field 6 Setthe following optional parameters to provide more information about the event e Application name e Priority value e Facility value Regular expre
250. nnot swap in K2SEG ient memory on node ient memory on node 2 ient memory on node annot allocate page annot allocate page annot allocate page 3 Poison page panic Page allocation failed H0 PN HB C rom fr page list err or 1 rom fr page list err r 2 page freeing E page freeing error 2 page freeing REL page allocation failed Page already fr te virtual page number nvalid cache operation location error for MFH I Logical swap fail Bad permissions Mload missing kernname XLV no failover 1 XLV unable to open XLV no failover 2 Table Overflow S through not init d 1 Vnode on free list 1 egative vnode count 1 Fork failed Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 23 23 24 25 25 25 25 25 25 25 25 25 25 26 26 26 26 26 26 C lO C0 C0 CO CO CO PO PO PO P2 PO PO PO PO F2 000000 0000 100 0 O C9 C0 C0 C0 CO WW Ww 143 144 145 146 147 148 149 150 153 152 153 154 155 156 157 158 1 5 9 160 161 162 163 164 165
251. ntries T balkan csd sgi com 08 13 2003 to 08 13 2003 Log Date Subject No User Va 10 administrator 08 13 2003 14 21 36 ran memory tests 2 administrator 08 13 2003 14 25 41 routine online testing Generate Report Figure 7 2 Specified Logbook Entries Single System Manager Mode Viewing Logbook Entries 5 Perform one the following actions to view a log entry e Set the check mark next to entry number and click on the Generate Report button Click on the subject link for the entry The interface displays the logbook entry information Refer to Figure 7 3 Smm esp Embedded Support Partner ver 30 A ESP Administration mi Set Environment Configuration Reports Logbook Entries 1 System name balkan csd sgi com Created by administrator Date created 08 13 2003 14 25 41 Subject routine online testing Log Entry Ran weekly runalldiags basic testing No failures were detected Figure 7 3 Logbook Entry Information Single System Manager Mode Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to view logbook entries in system group manager mode 1 Click on the Logbook button 2 Click on the view Log button The interface displays the view Logbook Entries window Refer to Figure 7 4 295 Chapter 7 Using the ESP Logbook Aesp Um Embedded Support Partner verzo a ESP Administration mi Set Environment Confi
252. nventory Report Single System Manager Mode 273 Software Inventory Reports for System Group Window System Group Manager Mode 275 Example Software Inventory Report System Group Manager Mode 276 History of Software Changes Window Single System Manager Mode 278 Example Software Changes Report Single System Manager Mode 279 Software Changes for System Group Window System Group Manager Mode 280 List of Figures Figure 6 40 Figure 6 41 Figure 6 42 Figure 6 43 Figure 6 44 Figure 6 45 Figure 6 46 Figure 6 47 Figure 6 48 Figure 7 1 Figure 7 2 Figure 7 3 Figure 7 4 Figure 7 5 Figure 7 6 Figure 7 7 Figure 7 8 Figure 7 9 Figure 7 10 Figure 7 11 Figure 7 12 Figure 8 1 Figure 8 2 Figure 8 3 Figure 8 4 Figure 8 5 Figure 8 6 Example Software Changes Report System Group Manager Mode 281 Example System Inventory Report Single System Manager Mode 283 Example System Inventory Report System Group Manager Mode 284 History of System Changes Window Single System Manager Mode 286 Example System Changes Report Single System Manager Mode 287 System Changes for System Group Window System Group Manager Mode 288 Example System Changes Report System Group Manager Mode 289 Site Reports Window 290 Site Information Report 292 View Logbook Entries Window Single System Manager Mode 294 Specified Logbook Entries Single System Manager Mode 294 Logbook Entry Information Single System Manager
253. o Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 81 81 81 81 3746 3745 3744 3743 3742 3741 3740 3739 3738 3737 3736 3435 3734 3733 3732 3339 3338 3337 3336 Dual active negotiation failed jumpers 433 Dual active automatic flash of replacement controller 432 Controller improperly shutdown Data might have been lost 43 1 Controller disconnected from cl uster 430 Controller connected to cluster 429 Low battery charge level Logic al drive may have lost data 1 82 Online controller firmware upgr ade has failed 75 Online controller firmware upgr ade has completed successfully 74 Online controller firmware upgr ade has started 73 Controller parameters checksum verification failed restored d efault 72 Mirror race recovery failed for logical drive 71 Physical disk port has failed o r cannot operate at the configu red channel speed 70 Physical disk has acquired an i nappropriate loop ID Enclosure disk slot operations are disab led while this condition persis ts Physical disk found on only one disk channel 67 Hot spare replaced with a small er capacity drive 62 Failed to communicate storage a rray s world wide name 0x6505 Remote storage array s world wi de name changed 0x6504 Communicat
254. octl unimplemented command ioctl unknown event Link up Link down Firmware init fail Firmware init error Hwgraph could not create net ve rtex Board not in master slot Kernel rebuild needed 1 Board not in master I04 Kernel rebuild needed 2 Adapter number in use Adapter not configured Bad enet address Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes YES Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 331 Chapter 10 Default Event Classes and Types 332 42 42 42 42 42 42 42 42 43 44 45 46 47 47 47 47 47 47 47 47 47 47 47 47 47 CO OO CO co CO OO CO CO OO OO CO COO OO 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 Cannot set interrupt vector Invalid enet address 2 Probe failed to find device RX error FIFO overflow TX link failed TX memory error Jabber detected Remote fault Memory allocation failure for m ulticast Memory request with incorrect s ize Sock
255. ode Perform the following procedure to set the system serial number in single system manager mode 1 Click onthe Set Environment button 2 Click on the Linux System SN button The interface displays the Add Linux System Serial Number window Refer to Figure 4 2 aj esp Embedded Support Partner v A ESP _ mill Set Environment RA Configuration Reports E Ba Logbook Linux System SN Fl Add Linux System Serial Number baltic csd sgi com System serial number Figure 4 2 Add Linux System Serial Number Window Single System Manager Mode 3 Enter the system serial number in the System serial number field Tip To determine the system serial number enter the cat proc sgi sn system serial number command 4 Clickon the Continue button The interface displays a verification window Refer to Figure 4 3 93 Chapter 4 Setting Up the ESP Environment as es Embedded Support Partner ver 30 A ESP Administration mi Set Environment Configuration Reports Logbook Linux System SN E Add Linux System Serial Number baltic csd sgi com System serial number N0900155 Figure 4 3 Add Linux System Serial Number Verification Window Single System Manager Mode Tip Verify that you correctly entered the serial number before you click on the Commit button You cannot change the serial number once it has been submitted 5 Click on the Commit button 94 Setting Up the System Serial Num
256. ode 247 Example Availability Report Single System Manager Mode 248 Availability Reports for System Group Window System Group Manager Mode 250 XV List of Figures xvi Figure 6 20 Figure 6 21 Figure 6 22 Figure 6 23 Figure 6 24 Figure 6 25 Figure 6 26 Figure 6 27 Figure 6 28 Figure 6 29 Figure 6 30 Figure 6 31 Figure 6 32 Figure 6 33 Figure 6 34 Figure 6 35 Figure 6 36 Figure 6 37 Figure 6 38 Figure 6 39 Example Availability Report for a Specific Host System Group Manager Mode 251 Diagnostic Results Window Single System Manager Mode 254 Example Diagnostic Results Report Single System Manager Mode 255 Diagnostic Results Window System Group Manager Mode 256 Example Diagnostic Results Report System Group Manager Mode 257 Hardware Inventory Report Window Single System Manager Mode 260 Example Hardware Inventory Report Single System Manager Mode 261 Hardware Inventory Reports for System Group Window System Group Manager Mode 263 Example Hardware Inventory Report System Group Manager Mode 264 History of Hardware Changes Window Single System Manager Mode 266 Example Hardware Changes Report Single System Manager Mode 267 Hardware Changes Reports for System Group Window System Group Manager Mode 269 Example Hardware Changes Report Single Group Manager Mode 269 Software Inventory Report Window Single System Manager Mode 272 Example Software I
257. og button The interface displays the Create Log window Refer to Figure 7 10 300 Adding a Logbook Entry Sm eSp Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Configuration GOTICE Logbook Add Log Create Log System baltic csd sgi com sj User administrator Subject a Submit Log Figure 7 10 Create Log Window System Group Manager Mode Note ESP automatically sets the User field to the user account that you are using Select the system that the log entry is for Enter a subject for the entry This required field can hold up to 128 characters Enter a log entry This required field can hold up to 4 Kbytes of data Qv gl Ms o9 Click on the Submit Log button The interface displays the information that you entered Refer to Figure 7 11 301 Chapter 7 Using the ESP Logbook Fi A esp To Embedded Support Partner ver 3o aA ESP Administration mil Set Environment I Configuration e Reports Create Log Figure 7 11 Logbook Entry Confirmation Window System Group Manager Mode 7 Click on the Commit button to create the entry Note All log entries are stored on the SGM server The interface displays the information that was added to the logbook Refer to Figure 7 12 302 Adding a Logbook Entry Lg es p Support Partner ver 30 aA ESP Administration m Set Environment Configuration LInDaCEME Logbook Create Log bal
258. ogger Tools The Q option makes a subscription query The uQ option makes an unsubscription by query result request The Rs option makes a remote subscription request The c option specifies the event class The t option specifies the event type The a option specifies the name of the application The s option specifies the source hostname of the event The o option specifies the origin of the event The p option specifies the priority value of the event The f option specifies the facility value of the event The P option specifies the delivery path for a remote subscription event The is option specifies string data The if option specifies file data The id option specifies digital binary data in hexadecimal format esplogger splogger s sequence number f filename m lt message gt p lt priority gt t lt time gt esplogger h esplogger V where The s sequence number option specifies the sequence number in decimal or hexadecimal You must use this option with the t option and the f or m options The f filename option specifies the file that contains data to log in the ESP framework You must include the s option with this option You cannot use this option with the m option The m message gt option specifies a message to log in the ESP framework You must include the s option with this option You cannot use this option with the f option 315
259. om an external application Refer to Chapter 9 Logging Events from Applications and Scripts Configuring Events ar esp Ro Embedded Support Partner ver 30 tion mi Set Environment Z Configuration E l Logbook EJ Add Event aA ESP Admini P Events Figure 5 12 Confirmation Message for Adding an Event Adding Event to New Class 157 Chapter 5 Configuring ESP Adding an Event to a New Event Class in a New Event Profile Figure 5 13 shows the Add Event window when you choose the Add new event to a new class in a new profile option refer again to Figure 5 3 F1 esp m d Embedded Support Partner v5 m ESP Administration mil Set Environment Z Configuration E Reports E Logbook P Events b Add EJ Add Event Figure 5 13 Add Event Window Adding an Event to a New Class in a New Profile 158 Configuring Events Perform the following procedure to use this window to add an event to a new event class 1 2 3 Enter the name of the new event profile in the New profile name field Enter the name of the new event class in the New custom class field Enter a description of the event in the Event description field ESP displays this description on other pages of the interface to identify the event Note The description cannot include the following characters Specify a status for the event Click on Enabled to add the event to the database
260. on is not unique the command displays all matching event types The following example shows output from this command karma espconfig show evtype tid 4194470 begin eventTyp class 7001 type 4194470 0x4000a6 classDescription Irix typeDescription unix CONFIG ISSUE throttleValue Ded actionFrequency 0 eventEnabled YES end eventType 145 146 Chapter 5 Configuring ESP Fi Adding Events You can add your own events to ESP on your system to have it monitor and register events that are specific to your system Using the Web based Interface Perform the following procedure to use the Web based interface to add an event 1 Click on the Configuration button 2 Clickon the Aaa button The interface displays the Add FIBI Sg Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Reports Logbook i b Events Add Event balkan csd sgi com Event window Refer to Figure 5 3 amp Add new event to an existing customer class in an existing profile C Add new event to a new class in an existing profile C Add new event to a new class in a new profile Ada gure 5 3 Add Event Window Single System Manager Configuring Events If the system is an SGM server the interface displays a list of clients Refer to Figure 5 4 Click on the client that you want to use and click on the continue button fp eSp Sag Embedded Support Pa
261. on page read Re Sponse Data Error to node Uncached read Packet Length Err or to node Uncached remote partition read Packet Length Error to node Uncached partition page read Pa cket Length Error to node Uncached access error bad erro r type Lost spool info on cached buser r Region not populated Cached remote partition access error Could not get instruction type assuming store instruction Trying to recover from ibus err or NACK error on local partition a ddr Unrecoverable bus error excepti on Mem info Hi Lo entry addresse S Mem info premium standard dir e ntry elo dir entry IO owned Cached remote partition time ou t error Cached partition page time out error Cached read access Time out er Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 339 Chapter 10 Default Event Classes and Types 340 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 75 79 75 75 75 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975
262. ook AA P Actions Mi Update P Enawte 7 osae i View Current Actions Execute Description Action Timeout No va Action String AS wa Enabled 1 email me lusr bin espnotify E nobody 600 M me sgi com n 7 m H 96D z 2 my action 1 opt contrib bin imy action1 nobody 600 3 Noti fy Jusr binfespnotify A 96D nobody 10 sysadmin on console 4 send me lusr binespnotify E nobody 300 mail me sgi com n 7 m 96H D z Figure 5 46 View Current Actions Window 4 Des elect the Enabled check mark 5 Click on the Commit button Tip To Set the i re enable the action perform the same procedure with the following difference Enabled check mark Using the Command Line Interface Actions cannot be disabled from the command line interface 207 Chapter 5 Configuring ESP Configuring Performance Monitoring 208 ESP monitors the performance of a system by evaluating a set of performance rules at specified time intervals Performance monitoring is disabled by default Using the Web based Interface Perform the following procedure to use the Web based interface to configure performance monitoring for the local system and or any ESP 3 0 SGM clients Notes e SGM clients must be directly connected to the SGM server to use this procedure the clients cannot connect through any intermediate systems To configure performance monitoring on an ESP 3 0 SGM client that is connected through an
263. or Date created 08 13 2003 14 12 58 Subject ran memory tests Log Entry Ran nmem and ndir Ran olmem and olcmt All tests passed Figure 7 6 Logbook Entry Information System Group Manager Mode Using the Command Line Interface Use the following syntax of the espreport command to view logbook entries usr sbin espreport logbook sysid system id host host name from mm dd yyyy to mm dd yyyy Use the sysid and nost options to select a system Use the from and to options to specify a range of dates If you do not use these options the report includes all available data 297 Chapter 7 Using the ESP Logbook Adding a Logbook Entry You should add logbook entries any time that you modify a system Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to add a logbook entry in single system manager mode 1 Click on the Logbook button 2 Click on the Add Log button The interface displays the create Log window Refer to Figure 7 7 fares p Support Partner ver 3 0 aA ESP Administration mi Set Environment Configuration GOTICE Logbook Add Log Create Log balkan csd sgi com User administrator Subject a Submit Log Figure 7 7 Create Log Window Single System Manager Mode Note ESP automatically sets the User field to the user account that you are using 298 Adding a Logbook Entry
264. or ESP 3 0 Client System Group Manager Mode 117 Add New Client Window for ESP 2 0 Client System Group Manager Mode 118 Update System Client Window System Group Manager Mode 122 Update System Information Window SGM Server Selected 123 Update Client Information Window ESP 3 0 SGM Client Selected 125 Update Client Information Window ESP 2 0 SGM Client Selected 129 Unsubscribe Delete Client Window 132 Add Password for a New Server Window 133 List of Figures Figure 4 22 Figure 5 1 Figure 5 2 Figure 5 3 Figure 5 4 Figure 5 5 Figure 5 6 Figure 5 7 Figure 5 8 Figure 5 9 Figure 5 10 Figure 5 11 Figure 5 12 Figure 5 13 Figure 5 14 Figure 5 15 Figure 5 16 Figure 5 17 Figure 5 18 Figure 5 19 Figure 5 20 Figure 5 21 Figure 5 22 Figure 5 23 Figure 5 24 Update Password for an Existing Server Window 134 Event Profile Window System Group Manager 141 Event Profile Window 141 Add Event Window Single System Manager 146 Add Event Window System Group Manager 147 Add Event Window Adding Event to Existing Class 148 Add Event Window with Sample Parameters Adding Event to Existing Class 150 Verification Message for Adding an Event Adding Event to Existing Class 151 Confirmation Message for Adding an Event Adding Event to Existing Class 152 Add Event Window Adding Event to New Class 153 Add Event Window with Example Parameters Adding Event to New Class 155 Verification Messa
265. or systems with less than max cpu count processors For single processor systems refer to the cpu util rule For multiprocessor systems with more than max cpu count processors refer to the cpu many util rule The number of system calls per second for at least one CPU exceeded a threshold value This rule applies only to multiprocessor systems For single processor systems refer to the cpu syscall rule At least one CPU was busy and the ratio of system time to busy time exceeded a threshold value This rule applies only to multiprocessor systems For single processor systems refer to the cpu system rule The number of packets that are being sent across an interface and causing collisions exceeded a threshold value Ethernet interfaces expect a certain number of packet collisions but a high ratio of collisions to packet sends indicates a saturated network For at least one network interface the error rate exceeded a threshold value 213 Chapter 5 Configuring ESP Table 5 4 PMIE Rules continued Rule Description Performance Issue per netif packets High network interface packet transfers shping response Shell ping PMDA slow application or service response shping status Shell ping PMDA application or service probe failure For atleast one network interface the average rate of packet transfers in and or out exceeded a threshold value This rule is disabled by default the per netif uti
266. orts Logbook AA Add An Action Action descriprion Send notification via e mail to abc123 sgi com Action string fusribin espnotify E abc123 sgi com m 96D s An event was just registered Action should be nobody executed as Action timeout 600 seconds Commit Figure 8 5 Example Verification Message for Sending an E mail Message Action 8 Click on the Commit button Figure 8 6 shows the confirmation message for this example aj esp Tg Embedded Support Partner ver 30 a ESP Administration Set Environment Reports Logbook AA P Actions badd Update Enable Disable Add Action Action description Send notification via e mail to abc 123 sgi com fusr binfespnotify E abc123 sgi com m D s An event was just registered Execute action zd nobody Action timeout 600 seconds Action string Update Figure 8 6 Example Confirmation Message for Sending an E mail Message Action 311 Chapter 9 Logging Events from Applications and Scripts The ESP framework provides two ways for you to send events from your local applications and scripts to ESP e By using the Event Manager Application Programming Interface API e By using the emgrlogger and esplogger tools Note You can also use the openlog syslog and closelog SYSLOG functions to send event information through SYSLOG Refer to the syslog 3c man page for more information Event Classification and Se
267. ory reports and system reports View Logs Enables the user to view logbook entries Create Log Enables the user to create logbook entries 8 Click on the Add User button 75 Chapter 3 Administering ESP 76 Using the Command Line Interface Use the following syntax of the espcon ig command to add a new user usr sbin espconfig add user name username p password User names have the following restrictions e User names are case sensitive for example User is different than USer e User names cannot be more than 126 characters e User names cannot include the following characters amp lt gt Passwords have the following restrictions e Passwords are case sensitive for example Password is different than PAssword e Passwords cannot be more than 126 characters e Passwords cannot include the following characters amp lt gt SPACE Tab Setting Up the User Permissions Updating a Password Any user with the ESP Administration and Set Environment permission can update user passwords You must know a user s current password to update their password If a user forgets their password delete their current user account and create a new account with the same user name Using the Web based Interface Perform the following procedure to use the Web based interface to update a user password 1 Clickonthe ESP Administration button 2 Clickonthe User Permissions
268. ould unsubscribe the event rather than disable it on the group manager system This reduces the overhead caused by unnecessary event delivery Configuring Group Management Perform the following procedure to configure group management 1 Select the group of systems that you want to monitor These systems are called the group members or SGM clients Each system in a group can be monitored by more then one group manager Each group manager has an independent set of events that it monitors An ESP 3 0 SGM server can have ESP 3 0 and or ESP 2 0 clients ESP 3 0 clients can run the IRIX or Linux OS ESP 2 0 clients can run the IRIX OS Select the system that you want to be the group manager This system is called the group manager or SGM server The group manager system can also be a group member for another group manager In that case the other group manager treats the system as a single system Configure the group manager system in SGM mode Refer to Setting Up the System Parameters Single System Manager Mode Only on page 114 Configure ESP on each client system You can configure each client as a single system manager or a system group manager and as a full node or a light node Add the SGM clients on the SGM server Refer to Adding a New SGM Client on page 116 Note For greater security configure an authentication password on the SGM server and clients You must configure the password on an SGM
269. oup management for your systems All ESP components are installed on your system by default when you load an operating system release or patch that contains ESP ESP begins monitoring your system when the system is booted You can access ESP by using the command line interface or Web based interface Using the Command Line Interface The command line interface includes three commands espconfig espreport and esplognote The espconfig command configures ESP The espreport command generates and displays ESP reports The esplognote command creates logbook entries espconfig has the following command line options system espconfig help Information Commands espconfig help prototype espconfig spec espconfig version Group Configuration espconfig add group name new group name espconfig delete group name group name espconfig list group espconfig listmembers group name group name gt 35 Chapter 2 Accessing ESP Event Configuration espconfig espconfig espconfig espconfig espconfig show vtyp tid type id td type desc sgmclient client alias gt list vtyp cid class id gt cd class desc gt nable disable log nolog sgmclient client alias gt add vtyp td type desc cid class id gt cd class desc throttle lt value gt nable disable log nolog acfreq action frequency value gt aci
270. ow to set up these parameters Note The paging parameters are not included in the ESP 3 0 Web based interface for the Linux OS ESP 3 0 for the Linux OS does not include paging by default because SGI does not distribute the OPage application for the Linux OS Paging capabilities are disabled when ESP 3 0 runs under the Linux OS The ESP 3 0 graphical user interface for the Linux OS does not include the Paging menu If you obtain the QPage application for the Linux OS from another source you should manually install and configure it and then create an ESP action that calls the oPage application Setting Up the Paging Parameters ESP for IRIX OS Only Setting Up the Modem Parameters ESP for IRIX OS Only A modem must be connected to the system that is running ESP so that the software can send pages when events occur You must specify the device to which the modem is connected and specify the modem initialization command ESP has been tested with the U S Robotics Sportster fax modem with X2 Using the Web based Interface Perform the following procedure to use the Web based interface to set up the modem parameters 1 Clickon the set Environment button 2 Clickon the Paging button By default the interface displays the Paging Modem Setup window Refer to Figure 4 9 107 Chapter 4 Setting Up the ESP Environment 108 e Embedded Support Partner ver 30 ps ESP Administration mil Set Environment 7 RA
271. p Support Partner verzo aA ESP Administration Configuration Reports Logbook I Update System Client Unsubscribe Delete Clet 0 Fl Update System Information baltic csd sgi com Warning All changes take effect immediately Alias name batic System mode SGM Ful node System group E Unknown z Update Figure 4 17 Update System Information Window SGM Server Selected 1 Set the parameters Table 4 5 describes the parameters that are available 2 Click the Update button 123 Chapter 4 Setting Up the ESP Environment 124 Table 4 5 Update System Information Window Parameters SGM Server Parameter Description Alias Specifies an alias that ESP uses to identify the SGM server System mode System group This parameter is optional If you do not set this parameter ESP uses the hostname of the client without the domain name This parameter can contain any non blank space character except for single or double quotes Specifies how the system is configured There are two choices SGM default and Full node The SGM option configures the system to be a system group manager system The Full node option configures the system as a single system manager The system does not have any clients Specifies the group to which the system belongs You can use groups to quickly access information about all systems in a group by generating a site report Example group names include
272. placement utilities CpuMemSets 0 8 The development option for 5 devel sgi221c1 06 18 2003 CpuMemsSets 6 Distutils 1 0 2 2 02 26 2003 Python distribution utilities A debugger which detects memory allocation violations Development library and header files for FreeVVnn 9 FreeWnn libs 1 11 19 02 26 2003 A runtime library for FreeWnn 10 GConf 1 0 4 3 02 26 2003 The Gnome Config System 1 of 110 3 Canna libs 06 13 2003 The runtime library for Canna 4 CpuMemSets 7 ElectricFence 2 2 2 8 02 26 2003 8 FreeWnn devel 1 11 19 02 26 2003 Figure 6 36 Example Software Inventory Report System Group Manager Mode 276 Software Reports Table 6 15 describes the contents of the report Table 6 15 Software Inventory Report Contents System Group Manager Mode Column Heading Description No Index number within the table Software Name Name of the software application Version Version number of the software application Installation Date Date on which the software application was installed Software Description Brief description of the software Using the Command Line Interface Use the following command to view a software inventory report configmon s 277 Chapter 6 Viewing Reports 278 Software Changes Reports Software changes reports show all software that has been added to or removed from a system within a specific time period Using the Web based Interface Single System Manager Mode
273. port Single System Manager Mode Table 6 18 describes the contents of the report Table 6 18 System Changes Report Contents Single System Manager Mode Column Name Description SysId System identification number System type Processor that the system uses System serial number Serial number of the system Hostname Hostname of the system IP address IP address of the system Date Time Date and time of the change 287 Chapter 6 Viewing Reports 288 Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a system inventory report from system group manager mode 1 Click on the Reports button 2 Clickon the System button 3 Click on the Changes button The interface displays the System Changes For System Group window Refer to Figure 6 45 ELE Embedded Support Partner ver 30 A ESP Administration mil Set Environment Configuration Logbook Ez Inventory P Changes History of System Changes Last 30 days C Last 7 days C 08 13 2003 to 08 13 2003 Sys System Serial Current Type Number Eu Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi com N A 134 16 241 91 Subscribed Figure 6 45 System Changes for System Group Window System Group Manager Mode System Name System Reports 4 Specify the range of dates for the report 5 Specify the systems to include in the report 6 Click on the Genera
274. pported SCSI chip 0x10 Controller out of memory 0x ti O on Fh e p O 0D MOS A O 0O 0H U EOG 0 UH d 5 e oo ov Error on drive open 0x10 Channel revived 0x10 Fatal error on root filesys xfs_buf_item_log_check attempting to delete a log item not in the AIL I O Error Detected Log I O Error Detected Corruption of in memory data de tected reservation ran out Need to up reservation bad inode forkoff detected corrupt incore inode Bad directory inode Bad regular inode Bad inode magic number XFS specific messages unhandled vetype unhandled attrtype old version disk label remote i o not supported io request cannot be routed rem otely ce O S o pe He Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 84 84 84 84 84 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 BS QR Gm Ga a 3682 3681 3680 3679 3678 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 1944 71 70 69 68 67 66 65 64 63 62 61 60 59
275. pter describes the ESP logbook how to view it and how to add entries to it About the ESP Logbook Use the ESP logbook to record changes that you make to a system Create a logbook entry each time that you perform a service related activity on a system Then if necessary any ESP user with the view logbook permission can view the entries to review the activities at a later time Viewing Logbook Entries You can view any logbook entries to review previous system activities Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to view logbook entries in single system manager mode 1 Click on the Logbook button 2 Clickonthe view Log button The interface displays the view Logbook Entries window Refer to Figure 7 1 293 Chapter 7 Using the ESP Logbook 294 3 Embedded Support Partner verzo A ESP Administration mi Set Environment Configuration LIE Logbook View Logbook Entries balkan csd sgi com C Last 30 days C Last 7 days o 08 13 2003 to 08 13 2003 View Log Entries Figure 7 1 View Logbook Entries Window Single System Manager Mode 3 Specify the range of dates to view 4 Clickonthe view Log Entries button The interface displays the specified logbook entries Refer to Figure 7 2 mM esp ag Embedded Support Partner ver 30 a ESP Administration mi Set Environment Configuration LIE Logbook Logbook E
276. ption to assign an action to an event by specifying an action description a string enclosed in quotes that describes the action If you do not specify an action no action is assigned to the event by default Use the pri ac appname and regexp options to provide more information about the event priority facility application name and regular expression Use the prfid or prfn option to add the event to an event profile Use the sgmclient or sysid to add the event to an SGM client 163 Chapter 5 Configuring ESP 164 Use the following syntax to update add an event class usr sbin espconfig add evclass cid class id cd class description sgmclient client alias sysid client system id Use the cid option to specify the event class by class ID Use the cd option to specify a new class description a string enclosed in quotes Use the sgmclient or sysid option to select the SGM client on which you want to update the event information Updating Events You can also update the parameters for existing events Using the Web based Interface Perform the following procedure to use the Web based interface to update an event 1 Click on the Configuration button 2 Click on the Events button 3 Click on the Update button Note If you are using ESP on a system group manager the interface displays the Update Event window with a list of SGM clients Refer to Figure 5 17 Sel
277. quence Numbers The ESP framework uses a standardized event classification scheme for the events that it registers This classification scheme was implemented to e Provide a meaningful representation of the events that have occurred so that users can easily interpret them e Provide an easy way to locate the source of an error by providing a general category and more specific information In this scheme events are categorized by class and type An event class describes a general area that ESP monitors for example SCSI An event type provides greater detail about individual events for example a SCSI controller initialization failure ESP automatically generates event class and type numbers when you create custom events and classes You can use these numbers with your local applications and scripts to send event information to the ESP framework through the Event Manager API and splogger and emgrlogger tools The ESP framework also uses unique sequence numbers for system messages These sequence numbers provide a mechanism that enables ESP to isolate problems at the source code level 313 Chapter 9 Logging Events from Applications and Scripts Using the Event Manager API The Event Manager API contains a set of functions that you can call from your local C or C programs to send event information to the Event Manager daemon eventmond The Event Manager forwards events to ESP on a subscription basis Refer to the Event M
278. r UNIX The name of the application that generated the event for example SYSLOG The event data Allevents that ESP receives pass to the Event Manager daemon from one of the following paths Syslog DSO esplogger Of emgrlogger logger Event Manager API 23 Chapter 1 Introduction 24 syslog DSO The syslog DSO runs as a separate task of the Event Manager daemon and performs the following functions e It reads all SYSLOG messages from the tmp eventmond events sock file Note The ESP installation script creates a configuration entry in the etc syslogd conf file that causes the syslogd daemon to write all messages to tmp eventmond events sock file e It converts the messages to Event Manager event format e It passes the events to the Event Manager The Event Manager sends any subscribed SYSLOG events to the ESP DSO consumer so ESP can process the events The ESP startup script starts the syslog DSO by loading it as a task of the Event Manager The syslog DSO continues to run as long as the Event Manager runs esplogger and emgrlogger The esplogger and emgrlogger applications provide a simple command line interface to submit events to the Event Manager emgr logger works with the new Event Manager and replaces esplogger which previous versions of eventmond and ESP used esplogger remains available to provide backward compatibility Note emgrlogger can produce any type of Event Manager event including subs
279. r in processor Yes Yes memory detected corrected 0x27 03 3289 Controller unexpected RPA inter Yes Yes rupt detected 0x2702 3288 PCI controller parity error 0x Yes Yes 2701 3287 Controller RPA memory parity er Yes Yes ror detected 0x2700 3286 Persistent controller memory pa Yes Yes rity error 0x2604 3285 Automatic controller firmware s Yes Yes ynchronization failed 0x2602 3284 Controller inserted or removed Yes Yes 0x2500 3283 Volume definition incompatible Yes Yes with ALT mode ALT disabled 0x2 255 3282 Redundancy parity and data mi Yes Yes smatch was detected 0x2254 3281 Drive marked offline during int Yes Yes rrupted writ 0x2252 3280 Drive failed reconstruction f Yes Yes ailure 0x2251 3279 Volume failure 0x2250 Yes Yes 3278 Drive failed initialization rec Yes Yes onstruction failure 0x224E 3277 Drive failed no response at sta Yes Yes rt of day 0x224D 3276 Drive failed initialization fai Yes Yes lure 0x224B 3275 Drive has wrong block size 0x2 Yes Yes 24A 3274 Drive capacity less than minimu Yes Yes m 0x2249 3273 Drive failed write failure 0 Yes Yes x2248 3272 Data lost on volume during unre Yes Yes covered interrupted write 0x22 359 Chapter 10 Default Event Classes and Types 360 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 81 3271 3270 3269 3268 3267
280. r passes subscribed events to ESP for processing Note Performance monitoring is available through the pmie application which is included in the Performance Co Pilot Execution Only Environment pcp eoe subsystem Refer to Performance Monitoring Tools on page 30 for more information Configuration Monitoring The base package includes a configuration monitoring application configmon configmon is a standalone application that monitors the system configuration by performing the following functions when configuration events occur e It determines the current software and hardware configuration of a system gathering as much detail as possible for example serial numbers board revision levels installed software products installed patches installation dates etc e It verifies that the configuration data in the SSDB is up to date by comparing the current system configuration data with the configuration data in the SSDB e It updates the SSDB so that it is current with information about the hardware or software that has changed e It provides data for various system configuration reports that the system administrator or field support personnel can use The con igmon application runs at system start up to gather updated configuration information configmon uses a producer consumer model Some functionality is provided by the producer and some is provided by the consumer which may or may not be on the same system as the producer i
281. r to Enabled so SGI can provide proactive support for your system providing this information helps the call center provide quick and accurate responses to problems on your system Specifies the format for e mail that ESP sends ESP can send e mail in plain text format or compressed and encrypted uuencoded format If e mail is sent in compressed and encrypted format recipients should use the amreceiver program to decode the e mail refer to the amreceiver man page for more information Recommendation Set this parameter to Compressed amp Encrypted 100 Setting Up the Global Configuration Parameters Table 4 1 Global Configuration Parameters continued Parameter Description Send e mail as Specifies the name that appears in the From portion of the e mail header This option affects e mail messages sent by espnotify availmon and espcall when registration with SGI is enabled E mail text format Specify e mail addresses that should receive e mail from E mail specified format ESP ESP sends these addresses the same messages that it sends to esp sgi com Ifthe Registration with SGI parameter is disabled ESP sends e mail to these addresses only it does not send e mail to esp sgi com TheE mail text format parameter specifies e mail addresses that should receive the e mail in plain text format TheE mail specified format parameter specifies e mail addresses that should receive e mail in t
282. racter except for single or double quotes Specifies the group to which the client belongs You can use groups to quickly access information about all systems in a group by generating a site report Example group names include Server Desktop Web Server and File Server To create a new group enter the name in the System group field Once you create one or more group names ESP displays a menu of the existing groups to select an existing group choose it from the menu Note When you enter group names the entry in the field takes precedence over the selection in the menu The proper way to create a new group is to set the menu to New Group and enter the group name in the System Group field The following three rules apply for creating group names 1 The case of characters does not matter ESP puts systems hat you enter in the groups named Web server and Web Server in the same group 2 Spacing between characters does matter ESP puts systems that you enter in the groups named Web server and Web server in different groups 3 Single and double quotes are not allowed This parameter is optional Specifies a password that the server and client must exchange before transmitting data to provide stronger security via authentication This parameter is required You must configure the password on the client side first Use the Leave it as is option to retain an existing password Use the Aad option to add a new password
283. ral variables in the message parameter Table 5 3 describes the variables Table 5 3 espnotify Parameters Variable Description C Event class ST Event type SD Event data SH Host where the event originated SS Time when the event occurred in seconds since 00 00 00 UTC on January 1 1970 SE Host that forwarded the event I System ID t Current time string s Current time in seconds since 00 00 00 UTC on January 1 1970 m Current minute of the hour SM Current month of the year sh Current hour of the day Sy Current year 3d Current day of the month 3 Enter the user account that will execute the command The default is the nobody account 4 Enter the amount of time that ESP should wait for the action to execute timeout value If the action does complete within this period of time ESP kills the action Figure 5 39 shows the Add an Action window with example parameters 197 Chapter 5 Configuring ESP esp Embedded Supponi Partner verzo I ESP Administration mil Set Environment Reports E WE Logbook Ia 2 Add An Action Action description fsendmemal Action string o usybin espnotity E me sgi com n Execute action as fooy S S Action timeout feo second s Figure 5 39 Example Parameters Add an Action Window Using Other Action Option 5 Click on the ada button The interface displays a verification page Refer to Figure 5 40 esp r Embedded ban Partner ver
284. restrictions e Passwords cannot be more than 126 characters e Tab 78 Passwords are case sensitive for example Password is different than PAssword Passwords cannot include the following characters amp lt gt SPACE Setting Up the User Permissions 8 Re enter the new password in the Verify Password field You must enter the password twice to ensure that it is entered correctly 9 Click on the Commit button Note If you change the password for the account you are currently using the interface displays an Authorization Failed message and prompts you for the new password Using the Command Line Interface Use the following syntax of the espconfig command to update a password usr sbin espconfig update user name username p new password Passwords have the following restrictions e Passwords are case sensitive for example Password is different than PAssword e Passwords cannot be more than 126 characters e Passwords cannot include the following characters amp lt gt 7o SPACE Tab 79 Chapter 3 Administering ESP 80 Updating Permissions for a User Any user with ESP Administration and Set Environment permission can update permissions for other users Updating permissions enables you to add or remove specific permissions for a user Note If a user attempts to access a feature for which he she does not have permission the interface displays
285. rface displays the System window Figure 6 41 shows an example system inventory report in single system manager mode Figure 6 42 shows an example system inventory report in system group manager mode System Reports ar esp Embedded Support Partner ver 30 A ESP Administration mE Set Environment v Configuration E Reports l Logboo f System Information Figure 6 41 Example System Inventory Report Single System Manager Mode 283 Chapter 6 Viewing Reports F 3 es p Ad Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Iv Configuration E Reports __ Logbook 8 System Information Figure 6 42 Example System Inventory Report System Group Manager Mode 284 System Reports Using the Command Line Interface Use the following syntax of the espreport command to generate a system information report usr sbin espreport sysinfo sysid system id host host name gt a11 If you specify the a11 option the command displays the system name serial number type IP address and system ID If you do not specify the a11 option this command displays only the system serial number Use the following syntax of the espreport command to view a summary report that includes system information events hardware and software changes logbook information availability overview and local system disk usage usr sbin espreport summary sysid system id host host name g
286. rmat Specifies event information to include in the notification Console Notification Notification message Specifies a message to add to the end of the notification Tip The message cannot include quotation marks single or double Notification format Specifies event information to include in the notification GUI pop up notification Display setting Specifies the X Window System display to use Notification message Specifies a message to add to the end of the notification Tip The message cannot include quotation marks single or double Notification format Specifies event information to include in the notification 8 Click on the Continue button The interface displays a verification message Refer to Figure 5 36 194 Configuring Actions fap esp E Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Reports Logbook AA P Actions Add An Action Action descriprion email me Action string lusribin espnotify E me sgi com n 7 m 96H 95D 96z Action should be executed as nobody Action timeout 600 seconds Commit Figure 5 36 Verification Message for Adding an Action Using Notification Action Option 9 Click on the Commit button The interface displays a confirmation message Refer to Figure 5 37 If you need to update the action parameters click on the Update button ap eSp E Embedded Support Partner ver 30 A ESP Administration mi Set Environment Reports Logbook
287. rmine the system id value Use the from and to options to select the range of dates for the report If you do not specify a range of dates the report displays all actions that have been taken Availability Reports Availability Reports Availability reports provide statistics about system availability from a specified time period Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate availability reports in single system manager mode 1 Clickon the Reports button 2 Clickonthe Availability button The interface displays the Availability Reports window Refer to Figure 6 17 at esp Embedded Support Partner ver 30 aA ESP Administration m l Set Environment Configuration Logbook Availability Availability Reports Last 30 days C Last 7 days DC ori 3 2003 to oer 3 2003 Figure 6 17 Availability Reports Window Single System Mode 3 Specify the range of dates for the report 4 Clickonthe Generate Report button Figure 6 18 shows an example availability report 247 Chapter 6 Viewing Reports 248 Zr aj esp UU Embedded Support Partner ver 30 a ESP Administration mil Set Environment Configuration Logbook Availability Availability Report balkan csd sgi com Interrupts Downtime MTBI Availability Unscheduled 33 min 246 hrs 15min 99 89 reset action 33 min 246 hrs 15 min Scheduled 24 min
288. rofile data file and update the events in ESP that are different in the event profile data file usr sbin espconfig merge eventprofile profile name gt allprofiles defaults dontsubscribe sgmclient client alias sysid system Id gt Note If the event is not already in the ESP event list the event is added to the list with the parameters defined for the event Use the following command syntax to remove all events that are in the specified event profile data file from the ESP event list usr sbin espconfig drop eventprofile eventprofile name gt allprofiles sgmclient client alias sysid system Id gt Note If the event being dropped is part of another event profile the event is not dropped 143 Chapter 5 Configuring ESP 144 Use the following command syntax to unload an event profile usr sbin espconfig unload eventprofile eventprofile name gt allprofiles sgmclient client alias sysid system Id gt Use the following command syntax to save the current ESP event list and assigned actions in an event profile data file usr sbin espconfig save eventprofile profile name gt allprofiles defaults Use the following command syntax to refresh the ESP event list and assigned actions from an event profile data file usr sbin espconfig refresh eventprofile profile name gt allprofiles defaults Use the following command syntax to show event information from a
289. rtner ver 30 H ESP Administration EF Set Environment Reports Logbook I Add Event Add new event to an existing custom class in an existing profile C Add new event to a new class in an existing profile C Add new event to a new class in a new profile System Name IP Type System Serial Number IP Address baltic csd sgi com N A 134 16 241 92 C balkan csd sgi com N A 134 16 241 91 Continue Figure 5 4 Add Event Window System Group Manager You should be aware of the following restrictions when you add events from an SGM server e When you select an SGM server from the System Name list ESP adds events only to the SGM server It does not add events to any of the SGM clients for that server You must select an SGM client to add events to it You cannot use this window to add events to ESP 2 0 clients To add events to an ESP 2 0 client from an SGM server click on Configuration gt Subscription Events gt 147 Chapter 5 Configuring ESP 148 Adding an Event to an Existing Event Class in an Existing Profile Figure 5 5 shows the Add Event window when you choose the Add new event to an existing customer class in an existing profile option Use this option to add an event to an event class that you already created You can only add events to the event classes that you create you cannot add events to the default event classes EL Embedded Sopront Partner ver 30 ESP prre mil Set Enviro
290. s 252 Table 6 7 describes the contents of the report Table 6 7 Single System Availability Report Contents System Group Manager Mode Row Description Unscheduled Information about any unscheduled downtime events count downtime due to the event in minutes mean time between interrupts in minutes and availability percentage Scheduled Information about scheduled downtime events count Scheduled and Unscheduled Average uptime Least uptime Most uptime Average downtime Least downtime Most downtime Logging started at Last boot at System has been up for All registered availability events downtime caused by the service action in minutes mean time between interrupts in minutes and availability percentage Tip Click on the link to view a report of all scheduled availability events that ESP registered during the time period Information about the total downtime for scheduled and unscheduled downtime count downtime in minutes caused by the action mean time between interrupts in minutes and availability percentage Tip Click on the link to view a report of all scheduled and unscheduled availability events that ESP registered during the time period Average uptime between availability events Shortest uptime between availability events Longest uptime between availability events Average downtime Shortest downtime Longest downtime Date and time that ESP began monitoring availability
291. s Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 82 82 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4002 4005 4005 4005 4005 4005 4005 4005 4005 4005 85 80 80 80 80 80 80 80 3704 3703 20974 20974 209741 209741 209741 209741 209741 209741 209741 209741 209741 209741 20974 20974 08 09 e co 10 01 w N ES L9 20 24 340 2098176 2098177 2098178 2098179 2098180 2098181 2098182 2098183 2098184 3764 3143 3142 3141 3140 3139 3138 3137 illegal mesging during recovery CMS Cannot allocate nCr handle cells Configmon init Sysinfo changed Hardware installed Harwdare de installed Software installed Software de installed System change Configuration error ESP registered with SGI ESP deregistered with SGI ESP package updated ESP package uninstalled ESP system information change ESP profile s update Customer information is updated Diagnostic start Diagnostic interrupted Diagnostic end Stress start Stress end SVP start SVP end SVP interrupted Stress interrupted snmp trap events Internal controller has encount ered Strong ARM processor speci fic error 928 Internal controller has encount ered i960 processor specific er
292. s View logs ESPpermission logbook_view Create log ESPpermission logbook 84 If you do not specify a user name this command adds the permission to all users Use the following command syntax to delete permissions from a user usr sbin espconfig delete userperm name user name gt perm permission name gt If you do not specify a user name this command deletes the specified permission from all users If you do not specify a permission name this command deletes all permissions from the specified user If you do not specify a permission name or user name this command deletes all permissions from all users Setting Up the User Permissions Deleting a User Any user with the ESP Administration and Set Environment permission can delete other ESP users To ensure that security is not compromised always delete users that no longer need access to ESP on a specific system Caution Do not delete the administrator user account All systems should have the administrator account Using the Web based Interface Perform the following procedure to use the Web based interface to delete a user 1 Clickonthe ESP Administration button 2 Clickonthe User Permissions button 3 Click on the Delete User button The interface displays the Delete User window Refer to Figure 3 10 fal eSp Sag Embedded Support Partner ver 30 f ESP Administration mill Set Environment Configuration Reports Logbook AA Vi
293. s Save Action Profile Execute Description Action Timeout No va Action String As va Enabled 1 Notify lusrisbiniespnotify A n 7 D l nobody 30 Enabled sysadmin on console 2 test mail fusrisbin espnotify E nobody 600 Enabled nadezhda sgi com s ESP test notification n 7 m 96H 96D 96z c C 96e T F l Just a test Disregard please Figure 5 45 Confirmation Message for Updating an Action 204 Configuring Actions Using the Command Line Interface Use the following espconfig command syntax to update an action usr sbin espconfig update evaction acid action id acd new action description gt acd action description act action string gt user lt name gt retry lt count gt tout timeout value gt throttle throttle value gt enabl disable Use the acid option to select an action by action ID If you use the acad option with the acid option this command updates the action description Use the aca option to select an action by description a string enclosed in quotes Note If you do not specify any of the following options ESP does not update the related action parameters Use the act option to update the command a string enclosed in quotes that the action performs Use the user option to update the UNIX user that executes the action Use the ret ry option to update the number of times that ESP should perform the action before stopping Use the
294. s Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes 329 Chapter 10 Default Event Classes and Types 330 31 31 31 3T 31 31 Sal 31 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 33 34 34 34 34 34 34 34 34 34 34 34 35 35 36 36 36 34 36 37 186 187 188 189 190 191 192 193 194 195 196 T97 198 199 200 201 202 203 204 205 206 207 208 209 N e NNNNNNDN NY co 10 OF WN EF KV N Q o 22 222 223 224 225 226 227 228 229 230 NOMEM too many devices hwgraph dev addr error No memory 1 No memory 2 Memory alignment error No memory 3 ISR installation error Hwgraph no device vhandle Interrupt adapter check status Statistics overflow Need more rxds No board found 10MB physical memory only No enet carrier 1 Full duplex unsupported Auto negation failed No enet carrier 2 Netlink restored Remote fault Jabber detected hwgraph no vertex Kmemory allocation error Memory fail to st big endian Interrupt setup failed hwgraph no vertex info No enet carrier Assertion routine No DMA space No VME space DMA error About to die 1 Board not detected About to die 2 Remote fault Jabber detected Link OK 1 Link down Memory base addr missing 1 Memory base addr missing 2 Remote fault Jabber detected Link down Link OK 2 Channel overrun Memory allocation fail for fram Yes Yes Yes Y
295. s Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS O O 1 J 1 J 1 J J1000000 00 CO XO iO DD OD oOoooooco0oco aor PPP SP BWNNNNN EF O 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 Parity error in DI Bus 1 Parity error in DI Bus 2 NMI 2 NMI 3 TOD battery 16 TOD battery 17 TOD battery 18 TOD battery 19 TOD battery 20 Bus error 7 Cache error 1 Cache error 2 Cache error 3 Cache error 4 Cache error 5 Bus error 8 Bus error 9 efs root mount failed Not enough filesystem quota str uctures Bad magic number Unexpect user project ID Disk block timer zero inode zero Re init disk quota structure fs too large for kernel typ vnode not char block device 1 Bad vnode found by console driv er vnode not char block device 2 Unexpected PMAP type Memory page not freed Memory page not found Page cache error Swap cache error Privilege memory pool error Watc
296. s is disabled not used Missing Configuration profile Group operation error Duplicate call log setting Incorrect argument Invalid user Duplicate system group name Missing customer information profile Missing or expired SGM license This operation is not allowed for ESP 2 0 client ESP 2 0 client error System time ctime on a client and SGM server is not synchronized System must be unsubscribed before deletion
297. s for the report 4 Specify the systems to include in the report 5 Clickonthe Generate Report button Figure 6 24 shows an example diagnostic results report IE Embedded Support Partner ver 30 ESP prem E Set Environment Configuration E Reports Ba Logbook Diagnostic Results balkan csd sgi com All Events Report Event Report for Diagnostics class Diagnostic Result Time No Diagnostic Name va Va Diagnostic Result 1 olemt Passed 08 13 2003 13 09 13 2 olmem Passed 08 13 2003 13 09 39 3 pandora Passed 08 13 2003 13 13 43 Figure 6 24 Example Diagnostic Results Report System Group Manager Mode 257 Chapter 6 Viewing Reports 258 Table 6 9 describes the contents of the report Table 6 9 Diagnostic Results Report Contents System Group Manager Mode Column Heading Description No Diagnostic Name Diagnostic Result Diagnostic Result Time System Name Index number within the table Name of the diagnostic When one or more tests run as a group under one program for example SVD the total number of tests run is shown in parentheses next to the diagnostic name for example SVP 86 indicates that 86 tests ran under SVP Result of the diagnostic PASS FAIL or COMPLETE PASS indicates that the diagnostic completed successfully FAIL indicates that the diagnostic failed COMPLETE indicates that multiple tests ran and one or more of them failed
298. se the Batch Update command to update these parameters 167 Chapter 5 Configuring ESP 168 7 10 11 12 Update the Event Status parameter e Click on Enabled to add the event to the ESP event list on your system and start monitoring it e Click on Disabled to add the event to the ESP event list on your system but not monitor it Update the Registration with SGI parameter e Click on Enabled to specify that ESP should return information about the event to SGI when the event occurs Click on Disabled to specify that ESP should not return information about the event to SGI when the event occurs The Registration with SGI parameter provides individual control over specific events that ESP returns to SGI To use this parameter you must also enable the global Registration with SGI parameter When the Registration with SGI global configuration parameter is enabled in the Global Configuration window refer to Figure 4 7 on page 98 the Registration with SGI parameter for each event takes precedence for the individual events When the Registration with SGI global configuration parameter is disabled the Registration with SGI parameter for individual events does not affect ESP operation The Registration with SGI parameter is not available for custom events ESP never returns information about custom events to SGI Update the Occurrences prior to registration parameter Select the actions to assign to the ev
299. server This parameter applies only to ESP 3 0 clients Setting Up the System Client Parameters System Group Manager Mode Only Table 4 6 Update Client Information Window Parameters ESP 3 0SGM Client continued Parameter Description Connection path Specifies the connection path between the SGM server and this client This parameter applies only to ESP 3 0 clients ESP 2 0 clients ignore this parameter ESP 3 0 does not require an SGM to know the hostname and IP address information for its clients ESP 3 0 allows an intermediate system to know this information about the SGM and client systems This enables ESP to work through a firewall For example system A is an SGM server and system D is a client but system A does not know the hostname or IP address of system D However system B knows about systems A and C and system C knows about systems B and D ESP 3 0 allows you to add system D as a client to system A by specifying the connection path as follows B gt C This means that events are forwarded from system D to system A following the connection path through system C and system B If only one system is intermediate enter a fully qualified hostname of that system If a direct connection can be established between SGM server and client systems leave this field blank Note A connection path must be specified in the direction from the SGM server towards a client The SGM server and client hostnames should be
300. specify the command a string enclosed in quotes that the action performs Use the user option to specify the UNIX user that executes the action If you do not specify a user ESP uses the default user nobody Use the ret ry option to specify the number of times that ESP should perform the action before stopping If you do not specify a value ESP uses the default value 0 Use the t out option to specify the amount of time in seconds that ESP should wait for the action to execute If the action does not complete before the timeout period expires ESP kills the action command If you do not specify a value ESP uses the default value 0 Use the throttle option to specify the throttling value for the action which specifies the number of times an event must occur before ESP performs the action If you do not specify a value ESP uses the default value 1 Use the enable option to enable the action or use the disable option to disable the action Configuring Actions Updating Actions You can update actions to customize them for your site Using the Web based Interface Perform the following procedure to use the Web based interface to update an action 1 Click on the Configuration button 2 Click on the Act ions button 3 Click on the Update button The interface displays the Update Current Actions window Refer to Figure 5 42 a esp Embedded SU Partner ve 5o aA ESP Peer mil Set Environment Configuration
301. ssion to match 7 Assign an action to the event If Event status is set to Enabled ESP performs this action when the event is registered 8 Specify the number of seconds that ESP should pause between multiple executions of an action in the Action frequency time field A value of 0 disables the option For example if you set this parameter to 5 seconds and ESP registers an event every second ESP executes the assigned action s every 5 seconds Figure 5 6 shows the Add Event window with example parameters 149 Chapter 5 Configuring ESP mM esp Embedded Support Partner verzo a ESP Administration mi Set Environment Z Configuration E Reports 3 Logbook EJ Add Event Demo Ej Demo ej demo event 4 Figure 5 6 Add Event Window with Sample Parameters Adding Event to Existing Class 9 Click on the Ada button The interface displays a verification message Refer to Figure 5 7 150 Configuring Events 2 M mM esp ES Embedded Support Partner verzo m ESP Administration mil Set Environment Reports Logbook AA P Events Load Profile Add Update Batch Update Delete subscription 3 Add Event balkan csd sgi com Profile name Demo Event class Demo1 Event description demo event 4 Event status Enabled Occurrences prior to registration 1 Application name demo1 Priority Not set Facility Not set Regular expr
302. stem Information Figure 2 13 ESP Main Page Single System Manager Mode 57 Chapter 2 Accessing ESP a esp A Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Iv Configuration E eports E Logbook f System Information Figure 2 14 ESP Main Page System Group Manager Mode 58 Configuring Single System Management Configuring Single System Management Perform the following procedure the first time that you use single system manager mode to configure it 1 Log into the system as root and enter espconfig createadmin to create the default user account administrator Enter espconfig enable ipaddr 127 0 0 0 and espconfig enable ipaddr 127 0 0 1to enable access to the ESP from the local system Open one of the following URLs in a Web browser http localhost 5554 e http systemname 5554 Refer to Using the Web based Interface on page 42 Change the default password to prevent unauthorized access to your system Refer to Updating a Password on page 77 e The default user name is administrator e The default password is partner Set up any user accounts and permissions that you want on your system Refer to Setting Up the User Permissions on page 71 Set up the access lists to allow systems to connect to the Configurable Web Server that ESP uses By default the Configurable Web Server is configured to refuse connections from all other IP addresses
303. stem id Use the following command syntax to set group management parameters for a system usr sbin espconfig set system host host name sysid system id alias new alias gt group group name gt gid group id Use the following command syntax to configure a system node in SGM or full mode usr sbin espconfig setnode system sgmnode fullnode Use the following command syntax to get information about the SGM license or update it usr sbin espconfig check system sgmlicense update Importing and Exporting ESP Environments Use the following command syntax to update the SGM license key usr sbin espconfig update sgmkey host host name p comm password pid key ID gt You can use the espconfig command to create and manage named groups Use the following command syntax to create a new group name espconfig add group name new group name Use the following command syntax to delete a group name espconfig delete group name group name Use the following command syntax to list the groups that are available espconfig list group Use the following command syntax to list the members of a group espconfig listmembers group name group name Importing and Exporting ESP Environments You can use the espcon ig command to import and export ESP environments between systems The espcon ig command transfers the following environmental information global confi
304. t from lt mm dd yyyy gt to lt mm dd yyyy gt Use the fromand to options to specify a range of dates If you do not use these options the report includes all available data 285 Chapter 6 Viewing Reports 286 System Changes Reports System change reports show any system changes system name IP address etc that occur within a specific time period Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate a system inventory report from single system manager mode 1 Click on the Reports button 2 Clickon the System button 3 Click on the Changes button The interface displays the History of System Changes window Refer to Figure 6 43 aM esp Sg Embedded Support Partner ver 30 aA ESP Administration E Set Environment Configuration Logbook Ia 21 Inventory Changos fo History of System Changes balkan csd sgi com C Last 7 days Last 30 days C 08 13 2003 to 08 13 2003 Generate Report Figure 6 43 History of System Changes Window Single System Manager Mode System Reports 4 Specify the range of dates for the report 5 Clickonthe Generate Report button Figure 6 44 shows an example system changes report far esp Embedded Support Partner ver 30 ESP pem mil Set Environment I Configuration Logbook OBS Notice No changes for this time period ok Figure 6 44 Example System Changes Re
305. t connected Figure 6 12 All Occurrences of a Specific Event System Group Manager Mode 240 Events Registered Reports Using the Command Line Interface Use the following syntax of the espreport command to view an events registered report sysid system id gt host lt hostname gt from mm dd yyyy to mm dd yyyy usr sbin espreport events tid type id td type desc gt cid class id cd lt class desc gt On group manager systems use the sysid or host options to select a specific system to include in the report If you do not specify a system the report contains events from the local host Note Enter usr sbin esreport sysinfo all to determine the system id value Use the from and to options to select the range of dates for the report If you do not specify a range of dates the report the report contains all events that have been registered Use the t id and ta options to select a specific event type If you do not specify an event type the report includes all events 241 Chapter 6 Viewing Reports Actions Taken Reports Actions taken reports show all actions that ESP performed within a specific time period Using the Web based Interface Single System Manager Mode Perform the following procedure to use the Web based interface to generate an actions taken report in single system manager mode 1 Click on the Reports button 2 Clickon the Act ions button
306. t of the espnot ify command has the following command line options A Specifies that the message should be displayed in the console window lt message gt Specifies the message that the window should display Enclose message in single quotes if the message contains more than one word 305 Chapter 8 Sending Notifications 306 n number Specifies an optional priority message which is determined by the value that you specify for number The number parameter can be a value from 1 to 7 espnot ify attaches a label to the message based on the value of number 1 or2 Critical System Error System Error 4 System Warning or5to7 System Information For example the following command displays the message This is the message to display on the console refer to Figure 8 1 usr bin espnotify A This is the message to display the me Figure 8 1 Displaying a Message in the Console Window Displaying a Message on an X Window System Display Use the following format of the espnot ify command to display a message on a local or remote X Window System display usr bin espnotify c message a D lt display gt g lt geometry gt i lt icon gt n lt number gt t lt title gt This format of the espnot ify command has the following command line options c message Specifies the message that the window should display Enclose message in double quotes
307. t to all hosts and set the allow access list to the hosts that you want to have access to ESP For example set the allow access listto 197 and the restrict access list to if you want only the systems that have IP addresses that begin with 197 to have access to ESP Caution All changes that you make to the restrict access and allow access lists immediately take effect Ensure that you do not set up access lists that prevent your administration system from connecting to ESP By default the restrict access list is set to to restrict all hosts You must enable access by the local host 127 0 0 0 and 127 0 0 1 before you can access the ESP Web server To do this enter the espconfig enable ipaddr 127 0 0 0 and espconfig enable ipaddr 127 0 0 1 commands before you attempt to access ESP on a system for the first time Using the Web based Interface Perform the following procedure to use the Web based interface to set up network permissions 1 Click onthe ESP Administration button 2 Click on the Network Permissions button The interface displays the Network Permissions window Refer to Figure 3 3 68 Setting Up the Network Permissions ap esp Sg Embedded Support Partner ver 30 Fal ESP Administration i Set Environment Configuration Reports Logbook Network Permissions E Network Permissions baltic csd sgi com Server Identification SGI Configurable Web Serv
308. taken Description of the command that the action performed Tip Click on an action to view the parameter settings for the action 243 Chapter 6 Viewing Reports 244 Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate an actions taken report in system group manager mode 1 Click on the Reports button 2 Click on the Act ions button The interface displays the Actions Report For System Group window Refer to Figure 6 15 far esp Ec v Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Configuration Logbook Actions Report For System Group C Last 30 days C Last days c 08 13 2003 to 08 13 2003 IP System Serial Current Type Number IP asteon Status C All subscribed systems Iv baltic csd sgi com NA 134 16 241 92 SGM C balkan csd sgi com N A 134 16 241 91 Subscribed Figure 6 15 Actions Report for System Group Window System Group Manager Mode System Name 3 Specify the range of dates for the report 4 Select the systems to include in the report 5 Clickonthe Generate Report button Actions Taken Reports Figure 6 16 shows an example actions taken report aj esp Embedded Support Partner ver 30 aA ESP prem E Set Environment I Configuration E Reports BE Logbook Action Report n baltic csd sgi com 08 13 2003 to 08 13 2003 Action Taken No Class Event Description Time Va
309. talled on the system Date that the software application was removed from the system Description of the software application 279 Chapter 6 Viewing Reports 280 Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate a software changes report from system group manager mode 1 Click on the Reports button 2 Click on the Software button 3 Click on the Changes button The interface displays the History of Software Changes For System Group window Refer to Figure 6 39 mM esp Embedded Support Partner ver 30 aA ESP Administration mi Set Environment Configuration Logbook Inventory P Changes History of Software Changes Last 30 days C Last days 08 13 2003 to 08 13 2003 Sys System Serial Current System Name Type Number IP Address Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi ccom NA 134 16 241 91 Subscribed Figure 6 39 Software Changes for System Group Window System Group Manager Mode 4 Specify the range of dates for the report 5 Select the system to include in the report 6 Clickon the Generate Report button Figure 6 40 shows an example software changes report Software Reports ar esp Embedded Support Partner v5 aA ESP paneer mil Set Environment I Configuration E Reports BE Logbook Inventory P Changes ESP Notice No changes for this time period ox Fi
310. te Report button Figure 6 46 shows an example system changes report ar esp Eco Embedded Support Partner ver 30 aA ESP Administration mil Set Environment Configuration Logbook AA System Inventory P Changes 0 ESP Notice No changes for this time period x Figure 6 46 Example System Changes Report System Group Manager Mode Table 6 19 describes the contents of the report Table 6 19 System Changes Report Contents System Group Manager Mode Column Name Description SysId System identification number System type Processor that the system uses System serial number Serial number of the system Hostname Hostname of the system IP address IP address of the system Date Time Date and time of the change Using the Command Line Interface System change reports are not available from the command line interface 289 Chapter 6 Viewing Reports 290 Site Reports System Group Manager Mode Only Site reports show information for various combinations of systems at a site ESP limits site reports to include only systems that meet specific criteria including e Systems that are in a specific group e Systems that run a specific operating system version e Systems that have a specific processor type Site reports can contain system information all available events or specific events by class for the selected systems Site reports are available only from SGM servers Perform the following procedure to
311. ted warning can t get client address Transport endpoint is not connected warning can t get client address Transport endpoint is not connected warning can t get client address Transport endpoint is not connected warning can t get client address Transport endpoint is not connected Events Registered Reports Using the Web based Interface System Group Manager Mode Perform the following procedure to use the Web based interface to generate an events registered report in system group manager mode 1 Click on the Reports button 2 Clickon the Events button The interface displays the Event Reports For System Group window Refer to Figure 6 8 mMm eSp zov Embedded Support Partner ver 30 A ESP Administration m l Set Environment Configuration Logbook Event Reports For System Group C Last 30 days C Last days c 08 13 2003 to 08 13 2003 IP System Serial Current System Name Type Number IP Address Status C All subscribed systems Iv baltic csd sgi com NA 134 16 241 92 SGM C balkan csd sgi com N A 134 16 241 91 Subscribed Continue Figure 6 8 Event Reports for System Group Window System Group Manager Mode 3 Specify the range of dates for the report 4 Select the systems to include in the report 5 Click on the Continue button The interface displays the list of classes Refer to Figure 6 9 235 Chapter 6 Viewing Reports mM esp mbedded Support Partner v5 aA ESP Ad
312. the Same Time Batch Updating 173 Using the Web based Interface 173 Using the Command Line Interface 177 Deleting Events 178 Using the Web based Interface 178 Using the Command Line Interface 180 Subscribing Events from SGM Clients 182 Using the Web based Interface 182 Using the Command Line Interface 186 Configuring Actions 187 Viewing the Existing Actions 187 Adding Actions 188 Using the Web based Interface 188 vi Contents Using the Command Line Interface 200 Updating Actions 201 Using the Web based Interface 201 Using the Command Line Interface 205 Disabling and Enabling Actions 206 Using the Web based Interface 206 Using the Command Line Interface 207 Configuring Performance Monitoring 208 Using the Web based Interface 208 Using the Command Line Interface 215 Configuring System Monitoring 216 Using the Web based Interface Single System Manager Mode 216 Using the Web based Interface System Group Manager Mode 220 Using the Command Line Interface 222 Viewing Reports 225 About Reports 225 Events Registered Reports 229 Using the Web based Interface Single System Manager Mode 229 Using the Web based Interface System Group Manager Mode 235 Using the Command Line Interface 241 Actions Taken Reports 242 Using the Web based Interface Single System Manager Mode 242 Using the Web based Interface System Group Manager Mode 244 Using the Command Line Interface 246 Availability Reports 247 Using the
313. tic csd sgi com User administrator Date 08 13 2003 14 12 58 Subject ran memory tests Log entry Ran nmem and ndir Ran olmem and olcmt All tests passed Figure 7 12 Completed Logbook Entry System Group Manager Mode Using the Command Line Interface Use the usr sbin esplognote command to add a logbook entry This command prompts you for the information that is required in a logbook entry 303 Chapter 8 Sending Notifications About the espnotify Tool The ESP software suite includes the espnotify tool which you can use to perform the following types of notification e Display a message on the system console Display a message on a local or remote X Window System display e Send an e mail message Note This chapter describes how to use the espnot ify command to create notifications ESP can also automatically generate the espnot ify command line from options that you select from the graphical user interface when you use the Notification Actionoption in the Add Action window The information in this chapter simply provides examples of how you can create command lines as actions If you need to create standard notification actions it is easiest to use the automated method Command Line Options for Displaying a Message on the Console Use the following format of the espnot ify command to display a message on the system console usr bin espnotify A message n lt number gt This forma
314. ting Up the Paging Parameters ESP for IRIX OS Only 105 Setting Up the Modem Parameters ESP for IRIX OS Only 107 Using the Web based Interface 107 Using the Command Line Interface 109 Setting Up the Paging Service Provider Parameters ESP for IRIX OS Only 110 Using the Web based Interface 110 Using the Command Line Interface 112 Setting Up the Paging Parameters ESP for the IRIX OS Only 112 Using the Web based Interface 112 Using the Command Line Interface 113 Setting Up the System Parameters Single System Manager Mode Only 114 Setting Up the System Client Parameters System Group Manager Mode Only 116 Adding a New SGM Client 116 Updating the System ora Client 122 Updating the SGM Server 123 Updating an ESP 3 0 SGM Client 125 Contents Updating an ESP 2 0 SGM Client 129 Unsubscribing SGM Clients 131 Setting Up the Authentication Password 133 Adding a Password for a New Server 133 Updating the Password for an Existing Server 134 Using the Command Line Interface to Configure SGM Settings 135 Importing and Exporting ESP Environments 137 5 Configuring ESP 139 Configuring Events 139 Managing Event Profiles 140 Using the Web based Interface 140 Using the Command Line Interface 143 Viewing Event Classes and Events 145 Adding Events 146 Using the Web based Interface 146 Using the Command Line Interface 163 Updating Events 164 Using the Web based Interface 164 Using the Command Line Interface 171 Updating Multiple Events at
315. ton Replaces the assigned action for an event Perform the following procedure 1 Click on the Continue button 2 Select the actions to replace 3 Select the new action 4 Click on the Replace Action button 5 Deselect the check box for any events for which you do not want to replace the action 6 Click on the Commit button 176 Configuring Events Table 5 1 Batch Update Options continued Option Description Replace events action Search by action keyword Remove action from events Search action Remove action from events Search by action keyword Replaces the assigned action for an event Perform the following procedure 1 Enter the keyword in the box 2 Click on the Cont inue button 3 Select the actions to replace 4 Select the new action 5 Click on the Replace Action button Removes an assigned action from an event Perform the following procedure 1 Click on the Continue button 2 Select the action to remove 3 Click on the Remove Action button 4 Deselect the check box for any events for which you do not want to delete the action 5 Click on the Commit button Removes an assigned action from an event finds event action combination by searching for an action Perform the following procedure 1 Enter the keyword in the box 2 Click on the Cont inue button 3 Select the action to remove 4 Click on the Remove Action button 5 Deselect the check mark for any events for
316. tricting ESP Administration and Set Environment permissions for a current user will result in the authentication failure Vv Vv Vv Vv Vv Iv Iv ESP Administration and Set Environment Configuration Events Actions Diagnostics and Site Reports Availability Reports HW and SW Reports View Logs Create and View Log Commit Figure 3 9 Updated Update User Permissions Window Web based Interface 6 Select the permissions that you want the user to have Refer again to Table 3 2 on page 75 for descriptions of the permissions Note Restricting the ESP Administration and Set Environment permission for the current user causes the interface to display an Authorization Failed message because the account no longer has access to the Update Permissions command 7 Click on the Commit button 82 Setting Up the User Permissions Using the Command Line Interface You can use the espconfig command to list the available permissions on a system and to list add or delete user permissions Use the following command syntax to create the default user account and password usr sbin espconfig createadmin Use the following command syntax to list the permissions that are available on a system usr sbin espconfig list permdesc perm permission name gt lt permission name gt If you do not specify a specific permission name this command displays all permissions that are available on the system Use the follow
317. tru ction 0x2008 Fail piece delayed 0x2007 Interrupted write completed 0x 2004 Interrupted write started 0x20 03 Repair completed 0x2002 Repair started 0x2001 Environmental card miswire reso lved 0x1512 Channel miswire resolved 0x151 1 Channel reset occurred 0x150D Unresponsive environmental card ESM bad AL PA error 0x150 c Unresponsive alternate controll er bad AL PA error 0x150B Loop port bypass LPB issued t utu zu A z Z zi Zz Oo Oo 00000080 z A 0 0 070 Z zZ O A aa zu Zz Zz 2 Z Zz Oo Oo 00000080 zi z O 0 0 0 Zz 2 9 ESP for the IRIX OS 3372 3371 3370 3369 3368 3367 3366 3365 3364 3363 3362 3361 3360 3359 3358 3357 3356 3355 3354 3353 o environmental card ESM 0x15 ie Loop port bypass LPB issue o alternate controller 0x15 Loop port bypass LPB issue o drive 0x15 Loop port enable PE issue o environmental card ESM 5 sue x15 Loop port enable PE issue o drive 0x15 Selective LIP reset issued to nvironmental card ESM 0x1503 Selective LIP reset issued to a lternate controller 0x150 Selective LIP reset issued to rive 0x150 oco S Oo Loop port enable PE i o alternate controller 91 OQ OQ Or Or Or 0 Qi O A X Wwe dence a E e qub gm pne S S
318. ts in diagnosis of Identifies performance Monitoring Tools performance analysis Extensible rule evaluation mechanism Local or remote service failure detection and quality of service monitoring system level performance issues Provides an easy method to add site or system specific rules to the default set Automates detection of failed services for proactive support hotspots and areas where system resource usage could be optimized for improved performance Enables use of additional software products to extend the range of monitored subsystems for example Cisco routers and Web servers Increases service availability and quality by automating service probing and checking ESP is a modular system that uses a producer client architecture and receives events from the Event Manager Each module works independently on a specific function and no functional overlap exists between the various modules Some modules run as daemons some run as dynamic shared objects DSOs that can load into the Event Manager and some run as stand alone applications that are driven by events Note For more information about the Event Manager and the client producer architecture refer to the Event Manager User Guide publication number 007 4661 00x The daemon components of ESP are e Core software System Support Database SSDB espdbd Monitoring software Event monitor subsystem eventmond ESP Architecture
319. umber Status baltic csd sgi com N A 134 16 241 92 SGM C balkan csd sgi com N A 134 16 241 91 Subscribed Continue System Name IP Address Current Figure 6 19 Availability Reports for System Group Window System Group Manager Mode 3 Specify the range of dates for the report 4 Select the systems to include in the report 5 Clickonthe Generate Report button Figure 6 20 shows an example availability report for a specific host Availability Reports Sm eSp Embedded Support Partner ver 30 rm ESP Administration nil Set Environment MEU EE Reports Logbook Availability Report baltic csd sgi com Interrupts Downtime MTBI Availability Unscheduled 2hrs43 min 125 hrs 3 min 99 46 reset action 2hrs43 min 125 hrs 3 min Scheduled 11 1hr32min 45 hrs 28 min 99 69 unknown 11 1hr32min 45 hrs 28 min Scheduled and Unscheduled 15 4hrs 15min 33 hrs 20 min 99 15 Average uptime 30 hrs 59 min Least uptime 4 min Most uptime 211 hrs 56 min current epoch Average downtime 17 min Least downtime 5 min Most downtime 1 hr 16 min Monitoring started at Wed Jul 23 16 52 26 2003 Last boot at Mon Aug 4 17 09 08 2003 Total time since last reboot 211 hrs 55 min Most Unsubscribed time 0 min All registered availability events Figure 6 20 Example Availability Report for a Specific Host System Group Manager Mode 251 Chapter 6 Viewing Report
320. valds used with permission by Silicon Graphics Inc MIPS is a trademark of MIPS Technologies Inc used under license by Silicon Graphics Inc Netscape is a trademark of Netscape Communications Corporation UNIX is a registered trademark and X Window System is a trademark of The Open Group U S Robotics and Sportster are trademarks of 3Com Corporation All other trademarks are the property of their respective owners Embedded Support Partner User Guide Document Number 007 4065 009 Contents List of Figures xi List of Tables xix What s New in this Document xxi Introduction 1 Distribution 3 BasePackage 3 Extended Package 4 Named Groups 6 Full and Light Nodes 7 TCP IP Protocol 9 Group Management Over Hierarchies 9 Simplified Group Management Configuration 11 Enhanced Configuration for SGM Clients 11 Central Logbook Capability 11 ESP Benefits 12 ESP Architecture 14 Core Software 19 System Support Database SSDB 19 ESP and SGM DSOs 19 Monitoring Software 21 Configuration Monitoring 21 Event Monitoring 22 Availability Monitoring 25 Notification Software 26 Console Software 28 Web based Interface 28 Contents Command Line Interface 29 External Tools 30 Performance Monitoring Tools 30 Diagnostic Tools 31 RAID Monitoring Tools 31 Remote Support Capability 31 Security Features 32 System Performance Impact of ESP 33 2 Accessing ESP 35 Using the Command Line Interface 35 Using the Web based Interface 42 Openi
321. vents sysid system id host host name Use the sysid option to select a system by system ID Use the nost option to select a system by hostname If you do not specify the sysid or host option this command deletes data from the database tables on the local system 181 Chapter 5 Configuring ESP 182 Subscribing Events from SGM Clients You can select which events to subscribe from the SGM clients Tip ESP 3 0 includes an automatic subscription option If you enable the Automatic events subscription option when you add a client ESP automatically subscribes events from the client Then you do not need to manually subscribe events via the Subscription button Using the Web based Interface Perform the following procedure to use the Web based interface to subscribe to events 1 Clickonthe Configuration button 2 Clickon the Events button 3 Clickon the Subscription button Note If the system is an SGM server the interface displays a list of clients Refer to Figure 5 29 Click on the client that you want to use and click on the continue button The interface displays the Events Subscription by Class window Refer to Figure 5 30 Configuring Events fap esp am Embedded Support Partner ver 30 A ESP Administration mi aaau v Configuration i Reports i Logbook AA Batch Event Subscription IP Serial Events ESP Ako quen TC Type Number Subscribed Version baltic baltic csd sg
322. x Process pid 0 9 kil led not enough memory to lock stack unix Process pid 0 9 kil led process or stack limit exc eeded unix ALERT Process generat ed trap but has signal 0 9 held or ignored unix Process pid 0 9 kil led due to no more swap space unix Process pid 0 9 kil led due to bad page read unix Swap failed on logical swap 0 9 blkno 0x for proc GS unix Process pid 0 9 kil led due to insufficient memory Swap unix Memory Deadlock with no one to kill unix Swap allocation overflow 2 unix Paging Daemon vhand no t running NFS server down unix Read error in swap ksta ck ext for pid 0 9 proces S cannot be run again unless th is is corrected unix Read error in swap for p id 0 9 process cannot be r un again unless this is correct ed unix out of logical swap Space during Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes ESP for the IRIX OS 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 7001 194383 194382 194381 194380 194379 194378 194377 194375 194374 194373 194372 194368 194367 194366 194365 194363 194361 194360 194359 194358 194357 un
323. ystem espreport help Information Commands espreport help prototype spreport spec espreport version Report Commands espreport availability sysid system id host host name gt from mm dd yyyy to mm dd yyyy espreport action taken sysid system id host host name gt from mm dd yyyy to mm dd yyyy espreport events sysid system id host host name gt from mm dd yyyy to mm dd yyyy tid type id td type desc gt cid class id cd class desc espreport hwchanges sysid system id host host name from mm dd yyyy to mm dd yyyy espreport swchanges sysid system id host host name gt from mm dd yyyy to mm dd yyyy espreport logbook sysid system id host host name gt from mm dd yyyy to mm dd yyyy espreport summary sysid system id host host name gt from mm dd yyyy to mm dd yyyy espreport sysinfo sysid system id host host name all Refer to Chapter 6 Viewing Reports for more information about using the espreport command esplognote does not have any command line options system esplognote Refer to Chapter 7 Using the ESP Logbook for more information about using the esplognote command 41 Chapter 2 Accessing ESP Using the Web based Interface The Web based interface provides a graphical interface that you can use to access ESP You can use the following methods to access the Web based
324. ystem that stores ESP data in a database on a local disk and also sends the data to a group manager system for storage In this case ESP maintains two copies of the data one copy on the local system and one copy on the group manager system A light node is a client system that sends all ESP data to a group manager system for storage No ESP data is stored on the client system which reduces the resources used on the system In this case ESP stores all data on the group manager system For light nodes you can generate reports on the SGM server by accessing the ESP 3 0 interface from the Web server or by running the espreport command on the SGM server Running espreport on a light node returns the following message ESPREPORT EventRprt This system is a light node espreport cannot be run on light node Note You can convert a light node to a full node at any time however only data that is generated after the conversion completes is stored in the local database Data generated before the conversion completes is stored only in the database on the SGM server Figure 1 4 shows an example of a group that contains full and light nodes Chapter 1 Introduction Group manager System 1 Full node System 2 Light node System 3 Light node System 4 Full node Figure 1 4 Full and Light Nodes Distribution TCP IP Protocol ESP 3 0 uses TCP IP protocol to communicate between a group manager system
325. zo a ESP Administration mi Set Environment Reports E FR Logbook AA Add An Action Action descriprion send me mail Action string fusribin espnotify E me sgi com n 7 m 96H 95D 96z Action should be executed as nobody Action timeout 600 seconds Commit Figure 5 40 Verification Message for Adding an Action Using Other Action Option 6 Click on the Commit button 198 Configuring Actions The interface displays a confirmation message Refer to Figure 5 41 If you need to update the action parameters click on the Update button FIBI E Embedded Support Partner ver 30 a ESP Administration mi Set Environment Z Configuration E Reports Logbook AA P Actions Add Action Action description send me mail Action string fusrfbinfespnotify E me sgi com n 7 m H 96D 96z Execute action as nobody Action timeout 600 seconds Update Figure 5 41 Confirmation Message for Adding an Action Using Other Action Option 199 Chapter 5 Configuring ESP 200 Using the Command Line Interface Use the following espconfig command syntax to add an action usr sbin espconfig add evaction acd action description act action string user lt name gt retry lt count gt tout lt timeout value gt throttle lt throttle value gt enabl disable Use the acd option to specify a description of the action a string enclosed in quotes Use the act option to

Embedded Support Partner User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents