Follow the arrows.  "RADIO CPU" means access to the device itself.  In this case GE1 can only connect to the "RADIO CPU" for mgmt access.  GE2 and RF interface can't connect to mgmt.

GE2 and the RF Interface connect to each other and nothing else. So that's the path for your payload.

So yeah you're always going through the switch, but the arrows show you which ports are grouped together.  Ports with arrows between could be thought of like ports in the same bridge on a Mikrotik.

PLA I think is for N+1.  So one switch module could take over a different radio module through the PLA port.  On this particular diagram it's just clutter and can be ignored.


On 10/29/2020 3:05 PM, Adam Moffett wrote:
I just downloaded the manual.  The short version is

IBM ON = both ports are switched together (but you can choose to allow mgmt traffic on only a specific one).  If you have IBM ON at both ends then you can use either port on either end for service traffic, and assuming you only connected one port you should probably make that one the mgmt port, but also note that mgmt access is allowed through the RF port regardless of which ethernet port is selected for Mgmt.

IBM OFF = both ports are separate.  The Mgmt port only access the radio, and the other carries the service traffic.

If you have IBM OFF then whichever port is NOT your mgmt port is the service traffic port.  So you could still mix SFP+Copper if you pick opposite mgmt ports on each side.  And in this mode it's noteworthy that mgmt access is NOT allowed through the RF interface, so mgmt traffic must be allowed to pass all the way through to the site's switch/router and back up through the second cable to the mgmt port.

That's 5 pages of manual condensed to 4 sentences.

They don't spell it out in the manual, but if IBM is ON then you could create a switch loop by connecting both cables to one switch.  I know this because I've done it accidentally.  Probably should avoid that.


On 10/29/2020 2:50 PM, Nate Burke wrote:
I read through the manual, and saw all the different modes described, but wasn't super clear how you configured those different modes.  It looks like the copper and SFP are in the same switch group regardless, but you have to choose which port management is on.

On 10/29/2020 1:47 PM, Adam Moffett wrote:
Now that I think about it more, the Plus had two modes shown in the GUI.  I think it was "Smart Mode" or something like that.  In one mode all the ports were in one switch group, and in the other mode they were separated by internal VLAN's.  If you wanted that VLAN mode on, but wanted to get creative like map port 2 on one to port 4 on the other, then that was where only Trango support could do it.

On the Lynx/Orion the settings for this are not obvious until you read the manual.  The OOB mode was one of the options that affected it, but there was another one too.  They had diagrams showing the pathways you'd create when you set those options in different ways.


On 10/29/2020 2:39 PM, Adam Moffett wrote:
On Giga/Apex Plus the ports were mapped 1 to 1, and there wasn't a way to change that mapping through the normal means (but Trango could by logging in as root and editing a VLAN config file).

On Giga/Apex Lynx the ports are all switched together in the default config.  You could change that behavior and the manual described a few different modes, but in the default config it absolutely did work to use SFP on one side and copper on the other.

I have not used Orion.....but it has the same software and instruction manual as the Lynx, so I'd bet it's switched together on that one too.


On 10/29/2020 2:27 PM, Nate Burke wrote:
It's been years since I've had to mess with the configuration, but something is rattling around in the back recesses of my mind.  Can you use the Copper port on one end of the link, and the SPF Port on the other end of the link? Something keeps popping up in my mind about virtual channels between interfaces, and the copper on one end only talks to the copper on the other end and same for the SFP. Maybe it was a different radio manufacturer that did that?




-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Reply via email to