|
|
This section gives the list of common error messages that may be received from the TL1Agent both in Standalone TL1 Agents and Multi-Protocol TL1 Agents, their possible causes and solutions.
"Invalid Target Identifier"
Reason: The Target ID mentioned in the Input Message is an invalid one. This can occur in both Standalone and Multi-Protocol agents.
Solution: Send the correct TargetID or ignore the TargetID. By default, the TargetID is the machine name. It can also be set by the method setTargetId(String) provided in WebNMSTL1Agent.java (or AgentName specified in the Compiler Code Generation Settings).
"Illegal Command Code"
Reason: Command specified in the Command Code part is not registered with the command registry. This can occur in both Standalone and Multi-Protocol agents.
Solution: Check whether the specified Command is valid and registered.
"Block Missing"
Reason: One or more blocks are missing in the Input Message. This can occur in both Standalone and Multi-Protocol agents.
Solution: Check the Input Message.
"Invalid Command"
One of the following has occurred
Reason 1: C-Tag is missing
If C-Tag is not specified in the field mentioned for it in the TL1Browser, the Browser itself sends the message with a C-Tag. If the message is sent with the option "Receive as String" in the settings, the browser does not set the C-Tag if not specified. This can occur in both Standalone and Multiprotocol agents.
Solution: Check the Input Message for proper C-Tag.
Reason 2: Error in doAction() Method
Error has occurred in the doAction() method and has not returned a TL1AgentResponseInfo object. This can occur in both Standalone and Multi-Protocol agents.
Solution: Check the doAction() method for any exceptions.
"Authentication Failed"
Reason: The Authentication is enabled and either the login code sent is wrong or the user name and/or the password are wrong. This can happen even when the user is logged out and tries to access the NE without Logging in again. This can occur in both Standalone and Multiprotocol agents.
Solution: Give proper Login Code (Auth Code) with valid user name and password.
"Data Missing"
Reason: Some data is missing in the Message Payload block of the Input Message. This can occur in Standalone Agents as well as Multi-Protocol agents for SET, CREATE, or DELETE requests.
Solution: Give information in the Message Payload block if necessary.
"Invalid Access Identifier"
Reason: The Access Identifier value sent in the Input Message is not valid according to the defined syntax. This can occur in both Standalone and Multi-Protocol agents.
Solution: Give proper Login Code (Auth Code) with valid user name and password. Also, correct AID should be specified in the Input message to be sent to the TL1 Agent
No Such Object"
Reason: The data specified in the AccessID part is not found in the Command Code Registry. This can occur in both Multi-Protocol and Standalone TL1 Agents.
Solution: In MPA, Check whether the scalar or table queried is registered with the MBean Server. In Standalone TL1 Agents, check whether the value/entry queried is present in the respective registry. e.g. Check UserSecurity.txt if an UID entry is not present.
"Read Only"
Reason: The attribute for which a SET or a CREATE is sent is a Read only attribute. This can occur in Multi-Protocol agents.
Solution: No solution. Cannot perform a SET for a Read only attribute.
"Parameter Extra"
Reason: This occurs if a GETALL is done with extra parameters in the Message Payload Block. This can occur in both Multi-Protocol and Standalone TL1 Agents.
Solution: Check for the number of parameters in the Message Payload block. An example in Standalone TL1 Agents is in CANC-USER, when the MPB is specified. Here also check for the number of parameters in the Message Payload block.
"Specified Object Entity does not exist"
Reason: This error occurs if a GETALL is done on a Table where the index / startindex mentioned in the Message Payload block is above the actual number of rows present in the table. This can occur in both Standalone and Multi-Protocol agents.
Solution: Check for the parameters in the Message Payload block.
"Data not valid"
Reason: The value specified in the Message Payload block is not a valid one. This can occur in both Standalone and Multi-Protocol agents.
Solution: Check for the parameters in the Message Payload block. If the Agent is Multi-Protocol, also check for the type of the attribute and the value sent.
"Index is Missing"
Reason: The index is not specified for a GET for a table, or a SET for a table or a DELETE for a table. This can occur in Multi-Protocol agents.
Solution: Provide the index values in the Message Payload block.
"Access Not Supported"
Reason: The MBean for which a request was sent is not accessible. This can occur in both Standalone and Multi-Protocol agents. Another reason is if the user has no privileges in executing a command when command security is enabled.
Solution: The attribute is not accessible.
"Invalid external index"
Reason: The Table's external index queried is invalid / does not exist. This can occur in Multi-protocol agents.
Solution: Give a valid external index.
"Row already exists"
Reason: This occurs when trying to CREATE a row, which already exists with the same instance. This can occur in Multi-Protocol agents.
Solution: Create a row with a different instance (index).
"Invalid Index"
Reason: The specified index for the table is invalid, i.e., its given type, or it does not exist. This can occur in Multi protocol agents.
Solution: Create a row with a valid index.
"Already logged in"
Reason: This may occur when a user is already logged in and trying to log in again with the same or different user name. This can occur in both Standalone and Multi-Protocol agents.
Solution: Log out and then log in.
|
|