Eaton Gigabit Network card (Network-M2)
Внимание, описание на Eaton Gigabit Network card (Network-M2) на сайте носит информационный характер и может отличаться от описания на Eaton Gigabit Network card (Network-M2), представленного в технической документации производителя Eaton (Powerware). Убедительно просим Вас при покупке товара проверять наличие желаемых функций и характеристик.
Уточнить технические характеристики, узнать стоимость, наличие и условия доставки Eaton Gigabit Network card (Network-M2) Вы можете позвонив по телефону, указанному в разделе «Контакты».
- Главная страница
- Каталог
- Электрооборудование и электропитание
- Аксессуары для ИБП
- Сетевая карта Eaton, Network-M2
- Загрузка цен
- Цены указаны за 1 шт с учётом НДС 20%
-
Уведомить о поступлении
Доставка в
- ПроизводительEaton
- ПродуктСетевая карта
- Описание
Гигабитная сетевая карта Eaton (Network-M2) — карта сетевого управления ИБП с современными возможностями и функциями. Сетевая карта со стабильно высокой скоростью и максимальным уровнем кибербезопасности позволяет обеспечить непрерывность бизнес-процессов за счет отправки администраторам уведомлений о неполадках.
Основные характеристики:
Скорость передачи данных: 1 Гбит/с
Количество разъемов RJ-45: 1
Максимальное энергопотребление: 25 Вт
Автоматическое определение (MDI/MDIX): есть
Габариты упаковки (ДхШхВ): 120х50х160 мм
Вес упаковки: 324 грамма
Купить сетевую карту Network-M2 производства компании Eaton можно на сайте Айдистрибьют.
Загрузка
Курьером (3-7 рабочих дней)0 руб.
(300 руб. при покупке до 5000 руб.)
Почтой России (5-10 рабочих дней)0 руб.
(300 руб. при покупке до 5000 руб.)
Самовывоз из ПВЗ (3-7 рабочих дней)0 руб.
(300 руб. при покупке до 5000 руб.)
ХАРАКТЕРИСТИКИ
Особенности
— С возможностью управления питанием
Совместимость
— 5SC (стойка) или RT, 5P, 5PX, 9SX, 9РХ
Функции
— Связь Web / SNMP
ОПИСАНИЕ
Гигабитная сетевая карта Eaton (Network-M2) — самое современное устройство подключения для ИБП Eaton, предоставляющий ИТ-специалистам новые возможности и характеристики. Благодаря более высокой скорости и защищенности гигабитная сетевая карта улучшает непрерывность бизнеса двумя способами: предоставляет предупреждения администраторам о нерешенных проблемах и помогает выполнять завершение работы серверов и хранилищ. Совместимость с моделями 5SC (стойка) или RT, 5P, 5PX, 9SX, 9РХ, 9E, 93PM, 9PHD, 91PS, 93PS, 93PS Marine.
Последние отзывы или вопросы
Нет отзывов о данном товаре.
UPS Network Management Card
Network-M2
User’s Guide
English
11/18/2019
1.7.4
Eaton is a registered trademark of Eaton Corporation or its subsidiaries and affiliates.
Phillips and Pozidriv are a registered trademarks of Phillips Screw Company.
National Electrical Code and NEC are registered trademarks of National Fire Protection Association, Inc.
Microsoft®, Windows®, and Windows Server® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. UNIX® is a registered trademark of The Open Group.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
Google™ is a trademark of Google Inc.
All other trademarks are properties of their respective companies. ©Copyright 2019 Eaton Corporation. All rights reserved.
No part of this document may be reproduced in any way without the express written approval of Eaton Corporation.
1 Table of Contents |
||
1 |
TABLE OF CONTENTS……………………………………………………………………………………………………………………. |
4 |
2 |
CONTEXTUAL HELP …………………………………………………………………………………………………………………….. |
13 |
2.1 |
Login page……………………………………………………………………………………………………………………………………………………. |
13 |
2.1.1 |
Logging in for the first time……………………………………………………………………………………………………………………….. |
13 |
2.1.2 |
Troubleshooting login issues……………………………………………………………………………………………………………………… |
13 |
2.2 |
Home…………………………………………………………………………………………………………………………………………………………… |
13 |
2.2.1 |
Menu structure………………………………………………………………………………………………………………………………………… |
14 |
2.2.2 |
Energy flow diagram…………………………………………………………………………………………………………………………………. |
16 |
2.2.2.1 |
Line interactive…………………………………………………………………………………………………………………………………….. |
16 |
2.2.2.2 |
Online…………………………………………………………………………………………………………………………………………………. |
18 |
2.2.3 |
Top bar……………………………………………………………………………………………………………………………………………………. |
20 |
2.2.4 |
Details…………………………………………………………………………………………………………………………………………………….. |
21 |
2.2.5 |
Show measures……………………………………………………………………………………………………………………………………….. |
21 |
2.2.5.1 |
Example #1………………………………………………………………………………………………………………………………………….. |
21 |
2.2.5.2 |
Example #2………………………………………………………………………………………………………………………………………….. |
21 |
2.2.6 |
Outlet status……………………………………………………………………………………………………………………………………………. |
21 |
2.2.7 |
Active Alarms ………………………………………………………………………………………………………………………………………….. |
22 |
2.3 |
Alarms …………………………………………………………………………………………………………………………………………………………. |
22 |
2.3.1 |
Alarm sorting…………………………………………………………………………………………………………………………………………… |
22 |
2.3.2 |
Alarm details……………………………………………………………………………………………………………………………………………. |
22 |
2.3.3 |
Alarm paging……………………………………………………………………………………………………………………………………………. |
22 |
2.3.4 |
Alarm export……………………………………………………………………………………………………………………………………………. |
23 |
2.3.5 |
Clear alarm logs……………………………………………………………………………………………………………………………………….. |
23 |
2.3.6 |
Alarm list with codes………………………………………………………………………………………………………………………………… |
23 |
2.4 |
Settings ……………………………………………………………………………………………………………………………………………………….. |
23 |
2.4.1 |
General…………………………………………………………………………………………………………………………………………………… |
23 |
2.4.1.1 |
Location………………………………………………………………………………………………………………………………………………. |
23 |
2.4.1.2 |
Contact……………………………………………………………………………………………………………………………………………….. |
24 |
2.4.1.3 |
System name ………………………………………………………………………………………………………………………………………. |
24 |
2.4.1.4 |
Default settings parameters and limitations……………………………………………………………………………………………… |
24 |
2.4.2 |
Date & Time ……………………………………………………………………………………………………………………………………………. |
24 |
2.4.2.1 |
Manual: Manually entering the date and time…………………………………………………………………………………………… |
24 |
2.4.2.2 |
Dynamic (NTP): Synchronizing the date and time with an NTP server………………………………………………………….. |
24 |
2.4.2.3 |
Default settings parameters and limitations……………………………………………………………………………………………… |
25 |
2.4.3 |
Users……………………………………………………………………………………………………………………………………………………… |
25 |
2.4.3.1 |
Password strength rules………………………………………………………………………………………………………………………… |
25 |
2.4.3.2 |
Account expiration………………………………………………………………………………………………………………………………… |
25 |
2.4.3.3 |
Session expiration ………………………………………………………………………………………………………………………………… |
26 |
2.4.3.4 |
Local users table…………………………………………………………………………………………………………………………………… |
26 |
2.4.3.5 |
LDAP ………………………………………………………………………………………………………………………………………………….. |
29 |
2.4.3.6 |
RADIUS ………………………………………………………………………………………………………………………………………………. |
32 |
2.4.3.7 |
Default settings parameters and limitations……………………………………………………………………………………………… |
35 |
2.4.4 |
Network………………………………………………………………………………………………………………………………………………….. |
35 |
2.4.4.1 |
LAN…………………………………………………………………………………………………………………………………………………….. |
35 |
2.4.4.2 |
IPv4…………………………………………………………………………………………………………………………………………………….. |
35 |
2.4.4.3 |
Domain……………………………………………………………………………………………………………………………………………….. |
37 |
2.4.4.4 |
IPv6…………………………………………………………………………………………………………………………………………………….. |
38 |
2.4.4.5 |
Default settings parameters and limitations……………………………………………………………………………………………… |
40 |
2.4.5 |
Protocols…………………………………………………………………………………………………………………………………………………. |
40 |
2.4.5.1 |
HTTPS…………………………………………………………………………………………………………………………………………………. |
40 |
2.4.5.2 |
Syslog…………………………………………………………………………………………………………………………………………………. |
40 |
2.4.5.3 |
Default settings parameters and limitations……………………………………………………………………………………………… |
41 |
2.4.6 |
SNMP…………………………………………………………………………………………………………………………………………………….. |
41 |
2.4.6.1 |
SNMP tables………………………………………………………………………………………………………………………………………… |
42 |
2.4.6.2 |
Trap receivers……………………………………………………………………………………………………………………………………… |
44 |
2.4.6.3 |
Actions……………………………………………………………………………………………………………………………………………….. |
45 |
2.4.6.4 |
Default settings parameters and limitations……………………………………………………………………………………………… |
46 |
2.4.7 |
Certificates ……………………………………………………………………………………………………………………………………………… |
46 |
2.4.7.1 |
Local certificates…………………………………………………………………………………………………………………………………… |
46 |
2.4.7.2 |
Certificate authorities (CA)……………………………………………………………………………………………………………………… |
48 |
2.4.7.3 |
Pairing with clients ……………………………………………………………………………………………………………………………….. |
49 |
2.4.7.4 |
Trusted remote certificates……………………………………………………………………………………………………………………. |
50 |
2.4.7.5 |
Default settings parameters and limitations……………………………………………………………………………………………… |
50 |
2.4.8 |
Email………………………………………………………………………………………………………………………………………………………. |
50 |
2.4.8.1 |
Email sending configuration …………………………………………………………………………………………………………………… |
50 |
2.4.8.2 |
Default settings parameters and limitations……………………………………………………………………………………………… |
53 |
2.4.9 |
My preferences……………………………………………………………………………………………………………………………………….. |
53 |
2.4.9.1 |
Profile …………………………………………………………………………………………………………………………………………………. |
54 |
2.4.9.2 |
Temperature………………………………………………………………………………………………………………………………………… |
54 |
2.4.9.3 |
Date format …………………………………………………………………………………………………………………………………………. |
55 |
2.4.9.4 |
Time format…………………………………………………………………………………………………………………………………………. |
55 |
2.4.9.5 |
Language ……………………………………………………………………………………………………………………………………………. |
56 |
2.4.9.6 |
Default settings parameters and limitations……………………………………………………………………………………………… |
56 |
2.5 |
Meters…………………………………………………………………………………………………………………………………………………………. |
56 |
2.5.1 |
Power…………………………………………………………………………………………………………………………………………………….. |
56 |
2.5.1.1 |
Input …………………………………………………………………………………………………………………………………………………… |
56 |
2.5.1.2 |
Output ………………………………………………………………………………………………………………………………………………… |
57 |
2.5.2 |
Battery……………………………………………………………………………………………………………………………………………………. |
57 |
2.5.2.1 |
Overview…………………………………………………………………………………………………………………………………………….. |
57 |
2.5.2.2 |
Details…………………………………………………………………………………………………………………………………………………. |
57 |
2.5.2.3 |
Test…………………………………………………………………………………………………………………………………………………….. |
57 |
2.5.3 |
Measure logs…………………………………………………………………………………………………………………………………………… |
58 |
2.5.3.1 |
Configuration……………………………………………………………………………………………………………………………………….. |
58 |
2.5.3.2 |
Measure logs……………………………………………………………………………………………………………………………………….. |
58 |
2.5.3.3 |
Default settings parameters and limitations……………………………………………………………………………………………… |
59 |
2.6 |
Controls……………………………………………………………………………………………………………………………………………………….. |
59 |
2.6.1 |
UPS………………………………………………………………………………………………………………………………………………………… |
59 |
2.6.1.1 |
Entire UPS…………………………………………………………………………………………………………………………………………… |
59 |
2.6.2 |
Outlets……………………………………………………………………………………………………………………………………………………. |
60 |
2.6.2.1 |
Group 1/ Group 2………………………………………………………………………………………………………………………………….. |
60 |
2.7 |
Protection…………………………………………………………………………………………………………………………………………………….. |
61 |
2.7.1 |
Scheduled shutdowns………………………………………………………………………………………………………………………………. |
61 |
2.7.1.1 |
Scheduled shutdowns table…………………………………………………………………………………………………………………… |
61 |
2.7.1.2 |
Actions………………………………………………………………………………………………………………………………………………… |
61 |
2.7.2 |
Agent list ………………………………………………………………………………………………………………………………………………… |
62 |
2.7.2.1 |
Pairing with shutdown agents………………………………………………………………………………………………………………… |
62 |
2.7.2.2 |
Agent list table……………………………………………………………………………………………………………………………………… |
62 |
2.7.2.3 |
Actions………………………………………………………………………………………………………………………………………………… |
63 |
2.7.3 |
Agent settings…………………………………………………………………………………………………………………………………………. |
63 |
2.7.3.1 |
Agent shutdown sequence timing ………………………………………………………………………………………………………….. |
63 |
2.7.3.2 |
Actions………………………………………………………………………………………………………………………………………………… |
64 |
2.7.3.3 |
Examples…………………………………………………………………………………………………………………………………………….. |
64 |
2.7.4 |
Power outage policy…………………………………………………………………………………………………………………………………. |
64 |
2.7.4.1 |
On power outage………………………………………………………………………………………………………………………………….. |
65 |
2.7.4.2 |
On low battery warning…………………………………………………………………………………………………………………………. |
69 |
2.7.4.3 |
When utility comes back……………………………………………………………………………………………………………………….. |
70 |
2.8 |
Card…………………………………………………………………………………………………………………………………………………………….. |
70 |
2.8.1 |
System information………………………………………………………………………………………………………………………………….. |
70 |
2.8.1.1 |
Identification………………………………………………………………………………………………………………………………………… |
70 |
2.8.1.2 |
Firmware information……………………………………………………………………………………………………………………………. |
71 |
2.8.2 |
Resources……………………………………………………………………………………………………………………………………………….. |
71 |
2.8.2.1 |
Processor…………………………………………………………………………………………………………………………………………….. |
71 |
2.8.2.2 |
Memory………………………………………………………………………………………………………………………………………………. |
71 |
2.8.2.3 |
Storage……………………………………………………………………………………………………………………………………………….. |
72 |
2.8.3 |
System logs…………………………………………………………………………………………………………………………………………….. |
72 |
2.8.4 |
Administration …………………………………………………………………………………………………………………………………………. |
73 |
2.8.4.1 |
Network module firmware …………………………………………………………………………………………………………………….. |
73 |
2.8.4.2 |
Sanitization ………………………………………………………………………………………………………………………………………….. |
74 |
2.8.4.3 |
Reboot………………………………………………………………………………………………………………………………………………… |
75 |
2.8.4.4 |
Maintenance………………………………………………………………………………………………………………………………………… |
75 |
2.8.4.5 |
Settings ………………………………………………………………………………………………………………………………………………. |
76 |
2.8.5 |
Commissioning (sensors)………………………………………………………………………………………………………………………….. |
78 |
2.8.5.1 |
Sensors commissioning table…………………………………………………………………………………………………………………. |
78 |
2.8.5.2 |
Actions………………………………………………………………………………………………………………………………………………… |
78 |
2.8.5.3 |
Note:…………………………………………………………………………………………………………………………………………………… |
81 |
2.9 |
Sensors………………………………………………………………………………………………………………………………………………………… |
81 |
2.9.1 |
Status (sensors)……………………………………………………………………………………………………………………………………….. |
81 |
2.9.1.1 |
Temperature table………………………………………………………………………………………………………………………………… |
81 |
2.9.1.2 |
Humidity table ……………………………………………………………………………………………………………………………………… |
81 |
2.9.1.3 |
Dry contacts table…………………………………………………………………………………………………………………………………. |
82 |
2.9.2 |
Alarm configuration (sensors)…………………………………………………………………………………………………………………….. |
82 |
2.9.2.1 |
Temperature………………………………………………………………………………………………………………………………………… |
82 |
2.9.2.2 |
Humidity……………………………………………………………………………………………………………………………………………… |
83 |
2.9.2.3 |
Dry contacts ………………………………………………………………………………………………………………………………………… |
84 |
2.9.2.4 |
Default settings parameters and limitations……………………………………………………………………………………………… |
84 |
2.9.3 |
Information (sensors)………………………………………………………………………………………………………………………………… |
84 |
2.10 |
Legal information (footer)……………………………………………………………………………………………………………………………….. |
85 |
2.10.1 |
Component list………………………………………………………………………………………………………………………………………… |
85 |
2.10.2 |
Notice for our proprietary (i.e. non-Open source) elements……………………………………………………………………………. |
85 |
2.10.3 |
Availability of source code…………………………………………………………………………………………………………………………. |
86 |
2.11 |
Contextual help and full documentation……………………………………………………………………………………………………………. |
86 |
2.11.1 |
Access to contextual help …………………………………………………………………………………………………………………………. |
86 |
2.11.2 |
Access to full documentation…………………………………………………………………………………………………………………….. |
86 |
3 |
SERVICING THE NETWORK MANAGEMENT MODULE……………………………………………………………………. |
88 |
3.1 |
Unpacking the Network module………………………………………………………………………………………………………………………. |
88 |
3.2 |
Installing the Network Module………………………………………………………………………………………………………………………… |
88 |
3.2.1 |
Mounting the Network Module………………………………………………………………………………………………………………….. |
88 |
3.3 |
Accessing the Network Module………………………………………………………………………………………………………………………. |
88 |
3.3.1 |
Accessing the web interface through Network…………………………………………………………………………………………….. |
88 |
3.3.1.1 |
Connecting the network cable………………………………………………………………………………………………………………… |
88 |
3.3.1.2 |
Accessing the web interface………………………………………………………………………………………………………………….. |
89 |
3.3.2 |
Finding and setting the IP address……………………………………………………………………………………………………………… |
89 |
3.3.2.1 |
Your network is equipped with a BOOTP/DHCP server (default)…………………………………………………………………. |
89 |
3.3.2.2 |
Your network is not equipped with a BOOTP/DHCP server………………………………………………………………………… |
89 |
3.3.3 |
Accessing the web interface through RNDIS……………………………………………………………………………………………….. |
90 |
3.3.3.1 |
Connecting the configuration cable…………………………………………………………………………………………………………. |
90 |
3.3.3.2 |
Web interface access through RNDIS……………………………………………………………………………………………………… |
90 |
3.3.4 |
Accessing the card through serial terminal emulation……………………………………………………………………………………. |
92 |
3.3.4.1 |
Connecting the configuration cable…………………………………………………………………………………………………………. |
92 |
3.3.4.2 |
Manual configuration of the serial connection…………………………………………………………………………………………… |
93 |
3.3.4.3 |
Accessing the card through Serial…………………………………………………………………………………………………………… |
94 |
3.3.5 |
Modifying the Proxy exception list……………………………………………………………………………………………………………… |
94 |
3.4 |
Configuring the Network Module settings………………………………………………………………………………………………………… |
96 |
3.5 |
Configuring/Commissioning/Testing LDAP ……………………………………………………………………………………………………….. |
97 |
3.5.1 |
Commissioning………………………………………………………………………………………………………………………………………… |
97 |
3.5.1.1 |
Configuring connection to LDAP database……………………………………………………………………………………………….. |
97 |
3.5.1.2 |
Testing connection to LDAP database …………………………………………………………………………………………………….. |
97 |
3.5.1.3 |
Map remote users to profile…………………………………………………………………………………………………………………… |
98 |
3.5.1.4 |
Testing profile mapping ………………………………………………………………………………………………………………………… |
98 |
3.5.1.5 |
Define LDAP user’s preferences…………………………………………………………………………………………………………….. |
98 |
3.5.2 |
Testing LDAP authentication……………………………………………………………………………………………………………………… |
98 |
3.5.3 |
Limitations………………………………………………………………………………………………………………………………………………. |
98 |
3.6 |
Pairing agent to the Network Module ………………………………………………………………………………………………………………. |
98 |
3.6.1 |
Pairing with credentials on the agent………………………………………………………………………………………………………….. |
99 |
3.6.2 |
Pairing with automatic acceptance (recommended if done in a secure and trusted network)……………………………… |
99 |
3.6.3 |
Pairing with manual acceptance ………………………………………………………………………………………………………………… |
99 |
3.7 |
Powering down/up applications (examples)…………………………………………………………………………………………………….. |
100 |
3.7.1 |
Powering down IT system in a specific order …………………………………………………………………………………………….. |
100 |
3.7.1.1 |
Target ……………………………………………………………………………………………………………………………………………….. |
100 |
3.7.1.2 |
Step 1: Installation setup……………………………………………………………………………………………………………………… |
100 |
3.7.1.3 |
Step 2: Agent settings…………………………………………………………………………………………………………………………. |
101 |
3.7.1.4 |
Step 3: Power outage policy settings…………………………………………………………………………………………………….. |
101 |
3.7.2 |
Powering down non-priority equipment first………………………………………………………………………………………………. |
102 |
3.7.2.1 |
Target ……………………………………………………………………………………………………………………………………………….. |
102 |
3.7.2.2 |
Step 1: Installation setup……………………………………………………………………………………………………………………… |
103 |
3.7.2.3 |
Step 2: Agent settings…………………………………………………………………………………………………………………………. |
103 |
3.7.2.4 |
Step 3: Power outage policy settings…………………………………………………………………………………………………….. |
104 |
3.7.3 |
Restart sequentially the IT equipment on utility recovery …………………………………………………………………………….. |
105 |
3.7.3.1 |
Target ……………………………………………………………………………………………………………………………………………….. |
105 |
3.7.3.2 |
Step 1: Installation setup……………………………………………………………………………………………………………………… |
106 |
3.7.3.3 |
Step 2: Power outage policy settings…………………………………………………………………………………………………….. |
106 |
3.8 |
Checking the current firmware version of the Network Module…………………………………………………………………………. |
107 |
3.9 |
Accessing to the latest Network Module firmware/driver/script…………………………………………………………………………. |
107 |
3.10 |
Upgrading the card firmware (Web interface / shell script)………………………………………………………………………………… |
107 |
3.10.1 |
Web interface………………………………………………………………………………………………………………………………………… |
107 |
3.10.2 |
Shell script…………………………………………………………………………………………………………………………………………….. |
107 |
3.10.2.1 |
Prerequisite ……………………………………………………………………………………………………………………………………….. |
107 |
3.10.2.2 |
Procedure………………………………………………………………………………………………………………………………………….. |
107 |
3.10.3 |
Example:……………………………………………………………………………………………………………………………………………….. |
108 |
3.11 |
Changing the RTC battery cell……………………………………………………………………………………………………………………….. |
108 |
3.12 |
Updating the time of the Network Module precisely and permanently (ntp server) ………………………………………………. |
110 |
3.13 |
Synchronizing the time of the Network Module and the UPS…………………………………………………………………………….. |
110 |
3.13.1 |
Automatic time synchronization……………………………………………………………………………………………………………….. |
110 |
3.13.1.1 |
Every day at 5 a.m………………………………………………………………………………………………………………………………. |
110 |
3.13.1.2 |
If the Network Module time is lost………………………………………………………………………………………………………… |
110 |
3.13.2 |
Manual time synchronization……………………………………………………………………………………………………………………. |
110 |
3.13.2.1 |
From the Network Module…………………………………………………………………………………………………………………… |
110 |
3.13.2.2 |
From the UPS…………………………………………………………………………………………………………………………………….. |
110 |
3.14 |
Changing the language of the web pages……………………………………………………………………………………………………….. |
110 |
3.15 |
Resetting username and password………………………………………………………………………………………………………………… |
111 |
3.15.1 |
As an admin for other users…………………………………………………………………………………………………………………….. |
111 |
3.15.2 |
Resetting its own password…………………………………………………………………………………………………………………….. |
111 |
3.16 |
Recovering main administrator password……………………………………………………………………………………………………….. |
111 |
3.17 |
Switching to static IP (Manual) / Changing IP address of the Network Module…………………………………………………….. |
112 |
3.18 |
Reading product (UPS) information in a simple way …………………………………………………………………………………………. |
112 |
3.18.1 |
Web page……………………………………………………………………………………………………………………………………………… |
112 |
3.19 |
Subscribing to a set of alarms for email notification………………………………………………………………………………………….. |
113 |
3.19.1 |
Example #1: subscribing only to one alarm (load unprotected)……………………………………………………………………… |
113 |
3.19.2 |
Example #2: subscribing to all Critical alarms and some specific Warnings ……………………………………………………. |
115 |
3.20 |
Saving/Restoring/Duplicating Network module configuration settings ………………………………………………………………… |
117 |
3.20.1 |
Modifying the JSON configuration settings file…………………………………………………………………………………………… |
117 |
3.20.1.1 |
JSON file structure……………………………………………………………………………………………………………………………… |
117 |
3.20.1.2 |
Sensitive data (like passwords) …………………………………………………………………………………………………………….. |
118 |
3.20.1.3 |
Modifying JSON file examples……………………………………………………………………………………………………………… |
119 |
3.20.1.4 |
Non-intuitive data values in the JSON file………………………………………………………………………………………………. |
121 |
3.20.2 |
Saving/Restoring/Duplicating settings through the CLI………………………………………………………………………………… |
124 |
3.20.3 |
Saving/Restoring/Duplicating settings through the Web interface…………………………………………………………………. |
124 |
4 |
SECURING THE NETWORK MANAGEMENT MODULE…………………………………………………………………… |
125 |
4.1 |
Cybersecurity considerations for electrical distribution systems ………………………………………………………………………… |
125 |
4.1.1 |
Purpose ………………………………………………………………………………………………………………………………………………… |
125 |
4.1.2 |
Introduction …………………………………………………………………………………………………………………………………………… |
125 |
4.1.3 |
Connectivity—why do we need to address cybersecurity for industrial control systems (ICS)? ………………………… |
125 |
4.1.4 |
Cybersecurity threat vectors ……………………………………………………………………………………………………………………. |
125 |
4.1.4.1 |
Paths to the control network………………………………………………………………………………………………………………… |
126 |
4.1.5 |
Defense in depth……………………………………………………………………………………………………………………………………. |
126 |
4.1.6 |
Designing for the threat vectors……………………………………………………………………………………………………………….. |
127 |
4.1.6.1 |
Firewalls ……………………………………………………………………………………………………………………………………………. |
127 |
4.1.6.2 |
Demilitarized zones (DMZ) …………………………………………………………………………………………………………………… |
127 |
4.1.6.3 |
Intrusion detection and prevention systems (IDPS)…………………………………………………………………………………. |
129 |
4.1.7 |
Policies, procedures, standards, and guidelines………………………………………………………………………………………….. |
129 |
4.1.7.1 |
Understanding an ICS network……………………………………………………………………………………………………………… |
129 |
4.1.7.2 |
Log and event management…………………………………………………………………………………………………………………. |
129 |
4.1.7.3 |
Security policy and procedures……………………………………………………………………………………………………………… |
130 |
4.1.7.4 |
ICS hardening…………………………………………………………………………………………………………………………………….. |
130 |
4.1.7.5 |
Continuous assessment and security training…………………………………………………………………………………………. |
130 |
4.1.7.6 |
Patch management planning and procedures…………………………………………………………………………………………. |
131 |
4.1.8 |
Conclusion…………………………………………………………………………………………………………………………………………….. |
131 |
4.1.9 |
Terms and definitions……………………………………………………………………………………………………………………………… |
131 |
4.1.10 |
Acronyms ……………………………………………………………………………………………………………………………………………… |
131 |
4.1.11 |
References……………………………………………………………………………………………………………………………………………. |
132 |
4.2 |
Cybersecurity recommended secure hardening guidelines ……………………………………………………………………………….. |
133 |
4.2.1 |
Introduction …………………………………………………………………………………………………………………………………………… |
133 |
4.2.2 |
Secure configuration guidelines ……………………………………………………………………………………………………………….. |
133 |
4.2.2.1 |
Asset identification and Inventory…………………………………………………………………………………………………………. |
133 |
4.2.2.2 |
Physical Protection……………………………………………………………………………………………………………………………… |
134 |
4.2.2.3 |
Authorization and Access Control………………………………………………………………………………………………………….. |
134 |
4.2.2.4 |
Deactivate unused features………………………………………………………………………………………………………………….. |
135 |
4.2.2.5 |
Logging and Event Management ………………………………………………………………………………………………………….. |
136 |
4.2.2.6 |
Secure Maintenance……………………………………………………………………………………………………………………………. |
136 |
4.2.3 |
References……………………………………………………………………………………………………………………………………………. |
136 |
4.3 |
Configuring user permissions through profiles…………………………………………………………………………………………………. |
137 |
4.4 |
Decommissioning the Network Management module ……………………………………………………………………………………… |
137 |
5 |
SERVICING THE EMP …………………………………………………………………………………………………………………. |
138 |
5.1 |
Description and features ………………………………………………………………………………………………………………………………. |
138 |
5.2 |
Unpacking the EMP……………………………………………………………………………………………………………………………………… |
138 |
5.3 |
Installing the EMP ……………………………………………………………………………………………………………………………………….. |
139 |
5.3.1 |
Defining EMPs address and termination……………………………………………………………………………………………………. |
139 |
5.3.1.1 |
Manual addressing ……………………………………………………………………………………………………………………………… |
139 |
5.3.2 |
Mounting the EMP…………………………………………………………………………………………………………………………………. |
139 |
5.3.2.1 |
Rack mounting with keyhole example……………………………………………………………………………………………………. |
140 |
5.3.2.2 |
Rack mounting with tie wraps example…………………………………………………………………………………………………. |
140 |
5.3.2.3 |
Wall mounting with screws example…………………………………………………………………………………………………….. |
141 |
5.3.2.4 |
Wall mounting with nylon fastener example…………………………………………………………………………………………… |
141 |
5.3.3 |
Cabling the first EMP to the device…………………………………………………………………………………………………………… |
142 |
5.3.3.1 |
Available Devices………………………………………………………………………………………………………………………………… |
142 |
5.3.3.2 |
Connecting the EMP to the device………………………………………………………………………………………………………… |
142 |
5.3.4 |
Daisy chaining EMPs………………………………………………………………………………………………………………………………. |
143 |
5.3.4.1 |
Material needed:…………………………………………………………………………………………………………………………………. |
143 |
5.3.4.2 |
Steps ………………………………………………………………………………………………………………………………………………… |
144 |
5.3.5 |
Connecting an external contact device………………………………………………………………………………………………………. |
144 |
5.4 |
Commissioning the EMP………………………………………………………………………………………………………………………………. |
144 |
5.4.1 |
On the Network-M2 device……………………………………………………………………………………………………………………… |
144 |
5.5 |
Using the EMP for temperature compensated battery charging…………………………………………………………………………. |
145 |
5.5.1 |
Addressing the EMP……………………………………………………………………………………………………………………………….. |
145 |
5.5.2 |
Commissioning the EMP…………………………………………………………………………………………………………………………. |
146 |
5.5.3 |
Enabling temperature compensated battery charging in the UPS………………………………………………………………….. |
146 |
6 |
INFORMATION…………………………………………………………………………………………………………………………… |
147 |
6.1 |
Front panel connectors and LED indicators……………………………………………………………………………………………………… |
147 |
6.2 |
Default settings and possible parameters……………………………………………………………………………………………………….. |
148 |
6.2.1 |
Settings ………………………………………………………………………………………………………………………………………………… |
148 |
6.2.1.1 |
General……………………………………………………………………………………………………………………………………………… |
148 |
6.2.1.2 |
Date & Time ………………………………………………………………………………………………………………………………………. |
148 |
6.2.1.3 |
Users………………………………………………………………………………………………………………………………………………… |
148 |
6.2.1.4 |
Network…………………………………………………………………………………………………………………………………………….. |
151 |
6.2.1.5 |
Protocols……………………………………………………………………………………………………………………………………………. |
151 |
6.2.1.6 |
SNMP……………………………………………………………………………………………………………………………………………….. |
152 |
6.2.1.7 |
Certificate………………………………………………………………………………………………………………………………………….. |
153 |
6.2.1.8 |
Email…………………………………………………………………………………………………………………………………………………. |
154 |
6.2.1.9 |
My preferences………………………………………………………………………………………………………………………………….. |
154 |
6.2.2 |
Meters………………………………………………………………………………………………………………………………………………….. |
155 |
6.2.3 |
Sensors alarm configuration…………………………………………………………………………………………………………………….. |
155 |
6.3 |
Specifications/Technical characteristics ………………………………………………………………………………………………………….. |
156 |
6.4 |
List of event codes………………………………………………………………………………………………………………………………………. |
156 |
6.5 |
Alarm log codes…………………………………………………………………………………………………………………………………………… |
156 |
6.5.1 |
Critical…………………………………………………………………………………………………………………………………………………… |
157 |
6.5.2 |
Warning………………………………………………………………………………………………………………………………………………… |
158 |
6.5.3 |
Info ………………………………………………………………………………………………………………………………………………………. |
160 |
6.5.4 |
With settable severity……………………………………………………………………………………………………………………………… |
161 |
6.6 |
System log codes………………………………………………………………………………………………………………………………………… |
162 |
6.6.1 |
Critical…………………………………………………………………………………………………………………………………………………… |
162 |
6.6.2 |
Warning………………………………………………………………………………………………………………………………………………… |
162 |
6.6.3 |
Info ………………………………………………………………………………………………………………………………………………………. |
163 |
6.7 |
SNMP traps………………………………………………………………………………………………………………………………………………… |
165 |
6.7.1 |
Sensor Mib traps……………………………………………………………………………………………………………………………………. |
165 |
6.7.2 |
Xups Mib traps ………………………………………………………………………………………………………………………………………. |
165 |
6.7.3 |
IETF Mib-2 Ups traps………………………………………………………………………………………………………………………………. |
166 |
6.8 |
CLI…………………………………………………………………………………………………………………………………………………………….. |
166 |
6.8.1 |
Commands available……………………………………………………………………………………………………………………………….. |
167 |
6.8.2 |
Contextual help………………………………………………………………………………………………………………………………………. |
167 |
6.8.3 |
get release info………………………………………………………………………………………………………………………………………. |
168 |
6.8.3.1 |
Description ………………………………………………………………………………………………………………………………………… |
168 |
6.8.3.2 |
Access………………………………………………………………………………………………………………………………………………. |
168 |
6.8.3.3 |
Help………………………………………………………………………………………………………………………………………………….. |
168 |
6.8.4 |
history…………………………………………………………………………………………………………………………………………………… |
168 |
6.8.4.1 |
Description ………………………………………………………………………………………………………………………………………… |
168 |
6.8.4.2 |
Access………………………………………………………………………………………………………………………………………………. |
168 |
6.8.4.3 |
Help………………………………………………………………………………………………………………………………………………….. |
168 |
6.8.5 |
ldap-test………………………………………………………………………………………………………………………………………………… |
168 |
6.8.5.1 |
Description ………………………………………………………………………………………………………………………………………… |
168 |
6.8.5.2 |
Access………………………………………………………………………………………………………………………………………………. |
169 |
6.8.5.3 |
Help………………………………………………………………………………………………………………………………………………….. |
169 |
6.8.6 |
logout……………………………………………………………………………………………………………………………………………………. |
169 |
6.8.6.1 |
Description ………………………………………………………………………………………………………………………………………… |
169 |
6.8.6.2 |
Access………………………………………………………………………………………………………………………………………………. |
170 |
6.8.6.3 |
Help………………………………………………………………………………………………………………………………………………….. |
170 |
6.8.7 |
maintenance………………………………………………………………………………………………………………………………………….. |
170 |
6.8.7.1 |
Description ………………………………………………………………………………………………………………………………………… |
170 |
6.8.7.2 |
Access………………………………………………………………………………………………………………………………………………. |
170 |
6.8.7.3 |
Help………………………………………………………………………………………………………………………………………………….. |
170 |
6.8.8 |
netconf …………………………………………………………………………………………………………………………………………………. |
170 |
6.8.8.1 |
Description ………………………………………………………………………………………………………………………………………… |
170 |
6.8.8.2 |
Access………………………………………………………………………………………………………………………………………………. |
170 |
6.8.8.3 |
Help………………………………………………………………………………………………………………………………………………….. |
170 |
6.8.8.4 |
Examples of usage……………………………………………………………………………………………………………………………… |
173 |
6.8.9 |
ping and ping6……………………………………………………………………………………………………………………………………….. |
173 |
6.8.9.1 |
Description ………………………………………………………………………………………………………………………………………… |
173 |
6.8.9.2 |
Access………………………………………………………………………………………………………………………………………………. |
173 |
6.8.9.3 |
Help………………………………………………………………………………………………………………………………………………….. |
173 |
6.8.10 |
reboot…………………………………………………………………………………………………………………………………………………… |
173 |
6.8.10.1 |
Description ………………………………………………………………………………………………………………………………………… |
173 |
6.8.10.2 |
Access………………………………………………………………………………………………………………………………………………. |
174 |
6.8.10.3 |
Help………………………………………………………………………………………………………………………………………………….. |
174 |
6.8.11 |
save_configuration | restore_configuration…………………………………………………………………………………………………. |
174 |
6.8.11.1 |
Description ………………………………………………………………………………………………………………………………………… |
174 |
6.8.11.2 |
Access………………………………………………………………………………………………………………………………………………. |
174 |
6.8.11.3 |
Help………………………………………………………………………………………………………………………………………………….. |
174 |
6.8.11.4 |
Examples of usage……………………………………………………………………………………………………………………………… |
174 |
6.8.12 |
sanitize………………………………………………………………………………………………………………………………………………….. |
175 |
6.8.12.1 |
Description ………………………………………………………………………………………………………………………………………… |
175 |
6.8.12.2 |
Access………………………………………………………………………………………………………………………………………………. |
175 |
6.8.12.3 |
Help………………………………………………………………………………………………………………………………………………….. |
175 |
6.8.13 |
ssh-keygen ……………………………………………………………………………………………………………………………………………. |
175 |
6.8.13.1 |
Description ………………………………………………………………………………………………………………………………………… |
175 |
6.8.13.2 |
Access………………………………………………………………………………………………………………………………………………. |
175 |
6.8.13.3 |
Help………………………………………………………………………………………………………………………………………………….. |
175 |
6.8.14 |
time ……………………………………………………………………………………………………………………………………………………… |
175 |
6.8.14.1 |
Description ………………………………………………………………………………………………………………………………………… |
175 |
6.8.14.2 |
Access………………………………………………………………………………………………………………………………………………. |
175 |
6.8.14.3 |
Help………………………………………………………………………………………………………………………………………………….. |
175 |
6.8.14.4 |
Examples of usage……………………………………………………………………………………………………………………………… |
176 |
6.8.15 |
traceroute and traceroute6………………………………………………………………………………………………………………………. |
176 |
6.8.15.1 |
Description ………………………………………………………………………………………………………………………………………… |
176 |
6.8.15.2 |
Access………………………………………………………………………………………………………………………………………………. |
176 |
6.8.15.3 |
Help………………………………………………………………………………………………………………………………………………….. |
176 |
6.8.16 |
whoami…………………………………………………………………………………………………………………………………………………. |
177 |
6.8.16.1 |
Description ………………………………………………………………………………………………………………………………………… |
177 |
6.8.16.2 |
Access………………………………………………………………………………………………………………………………………………. |
177 |
6.8.17 |
email-test………………………………………………………………………………………………………………………………………………. |
177 |
6.8.17.1 |
Description ………………………………………………………………………………………………………………………………………… |
177 |
6.8.17.2 |
Access………………………………………………………………………………………………………………………………………………. |
177 |
6.8.17.3 |
Help………………………………………………………………………………………………………………………………………………….. |
177 |
6.8.18 |
systeminfo_statistics………………………………………………………………………………………………………………………………. |
177 |
6.8.18.1 |
Description ………………………………………………………………………………………………………………………………………… |
177 |
6.8.18.2 |
Access………………………………………………………………………………………………………………………………………………. |
178 |
6.8.18.3 |
Help………………………………………………………………………………………………………………………………………………….. |
178 |
6.8.19 |
certificates…………………………………………………………………………………………………………………………………………….. |
178 |
6.8.19.1 |
Description ………………………………………………………………………………………………………………………………………… |
178 |
6.8.19.2 |
Access………………………………………………………………………………………………………………………………………………. |
178 |
6.8.19.3 |
Help………………………………………………………………………………………………………………………………………………….. |
178 |
6.8.19.4 |
Examples of usage……………………………………………………………………………………………………………………………… |
179 |
6.9 |
Legal information…………………………………………………………………………………………………………………………………………. |
179 |
6.9.1 |
Availability of Source Code………………………………………………………………………………………………………………………. |
179 |
6.9.2 |
Notice for Open Source Elements…………………………………………………………………………………………………………….. |
179 |
6.9.3 |
Notice for our proprietary (i.e. non-Open source) elements………………………………………………………………………….. |
180 |
6.10 |
Acronyms and abbreviations …………………………………………………………………………………………………………………………. |
181 |
7 |
TROUBLESHOOTING………………………………………………………………………………………………………………….. |
184 |
7.1 |
Action not allowed in Control/Schedule/Power outage policy…………………………………………………………………………….. |
184 |
7.1.1 |
Symptom………………………………………………………………………………………………………………………………………………. |
184 |
7.1.2 |
Possible Cause………………………………………………………………………………………………………………………………………. |
184 |
7.1.3 |
Action …………………………………………………………………………………………………………………………………………………… |
184 |
7.2 |
Client server is not restarting ………………………………………………………………………………………………………………………… |
184 |
7.2.1 |
Symptom………………………………………………………………………………………………………………………………………………. |
184 |
7.2.2 |
Possible Cause………………………………………………………………………………………………………………………………………. |
184 |
7.2.3 |
Action …………………………………………………………………………………………………………………………………………………… |
184 |
7.3 |
EMP detection fails at discovery stage …………………………………………………………………………………………………………… |
184 |
7.3.1 |
Symptom #1………………………………………………………………………………………………………………………………………….. |
184 |
7.3.1.1 |
Possible causes………………………………………………………………………………………………………………………………….. |
184 |
7.3.1.2 |
Action #1-1 ………………………………………………………………………………………………………………………………………… |
185 |
7.3.1.3 |
Action #1-2 ………………………………………………………………………………………………………………………………………… |
185 |
7.3.1.4 |
Action #1-3 ………………………………………………………………………………………………………………………………………… |
185 |
7.3.2 |
Symptom #2………………………………………………………………………………………………………………………………………….. |
185 |
7.3.2.1 |
Possible causes………………………………………………………………………………………………………………………………….. |
185 |
7.3.2.2 |
Action #2-1 ………………………………………………………………………………………………………………………………………… |
185 |
7.3.2.3 |
Action #2-2 ………………………………………………………………………………………………………………………………………… |
185 |
7.4 |
How do I log in if I forgot my password? ………………………………………………………………………………………………………… |
185 |
7.4.1 |
Action …………………………………………………………………………………………………………………………………………………… |
185 |
7.5 |
Card wrong timestamp leads to «Full acquisition has failed» error message on IPM/IPP ………………………………………… |
186 |
7.5.1 |
Symptoms:……………………………………………………………………………………………………………………………………………. |
186 |
7.5.2 |
Possible cause:………………………………………………………………………………………………………………………………………. |
186 |
7.5.3 |
Action: ………………………………………………………………………………………………………………………………………………….. |
186 |
7.6 |
IPP/IPM is not able to communicate with the Network module …………………………………………………………………………. |
186 |
7.6.1 |
Symptoms…………………………………………………………………………………………………………………………………………….. |
186 |
7.6.2 |
Possible cause……………………………………………………………………………………………………………………………………….. |
186 |
7.6.3 |
Setup……………………………………………………………………………………………………………………………………………………. |
186 |
7.6.4 |
Action #1 ………………………………………………………………………………………………………………………………………………. |
186 |
7.6.5 |
Action #2 ………………………………………………………………………………………………………………………………………………. |
187 |
7.7 |
LDAP configuration/commissioning is not working…………………………………………………………………………………………… |
187 |
7.8 |
Password change in My preferences is not working ………………………………………………………………………………………… |
187 |
7.8.1 |
Symptoms…………………………………………………………………………………………………………………………………………….. |
187 |
7.8.2 |
Possible cause……………………………………………………………………………………………………………………………………….. |
187 |
7.8.3 |
Action …………………………………………………………………………………………………………………………………………………… |
187 |
7.9 |
SNMPv3 password management issue with Save and Restore…………………………………………………………………………. |
188 |
7.9.1 |
Affected FW versions……………………………………………………………………………………………………………………………… |
188 |
7.9.2 |
Symptom………………………………………………………………………………………………………………………………………………. |
188 |
7.9.3 |
Cause……………………………………………………………………………………………………………………………………………………. |
188 |
7.9.4 |
Action …………………………………………………………………………………………………………………………………………………… |
188 |
7.10 |
The Network Module fails to boot after upgrading the firmware………………………………………………………………………… |
188 |
7.10.1 |
Possible Cause………………………………………………………………………………………………………………………………………. |
188 |
7.10.2 |
Action …………………………………………………………………………………………………………………………………………………… |
188 |
7.11 |
Web user interface is not up to date after a FW upgrade………………………………………………………………………………….. |
188 |
7.11.1 |
Symptom………………………………………………………………………………………………………………………………………………. |
188 |
7.11.1.1 |
Possible causes………………………………………………………………………………………………………………………………….. |
188 |
7.11.1.2 |
Action ……………………………………………………………………………………………………………………………………………….. |
188 |
Login page
2 Contextual Help
2.1 Login page
The page language is set to English by default but can be switched to browser language when it is managed. After navigating to the assigned IP address, accept the untrusted certificate on the browser.
2.1.1 Logging in for the first time
1. Enter default password
As you are logging into the Network Module for the first time you must enter the factory set default username and password.
•Username = admin
•Password = admin
2.Change default password
Changing the default password is mandatory and requested in a dedicated window.
Enter your current password first, and then enter the new password twice.
Follow the password format recommendations on the tooltip in order to define a secure password.
3. Accept license agreement
On the next step, License Agreement is displayed.
Read and accept the agreement to continue.
2.1.2 Troubleshooting login issues
For details on troubleshooting, see the Troubleshooting section.
2.2 Home
The Home screen provides status information for the device including synoptic diagrams, key measures and active alarms.
Contextual Help – 13
Home
2.2.1 Menu structure
Button |
Description |
Home |
Overview and status of UPS Module: |
• |
Synoptic |
|
• |
Active alarms |
|
• |
Outlet status |
|
Settings |
Module settings: |
|
• |
General |
|
• |
Date & Time |
|
• |
Users |
|
• |
Network |
|
• |
Protocols |
|
• |
SNMP |
|
• |
Certificates |
|
• |
|
|
• |
My preferences |
|
Alarms |
List of alarms with date and time: |
|
• |
Details |
|
• |
Clear |
|
• |
Export |
Contextual Help – 14
Meters
Controls
Protection
Sensors*
Card
Home
Power:
•Frequency
•Voltage
•Current
•Power
Battery:
•Overview
•Details
•Test
Measure logs:
•Configuration
•Measure logs
Control of:
•Entire UPS
•Outlets
•Scheduled shutdown
•Agent list
•Agent settings
•Power outage policy
•Status
•Alarm configuration
•Information
•System information
•System logs
•Administration
•Commissioning (Sensors)
* Displayed when sensors are commissioned in Card menu.
Contextual Help – 15
Home
2.2.2 Energy flow diagram
2.2.2.1 Line interactive
2.2.2.1.1 Diagram elements description
Description and |
Description |
Possible states |
|||
symbols |
|||||
Green |
Yellow |
Red |
Black / White / |
||
Greyed |
|||||
Input |
Main utility input. |
Powered |
Out of nominal range |
Not present |
|
Unknown |
|||||
AVR device. |
The equipment is |
Normal mode |
In overload |
Not powered |
|
protected and powered |
Buck mode |
Unknown |
|||
through an AVR device. |
|||||
Boost mode |
|||||
Output |
Output of the UPS. |
Protected |
In overload |
In short circuit |
Not powered |
Not protected |
Unknown |
||||
Charger |
Internal battery charger. |
Charging |
In fault |
Resting |
|
Floating |
Not powered |
||||
Unknown |
|||||
Battery status |
Battery status information. |
Powering the load |
End of life |
In fault |
Not used to power |
Not present |
the load |
||||
Unknown |
Contextual Help – 16
Home
Battery level |
Battery level for the |
> 50% |
< 50% |
backup power. |
and |
and |
|
> low battery |
> low battery |
||
threshold (Settable |
threshold (Settable |
||
on the UPS) |
on the UPS) |
< Below low battery threshold (Settable on the UPS)
Inverter |
Inverter: convert DC |
Powered |
In overload |
In short circuit |
Not powered |
power to AC power. |
In fault |
Unknown |
|||
Wiring |
Electrical connection |
Energy flow |
In overload |
No energy |
between blocks. |
Out of nominal range |
Unknown |
||
2.2.2.1.2 Line interactive diagram examples
Normal mode
Buck/Boost mode
Contextual Help – 17
Home
Battery mode
2.2.2.2 Online
2.2.2.2.1 Diagram elements description
Description and |
Description |
Possible states |
|||
symbols |
|||||
Green |
Yellow |
Red |
Black or white |
||
Input |
Main utility or second |
Powered |
Out of nominal range |
Not present |
|
utility. |
Unknown |
||||
Rectifier |
Rectifier: convert AC |
Powered |
In overload |
In short circuit |
Not powered |
power to DC power. |
HE mode (ready) / ESS |
In fault |
Unknown |
||
mode (ready) |
Inverter |
Inverter: convert DC |
Powered |
In overload |
In short circuit |
Not powered |
power to AC power. |
HE mode (ready) / ESS |
In fault |
Unknown |
||
mode (ready) |
Contextual Help – 18
Home |
|||||
Output |
Output of the UPS. |
Protected |
In overload |
In short circuit |
Not powered |
Not protected |
Unknown |
||||
Charger |
Internal battery |
Charging |
In fault |
Resting |
|
charger. |
Floating |
Not powered |
|||
Unknown |
|||||
Battery status |
Battery status |
Powering the load |
End of life |
In fault |
Not used to power the |
information. |
Not present |
load |
|||
Unknown |
Battery level |
Battery level for the |
> 50% and > low |
< 50% and > low |
< Below low battery |
backup power. |
battery threshold |
battery threshold |
threshold (Settable on |
|
(Settable on the UPS) |
(Settable on the UPS) |
the UPS) |
Automatic |
Automatic bypass. |
Powered (standby, auto In overload |
In fault |
Not powered |
bypass |
bypass, forced bypass, |
Unknown |
||
HE mode, ESS mode) |
||||
Maintenance |
Maintenance bypass |
Powered (maintenance |
Not powered |
bypass |
closed. |
bypass) |
Unknown |
(optional) |
|||
Maintenance bypass opened.
Wiring |
Electrical connection Energy flow |
In overload |
No energy |
between blocks. |
Out of nominal range |
Unknown |
|
2.2.2.2.2 Online diagram examples
Single input source |
Dual input sources |
Contextual Help – 19
Home
Online mode
Bypass mode
Battery mode
HE mode / ESS mode
Maintenance bypass mode
2.2.3 Top bar
Card name – Displays the card name
UPS name – Displays by default the UPS model or the system name if filled in the section Card>>>System information>>>System name
Current user – Displays current user name
Logout – Logs the current user out by destroying the current user session
Status – Provides device (example UPS) status information
Output power – Provides output power status information
Battery status – Provides battery status information
Alarms button – Open alarm page
Settings button – Open settings page
Contextual Help – 20
Home
2.2.4 Details
This view provides a summary of device identification information and nominal values:
•Name
•Model
•P/N
•S/N
•Location
•Firmware version
•Input Voltage
•Input Frequency
•Output Voltage
•Output Frequency
The COPY TO CLIPBOARD button will copy the information to your clipboard so that it can be past.
For example, you can copy and paste information into an email.
2.2.5 Show measures
Provides input and output measures on the synoptic.
2.2.5.1 Example #1
Single input source with 1 phase in and 1 phase out:
Input measures |
Output measures |
Voltage (V) |
Voltage (V) |
Current (A) |
Current (A) |
Frequency (Hz) |
Frequency (Hz) |
2.2.5.2 Example #2
Dual input sources with 3 phases in and 3 phases out
Input measures (main and secondary) |
Output measures |
||||
Phase #1 |
Phase #2 |
Phase #3 |
Phase #1 |
Phase #2 |
Phase #3 |
Voltage (V) |
Voltage (V) |
Voltage (V) |
Voltage (V) |
Voltage (V) |
Voltage (V) |
Current (A) |
Current (A) |
Current (A) |
Current (A) |
Current (A) |
Current (A) |
Load (W) |
|||||
Load (%) |
|||||
Frequency (Hz) |
Frequency (Hz) |
2.2.6 Outlet status
Provides the status of the UPS outlets (ON/OFF) by load segmentation:
•Status (ON/OFF— Protected/Not protected/Not powered)
•Load level (W) – availability depending on the UPS model
•Shutdown countdown
•Startup countdown
Contextual Help – 21
Alarms
Note: Load segmentations allow non-priority equipment to automatically power down during an extended power outage to keep battery runtime on essential equipment.
This feature is also used to remote reboot and sequential start servers to restrict inrush currents.
2.2.7 Active Alarms
Only active alarms are displayed, the Alarms icon will also display the number of active alarms.
Alarms are sorted by date, alert level, time, and description.
Note: To see the alarm history, press the Alarms button.
2.3 Alarms
2.3.1 Alarm sorting
Alarms can be sorted by selecting:
•All
•Active only
2.3.2Alarm details
All alarms are displayed and sorted by date, with alert level, time, description, and status.
Info/Warning/Critical logo |
Alarm description text |
|
Active |
In color |
In bold with «Active» label |
Opened In color
Closed Greyed
2.3.3 Alarm paging
The number of alarms per page can be changed (10-15-25-50-100).
When the number of alarms is above the number of alarms per page, the buttons First, Previous and Next appears to allow navigation in the Alarm list.
Contextual Help – 22
Settings
2.3.4 Alarm export
Press the Export button to download the file.
2.3.5 Clear alarm logs
Press the Clear button to clear alarms that are older than a specified date and up to a defined severity.
2.3.6 Alarm list with codes
For details on alarm codes, see the Information>>>Alarm log codes section.
2.4 Settings
2.4.1 General
2.4.1.1 Location
Text field that is used to provide the card location information.
Card system information is updated to show the defined location.
Contextual Help – 23
Settings
2.4.1.2 Contact
Text field that is used to provide the contact name information.
Card system information is updated to show the contact name.
2.4.1.3 System name
Text field that is used to provide the system name information.
Card system information is updated to show the system name.
2.4.1.4 Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.2 Date & Time
The current date and time appears in the footer at the bottom of the screen.
You can set the time either manually or automatically.
2.4.2.1 |
Manual: Manually entering the date and time |
|
1. |
Select the time zone for your geographic area from the time zone pull-down menu or with the map. |
|
2. |
Select the date and time. |
|
3. |
Save the changes. |
|
2.4.2.2 |
Dynamic (NTP): Synchronizing the date and time with an NTP server |
1.Enter the IP address or host name of the NTP server in the NTP server field.
2.Select the time zone for your geographic area from the time zone pull-down menu or with the map.
3.Save the changes.
Note: DST is managed based on the time zone.
Contextual Help – 24
Settings
2.4.2.3 Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.3 Users
2.4.3.1 Password strength rules
To set the password strength rules, apply the following restrictions:
•Minimum length
•Minimum upper case
•Minimum lower case
•Minimum digit
•Special character
Press Save after modifications.
2.4.3.2 Account expiration
To set the account expiration rules, apply the following restrictions:
•Password expires after (in days).
The main administrator password never expires.
Contextual Help – 25
Settings
1.If this feature is disabled, the administrator account can be locked after the password expiration.
2.If Enabled, the administrator password never expires, make sure it is changed regularly.
•Block account when invalid password is entered after (in number of attempts).
The main administrator account will never block.
1.If this feature is disabled, the administrator account can be locked after the number of failed connections defined.
2.If Enabled, the security level of the administrator account is reduced because unlimited password entry attempts are allowed.
Press Save after modifications.
2.4.3.3 Session expiration
To set the session expiration rules, apply the following restrictions:
•No activity timeout (in minutes).
If there is no activity, session expires after the specified amount of time.
•Session lease time (in minutes).
If there is activity, session still expires after the specified amount of time.
Press Save after modifications.
2.4.3.4 Local users table
Contextual Help – 26
Settings
The table shows all the supported local user accounts and includes the following details:
▪Username
▪Profile
Administrator |
Operator |
Viewer |
Export
Clear
Settings General
Date & Time
Users
Network
Protocols
SNMP
Certificates
My preferences
Meters Power
Battery
Measure logs
Configuration
Controls
Protection
Sensors Status
Alarm configuration
Contextual Help – 27
Settings |
|
Information |
|
Card |
System information |
Resources |
|
System logs |
|
Administration |
Commissioning (Sensors)
Legal information (footer)
Contextual and Full documentation
Command Line get release info Interface
history ldap-test logout maintenance
netconf (read-only)
(read-only) (read-only)
ping and ping6 reboot
save_configuration | restore_configuration
sanitize ssh-keygen time
(read-only) (read-only)
traceroute and traceroute6 whoami
email-test systeminfo_statistics certificates
•Status – Status could take following values – Inactive/Locked/Password expired/Active
Contextual Help – 28
Settings
2.4.3.4.1 Actions
a Add
Press the New button to create up to ten new users.
b Remove
Select a user and press the Delete button to remove it.
c Edit
Press the pen logo to edit user information and access to the following settings:
•Active
•Profile
•Username
•Full name
•Phone
•Organization – Notify by email about account modification/Password
•Reset password
•Generate randomly
•Enter manually
•Force password to be changed on next login
2.4.3.5LDAP
The table shows all the supported severs and includes the following details:
•Name
•Address
•Port
•Security
•Status – Status could take following values – Unreachable/Active
Contextual Help – 29
Settings
2.4.3.5.1 Actions
a Configure
1.Press Configure to access the following LDAP settings:
•Active
•Base access
Contextual Help – 30
Settings
•Security
SSL – None/Start TLS/SSL Verify server certificate
•Primary server – Name/Hostname/Port
•Secondary server – Name/Hostname/Port
•Credentials – Anonymous search bind/Search user DN/Password
•Search base – Search base DN
•Request parameters
•User base DN
•User name attribute
•UID attribute
•Group base DN
•Group name attribute
•GID attribute
2.Click Save.
b Profile mapping
1.Press Profile mapping to map remote groups to local profiles.
2.Click Save.
c Users preferences
All users preferences will apply to all remote users (LDAP, RADIUS).
Contextual Help – 31
Settings
1.Press Users preferences to define preferences that will apply to all LDAP users
•Language
•Temperature
•Date format
•Time format
2.Click Save.
2.4.3.6 RADIUS
Radius is not a secured protocol, for a maximum security, it is recomended to use LDAP over TLS.
The table shows all the supported severs and includes the following details:
•Name
•Address
Contextual Help – 32
Settings
2.4.3.6.1 Actions
a Configure
1.Press Configure to access the following RADIUS settings:
•Active
•Retry number
•Primary server – Name/Secret/Address//UDP port/Time out (s)
•Secondary server – Name/Secret/Address/UDP port/Time out (s)
2.Click Save.
Contextual Help – 33
Settings
b Profile mapping
1.Press Profile mapping to map RADIUS profile to local profiles.
2.Click Save.
c Users preferences
All users preferences will apply to all remote users (LDAP, RADIUS).
1.Press Users preferences to define preferences that will apply to all LDAP users
•Language
•Temperature
•Date format
•Time format
2.Click Save.
Contextual Help – 34
Settings
2.4.3.7 Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.4 Network
2.4.4.1 LAN
A LAN is a computer network that interconnects computers within a limited area.
The available values for LAN configuration are listed below:
•Auto negotiation
•10Mbps — Half duplex
•10Mbps — Full duplex
•100Mbps — Half duplex
•100Mbps — Full duplex
•1.0 Gbps — Full duplex
Any modifications are applied after the next Network Module reboot.
2.4.4.2 IPv4
Any modifications are applied after the Network Module reboots.
Contextual Help – 35
Settings
Press the More button to configure the network settings, select either the Manual or Dynamic settings option:
2.4.4.2.1 Manual
Select Manual, and then enter the network settings if the network is not configured with a BootP or DHCP server.
•Enter the IP Address.
The Network Module must have a unique IP address for use on a TCP/IP network.
•Enter the netmask.
The netmask identifies the class of the sub-network the Network Module is connected to.
•Enter the gateway address.
The gateway address allows connections to devices or hosts attached to different network segments.
Contextual Help – 36
Settings
2.4.4.2.2 Dynamic (DHCP)
Select dynamic DHCP to configure network parameters by a BootP or DHCP server.
If a response is not received from the server, the UPS Network Module boots with the last saved parameters from the most recent power up. After each power up, the UPS Network Module makes five attempts to recover the network parameters.
2.4.4.3 Domain
The DNS is a hierarchical decentralized naming system for computers, services, or other resources connected to the Internet or a private network.
Press the More button to configure the network settings, select either the Static or Dynamic settings.
2.4.4.3.1 Static
•Enter the Network Module Hostname.
•Enter the Network Module Domain name.
Contextual Help – 37
Settings
•Primary DNS server.
Enter the IP address of the DNS server that provides the translation of the domain name to the IP address.
•Secondary DNS server.
Enter the IP address of the secondary DNS server that provides the translation of the domain name to the IP address when the primary DNS server is not available.
2.4.4.3.2 Dynamic
•Enter the Network Module Hostname.
2.4.4.4IPv6
IPV6 status and the first three addresses are displayed.
Press the More button to configure the network settings and get more information, press the More button for access to the following IPV6 details.
Contextual Help – 38
Settings
2.4.4.4.1 Current configuration
•Address
•Gateway
2.4.4.4.2 Address settings
Mode Manual
•Addresses
•Prefix
•Gateway
Mode router
Contextual Help – 39
Settings
2.4.4.4.3 DNS settings
•Get automatically (will hide the following settings)
•Primary DNS
•Secondary DNS
2.4.4.5Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.5 Protocols
This tab contains settings for communication protocols used to get information from the device through the network, such as https for web browser.
2.4.5.1 HTTPS
Only https is available.
The default network port for https is 443. For additional security, the ports can be changed on this page.
Press Save after modifications.
Since only https is available, port 80 is not supported.
2.4.5.2 Syslog
2.4.5.2.1 Settings
This screen allows an administrator to configure up to two syslog servers.
Contextual Help – 40
Settings
To configure the syslog server settings:
a 1- Enable syslog.
Press Save after modifications.
b 2- Configure the syslog server:
1.Click the edit icon to access settings.
2.Enter or change the server name.
3.Select Yes in the Active drop-down list to activate the server.
4.Enter the Hostname and Port.
5.Select the Protocol – UDP/TCP.
6.In TCP, select the message transfer method – Octet counting/Non-transparent framing.
7.Select the option Using Unicode BOM if needed.
8.Press Save after modifications.
2.4.5.3Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.6 SNMP
This tab contains settings for SNMP protocols used for network management systems.
Changes to authentication settings need to be confirmed by entering a valid password for the active user account.
Contextual Help – 41
Settings
2.4.6.1 SNMP tables
The default port for SNMP is 161 and normally this should not be changed. Some organizations prefer to use non-standard ports due to cybersecurity, and this field allows that.
SNMP monitoring Battery status, power status, events, and traps are monitored using third-party SNMP managers.
To query SNMP data, you do not need to add SNMP Managers to the Notified Application page.
To set-up SNMP managers:
•Configure the IP address.
•Select SNMP V1 or V1 and V3.
•Compile the MIB you selected to be monitored by the SNMP manager.
For a list of supported MIBs, see the Information>>>Specifications/Technical characteristics section
.
Press the Supported MIBs button to download the MIBs.
2.4.6.1.1 Settings
This screen allows an administrator to configure SNMP settings for computers that use the MIB to request information from the UPS Network Module.
Default ports for SNMP are 161 (SNMP v1 and v3, set/get) and 162 (traps). These ports can be changed on the settings screen for additional security.
To configure the SNMP settings:
a 1- Enable the SNMP agent.
In addition to this also v1 and/or v3 must be enabled, along with appropriate communities and activated user accounts to allow SNMP communication.
Press Save after modifications.
Contextual Help – 42
Settings
b 2- Configure the SNMP V1 settings:
1.Click the edit icon on either Read-only or Read/Write account to access settings.
2.Enter the SNMP Community Read-Only string. The UPS Network Module and the clients must share the same community name to communicate.
3.Select Yes in the Active drop-down list to activate the account.
4.Access level is set to display information only.
c 3- Configure the SNMP V3 settings:
1. Click the edit iconon either Read Only or Read/Write account to access settings.
Contextual Help – 43
Settings
2.Edit the user name.
3.Select Yes in the Active drop-down list to activate the account.
4.Select access level.
Read only—The user does not use authentication and privacy to access SNMP variables.
Read/Write—The user must use authentication, but not privacy, to access SNMP variables.
5. Select the communication security mechanism.
Auth, Priv—Communication with authentication and privacy.
Auth, No Priv—Communication with authentication and without privacy.
No Auth, No Priv—Communication without authentication and privacy.
6. If Auth is selected on the communication security mechanism, select the Authentication algorithms.
It is recommended to set SHA256/SHA384/SHA512 with the AES192/AES256 Privacy algorithms.
SHA— SHA1 is not recommended as it is not secured.
SHA256—fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
SHA384—fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
SHA512—fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
AES / AES192 / AES256
7. If Priv is selected on the communication security mechanism, select the Privacy algorithms.
It is recommended to set AES192/AES256 with the SHA256/SHA384/SHA512 Authentication algorithms.
AES— fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
AES192—fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
AES256—fill in password and privacy keys. The password can be between 8 and 24 characters and use a combination of alphanumeric and the following special characters <>&@#%_=:;,./?|$*.
8. Enter your own login password and click Save.
2.4.6.2 Trap receivers
The table shows all the trap receivers and includes the following details:
•Application name
•Host
Contextual Help – 44
Settings
•Protocol
•Port
•Status: Active/Inactive/Error(configuration error)
2.4.6.3Actions
2.4.6.3.1 Add
1.Press the New button to create new trap receivers.
2.Set following settings:
•Active – Yes/No
•Application name
•Hostname or IP address
•Port
•Protocol – V1/V3
•Trap community (V1) / User (V3)
3.Press the SAVE button.
2.4.6.3.2 Remove
Select a trap receiver and press the Delete button to remove it.
2.4.6.3.3 Edit
Press the pen icon to edit trap receiver information and access to its settings.
2.4.6.3.4 Test all traps
Press the Test all traps button to send the trap test to all trap receivers.
Separate window provides the test status with following values:
•In progress
Contextual Help – 45
Settings
•Request successfully sent
•invalid type
For details on SNMP trap codes, see the Information>>>SNMP traps section.
2.4.6.4 Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.7 Certificates
2.4.7.1 Local certificates
Manage local certificates by :
•Generating CSR and import certificates signed by the CA.
•Generating new self-signed certificates.
2.4.7.1.1 Local certificates table
The table shows the following information for each local certificate.
•Used for
•Issued by
•Valid from
•Expiration
•Status — valid, expires soon, or expired
2.4.7.1.2 Actions
a Revoke
This action will take the selected certificate out of use.
Select the certificate to revoke, and then press the Revoke button.
A confirmation window appears, press Continue to proceed, this operation cannot be recovered.
Contextual Help – 46
Settings
Revoke will replace current certificate by a new self-signed certificate.
This may disconnect connected applications:
—Web browsers
—Shutdown application
—Monitoring application
The certificate that is taken out of use with the revoke action cannot be recovered.
b Export
Exports the selected certificate on your OS browser window.
c Configure issuer
Press the Configure issuer button.
A configuration window appears to edit issuer data.
•Country
•State or Province
•City or Locality
•Organization name
•Organization unit
•Contact email address
Press Save button.
Issuer configuration will be applied only after the revoke of the certificate.
d Edit
Allows access to the following:
•Certificate summary
•Actions
Generate a new self-signed certificate.
Contextual Help – 47
Settings
Generate CSR.
Import certificate (only available when CSR is generated).
•Details
2.4.7.1.3 Generate a new self-signed certificate
To replace a selected certificate with a new self-signed certificate.
This may disconnect applications such as a Web browser, shutdown application, or monitoring application. This operation cannot be recovered.
2.4.7.1.4 Create new certificates:
a CSR
Press Generate Signing Request button in the in the certificate edition.
The CSR is automatically downloaded.
CSR must be signed with the CA, which is managed outside the card.
b Import certificate
When the CSR is signed by the CA, it can be imported into the Network Module.
When the import is complete, the new local certificate information is displayed in the table.
2.4.7.2 Certificate authorities (CA)
Manages CAs.
2.4.7.2.1 CA table
The table displays certificate authorities with the following details:
•Used for
•Issued by
•Issued to
Contextual Help – 48
Settings
•Valid from
•Expiration
•Status — valid, expires soon, or expired
2.4.7.2.2 Actions
a Import
When importing the CA, you must select the associated service, and then upload process can begin through the OS browser window.
b Revoke
Select the certificate to revoke, and then press the Revoke button.
A confirmation window appears, press Continue to proceed, this operation cannot be recovered.
Export
Exports the selected certificate on your OS browser window.
c Edit
Gives access to a summary of the certificate.
2.4.7.3 Pairing with clients
For details on pairing instructions, follow the link pairing instructions in the tile or see the Servicing the Network Management Module>>>Pairing agent to the Network Module section.
During the selected timeframe, new connections to the Network Module are automatically trusted and accepted.
After automatic acceptance, make sure that all listed clients belong to your infrastructure. If not, access may be revoked using the Delete button.
The use of this automatic acceptance should be restricted to a secured and trusted network.
For maximum security, we recommend following one of the two methods on the certificate settings page:
•Import agent’s certificates manually.
•Generate trusted certificate for both agents and Network Module using your own PKI.
2.4.7.3.1 Actions
a Start
Starts the pairing window during the selected timeframe or until it is stopped.
Time countdown is displayed.
Contextual Help – 49
Settings
b Stop
Stops the pairing window.
2.4.7.4 Trusted remote certificates
The table shows the following information for each trusted remote certificate.
•Used for
•Issued by
•Issued to
•Valid from
•Expiration
In case a certificate expires, the connection with the client will be lost. If this happens, the user will have to recreate the connection and associated certificates.
•Status — valid, expires soon, or expired
2.4.7.4.1 Actions
a Import
When importing the client certificate, you must select the associated service, and then upload process can begin through the OS browser window.
b Revoke
Select the certificate to revoke, and then press the Revoke button.
A confirmation window appears, press Continue to proceed, this operation cannot be recovered.
c Edit
Gives access to a summary of the certificate.
2.4.7.5 Default settings parameters and limitations
For details on default parameters and limitations, see the Information>>>Default settings parameters section.
2.4.8 Email
2.4.8.1 Email sending configuration
For examples on email sending configuration see the Servicing the Network Management Module>>>Subscribing to a set of alarms for email notification section.
Contextual Help – 50
Loading…