Whether black boxes can be used to record VM logs and user behavior

5

Black boxes cannot be used to record VM logs and user behavior.
VM logs, user behavior, and operation records are generally recorded and managed by the upper-layer cloud management system.
A black box collects and stores running information about a physical machine (Domain0 and Xen) equipped with FusionCompute when the physical machine exits abnormally. The following OS-level information is involved:
(1) Kernel logs
(2) Screen output information from before the system exited
(3) Diagnosis information from the diagnosis tool (kernel module)

Other related questions:
Server black box
The black box consists of a built-in memory chip and fault monitoring software. The memory chip, independent from the server hard disks, stores fault information. The fault monitoring software records the kernel information when the server OS breaks down. For detailed information about the black box, see the iMana User Guide for your server model.

Whether an account can be bound to a user VM
An account is bound to a user VM during VM creation. When creating a VM, you need to perform the following configuration: When VM group type is set to Full copy, configure the Set assignment type, Add user, and Setting User Group parameters. When VM group type is set to Linked clone and Full memory, configure the Number of VMs and Add User (Group) parameters. After the VM has been created, the account is bound to the VM.

Can a box switch record logs and alarms after a loop detection-enabled interface detects a loop
A fixed switch can record alarms but not logs after a loop detection-enabled interface detects a loop. The configurations are as follows: In V100R005 and V100R006, you can run the snmp-agent trap enable feature-name ldttrap command to enable the alarm function for loop detection. If snmp-agent trap enable has been configured globally, the alarm function has been enabled. Loop detection and loopback detection have been available since V200R001. You can run the snmp-agent trap enable feature-name ldttrap command to enable the alarm function for loop detection and run the snmp-agent trap enable feature-name lbdt command to enable the alarm function for loopback detection. You can run the display trapbuffer command to view alarms.

Whether one TC can simultaneously log in to multiple VMs and whether the VMs can be displayed on different screens
One TC can log in to multiple VMs simultaneously, but only one VM can be displayed at a time on a single screen. This screen can be switched between VMs. Currently, multiple VMs cannot be displayed on different screens simultaneously using one TC.

Are all logs recorded in the log buffer
Only some logs are recorded in the log buffer. Logs that can be recorded in the log buffer are restricted. -By default, only logs at levels lower than the warning logs (level 4) are recorded in the log buffer. Therefore, logs at levels 0 to 4 are recorded to the log buffer and logs at levels 5 and 7 are not recorded. You can run the info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } command to set the levels of logs that can be recorded to the log buffer. -The log buffer space is limited. If the number of logs in the log buffer reaches the maximum value, new logs will replace the existing logs that are placed earlier in the log buffer until all the new logs are stored. By default, the log buffer can hold a maximum of 512 logs. You can run the info-center logbuffer size size command to set the maximum number to 1024.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top