iCC Help >> Typical Applications >> Basic Configuration Check Examples

Basic Configuration Check Examples

Operation Procedure

1. Select the Service tab, click the Compliance Center in the navigation tree to enter the Compliance Policy page.
2. Click Add.
3. Configure the following rule parameters:
   • Loose match: Matches devices' configurations that contain the specified strings. If you specify two or more strings, the string order and positions are not checked.
   • Negative loose match: Matches devices' configurations that do not contain the specified strings. If you specify two or more strings, the string order and positions are not checked.
   • Strict match: Matches devices' configurations that contain the specified strings in the specified order and at the specified positions.
   • Negative strict match: Matches devices' configurations that do not contain the specified strings in the specified order and at the specified positions.

Configuration Examples

1. Loose match

• Match patterns:
  access-limit disable
  state active
  This rule indicates that strings "access-limit disable" and "state active" must be contained but their positions are not restricted.
• Configuration segment 1:
  #
  domain system
  access-limit disable
  idle-cut disable
  state active
  self-service-url disable
  #
  This segment contains both "access-limit disable" and "state active". The segment meets the rule requirements.
• Configuration segment 2:
  #
  domain system
  access-limit disable
  idle-cut disable
  self-service-url disable
  #
  This segment contains "access-limit disable" but does not contain "state active". The segment does not meet the rule requirements.

2. Negative loose match

• Match patterns:
  access-limit disable
  state active
  This rule indicates that all the configurations, except those contain both "access-limit disable" and "state active", meet the rule requirements. The positions of the two strings are not restricted.
• Configuration segment 1:
  #
  domain system
  access-limit disable
  idle-cut disable
  state active
  self-service-url disable
  #
  This segment contains both "access-limit disable" and "state active". Therefore, it does not meet the rule requirements.
• Configuration segment 2:
  #
  domain system
  access-limit enable
  idle-cut disable
  self-service-url disable
  #
  This segment does not contain "access-limit disable", and "state active". Therefore, it meets the rule requirements.

3. Strict match

• Match patterns:
  access-limit disable
  state active
  This rule indicates that both "access-limit disable" and "state active" must be included and the former string must be located in the line right above the line where the latter string is located.
• Configuration segment 1:
  #
  domain system
  access-limit disable
  state active
  idle-cut disable
  self-service-url disable
  #
  This segment contains the two specified strings and the string order and positions are exactly the same as specified. Therefore, it meets the rule requirements.
• Configuration segment 2:
  #
  domain system
  access-limit disable state active
  idle-cut disable
  self-service-url disable
  #
  This segment contains the specified strings, but the two strings are located in the same line. Therefore, it does not meet the rule requirements.

4. Negative strict match

• Match patterns:
  access-limit disable
  state active
  This rule indicates that all the configurations, except those contains both "access-limit disable" and "state active" and the former string is located in the line right above the line where the latter string is located, meet the rule requirements.
• Configuration segment 1:
  #
  domain system
  access-limit disable
  state active
  idle-cut disable
  self-service-url disable
  #
  This segment contains the specified strings and string order and positions are exactly the same as specified. Therefore, it does not meet the rule requirements.
• Configuration segment 2:
  #
  domain system
  access-limit disable state active
  self-service-url disable
  idle-cut disable
  #
  This segment contains the specified strings, but the two strings are located in the same line. Therefore, it meets the rule requirements.

To view the check results, use one of the following methods:

• Click the Task History link of the check task that contains the previously mentioned rules.
• Click the Service tab, select Compliance Center > Task History from the navigation tree to display the Task History page, and then click the link of the operation.

Related Topics

• Advanced Configuration Check Examples