What Are the Possible Causes of the Failure in Importing Static Alarm Information from a Local Excel File to OperationCenter



3.0.9 and earlier

What are the possible causes of the failure in importing static alarm information from a local Excel file to OperationCenter?

Possible cause 1:
The Excel file contains no table headings, and it only contains alarm IDs and alarm names.

Possible cause 2:
The template downloaded from OperationCenter is an Excel 2003 file. OperationCenter only supports Excel 2003 files. Static alarm information cannot be imported from a local file in Excel 2007 or later versions.

Possible cause 3:
A message indicating that the file is imported successfully is displayed, but the imported alarm information is not displayed in the alarm list on OperationCenter.
The database table has been imported successfully, but OperationCenter does not interconnect with the corresponding system. As a result, the alarm information is not displayed on OperationCenter. After OperationCenter interconnects with the system, the imported static alarm information is displayed on OperationCenter.


Other related questions:
What are possible causes for L2TP dial-up failures of the AR router
Possible causes for L2TP dialup failures are as follows: - The firewall is configured on the public network or the local PC has the firewall, so L2TP packets are discarded. - When corresponding L2TP port is disabled or occupied, UDP port 1701 is often used. For example, ACL and NAT are configured. - The user name and password of the LAC are incorrect, or no users are specified for the LNS. - The configured address is incorrect. For example, the statically configured address of the VT interface is incorrect. - Tunnel authentication modes are different. - LCP renegotiation is not configured. - The IP address allocation is improper. The IP address pool has a small address range or not configured. - Gateway addresses are not configured in the IP address pool, so gateway addresses are allocated to clients. - There are unreachable routes. - In the L2TP group view, the specified tunnel name at the remote end is incorrect. - The configured authentication domain is incorrect. - L2TP negotiation fails because control packets sent by clients of the local PC do not carry the SQ. - When IPSec encryption is used, the IPSec parameters on the two ends of the tunnel are inconsistent.

Possible causes for iOS description file installation failure on the AnyOffice client
Possible causes are as follows: -The device certificate and device CA certificate are not correctly imported. The CN field in the device certificate includes the IP address and domain name to be accessed by the terminal. -In V2R2, the gateway is connected to the firewall in bypass mode. In NAT scenario, you need to enable the global load balancing acceleration function and configure an external IP address when creating a virtual gateway. -In V2R3, if the AE server translates the IP address and externally provides services through the NAT, load balancing, and access proxy devices, you need to enter the mapped IP address and domain name used for the access when you configure the client access address in the installation deployment tool.

Possible causes for a failure to ping an IPv6 address
In V100R002 and later versions, the IPv6 address of a device fails to be pinged due to the following possible causes: l. The physical state or protocol state of the interface is Down. You can run the display ipv6 interface interface-type interface-number command in any view to check the physical state and protocol state of an interface. 2. The switch fails to learn ND entries of the peer device. You can run the display ipv6 neighbors command in any view to check information about ND entries. 3. The link transmission delay is too long. The source device does not receive any Response packet from the destination device within the waiting time, and the ping operation fails. You can run the ping ipv6 -t timeout destination-ipv6-address command in any view to set “-t&rdquo to increase the timeout interval for waiting for Response packets.

What are the possible causes for SSH+TACACS authentication failure
There is no default authentication mode for SSH users. If no authentication mode is specified for SSH users, users cannot access the Internet. Solution: When configuring SSH authentication, run the ssh authentication-type default password command to configure password authentication for SSH users.

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