Data Communication Network (DCN)

INC 100MS specifications and constraints

NMS Specifications and Constraints

NMS Server (for INC 100MS) and NMS Client specifications and constraints
 INC 100MS specifications and constraints
NMS Specifications and Constraints
 INC 100MS specifications and constraints
NMS Specifications and Constraints
 OSI & TCP/IP
GNE (Gateway Network Element)

What is GNE (Gateway Network Element)?

The first SDH NE that is connected to network entrance from INC-100 via LAN or WAN
is called GNE.

When designing management network, its recommended to have at least 2 GNEs per
network. This is because the network will still be under management even when 1 GNE
fails.

NE
WAN
R R
INC-100 NE
LAN GNE

LAN NE NE NE
GNE
NE

Network
 OSI & TCP/IP
DCC Port
Physical Connection Speed
LAN 10Mbps
DCCr 192kbps
DCCm 576kbps

DCCr, DCCm

OSI & TCP/IP

 OSI & TCP/IP
DCC Port SPECIFICATION OF INDIVIDUAL NE
NE Name NMS No. of DCC ports Shape of LAN Package Name TARP
port Support
INC-100MS INC-100B DCCm DCCr SC Unit DCC AGENT Unit
Unit
SMS-150C 0 - 0 2 RJ45 The name specification is not available NO
SMS-150V 0 0 0 4 AUI SC SC AGENT NO
SMS-600V 0 0 0 8 AUI SC SC AGENT NO

SMS-2500C 0 - 0 8 AUI SC SC SGENT NO

SMS-2500A 0 0 0 4 BNC ACMHS ACMHS MCIA NO

8x4 BNC DCP

SMS-2500R2 0 0 0 4 RJ45 ACMHS ACMHS MCIA NO

WDM16/32(TERM) 0 - 0 1 RJ45 MNG AUX AGENT YES

WDM16/32(ILOADM) 0 - 0 2 RJ45 MNG AUX AGENT YES

WDM80(TERM) 0 - 1 0 RJ45 SCxx DCP AGENT YES

WDM80(ILOADM) 0 - 2 0 RJ45 SCxx DCP AGENT YES

U-NODE ADM 0 - 4 8 RJ45 MSC OHC MSC YES

4 4 COM

4x3 8x3 OHEXT

U-NODE REG 0 - 0 4 RJ45 MSC OHC MSC YES

SMS-2500A has a maximum of 36 ports but can use up to 12 for simultaneous connections
U-Node (ADM) has a maximum of 56 ports but can use up to 20 for simultaneous connections
 OSI
Network Size

There are 2 types of SDH NE within OSI network, V1 (Version 1) and V2 (Version 2).
-SMS-150A/ 150R/ 150T/ 150L/ 600W/ 600W2/ 600T/ 600R/ 2500T/ 2500R are known as V1
-SMS-150V/ 600V/ 2500A/ 2500R2 are known as V2.
In addition, this document treats with the network design involving WDM NE (Spectral Wave) as well as U-Node.

Maximum number of NEs (including router) which can be placed in one area:
- 60 NEs for V1/V2 equipments (limitation by agent function);
- 150 NEs for U-Node/DWDM equipments.

Maximum number of routing HOPs in one area:

- 51 HOPs for V1/V2 equipments;
- 50 HOPs for U-Node/DWDM equipments.

The farthest NE from INC-100MS:

- Less than 20 HOPs for V1/V2 equipments;
- 25 HOPs for U-Node/DWDM equipments.

Maximum number of OSI node (NE, Router etc), which can be located on the same LAN is
- 12 for V2 equipments and
- 6 for DWDM and U-Node.
 OSI
HOP number
What is HOP number?

HOP number is the number of nodes that passes through when transmitting data from
INC-100 to NE. In other words, HOP number is equal to number of NEs and Routers
that passed through during transmission.

HOP No.=0
HOP No. HOP No. HOP No.3
INC-100B NE NE NE
LAN
HOP No.3
Leased LineWAN
Router Router NE
HOP No.=1 HOP No.=2

NE NE
HOP No.4 HOP No.5
 OSI
LAN CAPACITY
The maximum number of OSI node (NE, Router etc) which can be located on the
same LAN needs to be considered. Considering performance of Agent/MCIA unit
of SDH NE, we must keep the number of OSI node (NE, Router etc) on the same
LAN less than the specified. Increasing of OSI nodes on the LAN causes over
crowding of protocol level packet, and unexpected trouble would be generated.
 OSI
LAN CAPACITY

Following is a list of the notices for designing of the managed network for WDM and U-
Node NEs, especially different point from SDH NEs case.

Maximum number of NE which you can locate on the same LAN connection:
- Maximum of 6 including Router and other vendors equipment.
This limitation is due to TARP packets characteristic.

(Note) In the case of SDH NE, maximum number of NE that you can locate on the same
LAN is 12.
SDH V2 U-NODE Mixed
WDM NE

Does NOT 12 - 12
support TARP

Support TARP Shared Hub N/A(*) 6 6

SWHUB N/A(*) 19 12

(*) SDH V2 does not support TARP

 OSI
ES & IS
NE settings
- NE can be set as either ES or IS. ES is used when NE is placed at end of the network, whereas IS is
used when its placed in between networks.
- There are 2 IS settings, one is Level1 IS and the other is Level2 IS. L1 IS setting controls routing within
an area, whereas L2 IS setting controls routing in between areas.
- At ES setting, LAN port is the only port being used even when DCCr port is plugged in.
- Use Router rather than Bridge for distant LAN connection.
What are ES and IS settings?
There are ES (End System) and IS (Intermediate System) settings for each NE within OSI network.
The ES is used when NE is placed at end of the network, and the IS is used when its placed in between
networks. This means that NE set as ES will only receive and wont give out any routing information,
whereas the IS setting will do both. From this, its quite clear the amount of work on each NE differs
greatly depending on the setting.

Intermediate

NE
ES) NE
LAN ES)

NE End
NE IS)
ES)
End NE
ES)

NE
ES)
 OSI
ES

When NE is set as ES, LAN port is the only port being used, even when DCCr or
DCCm port is plugged in. This means that its possible to reduce the data flow through
LAN by just controlling ES/ IS setting.

LAN

ES Setting Information transaction.
DCCr

This line is ignored.

Traffic through network is therefore much less by having lots of ES settings.

 OSI
Level1 IS and Level2 IS
What are Level1 IS and Level2 IS?
There are Level 1 IS-IS (Intermediate System-Intermediate System) and Level 2 IS-IS for IS settings.
The Level 1 IS-IS controls routing within an area, whereas Level 2 IS-IS controls routing in between areas.
The Figure is an example of Level 1 IS-IS and Level 2 IS-IS network.

LAN V1 (Version 1) NE can

INC-100B
NE only be set as L1 IS.
NE LAN
R
V2, DWDM and U-Node
Area 2
NE NEs can be set either
R as L1 IS, L2 IS or ES.
Area 1
DCCr

LAN
R R
NE
Area 3
NE
NE

R Level 2 IS (V2 NE or Router) Area 4

NE Level 1 IS (V1/V2 NE)

 OSI
ES & IS

Area ID=00010003

Area ID=00010001 Area ID=00010002

 OSI
TARP
SDH NE communicates with NMS using the layers 1-4, but WDM and U-Node NEs fully uses
layers 1-7. And, the mechanism called TARP required for WDM and U-Node NEs
communication is not supported in SDH NE.
In addition, different third party protocol software is adopted on the Server respectively for WDM,
U-Node NEs and SDH NE. Marben is used for WDM and U-Node NEs, and SUN Solstice OSI
for SDH NEs.
Explanation for TARP
WDM and U-Node NE are products originally developed for North America market, and
identification of individual NE on the Server is TID, which is the ID used in North America, but not
NSAP address. However, NSAP address is needed at the communication protocol level so is the
mechanism for finding the NSAP address from TID information. TARP is the mechanism defined
by Bell Core for that purpose. First, NMS sends TARP packet, which includes the TID information
of the target NE and asks what NSAP address the target NE has, to all NEs by broadcast. The
target NE, which has identified TID, sends back the response with NSAP address information.
Then, the NMS-NE communication is directly executed by using the returned NSAP address.
 OSI
TARP

Mechanism of TARP
 OSI
OSI over TCP/IP

OSI over TCP/IP

WDM and U-Node NEs supports the function called as OSI over TCP/IP. This
function makes it possible to connect between Server and GNE through TCP/IP
network. Please take care that this function is not supported by SDH NEs.
 OSI
NSAP address for V2
NSAP address
The NSAP address is given to all NEs in OSI network. Information transmission and routing is done using this
address. Address is inputted to each NE using LCT (Local Craft Terminal). NSAP address is usually decided upon
the customer.
Notice
Make sure NSAP address inputted by LCT and address inputted at INC-100 are the same.

NSAP address
NSAP address is composed of 2 parts, IDP and DSP. IDP is also divided into 2 parts, AFI and IDI.

SDH V1/ V2 recognizes DSP as 3 parts, HO DSP, System ID and SEL. Usually ADI+IDI+HO DSP is used as an
area address and System ID as ID. SEL has a fixed value of 01.

Example
[ADI:49]+[IDI: none] + [DSP: 0000|1111|2222|3333|4444|5555|6666|7777|8888|01]
To make this as Local address, first 2 octets of DSP has to be inputted as IDI.
 OSI
NSAP address for U-Node and WDM
NSAP Address format for WDM and U-Node NEs
NSAP address format for WDM and U-Node NEs is different from one for SDH NE that you
can set any format as follows;

AFI: 39 fixed
IDI: 840F fixed
DFI: 80 fixed
ORG: Any value you like
RES: 0000 fixed
RD: Any value you like
Area: Any value you like

System ID: Automatically assigned by

MAC address Agent unit owns

SEL: You can set the value for each

protocol (FTAM, ASE etc)

(Note) ORG, RD, Area, SEL can be set

by LCT

NSAP address format for WDM NE

39 840F 80 XXXX 0000 XXXX XXXX YYYYYYYYYYYY XX
(Note) XXXX means that you can set any value. YYYY means System ID,
and it is automatically assigned from the MAC address that Agent unit owns.
 OSI
NSAP address
Basic format for NSAP address

Octet

Type of NSAP supported by NE

NE Name Type A Type B Type C
WDM16/32 O X X
WDM80 O O X
Rel5.1 and above
U-Node X O X
SMS-150V/600V/2500C/2500A/2500R2 X X O
 OSI
NSAP address

NSAP Format that can be set in SDH/WDM NE

Type A (ANSI Standard)

39 840f 80 [AAAAAA] 0000 00010001 SYSTEM ID 00
(6 Byte)
Fixed Fixed Fixed User setup Fixed User setup Fixed Fixed
(3 Octet) (4 Octet)

Type B
39 840f 80 [AAAAAA] 0000 00010001 SYSTEM ID 00
(6 Byte)
User setup (13 Octet) Fixed Fixed

Type C
49 [ ] [ ] [ ] [ ] [ ] SYSTEM ID 00
(6 Byte)
User setup (19 Octet) Fixed
 TCP/IP
IP ADDRESS
 TCP/IP
IP ADDRESS

(*): The value of 2 is subtracted from the host address because a total of two addresses
(where all bits of the
host address are 0 and 1) have a special meaning.

All 0: Network address (Example: 192.168.1.0)

This address represents the network itself.

All 1: Broadcast address (Example: 192.168.1.255)

This address is used for communicating with the entire network.
When data is sent to this address, all equipment associated with the same network will
receive this
data. This address is used if the transmission destination is undefined when various
protocols are
initialized.

An IP address has a hierarchical structure. The first half of an address (higher-order bytes) serves
as the identifier of a network associated with the equipment (network address). The latter half of
the address (lower-order bytes) serves as an identifier of equipment in a network (host address).
An IP address is categorized as Class A to Class E depending on the location of the split between
network address and host address. There is a corresponding relationship between each class and
the highest byte.
 TCP/IP
Number of HOP
Number of HOP
The number of HOP indicates the number of networks passed by network equipment in order to reach a
specific network.
The figure below shows the method of calculating the number of HOP. The dashed line area in the figure below
indicates a network, and the number of HOP from R1 to this network is indicated on the right side of the dashed
line area. In this example, the number of HOP from R1 to PC1 is 4.
 TCP/IP
RIP
The Routing Information Protocol (RIP) version 1 is one of the routing protocols. Since the implementation of
RIP version 1 is easy and the processing load is light, it is applied to SDH NE.The routing method of RIP is
performed in the following manner: 1) a router informs the number of HOP required to reach each network (the
number of networks the data passes through until it reaches this network) every 30 seconds to its adjacent
router, and 2) each router calculates the shortest path based on this information. If the information is not
updated from the adjacent router within the designated period, it is assumed that the path to a network via this
router is unreachable, and a new path is calculated. Networks with more than 16 HOP are also assumed as
being unreachable (infinite distance and no data is transferred to this network).
The figure below shows the connection configuration of NE in a management network and the calculation
method of the number of HOP. As far as NE are concerned, the number of HOP to a network to which the LAN
port is connected is defined as the number of HOP until the NE of that network.
 TCP/IP
AGENT functions/performance constraints

AGENT functions/performance constraints

 TCP/IP
AGENT functions/performance constraints
 TCP/IP
Protocol (RIP) constraints

Protocol (RIP) constraints

 TCP/IP
Protocol (RIP) constraints
 TCP/IP
RIP entry
RIP entry
A maximum of 25 network data entries can be sent by 1 RIP, as defined by RFC1058 (Routing Information
Protocol).
A maximum of 23 network data entries can be sent by 1 RIP for SDH, because of the constraint on size
(512 bytes) at the DCC side.

The GNE shown in figure sends network data using RIP at the server side. This RIP contains 4 entries (192.1.2.0,
192.1.3.0, 192.1.100.0, 192.1.101.0).
 OSI & TCP/IP
AGENT Performance
AGENT Performance Problems
Management network designing come with a precondition that all data must be transferred even when there is a
maximum load. Tests have confirmed each NE can only transfer 10 Kbytes of data per second because of the
throughput limit in the DCCr port of its AGENT. When the data transfer volume reaches maximum, an alarm is
automatically transmitted to the NMS Server from each NE. The figure below shows the processing delay during
data transfer.

Conditions:
Reception of ACK TAT at NMS Server : 10 msec.
Transfer delay using DCC of NE : 30 msec.
Size of one packet from NE : 150 bytes
Alarm transmission processing delay at NE : Can be ignored.
 OSI & TCP/IP
AGENT Performance

If the data transfer volume of an NE is Dn, and the number of NEs the data has to pass
through until it reaches the NMS Server is n, then Dn can be calculated using the
following formula.

Therefore, the data D, arriving at a GNE that is connected with N+1 units in a linear
formation, can be expressed as follows.
 OSI & TCP/IP
AGENT Performance
Data flow is known as the amount of automatic response that flows when error occurs. More data
flows through DCC port as number of NE increases, and it is important to keep it under limit,
which is 10 Kbytes/sec. As long as it is kept under limit, there is no necessity to make any
alternative route using Router, Bridge etc. Here is a way of calculating such value.

When automatic response is generated, Round Trip Time (T) is calculated as follows;
It requires 30 ms to pass through 1 NE V1 or V2, 28.7 ms in case of DWDM and U-Node and
14.3 ms for U-Node regenerator. Automatic response is only generated after receiving
acknowledgement from INC-100.
It requires 10msec to acknowledge automatic response from each NE at INC-100.
Number of NEs that passes through from INC-100 to target NE is counted as N.

Calculation would be:

T=2*M*N+0.01, (M= time for pass through NE).
Assuming M= 0.03, the packet size for each automatic response is approximately 150
Bytes/packet. Therefore the amount of automatic response produced in 1 sec is:
150/T

Assume lots of NE produces automatic response to INC-100, passing through 1 DCC.

Total amount of automatic response from each NE is:
150/T1+150/T2+150/Tn
Maximum data flow through DCC, that is accepted by NEC product is 10Kbytes/sec.
150/T1+150/T2++150/Tn < 10Kbytes/sec
 OSI & TCP/IP
AGENT Performance
The figure below shows the data transfer volume for a linear connection. When a network is
configured using linear connections only, the speed is controlled by the constraints on the number
of HOP of RIP and by the data volume not exceeding the 10 kbps limit.
 OSI & TCP/IP
AGENT Performance
The caution must be exercised for a configuration that has several connected rings (7 rings in the figure) as shown
below because the data transfer volume can exceed the limit.
D = 1 D1 + 7 D2 + 14 D3 + 7 D4
= 2142 + 7 1153 + 14 789 + 7 600
= 25249 byte/sec.

As a result, the data transfer volume exceeds the limit.

In case of the above, a router (no data transfer volume limit) must be installed [SEE NEXT PAGE].
 OSI & TCP/IP
AGENT Performance

GNE
 OSI & TCP/IP
AGENT Performance

xM
If M=1
D = 1 D1 = 2142 byte/sec.
If M=2
D = 4 D1 = 2x2142 = 8568 byte/sec.
If M=5
D = 5 D1 = 5x2142 = 10710 byte/sec (>10k)
 OSI & TCP/IP
AGENT
Performance STN1 STN2 STN3 OPTICAL FIBER
STN10

ROUTERS

STN4
INC-100MS
STN9

STN5

STN8 STN7 STN6

 OSI & TCP/IP
AGENT STN1 STN2
Performance STN3 OPTICAL FIBER

GNE2
1 2 2 3 1 2 2 2 3 3

2
STN10

3
ROUTERS

STN4
3
GNE1

3
4
3

INC-100MS

4
STN9

2
2

4
STN5
1

2 3 4 4 4 4 5 5 5 5 5 4 6 6 5

STN8 STN7 STN6

 OSI & TCP/IP
AGENT Performance
D(GNE1) = [ (2 D1 )+ (5 D2 )+ (3 D3 )+ (5 D4 )+ (6 D5) +( 2 D6)
= [ (22142 )+ (5 1153 )+ (3 789 )+ (5 600 )+ (6 484) +( 2 405)
= 4284 + 5765 + 2367 + 3000 + 2904 + 810

= 19130 (>10k)

D(GNE1) = [ (2 D1 )+ (6 D2 )+ (6 D3 )+ (3 D4 )+ (1 D5) +( 2 D6)

= [ (22142 )+ (6 1153 )+ (6 789 )+ (3 600 )+ (1 484) +( 2 405)
= 4284 + 6918 + 4734 + 1800 + 484 + 810

= 19030 (>10k)
 NMS-GNE Bandwidth
NMS-NE Bandwidth (WAN Line)

The Bandwidth (WAN Line) needed between Router GNE,

Packet for normal condition + Excessive Packets = 19Kbps + 96 Kbps = 115Kbps
(See explanation below for Packet for normal condition & Excessive Packets )

Therefore 128Kbps is a proper NMS-NE Bandwidth (WAN Line)

Example for Single Server

If there are 5 GNEs connected to the router,
Then NMS-GNE Bandwidth = 128kbps x 5 = 640kbps

Example for Duplicate Server

If there are 5 GNEs connected to the router,
Then NMS-GNE Bandwidth = 128kbps x 5 x 2 (Duplicated)= 1280kbps
 NMS-GNE Bandwidth
Packet for normal condition (for TCP/IP)

All the communications are 2-way, the table below shows the packets needed for one way only

Class Type Packet for normal condition (bps)

Health check of application between
NMS and NE
Protocol Packet of layer 4 (Transport
layer) between NMS and NE
Rip, ETC
Health check for each NE in every 3
minutes
Inactivity Packet for every NE {for every
20 seconds}
3packets x 300byte/180seconds 2400bps
x60(No. of NEs under the GNE)
1packet x 100byte/20seconds 2400bps
x60(No. of NEs under the GNE)
+alpha

Total 4.8Kbps (+alpha)


Packet for normal condition (for OSI)
All the communications are 2-way, the table below shows the packets needed for one way only
Class
Health check of application between
NMS and NE
Protocol Packet of layer 4 (Transport
layer) between NMS and NE
Protocol Packet of layer 3 (Network
layer) between Router and GNE
NMS-GNE Bandwidth
Type
Health check for each NE in every 3
minutes
Inactivity Packet for every NE {for every
20 seconds}
L1 ISH (Intermediate System Hello)
Packet {for every 10 seconds}
L1 IIH (IS to IS Hello) Packet {for every
3 seconds}
L2 IIH packet {for every 3 seconds}
Packet for normal condition (bps)
3packets x 300byte/180seconds 2400bps
x60(No. of NEs under the GNE)
1packet x 100byte/20seconds 2400bps
x60(No. of NEs under the GNE)
1packet x 100byte/10seconds 240bps
1packet x 1500byte/3seconds 4000bps
1packet x 1500byte/3seconds 4000bps

L1 CSNP (Complete Sequence 2packet x 1500byte/10seconds (For 3600bps

Numbers PDU) Packet {for every 10 150 per Area)
seconds}
L2 CSNP Packet {for every 10 seconds} 1packet x 1500byte/10seconds (For 1200bps
75 Area)

In every 900 seconds, L1 LSP (Link 1packet x 400byte/900seconds x 533bps

state PDU) is transmitted from all L1 150(No. of NE in 1 area)
equipments. (Excluding Pseudo LSP)
In every 900 seconds, L2 LSP is 1packet x 400byte/900seconds x 75 267bps
transmitted from all L2 equipments. (No. of Area)
(Excluding Pseudo LSP)

Total 19Kbps
 NMS-GNE Bandwidth
Excessive Packets_ Auto-report packets
1. Auto-report packets
If there is error in any line, Path status (for every Path) will be reported to NMS. If there are 500 Path,
there will be alarm on both side of the Path and Path status (more than 2000 Auto-reports) of both sides
will be reported to NMS. (After the situation is recovered, once again, more than 2000 Auto-reports will be
reported to NMS)

40 alarms (Alarms/Status/TCA(PM)/others) per seconds can be reported from GNE.

40 packets x 300 bytes = 96kbps

Time needed for sending All the Auto-reports (2000 alarms)

Bandwidth between Communication Line Time needed for sending the

NMS-NE Auto-reports
64kbps WAN Line 75 seconds

128kbps GNE Processing 50 seconds

192kbps GNE Processing

 NMS-GNE Bandwidth
Excessive Packets_ F/W Download

2. F/W Download
When executing F/W Download (9 Mbyte) from NMS to NE, Download time is as shown below:

Bandwidth between Communication Line Download Time

NMS-NE
64kbps WAN Line 1125 seconds (19 Mins)

128kbps WAN Line 563 seconds (9 Mins)

192kbps WAN Line/DCC Line 375 seconds (6 Mins)

256kbps DCC Line

 NMS-GNE Bandwidth
Excessive Packets - Example

Step 1 : WDM Network Model

WDM WDM WDM WDM WDM WDM WDM WDM

WDM WDM WDM WDM WDM WDM

4CH 4CH 4CH

6CH 6CH 6CH

2500A fiber cut 2500A 2500A

600V 600V 600V 600V 600V 600V

2M Intf 2M Intf 2M Intf
U-Node U-Node U-Node

2M Intf 2M Intf 2M Intf

Example. 7 stations
 NMS-GNE Bandwidth
Excessive Packets - Example

Step 2 : Main Report from SDH

2500A 2500A 2500A 2500A

600V 600V PPS 600V 600V 600V 600V 600V 600V

.. .. .. .. .. .. .. ..
2M Intf 2M Intf 2M Intf 2M Intf
TU12 AIS Alarm
PPS Switching Status

2500A 2500A 2500A

600V 600V 600V 600V 600V 600V PPS

.. .. .. .. .. ..
2M Intf 2M Intf 2M Intf
TU12 AIS Alarm TU12 AIS Alarm
TU12 AIS Alarm
PPS Switching Status
 NMS-GNE Bandwidth
Excessive Packets - Example

Step 3 : Main Report from U-Node

U-Node U-Node U-Node U-Node

.. .. .. ..
PPS
2M Intf 2M Intf 2M Intf 2M Intf

TU12 AIS Alarm

PPS Switching Status

U-Node U-Node U-Node

.. .. ..
PPS
2M Intf 2M Intf 2M Intf

TU12 AIS Alarm

PPS Switching Status

Example. 7 stations
 NMS-GNE Bandwidth
Excessive Packets - Example

Step 4 : Total Report

Total report :
all though node => TU12 AIS Alarm
terminate node => PPS Switching Alarm

1CH (2.5G) : 1008 path x 6(average) = 6048 reports

Example.
10CH : 60480 reports
 NMS-GNE Bandwidth
Excessive Packets - Example

Step 5 : Server Processing

60480 reports
60480 reports

Client1
. Server0
.

(Master) DCN

60480
NEs
reports
(Note) NE send this
Client12 Server1 60480 reports reports for each server.

Traffic in DCN is heavy.

Server0 can receive 30 packets per second from NE.

60480/30 = 2016 s = 34 min
- DCN is heavy and NE can not reply quickly for the command from server.

Server0 can deal with 12 reports per second.

60480/12 = 5040 s = 84 min
- Server processing is heavy.
END