Using Directives To Eliminate Reporting Of Configuration Mismatches; Ignore_And_Do_Not_Push Command; Push_And_Exclude Command - Dell PowerConnect W-Airwave User Manual

Using Directives to Eliminate Reporting of Configuration Mismatches

AMP is designed to audit AP configurations to ensure that the actual configuration of the access point exactly
matches the Group template. When a configuration mismatch is detected, AMP generates an automatic alert
and flags the AP as having a Mismatched configuration status on the user page.
However, when using the templates configuration function, there will be times when the running-config file and
the startup-config file do not match under normal circumstances. For example, the
is almost never identical in the running-config file and the startup-config file. You can use directives such as
<ignore_and_do_not_push>
of variance.
AMP provides two types of directives that can be used within a template to control how AMP constructs the
startup-config file to send to each AP and whether it reports variances between the running-config file and the
startup-config file as "configuration mismatches." Lines enclosed in <push_and_exclude> are included in the AP
startup-config file but AMP ignores them when verifying configurations. Lines enclosed in
<ignore_and_do_not_push> cause AMP to ignore those lines during configuration verification.

Ignore_and_do_not_push Command

The
ignore and do not push
device, but always appears in the running-config file. Lines enclosed in the ignore and do not push directive will
not be included in the startup-config file that is copied to each AP.
When AMP is comparing the running-config file to the startup-config file for configuration verification, it will
ignore any lines in the running-config file that start with the text within the directive. Lines belonging to an
ignored and unpushed line, the lines immediately below the line and indented, are ignored as well. In the
example below, if you were to bracket NTP server, the NTP clock period would behave as if it were bracketed
because it belongs or is associated with the NTP server line.
NOTE: The line <ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push> will cause lines starting with "ntp clock-
period" to be ignored. However, the line <ignore_and_do_not_push>ntp </ignore_and_do_not_push> causes all lines starting with
"ntp" to be ignored, so it is important to be as specific as possible.

Push_and_exclude Command

Instead of using the full tags you may use the parenthesis shorthand, (substring). The push and exclude directive
is used to push commands to the AP that will not appear in the running-config file. For example, some no
commands that are used to remove SSIDs or remove configuration parameters do not appear in the running-
config file of a device. A command inside the push and exclude directive are included in the startup-config file
pushed to a device, but AMP excludes them when calculating and reporting configuration mismatches.
NOTE: The opening tag may have leading spaces.
Below are some examples of using directives:
...
line con 0
</push_and_exclude>no stopbits</push_and_exclude>
line vty 5 15
!
ntp server 209.172.117.194
<ignore_and_do_not_push>ntp clock-period</ignore_and_do_not_push>
end
Dell PowerConnect W-AirWave | User Guide
to customize the template to keep AMP from reporting mismatches for this type
directive should typically be used when a value cannot be configured on the
setting
ntp clock-period
Creating and Using Templates | 153