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 routingThe next set of commands defines a new PBR list (802). This list will be applied to the datainterface (VLAN 5). The purpose of this is to route data traffic through interfaces other than theE1/T1 interface, so that this traffic will not interface with voice traffic.G350-001(super)# ip pbr-list 802G350-001(super-PBR 802)# name "Data_To_HQ"Done!G350-001(super-PBR 802)# ip-rule 1G350-001(super-PBR 802/ip rule 1)# next-hop list 2Done!G350-001(super-PBR 802/ip rule 1)# ip-protocol tcpDone!G350-001(super-PBR 802/ip rule 1)# destination-ip host 149.49.43.189Done!G350-001(super-PBR 802/ip rule 1)# exitG350-001(super-PBR 802)# exitThe next set of commands creates next hop list 2. This next hop list routes traffic to the GREtunnel (Tunnel 1). If the GRE tunnel is not available, the next hop list checks the next entry onthe list and routes the traffic to the E1/T1 interface (Serial 4/1). If neither interface is available,the traffic is dropped. This allows data traffic to use the E1/T1 interface, but only when the GREtunnel is not available. Alternatively, the list can be configured without the E1/T1 interface,preventing data traffic from using the E1/T1 interface at all.G350-001(super)# ip next-hop-list 2G350-001(super-next hop list 2)#name "Data-To_HQ"Done!G350-001(super-next hop list 2)#next-hop-interface 1 Tunnel 1Done!G350-001(super-next hop list 2)#next-hop-interface 2 Serial 4/1Done!G350-001(super-next hop list 2)#next-hop-interface 3 Null0Done!G350-001(super-next hop list 2)#exitG350-001(super)#Finally, the next set of commands applies the PBR list to the data VLAN (5).G350-001(super)# interface Vlan 5G350-001(super-if:Vlan 6)# ip pbr-group 802Done!G350-001(super-if:Vlan 6)# exitG350-001(super)#286 Administration of the Avaya G350 Media Gateway
Chapter 20: Setting synchronizationIf the Avaya G350 Media Gateway contains an MM710 T1/E1 media module, it is advisable todefine the MM710 as the primary synchronization source for the G350. In so doing, clocksynchronization signals from the Central Office (CO) are used by the MM710 to synchronize alloperations of the G350. If no MM710 is present, it is not necessary to set synchronization.Use the set sync interface {primary|secondary} {mmID|[portID]} command todefine a potential stratum clock source (T1/E1 Media Module, ISDN-BRI), where:●●mmID is the Media Module ID of an MM stratum clock source of the form vn, where n is theMM slot number.portID is the port number for an ISDN clock source candidate. The port ID consists of theslot number of the media module and the number of the port. You can set more than oneport. For example: v2 1,3,5-8.Note:Note: The port ID parameter only applies if the source is a BRI module.By setting the clock source to primary, normal failover will occur. The identity of the currentsynchronization source is not stored in persistent storage. Persistent storage is used topreserve the parameters set by this command.Note:Note: Setting the source to secondary overrides normal failover, generates a trap, andasserts a fault. Thus, it is not recommended to set the clock source to secondaryexcept for testing purposes.To determine which reference source is the active source, use the set sync source{primary|secondary} command. If you choose secondary, the secondary source becomesactive, and the primary source goes on standby. In addition, fallback to the primary source doesnot occur even when the primary source becomes available.If neither primary nor secondary sources are identified, the local clock becomes the activesource.The following example sets the MM710 media module located in slot 2 of the G350 chassis asthe primary clock synchronization source for the Avaya G350 Media Gateway.set sync interface primary v2set sync source primaryIf the G350 includes a second MM710 media module, enter the following additional command:set sync interface secondary v3set sync source secondaryIssue 3 January 2005 287
- 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 280 and 281: Configuring policy-based routingMod
- Page 282 and 283: Configuring policy-based routingEdi
- Page 284 and 285: Configuring policy-based routingIn
- 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
- Page 330 and 331: Traps and MIBsNameParameters(MIB va
- Page 332 and 333: Traps and MIBsMIB FileIP-FORWARD-MI
- Page 334 and 335: Traps and MIBsObjectOIDgenOpResetSu
Chapter 20: Setting synchronizationIf <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> contains an MM710 T1/E1 media module, it is advisable todefine <strong>the</strong> MM710 as <strong>the</strong> primary synchronization source for <strong>the</strong> <strong>G350</strong>. In so doing, clocksynchronization signals from <strong>the</strong> Central Office (CO) are used by <strong>the</strong> MM710 to synchronize alloperations <strong>of</strong> <strong>the</strong> <strong>G350</strong>. If no MM710 is present, it is not necessary to set synchronization.Use <strong>the</strong> set sync interface {primary|secondary} {mmID|[portID]} command todefine a potential stratum clock source (T1/E1 <strong>Media</strong> Module, ISDN-BRI), where:●●mmID is <strong>the</strong> <strong>Media</strong> Module ID <strong>of</strong> an MM stratum clock source <strong>of</strong> <strong>the</strong> form vn, where n is <strong>the</strong>MM slot number.portID is <strong>the</strong> port number for an ISDN clock source candidate. The port ID consists <strong>of</strong> <strong>the</strong>slot number <strong>of</strong> <strong>the</strong> media module and <strong>the</strong> number <strong>of</strong> <strong>the</strong> port. You can set more than oneport. For example: v2 1,3,5-8.Note:Note: The port ID parameter only applies if <strong>the</strong> source is a BRI module.By setting <strong>the</strong> clock source to primary, normal failover will occur. The identity <strong>of</strong> <strong>the</strong> currentsynchronization source is not stored in persistent storage. Persistent storage is used topreserve <strong>the</strong> parameters set by this command.Note:Note: Setting <strong>the</strong> source to secondary overrides normal failover, generates a trap, andasserts a fault. Thus, it is not recommended to set <strong>the</strong> clock source to secondaryexcept for testing purposes.To determine which reference source is <strong>the</strong> active source, use <strong>the</strong> set sync source{primary|secondary} command. If you choose secondary, <strong>the</strong> secondary source becomesactive, and <strong>the</strong> primary source goes on standby. In addition, fallback to <strong>the</strong> primary source doesnot occur even when <strong>the</strong> primary source becomes available.If nei<strong>the</strong>r primary nor secondary sources are identified, <strong>the</strong> local clock becomes <strong>the</strong> activesource.The following example sets <strong>the</strong> MM710 media module located in slot 2 <strong>of</strong> <strong>the</strong> <strong>G350</strong> chassis as<strong>the</strong> primary clock synchronization source for <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>.set sync interface primary v2set sync source primaryIf <strong>the</strong> <strong>G350</strong> includes a second MM710 media module, enter <strong>the</strong> following additional command:set sync interface secondary v3set sync source secondaryIssue 3 January 2005 287