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 InterfaceFigure 5: Typical PPPoE Network TopologyISP APPPG350L2TPETH-WANPPPoEISP BEthernetDSL ModemATM over DSLDSLAMATMAccess Concentrator/PPPoE RelayAccess ConcentratorPPPoE configurationTo configure PPPoE on the Fast Ethernet port:1. Enter the context of the Fast Ethernet interface, using the command interfaceFastEthernet 10/2.2. Use the encapsulation pppoe command to change the encapsulation to PPPoE. Youmust change the encapsulation to PPPoE before configuring an IP address on the interface.Note:Note:You cannot use PPPoE if:- An IP address is configured on the interface- Dynamic CAC is enabled on the Fast Ethernet interface. See Dynamic CAC onpage 101.- The interface is part of a primary-backup interface pair. See Backup interfaces onpage 97.3. Use the ip address command to configure an IP address and subnet mask for theinterface. In most cases, PPPoE tunnels require a 32-bit subnet mask.92 Administration of the Avaya G350 Media Gateway
Initial WAN configuration4. Configure an authentication method and parameters:- For PAP authenticating, type the ppp pap-sent command, followed by a usernameand password. For example:G350-001(super-if:FastEthernet 10/2)# ppp pap-sent username avaya32 password 123456Done!- For CHAP authentication, use the ppp chap hostname command, followed by ahostname, and the ppp chap password command, followed by a password. Forexample:G350-001(super-if:FastEthernet 10/2)# ppp chap hostname avaya32Done!G350-001(super-if:FastEthernet 10/2)# ppp chap password 123456Done!Note:Note:Authentication parameters do not appear in the startup or running configurationfiles. You can use the show ppp authentication command to viewauthentication status. The copy running-config startup-configcommand stores authentication parameters in NVRAM.5. You can use the following commands to change the interface parameters:- Use the pppoe-client service name {name}command to force the PPPoE clientto connect only to access concentrators that support a specific service name. Use the noform of this command to deactivate connection to a specific service name. Whenconnection to a specific service name is deactivated, the PPPoe client attempts toautomatically discover the service name by initiating PADI frames with a blank servicename.- Use the mtu command to set the interface’s MTU to 1492. Since the header size ofPPPoE packets is 8 bytes, setting the MTU to 1492 ensures that the overall packet sizefor the PPPoE interface will not exceed 1500, which is the MTU for Ethernet.- Use the pppoe-client wait-for-ipcp command to set the amount of time (inseconds) between establishment of the PPPoE tunnel and establishment of the IPCPtunnel. If this time is exceeded, the PPPoE client terminates the PPPoE tunnel.- Use the pppoe-client persistent delay command to set the interval betweenpppoe-client dial attempts.- Use the pppoe-client persistent max-attempts command to limit the numberof consecutive connection establishment retries. When this number is reached, thePPPoE client stops trying to establish connections. To have the PPPoE client resumeIssue 3 January 2005 93
- Page 42 and 43: Accessing the Avaya G350 Media Gate
- Page 44 and 45: Accessing the Avaya G350 Media Gate
- Page 46 and 47: Accessing the Avaya G350 Media Gate
- Page 48 and 49: Accessing the Avaya G350 Media Gate
- Page 50 and 51: Basic device configurationConfiguri
- Page 52 and 53: Basic device configurationThe Media
- 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 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 104 and 105: Configuring a WAN InterfaceIf one o
- 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
Configuring a WAN InterfaceFigure 5: Typical PPPoE Network TopologyISP APPP<strong>G350</strong>L2TPETH-WANPPPoEISP BE<strong>the</strong>rnetDSL ModemATM over DSLDSLAMATMAccess Concentrator/PPPoE RelayAccess ConcentratorPPPoE configurationTo configure PPPoE on <strong>the</strong> Fast E<strong>the</strong>rnet port:1. Enter <strong>the</strong> context <strong>of</strong> <strong>the</strong> Fast E<strong>the</strong>rnet interface, using <strong>the</strong> command interfaceFastE<strong>the</strong>rnet 10/2.2. Use <strong>the</strong> encapsulation pppoe command to change <strong>the</strong> encapsulation to PPPoE. Youmust change <strong>the</strong> encapsulation to PPPoE before configuring an IP address on <strong>the</strong> interface.Note:Note:You cannot use PPPoE if:- An IP address is configured on <strong>the</strong> interface- Dynamic CAC is enabled on <strong>the</strong> Fast E<strong>the</strong>rnet interface. See Dynamic CAC onpage 101.- The interface is part <strong>of</strong> a primary-backup interface pair. See Backup interfaces onpage 97.3. Use <strong>the</strong> ip address command to configure an IP address and subnet mask for <strong>the</strong>interface. In most cases, PPPoE tunnels require a 32-bit subnet mask.92 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>