| Parameter Name | No. | Description |
| auth_support | 1 | An 8-bit value that contains authentication types support flags for the LAN channel. |
| auth_enables | 2 | Five 8-bit values that contain authentication types enable flags for Callback, User, Operator, Administrator, and OEM privilege levels for the LAN channel. |
| ip | 3 | A string value that contains the IP address assigned to the LAN channel in dotted decimal notation (e.g. 192.168.0.15). |
| ip_source | 4 | A value that encodes the source of the assigned IP address. |
| mac | 5 | A string value that contains the MAC address assigned to the LAN channel as 6 hexadecimal byte values delimited by ‘:’ symbols (e.g. 00:A0:24:C6:18:2F). |
| subnet_mask | 6 | A string value that contains the subnet mask assigned to the LAN channel in dotted decimal notation (e.g. 255.255.255.0). |
| ipv4_hdr_param | 7 | Three 8-bit values that contain various IPv4 header parameters for sending RMCP packets:Time-to-liveIP header flags (bits [7:5])Precedence (bits [7;5]) and type of service (bits [4:1]) |
| pri_rmcp_port | 8 | A 16-bit value that contains the primary RMCP port number (the port used for regular RMCP communication). |
| sec_rmcp_port | 9 | A 16-bit value that contains the secondary RMCP port number. (the port used for secure RMCP communication). |
| arp_control | 10 | Two flags that control ARP behavior on the LAN channel: Enable responding to ARP requests Enable sending Gratuitous ARPs |
| arp_interval | 11 | The Gratuitous ARP interval in seconds, in fixed-point format (potentially including a fractional part). |
| dft_gw_ip | 12 | A string value that contains the IP address of the default gateway in dotted decimal notation. |
| dft_gw_mac | 13 | A string value that contains the MAC address of the default gateway as 6 hexadecimal byte values delimited by ‘::’ symbols. |
| backup_gw_ip | 14 | A string value that contains the IP address of the backup gateway in dotted decimal notation. |
| backup_gw_mac | 15 | A string value that contains the MAC address of the backup gateway as 6 hexadecimal byte values delimited by ‘::’ symbols. |
| community | 16 | A string value (up to 18 symbols) that is put into the “Community String” field in PET Traps. |
# Example
To get and show the whole LAN parameter table for channel 1:
```txt
# clia getlanconfig 1
Authentication Type Support: 0x15 ( None MD5 Straight Password/Key )
Authentication Type Enables: 0x00
User level: 0x15 ( None MD5 Straight Password/Key )
Operator level: 0x15 ( None MD5 Straight Password/Key )
Administrator level: 0x15 ( None MD5 Straight Password/Key )
OEM level: 0x00
IP Address: 172.16.2.203
IP Address Source: Static Address (Manually Configured) (01)
MAC Address: 90:91:91:91:91:91
Subnet Mask: 255.255.255.0
IPv4 Header Parameters: 0x40:0x40:0x10
Primary RMCP Port Number: 0x026f
Secondary RMCP Port Number: 0x0298
BMC-generated ARP Control: 02
Enable BMC-generated Gratuitous Response
Gratuitous ARP Interval: 2.0 seconds
Default Gateway Address: 0.0.0.0
Default Gateway MAC Address: N/A
Backup Gateway Address: 0.0.0.0
Backup MAC Address: N/A
Community String: "public"
Number of Destinations: 16
```
# IPMC
# Syntax
```txt
ipmc [-v] [<IPMB-address>]
ipmc board <N>
```
# Purpose
Shows information about the IPM controller at the specified address, or about all IPM controllers known to the Shelf Manager, if IPMB-address is omitted.
The following information is shown for the IPM controller in standard mode:
▶ IPMB address of the controller as two hexadecimal digits
▶ Entity ID and Entity Instance for the IPM controller
▶ Maximum possible FRU device ID for the IPM controller
▶ PICMG extension version. This version should be 2.0 for PICMG 3.0-compliant IPM controllers.
Information on current hot swap state, previous hot swap state, and cause of the last state change for FRU device 0 of the IPM controller (which represents the IPM controller itself) may also be accessed. The hot swap states M0-M7 are defined in the PICMG 3.0 specification as follows:
▶ M0 – Not Installed
▶ M1 – Inactive
▶ M2 – Activation Request
▶ M3 – Activation in Progress
▶ M4 – FRU Active
▶ M5 – Deactivation Request
▶ M6 – Deactivation in Progress
▶ M7 – Communication Lost
# Examples
To get information about the IPM controller at address 9C:
```txt
# clia ipmc 88
IPM Sentry Shelf Manager Command Line Interpreter
88: Entity: (0xd0, 0x0) Maximum FRU device ID: 0x08
PICMG Version 2.0
Hot Swap State: M4 (Active), Previous: M3 (Activation In Process), Last State Change Cause: Normal State Change (0x0)
#
```
To get verbose information about the IPM controller at address 9C:
```txt
# clia ipmc -v 88
IPM Sentry Shelf Manager Command Line Interpreter
88: Entity: (0xd0, 0x0) Maximum FRU device ID:
0x08
PICMG Version 2.0
Hot Swap State: M4 (Active), Previous: M3
(Activation In Process), Last State Change
Cause: Normal State Change (0x0)
Device ID: 0x00, Revision: 0, Firmware: 1.01,
IPMI ver 1.5
Manufacturer ID: 00315a (PICMG), Product ID:
0000, Auxiliary Rev: 01ac10ac
Device ID String: "IPM Sentry 6"
Global Initialization: 0x0, Power State
Notification: 0x0, Device Capabilities: 0x29
Controller provides Device SDRs
Supported features: 0x29
"Sensor Device" "FRU Inventory Device"
"IPMB Event Generator"
```
# Minfanlevel
# Syntax
minfanlevel [<level>]
# Purpose
Shows or sets the minimum fan level. Under normal conditions, the cooling management algorithm gradually decreases the level for the fans in the system while thermal conditions stay normal. However the cooling management algorithm will not decrease the fan level below the minimum level specified by the configuration parameter MIN\_FAN\_LEVEL, or by this command.
The default value for the minimum fan level is 1. Setting the minimum fan level to a higher value does not prevent the fan level from being set below that value via the command clia setfanlevel or via the ATCA command SetFanLevel submitted over RMCP. The minimum fan level affects only the automatic management of the fan level by the cooling management facility.
This command without parameters shows the current minimum fan level. This command with an integer parameter sets the minimum fan level to the value of the parameter.
# Example
\# clia minfanlevel 3
IPM Sentry Shelf Manager Command Line Interpreter
Minimal Fan Level is set to 3
\# clia minfanlevel
IPM Sentry Shelf Manager Command Line Interpreter
Minimal Fan Level is 3
# Sel
# Syntax
```txt
sel [-v] [ <IPMB-address> [<record-count> [starting-entry] ] ]
sel clear [ <IPMB-address> ]
sel info [ <IPMB-address> ]
<IPMB addr> can be replaced by the "board <N>" or "shm <N>" abbreviations
```
# Purpose
Shows the contents of the SEL on the specified IPM Controller (by default, at IPMB address 20h). The optional parameter <record-count> could be specified to indicate how many records from the record number <starting-entry> in the SEL are shown. The optional parameter <starting-entry> is the entry number of the first SEL record to print relative to the beginning of the SEL. Both <record-count> and <starting-entry> must be within the range from 1 to the total number of records in the SEL. The default value of the optional parameter <starting-entry> is 1. The <starting-entry> is independent of the RecordID field of the SEL record.
# Examples
```txt
# clia sel info
IPM Sentry Shelf Manager Command Line Interpreter
20: SEL version: 1.5
Number of log entries: 43
Free space: 15680 bytes
Last addition timestamp: Nov 19 17:12:47 2003
Last erase timestamp: Oct 31 23:59:59 2003
Supported operations: 0x0f
#
# clia sel 20 5
IPM Sentry Shelf Manager Command Line Interpreter
0x0027: Event: at Nov 19 17:12:42 2003;
from:(0x9c,0,0); sensor:(0xf0,0);
event:0x6f(asserted): HotSwap: FRU 0 M4->M6,
Cause=0x1
```
```asm
0x0028: Event: at Nov 19 17:12:42 2003;
from:(0x9c,0,0); sensor:(0xf0,0);
event:0x6f(asserted): HotSwap: FRU 0 M6->M1,
Cause=0x0
0x0029: Event: at Nov 19 17:12:46 2003;
from:(0x9c,0,0); sensor:(0xf0,0);
event:0x6f(asserted): HotSwap: FRU 0 M1->M2,
Cause=0x2
0x002A: Event: at Nov 19 17:12:46 2003;
from:(0x9c,0,0); sensor:(0xf0,0);
event:0x6f(asserted): HotSwap: FRU 0 M2->M3,
Cause=0x1
0x002B: Event: at Nov 19 17:12:47 2003;
from:(0x9c,0,0); sensor:(0xf0,0);
event:0x6f(asserted): HotSwap: FRU 0 M3->M4,
Cause=0x0
#
```
```txt
# clia sel b4 5
IPM Sentry Shelf Manager Command Line Interpreter
0x00A4: Event: at Nov 19 01:24:25 2003;
from:(0x20,0,0); sensor:(0x02,4);
event:0x1(asserted): "Lower Non-Critical",
Threshold: 0xb3, Reading: 0xb3
0x00B8: Event: at Nov 19 00:04:11 2003;
from:(0x20,0,0); sensor:(0x02,4);
event:0x1(asserted): "Lower Non-Critical",
Threshold: 0xb3, Reading: 0xb3
0x00CC: Event: at Nov 19 00:36:32 2003;
from:(0x20,0,0); sensor:(0x02,7);
event:0x1(asserted): "Lower Non-Critical",
Threshold: 0xae, Reading: 0x94
0x00E0: Event: at Nov 19 00:36:32 2003;
from:(0x20,0,0); sensor:(0x02,7);
event:0x1(asserted): "Lower Critical",
Threshold: 0xac, Reading: 0x94
0x00F4: Event: at Nov 19 00:02:37 2003;
from:(0x20,0,0); sensor:(0x01,2);
event:0x1(asserted): "Upper Critical",
Threshold: 0x13, Reading: 0x1c
```
# Sensordata
# Syntax
```txt
sensordata [ <IPMB-address> [<sensor-name> |
[<lun>:]<sensor-number> ] ]
sensordata [-v] board <N> [<sensor-name> |
[<lun>:]<sensor-number> ] ]
sensordata [-v] shm <N> [<sensor-name> |
[<lun>:]<sensor-number> ] ]
```
# Purpose
Shows the actual value of the specified sensor(s) for a threshold-based sensor, or the currently asserted states of a discrete sensor. The target sensor is selected by its IPM controller's IPMB address and by sensor number or by sensor name (device ID string from the sensor SDR, enclosed in double quotes). If neither sensor name nor sensor number is specified, values of all sensors on the specified IPM controller are shown. If no parameters are specified, values of all known sensors are shown.
This command allows you to qualify the sensor number with the Logical Unit Number (LUN) if the target controller supports sensors on multiple LUNs. If the LUN is omitted, information about sensors with the specified sensor number on all LUNs is shown. <Lun> can take the value 0, 1, or 3 (LUN 2 is reserved.)
# Examples
To get sensor data values for a discrete (Hot Swap) sensor (#0) on IPM controller 9C.:
```txt
# clia sensordata 9c 0
IPM Sentry Shelf Manager Command Line Interpreter
9c: LUN: 0, Sensor # 0 ("FRU 0 HOT_SWAP")
Type: Discrete (0x6f), "Hot Swap" (0xf0)
Status: 0xc0
All event messages enabled from this
sensor
Sensor scanning enabled
Initial update completed
Sensor reading: 0x00
Current State Mask 0x0010
```
# Setfanlevel
# Syntax
```txt
setfanlevel <IPMB-address> <FRU-device-ID>
<level>
```
# Purpose
Sets the new level for the fan controlled by the FRU specified in the command parameters.
# Example
Set fan level for the fan residing at FRU #2 at IPMB address 0x20 to 5.
```txt
# clia setfanlevel 20 3 5
IPM Sentry Shelf Manager Command Line Interpreter
20: FRU # 3 Set Fan Level to: 5
#
```
# setlanconfig
# Syntax
```txt
setlanconfig <channel> <parameter-name>
<additional-parameters> |
setlanconfig <channel> <parameter-number>
<additional-parameters>
```
# Purpose
Sets the value of the specified LAN configuration parameter on the specified channel. The channel number, the configuration parameter name or number, and the parameter value should be explicitly specified.
The following table lists names and numbers of LAN configuration parameters supported by the "setlanconfig" command:
# Shelf
# Syntax
```xml
shelf <subcommand>
```
The following sub-commands are supported.
```txt
address_table
cooling_state
fans_state
power_distribution
power_management
pci_connectivity
ha_connectivity
h110_connectivity
point-to-point_connectivity
MaxCurrent [feed] <Amps>
MinVoltage [feed] <Volts>
Activation <addr> <fru_id> 1|0
Deactivation <addr> <fru_id> 1|0
BDSelGrounded <slot number> 1|0
1 means Enabled, 0 means Disabled
PwrCapability <addr> <fru_id> <Watts>
PwrDelay <addr> <fru_id> <10ths_of_second>
Allowance <seconds>
PwrReorder <addr1> <fru_id1> before|after <addr2>
<fru_id2>
info_refresh
info_force_update
```
# Purpose
Shows key Shelf FRU information plus selected current operating data for the shelf, and allows modifying some fields in the Shelf FRU information. The type of the information this command shows or modifies is specified in the command parameter.
The following subsection describes the syntax of the shelf command for different command applications.
# Displaying Shelf FRU Information
# Syntax
```txt
shelf [cooling_state | fans_state | address_table | power_distribution | power_management | pci_connectivity | ha_connectivity | h110_connectivity | point-to-point_connectivity]
```
# Purpose
This syntax of the command shelf shows key Shelf FRU information plus selected current operating data for the shelf. The type of the information this command shows is specified in the command parameter. The following table lists the parameters supported by the shelf command:
| Command Parameter | Provided Information |
| cooling_state (abbreviated as cs) | Shows the current cooling state of the shelf:Normal – all temperature sensors show normal operating temperature.Minor Alert – at least one temperature sensor is in minor alert state. None of the sensors is in major or critical alert state.Major Alert – at least one temperature sensor is in major alert state. None of the sensors is in critical alert state.Critical Alert – at least one temperature sensor is in critical alert state. |
| fans_state (abbreviated as fs) | Shows the current state of the fan tachometers in the shelf:Normal – all fan tachometer sensors show normal operating speed.Minor Alert – at least one fan tachometer sensor is in minor alert state. None of the sensors is in major or critical alert state.Major Alert – at least one fan tachometer sensor is in major alert state. None of the sensors is in critical alert state.Critical Alert – at least one fan tachometer sensor is in critical alert state. |
| address_table (abbreviated to at) | Shows the Address Table record in the Shelf FRU Info. The following information is provided:• Shelf Address (shown according to its type)• List of address table entries, showing Hardware Address, Site Type, and Site Number for each of them. |
| power_distribution (abbreviated as pd) | The following information is provided for each of the power feeds (mostly from the Shelf Power Distribution record of the Shelf FRU Information):• Maximum External Available Current• Maximum Internal Current• Minimum Expected Operating Voltage• Actual Power Available• Currently Used Power• List of FRUs connected to the feed, showing Hardware Address and FRU Device ID for each of them |
| power_management (abbreviated as pm) | The Shelf Power Management record in the Shelf FRU Info. This record contains a list of FRU Power Descriptors. For each descriptor the following information is provided:• Hardware Address• FRU Device ID• Maximum FRU Power Capability• Shelf Manager Controlled Activation• Delay Before Next Power On |
| pci_connectivity (abbreviated as pcic) | The Shelf PCI Connectivity record in the Shelf FRU Info. The following information is provided:• PCI Slot Descriptor• IDSEL Connection• Segment ID• Extended PCI Slot Descriptor• Geographic Address• Interface Number• System Slot Capable |
| ha_connectivity (abbreviated as ha) | The Shelf HAConnectivity record in the Shelf FRU Info. The following information is provided:• Radial Connectivity Support |
| h110_connectivity (abbreviated as h110c) | The Shelf H110 Connectivity record in the Shelf FRU Info. The following information is provided:• Geographic Address• Segment ID |
| point-to-point_connectivity (abbreviated as ppc) | The Shelf Point-to-Point Connectivity record in the Shelf FRU Info. The following information is provided:• Channel Type• Channel Count• Slot/ Hw Address• Channel Descriptor |
# Example
To get a shelf fan tachometer status (verbose).
```txt
# clia shelf -v fans_state
IPM Sentry Shelf Manager Command Line Interpreter
Fans state: "Major Alert"
Sensor(s) at this state: (0x7e,10) (0x7e,11)
(0x7e,12) (0x7e,13) (0x7e,14) (0x7e,15)
(0x7e,16) (0x7e,17)
```
# shmstatus
# Syntax
shmstatus
# Purpose
Returns the Shelf Manager status in redundant active or backup configurations. In verbose mode, this command reports more detailed information including Shelf FRU Info status, RMCP interface status, and state of the backup Shelf Manager (if the Shelf Manager being queried is the active one). The ready for operation flag is a parameter that shows as Yes:
▶ on the active Shelf Manager if it finds valid Shelf FRU Info and successfully initializes its RMCP interface.
▶ on the backup Shelf Manager if it successfully received the redundancy state information from the active Shelf Manager.
# Example
\# clia shmstatus -v
IPM Sentry Shelf Manager Command Line Interpreter
Shelf Manager status: "Active"
# ShowUnhealthy
# Syntax
showunhealthy
# Purpose
Shows the list of FRUs that appear to have a problem. In the PICMG 3.0 context, this list includes FRUs for which the cause of last hot swap state change is Communication Lost, Communication lost due to local failure, or Unexpected deactivation. In CompactPCI shelves, this command checks Board, Fan Tray, and Power Supply healthy status bits as well.
For each FRU, the following information are shown:
▶ IPMB address and FRU device ID
▶ Current hot swap state
▶ Previous hot swap state
▶ Cause of the last state change
# Example
To show the list of unhealthy components in the system:
\# clia showunhealthy
IPM Sentry Shelf Manager Command Line Interpreter
There are no unhealthy components in the shelf.
# switchover
# Syntax
switchover
# Purpose
Initiates switchover of redundant Shelf Manager instances. This command can be executed on either the active or the backup instance of the Shelf Manager.
# Examples
To initiate the switchover from either the active or backup instance:
\# clia switchover
This Shelf Manager is now active, but is shutting down to trigger a switchover.
\#
# Terminate
# Syntax
terminate [-reboot]
# Purpose
Terminates the Shelf Manager. This command also causes the ShMM to unconditionally reboot if the option -reboot is specified.
If the option -reboot is omitted, this command terminates the Shelf Manager without rebooting the ShMM, if this variant is supported by the ShMM on which the command is executed. Currently, no-reboot variant of the command is supported on the aCMM-2000.
If the ShMM does not support terminating the Shelf Manager without reboot, the ShMM is rebooted.
# Examples
To terminate the Shelf Manager on aCMM-2000 without rebooting the ShMM:
\# clia terminate
Terminating the Shelf Manager.
\#
# version
# Syntax
version
# Purpose
Shows the version information for the Shelf Manager software. This command can also be issued on the backup Shelf Manager.
# Example
\# clia version
IPM Sentry Shelf Manager Command Line Interpreter
IPM Sentry Shelf Manager ver. 2.3-pre5
IPM Sentry is a trademark of Pigeon Point Systems.
Copyright (c) 2002-2006 Pigeon Point Systems
Build date/time: January 12 2006 16:39:37
All rights reserved #
# 4.3 Web Interface
# IPM Sentry Web Interface
The web interface can be used to communicate with intelligent shelf management controllers, boards, and with the Shelf Manager itself remotely over the network via a web browser. The web interface is based on the Command Line Interface (CLI) and is essentially a front-end to the CLI.
In redundant configurations, the external IP address is always maintained by the active Shelf Manager and is switched over to the backup Shelf Manager when the general switchover takes place. Therefore, the client always communicates to the active Shelf Manager via the web interface in redundant configurations.
# Starting the Web Interface
Before using the web interface, check if the module meets the following requirements:
▶ one of the ethernet interfaces should be configured and up
▶ the web server boa must be running
▶ the Shelf Manager software (shelfman) must be running
To use the Web interface, launch any web browser (Internet Explorer, or Netscape), then point it to URL http://<Shelf-Manager-IP-Address>. For redundant Shelf Manager instances in a single shelf, the IP address should be the one exported outside the shelf and used for RMCP access to the Shelf Manager (instances). For example, if the Shelf Manager IP address is 192.168.1.204, the URL is http://192.168.1.204. The main page shows up in the browser and provides a menu.
To fill a field of a web form with a parameter value that includes the space symbol, you must enclose the value in backslashed quotes. For example, sensor Local Temp should be entered as \Local Temp\ in the field "Sensor Name or LUN:Sensor #:" on the page Set Sensor Hysteresis.
The main page contains a list of links to other pages, each of which corresponds to one of the commands available through the web interface. These commands and the corresponding pages are described in detail in subsequent sections. The documentation relating to the command line interface can also be very helpful as the web interface provides the same functionality via a web browser.
# Appendix A
# A.1 Overview of Intelligent Platform Management in ATCA
The IPM Sentry products are the first Intelligent Platform Management building blocks designed from the ground up for modular platforms like AdvancedTCA, wherein there is a strong focus on a dynamic population of Field Replaceable Units (FRUs) and maximum service availability. The Intelligent Platform Management Interface (IPMI) specification provides a solid foundation for the management of such platforms but requires significant extension to support them well.
Figure A-1: IPMI in ATCA Overview
The illustration above shows the logical elements of an example AdvancedTCA shelf, identified in terms of ATCA specification and potential sites for incorporation of IPM Sentry products.
# A.2 Features of IPM Sentry Shelf Manager
Executes on the ShMM, a compact SODIMM form-factor module, installed on a suitable carrier board for the shelf.
▶ Conforms to the AdvancedTCA specification.
Monitors activities within the shelf via the ATCA-specified dual redundant Intelligent Platform Management Bus (IPMB).
- Accepts and logs events posted by any intelligent FRU in the shelf (reflecting exceptions in temperatures, voltages, etc.); posts alerts outside the shelf based on configurable IPMI Platform Event Filters.
▶ Supports hot swapping of Field Replaceable Units (FRUs), while maintaining full management visibility.
▶ Interfaces to standard “Telco Alarm” infrastructures, via ShMM carrier-implemented dry contact relays.
▶ Supports redundant Shelf Manager instances for high availability.
▶ Integrates a watchdog timer, which resets the ShMM if not periodically strobed; such resets automatically trigger a switchover to the backup ShMM, if configured.
▶ Includes battery-backed real-time clock for time-stamping events.
- Implements a rich set of shelf-external interfaces accessible over Ethernet, including Remote Management Control Protocol (RMCP, required by AdvancedTCA), command line, web browser, Simple Network Management Protocol (SNMP).
# A.3 Support for Dual Redundant Operation
The IPM Sentry Shelf Manager can be configured with active/backup instances to maximize availability. Figure A-2 shows how both instances are accessible to the System Manager, with only the active instance interacting at any given time. Similarly, only the active instance communicates over IPMB-0 with the IPM Controller population in the shelf. The two instances communicate over TCP/IP, with the active instance posting incremental state updates to the backup. As a result, the backup can quickly step into the active role if necessary.
Figure A-2: IPM Sentry Shelf Manager Redundancy Support
Three cross-connected signals between the two Shelf Manager instances enhance their coordination:
▶ Presence: each Shelf Manager instance knows whether the other instance is present in the shelf.
▶ Health: each instance knows whether the other instance considers itself “healthy.”
▶ Switchover: the backup instance can force a switchover if necessary.
# A.4 IPM Sentry ShMM Shelf Management Mezzanines
The IPM Sentry Shelf Manager executes on the ShMM a small (67.60 mm x 50.80 mm) Shelf Management Mezzanine that conforms to the Small Outline Dual Inline Memory Module (SODIMM) specification.
| Feature | ShMM-500 |
| CPU | AMD Alchemy Au1550 |
| Processor core(s) | 333 Mhz MIPS-32 |
| SDRAM | 128 Mbytes |
| Flash | 64 Mbytes |
| Ethernet | Dual 10/100 Mbit |
| Serial | Two, one with modem controls |
| Universal Serial Bus (USB) | Host and device ports |
| Duplex IPMB-0 | Yes |
| Real-time clock, optionally battery backed on ShMM carrier | Yes |
| General Purpose I/O signals | Nine |
| Shelf Manager redundancy and hot swap interface, with on-board CPLD assist | Yes |
| High speed interface(s) to on-carrier devices | Multiple ports supporting either SPI or SMBus |
| JTAG interface for processor debug and flash programming | Yes |
This page intentionally left blank.
# Warranty Policy
Thank you for choosing ADLINK. To understand your rights and enjoy all the after-sales services we offer, please read the following carefully.
1. Before using ADLINK's products please read the user manual and follow the instructions exactly. When sending in damaged products for repair, please attach an RMA application form which can be downloaded from: http://rma.adlinktech.com/policy/.
2. All ADLINK products come with a limited two-year guarantee, one year for products bought in China:
The warranty period starts on the day the product is shipped from ADLINK's factory.
▶ Peripherals and third-party products not manufactured by ADLINK will be covered by the original manufacturers' warranty.
For products containing storage devices (hard drives, flash cards, etc.), please back up your data before sending them for repair. ADLINK is not responsible for loss of data.
▶ Please ensure the use of properly licensed software with our systems. ADLINK does not condone the use of pirated software and will not service systems using such software. ADLINK will not be held legally responsible for products shipped with unlicensed software installed by the user.
For general repairs, please do not include peripheral accessories. If peripherals need to be included, be certain to specify which items you sent on the RMA Request & Confirmation Form. ADLINK is not responsible for items not listed on the RMA Request & Confirmation Form.
3. Our repair service is not covered by ADLINK's guarantee in the following situations:
▶ Damage caused by not following instructions in the User's Manual.
▶ Damage caused by carelessness on the user's part during product transportation.
▶ Damage caused by fire, earthquakes, floods, lightening, pollution, other acts of God, and/or incorrect usage of voltage transformers.
▶ Damage caused by unsuitable storage environments (i.e. high temperatures, high humidity, or volatile chemicals).
▶ Damage caused by leakage of battery fluid during or after change of batteries by customer/user.
▶ Damage from improper repair by unauthorized ADLINK technicians.
▶ Products with altered and/or damaged serial numbers are not entitled to our service.
▶ This warranty is not transferable or extendible.
▶ Other categories not protected under our warranty.
4. Customers are responsible for shipping costs to transport damaged products to ADLINK.
If you have any further questions, please email our FAE staff: service@adlinktech.com.
[🔗 Link to the original document](.acmm-2000-50-1g003-1000-201/acmm-2000-50-1g003-1000-201.pdf)