Vm Monitoring Audit Log - Extreme Networks Ridgeline Guide Manual

Figure 135: VM Monitoring Device Details

VM Monitoring Audit Log

Information in the Audit Log for VM monitoring is listed under VM Monitoring tab>Audit Log node.
See Figure 136.
Ridgeline creates an Audit Log entry for the following reasons:
Ridgeline creates an Audit Log entry for the following reasons:
1 A virtual port profile has been modified (for example, an update of an ingress or egress policy.
2 A policy has been attached to a VPP
3 A policy has been detached from a VPP
4 To enable VM Tracking
5 To disable VM Tracking ports
6 To update VM Tracking ports
The VM Monitoring Audit Log table view lists the following attributes:
Action Time Time when the VM policy was attached or detached
Action Name of the action—Attachment of Detachment
User Name Name of user who performed the attachment or detachment operation
Overall Status The operation was a Success or it Failed
Ridgeline Concepts and Solutions Guide
11
175