Beruflich Dokumente
Kultur Dokumente
NECI-Technical Center
Page 2
256 28
128 27
64 26
32 16 8 4 2 1 25 24 23 22 22 20
Subnet Subnet available IP No.of Subnets
00000000 : 00000000 : 0000000 : 00000000 8 : 8 : 8 : 8 00000000 : 00000000 : 00000000 : 0/0000000 00000000 : 00000000 : 00000000 : 00/000000 00000000 : 00000000 : 00000000 : 000/00000 00000000 : 00000000 : 00000000 : 0000/0000 00000000 : 00000000 : 00000000 : 00000/000 00000000 : 00000000 : 00000000 : 000000/00 00000000 : 00000000 : 00000000 : 0000000/0
X.X.X.000 /24 X.X.X.128 /25 X.X.X.192 /26 X.X.X.224 /27 X.X.X.240 /28 X.X.X.248 /29 X.X.X.252 /30 X.X.X.254 /31
-256*1 -128 *2 -64 *4 -32 *8 -16 *16 -08 *32 -04 *64 -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
NEC Corporation 2005 NEC Internal Use Only
Ex : 192.168.1.0/25 Network address 192.168.1.0 Valid Hosts : 192.168.1.1 126 Broadcast address : 192.168.1.127 Mask : 255.255.255.128
EX: 192.168.1.128.0/25 N/W A : 192.168.1.128 Valid Hosts : 192.168.1.129-254 Broad Cast Address : 192.168.1.255 Mask : 255.255.255.128
Page 3
Ex : 192.168.1.0/26 Network address 192.168.1.0 Valid Hosts : 192.168.1.1 62 Broadcast address : 192.168.1.63 Mask : 255.255.255.192
EX: 192.168.1.128.0/26 N/W A : 192.168.1.64 Valid Hosts : 192.168.1.65 -126 Broad Cast Address : 192.168.1.127 Mask : 255.255.255.192
Ex : 192.168.1.0/26 Network address 192.168.1.128 Valid Hosts : 192.168.1.129 -190 Broadcast address : 192.168.1.191 Mask : 255.255.255.192
EX: 192.168.1.128.0/26 N/W A : 192.168.1.192 Valid Hosts : 192.168.1.193 -254 Broad Cast Address : 192.168.1.255 Mask : 255.255.255.192
Page 4
Class D address are used for Multicasting Class CLASS CALSS CLASS CLASS CLASS A address are reserved for testing & some mysterious future use. A 0 to 127 B 128 to 191 C 192 to 223 D 224 to 239 E 240 to 255
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
255.0.0.0
16777216-2=16,777,214
255.192.0.0
255.240.0.0 255.255.0.0 255.255.128.0 255.255.240.0
10
12 16 17 20
4
16 256 512 4096 131072 1048576
4194304-2 = 4,194,302
1048576-2 = 10,485,74 65536-2 = 65534 32768-2=32766 4096-2 = 4094 128-2=126 16-2=14
255.255.255.255.128 25 255.255.255.255.240 28
255.255.255.255.252 30
NEC Corporation 2005
4194304
NEC Internal Use Only
4-2 = 2
Page 6
255.255.0.0
16
65536-2=65534
111111111.11111111.00000000.00000000
255.255.192.0
18
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
255.255.255.0 255.255.255.128
24 25
0 2
256-2=254 128-2=126
11111111.11111111.11111111.00000000
11111111.11111111.11111111.10000000
255.255.255.192
255.255.255.224 255.255.255.240 255.255.255.248 255.255.255.252 255.255.255.254
26
27 28 29 30 31
4
8 16 32 64 128
64-2=62
32-2=30 16-2=14 8-2=6 4-2=2 2-2=0
11111111.11111111.11111111.11000000
11111111.11111111.11111111.11100000
11111111.11111111.11111111.11110000
11111111.11111111.11111111.11111000
11111111.11111111.11111111.11111100
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 PDH/SDH PDH/SDH SDH SDH 255.255.255.252 255.255.255.248 255.255.255.240 255.255.255.224 255.255.255.192 4 - 2 8 - 6 16 - 14 32 - 30 64 - 62
Page 9
NMS PC
Page 10
PNMS 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
Example Network
Root NE NEC IDU
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
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
NEC Corporation 2005 NEC Internal Use Only
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.
2/4
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.
Y
Check E1 Configuration
N
Check IP as per IP Plan or NOT and assign IP Proper
N
Replace Cables
N
E1 Configuration Problem: Check with E1 Provision Team as per Standard or Not
Y Y
By using auto discovery method now you can able to manage Route NE
You can get Reply from IDU NMS IP but not from Radio IP
Page 13
2.Root NE and Server Location BG20 , XDM 100 any other MUX:
3/4
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.
4/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 BG 20 or XDM 100 Ethernet port LED Blinking or NOT(Green & RED)
N
Check IP as per IP Plan or NOT and assign IP Proper
N
Replace Cables
N
E1 Configuration Problem: Check with E1 Provision Team as per Standard or Not
Check E1 Configuration settings (Auto Negotiation / Auto MDI/MDIX10base-T,Full duplex)Confirm From Customer Provisioning Team
By using auto discovery method now you can able to manage Route NE
You can get Reply from IDU NMS IP but not from Radio IP
Page 15
CTRL WINDOW
Page 16
CTRL Window Click on EQUIPMENT NETWORK SETTING>>Equipment Network Setting Window open as per below
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 NE 2.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.
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 NE 2.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 NE 2.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
to to to to
Equipment Network Setting >>General>>Select CTRL Type Branch NE Radio Assign IP and Subnet mask As per IP Plan. EM2/EM1 assign IP as per branch NE Details. Routing assign Routing IP ( Route NE IP).
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).
Page 28