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 policy-based routingModifying rulesTo modify a policy-based routing rule, you must enter the context of the rule and redefine therule criteria.To enter a rule context:1. Enter the context of the PBR list to which the rule belongs.2. Type the command ip-rule, followed by the number of the rule you want to modify. Forexample, to create rule 1, type ip-rule 1.To view the rules that belong to a PBR list, enter the list’s context and type ip show-rule.Rule criteriaThe rule criteria for PBR rules are largely the same as the rule criteria for other policy list rules.Refer to Rule criteria on page 262.In addition, PBR rules can use the packet’s DSCP field as a rule criteria. Use the dscpcommand, followed by a DSCP value (from 0 to 63) to apply the rule to all packets with thespecified DSCP value.Unlike other policy lists, PBR lists do not use composite operations. Thus, there is nooperation command in the context of a PBR rule. Instead, PBR lists use next hop lists. For anexplanation of next hop lists, see Next Hop Lists on page 280.Use the next-hop list command, followed by the list number of a next hop list, to specify anext hop list for the G350 to apply to packets that match the rule. You can specify DestinationBased Routing instead of a next hop list, in which case the G350 applies destination-basedrouting to a packet when the packet matches the rule.If the next hop list specified in the rule does not exist, the G350 applies destination-basedrouting to packets that match the rule.Next Hop ListsPBR rules include a next hop list. When the rule matches a packet, the G350 routes the packetaccording to the specified next hop list.This section describes next hop lists and contains the following topics:● Next hop list overview — an overview of next hop lists● Modifying next hop lists — instructions on how to modify a next hop list280 Administration of the Avaya G350 Media Gateway
Next Hop ListsNext hop list overviewEach next hop list can include up to 20 entries. An entry in a next hop list can be either an IPaddress or an interface. The G350 attempts to route the packet to the first available destinationon the next hop list. If every destination on the list is unavailable, the G350 routes the packetaccording to destination-based routing.Modifying next hop listsTo modify a next hop list, you must enter the context of the next hop list. To enter a next hop listcontext, type the command ip next-hop-list, followed by the number of the list you want toedit. For example, to modify next hop list 1, type ip next-hop-list 1.To show the next hops in an existing list, enter the context of the next hop list and type shownext-hop.To add entries to a next hop list:1. Enter the context of the next hop list.2. Use one of the following commands:- To enter an IP address as a next hop, use the next-hop-ip command, followed by theindex number of the entry and the IP address. For example, the commandnext-hop-ip 2 149.49.200.2 sets the IP address 149.49.200.2 as the secondentry on the next hop list.- To enter an interface as a next hop, use the next-hop-interface command, followedby the index number of the entry and the name of the interface. For example, thecommand next-hop-interface 3 Serial 5/1:1.1 sets VLAN 2 as the third entryon the next hop list.To delete an entry from a next hop list:1. Enter the context of the next hop list.2. Use one of the following commands:- To delete an IP address, use the no next-hop-ip command, followed by the indexnumber of the entry you want to delete. For example, the commandno next-hop-ip 2 deletes the second entry from the next hop list.- To delete an interface, use the no next-hop-interface command, followed by theindex number of the entry you want to delete. For example, the command nonext-hop-interface 3 deletes the third entry from the next hop list.Issue 3 January 2005 281
- Page 230 and 231: Configuring IPSec VPNip-rule 4sourc
- Page 232 and 233: Configuring IPSec VPNip-rule 10sour
- Page 234 and 235: Configuring IPSec VPN2. Configure B
- Page 236 and 237: Configuring IPSec VPNip-rule 20sour
- Page 238 and 239: Configuring IPSec VPNInterface vlan
- Page 240 and 241: Configuring IPSec VPN3. Allowed ICM
- Page 242 and 243: Configuring IPSec VPNip access-cont
- Page 244 and 245: Configuring IPSec VPNip-rule 70sour
- Page 246 and 247: Configuring IPSec VPNFigure 21: Ful
- Page 248 and 249: Configuring IPSec VPNConfiguration
- Page 250 and 251: Configuring IPSec VPNip-rule 30sour
- Page 252 and 253: Configuring IPSec VPN252 Administra
- Page 254 and 255: Configuring policyAccess control li
- Page 256 and 257: Configuring policyDefining policy l
- Page 258 and 259: Configuring policyAttaching policy
- Page 260 and 261: Configuring policyDevice-wide polic
- Page 262 and 263: Configuring policyEditing and creat
- Page 264 and 265: Configuring policySource and destin
- Page 266 and 267: Configuring policyComposite operati
- Page 268 and 269: Configuring policy●●●CoS —
- Page 270 and 271: Configuring policyThe following com
- Page 272 and 273: Configuring policySimulating packet
- Page 274 and 275: Configuring policy-based routingPol
- Page 276 and 277: Configuring policy-based routingCon
- Page 278 and 279: Configuring policy-based routing●
- Page 282 and 283: Configuring policy-based routingEdi
- Page 284 and 285: Configuring policy-based routingIn
- Page 286 and 287: Configuring policy-based routingThe
- Page 288 and 289: Setting synchronizationIf, for any
- Page 290 and 291: FIPSFigure 26: Image of the cryptog
- Page 292 and 293: FIPSSupported algorithmsThe cryptog
- Page 294 and 295: FIPSSecurity levelThe cryptographic
- Page 296 and 297: FIPSTable 14: Roles and required id
- Page 298 and 299: FIPSTable 15: Critical security par
- Page 300 and 301: FIPSCSP access rights within roles
- Page 302 and 303: FIPSTable 18 shows Role and Service
- Page 304 and 305: FIPSTable 18: Role and service acce
- Page 306 and 307: FIPSPassword guidelinesBelow are ge
- Page 308 and 309: FIPS2. Define the PMI (Primary Mana
- Page 310 and 311: FIPS10. Physically disconnect all n
- Page 312 and 313: FIPS18. To configure all interfaces
- Page 314 and 315: FIPS●Use the snmp-server user use
- Page 316 and 317: FIPS●●TFTPSNMPExample:G350-001(
- Page 318 and 319: FIPSG350-N(super)# ip crypto-list 9
- Page 320 and 321: FIPSError statesTable 19 describes
- Page 322 and 323: FIPSConsiderationsThe following rul
- Page 324 and 325: Traps and MIBsNameParameters(MIB va
- Page 326 and 327: Traps and MIBsNameParameters(MIB va
- Page 328 and 329: Traps and MIBsNameParameters(MIB va
Next Hop ListsNext hop list overviewEach next hop list can include up to 20 entries. An entry in a next hop list can be ei<strong>the</strong>r an IPaddress or an interface. The <strong>G350</strong> attempts to route <strong>the</strong> packet to <strong>the</strong> first available destinationon <strong>the</strong> next hop list. If every destination on <strong>the</strong> list is unavailable, <strong>the</strong> <strong>G350</strong> routes <strong>the</strong> packetaccording to destination-based routing.Modifying next hop listsTo modify a next hop list, you must enter <strong>the</strong> context <strong>of</strong> <strong>the</strong> next hop list. To enter a next hop listcontext, type <strong>the</strong> command ip next-hop-list, followed by <strong>the</strong> number <strong>of</strong> <strong>the</strong> list you want toedit. For example, to modify next hop list 1, type ip next-hop-list 1.To show <strong>the</strong> next hops in an existing list, enter <strong>the</strong> context <strong>of</strong> <strong>the</strong> next hop list and type shownext-hop.To add entries to a next hop list:1. Enter <strong>the</strong> context <strong>of</strong> <strong>the</strong> next hop list.2. Use one <strong>of</strong> <strong>the</strong> following commands:- To enter an IP address as a next hop, use <strong>the</strong> next-hop-ip command, followed by <strong>the</strong>index number <strong>of</strong> <strong>the</strong> entry and <strong>the</strong> IP address. For example, <strong>the</strong> commandnext-hop-ip 2 149.49.200.2 sets <strong>the</strong> IP address 149.49.200.2 as <strong>the</strong> secondentry on <strong>the</strong> next hop list.- To enter an interface as a next hop, use <strong>the</strong> next-hop-interface command, followedby <strong>the</strong> index number <strong>of</strong> <strong>the</strong> entry and <strong>the</strong> name <strong>of</strong> <strong>the</strong> interface. For example, <strong>the</strong>command next-hop-interface 3 Serial 5/1:1.1 sets VLAN 2 as <strong>the</strong> third entryon <strong>the</strong> next hop list.To delete an entry from a next hop list:1. Enter <strong>the</strong> context <strong>of</strong> <strong>the</strong> next hop list.2. Use one <strong>of</strong> <strong>the</strong> following commands:- To delete an IP address, use <strong>the</strong> no next-hop-ip command, followed by <strong>the</strong> indexnumber <strong>of</strong> <strong>the</strong> entry you want to delete. For example, <strong>the</strong> commandno next-hop-ip 2 deletes <strong>the</strong> second entry from <strong>the</strong> next hop list.- To delete an interface, use <strong>the</strong> no next-hop-interface command, followed by <strong>the</strong>index number <strong>of</strong> <strong>the</strong> entry you want to delete. For example, <strong>the</strong> command nonext-hop-interface 3 deletes <strong>the</strong> third entry from <strong>the</strong> next hop list.Issue 3 January 2005 281