Batboard

Have a fairly simple setup for a cap plus trunking 2 rptrs on firmware r02.30.02

when you first turn them on they appear happy and the trunking takes place as normal after an hour or so its like the master and peer quit communicating and the only traffic that will work is on the master rptr

I have the ips setup correctly best I can tell

master 192.168.1.1 gateway 192.168.1.254 subnet 255.255.255.0 UDP 50000
peer 192.168.1.2 same gateway and subnet udp 50001 peers master udp is 50000

rest channel ip 192.168.1.111 rest udp 55000 on both rptrs

right now I can keyup 4 talkgroups and all is well I can let it set and in an hour or so it will just stop, rebooting the master will fix the issue for a short time

Try making the other repeater the master and the master the peer. You need to change the ips to make it work.

I had the same issue, after 3 hrs on phone with moto that solved the issue. The master wouldn't work as a master, but functioned fine as a peer.

Might I add motorola had no explanation either. These were all new mtr's factory fresh out of the box.

Really? A shoulder shrug, and change the master / peer relationship was their *fix*? What would they say if this was an add-on? Wow.

WIll try that, Left the system running at the office over the weekend will check it Monday to see if its still trunking and if not ill swap them around

Agreed. It was a pain to trouble shoot. The tech on the phone obviously knew to try this "trick" out, as after we exhausted the normal testing like checking IP addresses, ping test, etc. He clearly instructed me to change the master repeater to a different unit.

Now, I am not saying that this is the fix or what is wrong with the OP equipment, but it is a simple place to start out.

Could also try changing out the switch, maybe that is fouled. I would also keep all the ports the same.

haven't swapped the repeater and so far its still working going to install next week after it burns in over the holiday and we shall see how it goes

WEll Spoke to Soon,

Still having issues,

Noticed in RDAC that when I have the issue that the peer does not show up you reboot the master reconnect and the peer is present

I switched the repeaters around so the peer is now the master and get the same error

I have tried 3 switches one being the Motorola preferred procurve we had from a smartnet system and 2 cicso switches so don't think its a switch

No clue why they quit talking

Anyone got any Ideas?

What is the master ip address?

FMROB wrote:What is the master ip address?

Master IP is 192.168.1.1
peer is 192.168.1.2 point to 192.168.1.1 on port 50000

one question I do have on the UDP ports does each rptr gets its own UDP port

so master is 50000
all peers get master udp set to 50000 then there is another udp port box should those be the same 50000 for all repeater or should peer 1 be say 50001 peer 2 50002

I spent 3 hrs on the phone with Motorola yesterday and as normal they were less than helpful with there tech support

celltech25 wrote:

FMROB wrote:What is the master ip address?

all peers get master udp set to 50000 then there is another udp port box should those be the same 50000 for all repeater or should peer 1 be say 50001 peer 2 50002

I spent 3 hrs on the phone with Motorola yesterday and as normal they were less than helpful with there tech support

That is how I did mine, I make the peer UPD port increment by one so they are not using the same UDP. Pretty much I don't bother calling Motorola unless I need to be humored for the day. They rarely have an answer to a question and the answer they do provide doesn't come with much confidence.

Just an idea to toss out there, have no clue at all if it applies or not.

Some managed network switches have various security sort of systems running in them to automatically protect computer networks from various attacks. Some of these sort of functions kick in over time. My thought is that the switch might be seeing whatever network traffic and deciding it does not like it. A total shot in the dark, and I really don't have much more specific than that. I have run into it in my day job as a computer tech with streaming sort of applications.

I am guessing a problem with the repeater itself, but an idea to check into at least. I think the networking term would be a packet flood.

Tim

Yeah I called Motorola to see what they had to say they went through programming and said it all looked good and of course blamed in on the switch, I told them I tried a crossover cable as well and had the same result

I am running RDAC on the system right now to see if when it quits it shows anything in RDAC

we shall see

There seems to be an issue in the firmware that no one wants to confirm.

Here is what I have tried so far that seems to work.

The Master repeater must have a radio ID higher than all peers.
All repeaters must have a unique UDP port.

The rest port UDP port must be the same for all repeaters as well as the IP address.
The master and peers cannot have a 0. in a subnet address, such as 10.0.0.xxx.
Do not assign IP addresses to anything above .200 (don't ask me why on this one, although I did find the repeaters are establishing their own connections BY THEMSELVES on .249 with a very high port number and madly exchanging packets back and forth).

And yes, for some reason, radio IDs, do matter, and make sure your RDAC ID is not higher than your master radio ID either.

so for a 4 repeater setup what would you suggest for the repeater addresses

as far as ip's and id's

2.30.20 repeater FW is still chasing IP connectivity bugs.

upgraded to 2.30.20

Still having a few small issues


for some reason if you busy out all the time slots currently 6 unkey one subscriber and try to key up it will not let you use that 6th time slot until another radio unkeys and there are 2 free slots

Can someone confirm my settings

Link establishment

Master 192.168.1.1
master udp 50000
Ethernet ip 192.168.1.1
gateway 192.168.1.254
netmask 255.255.255.0
udp port 50000
Cap Plus master rest channel 192.168.1.111 rest udp 55000


peer 1
master ip 192.168.1.1
master udp 50000
ethr ip 192.168.1.2
gway 192.168.1.254
netmask 255.255.255.0
udp port 50000
cap plus
rest channel 192.168.1.111
55000

peer 2

master ip 192.168.1.1
master udp 50000
ethr ip 192.168.1.3
gway 192.168.1.254
netmask 255.255.255.0
udp port 50000
cap plus
rest channel 192.168.1.111
55000

Change the peer UDP ports to be different from the master. They still will POINT to the master (Master UDP Port=50000) but supposedly they now must have a unique UDP port for each radio. Try incrementing them by +1 like the individual IP addresses.

As an aside, when your system is showing this activity with one port open, it is NOT beaconing, correct? And your subscriber radios are getting a steady BONK like a no system indication? Yellow light flashing like the radios are roaming around looking for a system to land on?

com501, Correct

so as far as the udp port jsut make them 50000, 50001, 50002

will try that today and see what happens I can say so far that capacity plus is not very stable, like connect plus much better but the cost of the controller is crazy