Avaya G250 Administration page 142

Configuring WAN interfaces
- Use the mtu command to set the interface's MTU to 1492. Since the header size of
PPPoE packets is 8 bytes, setting the MTU to 1492 ensures that the overall packet size
for 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 (in
seconds) between establishment of the PPPoE tunnel and establishment of the IPCP
tunnel. If this time is exceeded, the PPPoE client terminates the PPPoE tunnel.
- Use the pppoe-client persistent delay command to set the interval between
pppoe-client dial attempts.
- Use the pppoe-client persistent max-attempts command to limit the number
of consecutive connection establishment retries. When this number is reached, the
PPPoE client stops trying to establish connections. To have the PPPoE client resume
trying to establish connections, use the shutdown command to shut down the interface,
followed by the no shutdown command to reopen the interface.
G350-001(super)# interface FastEthernet 10/2
G350-001(super-if:FastEthernet 10/2)#
G350-001(super-if:FastEthernet 10/2)# shutdown
Interface FastEthernet 10/2, changed state to administratively down
Line protocol on FastEthernet 10/2, changed state to down
Done!
- In PPP, the remote peer requests the device to authenticate using a specific
authentication method (CHAP or PAP). Use the ppp chap refuse command to not
agree to authenticate with CHAP. Use the ppp pap refuse command to not agree to
authenticate with PAP. These commands prevent the device from authenticating with a
specific method.
- Use the show ppp authentication command to display the interface's PPP
authentication status. This command displays the following:
[PAP refuse]
PAP sent-username: [not] configured
[CHAP refuse]
CHAP hostname: <used CHAP hostname>
For example:
G350-001(super-if:FastEthernet 10/2)# show ppp authentication
PAP sent-username: configured
CHAP refuse
CHAP hostname: G350
- Use the keepalive-track command to bind interface status to an object tracker (see
Object tracking
packets at defined intervals to the other side of the interface. If the configured number of
consecutive keepalive requests are not answered, the interface track state changes to
down. The object tracker continues monitoring the interface, and when its track state
changes to up, the interface state changes to up.
142 Administration for the Avaya G250 and Avaya G350 Media Gateways
on page 171). When activated, the object tracker sends health checks