Rule of Meshing in Abc-F Networks With Signaling Over Ip/Use of Modulo 128

OmniPCX Enterprise
RULE OF MESHING IN ABC-F NETWORKS

WITH SIGNALING OVER IP/USE OF
MODULO 128
TECHNICAL COMMUNICATION No. TC0975 Ed. 03
OmniPCX Enterprise Nb of pages : 6 Date : 20 May 2014
URGENT
NOT URGENT TEMPORARY PERMANENT
SUBJECT: RULE OF MESHING IN ABC-F NETWORKS WITH SIGNALING OVER IP / USE OF

MODULO 128
CONTENTS
1. PURPOSE .................................................................................... 2
2. REMINDER ABOUT BACKBONE NOTION ..................................... 2
3. POSSIBLE MISFUNCTIONING ...................................................... 2
4. MANAGEMENT RULE .................................................................. 3
5. MESH RULE ................................................................................ 3
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2014 Alcatel-Lucent. All rights reserved.
Ed. 03 / 20 May 2014 1 TC0975

OmniPCX Enterprise
RÈGLE DE MAILLAGE DANS LES RÉSEAUX
ABC-F À SIGNALISATION SUR IP /
UTILISATION DU MODULO 128
1. PURPOSE
The purpose of this technical communication is to provide a rule in the node mesh of a backbone
with logical links using signaling over IP.
It concerns only link mesh; VPN hops are not concerned.
Backbones with TDM logical links (standard T2) are concerned by this technical communication only
if there is an instability of T2 link that may cause loops of 2832, 2846, 2872 messages; refer to
section 3.
This technical communication takes place the technical communication TC0702 System message
2873=PH:Update seq. synchro – Releases  6.1.
2. REMINDER ABOUT BACKBONE NOTION

A backbone is a set of meshed nodes whose logical links are created as "dynamic" routing type i.e.
X25 routing messages are sent to inform other nodes on the status of remote resources (presence of
other nodes, information about the rise or fall of remote links, X25 costs on remote ongoing
communications, X25 costs on shared trunk groups, etc.).
Nodes with "static" routing is not part of backbone and are ended nodes to a single adjacent node.
3. POSSIBLE MISFUNCTIONING
An instability of logical links can occur on strongly meshed backbone networks and already running.
This instability is caused by a loss of the link.
This loss of the logical link can occur when a node toggles or during an operation on the IP network
of the customer.
The logical links go down and rise permanently with the following messages:
17/06/07 08:13:26 000021M|19/00/0/000|=2:2868=PH:IP Hybrid Link to 5 is broken

(type 4 access 1 sig Main)
17/06/07 08:13:26 000021M|19/00/0/000|=3:2867=PH:Hybrid Access (5 1 Main) goes
down
17/06/07 08:13:26 000021M|19/00/0/000|=3:2865=PH:LLP 0 is down on Hybrid Access
(5 1 Main
17/06/07 08:14:35 000021M|19/00/0/000|=5:2864=PH:LLP 0 is up on Hybrid Access (5
1 Main)
17/06/07 08:14:43 000021M|5-21 |=5:2827=PH:Local link [21 5] is up
17/06/07 08:15:06 000021M|19/00/0/000|=2:2868=PH:IP Hybrid Link to 5 is broken
(type 4 access 1 sig Main)
17/06/07 08:15:06 000021M|19/00/0/000|=3:2867=PH:Hybrid Access (5 1 Main) goes
down
17/06/07 08:15:06 000021M|19/00/0/000|=3:2865=PH:LLP 0 is down on Hybrid Access
(5 1 Main
TC0975 2 Ed. 03 / 20 May 2014

OmniPCX Enterprise
MODULO 128
If this misfunctioning continues, the following incidents may appear on the other nodes specifying an
abnormal state of the logical link that changes from the accessible state to inaccessible in the same
second.
17/06/07 17:17:01 001001M|--/--/-/---|=3:2846=PH:Node 21 is reachable

17/06/07 17:17:01 001001M|--/--/-/---|=5:2872=PH:Remote link [21 5] is down
17/06/07 17:17:01 001001M|--/--/-/---|=3:2832=PH:Node 21 is unreachable
These incidents can be edited for several minutes and even several hours.
4. MANAGEMENT RULE
Management of modulo 128 for X25
In X25 management (X25 System Parameters), the Maintenance Packet mod 128 =
Yes/No parameter is used to define the numbering of maintenance packets for X25 routing:
No = Numbering modulo 8 = packets numbered from 0 to 7 (default value)
Yes = Numbering modulo 128 = packets numbered from 0 to 127
This parameter is to set to Yes to avoid an instability of logical links and loops of 2832 and 2872
incidents on the nodes of a meshed network.
Note
The modulo must be the same on each node of the network.
During the management, incidents of routing messages desynchronization relative to bad numbering
of expected and sent packets will appear on the nodes of the network.
When all nodes will be updated with the same modulo, the desynchronization incidents will stop
automatically.
5. MESH RULE
The mesh rule is to be applied on the networks which have an instability of logical links.
Concerned Releases:  6.1.
Ed. 03 / 20 May 2014 3 TC0975

OmniPCX Enterprise
RÈGLE DE MAILLAGE DANS LES RÉSEAUX
ABC-F À SIGNALISATION SUR IP /
UTILISATION DU MODULO 128
Installation with CPU 4400 and CS Installation with CS2 and

Appliance Server
Maximum number of 3 8
adjacent for each
node in a backbone
Change from Yes Yes
modulo 8 to modulo
128
Example
27/07/07 01:06:08 001003M|--/--/-/---|=3:2873=PH:Update seq synchro:Src=1

msg(exp=8 rcv=3) waitDelay=400 s
27/07/07 01:13:25 001003M|--/--/-/---|=3:2841=PH:link(1 17) is not updated
TC0975 4 Ed. 03 / 20 May 2014

OmniPCX Enterprise
MODULO 128
The incidents 2873 allow to know if the modulo is the same on all nodes.
The number of expected / received message specified in the incident gives the modulo of packet.
Example

Src=18 msg(exp=8 rcv=2)
The node 3 receives a message from node 18. It expects a message 8 and receives a message 2;
therefore the node 3 is in modulo 128.
The node 18 is in modulo 8.
Specific case
If there are one or more nodes connected by TDM logical links (standard T2) in an IP backbone
managed with modulo 128, they must also implement the modulo 128.
Ed. 03 / 20 May 2014 5 TC0975

Rule of Meshing in Abc-F Networks With Signaling Over Ip/Use of Modulo 128

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

Rule of Meshing in Abc-F Networks With Signaling Over Ip/Use of Modulo 128

Uploaded by

Copyright:

Available Formats

OmniPCX Enterprise

RULE OF MESHING IN ABC-F NETWORKS

TECHNICAL COMMUNICATION No. TC0975 Ed. 03

OmniPCX Enterprise Nb of pages : 6 Date : 20 May 2014

NOT URGENT TEMPORARY PERMANENT

SUBJECT: RULE OF MESHING IN ABC-F NETWORKS WITH SIGNALING OVER IP / USE OF

2. REMINDER ABOUT BACKBONE NOTION ..................................... 2

3. POSSIBLE MISFUNCTIONING ...................................................... 2

4. MANAGEMENT RULE .................................................................. 3

5. MESH RULE ................................................................................ 3

Ed. 03 / 20 May 2014 1 TC0975

2. REMINDER ABOUT BACKBONE NOTION

17/06/07 08:13:26 000021M|19/00/0/000|=2:2868=PH:IP Hybrid Link to 5 is broken

TC0975 2 Ed. 03 / 20 May 2014

17/06/07 17:17:01 001001M|--/--/-/---|=3:2846=PH:Node 21 is reachable

Ed. 03 / 20 May 2014 3 TC0975

Installation with CPU 4400 and CS Installation with CS2 and

27/07/07 01:06:08 001003M|--/--/-/---|=3:2873=PH:Update seq synchro:Src=1

TC0975 4 Ed. 03 / 20 May 2014

27/07/07 01:19:37 001003M|--/--/-/---|=3:2873=PH:Update seq synchro:Src=18

Ed. 03 / 20 May 2014 5 TC0975

You might also like