- Machine Control and Guidance Products
- CMD FOR HAULING (S/N: CM41-UP; CM51-UP; AT61-UP)
- Off-Highway Truck/Tractor
- 789D (S/N: SPD1-UP)
- 793F (S/N: D3T1-UP; RBT1-UP)
- 797F (S/N: LAJ1-UP; LTZ1-UP)
- 793F (S/N: D3T1-UP; RBT1-UP)
Introduction
This Special Instruction provides information for Autonomy Log Processing.
Important Safety Information
Do not perform any procedure in this Special Instruction until you have read this Special Instruction and you understand this information. Use only proper tools and observe all precautions that pertain to the use of those tools. Failure to follow these procedures can result in personal injury. The following procedures should also be observed.
Work safely. Most accidents that involve product operation, maintenance, and repair are caused by failure to observe basic safety rules or precautions. An accident can often be avoided by recognizing potentially hazardous situations before an accident occurs.
A person must be alert to potential hazards. This person should also have the necessary training, skills, and tools to perform these functions properly.
Safety precautions and warnings are provided in this instruction and on the product. If these hazard warnings are not heeded, bodily injury or death could occur to you or to other persons. Caterpillar cannot anticipate every possible circumstance that might involve a potential hazard.
Therefore, the warnings in this publication and the warnings that are on the product are not all inclusive. Ensure that any tool, procedure, work method, or operating technique you use that is not recommended by Caterpillar is safe.
System Overview
| |
| Illustration 1 | g03860250 |
- The system consists of a Network Attached Storage device, a minimum of four VMware appliances running in vSphere, and one VMware appliance (LTA) running on a Windows desktop via VMware Player
- The Network Attached Storage device stores the Applications package, incoming logs files, processed results, and system configurations.
- A minimum of four VMware Appliances (has been tested up to 10) running in vSphere runs the log processing, schedules jobs, generates e-mail reports and provides a web-based status and control interface.
- The LTA VM running on the desktop connects to the USB Log Disks and uploads the logs to the NAS. LTA VM also generates reports via email regarding log disk notices, results disk notices, and diagnostic messages (if configured).
Document Summary
This document shows how to set up the Autonomy Log Processing (ALP) system. The document covers the setup for the entire system, including configuration of the transfer appliance, the scheduler, the worker nodes, and the NAS settings. The tasks described in this document only need done once per ALP OS upgrade.
Download Most Recent Releases of the OS Image and Software
Download the most recent versions of the ALP OS image and the ALP software. Contact Product support for the current software and image version.
Required Tools
- Network connection to ESX server (hosting the processing appliances)
Note: Only ESX Version 5.1 has been tested
- VMware vCenter Converter (for uploading VMware appliances to the ESX Host.)
- VMware vSphere Client
- A desktop with VMware Player 5.0.2 (to host the log transfer appliance)
Note: Only VMware Player 5.0.2 has been tested
- Network Attached Storage (accessible via NFS version 3)
Required Hardware for Office Setup
Set Up Prior to Installing
Note: This system is only tested against an NFS version 3 file share. (NFS 4 and CIFS have several bugs and performance issues for these tasks.)
- The NAS IP Address is the numeric network address assigned to the NAS (192.168.1.100)
- The NAS Mountpoint is the directory or share that you specify when mounting the NAS (for instance if you run "mount 192.168.1.100:/volume/one /mnt" , then the NAS Mountpoint is "/volume/one"
All files and folders related to the Automated Log Processing will be contained to one base directory. (Though Caterpillar recommends having a dedicated NAS for the automated log processing, the ALP system should never touch a file that exists outside of this single base directory.)
Enable Virtualization Within the BIOS of the Log Transfer Host Machine
In order for the Log Transfer Appliance (LTA) VM to function properly, virtualization must be enabled within the BIOS of the motherboard. Both virtualization (VTx) and virtualization for direct I/O (VTd) must be enabled within the BIOS. If virtualization is not enabled, the VM will not function as designed. Failure to enable these features will result in an unpredictable performance such as slow transfer speeds.
Note: The configuration of the BIOS will vary from different manufacturers. The following images are taken from a Dell laptop BIOS. The configuration appearance may be different, but the BIOS settlings for virtualization will be the same among all Intel-based motherboards. The terminology may slightly differ for the virtualization settings on different manufacturers motherboards or different versions of the BIOS.
- Boot the computer into the BIOS screen. Booting into the BIOS varies between different manufacturers and different model machines. Contact the local service help desk if directions on how to boot into the BIOS is needed.
Show/hide table
Illustration 2 g03860260 - Once the BIOS is booted, enable Intel Virtualization Technology (VTx).
Note: The name for virtualization may slightly vary from different BIOS versions or manufacturers.
Show/hide table
Illustration 3 g03860261 - Once virtualization is enabled, also enable Virtualization for Direct I/O (VTd).
Note: The name for Virtualization for Direct I/O may slightly vary from different BIOS version or manufacturers.
- Once the BIOS changes have been enabled, apply the changes and the computer will be ready for setup after a reboot on the ALP LTA VM.
Prepare the Network Attached Storage (NAS) - Part 1
Note: This section must be performed from an OCS laptop logged in as the "pf" user. If not done from an OCS laptop as "pf", there may be permission issues that cause the ALP not to boot properly.
- Mount the NAS share that will be used for Automated Log Processing.
- Create the directory "automatedLogProcessing" at the top level of the NAS share with the exact spelling and capitalization as shown.
Determining Network Addresses
Determining Network Addresses will be dependent on the Network Administrator. The system requires one IP address on the same subnet for all the processing and log transfer nodes. A gateway which can access the Internet is required for the transmission of e-mail notifications. One or more valid DNS servers are required for looking up network time protocol servers, and e-mail servers.
To configure each node, the following features are needed:
| Hostname | Recommended format of "processing1", "processing2", ... or "lta1" |
| IP Address | IP Address can be a public or private IP address. A private, firewalled network is recommended as there is no direct security on the embedded web server |
| Netmask | Netmask must be the same netmask for all nodes |
| Gateway | Gateway is required for the transmission of e-mail and network time |
| DNS | One or more valid DNS servers to resolve e-mail servers and NTP servers |
| NAS IP Address | NAS IP Address is the network address of the dedicated Network Attached Storage device |
| NAS Mountpoint | NAS Mountpoint is the path of the file share on the NAS. If there is only one share, this may be a single forward slash ( "/"). NAS Mountpoint is dependent on the NAS and its configuration |
Setting Up the Processing Nodes
Setting Up the First Processing Node
- Uncompress the VM zip file to prepare for the ESXi conversion.
- Open VMware vCenter Converter
Show/hide table
Illustration 4 g03860262 - Select "Convert machine".
Show/hide table
Illustration 5 g03860264 - Configure the Source System page to look like the following:
- Select source type: "VMware Infrastructure virtual machine"
- Log in with the site-specific ESXi server address and username credentials
Show/hide table
Illustration 6 g03860265 - When all settings have been selected, click "Next >".
Show/hide table
Illustration 7 g03860266 - Configure the "Destination Virtual Machine" window.
Note: These settings will be site-specific and will require the server/account information for the local ESX/vSphere Infrastructure.
- Name the virtual machine. It is recommended when naming the VM to append the hostname that is : "CommandForHauling_ALP_2013-02-13-v3-processing1". It is also recommended to include the date of the ALP image release in the name, to tell which version of the ALP image is being ran on the servers easily.
- Select the location where to store the inventory of this current VM. This option is site-specific.
Show/hide table
Illustration 8 g03860265 - When all settings have been selected, click "Next >".
Show/hide table
Illustration 9 g03860267 - Configure the "Destination Location" window.
- Select the inventory location and datastore to save the VM to. This option is site-specific.
- Set the Virtual Machine Version to Version 8 if available. (If Version 8 is not available, set to Version 7)
Show/hide table
Illustration 10 g03860265 - When all settings have been selected, click "Next >".
Show/hide table
Illustration 11 g03860268 - When the "Options" window appears, confirm that the settings are set to the following.
- vCPUs: 2
- Disk controller: autoselect (internally the disk controller will use the most efficient paravirtual scsi)
- Memory: 8GB
- If all settings are correct, click "Next >" to proceed to the "Summary" page.
Show/hide table
Illustration 12 g03860269 - In the "Summary" page, confirm that all the settings are correct for what was configured earlier and all site-specific settings.
Show/hide table
Illustration 13 g03860270 - If all settings are correct, click "Finish".
Show/hide table
Illustration 14 g03860272 - The VM will be converted to the destination you specified. Wait for the process to finish before continuing. Wait for the Status of the conversion to say "Completed".
- Open VMware vSphere Client and login with the proper credentials.
Show/hide table
Illustration 15 g03860273 - Select the newly imported VM on the left-hand side and click "Edit virtual machine settings".
Show/hide table
Illustration 16 g03860275 - Select "Network adapter 1".
Show/hide table
Illustration 17 g03860276 - Click "Remove" to remove the default network adapter settings. A line will appear through the network adapter settings after the button has been pressed.
Show/hide table
Illustration 18 g03860278 - Click "Add...".
Show/hide table
Illustration 19 g03860279 - Select "Ethernet Adapter" and click "Next >".
Show/hide table
Illustration 20 g03860280 - Configure the "Network Type" window.
- Set Adapter Type to "VMXNET 3"
- Select the appropriate Network Label (Network Label is a site-specific parameter)
- Make sure "Connect at power on" is Selected
Show/hide table
Illustration 21 g03860281 - When all the settings have been changed, click "Next >"
Show/hide table
Illustration 22 g03860282 - Confirm in the "Ready to Complete" window that the Adapter type is set to VMXNET 3 and the Network Connection is set to the site-specific network settings. Click "Finish" if all settings are correct.
Show/hide table
Illustration 23 g03860283 - Click "OK" to exit the Setting window.
Show/hide table
Illustration 24 g03860284 - Wait for ESX to reconfigure the machine and for the window at the bottom to show the status of the reconfiguration as complete before proceeding.
- Refer to "Configuring a Blank ALP Virtual Machine" before proceeding to configure the settings of the blank virtual machine.
Show/hide table
Illustration 25 g03860285 - Once the "Error, Cannot Continue: No Application package in the directory at..." message has been received, power off the guest OS by right-clicking the virtual machine title and selecting "Power > Power Off".
Show/hide table
Illustration 26 g03860286 - When prompted, select "Yes" to confirm shutting down the VM.
- Once the VM has been marked as complete in the "Recent Tasks" window at the bottom of the application, the power off process is complete. Once the machine has powered off, proceed to "Prepare the Network Attached Storage (NAS) - Part 2".
Prepare the Network Attached Storage (NAS) - Part 2
- From a computer that can access NFS shares, mount the NAS share that will be used for Automated Log Processing. For instructions on how to mount an NFS share in Windows or Linux, refer to "Mounting NFS Shares".
- Verify that the directory "NAS_Directory/automatedLogProcessing/applications/" exists on the NAS where NAS_Directory is the location on the locale machine where the NAS was mounted. If the applications directory does not exist, then the processing node was incorrectly configured. If the directory exists, then the node successfully accessed the NAS.
Set Up the Remaining Processing Nodes
- Open VMware vSphere Client.
Show/hide table
Illustration 27 g03860289 - Verify that the first node is in state "Powered Off" by right-clicking the virtual machine and selecting "Power > Power Off". If the "Power Off" option is grayed out and there is not a green arrow next to the machine, then the machine is already powered off. If the machine has already powered off, proceed to Step 5.
Show/hide table
Illustration 28 g03860286 - When prompted, select "Yes" to confirm shutting down the VM.
Show/hide table
Illustration 29 g03860284 - Once the VM has marked as complete for the power off process, proceed to the next step.
Show/hide table
Illustration 30 g03860290 - Right-click on first node and select "Clone...".
Show/hide table
Illustration 31 g03860291 - Enter the name for the cloned machine (Maintaining the same basic name "CommandForHauling_ALP_2013-02-13-v3-processing2...10" is suggested) and select the Inventory Location that the node is to be saved to (site specific). When finished click "Next >".
Show/hide table
Illustration 32 g03860293 - Select the ESX Host/Cluster that will run the Node (site specific). When finished, click "Next >".
Show/hide table
Illustration 33 g03860294 - Select the Resource Pool to run the virtual machine within (site specific). When finished, click "Next >".
Show/hide table
Illustration 34 g03860296 - Select the appropriate Storage (site specific). When finished, click "Next >".
Show/hide table
Illustration 35 g03860297 - For the Guest Customization window select "Do not Customize" and click "Next >".
Show/hide table
Illustration 36 g03860299 - Confirm that all the settings are correct in the "Ready to Complete" window and click "Finish" to begin cloning the VM. Make sure that the "Edit virtual hardware" check box is not selected.
Show/hide table
Illustration 37 g03860300 - Wait for vSphere to Clone the Node. Do not proceed until the "Recent Tasks" confirms that the virtual machine clone has completed.
Show/hide table
Illustration 38 g03860301 - Power on the newly cloned node by right-clicking the machine and selecting "Power > Power On".
Show/hide table
Illustration 39 g06349457 - Select the "Console" tab of the newly cloned virtual machine. When fully booted and not yet configured, the console will show "Could not find Config File: /boot/CONFIG/ahs_alp_config.txt. END OF LINE".
Show/hide table
Illustration 40 g03860303 - Click inside the console, then Press "Alt + F2" and the current configuration window will display with all the cloned nodes network values.
Show/hide table
Illustration 41 g03860304 - To edit the network settings, press "1" then "Enter" to navigate to the network settings.
- Press "1" then "Enter" to change the hostname.
Show/hide table
Illustration 42 g03860305 - Enter in the new hostname for this node and press "Enter".
Note: Best practice for naming hostnames is to use only lower/uppercase letters, numbers, and hyphens. Hostnames cannot contain underscores within their name. If an invalid character is used, the ALP will not boot with an IP address.
- Press "2" then "Enter" to change the IP address
Show/hide table
Illustration 43 g03860319 - Enter in the new IP address for this node and press "Enter".
Note: When entering in arguments, make sure that only the number, period, and enter keys are pressed when entering the IP information. If any other keys are pressed that are not supposed to (such as CTRL, arrow keys, and ALT.) when entering in the IP arguments, the ALP may not boot with an IP address since a garbage character was added to the configuration.
- Now that the IP address and hostname have been changed for the cloned VM, press "0" then "Enter" to return to the main menu. If the network was successfully configured, the main menu should display all the desired network information.
Show/hide table
Illustration 44 g03860320 Show/hide table
Illustration 45 g03860322 - Upon rebooting, you should see the message "Error, Cannot Continue: No Application package in the directory at...". This message is expected. (only the OS has been configured and not the applications)
Note: If you see the message ,"Error, Cannot Continue: The directory “automatedLogProcessing” was not found on the NAS..." then repeat the instructions "Prepare the Network Attached Storage (NAS) - Part 1", then reboot the guest OS.
- Once the correct error message has been received, power off the node and proceed with cloning the next node.
- Repeat Steps 1 to 23 until all the process node blades have been set up.
Setting up the Log Transfer Appliance
Note: The log transfer appliance is intended to be ran on a Windows Desktop, but has also tested under a generic Linux desktop.
- Make sure that VMware Player 5.0.2 is installed.
- Copy the original ALP Virtual Machine zip file to the target Desktop.
- Uncompress the zip file and move the uncompressed file where the VM will be stored on the log transfer machine.
Show/hide table
Illustration 46 g03860323 - Open VMware Player and select "Player", then "File", and then "Open...".
- Navigate to the directory containing the virtual machine and select the vmx file to load.
Show/hide table
Illustration 47 g03860325 - The virtual machine will now be loaded into VMware Player. Select "Edit virtual machine settings".
Show/hide table
Illustration 48 g03860327 - Select "Processors" on the left-hand Device and change the number of processor cores on the right to the required amount. The default number of processor cores is set to "2". Having a processor core per autonomy logger connected to the ALP plus one extra core to run all the base system processes is recommended. (Example: four cores can productively handle three hard drives plugged into the VM)
Note: If the number of cores is not increased to more than the default of "2", the ALP will still function but could work at a much slower speed when more than one drive is attached.
Show/hide table
Illustration 49 g03860380 - When the number of processors has been set, select "OK" to apply the changes.
Show/hide table
Illustration 50 g03860381 - Select "Player", then "File", and then "Player Preferences".
Show/hide table
Illustration 51 g03860383 - Select "Power off the virtual machine" and click "OK".
Show/hide table
Illustration 52 g03860386 - Select the VM and press "Play virtual machine".
- Refer to "Configuring a Blank ALP Virtual Machine", before proceeding to configure the settings of the blank virtual machine.
Show/hide table
Illustration 53 g03860387 - Once Section 6 is complete, power off the Log Transfer Appliance by clicking "Player > Power > Shut Down Guest" .
Show/hide table
Illustration 54 g03860390 - When prompted for a confirmation to power off the machine, select "Yes".
The Log Transfer Appliance VM is now configured and is finished until the application bundle has been installed. Proceed to the next section to install the application bundle.
Copy the Application Package to the NAS
- Locate the ALP package file for the application install.
- Mount the log storage NAS on a workstation . For instructions on how to mount an NFS share in Windows or Linux, refer to "Mounting NFS Shares".
- Copy the Application Package to the applications directory:
- NAS_Directory/automatedLogProcessing/applications/
Configure the hosts.csv File
- Power on the log transfer appliances VM (The VM that is on the user accessible workstation that will be used to transfer the logs).
Show/hide table
Illustration 55 g03860393 - It should display the message "ERROR: This node IP:(ip address), is not defined in the file...".
- From the workstation that you used to upload the application package, open up the hosts.csv file at the following location and add all the necessary IP addresses, hostnames, and each machines function in the ALP process: (it should have been created when the Log Transfer appliance was first turned on).
- NAS_Directory/automatedLogProcessing/parameters/automatedLogProcessing/hosts.csv
The File is a standard CSV with a header that describes the columns. Add rows that describe each of the nodes at the site.
Note: Opening up the csv file in a text editor and not the Excel sheet editing program is recommended. The Excel sheet editing program may change the formatting of the csv and cause potential issues.
The IP_Address field must match the IP addresses assigned to the nodes during the "Prepare the Network Attached Storage (NAS) - Part 2" procedure.
The Hostname is arbitrary. If your site has fully qualified domain names, then they should be set to those hostnames. Spaces are not allowed in hostnames.
The third column describes the function of that node.
- The Virtual Machine that transfers logs is the "xta" (which represents the log/results transfer appliance). There should only be one of these at this time.
- Elect one of the nodes installed in the VMWare ESX infrastructure to be the "scheduler". Remember which node is the scheduler, you will use that nodes IP address later.
- The remaining nodes should be set to "worker".
Note: There can only be one xTA (ALP Transfer Appliance VM) per ALP setup. Multiple xTA stations assigned to the ALP may cause errors in the ALP system as it is not designed to support multiple copy stations.
Configure E-Mail
Note: This step is required for all locations. If the site does not have access to an SMTP server, the file is still required for designating the site name in the ALP software.
- Save the provided "email.txt" file to the NAS, in the following directory:
- ./automatedLogProcessing/parameters/automatedLogProcessing/
- Open the email.txt file, and change "Site_Name" to reflect which site the software is being deployed ( such as "Navajo"). The site name must not contain any spaces within the quotes.
ALP_EMAIL_SITE="Site_Name"
- If the site does not contain an SMTP server, save the file, and proceed to "Reboot the System". For non-Caterpillar networks in need of SMTP configuration, proceed to Step 6.
- For Caterpillar networks, register the IP address of the scheduler following the instructions in the Cat Document: E-Mail Enabled Applications.
- ForCaterpillar networks, register the IP address or system DNS name at:
http://smtpreg.cis.cat.com
- Open up the email.txt file and change the "ALP_EMAIL_SMTP" value in quotes to the address of the local SMTP server (varies by location).
Note: For Caterpillar networks, the SMTP address is already configured and this step can be skipped.
- Once the correct SMTP address has been entered, save the file and close the text editor. Proceed to"Reboot the System"to apply the configuration of the email.txt file.
Reboot the System
To get the ESX nodes to read the new hosts.csv file, the ESX nodes must be rebooted. Since it is the ESX nodes first time being configured this way, all the nodes must be manually rebooted with ESXi. After the ESX nodes are configured this way, the ESX nodes willbe ableto be rebootedfrom the Log Transfer Appliance for all future maintenance.
Reboot the ESXi Nodes
- Open VMware vSphere Client and login with the proper credentials.
Show/hide table
Illustration 56 g03860437 - Select the VM on the left-hand side to reboot and click Power > Restart Guest. If a confirmation dialog window opens, confirm that you want the machine rebooted.
Reboot the Log Transfer Appliance VM
- Open the Log Transfer Appliance Virtual Machine.
Show/hide table
Illustration 57 g03860986 - Click within the VMware console and press "Alt + F3". Pressing "Alt + F3" will bring up the ALP Maintenance page.
Note: This Maintenance Page may vary slightly from release to release.
- Press "2" then "Enter" to reboot all the nodes and the transfer appliance. The LTA will reboot all the processing nodes and scheduler then reboot automatically.
Note: On this interface, the status for scheduler and processing nodes only indicates if the node is pingable, not that the ALP software is functioning on that node.
Show/hide table
Illustration 58 g03860989 - Wait until all the processing nodes have rebooted and come online and the scheduler is online according to the main screen of the ALP Log Transfer Appliance window.
- After all the nodes reboot, the web page to monitor the status of the ALP system can be viewed. The web page is the IP address of the scheduler node, that is http://192.168.12.11 in the previous example.
Configuring a Blank ALP Virtual Machine
- Power on the VM
Show/hide table
Illustration 59 g03861848 - Open Console, When booted, and not yet configured, you should see "Could not find Config File" warning as shown below.
Show/hide table
Illustration 60 g03861851 - Click the console, then Press "Alt - F2" and the current configuration window will display with all blank values.
- To edit the network settings, press "1" and "Enter" to navigate to the network settings. A blank network settings window will appear. As the arguments are entered, the arguments will update on the network summary page.
Note: When entering in arguments, make sure that only the number keys, period key, and enter key are pressed while entering the IP information. If any other keys are pressed (such as CTRL, arrow keys, ALT, and so on.) when entering in the IP arguments, the ALP may not boot with an IP address since a garbage character was added to the configuration.
- Press "1" to change the hostname, "2" for the IP address, and so on.
- When finished entering in the desired IP information, press "Enter" to save each individual argument and return to the Network configuration page.
- Repeat Steps 8 to 9 until all the network settings have been saved.
Note: If the site is not using a Gateway or DNS address, a fake DNS address and gateway MUST be specified or the ALP will not boot with a network address. If no DNS or gateway is configured, enter in 0.0.0.0 as the IP.
Show/hide table
Illustration 61 g03861852 - When all the network configurations are saved, press "0" and "Enter" to return to the main menu. If the network was successfully configured, the main menu should display all the network information populated with the Network Attached Storage section still blank.
Show/hide table
Illustration 62 g03861853 - To edit the Network Attached Storage settings, press "2" and "Enter". A blank network settings window will appear. As the arguments are entered, the arguments will update on the network summary page.
- Press "1" to change the NAS IP, "2" to change the NAS Mountpoint, and so on. Press "Enter" when the desired option is selected.
- When finished entering in the arguments, press "Enter" to save each individual argument and return to the Network configuration page. As each argument is entered, the information should populate in the configuration window.
Note: When entering in the NAS mountpoint, make sure that the first slash is included in the mountpoint address (such as: /NAS/mount and not NAS/mount).
- Repeat Steps 13 to 14 until all the network settings have been saved.
- When all the Network Attached Storage arguments have been entered, press "0" then "Enter" to return to the main menu.
- Confirm that all the settings are correct on the Main Menu and press "0" then "Enter" again to reboot with the new settings.
Note: Every setting requires an entry except the NAS OPTIONS argument. This argument is optional.
Show/hide table
Illustration 63 g03861855 Show/hide table
Illustration 64 g03861869 - Upon rebooting, you should see the message "Error, Cannot Continue: No Application package in the directory at....". This message is expected (only the OS has been configured and not the applications).
Note: If you see the message ,"Error, Cannot Continue: The directory “automatedLogProcessing” was not found on the NAS..." then repeat the instructions "Prepare the Network Attached Storage (NAS) - Part 1", then reboot the guest OS.
Note: If after repeating the steps in "Prepare the Network Attached Storage (NAS) - Part 1" and rebooting the guest does not result in the expected message, then the NAS IP Address or NAS Mountpoint may be incorrect.
Updating Releases
Required Tools:
- Access to ALP Copy Station.
- Access to the NAS containing the Automated Log Processing directory.
- The latest ALP software update. This update can be found on the Cat Box website:
https://cat.app.box.com/files/0/f/1660074000/Command_for_hauling_Software
Preparing the Update
- Mount the NAS
- Open up a connection to the NAS and navigate to the automatedLogProcessing/applications directory.
Show/hide table
Illustration 65 g03861877 - Copy the updated software package to the folder. Do not delete the older version of the software yet.
Example:/AMT_TOOLS_PFM4_IM4.1_REL20_
ALPHA_01/outputALP/ahs-u1204-alp-
applications-2014-02-04-1456-v1-AMT_
TOOLS_PFM4_IM4.1REL20_ALPHA_01.package
Performing the Update
- Navigate to the copy station VM and click inside the VM. Once inside the log transfer appliance VM, press "Alt + F3".
The Maintenance Interface window should show up. Take note of the ALP "Application Version" to make sure that the software update changes the release version.
Note: If running an older version of the ALP software, this screen may not match entirely as the older versions only contained the software and OS version for the actual LTA and not all the nodes. For the older versions of software, reference the "ALP Version" instead for the "Application Version".
- Press "2" then "Enter" to reboot all the nodes and transfer appliance. A confirmation window will show up asking to confirm that all the nodes and copy station should be rebooted. Type "Yes" with a capital "Y" and press "Enter".
- The system will now reboot. Once the system has rebooted to the main transfer appliance window, press "Alt + F3" to return to the Maintenance Interface window.
Show/hide table
Illustration 67 g03861906 - Before proceeding, wait until all the Processing Nodes are online.
Show/hide table
Illustration 68 g03861907 - Once all the processing nodes are shown online, press "R" then "Enter" to refresh the Maintenance Interface screen. The processing nodes will all update with the current OS and Application versions. Check the "Application Version" of each ALP node and make sure all the ALP nodes match. If a software version differs from that running on the ALP transfer appliance, the Application Version will be displayed in red.
Note: The only way to confirm that the software version is correct for each node on the older software versions is to SSH into each node and view the banner at the time of login as shown below. This is no longer needed on the newer versions of software.
- If all the ALP nodes "Application Version" match the new ALP release, then it is safe to delete the older release of the ALP in the automatedLogProcessing/applications folder. Once the update is finished, there should not be any other version of software besides the current version within the applications folder.
| |
| Illustration 66 | g03861881 |
Required Tools
- Access to ALP Copy Station
- Access to the NAS containing the automatedLogProcessing/applications directory
- The ALP software update for downgrading.
ALP software update for downgrading can be found on the Cat Box website:
https://cat.app.box.com/files/0/f/1660074000/Command_for_hauling_SoftwarePreparing the Downgrade
- Mount the NAS.
- Open up a connection to the NAS and navigate to the automatedLogProcessing/applications directory.
Show/hide table
Illustration 69 g03861877 - Copy the older software package to the folder and delete the newer version of software. For Example:
/AMT_TOOLS_PFM4_IM4.1_REL20_ALPHA_01/outputALP/ahs-u1204-alp-applications-2014-02-04-1456-v1-AMT_TOOLS_PFM4_IM4.1REL20_ALPHA_01.package
Performing the Downgrade
- Navigate to the copy station VM and click inside the VM. Once inside the log transfer appliance VM, press "Alt + F3". The Maintenance Interface window should show up. Take note of the ALP "Application Version" to make sure that the software downgrade changes the release version.
Note: If running an older version of the ALP software, this screen may not match entirely as the older versions only contained the software and OS version for the actual LTA and not all the nodes. For the older versions of software, reference the "ALP Version" instead for the "Application Version".
- Press "2" then "Enter" to reboot all the nodes and transfer appliance. A confirmation window will show up asking to confirm that all the nodes and copy station should be rebooted. Type "Yes" with a capital "Y" and press enter.
- The system will now reboot. Once the system has rebooted to the main transfer appliance window, press "Alt + F3" to return to the Maintenance Interface window.
Show/hide table
Illustration 71 g03861906 - Before proceeding, wait until all the Processing Nodes are online.
- Once all the processing nodes are shown online, press "R" then enter to refresh the Maintenance Interface screen. The processing nodes will all update with the current OS and Application versions. Check the "Application Version" of each ALP node and make sure they all match. If a software version differs from that running on the ALP transfer appliance, the "Application Version" will be displayed in red.
Note: If running an older version of the ALP software, this screen may not match entirely as the older versions only contained the software and OS version for the actual LTA and not all the nodes. For the older versions of software, reference the "ALP Version" instead for the "Application Version".
| |
| Illustration 70 | g03861907 |
Mounting NFS Shares
Note: It is encouraged to mount the NFS share within Ubuntu as running the NFS share from Windows can potentially create permissions issues that would not exist if done from a Linux environment.
Mounting NFS Shares in Windows
Note: This feature is not supported in Windows 8.
Note: This feature is not possible if running Windows 7 Professional as Microsoft removed the support for mounting NFS shares in this version of Windows. Mounting NFS shares works in all other versions of Windows 7 besides Windows Professional.
Enabling the NFS Client on a Windows 7 System
- Open the "Control Panel" from the Windows Start Menu.
Show/hide table
Illustration 73 g03861917 - Select "Programs".
Show/hide table
Illustration 74 g03861920 - Select "Programs and Features".
Show/hide table
Illustration 75 g03861934 - Select "Turn Windows features on or off" on the left-hand sidebar.
Show/hide table
Illustration 76 g03861942 - Scroll down to "Services for NFS" and check the plus sign to the left of it. Check both "Administrative Tools" and "Client for NFS". When both items have been selected, press "OK".
Show/hide table
Illustration 77 g03861943 - A progress bar may appear saying that "Please wait while Windows makes changes to features. This might take several minutes.". Wait for this window to finish. Once the change has applied, NFS mounting should now be enabled.
| |
| Illustration 72 | g03861913 |
Connecting to an NFS Share Drive
- Connect to the network with the NFS share. If the network has a static IP, configure the computer so the computer has a static IP that is valid on the network.
Show/hide table
Illustration 78 g03861944 - Open up Windows Explorer. To open Windows Explorer, click the folder icon on the taskbar. If a Windows Explorer session is already opened, right-click on the icon and select "Windows Explorer" to open up a new session.
Show/hide table
Illustration 79 g03861948 - Click "Computer" on the left-hand pane.
Show/hide table
Illustration 80 g03861951 - Select "Map network drive" at the top of the explorer window.
Show/hide table
Illustration 81 g03861960 - Select the drive letter to mount the share to and enter in the NFS mount credentials. Select "Reconnect at logon" if you want the NFS drive to connect every time the computer is booted. "Connect using different credentials" will not make a difference since NFS does not require user credentials and is based solely on whether the IP address is authorized to access the share.
Note: 192.168.28.198 is the address of the NFS server and "NasMountPoint" is the name of the shared folder to map.
- When finished entering in the information, select "Finish" to map the NFS share drive. The share drive will automatically open after the drive is mapped to Windows.
Installing the NFS Software
Note: This step only needs performed once and is only required if the NFS utilities have not yet been installed.
- Open the Ubuntu Software Center by typing the name in the Dash Home and selecting the program.
- In the search bar at the top right, type "nfs-common" and press ''Enter''.
Show/hide table
Illustration 83 g03861964 - Select "nfs-common" and click "Install".
Show/hide table
Illustration 84 g03861966 - When prompted, enter in the root password to install the software.
Show/hide table
Illustration 85 g03861967 - Wait until the software has finished. When the software has a "Remove" button, the software has completed the installation. Closing the Software Center is now safe to do.
| |
| Illustration 82 | g03861961 |
Mounting the NFS Share
- Connect to the network with the NFS share. If the network has a static IP, configure the computer so the computer has a static IP that is valid on the network.
- Open a terminal window by pressing "Ctrl + Alt + T".
Show/hide table
Illustration 86 g03861968 Show/hide table
Illustration 87 g03861969 - Type in the above command to mount the NFS share and press "Enter"" If the command returns to the command line with no errors, then the NFS share should now be mounted locally.
Note: "172.20.23.18" is the IP address of the NFS share, "mountpoint" is the name and mountpoint of the NFS share, and "/mnt" is the directory location to mount the NFS share locally on the computer.
Note: If a "wrong fs type" error shows up, then the NFS software is not installed. Refer to "Installing the NFS Software".
