Page 101 / 138 Scroll up to view Page 96 - 100
Management and Diagnostic Console
96
Reviewing Bitloading
The Bitloading pane shows the bits loaded per tone for the upstream (tones 6 to 31) and downstream
(tones 32 to 255) spectrum. A single hex-digit for each tone shows the numeric values (0 to F) in addition to
the bar-graph depiction.
Exit Code
Indicates the reason for a lost connection or a terminated training attempt.
Following are examples of the typical values that can be represented:
ERR_LOF_LIMIT - Retrained due to loss of framing.
ERR_LOS_LIMIT - Retrained due to loss of signal.
ERR_HI_BER_LIMIT - Retrained due to excessive CRCs.
RESTART - System deliberately restarted modem (line search, reprovisioning, or 30-
second timeout when waiting for DSL signal.
ERR_STATE_TIMEOUT - Modem timed out during training (for example, the modem
failed to detect pilot signal at the appropriate time).
ERR_ALL_OPTIONS_FAIL - Failed to negotiate a final bitrate with DSLAM.
RETRAIN_HIGHER - Proactive retrain in order to obtain a significantly higher connect
rate.
Echo
A measure of the uncancelled echo
relative
to the background noise on the line.
This is an indication of how much the uncancelled echo is affecting DSL
performance, rather than an absolute measure of the uncancelled echo.
VXCO
Indicates the difference between the gateway’s and the DSLAM port’s crystal
frequency in parts per million (ppm).
Rx Gain
Indicates the current receive gain settings, which will depend on the length of the
DSL line.
INC Tones
Indicates the number of compensation tones on which impulse noise is detected.
Item
Description
Page 102 / 138
Management and Diagnostic Console
97
Troubleshooting - Event Log Page
The Troubleshooting – Event Log page displays all security related events for the broadband and local
network. Log information is stored in an 8 KB buffer. When the buffer is full, the oldest items are purged
from the log. You can also clear the log contents by clicking the
Clear Log
button.
Figure 41. MDC Troubleshooting Event Log Page
You can view specific information by selecting which log to view from the pull-down menu and then clicking
the
Filter
button (the screen capture depicted above has the
system
filter applied). Following are
descriptions of the logs.
Access.
Shows the current access log, which registers all significant Content Screening and Internet
Access Control events.
All.
Shows all logs that register a significant event (access, firewall, fw alert, system, and wra).
Firewall.
Shows all detailed firewall events, including Internet Access Control and Firewall Monitor.
FW Alert.
Shows the current Firewall Monitor log, which registers all significant Firewall Monitor-related
events.
Page 103 / 138
Management and Diagnostic Console
98
HURL.
Shows the Broadband Redirect messages that have been enabled by a service provider.
Modem.
Shows the current modem log, which registers all significant modem-related events.
System.
Shows the current system log, which registers all significant events within the 2Wire gateway
since it was last restarted.
WRA.
Shows the current Web Remote Access log, which registers all significant Web Remote Access-
related events.
Each log entry includes the severity level, a description of the event, and the actual time that it occurred.
The most recent events display at the
bottom
of the list.
Events generate an Informational (INF) or Warning (WRN) severity level. Informational indicates events that
are informational only; Warning indicates an unexpected condition that does not affect the 2Wire gateway’s
ability to operate (for example, a network problem or the 2Wire gateway is not configured properly).
For events that involve the transfer of packets, the following additional information is displayed.
Item
Description
src
Source IP address
dst
Destination IP address
ipprot
Protocol number as indicated in the IP header field
sport
Source port (TCP and UDP)
dport
Destination port (TCP and UDP)
Disposition of the event
The action taken when the event occurs (for example,
“Unknown inbound session stopped”)
Page 104 / 138
Management and Diagnostic Console
99
Troubleshooting - Network Tests Page
The Troubleshooting – Network Tests page provides the Ping, Traceroute, and DNS Query tools, which help
diagnose problems with the 2Wire gateway or 2Wire gateway connections.
Figure 42. MDC Troubleshooting Network Tests Page
The Ping test allows you to ensure that the 2Wire gateway can send data packets to (ping) a remote host.
The Traceroute test traces the number of times a data packet sent from the 2Wire gateway is routed before
it reaches its destination. The DNS Query test finds the IP address of the domain name service.
Page 105 / 138
Management and Diagnostic Console
100
To perform a ping or traceroute test:
1.
From the drop-down menu, select Ping or Traceroute.
2.
In the Host field, enter the URL of the host location to which you wish the 2Wire gateway to send the
ping or traceroute.
3.
In the Test field, enter the number of times you want the ping to occur (the maximum is 25) or the
number of hops you want traceroute to trace.
4.
In the Packet Size field, enter the packet size you wish to send. The maximum packet size is 576.
5.
Check the
Enable network name resolution
checkbox. This will ensure that the name of the host location
is displayed along with the corresponding IP address.
6.
Click the
Start
button.
The results are displayed on the page as they occur, and include round trip latency; the aggregate number of
packets sent, received, and lost; and the minimum, maximum, and average round-trip latency.
To discontinue Ping or Traceroute, click the
Stop
button.
To perform a DNS query:
1.
From the drop-down menu, select DNS Query.
2.
In the Host field, enter the domain name (URL) for which you wish to obtain the IP address.
3.
Click the
Start
button.

Rate

3.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top