Error Conditions Sample Clauses

Error Conditions. Each error condition is identified by a cause value that is included in the Cause Information Element. Some cause values result in the inclusion of additional diagnostic information in the variable length diagnostic element of the Cause Information Element. If the diagnostic element is not used, it is empty. The cause values are defined in Table 4. Error Description Cause Diagnostic Element Usage INCONSISTENT_BUNDLE Possible configuration mismatch detected. 1 Expected Bundle Identification value as provisioned at the endpoint sending the Cause Information Element. Refer to Note 2, Figure 8for the format of the element. UNKNOWN_VENDOR Unrecognized OUI in a received Vendor Specific Information Element. 2 None LINK_IDLE The bundle link is not operational. 3 None LINK_DOWN The bundle link physical layer is down. 4 None DIFFERENTIAL_DELAY The bundle link differential delay exceeds the maximum allowed. 5 None LOOPBACK_DETECTED The bundle link has detected a potential loopback condition. 6 None OTHER Generic failure cause described by text in diagnostic element. 7 Textual description of failure cause. Refer to Note 2, Figure 8for the format of the element. UNEXPECTED_ ADDLINK An ADD_LINK message was received when the Bundle Link was in up state. 8 None Table 4 Cause Values A Informative Annex – Bundle Link Protocol State Machine The purpose of this annex is to provide one example of a state machine representation of the bundle link procedures, to assist in the understanding of this agreement. This example of the bundle link procedures may not meet all the requirements specified in the procedure section (Section 4). The text description of the procedures is definitive. A simplified version (for clarity) of the state machine for the MFR Link Integrity Protocol is shown in Figure
Sample 1
AutoNDA by SimpleDocs
Error Conditions. If an error is present, the red HEARTBEAT indicator will flash with an unbalanced on/off pattern (on longer than it is off). The error(s) can be viewed under the DIAGNOSTICS mode. HIGH VOLTAGE INTERLOCK SWITCH MESSAGE DISPLAY FREE VEND KEYSWITCH (OPTIONAL) INSTRUCTION PLATE LETTERS NUMERALS 1-9, *,0, # MONETARY PANEL COIN RETURN BUTTON LOW VOLTAGE DOOR SWITCH SERVICE KEYPAD CABINET SELECTION SWITCH BILL ACCEPTOR (OPTIONAL) COIN INSERT MONETARY PANEL High Voltage Interlock Switch (U.S./ Canada). When the cabinet door is open, this switch turns off the optional fan and bean light (if equipped), and turns on the service light.
Sample 1
Error Conditions. A printer shall have mechanisms to allow software to interpret and act upon the following conditions.
Sample 1
Error Conditions. Error conditions are handled as described in section A.5 of Q.933. ANNEX A ENHANCED PVC MANAGEMENT PROCEDURES TO INCREASE THE NUMBER OF PVCS IN FULL STATUS REPORTS (NORMATIVE) The PVC management procedures, as defined in section 2.3.1 of this implementation agreement, are based on the procedures of Q.933 Annex A. The section 2.3.1 procedures are limited to reporting status on a limited number of PVCs: “the number of PVCs that can be supported by Q.933 Annex A is limited by the maximum frame size that can be supported by the user device and the network on the bearer channel.” These enhancement procedures are required to support “any number of” (e.g., greater than 1024) PVCs per bearer channel. This annex defines optional enhanced PVC management procedures to increase the number of PVCs in Full Status reports. Network User Full Status Continued Restart T392
Sample 1
Error Conditions. No changes.
Sample 1
Error Conditions. The following item is added at the end of the list: − The link layer core parameters and the Priority and service class parameters information elements are ignored if the user receives them and does not recognize them. B.3.5.1 Network operation errors No changes.
Sample 1

Related to Error Conditions

  • SUPERIOR CONDITIONS 21.01 All existing benefits, rights, privileges, practices, terms or conditions of employment which may be considered to be superior to those contained herein and which are set out in Appendix 4 are specifically retained by this Agreement unless otherwise agreed by the local parties. The parties agree to remove from Appendix 4 those superior conditions which no longer have application. Where the parties cannot agree on whether a superior condition continues to have application, the issue will be reduced to a grievance and referred to arbitration.

  • Specific Conditions If applicable, specific conditions required after a risk assessment will be included in Exhibit G. Grantee shall adhere to the specific conditions listed therein.

  • Change Order Conditions All Change Orders are issued under the following conditions and shall contain the following language as appropriate:

  • Contract Conditions This section contains conditions which shall be complied with during the performance of this contract. The conditions come in two parts, general conditions and special contract requirements.

  • Other Conditions v1.10 Questions? xxxxxxxxxxxx@xxxxxxxxx.xxx or +0-000-000-0000 (toll free in the US) or

  • BASIC CONDITIONS The State shall have no obligation to disburse money for the Project under this Grant Agreement until the Grantee has satisfied the following conditions:

  • Satisfaction of Conditions The conditions precedent set out in Section 6.1, Section 6.2 and Section 6.3 shall be conclusively deemed to have been satisfied, waived or released at the Effective Time.

  • Unsafe Conditions In accordance with 29 CFR § 1977, occasions might arise when an employee is confronted with a choice between not performing assigned tasks or subjecting himself/herself to serious injury or death arising from a hazardous condition at the workplace. If the employee, with no reasonable alternative, refuses in good faith to expose himself/herself to the dangerous condition, he/she would be protected against subsequent discrimination. The condition causing the employee's apprehension of death or injury must be of such a nature that a reasonable person, under the circumstances then confronting the employee, would conclude that there is a real danger of death or serious injury and that there is insufficient time, due to the urgency of the situation, to eliminate the danger by resorting to regular statutory enforcement channels. In addition, in such circumstances, the employee, where possible, must also have sought from his Employer, and been unable to obtain, a correction of the dangerous condition.

  • Weather Conditions In the event of temporary suspension of work or during inclement weather or whenever the OWNER shall direct, the CONSTRUCTION MANAGER will, and will cause its Subcontractors to protect carefully its and their work and material against damage or injury from the weather. If, in the opinion of the OWNER, any Work or material shall have been damaged or injured by reason of failure on the part of the CONSTRUCTION MANAGER or any of its Subcontractors so to protect his work, said materials shall be removed and replaced at the expense of the CONSTRUCTION MANAGER.

  • Adverse Weather Conditions Except in emergency situations, the Employer shall not require an employee:

Time is Money Join Law Insider Premium to draft better contracts faster.