Crocus SHDSL G703.pdf - FTP Directory Listing
Crocus SHDSL G703.pdf - FTP Directory Listing Crocus SHDSL G703.pdf - FTP Directory Listing
60 Crocus SHDSL G703 Chapter 5 User manual Step-by-step configuration 5.2.3 Discovering devices on the SHDSL line When you change the eocHandling attribute from none to any other value, the Crocus SHDSL G703 starts "scanning" the SHDSL line in order to determine which devices are present between itself and its remote counterpart. When the scan is finished, some new objects are added to the containment tree on the same level as the line object: • If one or more repeaters are present on the SHDSL line, a repeater[ ] object is added for every repeater. • For the remote counterpart, an end object is added. The new objects are not added instantaneously. It can take up to 5 minutes before these objects appear in the containment tree. For example, suppose you have a link with a Crocus SHDSL G703 as central device, a 1421 SHDSL Router as remote device and one Crocus SHDSL G703 Repeater in between. Suppose you set the eocHandling attribute to discovery. In that case the one repeater[ ] object and an end object is added to the containment tree as can be seen in the screenshot: The first discovered repeater will have id 3, the second one will have id 4, etc. 5.2.4 EOC retrieved information As said before, exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. This section gives an overview in which case which information is retrieved: • EOC status information, refer to EOC status information. • EOC performance information, refer to EOC performance information. • EOC alarm information, refer to EOC alarm information.
Crocus SHDSL G703 Chapter 5 61 User manual Step-by-step configuration EOC status information EOC status information Does the attribute or element display relevant information in case eocHandling is set to … Object crocusShdslTtRpG7 03/… Attribute (Element) none/passive discovery inventory info alarmConfiguration line eocAlarmThresholds (lineAttenuation, signal- Noise) No. The value is always 0.0. • On the central 1 : yes. The values are those as set in the linkAlarmThresholds attribute. • On the remote 2 : no. The value is always 0.0. Yes. The values are those as set in the linkAlarmThresholds attribute on the central device. 3 numDiscoveredRepeaters Yes. repeater[ ] or end vendorId (countryCode, provider- Code, vendorSpecific) No repeater[ ] or end object is created. Yes. vendorModel No. Yes. vendorSerial No. Yes. vendorSoftVersion No. Yes. eocSoftVersion Yes. shdslVersion Yes. eocState Yes. eocAlarmThresholds (lineAttenuation, signal- Noise) No. The value is always 0.0. Yes. The values are those as set in the linkAlarmThresholds attribute on the remote device. Yes. The values are those as set in the linkAlarmThresholds attribute on the central device. repeater[ ]/linePair[ ] or end/linePair[ ] lineAttenuation No repeater[ ] or end object is created. signalNoise No. The value is always 0.0. Yes. The values are the actual line attenuation and signal noise as measured on the remote device. 1. The central device is the device on which the channel attribute is set to central. 2. The remote device is the device on which the channel attribute is set to remote. 3. Refer to 5.2.2 - The EOC handling attribute on page 59 for more information on the alarmConfiguration value.
- Page 21 and 22: Crocus SHDSL G703 Chapter 1 9 User
- Page 23 and 24: Crocus SHDSL G703 Chapter 1 11 User
- Page 25 and 26: Crocus SHDSL G703 Chapter 2 13 User
- Page 27 and 28: Crocus SHDSL G703 Chapter 2 15 User
- Page 29 and 30: Crocus SHDSL G703 Chapter 2 17 User
- Page 31 and 32: Crocus SHDSL G703 Chapter 2 19 User
- Page 33 and 34: Crocus SHDSL G703 Chapter 2 21 User
- Page 35 and 36: Crocus SHDSL G703 Chapter 2 23 User
- Page 37 and 38: Crocus SHDSL G703 Chapter 2 25 User
- Page 39 and 40: Crocus SHDSL G703 Chapter 2 27 User
- Page 41 and 42: Crocus SHDSL G703 Chapter 2 29 User
- Page 43 and 44: Crocus SHDSL G703 Chapter 2 31 User
- Page 45 and 46: Crocus SHDSL G703 Chapter 3 33 User
- Page 47 and 48: Crocus SHDSL G703 Chapter 3 35 User
- Page 49 and 50: Crocus SHDSL G703 Chapter 3 37 User
- Page 51 and 52: Crocus SHDSL G703 Chapter 3 39 User
- Page 53 and 54: Crocus SHDSL G703 Chapter 4 41 User
- Page 55 and 56: Crocus SHDSL G703 Chapter 4 43 User
- Page 57 and 58: Crocus SHDSL G703 Chapter 4 45 User
- Page 59 and 60: Crocus SHDSL G703 Chapter 4 47 User
- Page 61 and 62: Crocus SHDSL G703 Chapter 4 49 User
- Page 63 and 64: Crocus SHDSL G703 Chapter 4 51 User
- Page 65 and 66: Crocus SHDSL G703 Chapter 5 53 User
- Page 67 and 68: Crocus SHDSL G703 Chapter 5 55 User
- Page 69 and 70: Crocus SHDSL G703 Chapter 5 57 User
- Page 71: Crocus SHDSL G703 Chapter 5 59 User
- Page 75 and 76: Crocus SHDSL G703 Chapter 5 63 User
- Page 77 and 78: Crocus SHDSL G703 Chapter 5 65 User
- Page 79 and 80: Crocus SHDSL G703 Chapter 5 67 User
- Page 81 and 82: Crocus SHDSL G703 Chapter 5 69 User
- Page 83 and 84: Crocus SHDSL G703 Chapter 5 71 User
- Page 85 and 86: Crocus SHDSL G703 Chapter 5 73 User
- Page 87 and 88: Crocus SHDSL G703 Chapter 5 75 User
- Page 89 and 90: Crocus SHDSL G703 Chapter 5 77 User
- Page 91 and 92: Crocus SHDSL G703 Chapter 5 79 User
- Page 93 and 94: Crocus SHDSL G703 Chapter 5 81 User
- Page 95 and 96: Crocus SHDSL G703 Chapter 5 83 User
- Page 97 and 98: Crocus SHDSL G703 Chapter 5 85 User
- Page 99 and 100: Crocus SHDSL G703 Chapter 5 87 User
- Page 101 and 102: Crocus SHDSL G703 Chapter 5 89 User
- Page 103 and 104: Crocus SHDSL G703 Chapter 5 91 User
- Page 105 and 106: Crocus SHDSL G703 Chapter 5 93 User
- Page 107 and 108: Crocus SHDSL G703 Chapter 5 95 User
- Page 109 and 110: Crocus SHDSL G703 Chapter 5 97 User
- Page 111 and 112: Crocus SHDSL G703 Chapter 5 99 User
- Page 113 and 114: Crocus SHDSL G703 Chapter 5 101 Use
- Page 115 and 116: Crocus SHDSL G703 Chapter 5 103 Use
- Page 117 and 118: Crocus SHDSL G703 Chapter 5 105 Use
- Page 119 and 120: Crocus SHDSL G703 Chapter 5 107 Use
- Page 121 and 122: Crocus SHDSL G703 Chapter 5 109 Use
60 <strong>Crocus</strong> <strong>SHDSL</strong> G703 Chapter 5<br />
User manual<br />
Step-by-step configuration<br />
5.2.3 Discovering devices on the <strong>SHDSL</strong> line<br />
When you change the eocHandling attribute from none to any other value, the <strong>Crocus</strong> <strong>SHDSL</strong> G703 starts<br />
"scanning" the <strong>SHDSL</strong> line in order to determine which devices are present between itself and its remote<br />
counterpart. When the scan is finished, some new objects are added to the containment tree on the<br />
same level as the line object:<br />
• If one or more repeaters are present on the <strong>SHDSL</strong> line, a repeater[ ] object is added for every repeater.<br />
• For the remote counterpart, an end object is added.<br />
The new objects are not added instantaneously. It can take up to 5 minutes before these objects appear<br />
in the containment tree.<br />
For example, suppose you have a link with a <strong>Crocus</strong> <strong>SHDSL</strong> G703 as central device, a 1421 <strong>SHDSL</strong><br />
Router as remote device and one <strong>Crocus</strong> <strong>SHDSL</strong> G703 Repeater in between. Suppose you set the<br />
eocHandling attribute to discovery. In that case the one repeater[ ] object and an end object is added to the<br />
containment tree as can be seen in the screenshot:<br />
The first discovered repeater will have id 3, the second one will have id 4, etc.<br />
5.2.4 EOC retrieved information<br />
As said before, exactly which information is retrieved from the remote <strong>SHDSL</strong> device(s) through the EOC<br />
channel depends on the setting of the eocHandling attribute.<br />
This section gives an overview in which case which information is retrieved:<br />
• EOC status information, refer to EOC status information.<br />
• EOC performance information, refer to EOC performance information.<br />
• EOC alarm information, refer to EOC alarm information.