Fujitsu BS2000/OSD User manual

Edition March 2013
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.vor
English
HNC
High-Speed Network Connect
BS2000/OSD Server
User Guide
Valid for:
HNC Software V2.1 (HNC-V 91854, HNC-VI 91855)

Comments…Suggestions…Corrections…
The User Documentation Department would like to know your
opinion on this manual. Your feedback helps us to optimize our
documentation to suit your individual needs.
Feel free to send us your comments by e-mail to:
[e-mail]
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system which
complies with the requirements of the standard
DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
This manual is printed
on paper treated with
chlorine-free bleach.
Copyright © Fujitsu Technology Solutions GmbH 2013.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Linux is a registered trademark of Linus Torvalds.
The Linux-based operating systems X2000 and MARS which are installed on the Server Unit and MARS contain
Open Source Software. You will find the licenses for this software in the ThirdPartyLicenseReadme.txt file on the
installation DVD.

U41655-J-Z125-5-74
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 20. March 2014 Stand 13:14.05 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.ivz
Contents
1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1 Objectives and target groups of the manual . . . . . . . . . . . . . . . . . . . . . 7
1.2 Summary of the contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3 Changes since the last edition of the manual . . . . . . . . . . . . . . . . . . . . . 8
1.4 Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Open Source Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1 Basic mode of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1.1 LAN connection of the HNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2 BS2000 connections and emulated BS2000 devices . . . . . . . . . . . . . . . . . 15
2.2 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Operating the HNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1 HNC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1 Calling the HNC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.2 Logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.1.3 Logging out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.4 Session management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1.5 Interface of the HNC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.5.1 Window types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.1.5.2 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1.5.3 Dialog boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.1.6 Calling an object or function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.7 Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Contents
U41655-J-Z125-5-74
3.1.8 Filtering a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.9 Sorting a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.10 Calling the online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.1.11 Error handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2 Access to the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.1 Opening a terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.2 Closing the terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2.3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3.1 auditLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3.2 cli_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3.3 hnc_state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3.4 init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 BS2000 connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5 Managing the HNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
5.1 Querying information about the HNC . . . . . . . . . . . . . . . . . . . . . . . . 37
5.2 HNC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.2.1 Managing the host name, default gateway, LAN interfaces, and DNS configuration . . 39
5.2.2 Configuring the system time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.2.3 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.2.4 Managing links to external devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
5.3 Managing accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.1 Managing local accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.3.2 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3.3 Configuring access to an LDAP server . . . . . . . . . . . . . . . . . . . . . . . . . 46
5.3.4 Managing LDAP accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.4 Managing backups (CSR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
5.5 Powering the HNC on and off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Contents
U41655-J-Z125-5-74
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 20. March 2014 Stand 13:14.05 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.ivz
6 Diagnostics and maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1 Maintenance concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1.1 Remote service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
6.1.2 Tasks of Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
6.1.3 Tasks of the customer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
6.2 Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
6.2.1 Tasks and responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
6.2.2 Obtaining updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.2.3 Managing updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
6.2.4 Actions for updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.3 Assisting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6.4 Diagnostic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.5 System log (audit log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Contents
U41655-J-Z125-5-74

U41655-J-Z125-5-74 7
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 20. März 2014 Stand 13:08.12 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k01
1 Preface
This manual describes the architecture and concept of the High-speed Network Connect
(abbreviated to: HNC). The HNC connects S servers to the LAN. The HNC offers a Web
interface, the HNC Manager, for its operation and management.
The manual describes the products HNC-V 91854 and HNC-VI 91855.
For the sake of simplicity, these are referred to as HNC in this manual.
1.1 Objectives and target groups of the manual
This manual is intended for systems support and the network administrator.
It is assumed readers have a knowledge of BS2000 system operation, BS2000 systems
support, and BS2000 administration.
1.2 Summary of the contents
The documentation for the HNC with the software status V2.1 consists of this manual, the
Security Manual, and the online help.
●The manual provides an overview of the architecture and concepts of the HNC and
presents its functions.
●The Security Manual [6], which also applies for the SQ server and the SKP, describes
aspects which are relevant to security for the HNC.
●The online help describes all the functions of the HNC Manager. You open the online
help in the HNC Manager, see also Calling the online help.
The manual is structured as follows:
The chapter “Architecture” provides a schematic description of the HNC’s architecture and
hardware and the connections to the S server.
The chapter “Operating the HNC” explains the structure of the Web interface and how the
HNC is accessed via the CLI (Command Line Interface).

Changes since the last edition of the manual Preface
8 U41655-J-Z125-5-74
The chapter “BS2000 connections” describes the main function of the HNC, which is to
monitor BS2000 connections and, when required, to restart them.
The chapter “Managing the HNC” describes how you manage the HNC using the functions
of the HNC Management in the HNC Manager.
The chapter “Diagnostics and maintenance” describes how you perform maintenance for
the HNC and how you proceed when a fault occurs.
These chapters are followed by the chapter on related publications and an index.
Further documentation
The manuals “System Installation” [1] and “Introductory Guide to Systems Support” [2] are
recommended for obtaining a basic understanding of BS2000/OSD.
The ”VM2000” manual [3] is recommended for obtaining a basic understanding of VM2000.
The “openNet Server BCAM” manual [4] is recommended to provide further information on
the data communication system BCAM.
The BS2000/OSD commands referred to in this manual are described in the “Commands”
manual [5], and the VM2000 commands in the “VM2000” manual [3].
Operation of the S servers is described in the relevant “Business Server Sxxx” Operating
Manuals.
Operation of the PRIMERGY server of the TX300/RX350 series which is used as the
hardware basis for the HNC is described in the relevant Operating Manual.
1.3 Changes since the last edition of the manual
This manual has been completely revised to describe the new functions of the HNC.

Preface Notational conventions
U41655-J-Z125-5-74 9
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 20. März 2014 Stand 13:08.12 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k01
1.4 Notational conventions
The following notational conventions are used in this manual:
The following abbreviations are used in this manual:
●S server for the business servers of the S series (/390 architecture)
●BS2000 for the BS2000/OSD operating system in compound nouns,
e.g. BS2000 system.
In the text, references to other manuals are made in abbreviated form. The full title of each
publication is referenced by a number in square brackets and can be found in the “Related
publications” under this number.
1.5 Open Source Software
The Linux-based base system of the HNC contains Open Source Software. The licenses
for this are contained in the ThirdPartyLicenseReadme.txt file on the relevant installation
DVD.
IIndicates important information and tips.
VIndicates a warning of data loss.
ÊIndicates the action which you must perform.
italics Indicates texts from the Web interface.
monospaced Indicates system inputs and outputs.
monospaced
semibold
Indicates statements which are entered via the keyboard.
UPPERCASE
LETTERS
Indicates BS2000 commands.
<abc> Indicates variables which are replaced by values.
[Key symbols] Keys are displayed as they appear on the keyboard. When uppercase
letters need to be entered, the Shift key is specified, e.g. [SHIFT] - [A]
for A. If two keys need to be pressed at the same time, this is indicated
by a hyphen between the key symbols.
Table 1: Notational conventions

Open Source Software Preface
10 U41655-J-Z125-5-74

U41655-J-Z125-5-74 11
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 27. März 2013 Stand 10:55.15 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k02
2 Architecture
The HNC (High-speed Network Connect) connects the BS2000/OSD system (or the
BS2000/OSD systems) of an S server to the LAN (connection type ZASLAN). The S server
can be connected to the HNC via Fibre Channel (FC).
The FC connection on the S server is established either via an FC switch or directly on the
S server’s FC channel.
The two integrated channel connections (ports on the FC controllers) enable the HNC to be
connected to the same or to two different S servers. Details of a redundancy strategy which
this approach are provided in the BCAM manual [4].
The HNC can also be connected in parallel to another HNC or to disk systems on the same
FC channel of the S server.
The HNC also supports communication between different BS2000/OSD systems
(connection type LOCLAN) which
●are running on the same BS2000 server
●are running on two different BS2000 servers which are connected to the same HNC
Data transfer is handled internally in the HNC without any load being placed on the network.
BS2000 connections, i.e. communication connections between the BS2000/OSD systems
and the LAN, are established by means of virtual network connections (also referred to as
VCAs = Virtual Channel Adapters in other documents).
The HNC supports the operation of a large number of VMs or BS2000/OSD systems with:
●up to 128 BS2000 connections per Fibre Channel
The ZASLAN connections which can actually be configured on an HNC depend on the
number of licenses/MAC addresses which are available.
For security reasons, the basic version of the HNC already offers its own physically
separated LAN connections for administration (administration LAN), for maintenance and
remote service (service LAN), and for the network connection of the BS2000 systems
(BS2000 connections of the type ZASLAN). This ensures that the administration paths are
decoupled from the data transfer paths.

Architecture
12 U41655-J-Z125-5-74
The HNC Manager is the graphical Web interface of the HNC and offers the following
functions:
●Detailed display of all BS2000 connection, including the current status and the option
of restarting individual BS2000 connections. The service engineer configures the
BS2000 connections or VCAs (one emulated device pair per BS2000 connection) when
the HNC is placed in service.
●Display of the information required for the HNC software and hardware, including the
current status
●Management of the authorizations for accessing the HNC
●Administration of the HNC, e.g. LAN configuration or NTP
●Maintenance of the HNC, e.g. configuration data backup or update

Architecture Basic mode of operation
U41655-J-Z125-5-74 13
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 27. März 2013 Stand 10:55.15 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k02
2.1 Basic mode of operation
The figure below provides a schematic view of the possible connections of the HNC. It
displays only the components and connections which are relevant for this manual.
Figure 1: Connections of the HNC
Data transfer between the BS2000 system and the connected LANs is implemented via a
device pair (WRITE and READ devices).
Data packets are generated by a BS2000 system and sent via a channel (WRITE device)
and the internal HNC LAN component SLAN (shared LAN) to one of the connected LANs,
or they are received by the SLAN and forwarded via the device address of a channel (READ
device) to a BS2000 system (connection type ZASLAN).
The BS2000/OSD system is connected to the HNC via Fibre Channel (FC). The FC
controller is identified unambiguously by its WWPN (World Wide Port Name).
Administration LAN
FC connection
BS2000
(BS2-MAC_ADR 2)
....
S server
LOCLAN
SLAN
ZASLAN
HNC
Administriation PC
with HNC Manager
BS2000
(BS2-MAC_ADR 1)
VM 1
VM 2
LAN controller
(MAC_ADR 1+2+ ...)
Production LAN (ZASLAN)
Onboard LAN
FC controller
(WWPN) VM n
Customer support
notebook (optional)
Service LAN
admin
service

Basic mode of operation Architecture
14 U41655-J-Z125-5-74
The MAC address in the header of a data packet is the criterion for forwarding received data
packets to the various BS2000 systems.
For this purpose the LAN controllers can receive data packets with different receiver
addresses and send them to different sender addresses.
The HNC uses two device addresses on the FC or ESCON connection: one for read
commands and one for write commands. Quasi full duplex mode is thus possible.
The device address is assigned a MAC address. The transferred data packets are not
processed further in the HNC. No special protocol is used between the BS2000 system and
the HNC.
Connection type ZASLAN
The HNC mainly transfers data packets between the BS2000 systems via LAN:
●The LAN controller transfers the data packets to or from the HNC’s central memory to
the LAN.
●With the support of the HNC CPU the FC controller transfers the packets between the
memory and the FC connection of the BS2000 system.
Connection type LOCLAN
A special case that the HNC permits is communication between two BS2000 (guest)
systems which
●are running on the same BS2000 server
●are running on two different BS2000 servers which are connected to the same HNC
This communication (routing in the HNC) is implemented by the software module SLAN
(internal “shared LAN”). It establishes the connection between a BS2000 (guest) system
and a LAN on the HNC.
This permits guest systems of the same S server, for instance, to communicate via
LOCLAN.

Architecture Basic mode of operation
U41655-J-Z125-5-74 15
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 27. März 2013 Stand 10:55.15 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k02
2.1.1 LAN connection of the HNC
The HNC is integrated into the following networks for its own administration and service
purposes:
Administration LAN
The administration LAN offers access to the HNC via an external PC. The administrator
manages the administration LAN using the HNC Manager.
Service LAN
The service LAN offers access to the HNC via an external service PC or directly via the
SKP. The service LAN is managed by Customer Support.
2.1.2 BS2000 connections and emulated BS2000 devices
On the HNC you can define multiple BS2000 connections for each of the two connection
types (ZASLAN or LOCLAN).
In BS2000/OSD these are presented as emulated devices, each with its associated device
pair (device address of a channel). To allow the emulated devices to be operated in
BS2000/OSD, they must be generated and assigned there.
From the HNC viewpoint ZASLAN and LOCLAN connections are referred to jointly as
BS2000 connections below. In older documents the term VCAs (Virtual Channel Adapter)
is often used for BS2000 connections.
In BS2000/OSD a LAN device is identified and addressed using its mnemonic name. The
mnemonic name is referred to as the mnemonic for short and abbreviated to MN in BS2000
device management.
The BS2000-compliant device address is defined when an emulated device is configured
in BS2000. There are differences between BS2000 and the HNC in the terms used:
●The HNC can be connected to the S server via Fibre Channel (FC0, FC1) or ESCON.
The corresponding Channel Path Identifier (corresponds to a virtual channel) is defined
in BS2000 when the system is generated.
●The unit ID specified on the HNC is included in the device address in BS2000 (corre-
sponds to the so-called host LUN).
When configuring a BS2000 device, not only the device-type-specific information must be
specified: specification of the mnemonic and unit ID and of the device node to permit
addressing on the BS2000 side is always obligatory.

Hardware Architecture
16 U41655-J-Z125-5-74
For details on the device address in BS2000/OSD, also refer to the “System Installation”
manual [1].
2.2 Hardware
The hardware basis of the HNC is a PRIMERGY server of the TX300/RX350 series
equipped as follows:
●Basic unit
–1DVDdrive
– No local console
●Onboard LAN
– 3x GBit LAN onboard
The onboard LAN interfaces are reserved for administration and service.
●Possible extensions for the interface cards
– A total of two channels (FC) are available for the channel connection.
A maximum of four connections are permitted for the network connections to the LAN.
●Connection to remote service
In the HNC the remote service access is established by the connection to the service
LAN.
Via these links connections can be set up from the SKP to the HNC which can also be
used via remote service (on the SKP). In this way the HNC is integrated into the
teleservice infrastructure of Fujitsu Technology Solutions.
Installation variants
The HNC is offered as a floor stand model or as a rack model.
Channel and LAN connections of the HNC
Fibre Channel 91855-KCG
(10/100/1000 CU)
91855-KGF
(1000 Fiber)
2 2 - 4 0
221-2

Architecture Software
U41655-J-Z125-5-74 17
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 27. März 2013 Stand 10:55.15 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k02
2.3 Software
This manual describes the software status V2.1 for the HNC.
The HNC software is Linux-based. You see amoung others the version of the Linux system
base SLES 11 with security corrections, e.g. in the system maintenance (security fixes).
An SNMP agent which also supports traps is preinstalled. The SNMP agent supports the
following MIBs:
●RFC 1213 (MIB-II)
●MIBs with private traps, see “Configuring SNMP” on page 41
When you select HNC Management in the HNC Manager, in the System overview tab you see,
among other things, the Linux version or the status of the security fixes.
For products on BS2000 level following software requirements apply:
●BS2000/OSD V5.0 or higher
●openNet Server V3.1 or higher (support of Fibre Channel)
●For VLAN, openNet Server V3.2 or higher
●For Link Aggregation & Checksum Offloading openNet Server ab V3.4
The HNC displays relevant information about the installed software in the HNC
Management>System overview tab, see “Querying information about the HNC” on page 37.

Software Architecture
18 U41655-J-Z125-5-74

U41655-J-Z125-5-74 19
Dokuschablonen 19x24 Version 7.4us für FrameMaker V7.x vom 09.02.2010 © cognitas GmbH 2001-2010 27. März 2013 Stand 10:55.15 Pfad: P:\FTS-BS\BS2-GA\OSD-V90\9999999_Einleitungen\HNC\prod_e\hnc.k03
3OperatingtheHNC
You operate the HNC using the HNC Manager or directly via the CLI (Command Line
Interface). The HNC Manager is a Web application with a GUI (Graphical User Interface)
which offers the following functions:
●Displaying and restarting BS2000 connections, see section “BS2000 connections” on
page 33
●Configuring and changing personalized administrator accounts, see section “Managing
accounts” on page 44
●Displaying and changing the HNC configuration, see section “HNC configuration” on
page 39
●Maintaining the HNC, see section “Diagnostics and maintenance” on page 51
●Accessing the HNC via the CLI, see section “Access to the CLI” on page 31
Before it is delivered, the HNC is installed and configured in accordance with your require-
ments.
3.1 HNC Manager
To use the HNC Manager “remotely” from a PC, you need a PC with a network connection
to the HNC which has a Java Runtime Environment Version 1.6.x or higher and a browser
installed.Microsoft Internet Explorer Version 7 through Version 10 and also Mozilla Firefox
Version 3.6 or 10.0 (incl. ESR) and higher are supported.
The browser on your PC must satisfy the following requirements:
●The execution of applets is permitted.
●The execution of JavaScript is permitted.
●Cookies are permitted.
A terminal access (shell to the HNC) is embedded in the HNC Manager.

HNC Manager Operating the HNC
20 U41655-J-Z125-5-74
Communication always takes place using HTTPS (HyperText Transfer Protocol Secure),
with the encryption protocols SSL 3.0 (Secure Sockets Layer) and TLS 1.0 (Transport Layer
Security) beneath this being supported. SSL 2.0 is not supported. Automatic redirection to
HTTPS takes place when HTTP is called.
The use of HTTPS/SSL requires not only an SSL key pair on the HNC, but also a (digital)
SSL certificate. For information on the security aspects when using the HNC Manager,
please refer to the Security Manual [6].
The languages of the HNC Manager are English and German. You can set the language
using the language option in the header area.
3.1.1 Calling the HNC Manager
ÊEnter the HNC’s address in the browser’s address bar.
ÊPress the Úkey. The login window opens.
3.1.2 Logging in
Access to the HNC Manager is protected. To log in, you must specify your account and the
associated valid password.
The login window provides access to the HNC Manager. It has a different layout from the
other windows:
Figure 2: Login window of the HNC Manager