COSD System Log Messages
This chapter describes messages with the COSD prefix. They are generated by the class-of-service (CoS) process (cosd), which enables the routing platform to provide different levels of service to applications based on packet classifications.
COSD_AGGR_CONFIG_INVALID
System Log Message
Error: Cannot have config error-message interface-name
Description
The class-of-service (CoS) process (cosd) did not apply the config on this interface because it was not valid in this case.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
One possible cause is if any Class-of-Service is configured on an interface which is a part of an aggregated interface
Action
Remove or change the config from/on the interface.
COSD_CHASSIS_SCHED_MAP_INVALID
System Log Message
Chassis scheduler map incorrectly applied to interface interface-name: error-message
Description
The class-of-service (CoS) process (cosd) did not apply a chassis scheduler map to the indicated interface, because the configuration used to apply the scheduler map was invalid.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
One possible cause is that the chassis scheduler map is applied to a specific interface. For most interface types, a scheduler map must be applied to all interfaces on the PIC; therefore, a wildcard must be used to specify the interfaces. One exception to this rule is the Gigabit Ethernet IQ PIC.
Action
Correct the configuration used to apply the chassis scheduler map to the interface.
COSD_CLASSIFIER_NO_SUPPORT_LSI
System Log Message
Cannot support classifier type classifier-type on lsi interface interface-name
Description
The Differentiated Services code point (DSCP) classifier and the 802.1p classifier are only supported on I-Chip based Flexible PIC Concentrators (FPCs).
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the DSCP or the 802.1p classifier configuration from the routing instance
COSD_CLASS_8021P_UNSUPPORTED
System Log Message
ieee-802.1 classifier is not valid on interface interface-name
Description
The IEEE 802.1p classifier is not supported on the indicated interface.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Remove the 802.1p classifier configuration from the interface, or configure an interface encapsulation type that supports 802.1p classifiers.
COSD_CLASS_NO_SUPPORT_IFD
System Log Message
BA/Fixed Classifier or Rewrite on Physical Interface is not allowed when ethernet switching family is configured: interace interface-name
Description
The Rewrite is not supported on this interface when ethernet switching is enabled
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the classifier configuration from the interface, instead apply it on the logical interface where ethernet switching family is enabled
Action
Remove the Rewrite configuration from the interface, instead apply it on the logical interface where ethernet switching family is enabled
COSD_CLASS_NO_SUPPORT_L3_IFL
System Log Message
BA/Fixed Classifier or Rewrite config is not allowed on logical interface (interface-name) with inet/inet6 family
Description
The Rewrite is not supported on this logical interface
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the classifier configuration from the logical interface, instead apply it on the main interface if inet/inet6 is configured on one of its logical interfaces
Action
Remove the Rewrite configuration from the logical interface, instead apply it on the main interface if inet/inet6 is configured on one of its logical interfaces
COSD_CONF_OPEN_FAILURE
System Log Message
Unable to open: filename, using default CoS forwarding classes, do 'commit full' in cli to avoid this message
Description
The class-of-service (CoS) process (cosd) could not read configuration data.
Type
Error: An error occurred
Severity
error
Facility
ANY
Cause
All of the following resons: mgd -I fails after upgrade-the file cosd.conf does not exist and is not created because of the mgd -I failure The first commit is 'commit' and not 'commit full'-the file cosd.conf does not commit and is not created automatically [class-of-service forwarding-classes] does not exist-the file cosd.conf does not get exported with plain 'commit'
Action
Do a 'commit full'
COSD_DB_OPEN_FAILED
System Log Message
Unable to open configuration database: error-message(name)
Description
The class-of-service (CoS) process (cosd) could not read configuration data for the indicated reason.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
The specified database does not exist
Action
Contact your technical support representative.
COSD_EXACT_RATE_UNSUPP_INTERFACE
System Log Message
Unable to apply scheduler map scheduler-map to interface interface-name because it does not support exact-rate transmission
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler named in the scheduler map specifies exact transmission rate. The interface is housed on a type of PIC that does not support exact transmission rate, such as an IQ2 PIC. In terms of configuration, the 'exact' statement is included in the scheduler definition at the [edit class-of-service schedulers <scheduler-name> transmit-rate (<rate> | percent <percentage>)] hierarchy level. The scheduler is included in the scheduler map that is applied to the interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the 'exact' statement from the scheduler in the scheduler map applied to the interface.
COSD_EXACT_RATE_UNSUPP_SESSION
System Log Message
Unable to apply CoS to L2TP session session-id, because scheduler map scheduler-map specifies exact rate transmission
Description
The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session, because the scheduler map specified by the RADIUS server for the session is configured for exact transmission rate. Exact transmission rate is not supported for L2TP sessions on the type of PIC that houses the interface, such as an IQ2 PIC. In terms of configuration, the 'exact' statement is included in a scheduler definition at the [edit class-of-service schedulers <scheduler-name> transmit-rate (<rate> | percent <percentage>)] hierarchy level. The scheduler is included in a scheduler map that is associated with a traffic control profile. The traffic control profile is named by an attribute in the RADIUS server's configuration file, which makes the profile apply to the session.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the 'exact' statement from the scheduler in the scheduler map applied to the session.
COSD_FRAGMENTATION_MAP_CONFLICT
System Log Message
Interface compression-device matches wildcard wildcard-interface-name, but fragmentation map fragmentation-map was not applied because interface is compression device for link interface link-interface-name
Description
The indicated fragmentation map is normally applied to interfaces that match the indicated wildcard. The class-of-service (CoS) process (cosd) did not apply the fragmentation map to the indicated interface, even though it matches the wildcard, because the interface is acting as a compression device for the indicated link interface.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Correct the configuration of the fragmentation map.
COSD_HIGH_PRIO_QUEUES_INTERFACE
System Log Message
Unable to apply scheduler map scheduler-map to interface interface-name, because multiple schedulers in map have "high,""medium-high," or "strict-high" priority
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the map includes more than one scheduler that has high, medium-high, or strict-high priority. For interfaces that are housed by certain PICs, such as an IQ2 PIC, the scheduler map can include only one scheduler that specifies one of those three priority levels. In terms of configuration, the 'priority' statement at the [edit class-of-service schedulers <scheduler-name>] hierarchy level has the value 'high, ' 'medium-high, ' or 'strict-high' for more than one of the schedulers in the map.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.
COSD_HIGH_PRIO_QUEUES_SESSION
System Log Message
Unable to apply CoS to L2TP session session-id, because multiple schedulers in scheduler map scheduler-map have "high,""medium-high," or "strict-high" priority
Description
The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session because the scheduler map specified by the RADIUS server for the session includes more than one scheduler that has high, medium-high, or strict-high priority. For interfaces that are housed by certain Physical Interface Cards (PICs), such as an IQ2 PIC, the scheduler map can include only one scheduler that specifies one of those three priority levels. In terms of configuration, the 'priority' statement at the [edit class-of-service schedulers <scheduler-name>] hierarchy level has the value 'high, ' 'medium-high, ' or 'strict-high' for more than one of the schedulers in the map. The map is associated with a traffic control profile that is named by an attribute in the RADIUS server's configuration file, which makes the profile apply to the session.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.
COSD_IFD_OUTPUT_SHAPING_RATE_ERR
System Log Message
Traffic shaping not supported on interface device interface-name
Description
The class-of-service (CoS) process (cosd) did not apply the shaping rate that is configured for the indicated interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
Shaping rate is valid only for interfaces housed by IQ and IQ2 PICs, and the interface is on a different type of PIC.
Action
Remove the shaping rate configuration from the interface.
COSD_IFD_SHAPER_ERR
System Log Message
port shaper not allowed on interface interface-name
Description
The non-queuing dense port concentrators (DPCs) did not support the specified shaping rate.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
The port shaper was not supported on the non-queuing DPCs.
Action
Remove the shaping rate configuration from the interface.
COSD_INTERFACE_NO_MEDIA
System Log Message
Unable to obtain media information for interface interface-name
Description
The message sent by the kernel for the indicated interface did not include required media information.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
Contact your technical support representative.
COSD_L2TP_COS_NOT_CONFIGURED
System Log Message
Unable to apply CoS to L2TP session session-id because session-aware CoS is not enabled for interface interface-name
Description
The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface, because the interface is not configured to support session-aware CoS for L2TP. In terms of configuration, the 'per-session-scheduler' statement is not included at the [edit interfaces <interface-name> unit <logical-unit-number>] hierarchy level.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Include the 'per-session-scheduler' statement in the configuration for the interface.
COSD_L2TP_COS_NOT_SUPPORTED
System Log Message
Unable to apply CoS to L2TP session session-id on interface interface-name: it does not support CoS
Description
The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface. The interface is configured to support session-aware CoS for L2TP, but is not on a PIC that supports that feature, such as an IQ2 PIC. In terms of configuration, the 'per-session-scheduler' statement is included at the [edit interfaces <interface-name> unit <logical-unit-number>] hierarchy level.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Determine whether the interface is on an PIC that supports session-aware CoS; if not, remove the 'per-session-scheduler' statement.
COSD_L2TP_SHAPING_NOT_CONFIGURED
System Log Message
Unable to apply CoS to L2TP session session-id because session-aware shaping is not enabled for interface interface-name
Description
The class-of-service (CoS) process (cosd) did not apply CoS settings to the indicated Layer 2 Tunneling Protocol (L2TP) session on the indicated interface, because session-aware traffic shaping for L2TP is not configured on the PIC that houses the interface. In terms of configuration, the 'session-shaping' statement is not included at the [edit chassis fpc <slot-number> pic <pic-number> traffic-manager mode] hierarchy level.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Include the 'session-shaping' statement in the configuration for the PIC.
COSD_LARGE_DELAY_BUFFER_INVALID
System Log Message
Error for interface interface-name error-message
Description
The class-of-service (CoS) process (cosd) did not apply the large delay buffer setting that is configured for the indicated interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
The interface is not housed on one of the PIC types that support large delay buffer.
Action
Remove the large delay buffer configuration from the interface.
COSD_MALLOC_FAILED
System Log Message
malloc failed: error-message
Description
The class-of-service (CoS) process (cosd) could not dynamically allocate memory for the indicated reason.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
A software bug caused a memory leak or the Routing Engine did not have sufficient memory.
Action
Contact your technical support representative. For more information, see http://kb.juniper.net/InfoCenter/index?page=content&id=KB18862.
COSD_MAX_FORWARDING_CLASSES_ABC
System Log Message
exceeding max 4 forwarding-class support.
Description
User configuration exceeds the maximum number of forwarding class that is supported.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Configure only four forwarding classes
COSD_MPLS_DSCP_CLASS_NO_SUPPORT
System Log Message
Cannot support MPLS DSCP classifier on ifl interface-name
Description
The MPLS Differentiated Services code point (DSCP) classifier is only supported on I-Chip based Flexible PIC Concentrators (FPCs). It is not supported on Q2 PICs.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the MPLS DSCP classifier configuration from the logical interface.
COSD_MULTILINK_CLASS_CONFLICT
System Log Message
Fragmentation map fragmentation-map for wildcard wildcard-interface-name specified multilink class class-name for queue queue-number on interface interface-name, which exceeds configured limit of limit
Description
The indicated fragmentation map is normally applied to interfaces that match the indicated wildcard, and specifies the indicated multilink class setting for queues on those interfaces. The class-of-service (CoS) process (cosd) did not apply the fragmentation map to the indicated interface, even though it matches the wildcard, because the setting in the map exceeds the indicated class limit, which is configured on the interface itself.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Correct the configuration so that the multilink class setting in the fragmentation map does not exceed the class limit for the interface.
COSD_NULL_INPUT_ARGUMENT
System Log Message
NULL input argument : error-message
Description
The pointer that was passed to this function was NULL.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Contact your technical support representative.
COSD_OUT_OF_DEDICATED_QUEUES
System Log Message
Queue usage count for interface interface-name is at percentage-value percent
Description
The class-of-service (CoS) process (cosd) is running out of dedicated queues.
Type
Event: This message reports an event, not an error
Severity
warning
Facility
LOG_DAEMON
COSD_RATE_LIMIT_INVALID
System Log Message
Unable to apply scheduler map scheduler-map to interface interface-name. description.
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the number of rate limited queues in the scheduler map exceeded the limit supported by this interface or the priority is not supported. The interface is housed in a type of PIC that does not support the number of configured rate limited queues or the priority is not supported. In terms of configuration, the 'rate-limit' statement is included in the scheduler definition at the [edit class-of-service schedulers <scheduler-name> transmit-rate <rate> | percent <percentage>] hierarchy level. The scheduler is included in the scheduler map applied to the interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Either limit the number of rate-limited schedulers in this scheduler map to the allowed maximum for this PIC and interface type or check the allowed priority for rate-limited queues
COSD_RATE_LIMIT_NOT_SUPPORTED
System Log Message
Unable to apply scheduler map scheduler-map to interface interface-name because it does not support rate limiting
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler named in the scheduler map is configured for rate limiting. The interface is housed in a type of PIC that does not support rate limiting. In terms of configuration, the 'rate-limit' statement is included in the scheduler definition at the [edit class-of-service schedulers <scheduler-name> transmit-rate <rate> | percent <percentage>] hierarchy level. The scheduler is included in the scheduler map applied to the interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove the 'rate-limit' statement from the scheduler in the scheduler map applied to the interface.
COSD_REWRITE_RULE_LIMIT_EXCEEDED
System Log Message
Number of rewrite rules applied to interface interface-name exceeds limit (maximum-value)
Description
The class-of-service (CoS) process (cosd) determined that the number of rewrite rules applied to the indicated interface exceeds the indicated limit for the interface. In terms of configuration, too many rewrite rules are included at the [edit class-of-service interfaces <interface-name> unit <logical-unit-number> rewrite-rules] hierarchy level.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Remove rewrite rules from the configuration for the interface.
COSD_RL_IFL_NEEDS_SHAPING
System Log Message
"rate-limit" configured in scheduler-map, but ifl interface-name does not have output shaper configured. It will use the ifd-shaping rate/ifd-transmit rate for implementation of rate-limit.
Description
The 'rate-limit' statement is configured in one or more schedulers that are part of the indicated scheduler map. In order to apply this scheduler map to the indicated interface, output shaping rate should be configured on the interface. Since no output shaping rate is configured, the transmit rate or shaping rate of the parent interface will be used instead.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Configure output shaping rate for the indicataed interface
COSD_SCHEDULER_MAP_CONFLICT
System Log Message
Forwarding classes "first-forwarding-class" and "second-forwarding-class" in scheduler map scheduler-map both map to queue queue-number
Description
Both of the indicated forwarding classes, which are defined in the indicated scheduler map, map to the same indicated queue. The double mapping is invalid.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Map only one forwarding class to the queue.
COSD_SCHED_AVG_CONST_UNSUPPORTED
System Log Message
Averaging constant not supported on interface interface-name. Value set in scheduler-map scheduler-map (scheduler name) will be ignored.
Description
Configuring averaging constant is not supported on the indicated interface. Value set in the indicated scheduler will be ignored.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Remove the averaging-constant configuration from the indicated scheduler.
COSD_SCHED_MAP_GROUP_CONFLICT
System Log Message
Interface interface-name cannot be bound to scheduler-map scheduler-map. It will be bound to default scheduler-map
Description
Interfaces belonging to a group cannot be bound to different scheduler maps. They will be bound to the default scheduler map.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Map only one scheduler map to all the interfaces of a group.
COSD_SHAPER_GROUP_CONFLICT
System Log Message
Interface interface-name cannot be bound to configured shaping-rate. It will be bound to default rate
Description
Interfaces belonging to a group cannot be bound to different shaping rates. They will be bound to the default shaping rate.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Map only one shaping rate to all interfaces of a group.
COSD_STREAM_IFD_CREATE_FAILURE
System Log Message
Unable to create special master interface device for interface-name
Description
The class-of-service (CoS) process (cosd) could not create the indicated internal interface device, which it needs for application of a chassis scheduler map.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
Contact your technical support representative.
COSD_TIMER_ERROR
System Log Message
Unable to set retry timer for rtsock write operation: error-message
Description
The class-of-service (CoS) process (cosd) used a routine from the rtsock library to write to the kernel, but the kernel did not accept the request. The cosd process could not set the retry timer for the request, for the indicated reason.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
Contact your technical support representative.
COSD_TRICOLOR_ALWAYS_ON
System Log Message
tri-color is always enabled in this platform. There is no need to explicitly set it.
Description
Tri-color marking is always enabled on this platform. There is no need to explicitly set it.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Action
Remove the 'tri-color' configuration statement
COSD_TRICOLOR_NOT_SUPPORTED
System Log Message
Unable to apply scheduler scheduler-map to interface interface-name, because it does not support tricolor marking
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because a scheduler included in the map specifies a packet loss priority (PLP) that is supported only with tricolor marking (TCM). The interface does not support TCM, either because TCM is not enabled or the interface is on a router that does not support TCM. In terms of configuration, the value 'medium-high' or 'medium-low' is specified for the 'loss-priority' statement in a scheduler definition at the [edit class-of-service schedulers <scheduler-name> drop-profile-map] hierarchy level. The scheduler is included in the scheduler map applied to the interface, but the 'tri-color' statement is either not included at the [edit class-of-service] hierarchy level, or is not supported.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Change the value of the 'loss-priority' statement in the scheduler or include the 'tri-color' statement to enable TCM on the router.
COSD_TX_QUEUE_RATES_TOO_HIGH
System Log Message
Unable to apply scheduler map scheduler-map to interface interface-name: sum of scheduler transmission rates exceeds interface shaping or transmission rate
Description
The class-of-service (CoS) process (cosd) did not apply the indicated scheduler map to the indicated interface, because the sum of the queue transmission rates defined in the schedulers in the scheduler map exceeds the shaping or transmission rate for the interface. In terms of configuration, the 'transmit-rate' statement is specified for each scheduler at the [edit class-of-service schedulers <scheduler-name>] hierarchy level. The sum of the configured transmission rates exceeds the transmission or shaping rate of the interface.
Type
Error: An error occurred
Severity
error
Facility
LOG_DAEMON
Action
Decrease the value of one or more 'transmit-rate' statements so that the sum is less than the interface transmission or shaping rate.
COSD_UNKNOWN_CLASSIFIER
System Log Message
classifier type classifier-type is invalid
Description
The class-of-service (CoS) process (cosd) did not recognize the indicated classifier type from the rtsock library.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
Contact your technical support representative.
COSD_UNKNOWN_REWRITE
System Log Message
rtsock rewrite type type is invalid
Description
The class-of-service (CoS) process (cosd) did not recognize the indicated rewrite type from the rtsock library.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
Contact your technical support representative.
COSD_UNKNOWN_TRANSLATION_TABLE
System Log Message
rtsock translation table type translation-table-type is invalid
Description
The class-of-service (CoS) process (cosd) did not recognize the indicated translation table type from the rtsock library.
Type
Error: An error occurred
Severity
warning
Facility
LOG_DAEMON
Cause
An internal software failure occurred.
Action
For more information, see http://kb.juniper.net/InfoCenter/index?page=content&id=KB18866.
