Disabling a single compliance policy, Disabling all compliance policies, Rule examples – H3C Technologies H3C Intelligent Management Center User Manual

Page 632

Advertising
background image

618

a.

Click the Service tab from the tabular navigation system on the top.

b.

Click the Compliance Center on the navigation tree on the left.

c.

Click Compliance Policy under Compliance Center on the left navigation tree.

The Policy List appears.

2.

Click the Enable All button.

Disabling a single compliance policy

To disable a single compliance policy:

1.

Navigation Service > Compliance Policy.

a.

Click the Service tab from the tabular navigation system on the top.

b.

Click the Compliance Center on the navigation tree on the left.

c.

Click Compliance Policy under Compliance Center on the left navigation tree.

The Policy List appears.

2.

Click the Enabled link of the compliancy policy to be disabled.

Disabling all compliance policies

To disable all compliance policies:

1.

Navigation Service > Compliance Policy.

a.

Click the Service tab from the tabular navigation system on the top.

b.

Click the Compliance Center on the navigation tree on the left.

c.

Click Compliance Policy under Compliance Center on the left navigation tree.

The Policy List appears.

2.

Click the Disable All button.

Rule examples

IMC predefines rules in a compliance policy. The following describes rules with the check type Device,

Interface, Link, Aggregate Link, and Configuration Segment.
A Device rule checks the configuration file or display command outputs on the device. For example, if a

rule checks the Latest backup running configuration file, it checks all the contents of the Latest backup

running configuration file. (HPA)Syslog enabled is used as an example.
An Interface rule checks the configuration segments about interface in the configuration file or the
configuration segments about interface in a display command output on the device. The start position

and end position of the configuration segment are determined by Start Identifier and End Identifier in the

rule. (Cisco) No delay an interface-CatOS is used as an example.
A Link rule checks the configuration segments about interface in the configuration file or the
configuration segments about interface in a display command output on the devices on the two ends of

a link.
The start position and end position of the configuration segment are determined by Start Identifier and

End Identifier in the rule. A Link rule checks devices by link rather than by device. (HPA) Duplex status is

used as an example.
An Aggregate Link rule checks the configuration segments about interface in the configuration file or the

configuration segments about interface in a display command output on the devices on the two ends of

an Aggregate Link. The start position and end position of the configuration segment are determined by

Advertising