Users may need to alert on specific hardware or software conditions (e.g., partition utilization, specific line card states) that are only visible by running commands in the router CLI and are not available via standard SNMP MIBs or configuration files.
All supported versons
1. Modiify the underlying NCM Perl/Bash capture scripts for the Juniper device family to execute the extra command and append it to the standard show configuration output.
2. Create a separate device family for a subset of devices. Isolate this NCM task by utilizing Global Collections and custom Device Families:
Create a Global Collection in OneClick with search criteria that specifically filters for this subset of routers
In the NCM workspace, associate the Global Collection with a specific Device Family. This ensures the customized capture script and policies only run against the devices in this specific bucket.
3. Configuring Spectrum to alarm on the condition. Once the CLI output is successfully appended to the captured configuration file, utilize the NCM Policy Manager:
Create a new NCM Policy.
Define a rule using Regular Expressions (Regex) that specifically looks for the condition string in the captured configuration block.
Configure the policy violation to generate an alarm in Spectrum. When NCM runs its scheduled capture and evaluates the policy, an alarm will trigger if the regex condition is met.