Configuration Mismatch Detection Clause Samples

Configuration Mismatch Detection. All bundle links of a MFR must use the same value in the Bundle identification Information Element. The local and remote ends of a bundle link may have different Bundle Identification values as long as the values are consistent with the other bundle links at a specific end of the bundle. Figure 15 illustrates an instance where one device, LONDON, is misconfigured. The link FOX assigned to bundle MARS should be assigned to bundle PLUTO. Device AMSTERDAM will report a bundle consistency error when the ADD_LINK message containing bundle MARS is received on a bundle link assigned to bundle ALPHA when prior ADD_LINK messages contained the bundle identifier PLUTO. Note that if the first ADD_LINK message was received from bundle MARS instead of bundle PLUTO, then the ADD_LINK from one of bundle PLUTO's links would fail. The consistency check is performed based on the first ADD_LINK to arrive. The bundle identification contained in the first ADD_LINK message is always considered the true bundle. Useful Bundle Identification values include network node identifiers, system serial numbers, and network addresses. A de vice should use a unique bundle identifier for each bundle if more than one bundle is supported between two devices. Device: AMSTERDAM Bundle ALPHA Bundle: PLUTO Link: BIRD Bundle PLUTO Bundle MARS Device: LONDON Bundle: PLUTO Link: DOG Bundle: MARS Link: FOX A received ADD_LINK message containing an inconsistent Bundle Identification value or Endpoint Capabilities encoding shall be processed as an invalid ADD_LINK message using the procedure described in Section 4.3.2.5.
View SourceView Similar (2)

Related to Configuration Mismatch Detection

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.