Help & Support

Find an answer to your question

How to interpret line test results

Diagnose result

The first thing you always see is the general diagnose message, letting know whether the test detected any problem or not, and suggesting to check one or another point.

  <itemKeyValueList type="diagnose result">
    <itemKey></itemKey>
    <itemValue>The measurements indicate no fault. If you decide to create a repair ticket, a field intervention will be created.</itemValue>
  </itemKeyValueList>

This message is usually related to copper analysis—it might detect a fault on the line that is synchronized, and detect no fault on the line that is out of sync. In case there is no synchronization on the line, but the line physical values are correct (it might be the case when the customer's modem is broken or not connected to the line), no fault will be detected. However, there are some diagnose messages that can be interpreted unambiguously. Below you can find some of them.

The copper measurements indicate no fault but the synchronization is not detected (the DSL port is locked). If you decide to create a repair ticket, the DSL port will be automatically unlocked.

This kind of message means that—for one or another reason—DSL port the customer's line is connected to is locked. A trouble ticket needs to be opened so that Proximus repair team can unlock it or investigate further.

The measurements indicate no fault, but one or several cross-connect are locked. If you decide to create a repair ticket, the cross-connect will be automatically unlocked.

When you get this type of message, you can be sure the customer has no binding due to a DSL-port that is cross-connected. In order to unlock it, a Proximus trouble ticket should be created.

The measurements indicate a fault. If you decide to create a repair ticket, a field intervention will be created./ Profile is set on fall-back mode because the modem of your customer is non-Vector Friendly or not detectable. Please take all appropriate action before ticket creation to avoid wrongful.

If you receive the message above, you need to update the firmware version of the modem that the customer is using or replace it by a vectoring-friendly (SAGEM F@st 3464, provided that it's equipped with the appropriate version of the modem firmware) or vectoring-compliant (BBox3 and AVM Fritz!box of 7360 or 7490 series with the appropriate version of the modem firmware installed).

Copper analysis

Copper analysis refers to the measurements of the copper pair itself. It is a suite of tests that characterize the line from the exchange to the premises terminations, so they don't depend in any way on the line sync analysis. Depending on the type of the system the customer's LEX/ROP is equipped, there are two different types of copper measurements: 4TEL (4TEL Demand Test) and AGW (Access Gateway). Below are the examples of the copper loop testing and analysis performed by both measurement platforms.

4TEL

Here is how the usual 4TEL copper analysis looks like. Measurements are made between each leg of the pair, from each leg to ground and from each leg to office battery:

  <itemKeyValueList type="copper analysis">
    <itemKey>CABLELENGTH</itemKey>
    <itemValue>1180 m</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>AE_Insulation</itemKey>
    <itemValue>10 MOHMS</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>BE_Insulation</itemKey>
    <itemValue>10 MOHMS</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>AB_Insulation</itemKey>
    <itemValue>10 MOHMS/itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>BA_Insulation</itemKey>
    <itemValue>10 MOHMS</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>AC_Insulation</itemKey>
    <itemValue>10 MOHMS</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>BC_Insulation</itemKey>
    <itemValue>10 MOHMS</b></itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>AE_Capacitance</itemKey>
    <itemValue>95 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>BE_Capacitance</itemKey>
    <itemValue>95 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>AB_CAPACITANCE</itemKey>
    <itemValue>382 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>BA_CAPACITANCE</itemKey>
    <itemValue>381 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>CableCapacitance</itemKey>
    <itemValue>53 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>MutualCapacitance</itemKey>
    <itemValue>549 nF</itemValue>
  </itemKeyValueList>
  <itemKeyValueList type="copper analysis">
    <itemKey>Copper test type</itemKey>
    <itemValue>4TEL</itemValue>

CableLength (m) indicates in meters the length of the line as estimated by the 4TEL system, from the exchange to the premises terminations
AE_Insulation (all insulation values are measured in MOHMS) gives the current insulation value between A wire (tip) and earth (ground)
BE_Insulation gives the current insulation value between B wire (tip) and earth (ground)
AB_Insulation gives the current insulation value between A wire (tip) and B wire (ring)
BA_Insulation gives the current insulation value between B wire (ring) and A wire (tip)
AC_Insulation gives the current insulation value between A wire (tip) and B wire (ring) of another pair in the cable
BC_Insulation gives the current insulation value between B wire (ring) and B wire (ring) of another pair in the cable

When the copper pair is perfect, all insulation values are at 10MHOMS. If one or several values get below 750 KOHMS, that should indicate a physical problem related to possible oxidation, bad functioning splitter on the line, short-circuit in the customer's interior installation etc.
Also worth nothing is that the only reliable test revealing whether it's internal or external wiring that is causing the loss in insulation can be done at the introduction with no internal cabling connected to the intropair. If while testing like this, insulation values are still not good, there is a high chance that there is a problem in the Proximus domain.

AE_Capacitance (all capacitance values are measured in nF): gives the current capacitance value between A wire (tip) and earth (ground).
BE_Capacitance gives the current capacitance value between B wire (ring) and earth (ground).
As the capacitance between a wire and earth (ground) is proportional to the length of the wire, values of AE_Capacitance and BE_Capacitance should not differ from more than 10%.

AB_Capacitance gives the current capacitance value between A wire and B wire.
BA_Capacitance gives the current capacitance value between B wire and A wire.
The values AB_Capacitance and BA_Capacitance should not differ from more than 10%.

CableCapacitance indicates the current calculated cable capacitance between wires A and B, without the capacitance of the CPE. Reference value: approximately 45 nF per km.
MutualCapacitance indicates the current calculated capacitance between wires A and B with CPE.

It's very important to keep in mind that, based on the mutual capacitance value, you can conclude if the test is detecting an NTP socket on the line or not. Since the internal capacitance of the NTP is around 470 nF, having a value below will indicate that NTP is not connected (that can be normal for ADSL line), that it is connected the wrong way or that there is a cabling issue between the socket and the introduction point.
By the same logic, one can understand that aside from NTP, there is a splitter connected to the line—the mutual capacitance value should then get above 1000 nF (that can also mean that the customer is using ISDN equipment).

AGW

Here is how the copper measurements look like when tested by AGW platform:

 <itemKeyValueList type="copper analysis">
   <itemKey>CABLELENGTH</itemKey>
   <itemValue>200 m</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>AE_Insulation</itemKey>
   <itemValue>10 MOhm</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>BE_Insulation</itemKey>
   <itemValue>10 MOhm</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>AB_Insulation</itemKey>
   <itemValue>10 MOhm</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>BA_Insulation</itemKey>
   <itemValue>10 MOhm</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>AE_Capacitance</itemKey>
   <itemValue>16 nF</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>BE_Capacitance</itemKey>
   <itemValue>16 nF</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>AB_CAPACITANCE</itemKey>
   <itemValue>553 nF</itemValue>
</itemKeyValueList>
<itemKeyValueList type="copper analysis">
   <itemKey>Copper test type</itemKey>
   <itemValue>AGW</itemValue>
</itemKeyValueList>

CableLength (m) indicates in meters the length of the line as estimated by the AGW system
AE_Insulation (all insulation values are measured in MOHMS) gives the current insulation value between A wire (tip) and earth (ground)
BE_Insulation gives the current insulation value between B wire (tip) and earth (ground)
AB_Insulation gives the current insulation value between A wire (tip) and B wire (ring)
BA_Insulation gives the current insulation value between B wire (ring) and A wire (tip)

Similarly to 4TEL measurements, if the quality of the twisted pair is perfect, all insulation values are equal to 10MHOMS. If one or several values get below 750 KOHMS, that should indicate a physical problem related to possible oxidation, bad functioning splitter on the line, short-circuit in the customer's interior installation etc.

AE_Capacitance (all capacitance values are measured in nF): gives the current capacitance value between A wire (tip) and earth (ground)
BE_Capacitance gives the current capacitance value between B wire (ring) and earth (ground).
As the capacitance between a wire and earth (ground) is proportional to the length of the wire, values of AE_Capacitance and BE_Capacitance should not differ from more than 10%.
AB_Capacitance indicates the current calculated capacitance between wires A and B with CPE.

Like the mutual capacitance in case of measurements performed by 4TEL system, AB Capacitance can help to understand whether the test is detecting an NTP socket on the line or not. Since the internal capacitance of the NTP is around 470 nF, having a value below will indicate that NTP is not connected, that it is connected the wrong way or that there is a cabling issue between the socket and the introduction point.

Synchro analysis

Let's see how the synchro measurements look like for ADSL line:

 <itemKeyValueList type="synchro analysis">
   <itemKey>LineProfile</itemKey>
   <itemValue>adsl2p_10000_740_256_192</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>PortState</itemKey>
   <itemValue>UNLOCK</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>SynchroState</itemKey>
   <itemValue>SYNCH</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DslamName</itemKey>
   <itemValue>G60RAN0000-2</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>AggregatorName</itemKey>
   <itemValue>C60RAN00003</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamAttenuation</itemKey>
   <itemValue>23.1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamAttenuation</itemKey>
   <itemValue>7.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamBitRate</itemKey>
   <itemValue>9996.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamBitRate</itemKey>
   <itemValue>733.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamNoiseMargin</itemKey>
   <itemValue>18.8</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamNoiseMargin</itemKey>
   <itemValue>17.4</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_AGG_VlanID</itemKey>
   <itemValue>2248</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_AgentCircuitID</itemKey>
   <itemValue>C60RAN00003 atm 1/1/03/01 70.241</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_AtmDown</itemKey>
   <itemValue>UBR_9999_0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_AtmUp</itemKey>
   <itemValue>UBR_739_0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_LineVC</itemKey>
   <itemValue>35</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_LineVP</itemKey>
   <itemValue>8</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_NetworkVC</itemKey>
   <itemValue>241</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_NetworkVP</itemKey>
   <itemValue>70</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_Pbit</itemKey>
   <itemValue>p0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_SSID</itemKey>
   <itemValue>000000002102674</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_OALID</itemKey>
   <itemValue>001066286</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_OLO_VLANID</itemKey>
   <itemValue>138</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>XC1_PING</itemKey>
   <itemValue>4171 us</itemValue>
</itemKeyValueList>

...and VDSL one:

 <itemKeyValueList type="synchro analysis">
   <itemKey>LineProfile</itemKey>
   <itemValue>vdsl2_30000_6000_IL8262_v1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>PortState</itemKey>
   <itemValue>UNLOCK</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>SynchroState</itemKey>
   <itemValue>SYNCH</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DslamName</itemKey>
   <itemValue>h87han00002</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamAttenuation</itemKey>
   <itemValue>8.7</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamAttenuation</itemKey>
   <itemValue>14.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamBitRate</itemKey>
   <itemValue>30080.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamBitRate</itemKey>
   <itemValue>6048.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>DownstreamNoiseMargin</itemKey>
   <itemValue>21.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>UpstreamNoiseMargin</itemKey>
   <itemValue>16.0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>VLAN10_AgentCircuitID</itemKey>
   <itemValue>*H87HAN00002 eth 4/2/01/37:10</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>VLAN10_PBIT</itemKey>
   <itemValue>p0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>VLAN10_OALID</itemKey>
   <itemValue>001066285</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>VLAN10_SSID</itemKey>
   <itemValue>000000002076507</itemValue>
</itemKeyValueList>
<itemKeyValueList type="synchro analysis">
   <itemKey>VLAN10_VLAN_OLO_S-tag</itemKey>
   <itemValue>129</itemValue>
</itemKeyValueList>

LineProfile refers to the profile that is configured on the line. We can check if the current profile corresponds to the one assigned upon provisioning of the line (important for VDSL2 lines), and also make sure it is one of edpnet line profiles the line is put to. If we see a profile with 4640 Kb/s in downstream or 384 Kb/s in upstream, we know that the DSLAM port is wrongly configured.
PortState shows whether DSLAM port is locked or not. In case it's locked (you should also see a confirming message in diagnose result section), a Proximus trouble ticket should be opened.
SynchroState shows whether the line is in sync or not.
DslamName, AggregatorName shows information about the exchange the line is connected to, not relevant for troubleshooting.
DownstreamAttenuation indicates the current downstream attenuation (in dB) of the line. A good and correct line must have an attenuation of approximately 10 dB for each kilometer of its length.
UpstreamAttenuation indicates the current upstream attenuation (in dB) of the line. A good and correct line must have an attenuation of approximately 7 dB (PSTN) or 8,5 dB (ISDN) for each kilometer of its length.
DownstreanBitRate indicates the current downstream bitrate defined on the DSLAM.
UpstreamBitRate indicates the current upstream bitrate defined on the DSLAM. In case of no synchronization, both values are shown as detected at the moment of the last sync.

Both bitrate values have to be as close as possible to the line profile rates (displayed in LineProfile)—the higher the signal loss is, the more the chance that the line is unstable and suffers from the packet losses.

DownstreanNoiseMargin indicates the current downstream noise margin (in dB) of the line. The minimal value must be 6 dB. The noise margin is the difference between the data signal and the noise on the line meaning that a bigger value of noise margin is better than a small one. A noise margin equal to 0 means that there is the same level of noise than the signal (resulting in saturated line).
UpstreamNoiseMargin indicates the current upstream noise margin (in dB) of the line. The minimal value must be 6 dB. The noise margin is the difference between the data signal and the noise on the line meaning that a bigger value of noise margin is better than a small one. A noise margin equal to 0 means that there is the same level of noise than the signal.

It needs to be kept in mind that if basing only on sync analysis, we cannot be sure of the problem location. Besides the fact that sync measurements should always be reviewed in common with the copper analysis, there is no direct link between the value and the possible problem cause. For instance, a low downstream noise margin can mean both bad internal installation and issue in the Proximus infrastructure (distribution pair, DSLAM port etc).
In case of ADSL line, downgrading it to the guaranteed profile (the highest one the line should always be able to support, based on the distance/attenuation of the copper pair) can help to reduce the level of noise and eliminate the loss in bitrate and noise margin values.
The loss in upstream bitrate and noise margin values often indicate a faulty equipment or wiring on the customer's side, but can also be due to the external cabling issue.
In all the cases, modem reboot is always the first thing to do.

XC1_PING (for ADSL lines) refers to the ping from the DSLAM to the end-user's equipment. If this value is equal to -1 ms or to ERROR, there is no response to ping, which means possible issue with the modem or its configuration.
VLAN10 info (for VDSL2 lines) corresponds to the VLAN configuration done by Proximus. If the test returns no such information, that can point to the wrongly configured line.

Additional analysis for VDSL2 lines

LED indicator

For some types of modems (Sagem or BBox series), the test shows the status of LEDs, mostly based on device physical ports.
Here you can see whether the modem is powered on, synchronized and connected to the server (see Binding, helping to understand if the modem is doing PPP or only acting as a bridge). It is also shown if there is any local device connected to one or another LAN or FON port of the modem and turned on.

 </itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>Modem type</itemKey>
   <itemValue>Sagem Black</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>Power</itemKey>
   <itemValue>On</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>Synchro</itemKey>
   <itemValue>On</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>LANPort 1</itemKey>
   <itemValue>On</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>LANPort 2</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>LANPort 3</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>LANPort 4</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>VOIPPort 1</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>VOIPPort 2</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>VOIPCommon port</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>WiFi</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>
<itemKeyValueList type="LED indicator">
   <itemKey>Binding</itemKey>
   <itemValue>Off</itemValue>
</itemKeyValueList>

Vectoring information

It may happen that the vectoring (a new technology that has been rolled-out in order to deliver high bandwidth over existing copper infrastructure, you can find more information on it here) is already activated on the ROP the customer's line is connected to (i.e. it is already equipped by the new VDSL2 cards), it can be seen directly in the test results, in ROP vectoring level:

 <itemKeyValueList type="Vectoring information">
   <itemKey>Firmware version</itemKey>
   <itemValue>1.100.131.30 A6</itemValue>
</itemKeyValueList>
<itemKeyValueList type="Vectoring information">
   <itemKey>ROP vectoring level</itemKey>
   <itemValue>Active</itemValue>
</itemKeyValueList>
<itemKeyValueList type="Vectoring information">
   <itemKey>Maintenance mode</itemKey>
   <itemValue>N</itemValue>
</itemKeyValueList>
<itemKeyValueList type="Vectoring information">
   <itemKey>Fallback mode</itemKey>
   <itemValue>NORMAL</itemValue>
</itemKeyValueList>

Important thing to check here is Fallback mode. If the customer is in correct sync on one of the vectoring profiles, you should see a NORMAL profile here (Line Profile in synchro analysis section should also be changed to the vectoring one). Otherwise, the line has been put on the fallback profile of 7500/512 Kb/s, in order to not disturb the continuous vectoring process.

Modem information

Here you can see some software-related information about the customer's modem read in real time, such as modem type, its current firmware version, and the last time has established synchronization at:

 <itemKeyValueList type="modem information">
   <itemKey>Modem Type</itemKey>
   <itemValue>b-box 2</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Firmware</itemKey>
   <itemValue>6LR10J-6LA07C</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>New firmware available</itemKey>
   <itemValue>false</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Last connection</itemKey>
   <itemValue>2014-11-28T16:11:44.000+01:00</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Last ZTC status</itemKey>
   <itemValue>PARTIALLY CONFIGURED</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Has pending request</itemKey>
   <itemValue>false</itemValue>
</itemKeyValueList>

If it's a Sagem that is connected on the line, you might also see some additional info as shown below. Based on this, you can conclude whether one or another option is enabled in the modem (1 stands for enabled option while 0 means that it's disabled), retrieve its LAN IP address and check the time that has passed since its last reboot.
In the context of troubleshooting, the most interesting line here is Internet in Service. If in front of it, the test returns 'false', the modem is only working in the bridge mode. If this value is 'true', we know that the modem is doing PPP, and can also see the username it's connected with:

 <itemKeyValueList type="modem information">
   <itemKey>Modem Type</itemKey>
   <itemValue>Sagem Black</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Firmware</itemKey>
   <itemValue>6LR10J-6LA07C</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>New firmware available</itemKey>
   <itemValue>false</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Last connection</itemKey>
   <itemValue>2014-11-28T12:01:38.000+01:00</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Last ZTC status</itemKey>
   <itemValue>FULLY CONFIGURED</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Has pending request</itemKey>
   <itemValue>false</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>LAN Mac Address</itemKey>
   <itemValue>00:00:00:00:00:00</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>LAN IP Address</itemKey>
   <itemValue>192.168.1.1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>DHCP server</itemKey>
   <itemValue>1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Has NAT enabled</itemKey>
   <itemValue>1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN Mac Address</itemKey>
   <itemValue>00:00:00:00:00:00</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN Enabled</itemKey>
   <itemValue>0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN SSID</itemKey>
   <itemValue>sagem-79f6</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN broadcast SSID</itemKey>
   <itemValue>1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN Channel</itemKey>
   <itemValue>1</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN Encryption Mode</itemKey>
   <itemValue>NoEncryption</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>WLAN Mac Filtering Enabled</itemKey>
   <itemValue>0</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Status of Wireless LAN</itemKey>
   <itemValue>Disabled</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Time since last modem boot (seconds)</itemKey>
   <itemValue>969520</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey></itemKey>
   <itemValue>None</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Internet in Service</itemKey>
   <itemValue>false</itemValue>
</itemKeyValueList>
<itemKeyValueList type="modem information">
   <itemKey>Login</itemKey>
   <itemValue>usename@EDPNETFIX</itemValue>
</itemKeyValueList>

DLM information

In the last section it can be checked whether Dynamic Line Management (DLM) is active on the customer's line.
Y as Eligibility flag means that DLM is running, N means that it's not yet turned on.
Current overrule DS speed incidates the line's actual downstream synchronization value (it should be the same as defined in LineProfile).

 <itemKeyValueList type="DLM information">
   <itemKey>Eligibility flag</itemKey>
   <itemValue>Y</itemValue>
</itemKeyValueList>
<itemKeyValueList type="DLM information">
   <itemKey>Zone</itemKey>
   <itemValue>DLMzone02</itemValue>
</itemKeyValueList>
<itemKeyValueList type="DLM information">
   <itemKey>Current overrule DS speed</itemKey>
   <itemValue>30200</itemValue>
</itemKeyValueList>
<itemKeyValueList type="DLM information">
   <itemKey>Current overrule INP</itemKey>
   <itemValue>3.2</itemValue>
</itemKeyValueList>
<itemKeyValueList type="DLM information">
   <itemKey>Current overrule VN model</itemKey>
   <itemValue>NO_DN_VN_MODEL</itemValue>
</itemKeyValueList>

Please always keep in mind that active DLM profile can be the reason of the line stability issues—if you suspect that (especially in case the downstream noise margin doesn't look good enough), do not hesitate to ask us to disable it.

Posted on Dec 23, 2014 | Tags:

I didn't find my answer

Contact details

  • Edpnet NV
    Van Landeghemstraat 20
    9100 Sint-Niklaas
  • Opening hours: Mon-Fri, 9AM till 5PM
  •  
  • 03 265 67 00
  •  
  • Mediation service