Batboard

I had an IPSC network that was working great until I had to replace my master repeater. I copied all the settings over to the new master repeater and all of a sudden my IPSC network can transmit messages from my master repeater but not receive. Plus my peers cannot receive any calls.

Anyone have any ideas? The only thing that has changed is the Master repeater hardware.

You need to reset your peers after replacing a master.

Alex

Had a customer with a similar situation after replacing ethernet boards on 4 repeaters.

The fix was to set the RSSI threshold to -40db. Something about the FCC lockout. May be related to the firmware of your master.

Can I reset the peers via RDAC or does it need to be a hard power cycle?

All the firmwares are the version before the current one.

marcosorourke wrote:Can I reset the peers via RDAC or does it need to be a hard power cycle?

All the firmwares are the version before the current one.

I am not sure if you can power cycle via RDAC. If they are XPR8400's and you can connect to them reading/writing the codeplug using the remote program feature may do it.

Let's assume though you could power cycle through RDAC. You replaced your master. The Peer's which are not working may not reconnect to the master. When you connect RDAC to the master you may or may not see the peer's to even send that reset. I would connect up with RDAC and see what you see.

I'd suggest you just have a local contact or go through and power cycle the repeaters yourself. Look in to some IP enabled power controls so you can do remote on/off via SNMP or other network commands for your remote sites. Consider using vpn tunnels or other technology to keep your mototrbo network on a closed network.

Alex

Thanks for the info Alex.

All of our repeaters are on a VPN.

I can see my whole network on RDAC when I connect to the Master. I'll try sending the Reset command and see if that wakes them up, otherwise I'll have to do it on my next visit to the sites.

Confirm your "Authentication Key" mataches for each repeater ?

There's no authentication key.

I tried to put the old repeater back in but that didn't wake things up. Looks like I need to make some trips out to our sites.

Thank you all for the feedback.

.. bummer. Storms damaged the network port on one of our Master repeaters last Friday. We had a backup MTR3000 sitting at the tower site. I read the config off the damaged repeater and cloned it to the new one; cabled everything back and everything came back up fine within a few minutes (5 peers). Sounds like we did the exact same thing....

TreyH wrote:.. bummer. Storms damaged the network port on one of our Master repeaters last Friday. We had a backup MTR3000 sitting at the tower site. I read the config off the damaged repeater and cloned it to the new one; cabled everything back and everything came back up fine within a few minutes (5 peers). Sounds like we did the exact same thing....

Same here. I've blown a codeplug into a spare repeater, taken it to site, swapped it in, and budda-bing budda-boom, everything is working again.

TreyH wrote:.. bummer. Storms damaged the network port on one of our Master repeaters last Friday. We had a backup MTR3000 sitting at the tower site. I read the config off the damaged repeater and cloned it to the new one; cabled everything back and everything came back up fine within a few minutes (5 peers). Sounds like we did the exact same thing....

Time for a refresh of the site grounding, eh?

Yes, the peers *should* rediscover the master within a few minutes of replacement. In fact, they should have all kept working among themselves even while the master was out of commission, as their peer tables were already built, so the master wasn't needed...it's technically only required when trying to add or replace a peer to the system, assuming all peers sites stay powered up & communicating via networking.

The fact that you can see the repeaters via RDAC tells us that they have 'reported' and the master knows about them, otherwise you wouldn't see them. So it's odd that the voice part isn't working. That could be a firmware issue, if the new master is significantly different from the peers.

It sounds like you were not able to reset them remotely...or if you could it didn't seem to help? Let us know if manually resetting them gets things going again.

escomm wrote:

TreyH wrote:.. bummer. Storms damaged the network port on one of our Master repeaters last Friday. We had a backup MTR3000 sitting at the tower site. I read the config off the damaged repeater and cloned it to the new one; cabled everything back and everything came back up fine within a few minutes (5 peers). Sounds like we did the exact same thing....

Time for a refresh of the site grounding, eh?

he he, yep. The 911 district owns the tower and their IT crew recently installed an IP security camera on the tower. They used copper ethernet cabling and ran it straight in from the tower, right past a thousand dollars worth of polyphasers and plugged it directly into the network switch. Go figure that....