No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R013C00 Log Reference

This document provides the explanations, causes, and recommended actions of logs on the product.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OPSA

OPSA

OPSA/4/CGROUP_CLOSE

Message

OPSA/4/CGROUP_CLOSE: The script is forcibly closed due to a high memory or CPU usage. (Script="[script-name]")

Description

The python script is forcibly stoped because the memory or CPU usage exceeds the specified value.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a python script name.

Possible Causes

The python script is stopped because the memory or CPU usage is high during script execution.

Procedure

  • Modify the python script and load it again to execute it.

OPSA/3/OPS_CLI_CLOSE_FAIL

Message

OPSA/3/OPS_CLI_CLOSE_FAIL: Failed to stop the terminal using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal=[cli-id])

Description

Failed to close a CLI terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[cli-id] Indicates a CLI terminal ID.

Possible Causes

In the execution phase of the user script, parameters of the Closing CLI Channel API (ops.cli.close) are incorrect.

Procedure

  1. In the execution phase of the user script, parameters of the Closing CLI Channel API (ops.cli.close) are incorrect. You need to modify the script.

OPSA/6/OPS_CLI_CLOSE_SUCCEED

Message

OPSA/6/OPS_CLI_CLOSE_SUCCEED: The terminal is stopped successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal=[cli-id])

Description

Succeeded in closing a CLI terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[cli-id] Indicates a CLI terminal ID.

Possible Causes

Succeeded in closing a CLI terminal using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CLI_EXECUTE_FAIL

Message

OPSA/3/OPS_CLI_EXECUTE_FAIL: Failed to execute the command using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal=[cli-id], command="[command]")

Description

Failed to execute a command after a CLI terminal was opened using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[cli-id] Indicates a CLI terminal ID.
[command] Indicates a command to be executed.

Possible Causes

In the execution phase of the user script, parameters of the Executing CLI Command API (ops.cli.execute) are incorrect.

Procedure

  1. In the execution phase of the user script, parameters of the Executing CLI Command API (ops.cli.execute) are incorrect. You need to modify the script.

OPSA/6/OPS_CLI_EXECUTE_SUCCEED

Message

OPSA/6/OPS_CLI_EXECUTE_SUCCEED: The command is executed successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal=[cli-id], command="[command]")

Description

Succeeded in executing a command after a CLI terminal was opened using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[cli-id] Indicates a CLI terminal ID.
[command] Indicates a command to be executed.

Possible Causes

Succeeded in executing a command after a CLI terminal was opened using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CLI_OPEN_FAIL

Message

OPSA/3/OPS_CLI_OPEN_FAIL: Failed to start the terminal using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id])

Description

Failed to open a CLI terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.

Possible Causes

When only three or less VTY resources are available, no more CLI channels can be opened.

Procedure

  1. When only three or less VTY resources are available, no more CLI channels can be opened. To increase the maximum number of VTY resources, run the user-interface maximum-vty number command.

OPSA/6/OPS_CLI_OPEN_SUCCEED

Message

OPSA/6/OPS_CLI_OPEN_SUCCEED: The terminal is started successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal=[cli-id])

Description

Succeeded in opening a CLI terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[cli-id] Indicates a CLI terminal ID.

Possible Causes

Succeeded in opening a CLI terminal using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CLI_SUBSCRIBE_FAIL

Message

OPSA/3/OPS_CLI_SUBSCRIBE_FAIL: Failed to subscribe to the CLI event using the script. (Script="[script-name]", event="[event-name]", expression="[expression]", enter=[enter], sync=[sync], async_skip=[async_skip], sync_wait=[sync_wait])

Description

Failed to subscribe the command line event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
expression Indicates the regular expression that matches commands.
enter Indicates the time when to match a regular expression:
  • True: A regular expression is matched immediately after Enter is pressed.

  • False: If an abbreviated keyword is specified in a command, a complete keyword will be matched against a regular expression.

sync Indicates whether to wait until the execution of scripts is complete after the command triggers an event:
  • True: yes

  • False: no

async_skip Indicates whether to skip the original command when the sync value is False:
  • True: yes

  • False: no

sync_wait Indicates the time taken by a command to wait for the execution of scripts if the sync value is True.

Possible Causes

In the subscription phase of the user script, parameters of the Command Line Event Subscription API (ops.cli.subscribe) are incorrect.

Procedure

  1. In the subscription phase of the user script, parameters of the Command Line Event Subscription API (ops.cli.subscribe) are incorrect. You need to modify the script.

OPSA/6/OPS_CLI_SUBSCRIBE_SUCCEED

Message

OPSA/6/OPS_CLI_SUBSCRIBE_SUCCEED: The CLI event is subscribed successfully using the script. (Script="[script-name]", event="[event-name]", expression="[expression]", enter=[enter], sync=[sync], async_skip=[async_skip], sync_wait=[sync_wait])

Description

Succeeded in subscribing to the command line event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
expression Indicates the regular expression that matches commands.
enter Indicates the time when to match a regular expression:
  • True: A regular expression is matched immediately after Enter is pressed.

  • False: If an abbreviated keyword is specified in a command, a complete keyword will be matched against a regular expression.

sync Indicates whether to wait until the execution of scripts is complete after the command triggers an event:
  • True: yes

  • False: no

async_skip Indicates whether to skip the original command when the sync value is False:
  • True: yes

  • False: no

sync_wait Indicates the time taken by a command to wait for the execution of scripts if the sync value is True.

Possible Causes

Succeeded in subscribing to the command line event using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CONTEXT_RETRIEVE_CONDITION_FAIL

Message

OPSA/3/OPS_CONTEXT_RETRIEVE_CONDITION_FAIL: Failed to retrieve the variable value using the script. (Script="[script-name]", variable="[varName]")

Description

Failed to recover the script variable in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[varName] Indicates a variable name.

Possible Causes

In the subscription phase of the user script, parameters of the Restoring Script Variable API (ops.context.retrieve) are incorrect or the context does not exist.

Procedure

  1. In the subscription phase of the user script, parameters of the Restoring Script Variable API (ops.context.retrieve) are incorrect or the context does not exist. You need to modify the script.

OPSA/6/OPS_CONTEXT_RETRIEVE_CONDITION_SUCCEED

Message

OPSA/6/OPS_CONTEXT_RETRIEVE_CONDITION_SUCCEED: The variable is retrieved successfully using the script. (Script="[script-name]", variable="[varName]")

Description

Succeeded in recovering the script variable in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[varName] Indicates a variable name.

Possible Causes

Succeeded in recovering the script variable in the subscription phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CONTEXT_RETRIEVE_EXECUTE_FAIL

Message

OPSA/3/OPS_CONTEXT_RETRIEVE_EXECUTE_FAIL: Failed to retrieve the variable value using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[varName]")

Description

Failed to recover the script variable in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[varName] Indicates a variable name.

Possible Causes

In the execution phase of the user script, parameters of the Restoring Script Variable API (ops.context.retrieve) are incorrect or the context does not exist.

Procedure

  1. In the execution phase of the user script, parameters of the Restoring Script Variable API (ops.context.retrieve) are incorrect or the context does not exist. You need to modify the script.

OPSA/6/OPS_CONTEXT_RETRIEVE_EXECUTE_SUCCEED

Message

OPSA/6/OPS_CONTEXT_RETRIEVE_EXECUTE_SUCCEED: The variable value is retrieved successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[varName]")

Description

Succeeded in recovering the script variable in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[varName] Indicates a variable name.

Possible Causes

Succeeded in recovering the script variable in the execution phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CONTEXT_SAVE_CONDITION_FAIL

Message

OPSA/3/OPS_CONTEXT_SAVE_CONDITION_FAIL: Failed to save the variable value using the script. (Script="[script-name]", variable="[varName]")

Description

Failed to save the script variable in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[varName] Indicates a variable name.

Possible Causes

In the subscription phase of the user script, parameters of the Saving Script Variable API (ops.context.save) are incorrect or the number of variables saved on the device has reached the upper limit.

Procedure

  1. In the subscription phase of the user script, parameters of the Saving Script Variable API (ops.context.save) are incorrect or the number of variables saved on the device has reached the upper limit (a maximum of 100 script variables can be saved). You need to modify the script.

OPSA/6/OPS_CONTEXT_SAVE_CONDITION_SUCCEED

Message

OPSA/6/OPS_CONTEXT_SAVE_CONDITION_SUCCEED: The variable value is saved successfully using the script. (Script="[script-name]", variable="[varName]", value="[value]")

Description

Succeeded in saving the script variable in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[varName] Indicates a variable name.
[value] Indicates a variable value.

Possible Causes

Succeeded in saving the script variable in the subscription phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CONTEXT_SAVE_EXECUTE_FAIL

Message

OPSA/3/OPS_CONTEXT_SAVE_EXECUTE_FAIL: Failed to save the variable using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[varName]")

Description

Failed to save the script variable in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[varName] Indicates a variable name.

Possible Causes

In the execution phase of the user script, parameters of the Saving Script Variable API (ops.context.save) are incorrect or the number of variables saved on the device has reached the upper limit.

Procedure

  1. In the execution phase of the user script, parameters of the Saving Script Variable API (ops.context.save) are incorrect or the number of variables saved on the device has reached the upper limit (a maximum of 100 script variables can be saved). You need to modify the script.

OPSA/6/OPS_CONTEXT_SAVE_EXECUTE_SUCCEED

Message

OPSA/6/OPS_CONTEXT_SAVE_EXECUTE_SUCCEED: The variable is saved successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[varName]", value="[value]")

Description

Succeeded in saving the script variable in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[varName] Indicates a variable name.
[value] Indicates a variable value.

Possible Causes

Succeeded in saving the script variable in the execution phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_CORRELATE_FAIL

Message

OPSA/3/OPS_CORRELATE_FAIL: Failed to correlate events using the script. (Script="[script-name]", events to correlate="[expression]")

Description

Failed to subscribe the combined event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[expression] Indicates a combined condition expression.

Possible Causes

In the subscription phase of the user script, parameters of the Multi-Condition Combination API (ops.correlate) are incorrect or a single simple event failed to be registered.

Procedure

  1. In the subscription phase of the user script, parameters of the Multi-Condition Combination API (ops.correlate) are incorrect or a single simple event failed to be registered. You need to modify the script.

OPSA/6/OPS_CORRELATE_SUCCEED

Message

OPSA/6/OPS_CORRELATE_SUCCEED: Events are correlated successfully using the script. (Script="[script-name]", events to correlate="[expression]")

Description

Succeeded in subscribing the combined event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[expression] Indicates a combined condition expression.

Possible Causes

Succeeded in subscribing the combined event using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_EVENT_DISCARD_QUEUEFULL

Message

OPSA/3/OPS_EVENT_DISCARD_QUEUEFULL: Failed to execute the script because "the script queue is full". (Script="[script-name]", event="[event-name]", instance=[instance-id])

Description

Failed to execute the script because the script queue is full.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.

Possible Causes

The script queue is full.

Procedure

  1. Run the ops uninstall file file-name command to delete unnecessary scripts or reduce the number of times this script will be triggered.

OPSA/3/OPS_EVENT_DISCARD_SCRIPTSTATE

Message

OPSA/3/OPS_EVENT_DISCARD_SCRIPTSTATE: Failed to execute the script because "the script is suspended or stopped". (Script="[script-name]", event="[event-name]", instance=[instance-id])

Description

Failed to execute the script because the assistant of the Python script was stopped or the OPS maintenance assistant function was disabled.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.

Possible Causes

The assistant of the Python script was stopped or the OPS maintenance assistant function was disabled.

Procedure

  1. Run the undo assistant scheduler suspend command to enable the OPS maintenance assistant function.
  2. Run the undo shutdown script-assistant script-name command to start the Python script assistant.

OPSA/6/OPS_EVENT_TRIGGER

Message

OPSA/6/OPS_EVENT_TRIGGER: An event has been triggered. (Script="[script-name]", event="[event-name]", instance=[instance-id])

Description

Succeeded in triggering the event subscribed in the user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.

Possible Causes

Succeeded in triggering the event subscribed in the user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_GET_ENV_CONDITION_FAIL

Message

OPSA/3/OPS_GET_ENV_CONDITION_FAIL: Failed to obtain the environment variable using the script. (Script="[script-name]", variable="[variable-name]")

Description

Failed to obtain the environment variable using a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[variable-name] Indicates an environment variable name.

Possible Causes

In the subscription phase of the user script, parameters of the Obtaining Environment Variable API (ops.environment.get) are incorrect or the environment variable does not exist.

Procedure

  1. In the subscription phase of the user script, parameters of the Obtaining Environment Variable API (ops.environment.get) are incorrect or the environment variable does not exist. You need to modify the script.

OPSA/6/OPS_GET_ENV_CONDITION_SUCCEED

Message

OPSA/6/OPS_GET_ENV_CONDITION_SUCCEED: The environment variable is obtained successfully using the script. (Script="[script-name]", variable="[variable-name]", value="[variable-value]")

Description

Succeeded in obtaining the environment variable using a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[variable-name] Indicates an environment variable name.
[variable-value] Indicates an environment variable value.

Possible Causes

Succeeded in obtaining the environment variable using a user script in the subscription phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_GET_ENV_EXECUTE_FAIL

Message

OPSA/3/OPS_GET_ENV_EXECUTE_FAIL: Failed to obtain the environment variable using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[variable-name]")

Description

Failed to obtain the environment variable using a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[variable-name] Indicates an environment variable name.

Possible Causes

In the execution phase of the user script, parameters of the Obtaining Environment Variable API (ops.environment.get) are incorrect or the environment variable does not exist.

Procedure

  1. In the execution phase of the user script, parameters of the Obtaining Environment Variable API (ops.environment.get) are incorrect or the environment variable does not exist. You need to modify the script.

OPSA/6/OPS_GET_ENV_EXECUTE_SUCCEED

Message

OPSA/6/OPS_GET_ENV_EXECUTE_SUCCEED: The environment variable is obtained successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], variable="[variable-name]", value="[variable-value]")

Description

Succeeded in obtaining the environment variable using a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[variable-name] Indicates an environment variable name.
[variable-value] Indicates an environment variable value.

Possible Causes

Succeeded in obtaining the environment variable using a user script in the execution phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_PROCESS_CREATE_FAIL

Message

OPSA/3/OPS_PROCESS_CREATE_FAIL: Failed to create the process using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id])

Description

Failed to create a process using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.

Possible Causes

An error occurs during script execution.

Procedure

  1. Run the display ops error [ name assistant-name ] command to check the script execution error and then modify the script.

OPSA/6/OPS_PROCESS_CREATE_SUCCEED

Message

OPSA/6/OPS_PROCESS_CREATE_SUCCEED: The process is successfully created using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], PID=[PID])

Description

Succeeded in creating a process using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[PID] Indicates a process ID.

Possible Causes

The process has been created successfully using the script, and the script begins to be executed.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/6/OPS_PROCESS_END

Message

OPSA/6/OPS_PROCESS_END: The system has finished executing the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], PID=[PID])

Description

Succeeded in executing the user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[PID] Indicates a process ID.

Possible Causes

Succeeded in executing the user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_RESULT_EXCEPTION

Message

OPSA/3/OPS_RESULT_EXCEPTION: An exception occurred when executing the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], exception="[reason]")

Description

An error occurs during user script execution.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[reason] Indicates a reason for the error occurring during user script execution.

Possible Causes

An error may occur on the user script during user script execution.

Procedure

  1. Run the display ops error [ name assistant-name ] command to check the script execution error and then modify the script.

OPSA/6/OPS_RESULT_USER

Message

OPSA/6/OPS_RESULT_USER: The script returned the user result. (Script="[script-name]", event="[event-name]", instance=[instance-id], usersresult=[user-result], scriptresult="[script-result]")

Description

The user script execution result is returned.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[user-result] Function execution result in the user script.
[script-result] User script execution result.

Possible Causes

User script execution ends, and the script execution result is returned.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_ROUTE_SUBSCRIBE_FAIL

Message

OPSA/3/OPS_ROUTE_SUBSCRIBE_FAIL: Failed to subscribe to the routing event using the script. (Script="[script-name]", event="[event-name]", network address="[network]", mask length=[maskLen], min. length=[minLen], max. length=[maxLen], NE length=[neLen], operation type="[optype]", protocol="[protocol]")

Description

Failed to subscribe the route event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[network] Indicates a route prefix.
[maskLen] Indicates a mask length.
[minLen] Indicates the shortest mask length.
[maxLen] Indicates the longest mask length.
[neLen] Indicates the unmatching mask length.
[optype] Indicates the route change event type.
[protocol] Indicates protocol attributes.

Possible Causes

In the subscription phase of the user script, parameters of the Route Change Event Subscription API (ops.route.subscribe) are incorrect.

Procedure

  1. In the subscription phase of the user script, parameters of the Route Change Event Subscription API (ops.route.subscribe) are incorrect. You need to modify the script.

OPSA/6/OPS_ROUTE_SUBSCRIBE_SUCCEED

Message

OPSA/6/OPS_ROUTE_SUBSCRIBE_SUCCEED: The routing event is subscribed successfully using the script. (Script="[script-name]", event="[event-name]", network address="[network]", mask length=[maskLen], min. length=[minLen], max. length=[maxLen], NE length=[neLen], operation type="[optype]", protocol="[protocol]")

Description

Succeeded in subscribing the route event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[network] Indicates a route prefix.
[maskLen] Indicates a mask length.
[minLen] Indicates the shortest mask length.
[maxLen] Indicates the longest mask length.
[neLen] Indicates the unmatching mask length.
[optype] Indicates the route change event type.
[protocol] Indicates protocol attributes.

Possible Causes

Succeeded in subscribing the route event using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_SNMP_CONDITION_FAIL

Message

OPSA/3/OPS_SNMP_CONDITION_FAIL: Failed to obtain the MIB object using the script. (Script="[script-name]", object="[object]")

Description

Failed to obtain detailed information about a leaf object with the specified OID using a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[object] Indicates a MIB object.

Possible Causes

In the subscription phase of the user script, parameters of the Obtaining Device Information Through SNMP (get) API (ops.snmp.get) are incorrect or the OID does not exist.

Procedure

  1. In the subscription phase of the user script, parameters of the Obtaining Device Information Through SNMP (get) API (ops.snmp.get) are incorrect or the OID does not exist (For how to obtain the MIB object OID, see S12700 V200R013C00 MIB Reference). You need to modify the script.

OPSA/6/OPS_SNMP_CONDITION_SUCCEED

Message

OPSA/6/OPS_SNMP_CONDITION_SUCCEED: The MIB object is obtained successfully using the script. (Script="[script-name]", object="[object]", value="[oid]")

Description

Succeeded in obtaining detailed information about a leaf object with the specified OID using a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[object] Indicates a MIB object.
[oid] Indicates the MIB object OID.

Possible Causes

Succeeded in obtaining detailed information about a leaf object with the specified OID using a user script in the subscription phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_SNMP_CONDITION_NEXT_FAIL

Message

OPSA/3/OPS_SNMP_CONDITION_NEXT_FAIL: Failed to obtain the next MIB object using the script. (Script="[script-name]", current MIB object="[object]")

Description

Failed to obtain detailed information about the next object for a leaf object with the specified OID a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[object] Indicates a MIB object.

Possible Causes

In the subscription phase of the user script, parameters of the Obtaining Device Information Through SNMP (getnext) API (ops.snmp.getnext) are incorrect or the OID does not exist.

Procedure

  1. In the subscription phase of the user script, parameters of the Obtaining Device Information Through SNMP (getnext) API (ops.snmp.getnext) are incorrect or the OID does not exist (For how to obtain the MIB object OID, see S12700 V200R013C00 MIB Reference). You need to modify the script.

OPSA/6/OPS_SNMP_CONDITION_NEXT_SUCCEED

Message

OPSA/6/OPS_SNMP_CONDITION_NEXT_SUCCEED: The next MIB object is obtained successfully using the script. (Script="[script-name]", current object="[object1]", next object value="[oid]", next object="[object2]")

Description

Succeeded in obtaining detailed information about the next object for a leaf object with the specified OID using a user script in the subscription phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[object1] Indicates a MIB object.
[oid] Indicates the OID of the next MIB object.
[object2] Indicates the next MIB object.

Possible Causes

Succeeded in obtaining detailed information about the next object for a leaf object with the specified OID using a user script in the subscription phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_SNMP_EXECUTE_FAIL

Message

OPSA/3/OPS_SNMP_EXECUTE_FAIL: Failed to obtain the MIB object using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], object="[object]")

Description

Failed to obtain detailed information about a leaf object with the specified OID using a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[object] Indicates a MIB object.

Possible Causes

In the execution phase of the user script, parameters of the Obtaining Device Information Through SNMP (get) API (ops.snmp.get) are incorrect or the OID does not exist.

Procedure

  1. In the execution phase of the user script, parameters of the Obtaining Device Information Through SNMP (get) API (ops.snmp.get) are incorrect or the OID does not exist (For how to obtain the MIB object OID, see S12700 V200R013C00 MIB Reference). You need to modify the script.

OPSA/6/OPS_SNMP_EXECUTE_SUCCEED

Message

OPSA/6/OPS_SNMP_EXECUTE_SUCCEED: The MIB object is obtained successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], object="[object]", value="[oid]")

Description

Succeeded in obtaining detailed information about a leaf object with the specified OID using a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[object] Indicates a MIB object.
[oid] Indicates the MIB object OID.

Possible Causes

Succeeded in obtaining detailed information about a leaf object with the specified OID using a user script in the execution phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_SNMP_EXECUTE_NEXT_FAIL

Message

OPSA/3/OPS_SNMP_EXECUTE_NEXT_FAIL: Failed to obtain the next MIB object using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], current object="[object]")

Description

Failed to obtain detailed information about the next object for a leaf object with the specified OID a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[object] Indicates a MIB object.

Possible Causes

In the execution phase of the user script, parameters of the Obtaining Device Information Through SNMP (getnext) API (ops.snmp.getnext) are incorrect or the OID does not exist.

Procedure

  1. In the execution phase of the user script, parameters of the Obtaining Device Information Through SNMP (getnext) API (ops.snmp.getnext) are incorrect or the OID does not exist (For how to obtain the MIB object OID, see S12700 V200R013C00 MIB Reference). You need to modify the script.

OPSA/6/OPS_SNMP_EXECUTE_NEXT_SUCCEED

Message

OPSA/6/OPS_SNMP_EXECUTE_NEXT_SUCCEED: The next MIB object is obtained successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], current object="[object1]", next object value="[oid]", next object="[object2]")

Description

Succeeded in obtaining detailed information about the next object for a leaf object with the specified OID using a user script in the execution phase.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[object1] Indicates a MIB object.
[oid] Indicates the OID of the next MIB object.
[object2] Indicates the next MIB object.

Possible Causes

Succeeded in obtaining detailed information about the next object for a leaf object with the specified OID using a user script in the execution phase.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/6/OPS_TERMINAL_READ_OVERTIME

Message

OPSA/6/OPS_TERMINAL_READ_OVERTIME: The script request for user input from the terminal timed out. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal="[vty]")

Description

Reading user input from the terminal using a user script times out.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[vty] Indicates a terminal.

Possible Causes

In the execution phase of the user script, the timeout parameter of the Reading User Input from a Terminal API (ops.terminal.read) is too small or no input exists.

Procedure

  1. In the execution phase of the user script, the timeout parameter of the Reading User Input from a Terminal API (ops.terminal.read) is too small or no input exists. You need to modify the script or input information.

OPSA/6/OPS_TERMINAL_READ_SUCCEED

Message

OPSA/6/OPS_TERMINAL_READ_SUCCEED: The script has obtained the user input from the terminal successfully. (Script="[script-name]", event="[event-name]", instance=[instance-id], terminal="[vty]", input="[msg]")

Description

Succeeded in reading user input from the terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[vty] Indicates a terminal.
[msg] Indicates the information input.

Possible Causes

Succeeded in reading user input from the terminal using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_TERMINAL_WRITE_FAIL

Message

OPSA/3/OPS_TERMINAL_WRITE_FAIL: Failed to display the string on the terminal using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], string="[msg]", terminal="[vty]")

Description

Failed to display prompt information to a terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[msg] Indicates the prompt information to be displayed.
[vty] Indicates a terminal.

Possible Causes

In the execution phase of the user script, parameters of the Displaying Prompt Information to a Terminal API (ops.terminal.write) are incorrect.

Procedure

  1. In the execution phase of the user script, parameters of the Displaying Prompt Information to a Terminal API (ops.terminal.write) are incorrect. You need to modify the script.

OPSA/6/OPS_TERMINAL_WRITE_SUCCEED

Message

OPSA/6/OPS_TERMINAL_WRITE_SUCCEED: The string is displayed on the terminal successfully using the script. (Script="[script-name]", event="[event-name]", instance=[instance-id], string="[msg]", terminal="[vty]")

Description

Succeeded in displaying prompt information to a terminal using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[event-name] Indicates an event name.
[instance-id] Indicates an instance ID.
[msg] Indicates the prompt information to be displayed.
[vty] Indicates a terminal.

Possible Causes

Succeeded in displaying prompt information to a terminal using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_TIMER_SUBSCRIBE_CRON_FAIL

Message

OPSA/3/OPS_TIMER_SUBSCRIBE_CRON_FAIL: Failed to subscribe to the CRON timer event using the script. (Script="[script-name]", timer="[timer-type]", event="[event-name]", crontime="[crontime]")

Description

Failed to subscribe the cron timer event using a script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[timer-type] Indicates a timer type.
[event-name] Indicates an event name.
[crontime] Indicates the cron timer time.

Possible Causes

In the user script, the cron timer parameters of the Timer Event Subscription API are incorrect.

Procedure

  1. In the user script, the cron timer parameters of the Timer Event Subscription API are incorrect. You need to modify the script.

OPSA/6/OPS_TIMER_SUBSCRIBE_CRON_SUCCEED

Message

OPSA/6/OPS_TIMER_SUBSCRIBE_CRON_SUCCEED: The CRON timer event is subscribed successfully using the script. (Script="[script-name]", timer="[timer-type]", event="[event-name]", crontime="[crontime]")

Description

Succeeded in subscribing to the cron timer event using a script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[timer-type] Indicates a timer type.
[event-name] Indicates an event name.
[crontime] Indicates the cron timer time.

Possible Causes

Succeeded in subscribing to the cron timer event using a script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_TIMER_SUBSCRIBE_NUM_FAIL

Message

OPSA/3/OPS_TIMER_SUBSCRIBE_NUM_FAIL: Failed to subscribe to the timer event using the script. (Script="[script-name]", timer="[timer-type]", event="[event-name]", period=[timelength])

Description

Failed to subscribe to the common timer event using a script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[timer-type] Indicates a timer type.
[event-name] Indicates an event name.
[timelength] Indicates the timer time.

Possible Causes

In the user script, the common timer parameters of the Timer Event Subscription API are incorrect.

Procedure

  1. In the user script, the common timer parameters of the Timer Event Subscription API are incorrect. You need to modify the script.

OPSA/6/OPS_TIMER_SUBSCRIBE_NUM_SUCCEED

Message

OPSA/6/OPS_TIMER_SUBSCRIBE_NUM_SUCCEED: The timer event is successfully subscribed using the script. (Script="[script-name]", timer="[timer-type]", event="[event-name]", period=[timelength])

Description

Succeeded in subscribing to the common timer event using a script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[timer-type] Indicates a timer type.
[event-name] Indicates an event name.
[timelength] Indicates the timer time.

Possible Causes

Succeeded in subscribing to the common timer event using a script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_TRIGGER_SUBSCRIBE_FAIL

Message

OPSA/3/OPS_TRIGGER_SUBSCRIBE_FAIL: Failed to subscribe to the trigger event using the script. (Script="[script-name]", trigger count=[occurs], period=[period], delay=[delay], suppress=[suppress])

Description

Failed to subscribe the triggered event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[occurs] Indicates the number of times an event meets triggering conditions.
[period] Indicates the detection period.
[delay] Indicates the delay in executing a script.
[suppress] Indicates the number of times the execution of the event in a script is suppressed.

Possible Causes

In the subscription phase of the user script, parameters of the Combined Event Trigger API (ops.trigger) are incorrect.

Procedure

  1. In the subscription phase of the user script, parameters of the Combined Event Trigger API (ops.trigger) are incorrect. You need to modify the script.

OPSA/6/OPS_TRIGGER_SUBSCRIBE_SUCCEED

Message

OPSA/6/OPS_TRIGGER_SUBSCRIBE_SUCCEED: The trigger event is subscribed successfully using the script. (Script="[script-name]", trigger count=[occurs], period=[period], delay=[delay], suppress=[suppress])

Description

Succeeded in subscribing the triggered event using a user script.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a user script name.
[occurs] Indicates the number of times an event meets triggering conditions.
[period] Indicates the detection period.
[delay] Indicates the delay in executing a script.
[suppress] Indicates the number of times the execution of the event in a script is suppressed.

Possible Causes

Succeeded in subscribing the triggered event using a user script.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/3/OPS_WAIT_FAIL

Message

OPSA/3/OPS_WAIT_FAIL: Failed to set the script to waiting state. (Script="[script-name]", event="[event-name]")

Description

Failed to set the resident script to the waiting state.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.

Possible Causes

An error occurs in the resident script.

Procedure

  1. An error occurs in the resident script. Run the undo script-assistant python script-name command to delete the Python script assistant, and then run the script-assistant python script-name command to reconfigure the script assistant.

OPSA/6/OPS_WAIT_SUCCEED

Message

OPSA/6/OPS_WAIT_SUCCEED: The script is successfully set to waiting state. (Script="[script-name]", event="[event-name]")

Description

The resident script is set to the waiting state.

Parameters

Parameter Name Parameter Meaning
[script-name] Indicates a script name.
[event-name] Indicates an event name.

Possible Causes

The resident script is set to the waiting state.

Procedure

  1. This log message is informational only, and no action is required.

OPSA/2/SCRIPT_LOG

Message

OPSA/2/SCRIPT_LOG: OPS: [message] (user="[script-name]", session=[session-id])

NOTE:

This log is a user-defined log.

Description

A user invokes the API (ops.syslog) to record a user-defined log at level 2 (critical).

Parameters

Parameter Name Parameter Meaning
[message] Indicates the log message.
[script-name] Indicates a script name.
[session-id] Indicates an instance ID.

Possible Causes

A user invokes the API (ops.syslog) to record a user-defined log at level 2 (critical).

Procedure

  1. Process the log according to the user-defined log content.

OPSA/3/SCRIPT_LOG

Message

OPSA/3/SCRIPT_LOG: OPS: [message] (user="[script-name]", session=[session-id])

NOTE:

This log is a user-defined log.

Description

A user invokes the API (ops.syslog) to record a user-defined log at level 3 (error).

Parameters

Parameter Name Parameter Meaning
[message] Indicates the log message.
[script-name] Indicates a script name.
[session-id] Indicates an instance ID.

Possible Causes

A user invokes the API (ops.syslog) to record a user-defined log at level 3 (error).

Procedure

  1. Process the log according to the user-defined log content.

OPSA/4/SCRIPT_LOG

Message

OPSA/4/SCRIPT_LOG: OPS: [message] (user="[script-name]", session=[session-id])

Description

A user invokes the API (ops.syslog) to record a user-defined log at level 4 (warning), or an error occurs in script parameter verification when the Python script assistant is configured.

Parameters

Parameter Name Parameter Meaning
[message] Indicates the log message.
[script-name] Indicates a script name.
[session-id] Indicates an instance ID.

Possible Causes

A user invokes the API (ops.syslog) to record a user-defined log at level 4 (warning), or an error occurs in script parameter verification when the Python script assistant is configured.

Procedure

  1. Process the log according to the user-defined log content, or change the parameter in the Python script according to the log.

OPSA/6/SCRIPT_LOG

Message

OPSA/6/SCRIPT_LOG: OPS: [message] (user="[script-name]", session=[session-id])

NOTE:

This log is a user-defined log.

Description

A user invokes the API (ops.syslog) to record a user-defined log at level 6 (informational).

Parameters

Parameter Name Parameter Meaning
[message] Indicates the log message.
[script-name] Indicates a script name.
[session-id] Indicates an instance ID.

Possible Causes

A user invokes the API (ops.syslog) to record a user-defined log at level 6 (informational).

Procedure

  1. Process the log according to the user-defined log content.
Translation
Download
Updated: 2019-04-09

Document ID: EDOC1100065665

Views: 5616

Downloads: 15

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next