Compaq 112726-001 - ProLiant - 6500 Guide de démarrage rapide

,QWHJUDWLRQ1RWH

September 1999

0096-0699-A

Prepared byECG Technology

Communications Group

Compaq Computer Corporation

Contents

Clustering Overview....................3

Clusters Defined........................3

Causes of Downtime..................3

Cost ofDowntime.......................4

Benefits of Clustering.................4

Summary....................................4

ProLiant Cluster for NetWare

4.2 Overview.................................5

Features and Benefits of the

ProLiant Cluster for NetWare

4.2..............................................5

Novell’s High-Reliability

Solution......................................5

The Failover Process.................6

Hardware Requirements............8

CompaqProLiant Servers..........8

CompaqStorageWorks

RAID Array 4000 Storage

System.......................................9

ClusterInterconnects...............12

Software Components...............13

Novell Software........................13

CompaqSoftware....................13

Planning NovellHigh

AvailabilityServer

Installation..................................15

Verification of NHAS

Installation................................15

ProLiant Cluster for NetWare

4.2 Administration.....................18

Increasing Availability...............18

IP and Applications Failover.....18

Management............................26

Technical FAQs.........................28

'HSOR\LQJWKH3UR/LDQW&OXVWHU

IRU1HW:DUH

Abstract:Compaq is renowned in the Enterprise market with its industry-

leading, highly available, fault-tolerant servers. Compaq servers and storage

deliver on this reputation byoffering the highest level of reliability and

uptime with features suchas:

•Industrystandard PCI Hot Plug and internal hot-plugstorage

•Redundanthot-plug fans, power supplies, and NICs

•Automatic Server Recovery-2 (ASR-2)

•ECC protected memory

•Integrated Management Display (IMD)

•Integrated Remote Console (IRC)

•Compaq SmartStart and Compaq Insight Manager

The Compaq ProLiant Cluster for NetWare 4.2 is designed to help

customers reduce the risk and costs of downtime due to hardware or

softwarefailures. Benefits include:

•Automatic failover protection - In the event of a failure on one server,

the remaining server maintains availabilityof network data and

resources.

•Active servers - Users can nowcluster two active NetWare 4.11 or

NetWare 4.2 servers onthe network, providingfailover support and

significant cost savings, since purchasing a dedicated server for failover

is no longer necessary.

•Shared storage -Support for shared storage devices allows customers to

reduce overall management costs bycentralizing administration and

back-up. Shared storage also allowsmore efficient use of storage space

byeliminating the need to maintain duplicate files on different servers.

•No single point offailure – The newCompaq StorageWorks RAID

Array4000 storage systemprovides redundant fibre channel loops for

No Single Point of Failure configurations.

The ProLiant Cluster for NetWare 4.2 provides the highest levels ofsystem

and application availabilityfor customers with high systemuptime

requirements for NetWare 4.x environments. These levels are necessaryto

meet the requirements of demanding business-critical environments. This

Integration Note details the configuration options and server requirements,

provides insight into the administration, and describes some ofthe features

available with the ProLiant Cluster for NetWare 4.2.

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

Notice

The information in this publication is subject to change without notice and is provided “AS IS” WITHOUT

WARRANTY OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OF THIS

INFORMATION REMAINS WITH RECIPIENT. IN NO EVENT SHALL COMPAQ BE LIABLE FOR

ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL, PUNITIVE OR OTHER DAMAGES

WHATSOEVER (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS

PROFITS, BUSINESS INTERRUPTION OR LOSS OF BUSINESS INFORMATION), EVEN IF

COMPAQ HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The limited warranties for Compaq products are exclusively set forth in the documentation accompanying

such products. Nothing herein should be construed as constituting a further or additional warranty.

This publication does not constitute an endorsement of the product or products that were tested. The

configuration or configurations tested or described may or may not be the only available solution. This test

is not a determination or product quality or correctness, nor does it ensure compliance with any federal

state or local requirements.

Product names mentioned herein may be trademarks and/or registered trademarks of their respective

companies.

Compaq, Contura, Deskpro, Fastart, Compaq Insight Manager, LTE, PageMarq, Systempro, Systempro/LT,

ProLiant, TwinTray, ROMPaq, LicensePaq, QVision, SLT, ProLinea, SmartStart, NetFlex, DirectPlus,

QuickFind, RemotePaq, BackPaq, TechPaq, SpeedPaq, QuickBack, PaqFax, Presario, SilentCool,

CompaqCare (design), Aero, SmartStation, MiniStation, and PaqRap, registered United States Patent and

Trademark Office.

Netelligent, Armada, Cruiser, Concerto, QuickChoice, ProSignia, Systempro/XL, Net1, LTE Elite,

Vocalyst, PageMate, SoftPaq, FirstPaq, SolutionPaq, EasyPoint, EZ Help, MaxLight, MultiLock,

QuickBlank, QuickLock, UltraView, Innovate logo, Wonder Tools logo in black/white and color, and

Compaq PC Card Solution logo are trademarks and/or service marks of Compaq Computer Corporation.

Microsoft, Windows, Windows NT, Windows NT Server and Workstation, Microsoft SQL Server for

Windows NT are trademarks and/or registered trademarks of Microsoft Corporation.

NetWare and Novell are registered trademarks and intraNetWare, NDS, Novell Directory Services, and

High Availability Server (NHAS) are trademarks of Novell, Inc.

Pentium is a registered trademark of Intel Corporation.

Deploying the ProLiant Cluster for NetWare 4.2

Integration Note prepared by ECG Technology Communications Group

Second Edition (June 1999)

Document Number 0096-0699-A

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

Clustering Overview

The computer industry has been using a wide range of solutions to reduce system downtime for

years. Many of these solutions have been both expensive and difficult to setup and maintain.

Historically, only mission-critical applications, such as those controlling stock exchange trading

floors and aerospace missions, were deemed important enough to justify proprietary clustering

solutions.

However, as the presence of computer systems in day-to-day business operations has increased,

the amount of acceptable downtime has decreased. Today, a new class of applications exists;

business-critical applications key to business success but not significant enough to justify the high

price tag of a proprietary clustering solution. More and more applications are becoming business-

critical. Computer applications are becoming more widely deployed and their failure causes

immediate lost revenue, decreased productivity, and, potentially, dissatisfied customers.

Poised to meet the increased demands, clustering technology is entering mainstream industry-

standard computing. As a result, new clustering solutions, using industry-standard hardware and

software, provide key clustering features at a lower price than proprietary clustering systems.

Clusters Defined

Traditionally, clustering is the integration of software and hardware that enables a set of loosely

coupled servers and storage to operate as a single system, presenting a single entity to clients. As

a cluster, the group of servers and storage offers a level of availability greatly exceeding the

reliability of a standalone server. This translates into increased performance and greater data

availability for end users.

The ProLiant Cluster for NetWare 4.2 extends the definition by providing the same level of

reliability while maintaining distinct network entities for each server. By defining distinct server

identities, tasks and users may be distributed easily between the distinct servers. With the focus

for clustered systems being reliability, the ProLiant Cluster for NetWare 4.2 delivers again with

automatic failover of all network resources and responsibilities in the event of a failure. Should

one server in the cluster lose access to the shared storage and network, the other server assumes

the responsibilities of the downed server.

Causes of Downtime

Computer downtime is the period of time that a computer system cannot meet the requests of its

users. The following are the leading causes of downtime:

•Planned service - In a cluster, a single server can be taken offline, while the other server takes

on the workload of the downed server. This allows planned service to occur with only

minimal interruption to the overall system operation.

•Software failures - Because clustering provides a mechanism to automatically fail over

processes when a discernible software failure occurs, the overall system operation can

continue with only minimal interruption.

•Hardware failures - If it is determined that a hardware failure will result in system downtime,

the cluster will fail over processes from one node to another, allowing the overall system

operation to continue with little interruption.

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

Cost of Downtime

The driving force behind the high-availability systems has been the elimination of costs

associated with downtime. The cost of downtime formula must include several factors. Among

these are:

•Productivity loss

•IM costs

•Lost transactions

•Customer or end user dissatisfaction

Each factor is weighted differently, depending on the critical nature of each factor as it pertains to

your business and to your specific application systems. For example, downtime during peak hours

of a point-of-sale operation would have a much greater impact on customer satisfaction issues

than downtime in an end-of-day email server backup operation. To understand the true cost of

computer downtime in your business environment, you must examine the impact and contribution

to increased costs of each factor as it applies to your business-critical applications.

Benefits of Clustering

With the causes enumerated and the costs understood, it is clear that the Novell High Availability

Server can eliminate your concerns and ease your tightening networking budget through

•Availability - Simply defined, availability is the measure of how well a computer system can

continuously deliver services to clients. This is dependent upon the system’s ability to

prevent or recover from failures or faults.

•Scalability - Clustering for scalability means increasing performance beyond that of a single

computer node by adding more nodes to the cluster. Performance scalability across cluster

nodes is difficult to achieve and requires not only scalable hardware, but also scalable

software, for example, a parallel database.

•Lower Total Cost of Ownership - By reducing downtime, you can eliminate both the high

costs of administrative support and, at the same time, the lost revenue caused by downtime

and customer dissatisfaction.

Summary

In general, clusters can provide both high availability and scalability for business-critical

applications. In today’s market, experts estimate that approximately 80-90% of clusters are used

to take advantage of the increase in server availability created by clusters.

The use of clusters to reduce computer system downtime has a direct impact on a company’s

revenue and the MIS department budget. The impact depends on your calculated costs of

downtime. In most cases, the cost of installing and maintaining a cluster are likely to be offset by

the reduction in downtime costs, and, as businesses’ reliance on computer systems intensifies, the

cost of downtime is likely to increase.

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

ProLiant Cluster for NetWare 4.2 Overview

Novell products are designed to support incremental network growth, and the ProLiant Cluster for

NetWare 4.2 continues this philosophy with its solid NetWare environment designed to provide

both industrial-strength availability and scalability at the hardware, operating system, and

application levels.

By deploying the ProLiant Cluster for NetWare 4.2, your company can reduce downtime and

operating costs. At the same time, your network can benefit from the latest Internet/intranet and

file and print services in a robust network environment for deploying general-purpose

applications.

Features and Benefits of the ProLiant Cluster for

NetWare 4.2

The ProLiant Cluster for NetWare 4.2 provides these features and benefits:

•Two node active-active cluster configuration

•Automatic failover and failback

•Protection against both hardware and software failures

•Failure detection over dedicated and/or non-dedicated links

•Support for any ODI™, IP compliant network interface card

•Support for Symmetric Multi-Processing (SMP)

•Industry-standard, non-proprietary hardware requirements

•High availability and lower total cost of ownership through:

−Support for Fiber Channel Arbitrated Loop (FCAL)

−Novell Directory Services (NDS) support

−NetWare Loadable Module™ (NLM™)-based installation

−Dynamic user licensing

−Application fallback via IP

Novell’s High-Reliability Solution

The ProLiant Cluster for NetWare 4.2, featuring Novell High Availability Server (NHAS),

increases network reliability through the use of two NetWare 4.11 or NetWare 4.2 servers with a

shared disk subsystem. By pairing two independent servers in an active-active configuration, the

NHAS allows each server to access and mount the other server's data if there is a failure on a

server in the cluster.

Each server monitors the status of the other server over three redundant lines of communication:

•NetWare Link – each server can monitor the presence of the other across the local network.

•Disk Link – NHAS uses quorum arbitration to allow each server to monitor the other server’s

shared storage connection and prevent concurrent access to the same data.

•Optional Dedicated Link – by creating a dedicated link between the two servers, each server

can monitor the presence of the other more reliably, eliminating false failures caused by

network traffic or prolonged disk inactivity.

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

The Failover Process

Costandby State

During normal operation, shown in Figure 1, each server node in the ProLiant Cluster for

NetWare 4.2 operates as if it were a completely independent entity on the network. Server A and

Server B are allocated their own dedicated volumes on the Compaq RAID Array 4000 shared

storage. NHAS controls access for the shared storage and prevents one server from accessing the

other server’s volume. This controlling mechanism is vital to the operation of the cluster, since it

prevents a split-brain scenario, wherein two servers may try to access the same data

simultaneously; obviously, this could result in data corruption. In the given configuration, each

server is operating in the costandby state, that is, independently but waiting for the other server to

fail.

Compaq RAID Array 4000

Volume 1

Accessed by

Node A only

Volume 2

Accessed by

Node B only

Server

Node A

Server

Node B

Local Area Network

Fibre Channel Storage Hub

Data

Inter-server Monitoring

Data and Monitoring

Network Clients

Dedicated Interserver Direct Link

Fibre Channel Arbitrated Loop

NetWare

Interconnects

Server A

Volume A

Logical Connections

Server B

Volume B

Figure 1. ProLiant Cluster for NetWare 4.2 Costandby State

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

Failover and Recovery States

Figure 2 illustrates the failover and recovery process. If no communication between the servers

can be established across any of the three lines of communication, the server that has lost

connections to the network and storage will enter failover state. At the same time, the other node,

in this case, Server B, will enter the recovery state (Figure 2A). Upon entering the recovery state,

Server B assumes responsibility for Server A volumes and clients (Figure 2B). Security and

licensing are maintained by transferring NDS rights to the surviving server. Total failover time

corresponds to the time necessary to detect the failure and complete the failover process. During a

failover, the remaining server must mount the new volumes, launch any active server-based

applications that were running on the failed device, and transfer security and license information.

NHAS also allows manual failover of shared volumes at any time by pressing F at the NHAS

console. By forcing a failover, you can remove a server from the network for scheduled

maintenance without interrupting access to that server’s volumes.

Disabled Server

Server

Node B

Local Area Network

Fibre Channel Storage Hub

Data

Inter-server Monitoring

Data and Monitoring

Network Clients

Dedicated Interserver Direct Link

Fibre Channel Arbitrated Loop

NetWare

Interconnects

Compaq RAID Array 4000

Volume 1

Accessed by

Node B only

Volume 2

Accessed by

Node B only

Server A

Volume A

Logical Connections

Server B

Volume B

A. Node B Entering Recovery State B. Node B Assuming

Responsibility for

Node A’s Volumes

Figure 2. Failover and Recovery

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

Hardware Requirements

As shown in Figure 3, a typical ProLiant Cluster for NetWare 4.2 hardware configuration consists

of two ProLiant servers with Fibre Channel Host Controllers, a Fibre Channel Storage Hub, and

a Compaq RAID Array 4000 storage system with a Fibre Channel Array Controller.

Fibre Channel Array

Fibre Channel

Storage Hub 7

ProLiant Server

Fibre Cable

Fibre Channel Array Controller

Fibre Channel Host Controller

Network Interface Controller

(Dedicated Interconnect)

Gigabit Interface Converter

Interconnect Cable

Figure 3. Typical ProLiant Cluster for NetWare 4.2 Configuration

Whether your intention is to upgrade an existing server or purchase a new Compaq server, the

following minimum hardware requirements must be met for a ProLiant Cluster for NetWare 4.2

configuration.

Compaq ProLiant Servers

The primary components of a cluster are the servers. The initial release of the ProLiant Cluster

for NetWare 4.2 supports a two-node cluster, where each node is a server. The key software

component that imparts high availability to the cluster servers is Novell High Availability Server

(NHAS). Throughout the development of the NHAS software, Compaq has been a partner with

Novell to ensure that Compaq ProLiant servers are the ideal platforms for NHAS. Compaq has

logged countless hours testing ProLiant clusters, which have successfully passed Novell’s NHAS

Certification test suite. This rigorous suite of tests ensures that the cluster works as an integrated

unit, not just as a collection of individual components.

CompaqRAIDArray 4000

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

The following Compaq ProLiant servers have been certified for use with both NHAS and Fibre

Channel:

•Compaq ProLiant 1850R – Intel Pentium II

•Compaq ProLiant 3000 – Intel Pentium II

•Compaq ProLiant 5500R – Intel Pentium II Xeon

•Compaq ProLiant 6400R – Intel Pentium III Xeon

•Compaq ProLiant 6500 – Intel Pentium II Xeon

•Compaq ProLiant 7000 – Intel Pentium II Xeon

NOTE: Check the Compaq website at http://www.compaq.com to obtain an up-to-date list of cluster-

certified servers. Each server in the cluster must have one local hard drive. In addition, Compaq

recommends 256MB of RAM in each server.

In addition to the increased availability of clustering, Compaq ProLiant servers include many

reliability features that provide a solid foundation for effective clustered server solutions. They

offer excellent reliability through redundant systems, hot-pluggable components, and server

health and monitoring. The high-availability features of ProLiant servers are a critical foundation

of an effective ProLiant Cluster for NetWare 4.2 deployment and the cornerstone of mission-

critical computing.

Compaq StorageWorks RAID Array 4000 Storage

System

The ProLiant Cluster for NetWare 4.2 is based on a cluster architecture known as Shared Storage

Clustering, in which clustered servers share access to a common set of hard drives. Novell High

Availability Server requires all shared data to be stored in an external storage system to

implement the necessary quorum arbitration.

The Compaq RAID Array 4000 storage system brings significant advantages to clustering,

including:

•100MB/s throughput

•Server-to-hub and hub-to-storage distances of up to 500 meters for short-wave and 10

kilometers for long-wave (per Fibre Channel link, 25 kilometers cumulative for all

links)

•Increased connectivity and ease of use

•Reliable transmission of data in shared configurations

•Hot-pluggable drives

•Hot-pluggable power supply (in redundant power supply configurations)

•Manageability through Compaq Insight Manager

By using standard short-wave Fibre Channel cabling, the Compaq RAID Array 4000 can be

placed up to 500 meters from the Fibre Channel Storage Hub, and the Fibre Channel Storage Hub

can be placed up to 500 meters from the server. By using long-wave Fibre Channel cabling,

'HSOR\LQJWKH3UR/LDQW&OXVWHUIRU1HW:DUH 

0096-0699-A

these distances can be increased to 10 kilometers (and a total of 25 kilometers on the Fibre

Channel loop).

NOTE: The maximum distance between a single server and the Fibre Channel Storage Hub is 10

kilometers. A NetWare connection or dedicated direct link will need to connect each cluster node.

Connecting the nodes over long distances will require a combined use of Ethernet network devices, such as

hubs, switches, or repeaters.

The Compaq RAID Array 4000 storage system consists of four primary components:

•Fibre Channel Array

•Fibre Channel Storage Hub

•Fibre Channel Array Controller

•Fibre Channel Host Controller

When planning your Compaq RAID Array 4000 storage system, remember to include any

necessary cabling. Also, the Fibre Channel Array Controller is not a separate component; rather,

the array controller is an integral part of the Fibre Channel Array.

Compaq Fibre Channel Array

The Compaq Fibre Channel Array is the storage chassis that contains the disk drives, power

supply, and Fibre Channel Array Controller. The Fibre Channel Array can hold twelve 1-inch or

eight 1.6-inch Wide-Ultra SCSI-3 drives. The Compaq Fibre Channel Array comes in both a rack

and a tower model.

Each ProLiant Cluster for NetWare 4.2 must have at least one Compaq RAID Array 4000 storage

system as external shared storage. As many as five Compaq RA4000s can be attached to the Fibre

Channel Storage Hub 7 and, with the Fibre Channel Storage Hub 12, up to ten Compaq RA4000s

are supported. In both cases, two ports on the hubs are used by the server connections. With the

Compaq RA4000 connected to both servers through the Fibre Channel Storage Hub, you can

independently manage volumes on the servers in the cluster as needed by your application and

environment.

Compaq Fibre Channel Storage Hub

The Fibre Channel Storage Hub creates the data path that allows one or more Compaq RAID

Array 4000 storage systems to communicate with one or more ProLiant servers. The Compaq

ProLiant Cluster for NetWare 4.2 requires at least one Fibre Channel Storage Hub; both servers

and all shared storage for the cluster must connect to this hub.

As the names imply, the Fibre Channel Storage Hub 7 and the Fibre Channel Storage Hub 12

contain seven and twelve ports, respectively. As mentioned, using the hubs in a cluster

environment will consume two ports for server connections, allowing five Compaq RAID Array

4000 storage systems on the Fibre Channel Storage Hub 7 and 10 arrays on the Fibre Channel

Storage Hub 12.

For higher availability, two Fibre Channel Storage Hubs can be configured as a redundant pair.

When used in combination with redundant Fibre Channel Array Controllers and redundant Fibre

Channel Host Controllers, a complete backup data path can be configured between the cluster

servers and the Compaq RAID Array 4000, as described below under “Redundant Fibre Channel

Loop for Increased Availability.”

Autres manuels pour 112726-001 - ProLiant - 6500

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels Compaq Serveur

Compaq

Compaq Evo Thin Client t20 Manuel de service

Compaq

Compaq 112726-001 - ProLiant - 6500 Guide de référence rapide

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Manuel de référence

Compaq

Compaq ProLiant 5500 Instructions d'utilisation et de sécurité

Compaq

Compaq 2500 - ProLiant - 64 MB RAM Manuel utilisateur

Compaq

Compaq 112726-001 - ProLiant - 6500 Guide de référence rapide

Compaq

Compaq BL10e - HP ProLiant - 512 MB RAM Instructions d'utilisation et de sécurité

Compaq

Compaq BL20p - ProLiant - G2 Manuel utilisateur

Compaq

Compaq ProLiant DL580 Instructions d'utilisation et de sécurité

Compaq

Compaq 234664-002 - ProLiant - ML330T02 Manuel utilisateur

Compaq

Compaq 850R - ProLiant - 32 MB RAM Manuel utilisateur

Compaq

Compaq ProLiant 5000 Manuel utilisateur

Compaq

Compaq ML530 - ProLiant - 128 MB RAM Manuel utilisateur

Compaq

Compaq Evo Thin Client t20 Manuel utilisateur

Compaq

Compaq ProLiant ML350 (G2) Manuel utilisateur

Compaq

Compaq t1000 - Terminal Thin Client PC Fiche technique

Compaq

Compaq ML350 - ProLiant - G2 Instructions d'utilisation et de sécurité

Compaq

Compaq 108164-003 - ProLiant - 800 Guide de référence rapide

Compaq

Compaq ML530 - ProLiant - 128 MB RAM Guide d'installation

Compaq

Compaq ProLiant ML350 (G2) Manuel utilisateur

Compaq

Compaq ProLiant 400 Guide de démarrage rapide

Compaq

Compaq 386746-001 - ProLiant - 1600 Guide de démarrage rapide

Compaq

Compaq T5720 - Thin Client Guide d'installation

Compaq

Compaq ML370 - ProLiant - G3 Manuel utilisateur

Manuels Serveur populaires d'autres marques

HP AlphaServer ES47 Manuel utilisateur

Dell

Dell PowerEdge R410 Manuel utilisateur

PowerNAS

PowerNAS CMA Manuel utilisateur

Supero

Supero FatTwin F617R3-FT Manuel utilisateur

MSI

MSI P1-109N-L70 Manuel utilisateur

Dell

Dell PowerEdge XE9640 Manuel

Dell

Dell PS4100 Instructions de montage

EtroVISION

EtroVISION EV3151 Manuel utilisateur

NEC

NEC Express5800/T110j Manuel utilisateur

HP ProLiant Gen9 Manuel utilisateur

Dell

Dell PowerEdge 3YPMN Manuel utilisateur

iRobo

iRobo IPC2U Manuel utilisateur

Nortel

Nortel 1000 Con?guration guide Manuel utilisateur

Asus

Asus AP7500 Manuel d'utilisation et d'entretien

Avid Technology

Avid Technology AirSpeed 5000 Manuel utilisateur

HP Integrity rx2600 Guide d'installation

Milestone

Milestone Husky IVO 350T Manuel utilisateur

Planet

Planet NAS-7410 Manuel utilisateur