It must be a bug in the code because I've tried that very section, and it barks at me that a gatekeeper zone is already configured and bounces me out of the config. I was able to make it work by registering the gateway to the two gatekeepers using different zones, but the problem is in the prefixes.
ok, obviously we can't say if this scenario would or would not be on the test, I thought that I should at least be prepared to handle it since I have two gatekeepers in my lab and can try it out. Thanks, Jeff -----Original Message----- From: Chris Parker To: Jeff BCI Cc: OSL Group Sent: 9/24/08 8:52 AM Subject: Re: [OSL | CCIE_Voice] Lost in Gatekeeper redundancy world Then I think you can use alternate gatekeeper as described here: http://www.cisco.com/en/US/docs/ios/12_3/vvf_c/cisco_ios_h323_configurat ion_guide/old_archives_h323/4gwconf.html#wp1036777 In CCM, I guess you would have 2 trunks to each GK and put both in a RL to do the failover from the ccm side. Though I'm not sure how this could come up on a lab given the topology. The logical choice for the GK is HQ, BR1 and BR2seem like bad choices for a redundant GK ... If HQ goes down you would lose connectivity to BR1 and BR2 Chris Jeff BCI wro te: > thought about that as well, but GKs will be in different subnets, hence > HSRP won't work. > > Wish it were that easy, rumor has it if I get a GK lab, this scenario is > there. > > Thanks, Jeff > > -----Original Message----- > From: Chris Parker > To: Jeff BCI; OSL Group > Sent: 9/23/08 8:53 PM > Subject: RE: [OSL | CCIE_Voice] Lost in Gatekeeper redundancy world > > I believe the way to do this is with HSRP? If a GK fails its IP moves to > the backup GK > > -----Original Message----- > From: Jeff BCI <[EMAIL PROTECTED]> > Sent: Tuesday, September 23, 2008 10:52 PM > To: Jeff BCI <[EMAIL PROTECTED]>; OSL Group > <ccie_voice@onlinestudylist.com> > Subject: Re: [OSL | CCIE_Voice] Lost in Gatekeeper redundancy world > > forgot to show the gateway's relevant config. > > -Jeff > > -------------------------- > Branch-B-2611XM# > Branch-B-2611XM#sh run int lo0 > Building configuration... > > Current configuration : 247 bytes > ! > interface Loopback0 > ip address 10.255.255.5 255.255.255.255 > h323-gateway voip interface > h323-gateway voip id Branch-B_ZONE ipaddr 10.255.255.10 1719 > h323-gateway voip h323-id Branch-B-2611XM > h323-gateway voip bind srcaddr 10.255.255.5 > end > > Branch-B-2611XM# > ---------------------------- > > -----Original Message----- > From: Jeff BCI [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 23, 2008 10:48 PM > To: OSL Group > Subject: [OSL | CCIE_Voice] Lost in Gatekeeper redundancy world > > > Greetings. > > Ok, all of my gatekeeper work is good, no problems there, but I'm trying > to > learn how to use two gatekeepers for redundancy (not load balancing) > such > that if GK_A croaks, the gateways registered to GK_A can then > automatically > move to GK_B without any manual intervention. I do have GK basic > redundancy > configured on GK_A and GK_B, I can see that this works fine, but the > gateways won't move over. > > Here's what I did. > > GK_A - the primary GK > configured in CUCM with trunk ccm-trunk, GK configured as well, works > fine > configured clustering to GK_B, that too works fine > > ---------------------- GK_01 config ------------- 10.255.255.10 > gatekeeper > zone local GL_ZONE bciassoc.net 10.255.255.10 > zone local HQ_ZONE bciassoc.net > zone local Branch-B_ZONE bciassoc.net > zone cluster local GKC_GL_ZONE GL_ZONE > element GL_ZONE_ATL_GK02 10.255.255.2 1719 > ! > zone prefix Branch-B_ZONE 1050.. > zone prefix HQ_ZONE 20.. > zone prefix HQ_ZONE 30.. > zone prefix HQ_ZONE 40.. > zone prefix Branch-B_ZONE 50.. > gw-type-prefix 999#* > gw-type-prefix 1#* default-technology > bandwidth interzone default 672 > bandwidth check-destination > no shutdown > ! > ------------------------- > > > did the exact same thing on GK_B > > ----------------- GK_02 config ----------- 10.255.255.2 > > ! > gatekeeper > zone local HQ_ZONE bciassoc.net 10.255.255.2 > zone local Branch-B_ZONE bciassoc.net > zone local GL_ZONE_ATL_GK02 10.255.255.2 > zone cluster local GKC_GL_ZONE GL_ZONE_ATL_GK02 > element GL_ZONE 10.255.255.10 1719 > ! > zone prefix HQ_ZONE 20.. > zone prefix HQ_ZONE 30.. > zone prefix HQ_ZONE 40.. > zone prefix Branch-B_ZONE 50.. > gw-type-prefix 1#* default-technology > bandwidth interzone default 144 > bandwidth check-destination > no shutdown > ! > ---------------------------------------- > > GK01# > GK01#sh gatek clu > > CONFIGURED CLUSTERS > =================== > Cluster Name Type Local Zone Elements IP > ------------ ---- ---------- -------- -- > GKC_GL_ZONE Local GL_ZONE GL_ZONE_ATL_G 10.255.255.2 1719 > > GK01# > ------------------------- > GK02#sh gatek clu > > CONFIGURED CLUSTERS > =================== > Cluster Name Type Local Zone Elements IP > ------------ ---- ---------- -------- -- > GKC_GL_ZONE Local GL_ZONE_ATL_GK0GL_ZONE 10.255.255.10 > 1719 > > GK02# > ------------------------- > > so they see each other, registered and whatnot, but I can't figure it > out > nor find out why. I bought a Cisco Press book "Cisco Voice Gateways and > Gatekeepers" and found a wealth of tips and things that cleared up my > understanding of gatekeepers, but it is completely missing anything on > actually showing this redundancy function in use. > > Thanks, Jeff > > > > > >
