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 a WAN InterfaceIf one of the Priority DLCIs is down, its traffic is dropped.Map the PVC control protocol on the routers at all ends of a multi-VC point-to-point link. Mapthis VC to the highest priority DLCI.Traffic Shaping and MarkingTraffic shaping monitors outgoing traffic and takes appropriate action if traffic exceeds agreedparameters. The action could be to drop the packets or mark them as being high-drop priority.The Avaya G350 Media Gateway supports the following traffic shaping parameters per PVC:●●●Committed Information Rate (CIR) — the amount of committed bandwidth to which thecustomer is entitledDiscard Eligible (DE) pre-mark — sets the threshold for pre-marking DE of non-highpriority traffic, in percentage of CIR.Link Fragmentation and Interleaving (LFI) — enables fragmentation of large frame relayframes per PVCYou can configure the traffic shaping parameters within map classes. A map class is comprisedof the following parameters:●●●●●CIR — Default 56,000 bpsCommitted Burst (BC) size — default 7,000 bpsExcess Burst (BE) size — default 0 bpsDE pre-mark — Specifies the amount of non-high priority (0 to 5) packets over the BCand under the BE to label as DE. This amount is measured in percentage of CIR. Thedefault is 100%, unconditionally dropping all packets above the BE.Fragmentation — Fragment size, in bytes. The default is No Fragmentation.You can configure up to 128 different map classes using different combinations of traffic shapingparameters. You then apply these map classes to either the Primary VC or to the Priority DLCIgroup VCs.Note:Note:You must configure the Primary VC before associating a DLCI map class to thePriority DLCI group VCs. Removing the Primary VC after associating a DLCI mapclass to the Priority LCI group VCs, removes their map class configuration.You can enable traffic shaping on a frame relay interface using the frame-relaytraffic-shaping command. After you enable traffic shaping, a default map class is appliedto all currently configured PVCs. In this default map class, the BE is zero. All traffic above theBC is dropped.104 Administration of the Avaya G350 Media Gateway
WAN configuration examplePriority queuingPriority queuing is designed to give all mission-critical programs higher priority than less criticaltraffic. Traffic is queued as high, normal, medium, or low. Using priority queuing, all high-prioritytraffic is serviced first, then normal, etc.The frame relay ingress queuing mechanism functions the same as on PPP interfaces. Theframe relay egress queuing mechanism also functions the same as on PPP interfaces, servingall PVCs configured on the interface, with an additional user-configurable DE buffer. The DEbuffer contains all traffic marked as Discard Eligible, and has the lowest priority.When using VoIP, the G350 enables a distinction within the high-priority queue betweenpriorities 6 and 7. The G350 uses priority 6 for the voice-bearer traffic, and priority 7 for thevoice-controller traffic. These two priorities are served on a round-robin basis. Within thehigh-priority queue, the priority 6 capacity is a maximum of 25% the size of the priority 7capacity to reduce the delay of voice flow. The priority 6-7 distinction exists in data mode aswell, where the queue is divided equally between both capacities.WAN configuration exampleThis section contains an example that illustrates a common PPP VoIP configuration betweentwo sites connected over a WAN.Issue 3 January 2005 105
- Page 54 and 55: Basic device configurationSetting r
- Page 56 and 57: Basic device configuration●●●
- Page 58 and 59: Basic device configurationEach firm
- Page 60 and 61: Basic device configurationThe follo
- Page 62 and 63: Configuring Ethernet portsConfiguri
- Page 64 and 65: Configuring Ethernet portsWAN Ether
- Page 66 and 67: Configuring loggingSyslog serverA S
- Page 68 and 69: Configuring loggingFilters and seve
- Page 70 and 71: Configuring loggingTable 5: Logging
- Page 72 and 73: Configuring VoIP QoSConfiguring RTP
- Page 74 and 75: Configuring VoIP QoSConfiguring QoS
- Page 76 and 77: Configuring VoIP QoSConfiguring Wei
- Page 78 and 79: Configuring the G350 for modem useN
- Page 80 and 81: Configuring the G350 for modem use8
- Page 82 and 83: Configuring a WAN Interface●●
- Page 84 and 85: Configuring a WAN InterfaceFigure 3
- Page 86 and 87: Configuring a WAN Interface3. Use t
- Page 88 and 89: Configuring a WAN InterfaceE1/T1 de
- Page 90 and 91: Configuring a WAN InterfaceUSP defa
- Page 92 and 93: Configuring a WAN InterfaceFigure 5
- Page 94 and 95: Configuring a WAN Interfacetrying t
- Page 96 and 97: Configuring a WAN Interface8. Use t
- Page 98 and 99: Configuring a WAN InterfaceConfigur
- Page 100 and 101: Configuring a WAN InterfaceFigure 6
- Page 102 and 103: Configuring a WAN InterfaceNote:Not
- Page 106 and 107: Configuring a WAN InterfacePPP VoIP
- Page 108 and 109: Configuring a WAN Interface● VLAN
- Page 110 and 111: Configuring a WAN Interface110 Admi
- Page 112 and 113: Configuring PoELoad detectionThe MM
- 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
Configuring a WAN InterfaceIf one <strong>of</strong> <strong>the</strong> Priority DLCIs is down, its traffic is dropped.Map <strong>the</strong> PVC control protocol on <strong>the</strong> routers at all ends <strong>of</strong> a multi-VC point-to-point link. Mapthis VC to <strong>the</strong> highest priority DLCI.Traffic Shaping and MarkingTraffic shaping monitors outgoing traffic and takes appropriate action if traffic exceeds agreedparameters. The action could be to drop <strong>the</strong> packets or mark <strong>the</strong>m as being high-drop priority.The <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> supports <strong>the</strong> following traffic shaping parameters per PVC:●●●Committed Information Rate (CIR) — <strong>the</strong> amount <strong>of</strong> committed bandwidth to which <strong>the</strong>customer is entitledDiscard Eligible (DE) pre-mark — sets <strong>the</strong> threshold for pre-marking DE <strong>of</strong> non-highpriority traffic, in percentage <strong>of</strong> CIR.Link Fragmentation and Interleaving (LFI) — enables fragmentation <strong>of</strong> large frame relayframes per PVCYou can configure <strong>the</strong> traffic shaping parameters within map classes. A map class is comprised<strong>of</strong> <strong>the</strong> following parameters:●●●●●CIR — Default 56,000 bpsCommitted Burst (BC) size — default 7,000 bpsExcess Burst (BE) size — default 0 bpsDE pre-mark — Specifies <strong>the</strong> amount <strong>of</strong> non-high priority (0 to 5) packets over <strong>the</strong> BCand under <strong>the</strong> BE to label as DE. This amount is measured in percentage <strong>of</strong> CIR. Thedefault is 100%, unconditionally dropping all packets above <strong>the</strong> BE.Fragmentation — Fragment size, in bytes. The default is No Fragmentation.You can configure up to 128 different map classes using different combinations <strong>of</strong> traffic shapingparameters. You <strong>the</strong>n apply <strong>the</strong>se map classes to ei<strong>the</strong>r <strong>the</strong> Primary VC or to <strong>the</strong> Priority DLCIgroup VCs.Note:Note:You must configure <strong>the</strong> Primary VC before associating a DLCI map class to <strong>the</strong>Priority DLCI group VCs. Removing <strong>the</strong> Primary VC after associating a DLCI mapclass to <strong>the</strong> Priority LCI group VCs, removes <strong>the</strong>ir map class configuration.You can enable traffic shaping on a frame relay interface using <strong>the</strong> frame-relaytraffic-shaping command. After you enable traffic shaping, a default map class is appliedto all currently configured PVCs. In this default map class, <strong>the</strong> BE is zero. All traffic above <strong>the</strong>BC is dropped.104 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>