You are on page 1of 42

DCN Guidelines

iPASOLINK

iPASO DCN Guidelines

For 2-way configurations,


back to back cable is no
longer necessary and only 1
IP is needed in this case as
opposed to 2 IP address
when
two
IDUs
are
connected back to back.

GNEs NMS port is


connected to Switch/Router
and on the NEs back to back
configurations, NE1 ports are
connected together by LAN
cable (cross or straight).

SV is out of band, the NMS


signal is separated from the
main traffic all throughout the
path.

iPasolink Network

iPASO DCN Guidelines

iPASO DCN Guidelines

Connecting iPasolink to Legacy Equipments

iPASO DCN Guidelines

Connecting iPasolink to Legacy Equipments

iPASO DCN Guidelines

Connecting iPasolink to Legacy Equipments

iPASO DCN Guidelines

Connecting iPasolink to Legacy Equipments

iPASO DCN Guidelines

SUPPORTED DCN CONNECTIONS (LEGACY)

iPasolink can be allocated


with the same IP block with
Pasolink V4 which is /28.
Even iPasolink can use /26,
Pasolink V4 F/W (limitation)
can only accommodate /28.

Straight or Cross CAT-5


LAN cable is connected to
either NMS or NE1 port of
iPasolink going to NMS LAN
port of Pasolink V4.

iPASO DCN Guidelines

Case 1: iPaso is GNE, Paso V4 is PMC LAN w/ bridge F/W version 8.00

iPASO DCN Guidelines

Case 1: iPaso is GNE, Paso V4 is PMC LAN w/ bridge F/W version 8.00

iPASO DCN Guidelines

Case 1: iPaso is GNE, Paso V4 is PMC LAN w/ bridge F/W version 8.00

iPASO DCN Guidelines

10

 Configuring V4 in bridge mode using PNMTj involves configuring the HDLC portion adding difficulty
to the configuration.

 Necessary to reconfigure the IP network and subnet mask for existing Pasolink V4 networks where
iPasolink will be inserted.

 Only Pasolink V4 PMC LAN with bridge function F/W version 8.00 is supported.

 Only maximum multiple /28 subnet is only available.

DISADVANTAGES:

 Simple cabling between iPasolink and Pasolink V4 since only LAN cable CAT-5 is needed for back to
back connections.

 Shown a single network in the PNMS logical connection view.

 Auto-Discovery can be use for all NEs (iPasolink and Pasolink V4).

ADVANTAGES:

Case 1: iPaso is GNE, Paso V4 is PMC LAN w/ bridge F/W version 8.00

 iPasolink is configured
using LCT Web and it can
be auto-discover in PNMS,
while Pasolink V4 must be
configured using NCT, and
the first V4 in the NE cluster
will become CPMC. These
NCT file will be uploaded to
PNMS, while the .cfg will
will be downloaded in the
NEs.

 iPasolink can be allocated


with
/26
subnet
and
Pasolink
V4
can
be
allocated /28 subnet.

 Connecting Pasolink V4
PMC Serial behind iPasolink
is via the NMS/RA port of V4
going to the Async port of
iPasolink which is NE2 (PPP
at 19.2kbps line speed).

iPASO DCN Guidelines

Case 2: iPaso is GNE, Paso V4 is PMC Serial

11

iPASO DCN Guidelines

Case 2: iPaso is GNE, Paso V4 is PMC Serial

12

iPASO DCN Guidelines

Case 2: iPaso is GNE, Paso V4 is PMC Serial

13

iPASO DCN Guidelines

14

 Maybe necessary to re-configure the IP network and subnet for existing V4 networks where iPasolink
will be inserted.

 Auto-Discovery is limited only to iPasolink NEs.

 iPasolink network and Pasolink V4 network are shown on a separate maps in PNMS logical
connection view.

DISADVANTAGES:

 If existing Pasolink V4 of the customer is PMC Serial, then no need to replace it with PMC LAN.

 Larger subnet mask (/26) can be allocated for iPasolink network and includes Pasolink V4 network
(/28).

ADVANTAGES:

Case 2: iPaso is GNE, Paso V4 is PMC Serial

 Connection is via CAT-5


LAN cable, straight or cross
cable as shown in the
illustration.

 In such cases that there is


no possibility to connect an
IP network, it is possible to
get the SV through the
Pasolink V4 cluster, but V4
must have User/WS/SC
LAN. Then the iPasolink SV
signal will be carried
separately from the Pasolink
V4 signal.

 In cases like iPasolink will


be
connected
behind
Pasolink V4, then this is the
supported DCN connection.
iPasolink cluster is normally
has the direct access to an
IP network, so this DCN
connection is a rare case
design.

iPASO DCN Guidelines

Case 3: Pasolink V4 with User/WS/SC LAN is GNE

15

 The 1st iPasolink NE will


become the GNE.

 Auto-Discovery in PNMS
will still be supported for
iPasolink network while there
is a need to upload the NCT
map in PNMS for created V4
cluster or network.

 Pasolink V4 must be
equipped with WS/SC LAN or
User LAN module/cards.

 iPasolink will be created in


a separate subnet from the
Pasolink V4. There is no need
to re-configure the existing
Pasolink V4 network. But in
cases like both Pasolink V4
and iPasolink are new
networks, then Pasolink V4
must be configured using NCT
while iPasolink must be
configured using LCT Web.

iPASO DCN Guidelines

Case 3: Pasolink V4 with User/WS/SC LAN is GNE

16

 PNMTj will be use to


configure the IP address
settings for Pasolink +/Mx,
while LCT Web for iPasolink
and both Nes can be AutoDiscover in PNMS.

Both iPasolink and Paso


+/Mx can be allocated same
subnetmask (/26).

 This DCN connection as


shown will only be supported if
Pasolink +/Mx is equipped
with the following bridge F/W
versions:
a). STM-1 (1.6.4)
b). PDH (1.2.1)
c). Mx (1.2.9)

 DCN Connection is using


CAT-5 LAN cable, straight or
cross as illustrated.

iPASO DCN Guidelines

Case 5: iPaso is GNE, Pasolink +/Mx through LAN

17

iPASO DCN Guidelines

Case 5: iPaso is GNE, Pasolink +/Mx through LAN

18

iPASO DCN Guidelines

Case 5: iPaso is GNE, Pasolink +/Mx through LAN

19

iPASO DCN Guidelines

 CTRL F/W upgrade maybe necessary.

 Only up to 62 NEs is supported for one network. Separate network creation and DCN will be
required for networks larger than 62 NEs.

DISADVANTAGES:

20

 In cases such as the iPasolink is use as the replacement / upgrade equipment for existing Pasolink
+/Mx, the same IP address can be utilized as long as the iPasolink is the upstream or GNE.

 Auto-Discovery function is supported for both iPasolink and Pasolink +/Mx.

 iPasolink and Pasolink +/Mx network can be seen in one network at PNMS logical connection view.

 Larger subnet mask (/26) can be allocated for both iPasolink and Pasolink +/Mx network.

ADVANTAGES:

Case 5: iPaso is GNE, Pasolink +/Mx through LAN

 The SV signal of the


iPasolink +/Mx and iPasolink
clusters will be carried
separately in the Pasolink
+/Mx radio.

 SC LAN of Pasolink +/Mx


will be connected to the NMS
port of iPasolink using CAT-5
LAN cable, straight or cross
and the SV signal from the
iPasolink will pass through to
this SC LAN port.

 In cases like this that


iPasolink will be connected
behind Pasolink V4, the
supported DCN connection is
as shown and illustrated. The
Pasolink +/Mx must be
equipped by SC LAN
card/module.

iPASO DCN Guidelines

Case 7: Pasolink +/Mx with SC LAN is GNE

21

 The subnet/clusters are


separate in the connection.
Wherein the Pasolink +/Mx
network can be existing or a
new network that can be
configured using NCT or
PNMTj (Bridge with AutoDiscovery), while iPasolink
will use LCT Web for IP
settings configuration and
Auto-Discovery in PNMS.

iPASO DCN Guidelines

Case 7: Pasolink +/Mx with SC LAN is GNE

22

iPASO DCN Guidelines

23

NOT SUPPORTED DCN CONNECTIONS (LEGACY)

iPASO DCN Guidelines

Case 4: Pasolink V4 PMC Serial is GNE

24

iPASO DCN Guidelines

Case 6: iPasolink is GNE, Pasolink +/Mx through V.11

25

iPASO DCN Guidelines

Case 8: Pasolink +/Mx V.11 is GNE

26

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

27

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

28

iPASO DCN Guidelines

29

SUPPORTED DCN CONNECTIONS (PASO NEO)

iPASO DCN Guidelines

30

 Pasolink NEO IP setting can be configured using NCT or PNMTj, while iPasolink link will use LCT Web.
But both supports auto-discovery in PNMS.

 Connection is using CAT-5 LAN cable, straight or cross from NEO NMS port to one of the iPasolink
FE/GbE ports in used. Both supports /26 network.

 Pasolink NEO SV can be carried through the iPasolink main traffic using VLAN. Pasolink NEO SV will
be extracted from the main traffic VLAN in GNE and in the PNMS.

Connecting iPasolink to Pasolink NEO Equipments

iPASO DCN Guidelines

 For physical back to back connections in this scenario, please refer to the next slide.

 On the GNE side, both SV signal are extracted from the NMS port of iPasolink Both support /26
network.

31

 In this DCN connection type, Pasolink NEO SV can be carried through the iPasolink 384kbps SV pipe.

Connecting iPasolink to Pasolink NEO Equipments

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

32

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

33

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

34

iPASO DCN Guidelines

Connecting iPasolink to Pasolink NEO Equipments

35

iPASO DCN Guidelines

Connecting iPasolink (Upstream) to Pasolink NEO Equipments

36

iPASO DCN Guidelines

37

IP Subnet and Cluster will be separate in PNMS

Connecting iPasolink (Downstream) to Pasolink NEO Equipments

iPASO DCN Guidelines

IP Subnet and Cluster will be same in PNMS.

Connecting iPasolink (Downstream) to Pasolink NEO Equipments

38

iPASO DCN Guidelines

RESTRICTIONS & NOT SUPPORTED DCN


CONNECTIONS (PASO NEO)

39

10.8.61.1

10.8.61.2

(Branch NE)

NEO

172.18.0.65

(Root NE)

NEO

172.18.0.1

(Branch NE)

NEO

10.8.61.65

(Root NE Bridge)

NEO

10.8.61.2

iPASO

NEO

iPASO

NEO

iPASO

NEO

iPASO

NEO
NMS/NE

172.18.0.67

NMS/NE

172.18.0.3

172.18.0.2

NMS/NE

10.8.61.67

10.8.61.66

NMS/NE

10.8.61.4

10.8.61.3

172.18.0.66

iPASO DCN Guidelines

10.8.61.6

10.8.61.1

172.18.0.5

192.168.1.2

192.168.1.1

pattern 2

PNMSj

PNMSj

192.168.1.2

192.168.1.1

pattern 1

<Condition>
 iPASOLINK must be located in NEO(Root NE Bridge) network.
 iPASOLINK can not be located in NEO(Root NE) or NEO(Branch NE) network.

iPASO

172.18.0.68

iPASO

172.18.0.4

iPASO

10.8.61.68

iPASO

10.8.61.5

40

Router
Same subnet
Radio
Wired

- IP address is an example.

Terima Kasih

iPASO DCN Guidelines

41