Implement
Execute your plan, test, and validate the deployment.
Implementing and testing your deployment will go quickly and effortlessly if you have spent adequate time in the Planning stage. The more detail you Plan has, the easier Implementation is.
Your plan should be executed as documented, following the steps you identified and tested, and then running the appropriate tests at each stage to ensure the implementation meets your requirements. Any step which fails to meet your test criteria should result in an implementation stoppage until you can positively identify the cause. If the issue requires a deviation from the plan then you should rollback that step and return to the Planning stage.
Table of Tasks for each product
These tables are available for you to use : Google Sheet Spreadsheet Of Delivery Tasks
An example of the NMIS tasks are below.
TESTING
Polling Server Performance -
Is the NMS server operating within acceptable performance metrics (CPU, Memory, polling, etc)
Are all devices being collected on, as desired? i.e. are appropriate device models being auto-assigned to each device, are devices responding to ICMP and SNMP polling
Are polling and update cycles being completed within acceptable windows (i.e. before the next collect cycle)
Are log files rotating properly
Is disk usage within the expected range(s)
Primary Server Performance (requires opHA)
Are device performance and events appearing on the Primary server from each Poller?
If you are using opEvents, and events are forwarded by the opEvents' API, is opEvents on the Primary being populated
TASK | NOTES | WIKI REFERENCE |
|---|---|---|
SECURITY |
|
|
Configure network security rules to allow management of devices using NMIS |
| https://docs.community.firstwave.com/wiki/display/NMIS/Information+about+Network+Ports |
Determine how users will authenticate with NMIS |
| https://docs.community.firstwave.com/wiki/display/NMIS/User+Management+in+NMIS8 |
Create initial list of users and identify each authorization level |
|
|
Determine server name, IP and FQDN |
|
|
Acquire certificate if server will run SSL/HTTPS |
|
|
Determine process/responsibility for maintaining NMIS host device (OS and hardware) |
|
|
|
|
|
COLLECT DEVICE DATA |
|
|
Collect list of devices to import into NMIS |
|
|
Collect SNMP Community strings and SNMP version for each device |
|
|
Collect WMI admin accounts for management of Windows servers |
|
|
Collect device MIBs for SNMPTrap processing |
|
|
|
|
|
COLLECT NOTIFICATION INFORMATION |
|
|
Collect email server information for sending notifications |
|
|
Identify options for SMS text messaging (if required) |
|
|
Is integration with a HelpDesk required? |
|
|
|
|
|
SYSTEM RESOURCES AND INSTALL |
|
|
Determine starting hardware specifications |
|
|
Install and configure host OS (if not Opmantek VM) |
|
|
Install NMIS or import and resize Opmantek VM |
| https://docs.community.firstwave.com/wiki/display/opCommon/The+Opmantek+Installer |
Install SSL certificate and configure for HTTPS |
|
|
If using the Opmantek VM change root password for applicance |
|
|
Test login to NMIS using default credentials |
| |
Copy manufacturer MIBs in SNMPTrap subfolder | Restart SNMPTrap daemon |
|
|
|
|
SETUP AND CONFIGURE NMIS (INITIAL) |
|
|
Complete Basic Setup Wizard | Set cookie type to OMK | https://docs.community.firstwave.com/wiki/display/NMIS/Configuring+Email+Server+for+NMIS+Notifications+including+Gmail+server |
Create/Edit NMIS Groups |
| https://docs.community.firstwave.com/wiki/display/NMIS/Leveraging+the+NMIS+Group |
Add/Edit Contacts | Populate email for Contact1; this Contact is used in testing NMIS email handling |
|
Add/Edit Customers |
|
|
Adjust Model Policy |
| https://docs.community.firstwave.com/wiki/display/NMIS/NMIS+Model+Policy |
Add/Edit Users | Users should NOT be using the NMIS or Admin user accounts, passwords for these accounts should be changed or the accounts disabled. |
|
Configure authentication (other than htpasswd) (if needed), and test |
| |
Test sending email |
| Configuring Email Server for NMIS Notifications including Gmail server |
Import 1-2 devices of each Model from device list |
| |
Monitor NMIS for proper operation; troubleshoot device connectivity | Are all devices responding to ICMP/SNMP/WMI? |
|
Configure simple Escalation | Configure a single escalation to handle all events and send emails to a test Contact | |
|
|
|
CONFIGURE NMIS (continued) |
|
|
Add/Edit Device Types |
|
|
Add/Edit Device Role |
|
|
Add/Edit Network Types |
|
|
Bulk Import Remaining Devices | Import ~250 devices at a time through bulk import; allow NMIS to complete first Updates before running next bulk import. | |
Monitor NMIS for proper operation; troubleshoot device connectivity | Are all devices responding to ICMP/SNMP/WMI? |
|
Identify devices requiring custom modeling |
| |
Setup/Disable events in NMIS |
| |
Tune Thresholds | These are the alarm levels NMIS applies that generate events. | |
Adjust Node Summary Field list | Changing the fields which NMIS sends to the summary file Config.nmis/node_summary_field_list | |
Adjust Node Configuration |
| How To Customize Interface Speed, Collection, Thresholds and Events Using Node Configuration |
|
|
|
ADVANCED NMIS |
|
|
Polling Policy |
| NMIS8 Node Polling Configuration |
Next Up
Observe - Monitor the system for performance, operation, and results.