Common use of Configuration Mismatch Detection Clause in Contracts

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.

Configuration Mismatch Detection. All bundle links of a MFR must use the same value in the Bundle identification Information ElementField. 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 device 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.