HB HiVision64 Us

F 6.
4 Manual
Hirschmann Network Management
HiVision Technical Support

Release 6.4 06/07 HAC-Support@hirschmann.de
F 6.4 Manual
Hirschmann Network Management
HiVision Technical Support

Release 6.4 06/07 HAC-Support@hirschmann.de
Trademarks mentioned in this manual, even if not specifically identified as such, give no right to
assume that such names may be considered as being free within the meaning of the trademark
legislation nor that anyone may use them freely.
© 2007 Hirschmann Automation and Control GmbH
Manuals and software are subject to copyright. All rights reserved. Copying, duplication, trans-
lation, conversion to any electronic medium or machine-readable form in whole or in part are not
permitted. The only exception applies to production of a backup of the software for the user's
own backup purposes. For devices with embedded software, the end-user license agreement
on the enclosed CD applies
The performance features described here are binding only if they have been expressly guaran-
teed in the contract. This publication has been created by Hirschmann Automation and Control
GmbH according to the best of our knowledge. Hirschmann reserves the right to change the con-
tents of this manual without prior notice. Hirschmann can give no guarantee in respect of the
correctness or accuracy of the details in this publication.
Under no circumstances can Hirschmann be held liable for any damage arising in any connec-
tion with use of the network components or their operating software. We also refer to the condi-
tions of use stated in the license agreement.
Printed in Germany (12.6.07)
Hirschmann Automation and Control GmbH

Stuttgarter Straße 45-51
72654 Neckartenzlingen
Germany
Tel. +49 1805 141538 039 584-640-01-0607
Contents
Contents
1 Introduction 11
1.1 HiVision management shell 12
1.2 The HiVision basic structure 15
1.2.1 The HiVision program 15
1.2.2 The HiVision management platform 16
1.3 With HiVision manageable products 17
1.4 Supported MIBs 21
2 Installation 23
2.1 File structure of the HiVision CD 26
2.2 PC-StandAlone solution for Windows 27
2.2.1 Installation requirements 27
2.2.2 Installation 28
2.2.3 Program start 29
2.2.4 Updates 31
2.2.5 Deinstallation 32
2.3 PC-StandAlone solution for Linux 33
2.3.1 Installation prerequisites 33
2.3.4 Updates 36
2.4 Integration with HP OpenView for Windows 38
2.4.4 Updates 41
2.5 Integration in HP OpenView for HP-UX 42
HiVision
Release 6.4 06/07 5
Contents
2.5.4 Updates 46
2.6 Trap destinations of the agent 48
2.7 OPC server under Windows 50
2.7.2 Updates 51
3 Overview of HiVision 53
3.1 Function overview 56
3.1.1 Main window 56
3.1.2 Device window 57
3.1.3 Detail window 58
3.1.4 License window 59
3.2 Using HiVision 60
3.2.1 Requirements 60
3.2.2 Getting started with HiVision 61
4 "HiVision" main window 65

4.1 Menu bar 67
4.1.1 Preferences 69
4.1.2 Licenses 75
4.1.3 Status configuration 76
4.1.4 Status propagation 77
4.1.5 Agent Polling 80
4.1.6 Network configuration 80
4.1.7 Assignment of MAC/IP address 82
4.1.8 Locate MAC Address 82
4.1.9 Port Manager/Port Analyzer 83
4.1.10Multi-device configuration 87
4.1.11Telnet window 88
4.2 Tool bar 89
4.3 Card index 91
4.3.1 Agent overview 92
4.3.2 Events 96
4.3.3 Event actions 100
4.3.4 VLAN Manager 102
HiVision
6 Release 6.4 06/07
Contents
4.4 Status line 103

4.4.1 Status messages 103
4.4.2 Symbol area 104
5 Device window 105

5.1 Tool bar 108
5.2 Image 110
5.2.1 Device image 110
5.2.2 Subdevice buttons 111
5.3 Physical Map 113
5.4 Logical Map 115
5.5 Device information 116
5.6 Events 117
5.7 Index 118
6 Detail window 119

6.1 Tool bar 121
6.2 Information presentation 123
6.2.1 SNMP monitor 124
6.2.2 RMON function 126
6.2.3 Detail polling 129
6.2.4 Rack Monitoring System 130
6.3 Configuration settings 131
6.3.1 Filter settings of the RMS 131
6.3.2 Switch configuration 133
6.3.3 Router configuration 137
6.3.4 Redundant routers 139
6.4 Index 145
7 VLAN manager 147

7.1 The function of the VLAN manager 149
7.1.1 Advantages of the VLAN manager 149
7.1.2 Configuration types 149
7.1.3 Data entry elements 151
7.1.4 The network management station as a user 153
HiVision
Release 6.4 06/07 7
Contents
7.2 Port-based VLANs 154

7.2.1 Selecting the configuration type 155
7.2.2 Selecting the agents 155
7.2.3 Creating groups 158
7.2.4 Defining Uplink and port access 159
7.2.5 Saving the configuration to a file 160
7.2.6 Saving the configuration to the agents 161
7.3 MAC-based VLANs 163
7.3.3 Creating stations 167
7.3.6 Saving the configuration in a file 173
7.3.7 Testing the configuration 174
7.4 VLAN configuration example 177
7.4.6 Examples for configuration files 191
8 Creating a PSM 193

8.1 Preparation 196
8.1.1 Program functions 196
8.1.2 Management Information Base 200
8.1.3 Image file 200
8.2 Creating a PSM structure 201
8.2.1 MIB files 203
8.2.2 Manuals for the product 204
8.3 Agent in the main window 205
8.3.1 Product family symbol 205
8.3.2 Product name 205
8.3.3 Agent status 206
8.4 Agent in the Device window 207
8.4.1 Cards 207
HiVision
8 Release 6.4 06/07
Contents

8.4.3 Symbols for device functions 208
8.5 Agent window 209
8.5.1 List display 209
8.5.2 Dialog display 209
8.6 Editing PSM files 210
8.6.1 PsmInfo.xml 212
8.6.2 Productimage.jpg 215
8.6.3 SysOidList.xml 215
8.6.4 ProductFamily.xpm 216
8.6.5 ProductFamily.xml 217
8.6.6 Agent.xml 218
8.6.7 AgentDialog.xml 224
8.6.8 Component.xml 232
8.6.9 action.xml 233
8.6.10outname.xml 235
8.6.11LanguageTable.conf 236
8.7 Testing PSM 238
A Appendix 243
A.1 Frequently asked questions 244
A.2 Device information 245
A.2.1 RMS 245
A.2.2 MIKE, MULTIMIKE and FCMA 245
A.2.3 ETH-12TP/M 246
A.2.4 FEH-24TP 247
A.2.5 RS2-../.. 247
A.2.6 MICE 248
A.2.7 ETS-14TP, -30TP, -16TP Plus, -32TP Plus,
FES-08TP Plus, -16TP Plus and -16TP 249
A.2.8 GES-24TP/2SX/FES-24TP 249
A.2.9 GES-24TP Plus, GES-24FX 250
A.2.10 ALS family 251
A.2.11 GLS family 251
A.2.12 MACH 3000 252
A.2.13 GRS family 252
A.2.14 FastIron series 252
A.2.15 BAT54-Rail 253
A.2.16 LION-24 TP 253
HiVision
Release 6.4 06/07 9
Contents
A.2.17 10 Gigabit/s ports 254

A.2.18 Platform-specific information
(HP OpenView integrated versions) 254
A.3 Hirschmann Competence 255
A.4 Readers Comments 257
A.5 Index 259
HiVision
10 Release 6.4 06/07
Introduction
1 Introduction
1.1 HiVision management shell 12
1.2 The HiVision basic structure 15

1.2.1 The HiVision program 15
1.2.2 The HiVision management platform 16
1.3 With HiVision manageable products 17
1.4 Supported MIBs 21
HiVision
Release 6.4 06/07 11
Introduction 1.1 HiVision management shell
1.1 HiVision management shell
HiVision is a management shell for managing Hirschmann agents and for

monitoring all SNMP-capable devices linked to the network. The agents can
be addressed via SNMP (Simple Network Management Protocol) or via
ICMP (Internet Control Message Protocol). This provides a comprehensive
overview of the whole network. All components are automatically identified.
HiVision generates a device view representing the device in its physical form.
HiVision also generates a logical view for hubs which displays the device
from the perspective of its interfaces (see “Logical Map” on page 115). The
device information window in HiVision provides information on the most im-
portant system parameters such as the system description, the MAC
address, ...
This enables at all times

D the current status of your network to be displayed,
D a rapid, comprehensive analysis, error search and control even with com-
plex networks.
Intuitive operation makes the use of functions both straightforward and rapid.
The network components are displayed as gray scale images. Color overlay-
ed status displays, click-on context menus at port, group and device level
provide further detailed information.
Multiple help functions and integrated expert knowledge facilitate effective
management without requiring special expertise on the part of the user
The following HiVision versions are available:

D PC-StandAlone version under Windows 2000/XP/Vista/2003 Server
D PC-StandAlone version under Linux
D Integration in the PC management platform HP OpenView for
Windows 2000/XP/2003 Server
D Integration in a HPUX management platform HP OpenView.
HiVision
12 Release 6.4 06/07
U PC-StandAlone version under Windows 2000/XP/Vista/

2003 Server
Designed as an economical starter solution for small to medium size net-
works with a modular design, the PC StandAlone solution for Windows
2000/XP/Vista/2003 Server opens up a wide range of management opti-
ons.
Auto-discovery of all components at program start-up, live monitoring of
the network, OPC connection to SCADA systems, and extensive config-
uration and monitoring functions offer a broad range of options for net-
work administration.
Trap handling with RMON alarms, event handling and freely definable
actions guarantee a differentiated, proactive monitoring of complex
networks.
U PC-StandAlone Version under Linux

The complete network management functionality of the PC stand-alone
version for Windows NT is also available under Linux. The high-capacity
Linux operating system and powerful hardware meet the highest stan-
dards in respect of stability and performance.
Trap handling with RMON alarms and event handling guarantee a diffe-
rentiated, proactive monitoring of complex networks.
U Integration in the PC management platform HP OpenView

for Windows 2000/XP/Vista/2003 Server
In addition to the PC StandAlone solution, all the options of the
management platform HP OpenView are open to the administrator under
Windows 2000/XP/Vista/2003 Server.
HiVision forwards status changes to the platform and thus affects the
way in which the symbols are displayed in the platform.
HiVision
Release 6.4 06/07 13
U Integration in the HPUX management platform

HP OpenView
In addition to the PC management platform under Windows, the powerful
Unix operating system with high capacity hardware fulfils the most
demanding criteria in relation to stability and performance. Long-term
investment security and migration paths in respect of business and
management systems are guaranteed by the support of major
producers.
HiVision
14 Release 6.4 06/07
Introduction 1.2 The HiVision basic structure
1.2 The HiVision basic structure
1.2.1 The HiVision program

HiVision is made up of a core program together with one to two modules. The
modules allow individual adaptation to the network. The modules are called:
D Industrial Line
for all ETHERNET (shared) components via the management card MIKE
inside the ASGE/MC/AMC and
Industrial Rail family for the Rail Switch RS2, RS20, RS30, RS40, Rail
Gateway RG2, MICE/Power MICE family, OCTOPUS, Wireless ETHER-
NET AP/AC BAT as well as MR8 and CS 30.
D Enterprise
for ALS, GLS, MACH 1000, MACH3000, MACH 4000, GRS, Foundry Net-
works FastIron Serie, Workgroup Switches, Wireless ETHERNET AP/AC
BAT 11B, FAMAMM2 and MultiMIKE inside the AMC and
for all FDDI components via the management card FCMA inside the
ASGE/MC
as well as Rail Gateway RG2, Workgroup Hubs ETH-12TP/M, ETPS-
22TP/M and FEH-24TP/M ds.
The scope of delivery includes the core program with all modules. The mo-
dules and PSMs cannot be run without valid license keys. The core program
already contains the Rack Monitoring System administration and the basic
administration of unknown devices.
As an introductory offer, you can use HiVision without a license for the
unrestricted administration of a single agent.
HiVision
Release 6.4 06/07 15
Introduction 1.2 The HiVision basic structure
1.2.2 The HiVision management platform

The management shell is arranged in three levels with corresponding
windows:
D Main window
The main window provides an overview over all contactable agents in the
network. Settings made in the main window affect the whole system.
D Device window
The device window contains various views of a selected device. Colored
symbols mean that the condition of the whole device, right down to the in-
dividual ports, can be seen at a glance.
D Detail window
The status messages can be qualified in the detail windows. The display
shows the MIB attributes read out from this device.
The detail information is subdivided into the groups
– configuration,
– performance,
– error and
– security.
When the mouse pointer is positioned over an MIB attribute, the descrip-
tion of the MIB attribute is shown by a bubble help.
Writeable MIB attributes can be reset in this window. The prerequisite is
the appropriate access entitlements.
The main component of each window is a card-index. The individual cards

display the contents of the card-index (= the device in the device window)
from various perspectives.
HiVision
16 Release 6.4 06/07
Introduction 1.3 With HiVision manageable products
1.3 With HiVision manageable

products
The following list shows the name of the products from the Hirschmann pro-
duct range, which are manageable with HiVision 6.4.
ETHERNET FDDI TokenRing

CYDE FCMM-MIC TCTMM-BFOC
KYDE-S FCMM-BFOC TCLTP6-RJ45
KYDE-S (RBDE) FCLC3-DSC TCTTP-RJ45
OYDE-S FCBMS-BFOC
OYDE-S (RBDE) FCSM-BFOC
TYDE FCAM-BFOC
IYDE-S FCTP3-RJ45
IYDE-S (RBDE) FCSTP
UYDE FCMA
ECAUI
ECFL2
ECFL4
ECFB2
ECTP3
MIKE
Table 1: Manageable interface cards for concentrators, hubs, MC, ASGE family

EAFL4 FATP6-GS-RJ45 TALTP12-GS-RJ45
EAFL4-GS FATP6-GS-DB9 TATLMM-GS
EAFL4-PS FALC6-GS-DSC TATLTP-GS-RJ$%
EAFL8 FAMM2-GS-DSC
EAFL8-GS FAMAMM2-GS
EAFB4
EAFB4-GS
EATP12
EATP12-GS
Table 2: Manageable interface cards for Advanced Media Centers
HiVision
Release 6.4 06/07 17

EATP12-PS
EATP12-FS
EACX8
EACX8-GS
EAAUI
EAAUI4-GS
EAMAFL2
EAMAFL2-GS
EAMAFB2-GS
FastSXM2
100EATP10-GS
FERxM
AESMM
ESTP6
MultiMIKE
Table 2: Manageable interface cards for Advanced Media Centers
MR8-03 ALS GLS MACH 3000/4000 MICE

EBAUI ELTP6 ELTP2-M M-BASIC4 MS2108 - 2 EEC)
EBGM ELCX6 ELTP12-F M-ETH 4MM-ST MS3124 - 2
EBMM ELMM6 ELMM10-F M-FAST 8Tp-RJ MM2 - 2FLM4
EBSM ELCX8 100ELTP4-F M-FAST 2MM-SC MM2 - 4TX1
EBSMP ELTP12 100ELMM4-F M-FAST 2SM-SC MM2 - 4TX1 - EEC
EBTP ELTP2-M 100ELSM4-F M-FAST 8MM-MT MM2 - 2FXP4
100ELMM2 100ELTP12 M-GIGA 2SX-SC MM2 - 4FXM3
100ELTP2 100ELMM12 M-GIGA 1LX-SC MM2 - 2FXM3 / 2TX1
100ELTP4 1000ELMM1 MACH 4000-48-4G MM2 - 2FXM2
100ELMM4 1000ELMM1+1R M4-8TP-RJ45 MM2 - 2FXS2
1000ELMM1-SC 1000ELSM1+1R M4-FAST 8TP- MM3 - 2AUI
RJ45-PoE
1000ELMM1+1R M4-FAST 8-SFP MM3 - 4FLM4
1000ELMS1+1R M4-GIGA 8-SFP MM3 - 2FLM4 / 2TX1 - RT
AAMM2 MM3 - 4TX5
AATP2 MM3 - 4TX1 - RT
MM3 - 4TX1 - PoE
MM3 - 4FXP4
MM3 - 1FXM2 / 3TX1
MM3 - 1FXM2 / 3TX1 -
EEC
MM3 - 2FXM2 / 2TX1
Tab. 3: Manageable interface cards and modules for switches
HiVision
18 Release 6.4 06/07
MR8-03 ALS GLS MACH 3000/4000 MICE

MM3 - 2FXM2 / 2TX1 -
EEC
MM3 - 2FXM2 / 2TX1 - RT
MM3 - 2FXM4 / 2TX1
MM3 - 4FXM2
MM3 - 4FXM4
MM3 - 1FXS2 / 3TX1
MM3 - 2FXS2 / 2TX1
MM3 - 2FXS2 / 2TX1 - RT
MM3 - 4FXS2
MM3 - 1FXL2 / 3TX1
MS4128 - 5
MM4 - 4TX / SF
Tab. 3: Manageable interface cards and modules for switches
GRS ASGE, MC, AMC

1000EGLX2+2-SC ERISDN
1000EGLX2-SC ACCESS-RXM2
1000EGSX2+2-SC
1000EGSX2-SC
1000EGSX6-SERV
100EGFX10-SC
100EGTP20-RJ45
100 EGFX20-MTRJ
FGMM2-SC
Table 4: Manageable interface cards for routers
Grundgeräte Workgroup Switches Workgroup Hubs Rail Switches

ASGE 1 ETS-12TP/M ETH-12TP/M RS2-FX/FX
ASGE 2 ETS-24TP/M ETPS-22TP/M RS2-FX-SM/FX-SM
ASGE-WG 24/TP ETS-12MM/M FEH-24TP/M ds RS2-TX/TX
ASGE-WG 24TP/M ETS-12MM-VF45/M RS2-4R
AMC 503 ETS-14TP RS2-16M
AMC 1006 ETS-30TP RS20
MR8-03 ETS-16TP Plus RS30
ALS 1605 ETS-32TP Plus RS40
Tab. 5: Manageable devices
HiVision
Release 6.4 06/07 19
Grundgeräte Workgroup Switches Workgroup Hubs Rail Switches

ALS 1604 FES-08TP Plus BAT 11B
ALS 402 FES-16TP Plus BAT54
ALS 201 FES-16TP BAT54-Rail
ALS 101 FES-24TP Plus
GLS 402 GES-24TP/2SX
GLS 1605 GES-16FX
GRS 1403 GES-24TP Plus
GRS 702 GES-24FX
FI 1500 LION-24TP
FI 800 LION-28TP
FI 400 PowerLION-24 TP
MACH 3001 Giga LION-24TP
MACH 3002
MACH 3005
MACH 4002
MS2108 - 2
MS2108 - 2 - EEC
MS3124 - 2
MS4128 - 5
MS20
MS30
OCTOPUS 8M
OCTOPUS 16M
OCTOPUS 24M
RMS
RG2-1TX
RG2-2TX-SL
CS30
EAGLE mGuard
Tab. 5: Manageable devices
HiVision
20 Release 6.4 06/07
Introduction 1.4 Supported MIBs
1.4 Supported MIBs
HiVision 6.4 supports the Hirschmann Private MIBs as well as the following
standard MIBs:
D rfc1213-MIB-II.mib
D rfc 1215-MIB-II.mib
D rfc1398-ETHER.mib
D rfc1493-BRIDGE.mib
D rfc1512-FDDI.mib
D rfc1516-REPEATER.mib
D rfc1724-RIP.mib
D rfc1757-RMON.mib
D rfc1850-OSPF.mib
D rfc1903-SNMPv2-TC.mib
D rfc1907-SNMPv2.mib
D rfc2037.mib
D rfc2096.mib
D rfc2233.mib
D rfc2239-MAU.mib
D rfc2613-SMON.mib
D rfc3621.mib
D IANAifType-MIB.mib
D ieee802-1-p.mib
D ieee802-1-q.mib
HiVision
Release 6.4 06/07 21
Introduction 1.4 Supported MIBs
HiVision
22 Release 6.4 06/07
Installation
2 Installation
2.1 File structure of the HiVision CD 26
2.2 PC-StandAlone solution for Windows 27

2.2.1 Installation requirements 27
2.2.4 Updates 31
2.3 PC-StandAlone solution for Linux 33

2.3.4 Updates 36
2.4 Integration with HP OpenView for Windows 38

2.4.4 Updates 41
2.5 Integration in HP OpenView for HP-UX 42

2.5.4 Updates 46
HiVision
Release 6.4 06/07 23
Installation
2.6 Trap destinations of the agent 48
2.7 OPC server under Windows 50

2.7.2 Updates 51
HiVision
24 Release 6.4 06/07
Installation
In the first part of this chapter, the file structure on the HiVision CD is detailed.
This is followed by the section on installation, subdivided according to the
various shells. The chapter on installation is concluded by the procedure for
setting an agent's trap targets.
HiVision
Release 6.4 06/07 25
Installation 2.1 File structure of the HiVision CD
2.1 File structure of the

HiVision CD
The following file structure can be presented in different ways depending on

the platform. Thus the file names for HP-UX appear in upper case letters
while those for AIX and Solaris are in lower case.
HPUX HiVision 6.4 for HP-UX and OpenView

HIVISION.DEPOT Depot HiVision 6.4 for HP-UX and OpenView
LIESMICH.HTM Installation instructions in German
README.HTM Installation instructions in English
LINUX HiVision 6.4 for Linux

INSTALL.SH Installationsprogramm
HIVISION.TAR.gz StandAlone HiVision 6.4 as a compressed tar-file
WINDOWS HiVision 6.4 for Windows 2000, XP, Vista and

2003 Server
SETUP.EXE Installation program
Datasheet_OpcServer.html
Data sheet of the HiControl OPC server
SMS SMS tool for Windows
LIESMICH.HTM “readme” file in HTML format in german language

LIESMICH.TXT “readme” file in ASCII format in german language
README.HTM “readme” file in HTML format
README.TXT “readme” file in ASCII format
HANDBUCH.PDF German manual HiVision in Acrobat Reader
format
MANUAL.PDF HiVision manual in Acrobat Reader format
AGREE.PDF License agreement in Acrobat Reader format
HiVision
26 Release 6.4 06/07
Installation 2.2 PC-StandAlone solution for Windows
2.2 PC-StandAlone solution for

Windows
2.2.1 Installation requirements

HiVision 6.4 requires for installation and operation:
D Hardware
Processor: x86 compatible CPU, >500 MHz recommended
Memory: 64 MB or better, 128 MB (recommended)
HiVision requires approximately 50 MB free RAM, plus
another 200 kB RAM for each detected agent.
In addition to this the network management station
requires RAM for the operating system and any
other applications it may use.
Hard disk: 80 MB free
D Windows 2000/XP/Vista/2003 Server
D a license for HiVision 6.4 (see “The HiVision program” on page 15, “Licen-
ses” on page 75 and “Order form for license on page 261”.
Windows 2000/XP/Vista/2003 Server is normally installed prior to delivery on

the PC. The version concerned should be checked in all cases.
Prerequisites with respect to the Hirschmann agents

MIKE software release 3.4
MultiMIKE software release 1.5
FCMA software release 3.4
MultiLAN Switch software release 2.1
Advanced LAN Switch release 2.12
Gigabit LAN Switch Release 3.20
Gigabit Routing Switch 3.2
FastIron Release 07.6.00CT53
H Workgroup Switches FES-24TP Plus und GES-24TP/2SX 2.0.0.2,
GES-24TP Plus 2.1.4
HiVision
Release 6.4 06/07 27
Rack Monitoring System 1.4b3 H2-14

MACH 3000 Rel. 3.1
Rail Switch RS2-../.. Rel. 5.1 and 7.0
MICE Rel. 3.0
BAT54-Rail Rel. 7.1
2.2.2 Installation
Administration entitlements are required before you can install HiVision.
V Insert the HiVision CD in the drive.

If the set-up program does not start automatically, then start it manually in
the "Windows" directory of the HiVision CD.
V Select the language and follow the instructions in the installation program.
V Select HiVision StandAlone and, if required, the Demo-Switch and

HiControl (refer “OPC server under Windows” on page 50).
Note: If there is user-specific data from an earlier installation, HiVision copies

it into the new version.
In release 5.1 and earlier releases, HiVision transfers in the data when you
install the new release in the same target directory.
Note: At the end of the installation, the HiVision set-up program checks
whether the SMScom program is already installed. If it is not installed,
HiVision gives you the option of starting the SMScom installation program.
If you want to install SMSCom later, you will find the installation program for
SMSCom in your HiVision directory, in the OEM-Setups sub-directory.
The function of SMScom is to send short messages when events occur
(see “Short Message Service (SMS)” on page 70).
Note: When you are installing the OPC Server software, refer to “Installation”
on page 51.
HiVision
28 Release 6.4 06/07
2.2.3 Program start

Individual input of the license key is necessary.
To be able to use all the HiVision functions, such as ICMP-Ping, you require
the administration rights on your network management station.
V HiVision saves
– all the default settings in the Preferences.xml file
– as well as other informations in further files
specifically for every user, in the directory
My documents\.hivision.
With the HIVISION_HOME environment variable, you can assign another
path to HiVision for these files on your network management station. You
click with the right mouse button on the My Computer symbol on your
desktop and select Properties:environment. In Variable you
enter the environment variable HIVISION_HOME and in Value you enter
the path. Then move the directory .hivision to this location.
V To be able to receive traps start the SNMP Trap Service in Windows

under Start:Control Panel:Management:Services.
V Start HiVision with the symbol on the desktop or from the start menu:
Start:Programs:Hirschmann:HiVision:HiVision 6.4
Or start HiVision with a command-line parameter:
Select the "HiVision 6.4" icon with the right mouse button under
Start:Programs:Hirschmann:HiVision. In the "Properties" win-
dow, enter the desired option(s) after the program name.
Parameter Meaning
-EditLicense (-L) Edit licences
help Display available options
-OpenAgentImage (-oi) <IP-Address> No network scan, only scan <IP-Address> and open
image
-ReadOnly HiVision is readonly
-remote Send commandline to a running HiVision
-ScanAgent (-a) <IP-Address> No network scan, only scan <IP-Address>
-SyntaxChecker Checks PSMs for syntax errors and consistency
Table 6: Command-line parameters for starting HiVision
HiVision
Release 6.4 06/07 29
V Select Configuration:Preferences:HiVision Licenses.

Enter the license key (see “License window” on page 59).
V Select the language you require under

Configuration:Preferences:Language.
Quit HiVision and restart it to put the language setting into effect.
V Enter the network range to be scanned by HiVision under the

Configuration:Preferences:Scan Ranges.
With Edit:Scan for new Devices, HiVision searches for devices in
the entered address ranges (see “Scan Range” on page 80).
When you start HiVision, if there is no entry for the network area to be
scanned, then HiVision enters the Class C subnetwork area, in which the
network management station is located.
As an alternative to the network area to be scanned, HiVision gives you

the option of searching for the devices in the device list. Under Confi
guration:Settings:Device list, you enter the IP addresses of
the agents for which HiVision should search after starting (see “Device
List” on page 81).
V Enter the communities for Snmp access to the agents in the Protocol
configuration window
(Configuration:Preferences:Protocol Configuration...):
public is the default read community and private is the default set
community.
Enter the IP address in the 'IP Address' field in the form x.x.x.x.
Each 'x' stands for a number from 0 to 255. The asterisk, used here as
the so-called 'wildcard', stands for any number from 0 to 255. If the IP
address of an agent is not entered explicitly in this dialog, then HiVision
proceeds with the settings in the *.*.*.* line.
The status symbols in the agent overview flash while HiVision is reading data
for these devices from the network.
U Specific feature for Windows Vista

Starting HiVision the Windows Firewall answers.
V Click „Unblock” to enable Hivision to query the devices duly.
HiVision
30 Release 6.4 06/07
Fig. 1: Vista Firewall release
V To be able to receive traps (see “Trap destinations of the agent” on

page 48) accept receiving traps in the Windows Firewall.
Therefore select Control Panel:Security.
Click "Allow a program through Windows Firewall” and select
"SNMP Trap”.
V To be able to use the HiVision telnet function enale the Windows
telnet client with Start:Control Panel:Software:Windows
components.
2.2.4 Updates
V Install HiVision according to “Installation” on page 28.
The new version of HiVision takes on the Preferences.xml file
(see “Program start” on page 29) of the earlier HiVision installation.
HiVision can take on the settings of an earlier HiVision installation before
release 6.0 if both HiVision installations are located on the same level of
the same root directory (e.g. C:\Program\Hirschmann).
You can deinstall an earlier version by following “Deinstallation” on
page 32.
When you are installing the OPC Server software, refer to “Installation” on
page 51.
HiVision
Release 6.4 06/07 31
2.2.5 Deinstallation
Note: The deinstallation maintains the directory

<installation path>/data/var. It contains the HiVision specific files
HiVision.key and the VLAN configurations (see “Program start” on page 29).
The user-specific files (see “Program start” on page 29) are also maintained.
V For deinstallation, select in the start menu:

Start:Programs:Hirschmann:HiVision 6.4 Toolbox:Dein
stallation of HiVision 6.4 Toolbox
Note: The license file HiVision key and other configuration files are remo-
ved by deleting the Hirschmann directory.
HiVision
32 Release 6.4 06/07
Installation 2.3 PC-StandAlone solution for Linux
2.3 PC-StandAlone solution for

Linux
2.3.1 Installation prerequisites

D Hardware
D Linux
Kernel from 2.2, libc6.1
D License for HiVision 6.4 (see “The HiVision program” on page 15, “Licen-
Installation of Linux is the responsibility of the user or system administrator.

GES-24TP Plus 2.1.4
HiVision
Release 6.4 06/07 33

MACH 3000 Rel. 3.1
MICE Rel. 3.0
BAT54-Rail Rel. 7.1
Note: If an earlier version of HiVision has been instaled, then

– deinstall it before the new installation,
– change the name of the directory /opt/HiVision (e.g. /opt/
HiVision61), so that it will not be overwritten during the new installation,
or
– move the directory /opt/HiVision to another location before the new
installation.
2.3.2 Installation
You require the administration rights on your network management station to
install HiVision.
V Logon as a super-user with: su.
V Mount CD on /cdrom with mount/cdrom.
V Change to the /cdrom/linux/ directory with

cd/cdrom/linux/↵
V Start the installation program with install.sh.

HiVision
34 Release 6.4 06/07
2.3.3 Program start

The following settings are nescessary to run HiVision:
V HiVision saves
specifically for every user, in the directory $HOME/.hivision
path to HiVision for these files on your network management station.
Therefore move the directory .hivision to this location.
V To receive traps, start the HiVision Trap Daemon as superuser:
/opt/HiVision/bin/hi_trapd.sh -s↵
V The Acrobat Reader acroread is needed to view the Online manual. Set
the environment variable PATH correspondingly.
V Enter the license key (see “License window” on page 59).
V Start HiVision by typing

/opt/HiVision/bin/hivision.sh↵
/opt/HiVision/bin/hivision.sh↵
followed by one or more parameters.
Parameter Meaning
image
HiVision
Release 6.4 06/07 35
V Select the language you require under Configuration:Preferenc

es:Language. Quit HiVision and restart it to put the language setting into
effect.
V Enter the network area to be scanned by HiVision under the

Configuration:Preferences:Scan Ranges.
With Edit:Scan for new Devices, HiVision searches for devices in
the entered address areas.
If no network area has been entered when HiVision is started, HiVision
automatically opens the "Prefrences" window. Enter the network area to
be scanned by HiVision.
V Enter the communities for Snmp access to the agents in the Control con-
figuration window
(Configuration:Preferences:Control Configuration...):
public is the default read community and service is the default write
community.
Enter the IP addresses of the agents in the 'IP Address' field in the form
x.x.x.x.
Each 'x' stands for a number from 0 to 255. The asterisk, used here as
the so-called 'wildcard', stands for any number from 0 to 255. If the IP
address of an agent is not entered explicitly in this dialog, then HiVision
proceeds with the settings in the *.*.*.* line.
The status symbols in the agent overview in the main window flash while
HiVision is reading in data for these devices from the network.
2.3.4 Updates
V If an earlier version of HiVision is installed, then
– deinstall it before the new installation, according to “Deinstallation” on
page 37
or
– move the directory /opt/HiViision to another location before the new
installation.
HiVision
36 Release 6.4 06/07
Read/write access to the root directory is required for deinstallation of
HiVision.
V Inside the directory /opt remove the directory HiVision

cd /opt↵
rm -rf HiVision↵
Note: In this process the license file and the VLAN configuration is removed
also.
HiVision
Release 6.4 06/07 37
Installation 2.4 Integration with HP OpenView for Windows
2.4 Integration with HP Open-

View for Windows

D Hardware
D Windows 2000/XP/2003 Server
D HP-OpenView V 5.0x, 6.0, 6.1, 6.2, 7.5
The user or system administrator is responsible for installation of HP Open-

View.

GES-24TP Plus 2.1.4
HiVision
38 Release 6.4 06/07

MACH 3000 Rel. 3.1
MICE Rel. 3.0
BAT54-Rail Rel. 7.1
2.4.2 Installation
V Insert the HiVision CD in drive.
If the set-up program does not start automatically, then you start it manu-
ally in the "Windows" directory of the HiVision CD.
V Select the language and follow the instructions in the installation program.
V Select HiVision for HP OpenView and, if required, the Demo-Switch

and HiControl (refer “OPC server under Windows” on page 50).

With release 5.1 and earlier releases, HiVision takes on the data when you
install the new release in the same target directory.
HiVision
Release 6.4 06/07 39
2.4.3 Program start

To be able to use all the HiVision functions, such as ICMP-Ping, you require
the administration rights on your network management station.
V HiVision saves
specifically for every user, in the directory
My documents\.hivision.
path to HiVision for these files on your network management station. You
click with the right mouse button on the My Computer symbol on your de-
sktop and select Properties:environment. In Variable you enter
the environment variable HIVISION_HOME and in Value you enter the
path. Then move the directory .hivision to this location.
V For HP OpenView, first execute ovstop and then ovstart. Then HP

OpenView displays the correct Hirschmann symbols after starting, and
the context menu contains the line Open Device.
V Start HiVision in HP OpenView via the menu item HiVision:Start.

To set an option, edit the /registration/C/
hivision_registration file in the OpenView installation directory.
The command call is then: Command -Shared $HIVISION_ROOT/
bin/OVwHiVision -<Parameter>".
Parameter Meaning
image
ReadOnlyOVw HiVision ist readonly mit einer readonly OpenView
Ansicht
HiVision
40 Release 6.4 06/07
In HP OpenView, the menu item HiVision contains the sub-items Start

and Open Device.
When you start HiVision, Open Device opens an agent. Otherwise
HiVision starts without opening the agent.

effect.
2.4.4 Updates
V Deinstall HiVision according to “Deinstallation” on page 41.
V For deinstallation, select in the start menu:
Start:Programs:Hirschmann:Deinstallation of HiVision
Toolbox
Note: The license file HiVision key and other configuration files are removed
by deleting the HiVision directory.
HiVision
Release 6.4 06/07 41
Installation 2.5 Integration in HP OpenView for HP-UX
2.5 Integration in HP OpenView

for HP-UX

D Hardware
HP Series 700
Memory : 128 MB or better, 256 MB (recommended)
D HP-UX Version 11.11 with
HP OpenView Network Node Manager Version 6.2 or later.
HP-UX is normally installed prior to delivery on the workstation. The version

concerned should be checked in all cases.
The user or system administrator is responsible for installation of HP Open-

View.
Before installing the HiVision, ensure that HP OpenView has been installed
with the Node Manager platform.

HiVision
42 Release 6.4 06/07

GES-24TP Plus 2.1.4
MACH 3000 Rel. 3.1
MICE Rel. 3.0
BAT54-Rail Rel. 7.1
Note: If an old version of HiVision is installed, then deinstall it before instal-

ling a new version.
2.5.2 Installation
If HP OpenView is active, it must be closed via File:Exit before starting
installation.
Read/write access to the root directory is required for installation of

HiVision.
The installation routine supposes that the environment variable $OV_BIN is

set. Be sure, that the Network Node Manager is started with
$OV_BIN/ovstatus.
V Mount the HiVision CD (in this case /cdrom)

mount /cdrom↵
V Install HiVision with the program “swinstall”. “swinstall” is part of “HP Soft-
ware Distributor”.
Start the program by typing
swinstall↵
Note: If the NNM is installed as part of a bundle, (e.g. ITO bundle, ITO-
EngOrzAll), an error message will be issued. It can be bypassed by swit-
ching off the option “Enforce Script Failures” in the menu Options.
HiVision
Release 6.4 06/07 43
V Enter the Source Depot Path:

/cdrom/HPUX/INSTALL/HIVISION.DEPOT.
V Select bundle HiVision.
V Execute action Install (analysis)É.
V On successful completion of the analysis phase, click “OK” for installation.
V Observe fault messages or warnings in the log window.
Without starting HP OpenView you may verify the installation with the aid of
the HP tool swverify.
V Start the program by typing

swverify HiVision↵
Note: If there is user-specific data from an earlier installation, then HiVision

copies it into the new version.
2.5.3 Program start

V HiVision saves
specifically for every user, in the directory $HOME/.hivision
path to HiVision for these files on your network management station.
Therefore move the directory .hivision to this location.
V The Acrobat Reader acroread is needed to view the Online manual. Set
the environment variable PATH correspondingly.
HiVision
44 Release 6.4 06/07
V For HP OpenView, first execute ovstop and then ovstart. Then HP

OpenView displays the correct Hirschmann symbols after starting, and
the context menu contains the line Open Device.
V Start HiVision in HP OpenView via the menu item HiVision:Start.

To set an option, edit the /registration/C/
hivision_registration file in the OpenView installation directory.
The command call is then: Command -Shared $HIVISION_ROOT/
bin/OVwHiVision.sh -<Parameter>".
Parameter Meaning
image
In HP OpenView, the menu item HiVision contains the sub-items Start

and Open Device.
When you start HiVision, Open Device opens an agent. Otherwise
HiVision starts without opening the agent.

effect.
HiVision
Release 6.4 06/07 45
2.5.4 Updates
V Deinstall HiVision according to “Deinstallation” on page 46.
Note: With Release 4.0 HiVision uses new device symbols. Delete symbols
of earlier releases in the shell.
If HP OpenView is active, it must be closed via File:Exit before starting
deinstallation.
Read/write access to the root directory is required for deinstallation of

HiVision.
Note: The deinstallation maintains the directory

/opt/HIVISION_ROOT/data/var. It contains your user specific files.
Archive these files at a secure place if you wish to install this version of
HiVision at a later time again.
V Deinstall HiVision with the program “swremove”. “swremove” is part of

“HP Software Distributor”.
Start the program by typing
swremove↵
V Select bundle HiVision.
V Execute the action Remove (analysis)É.
V On successful completion of the analysis phase, click “OK” for

deinstallation.
V Observe fault messages or warnings in the log window.
HiVision
46 Release 6.4 06/07
Note: After deinstallation, the vendor field of the OpenView database is still
set to Hirschmann.
Note: For deinstallation you always need the deinstallation program which
matches the installation program with the same version number.
HiVision
Release 6.4 06/07 47
Installation 2.6 Trap destinations of the agent
2.6 Trap destinations of the

agent
V Enter the IP-address of your management station as trap destination

address into the Hirschmann agent.
Example: Device agent
In the main window, click on the agent of your choice with the right
mouse button and select Agent Dialog in the context menu.
Select the Security tab page and click on Trap Destination in
the left frame.
Enter the IP address of your management station under IP
Address. Make a valid Community Index entry (see Community
Entry). Switch the status to valid in order to enable traps to be
sent to this IP address.
Examples: Multi Device Configuration
After selecting the desired agents in the main window, click the Multi
Device Configuration button on the tool bar.
Settings for all

agents
Function status
display
"Set" button
Fig. 2: Multi Device configuration
HiVision
48 Release 6.4 06/07
Installation 2.6 Trap destinations of the agent
Clicking the "Set" button transmits the configuration to the agents.

New settings overwrite existing settings in the agent that have the
same ID.
After the next scan, HiVision displays only those configuration set-
tings which all selected agents have in common.
Examples: ETHERNET Agent (MIKE, MultiMIKE)
−Enter trap destination address into the file mibadm2.ini

(refer to the manual of the Hirschmann agents).
−Entry via configuration file card:

Select configuration in the device window on the agent symbol
with the right-hand mouse key. Enter the trap destination
address in the card "Trap Destination" (with appropriate access
entitlement).
Display Meaning
Grey No message, e.g. no function has been started yet.
Red Action ended with error, e.g. due to incorrect Set Community.
Yellow, Action being carried out.
flashing
Green Action successfully completed.
Blue Action can not be carried out, e.g. because this action is not
implemented for the agent.
Table 10: Meanings for the function status display
HiVision
Release 6.4 06/07 49
Installation 2.7 OPC server under Windows
2.7 OPC server under Windows
OLE For Process Control (OPC) is a standardized interface for process data
management in the automation industry used for exchanging data objects
between applications. OPC is based on Microsoft’s Object Linking and Em-
bedding (OLE) method, which is widely known today as the Distributed Com-
ponent Object Model (DCOM).
The Hirschmann HiControl OPC Server is both an OPC Data Access server
and an OPC Alarm und Event server. In combination with the Windows 2000
or XP SNMP Trap Service it provides the SNMP Trap functions from certain
Hirschmann network components to the OPC Alarm und Event interface. In
connection with the HiVision network management software, HiControl pro-
vides a status display and a status updating facility for all network compon-
ents which can be managed by HiVision.
HiControl starts automatically after a request from an OPC client if HiControl

was selected in the installation proceeding.
You will find detailed information on the OPC server

D in the Windows/Datasheet_OPCServer.html file on the HiVision
CD-ROM or
D if you have already completed the standard installation of the OPC server,
under Windows: Start:Programs:Hirschmann:HiVision Rel.
XX Toolbox:HiControl :Specification.
Answers to the frequently asked questions, for example integration into pro-
cess visualization systems, can be found on Hirschmann’s Internet site (see
“Frequently asked questions” on page 244).
U OPC Data Access Specification

HiControl implements the OPC Data Access Specification Version 2.03.
HiControl provides device status interrogation and interrogation of the
cause of a status change for all devices managed by HiVision.
HiVision
50 Release 6.4 06/07
U OPC Alarm and Event Specification

HiControl implements the OPC Alarm and Event Specification
Version 1.01.
2.7.1 Installation
You usually install HiControl in conjunction with HiVision.
If you install it later, the procedure is the same as for the installation of
HiVision.
V Mark HiControl in the installation program.

If either HiVision or the demo-switch has been installed, then these lines
are also marked. If you remove these ticks, the programs are deinstalled.
If an earlier version of HiControl is installed on your computer, the instal-
lation program gives you the option of starting the deinstallation program
for the earlier version.
2.7.2 Updates
V Deinstall HiControl with the (de-)installation program with which you
installed it.
V Install HiControl according to “Installation” on page 51.
HiVision
Release 6.4 06/07 51
V For deinstallation, select from the start menu:
Start:Programs:Hirschmann:HiVision 6.4:(Un)Install
components.
V Remove the tick next to HiControl.
V Follow the instructions in the deinstallation program.
HiVision
52 Release 6.4 06/07
Overview of HiVision
3 Overview of HiVision
3.1 Function overview 56

3.1.1 Main window 56
3.1.2 Device window 57
3.1.3 Detail window 58
3.1.4 License window 59
3.2 Using HiVision 60

3.2.1 Requirements 60
3.2.2 Getting started with HiVision 61
HiVision
Release 6.4 06/07 53
HiVision
54 Release 6.4 06/07
This brief overview gives you the basics on the structure of the HiVision net-
work-management software - as well as the principles behind the application
philosophy.
HiVision
Release 6.4 06/07 55
Overview of HiVision 3.1 Function overview
3.1 Function overview
3.1.1 Main window

Once you start HiVision, the main window appears on the screen. It has four
main parts:
D menu bar,
D tool bar,
D card-index, which provides information on the entire network based on the
selected card,
D status bar.
For more information, see “"HiVision" main window” on page 65.
Menu bar
Tool bar
Card-index
Status bar
Bubble help
Column can be sorted by clicking
Fig. 3: Main window
HiVision
56 Release 6.4 06/07
U Using
– Column contents can be sorted by clicking the column heading
– Column width can be adjusted by dragging the column border
– Multiple selection with Ctrl and Shift like in Windows
– Bubble help can be called up depending on pointer location
– Search function via context menu with the right mouse button.
3.1.2 Device window

Double-clicking an SNMP-capable devices (default) row in the main window
(see Fig. 3) opens the associated device window (see “Device window” on
page 105).
Menu bar
Tool bar
Device card-index
Pop-up status display
- Display of
device functions
Status bar
Fig. 4: Device window with RS2 displayed
HiVision
Release 6.4 06/07 57
3.1.3 Detail window

Double-clicking a device detail in the device window (see Fig. 4) opens the
associated detail window (see “Detail window” on page 119).
Menu bar
Tool bar
Card-index
for
- Configuration
- Performance
- Faults
- Security
- Index
Status bar
Pop-up device status
Fig. 5: Detail window after double-clicking a port icon
HiVision
58 Release 6.4 06/07
3.1.4 License window

Selecting Configuration:Preferences:HiVision Licenses opens
the license window. Here you will find information on the existing licenses. To
enter a license, you quit HiVision and start the program "Enter license".
Green border: valid license

Red border: invalid license
Fig. 6: License window
HiVision
Release 6.4 06/07 59
Overview of HiVision 3.2 Using HiVision
3.2 Using HiVision
3.2.1 Requirements
HiVision requires:
D An existing network concept
D The completed hardware installation of the devices to be managed
D The completed base configuration (such as IP parameters) of the devices
to be managed, so that the network management station can communi-
cate with the agents of the devices
D The completed SNMP community assignment of the devices to be mana-
ged, so that the network management station also has access to the
agents
SNMP controls access permissions to the agents. Every SNMP agent
from Hirschmann has two tables:
- Community entries and
- Community access
The community entry table defines who can access the agents with write
and read permissions.
The community access table defines which computer, identified by IP
address, can be used to access the agents.
The Hirschmann agents have the following default configuration:
IP: *.*.*.*, which means that every computer can be used to access
the agents.
Read permission with the public community
Write permission with the service or private community
Note: The network management station must be given write permission

in the agent itself! Otherwise it will not be able to make any changes to the
agent.
Note: Protect your agents against unauthorized access by changing the

default access permissions. Make a note of your changes and keep in a
safe place.
HiVision
60 Release 6.4 06/07
3.2.2 Getting started with HiVision

HiVision saves a configuration file for each HiVision user (My documents
directory) in the .hivision directory.
If the HiVision program is opened repeatedly by one user at any one time,
then these sessions access the same configuration file. This can lead to un-
definable content in the configuration file.
U Scan Ranges, Device List (Stand-alone)

V Enter the IP-address range in which HiVision should search for agents
in Configuration:Preferences:Scan. You can start the scan
procedure by selecting Edit:Rescan Range.
As an alternative to the network area to be scanned, HiVision
enables you to search for devices from the device list.
Under Configuration:Settings:Device list you enter the
IP addresses of the agents which you want HiVision to search for after
starting (see “Device List” on page 81).
U PSM configuration
If you are not using GRS in your network, you can speed up the start pro-
cess for HiVision.
V Select Configuration:Preferences:PSMs.
V Select the line GRS in the left column and click on the field with the ar-
row pointing to the right.
V Click on Apply.
U SNMP access permission

V Check the SNMP configuration under Configuration:Prefe
rences:Protocol Configuration.
Note: HiVision can only manage those agents that are displayed in this
window (see Fig. 7) with valid read and write permissions.
HiVision
Release 6.4 06/07 61
Write community
Read community
IP address of the agent that these
communities can access.
Fig. 7: Protocol configuration
U Device configuration
V In the detail window, configure the individual devices according to your
network concept. The Port Manager function enables you to configure
the ports for all the devices in one window.
U Network monitoring
V To customize your network monitoring, set the parameters for status
propagation, RMON threshold value, link monitoring, etc.
HiVision
62 Release 6.4 06/07
U Network availability
Make sure to evaluate the following when network problems occur:
– Status propagation
The status propagation lets you track problems as far as the detail level.
The pop-up information gives you the quickest overview of the most
important situations.
– Statistics (see also “Port Analyzer” on page 85)

The statistics can help you detect network problems before they occur,
based on information such as a growing number of collisions, packet
errors, etc.
– Traps
The event messages are triggered right after an event occurs, enabling
the network administrator to act immediately.
HiVision
Release 6.4 06/07 63
HiVision
64 Release 6.4 06/07
"HiVision" main window
4 "HiVision" main window
4.1 Menu bar 67

4.1.1 Preferences 69
4.1.2 Licenses 75
4.1.3 Status configuration 76
4.1.4 Status propagation 77
4.1.5 Agent Polling 80
4.1.6 Network configuration 80
4.1.7 Assignment of MAC/IP address 82
4.1.8 Locate MAC Address 82
4.1.9 Port Manager/Port Analyzer 83
4.1.11Telnet window 88
4.2 Tool bar 89
4.3 Card index 91

4.3.1 Agent overview 92
4.3.2 Events 96
4.3.3 Event actions 100
4.3.4 VLAN Manager 102
4.4 Status line 103

4.4.1 Status messages 103
4.4.2 Symbol area 104
HiVision
Release 6.4 06/07 65
"HiVision" main window
The main window appears on the screen when HiVision is started. It consists
of four parts:
D the menu bar
D the tool bar
D the card index, which provides information to the whole network with re-
spect to the selected cardfile
D the status line
Menu bar
Tool bar
Card-index
Status bar
Bubble help
Column can be sorted by clicking
Fig. 8: Main window
HiVision
66 Release 6.4 06/07
"HiVision" main window 4.1 Menu bar
4.1 Menu bar
The menu bar is right at the top of the main window. It facilitates overall ope-
ration of HiVision. The main feature is the setting of the configuration and the
view selection. Overall operation also includes programming and license ad-
ministration not to mention quitting HiVision.
The menu bar has the following structure

File
Print...
Export...
Exit
Edit
Rescan1
Rescan Range...1
Stop scanning1
Add Device...1
Delete Device...
Device Description...
Agent Dialog
Update Device
Update MAC Address table
Multi Device Configuration...
Multi-Port-Manager
Multi-Port-Analyzer
Show Events
Acknowledge Events
Delete Events
Simulate Events
Acknoledge all Events
Delete all Wvents
Properties...
Delete all Events
View
Polling...
Address Resolution Table...
Product Families...
Locate MAC Address
1. All StandAlone solutions
HiVision
Release 6.4 06/07 67
Configuration
Port Status Configuration...
Interface Status Configuration...
PowerSupply Status Configuration...
Fan Status Configuration...
Relais Status Configuration...
ACA Status Configuration...
Router Status Configuration...
Chassis Status Configuration...
Protocol Status Configutaion...
Preferences...
Tools
Ping1
Telnet
Web Interface
SNMP Browser
VLAN-Manager
Clear...
Import stations
Rescan agents
Reload MAC tables
Guess uplink...
Agent list...
Agent properties
New...
Delete
Edit...
Clone...
Mgnt stations...
Analysis
Save
Load
Disable VLANS...
Traps...
Windows
Help
Program Info
Commandline Parameters
Release Notes...
Tutorials...
HiVision on the Web...
Technical Support
HiVision Manual
1. All StandAlone solutions
HiVision
68 Release 6.4 06/07
4.1.1 Preferences
The Configuration:Preferences dialog allows you to enter default set-
tings for the operation of HiVision.
Setting Description
Scan Ranges (see “Scan Range” on page 80)
Agent List (see “Device List” on page 81)
Protocol Configuration (see “SNMP access permission” on page 61)
Event Dialog Default setting for the event categories displayed when you
open an event window.
Event Actions (see “Event actions” on page 100)
Event Log (see “Protocol file” on page 99)
Mail (see “Mail” on page 71)
SMS (see “Short Message Service (SMS)” on page 70)
Ext. Applications Dialog for HiVision access to external programs
PSMs (see “Creating a PSM” on page 193)
Agenten Handling Dialog for setting the scope of the data that HiVision calls up
from the agent (see “Device Handling” on page 72).
Look & Feel (see “Look & Feel” on page 73)
Language HiVision offers you an American or German interface. If you
change the language setting, it becomes effective when you
restart HiVision.
Security (see “Security” on page 74)
HiVision Licenses (see “Licenses” on page 75)
Service Information for specialists carrying out service work.
Table 11: List of the default setting dialogs
HiVision saves the default settings specifically for every user in the
Preferences.xml file, in the directory
$HOME/.hivision.(Linux),
C:\WINNT\Profiles\user\My documents\.hivision (Windows NT)
or My documents\.hivision (Windows 2000/XP/Vista/2003 Server see
“Program start” on page 29).
HiVision
Release 6.4 06/07 69
U Short Message Service (SMS)

By defining event actions, you can get HiVision to carry out actions when
specific events occur. One of these actions is sending short messages
(SMS). Under Configuration:Preferences:SMS you enter the
SMS parameters that HiVision passes on to the SMS program, SMScom,
to send an SMS.
A precondition for this function is that your network management station
must be connected to the telephone network, e.g. via a modem.
Fig. 9: Setting the SMS parameters
V Click on Configure at the top right of the SMS dialog.

V Select the Services available tab page in the modem configura-
tion window that opens up
V Select a pre-defined service or define a new one.
Close the modem configuration window with OK, and enter the name
of the service in the Service Name field in the SMS dialog.
V Enter the telephone numbers of the SMS recipients in the SMS reci
pient 1-4 fields.
HiVision
70 Release 6.4 06/07
V If you enter the telephone number of your modem in the SMS sender
field, it is sent along with the message. Thus you can identify HiVision
as the sender in your mobile telephone display.
V If you mark the Log Errors field, then HiVision records in a log file
any errors occurring when SMSs are sent.
V With Apply HiVision saves the settings.
U Mail
By defining event actions you can get HiVision to carry out actions when
specific events occur. One of these actions is sending e-Mails. Under
Configuration:Preferences:Mail you enter the e-Mail parame-
ters that HiVision passes on to the e-Mail program to send an e-Mail.
Fig. 10: Setting the e-Mail parameters
HiVision
Release 6.4 06/07 71
U Device Handling
With this dialog you can specify the scope of the data that HiVision calls
up from the device, and how this data will be processed.
D DNS - Domain Name Service
"Resolve Hostnames via DNS" gets HiVision to call up the host names
of the detected devices from the Domain Name Server, and to display
them in a separate column of the main window. Because calling up a
Domain Name Server is usually very time-consuming, this slows down
the starting process of HiVision considerably. In the default setting,
therefore, DNS is deactivated.
D Manage Unknown Agents
Unknown agents are displayed in the main window and can be mana-
ged. Otherwise, HiVision discards all the data of unknown agents.
D Manage ping-devices
Non-SNMP-capable devices appear in the main window, and they can
be managed.
D Show Unknown Agents
Unknown agents are displayed in the main window when Manage
Unknown Agents is marked. With Show Unknown Agents you set
the default setting in the View:Product Families to unknown.
D Load MAC Tables on startup
Read the Forwarding Database (FDB) from all the agents with FDB on
starting HiVision.
Independently of this setting, HiVision automatically reads the FDB
when you open a device window, and a button in the tool bar allows
you to read in the FDB at any time.
D Remove permanently
When you are deleting a device in the main window with Edit:Remo
ve device, a confirmation window appears. This confirmation win-
dow opens with "Remove permanently" already marked as the default
option.
D IpNetToMedia-Tabellen beim Start laden
lesen der ARP-Cache-Information aus der IpNetToMedia-Tabelle aller
Agenten beim Start von HiVision.
D Edit Traps
Evaluate traps received and display the result, e.g. status change, in
the windows.
D Index Page First
Place the index page at the start of the card index.
D Show Protocol Column
Displays the protocol column in the device overview in the main
window.
HiVision
72 Release 6.4 06/07
D Device symbols blink during data collection

The status symbols in the agent overview of the main window flash
while HiVision is reading in data for this device from the network.
D System status source in OVw
HiVision automatically passes on the status detected to the manage-
ment platform. Remove the check to stop the status being passed on.
D Creating an agent after a trap
If HiVision receives a trap from an agent not listed in the main window,
then depending on this setting, the agent
– can continue not to be listed in the main window,
– can be listed in the main window, or
– can be listed in the main window if its IP address is within the scan-
ning area.
D Action carried out if the device is double-clicked in the main window
Specifies the action to be carried out if an agent in the main window is
double-clicked. This setting is only available if you click with the right
mouse button on an agent in the main window and select Set
tings:Double-click action.
U Look & Feel

With this dialog you can alter the interface layout of HiVision. In addition
to a number of layout characteristics, you can specify whether HiVision
displays the start window when you start it up:
D GUI Style.
D Font size.
D Font name.
D Logical table column separators.
D Welcome Window.
D SNMP Activity Animation.
D Shade table columns.
D Show "Freeze" button. Freeze enables you to open a window a num-
ber of times.
D "Freeze" button default value: default value for the Freeze check box
when it is shown in an open window.
D Show line numbers in main device list
Displays the column of line numbers in the device overview in the main
window.
D Show line numbers in event dialog
Displays the column of line numbers in the event lists.
D Search all columns
Selects the "All" default in the search dialog.
HiVision
Release 6.4 06/07 73
D Show ping warning message

To carry out the Ping function, you need administrator rights on your
network management station. If Ping can not be carried out, HiVision
sends a warning message.
D Group dialogs, e.g.
grouped not grouped
configuration
– load locally load configuration locally
– load remotely load configuration remotely
– save locally save configuration locally
– save remotely save configuration remotely
U Security
The Security setting allows you to operate HiVision in observation mode.
In the observation mode, HiVision only read accesses agents.
V Mark "Read Only".
V Click on OK to save the setting in the preferences file. The setting is
now effective.
To return to the normal operating mode from the observation mode, you
require write access to the preferences file.
V Mark "Read Only".
V Click on OK to save the setting in the preferences file. The setting is
now effective.
HiVision
74 Release 6.4 06/07
4.1.2 Licenses
In normal HiVision mode, the license window under Configuration:Pre
ferences:HiVision Licenses is read-only.
U Windows versions U Unix versions

V In order to edit the license win- V In order to edit the license win-
dow, first quit HiVision and then dow, first quit HiVision and then
log yourself in as administrator start HiVision as superuser with
at the management station with the option -L.
write entitlements
V Start the HiVision license dialog HiVsion for HPUX and Open-
from the start menu: View:
Start:Program:Hirsch /opt/HiVision/bin/OVw
mann:HiVision:Edit Li HiVision -L
cense HiVsion for Linux:
/opt/HiVision/bin/HiVi
sion -L
The license window is opened.
Note: When a license key is edited, the appropriate field is highlighted in red.
On correct entry of the last character of the license key, the background color
changes from red to green.
Note: Each different HiVision release requires a different license key.
HiVision
Release 6.4 06/07 75
4.1.3 Status configuration

These menu items under configuration are for setting the configurations for
all the devices for:
D Port Status Configuration,
D Interface Status Configuration,
D PowerSupply Status Configuration,
D Fan Status Configuration,
D Relay Status Configuration,
D ACA Status Configuration,
Status of the AutoConfiguration Adapters ACA 11.
D Router Status Configuration,
D Chassis Status Configuration,
D Protocol Status Configuration.
This means that the settings are transferred to all devices listed in the main
window. This applies to both selected as well as non-selected devices.
The Configuration window displays all parameters that can be set in any de-
vice that can be displayed in the window. Devices that only support a limited
number of parameters ignore the remaining parameters.
You can set shared status configurations for certain ports of different devices
in the multi-port manager (see “Port Manager/Port Analyzer” on page 83).
HiVision
76 Release 6.4 06/07
4.1.4 Status propagation

Status propagation specifies the color with which the selected object will be
marked.
Color Evaluation of Status

red Error
yellow Warning
green OK
blue unknown
Table 12: Color assignment for the possible conditions
Just how a status is evaluated is set in the configuration menu. These confi-
guration settings apply for the surface in which they are activated.
A configuration setting made

D in the main window applies for the whole surface (see “Status configura-
tion” on page 76).
D in the device window applies for the whole device.
D in the detail window applies for the selected detail.
D on one level applies for all lower levels,
D when the field “overwrite” is checked.
Settings can be made for individual ports, interfaces or an interface card by

means of the context menu (see page 120).
D The most recently set configuration supercedes the previous settings.
D A blue colored text line indicates a completed alteration.
D The arrow pointing down to the right in the left-hand window section
D indicates that the settings have been adopted by the higher level.
D The blue dot in the left-hand window section indicates that alterations
have been made on this level (see Fig.1).
HiVision
Release 6.4 06/07 77
Fig. 11: Setting the status configuration
The most critical status color in each case is forwarded to the next highest
level. If for example, the status color of a port is red, then the status symbol
of the device, to which this port belongs, is also displayed in red. If the status
symbol is yellow or red, then the bubble help displays the reason for this
status. The bubble help contains the causes of error/warning conditions
within the device. Here HiVision takes into account all the levels right down
to the detail level.
The bubble help for this object shows:

D which configuration settings are relevant for an object,
D the current status of the object, which is reported to the management
station.
Fig. 12: Port status propagation
HiVision
78 Release 6.4 06/07
Example: A terminal device is directly linked to a port of the MACK 3000 via
a TP cable.
When the terminal device is switched off, the port of the MACH 3000 identi-
fies a link error. The status of the link error is error . If the evaluation
error has been assigned in the configuration menu, then the port is presen-
ted in the color red (see Fig. 12).
Since a deactivated terminal device does not as a rule represent a serious
fault, a network administrator may less pay attention to this event. Therefore
he may assign the status link error an evaluation free to his choice. If he
assigns the evaluation Warning to the status link error the port will
get yellow when the terminal device is switched off.
U Status propagation with the MACH 3000

Every basic board of a MACH 3000 has its own agent. Along with the
status of the basic boards, its modules and ports, it also monitors the sta-
tus of the fan and the power supply units in the housing. Thus the fan
and the power supply units are monitored repeatedly.
Because the status color of the configuration for status propagation
depends on the agent, the status display of the same fan or power sup-
ply can be different from agent to agent.
The multi-agent in the clickable area of the device window takes the
most critical status color from all the agents of the MACH 3000. This sta-
tus color is sent on to the main window.
On the Physical Structure tab page you can monitor the status propaga-
tion (see Fig. 12).
U Status propagation to the management shell

HiVision automatically passes on the status to the management platform.
Remove the check on System Status Source in OVw
(Change Status Source in OVw) in the Configuration:Set
tings:Agent Handling dialog of HiVision to stop the status being
passed on.
HiVision
Release 6.4 06/07 79
4.1.5 Agent Polling

The management station regularly interrogates the ICMP and if available the
SNMP capability of administered devices. Polling prevents a device falsely
appearing to be error-free when the SNMP link to the management station
is interrupted.
U Polling with the StandAlone version

The polling parameter is set under
Configuration:Preferences:SNMP Configuration.
U Polling with a platform-integrated version

The polling parameters are set with the platform menu Options:SNMP
Configuration.
4.1.6 Network configuration

HiVision supports two principles for selecting the agents to be administered:
U Scan Range
The Configuration:Preferences:Scan Ranges dialog allows
you to set the IP address range that HiVision scans in the connected net-
work.
Mark "Scan the network during program start" to query the entire network
for agents in the IP address area when HiVision is started.
D "New" defines a new IP address area.
D "Duplicate“ creates a copy of a marked IP address area.
D With "Edit" you change the marked IP address area.
D With "Delete" you delete the marked table entry.
HiVision
80 Release 6.4 06/07
For devices detected by HiVision by means of the scanning function,

HiVision always displays the actual device type in the type column. In
contrast to this, the device list (see “Device List” on page 81) enables
you to reduce the display and the interogation to the "Ping" type.
Note: If the agent list is active, then HiVision additionally queries the
agents entered in the agent list during the program start.
U Device List
Saving the IP addresses found in the device list under Configura
tion:Preferences:Device List makes it possible for HiVision to
look specifically for these addresses after HiVision is restarted. This
makes HiVision start faster. Devices that are not found in the network,
although they are in the device list, are displayed in red. In the status line
HiVision displays the successfull loading of the device list.
The Configuration:Preferences:Device List dialog allows
you to enter devices in this list, and to remove them.
With the "left" arrow key you add the devices marked in the "Discovered
devices" list to the device list.
With the "right" arrow key you remove the devices marked from the
device list.
With the "Ping device" arrow key you add the devices marked in the "Dis-
covered devices" list to the device list as Ping devices.
With "Add device" you enter an IP address, which HiVision puts into the
device list.
Mark "Load device list on startup", to query the entire network for the
devices in the device list when starting HiVision.
Note: If the scanning areas are active, HiVision additionally queries the
devices in the IP address areas on startup.
HiVision
Release 6.4 06/07 81
4.1.7 Assignment of MAC/IP address

This menu item allows you to assign a MAC address to an IP address. HiVi-
sion carries out the assignment in the main window using the ARP caches of
the agents. The ARP cache contains only the addresses with which the agent
actively communicates. This usually means the management station. In con-
trast to the ARP cache, the forwarding database holds all the MAC addresses
transmitted by the switch of an agent. Because a router or gateway commu-
nicates on the IP level, all the addresses it transmits are also contained in its
ARP cache.
Note: If a router or gateway is displayed in the agent window, you are provi-
ded with a fairly comprehensive list.
V Select View:Address Resolution Table.
You click on the column header to sort the table contents.
You will find further assignment options:

D in the detail window for the agent, under Security,
D in the detail window for the port, under Security,
D in the bubble help for a port in the device window,
D in the physical structure of the device window.
4.1.8 Locate MAC Address

This menu item helps you find certain MAC addresses.
V On the "Agents" filecard, select all agents or the agents to which you think
the devices with the MAC addresses you are looking for are connected.
V Click on "Update MAC address table". If you have marked "Load agent list
on startup" under Configuration:Preferences:Agent Handling,
then HiVision has already loaded the MAC addresses.
HiVision
82 Release 6.4 06/07
V In the menu bar, select View:Locate MAC Address.

A window shows the contents of the agent’s Forwarding Database Table,
provided it supports the MIB according to RFC 1493.
V Click on MAC Address in the header line to sort the table by MAC
addresses.
Click the right-hand mousekey on the headline to open a search-window.
4.1.9 Port Manager/Port Analyzer

With the port manager and port analyzer functions you can
D enter shared settings for a number of ports simultaneously
or
D monitor the counter values of a number of ports simultaneously.
The ports can be shared by a number of devices. The ports of a device can
belong to different port groups.
V Mark
D the devices in the main window whose ports you want to group toge-
ther or
D the ports in the device window that you want to group together.
V Select Edit:Multi-Port-Manager or Edit:Multi-Port-Analy

zer in the menu bar.
A window displays a table with all the ports of the marked devices.
V With the menu item View:Remove Port, you can remove ports from the
list. When you open this window again, the ports appear again.
V To add more ports to the table, click on a table field with the right mouse
button and select Add Port in the context menu or click on a port in
a device window and pull it into the multi-port manager or multi-port
analyzer window.
HiVision
Release 6.4 06/07 83
V To move between the port manager and the port analyzer,

– mark the ports you require,
– click on a table field with the right mouse button and
– select Port-Manager/Port-Analyzer in the context menu.
U Port Manager
The port manager allows you to enter the same settings for a number of
ports, even for all the devices, in one step.
V Mark the lines in which you want to enter settings.
V In the selection fields to the left of the table, select the settings you
wish to apply to all the lines marked.
V When you click on "Set" in the tool bar, HiVision sends the new set-
tings to the agents. You can change these settings individually at a la-
ter date with another port selection in the port manager, or per port in
the detail window.
Application example:
In the default setting of the port status configuration, the condition color
green is assigned to the condition symbol for a connection error.
This setting is logical if there is a terminal device connected to a port.
If there are connections to switches or hubs, then a connection error
represents a serious error, which must be treated as such.
Select the ports in the device window and click on "Port manager" in the
tool bar.
Mark the ports in the Port Manager window and select Configura
tion:Port Status Configuration in the menu bar.
Check the "Link" box and select the red condition symbol for the "Error"
condition. Click on "Accept" and then "OK".
With "Set" you transfer the settings to the agent. Click on "Start" to carry
out the transfer and on "Save" to save the settings permanently on the
agent.
HiVision
84 Release 6.4 06/07
U Port Analyzer
In the port analyzer window you will find a table of the selected ports. It
contains the counter contents for
– Performance,
– Collisions and
– CRC errors.
Devices Performance Collisions CRC Errors

GRS yes yes yes
MACH 1000 yes yes yes
GLS yes yes yes
MICE yes yes yes
MS20/MS30 yes yes yes
RS2-../.. yes yes yes
RS20/RS30/Rs40 yes yes yes
OCTOPUS yes yes yes
FES/GES yes yes yes
ETS yes yes yes
MR 8-03 yes – –
ESTP6 yes – –
MIKE – – –
Multi-MIKE – – –
FCMA – – –
FEH – – –
ETH – – –
Table 13: Counters available in the table for each device
V In the Type selection window, you specify which counter values are
displayed in the table.
V Click on Polling Interval to specify the interval at which the port analy-
zer queries the counter values.
The small interval shows in seconds the time interval at which the port
analyzer queries all the counters, with the exception of the collision
counter. The length of the small interval depends on the amount of
data to be queried. Because a query process can take a number of se-
conds, the value should be set at a minimum of 5 seconds.
The big interval shows in seconds the time interval at which the port
HiVision
Release 6.4 06/07 85
analyzer queries the collision counter. Because collisions rarely occur

during normal operation, errors only become apparent after a longer
observation period. The big interval is an even multiple of the small in-
terval and is obtained by multiplying the small interval by the polling
factor.
V With Reset you set the counters in this port analyzer window to 0. If
you have a second port analyzer window open that contains a port
from the first window, then resetting the counters in the first window
has no effect on the second window.
Every port analyzer window you open begins with the counters set to
0.
The counter contents provide the expert with information about the struc-
ture of the network and allow him/her to detect any errors in the configu-
ration.
Example: Two connected devices have different port configurations.

Device A is configured with 100 MBit/s and full duplex, and device B with
100 MBit/s and half duplex. This will inevitably lead to collisions and late
collisions in device B. Typical counter values are above 2 in a thousand.
Since device A is working in full duplex mode, it detects CRC or align-
ment errors (ALE) instead of the collisions. These errors become visible
only after a longer observation period of more than 30 minutes and
amount to just a few per cent.
The port analyzer allows you to monitor a number of ports within an

SNMP monitor window.
V Click with the right mouse button in the field whose content you want
displayed in the SNMP monitor and select Monitor variable in the
context window.
If you want to display a number of fields in a column in this SNMP mo-
nitor window, you select the lines and click with the right mouse button
in a selected field of this column. Select Monitor variable for
all selected Ports in the context menu.
V Click with the right mouse button in any field and select Variables
to monitor in the contxt menu. Click on "SNMP Monitor" in the va-
riables to be recorded.
HiVision
86 Release 6.4 06/07
4.1.10 Multi-device configuration

The multi-device configuration enables you to configure a number of devices
at the same time with the same settings (see the example “Trap destinations
of the agent” on page 48).
The range of configuration options available depends on the devices selec-
ted. If you have only selected devices of the same type (MACH 3000, MICE
or RS2), then HiVision enables you to configure device-specific settings.
With multi-device configuration, you can also load and save configurations in
the devices and carry out a software update.
The status column provides information on the success of the action carried
out:
D Green light:
Action successfully completed.
D Red light:
Action failed. The speech bubble help provides information on the cause
of the failure. With the "Repeat failed action" key, you can start the action
again after resolving the error. In this case, HiVision starts the action for
the devices for which the action failed.
D Blue light:
The device does not support the action.
Repeat
failed
action
Fig. 13: Example of multi-device configuration
HiVision
Release 6.4 06/07 87
4.1.11 Telnet window

When a device symbol or in the device window, HiVision sets up a Telnet link
to the selected device with Tool:Telnet.
Fig. 14: Example of terminal settings with Windows NT
HiVision
88 Release 6.4 06/07
"HiVision" main window 4.2 Tool bar
4.2 Tool bar
The tool bar is located just below the menu bar. It is provided to simplify ope-
ration. The tool bar makes it unnecessary to open the various windows in or-
der to obtain a particular view.
List of functions in the tool bar:
File:Exit,
HiVision can also be exited by pressing the 'ESC' key.
File:Print... (with Windows)
File:Export...
s equivalent to double clicking the selected line in the device list and
opens the device window with detailed information on the device. This
tool is useful where several lines have been simultaneously selected
Edit:Multi Device Configuration...
Edit:Update Selected Agents
Edit:Update MAC Address table. This causes the forwarding-

database to be re-read from the switch.
Edit:Delete Selected Events
Edit:Acknowledge Events
Edit:Stop scanning
HiVision
Release 6.4 06/07 89
"HiVision" main window 4.2 Tool bar
View:Product Families
Edit:Port-Manager
Edit:Port-Analyzer
Tools:Telnet
Tools:Web Interface
VLAN Manager:Load...
VLAN Manager:Save...
VLAN Manager:New...
VLAN Manager:Delete...
User groups:Duplicate...
VLAN Manager:Edit...
Help: Online Manual, Manual (prerequisite is the previously com-

pleted installation of the Adobe Acrobat Reader 3.0)
Help:Program Info...
HiVision
90 Release 6.4 06/07
"HiVision" main window 4.3 Card index
4.3 Card index
The card index contains three (four) filecards:

D Agent overview
D Events
D VLAN Manager
D SyntaxChecker, if you started HiVision with a command-line parameter
(see “Testing PSM” on page 238 und Help:Commandline parameter)
U Multiple selection
Selection of several devices, which follow one another directly in the list:
V Select the first required device.
V Select the last required device with pressed shift key.
=>All devices which are between these two devices in the list, are sel-
ected. Previously made selections are cancelled.
Selection of individual devices from previously made selections:
V Select an individual device with pressed Ctrl key.
=>Changing the selection status of this device. Previously made
selections remain unchanged.
U Variable column width

Pressing the left mouse key when on a column line makes it possible to
alter the column width.
HiVision
Release 6.4 06/07 91
4.3.1 Agent overview

This card provides a rapid overview of devices with ICMP/SNMP agents for
the whole network.
While starting in the StandAlone version HiVision displays the following
devices:
D the devices of the agent list or
D the devices which are found from polling the agents of the network
configuration.
In the platform-integrated version, HiVision adopts the symbols for the

agents from the platform. Thus HiVision also displays devices which cannot
be addressed during the program start.
Use the context menu for to view details on the individual devices. To open
the context menu, click the device line with your right mouse button.
U Device selection
The Edit menu item allows you to
D Add devices by entering the IP address (Add Agent).
D Add devices by querying the active address range again (Rescan).
D Add devices by scanning an IP address range (Rescan Range).
D Remove selected devices (Delete Device). HiVision deletes the
data set stored for this device.
Changes in the agent window have no effect on the event table (see
“Events” on page 96) and the agent list (see “Device List” on page 81).
HiVision
92 Release 6.4 06/07
U Column topic
Click the column heading once and the card contents are sorted accor-
ding to column topic.
Column Meaning
Type Product family:
Industrial Line
Backbone Switch
Workgroup Switch
ETHERNET Hub
FDDI Hub
Rack Monitor
Ping device
Unknown
Status Device status (see “Status propagation” on page 77)
P Protocols to which the device responds. When you position the mouse poin-
ter on a symbol, a bubble displays details.
ICMP: device responds to Ping
SNMP: device responds to SNMP queries

E Event display (see “Events” on page 96).
The pink bell indicates that more than one event has occurred.
The symbol for an event category indicates that an event of this cateogy has
occurred.
The grey bell indicates that no event has occurred, or that events that have
occurred have already been acknowledged.
L The HiVision program consists of a core program and one or two modules.
Each of the two modules supports a defined group of devices. A module is
enabled by means of a valid license key.
An "x" in this column indicates that a valid license key is installed for the
module that supports this device.
M If HiVision is integrated into HP OpenView, then the agent overview also
includes the column "M"
In the management platforms, HP OpenView can be assigned to an object
with the "unmanaged" status. If there is no "x" in this column, then the agent
is assigned the "unmanaged" status, and the status symbol appears in blue.
IP Addresse IP address of the agent
Table 14: Column description of the agent overview
HiVision
Release 6.4 06/07 93
Column Meaning
Product Product identifier or content of the MIB Variable System Description.
System Location Location of the device, any entry may be made.
System Name Name for identifying the device, any entry may be made.
Special Infos Overview of more detailed information.
SW Version Software version of the agent currently running.
Table 14: Column description of the agent overview
Note: If the product field for a device is empty then it is likely that
− the access right is not unique (e.g. no SNMP community).
the first device in the device list which does not have the "unknown"
type in the device list is administered by HiVision even without a licence.
− the agent of the device is not licensed or
− the version number of the agent is not supported (see readme file).
Information is provided by the bubble help when the mouse pointer is

positioned over the status symbol for the device.
If the status symbol is yellow or red, then the speech bubble help dis-
plays the cause of this status. The speech bubble contains the causes
for error/warning conditions in the device. Here HiVision takes into
account all the levels right down to the detail level.
U Search
The search function allows you to quickly find specific devices, IP
addresses etc.
You click with the right mouse button on a table field to open the applica-
ble context menu.
HiVision
94 Release 6.4 06/07
U Inclusion of non-SNMP-capable devices

HiVision also displays non-SNMP-capable devices whose IP addresses
are within the scanning area. You can recognise these devices by
– the "non-SNMP-capable device" symbol: .
HiVision first checks the device accessibility via SNMP. If a device is not
accessible via SNMP, then HiVision tries to access the device via ICMP.
With Edit:Add Device you can add non-SNMP-capable devices to
the device list. If you select Non-SNMP in the type field, then HiVision
assigns the "non-SNMP-capable device" symbol to this device.
U Device properties
V Click with the right mouse button on the line of the device, or on a num-
ber of marked devices, to open the relevant context menu. Select
Preferences.
D The "Device info“ tab page allows you to enter the content for the
device list.
D The "Protocols" tab page enables you to read and change the SNMP
parameter default values set by HiVision.
D The "Double-click action“ tab page enables you to select the action
which is called up by a double-click on the agent line. Example: with
the Web browser option for devices which have Web-based man-
agement, a double-click on the agent line opens the Web-based man-
agement screen directly.
For non-SNMP-capable devices, HiVision sets the default value to
Web browser.
Application example for assigning product name:

V Mark all Rail VIP devices in the main window.
V Click with the right mouse button on a marked line and select
Preferences.
V Enter the "R-VIP" product name.
HiVision
Release 6.4 06/07 95
4.3.2 Events
This filecard shows
D all traps received from the management station
D inconsistancies in the network that HiVision detects with the aid of SNMP
queries
D information about the program execution of HiVision
HiVision evaluates the table entries and displays the effects in the individual
windows.
If the Log function is activated (see “Log files” on page 104) HiVision adds an
event entry to the protocol file as soon as it occurs.
U Event categories
In the list above the table you can mark specific event categories so that
they are not displayed in the table. HiVision still registers the event cate-
gories not displayed.
Symbol Category Meaning

Trap An alarm message has been received from
an agent.
Availability The availability of an agent has changed.
SNMP Error An SNMP PDU has been received whose

error status indicates an error.
Status Change The status of a device has been changed.
Application Info Information on the HiVision application run-

ning, e.g. HiVision has started.
Application Alert Some HiVision application is not running
correctly, e.g. SMS function has failed. The
administrator must intervene.
Configuration Change Configuration settings for HiVision have
been changed.
Internal Info Information for a service task.
Table 15: Event categories
HiVision
96 Release 6.4 06/07
U Table properties
D You click on the column header to sort the tab card contents in terms
of column subject.
D If you click with the right mouse button in a table field, you open a con-
text menu with search functions.
D You can delete selected entries by means of the recycle bin in the tool
bar.
D You can acknowledge selected entries by means of the bell in the tool
bar. HiVision displays acknowledged entries colourlessly in the
"Agents" tab card.
D You can simulate receiving an event again by selecting the entry in the
table and choosing Edit:Simulate Event. This function allows you
to test your event actions (see “Event actions” on page 100).
D The Edit menu item provides you with the following table-editing
functions:
– acknowledge selected events
– delete selected events
– acknowledge all events
– delete all events
– simulate receiving the selected event again
HiVision
Release 6.4 06/07 97
U Table contents
For every event that occurs, HiVision enters a line in this table. Depen-
ding on the category selection, the event lines are either displayed or
invisible.
HiVision allows you to query (polling) device details regularly (see “Detail
polling” on page 129). The polling is active if there is an arrow next to the
symbol.
Column Meaning
Ack A tick here indicates that the user has confirmed this
entry.
Time Time the event ocurred in year/month/day/hour/minute/
second format plus a counter for events occuring within
the same second.
Cat Category the event belongs to.
Source Device causing the event message.
Component Device component causing the event message.
Message Name of the event.
Description Description of the event.
Table 16: Column description for the event table
U Setting of the event display

The Configuration:Preferences:Event Dialog dialog allows
you to specify which event categories an event window displays on ope-
ning.
HiVision
98 Release 6.4 06/07
U Protocol file
The Configuration:Preferences:Event Log dialog allows you to
D activate/deactivate the recording of all events in a file.
D change the default file name. HiVision completes the file name auto-
matically with the addition of .log.
D specify the maximum number of protocol entries per file. If the current
protocol file contains the maximum number of entries, then HiVision
sets up a new file. HiVision completes the file name with a counter
number. Example: HiViLog01.log, HiViLog02.log, etc.
D specify the maximum hard disc space the protocol files can use.
You can open the protocol file with Microsoft Excel or a text editor.
HiVision
Release 6.4 06/07 99
4.3.3 Event actions

The "Event Actions" dialog allows you to define actions for HiVision to carry
out when a particular event occurs. You will find this dialog in the main win-
dow under Configuration:Preferences:Event Actions.
V Click on "New" or copy an existing entry to define a new action.
V Click on "Clone". A window shows you a list of the events that have oc-
curred up to this point. Select the event you want and click on "OK". HiVi-
sion then automatically fills in the event definition fields in this window.
If the event you want is missing from the list, then fill in the fields
– Catagory,
– Source,
– Component,
– Message and
– Description
For this you must know the exact text message. If you enter "Wildcards"
(* and ?), you reduce the possibility of errors.
"Wildcards" also allows you to define an action for several events. If you
enter, for example, Port * for the component, then the event triggers the
action at all the ports of this source.
D Active
Mark this field if you want HiVision to carry out this action when the
event occurs.
D Category
In the selection window, select the event category that will trigger the
action.
D Source
In the selection window, select the source (HiVision or the IP address
of an agent) from which the event message will be received.
D Component
Enter the component (e.g. agent, module 1, port 2) that relates to the
event.
D Message
Enter the object ID and the object identifier of the required event, or
select a text from the selection window in this line.
D Description
Enter the description of the event. This is usually the description text
of the MIB variables.
HiVision
100 Release 6.4 06/07
V In the following you specify the action to be carried out when the event
message is received.
D Action
Select the action from the selection field. The selection consists of:
– Sending SMS messages
– Sending e-mails
– Opening the information window on the network management stati-
on
– Executing a system command
D Action Message
Enter the message to be contained in, for example, an e-mail you want
to send. The bubble help shows you a variable you can include when
sending the mail.
Example:
"At $TIME, the $CATEGORY appeared in the $SOURCE."
D Timeout
Enter the time after which HiVision should stop trying to carry out the
action.
D Retries
Specify how often the timeout can occur before HiVision stops attemp-
ting to carry out the action.
D Allowing for the time period of an action
It takes a certain amount of time to carry out an action. For example,
sending an e-mail via the selection process takes considerably longer
than opening an information window.
If the same event recurs within the time period for an action, an error
message is generated.
By clicking on this field you avoid this error message. However, you do
not receive any information as to whether this event has occurred wi-
thin this action time period.
Responses from an external application, such as the confirmation of a suc-

cessfully sent SMS, are evaluated by the HiVision stand-alone versions in
the event action.
HiVision
Release 6.4 06/07 101
4.3.4 VLAN Manager

The VLAN Manager filecard enables you to configure VLANs. For a detailed
description of the VLAN-Manager, see “VLAN manager” on page 147.
HiVision
102 Release 6.4 06/07
"HiVision" main window 4.4 Status line
4.4 Status line
The status line at the bottom of the main window is divided into two areas:
D Status messages
D Symbol area
Status messages Symbol area
Fig. 15: Status line
4.4.1 Status messages

The status messages are shown on the left side of the status line. They show
the current HiVision processes.
HiVision
Release 6.4 06/07 103
"HiVision" main window 4.4 Status line
4.4.2 Symbol area
Note: When the mouse pointer is positioned over a symbol, a bubble help
with an explanation of this symbol appears.
U Data transmission
The symbols provide information about the data transmission (traps and
SNMP queries) between agents and HiVision.
Note: When the lightning bolt in the trap symbol in the StandAlone version
is crossed out, then start the Trapdaemon (see “Program start” on page
29 and “Program start” on page 35).
U Platform change
With platform-integrated versions, an additional symbol makes it possi-
ble to change over directly to the platform.
U Log files
The colored display of this symbol indicates that events are saved in a
protocol file as they occur (see “Protocol file” on page 99.
HiVision
104 Release 6.4 06/07
Device window
5 Device window
5.1 Tool bar 108
5.2 Image 110

5.2.2 Subdevice buttons 111
5.3 Physical Map 113
5.4 Logical Map 115
5.5 Device information 116
5.6 Events 117
5.7 Index 118
HiVision
Release 6.4 06/07 105
Device window
When a device line is double-clicked in the main window, the associated de-
vice window opens with the accompanying ip address and, if available, the
device name in the head line.
In the managment shell there are additional possibilities to open the device
window of a selected device:
D select HiVision:OpenDevice in the menu bar or
D select HiVision:OpenDevice with the right-hand mouse button in the
context menu.
Note: If a device still does not appear in the main window of HiVision during
initialization, an earlier entry can be induced via the management shell. To
do so open the device window on the platform level with HiVision:Open
Device in the context menu for the symbol.
In the context menu the line HiVision:OpenDevice is missing, if the shell
has not identified the device as Hirschmann agent yet. To speed up identifi-
cation close HP OpenView / IBM NetView and enter the following lines:
ovstop↵
ovstart ovwdb↵
ovw -fields¿
ovstart ovtopmd↵
ovtopofix -u↵
ovstart↵
Restart HP OpenView.
The device window consists of a menu line, the tool bar, a card index with
five cards and the status line. The card index has 6 cards:
D Image
D Physical map
D Logical map (for unknown agents, MIKE and MultiMIKE agents)
D Device info
D Events
HiVision
106 Release 6.4 06/07
Device window
The status line is highlighted with the symbol on the right. The color and
the term show the status of the whole device:
Ok
Warning
Error
Note: The states of the symbols are determined when the device window is
opened.
The content of a device window is updated:
− when the interface cards equipment is changed
− after View:Reload
− when a trap with content which affects the symbol color is received.
– when the MAC address table is reloaded.
HiVision
Release 6.4 06/07 107
Device window 5.1 Tool bar
5.1 Tool bar
List of functions in the tool bar:
File:Exit, closes the window
File:Print...
File:Export...
Edit:Update MAC Addresstable, reads in the forwarding data-

base of the switch.
Edit:Port-Manager.
Edit:Port-Analyzer.
Edit:Delete Selected Events
View:Set, data transmission to the agent
View:Reload
HiVision
108 Release 6.4 06/07
Device window 5.1 Tool bar
Configuration:Port Status Configuration...
Configuration:Interface Status Configuration...
Configuration:Power supply Status Configuration...
Configuration:Fan Status Configuration...
Configuration:Device Status Configuration...
Configuration:Relais Status Configuration...
ACA:AutoConfiguration Adapter Status

Configuration...
Configuration:Protocol Status Configuration...
Tools:Telnet...
Tools:Web Interface

HiVision
Release 6.4 06/07 109
Device window 5.2 Image
5.2 Image
The filecard “image” shows a representation of the corresponding device with

its actual setup. The card is subdivided into two areas:
D the device image
D the subdevice buttons
5.2.1 Device image

The device image shows the gray scale image of the relevant image with its
current equipment.
U Color symbols
The ports are overlayed color symbols. The status of the port is indicated
by the color as well as the form of the symbol:
nothing is connected to this port
this port is switched off
a single device is connected to this port
this port is linked to several devices

“MAC addresses” on page 113.
The significance of each color corresponds to the color assignment (see

Table 12 on page 77) .
HiVision
110 Release 6.4 06/07
U Bubble help
When the mouse pointer is positioned on certain device parts, the asso-
ciated bubble help appears. It contains the most important status infor-
mation.
5.2.2 Subdevice buttons

The subdevice buttons below the device image show symbols for parts of the
device, which may not be visible from the front of the device.
U Colored border
The symbols have colored borders.
The significance of each color corresponds to the color assginment (see
Table 12 on page 77) .
U Bubble help
mation.
The bubble help for the symbol indicates the logical, physical and
SNMP states.
U Net number
“all” is the default. This means that all possible colored symbols are
superimposed at the ports on the device image.
Note: When a particular net number is selected, then symbols are just su-
perimposed on those ports associated with the selected net number.
HiVision
Release 6.4 06/07 111
Note: The net number function is supported by ETS-12/24TP/M,

ETPS-22TP/M and all AMC devices. With all other devices, the setting
“all” is required to display the colored symbols.
HiVision
112 Release 6.4 06/07
Device window 5.3 Physical Map
5.3 Physical Map
This index card shows a representation of the physical device in tree struc-
ture. It enables the cause of a status change to be identified.
Example: A link error occurs at a twisted pair port. Thereupon the status
symbol of the affected device goes red. A quick glance in the map shows im-
mediately which port is causing the status propagation.
U Bubble help
ciated speech bubble appears. It contains the most important status
information.
SNMP states.
U MAC addresses
The MAC addresses are listed in addition to the port symbols. These
MAC addresses are associated with the devices, which are connected to
this port. If several devices are connected to one port, then the number
of devices connected appears in this field. You will obtain a list of all
MAC addresses by selecting “Security” with the right-hand mousekey on
the port (see page 120).
Special case TYDE and IYDE: The MAC addresses of all attached
devices are displayed at Port 1.
HiVision
Release 6.4 06/07 113
Device window 5.3 Physical Map
U IP addresses
The MAC- and IP-addresses are listed in addition to the port symbols.
These addresses are associated with the devices, which are connected
to this port. If several devices are connected to one port, then three dots
appear in this field. You will obtain a list of all addresses by selecting
“Security” with the right-hand mousekey on the port (see page 120).
In assigning MAC address to IP address, HiVision uses the IpNetToMe-
dia entries of the IP MIB on the agents in the network. You activate this
function by marking Load ipNetToMedia Tables on startup
under Configuration:Preferences:Agent Handling.
U Net number (with Agent MIKE/MultiMIKE)

The display and setting option for the net number assignment is located
next to the addresses. You will require a community with write-entitle-
ment to change the net number assignment.
HiVision
114 Release 6.4 06/07
Device window 5.4 Logical Map
5.4 Logical Map
This card represents the logical design of unknown agents, MIKE and Multi-
MIKE agents. The assignment of port to interface is immediately recognizab-
le. HiVision fetches RMON 1 (Statistics) and 2 (History) at the interface level.
U Bubble help
mation.
SNMP states.
HiVision
Release 6.4 06/07 115
Device window 5.5 Device information
5.5 Device information
The filecard indicates the configuration of the agent.
“Reload”: reloading from the agent MIB and updating the display
“Set”: fields with a white background can be edited. “Set” writes the
indicated values into the MIB of the agent.
HiVision
116 Release 6.4 06/07
Device window 5.6 Events
5.6 Events
The card shows the events for this agent. You will find more information on
the event window under “Events” on page 96.
HiVision
Release 6.4 06/07 117
Device window 5.7 Index
5.7 Index
The Index tab page allows you to find detailed information quickly that is
made available by the device window.
U Subject table
When you have found the term you want in the subject table, you can
double click on this line to go directly to the tab page of the device
window containing this term.
U Searching for a term

You enter the term in the search field and click on "Next match". When
HiVision finds the term in the table, HiVision marks the applicable line in
the table. If the line found does not meet your requirements, you click on
"Next match".
HiVision
118 Release 6.4 06/07
Detail window
6 Detail window
6.1 Tool bar 121
6.2 Information presentation 123

6.2.1 SNMP monitor 124
6.2.2 RMON function 126
6.2.3 Detail polling 129
6.2.4 Rack Monitoring System 130
6.3 Configuration settings 131

6.3.1 Filter settings of the RMS 131
6.3.2 Switch configuration 133
6.3.3 Router configuration 137
6.3.4 Redundant routers 139
6.4 Index 145
HiVision
Release 6.4 06/07 119
Detail window
Detail windows can be opened within the device window (image, physical
structure and logical structure cards) or at interface-card level, port level and
interface level or with an agent, chassis, power supply unit, fan or AutoCon-
figuration Adapter symbol. A drop-down menu is opened with the right hand
mousekey on a device detail. The selection of the required topic opens the
appropriate detail window.
Depending on the device detail, the following topics are available:

D Configuration
D Performance
D Fault
D Security
D Events
D Index
D Polling
Each topic represents a card index in the detail window. If a detail window is
open, then it is possible to switch directly to the next topic via the card
selection.
When a detail window is opened, HiVision polls the current values at the
agent. Attributes not supported by the agent are displayed by HiVision in red.
HiVision
120 Release 6.4 06/07
Detail window 6.1 Tool bar
6.1 Tool bar
List of functions in the tool bar list:
File:Exit, closes the window
File:Print... (with Windows)
File:Export...
Edit:Update MAC Address table. This causes the forwarding

database to be re-read from the switch.
View:Set, data transmission to the agent
View:Reload
View:Restart actions that finished with errors.
Graphical or tabular presentation of selected counters in the SNMP

monitor
Properties of a table entry
HiVision
Release 6.4 06/07 121
Detail window 6.1 Tool bar
Recreate table entry
Delete selected table entry
Stop loading procedure for a table
Tools:Telnet...
Configuration:Device Status Configuration...
Configuration:Power supply Status Configuration...
Configuration:Fan Status Configuration...
Configuration:Port Status Configuration...
Configuration:(ACA:)AutoConfiguration Adapter Sta

tus Configuration
Configuration:Relais Status Configuration...
Configuration:Router Status Configuration...
Configuration:Polling configuration...

HiVision
122 Release 6.4 06/07
Detail window 6.2 Information presentation
6.2 Information presentation
You receive detailed information of the device at all levels, e.g. agents, chas-
sis, card, port, power supply and fan level.
For this the Hirschmann agents put a whole series of counters and tables.
This allows an analysis of network events down to the layer 1 of the ISO/OSI
base reference model. The extensive configuration possibilities permit an in-
dividual customization to your own network environment.
Fig. 16: Example for the display of a fault counter
Depending on the window from which you start, by double-clicking on a table

line you open a dialog window for editing the individual table values.
HiVision
Release 6.4 06/07 123
6.2.1 SNMP monitor

A graphical representation of the counter values makes it easier to interpret
the values.
V Select the desired variables to be graphically displayed in the port window

of either the "Performance" or "Fault" card .
V Click "Grapher" in the tool bar.
U Setting
Under Edit:PreferencesÉ you will find entry fields for the:
– Log to file
– Path name of a log file
– Polling interval. When starting the Grapher, it accepts the value that
has been set under
Configuration:SNMP Configuration
– Duration of the data storage.
U Representation
The SNMP monitor provides the table values. The following display
options are available:
– Line diagram or bar diagramm,
– Pie chart and
– Table.
In the line/bar diagram you can change the horizontal scale with Zoom
in and Zoom out. To enlarge the scale, click the scroll bar at the top or
bottom and drag it in a vertical direction.
Note: HiVision offers this Grapher function in the PC stand-alone version. To

use this Grapher with a platform-integrated version, mark the appropriate
field in the Configuration:Preferences:Service dialog.
HiVision
124 Release 6.4 06/07
Fig. 17: Example for the display of the performance on port level with
graphic representation (platform version)
U Log files
The Grapher offers three methods for creating log files:
D File:SaveÉ saves the table contents as a text file.
D Edit:Copy copies the table contents onto the (Clipboard).
D Edit:Preferences writes the table values to the log file on an on-
going basis.
HiVision
Release 6.4 06/07 125
6.2.2 RMON function

So that information can also be presented by non-Hirschmann devices,
HiVision supports parts of the standardized RMON Management Information
Base.
1 iso
3 org
6 dod
1 internet
4 pr
2 mgmt
1 mib-2
16 rmon
1 statistics
2 history
3 alarm
9 event
Fig. 18: Tree structure of the RMON-MIB
Polling with RMON 1 and 2 always takes place at a device interface. HiVision
presents device interfaces of Hirschmann switches in the "Physical struc-
ture". For all other agents, the device interface is presented in the “logical
structure” in the device window (see “Logical Map” on page 115). Switches
directly link interface and port. RMON 1 and 2 are therefore also available at
port level.
Configuration of alarms and eventsfor any variables (RMON 3 and 9) takes
place at agent level.
HiVision
126 Release 6.4 06/07
Hinweis: In order to make RMON 2, 3 and 9 functions available, you will re-
quire write entitlement for the agent.
U Example of generation of an alarm with assistance from

RMON
In the following example, the temperature of a MACH 3000 should be
monitored. As the MACH 3000 is being operated in a very warm environ-
ment, the monitoring of the temperature is very important. Therefore, an
alarm should indicate when the threshold temperature specified has
been exceeded.
Starting from the device window, selecting "Security" in the context menu
of the agent symbol opens the agent window.
The choice of an RMON alarm in the filecard Security indicates the adju-
stable parameters (see Fig. 19).
The "Chassis" window is opened by selecting "Configuration" from the

context menu of the chassis symbol in the device window. The MIB
variable can be entered simply by moving from "Temperature Upper
Limit" to the 'MIB Variable' field of the agent window with the mouse but-
ton pressed (drag and drop).
The MIB variable for the upper temperature limit is (see Chap. 6, MACH
3000 manual): hmTempUprLimit.0 or
1.3.6.1.4.1.248.14.2.5.2.0.
The sampling rate can be adjusted with a sliding controller.
When the status is “active”, the alarm is activated with View:Set.
HiVision
Release 6.4 06/07 127
Fig. 19: Setting an RMON alarm
HiVision
128 Release 6.4 06/07
6.2.3 Detail polling

Detail polling allows the following statuses to be polled on a regular basis:
– Port status
– Power supply status
– Fan status
– Housing status
– Relay status and
– Statuses of symbols for device functions defined in the PSMs.
During the polling process, HiVision polls all the information required for cal-
culating the status. With the RS2, the variables AdminState, LinkError
and Standby/RedundancyManager, for example, are queried. These in-
formations are displayed in the event window on detail level.
V To activate/deactivate and set the polling interval, select Configurati

on:Polling ConfigurationÉin the Detail window
HiVision saves this configuration immediately afterward and reloads its
when the program is restarted.
The "Event" card in the device window lists the status changes. Apart from
the message indicating which result led to the change in status, HiVision also
stamps the time of the change.
For an overview of all active detail pollings, go to View:PollingÉin the

main window.
This table displays:
– The current status,
– The worst status to date (similar to a peak level indicator)
– The IP address of the polling target,
– The function type
– The polling detail and
– The polling interval.
By double-clicking a line in the table, you will be taken directly to the "Event"
card of the polling target.
You can tell whether detail polling has been activated according to what ap-
pears in the "E" column. In addition to the symbol (arrow around the symbol),
the speech bubble help for the symbol also provides information.
HiVision
Release 6.4 06/07 129
6.2.4 Rack Monitoring System

The Rack Monitoring System employs a two-dimensional array to represent
the sensors. The action View: Reload updates the values in the "sensors"
file card.
The proper representation of the sensor symbol depends on the name of the
sensor. To name a sensor, click the physical structure of a sensor with the
right mouse button and select "Configuration".
HiVision expects the following character sequence
door: door contact
ups: uninterruptable power supply
smoke: flue gas detector
vibration:vibration detector
Example of a name for a flue gas detector: "Smoke in storage space" or
"Storage space smoke".
HiVision
130 Release 6.4 06/07
Detail window 6.3 Configuration settings
6.3 Configuration settings
6.3.1 Filter settings of the RMS

The filter settings can be accessed via the context menu of a Rack Monitoring
System agent. Using the right mouse button, click the agent symbol within
the physical structure and select 'configuration'. The RMS offers 12 filter
options.
Example: If temperature sensor 3 measures more than 40°C, then a trap

should be sent.
Procedure:
V Click Filter in the left-hand list
V Double-click a filter option (e.g., 12). The Filter window will open.
V Change the appropriate settings in the Filter window.
Fig. 20: RMS filter settings
HiVision
Release 6.4 06/07 131
V Close the Filter window with "OK"

V Click Filter Temperature in the left-hand list.
V Double-click the line Filter Index 12, Sensor 3. The Filter
Temperature window will open.
V Change the appropriate settings in Filter Temperature
Fig. 21: RMS Filter condition
V Close Filter Temperature window with 'OK'
HiVision
132 Release 6.4 06/07
6.3.2 Switch configuration

The starting point for setting bridge/switch parameters is the device window
for a bridge or switch.
To open the configuration detail window, click an agent icon with the right
mouse button and select Configuration in the shortcut menu.
U HIPER-Ring
Before you start configuring a HIPER-Ring you specify
D all the switches in the HIPER-Ring
D the ringports of the individual switches
D the switch that assumes the redundancy manager function. A single
active redundancy manager (RM) controls the HIPER-Ring function in
a HIPER-Ring.
Device Ringport 1 Ringport 2 Ringport RM activated

configured by by means of
means of
MACH 1000 any any Software Software
MACH 3000 Port 1 of module 1 of any Software Software
the basic board in slot
1
MACH 4000 any any Software Software
MICE 1 2 or 5 DIP switch DIP switch
MS20 Port 1 of module 1 or Port 2 of module 1, DIP switch or soft- DIP switch or
any with software port 1 of module 2 or ware software
configuration any with software
configuration
MS30 Port 1 of Port 2 of module 1, DIP switch or soft- DIP switch or
Power MICE module 1 or 2 port 2 of module 2 or ware software
or any with software any with software
configuration configuration
RS2 Port with the highest Port with the highest – DIP switch
port number minus 1 port number
RS20/RS30/ Port 1 or any with Port 1 or any with Software DIP switch or
RS40 software configuration software configuration software
OCTOPUS any any Software Software
Table 17: Configuration options for the HIPER-Ring of the devices
HiVision
Release 6.4 06/07 133
Example: Configuring the HIPER-Ring on a MACH 3000

V Open the device window of the MACH 3000.
V Click with the right mouse button on the agent symbol of slot (board) 1.
V Select Configuration in the context menu. The agent configuration win-
dow opens.
V Click on HIPER-Ring in the left selection field.
V If an entry already exists in the HIPER-Ring dialog, then double-click
on this line. Otherwise, select Edit:New to make an entry.
Fig. 22: Configuring the HIPER-Ring
V Enter the required information:
Setting Meaning
Mode create, to make an entry.
Red. board Slot number of the redundant port
Red. port Port number of the redundant port in the format module.port.
Table 18: Settings for the HIPER-Ring
HiVision
134 Release 6.4 06/07
V With OK you enter the values in the table.

V To define the redundancy manager function, double-click on the entry
in the table.
V In the Mode field, select
delete - to delete the entry from the table
rm - for the redundancy manager
rs - for the redundant switch with the redundancy manager function
switched off.
V With OK you complete the configuration of the HIPER-Ring on this de-
vice.
U Link aggregation (MACH 3000)

V You first define a link aggregation on the agent level under
Agent:Configuration:Link Aggregation. With a double click
on a line of the link aggregation table, you open a dialog for entering
the name of this connection.
V You define on port level by marking the port assignation to the link ag-
gregation with Port:Configuration:Link Aggregation.
Repeat this procedure for each port that should be assigned to the link
aggregation.
U Dual homing (MACH 3000)

The left half of the configuration detail window contains the option list for
the possible configuration parameters.
V Select "Dual Homing". The dual-homing parameters appear on the
right side of the window.
V Click the "New" button on the tool bar. The window for creating a dual-
homing entry appears.
V Enter a real, existing board and a real, existing port for the main con-
nection (Prim.).
V Enter a real, existing board and a real, existing port for the redundant
connection (Red.).
V Enter a value of 0 for the PortRevivalDelay parameter, or a value
greater than 60000 with Spanning Tree active, or greater than 10000
with Spanning Tree deactivated.
V Click on Set to enter this configuration in the table.
HiVision
Release 6.4 06/07 135
U GARP (MACH 3000)

The line Priority Port GARP is located in the selection list in the left
half of the Configuration Detail window. This line is for setting the para-
meters of the Generic Attribute Registration Protocols.
With the help of these parameters the experienced network administrator
can influence how often GARP data packets are sent in large networks.
In most cases, the default values provide a reliable exchange of VLAN
data between the MACH 3000 devices.
The default values are:
– Join time: 20
– Leave time: 60
– Leave all time: 1000
U GVRP - GARP VLAN Registration Protocol (MACH 3000)

The line Switching General is located in the selection list in the left
half of the Configuration Detail window. This line is for activating and
deactivating the GARP VLAN Registration Protocol. This protocol des-
cribes the distribution of VLAN information to other switches. This makes
it possible for switches to learn the information of other VLANs. If the
VLAN information is to be distributed to neighboring devices, the GVRPs
must be activated globallly.
V Proceed by selecting enable für GVRP Status on the right side of
the Configuration Detail window.
V To activate GVRP really select additionaly in the port window VLAN
Port the GVRP Status.
U GMRP – GARP Multicast Registration Protocol

The line Switching General is located in the selection list in the left -
half of the Configuration Detail window. This line is for activating and
deactivating the GMRP. The GARP Multicast Registration Protocol
(GMRP) describes how multicast information is distributed to other swit-
ches. This makes it possible for switches to learn multicast adresses.
When entering a multicast address in the statistical address table, the
switch sends this information to all ports. Connected switches learn how
to forward this multicast address to this switch.
V Proceed by selecting enable for GMRP Status on the right side of
the Configuration Detail window .
V To activate GMRP really select additionaly in the port window GMRP.
HiVision
136 Release 6.4 06/07
6.3.3 Router configuration

The "Configuration" tab page of the router detail window allows you to display
and configure the routing functions of the HiVision.
U General
This dialog is for displaying general parameters and for setting the TTL
(time to live). The ICMP TTL Exceeded parameter enables you to
prevent this message from being sent (disable).
Entering a DHCP server IP address activates the BOOTP/DHCP relay
agent. It allows you to work mit BOOTP/DHCP across IP subnet
boundaries.
U IP Interfaces
This dialog allows you to configure the IP interfaces of the router.
D Index: serial number for the identification of an interface.
D Name: name of your choice for an interface.
D IP adress: IP address of the interface.
D Network mask: network mask for the network with which the inter-
face is connected.
D Vlan ID: assignment to a VLAN.
D Admin Status: switch (on/off) for the interface.
D Oper Status: operating status of the interface. If there is no router
module, then there are no ticks in this column.
Note: Agent and router interfaces have their own individual IP addresses.
By means of a router, the agent is accessible from other subnetworks. A
pre-condition of this is that the interface of the routers must be connected
to the subnetwork of the agent (IP interfaces). Thus the router can forward
data packets from other subnetworks to the agent.
If for security reasons you want to protect the agent from being accessed
from other subnetworks, then allocate to the agent a subnetwork not con-
nected to any interface of the router module. In this case, the Gateway
entry is no longer valid for the agent.
Note: The subnetwork of the router interface and the PPP settings must
not overlap.
HiVision
Release 6.4 06/07 137
Note: If you intend to set up a router redundancy, you will have the option
of entering the table contents of the "IP Interface" dialog in the "Router
Redundancy" dialog. HiVision then accepts the entries made in the "Rou-
ter Redundancy" dialog in the "IP Interfaces" dialog.
U ARP Table
As with every other terminal device, the router obtains the IP addresses
within the connected (sub)networks with the aid of the Address Resolu-
tion Protocol (ARP).
The ARP table contains the allocation of MAC address to IP address and
provides space for up to 8192 (2048) ARP entries.
The Third column enables you to assign a type to entries in this table.
D other: unknown type.
D invalid: with a click on Write you delete this entry.
D dynamic: the age of this entry is monitored continuously, and it can
be changed by means of routing protocols. This entry is deleted when
you restart, or 10 minutes after the last transmission to this address.
D static: this entry is not subject of age monitoring and is no longer
available after a restart.
U Routing table
The entries in the routing table specify to which IP interface a received
data packet is sent.
An entry in the current routing table consists of:

D Route Destination, an IP destination address (host route) or a
subnetwork address (network route).
D IF No, number of the interface (MIB-II ifIndex) with which the IP de-
stination address can be reached.
D Mask. The subnetwork mask for a host route is: 255.255.255.255.
D Gateway, the IP address of the next router/gateway located on the
route to the target address.
D Metric1, the number of intermediate stations on the way to the target
address.
– 0: the target can be reached directly via a router interface.
– 1: there is at least 1 gateway on the way to the target.
– 2: there are at least 2 gateways on the way to the target.
– etc.
HiVision
138 Release 6.4 06/07
D Type, the type description in accordance with MIB II.

– other: unknown type
– invalid: with a click on Write you delete this entry.
– direct: the target computer is connected directly to the MACH 3000.
– indirect: the target computer is not connected directly to the MACH
3000, but is reached via a gateway.
D Age, shows how long the entry has been in the table.
An entry in the static routing table consists of:

D Destination, a manually entered IP target address (host route) or a
subnetwork address (network route).
D Netmask, a manually entered subnetwork mask. The subnetwork
mask for a host entry is: 255.255.255.255.
D Gateway, the manually entered IP address of the next router/gateway
located on the route to the target address.
D Name, the name of your choice for this route.
The static routing table supports up to 256 entries for network routes,
and up to 1024 entries for host routes.
When the routing interface receives a data packet, the router module first
looks in the routing table for an entry with the host IP target address. If
this entry does not exist, then the router module looks for an entry with
the network mask. The last opportunity for transmitting the data packet is
to send it to the IP address entered as a default gateway. If this entry
does not exist either, then the data packet is not transmittable, and the
sender is informed of this via ICMP.
6.3.4 Redundant routers

The Hirschmann Router Redundancy Protocol (HiRRP) allows you switch
two routers in parallel. If both routers are ready for operation, then they both
transmit with the same priority. If you enter the default gateway address in
the end device, this determines the transmission route. If one of the routers
fails, the remaining router completely takes over the tasks of the other one.
You will find an example of this function in the MACH 3000 handbook,
section 5.7.4.
HiVision
Release 6.4 06/07 139
You enter the settings for the router redundancy in the detail window of the
router. With a double-click on the router module in the device window you
enter the "Configuration" detail window.
V "General" dialog
Carry out a general router configuration (see “General” on page 137).
With "Set" HiVision transfers the settings to the agent.
V "Router Static Table" dialog

Make entries in the "Static routing table" (see “Routing table” on page
138). With "Set" HiVision transfers the settings to the agent.
V "Router Redundancy" dialog:

D Enter IP address of the partner routers in the Router 2 field.
Click on "Reload Router 2". HiVision
- reads the router configuration of router 2,
- compares it with the configuration of router 1,
- establishes the differences between router 1 and router 2 and
- displays the differences in the comment field.
D Switch on router redundancy.
D Router interface table:
If there are entries in the table of the "IP Interfaces" dialog, then
HiVision displays them in the router interface table of the "Router
Redundancy" dialog. Make the desired entries in the table or complete
the existing ones.
If the partner router (router 2) already has entries in this table, then you
can click on "Match" for an automatic matching of the two tables. After
this, the tables on both routers have the same entries. Check the ent-
ries after the matching.
If the router static tables are different, then you can transfer the entries
from router 1 to router 2 by marking the line Transfer static
routes from Router 1 to Router 2.
D With "Set" you transfer the entries to the agents of router 1 and
router 2. Click on "Start" to carry out the transfer, and on "Save" to
save the entries permanently on the agents.
Note: A requirement of the router redundancy function is that the router

modules are installed in a MACH 3001 or on a basis board with a serial
number greater than 943 679 300 ... .
HiVision
140 Release 6.4 06/07
U Application example:
The following example shows the main components and settings for cor-
rectly configuring the HiRRP function.
Subnet 2 Subnet 4
149.218.20.xyz 149.218.30.xyz
149.218.20.13 149.218.30.13
Router 1 Router 2
Router/Switch 149.218.10.101 149.218.10.201 RouterSwitch
MACH 3002 MACH 3002
Fig. 23: Example of a simple HiRRP configuration
HiVision
Release 6.4 06/07 141
Fig. 24: Settings for a simple HiRRP configuration
HiVision
142 Release 6.4 06/07
IP address: 149.218.20.13
Subnet mask:255.255.255.0
Default Gateway: 149.218.20.1
SN 2
Switch VLAN Yellow

MACH 3002
= SN 3
SN 1 VLAN Green
Router 2
MACH 3002
Router/Switch
RouterSwitch
MACH 3002
Router 1
IP address: 149.218.30.13
Subnet mask:255.255.255.0
Default Gateway: 149.218.30.1
VLAN Blue
Switch = SN 4
MACH 3002
SN = Subnet
Fig. 25: Example of a HiRRP configuration in the HIPER-Ring
HiVision
Release 6.4 06/07 143
Setting Router 1 Router 2

Agent setting
IP address 149.218.10.101 149.218.10.201
Subnetmask 255.255.255.0 255.255.255.0
VLAN White White
Default Gateway 149.218.10.xyz 149.218.10.xyz
Redundant Router 149.218.10.201 149.218.10.101
Redundant Router Interface 1001 149.218.20.2 149.218.20.1
Redundant Router Interface 1002 149.218.30.2 149.218.30.1
Router Interface for Subnet 2 149.218.20.1 149.218.20.2

Index 1001 1001
Subnetmask 255.255.255.0 255.255.255.0
VLAN Green Green
Router Interface for Subnet 4 149.218.30.1 149.218.30.2

Index 1002 1002
Subnetmask 255.255.255.0 255.255.255.0
VLAN Blue Blue
Table 19: Router-Einstellungen zu vorhergehendem Beispiel
HiVision
144 Release 6.4 06/07
Detail window 6.4 Index
6.4 Index
The Index tab page allows you to find detailed information quickly that is
made available by the device window.
U Subject table
When you have found the term you want in the subject table, you can
double click on this line to go directly to the tab page of the device
window containing this term.
U Searching for a term

You enter the term in the search field and click on "Next match". When
HiVision finds the term in the table, HiVision marks the applicable line in
the table. If the line found does not meet your requirements, you click on
"Next match".
HiVision
Release 6.4 06/07 145
Detail window 6.4 Index
HiVision
146 Release 6.4 06/07
VLAN manager
7 VLAN manager
7.1 The function of the VLAN manager 149

7.1.1 Advantages of the VLAN manager 149
7.1.2 Configuration types 149
7.1.3 Data entry elements 151
7.1.4 The network management station as a user 153
7.2 Port-based VLANs 154

7.3 MAC-based VLANs 163

7.3.3 Creating stations 167
7.3.6 Saving the configuration in a file 173
7.3.7 Testing the configuration 174
7.4 VLAN configuration example 177

7.4.6 Examples for configuration files 191
HiVision
Release 6.4 06/07 147
VLAN manager
To create and manage VLANs you must first have worked out a VLAN
concept.
VLANs can also be configured virtually, which means that configuration can
take place in HiVision before the final hardware installation of the devices.
HiVision
148 Release 6.4 06/07
VLAN manager 7.1 The function of the VLAN manager
7.1 The function of the

VLAN manager
7.1.1 Advantages of the VLAN manager

The VLAN Manager provides three big advantages:
D Fast configuration of VLANs
– Unique multi-device configurations
– Simultaneous configuration of multiple stations, groups,
ports and security settings.
D Safe configuration of VLANs
The VLAN Manager checks the configuration before transferring it to the
agents. If the configuration is inconsistent the VLAN Manager will indicate
the problem.
A configuration installed in the network can be loaded (provided there is
at least one MACH 3000 with a MAC-based configuration in the network).
D Documentation of VLANs
Using the export function the configuration can be exported to a file as a
table or as an HTML file.
The file can then be read by other documentation program
7.1.2 Configuration types

The VLAN Manager differentiates between two types of configuration:
D Non-intersecting configuration
A non-intersecting configuration is where there is no overlap between va-
rious groups of stations. Each station belongs to one group only. Each
group has only one VLAN identification (VLAN ID). In this case each
group is also a VLAN (see Fig. 26).
HiVision assigns each VLAN a VLAN ID and enables the administrator to
assign VLAN IDs himself.
HiVision
Release 6.4 06/07 149
Example applications for a non-intersecting configuration:

– Restricting broadcasts in IP subnetworks
– Strict separation of VLANs within a network
D Intersecting configuration
An intersecting configuration is where various groups of stations overlap.
One or more stations can belong to more than one group (see Fig. 26). In
this case stations in a group can belong to VLANs with different VLAN
IDs.
Example applications for an intersecting configuration:

– Restricting broadcasts in IP subnetworks
– Secure access for different groups to a single server.
Properties Port-based, Port-based, MAC-based Port security

non-intersecting intersecting
dot1q x1 x1 - -
GRS x - - -
GES x x - -
MACH 1000 x x
MACH 3000 x x x x
MACH 4000 x x - -
Power MICE x x - -
MS 20/30 x x - -
RS 20/30/40 x x - -
OCTOPUS x x - -
Table 20: Device support for VLAN properties
1.The programming of non Hirschmann devices by the VLAN mana-

ger depends on the implementation of the dot1q-MIB in these
devices
HiVision
150 Release 6.4 06/07
non-intersecting configuration intersecting configuration
Group yellow
A B
VLAN ID = 2
C
Group brown
VLAN ID = 3 D
Group green,
VLAN ID = 1
VLAN ID = 4 VLAN ID = 6
Group yellow,
VLAN ID = 2
G E
F
VLAN ID = 5
Group green
Fig. 26: Non-intersecting and intersecting configurations
7.1.3 Data entry elements

The program provides numerous data entry elements to help you configure
VLANs.
D Filter
Using the filter function you can reduce the number of lines in the table
below the filter box. The filter function affects the left column in the table.
Enter the required sequence of characters in the filter box and click the
filter button. The table will then only show those records which contain the
sequence of characters you entered.
HiVision
Release 6.4 06/07 151
D Search function
To search for particular entries in a table, right-click on a field in the hea-
der line.
D Edit field
Double-click a field in a table to edit it. HiVision will then open the appro-
priate window.
D Shortcut menu
Right-click on a field in a table to open a shortcut menu to help you edit it.
D Sort function
Click on a field in the table header line to sort the table.
D Simultaneously editing several lines
Use "Ctrl" or the "Shift" key to select several lines in a table for editing.
HiVision enters the modified values in all the selected lines. Fields marked
ignore remain unchanged.
- Menu bar
- Toolbar
- Filecards
- View
Agent window Selection field for he The remaining selec-

Toggle switch for items to be edited. tion is shown on the
intersecting and non- right
intersecting groups
Fig. 27: VLAN Manager main window
HiVision
152 Release 6.4 06/07
7.1.4 The network management station as a user

According to their basic settings, most new switches installed in a network
are assigned to the VLAN with the ID 1.
In order that the network management station can always access new swit-
ches, we recommend assigning the network management station to the
VLAN with the ID 1.
With HiVision's automatic VLAN ID assignment, the network management

station is therefore always assigned to the VLAN with the ID 1. This means
that all stations belonging to the same group as the network management
station are also assigned to the VLAN with the ID 1.
For security reasons it is advisable to create a separate network manage-
ment group.
HiVision
Release 6.4 06/07 153
VLAN manager 7.2 Port-based VLANs
7.2 Port-based VLANs
Port-based VLANs are characterized by the assignment of ports to a particu-

lar VLAN.
Ports can be assigned to any VLAN.
As such, devices at any place in the network can belong to a common VLAN
when their ports are also assigned to the VLAN.
VLAN yellow
VLAN green
149.218.32....
MACH 3002
...100
...101
port ...100:1
VLAN green
VLAN yellow
port ...110:1
149.218.32....
MACH 3002
...110
...111 VLAN yellow

VLAN green
Fig. 28: Example of a port-based VLAN
HiVision
154 Release 6.4 06/07
7.2.1 Selecting the configuration type

V Select the configuration type as described in “Configuration types” on
page 149. The toggle switch for intersecting or non-intersecting configu-
rations is on the VLAN Manager filecard (see Fig. 27).
7.2.2 Selecting the agents

V Click on the Agent list... field in the bottom left corner of the VLAN
Manager filecard.
Fig. 29: Opening the agent selection window
HiVision
Release 6.4 06/07 155
V Highlight the agents you require in the right-hand column and click the left
arrow button with the port icon to move them to the left-hand column.
Click New to enter the IP addresses of virtual agents. Under Features

select the port-based setting and the agent type.
If you click the right arrow button, the highlighted line in the left-hand co-
lumn is deleted.
Fig. 30: Selecting the agents
V Click OK to transfer the agents to the list.

By selecting an agent and clicking a field under this table you can edit the
– IP address
– Selection of ports
– Port-based setting
HiVision shows the agents' ports in the middle of the VLAN Manager win-
dow.
HiVision
156 Release 6.4 06/07
Assign ports to virtually created agents by highlighting them and clicking

the Ports field.
Fig. 31: Entering ports for virtual agents
Note: For the GES 24TP Plus always enter all available ports.
HiVision
Release 6.4 06/07 157
7.2.3 Creating groups

V Click on the Edit field on the VLAN Manager filecard and select Groups.
V Select VLAN Manager:New... from the menu bar.
Fig. 32: Creating groups
V Enter the name of the group.
V If you want to enter the VLAN ID yourself, select Override and enter the
VLAN ID.
V A cross in the Default group checkbox identifies the group to which all
ports are assigned if they are not assigned to a group.
V On the Members filecard you can select the ports which will belong to the
group.
V Select Action: Add and click OK. HiVision assigns the selected ports to
the group (see Fig. 38).
HiVision
158 Release 6.4 06/07
7.2.4 Defining Uplink and port access

The connection between the switches is called the Uplink.
U Uplink
V Click on the Edit field on the VLAN Manager filecard and select VLAN
ports.
V Select the lines of the ports which are provided for linking different
switches.
V Right-click in the Role field and select Edit.
Fig. 33: Defining Uplink ports
V Select the type of connection you require and click OK.

The VLAN Manager offers 3 optional Uplink settings:
Uplink
The port supports GVRP.
The port transmits frames from VLAN 1 without tag and frames of
other VLANs with tag.
Uplink (No GVRP)

HiVision
Release 6.4 06/07 159
Uplink to GRS (no GVRP, all tagged)

The port transmits all frames with tag.
User, Group, Known, User

Only non-tagged packets are transmitted.
With an existing configuration HiVision provides the option of looking for

Uplinks. Enter a number for Guess UplinksÉ and click OK.
HiVision sets the ports at which packets have been received with at least
as many different MAC source addresses as the number you entered to
Uplink (no GVRP).
To make sure that all current MAC addresses are taken into account, first
load them by selecting Reload MAC tablesÉ. The antenna in the sta-
tus bar continues flashing until the transmission is completed.
U Network management station

V To identify your network management station, mark its port and click
the right mouse button. Select Mgmt stations.... Note that HiVisi-
on assigns the VLAN with the ID 1 to the network management stati-
on's group. This means all ports in the same group are also assigned
to the VLAN with the ID 1 (see “The network management station as
a user” on page 153).
7.2.5 Saving the configuration to a file

V Save the data you entered in a file. HiVision stores this file in the
HiVision/data/var/vlans/ folder.
In the menu, select VLAN Manager:Save:To file....
HiVision
160 Release 6.4 06/07
7.2.6 Saving the configuration to the agents

Once all the settings have been defined virtually and then validated, the data
can be transmitted to the agents.
Note: Do not transmit the settings to the agents before you have made sure
that your network management station still has access with these settings.
The network management station needs access to the port to which you are
connected, so that you can continue making configurations in the network.
V In the menu, select VLAN Manager:Save:To agents.... The wizard

guides you through the necessary steps.
First, it performs a consistency test and shows you the result.
When you click Next the wizard gives you the opportunity to change par-
ticular settings.
Click Next again, and you can select the agents on which to store the
configuration.
When you click Finish the wizard transfers the data to the selected
agents. The duration of the transmission depends upon the devices (with
GES and SNMP configuration in HiVision, set the timeout to >5s and 2 re-
tries).
Error messages and information from the consistency test

The name of the configuration is too long (maximum 39 characters)
There are no management ports/stations
Agent running in MAC-based VLAN mode
Device has fewer ports than defined in the configuration
Unknown agent type, the configuration must be saved on the device manually
Agent has no Uplinks
This agent is not responding
This agent is currently being queried, the port list may be incomplete
This configuration cannot be reloaded by the agents
Table 21: Consistency test
Note: With MACH 3000 and GRS HiVision switches off the Spanning Tree
algorithm at all ports except Uplink ports.
HiVision
Release 6.4 06/07 161
Note: If you expressly wish to have the Spanning Tree algorithm at an Uplink
port, then check this setting.
HiVision
162 Release 6.4 06/07
VLAN manager 7.3 MAC-based VLANs
7.3 MAC-based VLANs
Since MAC-based VLANs compile stations to groups, MAC-based VLANs

are also referred to as user groups.
MAC-based VLANs are much more flexible than standard port-based

VLANs.
D Flexibility
With MAC-based VLANs stations can be moved without reconfiguring the
switches. Since the VLAN assignment is defined using the station's MAC
address, it always belongs to the same group. It does not matter which
port the station is connected to.
D Security
Each station is bound to its group.
If a station changes to another port, it always retains its membership of
the group. This is not always the case with port-based VLANs.
Access rights can be set at each port.

If an access violation occurs at a port, the agent can react differently ac-
cording to the setting. Possible reactions include:
– Denying access
– Ignoring the violation
and/or
– Sending a trap.
HiVision
Release 6.4 06/07 163
Group yellow
149.218.32. A
MACH 3002 B
100
C
101
D
port 100:1
Group brown
G E
port 110:1 F
149.218.32.
MACH 3002
110
111 Group green
Fig. 34: Example of a MAC-based VLAN

V Select the configuration type as described in “Configuration types” on
page 149. The toggle switch for intersecting or non-intersecting configu-
rations is on the VLAN Manager filecard (see Fig. 27).
HiVision
164 Release 6.4 06/07

V Click on the Agent list... field in the bottom left corner of the VLAN
Manager filecard.
V Highlight the MACH 3000s you require in the right-hand column and click
the left arrow button without the port icon to move them to the left-hand
column.
Click New to enter the IP addresses of virtual agents. Under Features

select the MAC-based setting and the agent type.
If you click the right arrow button, the highlighted line in the left-hand co-
lumn is deleted.
HiVision
Release 6.4 06/07 165
Click OK to transfer the agents to the list.

By selecting an agent and clicking a field under this table you can edit
the
– IP address,
– Selection of ports,
– Port-based setting.
HiVision
166 Release 6.4 06/07
7.3.3 Creating stations

V In the main window on the VLAN-Manager tab, select Edit Stations.
Fig. 37: Selecting stations
V Create the stations.

– For the identity, enter the MAC address and the station name. HiVision
writes the name with the MAC address in the HiVision directory to the file
data/var/ethers.
V Under Security specify whether the station can be connected to any

port – select Unbound – or certain ports only – select Bound.
This setting is important for devices which – for security reasons – may
not be simulated at another port without authorization and using a fake
MAC address.
Stations which are often used in different places should be given the set-
ting Unbound.
HiVision
Release 6.4 06/07 167
If you have already defined the groups and port access rights, then you can
still assign the group membership and port access rights in this window. On
initial configuration it is easier to perform these settings later.
– Filecard
– Action selection
– Port selection window. Shows

all 32 possible ports for each
agent
Set Remove Add

Overwrites all settings Deletes all settings Retains all settings on
on this filecard with from the filecard this filecard and adds
the new values the changes
Fig. 38: Station configuration
V To identify your network management station, mark it and click the right
mouse button. Select Mgmt stations.... Note that HiVision assigns
the VLAN with the ID 1 to the network management station's group. This
means all devices in the same group are also assigned to the VLAN with
the ID 1 (see “The network management station as a user” on page 153).
HiVision
168 Release 6.4 06/07
7.3.4 Creating groups

V In the main window on the VLAN-Manager tab, select Edit Groups.
Fig. 39: Selecting groups
V Enter the name of the group.
V A cross in the Default group checkbox identifies the group to which all
stations are assigned if they are not assigned to a group.
V On the Members filecard you can select the stations which will belong to
the group.
HiVision
Release 6.4 06/07 169
Fig. 40: Group membership
V Under Security specify whether the stations in the group can be con-
nected to any port – select Unbound – or certain ports only – select
Bound.
This setting is important for devices which, for security reasons, may not
be replicated without authorization.
Groups whose stations are often used in different places should be given
the setting Unbound.
V Under Security specify how the agent reacts in the event of an access
violation.
HiVision
170 Release 6.4 06/07

The connection between two switches is called the Uplink.
U Uplink
V Click on the Edit field on the VLAN Manager filecard and select Port
security.
Fig. 41: Selecting port access
V Select the lines for the ports with the same connection type.
V Right-click in the AC field and select Edit.
HiVision
Release 6.4 06/07 171
Fig. 42: Defining port access
V Select the type of connection you require and click OK.

The VLAN Manager offers 7 optional connection settings:
Uplink
The port supports GVRP.
Uplink (No GVRP)

Uplink to GRS (no GVRP, all tagged)

The port transmits all frames with tag
User
Only non-tagged packets are transmitted. The port only accepts
those stations selected under Allowed stations.
Group
Only non-tagged packets are transmitted. The port only accepts the
group selected under Allowed groups.
HiVision
172 Release 6.4 06/07
Known
Only non-tagged packets are transmitted. The port only accepts
those stations entered in the switch's forwarding list.
World
Only non-tagged packets are transmitted. The port allows access for
all stations.
With an existing configuration HiVision provides the option of looking for

Uplinks. Enter a number for Guess Uplinks... and click OK.
HiVision shows you the ports at which packets have been received with
at least as many different MAC source addresses as the number you
entered.
To make sure that all current MAC addresses are taken into account, first
load them by selecting Reload MAC tables.... The antenna in the
status bar continues flashing until the transmission is completed.

V To identify your network management station, mark its line and click
the right mouse button. Select Mgmt stations.... Note that HiVisi-
on assigns the VLAN with the ID 1 to the network management stati-
on's group. This means all stations in the same group are also
assigned to the VLAN with the ID 1 (see “The network management
station as a user” on page 153).
7.3.6 Saving the configuration in a file

V Save the data you entered in a file. HiVision stores this file in the
HiVision/data/var/vlans/ folder.
In the menu, select VLAN Manager:Save:To file....
HiVision
Release 6.4 06/07 173
7.3.7 Testing the configuration

V Select VLAN-Manager:Analyse to test whether your network manage-
ment station can access the port to which it is connected (see Fig. 43).
When you double-click in the network management station line, HiVision
displays the port access rights in the lower section of the window.
V Also test the port access rights of the other stations.
Fig. 43: Analysis
HiVision
174 Release 6.4 06/07

Once all the settings have been defined virtually and then validated, the data
can be transmitted to the agents.
Note: Do not transmit the settings to the agents before you have made sure
that your network management station still has access with these settings.
The network management station needs access to the port to which you are
connected, so that you can continue making configurations in the network.
V In the menu, select VLAN Manager:Save:To agents.... The wizard

guides you through the necessary steps.
First, it performs a consistency test and shows you the result.
When you click Next the wizard gives you the opportunity to change par-
ticular settings.
Click Next again, and you can select the agents on which to store the
configuration.
When you click Finish the wizard transfers the data to the selected
agents.
Error messages and information from the consistency test

The name of the configuration is too long (maximum 39 characters)
There are no management ports/stations
Agent running in MAC-based VLAN mode
Device has fewer ports than defined in the configuration
Unknown agent type, the configuration must be saved on the device manually
Agent has no Uplinks
This agent is not responding
This agent is currently being queried, the port list may be incomplete
This configuration cannot be reloaded by the agents
Table 22: Consistency test
Note: With MACH 3000 HiVision switches off the Spanning Tree algorithm at
all ports except Uplink ports.
HiVision
Release 6.4 06/07 175
Note: If you expressly wish to have the Spanning Tree algorithm at an Uplink
port, then check this setting.
The network management station sends the same user and group informati-
on to each agent.
Each agent receives the port security data which is relevant to it.
Transmission sta-
tus:
Yellow - active
Red - transmission
error
Green - transmissi-
on completed
Fig. 44: Transmitting settings to agents
Once the transmission has been completed, the transmission status indicator
flashes and the window is closed. After the transmission has been completed
this user group management configuration is active.
HiVision
176 Release 6.4 06/07
VLAN manager 7.4 VLAN configuration example
7.4 VLAN configuration example
The following example provides a quick introduction to configuring a VLAN

network which is often used in practice.
The configuration is performed step-by-step using the “Example of a port-
based VLAN” on page 154 with the aid of the VLAN Manager.
The previous sections in this chapter contain more detailed information.
149.218.19.76
GES-24TP Plus
Network Management
Station
VLAN yellow VLAN green
VLAN brown
ID = 1
149.218.19.208
MACH 3002
Fig. 45: Example of a port-based VLAN
HiVision
Release 6.4 06/07 177
Fig. 46: Selecting a non-intersecting configuration
HiVision
178 Release 6.4 06/07
HiVision
Release 6.4 06/07 179
V Highlight the agents you require in the right-hand column and click the left
arrow button with the port icon to move them to the left-hand column.
Fig. 49: Adding the agents
HiVision
180 Release 6.4 06/07
U Creating groups
Fig. 50: Selecting groups
HiVision
Release 6.4 06/07 181
Fig. 51: New group
Fig. 52: Entering the name of the group – "brown"
HiVision
182 Release 6.4 06/07
Fig. 53: Assigning ports to the group
Fig. 54: Creating the yellow and green groups in the same way as the brown
group
HiVision
Release 6.4 06/07 183

The connection between the switches is called the Uplink.
U Uplink
Fig. 55: Selecting VLAN ports for the Uplink definition
HiVision
184 Release 6.4 06/07
Fig. 56: Highlighting Uplink ports and selecting "Edit"
Fig. 57: Selecting the connection type
HiVision
Release 6.4 06/07 185
Fig. 58: Highlighting the management connection port and selecting "Mgmt
stations"
Fig. 59: Specifying the management connection port
HiVision
186 Release 6.4 06/07
7.4.4 Saving the configuration to a file
Fig. 60: Selecting Save to file
Fig. 61: Entering the file name
HiVision
Release 6.4 06/07 187
Fig. 62: Selecting Save to agents
Fig. 63: Consistency test result
HiVision
188 Release 6.4 06/07
Fig. 64: Selecting configuration steps
Fig. 65: Selecting agents to be configured
HiVision
Release 6.4 06/07 189
Fig. 66: Starting the transmission of the configuration by clicking "Finish"
Fig. 67: Transmission status display
HiVision
190 Release 6.4 06/07
7.4.6 Examples for configuration files

In the HiVision directory under data/var/vlans/ you find configuration fi-
les with further VLAN examples.
In the HiVision directory under data/kernel/doc/vlans/ you find the de-

scription of the VLAN examples.
HiVision
Release 6.4 06/07 191
HiVision
192 Release 6.4 06/07
Creating a PSM
8 Creating a PSM
8.1 Preparation 196

8.1.1 Program functions 196
8.1.2 Management Information Base 200
8.1.3 Image file 200
8.2 Creating a PSM structure 201

8.2.1 MIB files 203
8.2.2 Manuals for the product 204
8.3 Agent in the main window 205

8.3.1 Product family symbol 205
8.3.2 Product name 205
8.3.3 Agent status 206
8.4 Agent in the Device window 207

8.4.1 Cards 207
8.4.3 Symbols for device functions 208
8.5 Agent window 209

8.5.1 List display 209
8.5.2 Dialog display 209
8.6 Editing PSM files 210

8.6.1 PsmInfo.xml 212
8.6.2 Productimage.jpg 215
8.6.3 SysOidList.xml 215
8.6.4 ProductFamily.xpm 216
8.6.5 ProductFamily.xml 217
8.6.6 Agent.xml 218
8.6.7 AgentDialog.xml 224
HiVision
Release 6.4 06/07 193
Creating a PSM
8.6.8 Component.xml 232

8.6.10outname.xml 235
8.6.11LanguageTable.conf 236
8.7 Testing PSM 238
HiVision
194 Release 6.4 06/07
Creating a PSM
Hirschmann supplies the modules Enterprise and Industrial Line with

HiVision. With these two modules, HiVision can all administrate all
Hirschmann agents. With the help of Product-Specific Modules (PSM), users
can themselves integrate third-party devices with HiVision and manage them
via HiVision.
This chapter explains how to create a PSM using the BinTec X1000 routers
as an example.
To create a PSM you will need the following:

D An image processing program, for example, Microsoft Photo Editor.
D A drawing program, for example,
Microsoft Paint (Windows) for bmp files
dticon (HP-UX) for xpm files
pixmap oder Kiconedit (Linux) for xpm files.
D A text editor, for example, Accesories:WordPad,
possibly an XML editor.
Hinweis: The Hirschmann Competence Center (see "Frequently asked

questions" on page 244) will be happy to receive your order for the creation
of PSMs.
HiVision
Release 6.4 06/07 195
Creating a PSM 8.1 Preparation
8.1 Preparation
8.1.1 Program functions

Before you start creating PSMs, you should be familiar with the functions of
the program you wish to describe with PSM.
Analyze the function units according to the criterion of how they can be inte-
grated into HiVision.
U Displaying the agents in the main window

HiVision provides the following fields for display in the main window:
– Type: Icon of the product family to which the product belongs.
– Type: Name of the product.
– System Location: Where the product is installed.
– System name: A significant name that you assign the product.
– Special information: any information that you would like to list
here.
– Software version, in as far as the product provides a MIB variable.
Fig. 68: PSM display in the main window
HiVision
196 Release 6.4 06/07
U Displaying the agent in the Device window

HiVision offers various cards and displays the device functions for dis-
playing the Device window.
– "Image" card with device functions

The "Image" card offers the option of displaying an image file in the
JPEG format.
Symbols are located above the status line in the Device window for
representing device-specific functions. HiVision automatically places the
agent and housing symbol in this line. You can freely define the other
symbols (parts).
– "Device Description" card

The card "Device Description" card models part of the system MIB.
– "Physical map" card

The "Physical Map" card displays the physical interfaces of the product.
– "Logical map" card

The "Logical Map" card shows the logical interfaces of the product. Use
this card for PSMs that describe switches.
– "Traps" cards
The "Traps" card shows the traps received from HiVision.
Depending on the product, you can omit the card or define new ones.
HiVision
Release 6.4 06/07 197
Cards
Device image
Symbols for
Device functions
(parts)
Fig. 69: PSM display in the device window
U Displaying the agent in the Agent window

After double-clicking the Agent symbol in the Device window of an agent,
the Agent window appears. Normally, it offers the card index with the fol-
lowing cards
– Configuration,
– Performance,
– Fault and
– Security.
You can create new cards or remove existing ones at any time.
As a rule, these cards are divided into a left and right area. The left side
displays a tree for selecting details that are displayed on the right-hand
side. HiVision provides two way to display these details:
– List display and
– Dialog display
HiVision
198 Release 6.4 06/07
The list display is to be used when you wish to have lines displayed as in
a table.
Fig. 70: List display in the Agent window
The dialog display is designed for those cases in which you wish to view
and edit a single-column matrix.
Fig. 71: Dialog display in the Agent window
HiVision
Release 6.4 06/07 199
8.1.2 Management Information Base

The Management Information Base (MIB) of the product that you wish to de-
scribe with the PSM should be available as a text file.
HiVision requires MIBs according to SMI V2.
8.1.3 Image file

The image file of the product that you wish to describe with the PSM should
be available as a JPEG file. You will need an image resolution of 200 x 200
pixels up to 1000 x 800 pixels. If the image file is a color picture, convert it
into a gray-scale image.
HiVision
200 Release 6.4 06/07
Creating a PSM 8.2 Creating a PSM structure
8.2 Creating a PSM structure
The first step in creating a new PSM is performed by HiVision. HiVision

creates a directory structure for a new PSM for you. HiVision places so-
called templates into the proper directories.
The templates are text files for describing the product to be integrated. They
are given the necessary parameters that HiVision interprets using key words.
V Open HiVision.
V Select PSMs under Configuration:Preferences.

This opens the window for configuring the PSM.
Fig. 72: Configuring the PSMs
V Click New PSM.

This opens the New PSM window.
HiVision
Release 6.4 06/07 201
Fig. 73: New PSM
V Enter the name of the PSM after Name. HiVision uses this name to create
the directory structure.
Enter the type designation after Agent identifier. Put a prefix before
the type designation that uniquely identifies the manufacturer. The prefix
"Hm" is reserved for Hirschmann.
Enter the system object identification (SysOID) of the product from the sy-
stem table after Agent sysObjectID.
Check As simple as possible, if you want your PSM to include only
a limited number of few functions. HiVision then combines the files
Agent.xml, AgentDialog.xml and Component.xml into one file
(see Fig. 74).
V Click OK.
The newly created PSM appears in blue in the column of available PSMs
in the PSM Configuration window. The blue color indicates that HiVision
has not yet loaded this PSM. Select the PSM and click the arrow pointing
left. The PSM also appears in blue in the left column. HiVision will load
this PSM when you restart the program.
In the meantime, HiVision has created the proper directory structure with the
template in the HiVision directory. The templates already contain the values
that you entered in New PSM window.
HiVision
202 Release 6.4 06/07
HiVision
|Ðdata
| |ÐBinTec
| | |Ðbitmap
| | | |ÐBinTec.xpm
| | |Ðconfig
| | | |ÐAgent.xml
| | | |ÐAgentDialog.xml
| | | |ÐComponent.xml
| | | |ÐProductFamily.xml
| | | |ÐPsmInfo.xml
| | | |ÐSysOidList.xml
| | |Ðdoc
| | |Ðimage
| | | |ÐX1000.jpg
| | |Ðmib
Fig. 74: Directory structure with templates
V Quit HiVision.
8.2.1 MIB files

In order for HiVision to access the MIBs of the product (page 200), copy the
MIB files in to the mib folder (see Fig. 74).
V Copy the private MIBs into the mib folder (see Fig. 74).
V Copy the standard MIBs that have not yet been loaded into the mib folder
(see Fig. 74).
Standard MIBs that are loaded by HiVision are located in the HiVisi
on\data\kernel\mib folder.
HiVision
Release 6.4 06/07 203
8.2.2 Manuals for the product

If you have manuals to your products as PDF files that you would like to de-
scribe with this PSM, copy these PDF files into the doc folder (see Fig. 74).
HiVision
204 Release 6.4 06/07
Creating a PSM 8.3 Agent in the main window
8.3 Agent in the main window
HiVision displays each agent in a line of the main window. The largest part of
the display is taken up by HiVision polling the MIB variables of the agent. The
display for the product family and the product name is defined in the PSM.
8.3.1 Product family symbol

To display an agent in the main window of HiVision, an image file that con-
tains the product family symbol is required.
The sections "ProductFamily.xpm" on page 216 and "ProductFamily.xml" on
page 217 describe this procedure.
8.3.2 Product name

HiVision displays the name in the "Product" column that you enter in the
agent.xml file (see "Agent.xml" on page 218). HiVision refers to the assign-
ment that follows the attribute ChassisVar or ChassisFix.
HiVision
Release 6.4 06/07 205
Creating a PSM 8.3 Agent in the main window
8.3.3 Agent status

To calculate the agent status, HiVision uses various information sources.
One the one hand, HiVision checks the SNMP availability of the agent. On
the other hand, you have the option of creating calculation formulas in the
"Agent.xml" on page 218 that determine the agent status.
HiVision
206 Release 6.4 06/07
Creating a PSM 8.4 Agent in the Device window
8.4 Agent in the Device window
In the templates, HiVision offers a standard display of the Device window. It

already contains cards.
8.4.1 Cards
The AgentDialog.xml template already describes the HiVision standard
cards. Modify the "AgentDialog.xml" on page 224 file to fit your needs.
8.4.2 Device image

An image file is required to display a device image in the HiVision Device win-
dow. The sections "Productimage.jpg" on page 215, "Component.xml" on
page 232 and "AgentDialog.xml" on page 224 in the subdialog
Agent_Image describe the size, the alignment as well as the definition of
the card.
HiVision
Release 6.4 06/07 207
Creating a PSM 8.4 Agent in the Device window
8.4.3 Symbols for device functions

You provide the symbols for the device functions as an xpm or bmp file. The
symbols size is 26 x 26 pixels. Copy these symbols to the bitmap directory.
Define the properties of the symbol according to the description in
"Agent.xml" on page 218. Describe the dialog boxes that appear after you
double-click the symbol in the AgentDialog.xml file as described on page
231.
HiVision
208 Release 6.4 06/07
Creating a PSM 8.5 Agent window
8.5 Agent window
The "AgentDialog.xml" on page 224 file describes how the agent appears in
HiVision:
– Agent window,
– Device window,
– Agent dialog boxes,
– Dialog boxes of the symbols for device functions.
8.5.1 List display

Examples for list dialog boxes can be found on page 227 in the description
for the AgentDialog.xml file. In addition to the dialog type EditList the-
re is also the dialog type ShowList. In a list of type EditList the values of
the list can be edited. After double-clicking a line, HiVision offers an additio-
nal window for editing.
8.5.2 Dialog display

The example on page 225 shows the dialog display. It uses the Dialog dia-
log type. Define the variables for the dialog in a group.
HiVision
Release 6.4 06/07 209
Creating a PSM 8.6 Editing PSM files
8.6 Editing PSM files
As the file structure(see Fig. 74) shows, there are 7 files to be edited. These
include configuration files in the XML format and also bitmap files.
The files in the XML format (V1.0) can be edited with a text or XML editor.
The DTD files that describe the structure of the XML files, i.e. describe the
visual text representation, are contained in HiVision.
The logical structure of the contents of the XML files consists of the definition
of elements. An element can possess several attributes. Attributes are assi-
gned a value:
<Element1 Attribute1="Value1" Attribute2="Value2" ></Element1>
or in the short form

<Element1 Attribute1="Value1" Attribute2="Value2"/>
These lines create the element Element1 with the attributes Attribute1
and Attribute2.
Elements can have subelements.

<Element1 Attribute1="Value1" Attribute2="Value2" >
<Element2 Attribute1="Value3" />
<Element2 Attribute1="Value4" />
</Element1>
Here, the element of type Element1 has two subelements of type

Element2. The subelements differ in the way they assign values.
HiVision
210 Release 6.4 06/07
Example for the PsmInfo.xml file:

<PsmInfoName="BinTec"
Version="1.0"
Copyright="Copyright 2001 Hirschmann Electronics .."
Description="Definition of BinTec Router Agents">
<File Name="mibbipx.mib"Type="Mib"/>
<File Name="mibbospf.mib"Type="Mib"/>
<File Name="mibbox.mib"Type="Mib"/>
</PsmInfo>
PsmInfo corresponds to Element1

Name corresponds to Attribute1
BinTec corresponds to Value1
Version corresponds to Attribute2
1.0 corresponds to Value2
File corresponds to Element2
Name corresponds to Attribute1
BinTec corresponds to Value1
Tables in the sections for the individual files contain the possible elements
and attributes.
The "Mandatory" column indicates whether the element /attribute is required
in the file or can be used optionally.
Note: If the meaning column contains a default value, the entry is then requi-
red, but HiVision eliminates the need for entering an attribute. In this case,
HiVision accepts the default value. In the example above, you are required
to enter the attribute Type since the default value (Config), (see Table 23
on page 214) does not correspond to the value (Mib).
HiVision
Release 6.4 06/07 211
8.6.1 PsmInfo.xml
After opening the PsmInfo.xml file, check to make sure that HiVision has
prepared the contents of the file as far as possible.
<PsmInfoName="BinTec"
Version="1.0"
Copyright="Copyright 2001 Hirschmann Electronics .."
Description="Definition of BinTec Router Agents">
<File Name="mibbipx.mib"Type="Mib"/>
<File Name="mibbospf.mib"Type="Mib"/>
<File Name="mibbox.mib"Type="Mib"/>
<File Name="BnTcFamily.xml"Type="Config"/>
<File Name="SysOidList.xml"Type="Config"/>
<File Name="BnTcAgent.xml"Type="Config"/>
<File Name="BnTc_component.xml"Type="Config"/>
<File Name="BnTc_dialog.xml"Type="Config"/>
<File Name="BnTc_outname.xml"Type="Config"/>
</PsmInfo>
The file PSMInfo.xml represents, so to speak, the package contents of the

PSM.
At first, the file contains general information such as name, version number,
copyright, and a brief description. A list of data then follows that is a compo-
nent of this PSM.
V Make the desired changes for the general information.
V List all file names of the MIBs that you have copied into the mib folder
8.2.1MIB files.
Pay particular attention to the order. HiVision reads the MIBs in the order
they are listed in this file. A MIB that, for example, imports another MIB,
cannot be loaded until the imported MIB has been loaded.
HiVision
212 Release 6.4 06/07
V A PSM contains the following configuration files:
Product family configuration file:

It defines information about the product family. Name the ProductFami
ly.xml template according to your product family.
(Example: BnTcFamily.xml).
This file can be omitted if you do not want a product family assignment.
System object identification file

This file contains the name of the products and their system object iden-
tifications (SysOid), that are described by the PSM.
Agent file
This file contains the general description of the agent of the PSM pro-
duct. Name the agent.xml template according to its agent (Example:
BnTcAgent.xml). If the PSM contains several agents, you can copy
this file with the name of another agent or describe several agents in a
single file.
Component file
This file contains the list of the product images. Name the compo
nent.xml template according to its agent (Example:
BnTc_Component.xml).
Agent dialog file

This file describes the dialogs with agents of this PSM product. Name the
template AgentDialog.xml according to its agent (Example:
BnTc_Dialog.xml). If the PSM contains several agents, you can copy
this file with the name of another agent or describe several agents dia-
logs in a single file.
MIB values assignment file

This files intended to give MIB variables
– Legible names for display in HiVision,
– Add attributes that are contained in the MIB but are required by
HiVision.
Name the template outname.xml according to its agent (Example:
BnTc_outname.xml).
HiVision
Release 6.4 06/07 213
Translation file
This file contains a list of terms for display in HiVision with the translation
into the language used. Name the LanguageTable.conf template
according to its agent (Example: BnTc_LanguageTable.conf). If the
PSM contains several agents, you can add a copy of this file with the
name of another agent or describe several agents in a single file.
This file can be omitted if you only want to display agent-specific terms in
a single language.
List all files that belong to your PSM in the PsmInfo.xml file.
V Save the file before closing.
Manda- Num-
Element Attribute Meaning tory ber
PsmInfo Defines PSM (name, version, ...) and names 1
files that belong to the PSM
Name Name of the PSM yes
Version Version number of the PSM yes
Description Brief description of the PSM yes
Copyright Copyright string yes
File Subelement of PsmInfo any
List of files that belong to the PSM
Name File name yes
Type Type of the file. Possible are: optional
Mib, Config or Language default: Config
and with HiVision 6.1 additionally: Manual and
Readme
Table 23: Element list for the PSM information
HiVision
214 Release 6.4 06/07
8.6.2 Productimage.jpg
This file represents the gray-level image of the product.
Place the product image of "Image file" on page 200 in the image folder (see
Fig. 74). If several products belong to the PSM, place all the image files of
this PSM in this folder.
8.6.3 SysOidList.xml
The system object identification list (SysOid) contains the names of the pro-
ducts that belong to this PSM and are to be detected by HiVision. If HiVision
detects a known SysOid during a network scan, HiVision creates a record for
this agent with this agent type.
<Resources>
<AgentSysOid
SysOid="1.3.6.1.4.1.272.4"
AgentID="BnTcX1000" />
</Resources>
V HiVision has already entered the name and the SysOid of the product in
the file that you entered when you created the new PSM.
If the PSM is to contain more than this product, add one element to this
file for each new product.
<Resources>
<AgentSysOid
SysOid="1.3.6.1.4.1.272.4"
AgentID="BnTcX1000" />
<AgentSysOid
SysOid="1.3.6.1.4.1.xy.4"
AgentID="Phantastic" />
</Resources>
HiVision
Release 6.4 06/07 215
V Save the file before closing.
Element Attribute Meaning Manda- Number

tory
AgentSysOid Assigning SysOids to agents any
SysOid SysOid that is assigned to the following agent. yes
Wildcards (* only) are permitted on the end
AgentID ID of an agent defined in agent.xml yes
Table 24: Element list for the system object identification list
8.6.4 ProductFamily.xpm
HiVision display the symbols of the product family which the agent in this line
belongs to in the left column of the agent card in the main window.
V Create a bitmap file that displays the symbol for each product family.
Save the bitmap file in the XPM or BMP format in the bitmap folder.
HiVision places an XPM template in the bitmap folder.
The file has a size of 20 x 20 pixels.
Transparent surfaces for the status display are possible for files in the
XPM format.
HiVision
216 Release 6.4 06/07
8.6.5 ProductFamily.xml
In the main window, HiVision displays the symbols of the product family
which the agent in this line belongs to in the left column of the agent card.
<Resources>
<ProductFamily
ProductFamilyID="BnTcBinTec-Router"
Label="BinTec-Router"
Symbol="BnTcRouter.xpm"
SortIndex="210" />
</Resources>
V Enter the identification of the product family after ProductFamilyID.

Add a prefix that uniquely identifies the manufacturer. The prefix "Hm" is
reserved for Hirschmann.
V Enter the product family name after Label that is to be displayed in HiVi-
sion. HiVision displays the product name in a speech bubble once you
place the mouse pointer on the symbol.
V Enter the name of file that contains the symbol of the product family after
Symbol(see "ProductFamily.xpm" on page 216).
V Enter a whole number with which you can influence the sort order in the
main window of HiVision after SortIndex.
The permissible number range is 200 to 999. The smaller the number, the
higher the agent appears in the list.
V If your PSM contains more that one product family, enter an element for
each product family.
HiVision
Release 6.4 06/07 217
8.6.6 Agent.xml
This file describes the line of the agent of the product as it appears in the
main window of HiVision and determines the status display. The status dis-
play also includes the symbols in the status line of the Device window as well
as the definition of the status forwarding.


<AgentAgentID="BnTcX1000"
ProductFamilyID="BnTcBinTec-Router"
ChassisVar="sysDescr.0"
ProductVar="sysDescr.0"
SwVersionVar="biboAdmSWVersion.0"
SupportsTelnet="Yes"
CalcPhysState="Yes"
PhysStateName="Physical State">
The upper section of this files describes the agent line in the main window.
This is where you determine what is to appear in the columns of the agent
line, whether HiVision activates the Telnet function and how HiVision for-
wards the physical status.
The lower section of this file describes the symbols for the device-specific
functions (parts). Here you determine which file contains the symbol, what
the symbol is to be called, and from which MIB variables the status of the
symbol is calculated.

<PartPartID="LAN_Button"
Label="$$LANSTATUS"
Symbol="LAN.xpm"
Instance="3"
ExprAvailable="ifOperStatus.1000.3!=0">
<PartStatus
Name="LAN-Status"
ExprOk="ifOperStatus.1000.3==1"
ExprWarning="ifOperStatus.1000.3==5"
ExprError="ifOperStatus.1000.3==2"
/>
HiVision
218 Release 6.4 06/07
</Part>
<PartPartID="ISDN_Button"
Label="$$ISDNSTATUS"
Symbol="ISDN.xpm"
Instance="7"
ExprAvailable="ifOperStatus.10001.7!=0">
<PartStatus
Name="ISDN-Status"
ExprOk="ifOperStatus.10001.7==1"
ExprWarning="ifOperStatus.10001.7==5"
ExprError="ifOperStatus.10001.7==2"
/>
</Part>
</Agent>
The following list contains the definition of the possible elements and
attributes:
Manda-
Element Attribute Meaning tory Number
Agent Agent definition any
AgentID String for communication with the agent yes
(AgentDialog.xml).
ProductFamilyID Assigns the agent to this family. To set this yes
value, see ProductFamily.xml
ChassisVar This variable holds the chassis name. HiVi- optional
sion displays this name in the "Product"
column of the main window.
ChassisFix Permanent assignment of the chassis optional
name. HiVision displays this name in the
"Product" column of the main window.
ChassisFix Formula for chassis name optional
DialogSelectVar Selects a product version. optional
SwVersionVar This variable holds the software version. optional
ShowSpecialInfo Possible: Yes or No, default: Yes optional
SupportsTelnet Supports the Telnet agent. Enter 'Yes' so optional
that HiVision activates the menu item,
Possible: Yes or No, default: No
Supports Web If the agent supports Web-based manage-
ment, then enter Yes so that HiVision activa-
tes the menu item (in HiVision 6.1 and
upwards:
Possible: Yes or No, default: No)
Table 25: Element list for the appearance of the agent
HiVision
Release 6.4 06/07 219
Manda-
CalcPhysState Calculate physical status, optional
PhysStateName Name of the physical status to be displayed optional
in the speech bubble help,
default: physical state
CalcLogState Calculate logical status, optional
LogStateName Name of the logical status to be displayed in optional
the speech bubble help,
default: logical state
GeneratePorts A port is generated for each interface. optional
The device must have interfaces.
Possible: Yes or No
Default: No
MaxPortNumber This is the maximum number a port can optional
have. If the number is exceeded, no port is
generated. This prevents ports being crea-
ted for internal interfaces (Router, Vlan, ...).
PortIfIndexFor- Formula for calculating the port number optional
mula from the interface index. This port number is
internal (not for display) and is used by
some agents, e.g. in private MIBs, for
instantiation.
PortNoFormula Formula for calculating the port numbers optional
(for display) from the interface index
Example: "((InterfaceIndex-1)%64)+1"
IF index from 1-64 on card 1, from 65-127
on card 2, etc.
CardNoFormula Formula for calculating the card number optional
(for display) from the interface index
Example: "(IntCast((InterfaceIndex-1)/
64))+1"
IF index from 1-64 on card 1, from 65-127
on card 2, etc.
SupportsIfMau- For Port Manager: If-Mau-MIB is supported optional
Mib Possible: Yes or No
Default: No
VlanManDriver Driver for Vlan Manager optional any
Possible: None, Dot1q, FastIron
Default: None
HiVision
220 Release 6.4 06/07
Manda-
SpecialInfo Subelement of agent optional any
Variables that are to be displayed in Special-
Info,
Without entry no special info is displayed
- with entry but without variable, the default
special info will be displayed (supported
MIBs)
- the text is displayed for each variable
- several variable are possible: Display:
in picture: separated by commas
in the speech bubble help: in new line
Text Text to be displayed yes
MibVariable The content of the variable is displayed yes
Instance Poll variable with this instance optional
This instance is also used to differentiate
between identical function symbols, for
example power supplies, see also
"Agent.xml" on page 218.
EnumString For Enums: use EnumString instead of the optional
integer,
BubbleHelp Subelement of agent any
Variables that are to be displayed in the
speech bubble agent
Text Text to be displayed yes
MibVariable Contents of the MIB variable that is to be yes
displayed
Instance Poll variable with this instance optional
EnumString for Enums: use EnumString instead of the optional
integer, if possible
Yes or No, default: No
IgnoreTrap Subelement of agent any
Normally, all variable traps are examined
that contribute to the status. Here you can
make the setting that this trap should not be
used for status changes.
TrapName MibName of the trap yes
Part Subelement of agent any
Definition of a symbols for displaying
device-specific functions
PartID Symbol ID yes
(Reference for Agent_Dialog.xml)
Label Name of the symbol for display yes
Symbol Symbol icon for display yes
see "ProductFamily.xpm" on page 216
Instance Instance of the symbol (number) yes
HiVision
Release 6.4 06/07 221
Manda-
Position Position of the symbol optional
(see "Component.xml" on page 232)
HideInstance In the physical representation, the display of optional
the instance is suppressed (helpful if only
one instance can exist)
possible: Yes or No, default: No
ExprAvailable Formula indicating whether the symbol optional
exists: if there is no formula, the symbol is
always created
PartStatus Subelement of Symbol (not of agent) Defini- any
tion of a subsymbol status. A symbol can
have several substatuses
Name Name of the status (speech bubble help) yes
ExprOk Formula with variable and instance for OK yes
status (green)
ExprWarning Formula with variable and instance for optional
warning status (yellow)
ExprError Formula with variable and instance for error optional
status (red)
PortMana- Formula for querying and setting port char- any
gerConfig acteristics in the Port Manager
Example in data/fastiron/config/Agent.xml
resource file
Attribute Characteristic of port yes
Possible: Admin, FullDuplex, Speed,
AutoNeg, FlowControl, LinkAlarm, Name
Default: Admin
Access Access to the characteristics (querying/ yes

setting). Possible: Get, Set
Default: Get
Option Options for all characteristics except
Possible: On, Off, 10, 100, 1000 for
Default: On Name
Expression Querying: if this formula is fulfilled, the char- yes
acteristic is set.
Setting: variable incl. instance
Value Value to be written only for
Set
HiVision
222 Release 6.4 06/07
U Variable
In order for HiVision to determine the correct value of a variable, it is
necessary to indicate an instance for the variable,
for example: hmChassisName.1. The correct instanz of a variable you
can find with an SNMP browser.
A variable can be assigned to a number or string. Via SNMP, a variable is
often output as a number that has been assigned a string according to
the MIB definition. In this case, the number is called "ENUM", and the
assigned string "ENUMSTRING."
In case you wish to replace an ENUM with a ENUMSTRING, insert
"ENUMSTRING" after the instance,
for example: hmProduct.1:ENUMSTRING.
U Status display
The formula for calculating the status can have constants and any num-
ber of variables. All variables in the formula are to be specified with an
instance.
The worst case of the individual statuses are always displayed in the
main window.
The table lists the permissible operands for the calculation formula (see
Tab. 26 on page 223). Operators with a higher priority are executed first.
Parenthetical expresions with ( and ) are permitted. The formula is
considered fulfilled if the result is not equal to 0. The calculation syntax
follows that of the C programming language).
Operator Meaning Priority Parameter

== equal to 4 numbers or strings
!= not equal to 4 numbers or strings
larger than 6 numbers or strings
= larger than or equal to 6 numbers or strings
< smaller than 5 numbers or strings
<= smaller than or equal to 5 numbers or strings
&& logical And 3 numbers
|| logical Or 1 numbers
& bitwise And 10 numbers
| bitwise Or 9 numbers
^ bitwise Exclusive Or 11 numbers
Table 26: Operators for determining the status
HiVision
Release 6.4 06/07 223
Operator Meaning Priority Parameter

+ addition 7 numbers or strings
- subtraction 7 numbers
* multiplication 8 numbers
/ division 8 numbers
% modulo 8 numbers
! not (unary) 12 numbers
? if 1 numbers or strings
isBitSet test on set bit 11 numbers
- negative sign (unary) 12 numbers
~ complement (unary) 12 numbers
intCast conversion to integer 12 number
(unary)
Table 26: Operators for determining the status
8.6.7 AgentDialog.xml
This file describes the dialogs. The structure is hierarchical. The description
of the contents of the first window is at the beginning. This is followed by the
description of the contents of the windows that appear in the first window as
the consequence of an action.
U Definition of the card index in the device window

The AgentDialog.xml file begins with the definition of the card index
in the device window:

<Resources>
<Dialog Name="Agent_Device"
Type="TabBook"
Title="%IpAddr"
AgentID="BnTcX1000">
<SubDialog Name="Agent_Image" />
HiVision
224 Release 6.4 06/07
<SubDialog Name="Agent_DeviceDescription" />

<SubDialog Name="Agent_PhysMap" />
<SubDialog Name="Agent_Trap" />
</Dialog>
The first block determines the card index and which index cards are loca-
ted in the card index of the Device window.


<Dialog Name="Agent_Image"
Type="AgentImage"
Title="$$IMAGE"
</Dialog>
<Dialog Name="Agent_PhysMap"
Type="AgentPhysMap"
Title="$$MAP"
</Dialog>
<Dialog Name="Agent_LogMap"
Type="AgentLogMap"
Title="$$AGENT_LOGICAL_MAP"
</Dialog>
<Dialog Name="Agent_Trap"
Type="TrapLog"
Title="Traps"
</Dialog>
<Dialog Name="Agent_DeviceDescription"
Type="Dialog" Title="$$DEVICEDESCRIPTION"
<Group Name="Group_BnTcX1000_DeviceDescription" />
</Dialog>
The second block determines the contents of the cards in the card index.
These cards can contain an image, the logical or physical structure, a
trap list etc. (see Table 28 on page 229).
HiVision
Release 6.4 06/07 225
<MibGroup Name="Group_BnTcX1000_DeviceDescription">
<MibName Name="sysDescr" Instance="0" />
<MibName Name="sysContact" Instance="0" />
<MibName Name="sysName" Instance="0" />
<MibName Name="sysLocation" Instance="0" />
</MibGroup>
The third block describes, if needed, the details of the window contents.
U Definition of the Agent window

The Agent window definition in the AgentDialog.xml file follows the
definition of the card index in the device window, the definition of.

<Dialog Name="Agent"
Type="TabBook"
Title="%IpAddr: Agent" *
<SubDialog Name="Agent_Configuration" />
<SubDialog Name="Agent_Performance" />
<SubDialog Name="Agent_Fault" />
<SubDialog Name="Agent_Security" />
</Dialog>
* %IPAddr represents a variable, see "Variables for agent dialogs" on page
230.
The first block determines the card index and which cards are located in
the card index of the Agent window.
HiVision
226 Release 6.4 06/07


<Dialog Name="Agent_Configuration"
Type="TreeBook"
Title="$$CONFIGURATION" *
<SubDialog Name="Agent_Trap_Destination" />
<SubDialog Name="Agent_ISDN_Call_Table" />
<SubDialog Name="IP_Route_Table" />
</Dialog>
* $$ represents a variable, see "Variables for agent dialogs" on page 230.
The second block determines the contents of the cards in the card index.
These cards can contain the most varied information (see Table 28 on
page 229).
<Dialog Name="Agent_Trap_Destination"
Type="EditList"
Title="Trap Destination"
<VarName Name="biboAdmTrapHostAddr" />
<VarName Name="biboAdmTrapHostStatus" />
</Dialog>
<Dialog Name="Agent_ISDN_Call_Table"
Type="ShowList"
Title="ISDN Call Table"
<VarName Name="biboDialIfIndex" />
<VarName Name="biboDialType" />
<VarName Name="biboDialDirection" />
<VarName Name="biboDialNumber" />
<VarName Name="biboDialSubaddress" />
<VarName Name="biboDialClosedUserGroup" />
<VarName Name="biboDialStkMask" />
<VarName Name="biboDialScreening" />
</Dialog>
The third block describes, if needed, the details of the window contents.
The template contains the standard dialogs created by HiVision.
V Check which existing dialogs are useful for describing your product. Make
the necessary changes to the file and add any information you may need.
HiVision
Release 6.4 06/07 227
U Elements and attributes for the AgentDialog.xml file

The elements and attributes in the table below are for describing the dia-
logs.
Manda-
Element Attribute Meaning Number
tory
Dialog Definition of a dialog box any
Name Name of the dialog box yes
Type Type of the dialog box, see "List of the yes
dialog types" on page 229
Title Dialog-box heading, variables are per- yes
mitted, see "Variables for agent dia-
logs" on page 230
AgentID Applies to this agent type optional
Parameter Parameter (depend on the dialog type) optional
see "Parameter list for dialog types" on
page 231
Instance Normal dialog box: The instance is for- optional
med from the values of these variables.
Numbering begins with 0! The instance
cannot be edited. Example: "0,1,2":
The instance is based on the first 3
values of the dialog.
LoadOnPopup When a subdialog is opened, the MIB optional
variables are reread.
Possible: Yes or no, default: No
OneVarPerSetPdu Dialog: when making the setting, optional
always pack one variable into a PDU,
in case the agent accepts only one
variable per PDU.
Possible: Yes or no, default: No
DialogSelect The dialog applies only to DialogSelect. any
The agent determines its DialogSelect
through DialogSelectVar in Agent.xml.
Name DialogSelect = yes
Contents of DialogSelectVar.
SubDialog Subelement of dialog subdialog only in any
TabBook or TreeBook
Name Name of the subdialog yes
Group Subelement of dialog only normal dia- any
log: The variables of this group are dis-
played in the dialog
Name Dialog displays this group of variables yes
Table 27: Element list for the appearance of the Agent dialog boxes
HiVision
228 Release 6.4 06/07
Manda-
VarName Subelement of dialog any
Only in ListDialogs: Display these
variables
Name Name of the Mib variables yes
ReadOnly MibVariable is read-only for this dialog: optional
Yes or no, default: No
Instance Do not query variable, but extract it optional
from the Oid of the first queried varia-
ble, see Determining variable from the
instance
VarOid Subelement of dialog only List dialogs: any
Only use display these variables, if the
MibName is not unique!
Oid Oid of the Mib variables yes
Table 27: Element list for the appearance of the Agent dialog boxes
The list of dialog types demonstrates the possibilities that HiVision provides
for dialogs.
Dialog type Description

TabBook Subdialog with several cards
TreeBook Subdialog with branches
AgentList HiVision main list
VlanConfiguration VLAN Manager (Main list)
TrapLog Trap log (main list and agent level)
MessageLog Message log (main list and agent level)
SyntaxCheckerLog Log of the syntax checkers (main list)
AgentPhysMap Physical map of the agent (agent housing card/
module port)
AgentLogMap Logical map of the agent (agent interface)
AgentImage Image of the agent
Dialog Normal SNMP dialog (Reload, Set)
PollDialog Dialog as in Dialog. It polls however. Interval can
be set (see Table 30 on page 231)
MacAddrList MacAddr list: dot1dTpFdb (possible on agents or
port level)
ShowList List dialog for display (Reload, Stop, Properties)
Table 28: List of the dialog types
HiVision
Release 6.4 06/07 229
Dialog type Description

EditList List dialog for editing (Reload, Stop, Properties, if
variable with DELETE_VALUE: New and Delete)
Rmon1Dialog Rmon diagram with statistics data
Rmon2Dialog Rmon diagram with log data
Rmon3Dialog Rmon diagram with Alams
Rmon1List Rmon list of the statistic data (for printing)
Rmon2List Rmon list of the log data (for printing)
RouterRedundancy Router redundancy dialog
for Hirschmann agents
ActionDialog Dialog can carry out an action. Actions are defined
for agents
Table 28: List of the dialog types
The variable list for agent dialogs shows the placeholders that HiVision pro-
vides. Placeholders make it possible to define a display whose contents is
read from an MIB.
Keyword Meaning
$$TOKEN Keyword from the "LanguageTable.conf" on
page 236 translation files
%IpAddr IP address of the agent with the name in
parentheses (if present)
%PartName Name of the part
%agentNo Number of the agent (normally 1)
%ipAddr IP address of the agent
%boxNo Number of the housing (always 1)
%portNo Number of the port
%interfaceIndex Number of the interface (ifIndex from MIB II)
%partNo Number of a symbol for device-specific
function
Table 29: Variables for agent dialogs
HiVision
230 Release 6.4 06/07
The parameter list shows the parameters that use the various dialog types.
Dialog type Parameter Meaning

Rmon1Dialog "Performance" "Performance Dialog
Rmon2Dialog "Fault Fault Dialog
Dialog "Options": Options, separated by
GrapherSelectAll commas (","). Possible
GrapherPolling- options:
Time=SEC All variables preselected
GrapherOpen=TAB for Grapher
Polling intervall for Gra-
pher: SEC in seconds
Grapher opens with TAB
(graph, pie, table)
PollDialog DialogPolling- Polling interval for Polling
Time=SEC Dialog: SEC in seconds
(default: 5)
Table 30: Parameter list for dialog types
U Definition of the Symbol dialog

At the end of the file the dialogs of symbols for device functions are defi-
ned.


<DialogName="Agent_Trap_Destination"
Type="TabBook"
Title="$$ISDNSTATUS"
<SubDialog Name="Agent_ISDN_Call_Table" />
</Dialog>
In the example above, double-clicking the "ISDN Button" symbol opens

the subdialog ISDN Call Table.
HiVision
Release 6.4 06/07 231
8.6.8 Component.xml
This file describes which image file HiVision assigns to the PSM products and
sets the image display.
<Resources>
<ComponentName="X1000"
Orientation="Vertical"
Width="1336"
Height="917"
Zoom="250"
Image="X1000sw.jpg"
</Component>
<ComponentName="BINTEC-X4000"
Orientation="Vertical"
Width="735"
Height="857"
Zoom="500"
Image="x4000sw.jpg"
</Component>
</Resources>
V For Name enter exactly the name that you have defined in the agent.xml
file with ChassisVar or ChassisFix.
V Orientation indicates the length of the image. Vertical is set by de-

fault. Horizontal is also possible.
V Enter the width and height of the product image for the variables Width
and Height.
V With the value for Zoom you can set the size with which HiVision displays
the product image in the device window.
The value 1000 stands for the factor 1.
V Enter the file name of the product image for image.
V If the PSM describes several products, repeat the procedure for each pro-
duct.
HiVision
232 Release 6.4 06/07
8.6.9 action.xml
This file describes actions and their implementation for the respective
agents.
Mandat
Element Attribute Meaning ory Number
Action Definition of an action any
ActionID String for identifying the action yes
Name Name (not used at present) yes
HelpText Help text (not used at present) optional
Param (Entry) Parameters which require the any
action. If no parameters exist, the dialog
is empty.
Type Type of entry field. Possible: Text, Bool, yes
Enum. Default: Text
ParamID Under this ID, the value in the action yes
implementation can be used.
Name This string is displayed in the dialog. yes
Description This string is displayed as speech bubble optional
help in the dialog.
ActionImplemen- Implementation of an action for an agent any
tation type
ActionID ID of the action (see above) yes
AgentID ID of the agent yes
Command An action can consist of a number of any
commands.
Type Type of action (set or poll variable). Possi- yes
ble: Set, Poll, Check. Default: Set
MibVariable Variable to be set only for Set Instance. only for
Instance of the variable to be set. Set
Expression Set: value to be set. Otherwise: formula to yes
be evaluated.
IgnoreTime- A Timeout can be ignored. Possible: Yes, optional
out No. Default: No
OnTimeout Value of a formula when a Timeout optional
Expression- occurs. Possible: Yes, No. Default: No
True
PollInt_dezi Polling interval (in 1/10 sec.) optional
Sec
Table 31: Element list for defining and implementing actions
HiVision
Release 6.4 06/07 233
Mandat
Element Attribute Meaning ory Number
MaxPoll- Maximum number of polling attempts optional
Count Optional PollLimitRetVal value of a for-
mula when the max. number of polling
attempts has been carried out. Possible:
OK, Error. Default: Error
ExecIf Formula with condition leading to inter- optional
ruption
Table 31: Element list for defining and implementing actions
U Definition of actions
Definition of general actions. Example: SaveConfigLocal,
SoftwareUpdate or RebootAgent. The description of the action also
specifies whether entry parameters are necessary. In the above
examples, they are only necessary for SoftwareUpdate (URL of the
software image).
U Implementation of actions
These actions can now be implemented for every agent type (if the agent
supports this action). An action consists of a number of commands,
which are carried out in sequence. They can be of the following types:
D Set: set an MIB variable to a value.
A fixed value or an entry parameter can be set.
D Poll: poll a variable (until it fulfills a formula).
Polling can also be carried out until a Timeout comes, or as long as a
Timeout is coming.
D Check: the result of the entire action is determined by the evaluation
of this formula.
The check should be the last command of an action.
U Call-up in dialogs
The actions can now be used in multi-agent dialogs. They are located
below the dialog called MultiDevConf and they are of the type
ActionDialog.
HiVision
234 Release 6.4 06/07
8.6.10 outname.xml
Use this file to assign additional attributes to an MIB variable .
<Resources>
<Mib variableName="biboAdmTrapHostStatus"
Label="Status" DeleteValue="2">
</MibVariable>
<Mib VariableName="biboAdmTrapHostStatus"
Label="TrapHostAddr">
</MibVariable>
</Resources>
In the example above, two MIB variables are given new attributes.
The assignment Label=ÓStatusÓ causes the name biboAdmTrapHost
Status to be replaced by the display Status.
The assignment DeleteValue="2" informs HiVision to provide a selec-
tion field called delete and permit a new entry. This assignment requires
HiVision, if no corresponding value exists in the MIB for the MIB variable.
Manda-
MibVariable Description of an MIB variable any
Name Name of the variable (from MIB) yes
Label This value is displayed in the dialog optional
DeleteValue This value allows you to delete and create optional
a table line
SendOnly- During deletion only this variable is sent optional
ThisVarFor- Possible values: Yes or No
Delete Default: Yes
DefaultValue This value is displayed by default upon optional
creation
OffsetValue Offset is subtracted from the variable for optional
display
Creatable This value is not required when created optional
Possible: Yes or No, default: Yes
Monitorable Adds a selection field for the SNMP moni- optional
tor to the dialog (from HiVision 6.1).
Possible: Yes/No.
Default:
– Yes for counter variables
– No for integer variables
Table 32: Element list for assigning values to MIB variables
HiVision
Release 6.4 06/07 235
Manda-
BitString The string is displayed as a hex (01 02 optional
FF) or decimal (001 002 256) number:
Hex or Dec
AllowedValue Subelement of MibVariable for string: dis- any
play popup, not edit field
Value Display these values as popup yes
MapValue Subelement of MibVariable Definition of any
an Enums here. Display as popup.
Value Value yes
Output Display string yes
ReadOnlyValue Subelement of MibVariable Definition of any
values that should not be written
Value Do not write this value yes
Table 32: Element list for assigning values to MIB variables
8.6.11 LanguageTable.conf
The language table is for adapting the PSM to various languages. HiVision
can translate terms that are displayed in the dialogs by using the variables
(see Table 29 on page 230) with the help of the language table. Two prece-
ding $ signs identify a variable that HiVision translates using the language ta-
ble (language table).
The following rule applies for the structure of the LanguageTable.conf file:
– Each line begins with the name of the variable to be translated followed
by the language ID and the translation term.
– Variable, language ID and translation term are separated by a tab or
blanks.
– Should the translation be followed by a blank, separate the variable from
the language ID with an additional blank.
– The language IDs are:
ENG for English,
GER for German,
FRE for French,
SPA for Spanish.
HiVision
236 Release 6.4 06/07
– Enter one line per language for each variable. If a line is missing for a lan-
guage, HiVision then inserts the English term.
– The #-character identifies the start of a comment. A comment ends with
the end of a line
– If an entry consists of several lines, "\n" creates a line feed.
############################################################
#
# LanguageTranslationTable File
#
# Supported Languages:
# ENG English
# GER German
#
############################################################
#################### english ###############################
LANSTATUSENGLAN state
ISDNSTATUSENGISDN state
#################### german ##################################

LANSTATUS GERLAN-Status
ISDNSTATUS GERISDN-Status
HiVision
Release 6.4 06/07 237
Creating a PSM 8.7 Testing PSM
8.7 Testing PSM
Starting HiVision with command-line parameter

-SyntaxChecker
causes HiVision to check the embedded PSMs for syntax error and consist-
ency. The syntax error and consistency testing are subject to:
D Dialogs
D Components
D Product families
D AgentSysOids
D Agents
D AddMibAttributes (outname.xml)
D MibGroups
D Used MIB variables
As an alternative to starting with the command line parameters, you can also
start a PSM check in Windows from the starting menu:
Start - Programs - Hirschmann - HiVision Toolbox -
HiVision - HiVision with Syntaxchecker.
U Dialogs
The syntax checker checks the following criteria in the AgentDia
log.xml file:
– Are all subdialogs present?
– Are not-used dialogs defined?
– Are dialogs repeated?
– Are the groups used available?
– Can the title be translated into the language set?
– Can the placeholders (%portNo) be translated?
– Are all dialogs available (Agent, Agent_Description, Function symbol
dialogs)?
HiVision
238 Release 6.4 06/07
U Components:
The syntax checker checks the following criteria in the Component.xml
file:
– Are any components repeated?
– If the component defines an image, does the image exist?
U Product families
The syntax checker checks the following criteria in the ProductFa
mily.xml file:
– Are any components defined more than once?
– Is a sort index used more than once?
– Does the icon exist?
U AgentSysOids
The syntax checker checks the following criteria in the SysOID
List.xml file:
– Is a SysOid used more than once?
– Does the AgentID exist?
U Agents
The syntax checker checks the following criteria in the agent.xml file:
– Do the MIB variables exist that are used in
ChassisVar,
DialogSelectVar,
SWVersionVar,
SpecialInfoVar und
BubbleHelpVar
– Do the traps exist that are specified in IgnoreTrap?
U AddMibAttributes
The syntax checker checks the following criteria in the Outname.xml
file:
– Are MIB variables defined twice?
HiVision
Release 6.4 06/07 239
U MibGroups
The syntax checker checks the following criteria in all dialogs:
– Are groups defined more than once?
– Are superfluous groups defined?
– Are MIB variables repeated in a group?
– Is the MIB access list valid?
U Used MIB variables

The syntax checker checks the following criteria in the outname.xml file
and in the loaded MIBs:
– Does variable exist in MIB?
– Does variable exist in outname.xml?
Error messages:
Dialog XXX defined but not used
Dialog XXX found YYY times
Dialog XXX not found
Group XXX not found
Dialog XXX: title cannot be translated: title: YYY
Dialog XXX: title with part token cannot be translated: title: YYY
Component XXX defined twice!
Component XXX: image YYY not found
Product Family XXX: uses same SortIndex as YYY, SortIndex: ZZZ
Product Family XXX: Symbol YYY not found
Agent SysOid Entry XXX found twice
Agent SysOid Entry: AgentID not found: YYY
Agent XXX: YYY: Mib Variable ZZZ not defined in loaded MIBs
Agent XXX: YYY: Trap ZZZ: not defined in loaded MIBs
Additional MIB Attribute for Mib Variable XXX: defined twice
Mib Variable XXX: not defined in loaded Mibs
Mib Variable XXX: not defined in loaded Mibs
Group XXX: defined twice
Group XXX: not used
Group XXX: Mib Variable YYY: defined twice
Group XXX: mib access list cannot be translated: access: YYY
Table 33: List of the possible error messages
HiVision
240 Release 6.4 06/07
Error status Result

Info For information on the results
Warning Can cause errors. Does not impair HiVision opera-
tion.
Error Error impairs HiVision operation. Modification
necessary.
Table 34: Error results
U Tips for testing PSMs:

D Deactivate HiVision with
Configuration:Configure PSMsÉ all PSMs that HiVision should
not check. This shortens the start phase.
When HiVision is restarted, HiVision performs a syntax check.
D You can carry out this test while creating the PSM without having to
completely edit the PSM. Save the current PSM files before the test.
HiVision
Release 6.4 06/07 241
HiVision
242 Release 6.4 06/07
Appendix
A Appendix
A.1 Frequently asked questions 244
A.2 Device information 245
A.3 Hirschmann Competence 255
A.4 Readers Comments 257
A.5 Index 259
HiVision
Release 6.4 06/07 243
Appendix A.1 Frequently asked questions
A.1 Frequently asked questions
Answers to the frequently asked questions can be found on Hirschmann’s In-

ternet site:
V Select Help:Hirschmann on the Web:FAQs in the menu bar
You will find detailed information on all the Hirschmann Competence Center
services on the Website:
V Select Help:Technical Support in the menu bar
U Application examples
Unter Help:Tutorials or in the directory .../HiVision/data/kernel/doc/
you will find application examples in Html format:
Subject File
Router-Redundancy routerred/index.html
VLAN-Manager vlans/index.html
Polling polling/index.html
Integration in HP OpenView div/HpOVwIntegration_us.html
Table 35: Application examples
HiVision
244 Release 6.4 06/07
Appendix A.2 Device information
A.2 Device information
A.2.1 RMS
The SNMP configuration of the agent is carried out via Telnet.
A.2.2 MIKE, MULTIMIKE and FCMA
U Saving the configuration

The Agent:Configuration:Config Files dialog allows you to
save the configuration of this agent.
The saving process takes approx. 30 seconds, during which time the
agent can not process any SNMP transactions. During this time, HiVision
receives a timeout message for SNMP transactions, upon which the sta-
tus of the agent changes.
U Gauges
HiVision allows you to edit MIKE gauges. You can create and delete gau-
ges via the Telnet interface.
U MAC addresses
The TYDE and IYDE cards do not recognize port assignment. All the
MAC addresses detected are assigned to port 1. In the physical map,
therefore, the MAC addresses received for all the ports appear at port 1.
HiVision
Release 6.4 06/07 245
U Link status
FastSXM2 recognizes the link status for optical ports when the Spanning
Tree is switched off.
U RMON
100EATP10 does not send any values to the agent:
– Packet sizes (RMON performance).
– Undersize and oversize (RMON fault). The agent sends the value 0.
A.2.3 ETH-12TP/M
Creating gauges:
When you are creating a gauge, default values are used.
In the Agent:Configuration:Create gauge you specify the default va-
lues before creating the gauge.
Changing gauges
V Delete gauge
V Change default values
V Create gauge
Port gauges
The SNMP access to the port gauges always applies to all 3 possible gau-
ges. Thus the 3 gauges behave like one gauge.
HiVision
246 Release 6.4 06/07
A.2.4 FEH-24TP
The user interface allows you to configure a new trap target address. You ac-
cess the user interface via Telnet. HiVision allows you to open a Telnet ses-
sion.
A.2.5 RS2-../..
U Software update
Software updates from versions before 5.0 cause an immediate re-start
as soon as the new software has been transferred in full.
Software updates from versions 5.0 and higher require the user to initiate
the re-start after the software transfer.
U Static address table

The active redundancy manager function does not permit Unicast
address entries for the HIPER-Ring ports in the static address table.
The device specifies the Receive Port "0" (see the Security tab page in
the agent window).
U Port mirroring
Although this function is displayed in releases 5.0 and earlier of the
RS2 software, the RS2 supports this function only from release 6.0.
During the configuration of this function (see the Configuration tab page
in the agent window), the device supports "copyBoth".
HiVision
Release 6.4 06/07 247
U Switching on relay contact

From release 5.0 of the RS2 software, you have the option of operating
the signal contact remotely. In this case you switch the relay contact
exclusively via an SNMP command.
V In the device window, click with the right mouse button on the relay
symbol and select configuration.
V Select the manual mode.
V Select on or off and click on the Set symbol in the tool bar to switch
on the contact.
A.2.6 MICE

The active redundancy manager function does not permit Unicast
address entries for the HIPER-Ring ports in the static address table.
The device specifies the Receive Port "0" (see the Security tab page in
the agent window).
U Switching on relay contact

From release 3.0 of the MICE software, you have the option of operating
the signal contact remotely. In this case you switch the relay contact
exclusively via an SNMP command.
V In the device window, click with the right mouse button on the relay
symbol and select configuration.
V Select the manual mode.
V Select on or off and click on the Set symbol in the tool bar to switch
on the contact.
HiVision
248 Release 6.4 06/07
A.2.7 ETS-14TP, -30TP, -16TP Plus, -32TP Plus,

FES-08TP Plus, -16TP Plus and -16TP
To make RMON 1 and 2 available on these switches, switch on the RMON
Ethernet statistics table and RMON history control table on the device with
the aid of Telnet.
After logging on, enter snmp/etherstattbl and
snmp/histcntrltbl.
A.2.8 GES-24TP/2SX/FES-24TP
The agents support port mirroring within a group (ports 1-8, 9-16 and 17-24).
Under Agent:Configuration:Portmirroring you set the port mirro-
ring function.
You set the AddressAgingTime in the agent directly via the user interface.
HiVision
Release 6.4 06/07 249
A.2.9 GES-24TP Plus, GES-24FX
U Changing access permission

You configure the SNMP communities and the trap targets via the Web-
based management.
U Changing SNMP Timeout

The packet transfer of the SNMP agent has a low priority. Click with the
right mouse button in the device line in the main window and select
Properties:Protocols to increase the Timeout to 1.5.
U Port settings
In the port manager (see “Port Manager/Port Analyzer” on page 83), the
display of Speed and Vollduplex is valid when there is a Link
Status display at the port effected.
HiVision
250 Release 6.4 06/07
A.2.10 ALS family

An ALS supports the setting of SNMP variables (e.g. system location) from
version 2.1. However, you can write in the field even in earlier versions.
Communication of the management station with an ALS agent has no direct
effect on the hardware of the interface cards.
Configuration settings are adopted by the hardware following a reset. Click
the relevant interface card with the right mouse button and select "Error" in
the context menu. Select Execute under "Reset" and click the "Set" button.
U MAC address table

In the agent window, in the Configuration tab page, select "Switching"
and "Selected Card" to select the interface card whose MAC addresses
you require.
A.2.11 GLS family

GLS provides link aggregation from version 3.3.
Communication of the management station with a GLS agent has no direct
effect on the hardware of the interface cards.
Configuration settings are adopted by the hardware following a reset. Click
the relevant interface card with the right mouse button and select "Error" in
the context menu. Select Execute under "Reset" and click the "Set" button.
U MAC address table

In the agent window, in the Configuration tab page, select "Switching"
and "Selected Card" to select the interface card whose MAC addresses
you require.
HiVision
Release 6.4 06/07 251
A.2.12 MACH 3000

A MACH 3000 takes over changes to the system parameters (IP address,
network mask and gateway address) from HiVision after a restart. These
system parameters remain in the Configuration tab page in the agent
window even if you select Configuration:load default.

The device specifies receive port "0" (see the Security tab page in the
agent window).
A.2.13 GRS family

The GRS family supports the RMON function at ports with a link.
A.2.14 FastIron series
U Saving a configuration locally

When you set "no snmp-server pw-check" in the user interface of the
FastIron, you can save the configuration locally on the agent (click with
the right mouse button on the agent symbol in the agent window and
select Configuration: load configuration locally). If you do
not enter this setting, an error message appears when you try to save
locally.
HiVision
252 Release 6.4 06/07
U Condition change for fan and power supply unit symbols

Devices of the FastIron type do not automatically pass on to HiVision any
condition changes in power supply units or fans. If you still want to be
informed about condition changes, click with the right mouse button on
the power supply/fan symbol in the device window and select Polling.
Put a check beside Polling switched on and click on OK.
U Card configuration display

If you remove a card from a slot, then you should delete the entry for this
card in the slot with the aid of the Web interface of the FastIron, with
Module:Delete. After this, when you put this card into another slot, the
FastIron can determine the correct slot by means of SNMP.
U Changing SNMP access rights

You change the SNMP access rights (Community) in the Web interface
or the user interface of the FastIron.
A.2.15 BAT54-Rail
HiVision does not support the VLAN function of the BAT54-Rail.
A.2.16 LION-24 TP
HiVision does not readout the MAC address table of the LION-24 TP.
HiVision
Release 6.4 06/07 253
A.2.17 10 Gigabit/s ports

The RFC1213 defines 32 bit counters to measure the network traffic. These
counters overflow if the network traffic is large. This is why the port analyzer
does not display correct values when the network traffic is large.
A.2.18 Platform-specific information

(HP OpenView integrated versions)
If the menu item Open Device is missing for a Hirschmann agent, then the
following steps can be taken to add this menu item:
V Quit OpenView
V ovstop, ovstart ovwdb, ovw -fields, ovstart ovtopmd, ovtopofix -u, ovstart
V Restart OpenView
or
V Delete the agent and then recreate it

– Select the agent
– Select the menu item Edit:Delete:From all Submaps
– Ping the agent
or
V Select Node unmanage and then Node manage.
HiVision
254 Release 6.4 06/07
Appendix A.3 Hirschmann Competence
A.3 Hirschmann Competence
In the long term, excellent products alone do not guarantee successful custo-
mer relationships. It is the all-round service that makes a difference world-
wide. In the global competitive market, the Hirschmann Competence Center,
with its complete spectrum of innovative services, has its nose ahead of the
competition in the following three ways:
D The consulting encompasses an all-round technical service ranging from
system assessment and network planning to configuration.
D The training includes basic training, product instruction and user training
with certification.
D The support services range from starting operation and on-call services
to maintenance concepts.
In choosing the Competence Center, you are making a decision without any
compromises. With the individualized customer range of services you can
select those services you want to avail of.
Internet:
http://www.hicomcenter.com
HiVision
Release 6.4 06/07 255
Appendix A.3 Hirschmann Competence
HiVision
256 Release 6.4 06/07
Appendix A.4 Readers Comments
A.4 Readers Comments
What do you think of this manual? It is our intention that our manuals descri-
be affected products completely and also provide important information so
that the product can be used without problem. Your comments and ideas
help us to raise the quality and level of information in this documentation.
Your opinion of this manual:
very good good satisfactory fair poor

Exact description O O O O O
Readability O O O O O
Easy to understand O O O O O
Examples O O O O O
Structure O O O O O
Completeness O O O O O
Graphics O O O O O
Drawings O O O O O
Tables O O O O O
Did you find any errors in this manual?

If so, which ones and where?
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
HiVision
Release 6.4 06/07 257
Appendix A.4 Readers Comments
Ideas and suggestions for improvements and additions:

.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
General Comments:
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
.......................................................................................................................
Company / Department ..........................................................................................................
Name / Phone number ..........................................................................................................
Street address ..........................................................................................................
City / Post (ZIP) Code ..........................................................................................................
Date / Signature ..........................................................................................................
Dear user,
Please return the completed form to

− fax ++49 7127/14-1798 or
− to
Hirschmann Automation and Control GmbH
Abteilung AMM
Stuttgarter Str. 45-51
D-72654 Neckartenzlingen
HiVision
258 Release 6.4 06/07
A.5 Index
A.5 Index
Numerics counter 123

100EATP10 246 Counter values 124
CRC 85, 86
A
ACA 76 D
access 60 Day 159
access permissions 60 DCOM 50
Access rights 163 Default setting 69
address table 136, 247, 248, 251, 252 Demo switch 28, 39
administrator 75 Detail window 16, 120
Adobe Acrobat Reader 90, 109, 122 Device details 120
Agent list 81 Device functions 197, 208
Agent status 206 device image 110, 111
Agent symbol 198 Device info 95, 106
Agent window 198, 226 Device list 81
AgentID 239 Device window 16, 89, 106, 120, 207, 225
Agents 12, 121, 123 Dialog 213
ALE 86 Dialog display 198
ALS 251 Dialog type 229
ARP 138 Directory structure 201
AutoConfiguration Adapter 76 DNS 72
Domain Name Service 72
B double-click action 95
base configuration 60 drag and drop 127
Bitmap 216
Bmp files 195 E
bubble help 57, 78, 111 E-Mail 71
ENUMSTRING 223
C equipment 110
card 16, 56, 66, 96, 106, 197 ETH-12TP/M 246
card index 16, 56, 66, 120 Event 99
Chassis 76 Event Actions 100
Clipboard 125 Event category 96
Collisions 63, 85, 86 Event message 63
color assignment 110, 111 Events 106, 120
color symbol 110 Expert 86
column 93 export function 149
column width 57
community 60, 114 F
Community access 60 Fan 76
Community entry 60 FastSXM2 246
Configuration 60, 67, 76, 116, 120, 245 Fault 120
Configuration error 86 fault counter 123
Configuration menu 77 FCMA 245
configuration settings 78 FEH-24TP 247
Configuration types 149 FES-24TP Plus 249
Configuration window 76 field in a table 152
Connection type 171 File 89, 121
Consistency 238 file name 26
core program 15 file structure 26
HiVision
Release 6.4 06/07 259
A.5 Index
Filter 151 Link Aggregation 135, 251

filter function 151 link monitoring 62
Link status 246
G List display 198
GARP 136 Log 125
GARP Multicast Registration Protocol 136 Log file 124
GARP VLAN Registration Protocol 136 Logical map 106, 197
Gateway 137, 252
Gauge 245, 246 M
Generic Attribute Registration Protocol 136 MAC address 245
GES-24TP/2SX 249, 250 MAC address table 251
GLS 251 MACH 3000 161, 175, 252
GMRP 136 Mail 71
Grapher 124 Main window 16, 56, 66, 67, 106, 205
graphical presentation 121 Management Information Base 200
Gray-scale image 110, 200, 215 Management shell 12
Group 158 Manual 90, 109, 122
Group membership 168 menu bar 56, 66, 67, 89, 106, 108, 121
GRS 160, 161, 252 Metric 138
Guess Uplinks 160, 173 MIB 200, 203, 212, 213, 240
GVRP 136, 159 MIB variable 127
MIKE 245
H Modem 70
HIPER-Ring 133, 247, 248 Module 15, 93
HiRRP 139 Monitoring mode 74
Hirschmann Competence Center 195, 244 Multicast address 136
Host route 138 MULTIMIKE 245
Hostname 72 multiple selection 57
HP OpenView 41, 45
HTML file 149 N
net number 111
I net number assignment 114
ICMP 92, 95, 139 network concept 60
Image 106, 110, 120 network environment 123
Image file 197, 200, 205, 232 network events 123
Index 120 Network management station 153, 160, 161,
initialization 106 168, 173, 174, 175
Integration 13 Network mask 252
Interface layout 73 network monitoring 62
Interface Status 76 network problem 63
Intersection 150 Network route 138, 139
IP address 60, 114, 156, 165, 252 non-intersecting configuration 149
IP address area 80 number function 112
ISO/OSI base reference model 123
IYDE 245 O
Object Linking and Embedding 50
L Observation period 86
Language ID 236 OLE 50
Language table 236 OPC 50
level 16, 78, 123 Open Device 41, 45, 254
license 59, 75 OpenView 254
license administration 67 overlap 150
license file 37
license key 15, 75
HiVision
Release 6.4 06/07 260
A.5 Index
P sensor 130
packet error 63 Set 108, 121
Parameter list 231 setup 110
PC stand-alone version 13 Shortcut menu 152
PDF file 204 SMS 70
Performance 85, 120 SMScom 70
Physical map 106, 197 SNMP 60, 92, 95
Polling 98, 120, 129 SNMP configuration 61, 161, 175, 245
Polling interval 124, 129 SNMP monitor 86, 124
Pop-up information 63 SNMP parameters 95
Port access rights 168, 174 SNMP states 115
Port analyzer 85 SNMP variable 251
Port assignment 245 Sort 93
Port group 83 Sort function 152
Port manager 84 Sort index 239
Port Mirroring 247 Spanning tree 162, 175
Port mirroring 249 Special information 196
Port status 76, 129 Standard MIB 203
Port-based 154 Start 41, 45
Power Supply 76 Start window 73
PPP 137 startup 81
Preferences file 74 state 107
Product family 196, 205, 213, 216 static address table 247, 248, 252
Product image 213, 215, 232 statistics 63
Program start 81 status 77, 107, 110
protocol 95 status bar 56
Protocol file 99 Status calculation 129, 223
Protocol Status 76 status color 78
PSM 195 Status display 218
Status forwarding 218
Q status information 111
quitting 67 Status line 66, 197, 218
Status propagation 62, 63, 77, 79
R status symbol 78
Rack Monitoring System 15, 130, 131 subdevice buttons 110
Read permission 60 Subnetwork 137
receive port 247, 248, 252 Subnetwork mask 139
Redundancy manager 133 Symbols 208
Relay Status 76 Syntax errors 238
Reload 108, 121 SyntaxChecker 91
RMON 115, 126, 246, 249, 252 SysOid 202, 213, 215, 239
RMS 131, 245 system assessment 255
Router 137 System MIB 197
Router Redundancy 139
Router Status 76 T
Routing table 138 Table 123, 151
Target address 139
S Telephone network 70
sampling rate 127 Telnet 122, 247
scan procedure 61 Templates 201
scanning area 95 Text file 125
Search 152 Third-party devices 195
Search function 94 Timeout 245
Security 74, 120 tool bar 56, 66, 89, 108, 121
HiVision
261 Release 6.4 06/07
A.5 Index
Translation file 214

Trap 63, 163, 197
Trap destination 48
Trap target address 247
TYDE 245
U
Uplink 159
User groups 163
user training 255
V
Variable list 230
version 12
view selection 67
Virtual 157
VLAN ID 149, 158
VLAN ID assignment 153
VLAN identification 149
W
Web browser 95
Web-based management 95
X
XML format 210
Xpm files 195
Z
Zoom 232
HiVision
Release 6.4 06/07 262

HB HiVision64 Us

Uploaded by

Copyright:

Available Formats

HB HiVision64 Us

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HB HiVision64 Us

Uploaded by

Copyright:

Available Formats

F 6.

HiVision Technical Support

HiVision Technical Support

© 2007 Hirschmann Automation and Control GmbH

Printed in Germany (12.6.07)

Hirschmann Automation and Control GmbH

4 "HiVision" main window 65

4.4 Status line 103

5 Device window 105

6 Detail window 119

7 VLAN manager 147

7.2 Port-based VLANs 154

8 Creating a PSM 193

8.4.2 Device image 207

A.2.17 10 Gigabit/s ports 254

1.1 HiVision management shell 12

1.2 The HiVision basic structure 15

1.3 With HiVision manageable products 17

1.4 Supported MIBs 21

1.1 HiVision management shell

HiVision is a management shell for managing Hirschmann agents and for

This enables at all times

The following HiVision versions are available:

U PC-StandAlone version under Windows 2000/XP/Vista/

U PC-StandAlone Version under Linux

U Integration in the PC management platform HP OpenView

U Integration in the HPUX management platform

1.2 The HiVision basic structure

1.2.1 The HiVision program

1.2.2 The HiVision management platform

The main component of each window is a card-index. The individual cards

1.3 With HiVision manageable

ETHERNET FDDI TokenRing

ETHERNET FDDI TokenRing

Table 2: Manageable interface cards for Advanced Media Centers

ETHERNET FDDI TokenRing

Table 2: Manageable interface cards for Advanced Media Centers

MR8-03 ALS GLS MACH 3000/4000 MICE

Tab. 3: Manageable interface cards and modules for switches

MR8-03 ALS GLS MACH 3000/4000 MICE

Tab. 3: Manageable interface cards and modules for switches

GRS ASGE, MC, AMC

Table 4: Manageable interface cards for routers

Grundgeräte Workgroup Switches Workgroup Hubs Rail Switches

Tab. 5: Manageable devices

Grundgeräte Workgroup Switches Workgroup Hubs Rail Switches

Tab. 5: Manageable devices

1.4 Supported MIBs

2.1 File structure of the HiVision CD 26

2.2 PC-StandAlone solution for Windows 27

2.3 PC-StandAlone solution for Linux 33

2.4 Integration with HP OpenView for Windows 38

2.5 Integration in HP OpenView for HP-UX 42

2.6 Trap destinations of the agent 48

2.7 OPC server under Windows 50

2.1 File structure of the

The following file structure can be presented in different ways depending on

HPUX HiVision 6.4 for HP-UX and OpenView

LINUX HiVision 6.4 for Linux

WINDOWS HiVision 6.4 for Windows 2000, XP, Vista and