µMAGBES Frequently Asked Questions
Manuals, Data Sheets, and Press Releases can be found in the
MPL Documentation area of this homepage.
| Question #414: | Is the µMAGBES an OSI layer 3 switch? |
| Answer: | The µMAGBES is a layer 2 switch with some layer 3 protocols implemented. Full-featured layer 3 routing is not possible. If you need full layer 3 support, you may have to look at the µGUARD product from MPL. |
| Question #373: | I try to use a third-party SFP with your MAGEBS / TX2FX but it does not work. If I insert the SFP into a media-converter / switch of a different brand, it works without a problem. Is the MAGEBS / TX2FX broken? |
| Answer: | Not necessarily. According to the standard "SFP Multi Source Agreement" (SFP MSA), all SFP modules contain a small memory device, where the capabilities supported by a particular SFP are being stored. Problems of the above mentioned kind are mostly caused by incorrect or even missing capability information. Because the MAGEBS / TX2FX is able to "translate" between different link speeds and media types, it is absolutely vital that the SFP module reports accurate capability information. Otherwise the MAGEBS / TX2FX is unable to set up its internal hardware correctly. For media-converters supporting only one link speed and / or media type, reading and interpreting the SFP information may not be necesarry at all, which may explain why the SFP works in conjunction with theses devices. Therefore please recheck with a SFP module from another manufacturer. If this is not an option, please contact the SFP manufacturer and make sure that the SFP meets the MSA specification and is Ethernet compatible. SFP modules which only support "Fibre Channel" or "SONET" are NOT supported by the MAGEBS / TX2FX! |
| Question #407: | Can I use my Cisco and/or HP branded SFP modules with your products? |
| Answer: | Some big network companies, such as Cisco or HP, sell SFP modules which will work only with their own network equipment. They use special contents in the EEPROM of the SFP to identify their own modules. Since the contents of the EEPROM is a part of the "SFP Multi Source Agreement" (SFP MSA), these SFP's are not MSA compatible and therefore are not supported by the MPL product. But this does not necessarily mean that the MPL products will not work together with third-party products on the other end of the network link. If you find and use a MSA compliant SFP with the same wavelength and other optical parameters as the unsupported SFP, then the odds are good that a network connection between the MPL product and the third-party network device can be established. |
| Question #392: | If we use your MAGBES / TX2FX in conjunction with other, non-MPL network products, we are facing more or less severe compatibility problems. All is fine if we don't use your product. Is there a fix or work-around to make your product work as expected? |
| Answer: | Most probably there is NO fix or work-around! As a general rule of thumb, please make sure that the SFPs used and/or your other non-MPL products are ethernet compliant. Also check the other "compatibility" related FAQs in this section. |
| Question #383: | I try to use your MAGBES with a SFP module from a big networking equipment producing company, but it does not work. Is there a MAGBES configuration option that I can change to make it work? |
| Answer: | Please note that some companies are selling SFP modules which are specially designed to be usable only with their own network products. While these modules may normally be compatible with the MAGBES from a mechanical point of view, they are NOT compatible from the "software" point of view. Please make sure to use a SFP module which fully meets the MSA standard and is Ethernet compatible as described in the FAQs referenced below: |
