12-12-2012 06:27 AM
Storm is just Q1's SIEM with a Juniper sticker on it.
So I'm assuming you're still running NSM ? I noticed there is a lot I cant do with it when it comes to the managing the hardware.
12-12-2012 10:34 AM
Yes, I am forced to use NSM for the time being and I hate it. Most customers I work with are smaller shops and they need a fully integrated solutions (e.g. containing logging and allowing management of legacy devices).
08-28-2013 05:49 AM
I am. It is definitely not the most stable product. We use to be an all Juniper shop. Now we are moving to Cisco switching and Palo Alto firewalls and Splunk for the SIEM. I still like Juniper's SSL VPN/Junos Pulse though, even though you really can't manage it effectively through NSM.
08-29-2013 10:26 AM - edited 08-29-2013 10:29 AM
This might be old news to someone but for me it was new info. Anyways I've heard that there will never be ScreenOS support on Space after all so this means some of us need to run NSM a little longer if we need a central management.. :-)
08-29-2013 10:12 PM
Space. That was confirmed to me by Juniper. ETA end of 2013 or beginning of
08-30-2013 01:21 AM
Well, I've got my information from Juniper representive aswell and this was very recent. I guess we'll see then who from Juniper knows best..
03-03-2014 11:16 AM
I know this thread is quite old, but we did invest significant Engineering effort to stabilize and improve NSM since the last comments on this thread.
In fact, we've had quite positive feedback to the improvements in NSM2012.*
I don't want to exagerate- NSM is an old software platform with an out of date heavy client architecture.
2012 is better than previous versions, but I would still strongly recommend migrating to Space & Security Director.
03-03-2014 11:42 AM
tends to forget these days is the enormously large install base of "legacy"
ScreenOS devices (that are still being sold with recently updated EOL dates
2018). There is no support in Space for ScreenOS. Even though there was
once through a plugin. Also, Space has no built in logging. Again, Juniper
forgetting about it's smaller to medium sized customers who can not or
don't want to invest in a separate logging solution (conviniently sold by
Juniper). Juniper should just get rid of their firewall business
altogether. They failed. Anyone looking for a good firewall? Check out Palo
03-03-2014 12:02 PM
This is still my favorite thread.
I have both Juniper and Palo Alto. Now, I am still managing My SRXs with NSM because of the very reason you stated, no logging. That being said, if your gripe is bad management tools, Palo Alto is worse, much worse. Their Panorama Central Console product is a joke and their GUI is a disaster. Every feature on the PA besides dynamic threat detection and basic firewalling is junk. (URL Filtering, Reporting, DLP, etc, etc)
Next time around Im going back to Checkpoint for my 2nd layer firewall. I still prefer Juniper as my primary. They are fast, cheap and reliable, even if there is no good management option with logging. And I mean, I am totally with you on the lack of logging. It should be there.
03-03-2014 01:28 PM
even today, years (!) after opening this thread: NSM is a piece of junk and
a shame for Juniper.
04-22-2014 05:21 AM
Just a heads up and many of you already know this but..
Junos Space Platform 13.3r1.8 in concert with Security Directory 13.3rx.x (yet to be named and to be released in lat May early June), will have limited logging added back in (again).
So, this could be the death of NSM ??? Or at least the death of the need for NSM ? I am preparing and am optimistic.
There will be funeral services for NSM followed by an after party at McSorelys in NYC.
04-23-2014 07:57 PM
04-24-2014 12:20 AM
are you sure about the release of Security Directore 13.3 (late May early June)?
The latest statement i did receive from our SE (2 weeks ago) was that it should arrive at the end of april / may.
Thank you in advance
05-09-2014 10:39 AM
It's out now. I loaded the newest Network Director, Security Director, Log Director, and the Log VM. I think I did it all right. I cant figure out how to get the devices to start logging though. Do I just set them to syslog to the IP of the Log VM ? The doc isnt really clear on that point. Or maybe Im just dense.
05-10-2014 04:39 AM
indeed you'll have to set syslog destination to the indicated Log VM.
With the now latest release 13.3 of security director you can do this from:
Device-Management->Device -> Edit Device condiguration (now you can set it in a way more easier way then in previous version routing/interface/zone/syslog configuration)
Hope this helps you.
07-25-2014 06:11 AM
I'm officially done with NSM. I cannot do another firewall import losing all my groupings and policy descriptions without losing my mind. Also I believe its causing my firewalls to run at 100% CPU.
[ runs screaming with flaming sword in hand into the land of Junos Space and log director ]