I have installed an AIRMatrix radio onto a tower site which has an MT RB/600.
The RB/600 ‘ether 2’ port is interfaced with the only ethernet port on the AIRMatrix radio.
At this point I am able to ping the AM radio at 10.0.0.14 from any point within the network, but I need to communicate to the AM radio VIA port 3517 for configuration with the NMS software.
The Configuration
RB/600 ether2 IP: 192.168.2.4
RB/600 Default Gateway: 10.0.0.3
AIRMAtrix Radio ether1 IP: 10.0.0.14
Primary Infrastructure Network: 10.0.0.0/24
I have attempted using Filter Rules and NAT unsuccessfully in trying to get it where the AIRMatrix NMS application can access the destination port 3517.
When I attempt to access the AM radio VIA HTTP, Telent or SSH at 10.0.0.14 either one actually logs into a NOC radio 10.0.0.3 between this tower and the NOC itself.
What method would I use to achieve communications to the AM radios :3517 enabling use of the NMS software AIRMatrix wrote for their radios?
Thanking you in advance for your help with this issue.
RB600’s Ether2 has an IP of: 192.168.2.4.. and the device plugged into that port (airmax) has an IP on a completely different subnet (10.0.0.14/24)?
I’d say that’s your problem… the RB600 doesn’t know that 10.0.0.14/24 is connected to ether2 because it thinks 192.168.2.0/24 is the only subnet on that interface.
I don’t see how you’re even pinging this device..
can you describe the network a little better..? I don’t see the relationship between the RB600, airmax, and the 192.168.2.0/24 10.0.0.0/24 networks.
can you describe the network a little better..? I don’t see the relationship between the RB600, airmax, and the 192.168.2.0/24 10.0.0.0/24 networks.
The RB/600 is equipped with 3 5Ghz cards serving 1 AP and 2 links and 1 900Mhz card serving NLoS clients.
The primary IP network used throughout the wireless distribution network is within the 10.0.0.0/24 subnet, from ether2 of the RB/600 IP 192.168.2.4 I am wanting to tie into the AIRMatrix radio which is to feed another area exclusively with the AIRMatrix equipment.
RB/600 ether2 IP: 192.168.2.4/24
RB/600 Default Gateway: 10.0.0.3/32
5Ghz Link 1 IP: 10.0.0.4/24
5Ghz Link 2 IP: 10.0.0.5/24
5Ghz AP 1 IP: 10.0.0.6/24
900Mhz AP 1 IP: 10.0.100.1 (routed)
ether1 of the AIRMatrix radio is 10.0.0.14
At the back-end my wireless systrem interfaces into a LOK Box 325 with it’s LAN side interfaces configured with the following networks:
10.0.0.0/24 (system infrastructure)
10.10.0.0/24 (following networks aree for client devices only)
172.16.2.1/24
172.16.3.1/24
172.16.4.1/24
172.16.5.1/24
172.16.6.1/24
172.16.7.1/24
172.16.8.1/24
where is the NMS located in this?
The NMS is simply software that is installed on desktop PC’s & LapTops in and out of the office.
I don’t see how you’re even pinging this device..
Here are results while logged into the RB/600 just a moment ago:
[MyAdmin@<–TOWER 1 RB/600 QuadPlay–>] > ping 192.168.2.4
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
192.168.2.4 64 byte ping: ttl=64 time<1 ms
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 0/0.0/0 ms
[MyAdmin@<–TOWER 1 RB/600 QuadPlay–>] > ping 10.0.0.14
10.0.0.14 64 byte ping: ttl=64 time=31 ms
10.0.0.14 64 byte ping: ttl=64 time=30 ms
10.0.0.14 64 byte ping: ttl=64 time=30 ms
10.0.0.14 64 byte ping: ttl=64 time=40 ms
10.0.0.14 64 byte ping: ttl=64 time=40 ms
10.0.0.14 64 byte ping: ttl=64 time=39 ms
10.0.0.14 64 byte ping: ttl=64 time=44 ms
10.0.0.14 64 byte ping: ttl=64 time=39 ms
10.0.0.14 64 byte ping: ttl=64 time=44 ms
10.0.0.14 64 byte ping: ttl=64 time=39 ms
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 30/37.6/44 ms
I found that all I needed to do was to place the port ether2 on the RB/600 into the Bridge and all communications was then opened for IP traffic and use of the AIRMatrix Network Management System ‘NMS’.