• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Hardware/Software Co-Development, Verification…
  3. XFP not supporting FC800 services OSN8800 TN55TQX

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 49
  • Views 13059
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XFP not supporting FC800 services OSN8800 TN55TQX

Joshuakoo
Joshuakoo over 10 years ago

TN55TQX card in general supports various service types including STM-64, OC192, 10GE, FC800, FC1200 or OTU2. However there are dedicated XFP modules (BOMs) for different services. Unfortunately U2000 does not alert or notify when user creates service with wrong XFP type. Moreover many XFPs will actually work although wrong service type is created. For example customer ordered several TQX cards equipped with: 10GE/STM64 dedicated XFPs (BOM 34060313), and FC800 dedicated XFPs (BOM 34060658). However XFPs arrived distributed randomly and customer didn’t pay attention to verify XFP type while creating services. Unexpectedly most services ware working although wrong XFP BOMs were used. Eventually one of the FC800 services failed and after investigation XFPs mismatch across the network has been discovered on OSN 8800.

Software version OSN 8800 V100R007C02SPC200

iManager U2000 V100R008C00SPC300

The following XFP types have been delivered to the customer:

BOM 34060313 (dedicated for STM64/10GE):

-          FTLX1412M3BCL(also working when FC800 configured)

-          FTLX1413M3BCL-HW (also working when FC800 configured)

-          SXP3104NV-H1

-          TRF5013FN-GA420

-          TRF5015FN-GA420

BOM 34060658 (dedicated for FC800 services):

-          PT745F-81-1D (also working when 10GE or STM64 configured)

The problem with XFP mismatch has been discovered when FC800 service was created with XFP SXP3104NV-H1 type.  U2000 didn’t rapport any problems although the far end equipment reported link down. The issue has been resolved by relocating XFPs across the network to get dedicated XFPs for all relevant services.Wrong XFP types were used when crating FC800 serviceXFP modules relocation

Although some XFP types can work even when incorrect service type is created, this configuration is not recommended or supported by Huawei transport network. There is no guarantee this configuration is stable, and under certain conditions errors might occur.

  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information