Administration of the Avaya G350 Media Gateway - Avaya Support
Administration of the Avaya G350 Media Gateway - Avaya Support Administration of the Avaya G350 Media Gateway - Avaya Support
Configuring the routerDHCP/BOOTP relayThe Avaya G350 Media Gateway supports the DHCP/BOOTP relay agent function. This is anapplication that accepts DHCP/BOOTP requests that are broadcast on one VLAN. Theapplication sends them to a DHCP/BOOTP server. That server connects to another VLAN or aserver that might be located across one or more routers that might otherwise not get thebroadcast request. The relay agent handles the DHCP/BOOTP replies as well. The relay agenttransmits the replies to the client directly or as broadcast, according to a flag in the replymessage.Note:Note:The same DHCP/BOOTP relay agent serves both the BOOTP and DHCPprotocols.When there is more than one IP interface on a VLAN, the G350 chooses the lowest IP addresson this VLAN when relaying DHCP/BOOTP requests. The DHCP/BOOTP server then uses thisaddress to decide the network from which to allocate the address. When there are multiplenetworks configured, the G350 performs a round-robin selection process.When the DHCP/BOOTP server is configured to allocate addresses only from a singlesubnetwork among the different subnetworks defined on the VLAN, you might need to configurethe G350 with the relay address on that subnet so the DHCP/BOOTP server can accept therequest.DHCP/BOOTP Relay in G350 is configurable per VLAN and allows for two DHCP/BOOTPservers to be specified. In this case, the G350 duplicates each request, and sends it to bothservers. This duplication provides redundancy and prevents the failure of a single server fromblocking hosts from loading. You can enable or disable DHCP/BOOTP Relay in G350.DHCP/BOOTP relay commandsUse the following commands to configure DHCP relay and BOOTP relay:●●●Use the ip bootp-dhcp network command to select the network from which theBOOTP/DHCP server should allocate an address. This command is required only whenthere are multiple IP interfaces over the VLAN. Use the no form of this command torestore the default value. You must be in interface context to use this command.Use the ip bootp-dhcp relay command to enable relaying of BOOTP and DHCPrequests to the BOOTP/DHCP server. Use the no form of this command to disablerelaying of BOOTP and DHCP requests. You must be in general context to use thiscommand.Use the ip bootp-dhcp server command to add a BOOTP/DHCP server to handleBOOTP/DHCP requests received by this interface. A maximum of two servers can beadded to a single interface. Use the no form of this command to remove a server. Youmust be in interface context to use this command.178 Administration of the Avaya G350 Media Gateway
Configuring DHCP serverConfiguring DHCP serverThe G350 supports DHCP server. DHCP server is a protocol for automatically assigning IPaddresses and other configuration parameters to clients on a TCP/IP network. DHCP serverminimizes the maintenance of a network of, among other things, IP telephones and PCs, byremoving the need to assign and maintain IP addresses and other parameters for each deviceon the network individually.Since a DHCP server can be configured on the G350, local branch devices are not dependanton receiving configuration parameters over the WAN from a remote DHCP server and thereforecan be assigned IP configuration parameters in case of WAN failure.The G350 supports the following DHCP server features:● Up to 32 DHCP pools● Up to 120 users● Up to 256 IP addresses for all DHCP pools together● Automatic and reservation pools● Standard DHCP options and IP phone and wireless special options● Vendor specific information option● DHCP relay packets● Global statistics● Syslog/traps for special eventsThe G350 Media Gateway can function as a DHCP server or as a DHCP relay or bothsimultaneously, with each interface configured in either DHCP server mode or DHCP relaymode. For example, you can configure the G350 to provide DHCP service to voice deviceswhile DHCP requests by data devices are routed to a central remote DHCP server using DHCPrelay.Issue 3 January 2005 179
- Page 128 and 129: Configuring SNMPConfiguring dynamic
- Page 130 and 131: Configuring SNMPThe following examp
- Page 132 and 133: Configuring advanced switchingVLAN
- Page 134 and 135: Configuring advanced switchingMulti
- Page 136 and 137: Configuring advanced switching●
- Page 138 and 139: Configuring advanced switchingRelia
- Page 140 and 141: Configuring advanced switchingSwitc
- Page 142 and 143: Configuring advanced switchingPort
- Page 144 and 145: Configuring advanced switchingThe S
- Page 146 and 147: Configuring advanced switching●Po
- Page 148 and 149: Configuring advanced switchingThe f
- Page 150 and 151: Configuring advanced switchingPort
- Page 152 and 153: Configuring contact closureContact
- Page 154 and 155: Configuring contact closure154 Admi
- Page 156 and 157: Configuring RMON monitoringRMON CLI
- Page 158 and 159: Configuring RMON monitoring158 Admi
- Page 160 and 161: Configuring the routerOverview of t
- Page 162 and 163: Configuring the routerLayer 2 logic
- Page 164 and 165: Configuring the routerStatic routes
- Page 166 and 167: Configuring the routerRouting table
- Page 168 and 169: Configuring the routerRouting packe
- Page 170 and 171: Configuring the routerThe following
- Page 172 and 173: Configuring the routerDynamic MTU d
- Page 174 and 175: Configuring the routerAdditional GR
- Page 176 and 177: Configuring the routerYou can use t
- Page 180 and 181: Configuring the routerApplication
- Page 182 and 183: Configuring the routerNote:Note:If
- Page 184 and 185: Configuring the routerG350-001(supe
- Page 186 and 187: Configuring the routerDirected broa
- Page 188 and 189: Configuring the routerDynamic ARP t
- Page 190 and 191: Configuring the routerConfiguring I
- Page 192 and 193: Configuring the routerPoison-revers
- Page 194 and 195: Configuring the router●●●●U
- Page 196 and 197: Configuring the routerOSPF commands
- Page 198 and 199: Configuring the routerand what metr
- Page 200 and 201: Configuring the router●●●●
- Page 202 and 203: Configuring the routerReassembly pa
- Page 204 and 205: Configuring IPSec VPNConfiguring a
- Page 206 and 207: Configuring IPSec VPNConfiguring IP
- Page 208 and 209: Configuring IPSec VPNPrerequisite -
- Page 210 and 211: Configuring IPSec VPN●hash: the h
- Page 212 and 213: Configuring IPSec VPNTo configure p
- Page 214 and 215: Configuring IPSec VPN3. Exit crypto
- Page 216 and 217: Configuring IPSec VPN9. Exit crypto
- Page 218 and 219: Configuring IPSec VPNIPSec VPN main
- Page 220 and 221: Configuring IPSec VPN2. Use the set
- Page 222 and 223: Configuring IPSec VPNConfiguring th
- Page 224 and 225: Configuring IPSec VPNip-rule 30sour
- Page 226 and 227: Configuring IPSec VPNFull or partia
Configuring <strong>the</strong> routerDHCP/BOOTP relayThe <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> supports <strong>the</strong> DHCP/BOOTP relay agent function. This is anapplication that accepts DHCP/BOOTP requests that are broadcast on one VLAN. Theapplication sends <strong>the</strong>m to a DHCP/BOOTP server. That server connects to ano<strong>the</strong>r VLAN or aserver that might be located across one or more routers that might o<strong>the</strong>rwise not get <strong>the</strong>broadcast request. The relay agent handles <strong>the</strong> DHCP/BOOTP replies as well. The relay agenttransmits <strong>the</strong> replies to <strong>the</strong> client directly or as broadcast, according to a flag in <strong>the</strong> replymessage.Note:Note:The same DHCP/BOOTP relay agent serves both <strong>the</strong> BOOTP and DHCPprotocols.When <strong>the</strong>re is more than one IP interface on a VLAN, <strong>the</strong> <strong>G350</strong> chooses <strong>the</strong> lowest IP addresson this VLAN when relaying DHCP/BOOTP requests. The DHCP/BOOTP server <strong>the</strong>n uses thisaddress to decide <strong>the</strong> network from which to allocate <strong>the</strong> address. When <strong>the</strong>re are multiplenetworks configured, <strong>the</strong> <strong>G350</strong> performs a round-robin selection process.When <strong>the</strong> DHCP/BOOTP server is configured to allocate addresses only from a singlesubnetwork among <strong>the</strong> different subnetworks defined on <strong>the</strong> VLAN, you might need to configure<strong>the</strong> <strong>G350</strong> with <strong>the</strong> relay address on that subnet so <strong>the</strong> DHCP/BOOTP server can accept <strong>the</strong>request.DHCP/BOOTP Relay in <strong>G350</strong> is configurable per VLAN and allows for two DHCP/BOOTPservers to be specified. In this case, <strong>the</strong> <strong>G350</strong> duplicates each request, and sends it to bothservers. This duplication provides redundancy and prevents <strong>the</strong> failure <strong>of</strong> a single server fromblocking hosts from loading. You can enable or disable DHCP/BOOTP Relay in <strong>G350</strong>.DHCP/BOOTP relay commandsUse <strong>the</strong> following commands to configure DHCP relay and BOOTP relay:●●●Use <strong>the</strong> ip bootp-dhcp network command to select <strong>the</strong> network from which <strong>the</strong>BOOTP/DHCP server should allocate an address. This command is required only when<strong>the</strong>re are multiple IP interfaces over <strong>the</strong> VLAN. Use <strong>the</strong> no form <strong>of</strong> this command torestore <strong>the</strong> default value. You must be in interface context to use this command.Use <strong>the</strong> ip bootp-dhcp relay command to enable relaying <strong>of</strong> BOOTP and DHCPrequests to <strong>the</strong> BOOTP/DHCP server. Use <strong>the</strong> no form <strong>of</strong> this command to disablerelaying <strong>of</strong> BOOTP and DHCP requests. You must be in general context to use thiscommand.Use <strong>the</strong> ip bootp-dhcp server command to add a BOOTP/DHCP server to handleBOOTP/DHCP requests received by this interface. A maximum <strong>of</strong> two servers can beadded to a single interface. Use <strong>the</strong> no form <strong>of</strong> this command to remove a server. Youmust be in interface context to use this command.178 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>