Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Implement transceiver support.
See original GitHub issueAs discussed in #430, Unified plan does not permit non-initiators to add media lines. The initiator must instead create a transceivers for each media streams it wants to receive.
We can either expose addTransceiver or use the out-of-band “renegotiate” signal message to call addTransceiver on the initiator automatically during negotiation.
An urgent subset of #351.
Issue Analytics
- State:
- Created 5 years ago
- Comments:17
Top Results From Across the Web
How to Use Cisco DOM for All Transceivers Type?
Ensure that your optical transceiver supports DOM. For Cisco original optical transceivers, you need the transceiver module compatibility ...
Read more >Turn ON digital optical monitoring (DoM) - Cisco Community
Transceiver supports it, as Digital Optical Monitoring Compatibility Matrix said (GLC-ZX-SM). ... What I should do to implement collecting DOM info?
Read more >Determining Transceiver Support and Specifications
Use the Hardware Compatibility Tool to determine if your transceiver supports monitoring. See the Junos OS documentation for your device for a description ......
Read more >How to Use the Transceiver Optics Compatibility Matrix
Will this SFP work in my switch? We go over how to check compatibility of different transceivers (SFP, QSFP, Etc..)
Read more >Forcing A Cisco Catalyst Switch To Use 3rd Party SFP Modules
the use of third-party transceivers installed by a customer or reseller, then, at Cisco's discretion, Cisco may withhold support under warranty or
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@t-mullen Your latest change appears to have corrected my issue. I am able to repeatedly add and remove (and re-add) secondary streams from the non-initiator now. Thank you 😃
@t-mullen Yes, this behavior only occurs when removing a stream and the adding a new/different stream.