If you have IBM enabled on both sides of the link and running on a different subnet than the OBM, you can use the debug node to check for connectivity to the other side as well as telnet or ssh to the other radio for management. It will require an active link and anything that is changed that would cause link loss will cause the IBM management across the link to be lost as well.
Follow the normal steps to setup IBM on each side of the link by configuring an IP address that is in a subnet different from the Out of Band Management IP address. This IP address does not need to be something that is routed on your network as it will only be used between the two radios. You can even assign it to a port that isn't in use so that the traffic cannot leave the radio. Ensure the vlan is set the same on both sides. The default settings when configured in the factory are for A side to be 172.16.1.1/24 and B side 172.16.1.2/24 on vlan 4085. It will be set to default to port ge1, but this can be changed if you do not want this traffic getting onto your production network.
(.51-config)# ibm ip 172.16.1.1 255.255.255.0
IBM IP Address: 172.16.1.1
IBM netmask: 255.255.255.0
(.51-config)# ibm vlanid 4085
IBM IP vlan ID: 4085
(.51-config)# ibm port 1
IBM Port: ge1
(.51-config)# ibm enable on
IBM enable: on
IBM Enable: on
IBM Vlan ID: 4085
IBM Port: ge1
IBM IP address: 172.16.1.1
IBM Netmask: 255.255.255.0
From either side when in the command line, enter debug node by typing debug at the config node prompt. You can then ping the other side - or any other device on the network - with ping <ip address>, i.e. ping 172.16.1.2. To stop the ping, press ctrl+c. If you get ping success, you can then try logging into the far side via telnet or ssh. <telnet 172.16.1.2> or <ssh firstname.lastname@example.org>.
debug> ping 172.16.1.2
PING 172.16.1.2 (172.16.1.2): 56 data bytes
64 bytes from 172.16.1.2: seq=0 ttl=64 time=1.108 ms
64 bytes from 172.16.1.2: seq=1 ttl=64 time=0.990 ms
--- 172.16.1.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.990/1.049/1.108 ms
debug> ssh email@example.com
ssh: Warning: failed creating /home/default/.ssh: Permission denied
Host '172.16.1.2' is not in the trusted hosts file.
(fingerprint md5 00:re:mo:ve:d0:00)
Do you want to continue connecting? (y/n) y
Trango System: TrangoLINK GigaPlus Command Line Interface v1.3.3
Since you will then be logged into the other side of the link and your telnet/ssh window may indicate you are in the local radio, it is suggested that you change the cli prompt to indicate which side you are managing. In CLI config node, use the command prompt followed by ten characters to identify the radio. This is similar to remark, but has fewer characters since it is printed on every line.
(.51-config)# prompt trango
(trango-config)# prompt SiteA>B
(SiteA>B-config)# prompt .51
To return to the local radio, either open a new cli session via telnet or ssh in your client, or from the remote radio's debug node, type exit. You'll then be back at the debug node of the first radio.
At this point you can use the command <cli> to return to the view node or type exit to close the session.