cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

21
Views
0
Helpful
1
Replies
Highlighted
Cisco Employee

netsim kills ncs daemon

Hi team

I reecently upgraded my NCS 3.4 -> 3.4.1 -> 3.4.2 and have noticed that the NCS daemon will die as soon as I bring up netsim. Without netsim up, NCS tends to stay up.

Has anyone else experienced this ?

netsim kills.png

Thanks,

Nick Khemani

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: netsim kills ncs daemon

It's a bit of bad naming here, it's not the NCS daemon that dies.
This you can easily verify by calling,

$ ncs --status

And it'll say that all is fine.

The misleading nomenclature here is the word "daemon" and it refers to a data provider, in your case, AluSrDp and it is apparently misbehaving so bad, so that it brings down the entire JVM with possibly additional packages too.
The NCS daemon itself isn't JVM, it's the Erlang VM

Check your java logs, and also devel.log which may contain clues.

Background:

The name daemon here goes all the way back to when we only had ConfD and no NCS. The API, the data provider API is still the same. Same both for ConfD and NCS. At the time, a data provider was a C-program, running on a router, providing stats callbacks.

Usually an internal router "daemon"
Probably named so in 2006 or something.

/klacke

View solution in original post

1 REPLY 1
Cisco Employee

Re: netsim kills ncs daemon

It's a bit of bad naming here, it's not the NCS daemon that dies.
This you can easily verify by calling,

$ ncs --status

And it'll say that all is fine.

The misleading nomenclature here is the word "daemon" and it refers to a data provider, in your case, AluSrDp and it is apparently misbehaving so bad, so that it brings down the entire JVM with possibly additional packages too.
The NCS daemon itself isn't JVM, it's the Erlang VM

Check your java logs, and also devel.log which may contain clues.

Background:

The name daemon here goes all the way back to when we only had ConfD and no NCS. The API, the data provider API is still the same. Same both for ConfD and NCS. At the time, a data provider was a C-program, running on a router, providing stats callbacks.

Usually an internal router "daemon"
Probably named so in 2006 or something.

/klacke

View solution in original post

Content for Community-Ad
FusionCharts will render here