Project Management, lessons learned and, migration pitfall to share?

Ianthia

Greetings,

I am the Project Manager for the Orion NPM implementation at my company.  We are replacing an existing monitoring tool  with Orion NPM. 

• Has anyone done this type of migration and willing to share information about the Project management piece. 
  • For example, how many hours would it take to manage this type of project? 

• Also, I’d like to learn about the types of issues you had to address and provide advice about how to avoid any pitfalls,

• Lastly, are there any lessons learned that you might be able to share.   Thank you.

netlogix

I would say the biggest thing that will affect any answer to this is "Scope".  It's also what will make it a successful implementation on not.  What is the Goal?

  If it is to just implemented NPM where all nodes (200-300) are Windows, Cisco, ESX, or ESXi, then if SNMP is installed and configured already on all of them, and you have a list of IP addresses to monitor, setup could be 1 day.  Tuning would be a week of one hour a day, then a month of one hour a week.  Steps could be, Install OS (1 Hour), Patch OS (1 hour), Setup Company Specific Settings (1 hour), Install NPM (1 hour), Setup Network Sonar (1 hour), Tweak setting.

Also, I would recommend remote SQL Database.

  But if you are adding the planning time, goal determination, of have 50+ different node types, are also going to use APM, NTA, NCM, etc.  Then these are a lot of variables and the project should be split into smaller implementations (like one for NPM, another for APM, NCM, etc).  There are so many choices for each of those and NPM can be up and running while you are trying to figure out what application are important enough to be monitored by APM.  Oh, but NCM might want to be started before APM, unless you are going to be writing a lot of policies on device configuration, which will be as complicated as APM.

So, to sum it up, can we get more info about what you looking to accomplish?