Configuring Directory Gatekeepers
As the number of gatekeepers in a network grows, the administrative overhead that is associated with adding gateways or prefixes grows exponentially. You must replicate every change or addition in each gatekeeper. For large networks, a directory gatekeeper can reduce the administrative overhead that is associated with multiple gatekeepers. The following steps describe how to migrate from a full mesh gatekeeper environment to a directory gatekeeper:
|
Step 1. |
Configure a local zone in the directory gatekeeper. By convention, the hostname of the directory gatekeeper is used for the local zone name. No prefixes are configured for this local zone, because endpoints do not register with the directory gatekeeper.
|
|
Step 2. |
Configure each remote zone in the directory gatekeeper and the prefixes that are associated with each zone.
|
|
Step 3. |
Configure the directory gatekeeper to forward LRQ messages using the lrq forward-queries command. This command is what turns a standard gatekeeper into a directory gatekeeper.
|
|
Step 4. |
Add a remote zone in each gatekeeper for the directory gatekeeper.
|
|
Step 5. |
Add a prefix of * pointing to the directory gatekeeper. This causes the gateway to send an LRQ to the directory gatekeeper for all unknown prefixes. The directory gatekeeper forwards the LRQs to the appropriate gatekeeper based on the prefixes that are defined in Step 2.
|
|
Step 6. |
Remove all remote zones and prefixes from the gatekeepers except for the zone and prefix that point to the directory gatekeeper. Only the local zones and prefixes should remain.
|
Example 17-8 shows the configuration that is necessary to add a directory gatekeeper to the previous example.
|
CORPORATE GATEKEEPER GK_Corp#show running-config Building configuration... ! ! Unnecessary output deleted ! interface Loopback0 description Gatekeeper interface ip address 10.100.101.1 255.255.255.255 ! gatekeeper zone local ny cisco.com 10.100.101.1 zone local boise cisco.com zone remote DGK cisco.com 10.1.10.15 1719 zone prefix boise 120855501.. zone prefix ny 1212555.... zone prefix DGK * gw-type-prefix 1#* default-technology rrq dynamic-prefixes-accept no shutdown ! end |
|
NEW DIVISION GATEKEEPER GK_NewCo#show running-config Building configuration... ! ! Unnecessary output deleted ! interface Loopback0 description Gatekeeper interface ip address 10.100.100.1 255.255.255.255 ! gatekeeper zone local miami cisco.com 10.100.100.1 zone remote DGK cisco.com 10.1.10.15 1719 zone prefix miami 130555501.. zone prefix DGK * gw-type-prefix 1#* default-technology rrq dynamic-prefixes-accept no shutdown ! end |
|
DIRECTORY GATEKEEPER DGK#show running-config Building configuration... ! ! Unnecessary output deleted ! interface Loopback0 description Gatekeeper interface ip address 10.1.10.15 255.255.255.255 ! gatekeeper zone local DGK cisco.com 10.1.10.15 zone remote miami cisco.com 10.100.100.1 1719 zone remote ny cisco.com 10.100.101.1 1719 zone remote boise cisco.com 10.100.100.1 1719 zone prefix miami 130555501.. zone prefix boise 120855501.. zone prefix ny 1212555.... lrq forward-queries gw-type-prefix 1#* default-technology rrq dynamic-prefixes-accept no shutdown ! end |
Troubleshooting Gatekeepers
|