Management

Hi all good folks!

This might be a bit of a confusing post, but I'll try to break it down so that it will be understandable. 

So the background is that I've been having a look at the new major release for Junos Space, version 24.1. When I look at the release notes, I see this sentence:

What does this actually mean? I thought that OpenNMS was the building block of Junos Space NMP and that whenever I register a new device in Space NMP or Security Director, that this was registered in OpenNMS. What will be the consequences of upgrading to 24.1 and loosing OpenNMS? Could someone please enlighten me?

The second comment/question is related to rumours that the OnPrem version of Junos Security Director will be "rebuilt" to be more a standalone application like the sky version is right now. Is the decoupling of OpenNMS in Space NMP a part of this transition? 

Hi,

As it mentioned in RN, Network Monitoring (OpenNMS) is decoupled starting 24.1 Junos Space so there is no SNMP monitoring or event / trap can be seen for managed devices in Space but user can deploy their own OpenNMS server and integrate it to Space, steps are mentioned in the guide.

Hi all good folks!

This might be a bit of a confusing post, but I'll try to break it down so that it will be understandable. 

So the background is that I've been having a look at the new major release for Junos Space, version 24.1. When I look at the release notes, I see this sentence:

What does this actually mean? I thought that OpenNMS was the building block of Junos Space NMP and that whenever I register a new device in Space NMP or Security Director, that this was registered in OpenNMS. What will be the consequences of upgrading to 24.1 and loosing OpenNMS? Could someone please enlighten me?

The second comment/question is related to rumours that the OnPrem version of Junos Security Director will be "rebuilt" to be more a standalone application like the sky version is right now. Is the decoupling of OpenNMS in Space NMP a part of this transition? 

Hi,

So means junos space version 24.1 and above cannot display the utilization for each interface of device that has been discovered? Also it will cannot display utilization for each line card device discovered? Previously all that feature do by OpenNMS in junos space. Can someone reconfirm again?

Thanks

Hi,

As it mentioned in RN, Network Monitoring (OpenNMS) is decoupled starting 24.1 Junos Space so there is no SNMP monitoring or event / trap can be seen for managed devices in Space but user can deploy their own OpenNMS server and integrate it to Space, steps are mentioned in the guide.

Hi all good folks!

This might be a bit of a confusing post, but I'll try to break it down so that it will be understandable. 

So the background is that I've been having a look at the new major release for Junos Space, version 24.1. When I look at the release notes, I see this sentence:

What does this actually mean? I thought that OpenNMS was the building block of Junos Space NMP and that whenever I register a new device in Space NMP or Security Director, that this was registered in OpenNMS. What will be the consequences of upgrading to 24.1 and loosing OpenNMS? Could someone please enlighten me?

The second comment/question is related to rumours that the OnPrem version of Junos Security Director will be "rebuilt" to be more a standalone application like the sky version is right now. Is the decoupling of OpenNMS in Space NMP a part of this transition? 

Hi guys. 

My conclusion is that if you want the "monitoring" part, you need to implement a separate OpenNMS server. So Space will kind of become a management tool only with 24.1. Probably all things like "CPU usage", "Memory usage", "Storage usage" etc. in Security Director will be gone if you don't implement a separate OpenNMS server. 

In our case this is not a problem since we already have another NMS, but a plus about OpenNMS is that this can be connected with Space. So performance data and traps will then be visible in Space. 

I will probably disable OpenNMS in my current Space implementation (running 23.x) to get a feel of the consequences prior to upgrading. 

Anyone disagree with my conclusion?

Hi,

So means junos space version 24.1 and above cannot display the utilization for each interface of device that has been discovered? Also it will cannot display utilization for each line card device discovered? Previously all that feature do by OpenNMS in junos space. Can someone reconfirm again?

Thanks

Hi,

As it mentioned in RN, Network Monitoring (OpenNMS) is decoupled starting 24.1 Junos Space so there is no SNMP monitoring or event / trap can be seen for managed devices in Space but user can deploy their own OpenNMS server and integrate it to Space, steps are mentioned in the guide.

Hi all good folks!

This might be a bit of a confusing post, but I'll try to break it down so that it will be understandable. 

So the background is that I've been having a look at the new major release for Junos Space, version 24.1. When I look at the release notes, I see this sentence:

What does this actually mean? I thought that OpenNMS was the building block of Junos Space NMP and that whenever I register a new device in Space NMP or Security Director, that this was registered in OpenNMS. What will be the consequences of upgrading to 24.1 and loosing OpenNMS? Could someone please enlighten me?

The second comment/question is related to rumours that the OnPrem version of Junos Security Director will be "rebuilt" to be more a standalone application like the sky version is right now. Is the decoupling of OpenNMS in Space NMP a part of this transition? 

Hi guys. 

My conclusion is that if you want the "monitoring" part, you need to implement a separate OpenNMS server. So Space will kind of become a management tool only with 24.1. Probably all things like "CPU usage", "Memory usage", "Storage usage" etc. in Security Director will be gone if you don't implement a separate OpenNMS server. 

In our case this is not a problem since we already have another NMS, but a plus about OpenNMS is that this can be connected with Space. So performance data and traps will then be visible in Space. 

I will probably disable OpenNMS in my current Space implementation (running 23.x) to get a feel of the consequences prior to upgrading. 

Anyone disagree with my conclusion?

Hi,

So means junos space version 24.1 and above cannot display the utilization for each interface of device that has been discovered? Also it will cannot display utilization for each line card device discovered? Previously all that feature do by OpenNMS in junos space. Can someone reconfirm again?

Thanks

Hi,

As it mentioned in RN, Network Monitoring (OpenNMS) is decoupled starting 24.1 Junos Space so there is no SNMP monitoring or event / trap can be seen for managed devices in Space but user can deploy their own OpenNMS server and integrate it to Space, steps are mentioned in the guide.

Hi all good folks!

This might be a bit of a confusing post, but I'll try to break it down so that it will be understandable. 

So the background is that I've been having a look at the new major release for Junos Space, version 24.1. When I look at the release notes, I see this sentence:

What does this actually mean? I thought that OpenNMS was the building block of Junos Space NMP and that whenever I register a new device in Space NMP or Security Director, that this was registered in OpenNMS. What will be the consequences of upgrading to 24.1 and loosing OpenNMS? Could someone please enlighten me?

The second comment/question is related to rumours that the OnPrem version of Junos Security Director will be "rebuilt" to be more a standalone application like the sky version is right now. Is the decoupling of OpenNMS in Space NMP a part of this transition?