Issue

Use this article to troubleshoot UI alarm-object definitions and differences in understanding event objects.

Environment

• Product: ZCF
• Versions: 4.x, 5.x
• Component: Cloud
• Affected objects: UI alarms, event alarms, elastic IPs, VM networks, and physical-host networks

Symptoms

• The UI displays an alarm indicating that a physical-host NIC is disconnected.
• The alarm title is understood as a physical NIC exception on a physical host.
• The alarm-object field actually points to an elastic IP interface bound to a VM.

Possible causes

• The alarm title describes the event type, whereas the alarm-object field points to the specific affected resource.
• A physical network event and a VM elastic IP resource have a binding relationship, leading to interpretations from different resource levels.
• UI wording or object display is unclear, causing misunderstanding of the resource level.
• The product object mapping or event details can contain a display defect that requires further confirmation.

Resolution

1. Record the alarm title, alarm object name, alarm object UUID, resourceType, and trigger time.
2. Open alarm details or use the API to confirm resourceUuid, resourceType, and eventName.
3. Use elastic-IP bindings to trace back through the VM, VPC/flat network, physical network, and physical-host NIC path.
4. Determine whether the alarm object is the affected resource or whether a displayed field is mapped incorrectly.
5. If UI wording or object mapping is confirmed to be unclear, retain screenshots, event details, and version information and submit a defect or enhancement request.

Remediation

• During troubleshooting, use resourceUuid, resourceType, and eventName in event details as the basis.
• Explain the resource-level relationship between the alarm title and the actual object.
• If a UI display issue is confirmed, track the fixed version or submit a product enhancement.

Verification

• The actual platform resource can be located through the alarm object UUID.
• The association between that resource and the event described by the alarm title can be explained.
• The customer confirms the alarm-object definition, or a product-side defect record is created.

Risks and rollback

• Do not make physical-network changes based only on the alarm title.
• Before changing elastic IPs, VPCs, or physical networks, confirm service impact.

Notes

• Before adjusting management services, databases, certificates, permissions, auditing, or security settings, confirm the HA state, service window, rollback plan, and compliance-retention requirements.
• For management networks, storage networks, service networks, DHCP/VNC, VLANs, bonds, port groups, or switch-side settings, retain an available management channel and preferentially perform changes during a maintenance window.
• If database modifications, underlying file operations, lock release, service restarts, driver or firmware upgrades, or bulk resource changes are required, contact ZStack technical support before proceeding.