28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

4.14 Tracking Router Configuration Changes<br />

Problem<br />

You want an NMS system to track when the router’s configuration has been changed.<br />

Solution<br />

First, define the NMS system and its password:<br />

[edit snmp v3]<br />

aviva@router1# set usm local-engine user nms2 authentication-sha authenticationpassword<br />

$0212roZH<br />

aviva@router1# set usm local-engine user nms2 privacy-des privacy-password 0212roZH<br />

Then, define two views that allow the NMS access to the configuration information.<br />

The first view defines what the NMS can read from the MIB:<br />

[edit snmp v3]<br />

aviva@router1# set view config-info-read oid jnxCfgMgmt include<br />

The second view sets what the router includes in notifications sent to the NMS:<br />

[edit snmp v3]<br />

aviva@router1# set view config-info-notify oid jnxCfgMgmt include<br />

aviva@router1# set view config-info-notify oid jnxCmNotifications include<br />

aviva@router1# set view config-info-notify oid snmpMIBObjects include<br />

aviva@router1# set view config-info-notify oid system include<br />

Finally, create groups and their users and assign access privileges for the groups:<br />

[edit snmp v3]<br />

aviva@router1# set vacm security-to-group security-model usm security-name nms2 group<br />

config-only<br />

aviva@router1# set vacm access group config-only default-context-prefix securitymodel<br />

usm security-level privacy read-view config-info-read<br />

aviva@router1# set vacm access group config-only default-context-prefix securitymodel<br />

usm security-level privacy notify-view config-info-notify<br />

<strong>Discussion</strong><br />

To use SNMP to extract the router configuration, use the Juniper Networks configuration<br />

management MIBextension, which tracks who made changes to the configuration<br />

and when. This recipe gives the NMS system called nms2 access to configuration<br />

information.<br />

The first commands in this recipe configure USM for security, with SHA1 authentication<br />

and DES message payload encryption. You then create two views, one that<br />

defines what nms2 can read from the MIBand a second that sets what the router can<br />

include in notifications. The final commands configure the VACM to provide access<br />

to desired groups.<br />

156 | Chapter 4: SNMP<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!