Skip to main content

KEYMILE ROFBU 367 105/1 SYNIO Interface Card (UMUX)

Keymile

Call For Pricing

SKU:
ROFBU 367 105/1
Condition:
Refurbished
Availability:
Usually ships in 24 hours
Weight:
2.00 LBS
Ship from:
Dublin - Ireland
Hs code:
8517.62

The KEYMILE ROFBU 367 105/1 is a plug-in card identified by the functional designation SYNIO, used within the Keymile UMUX multi-service access and transport platform. This part was also distributed under the Nortel brand (Nortel resold/rebranded Keymile UMUX equipment in certain markets), so listings may reference either "Nortel" or "Keymile" as the manufacturer for the same physical card. Based on its naming convention (SYN- prefix, shared with other synchronization/timing-related UMUX units such as SYNAC, SYNAD, SYNUF, SYN4E), SYNIO likely relates to synchronization/timing interface or I/O functions within the UMUX system core. UMUX is a carrier-grade multiplexer platform used by dedicated network operators such as utilities, railways, and airports; Keymile was acquired by ABB in 2017, and the UMUX range was later discontinued — cards like this are now sourced mainly as refurbished or pulled spares.

Key Features:

  • One-slot plug-in unit for UMUX subracks
  • Functional designation SYNIO — part of the SYN-series synchronization/timing unit family
  • Cross-branded: sold under both Nortel and Keymile labels
  • Managed via Keymile UCST/UNEM network management tools

Technical Specifications:

  • Manufacturer Part Number: ROFBU 367 105/1
  • Hardware Revision: R1C
  • Date Code: 2003W48 (week 48, 2003)
  • Functional Unit Type: SYNIO
  • Manufacturer: KEYMILE AG (also distributed as Nortel)
  • Platform Compatibility: UMUX
  • Form Factor: Single mechanical slot, standard UMUX plug-in unit
  • Note: Exact port count and electrical/signal specification for SYNIO were not found in a standalone public datasheet — its function family (synchronization/timing) is inferred from naming convention and card family context; recommend verifying exact function with Keymile/DZS legacy documentation before publishing precise technical claims.
90 DAY'S