 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
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.
Chassis scheduler map incorrectly applied to interface interface-name: error-message
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.
Error: An error occurred
error
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 Physical Interface Card (PIC); therefore, a wildcard must be used to specify the interfaces. One exception to this rule is the Gigabit Ethernet IQ PIC.
Correct the configuration used to apply the chassis scheduler map to the interface.
Unable to open: filename, using default CoS forwarding classes, do 'commit full' in cli to avoid this message
The class-of-service (CoS) process (cosd) could not read configuration data.
Error: An error occurred
error
All of the following:mgd -I fails after upgrade (cosd.conf does not exist and is not created because of the mgd -I failure), the first commit is 'commit' and not 'commit full'(cosd.conf will not commit is 'commit' and not 'commit full'(cosd.conf will not automatically be created), [class-of-service forwarding-classes] does notexist(the file cosd.conf will not get exported with plain 'commit')
Do a 'commit full'
Unable to open configuration database: error-message
The class-of-service (CoS) process (cosd) could not read configuration data for the indicated reason.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to apply scheduler map scheduler-map to interface interface-name because it does not support exact-rate transmission
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 Physical Interface Card (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.
Error: An error occurred
error
Remove the 'exact' statement from the scheduler in the scheduler map applied to the interface.
Unable to apply CoS to L2TP session session-id, because scheduler map scheduler-map specifies exact rate transmission
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 Physical Interface Card (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.
Error: An error occurred
error
Remove the 'exact' statement from the scheduler in the scheduler map applied to the session.
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
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.
Error: An error occurred
warning
Correct the configuration of the fragmentation map.
Unable to apply scheduler map scheduler-map to interface interface-name, because multiple schedulers in map have "high,""medium-high," or "strict-high" priority
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 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.
Error: An error occurred
error
Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.
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
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.
Error: An error occurred
error
Correct the configuration so that the scheduler map includes only one scheduler with high, medium-high, or strict-high priority.
Unable to open chassis hardware database: error-message
The class-of-service (CoS) process (cosd) encountered the indicated error while opening the chassis hardware database.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Traffic shaping not supported on interface device interface-name
The class-of-service (CoS) process (cosd) did not apply the shaping rate that is configured for the indicated interface.
Error: An error occurred
error
Shaping rate is valid only for interfaces housed by IQ and IQ2 Physical Interface Cards (PICs), and the interface is on a different type of PIC.
Remove the shaping rate configuration from the interface.
Unable to obtain media information for interface interface-name
The message sent by the kernel for the indicated interface did not include required media information.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to apply CoS to L2TP session session-id because session-aware CoS is not enabled for interface interface-name
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.
Error: An error occurred
error
Include the 'per-session-scheduler' statement in the configuration for the interface.
Unable to apply CoS to L2TP session session-id on interface interface-name: it does not support CoS
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 Physical Interface Card (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.
Error: An error occurred
error
Determine whether the interface is on an PIC that supports session-aware CoS; if not, remove the 'per-session-scheduler' statement.
Unable to apply CoS to L2TP session session-id because session-aware shaping is not enabled for interface interface-name
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 Physical Interface Card (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.
Error: An error occurred
error
Include the 'session-shaping' statement in the configuration for the PIC.
Error for interface interface-name error-message
The class-of-service (CoS) process (cosd) did not apply the large delay buffer setting that is configured for the indicated interface.
Error: An error occurred
error
The interface is not housed on one of the Physical Interface Card (PIC) types that supports large delay buffer.
Remove the large delay buffer configuration from the interface.
malloc failed: error-message
The class-of-service (CoS) process (cosd) could not dynamically allocate memory, for the indicated reason.
Error: An error occurred
error
A software bug caused a memory leak, or the Routing Engine did not have sufficient memory.
Contact your technical support representative.
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
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.
Error: An error occurred
warning
Correct the configuration so that the multilink class setting in the fragmentation map does not exceed the class limit for the interface.
Unable to apply scheduler map scheduler-map to interface interface-name because it does not support rate limiting
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 Physical Interface Card (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.
Error: An error occurred
error
Remove the 'rate-limit' statement from the scheduler in the scheduler map applied to the interface.
Number of rewrite rules applied to interface interface-name exceeds limit (maximum-value)
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.
Error: An error occurred
error
Remove rewrite rules from the configuration for the interface.
Forwarding classes "first-forwarding-class" and "second-forwarding-class" in scheduler map scheduler-map both map to queue queue-number
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.
Error: An error occurred
error
Map only one forwarding class to the queue.
Unable to create special master interface device for interface-name
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.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to set retry timer for rtsock write operation: error-message
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.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to apply scheduler scheduler-map to interface interface-name, because it does not support tricolor marking
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.
Error: An error occurred
error
Change the value of the 'loss-priority' statement in the scheduler or include the 'tri-color' statement to enable TCM on the router.
Unable to apply scheduler map scheduler-map to interface interface-name: sum of scheduler transmission rates exceeds interface shaping or transmission rate
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.
Error: An error occurred
error
Decrease the value of one or more 'transmit-rate' statements so that the sum is less than the interface transmission or shaping rate.
classifier type classifier-type is invalid
The class-of-service (CoS) process (cosd) did not recognize the indicated classifier type from the rtsock library.
Error: An error occurred
warning
An internal software failure occurred.
Contact your technical support representative.
rtsock rewrite type type is invalid
The class-of-service (CoS) process (cosd) did not recognize the indicated rewrite type from the rtsock library.
Error: An error occurred
warning
An internal software failure occurred.
Contact your technical support representative.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |