There are some projects which I handle this year especially Cisco Prime Infrastructure (PI). PI is Network Monitoring System (NMS) produced by Cisco inc. PI is similar to other NSMs like Solarwind, Splunk, Cacti, CiscoWork or Cisco Carrier Management, etc.
Before PI, Cisco produced some NMS (Cisco Work, LMS, NCS, WCS). Now, Cisco is producing and developing PI to replace LMS. The LMS is only produced till 4.2 version and PI is introduced to replace it. PI is produced with 3 variants: Express, Standard and Professional. There is PI Express Custom, but it is not downloadable from cisco.com. PI Express custom is customized based on PI express.
Every variant has different coverage, depend on database that create in first installation. The specification of RAM, HDD and CPU is also different.
When we deploying PI, the first thing that we need to consider several things:
1. How many devices (node) that will be covered by PI? we can use PI express, standard or professional for big deployment
2. How many space in our storage (HDD), RAM, or CPU?
3. Is it deployed in virtual machine (virtual appliance) or physical appliance?
4. Consider how many IP address which used by PI or others. For example, if we used UCS and VMware then we need some IP address for vSphere management, CIMC management or UCS Manager (Fabric Interconnect, etc)
5. Consider SNMP community and Node IP address which can be reached by PI. In my suggestion, used loopback ip address as snmp client (node/NE).
6. Prepare hostname, NTP, domain, & DNS address for used by PI to access internet and/or upgrade when we need to.
Let’s install PI (virtual appliance) by accessing vSphere client or vSphere web client if we use vCenter.
1. Prepare and download PI Express, standard or professional from Cisco.com
2. Open Esxi vSphere Client and login:
3. Click on File –>Deploy OVF Template and browse to where PI ova stored.
4. Click Next and Next till finish and display like below. The PI is deploying on vmware infrastructure.
5. Wait untill it finish configuring and start the PI.
6. Type ‘setup’ and input some parameters like hostname, ip address etc. Then, let it configuring itself automatically.
7. After interface is up, then configuring HA, web interface, ftp and root password.
Finally we can login to PI. In this sample I used PI version 1.2. I have try and implement PI 2.0 in some customers.
8. The last thing is discover Network Element and configure snmp community, username/password to used when discovering NE by PI.