Need a strategy for MCU redundancy

Unanswered Question
Jan 23rd, 2010

I have 2 MCUs working fine on my network.  One is a MCU 3515, the other is an older MCU 3545.  Both register with the same gatekeeper and work fine.

How do I configure these to work as backups to each other?  I'm sure there are many strategies, what would you recommend?

Here is what I'd "like" to do, but I'm not sure if it's possible or not.

All prefixes 20* go to MCU3515

If MCU3515 fails, then all 20* go to MCU3454.

All prefixed 80* go to MCU3545

If MCU3545 fails, then all 80* go to MCU3515.

Thank you.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
gogasca Wed, 01/27/2010 - 01:14

MCU will register their prefixes to GK, (Terminal)

Then based on that you can assign priorities for terminals or/prefixes

Can you post your show gatekeeper endpoints

and show run for gatekeeper portion

and we can post a config for you

Tod Larson Wed, 01/27/2010 - 06:10

Here is the output you requested. You can see, you can see the gatekeeper is in a 2 GK cluster.  That feature is working just fine so if one gatekeeper router fails then the other gatekeeper router picks up and continues.

thank you.

#sh gatekeeper endpoints



CallSignalAddr Port RASSignalAddr Port Zone Name Type Flags

--------------------- ------ ---------------------- -------- ---------------- ------- -------- 2720 2719 H323GK-1 H320-GW

H323-ID: Cisco MCU-192168003003 1720 1719 H323GK-1 H320-GW A

H323-ID: Cisco MCU-192168003010 46702 32024 H323GK-1 TERM

H323-ID: GatekeeperControlledTrunk_1

# sh gatekeeper gw-type-prefix



Prefix: 20*

Zone: H323GK-1 master gateway list: Cisco MCU-192168003010

Prefix: 80*

Zone: H323GK-1 master gateway list: Cisco MCU-192168003010

# sh run



zone local H323GK-1

zone cluster local H323GK H323GK-1

element H323KG-2 1719



This Discussion