Geek Speak

Orion Network Configuration Manager (NCM) - Sneak Peak

Usually when I'm working with companies on their network management strategy, while fault and performance management are top of mind, configuration management falls by the wayside. Nearly everyone that I've worked with wants to have easy to use, effective, and integrated configuration management - but for the most part this has historically been just too much trouble to make it feasible with everything else we have going on.

I'm proud to announce that this situation has now changed. Tomorrow we're going to officially announce the new Orion Network Configuration Manager (NCM). Orion NCM is a new and improved configuration management application that replaces our Cirrus Configuration Manager and offers tight integration with the Orion that everyone knows and loves - Orion Network Performance Monitor (NPM).

More information will be available over the next few days, but you can watch a sneak peak video here.

Flame on...
Josh

Published Aug 25 2008, 09:20 PM by Josh Stephens

Comments

 

Albany Mike said:

We just purchased Cirrus not even a month ago. Is this going to be some sort of upgrade feature, or is our Cirrus now 2nd rate to this product. It would be a huge shame if we missed out on this and it isnt offered to existing Cirrus customers as an upgrade.
August 26, 2008 10:59 AM
 

Josh Stephens said:

Mike,

Good news - this will be a FREE upgrade for you. All Cirrus customers with active maintenance will be entitled to the new Orion NCM.

Josh

August 26, 2008 11:16 AM
 

ddawson said:

Will Orion NPM and Orion v9 PM share the same database or will they still be two seperate databases?
September 3, 2008 10:36 PM
 

Josh Stephens said:

DDawson,

Orion NPM and NCM (was Cirrus) don't share a common database but it'll feel like they do in many ways. We leverage the SolarWinds Information Service (SWIS) to allow the applications to integrate without requiring that they share a common database.

Josh

September 4, 2008 5:57 PM
 

wvitalec said:

Maybe you can help me. I am currently running to different locations in SolarWinds. In one location I have 3 pollers and a HSB and in the 2nd I have 2 pollers and a HSB. They are totally seperate environments. Each has its own SQL server. Also, everything is on a virtual environment. I have heard that it would be better to have the SQL servers on a physical box. Can you tell me specifically why?
September 10, 2008 4:00 PM
 

Josh Stephens said:

wvitalec,

This is a great question. Generally speaking, there is no reason why you can't run SQL Server on a virtual server. However, the reason that most people run SQL Server on a physical server is that it's easier to guarantee system performance/resources that way. SQL tends to be very disk I/O and memory intensive and in many cases applications like this perform better on a physical server than a virtual server.

If you do decide to keep it on a virtual server you can certainly configure it so that it will scale in similar ways to a physical server, it's just not a "typical" VM at that point.

Please let me know if I can provide any additional information or assistance.

Thanks,,

Josh

September 11, 2008 12:23 PM
 

People Over Process » Links for September 24th said:

Pingback from  People Over Process » Links for September 24th

September 24, 2008 5:10 PM

About Josh Stephens

Josh Stephens is a Vice President – and Head Geek – at SolarWinds, where he plays an integral part in the development and delivery of our award-winning network management products. Josh has extensive experience in network management systems, network engineering, and software development. His 15-plus years of experience in technology include designing and deploying advanced networks and network management systems within organizations including the US Air Force, Sprint, MCI/UUNET, and Wal-Mart. He has received several industry certifications including those from Cisco Systems, Microsoft, and HP.