Pillar Axiom Replication Engine (MaxRep)
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
 

In this Document

Purpose

Scope

Details

The Replication Bundle

Directory Structure Composition

Key Information Gathering

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Internal processing commands.

Applies to:

Purpose

Little or no documentation exists on how to process MaxRep information in an Axiom or FS1-2 log bundle collection.

Scope

This document was created to assist support personnel in doing an initial triage of a MaxRep issue based solely on the contents of the replication directory.  As more information becomes known, this document will be updated to reflect the new information.

Details

The Replication Bundle

In order to properly troubleshoot a MaxRep issue, it is necessary to have an Axiom or FS1-2 log bundle with the replication sub directory included.  If this sub directory is missing, it will be necessary to gather a manual log bundle and attach it to the Service Request.  Please refer to KM Document 1943289.1 FS System: How to Attach a Manual Log Bundle to an Existing MOS Service Request.  Be sure to confirm that the replication box is checked.

Inside the replication sub-directory, the MaxRep log will be in the following format:
DFEE5CB023AA4D70BA31793C9367643B-FS1-MAXREP-161201191518.tar.gz

The information can be uncompressed using the tar utility with the xzf options:

Directory Structure Composition

The list directory structure below is based on R3.  MaxRep R2 has a single directory (hostlogs).  Items (files or directories) that end in an asterisk can be found in the hostlogs directory under the same or very similar name.  Filenames in italics indicate multiple files with the same type of information.  Example: monitor_jobs.log, monitor_jobs.log.1.gz.

• home/svsystems
  • etc/amethyst.conf^*
  • system/var
    • monitor_jobs.log
    • readme.txt = this directory contains logs related to the support User Interface.
    • run_job.log
    • system_job.log
    • system_job.pid
  • transport/log^*
    • cxps.err.log
    • cxps.monitor.log
    • cxps-xfer.log
    • cxps.xfer.log.diff
  • var
    • Message.log
    • PS_GUIDS
    • ResyncStartNotify.log
    • VolumeProtection.lo
    • apache.txt
    • array.log
    • bpmtrace.log^*
    • check_report_date.txt
    • configurator.log
    • configurator_resister_host_dynamic.log
    • cs_db_backup/
    • cs_migration.log
    • curl_monitor.log^*
    • cxapi.txt
    • exs.log
    • event_data_.txt
    • hosts/
    • ipmi.log = information (part #s etc) gathered from ILOM
    • monitor.log^*
      
    • monitor_disks.log^*
    • monitor_protection.log^*
    • monitor_ps.log^*
    • perl_sql_error.log^*
    • php_sql_error.log
    • phpdebug.txt^*
    • prism.log^*
    • psaitest.log
    • rx.log
    • schedulerapi.log
    • services/
    • system_job.log
    • system_job.pid
    • systemmonitor.log = output of show /System/Open_Problems command in ILOM
    • tmp-arch583e3ee5ae685/
    • unmarshal.txt^*
    • volsync*.log^*
    • volume_register.log^*
    • vxstub.log
    • vxstub_get_application_settings.log
    • vxstub_get_initial_settings.log
    • vxstub_update_cdp_information_v2.log
    • vxstub_update_discovery_info.log
    • vxstub_update_policy.log
      
      
• usr/local/InMage^*
  • Fx
    • config.ini
    • sv.log
  • Vx/etc
    • drscout.conf
      
      
• var/log^*
  • CDPMgr.log
  • CacheMgr.log
  • InMage_drivers.log
  • appservice.log = information related to array registration, rediscovery, LUN mapping/unmapping commands
  • cdpcli.log
  • cx_install.log
  • fabricagent.log = port offline and vsnap export operations
  • fabricmanager.log = Fibre Channel information
  • pcli.log = information related to array registration, rediscovery, LUN mapping/unmapping commands
  • re_install.log
  • read-only-mount.log
  • s2.log
  • svagents.log = volume reporting
  • ua_install.log
  • vcaps.log

Key Information Gathering

• Gather basic information about the MaxRep Engine (version etc):
  
  • From inside the log bundle directory, cd replication/home/svsystems/var
  • R2.x versions will have a file called array_register.log:
    
    % grep  -m 1 ApplianceVersion array_register.log| gawk 'BEGIN { FS = "\"" } ; { print  "", $26, $28, "\n", $42, $44, "\n", $30, $32, "\n", $10, $12, "\n", $38, $40, "\n", $14, $16, "\n", $22, $24, "\n", $18, $20, "\n", $6, $8, "\n", $46, $48, "\n", $34, $36, "\n" " type", $4 }'
     LogCollectionUrl http://130.200.109.244:80/Axiom_Log_Collector.php
     uname replication
     ManagementUrl http://130.200.109.244:80
     SharedApplianceGuid df825fba-6d3b-4fcf-8619-d414d9de8209
     ip 130.200.100.170
     ApplianceName MAXREPENG.PRPA.GOBIERNO.PR
     ApplianceVersion 2.00.05
     ApplianceIpAddress 130.200.109.244
     ApplianceGuid 423d4235-5bfe-460a-9d77-d06d25052e11
     pwd TwinPeaks
     arrayGuid 12D8D634-CF0A-466D-B883-6EAECD242F3E
     type Axiom
     
  • R3.x versions will have a file called configurator.log:
    
    % grep -m 1 -A 5 -B 8 '\[ApplianceVersion\]' configurator.log
        [LogCollectionUrl] => http://192.168.250.133:80/Axiom_Log_Collector.php
        [uname] => replication
        [ManagementUrl] => http://192.168.250.141:80
        [SharedApplianceGuid] => a618a961-beb2-4be1-953a-c30dda8783f9
        [ip] => 192.168.250.135
        [status] => success
        [ApplianceName] => maxrep1.magnasur.local
        [ApplianceSerialNumber] => 1605NM2036
        [ApplianceVersion] => 3.0.4
        [ApplianceIpAddress] => 192.168.250.133
        [ApplianceGuid] => 9e9ffff8-ffa9-4119-a2d9-d6f5c49ed603
        [pwd] => 2013bc1d8192736333bf828ed7a4d0778aU2FsdGVkX1/lmDooVLVgEe8ghKU1mVCCb4WE70lvhls=
        [arrayGuid] => A824F7EB-89FC-435A-B996-F79A4F395696
        [type] => Axiom

 More information to follow....

This solution has no attachment