|
|
The is appendix describes the log messages that are displayed by the MGC. There are more than 1000 messages possible. Only slightly more than 100 currently are documented.
MESSAGE:
CP_ERR_DUP_ENDPOINT: %s: duplicate endpoint %s, %s
DESCRIPTION:
Configuration error message that the specified bearer channel has the same endpoint as a previously-specified one.
PARAMETERS:
%s: class::method
%s: existing bearChan
%s: bearChan with dup endpoint
MESSAGE:
CP_ERR_HUNG_CXN: %s: bearChan %s hung on VSF %C
DESCRIPTION:
Error message that this bearer channel is still set as `in use' on the VSF, though the call that created the connection has ended.
PARAMETERS:
%s: class::method
%s: bearChan ID
%C: VSF ID
MESSAGE:
CP_ERR_MDL_MSG_PARSE: %s: message parse failed, call ID %d
DESCRIPTION:
Error message that engine cannot parse a message from MDL.
PARAMETERS:
%s: class::method
%d: call ID
MESSAGE:
CP_INFO_SET_ALARM: Alarm set: sigPath=%C, %s
DESCRIPTION:
This log is generated to further specify the scope of the alarm generated for the signalling path noted.
PARAMETERS:
%C: component name of the SigPath
%s: span, bearer channel, and alarmIndex of alarm, where, span=<span>, bc=<bearer channel>, alarmIndex=nnn
MESSAGE:
CP_WARN_STATE_MISMATCH: %s: connection %s doesn't match response message %u
DESCRIPTION:
Warning message that this connection is in an unexpected state when receiving a response from VSF.
PARAMETERS:
%s: class::method
%s: cxn ID, state
%u: msg type
MESSAGE:
CP_WARN_WRITE_SIGPATH: %s: cannot write to %C, state %u
DESCRIPTION:
Warning message that this connection sigPath is not in service.
PARAMETERS:
%s: class::method
%C: sigPath ID
%u: sigPath state
MESSAGE:
ENV_CRIT_LOGSRVR_REREAD_REQUEST: Logger requested to reread component.dat
DESCRIPTION:
The LogServer has been notified that it should reread the components file in order to pick up any updates that might have been applied so that the component id translation to MML name is accurate.
 |
Note This message is reserved for use by the log server only. |
MESSAGE:
ENV_CRIT_PROC_ERR: Unexpected return from %s stage, status = %d (%s)
DESCRIPTION:
Process initialization failure message in the XEProcShell.
PARAMETERS:
%s: One of `Pre-init', `init', `Post-init', `Run', `Pre-finalize', `Finalize' or `Post-finalize'
%d: XE Status code - reason for the failure
%s: Status code converted to an error message string
MESSAGE:
ENV_ERR_LOGCLNT_LOST_CONNECTION: %s lost connection to Log Server
DESCRIPTION:
This message is written by the LogClient process to indicate that it has lost connection to the Log Server process. The Log Client will attempt to regain the connection on a regular basis (every 10 seconds in Elan 4MR)
|
Note This message is reserved for use solely by log client code. |
PARAMETERS:
%s: Log Client process identity
MESSAGE:
ENV_ERR_LOGCLNT_NOTCON: %s unable to connect to Log Server
DESCRIPTION:
This message is written by the Log Client process to indicate that it was unable to connect to the Log Server
|
Note This message is reserved for use solely by log client code. |
PARAMETERS:
%s: Log Client process identity
MESSAGE:
ENV_ERR_LOGSRVR_COMP_REREAD: Log Server failed to reread components.dat file
DESCRIPTION:
This message is written by the LogServer process to indicate that it failed to reread the components.dat file.
|
Note This message is reserved for use by the log server only. |
MESSAGE:
ENV_ERR_LOGSRVR_MISMATCH: Log Server encounted parameter mismatch for message: %s
DESCRIPTION:
This message is written by the LogServer process to indicate that a substitution paramater mismatch occurred (supplied string, but spec in messages indicated integer).
|
Note This message is reserved for use by the log server only. |
PARAMETERS:
%s: copy of entire message template
MESSAGE:
ENV_ERR_LOGSRVR_ROTATE: Log Server failed to rotate active log file
DESCRIPTION:
This message is written by the LogServer process to indicate a log rotation attempt has failed.
|
Note This message is reserved for use by the log server only. |
MESSAGE:
ENV_ERR_LOGSRVR_SOCKET: Log Server failed to find local socket address %s
DESCRIPTION:
This message is written by the LogServer to indicate that is is unable to open a local socket for client process communication. The Log Server exits in this case.
|
Note This message is reserved for use by the log server only. |
PARAMETERS:
%s: socket address attempted to be used for IPC communication
MESSAGE:
GEN_CRIT_AB_SWITCH_INIT_FAIL: %s Error initializing A/B switch, switchover failed - will retry every %d seconds
DESCRIPTION:
This message is logged when the AB Switch initialization fails during switch over
PARAMETERS:
%s: Classmethod
%d: period in seconds, after which a retry will be attempted
MESSAGE:
GEN_CRIT_PINIT: %s: Process %s initialization failed. %s
DESCRIPTION:
Process initialization failure message.
PARAMETERS:
%s: class::method
%s: process name
%s: specific reason for failure
MESSAGE:
GEN_ERR_AB_SWITCH_MODE_SET_FAIL: Cannot set %s mode (errno: %d), will retry every %d seconds
DESCRIPTION:
This message is logged when the system fails to set the mode of the AB Switch
PARAMETERS:
%s: name of the mode
%d: error no
%d: period in seconds, after which a retry will be attempted
MESSAGE:
GEN_ERR_AB_SWITCH_OPEN_FAIL: Cannot open %s (errno: %d), will retry every %d seconds
DESCRIPTION:
This message is logged when the system fails to open the AB Switch port
PARAMETERS:
%s: name of the device (path) to which the AB Switch is connected
%d: error no
%d: period in seconds, after which a retry will be attempted
MESSAGE:
GEN_ERR_AB_SWITCH_SIG_FAIL: Could not set %s on %s (errno: %d)
DESCRIPTION:
This message is logged to indicate the failure to send a sequence of pulses that control the A/B switch
PARAMETERS:
%s: <signal name> (RTS,DTR etc.)
%s: name of the device (path) to which the AB Switch is connected
%d: errno
MESSAGE:
GEN_ERR_BUFFOV: %s buffer overflow
DESCRIPTION:
This message indicates an error due to overflow of an internal buffer.
PARAMETERS:
%s: name of the buffer
MESSAGE:
GEN_ERR_FOVERD: %s
DESCRIPTION:
This log message is generated by foverd to reflect the pertinent fault tolerant error information
PARAMETERS:
%s: error string
MESSAGE:
GEN_ERR_HA_MSO: Cannot comply with Manual Switch Over request. Reason %s
DESCRIPTION:
This log message is generated by the process manager when a request for Manual Switchover cannot be completed.
PARAMETERS:
%s: reason string
MESSAGE:
GEN_ERR_HA_PFAIL: Process %s failed to respond to %s command. Reason %s
DESCRIPTION:
This message is used by components that receive an HA command from the process manager but which fail to comply with the HA command received.
PARAMETERS:
%s: process name
%s: command received <Active/Standby/OOS/FSO/CSO>
%s: reason string to explain reason for non-compliance
MESSAGE:
GEN_ERR_HA_RSP: Received a NAK for Platform State from %s
DESCRIPTION:
This is an error message logged by the process manager when a component fails to respond favorably to an HA command
PARAMETERS:
%s: component name
MESSAGE:
GEN_ERR_IFINIT_FAIL: Could not initialize %s: %s
DESCRIPTION:
This message is logged to indicate the failure to initialize an interface such as the alarm manager, etc
PARAMETERS:
%s: interface name
%s: format string used for logging a symbolic status code
MESSAGE:
GEN_ERR_LIBCFAIL: C Library call %s failure %d
DESCRIPTION:
This message indicates an error was returned by a C library function.
PARAMETERS:
%s: name of the C Library function
%d: error code
MESSAGE:
GEN_ERR_OBJCRT_FAIL: compId %C: Instantiation of %s failed in %s
DESCRIPTION:
Used when object instantiation fails
PARAMETERS:
%C: Component Id
%s: name of the object being instantiated
%s: is class::metthod name
MESSAGE:
GEN_ERR_UNKN_COMPID: compId %C: unknown component Id %C
DESCRIPTION:
This message is used to incase of getting a invalid component id
PARAMETERS:
%C: component id of the component that generates the message.
%C: component id which is invalid
MESSAGE:
GEN_ERR_UNKN_STATUS: compId %C: unknown status %d
DESCRIPTION:
This message is used when a component id is asked to goto unknown status
PARAMETERS:
%C: component id
%d: the unknown status
MESSAGE:
GEN_ERR_UNKN_TXN: compId %C: unknown Transaction Type %d
DESCRIPTION:
This message is used to incase of getting a invalid transation type from engine
PARAMETERS:
%C: component id to which the connection req comes from engine
%d: the transaction type which is found as invalid
MESSAGE:
GEN_INFO_FOVERD: %s
DESCRIPTION:
This log message is generated by foverd to reflect the pertinent fault tolerant information
PARAMETERS:
%s: info string
MESSAGE:
GEN_INFO_HA_ACTION: %s: handling HA command %s %s
DESCRIPTION:
This message is used by components that receive an HA command from the process manager. When the process manager propagates High Availability commands to transition the platform to a certain Active / Standby state, these commands are received by different components like Alarm Manager, Engine, Replicator, IOCM, etc. These messages are used by these components when handling such commands.
PARAMETERS:
%s: name of the process
%s: HA command <Standby/OOS/FSO/CSO>
%s: node for which this command is intended <local/remote>
MESSAGE:
GEN_INFO_HA_ACT_OOS: Platform ACTIVE: Commanded into Standby will transit to OOS first
DESCRIPTION:
This message is generated by the process manager to log an event where some corrective action needs to happen.
MESSAGE:
GEN_INFO_HA_MSO: Received a request for Manual Switch Over.
DESCRIPTION:
This message is generated by the process manager when a request for Manual Switchover is received via the MML.
MESSAGE:
GEN_INFO_HA_PEER_STATE: Recognizing peer platform in %s state
DESCRIPTION:
Generated when the process manager recognizes and performs the necessary actions to put the redundant platform to a particular state.
PARAMETERS:
%s: state <Standby/OutOfService>
MESSAGE:
GEN_INFO_HA_PLAT_GEN: Auto Platform State generated
DESCRIPTION:
Generated by the process manager at startup time when it detects a standalone flag.
MESSAGE:
GEN_INFO_HA_PLAT_STATE: Platform in %s state
DESCRIPTION:
Generated when the process manager declares the state of the system.
PARAMETERS:
%s: state <Out of Service/Active/Standby>
MESSAGE:
GEN_INFO_PEXIT: Process %s exiting.
DESCRIPTION:
This message is used by the process who is existing itself
PARAMETERS:
%s: process which is exiting
MESSAGE:
GEN_INFO_PINIT: Process %s initialization complete.
DESCRIPTION:
Initialization complete message.
PARAMETERS:
%s: process name
MESSAGE:
GEN_INFO_PSTART: Starting process %s.
DESCRIPTION:
This message is used by the process who starts another process
PARAMETERS:
%s: name of process that was started
MESSAGE:
GEN_INFO_PSTARTED: Process %s started.
DESCRIPTION:
This message is used by the process that was started by another process
PARAMETERS:
%s: name of process that was started
MESSAGE:
GEN_INFO_PSTOP: Stopping process %s.
DESCRIPTION:
This message is used by the process who stops another process
PARAMETERS:
%s: process stopped
MESSAGE:
GEN_TRACE_FREAD: Reading %s, status = %d, size = %d
DESCRIPTION:
This message is used to show the status of reading a FIFO.
PARAMETERS:
%s: FIFO name
%d: status of read operation
%d: number of bytes read
MESSAGE:
GEN_TRACE_FWRITE: Writing %s, status = %d, size = %d
DESCRIPTION:
This message is used to show the status of writing a FIFO.
PARAMETERS:
%s: FIFO name
%d: status of read operation
%d: number of bytes written
MESSAGE:
GEN_TRACE_HA_FCMD: Received HA cmd: %s from foverd for node: %d in %s state
DESCRIPTION:
This is a trace level message by the process manager used when the process manager receives any command from the fail over daemon.
PARAMETERS:
%s: command <Active/Standby/OOS/FSO/CSO/ACK>
%d: NodeId that the fail over daemon sends
%s: current state of the platform <Active/Standby/OOS>
MESSAGE:
GEN_TRACE_HA_PFCMD: Previous HA cmd: %s from foverd for previous node: %s
DESCRIPTION:
This is a trace level message by the process manager used when the process manager received any command from the fail over daemon.
PARAMETERS:
%s: command <Active/Standby/OOS/FSO/CSO>
%s: the node for which the command was sent <Local/Remote>
MESSAGE:
GEN_TRACE_HA_PSTATE: Sending HA command %s to %s (%s)
DESCRIPTION:
This message is used by the process manager to trace the HA command sent to the appropriate processes.
PARAMETERS:
%s: command name <Active/Standby/OOS/FSO/CSO>
%s: component name
%s: status <Normal Operation/Restart/Standalone>
MESSAGE:
GEN_TRACE_HA_RSP: Received an %s for HA command from %s
DESCRIPTION:
This message is logged by the process manager when it receives a response for its HA command from the processes.
PARAMETERS:
%s: <ACK/NAK>
%s: component name
MESSAGE:
GEN_TRACE_HA_SHELL_PSTATE: Setting process %s to %s
DESCRIPTION:
This message is logged by the process manager when the final platform state is sent to the process.
PARAMETERS:
%s: component name
%s: state of the platform <Active/Standby/OOS>
MESSAGE:
MGMT_ERR_POLL_ERROR: %s
DESCRIPTION:
Polling error from MMDB daemon
PARAMETERS:
%s: error message
MESSAGE:
MGMT_INFO_RPTALM: Alarm with category ID %d and component ID %C
DESCRIPTION:
This message is used to report any valid alarm.
PARAMETERS:
%d: category ID
%C: component ID
MESSAGE:
PROT_ERR_ATM_ADDPOLLDEV_FAIL: compId %C: Error adding poll device %s
DESCRIPTION:
Used to indicate the failure to add poll device
PARAMETERS:
%C: componentId
%s: name of the interface
MESSAGE:
PROT_ERR_ATM_ADDVPCI_FAIL: Add VPCI failed: %s
DESCRIPTION:
Used to indicate failure of VPCI addition.
PARAMETERS:
%s: Error code converted to string (strerr(errno)), preceded by the file descriptor and VPCI value.
MESSAGE:
PROT_ERR_ATM_ATTACH_FAIL: ATM Attach failed: %s
DESCRIPTION:
Used to indicate failure of ATM attach
PARAMETERS:
%s: Error code converted to string (strerr(errno)), preceded by the File descriptor and interface number.
MESSAGE:
PROT_ERR_ATM_BAD_FD: %s: Bad File descriptor %d
DESCRIPTION:
Used when the ATM transport layer receives a bad file descriptor
PARAMETERS:
%s: function name in which this call was made
%d: File descriptor
MESSAGE:
PROT_ERR_ATM_BWALLOC_FAIL: Bandwidth Alloc failed: %s
DESCRIPTION:
Used to indicate failure of ATM BandWidth Allocation.
PARAMETERS:
%s: Error code converted to string (strerr(errno)), preceded by the interface number
MESSAGE:
PROT_ERR_ATM_INTF_OPEN_FAIL: ATM interface open failed: %s
DESCRIPTION:
Used to indicate a ATM interface open failure
PARAMETERS:
%s: Error code converted to string (strerr(errno)), preceded by the interface name.
MESSAGE:
PROT_ERR_ATM_NO_LOCAL_DSL: compId %C: No local DSL available: %s
DESCRIPTION:
Used to indicate the non availability of local DSL
PARAMETERS:
%C: componentId
%s: function name in which this call was made
MESSAGE:
PROT_ERR_ATM_SETRAW_FAIL: ATM Set RAW failed: %s
DESCRIPTION:
Used to indicate failure of ATM Set RAW
PARAMETERS:
%s: Error code converted to string (strerr(errno)), preceded by the interface number
MESSAGE:
PROT_ERR_SRCP_BLD_ACTION: compId %C: Cannot specify action with SRCP signals %d
DESCRIPTION:
This message indicates that the SRCP message cannot be built because actions are not allowed with SRCP signals.
PARAMETERS:
%C: component id
%d : encoded value of the signal
MESSAGE:
PROT_ERR_SRCP_BLD_CVID: compId %C: Unrecognized control vector %d
DESCRIPTION:
This message indicates an unknown parameter (encoded in binary data stream format as a control vector) in the message received from upper layer. An attempt will be made to skip over the unrecognized control vector but the message built will likely be incomplete.
PARAMETERS:
%C: component id
%d : control vector id
MESSAGE:
PROT_ERR_SRCP_BLD_CVLEN: compId %C: Incorrect length of control vector %d
DESCRIPTION:
This message indicates an inconsistency in the message (encoded in binary data stream format) received from upper layer, specifically the size of a particular parameter (control vector), and building of the message is aborted.
PARAMETERS:
%C: component id
%d : control vector id
MESSAGE:
PROT_ERR_SRCP_BLD_EVT: compId %C: SRCP event %d out of range
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the event specified is not in the associated package.
PARAMETERS:
%C: component id
%d : encoded value of the event
MESSAGE:
PROT_ERR_SRCP_BLD_MODE: compId %C: Invalid SRCP mode %d
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the mode parameter is invalid.
PARAMETERS:
%C: component id
%d : encoded value of the mode
MESSAGE:
PROT_ERR_SRCP_BLD_MSGTYPE: compId %C: Invalid SRCP message type %d
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the message type specified is invalid.
PARAMETERS:
%C: component id
%d : encoded value of the message type
MESSAGE:
PROT_ERR_SRCP_BLD_OFFLIMIT: compId %C: Traversing pass end of GDS
DESCRIPTION:
This message indicates an inconsistency in the message (encoded in binary data stream) received from upper layer, specifically the length of the data stream, and building of the message is aborted.
PARAMETERS:
%C: component id
MESSAGE:
PROT_ERR_SRCP_BLD_PARMTYPE: compId %C: Unknown or unsupported SRCP parameter type %d
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the event parameter type is unknown or unsupported.
PARAMETERS:
%C: component id
%d: encoded value of the event parameter type
MESSAGE:
PROT_ERR_SRCP_BLD_PKG: compId %C: SRCP package %d out of range
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the package parameter is not within the range of supported packages.
PARAMETERS:
%C: component id
%d: encoded value of the package
MESSAGE:
PROT_ERR_SRCP_BLD_REQEVT: compId %C: SRCP event %d cannot be requested
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the requested event parameter specifies a non-requestable SRCP event.
PARAMETERS:
%C: component id
%d: encoded value of the event
MESSAGE:
PROT_ERR_SRCP_BLD_REQINFO: compId %C: Invalid SRCP requested info %d
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the requested info parameter is invalid.
PARAMETERS:
%C: component id
%d : encoded value of the requested info
MESSAGE:
PROT_ERR_SRCP_BLD_SIGEVT: compId %C: SRCP event %d cannot be signalled
DESCRIPTION:
This message indicates that the SRCP message cannot be built because the signal request parameter specifies a non-signallable SRCP event.
PARAMETERS:
%C: component id
%d : encoded value of the event
MESSAGE:
PROT_ERR_SRCP_PARSE_EPID: compId %C: Cannot parse SRCP endpoint id in %.60s
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because the endpoint id is invalid (cf. RFC 821).
PARAMETERS:
%C: component id
%.60s: endpoint id
MESSAGE:
PROT_ERR_SRCP_PARSE_EVT: compId %C: SRCP event %.3s not found in package %s
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because it contains an event which cannot be found in the associated package.
PARAMETERS:
%C : component id
%.1s: first 3 letters of the event
%s : package
MESSAGE:
PROT_ERR_SRCP_PARSE_EVTPARM: compId %C: Cannot parse SRCP parameter for %s/%s
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because it contains an event which carries an invalid or extraneous parameter.
PARAMETERS:
%C: component id
%s: package
%s: event which carries the parameter
MESSAGE:
PROT_ERR_SRCP_PARSE_LINE: compId %C: Cannot parse %.60s
DESCRIPTION:
This message indicates that an entire line in the SRCP message cannot be parsed.
PARAMETERS:
%C: component id
%.60s: message line
MESSAGE:
PROT_ERR_SRCP_PARSE_MAJVER: compId %C: SRCP major version mismatch %d
DESCRIPTION:
This message indicates the major version number in the SRCP message does not match what this version of software supports.
PARAMETERS:
%C: component id
%d : major version number
MESSAGE:
PROT_ERR_SRCP_PARSE_MINVER: compId %C: SRCP minor version mismatch %d
DESCRIPTION:
This message indicates the minor version number in the SRCP message does not match what this version of software supports.
PARAMETERS:
%C: component id
%d : minor version number
MESSAGE:
PROT_ERR_SRCP_PARSE_MSGTYPE: compId %C: Unknown or unexpected message type %.20s
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because the message type is unknown or unexpected (for call agent).
PARAMETERS:
%C: component id
%.20s: message type
MESSAGE:
PROT_ERR_SRCP_PARSE_PKG: compId %C: SRCP package %.1s not found
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because it contains an unrecognized package.
PARAMETERS:
%C: component id
%.1s: first letter of the package
MESSAGE:
PROT_ERR_SRCP_PARSE_PROT: compId %C: Protocol %.20s not SRCP
DESCRIPTION:
This message indicates that the SRCP message cannot be parsed because the protocol field in the command line is not SRCP.
PARAMETERS:
%C: component id
%.20s: protocol
MESSAGE:
PROT_ERR_SRCP_RANGE_TXNID: compId %C: SRCP transaction ID %u out of range
DESCRIPTION:
This message is used by components that handle SRCP messages. It indicates an error due to an out of range transaction id. SRCP transaction id ranges from 1 to 999999999.
PARAMETERS:
%C: component id
%u : transaction id
MESSAGE:
PROT_ERR_XGCP_BLD_ACTION: compId %C: Cannot specify action with SGCP/MGCP signals %d
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because actions are not allowed with SGCP/MGCP signals.
PARAMETERS:
%C: component id
%d : encoded value of the signal
MESSAGE:
PROT_ERR_XGCP_BLD_CVID: compId %C: Unrecognized control vector %d
DESCRIPTION:
This message indicates an unknown parameter (encoded in binary data stream format as a control vector) in the message received from upper layer. An attempt will be made to skip over the unrecognized control vector but the message built will likely be incomplete.
PARAMETERS:
%C: component id
%d : control vector id
MESSAGE:
PROT_ERR_XGCP_BLD_CVLEN: compId %C: Incorrect length of control vector %d
DESCRIPTION:
This message indicates an inconsistency in the message (encoded in binary data stream format) received from upper layer, specifically the size of a particular parameter (control vector), and building of the message is aborted.
PARAMETERS:
%C: component id
%d: control vector id
MESSAGE:
PROT_ERR_XGCP_BLD_EVT: compId %C: SGCP/MGCP event %d out of range
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the event specified is not in the associated package.
PARAMETERS:
%C: component id
%d: encoded value of the event
MESSAGE:
PROT_ERR_XGCP_BLD_MODE: compId %C: Invalid SGCP/MGCP mode %d
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the mode parameter is invalid.
PARAMETERS:
%C: component id
%d: encoded value of the mode
MESSAGE:
PROT_ERR_XGCP_BLD_MSGTYPE: compId %C: Invalid SGCP/MGCP message type %d
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the message type specified is invalid.
PARAMETERS:
%C: component id
%d: encoded value of the message type
MESSAGE:
PROT_ERR_XGCP_BLD_OFFLIMIT: compId %C: Traversing pass end of GDS
DESCRIPTION:
This message indicates an inconsistency in the message (encoded in binary data stream) received from upper layer, specifically the length of the data stream, and building of the message is aborted.
PARAMETERS:
%C: component id
MESSAGE:
PROT_ERR_XGCP_BLD_PARMTYPE: compId %C: Unknown or unsupported SGCP/MGCP parameter type %d
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the event parameter type is unknown or unsupported.
PARAMETERS:
%C: component id
%d : encoded value of the event parameter type
MESSAGE:
PROT_ERR_XGCP_BLD_PKG: compId %C: SGCP/MGCP package %d out of range
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the package parameter is not within the range of supported packages.
PARAMETERS:
%C: component id
%d : encoded value of the package
MESSAGE:
PROT_ERR_XGCP_BLD_REQEVT: compId %C: SGCP/MGCP event %d cannot be requested
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the requested event parameter specifies a non-requestable SGCP/MGCP event.
PARAMETERS:
%C: component id
%d : encoded value of the event
MESSAGE:
PROT_ERR_XGCP_BLD_REQINFO: compId %C: Invalid SGCP/MGCP requested info %d
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the requested info parameter is invalid.
PARAMETERS:
%C: component id
%d : encoded value of the requested info
MESSAGE:
PROT_ERR_XGCP_BLD_SIGEVT: compId %C: SGCP/MGCP event %d cannot be signalled
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be built because the signal request parameter specifies a non-signallable SGCP/MGCP event.
PARAMETERS:
%C: component id
%d : encoded value of the event
MESSAGE:
PROT_ERR_XGCP_PARSE_EPID: compId %C: Cannot parse SGCP/MGCP endpoint id in %.60s
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because the endpoint id is invalid (cf. RFC 821).
PARAMETERS:
%C: component id
%.60s: endpoint id
MESSAGE:
PROT_ERR_XGCP_PARSE_EVT: compId %C: SGCP/MGCP event %.3s not found in package %s
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because it contains an event which cannot be found in the associated package.
PARAMETERS:
%C: component id
%.1s: first 3 letters of the event
%s : package
MESSAGE:
PROT_ERR_XGCP_PARSE_EVTPARM: compId %C: Cannot parse SGCP/MGCP parameter for %s/%s
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because it contains an event which carries an invalid or extraneous parameter.
PARAMETERS:
%C: component id
%s: package
%s: event which carries the parameter
MESSAGE:
PROT_ERR_XGCP_PARSE_LINE: compId %C: Cannot parse %.60s
DESCRIPTION:
This message indicates that an entire line in the SGCP/MGCP message cannot be parsed.
PARAMETERS:
%C : component id
%.60s: message line
MESSAGE:
PROT_ERR_XGCP_PARSE_MAJVER: compId %C: SGCP/MGCP major version mismatch %d
DESCRIPTION:
This message indicates the major version number in the SGCP/MGCP message does not match what this version of software supports.
PARAMETERS:
%C: component id
%d : major version number
MESSAGE:
PROT_ERR_XGCP_PARSE_MINVER: compId %C: SGCP/MGCP minor version mismatch %d
DESCRIPTION:
This message indicates the minor version number in the SGCP/MGCP message does not match what this version of software supports.
PARAMETERS:
%C: component id
%d : minor version number
MESSAGE:
PROT_ERR_XGCP_PARSE_MSGTYPE: compId %C: Unknown or unexpected message type %.20s
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because the message type is unknown or unexpected (for call agent).
PARAMETERS:
%C : component id
%.20s: message type
MESSAGE:
PROT_ERR_XGCP_PARSE_PKG: compId %C: SGCP/MGCP package %.1s not found
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because it contains an unrecognized package.
PARAMETERS:
%C: component id
%.1s: first letter of the package
MESSAGE:
PROT_ERR_XGCP_PARSE_PROT: compId %C: Protocol %.20s not SGCP/MGCP
DESCRIPTION:
This message indicates that the SGCP/MGCP message cannot be parsed because the protocol field in the command line is not SGCP/MGCP.
PARAMETERS:
%C : component id
%.20s: protocol
MESSAGE:
PROT_ERR_XGCP_RANGE_TXNID: compId %C: SGCP/MGCP transaction ID %u out of range
DESCRIPTION:
This message is used by components that handle SGCP/MGCP messages. It indicates an error due to an out of range transaction id. SGCP/MGCP transaction id ranges from 1 to 999999999.
PARAMETERS:
%C: component id
%u : transaction id
MESSAGE:
PROT_TRACE_ATM_AAL5_CLOSE: compId %C: Deleting Stream %s
DESCRIPTION:
Used to indicate the closing of an AAL5 interface
PARAMETERS:
%C: componentId
%s: info on DSL number and File descriptoR
MESSAGE:
PROT_TRACE_ATM_AAL5_OPEN: compId %C: IO stream AAL5 Open interface %s
DESCRIPTION:
Used to indicate the opening of an AAL5 interface
PARAMETERS:
%C: componentId
%s: name of the interface
MESSAGE:
PROT_TRACE_ATM_SEND: SEND TO >>>> %C <: %s
DESCRIPTION:
Used to indicate a ATM message send
PARAMETERS:
%C: component Id of the port on which message is sent
%s: VPCI to which message was sent
MESSAGE:
PROT_TRACE_MGCP_FROM_GW: compId: %C, MGCP msg from gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an MGCP message from gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_TRACE_MGCP_TO_GW: compId: %C, MGCP msg to gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an MGCP message to gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_TRACE_SGCP_FROM_GW: compId: %C, SGCP msg from gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an SGCP message from gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_TRACE_SGCP_TO_GW: compId: %C, SGCP msg to gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an SGCP message to gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_TRACE_SRCP_FROM_GW: compId: %C, SRCP msg from gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an SRCP message from gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_TRACE_SRCP_TO_GW: compId: %C, SRCP msg to gateway, ip: %s, msg: %s
DESCRIPTION:
This message captures an SRCP message to gateway.
PARAMETERS:
%C: the component ID
%s: the gateway's ip address
%s: the message
MESSAGE:
PROT_WARN_SRCP_PARSE_LONGCOMM: compId %C: Long SRCP comment truncated %.60s
DESCRIPTION:
This message indicates that the SRCP message contains a long comment and only a truncated copy will be passed to upper layer.PARAMETERS:
%C: component id
%.60s: commentMESSAGE:
PROT_WARN_XGCP_PARSE_LONGCOMM: compId %C: Long SGCP/MGCP comment truncated %.60sDESCRIPTION:
This message indicates that the SGCP/MGCP message contains a long comment and only a truncated copy will be passed to upper layer.
PARAMETERS:
%C: component id
%.60s: comment
MESSAGE:
TIOS_ERR_PROC_EXIST: %C component does not exist in process
DESCRIPTION:
The specified internal component does not exist in the process reporting the error. It may exist in the future. The question marks indicate that there is no MML mapping to the component id, meaning there is no component entry.
PARAMETERS:
:%C: component id of process
Posted: Tue Jun 6 07:48:33 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.