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 routerYou can use the following commands to configure GRE tunneling (with OSPF) in this example:Router 1 ConfigurationG350-001(super)# interface FastEthernet 10/2G350-001(super-if:FastEthernet 10/2)# ip address 11.0.0.10 255.255.255.0G350-001(super-if:FastEthernet 10/2)# exitG350-001(super)# interface tunnel 1G350-001(super-if:Tunnel 1)# keepalive 10 3Done!G350-001(super-if:Tunnel 1)# tunnel source 11.0.0.10Done!G350-001(super-if:Tunnel 1)# tunnel destination 12.0.0.20Done!G350-001(super-if:Tunnel 1)# ip address 1.1.1.1 255.255.255.0Done!G350-001(super-if:Tunnel 1)# exitG350-001(super)# ip route 12.0.0.0 255.255.255.0 11.0.0.1 1 highG350-001(super)# router ospfG350-001(super router:ospf)# network 1.1.1.0 0.0.0.255 area 0.0.0.0Done!G350-001(super router:ospf)# exitG350-001(super)#Router 2 ConfigurationG350-001(super)# interface vlan 1G350-001(super-if:Vlan 1)# ip address 12.0.0.10 255.255.255.0G350-001(super-if:Vlan 1)# exitG350-001(super)# interface tunnel 1G350-001(super-if:Tunnel 1)# tunnel source 12.0.0.20Done!G350-001(super-if:Tunnel 1)# tunnel destination 11.0.0.10Done!G350-001(super-if:Tunnel 1)# ip address 1.1.1.2 255.255.255.0G350-001(super-if:Tunnel 1)# exitG350-001(super)# ip route 11.0.0.0 255.255.255.0 12.0.0.1 1 highG350-001(super)# router ospfG350-001(super router:ospf)# network 1.1.1.0 0.0.0.255 area 0.0.0.0Done!G350-001(super router:ospf)# exitG350-001(super)#176 Administration of the Avaya G350 Media Gateway
Configuring DHCP and BOOTP relayConfiguring DHCP and BOOTP relayYou can configure the router to relay Dynamic Host Configuration Protocol (DHCP) andBOOTstrap Protocol (BOOTP) client broadcasts to a server on a different segment of thenetwork. When you configure DHCP and BOOTP relay, you can control how the router relaysDHCP and BOOTP packets. The router also relays replies from the server back to the client.The G350 can alternatively function as a DHCP server, providing DHCP service to localdevices. For information about configuring DHCP server on the G350, see Configuring DHCPserver on page 179.DHCPDHCP assigns dynamic IP addresses to devices on a network. With dynamic addressing, adevice can have a different IP address whenever the device connects to the network. In somesystems, the device’s IP address can even change while it is still connected. DHCP alsosupports a mix of static and dynamic IP addresses.Dynamic addressing simplifies network administration because the software keeps track of IPaddresses rather than requiring an administrator to manage the task. This means you can add anew computer to a network without needing to manually assign a unique IP address. Many ISPsuse dynamic IP addressing for dial-up users. However, dynamic addressing may not bedesirable for a network server.BOOTPBOOTP is an Internet protocol that allows a diskless workstation to discover the following:●●●Its own IP addressThe IP address of a BOOTP server on the networkA file to be loaded into memory to boot the workstationBOOTP allows the workstation to boot without requiring a hard disk or diskette drive. It is usedwhen the user or station location changes frequently. The protocol is defined by RFC 951.Issue 3 January 2005 177
- Page 126 and 127: Configuring SNMP- notification type
- 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 178 and 179: Configuring the routerDHCP/BOOTP re
- 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
Configuring DHCP and BOOTP relayConfiguring DHCP and BOOTP relayYou can configure <strong>the</strong> router to relay Dynamic Host Configuration Protocol (DHCP) andBOOTstrap Protocol (BOOTP) client broadcasts to a server on a different segment <strong>of</strong> <strong>the</strong>network. When you configure DHCP and BOOTP relay, you can control how <strong>the</strong> router relaysDHCP and BOOTP packets. The router also relays replies from <strong>the</strong> server back to <strong>the</strong> client.The <strong>G350</strong> can alternatively function as a DHCP server, providing DHCP service to localdevices. For information about configuring DHCP server on <strong>the</strong> <strong>G350</strong>, see Configuring DHCPserver on page 179.DHCPDHCP assigns dynamic IP addresses to devices on a network. With dynamic addressing, adevice can have a different IP address whenever <strong>the</strong> device connects to <strong>the</strong> network. In somesystems, <strong>the</strong> device’s IP address can even change while it is still connected. DHCP alsosupports a mix <strong>of</strong> static and dynamic IP addresses.Dynamic addressing simplifies network administration because <strong>the</strong> s<strong>of</strong>tware keeps track <strong>of</strong> IPaddresses ra<strong>the</strong>r than requiring an administrator to manage <strong>the</strong> task. This means you can add anew computer to a network without needing to manually assign a unique IP address. Many ISPsuse dynamic IP addressing for dial-up users. However, dynamic addressing may not bedesirable for a network server.BOOTPBOOTP is an Internet protocol that allows a diskless workstation to discover <strong>the</strong> following:●●●Its own IP addressThe IP address <strong>of</strong> a BOOTP server on <strong>the</strong> networkA file to be loaded into memory to boot <strong>the</strong> workstationBOOTP allows <strong>the</strong> workstation to boot without requiring a hard disk or diskette drive. It is usedwhen <strong>the</strong> user or station location changes frequently. The protocol is defined by RFC 951.Issue 3 January 2005 177