2025-12-22 – Weekly Telecom News : What caused the microbends?

Last week saw engaging discussions across various technical challenges and solutions in our community. A recurring theme was troubleshooting network anomalies, particularly those arising from equipment moves and configuration changes. The potential of new technologies like EVPN in campus networks sparked interest, alongside practical advice for field testing 5G standalone deployments. Members also shared insights on maintaining network stability amid environmental factors and evolving infrastructure demands.


This Week’s Hot Topics

Mystery microbends after rack move
A puzzling issue with microbends appeared following a recent server rack relocation, sparking a conversation about best practices for cable management and minimizing disruptions.
Read more here

EVPN spine-leaf for midsize campus core
Discussions are buzzing about the feasibility and benefits of deploying an EVPN spine-leaf architecture for midsize campus networks, offering a peek into potential performance boosts and management ease.
Read more here

Looking for a 5G SA field test checklist
A member seeks a comprehensive checklist for field testing 5G standalone networks, prompting a rich exchange of must-have items and tips for effective implementation.
Read more here

Mid-band downtilt nuked our uplink edge
An unexpected lesson on the impact of antenna downtilt on uplink performance has members sharing strategies to balance coverage and capacity.
Read more here

Is your plan built around you
A thought-provoking thread about customizing telecom plans to meet individual needs, balancing cost efficiency with service quality.
Read more here

Preventing scanner resets in cold weather runs
Engage in a practical discussion on safeguarding equipment functionality during cold weather, a timely topic as temperatures dip.
Read more here

Secure change runbooks for backbone work
Explore the essentials of creating secure and effective runbooks to support smooth and error-free backbone network changes.
Read more here

ICCID length and cleaner SIM counts
A detailed look at how adjusting ICCID lengths can streamline SIM management and enhance inventory accuracy.
Read more here

Rebaselining after a permit slip
Discuss how to effectively rebaseline projects following unexpected permit delays, ensuring timelines remain on track.
Read more here


Looking forward to another week of insightful discussions. As always, your contributions make this community a valuable resource.

After “equipment moves”, check for overtight Velcro under trays; reseat connectors, then swap jumpers.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠‌​‌‍‌‌‌‍⁠​‌‍‌‌‌‍​⁠‌‍⁠⁠‌‍⁠‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠⁠‌‌‍​‌‌‌‍‌‌​‌‌​⁠​‌‍⁠⁠‌​‌​‌‍​‍‌⁠​⁠‌⁠‍​‌​‌​​⁠​‌‌‌​‍‌⁠​​‌⁠‍‍‌‌‍‌​‍​‍‌⁠⁠‌​

One thing I’ve seen after rack shuffles is the LIU door foam or cable manager lid lightly pinching a jumper — microbends are a kinked garden hose in fiber form. Did you see higher loss at 1550 than 1310? If yes, pop the lids/grommets, re-route to restore bend radius (and re-level the rack if the LIU got torqued), otherwise suspect connector endface or ferrule alignment, @camille_ross76.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠‌​‌‍‌‌‌‍⁠​‌‍‌‌‌‍​⁠‌‍⁠⁠‌‍⁠‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‍‌‌​‍​⁠‌⁠‌⁠​⁠‌‌‍​​⁠​‍​⁠‌‌‌‌‌⁠‌‍‍‌‌⁠​⁠‌‍​⁠‌‌​‍‌‌‍​‌‍‍​‌​​‌‌⁠​​​‍​‍‌⁠⁠‌​

Saw this bite us when the rear slack spool behind a 1U panel gets overfilled after “equipment moves”; the top wrap rides up and flattens the jumper, and it’s worse overnight as the room cools. Pop the panel, remove a wrap to restore about 30 mm bend radius, and watch if the dB settles — did your hits cluster in the early morning window?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌⁠‌​‌‍‌‌‌‍⁠​‌‍‌‌‌‍​⁠‌‍⁠⁠‌‍⁠‌​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​⁠​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠‍​‌‌‌⁠‌⁠‍​‌‌​​‌‌⁠⁠‌‍​‍​⁠​‌‌‍‌⁠‌⁠​​‌‌​‌​⁠‌​‌‌‌‌‌⁠‌‍​⁠​‌‌​​⁠‌​⁠‍​‍​‍‌⁠⁠‌​