AppendixF IDU Updates
Baseline Configuration Compare Command feature
F-10
User Guide for CiscoWorks Small Network Management Solution
78-15693-03
For this device, non-compliance is also because it does not have a read-write
community string.
For each of the non-compliant devices, the set of commands needed to make it
compliantis generated. The parameters are replaced by the device-specific values,
given in the mapping file. For further details, seeSubstituting Parameters.
For example, for the non-compliant device, Cat-Dev1, in the mapping file,
d:\temp\Baseline\Mapping.ini, if there is value, mycompany, for the
read-write-community-name-string the following set of commands is generated.
set snmp community read-write mycompany
set snmp community read-only
set udld disable 2/34
set udld disable 3/48
set spantree macreduction enable
These commands are stored in the file:
d:\temp\Baseline\output\Cat-Dev1-Ver-latest-vs-BaseLineMandDis.cfg.
The following entries are logged in the generated command file:
d:\temp\baseline\commandfile.txt, one, for each of the non-compliant devices.
This file was specified using the-generatecmdfile option, in the cwconfig
comparewithbaseline command.
-device Cat-Dev1-f
d:\temp\Baseline\output\Cat-Dev1-Ver-latest-vs-BaseLineMandDis.cfg
-device Cat-Dev2 -f
d:\temp\Baseline\output\Cat-Dev2-Ver-latest-vs-BaseLineMandDis.cfg
-device Cat-Dev3 -f
d:\temp\Baseline\output\Cat-Dev3-Ver-latest-vs-BaseLineMandDis.cfgIn this
example, the following filescontain the commands required to make the devices
Cat-Dev2 and Cat-Dev3 compliant:
•d:\temp\Baseline\output\Cat-Dev2-Ver-latest-vs-BaseLineMandDis.cfg
•d:\temp\Baseline\output\Cat-Dev3-Ver-latest-vs-BaseLineMandDis.cfg
Todownload the commands onto the respective devices, use the cwconfig import
command:
cwconfig import -u username -p password import -input
d:\temp\baseline\commandfile.txt