4760 Release 4.2 synchronization problem with OXE Release 10

4760 Release 4.2 synchronization problem with OXE Release 10

Postby ybelal » Wed Aug 01, 2012 12:19 am

Hi
We are using 4760 r-4.2 and OXE 7.1( for 10 nodes), recently we have upgraded one of the node to OXE r-10 now, 4760 r-4.2 failing to synchronize that node with rel-10. It shows

[8/1/2012 12:04:18 AM] Scheduler: The job is started.
[8/1/2012 12:04:25 AM]
New Status : Establishing IP/X25 connection
[8/1/2012 12:04:35 AM]
New Status : IP/X25 connection established
[8/1/2012 12:04:35 AM]
New Status : MIB Synchronization
[8/1/2012 12:04:35 AM] Target: Lengthy operation protected by timer 02:15:00
[8/1/2012 2:19:46 AM]
Error : Successful Operation - No Error
[8/1/2012 2:19:46 AM] Target: Some PCX systems have not been fully loaded!

[8/1/2012 2:19:46 AM] Scheduler: Job failed.

help needed. is it because of that timer and if it is then where and how can i change this timer? if not timer then help me with expart advose,please.


Thanks.
ybelal
Member
 
Posts: 107
Joined: Sun Dec 27, 2009 5:51 am

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby alex » Wed Aug 01, 2012 11:32 pm

From the official point of view - R4.2 is not compatible with R10 of OXE.
The timer (02:15:00) should be hidden somewhere deep inside NMC's LDAP structure. It wouldn't be a good idea to increase it as it protects NMC from running too "lengthy operations" and blocking other jobs.
You'd better check why MIB Synchronization with this node takes so much time.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
User avatar
alex
Senior Member
 
Posts: 1080
Joined: Tue Jul 06, 2004 4:27 am
Location: Russia

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby ybelal » Thu Aug 02, 2012 1:02 am

Thank you,

Is there any command to run in OXE after upgrading to make it enable or make the object to be loaded/synchronised with 4760?

Thanks.
ybelal
Member
 
Posts: 107
Joined: Sun Dec 27, 2009 5:51 am

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby alex » Thu Aug 02, 2012 4:22 am

ybelal wrote:Is there any command to run in OXE after upgrading to make it enable or make the object to be loaded/synchronised with 4760?

No such command exist, because it is not object - these are MIB files.

4760 needs MIB files for that version (R10) in any case - whether you checked "local save" or not. OmniVista loads them every time you start
This MIB Synchronization also runs on Daily job.Configuration(from PBX or from local disk).
Can you configure this R10 node?

You could try to load them locally (as you use IP/X.25 tunnel, BTW there is no IP connection to this node?), e.g. from the demo/lab CPU with the same version and see how it is working.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
User avatar
alex
Senior Member
 
Posts: 1080
Joined: Tue Jul 06, 2004 4:27 am
Location: Russia

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby ybelal » Thu Aug 02, 2012 1:09 pm

I have installed /upgraded 4760-r4.2 to 4760 -r5.2 and i could synchronize all other nodes with different release( 7.1,8,9) but still unable to synchronize this node with r-10. it fail showing
Error : Successful Operation - No Error
Target: Some PCX systems have not been fully loaded!
FAIL....

That node do not have direct IP connection, it's connected to other 2 nodes by IP/X.25 and those nodes are connected to the same network with 4760.

where in oxe i can find the MIB files and where to copy them in 4760,please?
ybelal
Member
 
Posts: 107
Joined: Sun Dec 27, 2009 5:51 am

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby alex » Fri Aug 03, 2012 1:55 am

ybelal wrote:I have installed /upgraded 4760-r4.2 to 4760 -r5.2 and i could synchronize all other nodes with different release( 7.1,8,9) but still unable to synchronize this node with r-10. it fail showing
Error : Successful Operation - No Error
Target: Some PCX systems have not been fully loaded!
FAIL....

That node do not have direct IP connection, it's connected to other 2 nodes by IP/X.25 and those nodes are connected to the same network with 4760.

There are some problems with IP/X.25 tunnel. Can you ping this node or telnet this node from NMC or use configuration app with this node?
ybelal wrote:where in oxe i can find the MIB files and where to copy them in 4760,please?
Install demo CPU with the exact R10 version , connect it to a LAN where NMC is and configure it in NMC and make synchronization. You'll get MIBs imported to NMC.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
User avatar
alex
Senior Member
 
Posts: 1080
Joined: Tue Jul 06, 2004 4:27 am
Location: Russia

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby ybelal » Fri Aug 03, 2012 2:20 am

""
There are some problems with IP/X.25 tunnel. Can you ping this node or telnet this node from NMC or use configuration app with this node? ""

Yes , by managing the route in 4760 server, i can ping the node from 4760.
ybelal
Member
 
Posts: 107
Joined: Sun Dec 27, 2009 5:51 am

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby alex » Fri Aug 03, 2012 2:47 am

ybelal wrote:Yes , by managing the route in 4760 server, i can ping the node from 4760.

There is no need to manage a route in OS.
Make a telnet connection from 4760 and from CLI try to get some files from the node with ftp.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
User avatar
alex
Senior Member
 
Posts: 1080
Joined: Tue Jul 06, 2004 4:27 am
Location: Russia

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby ybelal » Fri Aug 03, 2012 8:13 am

Node IP is 172.30.253.12, from 4760 server machine i can ping from CLI to the node but when i try telnet or ftp from cli (from the 4760 server)to node(172.30.253.12) then it say port is not open but when i do connect from 4760 by right click on that node and select connect to that node then it connect to mtcl !!

should i try ftp from 4760 server cli promt as mtcl user or as adfexc user(just asking even though it's not giving me option to enetr user name and password, refuse the connection)?
ybelal
Member
 
Posts: 107
Joined: Sun Dec 27, 2009 5:51 am

Re: 4760 Release 4.2 synchronization problem with OXE Releas

Postby alex » Fri Aug 03, 2012 9:53 am

It is kind of a dynamic routing in 4760 when connecting to IP/X.25 tunnel. When you are connected to the node over the tunnel from 4760 (e.g., using telnet from 4760) then the route to this node is established. That's why I wrote 1st you should establish a telnet connection from 4760 to this node then try to ftp this node from CLI or any FTP-client available on a server and try to get any file from the node. Try with "mtcl" account" 1st.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
User avatar
alex
Senior Member
 
Posts: 1080
Joined: Tue Jul 06, 2004 4:27 am
Location: Russia

Next

Return to 4760

Who is online

Users browsing this forum: No registered users and 1 guest

Creative Commons License
AlcatelUnleashed by AlcatelUnleashed is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Based on a work at www.AlcatelUnleashed.com.
AlcatelUnleashed is NOT affiliated with or endorsed by Alcatel-Lucent.
Access our mailing lists here.