[INUG-Users] OSS-RC Probe not receiving any Notification

Wed Apr 1 12:58:06 EDT 2009

Hi All/Kristian,

Thanks for the information. I even asked OSS-RC team to debug from their side, but no response.

I even tested with the IOR generated by DumpNameService [NMSNAConsumer], still it’s the same problem. During Synchronization the NetcoolIRPManager is able to receive the alarms [Below logs]. 

03/31/09 12:10:34: Debug: POLL: Primary server poll time not yet reached.
03/31/09 12:10:34: Information: NetcoolIRPManager: processed 72533 events
03/31/09 12:10:34: Debug: NetcoolIRPManager: Event 34 of 100
03/31/09 12:10:34: Debug: AdditionalText length is 98

- But after the below log message END SYNCHRONIZATION nothing works for me.

03/31/09 12:10:51: Information: Probewatch: END SYNCHRONIZATION
03/31/09 12:10:51: Debug: OSS_RC: Opening Telnet Commandline Interface
03/31/09 12:10:51: Debug: Flushing events to object server
03/31/09 12:10:51: Debug: POLL: Primary server poll time not yet reached.
03/31/09 12:10:51: Debug: Flushing events to object server
03/31/09 12:10:51: Debug: [Command Port] Starting CLI Server Thread
03/31/09 12:10:51: Debug: CommandPortLimit->    10
03/31/09 12:10:51: Debug: OSS_RC: Will loop until signal or error
03/31/09 12:10:51: Debug: CommandPort-> 6970

Can you provide some more information or show me a pointer to move forward.

Thanks & Regards,
Shalu Khesav..

-----Original Message-----
From: users-bounces at netcoolusers.org [mailto:users-bounces at netcoolusers.org] On Behalf Of Kristian Appiah Endresen
Sent: Wednesday, April 01, 2009 6:28 PM
To: users at netcoolusers.org
Subject: [INUG-Users] OSS-RC Probe not receiving any Notification

FWIW,

We've had some problems with our RadioCommander probe, and its
normally been caused by either connectivity problems (RC is at a
remote site, which was connectied via a dodgy link for a while) or IRP
files that needed updating.  _If_ you're using IRP files, try to
regenerate them using DumpNameService, even if your guys think the
current NotificationIRP is fine (not that I know something they dont,
but people make mistakes).

At one point we had a problem that was not caused by either of the
above.  It would only send through alarms (seemingly unrelated) in
batches - it would keep saying "Waiting for connections" for 10-40
minutes and then a whole bunch would come in.  We never determined the
cause - it lasted for a few days only, and presumed it was some
problem with the remote CORBA interface.

Kristian

> Date: Wed, 1 Apr 2009 17:07:08 +0200
> From: "Shalu Keshav" <Shalu.Keshav at vodafone.com>
> Subject: [INUG-Users] OSS-RC Probe not receiving any Notification
>        alarms.
> To: <users at netcoolusers.org>
> Message-ID:
>        <C6BE1659332EF443AF5169F5D1C4C7BC045D861B at SVLE3KA1.clickgsm.Misrfone.com>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
>
>
> We had an issue with OSS-RC probe. The probe is able to connect to
> OSS-RC and get the subscription-ID as well as it is able to resynch the
> alarms. Soon after the synchronization is over I am seeing the below
> logs and unable to receive any ongoing alarms from the OSS-RC.
>
>
>
> 04/01/09 16:30:50: Debug: NetcoolIRPManager: 180 Seconds since last
> event batch was received
>
> 04/01/09 16:30:59: Debug: NetcoolIRPManager: 190 Seconds since last
> event batch was received
>
> 04/01/09 16:30:59: Debug: [Command Port] Checking 0 connections for
> timeouts
>
> 04/01/09 16:30:59: Debug: [Command Port] Waiting for connections
>
> 04/01/09 16:31:07: Debug: Checking subcription status ....
>
> 04/01/09 16:31:07: Debug: subscription id :1f1 received
>
> 04/01/09 16:31:07: Debug: subscription id :1z1 received
>
> 04/01/09 16:31:07: Debug: subcription status .... O.K
>
>
>
> Some times after synchronization, I am seeing the Attach method failed
> with below log:
>
>
>
> 03/13/09 23:21:22: Debug: GetFMErrorMessages->  false
>
> 03/13/09 23:21:22: Information:  Attaching with notification category
> 1f1
>
> 03/13/09 23:21:22: Debug: [Command Port] Checking 0 connections for
> timeouts
>
> 03/13/09 23:21:22: Debug: [Command Port] Waiting for connections
>
> 03/13/09 23:21:32: Debug: [Command Port] Checking 0 connections for
> timeouts
>
> 03/13/09 23:21:32: Debug: [Command Port] Waiting for connections
>
> 03/13/09 23:21:42: Debug: [Command Port] Checking 0 connections for
> timeouts
>
> 03/13/09 23:21:42: Debug: [Command Port] Waiting for connections
>
> 03/13/09 23:21:52: Warning: connect failed : exception
> NotificationIRPSystem.Attach {
>
> java.lang.String reason="From InterNA: exception
> com.ericsson.nms.cif.na.v3_0.NotificationIRPSystem.Attach {
>
> java.lang.String reason="org.omg.CORBA.TIMEOUT: Read timed out  vmcid:
> OMG  minor code: 0 completed: Maybe"
>
> }"
>
> }
>
> 03/13/09 23:21:52: Information: Probewatch: Unable to get events
>
> 03/13/09 23:21:52: Error: Unable to get events:
> IDL:3gppsa5.org/NotificationIRPSystem/Attach:1.0
>
> 03/13/09 23:21:52: Debug: Retry->       true
>
>
>
> Looks like the first phase of probe is working fine like synchronization
> & Subscription status, the second phase Notification alarms should be
> the problem. I also verified with OSS-RC team as per their configuration
> the NotificationIRP is working fine which is tested by testman
> application from their end.
>
>
>
> It would be great if some one knows a resolution for this and help me
> out.
>
>
>
> Thanks in Advance..
>
>
>
> Regards,
>
> Shalu Khesav..
>

_______________________________________________
Sent by the netcoolusers.org "users" mailing list
Post: users at netcoolusers.org
Unsubscribe: users-unsubscribe at netcoolusers.org
Search: http://netcoolusers.org/Search

*************************************************************************************************************************

The content of this document is classified as Vodafone Egypt S.A.E. Confidential and Proprietary Information.

The recipient hereby is committed to hold in strict confidence the contents of this (e-mail, document, information) and not to disclose to any third party without the prior written consent of Vodafone Egypt S.A.E. Recipient will be held liable for any unauthorized disclosure.

If you have received this message in error, please notify the sender by return e-mail and delete the message in its entirety, including any attachments.

*************************************************************************************************************************