NMS Connectivity Checking

NMS Connectivity Basics

NECI-Technical Center

NEC Internal Use Only© NEC Corporation 2005

Page 2

256 128 64 32 16 8 4 2 1

28 27 26 25 24 23 22 22 20

00000000 : 00000000 : 0000000 : 00000000 Subnet Subnet available IP No.of Subnets

8 : 8 : 8 : 8 /24 X.X.X.000 /24 -256*1

00000000 : 00000000 : 00000000 : 0/0000000 /25 X.X.X.128 /25 -128 *2

00000000 : 00000000 : 00000000 : 00/000000 /26 X.X.X.192 /26 -64 *4

00000000 : 00000000 : 00000000 : 000/00000 /27 X.X.X.224 /27 -32 *8

00000000 : 00000000 : 00000000 : 0000/0000 /28 X.X.X.240 /28 -16 *16

00000000 : 00000000 : 00000000 : 00000/000 /29 X.X.X.248 /29 -08 *32

00000000 : 00000000 : 00000000 : 000000/00 /30 X.X.X.252 /30 -04 *64

00000000 : 00000000 : 00000000 : 0000000/0 /31 X.X.X.254 /31 -02 *128

CLASS A 1-126/8 === Networks 28 & Hosts 224

CLASS B 128-191/16 === Networks 216 & Hosts 216

CLASS C 192-223/24 ==Networks 224 & Hosts 28

Ex : 192.168.1.0/24

Network address 192.168.1.0

Valid Hosts : 192.168.1.1 – 254

Broadcast address : 192.168.1.255

Mask : 255.255.255.0


Page 3Ex : 192.168.1.0/25 EX: 192.168.1.128.0/25

Network address 192.168.1.0 N/W A : 192.168.1.128

Valid Hosts : 192.168.1.1 – 126 Valid Hosts : 192.168.1.129-254

Broadcast address : 192.168.1.127 Broad Cast Address : 192.168.1.255

Mask : 255.255.255.128 Mask : 255.255.255.128

Ex : 192.168.1.0/26 EX: 192.168.1.128.0/26


Valid Hosts : 192.168.1.1 – 62 Valid Hosts : 192.168.1.65 -126


Mask : 255.255.255.192 Mask : 255.255.255.192

Ex : 192.168.1.0/26 EX: 192.168.1.128.0/26


Valid Hosts : 192.168.1.129 -190 Valid Hosts : 192.168.1.193 -254


Mask : 255.255.255.192 Mask : 255.255.255.192


Page 4

Basic Concepts IP address Classes :

IP address are divided into 5 CLASSES A to E

Class ―D‖ address are used for Multicasting

Class ―A‖ address are reserved for testing & some mysterious future use.

CLASS A 0 to 127CALSS B 128 to 191CLASS C 192 to 223CLASS D 224 to 239CLASS E 240 to 255

For Private Addressing

Class A 10.0.0.0 to 10.255.255.255 ----- 1 Class A networkClass B 172.16.0.0 to 172.31.255.255 ------ 16 Contiguous Class B NetworksClass C 192.168.0.0 to 192.168.255.255 -----255 contiguous Class C networks

Why Subnetting :

Network administrators sometimes need to divide networks, particularly large networks, into smaller networks,

called subnetworks,in order to provide extra flexibility.

The primary reason for using a subnet is to reduce the size of a broadcast domain.Broadcast are sent to all hosts on a network or subnetwork.When broadcast traffic begins to consume too much of the available bandwidth, network administrator may choose to reduce the size of the broadcast domain.


Page 5

Class A Subnet MasksSubnet Mask

No.of 1 Bits in Mask

No.of Subnets Number of Hosts per subnet

255.0.0.0 8 0 16777216-2=16,777,214

255.192.0.0 10 4 4194304-2 = 4,194,302

255.240.0.0 12 16 1048576-2 = 10,485,74

255.255.0.0 16 256 65536-2 = 65534

255.255.128.0 17 512 32768-2=32766

255.255.240.0 20 4096 4096-2 = 4094

255.255.255.255.128 25 131072 128-2=126

255.255.255.255.240 28 1048576 16-2=14

255.255.255.255.252 30 4194304 4-2 = 2


Page 6

Class B Subnet MasksSubnet Mask


No.of Subnets

Number of Hosts per subnet

Binary Subnet Mask

255.255.0.0 16 0 65536-2=65534 111111111.11111111.00000000.00000000

255.255.192.0 18 4 32768-2=32766 111111111.11111111.11000000.00000000

255.255.240.0 20 16 4096-2=4094 111111111.11111111.11110000.00000000

255.255.255.0 24 256 256-2=254 111111111.11111111.11111111.00000000

255.255.255.240 28 4096 16-2=14 111111111.11111111.11111111.11110000

255.255.255.252 30 16384 4-2=2 111111111.11111111.11111111.11111100


Page 7

Class C Subnet MasksSubnet Mask


No.of Subnets Number of Hosts per subnet Binary Subnet Mask

255.255.255.0 24 0 256-2=254 11111111.11111111.11111111.00000000

255.255.255.128 25 2 128-2=126 11111111.11111111.11111111.10000000

255.255.255.192 26 4 64-2=62 11111111.11111111.11111111.11000000

255.255.255.224 27 8 32-2=30 11111111.11111111.11111111.11100000

255.255.255.240 28 16 16-2=14 11111111.11111111.11111111.11110000

255.255.255.248 29 32 8-2=6 11111111.11111111.11111111.11111000

255.255.255.252 30 64 4-2=2 11111111.11111111.11111111.11111100

255.255.255.254 31 128 2-2=0 11111111.11111111.11111111.11111110


Page 8

PDH Rs232 NE1 NE2 V.11

NEOi All Ethernet

Pas0+ Rs 422 Synch Rs 485 A synch

PDH/SDH 255.255.255.252 4 - 2

PDH/SDH 255.255.255.248 8 - 6

PDH/SDH 255.255.255.240 16 - 14

SDH 255.255.255.224 32 - 30

SDH 255.255.255.192 64 - 62


Page 9

Before Implementation Check following Information:

1.IP Plan for EACH Element, NMS Server status(ON/OFF) & Sever IP .

2.DCN (Physical Connectivity) E1 Connectivity Between Server to Root NE.

3.Equipment availability at Root NE Location i.e. E1 to Ethernet converter/any Other equipment Like BG20,XDM 100 and Modem/Switch (to Connect multiple root NE)

4.Equipment availability at Server Location i.e. E1 to Ethernet converter/any Other equipment Like BG20,XDM 100 etc and Switch/Modem(to connect multiple Root NE’s).

5. NEC idu NMS and NE Port(RJ45) type -Auto Negotiation / Auto MDI/MDIX-10base-T.(Full and Half duplex)

6.Check with TTSL E1 Readiness (Root NE to Server Location).

7.Carry following tools with implementation Engg.Laptop,RJ 45 Crimp tool,RJ 45 Connectors,Cat5 Cable. Login cables,IP Plan, Cable Tester.


Page 10

172.18.0.0

255.255.255.0

NMS PC IP : 172.18.0.1

Mask : 255.255.255.0

NMS PC Root NE NEC IDUPNMS IP : 172.18.0.2

Mask : 255.255.255.0

Default GW : 172.18.0.1

192.168.30.0

IDU IP : 192.168.30.1

Mask : 255.255.255.0

PNMS IP : 172.18.0.4

Mask : 255.255.255.0

Default GW : 172.18.0.1

192.168.20.0

IDU IP : 192.168.20.1

Mask : 255.255.255.0

PNMS IP : 172.18.0.3

Mask : 255.255.255.0

Default GW : 172.18.0.1

192.168.18.0

IDU IP : 192.168.18.1

Mask : 255.255.255.0

Add Routes in NMS PC Permanent -P

1.Route add 192.168.30.0 mask 255.255.255.0 172.18.0.2

2. Route add 192.168.18.0 mask 255.255.255.0 172.18.0.3

3. Route add 192.168.20.0 mask 255.255.255.0 172.18.0.4

E1 to Ethernet

Converter or any Other

Equipment(BG20,XDM

100 etc..)

Example

Network

Root NE NEC IDU

Root NE NEC IDU


Page 11

HOW to Check Connectivity Between Root NE to Server Location:1/4

1. Root NE and Server Location -- E1 to Ethernet Converters:1.Server Location:

Connect Server to Ethernet converter by using Straight or Cross Cable .(RJ 45) .(Ex : Server equipped with

IP 10.10.10.1 mask 255.255.255.0).

2.Root NE Location:

Connect your Laptop to Ethernet converter port by using Straight or Cross Cable(RJ 45) and assign IP to

your Laptop with in same subnet of Server IP (Laptop and Server IP with in same Subnet ) ( Ex. Laptop IP

:10.10.10.2 mask 255.255.255.0)

3.Goto START>>RUN>>CMD>>Now your are in Command window (Below window Display )

4.Ping from Root NE Location to Server IP (Ex. Ping 10.10.10.1) if your are getting Reply from Server IP Your

Connectivity Between Root NE to Server Ready to use VISE VERSA Check from Server to LAPTOP.


Page 12

5. Login to IDU Assign IP address as per IP Plan and Remove cable from your laptop connect to IDU NMS Port.

6. Ping from NMS PC to IDU IP you can get reply from IDU NMS IP after that add route Command as per Slide no 10.

7. Some times when you connected Laptop in Both ends you can get Reply from One end to another end . But when u connected to IDU your are not getting Reply. In this case follow below Flow Chart and check Following Configuration.

Check IDU NMS IP and Server IP with in same subnet or NOT

Check Both ends Cable connectivity

Check E1 to Ethernet Converter Ports LED Blinking or NOT(Green & Orange)

Check IP as per IP Plan or NOT and assign IP Proper

Check E1 Configuration

Y Y

By using auto discovery method now you can able to manage Route NE

Add route add command in Server as per slide no 10

You can get Reply from IDU NMS IP but not from Radio IP

N E1 Configuration Problem: Check with E1 Provision Team as per Standard or Not

Replace Cables

NN Y

Y

Y Y

Y

2/4


Page 13

2.Root NE and Server Location – BG20 , XDM 100 any other MUX:

1.Server Location : Connect Server to BG20 Port(Ethernet Port) by using Cross or Straight Cable (Server IP :10.10.10.1 mask 255.255.255.0.2.Root NE Location :Connect Laptop to BG 20 Port(Ethernet Port) by using cross or Straight cable and assign IP to your laptop with in same subnet of Server IP (Laptop and Server IP with in same subnet)( Laptop IP : 10.10.10.2 mask 255.255.255.0)

3.Goto START>>RUN>>CMD>>Now your are in Command window (Below window Display )

4.Ping from Root NE Location to Server IP (Ex. Ping 10.10.10.1) if your are getting Reply from Server IP Your E1 Connectivity Between Root NE to Server Ready VISE VERSA Check from Server to LAPTOP.

3/4


Page 14

5. Login to IDU Assign IP address as per IP Plan and Remove cable from your laptop connect to IDU NMS Port.

6. Ping from NMS PC to IDU IP you can get reply from IDU NMS IP after that add route Command as per Slide no 10.

7. Some times when you connected Laptop in Both ends you can get Reply from One end to another end . But when u connected to IDU your are not getting Reply. In this case follow below Flow Chart and check Following Configuration.

Check IDU NMS IP and Server IP with in same subnet or NOT

Check Both ends Cable connectivity

Check BG 20 or XDM 100 Ethernet port LED Blinking or NOT(Green & RED)

Check IP as per IP Plan or NOT and assign IP Proper

Check E1 Configuration settings (Auto Negotiation / Auto MDI/MDIX-10base-T,Full duplex)—Confirm From Customer Provisioning Team

Y Y

By using auto discovery method now you can able to manage Route NE

Add route add command in Server as per slide no 10

You can get Reply from IDU NMS IP but not from Radio IP

N E1 Configuration Problem: Check with E1 Provision Team as per Standard or Not

Replace Cables

NN

Y

Y Y

Y

4/4


Page 15

How to assign IP in NEC IDU Manual

Login By Using PNMT Software >>Click on CTRL >>CTRL window open as per below

CTRL WINDOW


Page 16

CTRL Window Click on EQUIPMENT NETWORK SETTING>>Equipment Network Setting Window open as per below

Equipment Network Setting window


Page 17

ROOT NE IP Configuration

Go to Equipment Network Setting >>General>>Select CTRL Type ROOT NE

Root NE

Parameters


Page 18

1.Go to Equipment Network Setting >>General>>Select CTRL Type ROOT NE2.Go to Radio/EM2 Assign IP and Subnet mask As per IP Plan


Page 19

1.Go to Equipment Network Setting >>General>>Select CTRL Type ROOT NE.2.Go to Radio/EM2 Assign IP and Subnet mask As per IP Plan.3. Go to PNMS(EM1) Assign IP and subnet as per plan (PNMS IP and Server IP should be in same subnet).


Page 20

1.Go to Equipment Network Setting >>General>>Select CTRL Type ROOT NE.2.Go to Radio/EM2 Assign IP and Subnet mask As per IP Plan.3.Go to PNMS(EM1) Assign IP and subnet as per plan (PNMS IP and Server IP should be in same subnet).4.Go to Routing Assign Routing IP (Server IP) and if you have Branch add Routing table according to Branch IP.

If you have Branch .Add routing

table by using Add Button.

Route NE Configuration Completed


Page 21

Branch NE IP Configuration

1.Go to Equipment Network Setting >>General>>Select CTRL Type Branch NE:

Branch NE

Parameters


Page 22

1.Go to Equipment Network Setting >>General>>Select CTRL Type Branch NE2.Go to Radio Assign IP and Subnet mask As per IP Plan


Page 23

1.Go to Equipment Network Setting >>General>>Select CTRL Type Branch NE2.Go to Radio Assign IP and Subnet mask As per IP Plan.3.Go to EM2/EM1 assign IP as per branch NE Details


Page 24

1.Go to Equipment Network Setting >>General>>Select CTRL Type Branch NE2.Go to Radio Assign IP and Subnet mask As per IP Plan.3.Go to EM2/EM1 assign IP as per branch NE Details.4.Go to Routing assign Routing IP ( Route NE IP).

Branch NE Configuration Completed


Page 25

Normal NE IP Configuration

1.Go to Equipment Network Setting >>General>>Select CTRL Type Normal NE


Page 26

1.Go to Equipment Network Setting >>General>>Select CTRL Type Normal NE.2.Go to Radio/EM1/EM2 assign IP as per IP Plan.


Page 27

1.Go to Equipment Network Setting >>General>>Select CTRL Type Normal NE.2.Go to Radio/EM1/EM2 assign IP as per IP Plan.3.Go to Routing assign Routing IP ( should be Root NE IP or Branch NE IP).

Normal NE Configuration Completed


Page 28

Documents

NMS Connectivity Checking