Editing DGARM Nagios Core - Storage Onboarding Summary


'''Source videos:'''
* <code>DGRAM-Infosys-Nagios-Core-Deployment-.storage-1.mp4</code> (35 min)
* <code>DGRAM-Infosys-Nagios-Core-Deployment-storage-2.mp4</code> (75 min)

: '''Note on this summary''': audio across both recordings is sparse/degraded (mostly
: silent screen-work, with Part 2 particularly affected by background noise the
: transcription model couldn't handle). This summary is built primarily from clear
: on-screen terminal/browser evidence.

== Summary ==

Two-part, same-day session onboarding '''NetApp storage monitoring''', working from the '''existing Nagios XI server''' (<code>dcprodnagios01</code>) to carry storage plugins and configs across to the new Core server (<code>dcprdlmonitor02</code> / <code>10.150.24.167</code>) — the "copy templates from XI" plan described back in the kick-off meeting, now executed for the storage category. Also continues network switch onboarding using the automation from the Network Switch session.

=== Part 1 — plugin and config transfer ===
* '''Plugin identified''': <code>check-netapp-ng.pl</code> (Perl), at <code>/usr/local/nagios/libexec/check-netapp-ng.pl</code> on the XI server. Handles multiple check types via SNMP against NetApp filers, including:
** <code>SHELFINFO</code> — disk shelf status/count
** <code>FSSTATUS</code> — overall filesystem/volume status, read via SNMP OID <code>snmpfsOverallStatus</code> (and its <code>_text</code> companion), mapped to OK/WARNING/CRITICAL
* '''Existing NetApp config files copied across via <code>scp</code>''' from XI (<code>/usr/local/nagios/etc/services/</code>) to the Core host's <code>/opt</code> staging area: <code>Netapp_cpu.cfg</code>, <code>Netapp_disksummary.cfg</code>, <code>Netapp_fan.cfg</code>, <code>Netapp_shelf.cfg</code>, <code>NetApp_top_volumes.cfg</code>, <code>Netapp_uptime.cfg</code> — six standard NetApp health checks reused as-is rather than rebuilt.
* '''Scale context''': the XI server's services directory showed dozens of per-device config files for switches, routers, and NetApp filers (e.g. <code>KOLKATA-AIU-SWITCH.cfg</code>, <code>MIAL-AGGREGATOR-SWITCH.cfg</code>, <code>NDC_Netapp_*.cfg</code>, <code>NDCPRDLSWT02.cfg</code>) — this is a large, long-running XI estate being incrementally extended into Core, not a greenfield setup.
* '''XI already has notification glue scripts''': <code>xi_service_event_handler</code> / <code>xi_service_notification_handler</code> commands call <code>/usr/local/nagiosxi/scripts/handle_nagioscore_event.php</code> and <code>handle_nagioscore_notification.php</code> — worth evaluating reuse of these for Core rather than writing new notification handling.
* Brief mentions (not demonstrated in detail): '''Grafana''' as a possible alternative/supplement to PNP4Nagios for storage graphing, and confirmation that '''PowerShell-based checks''' are still in active use for some Windows-side checks.

=== Part 2 — going live ===
* '''NetApp storage host added''': <code>NDC_NetApp_Storage</code> (<code>10.50.18.100</code>), confirmed live in Thruk with service <code>imp_NDC_NetApp_Storage - NetApp CPU</code> (the <code>imp_</code> prefix matches the same NagiosQL import workflow used for switches).
* '''Same transient "pending" pattern''' seen elsewhere: newly imported host showed <code>PENDING (obj has not been checked yet)</code> immediately after import — clears after the first active check cycle, not a fault.
* '''More switch interfaces onboarded on a second switch''' (<code>dcprdlswt02</code>), following the same LAG (link aggregation) naming convention from the Network Switch session: <code>dcprdlswt02_lag7_a01_sr04_status</code>, <code>..._lag8_a02_sr04_bandwidth</code>, <code>..._lag9_a01_sr05_status</code>, etc. — confirms the discovery-and-import automation is now the standard process, not a one-off.
* Only '''one storage device onboarded so far''', with the intent that the client's team repeats the process for the rest independently — same pacing pattern as other device categories. Session closed out for the day at the end.

== Additions to the runbook ==

{| class="wikitable"
|-
! Area
! Note
|-
| Storage checks
| Reuse <code>check-netapp-ng.pl</code> + the six standard <code>Netapp_*.cfg</code> service definitions from XI rather than rebuilding NetApp monitoring from scratch
|-
| Notifications
| Check whether XI's <code>handle_nagioscore_event.php</code> / <code>handle_nagioscore_notification.php</code> scripts are meant to be reused for Core's notification handling before writing new ones
|-
| Graphing
| Grafana was mentioned as a possible alternative/addition to PNP4Nagios for storage metrics — needs a decision, not yet implemented
|-
| Storage host onboarding
| Same NagiosQL import pipeline as network devices: generate/prepare host + service config, copy into the import directory, import, write config, wait for pending → active
|-
| "Pending" status after import
| Expected transient state, not a bug — clears after the first scheduled active check completes
|-
| LAG interfaces
| The switch discovery script's naming convention extends to link-aggregation (LAG) interfaces, not just physical ports — confirmed on a second switch (<code>dcprdlswt02</code>)
|}

[[Category:INFOSYS_DGARM_NAGIOS]]
== Source recordings ==
=== Part 1 ===
[[File:DGARM_Nagios_Core_Storage_Onboarding_Part1.mp4|600px]]

=== Part 2 ===
[[File:DGARM_Nagios_Core_Storage_Onboarding_Part2.mp4|600px]]