...
| Code Block | ||
|---|---|---|
| ||
'IOS_TS_BGP' => {
'os_info' => {
'version' => '/12.2|12.4|15.\d+/',
'os' => 'IOS',
},
'scheduling_info' => {
'run_commands_on_separate_connection' => 'false',
'attempt_timeout_recovery' => 1,
},
'purging_policy' => {
'keep_last' => 1000,
'purge_older_than' => 2592000, # 30 days
'autoprotect_first_revision' => 'true',
},
'commands' => [
{
'multipage' => 'true',
'privileged' => 'true',
'command' => 'show ip bgp',
'tags' => [ 'troubleshooting', 'routing', 'detect-change' ],
},
{
'multipage' => 'true',
'privileged' => 'true',
'command' => 'show ip bgp summary',
'tags' => [ 'troubleshooting', 'routing', 'detect-change' ],
},
{
'multipage' => 'true',
'privileged' => 'true',
'command' => 'show ip route summary',
'tags' => [ 'troubleshooting', 'routing', 'detect-change' ],
},
],
}, |
Testing and Verification
The easiest way to this configuration is to administratively shutdown a BGP peer. After the next NMIS collect cycle a BGP Peer Down alert will be processed by opEvents. Here's an example from our lab.