CeraWeb Course Handbook - v4.4

®
FibeAirIPͲ10GͲSeries
Setting Management
Proprietary and Confidential
Agenda
• Getting started
• General notes
• General commands
• Command history y
• Reading current IP
• Setting new IP
• Connecting PC to IDU
• Troubleshooting
• Factory Defaults
2
Advanced Operation & Maintenance Course

Page 110
Getting started
Verify that physical installation is successfully completed:
• IDU is properly mounted in a shelf / rack

• Power + GND
• IF Cable between IDU and ODU
Connect a PC to the Terminal connector and launch a serial application
• Baud: 115200
• Data bits: 8 YoumayuseanySerial
• Parity: None ApplicationsuchasHyper
• Stop
St bits:
bit 1 Terminal PuTTY TeraTerm
Terminal,PuTTY,TeraTerm
etc…
• Flow Control: None
Log on using (admin/admin) for user name and password.

Now, you should be able to see the IP-10 CLI Prompt
3
General notes on CLI
+2
Note that the chevron > sign indicates your current directory in the CLI tree
Most of the CLI commands are based on GET/SET concept

Some commands may require a different syntax
Ceragon strongly recommends to use CLI only for setting management IP

address when current IP is unknown
All functions & features can be configured faster and easier using the WEB
based EMS
4

Page 111
General Commands
+2 !
+2NU
+2NUR
+2 GZKV
+2 EF
+2 EF
Type ? (question mark) to list helpful commands

Type ls to list your current directory
Type lsp to available commands of current directory
Type exit to terminate the session
Type cd to change directory

Type cd .. to return to root directory
5
Command History
Use the arrow keys to navigate through recent

commands
Use the TAB key to auto-complete a syntax
6

Page 112
Reading current IP
To read current IP type the following:
+2 EF OCPCIGOGPVPGVYQTMKPIKRCFFTGUU
+2OCPCIGOGPVPGVYQTMKPIKRCFFTGUU
Note that the prompt has changed. Now, type get ip-address:
+2OCPCIGOGPVPGVYQTMKPIKRCFFTGUU IGVKRCFFTGUU
completion the current IP will be displayed

Upon completion, displayed, followed by the new
prompt:
+2OCPCIGOGPVPGVYQTMKPIKRCFFTGUU IGVKRCFFTGUU

+2OCPCIGOGPVPGVYQTMKPIKRCFFTGUU
7
Setting new IP
Now, let us set a new IP for the MNG:
We assume the required IP is 192.168.1.144
Type set ip-address 192.168.1.144
+2OCPCIGOGPVPGVYQTMKPIKRCFFTGUU UGVKRCFFTGUU
Upon completion, you will be prompt:
;QW OC[ NQUG TGOQVG OCPCIGOGPV EQPPGEVKQP VQ VJG WPKV KH VJKU XCNWG
;QWOC[NQUGTGOQVGOCPCIGOGPVEQPPGEVKQPVQVJGWPKVKHVJKUXCNWG
KUEJCPIGFKPEQTTGEVN[
#TG[QWUWTG! [GUPQ
Type yes and connect the IDU to your network / PC
8

Page 113
Connecting IDU to EMS
1. Connect your EMS/NMS to the IDU (port 7) with ETH CAT.5 cable
2. Verify that your PC’s IP is in the same subnet
3 Make sure Link is up

3.
4. PING the IDU
5. Launch a WEB browser with the URL set as the IDU’s IP
9
Management Troubleshooting
In case PC cannot PING IDU –
1. Check your ETH cable – it might not be inserted properly (broken PIN)
2. Verify the management port is enabled in the EMS General/Management
configuration
3. Make sure you connect to a management-enabled port (7, 6 or 5)
4. Verify right LED is ON (see below)
5. Verify your PC is in the same subnet as the IDU
6. In case your IDU is connected to a router: set the IDU’s Default GW = Router IP
7. In case your PC is connected to several IDUs (through switch/hub) – make sure
every IDU has a unique IP
When ON (Green) = Port is set to Management
When OFF = Port is set to Data
10

Page 114
Back to factory defaults
Going back to factory defaults can be done with EMS or CLI

In case you need to set factory defaults with CLI type the following -
+2 EF OCPCIGOGPVOPIUGTXKEGUEHIUGTXKEG
In the new directory type the following:
+2OCPCIGOGPVOPIUGTXKEGUEHIUGTXKEG UGVVQFGHCWNV
11
ThankYou!
training@ceragon.com

Page 115
10/5/2010
FibeAir ® IP-10 G-Series

EMS Performance Monitoring
Agenda
EMS – General Information
Faults:
• Current Alarms
• Event Log
PM & Counters:
• Remote Monitoring
• TDM Trails
• TDM interfaces
• Radio (RSL, TSL, MRMC and MSE)
• Radio TDM
• Radio ETH
• XPI
2 Proprietary and Confidential
Page 116 1
10/5/2010
EMS - General
9 Easy, user friendly GUI
9 No need to install an application – WEB Based software
9 No need to upgrade your EMS application – embedded in the IDU SW
9 No need for strong working station – simple PC is sufficient
(For maintenance issues FTP Server is required)
9 Easy access – simply type the IP address of the IDU on your web page
9 Supports all IDU versions and configurations
3 Proprietary and Confidential
EMS Main View
Access application via IP address
User friendly navigation menu
Page 117 2
10/5/2010
EMS Main View
Graphical “MENU”: Click to configure
EMS Main View
Protection Status Display &

Quick Access Icons
Page 118 3
10/5/2010
EMS Main View

In this example slot #1 and slot #2 are configured to support 1+1 Protection
Slot #1 is selected and in Active mode.
Black Rectangular to indicate

selected slot for configuration
EMS Main View
When the user selects Slot 2 the GUI updates automatically
8
Page 119 4
10/5/2010
Faults - CAS
The CAS window shows collapsed list of alarms
By expanding a line we can see additional information:
• Probable cause
• Corrective Actions
9
Faults – Event Log

The Event Log shows max. 200 lines of events
When Event #201 occurs, Event #1 is erased and #201
is logged as #200.
Page 120 5
10/5/2010
Available PM Statistics - Radio
TDM PM
(allocated E1/T1 VCs)
TDM
(E1/T1)
ETH PM (Data + In-Band):

1. Aggregated Errors STMͲ1
2. Throughput STM-1 PM
3. Capacity
4. Radio Link Utilization When STM-1 T-Card
5. RMON standard is is inserted in front
implemented
p as well to panel)
p )
provide detailed data
Radio Signal PM:
ETH BW is a function of 1. RSL
available radio capacity as TDM 2. MSE
and STM-1 have higher priority 3. MRMC (ACM)
4. Aggregate
11
Available PM Statistics – Line Interfaces
• STM-1 interface facing customer equipment

• TDM interfaces facing
g customer equipment
q p
• End-to-End Trails
12
Page 121 6
10/5/2010
Clearing previous data

To erase all IDU PM data, click the CLEAR button -
13
ETH PM – RMON
The system supports Ethernet statistics counters (RMON) display (depends on
port availability). The counters are designed to support:
• RFC 2819 – RMON MIB.

• RFC 2665 – Ethernet-like MIB.
• RFC 2233 – MIB II.
• RFC 1493 – Bridge MIB.
14
Page 122 7
10/5/2010
ETH PM – RMON
15
PM – RMON – Special Registers

RMONregister /Counter Description
Undersizeframesreceived Framesshorterthan64bytes
Oversize frames received

Oversizeframesreceived Frames longer than 1632 bytes
Frameslongerthan1632bytes
Totalframesreceivedwithalengthofmorethan1632bytes,
Jabberframesreceived
butwithaninvalidFCS
Totalframesreceivedwithalengthoflessthan64
Fragmentsframesreceived
bytes,andaninvalidFCS
Rxerrorframesreceived TotalframesreceivedwithPhyͲerror
TotalframesreceivedwithCRCerror,notcounteredin
FCSframesreceived
Fragments ,"Jabber"
"Fragments", Jabber or
or "Rx error"counters
Rxerror counters
Countsgoodframesthatcannotbeforwardeddueto
InDiscardFrames
lackofbuffermemory
Countsgoodframesthatwerefilteredduetoegress
InFilteredFrames
switchVLANpolicyrules
Pauseframesreceived NumberofflowͲcontrolpauseframesreceived
16
Page 123 8
10/5/2010
Troubleshooting with RMON: Filtering Example

Radio port is a Radio port is a
Site A member of VID 100 member of VID 100 Site B
A Tagging T No membership
T A
Untagged Frames Access port with

Tagged with default default VID = 300
VID 100
Site B Ingress port (Radio) receives the frame and checks the Egress port VID
membership
Egress port default VID is 300, therefore frame is filtered by the remote Radio port
17
Troubleshooting with RMON: Oversized frames
Site A Site B
T T T A
Tagged Frames with

frame size > 1632 bytes
When ingress frames exceed the maximum frame size, RMON counter “Oversized frames
received” is updated accordingly
18
Page 124 9
10/5/2010
Troubleshooting with RMON: Discarding Example
Site A Site B
T T T A
Ingress traffic does not

comply to Policer rules
Discarding Examples:
Ingress rate > Rate Limiter

Ingress frames do not qualify to Policer rules
19
Troubleshooting with RMON: Monitoring specific

traffic types
Site A Site B
Rate Limiter
T T
Monitor
Video streams are generally transmitted over UDP

with multicast addresses
To monitor traffic, check out the Multicast Frames

Received register
To limit MC traffic, assign a Policer with a UDP & MC

CIR rules
20
Page 125 10
10/5/2010
PM – TDM Trails
Trails can only be configured in the Main

IDU/Slot #1
Extension Trails (trails via extension IDU)

are also configured in the Main IDU
TDM Trail PM can only be viewed in the

Main IDU menu
The number of trails that can be

configured is a function of available radio
BW (license + script)
21
PM – TDM Trails
22
Page 126 11
10/5/2010
PM – TDM Trails – In Detail
Errored Second (ES):
A one-second period with one or more errored blocks or at least one defect
23
Severely Errored Second (SES):
A one-second period, which contains t30% errored blocks or at least one

defect.
defect
SES is a subset of ES.
24
Page 127 12
10/5/2010
A period of unavailable time begins at the onset of 10 consecutive Severely

Errored Second (SES) events. These 10 seconds are considered to be part of
unavailable time.
A new period of available time begins at the onset of 10 consecutive non-SES

events. These 10 seconds are considered to be part of available time.
25
Background Block Error (BBE):
An errored block not occurring as part of a SES.
26
Page 128 13
10/5/2010
Number of Switches (only relevant for Protected SNCP Trails):
The number of times the IP-10 switched from Primary Path to Secondary Path
and vice versa (per 15min or 24hrs interval)
Active Path Seconds (only relevant for Protected SNCP Trails):
The number of times seconds the Active Path was available
Page 129 14
10/5/2010
Integrity:
Indicates whether information is reliable for analysis (ticked) or not
For example – if clock was changed or system was restarted during this interval
then information is not reliable
29
PM – TDM Trails through Radio
30
Page 130 15
10/5/2010
PM – E1 / DS-1 (PM received from customer)
This PM data
relates to the
TDM Line
Interfaces.
Interfaces
31
PM – STM-1 (Slot #2)
32
Page 131 16
10/5/2010
PM – Radio - RF
Signal Level – RSL & TSL analysis
Allows setting RSL & TSL thresholds

EMS will notify when signal exceeds THSLD
>> Easier maintenance
Aggregated radio traffic analysis
MRMC – PM related to ACM:
• Associated Script
• Available Bit rate
• Available Radio VCs
MSE analysis (quality of received signal)

XPI analysis (when XPIC enabled)
33
PM – Radio – Signal Level – Using Threshold
- 40dBm = Nominal RSL for an operational Link

Level 1: 25 sec
Level 2: 15 sec
900 sec = 15min Interval
34
Page 132 17
10/5/2010
PM – Radio – Signal Level - Using Threshold
Using graphical display of the THSLD analysis allows us easier

examination of the RSL & TSL state throughout certain period of time
RSL
-40
-50
-68
-99 T [sec]
10 5 10
35
PM – Radio - Aggregate
Aggregated radio
traffic analysis
36
Page 133 18
10/5/2010
PM – Radio - MRMC
The information displayed in this page is derived from the license and script
assigned to the radio.
When ACM is enabled and active,

active as link quality degrades or improves
improves, the
information is updated accordingly.
37
PM – Radio - MRMC
38
Page 134 19
10/5/2010
PM – Radio - MSE
The information
displayed in this page
is derived from the
license and script
assigned to the radio.
When link quality
degrades or
improves, the MSE
reading is updated
accordingly.
Differences of 3dB
gg ACM
trigger
modulation changing.
Threshold can be
configured as well for
easier maintenance.
39
PM – Radio - XPI
Use this report to evaluate the cross-polarization

interference
Apply a threshold to establish a better notification

40
Page 135 20
10/5/2010
PM – Radio - Ethernet
Frame Error Rate – (%) measured on radio-Ethernet
interface (port 8)
Ethernet Capacity (a.k.a. Ethernet L1 capacity) - Total

bit rate from an Ethernet user port. Taking into account
the full Ethernet frame including the IFG and preamble
fields. Ethernet capacity is sometimes referred to as
"port utilization rate".
Radio Throughput - Total bit rate supported by the

radio link running in a specific channel/modulation
including radio frame overhead, etc.
Utilization (%) is displayed as one of five bins:

0 20% 20-40%,
0-20%, 20 40% 40-60%,
40 60% 60-80%,
60 80% 80-100%
80 100%
Ethernet throughput & Capacity PMs are measured by

accumulating the number of Ethernet octets every
second
Accurate analysis requires accumulating a full interval

(15min/24hrs)
41
PM – Ethernet – Frame Error Rate
42
Page 136 21
10/5/2010
PM – Ethernet – Throughput
43
PM – Ethernet – Capacity
44
Page 137 22
10/5/2010
PM – Ethernet – Utilization
45
Throughput / Capacity / Utilization

To better understand these terms, we shall examine the Ethernet tagged frame full
structure:
A frame viewed on the actual physical wire would show Preamble and Start Frame
Delimiter,, in addition to the other data (required
( q by
y the p
physical
y hardware).
)
However, these bits are stripped away at OSI Layer 1 by the Ethernet adapter before
being passed on to the OSI Layer 2 which is where data is detected.
Pre. SFD DA SA VLAN ETH Type Payload+ CRC Interframe

/Length Padding Gap
7octets 1octet 6octets 6octets 4octets 2octets 46Ͳ1500 4octets 12octets

octets
DataRate:min.64 octets– max.1522octets
Physicalwirerate:min.84octets– max.1542octets
46
Page 138 23
10/5/2010
Pre. SFD DA SA VLAN ETH Type Payload+ CRC Interframe

/Length Padding Gap
7octets 1octet 6octets 6octets 4octets 2octets 46Ͳ1500 4octets 12octets

octets
DataRate:min.64 octets– max.1522octets
Physicalwirerate:min.84octets– max.1542octets
In case we use a 64 bytes frame:
Throughput (Data rate) = ~ 77% of physical transmitted rate (64/84=0.77)

Stripped bits = ~ 23% of physical transmitted rate (20/84=0.23)
Hence, when we transmit 100Mbps, the actual throughput would be 77 Mbps

47
Throughput = 77 Mbps
Radio Capacity =
(license) = 400Mbps
Transmitted rate = Capacity = Received frame rate

100 Mbps = 100 Mbps
Utilization = Throughput = 77 = 20 %
Radio Capacity 400
48
Page 139 24
10/5/2010
ThankYou!
training@ceragon com
Page 140 25
12/7/2010
FibeAir ® IP-10 G-Series

EMS General Configuration
Agenda
In this module we shall explain the following

features as they appear on the EMS
navigation Menu
Page 141 1
12/7/2010
Menus
Menu of a Main unit
Menu of an Extension
Unit Parameters – Step # 1
Configure specific
information that may
assist you later
Such info will help you

locate your site easier
and faster
Page 142 2
12/7/2010
VDC reading
Celsius (metric) or
Fahrenheit (Imperial)
Page 143 3
12/7/2010
By default the time &

date are derived from
the operating system
clock
User may set new

values
These settings are also

used for NTP
connection (later
explained)
IDU Serial number is

important when you
submit your request
for a License upgrade
When you complete

configuring all
settings, click Apply.
Page 144 4
12/7/2010
External Alarms – Collapsed Input Alarm Config.
Dry Contact Alarms (DB-9):
5 Inputs
1 Output
External Alarms – Expended Input Alarm Config.
Page 145 5
12/7/2010
External Alarms – Configuring the Output Alarm

‘Group’ of alarms will trigger the external alarm Output.
Communication – Alarms related to traffic: Radio / Ethernet line / TDM line
Q lit off Service

Quality S i – WeW do
d nott h
have specific
ifi alarms
l off QoS
Q S
Processing – Alarms related to SW: Configuration / Resets / corrupted files
Equipment – Alarms related to: HW / FAN / RFU mute / Power Supply / Inventory.
Environmental – Alarms of ‘extreme temperature’.
All Groups.
Test mode – manual switch.
Management – Menu of Extension Slots
This is the switch MAC address
Here you can set/review the IP

address of the remote site
You can also access the EMS of the

remote site (assuming both IDUs are
configured identically in terms of
MNG…)
Page 146 6
12/7/2010
Management – Main IDU: Setting IP Address

Here you can set the IP address of
the IDU
Let us examine the following

examples to understand how and
when we use each one of these
parameters…
Node / standalone, no protection:

Connect your PC to any one of the MNG ports (7,6,5)
IP: 192.168.1.10
SM: 255.255.255.0 ETH Cross Cable IP: 192.168.1.100
D.GW: 0.0.0.0 SM: 255.255.255.0
Page 147 7
12/7/2010

Node, Standalone, no protection, going through a Router:
Set the Default GW address
10.10.2.10
DCN
IP: 192.168.1.10
SM: 255.255.255.0
255 255 255 0
D.GW: 192.168.1.12
192.168.1.12
IP: 10.10.2.100
SM: 255.255.255.0

Node/Standalone, 1+1 Protection:
Set a Floating IP
The floating
g IP address pprovides a
single IP address that will always give
direct access to the current active
main unit.
IP Slot #1: 192.168.1.10 ETH Y-Cable

IP Slot #2: 192.168.1.11 IP: 192.168.1.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 0.0.0.0
Floating IP: 192.168.1.22
See “1+1 Protection PPS” for further info
Page 148 8
12/7/2010

Node/Standalone, 1+1 Protection, going through a Router:
Set a Floating IP + D. GW
192.168.1.100
IP Slot #1: 192.168.1.10 ETH Y-Cable

IP Slot #2: 192.168.1.11 IP: 10.10.2.100
SM: 255.255.255.0 SM: 255.255.255.0
D.GW: 192.168.1.100
Floating IP: 192.168.1.22
See “1+1 Protection PPS” for further info
Management – Main IDU: Setting No. of MNG Ports
This is the switch MAC address
If your link is up – you should be

able to see the other end’s IP
The IDU has 3 ports for local management:

Port 7,, Port 6 and Port 5.
You may enable none or up to 3 ports:
Number of ports =3 Port 7, Port 6, Port 5

Number of ports =2 Port 7, Port 6
Number of ports =1 Port 7
Number of ports =0 NO LOCAL MANAGEMENT !!!
Page 149 9
12/7/2010
Management – Main IDU: In Band Properties
In Band Management
g
requires unique VLAN ID
This helps separating
MNG traffic from other
services
In Band MNG packets are
transferred via the radio
link
When the link is down,
management is down as
well.
Management – Main IDU: Port Properties
These parameters allow

you setting the
management capacity and
ports’ physical properties
Page 150 10
12/7/2010
Trap Configuration (OSS / NMS / Northbound)
To manage the IDU with OSS / NMS, you will need to configure the IP address
of the OSS Server
You may configure up to 4 Servers (Trap Destinations)
See next slide for more info….
Trap Configuration – T. Destination Configuration
Page 151 11
12/7/2010
Licensing – Copy, Paste, Ready to start…
Licenses are generated per IDU S/N (capacity / ACM / switch mode)
License upgrade requires system reset.
NTP Client Properties

• Enable / Disable
• Type NTP Server IP address
• Expect IDU to lock on NTP Server’s clock
• Expected Status:
1. If locked, it returns the IP address of the server it is locked on.
2. “Local” – if the NTP client is locked to the local element’s real-time clock
3. “NA” - if not synchronized with any clock (valid only when Admin is set to
Disable).
The feature supports “Time Offset” and “Daylight Saving Time”.

“Time Offset” and “Daylight Saving Time” can be configured via WEB (“Unit Information”
page) or via CLI: /management/mng-services/time-service>
Page 152 12
12/7/2010
NTP Properties
NTP Properties
When using NTP with external protection 1+1, both “Active” and “Standby”
units
nits sho
should
ld be locked independentl
independently on the “NTP ser
server”,
er” and report
independently their “Sync” status.
Time & Date are not copied from the “Active” unit to the “Standby” unit
When using NTP in a shelf configuration

configuration, all units in the shelf (including
standby main units) are automatically synchronized to the active main unit’s
clock.
Page 153 13
12/7/2010
IP Table
Here you can manually set your neighbor’s network properties
SNMP
• V1
• V2c
• V3
• No security
• Authentication
• Authentication privacy
• SHA
• MD5
• No Authentication
Page 154 14
12/7/2010
All ODU
This feature is used to feed the integrated fans of the All Outdoor Enclosure
(standalone outdoor rack)
When Enabled, the All ODU enclosure interface is activated, and the enclosure
controller can then be powered to monitor fan failure alarms.
The External Alarm Input #1 becomes an output, which together with 3.3V is
used to drive the enclosure’s electronic board.
External Alarm Input #2 is set with a specific text & severity, and is used to
monitor any enclosure fan failure, and to raise an alarm for it (polarity change
was required to adapt it to the enclosure behavior).
All ODU Disabled All ODU Enabled

All ODU - External Alarms Status
All ODU = Disabled
All ODU = Enabled
Page 155 15
12/7/2010
Versions - IDU
Versions - ODU
Page 156 16
12/7/2010
Versions – Running / Installed / Upgrade / Downgrade
Let’s explore this example:
• The IDU running SW is displayed in the aidu line and currently it is 3.0.92
3 0 92
• A new SW was downloaded sometime in the past (3.0.97)
• The IDU was not upgraded yet
ThankYou!

Page 157 17

CeraWeb Course Handbook - v4.4

Uploaded by

Document Information

Original Title

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

CeraWeb Course Handbook - v4.4

Uploaded by

Copyright:

Available Formats

®

Proprietary and Confidential

Advanced Operation & Maintenance Course

Verify that physical installation is successfully completed:

• IDU is properly mounted in a shelf / rack

Connect a PC to the Terminal connector and launch a serial application

Log on using (admin/admin) for user name and password.

General notes on CLI

Most of the CLI commands are based on GET/SET concept

Ceragon strongly recommends to use CLI only for setting management IP

Advanced Operation & Maintenance Course

Type ? (question mark) to list helpful commands

Type exit to terminate the session

Type cd to change directory

Use the arrow keys to navigate through recent

Use the TAB key to auto-complete a syntax

Advanced Operation & Maintenance Course

completion the current IP will be displayed

We assume the required IP is 192.168.1.144

Type set ip-address 192.168.1.144

Upon completion, you will be prompt:

Type yes and connect the IDU to your network / PC

Advanced Operation & Maintenance Course

2. Verify that your PC’s IP is in the same subnet

3 Make sure Link is up

4. PING the IDU

5. Launch a WEB browser with the URL set as the IDU’s IP

Advanced Operation & Maintenance Course

Going back to factory defaults can be done with EMS or CLI

+2 EF OCPCIGOGPVOPIUGTXKEGUEHIUGTXKEG

In the new directory type the following:

Proprietary and Confidential

Advanced Operation & Maintenance Course

FibeAir ® IP-10 G-Series

Proprietary and Confidential

EMS – General Information

2 Proprietary and Confidential

9 Easy, user friendly GUI

9 No need to install an application – WEB Based software

9 No need to upgrade your EMS application – embedded in the IDU SW

9 No need for strong working station – simple PC is sufficient

(For maintenance issues FTP Server is required)

9 Supports all IDU versions and configurations

3 Proprietary and Confidential

EMS Main View

Access application via IP address

User friendly navigation menu

Proprietary and Confidential

EMS Main View

Graphical “MENU”: Click to configure

Proprietary and Confidential

EMS Main View

Protection Status Display &

Proprietary and Confidential

EMS Main View

Black Rectangular to indicate

Proprietary and Confidential

EMS Main View

When the user selects Slot 2 the GUI updates automatically

The CAS window shows collapsed list of alarms

By expanding a line we can see additional information:

Faults – Event Log

Proprietary and Confidential

+2 EF OCPCIGOGPVOPIUGTXKEGUEHIUGTXKEG