Current Location:Home > System Equipment Forum > Transmission products
Subject initiator:JMutie       Replies:5       Published on:2012-08-10
Legends: ZTE engineer:Administrator
Subject:  configuring ip management of s385 and s200 mux
Common member
JMutie

Common member
Score::31
Registered on:2010-08-06
configuring ip management of s385 and s200 mux (Published on:8/10/2012 5:26:27 PM)

hello, I use zte equipment in Kenya. I want to configure s200 mux and s385 mux for management via a server at HQ. The equipment is connected toeach other and zte 8908/zte8905 routing switch. how is the ip planning supposed to be.is it same subnet? when you connect the s200 t0 s385 mux via optical fiber then to the routing  switch are the 2 equipment supposed to be given  IP in the same subnet. how does the equipment handle data destined for management? does it have an integrated Ethernet switch or hub?


Thank you





Common member
Zamri88

Common member
Score::2
Registered on:2016-11-16
Reply:configuring ip management of s385 and s200 mux (Published on:11/16/2016 12:38:00 AM)




ZTE engineer
Alexander Medina

ZTE engineer
Score::51
Registered on:2011-07-26
Reply:configuring ip management of s385 and s200 mux (Published on:9/5/2012 11:36:03 AM)

My god...

 

Well first the all MSTP products of ZTE can use OSPF protocol to route the monitoring management data to and from EMS. In doing so Agent (the software running in the NCP board, you can say this is the brain of the NE) assigns IP addresses to some of the opticals boards of the NE in order for OSPF protocol to be able to work propperly (please refer to some documents to learn about OSPF in ZTE equipments, you can find them by looking for ECC documents) so additionaly of the IP address you assign to the NCP, ergo the NE, also the NE will use IP addresses the will be in the same IP segment of the NCP address, in other words, if you assign contiguos IP addresses to different NEs their optical boards IP addresses might confilct with each other, so you can use the following formula for the IP address:

 

Area ID.NE number.NE number:18

Example: first 192.1.1.18, next NE 192.1.2.18, 192.1.3.18 and so on but never repeat the third octect of the IP address in any NE

 

For the routers I am afraid I cannot help you, you can configure them as you please but you need to make sure the IPs addresses of MSTP and datacomm equipments NEVER repeat or else you will have problems, you also need to make sure the access NEs monitoring packets (the data of QX port) can get to the server without problems, for this you can use whatever protocol or scheme you want as long as the EMS server and the access NEs can communicate to each other. SORRY FOR NOT HELP YOU IN THIS PART OF YOUR PROBLEM

 

Also when the Access NEs and the EMS server are on different networks (physically) you need to make static routes to the EMS server and also to the NEs, to the server you can run the command route add of windows (if it is solaris you need to get help from people that know how to do this because I don´t) and to the NEs you can go to the menu Device Management > SDH Management > Static Route Config to configure the static route to the server being the target IP the IP address of the server and the gateway the IP address of the router or switch directly connected to the QX of the NE

If this words do not help you at all, you can request for help formally to our office in Venezuela or maybe the chinese at HQ (the chinese of your country should supply you with the propper documentation)

 

My skype is amedin4 but I will not be in the office this week I will be on site.

 

And again please forgive me if with this you cannot solve your problems if it was on me I personally would go there and help you, but you can look for documentation on ECC and Gateway configuration on the support page, the DMS or the gold book, if you don´t know these things please contact you chinese staff they should know them.

 

Regards

 

 





Common member
Jackson Mutie

Common member
Score::31
Registered on:2010-08-06
Reply:configuring ip management of s385 and s200 mux (Published on:8/31/2012 10:40:26 PM)

Hello Medina,

          Thank you very much  for the information. The NEs are managed through a data communication network where the s385 at the regions(other cities) act as gateway NEs and connect to ip network via Qx port to FE port of zte 8908 routing switch. The EMS server is at HQ on a different vlan reached through the corporate LAN. EMS server ip is 10.35.45.14/24. The transmission between NEs is fiber and microwave.


NE ips 

MUX Model IP ADDRESS
S385   192.1.1.18
S385   192.1.3.18
S385   192.1.2.18
S385   192.1.30.18
S385   192.1.4.18
S385   192.1.5.18
S385   192.1.6.18
S200 1 192.1.10.18
S200 1 192.1.104.18
S200 1 192.1.103.18
S200 1 192.1.102.18
S200 1 192.1.101.18
S200 1 192.1.105.18
S200 1 192.1.106.18
S200 2 192.1.107.18
S200 1 192.1.108.18
S200 1 192.1.109.18
S200 1 192.1.110.18
S200 2 192.1.111.18
S200 1 192.1.112.18
S200 2 192.1.113.18
S200 2 192.1.114.18
S200 2 192.1.115.18
S200 1 192.1.116.18
S200 1 192.1.117.18
S200 1 192.1.4.10
S200 1 192.1.6.10
S200 2 192.2.2.18
 

can the NEs work if the ip is configured to be on the same subnet? because the ones that are working are on different subnets,when I try to make them same subnet they are not reachable. Question. In one of the s385 mux gateway NEs I can see that it is advertising the s200 in ospf as though the  s385 NEs and s200 NEs are exchanging routes with zte 8905 switch dynamically through ospf.how is that possible.can the s385 participate in ospf routing protocol to advertise the networks(s200 NEs) that are directly being managed through it?


I was not able to upload the topology the web page is saying that the path is fakepath although I am pointing to a document on my desktop


Kindly tell me how I can plan and configure the NEs Management to work both at the s385 ,s200 and zte routers and EMS server which has a single ip as default gateway 


Kind Regards

     






Download s385 and s200 management topolgy.png
ZTE engineer
Alexander Medina

ZTE engineer
Score::51
Registered on:2011-07-26
Reply:configuring ip management of s385 and s200 mux (Published on:8/28/2012 4:47:24 AM)
Also you ask "how does the equipment handle data destined for management? does it have an integrated Ethernet switch or hub?" remember that the SDH NEs use the ECC over DCC scheme to realize the inband (this means that the NEs transmit the monitoring thrugh the fiber when they are non backbone) monitoring management, this is automatically done by the NE (if you make the IP plan right) the out of band monitoring is done through the Qx port using TCP/IP protocol stack.



ZTE engineer
Alexander Medina

ZTE engineer
Score::51
Registered on:2011-07-26
Reply:configuring ip management of s385 and s200 mux (Published on:8/27/2012 11:49:27 PM)

Hello my friend!

 

Ok you need to specify how the networking will be? for example: are going to be both NEs Gateway for the network? is going to be the S200 a GW NE?() I really don´t recommend you that) What is the management software U31 or E300?

In either case different configurations will apply, but I would recommend you to let the S385 be the GW NE(access NE) and the S200 to be non GW NE. connect them both by fiber and let the S385 be the access NE.

You also need to tell us if the customer is giving you directions about the IP plan, as usually it is, if not answer the questions above and send a topology diagram and we can help you.

 

Regards 






Total: 5 Records Page: 1 /1 First Prev Next Last Go to
 
Subject:  configuring ip management of s385 and s200 mux
 Attachment  
 Reply Content