Coding universal SFP/XFP modules to Hirschmann M-SFP part numbers for RS30 and MACH104
I do industrial installs, mostly Hirschmann switches in cabinets nobody wants to open twice. On the last couple of projects the optics were the line item that hurt: the switches expect Hirschmann-coded modules, and the original M-SFP parts cost several times an equivalent generic module, with lead times to match.
What is in front of me:
- RS30 and MACH104 in the cabinets, one GRS1020 closing the ring
- singlemode and BiDi links, plus CWDM channels spread across the 1270-1610 nm range
- two XFP uplinks between buildings, reaches from a couple of km up to the long spans
- the parts I need equivalents for, straight off the BOM:
M-SFP-LH/LC
M-XFP-LR/LC
The plan is to buy programmable universal modules and write the Hirschmann coding into them, the way people have been doing for years with Cisco and HP gear. Matching wavelength and optical budget from datasheets I can do myself. What I want to know is whether the coding side has surprises:
- has anyone run coded universal modules in RS30 / MACH104 / GRS1020 long-term, or does the switch keep grumbling in the log even after the link comes up?
- for cabinets that see real temperature swings, is the industrial variant (the D-I / D-IL suffixed parts) the thing to match, or is a standard-grade module fine inside a heated enclosure?
- when you code to an M-SFP part number, is anything beyond the vendor string and part number being checked, or is that the whole gate?
Comments 0
No comments yet.