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 routerStatic routes can be configured with the following as next-hops:●Via-interface route — specifies a serial interface as the next-hop, without a specificnext-hop IP address. See Via-interface static route on page 165.● Next-hop IP address — specifies the IP address of a router as a next-hop. The next-hoprouter must belong to one of the directly attached networks for which the Avaya G350Media Gateway has an IP interface.Two kinds of static routes can be configured:● High Preference static routes — preferred to routes learned from any routing protocol● Low Preference static routes — used temporarily until the route is learned from a routingprotocol.By default, a static route has low preference.Static routes can be advertised by routing protocols, such as RIP and OSPF. For moreinformation, see Route redistribution on page 197. Static routes also support load-balancingsimilar to OSPF. You can configure up to three next-hops for each static route in one of thefollowing manners:●Enter all of the next-hops using a single ip route command. To add a new next-hop toan existing static route, enter the new next-hop individually, as in the following option.● Enter each next-hop individually with it’s own ip route command.Using the no ip route command deletes the route including all of its next-hops, whetherentered individually or with a single command. For example, to specify next-hops 149.49.54.1and 149.49.75.1 as a static route to the network 10.1.1.0, perform one of the following:Or●Use the single ip route 10.1.1.0 24 149.49.54.1 149.49.75.1 commandspecifying all next-hops together,● Use the individual ip route 10.1.1.0 24 149.49.54.1 and ip route 10.1.1.024 149.49.75.1 commands.Next-hops can only be added to an existing static route if they have the same preference andmetric as the currently defined next-hops.Note:Note: Metrics are used to choose between routes of the same protocol. Preferencesare used to choose between routes of different protocols.The Avaya G350 Media Gateway supports the following Static Route configurations:● Via-interface static route● Permanent static route● Discard route164 Administration of the Avaya G350 Media Gateway
Configuring the routing tableVia-interface static routePPP and frame relay allow for a Layer 3 interface to be established without knowing in advancethe next-hop on the other side of a serial link. In this case you can specify a Serial Layer 2interface or a GRE tunnel as a next-hop instead of providing a specific next-hop IP address.This is equivalent to specifying the node on the other side of the serial link as the next-hop whenits IP address is unknown. The via interface option is configured by specifying the type and thenumber of the serial interface using the ip route command.Note:Note: The interface used in the via route must have an IP address attached to it.For example, the command ip route 193.168.10.0 24 serial 2/1:1 creates a staticroute to the network 193.168.10.0 24 via the Serial 2/1:1 interface.A static route can have both via interface and IP addressed next-hops, with a maximum of threenext-hops. If such a combination is required, separate ip route commands should be usedfor the via interface static route and the IP addressed next-hop routes. Also, if more than one viainterface next-hops are required, each must be configured by separate ip route commands.Permanent static routeThe Avaya G350 Media Gateway enables you to configure a static route as a permanent route.Configuring this option prevents the static route from becoming inactive when the underlyingLayer 2 interface is down. This prevents routing table updates from being sent each time aninterface goes up or down when there is a fluctuating Layer 2 interface on the static route.Configure the permanent option using the ip route command.For example, the command ip route 193.168.10.0 24 serial 2/1:1 permanentcreates a permanent static route to the network 193.168.10.0 24 via the Serial 2/1:1 interface.Permanent static routes should not be configured over Serial Layer 2 interfaces that participatein a Primary-Backup pair. For more information on Backup interfaces, see Backup interfaces onpage 97.Discard routeDiscard route enables you to prevent forwarding traffic to specific networks. You can configure astatic route that drops all packets destined to the route. This is called a discard route, indicatedby the null0 parameter, and is configured using the ip route null0command.For example, the command ip route 134.66.0.0 16 Null0 configures the network134.66.0.0 16 as a discard route.Issue 3 January 2005 165
- Page 114 and 115: Configuring PoEPoE configuration CL
- Page 116 and 117: Configuring PoE116 Administration o
- Page 118 and 119: Configuring Emergency Transfer Rela
- Page 120 and 121: Configuring SNMPThere are several w
- Page 122 and 123: Configuring SNMPUsersSNMPv3 uses th
- Page 124 and 125: Configuring SNMPGroup NameSecurityM
- 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 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 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
Configuring <strong>the</strong> routerStatic routes can be configured with <strong>the</strong> following as next-hops:●Via-interface route — specifies a serial interface as <strong>the</strong> next-hop, without a specificnext-hop IP address. See Via-interface static route on page 165.● Next-hop IP address — specifies <strong>the</strong> IP address <strong>of</strong> a router as a next-hop. The next-hoprouter must belong to one <strong>of</strong> <strong>the</strong> directly attached networks for which <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong><strong>Media</strong> <strong>Gateway</strong> has an IP interface.Two kinds <strong>of</strong> static routes can be configured:● High Preference static routes — preferred to routes learned from any routing protocol● Low Preference static routes — used temporarily until <strong>the</strong> route is learned from a routingprotocol.By default, a static route has low preference.Static routes can be advertised by routing protocols, such as RIP and OSPF. For moreinformation, see Route redistribution on page 197. Static routes also support load-balancingsimilar to OSPF. You can configure up to three next-hops for each static route in one <strong>of</strong> <strong>the</strong>following manners:●Enter all <strong>of</strong> <strong>the</strong> next-hops using a single ip route command. To add a new next-hop toan existing static route, enter <strong>the</strong> new next-hop individually, as in <strong>the</strong> following option.● Enter each next-hop individually with it’s own ip route command.Using <strong>the</strong> no ip route command deletes <strong>the</strong> route including all <strong>of</strong> its next-hops, whe<strong>the</strong>rentered individually or with a single command. For example, to specify next-hops 149.49.54.1and 149.49.75.1 as a static route to <strong>the</strong> network 10.1.1.0, perform one <strong>of</strong> <strong>the</strong> following:Or●Use <strong>the</strong> single ip route 10.1.1.0 24 149.49.54.1 149.49.75.1 commandspecifying all next-hops toge<strong>the</strong>r,● Use <strong>the</strong> individual ip route 10.1.1.0 24 149.49.54.1 and ip route 10.1.1.024 149.49.75.1 commands.Next-hops can only be added to an existing static route if <strong>the</strong>y have <strong>the</strong> same preference andmetric as <strong>the</strong> currently defined next-hops.Note:Note: Metrics are used to choose between routes <strong>of</strong> <strong>the</strong> same protocol. Preferencesare used to choose between routes <strong>of</strong> different protocols.The <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> supports <strong>the</strong> following Static Route configurations:● Via-interface static route● Permanent static route● Discard route164 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>
Change language