telindus1423(fr)

Telindus 1423 SHDSL Router

Reference manual

1

Reference manual

Telindus 1423 SHDSL Router Table of contents

User and reference manual

1

Table of contents

Reference manual .................................................................................. 1

MR-1Configuration attributes ...................................................................................4MR-1.1Configuration attribute overview .............................................................................. 5MR-1.2General configuration attributes............................................................................. 14MR-1.3LAN interface configuration attributes.................................................................... 20MR-1.4WAN interface configuration attributes .................................................................. 35MR-1.5Encapsulation configuration attributes................................................................... 37MR-1.6SHDSL line configuration attributes....................................................................... 66MR-1.7End and repeater configuration attributes.............................................................. 77MR-1.8BRI configuration attributes ................................................................................... 79MR-1.9Profiles configuration attributes ............................................................................. 88MR-1.10Dial maps configuration attributes ..................................................................... 116MR-1.11Bundle configuration attributes .......................................................................... 121MR-1.12Router configuration attributes........................................................................... 126MR-1.13Bridge configuration attributes ........................................................................... 222MR-1.14SNMP configuration attributes ........................................................................... 235MR-1.15Management configuration attributes ................................................................ 237

MR-2Status attributes ............................................................................................248MR-2.1Status attribute overview ..................................................................................... 249MR-2.2General status attributes...................................................................................... 258MR-2.3LAN interface status attributes............................................................................. 262MR-2.4WAN interface status attributes ........................................................................... 271MR-2.5Encapsulation status attributes............................................................................ 274MR-2.6SHDSL line status attributes................................................................................ 297MR-2.7End and repeater status attributes....................................................................... 302MR-2.8BRI status attributes ............................................................................................ 306MR-2.9AUX status attributes ........................................................................................... 318MR-2.10Profile status attributes ...................................................................................... 321MR-2.11Dial maps status attributes ................................................................................ 323MR-2.12Bundle status attributes ..................................................................................... 326MR-2.13Router status attributes...................................................................................... 334MR-2.14Bridge status attributes ...................................................................................... 377MR-2.15Management status attributes ........................................................................... 384MR-2.16File system status attributes .............................................................................. 389MR-2.17Operating system status attributes .................................................................... 399



2

MR-3Performance attributes .................................................................................402MR-3.1Performance attributes overview ......................................................................... 403MR-3.2General performance attributes ........................................................................... 410MR-3.3LAN interface performance attributes .................................................................. 412MR-3.4WAN interface performance attributes................................................................. 417MR-3.5Encapsulation performance attributes ................................................................. 418MR-3.6SHDSL line performance attributes ..................................................................... 431MR-3.7End and repeater performance attributes ............................................................ 435MR-3.8BRI performance attributes.................................................................................. 436MR-3.9AUX performance attributes ................................................................................ 441MR-3.10Dial maps performance attributes...................................................................... 442MR-3.11Bundle performance attributes........................................................................... 444MR-3.12Router performance attributes ........................................................................... 447MR-3.13IP traffic policy performance attributes .............................................................. 469MR-3.14Bridge performance attributes ........................................................................... 471MR-3.15Management performance attributes................................................................. 477MR-3.16Operating system performance attributes.......................................................... 480

MR-4Alarm attributes.............................................................................................484MR-4.1Alarm attributes overview .................................................................................... 485MR-4.2Introducing the alarm attributes ........................................................................... 488MR-4.3General alarms .................................................................................................... 491MR-4.4LAN interface alarms ........................................................................................... 493MR-4.5WAN interface alarms.......................................................................................... 494MR-4.6SHDSL line alarms .............................................................................................. 495MR-4.7SHDSL line pair alarms ....................................................................................... 496MR-4.8End and repeater alarms ..................................................................................... 498MR-4.9BRI alarms ........................................................................................................... 500MR-4.10B-channel alarms............................................................................................... 501MR-4.11AUX alarms........................................................................................................ 502MR-4.12Bundle alarms.................................................................................................... 503MR-4.13Router alarms .................................................................................................... 504

MR-5TMA sub-system picture...............................................................................506

MR-6Auto installing the Telindus 1423 SHDSL Router.......................................508MR-6.1Introducing the auto-install protocols ................................................................... 509MR-6.2Auto-install on the LAN interface ......................................................................... 511MR-6.3Auto-install on the WAN interface........................................................................ 516MR-6.4Creating a configuration file ................................................................................. 523MR-6.5Restoring a configuration file ............................................................................... 530



3

MR-7Downloading software ..................................................................................534MR-7.1What is boot and application software? ............................................................... 535MR-7.2Downloading application software using TMA ..................................................... 536MR-7.3Downloading application software using TFTP.................................................... 537MR-7.4Downloading application software using TML ..................................................... 538MR-7.5Downloading application software using FTP...................................................... 539MR-7.6Downloading application software in boot mode ................................................. 540MR-7.7Downloading files to the file system..................................................................... 541

MR-8Technical specifications...............................................................................542MR-8.1SHDSL line specifications.................................................................................... 543MR-8.2Basic Rate ISDN interface specifications ............................................................ 545MR-8.3LAN interface specifications ................................................................................ 546MR-8.44 port Ethernet switch specifications ................................................................... 546MR-8.5Control connector specifications.......................................................................... 547MR-8.6IP address assignment and auto-provisioning..................................................... 548MR-8.7ATM encapsulation specifications ....................................................................... 549MR-8.8Frame Relay encapsulation specifications .......................................................... 550MR-8.9PPP encapsulation specifications........................................................................ 550MR-8.10Other WAN encapsulation specifications........................................................... 550MR-8.11IP routing specifications..................................................................................... 551MR-8.12Bridging specifications ....................................................................................... 553MR-8.13Network address translation specifications........................................................ 554MR-8.14Tunnelling and VPN specifications .................................................................... 555MR-8.15Priority and traffic policy specifications .............................................................. 556MR-8.16Routing and bridging performance specifications.............................................. 558MR-8.17Firewall specifications........................................................................................ 558MR-8.18Access security specifications ........................................................................... 559MR-8.19Maintenance and management specifications................................................... 559MR-8.20Memory specifications ....................................................................................... 560MR-8.21Power requirements........................................................................................... 560MR-8.22Dimensions ........................................................................................................ 560MR-8.23Safety compliance ............................................................................................. 561MR-8.24Over-voltage and over-current protection compliance....................................... 561MR-8.25EMC compliance................................................................................................ 561MR-8.26Environmental compliance................................................................................. 561

Annex .................................................................................................. 562

Index.................................................................................................... 568

Telindus 1423 SHDSL Router Chapter MR-1

User manual Configuration attributes

4

MR-1 Configuration attributes

This chapter discusses the configuration attributes of the Telindus 1423 SHDSL Router. The following gives an overview of this chapter:

• MR-1.1 - Configuration attribute overview on page 5• MR-1.2 - General configuration attributes on page 14• MR-1.3 - LAN interface configuration attributes on page 20• MR-1.4 - WAN interface configuration attributes on page 35• MR-1.5 - Encapsulation configuration attributes on page 37• MR-1.6 - SHDSL line configuration attributes on page 66• MR-1.7 - End and repeater configuration attributes on page 77• MR-1.8 - BRI configuration attributes on page 79• MR-1.9 - Profiles configuration attributes on page 88• MR-1.10 - Dial maps configuration attributes on page 116• MR-1.11 - Bundle configuration attributes on page 121• MR-1.12 - Router configuration attributes on page 126• MR-1.13 - Bridge configuration attributes on page 222• MR-1.14 - SNMP configuration attributes on page 235• MR-1.15 - Management configuration attributes on page 237



5

MR-1.1 Configuration attribute overview

Refer to MU-4.3 - Les objets dans l'arborescence Routeur Telindus 1423 SHDSL on page 46 to find out which objects are present by default, which ones you can add yourself and which ones are added auto-matically.

> telindus1423RoutersysNamesysContactsysLocationbootFromFlashsecurityalarmMaskalarmLevelAction: Activate ConfigurationAction: Load Default ConfigurationAction: Load PreconfigurationAction: Load Saved ConfigurationAction: Cold Boot

>> lanInterfacenamemodeipbridgingpriorityPolicyarpadapter1

vlanswitchMode2

ports2

bcastStormProtection2

alarmMaskalarmLevel

>> wanInterfacenameencapsulationpriorityPolicymaxFifoQLenalarmMaskalarmLevel

>>> atmpvcTablevpatm

1. Only present on the single port LAN interface.2. Only present on the 4 port LAN interface.



6

>>> frameRelayipdlciTablelmimodeLearnedDlcidelayOptimisationfragmentationmru

>>> pppipmodebridgingdelayOptimisationmrucompressionlinkMonitoringauthenticationauthenPeriodsessionNamesessionSecret

>>> hdlcbridgingmru

>>> errorTesttestTypeblockSizeprogrammablePattern



7

>>> linechannelregiontimingModeretrainstartupMarginminSpeedmaxSpeedminSpeed2P3

maxSpeed2P3

mode3

dualPairModelinkAlarmThresholdsnumExpectedRepeaterseocHandlingmanagementalarmMaskalarmLevel

>>>> linePair[ ]alarmMaskalarmLevel

>>> repeater[ ]

>>>> networkLinePair[ ]alarmMaskalarmLevel

>>>> customerLinePair[ ]alarmMaskalarmLevel

>>> end

>>>> linePair[ ]alarmMaskalarmLevel

>> bri[1]4

teiteiValuetelephoneNrsdialAllowedalarmMaskalarmLevel

3. Only present in case of a 2 pair version.4. Only present on the Telindus 1423 SHDSL Router ISDN version.



8

>>> bChannel[1]alarmMaskalarmLevel

>>> bChannel[2]<Contains the same attributes as the bChannel[1] object.>

>>> leasedLine[ ]encapsulationpriorityPolicymaxFifoQLenchannelAllocationalarmMaskalarmLevel

>>>> frameRelayipmodedlciTablelmimodeLearnedDlcidelayOptimisationfragmentationmru

>>>> pppipmodebridgingdelayOptimisationmrucompressionlinkMonitoringauthenticationauthenPeriodsessionNamesessionSecret

>>>> hdlcbridgingmru

>>>> errorTesttestTypeblockSizeprogrammablePattern

>> bri[2]5

<Contains the same attributes as the bri[1] object.>



9

>> profiles4

>>> dial

>>>> defaultIsdnisdnInterfacesdialPktBufSizeidleTimeOutfastIdleTimeOutcallIntervalcallTimeOut24hMaxCallTimedialTimeTablemaxChannelsUsedminChannelsFree

>>>> isdn[ ]<Contains the same attributes as the dial/defaultIsdn object.>

>>> encapsulation

>>>> defaultPpplinkMonitoringauthenticationauthenPeriodcompressionconnectionmultilink

>>>> ppp[ ]<Contains the same attributes as the encapsulation/ppp object.>

>>> forwardingMode

>>>> defaultRoutingippriorityPolicymaxFifoQLen

>>>> routing[ ]<Contains the same attributes as the forwardingMode/defaultRouting object.>

5. Only present on the Telindus 1423 SHDSL Router 2 port ISDN version.



10

>>> policy

>>>> traffic

>>>>> ipTrafficPolicy[ ]methodtrafficShapingtos2QueueMappingdropLevels

>>>>> bridgingTrafficPolicy[ ]vlanPriorityMapdropLevels

>>>> priority

>>>>> priorityPolicy[ ]algorithmcountingPolicyqueueConfigurationslowdelayQuotumbandwidth

>> dialMaps4

mapping

>> bundle

>>> pppBundle[ ]membersmodeipbridgingfragmentationmulticlassInterfacesalarmMaskalarmLevel



11

>> routerdefaultRouteroutingTableroutingProtocolalternativeRoutesripUpdateIntervalripHoldDownTimeripv2SecretTablesysSecretpppSecretTablehelperProtocolssendTtlExceededsendPortUnreachablesendAdminUnreachabledhcpStaticdhcpDynamicdhcpCheckAddressradiusdnsaddrPools4

alarmMaskalarmLevel

>>> defaultNatpatAddressportTranslationsservicesAvailableaddressesgatewaytcpSocketTimeOutudpSocketTimeOuttcpSocketsudpSocketsdmzHost

>>> nat[ ]<Contains the same objects as the defaultNat object.>

>>> tunnelsl2tpTunnelsipsecL2tpTunnels

>>> manualSA[ ]espEncryptionAlgorithmespEncryptionKeyespAuthenticationAlgorithmespAuthenticationKeyspi



12

>>> ikeSA[ ]phase1phase2

>>> routingFilter[ ]filter

>>> ospfrouterIdrefBandwidthkeyChains

>>>> areaareaIdstubnetworksvirtualLinksranges

>>> firewallinspectionoutboundPoliciesinboundPoliciesoutboundSelfPoliciesinboundSelfPoliciesattackslog

>> bridge

>>> bridgeGroupnameiparpbridgeCachebridgeTimeOutspanningTreelocalAccessmacAddressvlanvlanSwitching



13

>>> vpnBridgeGroup[ ]iparpbridgeCachebridgeTimeOutspanningTreelocalAccessmacAddressvlanvlanSwitching

>>> accessList[ ]macAddress

>> snmptrapDestinationsmib2Traps

>> managementcms2AddressaccessListsnmptelnettftpftpaccessPolicyconsoleNoTrafficTimeOutalarmFilteratwinGraphicstimedStatsAvailabilitytimeServertimeZonesysLogloginControlctrlPortProtocol

>>> loopbackipAddressipNetMask



14

MR-1.2 General configuration attributes

This section describes the following configuration attributes:

• telindus1423Router/sysName on page 15• telindus1423Router/sysContact on page 15• telindus1423Router/sysLocation on page 15• telindus1423Router/bootFromFlash on page 15• telindus1423Router/security on page 16• telindus1423Router/<alarmConfigurationAttributes> on page 17

This section describes the following actions:

• telindus1423Router/Activate Configuration on page 18• telindus1423Router/Load Default Configuration on page 18• telindus1423Router/Load Preconfiguration on page 18• telindus1423Router/Load Saved Configuration on page 19• telindus1423Router/Cold Boot on page 19



15

telindus1423Router/sysName

Use this attribute to assign a name to the Telindus 1423 SHDSL Router. The sysName attribute is an SNMP MIB2 parameter.

This attribute is also used in the PPP authentication process. The PPP authenticator uses the sysName attribute in order to verify the peer its response.

For more information on PPP authentication, refer to …

• MU-7.4.6 - Configuration de PAP on page 171• MU-7.4.8 - Configuration de CHAP on page 175

telindus1423Router/sysContact

Use this attribute to add contact information. You could, for instance, enter the name and telephone number of the person to contact in case problem occur.

The sysContact attribute is an SNMP MIB2 parameter.

telindus1423Router/sysLocation

Use this attribute to specify the physical location of the Telindus 1423 SHDSL Router. The sysLocation attribute is an SNMP MIB2 parameter.

telindus1423Router/bootFromFlash

Part of the flash memory of the Telindus 1423 SHDSL Router is organised as a file system. In this file system, you can store two complete application software versions. You can use the bootFromFlash attribute to switch between these softwares.

When you store two application software versions in the file system, they are automatically renamed as CONTROL1 and CONTROL2, respectively. You can check this with the status attribute telindus1423Router/fileSystem/fileList.

The bootFromFlash attribute has the following values:

Value When the Telindus 1423 SHDSL Router boots …

flash1 the application software CONTROL1 is active.

flash2 the application software CONTROL2 is active.

auto the Telindus 1423 SHDSL Router automatically chooses the most recent applica-tion software. It does this by comparing the application software version numbers.

Default:<empty>Range: 0 … 64 characters



Default:autoRange: enumerated, see below



16

telindus1423Router/security

Use this attribute to create a list of passwords with associated access levels in order to avoid unauthorised access to the Telindus 1423 SHDSL Router and the network.

The security table contains the following elements:

The following table shows, for each access level, what you can or can not do:

Element Description

password Use this element to set the password. You can then associate this password with a certain access level.

Also see Important remarks on page 17.

accessRights Use this element to set the access level associated with the password. It is a bit string of which each bit corresponds to an access level. The different access levels are listed below.

Access level

Read attributes

Change attributes

Read secu-rity attributes1

1. The Telindus 1423 SHDSL Router has the following security attributes:telindus1423Router/sysNametelindus1423Router/securitytelindus1423Router/router/sysSecret, pppSecretTable and ripv2SecretTabletelindus1423Router/router/priorityPolicy and trafficPolicytelindus1423Router/wanInterface/ppp/authentication and authenPeriodtelindus1423Router/management/accessList, snmp, telnet and tftp

Change security attributes

Execute actions2

2. Actions are e.g. Cold Boot, clearArpCache, clearBridgeCache, etc…

Access file system

readAccess yes no no no no no

writeAccess yes yes no no yes no

securityAccess no no yes yes no no

fileSystem-Access

no no no no no yes

Default:<empty>Range: table, see below


Default:1111Range: bit string, see below



17

Important remarks

• If you create no passwords, everybody has complete access.• If you define at least one password, it is impossible to access the Telindus 1423 SHDSL Router with

one of the management systems without entering the correct password.• If you create a list of passwords, create at least one with write and security access. If not, you will be

unable to make configuration and password changes after activation of the new configuration.• If you access the Telindus 1423 SHDSL Router via RADIUS, then this requires that the password is

associated with a user. So in that case, enter the username and password in the password element as follows: "username:password".- Note that if the ‘:’ is omitted, then the string is considered to be a password.- Note that if you do not access the device via RADIUS, but you access it directly with e.g. TMA,

then you have to enter the complete string, i.e. "username:password". Not just the password part of the string.

telindus1423Router/<alarmConfigurationAttributes>

For more information on …

• the alarm configuration attributes alarmMask and alarmLevel and on the alarms in general, refer to MR-4.2 - Introducing the alarm attributes on page 488.

• the alarms of the telindus1423Router object, refer to MR-4.3 - General alarms on page 491.



18

telindus1423Router/Activate Configuration

If you execute this action, then the editable non-active configuration becomes the active configuration. Refer to MU-5.6.1 - Quels sont les différents types de configuration ? on page 89 for more information.

When use this action?

If you configure the Telindus 1423 SHDSL Router using …

• any other maintenance tool than the graphical user interface based TMA (e.g. ATWIN, CLI, Web Interface, EasyConnect terminal, TMA CLI), then execute the Activate Configuration action to activate the configuration after you finished configuring the Telindus 1423 SHDSL Router or after you executed the Load Saved Configuration or Load Default Configuration action.

• TMA, then do not just execute the Activate Configuration action to activate the configuration after you fin-ished configuring the Telindus 1423 SHDSL Router, but use the TMA button Send all attributes to device instead. You must, however, execute the Activate Configuration action after you executed the Load Saved Configuration or Load Default Configuration action. The default or saved configuration will only be activated by the action Activate Configuration.

telindus1423Router/Load Default Configuration

If you execute this action, then the non-active configuration is overwritten by the default configuration. Refer to MU-5.6.1 - Quels sont les différents types de configuration ? on page 89 for more information.


If you install the Telindus 1423 SHDSL Router for the first time, all configuration attributes have their default values. If the Telindus 1423 SHDSL Router has already been configured but you want to start from scratch, then use this action to revert to the default configuration.

telindus1423Router/Load Preconfiguration

If you execute this action, then the non-active configuration is overwritten by the preconfiguration (if present, else this action does nothing). Refer to MU-5.6.1 - Quels sont les différents types de configura-tion ? on page 89 for more information.


If you install the Telindus 1423 SHDSL Router for the first time and if a preconfiguration is present (i.e. a precfg.cms file is present on the file system), then some configuration attributes will be set to a pre-configured value. The rest of the attributes will be set to their default values. If the Telindus 1423 SHDSL Router has already been configured but you want to revert to the preconfiguration, then use this action.



19

telindus1423Router/Load Saved Configuration

If you execute this action, then the non-active configuration is overwritten by the active configuration cur-rently used by the Telindus 1423 SHDSL Router. Refer to MU-5.6.1 - Quels sont les différents types de configuration ? on page 89 for more information.


If you are in the progress of modifying the non-active configuration but made some mistakes, then use this action to revert to the active configuration.

telindus1423Router/Cold Boot

If you execute this action, then the Telindus 1423 SHDSL Router reboots. As a result, the Telindus 1423 SHDSL Router …

• performs a self-test.• checks the software.• reads the saved configuration and restarts program execution.


Use this action, for instance, to activate new application software.



20

MR-1.3 LAN interface configuration attributes


• telindus1423Router/lanInterface/name on page 21• telindus1423Router/lanInterface/mode on page 21• telindus1423Router/lanInterface/ip on page 21• telindus1423Router/lanInterface/bridging on page 21• telindus1423Router/lanInterface/priorityPolicy on page 22• telindus1423Router/lanInterface/arp on page 22• telindus1423Router/lanInterface/adapter on page 23• telindus1423Router/lanInterface/vlan on page 24• telindus1423Router/lanInterface1/switchMode on page 30• telindus1423Router/lanInterface1/ports on page 30• telindus1423Router/lanInterface1/bcastStormProtection on page 33• telindus1423Router/lanInterface/<alarmConfigurationAttributes> on page 34



21

telindus1423Router/lanInterface/name

Use this attribute to assign an administrative name to the LAN interface.

telindus1423Router/lanInterface/mode

Use this attribute to determine whether the packets are treated by the rout-ing process, the bridging process or both.

The mode attribute has the following values:

telindus1423Router/lanInterface/ip

Use this attribute to configure the IP related parameters of the LAN inter-face.

Refer to …

• MU-5.2 - Configuration d'adresses IP on page 59 for general information on configuring IP addresses.

• MU-5.2.3 - Explication de la structure ip on page 63 for a detailed description of the ip structure.

Important remark

If you set the configuration attribute telindus1423Router/lanInterface/mode to bridging, then the settings of the configuration attribute telindus1423Router/lanInterface/ip are ignored. As a result, if you want to manage the Telindus 1423 SHDSL Router via IP, you have to configure an IP address in the bridgeGroup object instead: telindus1423Router/bridge/bridgeGroup/ip.

telindus1423Router/lanInterface/bridging

Use this attribute to configure the bridging related parameters of the LAN interface.

Refer to …

• MU-9 - Configuration du pontage on page 277 for more information on bridging.• MU-9.2.6 - Explication de la structure bridging on page 296 for a detailed description of the bridging

structure.

Value Description

bridging All packets are bridged.

The settings of the IP configuration attributes of the LAN are ignored. If you want to manage the Telindus 1423 SHDSL Router via IP, you have to con-figure an IP address in the bridgeGroup object. Refer to telindus1423Router/bridge/

bridgeGroup/ip on page 224.

routing The IP packets are routed. All other protocols are discarded.

routingAndBridging IP packets are routed. Non-IP packets are bridged.

The settings of the IP configuration attributes are taken into account.

Default:lanRange: 1 … 24 characters

Default:bridgingRange: enumerated, see below

Default:-Range: structure, see below




22

telindus1423Router/lanInterface/priorityPolicy

Use this attribute to apply a priority policy on the LAN interface.

Do this by entering the index name of the priority policy you want to use. You can create the priority policy itself by adding a priorityPolicy object and by configuring the attributes in this object.

Example

If you created a priorityPolicy object with index name my_priority_policy (i.e. priorityPolicy[my_priority_policy]) and you want to apply this priority policy here, then enter the index name as value for the priorityPolicy attribute.

Refer to MU-8.8.6 - Création d'une politique de priorité on page 259 for more information on priority pol-icies.

telindus1423Router/lanInterface/arp

Use this attribute to configure the Address Resolution Protocol (ARP) cache.

The arp structure contains the following elements:

What is the ARP cache?

The LAN interface has been allocated a fixed Ethernet address, also called MAC (Medium Access Con-trol) address. This MAC address is not user configurable. The IP address of the LAN interface, on the other hand, is user configurable. This means that the user associates an IP address with the predefined MAC address. The MAC address - IP address pairs are kept in a table, called the ARP cache. Refer to telindus1423Router/lanInterface/arpCache on page 265 for an example of such a table.

How does the ARP cache work?

Before the Telindus 1423 SHDSL Router sends an IP packet on the LAN interface, it has to know the MAC address of the destination device. If the address is not present in the ARP cache table yet, the Tel-indus 1423 SHDSL Router sends an ARP request on the Ethernet to learn the MAC address and asso-ciated IP address of the destination device. This address pair is then written in the ARP cache. Once the address pair is present, the Telindus 1423 SHDSL Router can reference to this pair if it has to send an IP packet to the same device later on.

Element Description

timeOut Use this element to set the ageing time of the ARP cache entries. Refer to The ARP cache time-out.

proxyArp Use this element to enable or disable the proxy ARP mechanism. Refer to What is proxy ARP?.

Note that when you want to access a proxied device via its IP address that is configured in the telindus1423Router/proxy/nmsGroup/objectTable, then the proxyArp element must be set to enabled.



Default:00000d 02h 00m 00sRange: 00000d 00h 00m 00s -

24855d 03h 14m 07s

Default:enabledRange: enabled / disabled



23

The ARP cache time-out

Summarised, all the MAC address - IP address pairs from ARP requests and replies received on the LAN interface are kept in the ARP cache. However, if devices on the network are reconfigured then this MAC address - IP address relation may change. Therefore, the ARP cache entries are automatically removed from the cache after a fixed time-out. This time-out period can be set with the timeOut element.

What is proxy ARP?

Proxy ARP is the technique in which one host, usually a router, answers ARP requests intended for another machine. By "faking" its identity, the router accepts responsibility for routing packets to the "real" destination. Proxy ARP can help machines on a subnet reach remote subnets without configuring routing or a default gateway.

The advantages and disadvantages of proxy ARP are listed below:

telindus1423Router/lanInterface/adapter

Only present on the single port LAN interface.

Use this attribute to set the Ethernet mode of the LAN interface.

The adapter attribute has the following values: autoDetect, 10Mb/halfDuplex, 10Mb/fullDuplex, 100Mb/halfDuplex, 100Mb/fullDuplex.

advantages The main advantage of using proxy ARP is that it can be added to a single router on a network without disturbing the routing tables of the other routers on the net-work.

Proxy ARP should be used on the network where IP hosts are not configured with default gateway or does not have any routing intelligence.

disadvantages Hosts have no idea of the physical details of their network and assume it to be a flat network in which they can reach any destination simply by sending an ARP request. But using ARP for everything has disadvantages, some of which are listed below:

• It increases the amount of ARP traffic on your segment.• Hosts need larger ARP tables to handle IP-to-MAC address mappings.• Security may be undermined. A machine can claim to be another in order to

intercept packets, an act called "spoofing."• It does not work for networks that do not use ARP for address resolution.• It does not generalise to all network topologies (for example, more than one

router connecting two physical networks).

Default:autoDetectRange: enumerated, see below



24

telindus1423Router/lanInterface/vlan

Use this attribute to create and configure VLANs. Refer to MU-10.3 - Con-figurer les VLAN on page 325 for an introduction and a step-by-step procedure.

As long as no VLANs are created in the vlan table, the LAN interface accepts both VLAN untagged and VLAN tagged frames. The VLAN untagged frames are bridged and/or routed (depending on the setting of the mode attribute). The VLAN tagged frames are bridged (in case the mode attribute is set to bridging or bridgingAndRouting, else they are discarded).

As soon as a VLAN is created in the vlan table, the LAN interface still accepts VLAN untagged frames but only accepts those VLAN tagged frames of which the VLAN ID corresponds with the VLAN ID that has been configured in the vlan table (refer to the configuration element vid on page 26). Other VLAN tagged frames are discarded.

Note that in case of the Telindus 1423 SHDSL Router 4 port Ethernet switch, the vlan table of the 4 port Ethernet switch has to be used only if you want that VLAN tagged packets inside the 4 port Ethernet switch are forwarded to the bridging or routing function of the Telindus 1423 SHDSL Router. Refer to for MU-10.4 - Configuration de VLAN sur le commutateur Ethernet à 4 ports on page 334 more information.

The vlan table contains the following elements:

Element Description

name Use this element to assign an administrative name to the VLAN.

adminStatus Use this element to activate (up) or deactivate (down) the VLAN.

mode Use this element to determine whether, for the corre-sponding VLAN, the packets are treated by the rout-ing process or the bridging process.

The mode element has the following values:

• bridging. All packets received on the VLAN are bridged.• routing. All packets received on the VLAN are routed.

ip Use this element to configure the IP related parame-ters of the VLAN.

Refer to …



bridging Use this element to configure the bridging related parameters of the VLAN.

Refer to …

• MU-9 - Configuration du pontage on page 277 for more information on bridging.• MU-9.2.6 - Explication de la structure bridging on page 296 for a detailed

description of the bridging structure.



Default:upRange: up / down






25

vlan Use this element to configure the specific VLAN parameters.

Refer to telindus1423Router/lanInterface/vlan/vlan on page 26 for a detailed description of the vlan structure.

Element Description




26

telindus1423Router/lanInterface/vlan/vlan

Use the vlan structure in the vlan table to configure the VLAN related param-eters of the corresponding VLAN.

Refer to MU-10.3 - Configurer les VLAN on page 325 for an introduction on VLANs.

The vlan structure contains the following elements:

Element Description

vid Use this element to set the VLAN ID.

Important remark

You can also enter VLAN tag 0 as VLAN ID. This is not really a VLAN, but a way to reverse the filtering:

- all the untagged data is passed, internally, to VLAN 0.- all the other, tagged, data for which no VLANs are defined, are handled by

the main LAN interface.

This allows a set-up where a number of VLANs are VLAN switched, while other VLANs and untagged data are bridged. This is particularly interesting for VLAN based networks with Ethernet switch discovery protocols like Cisco CDP. Until now, this was not possible since the VLAN switching mode did not allow flooding packets over multiple interfaces (bridging), nor did it allow terminating manage-ment data in the device.

In such set-up, the configuration looks as follows:- A first bridge group includes all VLANs that need to be switched. This bridge

group is set in VLAN switching mode.- A second bridge group includes VLAN 0 and possibly also a VLAN for man-

agement of the device.- The interface VLAN table(s) include(s) entries for all switched VLANs, VLAN

0 and possibly a VLAN for management.


Default:1Range: 0 … 4095



27

tagSignificance This element is only relevant when you set the mode element to bridging.

Use this element to determine whether the VLAN tag has a local or a global signif-icance.

The tagSignificance element has the following values:

• local. The VLAN tag only has a local significance, i.e. it is only present on the LAN interface side. This means that when the data is moved …- from the LAN interface to the bridge group, the VLAN tag is removed.- from the bridge group to the LAN interface, the VLAN tag is added.

Keep in mind that when the VLAN tag is removed, you not only discard the VLAN ID but also the user priority.

When you perform bridging between VLANs, then set the tagSignificance element to local. Else you get multiple VLAN tags in the Ethernet frames.

• global. The VLAN tag has a global significance, i.e. it is both present on the LAN interface and the bridge group side.This means that when the data is moved from the LAN interface to the bridge group or vice versa, the VLAN tag is always preserved.

Refer to the figure Local or global VLAN tag significance on page 29.

txCos Use this element to set the default user priority (802.1P, also called COS) of the transmitted VLAN frames.

changeTos Use this element to enable or disable the COS to TOS mapping.

If you set the changeTos attribute to disabled, then the element cosTosMap is ignored.

Note that the TOS to COS mapping is always enabled, irrespective with the setting of the changeTos attribute.

cosTosMap Use this element to determine how the VLAN user pri-ority (COS) maps onto the IP TOS byte value.

Note that the COS to TOS mapping only occurs in case …

• the mode element is set to routing and the changeTos element is set to enabled.

or

• the mode element is set to bridging, the changeTos element is set to enabled and the tagSignificance element is set to local.

The cosTosMap structure contains the following elements:

• p0 … p7. Use these elements to define which VLAN user priority (0 up to 7) maps onto which IP TOS byte value (0 up to 255).

Element Description

Default:globalRange: local / global


Default:disabledRange: enabled / disabled





28

tosCosMap Use this element to determine how the IP TOS byte value maps onto the VLAN user priority (COS).

Note that the COS to TOS mapping only occurs in case …

• the mode element is set to routing.

or

• the mode element is set to bridging and the tagSignificance element is set to local.

The tosCosMap table contains the following elements:

• startTos and endTos. Use these elements to set the TOS byte value range that has to be mapped.

• cos. Use this element to set the VLAN user priority (COS) value on which the specified TOS byte value range has to be mapped.

Element Description

Default:-Range: table, see below





29

Local or global VLAN tag significance

The following figure shows how the tagSignificance element influences the VLAN tagging between the LAN interface and the bridge group:



30

telindus1423Router/lanInterface1/switchMode

Only present on the 4 port Ethernet LAN interface.

Use this attribute to select the switching mode of the 4 port Ethernet interface.

The switchMode attribute has the following values:

telindus1423Router/lanInterface1/ports


Use this attribute to …

• set the Ethernet mode for each port of the 4 port Ethernet interface.• set the VLAN tagging mode for each port of the 4 port Ethernet interface.

The ports table contains 4 entries. Each entry corresponds with a port of the 4 port Ethernet interface. So you can configure the Ethernet and VLAN tagging mode for each port separately. The ports table contains the following elements:

Value Description

portSwitching The 4 port Ethernet interface behaves as a normal Ethernet switch.

dot1QSwitching The 4 port Ethernet interface behaves as a VLAN switch.

Element Description

adapter Use this element to set the Ethernet mode for each port of the 4 port Ethernet interface.

The first part of the adapter element has the following values:

• autoNegotiate. The port automatically negotiates with its link partner which Ethernet mode they are going to use.Using the second part of the adapter element, you can determine which capabil-ities the port may advertise in this negotiation process. Do this by setting the corresponding element in this structure to enabled. The structure contains the following elements: 10Mb/halfDuplex, 10Mb/fullDuplex, 100Mb/halfDuplex, 100Mb/fullDu-plex, flowControl. By default, all these elements are set to enabled.

• fixed. The port is set to a fixed Ethernet mode.Using the second part of the adapter element, you can select the Ethernet mode. Possible values are: 10Mb/halfDuplex, 10Mb/fullDuplex, 100Mb/halfDuplex, 100Mb/fullDuplex.

Default:portSwitchingRange: enumerated, see below


Default:autoNegotiateRange: choice, see below

Default:all enabledRange: structure, see below

Default:10Mb/halfDuplexRange: enumerated, see below



31

vlanTagging Use this element to set the VLAN tagging mode for each port of the 4 port Ethernet interface.

Refer to MU-10.4.2 - Configuration de VLAN sur le commutateur Ethernet à 4 ports on page 338 for more information and some examples.

The first part of the vlanTagging element has the following values:

• untagged- Incoming …

› untagged packets and null-VID tagged packets are internally tagged with the con-figured VID before they are forwarded.

› tagged packets are forwarded unaltered if the VID corresponds with the one configured on the port.

› packets tagged with a different VID are discarded.- Outgoing …

› untagged packets are forwarded unaltered.› tagged packets their VLAN tag is removed before they are forwarded.

Use the second part of the vlanTagging element to set the VID value.

• tagged- Incoming …

› untagged packets and null-VID tagged packets are discarded.


› packets tagged with a different VID are discarded.- Outgoing …


Use the second part of the vlanTagging element to set the VID value.

• trunk. The trunk port is a special kind of tagged port. It can be seen as a concentrator for packets of all other ports or as an uplink to a backbone LAN. On a trunk you can configure more than one VID.- Incoming …

› untagged packets and null-VID tagged packets are discarded.› tagged packets are forwarded unaltered if the VID corresponds with the

one configured on the port.› packets tagged with a different VID are discarded.

- Outgoing …› tagged packets are forwarded unaltered if the VID corresponds with the

one configured on the port.Use the second part of the vlanTagging element to set the different VID values.

Element Description

Default:<untagged> 1Range: choice, see below






32

• portSniffing. If a port is configured as sniffing port, its normal function is suspended and this port starts to transmit all packets it has to monitor. So on a sniffing port the VLAN filtering and incoming and outgoing tagging rules are all disabled.All packets (including packets that do not successfully pass the validation proc-ess) entering or exiting a sniffed port are copied to the sniffing port and trans-mitted unaltered there. If you then connect a VLAN-enabled sniffing program to the sniffing port, you can monitor all traffic to and from the sniffed port.Refer to telindus1423Router/lanInterface1/ports/vlanTagging/<portSniffing> on page 33 for a detailed description of the portSniffing element.

Element Description




33

telindus1423Router/lanInterface1/ports/vlanTagging/<portSniffing>

If you set the first part of the vlanTagging element to portSniffing, then a table appears in the second part. In this table you can determine which ports have to be sniffed and what has to be sniffed on these ports. Do this by adding one or more entries to this table and by configuring these entries.

Each entry consists of a choice element. The first part of this choice element has the following values:

If you want to enable port sniffing, the switchmode attribute has to be set to dot1QSwitching. Refer to telindus1423Router/lanInterface1/switchMode on page 30.

telindus1423Router/lanInterface1/bcastStormProtection


Use this attribute to protect the 4 port Ethernet interface against broadcast/multicast storms. Note that this configuration is done for all ports at once (including the local port).

The bcastStormProtection structure contains the following elements:

Value Description

txSniff Only the outgoing packets of a port are sniffed.

Use the second part of the choice element to determine which port has to be sniffed. Possible values are: port1, port2, port3, port4, localPort.

rxSniff Only the incoming packets of a port are sniffed.


txOrRxSniff Both outgoing and incoming packets of a port are sniffed.


Element Description

mode Use this element to enable or disable the broadcast/multicast storm protection.


• disabled. The broadcast/multicast storm protection is not active.• enabled. The broadcast storm protection is active. However, there is no multicast

storm protection!• inclMulticastStormProt. The broadcast/multicast storm protection is active.

rate Use this element to set the percentage of “64-byte blocks” of packet data that is allowed on an input port during a fixed period. This period is 500 ms for a speed of 10 Mbps and 50 ms for a speed of 100 Mbps.

For example, in case of the default of 1%:

148800 frames/sec * 50 ms/interval * 1% = 74 frames/interval

Default:<txSniff> localPortRange: choice, see below


Default:disabledRange: enumerated, see below




34

telindus1423Router/lanInterface/<alarmConfigurationAttributes>



• the alarms of the lanInterface object, refer to MR-4.4 - LAN interface alarms on page 493.



35

MR-1.4 WAN interface configuration attributes


• telindus1423Router/wanInterface/name on page 36• telindus1423Router/wanInterface/encapsulation on page 36• telindus1423Router/wanInterface/priorityPolicy on page 36• telindus1423Router/wanInterface/maxFifoQLen on page 36• telindus1423Router/wanInterface/<alarmConfigurationAttributes> on page 36



36

telindus1423Router/wanInterface/name

Use this attribute to assign an administrative name to the WAN interface.

telindus1423Router/wanInterface/encapsulation

Use this attribute to select the encapsulation protocol on the WAN interface.

The encapsulation attribute has the following values: atm, frameRelay, ppp and hdlc.

Note that not all encapsulation protocols are present on all Telindus 1423 SHDSL Router versions. Refer to MU-1.3 - Aperçu de la famille de routeurs Telindus SHDSL 1423 on page 7.

telindus1423Router/wanInterface/priorityPolicy

Use this attribute to apply a priority policy on the WAN interface.


Example



telindus1423Router/wanInterface/maxFifoQLen

Use this attribute to set the maximum length (number of packets) of the First In First Out queue.

Refer to telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/algorithm on page 112 for more information on this queue.

telindus1423Router/wanInterface/<alarmConfigurationAttributes>



• the alarms of the wanInterface object, refer to MR-4.5 - WAN interface alarms on page 494.

Default:wanRange: 1 … 24 characters

Default:atmRange: enumerated, see below





37

MR-1.5 Encapsulation configuration attributes

This section discusses the configuration attributes of the encapsulation protocols that can be used on the Telindus 1423 SHDSL Router.

Note that these encapsulation protocols cannot only be used on the xDSL line but, if your Telindus 1423 SHDSL Router is equipped with (an) ISDN interface(s), also on the ISDN interface(s).The protocols Frame Relay, PPP and HDLC are only relevant for TDM operation.Refer to MU-1.3 - Aperçu de la famille de routeurs Telindus SHDSL 1423 on page 7 for more information about which protocols are available on which Telindus 1423 SHDSL Router version.

The following gives an overview of this section:

• MR-1.5.1 - ATM configuration attributes on page 38• MR-1.5.2 - Frame Relay configuration attributes on page 47• MR-1.5.3 - PPP configuration attributes on page 56• MR-1.5.4 - HDLC configuration attributes on page 62• MR-1.5.5 - Error test configuration attributes on page 64



38

MR-1.5.1 ATM configuration attributes


• telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable on page 39• telindus1423Router/wanInterface/channel[wan_1]/atm/vp on page 45• telindus1423Router/wanInterface/channel[wan_1]/atm/atm on page 46



39

telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable

Use this attribute to configure the ATM Permanent Virtual Circuits (PVCs).

Refer to MU-7.2.2 - Configuration des ATM PVC on page 127 for more information on PVCs.

The pvcTable contains the following elements:

Element Description

name Use this element to assign an administrative name to the PVC.

adminStatus Use this element to activate (up) or deactivate (down) the PVC.

mode Use this element to determine whether, for the corre-sponding PVC, the packets are treated by the routing process, the bridging process or both.


• bridging. All packets received on the PVC are bridged.• routing. All packets received on the PVC are routed.• routingAndBridging. The SNAP header is checked to determine whether the pack-

ets have to be bridged or routed.

priorityPolicy Use this element to set a priority policy per PVC.

Refer to telindus1423Router/wanInterface/priorityPolicy on page 36 for more information.

ip Use this element to configure the IP related parame-ters of the PVC.

Refer to …



bridging Use this element to configure the bridging related parameters of the PVC.

Refer to …



atm Use this element to configure the specific PVC param-eters.

Refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm on page 41 for a detailed description of the atm structure.




Default:routingRange: enumerated, see below







40

ppp Use this element to configure the PPP related param-eters of the PVC in case you choose to map PPP onto AAL5 (refer to the elements higherLayerProtocol and mul-tiProtocolMech on page 41).

Refer to MR-1.5.3 - PPP configuration attributes on page 56 for a detailed descrip-tion of the elements in the ppp structure.

Element Description




41

telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm

Use the atm structure in the pvcTable to configure the ATM related parame-ters of the corresponding PVC.

Refer to MU-7.2.2 - Configuration des ATM PVC on page 127 for more information on PVCs.

The atm structure contains the following elements:

Element Description

vpi Use this element to set the Virtual Path Identifier (VPI).

vci Use this element to set the Virtual Channel Identifier (VCI).

You can configure multiple virtual channels per virtual path. Refer to Qu’est-ce que VPI et VCI ? on page 118.

higherLayerProtocol Use this attribute to select the protocol you want to run over ATM.

The higherLayerProtocol element has the following values:

• rfc2684. Select this value in case you want to run bridged/routed Ethernet/IP over ATM (RFC 2684).

• ppp. Select this value in case you want to run PPP over ATM (PPPoA, RFC 2364).

• pppOverEthernet. Select this value in case you want to run PPP over Ethernet (PPPoE, RFC 2516).

-In the PPPoE context, the Telindus 1423 SHDSL Router can only act as a client.

- If you use PPPoE on your computer, then the IP MTU size has to be limited to 1492 bytes. This is a general rule defined in the PPPoE protocol.

multiProtocolMech Use this element to define how you want to encapsu-late the higher layer protocol data in ATM.

The multiProtocolMech element has the following values:

• llcEncapsulation. Logical Link Control (LLC) encapsulation multiplexes multiple protocols over a single virtual connection. The protocol type of each protocol data unit (PDU) is identified by a prefixed IEEE 802.2 Logical Link Control (LLC) header.In general, LLC encapsulation tends to require fewer VCs in a multi-protocol environment but has more fragmentation overhead.

• vcMultiplexing. Virtual Circuit (VC) multiplexing uses one virtual connection to carry the PDUs of exactly one protocol type. When multiple protocols need to be transported, there is a separate VC for each.VC multiplexing tends to reduce fragmentation overhead (e.g. an IPV4 data-gram containing a TCP control packet with neither IP nor TCP options exactly fits into a single cell) but needs more VCs.




Default:rfc2684Range: enumerated, see below

Default:llcEncapsulationRange: enumerated, see below



42

serviceCategory Use this element to specify the ATM service category.

The serviceCategory element has the following values: cbr, vbr-rt, vbr-nrt, ubr.

For more information on ATM service categories, refer to MU-7.2.1 - Introduction ATM on page 118.

peakCellRate Use this element to set the Peak Cell Rate (PCR) of the PVC.

The peakCellRate is expressed in bps. Enter a multiple of 64000 bps as peakCellRate value (e.g. 2048000). The maximum value is the physical connection towards the ATM network.

In auto mode, the PVC will try to get the maximum bandwidth, i.e. the speed of the physical connection towards the ATM network. This is the line speed on which the Telindus 1423 SHDSL Router is trained.

For more information on PCR and how to configure it, refer to …

• MU-7.2.1 - Introduction ATM on page 118• MU-7.2.6 - Configuration de UBR on page 132• MU-7.2.7 - Configuration de VBR-nrt on page 133• MU-7.2.8 - Configuration de VBR-rt on page 134• MU-7.2.9 - Configuration de CBR on page 135

sustCellRate Use this element to set the Sustainable Cell Rate (SCR) of the PVC.

The sustCellRate is expressed in bps. Enter a multiple of 64000 bps as sustCellRate value (e.g. 2048000). The maximum value is the physical connection towards the ATM network.

For more information on SCR and how to configure it, refer to …

• MU-7.2.1 - Introduction ATM on page 118• MU-7.2.7 - Configuration de VBR-nrt on page 133• MU-7.2.8 - Configuration de VBR-rt on page 134

maxBurstSize Use this element to set the Maximum Burst Size (MBS) of the PVC.

The maxBurstSize is expressed in a number of cells (cell times).

For more information on MBS and how to configure it, refer to …

• MU-7.2.1 - Introduction ATM on page 118• MU-7.2.7 - Configuration de VBR-nrt on page 133• MU-7.2.8 - Configuration de VBR-rt on page 134

inArpTimeOut Use this element to set the time between the trans-mission of two consecutive Inverse ARP frames.

Element Description

Default:ubrRange: enumerated, see below

Default:autoRange: auto, 64000…

Default:<opt>Range: 0 …

Default:<opt>Range: 0 … 2147483647


00000d 01h 00m 00s



43

oamF5Loopback Use this element to configure the transmission of OAM F5 LoopBack cells. Refer to Que sont les cel-lules OAM LoopBack (LB) ? on page 126.

Refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm/oamF5Loopback on page 44 for a detailed description of the oamF5Loopback structure.

Element Description




44

telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm/oamF5Loopback

Use the oamF5Loopback structure to configure the transmission of OAM F5 loopback cells.

The oamF5Loopback structure contains the following elements:

Element Description

operation Use this element to enable or disable loopback oper-ation.

The operation element has the following values:

• disabled. Loopback operation is disabled, i.e. the loopback cells are not sent. This means that the ifOperStatus of the PVC becomes up when the ATM is syn-chronised globally. However, this does not guarantee that the PVC is config-ured (correctly) on the remote side.

• enabled. Loopback operation is enabled, i.e. the Telindus 1423 SHDSL Router sends loopback cells at regular intervals. If consecutive cells are not returned by the remote side, then the ifOperStatus of the PVC becomes down.

The Telindus 1423 SHDSL Router always responds to OAM LB cells received from the peer ATM device (both segment and end-to-end cells). However, when OAM LB is activated, the Telindus 1423 SHDSL Router only

sends end-to-end OAM LB request cells.

interval Use this element to set the time interval between the sending of two consecutive loopback cells.

failsPermitted Use this element to set the number of non-returned loopback cells after which the Telindus 1423 SHDSL Router declares the PVC down.

Example

Suppose failsPermitted is set to 10. If 10 consecutive loopback cells are not returned by the remote side, then the Telindus 1423 SHDSL Router declares the PVC down.




24855d 03h 14m 07s




45

telindus1423Router/wanInterface/channel[wan_1]/atm/vp

Use this attribute to configure the transmission of OAM F4 loopback cells.

The vp table contains the following elements:

All entries in the vp configuration table are considered, even if for a certain VPI number no corresponding PVC has been configured. In the vp status and performance tables only the information about VPs that are configured in the vp configuration table is shown. However, the Telindus 1423 SHDSL Router does respond to loopback requests for VPs that are not configured in the vp configuration table but for which a PVC has been configured.

Element Description

vpi Use this element to enter the Virtual Path Identifier (VPI) of the Virtual Path for which you want to send the OAM F4 loopback cells.

oamF4Loopback Use this element to configure the transmission of OAM F4 LoopBack cells. Refer to Que sont les cel-lules OAM LoopBack (LB) ? on page 126.

The elements contained in this structure are the same as those in the oamF5Loopback structure. For a detailed description of these elements refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm/oamF5Loopback on page 44.






46

telindus1423Router/wanInterface/channel[wan_1]/atm/atm

Use this attribute to configure the general ATM parameters.


The atm attribute is only relevant when the Telindus 1423 SHDSL Router operates in plesiochronous SHDSL timing mode.

Element Description

idleCellFormat Use this element to set the format of the ATM idle cells. These cells are transmitted when no data is transmitted over the line. I.e. the line is idle.

The idleCellFormat element has the following values:

• itu. Sets the cells according to the ITU-T format. In this case they are effectively called “idle cells”.

• atmForum. Sets the cells according to the ATM forum format. In this case they are actually called “unassigned cells”.

Some devices use the ITU-T format, others the ATM forum format. Should the per-formance attribute telindus1423Router/wanInterface/channel[wan_1]/atm/unknownCells increase rapidly, then try selecting a different format. However, the default value suffices in most cases.

scrambling Use this element to enable or disable scrambling.

Scrambling is designed to randomise the pattern of 1s and 0s carried in ATM cells or the physical layer frame. Randomising the digital bits can prevent continuous, non-variable bit patterns, in other words long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.

coset Use this element to enable or disable coset polyno-mial algorithm.

The coset polynomial algorithm is used to do header error check calculations.


Default:ituRange: enumerated, see below





47

MR-1.5.2 Frame Relay configuration attributes


• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/ip on page 48• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable on page 49• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi on page 52• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/modeLearnedDlci on page 55• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/delayOptimisation on page 55• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/fragmentation on page 55• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/mru on page 55

These attributes are not present on the on the Telindus 1423 SHDSL Router versions without HWA.



48

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/ip

Use this attribute to globally configure the IP parameters of the DLCIs. More specifically, use this attribute to configure the IP related parameters of all the DLCIs for which …

• in the dlciTable no IP address is defined for that specific DLCI,• and the mode element is set to routing or routingAndBridgning.

If you want to configure the IP related parameters for one specific DLCI, then configure for that DLCI the ip structure in the dlciTable.

Refer to …


• MU-5.2.3 - Explication de la structure ip on page 63 for a detailed description of the ip structure.• MU-7.3.4 - Configuration d’adresses IP dans Frame Relay on page 152 for more specific information

on configuring IP addresses in Frame Relay.

Default:<empty>Range: structure, see below



49

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable

Use this attribute to configure the Frame Relay Data Link Connection Iden-tifiers (DLCIs).

Refer to MU-7.3.2 - Configuration des DLCI Frame Relay on page 149 for more information on DLCIs.

The dlciTable contains the following elements:

Element Description

name Use this element to assign an administrative name to the DLCI.

adminStatus Use this element to activate (up) or deactivate (down) the DLCI.

mode Use this element to determine whether, for the corre-sponding DLCI, the packets are treated by the routing process, the bridging process or both.


• bridging. All packets received on the DLCI are bridged.• routing. All packets received on the DLCI are routed.• routingAndBridging. The SNAP header is checked to determine whether the pack-


priorityPolicy Use this element to set a priority policy per DLCI.


ip Use this element to configure the IP related parame-ters of the corresponding DLCI.

Refer to …



• MU-7.3.4 - Configuration d’adresses IP dans Frame Relay on page 152 for more specific information on configuring IP addresses in Frame Relay.

bridging Use this element to configure the bridging related parameters of the DLCI.

Refer to …



frameRelay Use this element to configure the specific DLCI parameters.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable/frameRelay on page 50, for a detailed description of the frameRelay structure.











50

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable/frameRelay

Use the frameRelay structure in the dlciTable to configure the Frame Relay related parameters of the corresponding DLCI.

Refer to …

• MU-7.3.2 - Configuration des DLCI Frame Relay on page 149 for more information on DLCIs.• MU-7.3.6 - Configuration de CIR et EIR on page 156 for more information on CIR and EIR.

The frameRelay structure contains the following elements:

Element Description

dlci Use this element to set the Data Link Connection Identifier (DLCI).

The DLCI number may have any value between 16 and 1022. However, if you set the type element of the lmi structure to q933-Annex-A, you should only use DLCIs up to 1007.

cir Use this element to set the Committed Information Rate for the DLCI.

The cir is expressed in bps. Enter a multiple of 64000 bps as cir value (e.g. 2048000). The maximum value is the physical connection towards the Frame Relay network. If the cir value is set to 0 (default), it means the complete bandwidth may be used (no flow control).

eir Use this element to set the Excess Information Rate for the DLCI.

The eir is expressed in bps. Enter a multiple of 64000 bps as eir value (e.g. 2048000). The maximum value is the physical connection towards the Frame Relay network. If the eir value is set to 0 (default), it means no excess burst is allowed.

The bursts of data that are allowed are the CIR value + EIR value. I.e. If you want a CIR of 1 Mbps and you want to allow bursts up to 1.5 Mbps, then set the CIR to 1024000 bps and the EIR to 512000 bps.

overhead Use this element to set the amount of overhead you want to add to the configured CIR value. The overhead element is expressed in bytes.

Normally when you specify CIR, you have to make sure that the CIR value you enter includes the user data (i.e. the payload) and the Frame Relay headers (i.e. the overhead). However, you could choose to only specify the amount of payload as CIR value. In that case use the overhead element to specify the amount of over-head.

tc Use this element to set the measurement interval (TC). The TC interval is expressed in milliseconds.

TC is the time over which rates and burst sizes are measured. In general, the dura-tion of TC is proportional to the burstiness of traffic.



Default:0Range: 0 …






51

slidingWindow Use this element to enable or disable sliding window.

If the slidingWindow element is set to …

• disabled (default), then TC is a periodic time interval.• enabled, then TC is a sliding window. This means that data triggers the TC inter-

val which continues until it completes its commuted duration.

deBitSet Use this element to determine, in case the CIR is exceeded, whether all subsequent frames get marked Discard Eligible (deBitSet = enabled) or not (deBitSet = dis-abled).

If congestion occurs at a node in the Frame Relay network, packets marked DE are the first to be dropped.

defaultQueue Use this element to select a default queue.

This allows you to easily set up a traffic policy without having to create and apply traffic policy profiles. However, you still have to create and apply a priority policy profile to empty the queues.

Refer to MU-8.8.9 - Attribut de la file par défaut ou profil de politique de trafic on page 265 for more information.

fragmentation Use this element to enable or disable Frame Relay fragmentation on an end-to-end level. Refer to Qu’est-ce que la fragmentation Frame Relay de bout en bout ? on page 147.

The fragmentation structure contains the following elements:

• endToEndFormat. Use this element to enable or dis-able Frame Relay fragmentation on an end-to-end level.When end-to-end Frame Relay fragmentation is enabled, long frames are frag-mented into a sequence of shorter frames. At the remote side they are reas-sembled into the original frame.

Element Description



Default:queue1Range: enumerated, see below





52

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi

Use this attribute to select the Local Management Interface (LMI) protocol and to fine-tune the LMI operation.

Refer to MU-7.3.5 - Configuration de LMI on page 155 for more information on LMI.

The lmi structure contains the following elements:

Element Description

mode Use this element to set the Frame Relay mode.


• noLmi. No LMI is used.• user. In the LMI context, the Telindus 1423 SHDSL Router is defined as Frame

Relay user. This means it only sends Status Enquiries and receives Status Responses.

• network. In the LMI context, the Telindus 1423 SHDSL Router is defined as Frame Relay network. This means it only receives Status Enquiries and sends Status Responses.

• auto. In the LMI context, the Telindus 1423 SHDSL Router is both Frame Relay user and Frame Relay network. This means it can both send and receive Status Enquiries and Status Responses.At initialisation, the Telindus 1423 SHDSL Router sends the first Full Status Enquiry. As soon as it gets a Full Status Response, it declares that LMI is up.

If you use the Telindus 1423 SHDSL Router in combination with equipment from another vendor and you set the LMI mode to auto, then the LMI mode on the other equipment may only be set to user or network to insure valid oper-

ation.

• nni. In the LMI context, the Telindus 1423 SHDSL Router is both Frame Relay user and Frame Relay network. This means it can both send and receive Status Enquiries and Status Responses.In a Network-to-Network Interface (NNI) it is important for the connected Frame Relay devices that they know which DLCIs are configured on each side. There-fore, in comparison with the auto setting, one extra step is required before LMI is declared to be up.So at initialisation, the Telindus 1423 SHDSL Router sends the first Full Status Enquiry and receives a Full Status Response. Then it waits until it receives a Full Status Enquiry from the remote before it declares that LMI is up.

Refer to Interaction between the LMI modes on page 54 for an overview of how the different LMI modes work together.





53

type Use this element to set the LMI variant. There are sev-eral standards for the LMI protocol with small varia-tions between them. Therefore you should configure the Telindus 1423 SHDSL Router according to the standard that is used by your service provider.

The type element has the following values:

• lmiRev1. Set this value only for compatibility with older equipment.• ansiT1-617-d. Set this value for ANSI LMI compliance.• q933-Annex-A. Set this value for ITU-T LMI compliance.• frf1-2. Set this value for FRF.1-2 compliance.

pollingInterval Use this element to set the time between consecutive Status Enquiry messages.

errorThreshold Use this element to set the maximum number of unan-swered Status Enquiry messages that the Telindus 1423 SHDSL Router will accept before declaring the DLCI down. Also see the monitoredEvents element.

monitoredEvents Use this element to set the number of status polling intervals over which the error threshold is counted.

In other words, if the station receives an errorThreshold number of unanswered Sta-tus Enquiry messages within a monitoredEvents number of pollingInterval intervals, then the interface is declared down.

Example

If the station receives 3 unanswered Status Enquiry messages within 4 x 10s = 40s, then the interface is declared down.

expectedPollInterval Use this element to set the maximum time between two consecutive incoming Status Enquiry messages. Select the value 0 in order to disable verification.

This element is only relevant when using Frame Relay over a point-to-point link (no Frame Relay network). In Frame Relay language, a router is normally considered as a Frame Relay user or DTE. However, if two routers are connected to each other in Frame Relay but without a real Frame Relay network in between, then the routers also have to take the role of a Frame Relay network or DCE (refer to the mode element). In that case the Status Enquiry messages are sent in both direc-tions.

fullEnquiryInterval Use this element to set the number of Status Enquiry intervals that have to pass before sending a Full Sta-tus Enquiry message.

Element Description

Default:q933-Annex-ARange: enumerated, see below


00000d 00h 00m 30s




00000d 00h 00m 30s




54

Interaction between the LMI modes

The following table shows how the different LMI modes work together when two routers are connected to each other over a Frame Relay network:

LMI mode LMI status DLCI status Router learns DLCIs?

Router A

Router B

Router A

Router B

Router A

Router B

Router A Router B

noLmi noLmi up up up up no no

user up down up down no no

network up down up down no no

nni up down up down no no

auto up down up down no no

user user down down down down no no

network up up up up learns (user) no

nni up down up down learns (user) no

auto up up up up learns (user) no

network network down down down down no no

nni up down up down no learns (nni)

auto up up up up no learns (auto)

nni nni up up up up learns learns

auto up up up up learns learns

auto auto up up up up learns learns



55

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/modeLearnedDlci

If the Frame Relay network supports LMI, then the Telindus 1423 SHDSL Router can learn its active and inactive DLCIs. Use this attribute to determine whether, for learned DLCIs, the packets are treated by the routing process, the bridging process or both.

The modeLearnedDlci attribute has the following values:

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/delayOptimisation

Use this attribute to reduce the delay on low speed links. Especially if these links have to transport delay sensitive data (e.g. voice over IP).

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/fragmentation

Use this attribute to enable or disable Frame Relay fragmentation on (phys-ical) interface level. Refer to What is interface Frame Relay fragmentation? on page 145.

The fragmentation structure contains the following elements:

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/mru

Use this attribute to set the Maximum Receive Unit (MRU) of the interface.

What is MRU?

The Maximum Receive Unit (MRU) is the largest size packet or frame, specified in octets (eight-bit bytes), that can be received in a packet- or frame-based network (e.g. the Internet).

Value Description

bridging All packets received on the DLCI are bridged.

routing All packets received on the DLCI are routed.

routingAndBridging The SNAP header is checked to determine whether the packets have to be bridged or routed.

Element Description

interfaceFormat Use this element to enable or disable Frame Relay fragmentation on (physical) interface level.

When interface Frame Relay fragmentation is enabled, long frames are frag-mented into a sequence of shorter frames. At the remote side they are reassem-bled into the original frame.


Default:noneRange: none / lowSpeedLinks






56

MR-1.5.3 PPP configuration attributes


• telindus1423Router/wanInterface/channel[wan_1]/ppp/ip on page 57• telindus1423Router/wanInterface/channel[wan_1]/ppp/mode on page 57• telindus1423Router/wanInterface/channel[wan_1]/ppp/bridging on page 57• telindus1423Router/wanInterface/channel[wan_1]/ppp/delayOptimisation on page 57• telindus1423Router/wanInterface/channel[wan_1]/ppp/mru on page 57• telindus1423Router/wanInterface/channel[wan_1]/ppp/compression on page 58• telindus1423Router/wanInterface/channel[wan_1]/ppp/linkMonitoring on page 59• telindus1423Router/wanInterface/channel[wan_1]/ppp/authentication on page 60• telindus1423Router/wanInterface/channel[wan_1]/ppp/authenPeriod on page 60• telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionName on page 61• telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionSecret on page 61




57

telindus1423Router/wanInterface/channel[wan_1]/ppp/ip

Use this attribute to configure the IP related parameters of the PPP link.

Refer to …



telindus1423Router/wanInterface/channel[wan_1]/ppp/mode



telindus1423Router/wanInterface/channel[wan_1]/ppp/bridging

Use this attribute to configure the bridging related parameters of the PPP link.

Refer to …


structure.

telindus1423Router/wanInterface/channel[wan_1]/ppp/delayOptimisation

Use this attribute to reduce the delay on low speed links. Especially if these links have to transport delay sensitive data (e.g. voice over IP).

telindus1423Router/wanInterface/channel[wan_1]/ppp/mru


What is MRU?


Value Description

bridging All packets received on the PPP link are bridged. BCP is set up.

routing All packets received on the PPP link are routed. IPCP is set up.

routingAndBridging The SNAP header is checked to determine whether the packets have to be bridged or routed. IPCP and BCP are set up.

multiLink Select this value if the PPP link is part of a bundle of PPP links (multi-link PPP or MLPPP).




Default:noneRange: none / lowSpeedLinks




58

telindus1423Router/wanInterface/channel[wan_1]/ppp/compression

Use this attribute to enable or disable the compression of PPP encapsu-lated packets.

The compression attribute has the following values:

Important remark

The PPP compression algorithm uses a lot of memory (64 KB for compression and 64 KB for decom-pression, per PPP session). Since it is possible to have multiple PPP sessions (when using ATM PVCs up to 31 simultaneous sessions are allowed, which can all be configured to use PPP compression), the memory can turn out to be insufficient. In this case …

• the compression is switched off on the interfaces that could not allocate enough memory,• a message is dumped in the message table, containing the relevant interface and a warning that the

router must be rebooted to reactivate compression on that specific interface.

It is also possible that, when looking at the statistics, enough memory seems to be available but that the allocation problem remains. This means that the memory is fragmented and no block as big as 64 KB is found.

Value Description

disabled No PPP compression is done.

predictor1 PPP compression is done using the Predictor type 1 compression algorithm (RFC 1978). Using compression you can increase the throughput on PPP links.




59

telindus1423Router/wanInterface/channel[wan_1]/ppp/linkMonitoring

Use this attribute to enable or disable link monitoring and to fine-tune it.

Refer to MU-7.4.5 - Configuration de la surveillance de liaison on page 170 for more information on link monitoring.

The linkMonitoring structure contains the following elements:

Element Description

operation Use this element to enable or disable link monitoring.

interval Use this element to set the time interval between two consecutive echo requests.

replyTimeOut Use this element to set the time the Telindus 1423 SHDSL Router waits for a reply on the echo request.

If no reply has been received within this time-out, then the Telindus 1423 SHDSL Router considers this as a failed echo request.

failsPermitted Use this element to set the number of failed echo requests after which the Telindus 1423 SHDSL Router declares the PPP link down.

Example

Suppose failsPermitted is set to 10. If on 10 consecutive echo requests no reply is given, then the Telindus 1423 SHDSL Router declares the PPP link down and the PPP handshake is started again.




24855d 03h 14m 07s


00000d 00h 04m 15s




60

telindus1423Router/wanInterface/channel[wan_1]/ppp/authentication

Use this attribute to enable or disable authentication on the PPP link.


• MU-7.4.6 - Configuration de PAP on page 171.• MU-7.4.8 - Configuration de CHAP on page 175.

The authentication attribute has the following values:

telindus1423Router/wanInterface/channel[wan_1]/ppp/authenPeriod

Use this attribute to set the PPP authentication interval.

Normally on an authenticated PPP link, authentication is not only performed at link set-up but also at regular intervals during the data transfer. You can set this interval using the authenPeriod attribute. If you set the authenPeriod attribute to 00000d 00h 00m 00s, then authentication is only performed at link set-up and not during the data transfer.


• MU-7.4.6 - Configuration de PAP on page 171.• MU-7.4.8 - Configuration de CHAP on page 175.

Value Description

disabled Authentication is disabled. However, the Telindus 1423 SHDSL Router will answer to authentication requests received from the remote side.

pap This side of the link requests a PAP authentication from the remote router.

chap This side of the link requests a CHAP authentication from the remote router.

chapOrPap This side of the link requests a CHAP or PAP authentication from the remote router.

If the remote router supports …

• only PAP, then PAP is used.• only CHAP, then CHAP is used.• both CHAP and PAP, then CHAP is used.

msChap This side of the link requests an MS CHAP version 1 authentication from the remote router.

msChapV2 This side of the link requests an MS CHAP version 2 authentication from the remote router.



24855d 03h 14m 07s



61

telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionName

Use this attribute to set the PPP authentication name of the Telindus 1423 SHDSL Router.



telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionSecret

Use this element to set the PPP authentication secret of the Telindus 1423 SHDSL Router.







62

MR-1.5.4 HDLC configuration attributes


• telindus1423Router/wanInterface/channel[wan_1]/hdlc/bridging on page 63• telindus1423Router/wanInterface/channel[wan_1]/hdlc/mru on page 63




63

telindus1423Router/wanInterface/channel[wan_1]/hdlc/bridging

Use this attribute to configure the bridging related parameters of the HDLC link.

Refer to …


structure.

telindus1423Router/wanInterface/channel[wan_1]/hdlc/mru


What is MRU?






64

MR-1.5.5 Error test configuration attributes


• telindus1423Router/wanInterface/channel[wan_1]/errorTest/testType on page 65• telindus1423Router/wanInterface/channel[wan_1]/errorTest/blockSize on page 65• telindus1423Router/wanInterface/channel[wan_1]/errorTest/programmablePattern on page 65




65

telindus1423Router/wanInterface/channel[wan_1]/errorTest/testType

Use this attribute to select a test pattern.

Possible patterns are: itu511(2^9), ituInv511(2^9), tls1023(2^10), tlsInv1023(2^10), itu2047(2^11), ituInv2047(2^11), itu32767(2^15), ituInv32767(2^15), itu1048575(2^20), ituInv1048575(2^20), itu8388607(2^23), ituInv8388607(2^23), space, mark, dot, programmablePattern.

If you set the testType attribute to programmablePattern, then you can generate your own test pattern by typ-ing a test pattern in the programmablePattern attribute (refer to telindus1423Router/wanInterface/channel[wan_1]/errorTest/programmablePattern on page 65).

Refer to MU-7.6 - Configuration d'un test d'erreur on page 189 for more information on setting up an error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/blockSize

Use this attribute to set the size of the test blocks.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/programmablePattern

Use this attribute to generate your own test pattern.

Do this by typing a test pattern in the programmablePattern attribute and by setting the testType attribute to programmablePattern (refer to telindus1423Router/wanInterface/channel[wan_1]/errorTest/testType on page 65).

Default:itu32767(2^15)Range: enumerated, see below

Default:512Range: 256, 512, 1024

Default:<empty>Range: 32 bit string



66

MR-1.6 SHDSL line configuration attributes

This section describes the following line configuration attributes:

• telindus1423Router/wanInterface/line/channel on page 67• telindus1423Router/wanInterface/line/region on page 67• telindus1423Router/wanInterface/line/timingMode on page 68• telindus1423Router/wanInterface/line/retrain on page 69• telindus1423Router/wanInterface/line/startupMargin on page 71• telindus1423Router/wanInterface/line/minSpeed on page 71• telindus1423Router/wanInterface/line/maxSpeed on page 71• telindus1423Router/wanInterface/line/minSpeed2P on page 72• telindus1423Router/wanInterface/line/maxSpeed2P on page 72• telindus1423Router/wanInterface/line/mode on page 72• telindus1423Router/wanInterface/line/dualPairMode on page 72• telindus1423Router/wanInterface/line/linkAlarmThresholds on page 74• telindus1423Router/wanInterface/line/numExpectedRepeaters on page 75• telindus1423Router/wanInterface/line/eocHandling on page 75• telindus1423Router/wanInterface/line/management on page 75• telindus1423Router/wanInterface/line/<alarmConfigurationAttributes> on page 76

This section describes the following line pair configuration attributes:

• telindus1423Router/wanInterface/line/linePair[ ]/<alarmConfigurationAttributes> on page 76



67

telindus1423Router/wanInterface/line/channel

Use this attribute to determine which unit is the central unit and which the remote unit. I.e. it determines which unit acts as master and which as slave during the synchronisation procedure. Therefore set one device to central and its remote counterpart to remote.

On the Telindus 1423 SHDSL Router, the clocking follows the channel attribute:

Important remark

Note that also the timingMode attribute influences the clocking. Refer to telindus1423Router/wanInterface/line/timingMode on page 68.

telindus1423Router/wanInterface/line/region

Use this attribute to determine which SHDSL standard is used.

The region attribute has the following values:

If the channel attribute is set to … then the clocking is set to …

central internal.

remote slave-receive.

Value Description

annexA The North-American SHDSL standard is used.

annexB The European SHDSL standard is used.

auto The Telindus 1423 SHDSL Router itself determines which standard it has to use.

Default:remoteRange: central / remote




68

telindus1423Router/wanInterface/line/timingMode

Use this attribute to set the timing mode. It is important to set the timingMode attribute correct when using the Telindus 1423 SHDSL Router in combination with other SHDSL devices. For more information on compatibility issues, refer to the document “Interoperability for OneAccess SHDSL products” (PDF).

• This attribute is not present on the Telindus 1423 SHDSL Router equiped with ISDN ports.• The timingMode attribute is only available on the 1423 SHDSL 1P 2ETH4P HWA and 1423 SHDSL 2P

2ETH4P HWA. Refer to MU-1.3 - Aperçu de la famille de routeurs Telindus SHDSL 1423 on page 7 for a complete overview of the OneAccess 1423 SHDSL Router family.

The timingMode attribute has the following values:

Important remarks

• The timingMode attribute is only relevant for TDM operation. If you have two Telindus 1423 SHDSL Routers on which you set the timingMode attribute to plesiochronous, then you can not connect them with each other point-to-point because they both operate in slave-receive clocking.

• Plesiochronous mode can only work when the speed falls within the range of 192 kbps and 2048 kbps (i.e. minSpeed = 192kbps or minSpeed2P = 384kbps and maxSpeed(2P) = 2048kbps). If a speed is selected which is …- lower than 192 kbps, the actual speed is automatically increased to 192 kbps (or 384 kbps in case

of a 2 pair version).- higher than 2048 kbps, the actual speed is automatically limited to 2048 kbps.

Value Description

synchronous The Telindus 1423 SHDSL Router operates in synchronous mode. In this case the clocking follows the setting of the channel attribute. Refer to telindus1423Router/wanIn-terface/line/channel on page 67.

plesiochronous The Telindus 1423 SHDSL Router operates in plesiochronous mode. In this case the clocking is always slave-receive, independently of the setting of the channel attribute. This means that the remote device (e.g. a Crocus SHDSL) has to supply the clock.

Default:synchronousRange: enumerated, see below



69

telindus1423Router/wanInterface/line/retrain

Use this attribute to determine when the Telindus 1423 SHDSL Router should retrain.

The retrain criteria

The following criteria determine when to retrain:

Criterion Description

no SHDSL frame synchro-nisation

When the Telindus 1423 SHDSL Router cannot synchronise on the SHDSL framing, it retrains.

SHDSL frame CRC error threshold exceeded

SHDSL framing sends 166 blocks per second over the line, independ-ently of the speed. Each block has a CRC check. When a certain per-centage of frames has a CRC error, the Telindus 1423 SHDSL Router retrains.

signal to noise ratio too low When the signal to noise ratio becomes too low during a certain period of time, the Telindus 1423 SHDSL Router retrains.

layer 2 protocol not yet up When you connect the Telindus 1423 SHDSL Router with a remote SHDSL device, the Telindus 1423 SHDSL Router trains and establishes a layer 1 link with the remote SHDSL device. Then the Telindus 1423 SHDSL Router tries to establish a layer 2 link (e.g. PPP, FR, ATM). If the layer 2 handshake does not succeed within 1 minute, then the Telindus 1423 SHDSL Router retrains and the whole process restarts. Also the following message is dumped in the message table: Retrain due to framer-out-of-sync. However, once the layer 2 handshake succeeds (layer 2 is up), then a drop of the layer 2 link will not cause a retrain.




70

Configuring the retrain criteria

The retrain structure contains the following elements:

Element Description

enabled Use this attribute to enable (yes) or disable (no) retraining. So when selecting no, the Telindus 1423 SHDSL Router will never retrain (even not when the line is disconnected).

errorPersistence-Time

Use this element to set the period, in seconds, during which each retrain criterion is measured. If within this period the predefined criterion value is equalled or exceeded, the Telindus 1423 SHDSL Router retrains.

errorThreshold Use this element to set the amount of CRC errors, in promille, at which the Telindus 1423 SHDSL Router should retrain. If the amount of CRC errors exceeds this value, then the Telindus 1423 SHDSL Router retrains.

The erroneous SHDSL frames can be monitored using the performance attribute codeViolations.

snrThreshold Use this element to set the signal to noise ratio, in dB, which has to be maintained. If the measured signal to noise ratio drops below this value, then the Telindus 1423 SHDSL Router retrains. It will retrain at a lower speed (because of the dete-riorated line conditions).

stepupMargin In case the Telindus 1423 SHDSL Router retrains because the measured signal to noise ratio drops below the snrThreshold value, then it will retrain at a lower speed (because of the deteriorated line conditions).

If after this retrain the measured signal to noise value increases again with a value as configured in the stepupMargin element, then the Telindus 1423 SHDSL Router retrains again in order to achieve a higher speed.

Default:yesRange: yes / no




Default:disabledRange: 3 … 15



71

telindus1423Router/wanInterface/line/startupMargin

Use this attribute to set the target margin in function of which a line speed has to be selected during the ITU-T G.994.1 auto speed negotiation.

The startupMargin attribute is only relevant in case on both the central and remote Telindus 1423 SHDSL Router (or any other compatible SHDSL device) a speed range is selected. In other words, the startup-Margin attribute has no function in case a fixed speed is selected (i.e. minSpeed(2P) = maxSpeed(2P)).

The higher the startupMargin, the lower the selected line speed but the more stable the line will be. The startupMargin attribute has the following values: disabled, 0dB, 1dB, 2dB, 3dB, 4dB, 5dB, 6dB, 7dB, 8dB, 9dB, 10dB. When you set the startupMargin to disabled, the target margin is not considered during the ITU-T G.994.1 auto speed negotiation. I.e. all the speeds in the range as set with the attributes minSpeed(2P) and maxSpeed(2P) are available.

What is the target margin?

The target margin is the amount of received signal power in excess of that required to achieve the DSL target bit error rate of 10-7.

telindus1423Router/wanInterface/line/minSpeed

Use this attribute to set the lowest line speed the Telindus 1423 SHDSL Router may select. The minSpeed attribute has the following values: 64kbps up to 2304kbps in steps of 64kbps.

Refer to MU-5.3.2 - Sélection d'une vitesse de ligne SHDSL (gamme) on page 77 for more information.

telindus1423Router/wanInterface/line/maxSpeed

Use this attribute to set the highest line speed the Telindus 1423 SHDSL Router may select. The maxSpeed attribute has the following values: 64kbps up to 2304kbps in steps of 64kbps.


Default:2dBRange: enumerated, see below

Default:64kbpsRange: enumerated, see below




72

telindus1423Router/wanInterface/line/minSpeed2P

This attribute is only present on the Telindus 1423 SHDSL Router 2 pair ver-sion.

Use this attribute to set the lowest line speed the Telindus 1423 SHDSL Router 2 pair version may select (if it is truly in 2 pair operation, refer to telindus1423Router/wanInterface/line/mode). The minSpeed2P attribute has the following values: 128kbps up to 4608kbps in steps of 128kbps.


telindus1423Router/wanInterface/line/maxSpeed2P


Use this attribute to set the highest line speed the Telindus 1423 SHDSL Router 2 pair version may select (if it is truly in 2 pair operation, refer to telindus1423Router/wanInterface/line/mode). The maxSpeed2P attribute has the following values: 128kbps up to 4608kbps in steps of 128kbps.


telindus1423Router/wanInterface/line/mode


Use this attribute to select between single pair or dual pair operation. When you change the mode attribute, then make sure that you use the correct speed attributes to set the speed:

telindus1423Router/wanInterface/line/dualPairMode


If the mode attribute is set to dualPair, then use the dualPairMode attribute to set the dual pair operation mode. The dualPairMode attribute has the following possible values:

If the mode attribute is set to … then configure the speed using the attributes …

singlePair, minSpeed and maxSpeed.

dualPair, minSpeed2P and maxSpeed2P.

Value Description

standard The dual pair SHDSL line operates strictly as described in the SHDSL standard. If the Telindus 1423 SHDSL Router is connected to a remote device that operates strictly according to the SHDSL standard, then select the standard value.

enhanced The dual pair SHDSL line operates slightly different than described in the SHDSL standard (some enhancements are present). If you select the enhanced value, then it is possible that you experience problems when connecting to third party SHDSL devices. In that case, select the standard value.



Default:dualPairRange: singlePair / dualPair

Default:standardRange: standard / enhanced



73

If you have two Telindus 1423 SHDSL Routers connected to each other in a point-to-point set-up, then make sure that you set the dualPairMode attribute to the same value at both sides!



74

telindus1423Router/wanInterface/line/linkAlarmThresholds

Use this attribute to set the alarm threshold values of the most important line parameters. If this predefined threshold value is exceeded, then a corresponding alarm is generated.

The linkAlarmThresholds structure contains the following elements:

Element Description

lineAttenuationOn Use this element to set the alarm threshold value of the line attenuation in dB. If the line attenuation …

• exceeds this value during at least 10 seconds, then the lineAttenuation alarm is raised.

• drops below this value during at least 10 seconds, then the lineAttenuation alarm is cleared.

signalNoiseOn Use this element to set the alarm threshold value of the signal noise in dB. If the signal noise …

• drops below this value during at least 10 seconds, then the signalNoise alarm is raised.

• exceeds this value during at least 10 seconds, then the signalNoise alarm is cleared.

errSecOn Use this element to set the alarm threshold value of the erroneous seconds in days, hours, minutes and seconds. If the amount of erroneous seconds …

• exceeds this value within a 15 minutes period1, then the errSecExceeded alarm is raised.

• drops below this value within a 15 minutes period, then the errSecExceeded alarm is cleared.

1. The 15 minutes periods run synchronous with the 15 minutes periods of the telindus1423Router/wanInterface/line/h2Line performance attribute.Because alarms are raised or cleared within 15 minutes periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minutes period the errSecOn value is exceeded, then the errSecRatioExceeded alarm is raised. The alarm stays on for the remainder of the 15 minutes period. The alarm is only cleared if also in the next 15 minutes period the errSecOn value is not exceeded.

sevErrSecOn Use this element to set the alarm threshold value of the severely erroneous seconds in days, hours, min-utes and seconds. If the amount of severely errone-ous seconds …

• exceeds this value within a 15 minutes period1, then the sevErrSecExceeded alarm is raised.

• drops below this value within a 15 minutes period, then the sevErrSecExceeded alarm is cleared.


Default:0.0Range: 0.0 … 63.5

Default:0.0Range: 0.0 … 58.4


00000d 18h 12m 15s


00000d 18h 12m 15s



75

telindus1423Router/wanInterface/line/numExpectedRepeaters

Use this attribute to set the number of Crocus SHDSL Repeaters that the Telindus 1423 SHDSL Router can expect to find on the SHDSL line. If the actual number of repeaters does not match the number you entered in the numExpectedRepeaters attribute, then the invalidNumRepeaters alarm is raised.

telindus1423Router/wanInterface/line/eocHandling

SHDSL devices can communicate with each other through the Embedded Operations Channel (EOC). Use the eocHandling attribute to define the handling of the EOC messages.

Refer to MU-5.4.3 - Contrôle d’échange de messages EOC standard on page 80 for more information.

telindus1423Router/wanInterface/line/management

Use this attribute to determine whether and which management data is for-warded over the SHDSL line.

Refer to MU-5.4.2 - Contrôle d’échange de messages EOC propriétaire on page 79 for more information.


Default:noneRange: enumerated, see below

Default:o10-PathManagementRange: enumerated, see below



76

telindus1423Router/wanInterface/line/<alarmConfigurationAttributes>



• the alarms of the line object, refer to MR-4.6 - SHDSL line alarms on page 495.

telindus1423Router/wanInterface/line/linePair[ ]/<alarmConfigurationAttributes>



• the alarms of the linePair[ ] object, refer to MR-4.7 - SHDSL line pair alarms on page 496.



77

MR-1.7 End and repeater configuration attributes


• telindus1423Router/wanInterface/repeater[ ]/<alarmConfigurationAttributes> on page 78• telindus1423Router/wanInterface/end/<alarmConfigurationAttributes> on page 78

The repeater[ ] and the end objects are not present in the containment tree by default. They are added auto-matically when you configure the eocHandling attribute. Refer to MU-5.4.3 - Contrôle d’échange de mes-sages EOC standard on page 80.



78

telindus1423Router/wanInterface/repeater[ ]/<alarmConfigurationAttributes>



• the alarms of the repeater[ ] object, refer to MR-4.8 - End and repeater alarms on page 498.

telindus1423Router/wanInterface/end/<alarmConfigurationAttributes>



• the alarms of the end object, refer to MR-4.8 - End and repeater alarms on page 498.



79

MR-1.8 BRI configuration attributes

This section discusses the configuration attributes of the BRI interface. First it describes the configura-tion attributes of the BRI interface in general. Then it describes more specifically the configuration attributes of the B-channels and of the leasedLine[ ] object that can be added under the bri[ ] object.


• MR-1.8.1 - General BRI configuration attributes on page 80• MR-1.8.2 - B-channel configuration attributes on page 83• MR-1.8.3 - ISDN leased line configuration attributes on page 85



80

MR-1.8.1 General BRI configuration attributes


• telindus1423Router/bri[ ]/tei on page 81• telindus1423Router/bri[ ]/teiValue on page 81• telindus1423Router/bri[ ]/telephoneNrs on page 82• telindus1423Router/bri[ ]/dialAllowed on page 82• telindus1423Router/bri[ ]/<alarmConfigurationAttributes> on page 82



81

telindus1423Router/bri[ ]/tei

Use this attribute to determine how a Terminal Endpoint Identifier (TEI) is assigned to the Basic Rate ISDN interface. TEIs are used to distinguish between several different devices using the same ISDN links.

The tei attribute has the following values:

telindus1423Router/bri[ ]/teiValue

Use this attribute to set the Terminal Endpoint Identifier (TEI) of the Basic Rate ISDN interface in case you set the configuration attribute telindus1423Router/bri[ ]/tei to fixed.

Value Description

fixed The TEI value of the Basic Rate ISDN interface has to be set by the user using the configuration attribute telindus1423Router/bri[ ]/teiValue.

In this case the TEI value can range from 1 up to 63.

auto The TEI value of the Basic Rate ISDN interface is set automatically by the Network Terminator (NT) to which the interface is attached to. The setting of the configura-tion attribute telindus1423Router/bri[ ]/teiValue is ignored.

In this case the TEI value can range from 64 up to 126.

permanent The TEI value of the Basic Rate ISDN interface is set to 0. The setting of the con-figuration attribute telindus1423Router/bri[ ]/teiValue is ignored.

In this case both layer 1 and layer 2 are permanently up.





82

telindus1423Router/bri[ ]/telephoneNrs

Use this attribute to assign (a) telephone number(s) to the Basic Rate ISDN interface. These numbers are only relevant in case BAP is enabled. The following tries to explains this.

When BAP is activated and when the local router decides that it needs to add a member to the existing ISDN bundle (because the tx or rx throughput threshold was exceeded), then it sends a request to the remote router asking for the addition of a link to the bundle. If the remote router agrees (based on its throughput threshold settings), the remote router will acknowledge the request. In this acknowledgement message, the remote router adds the telephone number to which the central router has to call to. This telephone number is one defined on a BRI that still has available channels. The central router then will establish a new call using the telephone number it received from the remote router. This whole proce-dure ensures that the central calls a BRI that is still available (i.e. for which not all B-channels are assigned to ISDN calls).

Note however that is not mandatory to enter telephone numbers in the telephoneNrs table. If you leave this table empty and the remote ISDN device wants to add an extra B-channel to the bundle, then any avail-able B-channel on any available BRI interface of the local ISDN interface will be taken.

The telephoneNrs table contains the following elements:

telindus1423Router/bri[ ]/dialAllowed

Use this attribute allow (yes) or deny (no) dial-up calls (both in and out) on the BRI interface.

If the dialAllowed attribute is set to yes, then you can use the BRI interface both in dial-up operation as leased line operation. If, however, the dialAllowed attribute is set to no, then you can use the BRI interface only in leased line operation.

telindus1423Router/bri[ ]/<alarmConfigurationAttributes>



• the alarms of the bri[ ] object, refer to MR-4.9 - BRI alarms on page 500.

Element Description

telNr Use this element to enter the telephone number.

uniqueDigits Use this element to set the number of unique digits. Refer to What are unique digits?.

Setting the uniqueDigits to 0 means that the complete telephone number as entered in the telNr element should be considered as unique digits.


Default:<empty>Range: 0 … 36 tel. characters


Default:yesRange: yes / no



83

MR-1.8.2 B-channel configuration attributes


• telindus1423Router/bri[ ]/bChannel[ ]/<alarmConfigurationAttributes> on page 84



84

telindus1423Router/bri[ ]/bChannel[ ]/<alarmConfigurationAttributes>



• the alarms of the bChannel[ ] object, refer to MR-4.10 - B-channel alarms on page 501.



85

MR-1.8.3 ISDN leased line configuration attributes


• telindus1423Router/bri[ ]/leasedLine[ ]/encapsulation on page 86• telindus1423Router/bri[ ]/leasedLine[ ]/priorityPolicy on page 86• telindus1423Router/bri[ ]/leasedLine[ ]/maxFifoQLen on page 86• telindus1423Router/bri[ ]/leasedLine[ ]/channelAllocation on page 87• telindus1423Router/bri[ ]/leasedLine[ ]/<alarmConfigurationAttributes> on page 87

For the configuration attributes of the encapsulation objects (frameRelay, ppp, hdlc and errorTest) which are located under the leasedLine[ ] object, refer to MR-1.5 - Encapsulation configuration attributes on page 37.



86

telindus1423Router/bri[ ]/leasedLine[ ]/encapsulation

Use this attribute to select the encapsulation protocol on the leased line ISDN connection.

The encapsulation attribute has the following values: frameRelay, ppp, hdlc and errorTest.

Refer to 6.6 - How to configure a leased line ISDN connection on a BRI interface?_ (Telindus 1034 Router only)_ on page 203 for more information on how to set up a leased line ISDN.

telindus1423Router/bri[ ]/leasedLine[ ]/priorityPolicy

Use this attribute to apply a priority policy on the leased line ISDN connec-tion.


Example



telindus1423Router/bri[ ]/leasedLine[ ]/maxFifoQLen



Default:frameRelayRange: enumerated, see below





87

telindus1423Router/bri[ ]/leasedLine[ ]/channelAllocation

Use this attribute to activate the BRI channels of the leased line ISDN con-nection.

The channelAllocation structure contains the elements:

Depending which channels you activate, you can comply with the following standards:

• 64S: B1 channel• 64S2: B1+B2 channel• TS01: B1+D channel• TS02: B1+B2+D channel

Refer to 6.6 - How to configure a leased line ISDN connection on a BRI interface?_ (Telindus 1034 Router only)_ on page 203 for more information on how to set up a leased line ISDN.

telindus1423Router/bri[ ]/leasedLine[ ]/<alarmConfigurationAttributes>



• the alarms of the bri[ ]/leasedLine[ ] object, refer to MR-4.10 - B-channel alarms on page 501.

Element Description

d Use this element to activate (on) or deactivate (off) the D-channel.

b1 Use this element to activate (on) or deactivate (off) the B1-channel.

b2 Use this element to activate (on) or deactivate (off) the B2-channel.


Default:offRange: on / off





88

MR-1.9 Profiles configuration attributes

If you want to establish an ISDN dial-up connection, then you first have to set up dial, encapsulation and forwarding profiles. Then you have to config-ure the dial map in which you combine the different profiles. Refer to MU-6 - Configuration des connex-ions ISDN on page 95 for more information.

Also setting up traffic and priority policies involves creating and applying profiles. Refer to MU-8.8 - Con-figuration de la politique de trafic et de priorité sur le routeur on page 249 and MU-9.3 - Configuration de la politique de trafic et de priorité sur le pont on page 300 for more information.

This section lists the configuration attributes that are present in the different profiles.


• MR-1.9.1 - ISDN dial profile configuration attributes on page 89• MR-1.9.2 - Encapsulation profile configuration attributes on page 94• MR-1.9.3 - Forwarding profile configuration attributes on page 98• MR-1.9.4 - IP traffic policy configuration attributes on page 100• MR-1.9.5 - Bridging traffic policy configuration attributes on page 109• MR-1.9.6 - Priority policy configuration attributes on page 111

Default:all time slots enabled, except 0 and 16

Range: bit string



89

MR-1.9.1 ISDN dial profile configuration attributes


• telindus1423Router/profiles/dial/defaultIsdn/isdnInterfaces on page 90• telindus1423Router/profiles/dial/defaultIsdn/dialPktBufSize on page 90• telindus1423Router/profiles/dial/defaultIsdn/idleTimeOut on page 90• telindus1423Router/profiles/dial/defaultIsdn/fastIdleTimeOut on page 90• telindus1423Router/profiles/dial/defaultIsdn/callInterval on page 90• telindus1423Router/profiles/dial/defaultIsdn/callTimeOut on page 90• telindus1423Router/profiles/dial/defaultIsdn/24hMaxCallTime on page 91• telindus1423Router/profiles/dial/defaultIsdn/dialTimeTable on page 91• telindus1423Router/profiles/dial/defaultIsdn/maxChannelsUsed on page 93• telindus1423Router/profiles/dial/defaultIsdn/minChannelsFree on page 93



90

telindus1423Router/profiles/dial/defaultIsdn/isdnInterfaces

Use this attribute to determine through which BRI interface the ISDN con-nection has to be set up.

The isdnInterfaces table only contains one element: interface. This element has possible values bri[1] and bri[2]. If you leave the isdnInterfaces table empty, then both BRI interfaces are used (this would be the same as entering bri[1] and bri[2]).

If both BRI interfaces can be used (i.e. the isdnInterfaces table is empty or contains both bri[1] and bri[2]), then it is not possible for the Telindus 1423 SHDSL Router to know which interface is active because sometimes layer 1 is kept down by the Network Termination device until a call is set up. So in this par-ticular case, when a call has to be set up, BRI 1 is always tried first. If BRI 1 fails, then BRI 2 is tried. Switching between BRI 1 and BRI 2 takes about 10 seconds.

telindus1423Router/profiles/dial/defaultIsdn/dialPktBufSize

Use this attribute to set the size of the buffer, in packets, that is used to buffer the data when the ISDN connection is being set up.

telindus1423Router/profiles/dial/defaultIsdn/idleTimeOut

Use this attribute to set the time during which an incoming or outgoing ISDN call may be idle (i.e. the connection is up, but no data is sent) before it is terminated. Both incoming and outgoing traffic is considered. I.e. the ISDN line goes idle only if during the idle timer no packets have been transmitted nor received.

telindus1423Router/profiles/dial/defaultIsdn/fastIdleTimeOut

Use this attribute to set the time during which an incoming or outgoing ISDN call may be idle (i.e. the connection is up, but no data is sent) before it is terminated, in case another application needs an ISDN connection but when all B-channels are in use.

telindus1423Router/profiles/dial/defaultIsdn/callInterval

Use this attribute to set the …

• minimum time between two consecutive outgoing ISDN calls.• callback time-out. This is the time-out period in which the device that calls back must have done so

in order for a callback to be accepted. Callback attempts that fall out of this period are no longer accepted. Refer to 6.8 - How to configure callback? on page 206.

telindus1423Router/profiles/dial/defaultIsdn/callTimeOut

Use this attribute to set the time after which the Telindus 1423 SHDSL Router should cancel the connection attempt. Note that the connection is considered as up only if the PPP negotiation was successful.




00000d 01h 00m 00s


00000d 01h 00m 00s


00000d 01h 00m 00s


00000d 01h 00m 00s



91

telindus1423Router/profiles/dial/defaultIsdn/24hMaxCallTime

Use this attribute to determine how long (an) outgoing ISDN call(s) may last in a 24 hour time span, starting from midnight. In other words, this attribute defines the total “up” time per day of the sum of all connections initiated by the dial map that refers to this profile. If the maximum time is exceeded then the call is terminated.

E.g. suppose you have a dial profile in which you set the 24hMaxCallTime to 3 hours and you have a dial map that refers to this profile and, furthermore, this dial map causes 2 connections to be set up. Then in a time span of 24 hours (starting from midnight) the total time call for the 2 connections set up by the dial map can be maximum 3 hours (e.g. 1,5 hour per connection, or 2 hours for one connection and 1 hour for the other connection, etc.).

telindus1423Router/profiles/dial/defaultIsdn/dialTimeTable

Use this attribute to determine when exactly ISDN calls are allowed. In other words, this attribute allows you to control the up-time of your outgoing ISDN call.

The dialTimeTable contains the following elements:

Element Description

start Use this attribute to set the beginning of the period during which outgoing ISDN calls are allowed.

The start structure contains the following elements:

• month. Use this element to set the month. Possible values are: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

• dayOfMonth. Use this element to set the day of the month.Either set a dayOfMonth or dayOfWeek, not both.

• dayOfWeek. Use this element to set the day of the week. Possible values are: monday, tuesday, wednes-day, thursday, friday, saturday, sunday.Either set a dayOfMonth or dayOfWeek, not both.

• hour. Use this element to set the hour.

• minute. Use this element to set the minute.

end Use this attribute to set the end of the period during which outgoing ISDN calls are allowed.

The end structure contains the same elements as the start structure. See above.


00001d 00h 00m 00s


Default:<opt>Range: enumerated, see below



Default:<opt>Range: 0 … 23Default:<opt>Range: 0 … 59



92

Remarks

• Leaving an element at its <opt> (optional) value means it is not considered (wild card).• The ranges that you define are “inclusive”. This means that if you define a range from e.g. start hour

= 7 up to end hour = 19, you actually end at 19 hours and 59 minutes.• It is possible that you make invalid entries in the dialTimeTable. An invalid entry could be:

- You define a start value, but no end value or vice versa.- The start value is bigger than the end value.- Both dayOfMonth and dayOfWeek are filled in (you can only set one of both).

• If you made an invalid entry, an error message appears in the message table (refer to telindus1423Router/messages on page 260). Moreover, the invalid entry is ignored.

Example

You could specify that outgoing ISDN calls are only allowed on working days, during office hours. In that case, the dialTimeTable looks as follows:



93

telindus1423Router/profiles/dial/defaultIsdn/maxChannelsUsed

Use this attribute to determine the maximum amount of B-channels that may be used by an ISDN call. This to avoid that the dial map entries that refer to this ISDN profile use all available B-channels.

If you set the maxChannelsUsed attribute to …

• 0, then no B-channels may be used.• 1 or 2, then maximum 1 or 2 B-channels may be used.• 3 or 4, then maximum 3 or 4 B-channels may be used. Since there are only 2 B-channels per BRI

interface, using 3 or 4 B-channels is only possible if you entered both BRI interfaces in the configu-ration attribute telindus1423Router/profiles/dial/defaultIsdn/isdnInterfaces on page 90.

• <opt> (optional), then the attribute is ignored. In this case, all available B-channels may be used (i.e. 2 B-channels in case you use 1 BRI interface, 4 B-channels in case you use 2 BRI interfaces).

telindus1423Router/profiles/dial/defaultIsdn/minChannelsFree

Use this attribute to determine the minimum amount of B-channels that has to be kept free. This to keep channels free for e.g. incoming ISDN calls.

If you set the minChannelsFree attribute to …

• 0, then no B-channels are kept free. In this case, all available B-channels may be used (i.e. 2 B-chan-nels in case you use 1 BRI interface, 4 B-channels in case you use 2 BRI interfaces).

• 1, 2 or 3, then minimum 1, 2 or 3 B-channels are kept free.• 4, then all B-channels are kept free.• <opt> (optional), then the attribute is ignored. In this case, no B-channels are kept free. This means

all available B-channels may be used (i.e. 2 B-channels in case you use 1 BRI interface, 4 B-channels in case you use 2 BRI interfaces).

As opposed to the maxChannelsUsed attribute, the minChannelsFree attribute is actually profile independent. As soon as one profile specifies that e.g. 2 channels should be kept free, then 2 channels are kept free even if another profile specifies that only 1 channel should be kept free.





94

MR-1.9.2 Encapsulation profile configuration attributes


• telindus1423Router/profiles/encapsulation/defaultPpp/linkMonitoring on page 95• telindus1423Router/profiles/encapsulation/defaultPpp/authentication on page 95• telindus1423Router/profiles/encapsulation/defaultPpp/authenPeriod on page 95• telindus1423Router/profiles/encapsulation/defaultPpp/compression on page 95• telindus1423Router/profiles/encapsulation/defaultPpp/connection on page 95• telindus1423Router/profiles/encapsulation/defaultPpp/multiLink on page 96• telindus1423Router/profiles/encapsulation/defaultPpp/callback on page 97



95

telindus1423Router/profiles/encapsulation/defaultPpp/linkMonitoring

Use this attribute to enable or disable link monitoring and to fine-tune it.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/linkMonitoring on page 59 for more information.

telindus1423Router/profiles/encapsulation/defaultPpp/authentication

Use this attribute to enable or disable authentication on the PPP link.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/authentication on page 60 for more information.

telindus1423Router/profiles/encapsulation/defaultPpp/authenPeriod

Use this attribute to set the PPP authentication interval.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/authenPeriod on page 60 for more information.

telindus1423Router/profiles/encapsulation/defaultPpp/compression

Use this attribute to enable or disable the compression of PPP encapsu-lated packets.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/compression on page 58 for more information.

telindus1423Router/profiles/encapsulation/defaultPpp/connection

Use this attribute to determine whether you want set up a single link or multi-link PPP connection.

Refer to MU-7.4.14 - Configuration de MLPPP sur une interface BRI en mode de numérotation on page 186 for more information.

The connection attribute has the following values:

Value Description

singleLink One PPP link only uses one B-channel.

multiLink One PPP link uses several B-channels. I.e. different B-channels are bundled to create one PPP link. In this way you can bundle up to 4 B-channels.




24855d 03h 14m 07s

Default:disabledRange: disabled / predictor1

Default:multiLinkRange: enumerated, see below



96

telindus1423Router/profiles/encapsulation/defaultPpp/multiLink

If you set the telindus1423Router/profiles/encapsulation/defaultPpp/connection attribute to multiLink, then use the multiLink attribute to configure the channel usage of the multi-link PPP connection.

The multiLink structure the following elements:

telindus1423Router/profiles/encapsulation/defaultPpp/multiLink/bap

Use the bap structure in the multiLink structure to enable, disable and fine-tune the Bandwidth Allocation Protocol (BAP). Refer to Qu'est-ce que le BAP ? on page 164.

The bap structure contains the following elements:

Element Description

initialChannels Use this element to set the number of B-channels you would like the multi-link PPP connection to contain ini-tially.

For example, if you set the initialChannels element to e.g. 2 and e.g. 4 B-channels are available, then the Telindus 1423 SHDSL Router only activates 2 channels.

Another example, if you set the initialChannels element to e.g. 2 and 2 B-channels are available, then the Telindus 1423 SHDSL Router activates these 2 channels. Suppose that after that 1 channel drops, then the Telindus 1423 SHDSL Router continuous to operate on this 1 channel. However, if the channel comes up again, then the Telindus 1423 SHDSL Router will not reactivate the channel (at least, not if BAP is disabled).

bap Use this element to enable, disable and fine-tune the Bandwidth Allocation Protocol (BAP).

Refer to telindus1423Router/profiles/encapsulation/defaultPpp/multiLink/bap on page 96 for a detailed description of the elements in the bap structure.

Element Description

operation Use this element to enable or disable BAP.

maxChannels Use this element to set the maximum number of B-channels the multi-link PPP connection may contain.

removeTimeout Use this element to set the period, in seconds, over which the load of the multi-link PPP connection is cal-culated and which determines, together with the removeThresholdIn and removeThresholdOut attributes, when a channel is removed from the multi-link PPP connection.

addTimeout Use this element to set the period, in seconds, over which the load of the multi-link PPP connection is cal-culated and which determines, together with the addThresholdIn and addThresholdOut attributes, when a channel is added to the multi-link PPP connection.











97

telindus1423Router/profiles/encapsulation/defaultPpp/callback

Use this attribute to enable or disable callback. Refer to 6.8 - How to config-ure callback? on page 206 for more information.

The callback structure contains the following elements:

removeThresholdIn Use this element to determine the load, in percents, that has to be reached over the removeTimeout period before a channel is removed from the multi-link PPP connection in the receive direction.

removeThreshold-Out

Use this element to determine the load, in percents, that has to be reached over the removeTimeout period before a channel is removed from the multi-link PPP connection in the transmit direction.

addThresholdIn Use this element to determine the load, in percents, that has to be reached over the addTimeout period before a channel is added to the multi-link PPP con-nection in the receive direction.

addThresholdOut Use this element to determine the load, in percents, that has to be reached over the addTimeout period before a channel is added to the multi-link PPP con-nection in the transmit direction.

callBackRequests Use this element to allow (accept) or deny (reject) that the remote side triggers the adding of channels to the multi-link PPP connection at the local side.

Element Description

type Use this element to enable or disable callback.


• disabled. No callback is done.• authentication. The callback is based on PPP authentication. Refer to What is

authentication callback? on page 207.• e164Number. The callback number is communicated during the callback negoti-

ation. Refer to What is E.164 number callback? on page 208.

Element Description





Default:rejectRange: reject / accept





98

MR-1.9.3 Forwarding profile configuration attributes

On the ISDN interfaces, only a routing forwarding profile can be set up. This means that the ISDN inter-faces can only operate in routing mode, not in bridging mode. The reason for not supporting bridging mode is that the risk is too high that the ISDN connections stay up permanently due to broadcasts and multicasts.


• telindus1423Router/profiles/forwardingMode/defaultRouting/ip on page 99• telindus1423Router/profiles/forwardingMode/defaultRouting/priorityPolicy on page 99• telindus1423Router/profiles/forwardingMode/defaultRouting/maxFifoQLen on page 99



99

telindus1423Router/profiles/forwardingMode/defaultRouting/ip

Use this attribute to configure the IP related parameters of the PPP links that can be set up on the BRI interfaces.

Refer to …



telindus1423Router/profiles/forwardingMode/defaultRouting/priorityPolicy

Use this attribute to apply a priority policy on the interface.


telindus1423Router/profiles/forwardingMode/defaultRouting/maxFifoQLen








100

MR-1.9.4 IP traffic policy configuration attributes


• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method on page 101• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/trafficShaping on page 103• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/dropLevels on page 106• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/tos2QueueMapping on page 108

This object is not present in the containment tree by default. If you want to use the feature associated with this object, then add the object first. Refer to MU-4.4 - Ajout d'un objet dans l'arborescence on page 50.



101

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method

Use this attribute to choose an IP traffic policy method. This IP traffic policy is then used to …

• determine, on traffic overload conditions, how and which queues are filled with the “excess” data. Refer to MU-8.8 - Configuration de la politique de trafic et de priorité sur le routeur on page 249.

• do policy based routing. Refer to MU-8.4 - Configuration d'acheminement en fonction de la politique on page 204.

• filter data on an interface. Refer to MU-10.2 - Configuration des restrictions d'accès on page 312.

The method attribute has the following values:

Value Description

trafficShaping The data is …

• redirected to the queues based on the settings of the trafficShaping attribute (queueing).

• redirected to an interface or a gateway based on the settings of the trafficShaping attribute (policy based routing).

• filtered based on the settings of the trafficShaping attribute (extended access list).

Refer to telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/trafficShaping on page 103 for more information on traffic shaping.

tosDiffServ The data is redirected to the queues based on DiffServ (refer to RFC 2597) regard-ing class and drop precedence. Refer to Qu'est-ce que AF PHB ? on page 252.

This means that, depending on their DSCP field in the TOS byte, some packets are moved to other queues and/or dropped sooner than other packets in case the queue is full.

The highest 3 bits of the DSCP field are mapped as follows:

The next 2 bits of the DSCP field define the drop levels:

Refer to the attribute telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/dropLevels on page 106 for more information on drop levels.

Default:trafficShapingRange: enumerated, see below

Bit values … are mapped to …

000 up to 100 queues 1 up to 5, respectively.

101 and higher the low delay queue.

Bit values … correspond with …

00 and 01 dropLevel1

10 dropLevel2

11 dropLevel3



102

tosMapped The data is redirected to …

• the queues based on the settings of the tos2QueueMapping attribute (queueing).• an interface or a gateway based on the settings of the tos2QueueMapping attribute

(policy based routing).

Refer to the attribute telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/tos2QueueMapping on page 108 for more information on TOS to queue mapping.

Value Description



103

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/trafficShaping

The function of this attribute is threefold:

• Traffic and priority policingIn case you have set the telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method attribute to trafficShap-ing, then use the trafficShaping table to specify which data has to be redirected to which queue. If an overload condition occurs, then a packet is redirected to the specified queue when the criteria as specified in the trafficShaping table are met.Refer to MU-8.8 - Configuration de la politique de trafic et de priorité sur le routeur on page 249.

• Policy based routingIn case you have set the telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method attribute to trafficShap-ing, then use the trafficShaping table to specify which data has to be redirected to which interface or gateway. Packets are redirected to the specified interface or gateway when the criteria as specified in the trafficShaping table are met.Refer to MU-8.4 - Configuration d'acheminement en fonction de la politique on page 204.

• Extended access listIn case you have set the telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method attribute to trafficShap-ing, then use the trafficShaping table to specify which data is forwarded. Packets are forwarded when the criteria as specified in the trafficShaping table are met. If more than one entry applies to the same packet, then the entry which has the narrowest filter range (when looking at the filter criteria from left to right) is chosen.Refer to MU-10.2 - Configuration des restrictions d'accès on page 312.

Important remarks

• By default, the entries in the trafficShaping table are “allow” rules. I.e. only the traffic defined in the table is permitted, all other traffic is discarded (independent whether the traffic shaping table is used as an access list, for priority policing or policy based routing). However, you can inverse an entry making it a “deny” rule by entering “discard” as value of the interface element.

• If more than one entry applies to the same packet, then the entry which has the narrowest filter range (when looking at the filter criteria from left to right) is chosen. For example: two rows in the trafficShaping table apply to the same packet, but row 1 wants to forward packets to queue 3 and row 2 wants to forward packets to the low delay queue. In that case, first the IP source address is considered. The row with the smallest range wins. If the ranges are exactly the same, then the IP destination address is considered. And so on. Should the two rows be completely identical except for the queue, then one of the rows is chosen at random.

• You do not necessarily have to fill in IP addresses in the trafficShaping table. It is perfectly valid to filter on IP protocol, IP protocol/port combination or TOS values only. However, you can not filter on port numbers only. What is more, you can only filter on port numbers when the IP protocol is set to TCP or UDP. So in other words, if the IP protocol element is set to a value different from TCP or UDP, then all the port elements are ignored.




104

The trafficShaping table contains the following elements:

Element Description

sourceIpStart-Address

Use these elements to set the IP source address as specified in the IP header.

Packets that fall within the specified range are forwarded and queued if applicable.sourceIpEnd-Address

destinationIpStart-Address

Use these elements to set the IP destination address as specified in the IP header.

Packets that fall within the specified range are forwarded and queued if applicable.destinationIpEnd-Address

tosStartValue Use these elements to set the TOS byte value.

Packets that fall within the specified range are for-warded and queued if applicable.

tosEndValue

ipProtocol Use this element to set the protocol field from the IP header.

Packets that have the specified protocol field are forwarded and queued if applica-ble.

You can specify the protocol by typing the protocol number. For ease of use, some common protocols can be selected from a drop-down box: any (0), ICMP (1), IGMP (2), IPinIP (4), TCP (6), EGP (8), IGP (9), UDP (17), RSVP (46), IGRP (88), OSPFIGP (89), TCPestablished (255).

sourcePortStart Use these elements to set the source port as specified in the UDP / TCP headers.

Packets that fall within the specified range are forwarded and queued if applicable.

You can specify the port by typing the protocol number. For ease of use, some common port numbers can be selected from a drop-down box: any or optional (0), echo (7), discard (9), ftp-data (20), ftp (21), telnet (23), smtp (25), domain (53), www-http (80), pop3 (110), nntp (119), snmp (161), snmptrap (162), z39.50 (210), syslog (514), router (520), socks (1080), I2tp (1701), telindus (1728).

Note that the predefined “echo” value is a UDP port. It has nothing to do with ICMP echo.

sourcePortEnd

destinationPortStart Use these elements to set the destination port as specified in the UDP / TCP headers.

Packets that fall within the specified range are forwarded and queued if applicable.

You can specify the port by typing the protocol number. For ease of use, some common port numbers can be selected from a drop-down box: see above.

destinationPortEnd

newTosValue Use this element to set the new TOS byte value.

When you select a new TOS byte value, then a packet that matches an entry in the trafficShaping table its TOS byte value is changed. Selecting unchanged, leaves the TOS byte value as it is.

Default:0.0.0.0Range: up to 255.255.255.255


Default:any(start)/optional(end)Range: 0 … 256

Default:anyRange: 0 … 255



Default:unchangedRange: 0 … 256



105

Start and end values

Except for the ipProtocol, newTosValue and priority elements, it is possible to specify ranges using the start and end values. There are two special cases:

• A start value is entered, but no end value ⇒ an exact match is needed for the start value.• Neither a start nor an end value is entered ⇒ the field is not checked.

priority Use this element to set the destination queue for a packet matching an entry in the trafficShaping table.

In case an overload condition occurs, then a packet that matches an entry in the trafficShaping table is sent to the specified queue.

The priority element has the following values: queue1, queue2, queue3, queue4, queue5, lowDelayQueue.

interface Use this element to set the destination interface for a packet matching an entry in the trafficShaping table. This is policy based routing.

Type the name of the interface in the interface element, e.g. lan.

Note that by default, the entries in the trafficShaping table are “allow” rules. I.e. only the traffic defined in the table is permitted, all other traffic is discarded (independ-ent whether the traffic shaping table is used as an access list, for priority policing or policy based routing). However, you can inverse an entry making it a “deny” rule by entering “discard” as value of the interface element.

gateway Use this element to set the gateway for a packet matching an entry in the trafficShaping table. This is pol-icy based routing.

Element Description



Default:<opt>Range: up to 255.255.255.255



106

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/dropLevels

Use this attribute to define for each user configurable queue, how many packets may be queued before they are dropped.

The dropLevels table contains the following elements:

Examples

Suppose …

• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method is set to trafficShaping or tosMapped.• for queue 1 you set maxLength1 = 1000, for queue 2 to 500, for queue 3 to 3000, for queue 4 to 1000

and for queue 5 to 200.

In this case, packets are dropped when the amount of packets in the queue exceeds the amount as specified with the maxLength1 element.

Element Description

dropLevel1 Use this element to set the maximum length (drop level 1), in packets, of each user configurable queue.

In case you set the attribute telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method to …

• trafficShaping or tosMapped, then only this drop level is relevant.• tosDiffServ, then this drop level corresponds with the drop level bits value 00 and

01.



• trafficShaping or tosMapped, then this drop level is not relevant.• tosDiffServ, then this drop level corresponds with the drop level bits value 10.



• trafficShaping or tosMapped, then this drop level is not relevant.• tosDiffServ, then this drop level corresponds with the drop level bits value 11.




Default:100Range: 1 … 3000Default:100Range: 1 … 3000



107

Suppose …

• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method is set to tosDiffServ.• for queue 1 you set maxLength1 = 100, maxLength2 = 200 and maxLength3 = 50.

In this case, the following applies:

Queue 1 contains … data packets.

An incoming data packet with … is …

drop level1 1

1. As defined in the TOS byte.

drop level 2 drop level 3

less than 50 accepted accepted accepted

more than 50, less than 100 accepted accepted dropped

more than 100, less than 200 dropped accepted dropped

more than 200 dropped dropped dropped



108

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/tos2QueueMapping

• Traffic and priority policingIn case you have set the telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method attribute to tosMapped, then use the tos2QueueMapping table to specify which data has to be redirected to which queue. If an overload condition occurs, then a packet is redirected to the specified queue when the criteria as specified in the tos2QueueMapping table are met.Refer to MU-8.8 - Configuration de la politique de trafic et de priorité sur le routeur on page 249 and MU-9.3.2 - Configuration d'une politique de trafic sur le pont on page 302.

• Policy based routingIn case you have set the telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/method attribute to tosMapped, then use the tos2QueueMapping table to specify which data has to be redirected to which interface or gateway. Packets are redirected to the specified interface or gateway when the criteria as specified in the tos2QueueMapping table are met.Refer to MU-8.4 - Configuration d'acheminement en fonction de la politique on page 204.

The tos2QueueMapping table contains the following elements:

Element Description

startTos Use these elements to set the TOS byte value.

Packets that have a TOS byte value within the speci-fied range are redirected to the targetQueue.

endTos

targetQueue Use this element to set the destination queue.

The targetQueue element has the following values: Queue1, Queue2, Queue3, Queue4, Queue5, lowDelayQueue.

interface Use this element to set the destination interface for a packet matching an entry in the tos2QueueMapping table. This is policy based routing.

Type the name of the interface in the interface element, e.g. lan.

gateway Use this element to set the gateway for a packet matching an entry in the tos2QueueMapping table. This is policy based routing.


Default:0 (start) / 255 (end)Range: 0 … 255

Default:Queue1Range: enumerated, see below





109

MR-1.9.5 Bridging traffic policy configuration attributes


• telindus1423Router/profiles/policy/traffic/bridgingTrafficPolicy[ ]/vlanPriorityMap on page 110• telindus1423Router/profiles/policy/traffic/bridgingTrafficPolicy[ ]/dropLevels on page 110




110

telindus1423Router/profiles/policy/traffic/bridgingTrafficPolicy[ ]/vlanPriorityMap

Use this attribute to impose a bridging traffic policy on the bridged VLAN frames received by the Telindus 1423 SHDSL Router.

Each VLAN frame has a certain priority (this is specified in the 802.1P part of the 802.1Q header of the VLAN frame). In case a traffic overload condition occurs and in case you imposed this traffic policy on a certain interface, then the VLAN frames are sent to a queue. Using the vlanPriorityMap attribute, you can specify which VLAN frame is sent to which queue based on the priority of the VLAN frame.

The vlanPriorityMap structure contains the following elements:

telindus1423Router/profiles/policy/traffic/bridgingTrafficPolicy[ ]/dropLevels

Use this attribute to define for each user configurable queue, how many packets may be queued before they are dropped.

The dropLevels table contains the following element:

Element Description

priority0…

priority7

Use these elements to define which priority corresponds with which queue. The possible queues are: queue1 up to queue5 and lowDelayQueue. To empty these queues, specify a priority policy.

Frames that are not tagged are all considered to have priority 0.$

Refer to MU-9.3.2 - Configuration d'une politique de trafic sur le pont on page 302 for more information on traffic policy, priority policy and priority queuing.

Element Description

dropLevel1 Use this element to set the maximum length, in pack-ets, of each user configurable queue.






111

MR-1.9.6 Priority policy configuration attributes


• telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/algorithm on page 112• telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/countingPolicy on page 114• telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/queueConfigurations on page 114• telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/lowdelayQuotum on page 114• telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/bandwidth on page 115




112

telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/algorithm

Use this attribute to determine how and which queues are emptied.

The algorithm attribute has the following values:

Value Description

fifo This is a First In First Out queue. The data that enters the queue first, also leaves the queue first. This is the fastest but most superficial queuing mechanism.

You can change the maximum length of the FIFO queue on an interface using the configuration attribute maxFifoQLen.

roundRobin This is a priority queuing mechanism. In this case, all user configurable queues containing data have an equal weight. In other words, if all the user configurable queues contain data, they are addressed in turns. The low delay has a higher pri-ority, it is addressed between every user configurable queue. The system queue has absolute priority, it is emptied as soon as it contains data.

• Queues 1 up to 5: user configurable queues. These queues are addressed in turns.

• Queue 6: low delay queue. This queue is addressed between every user con-figurable queue.

• Queue 7: system queue. This queue has absolute priority over all other queues. As soon as it contains data, it is emptied.

absolutePriority This is a priority queuing mechanism. In this case, queues with a high priority have absolute priority over queues with a low priority. In other words, no lower priority queue is emptied as long as a higher priority queue contains data.

The priority of the queues runs parallel to the queue number. I.e. the user config-urable queue number 1 has the lowest priority, whereas the system queue (number 7) has the highest priority.

• Queues 1 up to 5: user configurable queues. Queue 1 has the lowest priority whereas queue 5 has the highest priority. A lower priority queue is only emptied in case no higher priority queue contains data.

• Queue 6: low delay queue. This queue is only emptied in case the system queue contains no data.


Note that there is a risk of starvation. This means that it is possible that the lower priority queues are never emptied because a higher priority queue continuously receives data.

Default:fifoRange: enumerated, see below



113

weightedFair-Queueing

This is a priority queuing mechanism. In this case, the user configurable queues are addressed based on their weight. The low delay has a higher priority, it is addressed between every user configurable queue. The system queue has abso-lute priority, it is emptied as soon as it contains data.

• Queues 1 up to 5: user configurable queues. These queues are addressed based on their weight. The weight can be configured in the telindus1423Router/pro-files/policy/priority/priorityPolicy[ ]/queueConfigurations attribute.

• Queue 6: low delay queue. This queue is addressed between every user con-figurable queue.


lowDelayWeighted-FairQueueing

This is a priority queuing mechanism. It is a combination of absolute priority and weighted fair queueing. In this case, the user configurable queues are addressed based on their weight. The low delay queue has absolute priority over all user con-figurable queues and the system queue has absolute priority over all queues.

• Queues 1 up to 5: user configurable queues. These queues are addressed based on their weight. The weight can be configured in the telindus1423Router/pro-files/policy/priority/priorityPolicy[ ]/queueConfigurations attribute.

• Queue 6: low delay queue. This queue has absolute priority over all user con-figurable queues. If the system queue does not contain data but the low delay queue and the user configurable queues do, then it is the low delay queue that is emptied.


In a network that carries both voice and data, the lowDelayWeightedFairQueueing algorithm is the most suited mechanism to get the voice over the network with a minimum delay. In this case, the voice has to be queued in the low

delay queue.

Value Description



114

telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/countingPolicy

Use this attribute to define whether the quotum of the queues is expressed in bytes or packets.

telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/queueConfigurations

Use this attribute to …

• set the number of bytes/packets that is dequeued from the user configurable queue when the queue is addressed.

• set the relative importance of the user configurable queues.

The queueConfigurations table contains the following elements:

Refer to MU-8.8.1 - Présentation de la politique de trafic et de priorité on page 250 for more information on queues.

telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/lowdelayQuotum

Use this attribute to set the number of bytes/packets that is dequeued from the low delay queue when the queue is addressed. The unit of the quotum (bytes or packets) can be set with the telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/countingPolicy attribute.


Element Description

quotum Use this element to set the number of bytes/packets that is dequeued from the user configurable queue when the queue is addressed.

The unit of the quotum (bytes or packets) can be set with the telindus1423Router/pro-files/policy/priority/priorityPolicy[ ]/countingPolicy attribute.

weight Use this element to set the relative importance of the user configurable queues.

The weight element is only relevant in case the telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/algorithm attribute is set to weightedFairQueueing.

Example

Suppose queue 1 has weight 2, queue 2 has weight 1 and both queues contain data. In that case the queues are emptied in the following order: queue 1 → queue 1 → queue 2 → queue 1 → queue 1 → queue 2 → etc.

Default:bytesRange: enumerated, see below







115

telindus1423Router/profiles/policy/priority/priorityPolicy[ ]/bandwidth

Use this attribute to set the bandwidth per queue.

The bandwidth table contains the following elements:


Element Description

cir Use this element to set the Committed Information Rate (CIR), in bits per second, of the different queues.

Using entry 1 up to 5 in the bandwidth table you can set the CIR for queues 1 up to 5, respectively. Using entry 6 in the bandwidth table you can set the CIR for the low delay queue.

If the CIR is exceeded, then the data is first queued. The amount of data that is queued can be set using the maxFifoQLen attribute. If the queue is completely filled up, then the data is discarded.





116

MR-1.10 Dial maps configuration attributes

If you want to establish an ISDN dial-up connection, then you first have to set up dial, encapsulation and forwarding profiles. Then you have to configure the dial map in which you combine the different profiles. Refer to MU-6 - Configuration des connexions ISDN on page 95 for more information.


• telindus1423Router/dialMaps/mapping on page 117



117

telindus1423Router/dialMaps/mapping

Use this attribute to configure dial maps. This means that you can create entries in this table (called dial maps) which actually make up an ISDN dial-up connection.

Refer to MU-6 - Configuration des connexions ISDN on page 95 for an elaborate explanation on setting up ISDN dial-up connections using profiles and dial maps.

The mapping table contains the following elements:

Element Description

name Use this element to specify a name for the dial map. This name has to be used in the routing table in order to point to a specific dial map.

Refer to 6.3.3 - How to create a route that points to a dial map? on page 200 for more information.

localTelNrs Use this element to enter the local telephone number. This is the telephone number a remote ISDN device has to use to dial in.

The localTelNrs table contains the following elements:

• telNr. Use this element to enter the telephone number.

• uniqueDigits. Use this element to set the number of unique digits. Refer to What are unique digits?.Setting the uniqueDigits to 0 means that the com-plete telephone number as entered in the telNr element should be considered as unique digits.

It is not mandatory to fill in the localTelNrs table. If you leave the localTelNrs table empty, then all incoming calls are accepted. However, if you do specify a tele-phone number in the localTelNrs table, then only the calls to this specific telephone number are accepted.


Default:mapRange: 1 … 24 characters






118

remoteTelNrs Use this element to enter the remote telephone number(s).

The remoteTelNrs table contains the following elements:

• telNr. Use this element to enter the telephone number.

• uniqueDigits. Use this element to set the number of unique digits. Refer to What are unique digits?.Setting the uniqueDigits to 0 means that the com-plete telephone number as entered in the telNr element should be considered as unique digits.

In case of an …

• outgoing call, these numbers are used to dial out.• incoming call, these numbers are used to authenticate the remote caller.

Since the remoteTelNrs element is a table, you can enter several remote telephone numbers. In case of an …

• outgoing call, the first number in the list is taken to dial out. If for this number the call set-up fails (due to network problems, e.g. busy, dial time-out, etc.), then the next telephone number in the list is tried.

• incoming call, if the telephone number of the remote caller is present some-where in the list, then the call is accepted.

Element Description






119

What are unique digits?

The unique digits are, as the word says, that part of the telephone number that is truly “unique”.

Once a call reaches the ISDN network itself, things such as access codes and country access codes have no significance anymore and hence are discarded. However, should you use the telephone number for verification purposes, then you have to specify which part of the number you entered should be used. Typically, the part after the access code is considered to be the unique number.

For example: telephone number 00 32 16 124578, where 00 is the access code, 32 is the country code, 16 is the regional code and 124578 is the actual telephone number. Typically, the 00 and 32 are dropped once the call reaches the ISDN network. If you want that only the numbers 16 124578 are considered as unique digits, then enter 8 as value for the uniqueDigits element.

callDirection Use this element to determine whether a call can be an incoming, outgoing or an incoming + outgoing call.

sessionName Use this attribute to set the PPP authentication name of the remote router.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionName on page 61 for more information.

sessionSecret Use this element to set the PPP authentication secret of the remote router.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/sessionSecret on page 61 for more information.

Element Description

00 32 16 124578

8 unique digits

Default:incalls+outcallsRange: enumerated, see below





120

dial Use this element to determine which dial profile you want to use for this dial map.

The dial element value consists of two parts:

• Use the first part of the dial element value to select the dial profile type: isdn.• Use the second part of the dial element value to select the actual profile. If you

want to use …- the default profile, then enter, in the second field of the dial

element value, the string “default”.- a custom profile, then enter, in the second field of the dial ele-

ment value, the index name of the custom profile you want to use. You can create the profile itself by adding an isdn[ ] object under the profiles/dial object and by configuring the attributes in this object.

Example

If you created an isdn object with index name my_isdn (i.e. isdn[my_isdn]) and you want to apply this profile here, then enter the index name as value for the dial element.

Refer to 6.3.1 - How to create a profile? on page 196 for more information on cre-ating profiles.

encapsulation Use this element to determine which encapsulation profile you want to use for this dial map.

Do this in the same way as for the dial element.

forwardingMode Use this element to determine which forwarding pro-file you want to use for this dial map.

Do this in the same way as for the dial element.

Element Description

Default:<isdn> defaultRange: isdn

Default:<ppp> defaultRange: choice, see below

Default:<routing> defaultRange: choice, see below



121

MR-1.11 Bundle configuration attributes

This section describes the configuration attributes of the different bundles that you can set up on the Tel-indus 1423 SHDSL Router.


• MR-1.11.1 - PPP bundle configuration attributes on page 122



122

MR-1.11.1 PPP bundle configuration attributes


• telindus1423Router/bundle/pppBundle[ ]/members on page 123• telindus1423Router/bundle/pppBundle[ ]/mode on page 123• telindus1423Router/bundle/pppBundle[ ]/ip on page 123• telindus1423Router/bundle/pppBundle[ ]/bridging on page 123• telindus1423Router/bundle/pppBundle[ ]/fragmentation on page 124• telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces on page 124• telindus1423Router/bundle/pppBundle[ ]/<alarmConfigurationAttributes> on page 125




123

telindus1423Router/bundle/pppBundle[ ]/members

Use this attribute to make the WAN interface a part of the PPP bundle. Do this by adding one entry to the members table and by typing “wan” as value of the interface element.

Note that in case you run PPP over ATM (PPPoA) you can also create PPP bundles. In that case, just type the name of the ATM PVC as value of the interface element in the members table.

Refer to MU-7.4.11 - Configuration PPP multiliaisons on page 179 for more information on how to set up a PPP bundle.

telindus1423Router/bundle/pppBundle[ ]/mode



telindus1423Router/bundle/pppBundle[ ]/ip

Use this attribute to configure the IP related parameters of the PPP bundle.

Refer to …



telindus1423Router/bundle/pppBundle[ ]/bridging

Use this attribute to configure the bridging related parameters of the PPP bundle.

Refer to …


structure.

Value Description

bridging All packets received on the PPP bundle are bridged. BCP is set up.

routing All packets received on the PPP bundle are routed. IPCP is set up.

routingAndBridging The SNAP header is checked to determine whether the packets have to be bridged or routed. IPCP and BCP are set up.







124

telindus1423Router/bundle/pppBundle[ ]/fragmentation

Use this attribute to enable or disable PPP fragmentation. Refer to Qu'est-ce que la fragmentation PPP ? on page 164.

When PPP fragmentation is enabled, long frames are fragmented into a sequence of shorter frames. At the remote side they are reassembled into the original frame.

telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces

Use this attribute to set up multiclass PPP links. So you have to add an entry to the multiclassInterfaces table for every multiclass PPP link that you want to create.

Refer to MU-7.4.13 - Configuration PPP multiclasses on page 183 for more information.

The multiclassInterfaces table contains the following elements:

Element Description

name Use this element to assign an administrative name to the multiclass PPP link.

adminStatus Use this element to activate (up) or deactivate (down) the multiclass PPP link.

mode Use this element to determine whether, for the corre-sponding multiclass PPP link, the packets are treated by the routing process, the bridging process or both.


• bridging. All packets received on the multiclass PPP link are bridged.• routing. All packets received on the multiclass PPP link are routed.• routingAndBridging. The SNAP header is checked to determine whether the pack-


ip Use this element to configure the IP related parame-ters of the multiclass PPP link.

Refer to …



bridging Use this element to configure the bridging related parameters of the multiclass PPP link in case the mul-ticlass PPP link is in bridging mode (i.e. in case the mode element is set to bridging).

Refer to …












125

telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces/multiclass

Use this structure to configure the multiclass specific parameters of the mul-ticlass PPP link.

The multiclass structure contains the following elements:

telindus1423Router/bundle/pppBundle[ ]/<alarmConfigurationAttributes>


• the alarm configuration attributes alarmMask, alarmLevel, alarmContactHighMask and alarmContactLowMask and on the alarms in general, refer to MR-4.2 - Introducing the alarm attributes on page 488.

• the alarms of the pppBundle[ ] object, refer to MR-4.12 - Bundle alarms on page 503.

multiclass Use this element to configure the multiclass specific parameters of the multiclass PPP link.

Refer to telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces/multiclass on page 125 for a detailed description of the multiclass structure.

Element Description

multiclass Use this element to set a multiclass identifier for the multiclass PPP link.

defaultQueue Use this element to select a default queue.

This allows you to easily set up a traffic policy without having to create and apply traffic policy profiles. However, you still have to create and apply a priority policy profile to empty the queues.

Refer to MU-8.8.9 - Attribut de la file par défaut ou profil de politique de trafic on page 265 for more information.

Element Description







126

MR-1.12 Router configuration attributes

This section discusses the configuration attributes concerned with routing. First it describes the general routing configuration attributes. Then it explains the configuration attributes of the extra features as there are NAT, L2TP tunnelling, filtering, traffic and priority policy, etc…


• MR-1.12.1 - General router configuration attributes on page 127• MR-1.12.2 - NAT configuration attributes on page 152• MR-1.12.3 - L2TP tunnel configuration attributes on page 156• MR-1.12.4 - Manual SA configuration attributes on page 166• MR-1.12.5 - IKE SA configuration attributes on page 170• MR-1.12.6 - OSPF configuration attributes on page 178• MR-1.12.7 - Routing filter configuration attributes on page 192• MR-1.12.8 - VRRP configuration attributes on page 194• MR-1.12.9 - Firewall configuration attributes on page 198



127

MR-1.12.1 General router configuration attributes


• telindus1423Router/ip/router/defaultRoute on page 128• telindus1423Router/ip/router/routingTable on page 129• telindus1423Router/ip/router/routingProtocol on page 130• telindus1423Router/ip/router/alternativeRoutes on page 130• telindus1423Router/ip/router/ripUpdateInterval on page 130• telindus1423Router/ip/router/ripHoldDownTime on page 131• telindus1423Router/ip/router/ripv2SecretTable on page 132• telindus1423Router/ip/router/sysSecret on page 133• telindus1423Router/ip/router/pppSecretTable on page 133• telindus1423Router/ip/router/helperProtocols on page 134• telindus1423Router/ip/router/sendTtlExceeded on page 135• telindus1423Router/ip/router/sendPortUnreachable on page 136• telindus1423Router/ip/router/sendAdminUnreachable on page 136• telindus1423Router/ip/router/dhcpStatic on page 137• telindus1423Router/ip/router/dhcpDynamic on page 139• telindus1423Router/ip/router/dhcpCheckAddress on page 141• telindus1423Router/ip/router/radius on page 142• telindus1423Router/ip/router/dns on page 144• telindus1423Router/ip/router/addrPools on page 145• telindus1423Router/ip/router/<alarmConfigurationAttributes> on page 151



128

telindus1423Router/ip/router/defaultRoute

Use this attribute to set the default route, also called gateway address.

Refer to MU-8.3 - Configuration de chemins statiques on page 195 for more information on static routes.

The defaultRoute structure contains the following elements:

Element Description

gateway Use this element to specify the IP address of the next router that will route all packets for which no specific (static or dynamic) route exists in the routing table.

Whether you can omit the gateway element or not, is linked to the following condi-tions:

interface Use this element to specify the interface through which the gateway can be reached.

Do this by typing the name of the interface as you assigned it using the configura-tion attribute name (e.g. telindus1423Router/lanInterface/name). Note that this interface can also be a DLCI, PVC, tunnel, etc.

If you do not specify a value for the interface element, then it is deduced by checking all interfaces (including DLCIs, PVCs and tunnels) and finding an interface for which the gateway lies in the subnet defined by the IP address and net mask of that interface.

Typing the string “discard”, discards all packets for the corresponding destination.

preference Use this element to set the level of importance of the default route with respect to routes learnt via RIP.

RIP routes always have a preference of 60. Routes with a lower preference value are chosen over routes with higher preference value.

metric Use this element to set with how much the metric parameter of a route has to be incremented.

If two routes exist with the same preference, then the route with the lowest metric value is chosen. This element is only important when combining static routes and RIP routes.

Refer to MU-8.5.3 - Explication de la structure rip on page 214 for more information on the metric parameter.



If the interface element specifies …

then …

the LAN interface, you can not omit the gateway element.

the WAN interface, you can omit the gateway element only when using PPP encapsulation.

a DLCI, PVC or tunnel, you can omit the gateway element.






129

telindus1423Router/ip/router/routingTable

Use this attribute to configure the static IP routes.

Refer to MU-8.3 - Configuration de chemins statiques on page 195 for more information on static routes.

The routingTable table contains the following elements:

Element Description

network Use this element to specify the IP address of the des-tination network.

mask Use this element to specify the network mask of the destination network.

gateway Use this element to specify the IP address of the next router on the path to the destination network.

Whether you can omit the gateway element or not, is linked to the following condi-tions:

interface Use this element to specify the interface through which the destination network can be reached.

Do this by typing the name of the interface as you assigned it using the configura-tion attribute name (e.g. telindus1423Router/lanInterface/name on page 21). Note that the “interface” can also be a DLCI, PVC, tunnel, etc.

If you do not specify a value for the interface element, then it is deduced by checking all interfaces (including DLCIs, PVCs and tunnels) and finding an interface for which the gateway lies in the subnet defined by the IP address and net mask of that interface.

Typing the string “discard”, discards all packets for the corresponding destination.

preference Use this element to set the level of importance of the route.

Routes with a lower preference value are chosen over routes with higher prefer-ence value. Note that routes learned through RIP always have a preference of 60.

metric Use this element to set with how much the metric parameter of a route has to be incremented.

If two routes exist with the same preference, then the route with the lowest metric value is chosen. Refer to MU-8.5.3 - Explication de la structure rip on page 214 for more information on the metric parameter.





If the interface element specifies …

then …

the LAN interface, you can not omit the gateway element.

the WAN interface, you can omit the gateway element only when using PPP encapsulation.

a DLCI, PVC or tunnel, you can omit the gateway element.






130

telindus1423Router/ip/router/routingProtocol

Use this attribute to activate or deactivate the Routing Information Protocol (RIP).

Refer to MU-8.5 - Configuration de RIP on page 209 for more information on RIP.

The routingProtocol attribute has the following values:

telindus1423Router/ip/router/alternativeRoutes

Use this attribute to determine how the Telindus 1423 SHDSL Router deals with identical routes.

If more than one route to a (sub-)network is defined in the routing table, and these routes have …

• identical destination addresses, masks, preferences and metrics,• a different gateway,

… then you can use the alternativeRoutes attribute to determine which route the Telindus 1423 SHDSL Router uses to reach the (sub-)network.

The alternativeRoutes attribute has the following values:

telindus1423Router/ip/router/ripUpdateInterval

Use this attribute to set the interval the Telindus 1423 SHDSL Router trans-mits RIP update messages.

Normally, RIP update messages are transmitted every 30 seconds. It is possible to change this interval. However, changing this interval will also change the lifetime of routes learnt through RIP. If a RIP route is received for the last time, it is declared down after 6 times the ripUpdateInterval. After the route is down, it is deleted after 4 times the ripUpdateInterval.

Value Description

none No routing protocol is used. Only static routes are used.

rip The RIP routing protocol is active. You can set the RIP version per interface. Refer to the elements txVersion and rxVersion in the rip structure (refer to MU-8.5.3 - Expli-cation de la structure rip on page 214).

Value Description

backup The Telindus 1423 SHDSL Router always uses the same route to reach the (sub-)network. Only when this route goes down, it uses the alternative route.

roundRobin The Telindus 1423 SHDSL Router alternately uses the two possible routes to reach the (sub-)network. However, once a certain route is used to reach a specific address, this same route is always used to reach this specific address.


Default:backupRange: enumerated, see below


00000d 00h 10m 00s



131

telindus1423Router/ip/router/ripHoldDownTime

Use this attribute to set the time during which routing information regarding better paths is suppressed.

It should be at least three times the value of the ripUpdateInterval attribute. A route enters into a hold-down state when an update packet is received that indicates the route is unreachable. The route is marked inaccessible and advertised as unreachable. However, the route is still used for forwarding packets. When hold-down expires, routes advertised by other sources are accepted and the route is no longer inaccessible.

What is the RIP hold-down time?

Suppose you have a situation as depicted in the figure alongside.

Now suppose the following happens:

1. Route X goes down.⇒Router A sends a RIP update message to router B

declaring route X down.

2. Only a few moments later, route X goes up for a while after which it goes down again. This continues for a certain time. In other words, the route status tog-gles between up and down.⇒Every time the status of route X changes, Router A sends a RIP update message to router B. Also

router B propagates these RIP update messages. In other words, the toggling of route X causes that a lot of RIP update messages are sent.

The ripHoldDownTime attribute tries to avoid situations as described above. Suppose router B has a ripHoldDownTime attribute. In that case, the situation is as follows:

1. Route X goes down.⇒Router A sends a RIP update message to router B declaring route X down. Router B starts the RIP

hold-down timer.

2. The status of route X starts toggling between up and down.⇒Router A sends several RIP update messages concerning route X to router B. Router B holds the

status of route X down, as longs as the RIP hold-down timer has not expired.

When the RIP hold-down timer expires and the route is …• down, then the route status stays down.• up, then the route status changes to up.


00000d 00h 10m 00s



132

telindus1423Router/ip/router/ripv2SecretTable

Use this attribute to define the secrets used for the RIP authentication.

Refer to MU-8.5.4 - Activation de l'authentification RIP sur une interface on page 218 for more informa-tion on RIP authentication.

The ripv2SecretTable table contains the following elements:

Remarks

• If authentication is enabled (either text or md5), then only updates using that authentication are proc-essed. All other updates on that interface are discarded.

• If you use md5 and if for a certain interface multiple secrets are present in the ripv2SecretTable, then the first entry in the ripv2SecretTable is used to transmit RIP updates. Authentication of the received RIP updates is done by looking for the first secret with a matching key.

• If you use text and if for a certain interface multiple secrets are present in the ripv2SecretTable, then only the first entry in the ripv2SecretTable is used to transmit and receive RIP updates.

Element Description

keyId Use this element to set a unique identifier for each secret.

secret Use this element to define the secret.

This secret is sent with the RIP updates on the speci-fied interface. It is also used to authenticate incoming RIP updates.

interface Use this element to specify on which interface the secret is used.

Entering the string “all” (default) means the secret is used on all the interfaces.




Default:allRange: 0 … 24 characters



133

telindus1423Router/ip/router/sysSecret

Use this attribute for the PPP authentication process. The PPP authentica-tor uses the sysSecret attribute in order to verify the peer its response.



telindus1423Router/ip/router/pppSecretTable

Use this attribute for the PPP authentication process. Enter the authentica-tion name and secret of the remote router in this table.



The pppSecretTable contains the following elements:

Element Description

name Use this element to set the PPP authentication name of the remote router.

If the remote router is a Telindus 1423 SHDSL Router, then the name element should correspond with the remote Telindus 1423 SHDSL Router its sysName or sessionName attribute. Refer to MU-7.4.10 - Quels attributs de nom et de secret uti-liser en vue de l’authentification PPP ? on page 178.

secret Use this element to set the PPP authentication secret of the remote router.

If the remote router is a Telindus 1423 SHDSL Router, then the secret element should correspond with the remote Telindus 1423 SHDSL Router its sysSecret or sessionSecret attribute. Refer to MU-7.4.10 - Quels attributs de nom et de secret uti-liser en vue de l’authentification PPP ? on page 178.







134

telindus1423Router/ip/router/helperProtocols

Use this attribute to define the TCP and UDP port numbers for which broad-cast forwarding is required. Use this attribute if you specified helper IP addresses using the helpers ele-ment in the ip structure of the LAN interface. Refer to MU-5.2.3 - Explication de la structure ip on page 63.

If the helperProtocols table is empty (default), then address substitution is applied for the following proto-cols:

Important remark

Specifying at least one value in the helperProtocols table clears the default helper list automatically. In that case, if you want that for instance NetBios Datagram Server broadcast is forwarded, you have to specify port number 138 again.

For BootP / DHCP broadcast packets, the Telindus 1423 SHDSL Router is also a BootP / DHCP Relay Agent. If the protocol is selected, then the Telindus 1423 SHDSL Router will write the IP address of its Ethernet interface in the BootP or DHCP gateway field and increment the hops field in addition to the address substitution.

Protocol name TCP/UDP port number

Time Server 37

IEN-116 Host Name Server 42

Domain Name Server 53

TACACS database service 65

Boot Protocol (BootP) / DHCP server 68

NetBIOS Name Server 137

NetBIOS Datagram Server 138




135

telindus1423Router/ip/router/sendTtlExceeded

Use this attribute to enable or disable the sending of ICMP “TTL exceeded“ messages.

The sendTtlExceeded attribute has the following values:

What is Time To Live (TTL)?

Each IP packet has a Time To Live (TTL) value in its header. Each device that sends an IP packet sets this parameter at some fixed or predefined value. When the packet enters a router, the router decre-ments the TTL value. If a router finds a value 0 after decrementing the TTL, it discards the packet. This because a value 0 means the packet has passed too many routers. Probably the packet is looping between a number of routers. This mechanism avoids that routers with configuration errors bring down a complete network.

The ICMP message “TTL exceeded”

If a router discards a packet because its TTL is exceeded, it normally sends an ICMP “TTL exceeded“ message to the originator of the packet. With the sendTtlExceeded attribute you can define whether you want the Telindus 1423 SHDSL Router to send such ICMP messages or not.

It has been chosen to allow TTL exceeded messages in case of PPP. However, this has the effect that TTL exceeded is also transmitted on some Ethernet broadcasts.

Value Description

enabled The Telindus 1423 SHDSL Router sends ICMP “TTL exceeded" messages.

disabled The Telindus 1423 SHDSL Router does not send ICMP “TTL exceeded” mes-sages.

This also implies that the router is not recognised by the UNIX or Windows trace-route feature.




136

telindus1423Router/ip/router/sendPortUnreachable

Use this attribute to enable or disable the sending of ICMP “Destination unreachable: Port unreachable“ messages.

The sendPortUnreachable attribute has the following values:

The ICMP message “port unreachable”

The Telindus 1423 SHDSL Router supports a number of higher-layer IP protocols (Telnet, SNMP and TMA) for management purposes. If an IP packet is sent to the Telindus 1423 SHDSL Router for a higher-layer protocol that it does not support, it normally sends an ICMP “Destination unreachable: Port unreachable“ message to the originator of the packet. With the sendPortUnreachable attribute you can define whether you want the Telindus 1423 SHDSL Router to send such an ICMP message or not.

telindus1423Router/ip/router/sendAdminUnreachable

Use this attribute to enable or disable the sending of ICMP "Destination unreachable: Communication with destination is administratively prohibited” messages.

The sendAdminUnreachable attribute has the following values:

The ICMP message “communication prohibited”

If the Telindus 1423 SHDSL Router receives an IP packet that is destined for a prohibited destination (because this destination is defined in an access list), then it sends an ICMP "Destination unreachable: Communication with destination is administratively prohibited” message to the originator of the packet. With the sendAdminUnreachable attribute you can define whether you want the Telindus 1423 SHDSL Router to send such an ICMP message or not.

Value Description

enabled The Telindus 1423 SHDSL Router sends ICMP “port unreachable" messages.

disabled The Telindus 1423 SHDSL Router does not send ICMP “port unreachable” mes-sages.

This also implies that the router is not recognised by the UNIX or Windows trace-route feature.

Value Description

enabled The Telindus 1423 SHDSL Router sends ICMP “communication prohibited“ mes-sages.

disabled The Telindus 1423 SHDSL Router does not send ICMP “communication prohib-ited“ messages.





137

telindus1423Router/ip/router/dhcpStatic

This attribute activates the DHCP server on the Telindus 1423 SHDSL Router. Use this attribute to assign a fixed IP address to a client its MAC address and this for an infinite time.

The dhcpStatic table contains the following elements:

Element Description

ipAddress Use this element to assign an IP address to a certain client. This client is identified with its MAC address.

If no IP address is specified, then there is no connection to the client. In that case, all other attributes in the table are ignored for this client.

mask Use this element to set the client its subnet mask.

gateway Use this element to set the default gateway for the cli-ent its subnet.

If the interface element is left empty (default), then it is the gateway element that determines on which interface the Telindus 1423 SHDSL Router will act as DHCP server. Namely the interface through which the IP address as entered in the gate-way element can be reached.

If no gateway is specified, then the Telindus 1423 SHDSL Router gives its own address. This address lies in the subnet of the interface through which the Telindus 1423 SHDSL Router sends out the DHCP reply.

interface Use this element to specify the name of the interface on which you want the Telindus 1423 SHDSL Router to act as DHCP server.

dnsSetting Use this element to determine which DNS servers are used for handling the DNS requests.

The dnsSetting element has the following values:

• configured. The Telindus 1423 SHDSL Router sends all DNS requests to the DNS servers that have been configured in the attribute telindus1423Router/ip/router/dns on page 144.

• learned. If DNS servers have been configured in the attribute telindus1423Router/ip/router/dns, then all DNS requests are sent to these servers. However, if no DNS servers have been configured, then the Telindus 1423 SHDSL Router tries to learn the DNS servers from the network. During the time the Telindus 1423 SHDSL Router has not learned the DNS servers yet, DNS relay is active allow-ing DNS between the clients that already have been given an IP address.

• relay. The Telindus 1423 SHDSL Router acts as a DNS server for its clients, caching all DNS requests. It answers to DNS requests if possible. However, if an entry is not present in its cache, then it relays this request to the DNS serv-ers that have been configured in the attribute telindus1423Router/ip/router/dns.

nameServer Use this element to set the IP address of the name server that is available to the client.






Default:learnedRange: enumerated, see below




138

nameServer2 Use this element to set the IP address of the second name server that is available to the client.

tftpServer Use this element to set the IP address of the TFTP server that is available to the client. It is the next server to use in boottrap.

macAddress Use this element to enter the client its MAC address.

If no MAC address is specified, then there is no con-nection to the client. Therefore, all other attributes in the table are ignored for this client.

bootFile Use this element to set the location of the boot file.

hostName Use this element to set the name of the client.

domainName Use this element to set the name the client should use when resolving hostnames via the Domain Name System (DNS).

netbiosNameServer Use this element to set the IP address of the NetBios server.

netbiosNameServer2

Use this element to set the IP address of the second NetBios server.

netbiosNodeType Use this element to configure the client as described in RFC 1001 / RFC 1002.

The netbiosNodeType element has the following values: no-node, B-node, P-node, M-node, H-node.

Element Description



Default:0.0.0.0.0.0Range: up to ff.ff.ff.ff.ff.ff









139

telindus1423Router/ip/router/dhcpDynamic

This attribute activates the DHCP server on the Telindus 1423 SHDSL Router. Use this attribute to specify the IP address range from which an IP address may be dynamically assigned to a client its MAC address.

The dhcpDynamic table contains the following elements:

Element Description

ipStartAddress Use this element to define the start address of the IP address range. It is from this range that an IP address will be dynamically assigned to a client.

If no IP start address is specified, all other attributes on the same line in the table are ignored.

ipEndAddress Use this element to define the end address of the IP address range. It is from this range that an IP address will be dynamically assigned to a client.

The IP address range will only contain the ipStartAddress in case …

• no ipEndAddress is specified,• the specified ipEndAddress is the same as the ipStartAddress,• the specified ipEndAddress is smaller than the ipStartAddress,• the specified ipEndAddress belongs to another subnet than the ipStartAddress.

Do not include the Telindus 1423 SHDSL Router its own IP address in this range!

mask Use this element to set the client its subnet mask for the specified IP address range.

gateway Use this element to set the default gateway for the cli-ent its subnet.

If the interface element is left empty (default), then it is the gateway element that determines on which interface the Telindus 1423 SHDSL Router will act as DHCP server. Namely the interface through which the IP address as entered in the gate-way element can be reached.

If no gateway is specified, then the Telindus 1423 SHDSL Router gives its own address. This address lies in the subnet of the interface through which the Telindus 1423 SHDSL Router sends out the DHCP reply.

interface Use this element to specify the name of the interface on which you want the Telindus 1423 SHDSL Router to act as DHCP server.









140

dnsSetting Use this element to determine which DNS servers are used for handling the DNS requests.

The dnsSetting element has the following values:

• configured. The Telindus 1423 SHDSL Router sends all DNS requests to the DNS servers that have been configured in the attribute telindus1423Router/ip/router/dns on page 144.

• learned. If DNS servers have been configured in the attribute telindus1423Router/ip/router/dns, then all DNS requests are sent to these servers. However, if no DNS servers have been configured, then the Telindus 1423 SHDSL Router tries to learn the DNS servers from the network. During the time the Telindus 1423 SHDSL Router has not learned the DNS servers yet, DNS relay is active allow-ing DNS between the clients that already have been given an IP address.

• relay. The Telindus 1423 SHDSL Router acts as a DNS server for its clients, caching all DNS requests. It answers to DNS requests if possible. However, if an entry is not present in its cache, then it relays this request to the DNS serv-ers that have been configured in the attribute telindus1423Router/ip/router/dns.

nameServer Use this element to set the IP address of the name server that is available to the client.

nameServer2 Use this element to set the IP address of the second name server that is available to the client.

tftpServer Use this element to set the IP address of the TFTP server that is available to the client. It is the next server to use in boottrap.

leaseTime Use this element to set the maximum time a client can lease an IP address from the specified IP address range.

If 00000d 00h 00m 00s (default) is specified, then the lease time is infinite.

holdTime Use this element to set the time between two consec-utive leases of an IP address. I.e. if a client has just let go of its dynamically assigned IP address, then this same IP address can not be reassigned before the holdTime has elapsed.

bootFile Use this element to set the location of the boot file.

hostName Use this element to set the name of the client.

Because the DHCP server can not give the same name to all clients of this IP address range, a number is added to the hostname from the second IP address onwards. The number goes up to 99.

Example

Suppose the hostname is OneAccess. In that case the name for the start IP address is OneAccess, for the second IP address OneAccess1, and so on.

Element Description

Default:learnedRange: enumerated, see below





24855d 03h 14m 07s


24855d 03h 14m 07s





141

telindus1423Router/ip/router/dhcpCheckAddress

Use this attribute to allow that the IP address assigned by the DHCP server is probed with an ARP request (Ethernet) or ICMP Echo Request (IP). This checks and prevents the dou-ble use of IP addresses.

The dhcpCheckAddress attribute has the following values:

domainName Use this element to set the name the client should use when resolving hostnames via the Domain Name System (DNS).

netbiosNameServer Use this element to set the IP address of the NetBios server.

netbiosNameServer2

Use this element to set the IP address of the second NetBios server.

netbiosNodeType Use this element to configure the client as described in RFC 1001 / RFC 1002.

The netbiosNodeType element has the following values: no-node, B-node, P-node, M-node, H-node.

Value Description

disabled No probing is done when an IP address is leased by a client.

enabled Probing is done when an IP address is leased by a client. In case of …

• Ethernet, the probing is done with an ARP request.• IP, the probing is done with an ICMP Echo Request (ping).

If a reply is received, it means the IP address is already in use. Therefore, another IP address is assigned.

arpOnly Probing is done when an IP address is leased by a client. However, the probing is only done by means of an ARP request (Ethernet).

Element Description








142

telindus1423Router/ip/router/radius

Use this attribute to configure the Telindus 1423 SHDSL Router for RADIUS. Also see MU-10.7 - Configuration RADIUS on page 375.

To enable the use of RADIUS in PPP, PAP or CHAP should be enabled on the Telindus 1423 SHDSL Router. The local configuration of the username and password is ignored if a table of RADIUS servers exist. Furthermore, remote IP address and remote netmask are ignored if a RADIUS server imposes these attributes.

The radius structure contains the following elements:

Element Description

authServers Use this element to select an authentication server. You can create a list of several authentication servers.

The authServers table contains the following elements:

• address. Use this element to specify the IP address of the authentication server.

• secret. Use this element to set the shared secret to authenticate the transaction with the authentica-tion server.

• timeOut. Use this element to specify the authentica-tion time-out.

acctServer Use this element to select an accounting server. You can only select one accounting server.

The acctServer structure contains the following elements:

• address. Use this element to specify the IP address of the accounting server.

• secret. Use this element to set the shared secret to authenticate the transaction with the accounting server.

• timeOut. Use this element to specify the accounting time-out.

retries Use this element to specify the number of retries before selecting the next authentication server in the authServers table.

acctUpdate Use this element to specify the time at which an update of the accounting data should be send to the server.

Set this element to 0 (default) if no update is required. Note that this is not always supported by the accounting server.






00000d 00h 00m 10s





00000d 00h 00m 10s



00000d 00h 01m 00s



143

login Use this element to set the authentication of access to the Telindus 1423 SHDSL Router using Telnet, FTP, TFTP or TMA. No accounting data is sent to the server.

The login element has the following values:

• disabled. No RADIUS login authentication is done.• enabled. Login authentication is always done using a RADIUS server.

The username and password have to be entered as follows: "username:pass-word". If the ‘:’ is omitted, then the string is considered to be a password.Multiple passwords can be added using the same username. Access rights are sent using the RADIUS attribute CLASS (25) encoded as a string carrying a binary value. The bit definitions are:- readAccess = 00000001B- writeAccess = 00000010B- securityAccess = 00000100B- countryAccess = 00001000B (only used on aster4/5)- fileAccess = 00010000BCaution should be taken since all access to the device has to be authenticated by a RADIUS server.

• fallback. Login authentication is done using a RADIUS server. However, if the server is not available, then authentication is done using the local security table of the device.

ppp Use this element to set the authentication of a PPP connection that uses PAP or CHAP.

The ppp element has the following values:

• disabled. PPP authentication is done using the local sysName/sysSecret or session-Name/sessionSecret of the device.

• enabled. PPP authentication is always done using a RADIUS server.

Element Description


Default:enabledRange: enumerated, see below



144

telindus1423Router/ip/router/dns

Use this attribute to enter the DNS server addresses. Also see What is DNS? on page 509.

The dns structure contains the following elements:

What is DNS?

The Domain Name Service (DNS) is an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they are easier to remember. The Internet however, is really based on IP addresses. Therefore, every time you use a domain name, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.mywebsite.com might translate to 198.105.232.4.

The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.

What is DNS proxy?

The Telindus 1423 SHDSL Router is a DNS proxy. This means that if the Telindus 1423 SHDSL Router has not received a DNS address (as DHCP client), then it gives its own address in DHCP requests (as DHCP server). The Telindus 1423 SHDSL Router relays DNS requests it receives to configured or learned DNS servers.

Element Description

primaryDns Use this element to specify the IP address of the pri-mary DNS server.

secondaryDns Use this element to specify the IP address of the sec-ondary DNS server.

domainName Use this element to enter the domain name to which the Telindus 1423 SHDSL Router belongs.







145

telindus1423Router/ip/router/addrPools

This attribute is only present on the Telindus 1423 SHDSL Router ISDN ver-sion.

Use this attribute to create a list or an interval of IP addresses from which the Telindus 1423 SHDSL Router can pick IP addresses and use them on a PPP link6.

The addrPool table contains the following elements:

6. The ip structure in the forwardingMode profile applies on the PPP link(s) that you can set up on the ISDN interface(s).

Element Description

name Use this element to assign a name to the IP pool.

pool Use this element to select between an IP pool type and to add IP addresses to the pool.

You can select between the following IP pool types:

• an IP list pool. Refer to telindus1423Router/ip/router/addrPools/pool/list on page 146.• an IP interval pool. Refer to telindus1423Router/ip/router/addrPool/pool/interval on

page 149.



Default:<empty>Range: choice, see below



146

telindus1423Router/ip/router/addrPools/pool/list

Use this element to create one or more lists of IP addresses from which the Telindus 1423 SHDSL Router can pick IP addresses and use them as local and remote IP address for a PPP link. Use the addrPool element in the ip structure to determine from which IP list pool the Telindus 1423 SHDSL Router has to pick IP addresses. Refer to MU-5.2.3 - Explication de la structure ip on page 63 for more information.

The list table contains the following elements:

Important remark

Note again that an IP list pool is for both local and remote IP addresses.

Element Description

name Use this element to assign a name to the IP list pool.

pool Use this element to create a list of IP addresses from which the Telindus 1423 SHDSL Router can pick one.

The pool table contains the following elements:

• local. Use this element to set the local IP address.

• remote. Use this element to set the remote IP address.

• netmask. Use this element to set the subnet mask.




Default:0.0.0.0Range: up to 255.255.255.255Default:0.0.0.0Range: up to 255.255.255.255




147

Example

Suppose …

• you want to create two IP list pools: myList1 and myList2.• you want that the Telindus 1423 SHDSL Router picks local and remote IP addresses from myList2.

Configure this as follows:

Step Action

1 Create two entries in the router/addrPools table and specify a name for each entry.

2 In the pool element select the value list.

3 Expand the pool element by clicking on the black triangle of the pool element.

4 Double-click on the <Table> string situated in the pool/list column.



148

5 Create entries in the pool/list tables and enter a local IP address, remote IP address and a netmask for each entry.

6 In the addrPool element of the ip structure, select the value “list” and enter the name of the IP list pool from which you want to pick IP addresses. In our example, this is myList2.

Step Action



149

telindus1423Router/ip/router/addrPool/pool/interval

Use this element to create one or more ranges of IP addresses from which the Telindus 1423 SHDSL Router can pick IP addresses and use them as remote IP address for a PPP link. Use the addrPool element in the ip structure to determine from which IP interval pool the Telindus 1423 SHDSL Router has to pick IP addresses. Refer to MU-5.2.3 - Explication de la structure ip on page 63 for more information.

The interval structure contains the following elements:

Important remark

Note again that an IP interval pool is for remote IP addresses only.

Element Description

name Use this element to assign a name to the IP interval pool.

fromto

Use these elements to create a range of IP addresses from which the Telindus 1423 SHDSL Router can pick one.






150

Example

Suppose …

• you want to create two IP interval pools: myInterval1 and myInterval2.• you want that the Telindus 1423 SHDSL Router picks a remote IP addresses from myInterval2.

Configure this as follows:

Step Action

1 Create two entries in the router/addrPools table and specify a name for each entry.

2 In the pool element select the value interval.

3 Expand the pool element by clicking on the black triangle of the pool element.

4 Double-click on the <Struct> string situated in the pool/interval column.



151

telindus1423Router/ip/router/<alarmConfigurationAttributes>



• the alarms of the router object, refer to MR-4.13 - Router alarms on page 504.

5 Configure the pool/interval structures. I.e. create an IP address range using the elements from and to.

6 In the addrPool element of the ip structure, select the value “interval” and enter the name of the IP interval pool from which you want to pick IP addresses. In our example, this is myInterval2.

Step Action



152

MR-1.12.2 NAT configuration attributes


• telindus1423Router/ip/router/defaultNat/patAddress on page 153• telindus1423Router/ip/router/defaultNat/portTranslations on page 153• telindus1423Router/ip/router/defaultNat/servicesAvailable on page 154• telindus1423Router/ip/router/defaultNat/addresses on page 154• telindus1423Router/ip/router/defaultNat/gateway on page 155• telindus1423Router/ip/router/defaultNat/tcpSocketTimeOut on page 155• telindus1423Router/ip/router/defaultNat/udpSocketTimeOut on page 155• telindus1423Router/ip/router/defaultNat/tcpSockets on page 155• telindus1423Router/ip/router/defaultNat/udpSockets on page 155• telindus1423Router/ip/router/defaultNat/dmzHost on page 155



153

telindus1423Router/ip/router/defaultNat/patAddress

Use this attribute to enter the official IP address that has to be used for the Port Address Translation. Entering an address different from the default value 0.0.0.0 automatically ena-bles PAT.

Refer to MU-8.7 - Configuration de translation d'adresses on page 229 for more information on PAT.

telindus1423Router/ip/router/defaultNat/portTranslations

Use this attribute to define specific port number ranges that should not be translated.

Some TCP or UDP applications do not allow port translations: these applications require a dedicated source port number. In the portTranslations table you can define UDP and TCP port ranges that should not be translated. If a packet with a source port number in such a range is received, PAT replaces only the source IP address provided it is the first device using this port number. When other devices using the same application (hence the same port number) try to send traffic to the same Internet destination address, PAT discards this traffic.

It is also possible to define port ranges that PAT should always discard. The port translation range PAT uses goes from 60928 up to 65535.

The portTranslations table contains the following elements:

Element Description

protocol Use this element to select the protocol: tcp or udp.

startPort Use this element to set the lowest value of the TCP or UDP port range.

endPort Use this element to set the highest value of the TCP or UDP port range.

If no endPort value is defined (<opt>), then the port range is limited to the startPort value only.

action Use this element to set the action in case a packet is received with a source port number that falls within the specified port range.

The action element has the following values:

• noTranslation. The port numbers that fall within the specified port range are not translated.

• deny. Packets with port numbers that fall within the specified port range are dis-carded.



Default:tcpRange: tcp / udp



Default:noTranslationRange: enumerated, see below



154

telindus1423Router/ip/router/defaultNat/servicesAvailable

Use this attribute to define specific port number ranges for incoming Internet traffic that should not be translated. Instead it is sent to the corresponding private IP address.

The servicesAvailable table makes it possible to have a server on the local network that can be accessed from the Internet, although it has no official IP address.

The servicesAvailable table contains the following elements:

telindus1423Router/ip/router/defaultNat/addresses

Use this attribute to enter all the official IP addresses that have to be used for Network Address Translation. Entering an address in the addresses table automatically enables the general NAT process. Now you can activate or deactivate NAT per IP interface. Note that by default NAT is deactivated on all IP interfaces.

Refer to MU-8.7 - Configuration de translation d'adresses on page 229 for more information on NAT.

The addresses table contains the following elements:

Element Description

protocol Use this element to select the protocol: tcp or udp.

startPort Use this element to set the lowest value of the TCP or UDP port range.

endPort Use this element to set the highest value of the TCP or UDP port range.

If no endPort value is defined (<opt>), then the port range is limited to the startPort value only.

serverAddress Use this element to set the private server address.

If a packet is received with a source port number that falls within the specified port range, then it is sent to the private server address.

Element Description

officialAddress Use this element to set the official IP address.

These addresses are used in the reverse order as they appear in the list.

privateAddress Use this element to set the private IP address, i.e. to permanently assign an official IP address to a private address.

If you do not specify a private IP address, then NAT is applied dynamically. I.e. the official IP address is used for any private source IP address.


Default:tcpRange: tcp / udp









155

telindus1423Router/ip/router/defaultNat/gateway

Use this attribute to define the gateway addresses of routes on which NAT or PAT should be applied. If you do not configure the gateway attribute, then NAT or PAT is applied on all routes through this interface.

telindus1423Router/ip/router/defaultNat/tcpSocketTimeOut

Use this attribute to define the time-out for TCP sessions that are not closed by the application.

Such sessions, whether PAT or NAT is in use, remain active for one day by default. Only decrease this attribute if some TCP applications do not close properly, filling up the available translation sessions.

telindus1423Router/ip/router/defaultNat/udpSocketTimeOut

Use this attribute to define the time-out for UDP sessions that are not closed by the application.

Such sessions, whether PAT or NAT is in use, remain active for 3 minutes by default. Only decrease this attribute if some UDP applications do not close properly, filling up the available translation sessions.

telindus1423Router/ip/router/defaultNat/tcpSockets

Use this attribute to set the maximum number of TCP session that may be used simultaneously for address translation.

telindus1423Router/ip/router/defaultNat/udpSockets

Use this attribute to set the maximum number of UDP session that may be used simultaneously for address translation.

telindus1423Router/ip/router/defaultNat/dmzHost

Use this attribute to set the address of the DMZ (demilitarised zone) host.

What is a DMZ?

In computer networks, a DMZ (demilitarised zone) is a computer host or small network inserted as a "neutral zone" between a company's private network and the outside public network. It prevents outside users from getting direct access to a server that has company data. A DMZ is an optional and more secure approach to a firewall and effectively acts as a proxy server as well.

In a typical DMZ configuration for a small company, a separate computer receives requests from users within the private network for access to Web sites or other companies accessible on the public network. The DMZ host then initiates sessions for these requests on the public network. However, the DMZ host is not able to initiate a session back into the private network. It can only forward packets that have already been requested.

Users of the public network outside the company can access only the DMZ host. The DMZ may typically also have the company's Web pages so these could be served to the outside world. However, the DMZ provides access to no other company data. In the event that an outside user penetrated the DMZ host's security, the Web pages might be corrupted but no other company information would be exposed.



24855d 03h 14m 07s


24855d 03h 14m 07s






156

MR-1.12.3 L2TP tunnel configuration attributes


• telindus1423Router/ip/router/tunnels/l2tpTunnels on page 157• telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels on page 162



157

telindus1423Router/ip/router/tunnels/l2tpTunnels

Use this attribute to configure the Layer 2 Tunnelling Protocol tunnels you want to set up. Add a row to the l2tpTunnels table for each L2TP tunnel you want to set up.

The l2tpTunnels table contains the following elements:

Element Description

name Use this element to assign an administrative name to the tunnel.

adminStatus Use this element to activate (up) or deactivate the tun-nel (down).

mode Use this element to determine whether for the corre-sponding tunnel, IP packets are treated by the routing process, the bridging process or both.


• bridging. All packets received on the tunnel are bridged.• routing. All packets received on the tunnel are routed.• routingAndBridging. The SNAP header is checked to determine whether the pack-


ip Use this element to configure the IP related parame-ters of the tunnel.

Refer to …



bridging Use this element to configure the bridging related parameters of the tunnel.

When bridging is enabled on a tunnel interface, the tunnel acts exactly as a bridge port for a physical PPP connection.

Refer to …



l2tp Use this element to configure the L2TP related parameters of the tunnel.

Refer to telindus1423Router/ip/router/tunnels/l2tpTunnels/l2tp on page 158 for a detailed description of the l2tp structure.

backup Use this element to configure the back-up related parameters of the tunnel.

Refer to telindus1423Router/ip/router/tunnels/l2tpTunnels/backup on page 161 for a detailed description of the backup structure.



Default:downRange: up / down








158

telindus1423Router/ip/router/tunnels/l2tpTunnels/l2tp

Use the l2tp structure in the l2tpTunnels table to configure the L2TP related parameters of the tunnel.

The l2tp structure contains the following elements:

Element Description

localIpAddress Use this element to set the official IP address that serves as start point of the L2TP connection.

remoteIpAddress Use this element to set the official IP address that serves as end point of the L2TP connection.

Both localIpAddress and remoteIpAddress together with the well-known port number for L2TP (i.e. 1701), make up the socket used for the L2TP session. At the moment, only one L2TP session can exist between one localIpAddress and remoteIpAddress combination.

remoteDnsName Instead of specifying a remoteIpAddress, you can specify the DNS name of the end point of the L2TP connec-tion. In that case, the DNS name will be resolved to an IP address.

Note that in this case, DNS has to be configured on the Telindus 1423 SHDSL Router. Refer to telindus1423Router/ip/router/dns on page 144.

pppAuthentication Use this element to enable or disable authentication on the PPP link in the tunnel.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/authentication on page 60 for more information.

pppSesionName Use this element to set the PPP authentication name of the PPP link in the tunnel.

pppSesionSecret Use this element to set the PPP authentication secret of the PPP link in the tunnel.

linkMonitoring Use this element to enable or disable link monitoring on the PPP link in the tunnel and to fine-tune it.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/linkMonitoring on page 59 for more information.











159

type Use this element to specify the tunnel type.


• outgoingDial. The outgoing tunnel is not continuously open. It is opened when-ever data has to be sent through the tunnel, and closed when no data is detected for a certain time.

• outgoingLeasedLine. The outgoing tunnel is opened as soon as the Telindus 1423 SHDSL Router is up, and it stays open.

• incoming. The tunnel is an incoming tunnel.

Important remark

Make sure that if the type element is set to outgoingDial or outgoingLeasedLine at one end of the tunnel, that at the other end of the tunnel the type element is set to incoming.

dataChannelSe-quenceNumbering

Use this element to enable (on) or disable (off) sequence numbering on the data messages. These sequence numbers are used to detect lost packets and/or restore the original sequence of packets that may have been reordered dur-ing transport.

On control messages, sequence numbering is always enabled.

It is recommended that for connections where reordering or packet loss may occur, dataChannelSequenceNumbering is enabled.

keepAliveTimeOut Use this element to set the amount of time (in sec-onds) the tunnel waits before it sends a keep alive message in case it receives no data.

If the tunnel does not receive incoming data during a certain time, it sends a keep alive message to the other side and waits for an acknowledgement.

noTrafficTimeOut This element applies on dial tunnels only (i.e. for which the type element is set to outgoingDial).

Use this element to set the amount of time (in seconds) the tunnel waits before it closes in case it receives no data.

l2tpMode Use this element to set the L2TP function of the Telindus 1423 SHDSL Router.

The l2tpMode element has the following values:

• lac. The Telindus 1423 SHDSL Router acts as an L2TP Access Concentrator.• lns. The Telindus 1423 SHDSL Router acts as an L2TP Network Server.• auto. If both local and remote Telindus 1423 SHDSL Router are set to auto, they

mutually decide who will be the LAC and who the LNS.

Important remark

Only select auto if you use a OneAccess router at both sides of the tunnel. In conjunction with routers from other vendors (e.g. Cisco), specifically select an L2TP mode (lac or lns).

Element Description

Default:outgoingDialRange: enumerated, see below






160

tunnelAuthentication Use this element to enable (on) or disable (off) tunnel authentication.

L2TP incorporates a simple, optional, CHAP-like tunnel authentication system dur-ing control connection establishment.

If the LAC or LNS wishes to authenticate the identity of the peer it is contacting or being contacted by, it sends a challenge packet. If the expected response and response received from a peer does not match, the tunnel is not opened.

To participate in tunnel authentication, a single shared secret has to exist between the LAC and LNS.

tunnelSecret Use this element to set the tunnel secret. This secret is used in the tunnel authentication in order to verify the peer its response.

copyTos Use this element to enable (on) or disable (off) the cop-ying of the TOS byte value from the payload its IP header to the L2TP header.

maxNrOfRetrans-missions

Use this element to set the number of times a control message has to be retransmitted in case no acknowl-edgement follows, before the tunnel is closed.

transmitWindowSize Use this element to set the window size for transmit-ting control messages.

receiveWindowSize Use this element to set the window size for receiving control messages.

udpChecksum Use this element to enable (on) or disable (off) the UDP checksum.

It is recommended to enable the UDP checksum on lower quality links.

calledNr Use this element to set the called number. This ele-ment is present for compatibility with other vendors that support this feature. If you set up a tunnel between two OneAccess devices, then you can leave this element empty.

The called number is an indication to the receiver of a call as to what (telephone) number the caller used to reach it. It encodes the (telephone) number to be called for an outgoing call request (OCRQ) and the called number for an incoming call request (ICRQ).

The called number is an ASCII string. Contact between the administrator of the LAC and the LNS may be necessary to coordinate interpretation of the value needed in this element.

speed Use this element to make an indication of the expected speed for the tunnel in case of MLPPP.

In case you use MLPPP, the Bandwidth Allocation Protocol adds or deletes PPP links from the bundle depending on the actual amount of traffic. However, some-how you have to be able to specify the normally required speed. Do this using the speed element.

Element Description



Default:onRange: on / off






Default:64000Range: 0 … 2147483647



161

telindus1423Router/ip/router/tunnels/l2tpTunnels/backup

Use the backup structure in the l2tpTunnels table to configure the back-up related parameters of the tunnel.

In a main/back-up tunnel mechanism, configuring the backup element allows you to quickly set up a back-up tunnel as soon as the main tunnel goes down, instead of waiting on several time-outs before the back-up tunnel is set up. Refer to MU-10.5.4 - Configuration d’un tunnel principal et de secours on page 351.

The backup structure contains the following elements:

Element Description

interface Use this element to enter the name of the tunnel that will act as back-up in a main/back-up mechanism.

Alternatively, if the string "discard" is entered as a backup interface, then the backup functionality is executed for the main tunnel even if no backup tunnel is present. So the main tunnel is reset and the route to the main tunnel is closed (so the route status goes “down” instead of “spoofing”). In that case, if an alternative route is present, then this route will be taken.

timeOut Use this element to set the set-up time-out in sec-onds. If the tunnel is not set up within the specified time-out, then the back-up tunnel is set up.

autoRetry This element is only relevant in case the type element of the tunnel is set to outgoingLeasedLine.

Use this element to determine, if a leased line tunnel does not come up, whether it has to keep trying to come up (yes) or quit after one try (no).




Default:noRange: yes / no



162

telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels

Use this attribute to configure the IP secured Layer 2 Tunnelling Protocol tunnels you want to set up. Add a row to the IpsecL2tpTunnels table for each IPSEC L2TP tunnel you want to set up.

The elements of the ipsecL2tpTunnel are basically the same as the elements of the l2tpTunnel (refer to telindus1423Router/ip/router/tunnels/l2tpTunnels on page 157). The only difference is the presence of the ipsec ele-ment within the l2tp structure. Refer to telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec on page 162 for more information on the ipsec element.

telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec

Use this element to apply a security association on the IPSEC L2TP tunnel.

Do this by typing the index name of the security association you want to use. You can create the security association itself by adding a manualSA or ikeSA object and by configuring the attributes in this object. Refer to MU-10.6 - Configuration d'une sécurité IP on page 354 for more information on IP security.

The ipsec element offers you the following choice:

Choice Description

fdxManualSA Select this value if you want to apply a manual secu-rity association on both the inbound and outbound traffic of the IPSEC L2TP tunnel.

If you select this value, then a field appears behind the value. Type the manualSA object its index name in this field.

Example

If you created a manualSA object with index name my_SA (i.e. manualSA[my_SA]) and you want to apply this security association on an IPSEC L2TP tunnel, then enter the index name as value of the ipsec element.


Default:-Range: choice, see below




163

hdxManualSA Select this value if you want to apply a manual secu-rity association on the inbound traffic and another manual security association on the outbound traffic of the IPSEC L2TP tunnel.

If you select this value, then a structure appears behind the value. This structure contains the following elements:

• inbound. To apply a security association on the inbound traffic, type the manualSA object its index name in this field.

• outbound. To apply a security association on the outbound traffic, type the manualSA object its index name in this field.

Example

If you created a manualSA object with index name my_SA_in (i.e. manualSA[my_SA_in]) and one with index name my_SA_out (i.e. manualSA[my_SA_out]) and you want to apply the first on the inbound and the latter on the outbound traffic, then enter the index names of the manualSA objects as follows:

ikePresharedSA Select this value if you want to apply an IKE pre-shared key security association on both the inbound and outbound traffic of the IPSEC L2TP tunnel.

If you select this value, then a structure appears behind the value. Refer to telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec/ikePresharedSA on page 164 for a detailed description of the ikePresharedSA structure.

ikeCertificateSA Select this value if you want to apply an IKE certificate security association on both the inbound and out-bound traffic of the IPSEC L2TP tunnel.

If you select this value, then a structure appears behind the value. Refer to telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec/ikeCertificateSA on page 165 for a detailed description of the ikeCertificateSA structure.

Choice Description








164

telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec/ikePresharedSA

Use the ikePresharedSA structure in the ipsec structure to apply an IKE pre-shared key security association on both the inbound and outbound traffic of the IPSEC L2TP tunnel.

The ikePresharedSA structure contains the following elements:

Element Description

ikeSA Use this element to apply a certain IKE preshared key security association on the IPSEC L2TP tunnel.

Do this by typing the ikeSA object its index name in this field.

Example

If you created an ikeSA object with index name mySA (i.e. ikeSA[mySA]) and you want to apply this security association on an IPSEC L2TP tun-nel, then enter the index name as value of the ikeSA element.

localId Use this element to set the local identifier for use in IKE phase 1 negotiation.

The localId element has the following values:

• ipAddress. Set the IP address that will be used as local ID. If you leave the ipAd-dress element at its default value (0.0.0.0), then the local IP address of the L2TP tunnel is used as local ID.

• hostname. Set the hostname that will be used as local ID. The hostname has to be of the form “host.domain.com”.

• user. Set the username that will be used as local ID. The username has to be of the form “[email protected]”.

remoteId Use this element to set the remote identifier for use in IKE phase 1 negotiation.

The remoteId element has the following values:

• ipAddress. Sets the IP address that will be used as remote ID. If you leave the ipAddress element at its default value (0.0.0.0), then the remote IP address of the L2TP tunnel is used as remote ID.

• hostname. Sets the hostname that will be used as remote ID. The hostname has to be of the form “host.domain.com”.

• user. Sets the username that will be used as remote ID. The username has to be of the form “[email protected]”.

preSharedKey Use this element to set the pre-shared key string.

This key string in combination with the selected IKE DH group is used to calculate the key during the key exchange in phase 1 of the IKE negotiation. Refer to diffieHelmanGroup on page 173.



Default:<ipAddress> 0.0.0.0Range: choice, see below


Default:presharedkeyRange: 12 … 49 characters



165

telindus1423Router/ip/router/tunnels/ipsecL2tpTunnels/l2tp/ipsec/ikeCertificateSA

Use the ikeCertificateSA structure in the ipsec structure to apply an IKE certifi-cate security association on both the inbound and outbound traffic of the IPSEC L2TP tunnel.

The ikeCertificateSA structure contains the following elements:

Element Description

ikeSA Use this element to apply a certain IKE certificate security association on the IPSEC L2TP tunnel.

Do this by typing the ikeSA object its index name in this field.

Example

If you created an ikeSA object with index name mySA (i.e. ikeSA[mySA]) and you want to apply this security association on an IPSEC L2TP tun-nel, then enter the index name as value of the ikeSA element.

localId Use this element to set the local identifier for use in IKE phase 1 negotiation.

The localId element has the following values:

• ipAddress. Set the IP address that will be used as local ID. If you leave the ipAd-dress element at its default value (0.0.0.0), then the local IP address of the L2TP tunnel is used as local ID.

• hostname. Set the hostname that will be used as local ID. The hostname has to be of the form “host.domain.com”.

• user. Set the username that will be used as local ID. The username has to be of the form “[email protected]”.

The localId element has to be the same as the IP address / hostname / username in the certificate of the local device.

remoteId Use this element to set the remote identifier for use in IKE phase 1 negotiation.

The remoteId element has the following values:

• ipAddress. Sets the IP address that will be used as remote ID. If you leave the ipAddress element at its default value (0.0.0.0), then the remote IP address of the L2TP tunnel is used as remote ID.

• hostname. Sets the hostname that will be used as remote ID. The hostname has to be of the form “host.domain.com”.

• user. Sets the username that will be used as remote ID. The username has to be of the form “[email protected]”.

The remoteId element has to be the same as the IP address / hostname / username in the certificate of the remote device.







166

MR-1.12.4 Manual SA configuration attributes


• telindus1423Router/ip/router/manualSA[ ]/espEncryptionAlgorithm on page 167• telindus1423Router/ip/router/manualSA[ ]/espEncryptionKey on page 168• telindus1423Router/ip/router/manualSA[ ]/espAuthenticationAlgorithm on page 169• telindus1423Router/ip/router/manualSA[ ]/espAuthenticationKey on page 169• telindus1423Router/ip/router/manualSA[ ]/spi on page 169




167

telindus1423Router/ip/router/manualSA[ ]/espEncryptionAlgorithm

Use this attribute to select the algorithm that will be used to encrypt the data when using IPSEC.

The espEncryptionAlgorithm attribute has the following values:

Make sure that for the same security association on both the local and remote router the same ESP encryption algorithm is selected.

Value Description

null No encryption is done.

The null encryption algorithm is simply a convenient way to represent the optional use of applying encryption within ESP. ESP can then be used to provide authenti-cation and integrity without confidentiality.

des DES is used to encrypt / decrypt the data. The DES key has to be entered in the espEncryptionKey attribute.

3des Triple DES is used to encrypt / decrypt the data. The 3DES key has to be entered in the espEncryptionKey attribute.

Default:desRange: enumerated, see below



168

telindus1423Router/ip/router/manualSA[ ]/espEncryptionKey

Use this attribute to define the key that will be used in the encryption / decryption process when using IPSEC.

The algorithm can be selected using the espEncryptionAlgorithm attribute.

Make sure that for the same security association on both the local and remote router the same ESP encryption key is used.

If you use … then …

null encryption the setting of the espEncryptionKey attribute is irrelevant.

DES encryption only the first 8 octets of the key are used. All other octets are ignored.

3DES encryption at the transmitter side, the first set of 8 octets of the key are used to encrypt the data, the second set of 8 octets to decrypt the data and the third set of 8 octets to encrypt the data again.

At the receiver side, the opposite occurs.

Default:<empty>Range: octet string, 0 … 24

11 11 11 11 11 11 11 11 22 22 22 22 22 22 22 22 33 33 33 33 33 33 33 33

used in the encryption / decryption process

not used in the encryption / decryption process

11 11 11 11 11 11 11 11 22 22 22 22 22 22 22 22 33 33 33 33 33 33 33 33

encryption decryption

encryption



169

telindus1423Router/ip/router/manualSA[ ]/espAuthenticationAlgorithm

Use this attribute to select the algorithm that will be used to authenticate the data when using IPSEC.

The espAuthenticationAlgorithm attribute has the following values:

Make sure that for the same security association on both the local and remote router the same ESP authentication algorithm is selected.

telindus1423Router/ip/router/manualSA[ ]/espAuthenticationKey

Use this attribute to define the key that will be used in the authentication process when using IPSEC. The algorithm can be selected using the espAuthenticationAlgorithm attribute.

Make sure that on both the local and remote router the same ESP authentication key is used.

telindus1423Router/ip/router/manualSA[ ]/spi

Use this attribute to set the SPI value. Each security association must have a unique SPI value because this value is used to identify the security association.

Make sure that for the same security association on both the local and remote router the same SPI value is used.

Value Description

null No authentication is done.

hmac_md5 The MD5 hash function is used to authenticate the data. The MD5 key has to be entered in the espAuthenticationKey attribute.

hmac_sha-1 The SHA-1 hash function is used to authenticate the data. The SHA-1 key has to be entered in the espAuthenticationKey attribute.

If you use … then …

null authentication the setting of the espAuthenticationKey attribute is irrelevant.

MD5 authentication only the first 16 octets of the key are used. All other octets are ignored.

SHA-1 authentication all 20 octets of the key are used.

Default:hmac_md5Range: enumerated, see below

Default:<empty>Range: octet string, 0 … 20

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20

used in the authentication process

not used in the authentication process

Default:256Range: 256 … 2147483647



170

MR-1.12.5 IKE SA configuration attributes


• telindus1423Router/ip/router/ikeSA[ ]/phase1 on page 171• telindus1423Router/ip/router/ikeSA[ ]/phase2 on page 175




171

telindus1423Router/ip/router/ikeSA[ ]/phase1

Use this attribute to configure the parameters of phase 1 in the IKE negoti-ation process. IKE phase 1 negotiations are used to establish IKE SAs. These SAs protect the IKE phase 2 negotiations.

The phase1 structure contains the following elements:

Element Description

type Use this element to determine who initiates phase 1 of the IKE negotiation.


• client: This side initiates phase 1.• server: This side waits until the remote side initiates phase 1.• peerToPeer: Both sides can initiate phase 1.

mode Use this element to set the IKE mode. The choice between these modes is a matter of trade-offs.


• main: Main mode is selected. Some characteristics of main mode are:- Protects the identities of the peers during negotiations and is therefore more

secure. - Allows greater proposal flexibility than aggressive mode. - Is more time consuming than aggressive mode because more messages

are exchanged between peers. (Six messages are exchanged in main mode.)

• aggressive: Aggressive mode is selected. Some characteristics of aggressive mode are:- Exposes identities of the peers to eavesdropping, making it less secure than

main mode.- Takes half the number of messages of main mode, has less negotiation

power, and does not provide identity protection.- Is faster than main mode because fewer messages are exchanged between

peers. (Three messages are exchanged in aggressive mode.)


Default:clientRange: enumerated, see below

Default:aggressiveRange: enumerated, see below



172

encryptionAlgorithm Use this element to select the IKE encryption algo-rithm.

The encryption key is calculated using the selected diffieHelmanGroup algorithm in combination with the value of the preSharedKey element.

The encryptionAlgorithm element has the following values:

• des: DES (56 bits) is used to encrypt / decrypt the data.• 3des: Triple DES (168 bits) is used to encrypt / decrypt the data.• aes128: AES128 (128 bits) is used to encrypt / decrypt the data.• aes192: AES192 (192 bits) is used to encrypt / decrypt the data.• aes256: AES256 (256 bits) is used to encrypt / decrypt the data.

Make sure that for the same security association on both the local and remote router the same encryption algorithm is selected.

authenticationAlgo-rithm

Use this element to select the IKE authentication algo-rithm.

The authentication key is calculated using the selected diffieHelmanGroup algorithm in combination with the value of the preSharedKey element.

The authenticationAlgorithm element has the following values:

• hmac_md5: The MD5 hash function is used to authenticate the data.• hmac_sha-1: The SHA-1 hash function is used to authenticate the data.

Make sure that for the same security association on both the local and remote router the same authentication algorithm is selected.

Element Description


Default:hmac_sha-1Range: enumerated, see below



173

diffieHelmanGroup Use this element to select the algorithm that will be used to calculate the phase 1 IKE key. This key is then used to encrypt and authenticate the data. The calculation of the IKE key is based on the value of the preSharedKey element (refer to preSharedKey on page 164).

The diffieHelmanGroup element has the following values:

• 1_modp768: The Diffie-Hellman group 1 (768 bits) is used to calculate the IKE key.



Important remarks

• Note that the heavier the algorithm, the more processing power is required. E.g. when selecting the Diffie-Hellman group 5, up to 30 seconds may be needed to generate a key.

• Make sure that for the same security association on both the local and remote router the same Diffie-Hellman algorithm is selected.

lifeTime Use this element to set the life time, in seconds, of the IKE SA.

When the life time expires, it is replaced by a new SA (and SPI) or terminated.

keepAlive Use this element to configure the IKE keep alive mes-sages. Keep alive messages are sent to check and maintain, or keep alive, the connection between local and remote.

Refer to telindus1423Router/ip/router/ikeSA[ ]/phase1/keepAlive on page 174 for a detailed description of the keepAlive structure.

Element Description

Default:1_modp768Range: enumerated, see below

Default:28800Range: 120 … 86400




174

telindus1423Router/ip/router/ikeSA[ ]/phase1/keepAlive

Use the keepAlive structure in the phase1 structure to configure the IKE keep alive messages.

The keepAlive structure contains the following elements:

Element Description

mode Use this element to set the keep alive mode.


• disabled: Keep alive is disabled, i.e. no keep alive messages are sent.• onDemand: Keep alive messages are sent on the basis of traffic patterns. For

example, if a router has to send outbound traffic and the liveliness of the peer is questionable, the router sends a keep alive message to query the status of the peer. If a router has no traffic to send, it never sends a keep alive message.

• periodic: Keep alive messages are sent at the interval specified by the delay ele-ment.

delay Use this element to set the interval at which keep alive messages are sent in case the mode element is set to periodic.

failsPermitted Use this element to set the number of times a keep alive message is resent in case no answer was received on the original keep alive message.

interval Use this element to set the delay between the retries.

For example, considering the default values, if no answer is received on a keep alive message, then the router retries 3 times to resent the keep alive message with an interval of 10 sec-onds.


Default:onDemandRange: enumerated, see below


24855d 03h 14m 07s



24855d 03h 14m 07s



175


Use this attribute to configure the parameters of phase 2 in the IKE negoti-ation process.

The phase2 structure contains the following elements:

Element Description

pfsGroup Use this element to select the Perfect Forward Secrecy algorithm.

The pfsGroup element has the following values:

• none: No Perfect Forward Secrecy is performed. The IKE key is calculated based on the previous key.

• 1_modp768: A completely new key is calculated using the Diffie-Hellman group 1 (768 bits).



Important remarks

• Note that the heavier the algorithm, the more processing power is required. E.g. when selecting the Diffie-Hellman group 5, up to 30 seconds may be needed to generate a key.

• Make sure that for the same security association on both the local and remote router the same PFS algorithm is selected.

natTraversal Use this element to enable or disable NAT traversal.

If natTraversal is enabled, then IPSEC traffic flows transparently through a NAT device, thereby allowing one or more remote hosts located behind the NAT device to use secure L2TP/IPSec tunnel connections to access the router.

natVendorId Use this element to determine which vendor identifi-cation string is exchanged with the remote in order to detect NAT support.

proposal Use this element to configure the IKE proposal. A pro-posal is a list of IKE attributes to protect the IKE con-nection between the IKE host and its peer.

Refer to telindus1423Router/ip/router/ikeSA[ ]/phase2/proposal on page 176 for a detailed description of the proposal structure.




Default:rfc3947Range: rfc3947 / draft




176

telindus1423Router/ip/router/ikeSA[ ]/phase2/proposal

Use the proposal structure in the phase2 structure to configure the IKE pro-posal. A proposal is a list of IKE attributes to protect the IKE connection between the IKE host and its peer.

The proposal structure contains the following elements:

Element Description

espEncryptionAlgo-rithm

Use this element to select the IPSEC encryption algo-rithm (in case of ESP).

The espEncryptionAlgorithm element has the following values:

• null: No encryption is done.The null encryption algorithm is simply a convenient way to represent the optional use of applying encryption within ESP. ESP can then be used to pro-vide authentication and integrity without confidentiality.

• des: DES (56 bits) is used to encrypt / decrypt the data.• 3des: Triple DES (168 bits) is used to encrypt / decrypt the data.• disabled: No encryption is done.

Make sure that for the same security association on both the local and remote router the same encryption algorithm is selected.

espAuthentication-Algorithm

Use this element to select the IPSEC authentication algorithm (in case of ESP).

The epsAuthenticationAlgorithm element has the following values:

• hmac_md5: The MD5 hash function is used to authenticate the data.• hmac_sha-1: The SHA-1 hash function is used to authenticate the data.• disabled: No authentication is done.


ahAuthenticationAl-gorithm

Use this element to select the IPSEC authentication algorithm (in case of AH).

The ahAuthenticationAlgorithm element has the following values:

• hmac_md5: The MD5 hash function is used to authenticate the data.• hmac_sha-1: The SHA-1 hash function is used to authenticate the data.• disabled: No authentication is done.




Default:hmac_md5Range: enumerated, see below




177

lifeTime Use this element to set the life time of the IPSEC SA.

When the life time expires, it is replaced by a new SA (and SPI) or terminated.

The lifeTime structure contains the following elements:

• time. Use this element to set the life time, in sec-onds, of the IPSEC SA.

• kBytes. Use this element to set the life time, in kilo-bytes, of the IPSEC SA.

As soon as one of the two criteria is exceeded (i.e. either the time or the number of kilobytes), the IPSEC SA is timed out.

Element Description



Default:4250000Range: 2500 … 4250000



178

MR-1.12.6 OSPF configuration attributes

This section discusses the configuration attributes concerned with OSPF. First it describes the general OSPF configuration attributes. Then it explains the OSPF area configuration attributes.


• General OSPF configuration attributes on page 179• Area configuration attributes on page 183



179

General OSPF configuration attributes


• telindus1423Router/ip/router/ospf/routerId on page 180• telindus1423Router/ip/router/ospf/refBandwidth on page 180• telindus1423Router/ip/router/ospf/keyChains on page 180• telindus1423Router/ip/router/ospf/importMetrics on page 181• telindus1423Router/ip/router/ospf/importFilter on page 182



180

²v

telindus1423Router/ip/router/ospf/routerId

Use this attribute to set the unique sequence number for the router in the OSPF network.

telindus1423Router/ip/router/ospf/refBandwidth

Use this attribute to set the reference bandwidth. It is used to calculate the cost of an interface in OSPF. Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information about cost.

telindus1423Router/ip/router/ospf/keyChains

Use this attribute to set the key chains that will be used in the MD-5 authen-tication process. For more information on authentication, refer to …

• MU-8.6.3 - Activation de l'authentification OSPF on page 227• telindus1423Router/ip/router/ospf/area[ ]/networks/authentication on page 188• telindus1423Router/ip/router/ospf/area[ ]/virtualLinks/authentication on page 190

The keyChains table contains the following elements:

Element Description

name Use this element to assign an administrative name to the key chain.

chain Use this element to set the properties of each key chain.

Refer to telindus1423Router/ip/router/ospf/keyChains/chain on page 181 for a detailed description of this element.


Default:100000 bpsRange: 0 … 2147483647


Default:chainRange: 0 … 24 characters




181

telindus1423Router/ip/router/ospf/keyChains/chain

The chain table contains the following elements:

telindus1423Router/ip/router/ospf/importMetrics

Use this attribute to configure the default cost for importing RIP and static routes into OSPF.

The importMetrics structure contains following elements:

Element Description

keyId Use this element to set a unique identifier for each secret.

secret Use this element to define the secret.

sendDate Use this element to set the start date from which the secret is allowed to be sent. Enter the date as argu-ment value in the format dd/mm/yy (e.g. 01/01/05)

sendTime Use this element to set the time from which the secret is allowed to be sent. Enter the time as argument value in the format hh:mm:ss (e.g. 12:30:45).

sendDuration Use this element to set the period of time during which the secret is allowed to be sent.

acceptDate Use this element to set the start date from which the secret is allowed to be accepted by the other routers in the OSPF network. Enter the date as argument value in the format dd/mm/yy (e.g. 01/01/05)

acceptTime Use this element to set the time from which the secret is allowed to be accepted by the other routers in the OSPF network. Enter the time as argument value in the format hh:mm:ss (e.g. 12:30:45).

acceptDuration Use this element to set the period of time during which the secret is allowed to be accepted by the other rout-ers in the OSPF network. Enter this value in seconds.

Element Description

static Use this element to set the default cost of a static route which will be imported into OSPF.

rip Use this element to set the default cost of a RIP route which will be imported into OSPF.




Default:01/01/01Range: 01/01/01 … 31/12/99

Default:00:00:00Range: 00:00:00 … 23:59:59


24855d 03h 14m 07s

Default:01/01/01Range: 01/01/01 … 31/12/99

Default:00:00:00Range: 00:00:00 … 23:59:59


24855d 03h 14m 07s


Default:20Range: 0 … 2147483647

Default:20Range: 0 … 2147483647



182

telindus1423Router/ip/router/ospf/importFilter

Use this attribute to configure the import filter which allows or denies the import of external routes into OSPF.

The importFilter table contains following elements:

Element Description

type Use this element to select the type of routes which will be allowed or denied into OSPF.

Whether a route is allowed into OSPF or denied access to OSPF, is set by the ele-ment mode which is described further on in this table.


• all. All routes are allowed into OSPF / denied access to OSPF.• static. Static routes are allowed into OSPF / denied access to OSPF.• rip. Rip routes are allowed into OSPF / denied access to OSPF.

address Use this element to set the IP address the external route has to comply to.

mask Use this element to set the netmask the external route has to comply to.

Address and mask define the address range the external route has to comply to.

mode Use this element to allow or deny the import of exter-nal routes into OSPF.

costType Use this element to set the type of cost of the external route.

The costType element has the following values:

• type1. The external cost is expressed in the same units as OSPF interface cost (i.e. in terms of the link state metric).

• type2. The external cost is an order of magnitude larger; any type 2 cost is con-sidered greater than the cost of any path internal to the OSPF routing domain. Use of type 2 external cost assumes that routing outside the OSPF domain is the major cost of routing a packet, and eliminates the need for conversion of external costs to internal link state costs.

cost Use this element to set the cost of the external route.

tag Each external route can be tagged, enabling the passing of additional information between AS bound-ary routers.


Default:allRange: static / rip / all



Default:allowRange: deny / allow

Default:type2Range: type1 / type2





183

Area configuration attributes


• telindus1423Router/ip/router/ospf/area[ ]/areaId on page 184• telindus1423Router/ip/router/ospf/area[ ]/stub on page 184• telindus1423Router/ip/router/ospf/area[ ]/networks on page 186• telindus1423Router/ip/router/ospf/area[ ]/virtualLinks on page 189• telindus1423Router/ip/router/ospf/area[ ]/ranges on page 191




184

telindus1423Router/ip/router/ospf/area[ ]/areaId

Use this attribute to set the unique sequence number for the area. The back bone area must always be area 0.

telindus1423Router/ip/router/ospf/area[ ]/stub

Use this attribute to define an area as a stub area. Refer to MU-8.6.1 - Intro-duction à OSPF on page 220 for the definition of a stub area.

The stub structure contains the following elements:

Element Description

mode Use this element to enable or disable the area as a stub area.

defaultCost Use this element to assign a default cost to the area. This is the cost of the default route of the area.

importSummaries Use this element to enable or disable the import of summary links into the stub area.

When this attribute is disabled, only the default route will be injected into the area (by the Area Border Router). When it is enabled, also the summary links are injected into the area.

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for the definition of a sum-mary link.

translatorRole Use this element to specify whether or not the Telin-dus 1423 SHDSL Router will unconditionally translate Type-7 LSAs into Type-5 LSAs.

The translatorRole element has the following values:

• always. The Telindus 1423 SHDSL Router always translates Type-7 LSAs into Type-5 LSAs regardless of the translator state of other NSSA border routers.

• candidate. The Telindus 1423 SHDSL Router participates in the translator elec-tion process. I.e. only one NSSA border router is elected as Type-7 translator among all the NSSA border routers that were set as candidate.





Default:enabledRange: disabled / enabled

Default:candidateRange: candidate / always



185

translatorInterval Use this element to define the length of time the Tel-indus 1423 SHDSL Router, if it is an elected Type-7 translator, will continue to perform its translator duties once it has determined that its translator status has been deposed by another NSSA border router translator.

If an NSSA border router is elected as Type-7 translator among all the NSSA bor-der routers that were set as candidate, then it will continue to perform translation duties until supplanted by a reachable NSSA border router whose Nt bit is set or whose router ID is greater. Such an event may happen when an NSSA router with translatorRole set to always regains border router status, or when a partitioned NSSA becomes whole. If an elected translator determines its services are no longer required, it continues to perform its translation duties for the additional time interval defined by the translatorInterval. This minimizes excessive flushing of translated Type-7 LSAs and provides for a more stable translator transition.

Element Description


00000d 18h 12m 15s



186

telindus1423Router/ip/router/ospf/area[ ]/networks

Use this attribute to identify the interfaces which are part of the area.

The networks table contains following elements:

Element Description

name Use this element to assign an administrative name to a network.

address Use this element to specify the IP address of the net-work.

mask Use this element to specify the IP address mask of the attached network (Network Mask).

Address and mask define the network address to select the interfaces that will be part of the OSPF network (with the OSPF parameters defined in this net-work).

cost Use this element to specify the cost of the link. When the cost is set to 0, the actual cost is calculated auto-matically.

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information about cost.

priority Use this element to set the priority of the link. On the basis of this element, the designated router in the net-work is elected.

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information about designated routers.

This element is only important for broadcast networks. It must not be set for P2P links.

helloInterval Use this element to specify the length of time, in sec-onds, between the hello packets that a router sends on an OSPF interface.

OSPF requires the hello interval and dead interval to be exactly the same for all routers attached to a common network.


Default:<network>Range: 0 … 24 characters






00000d 18h 12m 15s



187

deadInterval Use this element to specify the maximum length of time, in seconds, before the neighbours declare the OSPF router down when they stop hearing the router's Hello Packets.

retransmitinterval Use this element to specify the length of time, in sec-onds, after which an hello packet is retransmitted.

authentication Use this element to authenticate OSPF packets.

OSPF packets can be authenticated so that routers can be part of routing domains based on predefined passwords. By default, a router uses a Null authentication which means that routing exchanges over a net-work are not authenticated. There are two other authentication methods: Simple Password authentication and Message Digest authentication (MD-5).

Refer to telindus1423Router/ip/router/ospf/area[ ]/networks/authentication on page 188 for a detailed description of this element.

mode Use this element to activate or disable an interface in the OSPF network.

When an interface is active it is known in the OSPF network, and will pass OSPF data through the OSPF network. When it is disabled the interface is known in the OSPF network, but OSPF data will not be passed through (e.g. if an interface is connected to the outside world using RIP, the other routers in the area will know this interface, but there is no OSPF link to the outside world).

Element Description


24855d 3h 14m 07s


00000d 00h 4m 15s


Default:activeRange: active / disabled



188

telindus1423Router/ip/router/ospf/area[ ]/networks/authentication

The authentication structure contains the following elements:

Element Description

type Use this element to set the type of authentication.


• disabled. No authentication is done.• test. This allows a password (key) to be configured per interface. Interfaces of

different routers that want to exchange OSPF information will have to be con-figured with the same key.

• md5. Message Digest authentication. This is a cryptographic authentication. A key (password) and key-id are configured on each router. The router uses an algorithm based on the OSPF packet, the key, and the key-id to generate an "authentication secret" that gets added to the packet. Unlike the simple authen-tication, the key is not exchanged over the wire.

text Use this element to set the password when using text authentication.

keyChain Use this element to set the key chain which will be used in this network when using md5 authentication.


Default:disabledRange: disabled / text/ md5

Default:-Range: 0 … 8 characters




189

telindus1423Router/ip/router/ospf/area[ ]/virtualLinks

Use this attribute to set up a virtual link between the current area and a remote area which is not physically connected to the backbone area.

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information on the back bone area.

The virtual links table contains following elements:

Element Description

remoteId Use this element to set the IP address of the remote router with which the virtual link is established.

helloInterval Use this element to specify the length of time, in sec-onds, between the hello packets that a router sends on an OSPF interface.

deadInterval Use this element to specify the maximum length of time, in seconds, between the sent hello packets after which the neighbours declare the virtual link down.

retransmitinterval Use this element to specify the length of time, in sec-onds, after which an hello packet is retransmitted.

authentication Use this element to authenticate OSPF packets.

OSPF packets can be authenticated so that routers can be part of routing domains based on predefined passwords. By default, a router uses a Null authentication which means that routing exchanges over a net-work are not authenticated. There are two other authentication methods: Simple Password authentication and Message Digest authentication (MD-5).

Refer to telindus1423Router/ip/router/ospf/area[ ]/virtualLinks/authentication on page 190 for more information.




00000d 18h 12m 15s


24855d 3h 14m 07s


00000d 00h 4m 15s




190

telindus1423Router/ip/router/ospf/area[ ]/virtualLinks/authentication

The authentication structure contains the following elements:

Element Description

type Use this element to set the type of authentication.


• disabled. No authentication is done.• test. This allows a password (key) to be configured per interface. Interfaces of

different routers that want to exchange OSPF information will have to be con-figured with the same key.

• md5. Message Digest authentication. This is a cryptographic authentication. A key (password) and key-id are configured on each router. The router uses an algorithm based on the OSPF packet, the key, and the key-id to generate an "authentication secret" that gets added to the packet. Unlike the simple authen-tication, the key is not exchanged over the wire.

text Use this element to set the password when using text authentication.

keyChain Use this element to set the key chain which will be used in the virtual link when using md5 authentication.


Default:disabledRange: disabled / text/ md5

Default:--Range: 0 … 8 characters




191

telindus1423Router/ip/router/ospf/area[ ]/ranges

By defining ranges in an area, Summary-LSAs can be condensed before being injected in an other area (by defining a larger subnet mask).

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information about Summary-LSAs.

Each address range is defined as an address-mask pair. Many separate networks may then be con-tained in a single address range, just as a subnetted network is composed of many separate subnets. Area border routers then summarize the area contents (for distribution to the backbone) by advertising a single route for each address range. The cost of the route is the maximum cost to any of the networks falling in the specified range.

The ranges table contains following elements:

Element Description

type Use this element to set the type of Summary-LSA that has to be created.


• summary. The area's routing information is condensed.• nssa. In case of an NNSA, multiple Type-7 LSAs are aggregated into a single

Type-5 LSA.• all. Both tasks are performed.

network Use this element to set the IP address of the network.

mask Use this element to set the subnet mask.

advertise Use this element to enable or disable the advertise-ment of the Summary-LSAs into the other areas.

When this element is disabled, the Summary-LSAs which are part of this range, will not be known in the other area’s in the OSPF network. When this element is enabled, the summaries are injected in the other areas of the OSPF network.

tag This element is only relevant in case of NSSAs.

Use this element to retag the summary of the external routes entering the NSSA.


Default:allRange: enumerated, see below







192

MR-1.12.7 Routing filter configuration attributes


• telindus1423Router/ip/router/routingFilter[ ]/filter on page 193




193

telindus1423Router/ip/router/routingFilter[ ]/filter

Use this attribute to set up a routing update filter.

Only the routes to networks that are specified in the filter table are forwarded. All other routes are blocked. If the filter table is empty, then all routes are forwarded.

The filter table contains the following elements:

Currently, the Telindus 1423 SHDSL Router supports up to 5 routing update filters. Although you can add more than 5 routingFilter[ ] objects to the containment tree, no more than 5 will be active.

Example

This example shows a filter that only forwards the route to subnet 192.168.48.0.

Element Description

network This is the IP address of the network. The address may be a (sub-)network address. It should match an entry in the telindus1423Router/ip/router/routingTable status attribute of the Telindus 1423 SHDSL Router.

mask This is the IP subnet mask of the network. By combin-ing an IP address with a mask you can uniquely iden-tify a range of addresses.






194

MR-1.12.8 VRRP configuration attributes


• telindus1423Router/ip/router/vrrp[ ]/vrId on page 195• telindus1423Router/ip/router/vrrp[ ]/ipAddresses on page 195• telindus1423Router/ip/router/vrrp[ ]/interfaces on page 196• telindus1423Router/ip/router/vrrp[ ]/criticals on page 196• telindus1423Router/ip/router/vrrp[ ]/advertiseInterval on page 197• telindus1423Router/ip/router/vrrp[ ]/preemptMode on page 197




195

telindus1423Router/ip/router/vrrp[ ]/vrId

Use this attribute to set the identification of the virtual router. Specify a number between 1 and 255. The VRID has to be set the same on all participating routers.

Setting the vrId to 0 (default) disables this virtual router instance.

telindus1423Router/ip/router/vrrp[ ]/ipAddresses

Use this attribute to configure one or more IP addresses on the virtual router.

The ipAddresses table contains the following element:

It is important that all VRRP routers have a physical interface configured with an IP address in the same subnet as the virtual router. The VRRP protocol sends only IP addresses and not subnet information. Without the corresponding subnet information, the VRRP router will add the virtual router address as a single IP address with a host (255.255.255.255) netmask. This will prevent routing from working prop-erly, as the virtual router will not listen to broadcasts from the local network.

Element Description

address Use this element to configure the IP address of the vir-tual router. This address must be the same on all rout-ers participating in this virtual router.

By adding several IP addresses, several IP addresses can be configured on a sin-gle virtual router. This can be used to ensure redundancy while migrating from one address scheme to another. It cannot be used for load balancing purposes, in this case multiple virtual routers must be used.

If no IP address is configured, this virtual router instance is not active.






196

telindus1423Router/ip/router/vrrp[ ]/interfaces

Use this attribute to add Ethernet-alike interfaces7 to the virtual router and assign a priority to them. This priority is used in the master virtual router election process.

The interfaces table contains the following element:

telindus1423Router/ip/router/vrrp[ ]/criticals

Use this attribute to specify which interfaces must be up before a router may be elected as master virtual router.

The criticals table contains the following element:

7. Ethernet-alike interfaces are e.g. an Ethernet interface, a VLAN on an Ethernet interface, a bridge group, a VLAN on a bridge group, etc.

Element Description

name Use this element to specify the name of the interface that you want to add to the virtual router.

priority Use this element to specify the priority of the interface. Specify a number between 1 and 254. The higher the number, the higher the priority.

The numbers 0 and 255 are reserved numbers and cannot be set by the user:

• 0 specifies that the master has stopped working and that the backup router needs to transition to master state.

• 255 specifies that the VRRP router is the IP address owner and therefore is master, independently from the priority settings.

Refer to MU-8.9.1 - Introduction VRRP on page 271 for more information on how the priority plays a role in the election of a master virtual router.

Element Description

name Use this element to specify the name of the interface that must be up before the router may be elected as master.

So as soon as an interface that is defined in the criticals table goes down, the com-plete router is considered to be down (on VRRP level that is). In that case, a new master has to be elected. So this adds an extra condition to the election process as shown in Comment le routeur virtuel maître est-il choisi ? on page 272.








197

telindus1423Router/ip/router/vrrp[ ]/advertiseInterval

Use this attribute to set the time between VRRP advertisement transmis-sions.

Actually, only the master virtual router sends VRRP advertisements. However, the advertisement inter-val has to be set the same on all participating routers.

telindus1423Router/ip/router/vrrp[ ]/preemptMode

Use this attribute to allow a backup virtual router to take over from the mas-ter virtual router in case the backup virtual router has a higher priority on the enclosing virtual router.

The preemptMode attribute has the following values:

While preemption can ensure that a primary router will return to master status once it returns to service, preemption also causes a brief outage while the election process takes place. Disabling preemption will ensure maximum up-time on the network, but will not always result in the primary or highest priority router acting as master.

Note that, regardless of the setting of the preemptMode attribute, the VRRP IP address owner will always preempt.

Value Description

enabled If after a router is elected as master a backup appears which has a higher priority than the master, then the backup begins to send its own advertisements. The cur-rent master will see that the backup has higher priority and stop functioning as the master. The backup will then see that the master has stopped sending advertise-ments and assume the role of master.

disabled Once a router is elected as master, it stays master until it goes down. So the appearance of a backup with a higher priority after the master has been elected does not cause a new election process.


00000d 18h 12m 15s




198

MR-1.12.9 Firewall configuration attributes


• telindus1423Router/ip/router/firewall/inspection on page 199• telindus1423Router/ip/router/firewall/outboundPolicies on page 199• telindus1423Router/ip/router/firewall/inboundPolicies on page 204• telindus1423Router/ip/router/firewall/outboundSelfPolicies on page 209• telindus1423Router/ip/router/firewall/inboundSelfPolicies on page 213• telindus1423Router/ip/router/firewall/attacks on page 217• telindus1423Router/ip/router/firewall/log on page 219



199

telindus1423Router/ip/router/firewall/inspection

Use this attribute to enable or disable the firewall.

telindus1423Router/ip/router/firewall/outboundPolicies

Use this attribute to define outbound SNet policies. Refer to MU-10.9.4 - Définition d’une politique SNet sortante on page 407 for more information.

The outboundPolicies table contains the following elements:

Element Description

sNet Use this element to specify the name of the source SNet for which you want to create an outbound SNet policy.

The sNet element is a choice element. The first part of the sNet element has the fol-lowing values:

• name. Select this value if the source SNet is one of the standard SNets. In the second part of the sNet element, use the drop-down box to select one of the standard SNets:- corp. The source SNet is “corporate”. If you select this

value, then you create a policy for the traffic from the corporate SNet to any SNet except the self SNet.

- dmz. The source SNet is “DMZ”. If you select this value, then you create a policy for the traffic from the DMZ SNet to any SNet except the self SNet.

• custom. Currently, you can only select standard SNets. In future releases of the TDRE, it will be possible to select custom created SNets.

Note that you only have to set the source SNet. The destination SNet is always any SNet except the self SNet.



Default:<name> corpRange: choice, see below

Default:corpRange: corp / dmz




200

sourceIp Use this element to specify the source IP address(es) for which you want to create an outbound SNet policy.

The sourceIp element is a choice element. The first part of the sourceIp element has the following values:

• network. Select this value if you want to create a pol-icy for the traffic coming from a specific network. In the second part of the sourceIp element, specify the address of that network.The network structure contains the following ele-ments:- address. Use this element to specify the IP

address of the network.- netmask. Use this element to specify the net-

mask of the network.

• custom. Select this value if you want to create a policy for the traffic coming from a specific (range of) IP address(es). In the second part of the sourceIp element, specify the IP address (range).The custom structure contains the following ele-ments:- startAddress. Use this element to specify the start

of the source IP address range.- endAddress. Use this element to specify the end

of the source IP address range.Note that you can specify one single source IP address by filling in the startAddress element and leaving the endAddress ele-ment at its default value (<opt>).

Note that if you leave the sourceIp element at its default value (<opt>), then no source IP address(es) is/are specified.

Element Description

Default:<opt>Range: choice, see below







201

destIp Use this element to specify the destination IP address(es) for which you want to create an outbound SNet policy.

The destIp element is a choice element. The first part of the destIp element has the following values:

• network. Select this value if you want to create a pol-icy for the traffic destined for a specific network. In the second part of the destIp element, specify the address of that network.The network structure contains the following ele-ments:- address. Use this element to specify the IP



• custom. Select this value if you want to create a policy for the traffic destined for a specific (range of) IP address(es). In the second part of the destIp element, specify the IP address (range).The custom structure contains the following ele-ments:- startAddress. Use this element to specify the start

of the destination IP address range.- endAddress. Use this element to specify the end

of the destination IP address range.Note that you can specify one single destina-tion IP address by filling in the startAddress element and leaving the endAddress element at its default value (<opt>).

Note that if you leave the destIp element at its default value (<opt>), then no destination IP address(es) is/are specified.

Element Description








202

application Use this element to specify the application for which you want to create an outbound SNet policy.

The application element is a choice element. Currently, the first part of the application element is always custom. The custom structure contains the following elements:

• protocol. Use this element to specify the protocol. The protocol element has the following values: any, icmp, tcp, udp, ah, esp.Note that if you leave the protocol element at its default value (any), then no pro-tocol is specified.

• startPort. Use this element to specify the start of the port range. Specify the port by typing the port number. For ease of use, some common port num-bers can be selected from a drop-down box.Note that if you leave the port element at its default value (any), then no port is specified.

• endPort. Use this element to specify the end of the port range. Specify the port by typing the port number. For ease of use, some common port num-bers can be selected from a drop-down box.Note that you can specify one single port by filling in the startPort element and leaving the endPort element at its default value (<opt>).

Note that if you leave the application element at its default value (<opt>), then no application is specified.

action Use this element to determine whether the outbound SNet policy allows or denies traffic.


• allow. Packets that fall within the specification of the policy are passed on.• deny. Packets that fall within the specification of the policy are dropped.

Element Description


Default:anyRange: enumerated, see below

Default:0 (any)Range: 0 … 65535


Default:allowRange: allow / deny



203

nat Use this element to determine whether address trans-lation has to be done for the outbound SNet policy and, if so, which translation address has to be taken.

The nat element is a choice element. The first part of the nat element has the fol-lowing values:

• ipAddress. Select this value if you want to specify a fixed IP address for the address translation. In the second part of the nat element, specify the IP address.

• interface. Select this value if you want to that the IP address that is used for the address translation is taken from another interface. In the second part of the nat element, specify the name of the interface.

Note that if you leave the nat element at its default value (<opt>), then no address translation is done.

Important remark

If you want to enable NAT on an interface but you also want that the inter-face is inspected by the firewall, then enable NAT in the policies of the firewall and not in the ip structure of the interface.

log Use this element to determine whether limited (disa-bled) or extended (enabled) logging is done for this pol-icy.

name Use this element to assign a name (description) to the outbound SNet policy. By doing so, you can easily identify the policy when it is listed in status and per-formance tables.

Element Description








204

telindus1423Router/ip/router/firewall/inboundPolicies

Use this attribute to define inbound SNet policies. Refer to MU-10.9.5 - Déf-inition d’une politique SNet entrante on page 410 for more information.

The inboundPolicies table contains the following elements:

Element Description

sNet Use this element to specify the name of the destina-tion SNet for which you want to create an inbound SNet policy.


• name. Select this value if the destination SNet is one of the standard SNets. In the second part of the sNet element, use the drop-down box to select one of the standard SNets:- corp. The destination SNet is “corporate”. If you select

this value, then you create a policy for the traffic from any SNet except the self SNet to the corporate SNet.

- dmz. The destination SNet is “DMZ”. If you select this value, then you create a policy for the traffic from any SNet except the self SNet to the DMZ SNet.


Note that you only have to set the destination SNet. The source SNet is always any SNet except the self SNet.







205

sourceIp Use this element to specify the source IP address(es) for which you want to create an inbound SNet policy.









Element Description








206

destIp Use this element to specify the destination IP address(es) for which you want to create an inbound SNet policy.









Element Description








207

application Use this element to specify the application for which you want to create an inbound SNet policy.






action Use this element to determine whether the inbound SNet policy allows or denies traffic.



Element Description








208

nat Use this element to determine whether address trans-lation has to be done for the inbound SNet policy and, if so, which translation address has to be taken.

The nat element is a choice element. Currently, the first part of the nat element is always custom. The custom structure contains the following elements:

• ipAddress. Use this element to specify the IP address of the server that will handle the applica-tion specified in the policy.

• port. Use this element to specify the new port number.Note that if you leave the port element at its default value (<opt>), then no port translation is done.

Note that if you leave the nat element at its default value (<opt>), then no address translation is done.

Important remark

If you want to enable NAT on an interface but you also want that the inter-face is inspected by the firewall, then enable NAT in the policies of the firewall and not in the ip structure of the interface.


name Use this element to assign a name (description) to the inbound SNet policy. By doing so, you can easily iden-tify the policy when it is listed in status and perform-ance tables.

Element Description








209

telindus1423Router/ip/router/firewall/outboundSelfPolicies

Use this attribute to define outbound self policies. Refer to MU-10.9.6 - Déf-inition d’une politique self sortante on page 413 for more information.

The outboundSelfPolicies table contains the following elements:

Element Description

sNet Use this element to specify the name of the destina-tion SNet for which you want to create an outbound self policy.


• name. Select this value if the destination SNet is one of the standard SNets. In the second part of the sNet element, use the drop-down box to select one of the standard SNets:- corp. The destination SNet is “corporate”. If you select

this value, then you create a policy for the traffic from the device itself (self SNet) to the corporate SNet.

- dmz. The destination SNet is “DMZ”. If you select this value, then you create a policy for the traffic from the device itself (self SNet) to the DMZ SNet.

- internet. The destination SNet is “internet”. If you select this value, then you create a policy for the traffic from the device itself (self SNet) to the internet SNet.


Note that you only have to set the destination SNet. The source SNet is always the self SNet.







210

sourceIp Use this element to specify the source IP address(es) for which you want to create an outbound self policy.









Element Description








211

destIp Use this element to specify the destination IP address(es) for which you want to create an outbound self policy.









Element Description








212

application Use this element to specify the application for which you want to create an outbound self policy.






action Use this element to determine whether the outbound self policy allows or denies traffic.




name Use this element to assign a name (description) to the outbound self policy. By doing so, you can easily iden-tify the policy when it is listed in status and perform-ance tables.

Element Description










213

telindus1423Router/ip/router/firewall/inboundSelfPolicies

Use this attribute to define inbound self policies. Refer to MU-10.9.4 - Défi-nition d’une politique SNet sortante on page 407 for more information.

The inboundSelfPolicies table contains the following elements:

Element Description

sNet Use this element to specify the name of the source SNet for which you want to create an inbound self pol-icy.


• name. Select this value if the source SNet is one of the standard SNets. In the second part of the sNet element, use the drop-down box to select one of the standard SNets:- corp. The source SNet is “corporate”. If you select this

value, then you create a policy for the traffic from the corporate SNet to the device itself (self SNet).

- dmz. The source SNet is “DMZ”. If you select this value, then you create a policy for the traffic from the DMZ SNet to the device itself (self SNet).

- internet. The source SNet is “internet”. If you select this value, then you create a policy for the traffic from the internet SNet to the device itself (self SNet).


Note that you only have to set the source SNet. The destination SNet is always the self SNet.







214

sourceIp Use this element to specify the source IP address(es) for which you want to create an inbound self policy.









Element Description








215

destIp Use this element to specify the destination IP address(es) for which you want to create an inbound self policy.









Element Description








216

application Use this element to specify the application for which you want to create an inbound self policy.






action Use this element to determine whether the inbound self policy allows or denies traffic.




name Use this element to assign a name (description) to the inbound self policy. By doing so, you can easily iden-tify the policy when it is listed in status and perform-ance tables.

Element Description










217

telindus1423Router/ip/router/firewall/attacks

Use this attribute to determine, per type of attack, whether the firewall has to check for this type of attack and neutralise it.

The attacks structure contains the following elements:

Element Description

synFlooding Use this element to enable or disable the detection and neutralisation of the SYN Flooding attack. Refer to Qu'est-ce que l'attaque SYN Flooding ? on page 401.

If you set the synFlooding element to enabled, then the firewall filters out forged serv-ice requests while allowing legitimate requests to pass through.

sourceRouting Use this element to enable or disable the detection and neutralisation of Source Routing attack. Refer to Qu’est-ce qu’une attaque Source Routing ? on page 401.

If you set the sourceRouting element to enabled, then the firewall filters out all data-grams with strict or loose source routing option enabled.

winNuke Use this element to enable or disable the detection and neutralisation of the WinNuke attack. Refer to Qu'est-ce que l'attaque WinNuke ? on page 402.

If you set the winNuke element to enabled, then the firewall filters out this attack.

ftpBounce Use this element to enable or disable the detection and neutralisation of the FTP Bounce attack. Refer to Qu'est-ce que l'attaque FTP Bounce ? on page 402.

If you set the ftpBounce element to enabled, then the firewall checks that the data con-nection is to the same system as that of the control connection.

ipUnalignedTimeS-tamp

Use this element to enable or disable the detection and neutralisation of the IP Unaligned Timestamp attack. Refer to Qu'est-ce que l'attaque IP Unaligned Timestamp ? on page 402.

If you set the ipUnalignedTimeStamp element to enabled, then the firewall checks whether the IP packets received have the timestamp option set. If so, it checks that it is aligned on a 32-bit boundary and drops the packet if it is not.









218

mime Use this element to enable or disable the detection and neutralisation of the MIME attack. Refer to Qu'est-ce que l'attaque MIME ? on page 402.

By configuring the mime structure, you can close the connection if the number of received MIME headers exceeds the number of MIME headers you configured.

The mime structure contains the following elements:

• flood. Use this element to enable or disable the detection and neutralisation of the MIME attack.

• maxHeaderLength. Use this element to determine the maximum length of the MIME header that may be included in the HTTP request.

• maxHeaders. Use this element to determine the maximum number of MIME headers that may be included in the HTTP request.

seqNumPrediction Use this element to enable or disable the detection and neutralisation of the Sequence Number Predic-tion attack. Refer to Qu’est-ce que l’attaque Sequence Number Prediction ? on page 402.

If you set the seqNumPrediction element to enabled, then the firewall manipulates the initial sequence number with a new sequence number generated by the firewall making it difficult to guess the sequence number for the attacker.

seqNumOutOf-Range

Use this element to enable or disable the detection and neutralisation of the Sequence Number Out Of Range attack. Refer to Qu’est-ce que l’attaque Sequence Number Out Of Range ? on page 402.

If you set the seqNumOutOfRange element to enabled, then the firewall drops the pack-ets with sequence numbers that are out of range.

icmpErrorMessages Use this element to enable or disable the detection and neutralisation of the ICMP Error Message attack. Refer to Qu'est-ce que l'attaque ICMP Error Message ? on page 402.

If you set the icmpErrorMessages element to enabled, then the firewall drops ICMP error packets with a destination different from the internet SNet.

Element Description










219

telindus1423Router/ip/router/firewall/log

Use this attribute to enable or disable logging and to determine what is logged.

The log structure contains the following elements:

Element Description

mode Use this element to enable or disable logging.

The log information can be checked in the log status attribute. Refer to telindus1423Router/ip/router/firewall/log on page 376.

attacks Use this element to enable or disable, per type of attack, whether it is logged or not.

The attacks structure contains the following elements:

• synFlooding. Use this element to enable or disable the logging of a SYN Flooding attack. Refer to Qu'est-ce que l'attaque SYN Flooding ? on page 401.

• pingOfDeath. Use this element to enable or disable the logging of a Ping Of Death attack. Refer to Qu’est-ce qu’une attaque Ping Of Death ? on page 403.

• ipSpoofing. Use this element to enable or disable the logging of an IP Spoofing attack. Refer to Qu'est-ce que l'attaque IP Spoofing ? on page 403.

• winNuke. Use this element to enable or disable the logging of a WinNuke attack. Refer to Qu'est-ce que l'attaque WinNuke ? on page 402.

• ipOptionAttack. Use this element to enable or disable the logging of an IP Option attack. Refer to Qu'est-ce que l'attaque IP Option ? on page 403.

All these attacks are logged with the priority “alert”.











220

general Use this element to enable or disable some general loggings.

The general structure contains the following elements:

• systemErrorMessages. Use this element to enable or disable the logging of system error messages. E.g. memory allocation problems, module initialisation problems, resource allocation problems. This is logged with the priority “notice”.

• denyPolicies. Use this element to enable or disable the logging of deny policies. I.e. a policy of which the action is set to “deny”. This is logged with the pri-ority “alert”.Note that this is only logged if for this policy, the log element is set to enabled.

• allowPolicies. Use this element to enable or disable the logging of allow policies. I.e. a policy of which the action is set to “allow”. This is logged with the pri-ority “info”.Note that this is only logged if for this policy, the log element is set to enabled.

• dataInspection. Use this element to enable or disable the logging of data that is not allowed. E.g. due to memory allocation problems, buffer limits, invalid requests. This is logged with the priority “warning”.

• generalAttacks. Use this element to enable or disable the general logging of attacks. You can then spec-ify per attack whether it is logged or not. Refer to the attacks element. This is logged with the priority “alert”.

• unavailablePolicies. Use this element to enable or dis-able the logging of unavailable policies. I.e. when no matching policy could be found. This is logged with the priority “warning”.

• accessStatistics. Use this element to enable or disa-ble the logging of access statistics. E.g. logs about connection termination, closing, time-out, trans-ferred bytes. This is logged with the priority “info”.Note that this is only logged if for this policy, the log element is set to enabled.

• verbose. Use this element to enable or disable the logging of ICMP messages, DNS requests and replies. This is logged with the priority “info”.

Element Description












221

thresholds Use this element to set the threshold to trigger the log-ging. The threshold is set per log entry type, except for denyPolicies and allowPolicies. In that case the threshold is set per policy.

Logging thresholds are provided so that the logging system does not get flooded with a huge number of duplicate logs in case the firewall or the corporate network connected to it is under attack.

The thresholds structure contains the following elements:

• attack. Use this element to determine the number of attacks that should occur before they are logged.

• general. Use this element to determine the number of general events that should occur before they are logged.

tableLength Use this element to set the length of the log table.

Note that changing this value clears the table.

Element Description







222

MR-1.13 Bridge configuration attributes

This section discusses the configuration attributes concerned with bridging. First it describes the general bridging configuration attributes. Then it explains the configuration attributes of the extra features as there are access listing, user priority mapping, etc…


• MR-1.13.1 - Bridge group configuration attributes on page 223• MR-1.13.2 - Bridge access list configuration attributes on page 233



223

MR-1.13.1 Bridge group configuration attributes


• telindus1423Router/bridge/bridgeGroup/name on page 224• telindus1423Router/bridge/bridgeGroup/ip on page 224• telindus1423Router/bridge/bridgeGroup/arp on page 224• telindus1423Router/bridge/bridgeGroup/bridgeCache on page 225• telindus1423Router/bridge/bridgeGroup/bridgeTimeOut on page 226• telindus1423Router/bridge/bridgeGroup/spanningTree on page 226• telindus1423Router/bridge/bridgeGroup/localAccess on page 227• telindus1423Router/bridge/bridgeGroup/macAddress on page 228• telindus1423Router/bridge/bridgeGroup/vlan on page 229• telindus1423Router/bridge/bridgeGroup/vlanSwitching on page 231



224

telindus1423Router/bridge/bridgeGroup/name

Use this attribute to assign an administrative name to the bridge.

This attribute is only present on the default bridge group (bridgeGroup), not on the user instantiatable bridge groups (vpnBridgeGroup[ ]). The user instantiatable bridge groups their name is the index name that you have to specify when you add the bridge group object to the containment tree (refer to MU-9.2.3 - Ajout d'un groupe de pontage on page 292).

telindus1423Router/bridge/bridgeGroup/ip

Use this attribute to configure the IP related parameters of the bridge.

Refer to …



Important remark

If you set the configuration attribute telindus1423Router/lanInterface/mode to bridging, then the settings of the configuration attribute telindus1423Router/lanInterface/ip are ignored. As a result, if you want to manage the Telindus 1423 SHDSL Router via IP, you have to configure an IP address in the bridgeGroup object instead: telindus1423Router/bridge/bridgeGroup/ip.

telindus1423Router/bridge/bridgeGroup/arp

Use this attribute to configure the Address Resolution Protocol (ARP) cache of the bridge.

Refer to telindus1423Router/lanInterface/arp on page 22 for a detailed description of the arp structure.

Default:bridgeRange: 1 … 24 characters





225

telindus1423Router/bridge/bridgeGroup/bridgeCache

Use this attribute to determine how the bridge group should act: as a repeater, a filter or a switch.

The bridgeCache attribute has the following values:

What is the bridge cache?

Whereas the ARP cache keeps MAC address - IP address pairs, the bridge cache (also called address database) keeps MAC address - interface pairs. This allows the bridge to know which device is reacha-ble through which interface. Refer to telindus1423Router/bridge/bridgeGroup/bridgeCache on page 380 for an example of such a table.

Value Description

disabled The bridge group acts as a repeater.

All the data which origi-nates from network 1 will be let through to network 2. Even if the data is not destined for that network.

learning The bridge group acts as a filter.

Data coming from network 1, will only be let through by the bridge if this data has a destination outside network 1 or if it has a broadcast or multicast address. This means the bridge filters the data and decreases the amount of data traffic on the separated LAN segments.

switching The bridge group acts as a VLAN switch.

VLANs on network 1 are switched to VLANs on network 2. Use the vlanSwitching attribute to specify which VLANs you want to switch. Refer to …

• telindus1423Router/bridge/bridgeGroup/vlanSwitching on page 231• MU-10.3.4 - Configuration de la commutation VLAN on page 331

Default:learningRange: enumerated, see below



226

telindus1423Router/bridge/bridgeGroup/bridgeTimeOut

Use this attribute to set the ageing time of the bridge cache entries.

The bridge cache time-out

If devices on the network are (re)moved then the MAC address - interface relation changes (refer to What is the bridge cache?). Therefore, the bridge cache entries are automatically removed from the cache after a fixed time-out. This time-out period can be set with the bridgeTimeOut attribute. This in case no topology change is detected, otherwise the time-out is equal to the value of the bridgeForwardDelay ele-ment of the spanningTree attribute.

When checking the bridgeCache it may appear that some entries are present for a longer time than is con-figured with the bridgeTimeOut attribute. This because the entries in the bridgeCache are not monitored con-tinuously, but once per minute. As a result, some entries may appear to be “overtime”. However, this should be no more than ± 75 seconds.

telindus1423Router/bridge/bridgeGroup/spanningTree

Use this attribute to configure the bridging related parameters.

Whereas the bridging attribute groups the bridging related parameters per interface, the spanningTree attribute groups the bridging related parameters of the bridge as a whole.

The spanningTree structure contains the following elements:

Element Description

protocol Use this element to select the bridging protocol.

The protocol element has the following values:

• none. The Telindus 1423 SHDSL Router uses the self-learning principle.This means that the bridge itself learns which data it has to forward and which data it has to block. I.e. it builds its own bridging table.

• p802.1D. The Telindus 1423 SHDSL Router uses the self-learning principle in conjunction with the Spanning Tree protocol.Because Spanning Tree bridging is somewhat more complicated than self-learning bridging, an introduction is given in MU-9.1.2 - Le pont à auto-appren-tissage et le Transparent Spanning Tree on page 280.

When using Frame Relay or ATM encapsulation on the WAN interface together with the Spanning Tree protocol, every DLCI or PVC link is consid-ered as a separate bridge port. Each link is than considered as a special

kind of LAN with only both end points connected.

Default:00000d 00h 05m 00sRange: 00000d 00h 00m 00s-

24855d 03h 14m 07s





227

telindus1423Router/bridge/bridgeGroup/localAccess

Use this attribute to allow or deny access to the bridge group itself.

The localAccess attribute has the following values:

bridgePriority Use this element to set the priority of the bridge.

The bridge its MAC address together with the bridgePriority element form a unique bridge identifier. This identifier is used to deter-mine which bridge becomes the root bridge.

The bridge with the lowest bridgePriority value becomes the root bridge. If two bridges have the same bridgePriority value, then the bridge with the lowest MAC address becomes the root bridge.

bridgeMaxAge Use this element to set the time the bridge retains bridging information before discarding it.

bridgeHelloTime Use this element to set the interval by which the root bridge sends Configuration BPDUs, also called Hello messages.

bridgeForwardDelay Use this element to set …

• the delay a bridge port applies to move from listen-ing state to learning state or from learning state to forwarding state. Refer to MU-9.1.5 - Etats des ports de pontage du Spanning Tree on page 283 for more information on the possible states of a bridge port.

• the time-out (or ageing) for purging MAC addresses from the bridge cache in case a topology change is detected.

Value Description

permitted Bridged packets can be delivered to the bridge group itself.

restricted No bridged packets can be delivered to the bridge group itself. This adds some security, because the Telindus 1423 SHDSL Router can not be accessed through the bridge group.

You could for instance create one bridge group specifically for …

• management purposes. In this bridge group, set the localAccess attribute to peri-mitted.

• the actual data coming from the customers. In this bridge group, set the localAc-cess attribute to restricted. In this way, the customer can never access the Telin-dus 1423 SHDSL Router itself.

Element Description



00000d 00h 00m 40s


00000d 00h 00m 10s


00000d 00h 00m 30s

Default:permittedRange: enumerated, see below



228

telindus1423Router/bridge/bridgeGroup/macAddress

Use this attribute to determine whether a fixed, a random or a user defined MAC address is associated with the bridge group.

The macAddress attribute has the following values:

Value Description

deviceMac A MAC address from the Telindus 1423 SHDSL Router itself is associated with the bridge group.

Use the second part of the macAddress attribute to define which MAC address has to be selected:

• lan. The LAN interface its MAC address is associated with the bridge group.• random. The Telindus 1423 SHDSL Router generates a random MAC address

and this is associated with the bridge group.

userMac A user defined MAC address is associated with the bridge group.

Use the second part of the macAddress attribute to enter the MAC address.

Default:<deviceMac> lanRange: choice, see below



229

telindus1423Router/bridge/bridgeGroup/vlan

Use this attribute to set up (a) VLAN(s) on the bridge group in case you want to manage the Telindus 1423 SHDSL Router over (a) VLAN(s).

Although the Telindus 1423 SHDSL Router bridges VLAN tagged frames when connected to a VLAN aware switch, the Telindus 1423 SHDSL Router itself can only be managed via IP if a VLAN is configured on the bridge group. In other words, if you want that the data carried by a VLAN can be delivered to the protocol stack of the Telindus 1423 SHDSL Router (e.g. so that it can be routed), then you have to con-figure the VLAN on the bridge group.


Element Description

name Use this element to assign an administrative name to the VLAN.

adminStatus Use this element to activate (up) or deactivate (down) the VLAN.

ip Use this element to configure the IP related parame-ters of the VLAN.

Refer to …



vlan Use this element to configure the specific VLAN parameters.

Refer to telindus1423Router/bridge/bridgeGroup/vlan/vlan on page 230 for a detailed descrip-tion of the vlan structure.








230

telindus1423Router/bridge/bridgeGroup/vlan/vlan

Use this structure to configure the specific VLAN related parameters of a VLAN.


Element Description

vid Use this element to set the VLAN ID.

txCos Use this element to set the default user priority (802.1P, also called COS) of the transmitted VLAN frames.

changeTos Use this element to enable or disable the COS to TOS mapping.

If you set the changeTos attribute to disabled, then the element cosTosMap is ignored.

Note that the TOS to COS mapping is always enabled, irrespective with the setting of the changeTos attribute.

cosTosMap Use this element to determine how the VLAN user pri-ority (COS) maps onto the IP TOS byte value.

The cosTosMap structure contains the following elements:

• p0 … p7. Use these elements to define which VLAN user priority (0 up to 7) maps onto which IP TOS byte value (0 up to 255).

tosCosMap Use this element to determine how the IP TOS byte value maps onto the VLAN user priority (COS).

The tosCosMap table contains the following elements:

• startTos and endTos. Use these elements to set the TOS byte value range that has to be mapped.

• cos. Use this element to set the VLAN user priority (COS) value on which the specified TOS byte value range has to be mapped.

arp Use this element to configure the Address Resolution Protocol (ARP) cache.

Refer to telindus1423Router/lanInterface/arp on page 22 for more information.













231

telindus1423Router/bridge/bridgeGroup/vlanSwitching

Use this attribute specify which VLANs you want to switch in case the bridge group is used as a VLAN switch. Note that you have to enable VLAN switching on the bridge group by setting the bridgeCache attribute to switching. Refer to …

• telindus1423Router/bridge/bridgeGroup/bridgeCache on page 225• MU-10.3.4 - Configuration de la commutation VLAN on page 331

The vlanSwitching attribute contains the following elements:

Element Description

sourceIntf Use this element to enter the name of the (physical) source interface which carries the VLAN that has to be switched.

sourceVlan Use this element to enter the VLAN ID of the VLAN that has to be switched.

Stripping the VLAN tag

Entering 0 as VLAN ID strips the VLAN tag of the Ethernet frame.

Example: suppose you enter 1 as srcVlan and 0 as dstVlan. So VLAN 1 is switched from the source interface to the destination interface. But before it is sent out on the destination interface, the VLAN tag is stripped. So instead of VLAN tagged Ethernet frames, plain Ethernet frames are sent out. In the opposite direction how-ever, the VLAN tag is added again.

sourcePMap Use this element to, if desired, remap the VLAN prior-ities. The priorities defined in the sourcePMap are applied after the VLAN is switched from destinationVlan to sourceVlan.

The structure contains the elements p0 up to p7, which represent priority 0 up to priority 7. If you want to remap priorities, then enter the new priority value under one of these priority elements.

Example: suppose you want to remap priority 5 to priority 7, then enter 7 as value of the p5 element.

destinationIntf Use this element to enter the name of the (physical) destination interface which carries the VLAN when it has been switched.

The destination interface can also be a bridge group, in that case just enter the name of the bridge group.

destinationVlan Use this element to enter the VLAN ID of the VLAN when it has been switched.

Entering 0 as VLAN ID strips the VLAN tag of the Ethernet frame. Refer to Strip-ping the VLAN tag for more information.









232

Note that the switching always happens in both directions (bidirectional, i.e. from source to destination and vice versa).

destinationPMap Use this element to, if desired, remap the VLAN prior-ities. The priorities defined in the destinationPMap are applied after the VLAN is switched from sourceVlan to destinationVlan.

Refer to the sourcePMap element for more information on this structure.

Element Description




233

MR-1.13.2 Bridge access list configuration attributes


• telindus1423Router/bridge/accessList[ ]/macAddress on page 234




234

telindus1423Router/bridge/accessList[ ]/macAddress

Use this attribute to filter bridged frames based on the source MAC address.

This is an outbound access list. Packets coming from MAC addresses that are specified in the access list are not sent out on the interface on which the access list is applied.

To apply the access list on a bridge interface, type the index name of the accessList[ ] object as value of the accessList element in the bridging structure.

Example

If you created an accessList object with index name my_access_list (i.e. access-List[my_access_list]) and you want to apply this access list on a bridge interface, then enter the index name as value for the accessList element in the bridging structure.




235

MR-1.14 SNMP configuration attributes


• telindus1423Router/snmp/trapDestinations on page 236• telindus1423Router/snmp/mib2Traps on page 236



236

telindus1423Router/snmp/trapDestinations

Use this attribute to define to which IP address the SNMP traps have to be sent.

The Telindus 1423 SHDSL Router translates all alarm status changes into SNMP traps. These traps can then be sent to a management system. To enable this, configure in the trapDestinations table the IP addresses to which the traps have to be sent. If the trapDestinations table is empty then no traps are sent.

The trapDestinations table contains the following elements:

telindus1423Router/snmp/mib2Traps

Use this attribute to enable (on) or disable (off) the sending of SNMP traps as MIB2 traps.

If you want to send the SNMP traps as MIB2 traps, proceed as follows:

Element Description

address Use this element to set the IP address of the manage-ment station to which the SNMP trap messages have to be sent.

community Use this element to set the community string which is included in the SNMP traps that are sent to the man-agement station. It is used as a password in the SNMP communication. Give it the same value as on your SNMP management sta-tion.

Step Action

1 Select the snmp/trapDestinations attribute. Add an entry to this table for each network man-agement station that should receive SNMP traps. Refer to telindus1423Router/snmp/trapDes-tinations on page 236.

2 Configure the mib2Traps attribute:

• on. The alarms coldBoot, warmBoot and linkDown are sent as MIB2 traps instead of enter-prise specific (private) MIB traps.

• off. All alarms are sent as enterprise specific (private) MIB traps.

3 Set for each object of the Telindus 1423 SHDSL Router:

• the alarms that you want to send using the attribute alarmMask.• the importance of each alarm using the attribute alarmLevel.

By default only the most important alarms are enabled.



Default:publicRange: 0 … 20 characters




237

MR-1.15 Management configuration attributes


• telindus1423Router/management/sysLog on page 238• telindus1423Router/management/timeServer on page 240• telindus1423Router/management/timeZone on page 240• telindus1423Router/management/cms2Address on page 241• telindus1423Router/management/accessList on page 242• telindus1423Router/management/snmp on page 243• telindus1423Router/management/telnet on page 243• telindus1423Router/management/tftp on page 243• telindus1423Router/management/ftp on page 243• telindus1423Router/management/accessPolicy on page 243• telindus1423Router/management/consoleNoTrafficTimeOut on page 244• telindus1423Router/management/alarmFilter on page 244• telindus1423Router/management/timedStatsAvailability on page 244• telindus1423Router/management/atwinGraphics on page 245• telindus1423Router/management/loginControl on page 246• telindus1423Router/management/ctrlPortProtocol on page 247• telindus1423Router/management/loopback/ipAddress on page 247• telindus1423Router/management/loopback/ipNetMask on page 247



238

telindus1423Router/management/sysLog

Use this attribute to configure the sending of syslog messages.

The sysLog structure contains the following elements:

What is syslog?

The syslog protocol (RFC 3164) is used for the transmission of event notification messages across net-works.

A syslog message is sent on UDP port 514. It has the following format:

"<facility*8+severity> date hostname message"

where …

• the priority value is the number contained within the angle brackets, i.e. <facility*8+severity>.• facility is a part of the priority value: facility = 23 * 8 = 184

In this case no facility has been explicitly assigned and therefore a "local use" facility is used (numer-ical code value 23).

• severity is a part of the priority value: severity = 6 - <alarmLevel of the alarm>The severity only ranges from 0 up to 6. So in case the alarm level of an alarm is bigger than 6, the severity is limited to 0.

• date is the date the syslog message was generated: Mmm dd hh:mm:ss (e.g. Jan 01 12:45:55).• hostname is the IP address of the interface through which the syslog message was sent (e.g.

10.0.28.3).• message is the alarm message. It has the following format:

"alarm:<sysName>;<realTimeClock>;<sysUpTime>;<devSeverityLevel>;<severit-

yLevel>;<alarmMessage>"

where …- <sysName> is the sysName configured in the Telindus 1423 SHDSL Router.- <realTimeClock> is the value of the real time clock at the moment the alarm was generated: dd/

mm/yy hh:mm:ss (e.g. 25/12/02 22:45:55).- <sysUpTime> is the system up-time of the Telindus 1423 SHDSL Router at the moment the alarm

was generated: xxxxxd xxh xxm xxs (e.g. 00025d 08h 45m 55s).

Element Description

separator Use this element to specify the separator character in the syslog messages. Refer to What is syslog? on page 238 for more information on the syslog mes-ages.

destinations Use this element to enter the IP address(es) of the syslog server(s). Up to 3 addresses can be entered.

As soon a valid syslog server address is entered, a syslog message is sent to this server for each (unmasked) alarm that occurs. If multiple syslog server addresses are sent, then the syslog messages are sent to all servers.

The syslog messages are not sent in case the interface or the route through which they have to be sent is down. In this case, the syslog messages are kept in a his-tory list (maximum 31 messages). These pending messages are sent as soon as the interface and/or route comes up again.


Default:;Range: 1 character




239

- <devSeverityLvl> is the device severity level: devSeverityLvl = 6 - <totalAlarmLevel of the device>. The device severity level only ranges from 0 up to 6. So in case the total alarm level of the Telindus 1423 SHDSL Router is bigger than 6, the device severity level is limited to 0.

- <severityLvl> is the alarm severity level: severityLvl = 6 - <alarmLevel of the alarm>. The alarm severity level only ranges from 0 up to 6. So in case the alarm level of an alarm is bigger than 6, the alarm severity level is limited to 0.

- <alarmMessage> is the alarm itself: path.alarmName on|off (e.g. telindus1423Router/lan-Interface.linkDown on).

- ; is the separator character. If desired, you can specify another separator character. Refer to the configuration element separator on page 238.

Example:

The following gives an example of a complete syslog message. In this case, the separator is the ^ char-acter.

"<189>Feb 28 16:56:15 10.0.28.2 alarm:telindus1423Router^28/02/03 16:56:15^130^3^5^telindus1423Router.configChanged on"



240

telindus1423Router/management/timeServer

Use this attribute to enter the IP address of the SNTP time server with which the Telindus 1423 SHDSL Router can synchronise its clock. Date and time are displayed in the status attributes telindus1423Router/date and telindus1423Router/time.

You can also set the time zone and the daylight saving time using the configuration attribute telindus1423Router/management/timeZone on page 240.

What is SNTP?

Short for Simple Network Time Protocol, a simplified version of NTP. SNTP is used when the ultimate performance of the full NTP implementation described in RFC 1305 is not needed or justified.

The Telindus 1423 SHDSL Router can only act as an SNTP client, not as an SNTP server.

telindus1423Router/management/timeZone

Use this attribute to set the time zone when using an SNTP time server. Refer to telindus1423Router/management/timeServer on page 240.

The timeZone structure contains the following elements:

Element Description

timeZone Use this element to set the time zone.

The timeZone element has the following values: utc, utc+1 up to utc+12 and utc-1 up to utc-12.

What is UTC?

UTC is the coordinated universal time, formerly known as Greenwich mean time (GMT). It is the international time standard.

daylightSaving Use this element to set the daylight saving time.

The daylightSaving element has the following values: europeanUnion and none.



Default:utc+1Range: enumerated, see below

Default:europeanUnionRange: europeanUnion / none



241

telindus1423Router/management/cms2Address

Use this attribute to assign an absolute address to the Telindus 1423 SHDSL Router.

What is relative and absolute addressing?

If you want to connect with TMA to a OneAccess device, you have to specify the address of the device in the Connect… window. Refer to MU-4 - Maintenance du Routeur Telindus 1423 SHDSL on page 35.

There are two different address types: relative and absolute. The following table explains the difference between these address types:

Type Description

relative This type of addressing is meant for a network topology where the OneAccess devices are connected in-line on management level. I.e. with extended manage-ment connections between two OneAccess devices. An extended management connection is realised with a crossed cable between the control connectors of two OneAccess devices.

To enable relative addressing, no address has to be specified in the OneAccess device. In other words, leave the cms2Address attribute at its default value, being 0.

absolute This type of addressing is meant for a network topology where the OneAccess devices are not connected in-line on management level. I.e. when there is a digital multipoint device present (e.g. an Orchid DM).

To enable absolute addressing, an address has to be specified in the OneAccess device. Do this using the cms2Address attribute. The absolute addressing range goes from 1 up to 65535.




242

telindus1423Router/management/accessList

Use this attribute to set up an inbound simple access list on the protocol stack. Refer to MU-10.2 - Configuration des restrictions d'accès on page 312 for more information on inbound access lists.

The access list filters incoming traffic, based on the source IP address. You can specify multiple entries within the access list. When more than one entry applies to the same packet, then only the most specific one is taken in consideration. I.e. the entry covering the smallest range. If not one entry matches, then the packet is dropped. If the access list is empty, then all packets are forwarded.

The accessList table contains the following elements:

If you specify one entry or multiple entries for which the action is set to deny, then also specify at least one entry for which the action is set to allow. Else all packets are dropped!

Example 1

This example shows an access list that only allows traffic from subnet 192.168.48.0, except for packets from station 192.168.48.10.

Example 2

The next example shows an access list that allows all traffic, except the traffic from subnet 192.168.48.0. The second entry is the rule to add if you want all pack-ets that do not match the previous entries to be allowed.

Element Description

sourceAddress Use this element to set the IP source address of the packet. The address may be a (sub)network address.

mask Use this element to set the IP subnet mask for the sourceAddress. By combining an IP address with a mask you can uniquely identify a range of addresses.

action Use this element to set the action when a packet arrives with a source IP address that falls within the specified address range.

The possible actions are:

• deny. The packet is dropped.• allow. The packet is forwarded.




Default:denyRange: enumerated, see below



243

telindus1423Router/management/accessPolicy

Use this attribute to apply an inbound extended access list on the protocol stack.

Do this by entering the index name of the traffic policy you want to apply. You can create the traffic policy itself by adding a trafficPolicy object and by configuring the attributes in this object.

Important remark

It is possible that the Telindus 1423 SHDSL Router has to answer to DHCP requests or terminate L2TP and IPSec tunnels. In that case, if you set up an access list on the protocol stack, then make sure that these protocols are allowed access to the protocol stack.

Refer to MU-10.2 - Configuration des restrictions d'accès on page 312 for more information on inbound access lists.

Example

If you created a trafficPolicy object with index name my_traffic_policy (i.e. trafficPolicy[my_traffic_policy]) and you want to apply this traffic policy here, then enter the index name as value for the trafficPolicy element.

telindus1423Router/management/snmp

Use this attribute to accept (enabled) or discard (disabled) SNMP requests.

telindus1423Router/management/telnet

Use this attribute to accept (enabled) or discard (disabled) Telnet sessions.

Use this attribute also to accept (enabled) or discard (disabled) HTTP (Web Interface) sessions.

telindus1423Router/management/tftp

Use this attribute to accept (enabled) or discard (disabled) TFTP sessions.

telindus1423Router/management/ftp

Use this attribute to accept (enabled) or discard (disabled) FTP sessions.








244

telindus1423Router/management/consoleNoTrafficTimeOut

Use this attribute to set the time-out period after which a management ses-sion is closed when there is no user interaction. The purpose of such a timer is to protect the Telindus 1423 SHDSL Router against unauthorised access in case the last user did not close his session.

This timer applies on …

• terminal (emulation) sessions (through the control port).• Telnet and HTTP sessions (over IP).

It does not apply on TMA or TMA CLI sessions (nor through the control port, nor over IP). They have a fixed time-out of 15 minutes.

telindus1423Router/management/alarmFilter

Use this attribute to selectively ignore / drop alarms in TMA for HP Open-View if these alarms are below a certain level.

The filter number that you define using the alarmFilter attribute, has to correspond with a filter that you have to define in the Alarm Manager of TMA for HP OpenView. In the Alarm Manager, it is possible to specify a minimum alarm level that is needed before alarms are logged in HP OpenView. This can be specified for each filter number.

telindus1423Router/management/timedStatsAvailability

Use this attribute to determine whether the nested tables in the timed per-formance statistics (i.e. 2 hour, 24 hour and 7 days performance statistics) are visible or not.

The timedStatsAvailability attribute has the following values:

Value Description

none Only the “first level” timed performance statistics are available. In other words, the nested tables (i.e. a table in a table) in the timed performance statistics are not dis-played.

basic The full performance statistics are available on the physical interfaces only (e.g. the LAN interface, etc.). Not on the logical interfaces (e.g. a PVC, a VLAN, etc.).

full The full performance statistics are available on both the physical (e.g. the LAN interface, etc.) and logical (e.g. a PVC, a VLAN, etc.) interfaces

If you have a lot of PVCs this may require quite some memory space and processing power.


24855d 03h 14m 07s


Default:basicRange: enumerated, see below



245

telindus1423Router/management/atwinGraphics

Use this attribute to enable or disable the graphical symbols in the ATWIN user interface.

One of the tools that allows you to manage the Telindus 1423 SHDSL Router is ATWIN (refer to MU-1.4 - Outils de gestion et de maintenance on page 8). ATWIN is a basic, menu-driven user interface. You can start it using a terminal (emulation program) on the control port or using Telnet on an IP interface (e.g. the LAN interface) and by typing atwin at the command prompt (refer to the Maintenance tools manual (PDF) for more information).

By default, ATWIN uses graphical symbols to draw the borders of the “windows”. In some cases how-ever, these graphical symbols are displayed incorrectly. In that case you can choose to disable the graphical symbols. By doing so, the window borders are drawn using + and - signs.

The atwinGraphics attribute has the following values:

Value Description

enabled The ATWIN window borders are drawn using graphical symbols.

disabled The ATWIN window borders are drawn using + and - signs.




246

telindus1423Router/management/loginControl

Use this attribute to configure the monitoring of management access to the device.

The loginControl structure contains the following elements:

Element Description

alarm Use this element to determine when the access failure alarm should be logged in the accessLog table and a syslog message is sent.

The alarm structure contains the following elements:

• maxFailCnt. Use this element to set the access fail-ure alarm threshold. If this value is exceeded within the access failure alarm period, then the access failure alarm is raised.

• period. Use this element to set the access failure alarm period. If within this period the access failure alarm threshold is exceeded, then the access fail-ure alarm is raised.

Example

By default, if within a period of 15 minutes 3 access attempts fail, then the access failure alarm is logged in the accessLog table as follows:Jul 13 11:00:00 00000d 00h 15m 58s accessFailureOn

If within the consecutive period of 15 minutes no or less than 3 access attempts fail, then the access failure alarm is cleared in the accessLog table as follows:Jul 13 11:15:00 00000d 00h 30m 58s accessFailureOff

Also see telindus1423Router/management/accessLog on page 386.





00001d 00h 00m 00s



247

telindus1423Router/management/ctrlPortProtocol

Use this attribute to set the function of the control connector.

The ctrlPortProtocol attribute has the following values:

telindus1423Router/management/loopback/ipAddress

Use this attribute to assign an IP address to the loopback interface.

The loopback interface is a software interface which can be used for management purposes. This inter-face is always up, regardless of the state of the physical interfaces. This means the router will always respond to ICMP echo requests sent to this address. In every other respect the loopback address behaves the same as an IP address of a physical interface.

If the loopback address is used and RIP is active, then a host route to the loopback address is included in the RIP updates.

telindus1423Router/management/loopback/ipNetMask

Use this attribute to assign an IP netmask to the loopback interface.

Also see telindus1423Router/management/loopback/ipAddress on page 247.

Value Description

management Select this value if you want to connect the control connector of the Telindus 1423 SHDSL Router to …

• a management concentrator for management purposes.• the control connector of another OneAccess device using a crossed cable (i.e.

they are connected back-to-back) in order to create an extended management link. Refer to What is relative and absolute addressing? on page 241 for more information on extended management links.

When connecting the control connector of the Telindus 1423 SHDSL Router to a COM port of your computer, you can still open a TMA session on the Telindus 1423 SHDSL Router. You can however not open a CLI or ATWIN session.

console Select this value if you want to connect the control connector of the Telindus 1423 SHDSL Router to a COM port of your computer in order to manage the Telindus 1423 SHDSL Router using TMA, CLI, ATWIN, etc.

Default:consoleRange: enumerated, see below




User manual Status attributes

248

MR-2 Status attributes

This chapter discusses the status attributes of the Telindus 1423 SHDSL Router. The following gives an overview of this chapter:

• MR-2.1 - Status attribute overview on page 249• MR-2.2 - General status attributes on page 258• MR-2.3 - LAN interface status attributes on page 262• MR-2.4 - WAN interface status attributes on page 271• MR-2.5 - Encapsulation status attributes on page 274• MR-2.6 - SHDSL line status attributes on page 297• MR-2.7 - End and repeater status attributes on page 302• MR-2.8 - BRI status attributes on page 306• MR-2.9 - AUX status attributes on page 318• MR-2.10 - Profile status attributes on page 321• MR-2.11 - Dial maps status attributes on page 323• MR-2.12 - Bundle status attributes on page 326• MR-2.13 - Router status attributes on page 334• MR-2.14 - Bridge status attributes on page 377• MR-2.15 - Management status attributes on page 384• MR-2.16 - File system status attributes on page 389• MR-2.17 - Operating system status attributes on page 399



249

MR-2.1 Status attribute overview

Refer to MU-4.3 - Les objets dans l'arborescence Routeur Telindus 1423 SHDSL on page 46 to find out which objects are present by default, which ones you can add yourself and which ones are added auto-matically.

> telindus1423RoutersysDescrsysObjectIDsysUpTimesysServicesflash1Versionflash2VersionactiveFlashflashVersionsbootVersiontdreVersionmessagesdeviceIdconfigurationSavingdatetimeAction: Set DateAction: Set Time

>> lanInterfaceifDescrifTypeifOperStatusifLastChangeifSpeedifMtuipmacAddressarpCachebridgingadapter1

vlanports2

ipAdEntBcastAddripAdEntReasmMaxSizeAction: clearArpCache

1. Only present on the single port LAN interface.2. Only present on the 4 port LAN interface.



250

>> wanInterfaceifDescrifTypeifOperStatusifLastChangeifSpeedifMtu

>>> atmatmSyncpvcTablevp

>>> frameRelayipdlciTablelmicllmLastCongestionCause

>>> pppipbridginglcpStateipcpStatebcpStateccpStatelcpMyOptionslcpHisOptionsipcpMyOptionsipcpHisOptionsbcpMyOptionsbcpHisOptionsccpMyOptionsccpHisOptionsmyCompressionRatiohisCompressionRatiomyAuthenticationStatushisAuthenticationStatus

>>> hdlcbridging



251

>>> errorTeststatustypestartSysUpTimedurationblockSizeprogrammablePatternreceiveSample

>>> lineifDescrifTypeifOperStatusifSpeedregionmaxSpeedSearchmaxSpeedResultlinePairsSwappednumDiscoveredRepeaterseocAlarmThresholdsAction: maximumSpeedSearch

>>>> linePair[ ]ifSpeedifOperStatusstatustimeSinceLastRetrainlineAttenuationsignalNoiseactualBitRate

>>> repeater[ ]vendorIdvendorModelvendorSerialvendorSoftVersioneocSoftVersionshdslVersioneocStateeocAlarmThresholdsAction: loopbackActivation

>>>> networkLinePair[ ]lineAttenuationsignalNoise

>>>> customerLinePair[ ]lineAttenuationsignalNoise



252

>>> endvendorIdvendorModelvendorSerialvendorSoftVersioneocSoftVersionshdslVersioneocStateeocAlarmThresholds

>>>> linePair[ ]lineAttenuationsignalNoise

>> bri[1]3

ifDescrifTypeifOperStatusifLastChangeifMtul1StatuslapdLinksbChannelUsagetestTypetestStatusAction: loopbackActivationAction: clearIsdnCall

>>> bChannel[1]ifDescrifTypeifOperStatusifLastChangeifMtudialMapEntrylocalPhoneNrremotePhoneNrcallDirection

3. Only present on the Telindus 1423 SHDSL Router ISDN version.



253

>>>> pppiplcpStateipcpStateccpStatelcpMyOptionslcpHisOptionsipcpMyOptionsipcpHisOptionsccpMyOptionsccpHisOptionsmyCompressionRatiohisCompressionRatiomyAuthenticationStatushisAuthenticationStatus

>>> leasedLine[ ]ifDescrifTypeifOperStatusifLastChangeifSpeedifMtu

>>>> frameRelayipdlciTablelmicllmLastCongestionCause

>>>> pppipbridginglcpStateipcpStatebcpStateccpStatelcpMyOptionslcpHisOptionsipcpMyOptionsipcpHisOptionsbcpMyOptionsbcpHisOptionsccpMyOptionsccpHisOptionsmyCompressionRatiohisCompressionRatiomyAuthenticationStatushisAuthenticationStatus



254

>>>> hdlcbridging

>>>> errorTeststatustypestartSysUpTimedurationblockSizeprogrammablePatternreceiveSample


>> bri[2]3


>> profiles3

>>> dial

>>>> defaultIsdnprofileUsers

>>>> isdn[ ]profileUsers

>>> encapsulation

>>>> defaultPppprofileUsers

>>>> ppp[ ]profileUsers

>>> forwardingMode

>>>> defaultRoutingprofileUsers

>>>> routing[ ]profileUsers

>> dialMaps3

mapping



255

>> bundle

>>> pppBundle[ ]4

ifDescrifTypeifOperStatusifSpeedmembersipbridgingipcpStateipcpMyOptionsipcpHisOptionsbcpStatebcpMyOptionsbcpHisOptionsmulticlassInterfaces

>>> isdnBundle[ ]5

ifDescrifTypeifOperStatusifSpeedmembersipipcpStateipcpMyOptionsipcpHisOptionsbacpStatebacpMyOptionsbacpHisOptionsinBandwidthoutBandwidth

>> routerroutingTableigmpTabledhcpBindingdhcpStatisticsdhcpBlackListradiusdnsdnsServersaddrPools3

Action: unBlacklist

4. This is the PPP bundle in case of MLPPP on the WAN interface.5. This is the PPP bundle in case of MLPPP on the ISDN interfaces.



256

>>> defaultNataddresses

>>> tunnelsl2tpTunnelsipsecL2tpTunnels

>>> ikeSA[ ]phase1phase2

>>> ospftyperoutersexternalRoutesasExtLsas

>>>> areainterfaceshostsneighborsroutersstubrouterLsasnetworkLsassummLsasasbrLsasnssaLsas

>>> vrrp[ ]macAddressinterfacescriticals

>>> firewallsessionsreverseSessionslogsNet



257

>> bridge

>>> bridgeGroupifDescrifTypeifOperStatusifMtuiparpCachebridgeCachebridgingspanningTreeAction: clearArpCacheAction: clearBridgeCache

>> managementcms2AddresstimeServeralarmLogaccessLog

>>> loopbackifDescrifTypeifOperStatusifMtuipAddress

>> fileSystemfileListfreeSpacestatuscorruptBlockstrustedCertificatesselfCertificatesAction: Delete FileAction: Rename FileAction: loadTrustedCertificateAction: generateSelfCertificateRequestAction: loadSelfCertificateAction: getTrustedCertificateScepAction: getSelfCertificateScepAction: getCrlScepAction: saveCertificates

>> operatingSystemtaskInfo



258

MR-2.2 General status attributes

This section describes the following status attributes:

• telindus1423Router/sysDescr on page 259• telindus1423Router/sysObjectID on page 259• telindus1423Router/sysUpTime on page 259• telindus1423Router/sysServices on page 259• telindus1423Router/flash1Version on page 259• telindus1423Router/flash2Version on page 259• telindus1423Router/activeFlash on page 260• telindus1423Router/flashVersions on page 260• telindus1423Router/bootVersion on page 260• telindus1423Router/tdreVersion on page 260• telindus1423Router/messages on page 260• telindus1423Router/deviceId on page 261• telindus1423Router/configurationSaving on page 261• telindus1423Router/date on page 261• telindus1423Router/time on page 261


• telindus1423Router/Set Date on page 261• telindus1423Router/Set Time on page 261



259

telindus1423Router/sysDescr

This attribute displays a textual description of the device.

Example: Telindus 1423 SHDSL Router Txxxx/xxxxx 01/01/00 12:00

In this example the following parameters are visible:

• Telindus 1423 SHDSL Router is the device name.• Txxxx/xxxxx is the application software code and version.• 01/01/00 12:00 is the application software release date and time.

telindus1423Router/sysObjectID

This attribute displays the identification string.

telindus1423Router/sysUpTime

This attribute displays the elapsed time since the last power-on or cold boot of the Telindus 1423 SHDSL Router.

telindus1423Router/sysServices

This attribute displays the service identification.

telindus1423Router/flash1Version

This attribute displays the code and version of the application software stored as CONTROL1.

Example: Txxxx/xxxxx 01/01/00 12:00


• Txxxx is the application software code for this device.• /xxxxx is the application software version.• 01/01/00 is the application software release date.• 12:00 is the application software release time.

telindus1423Router/flash2Version

This attribute displays the code and version of the application software stored as CONTROL2.

Example: Txxxx/xxxxx 01/01/00 12:00


• Txxxx is the application software code for this device.• /xxxxx is the application software version.• 01/01/00 is the application software release date.• 12:00 is the application software release time.



260

telindus1423Router/activeFlash

This attribute displays which application software is currently active. Possible values are:

telindus1423Router/flashVersions

This attribute displays how many application software versions can be stored in the file system.

telindus1423Router/bootVersion

This attribute displays the code, version, release date and time of the boot software currently used in the Telindus 1423 SHDSL Router.

telindus1423Router/tdreVersion

This attribute displays the version of the TDRE (OneAccess Dynamic Routing Engine) currently used in the Telindus 1423 SHDSL Router.

Example: xxx.yyy.zzz


• xxx is the major TDRE version. This number is incremented only when a complete new version of the TDRE is released.

• yyy is the minor TDRE version. This number is incremented every time new features are added to the TDRE.

• zzz is the build version. This number is incremented every time a new TDRE version is built (also in case of bug fixes etc.).

telindus1423Router/messages

This attribute displays informative and error messages, e.g. Reconfigured, Cold Boot, … The messages table displays maximum 20 messages.

If you open a TMA session on the Telindus 1423 SHDSL Router over IP, i.e. not through the control port, then the messages are also sent to the control port. This means that if you open a terminal emulation session on the control port, you can monitor these messages. If you hit the ENTER key, the messages stop and you get the (CLI) password prompt.

Value Description

flash1 The application software CONTROL1 is active.

flash2 The application software CONTROL2 is active.



261

telindus1423Router/deviceId

This attribute displays a unique code. This code is programmed into the Telindus 1423 SHDSL Router before it leaves the factory. You can use this code for inventory purposes.

telindus1423Router/configurationSaving

This attribute indicates when the Telindus 1423 SHDSL Router is writing its (new) configuration to the flash memory. Possible values are:

telindus1423Router/date

This attribute displays the current date in the format dd/mm/yy (e.g. 01/01/00).

telindus1423Router/time

This attribute displays the current time in the format hh:mm:ss (e.g. 12:30:45).

telindus1423Router/Set Date

Use this action to set the current date. Enter the date as argument value in the format dd/mm/yy (e.g. 01/01/00). Then execute the action.

telindus1423Router/Set Time

Use this action to set the current time. Enter the time as argument value in the format hh:mm:ss (e.g. 12:30:45). Then execute the action.

Value Description

busy The Telindus 1423 SHDSL Router is busy writing its configuration to the flash memory. During this state, do not power-down or reboot the Telindus 1423 SHDSL Router else the new configuration will be lost.

done The Telindus 1423 SHDSL Router has finished writing its configuration to the flash memory.



262

MR-2.3 LAN interface status attributes


• telindus1423Router/lanInterface/ifDescr on page 263• telindus1423Router/lanInterface/ifType on page 263• telindus1423Router/lanInterface/ifOperStatus on page 263• telindus1423Router/lanInterface/ifLastChange on page 263• telindus1423Router/lanInterface/ifSpeed on page 263• telindus1423Router/lanInterface/ifMtu on page 263• telindus1423Router/lanInterface/ip on page 264• telindus1423Router/lanInterface/macAddress on page 264• telindus1423Router/lanInterface/arpCache on page 265• telindus1423Router/lanInterface/bridging on page 266• telindus1423Router/lanInterface/adapter on page 268• telindus1423Router/lanInterface/vlan on page 268• telindus1423Router/lanInterface/ports on page 269• telindus1423Router/lanInterface/ipAdEntBcastAddr on page 269• telindus1423Router/lanInterface/ipAdEntReasmMaxSize on page 269


• telindus1423Router/lanInterface/clearArpCache on page 270



263

telindus1423Router/lanInterface/ifDescr

This attribute displays the interface description.

telindus1423Router/lanInterface/ifType

This attribute displays the interface type.

telindus1423Router/lanInterface/ifOperStatus

This attribute displays the current operational status of the interface.

telindus1423Router/lanInterface/ifLastChange

This attribute shows the system-up time on the moment the interface entered its current operational state. I.e. the moment the value of the ifOperStatus status attribute changes (from up to down or vice versa), the system-up time value is written into the ifLastChange status attribute.

telindus1423Router/lanInterface/ifSpeed

This attribute displays the interface speed in bits per second (bps).

telindus1423Router/lanInterface/ifMtu

This attribute displays the interface its Maximum Transfer Unit, i.e. the maximum number of bytes that one packet can contain on this interface.



264

telindus1423Router/lanInterface/ip

This attribute displays the IP information of the interface.

The ip structure contains the following elements:

telindus1423Router/lanInterface/macAddress

This attribute displays the MAC address of the Telindus 1423 SHDSL Router its LAN interface.

The LAN interface has been allocated a fixed Ethernet address, also called MAC (Medium Access Con-trol) address. The MAC address is globally unique and can not be modified. It is a 6 byte code, repre-sented in hexadecimal format. Each byte in the code is separated by a colon.

Refer to What is the ARP cache? on page 22 for more information on the MAC addresses.

Element Description

status This is the current operational status of the IP layer (layer 3).

address This is the IP address of the interface. It is either configured or retrieved automat-ically.

netMask This is the IP subnet mask of the interface. It is either configured or retrieved auto-matically.



265

telindus1423Router/lanInterface/arpCache

This attribute displays all the MAC address - IP address pairs from ARP requests and replies received on the LAN interface. Refer to What is the ARP cache? on page 22 for more information.

The arpCache table contains the following elements:

Example

The following figure shows part of an ARP cache table as an example:

Element Description

macAddress This is the MAC address.

ipAddress This is the associated IP address.

type This is the ARP cache entry type. Possible values are:

• dynamic. The MAC - IP address pair is retrieved from an ARP request or reply message.

• static. The MAC - IP address pair is configured.There is only one static entry, i.e. the Telindus 1423 SHDSL Router its own IP and MAC address.

timeOut This is the time the entry will remain in the ARP cache. For the static entry, this value is 0.



266

telindus1423Router/lanInterface/bridging

This attribute displays the bridging status of the interface.

The bridging structure contains the following elements:

Element Description

state This displays the current state of the port. Possible values are:

• disabled1. The port is not in use because of a management action.• blocking. The port does not participate in frame forwarding.• listening. The port prepares to participate in frame forwarding, but it does not

update its MAC address database (also called bridge cache).• learning. The port prepares to participate in frame forwarding, and it learns the

present MAC addresses.• forwarding1. The port participates in frame forwarding.

Refer to MU-9.1.5 - Etats des ports de pontage du Spanning Tree on page 283 for more information on port states2.

subState2 This gives additional information on the port state. Possible values are:

• root. This is the port through which the root bridge can be reached. Conse-quently, the root bridge itself does not have a root port. All other bridges must have a root port.

• designated. This is the designated port for this (virtual) LAN. All ports of the root bridge are designated ports.

• alternate. This port is not active. Either because of a management action, or through protocol intervention.

designatedPriority2 Together, these two elements form a unique bridge identifier. Depending whether the current port is a designated port or not, these two elements display the unique bridge identifier of …

• the bridge to which this port belongs, in case of a designated port.• the bridge believed to be the designated bridge for the LAN that is currently

connected to this port, in all other cases.

This bridge identifier is used …

• together with the designatedPortPriority and designatedPortId attributes to determine whether this port should be the designated port for the LAN that is currently connected to this port.

• to test the value of the bridge identifier parameter conveyed in received Config-uration BPDUs.

designatedMac2



267

designatedPort-Priority2

Together, these two elements form a unique port identifier. They display the unique port identifier of the bridge port through which the designated bridge trans-mits the configuration message information stored by this port.

This port identifier is used …

• together with the designatedPriority and designatedMac attributes to determine whether this port should be the designated port for the LAN that is currently connected to this port.

• by the management system to determine the topology of the bridged LAN.

designatedPortId2

topologyChangeAck2

This displays the value of the Topology Change Acknowledgement flag in the next Configuration BPDU that will be transmitted on this port.

This element is used to assess the need to set the Topology Change Acknowl-edgement flag in response to a received Topology Change Notification BPDU.

configuration-Pending2

This is used to determine whether a Configuration BPDU should be transmitted on this port after expiry of the hold timer. This avoids that Configuration BPDUs are transmitted too often, although ensuring that up-to-date information is transmitted.

1. These are the only possible port states for a bridge that is not running the Spanning Tree pro-tocol (IEEE p802.1D).

2. Only relevant when the bridge uses the Spanning Tree Protocol.

Element Description



268

telindus1423Router/lanInterface/adapter

Only present on the single port LAN interface.

This attribute displays the Ethernet mode of the LAN interface as set using the telindus1423Router/lanInter-face/adapter attribute.

The adapter structure contains the following elements:


This attribute displays the status of the VLAN(s) on this interface.


Element Description

speed This is the Ethernet speed in Mbps. Possible values are: 10 and 100.

duplex This is the Ethernet duplex mode. Possible values are: halfDuplex and fullDuplex.

Element Description

name This is the name of the VLAN as you configured it. If you did not configure a name, then this element displays: <LAN interface name> “vlan” <VLAN ID>.

E.g. lan vlan 2

ifOperStatus This is the current operational status of the VLAN.

ifLastChange This is the system-up time on the moment the VLAN entered its current operational state. I.e. the moment the value of the ifOperStatus element changes (from up to down or vice versa), the system-up time value is written into the ifLastChange element.

ip This displays the IP address and subnet mask of the VLAN.

bridging This displays the bridging information of the VLAN.

Refer to telindus1423Router/lanInterface/bridging on page 266 for a detailed description of the bridging structure.

vlan This displays the specific VLAN related status information.


• identifier. This element displays the VLAN identifier.• arpCache. This element displays all the MAC address - IP address pairs from

ARP requests and replies received on the VLAN.Refer to telindus1423Router/lanInterface/arpCache on page 265 for a detailed descrip-tion of the arpCache table.



269

telindus1423Router/lanInterface/ports


This attribute displays the status of each port of the 4 port Ethernet interface (including the local port, refer to Qu’est-ce que le commutateur Ethernet à 4 ports ? on page 335).

The ports table contains the following elements:

telindus1423Router/lanInterface/ipAdEntBcastAddr

This attribute displays the value of the least-significant bit in the IP broadcast address. This address is used for sending packets on the interface which is associated with the IP address of this entry. The value applies to the general broadcast, the subnet and network broadcasts.

telindus1423Router/lanInterface/ipAdEntReasmMaxSize

This attribute displays the size of the largest IP packet which this entity can re-assemble from incoming IP fragmented packets received on this interface.

Element Description

portName This element displays the port name. Possible values are port1, port2, port3, port4 or localPort. Refer to Qu’est-ce que le commutateur Ethernet à 4 ports ? on page 335 for more information on what the local port is.

ifOperStatus This element displays the current operational status of the port.

speed This element displays the port speed in megabits per second (Mbps).

duplex This element displays the duplex mode of the port. Possible values are: fullDuplex or halfDuplex.

autoNegotiate This element displays the status of the Ethernet mode auto negotiation process. Possible values are:

• disabled. The adapter element in ports configuration attribute is set to fixed. I.e. the auto negotiation process is disabled.

• done. The adapter element in ports configuration attribute is set to autoNegotiate and the auto negotiation process is finished.

• notDone. The adapter element in ports configuration attribute is set to autoNegotiate but the auto negotiation process is not finished (yet).

linkPartnerCaps This element displays the Ethernet mode capabilities of the port its link partner. So this structure contains the following elements: 10Mb/halfDuplex, 10Mb/fullDuplex, 100Mb/halfDuplex, 100Mb/fullDuplex, flowControl. Each element can have the value capable or notCapable.

vlanMembership This element displays the VLAN membership of the port. The vlanMembership table contains the following elements:

• vid. This element displays the VLAN ID.• portMembership. This element displays which port is a member (yes) or no mem-

ber (no) of the corresponding VLAN.



270

telindus1423Router/lanInterface/clearArpCache

Use this action to clear the ARP cache table.



271

MR-2.4 WAN interface status attributes


• telindus1423Router/wanInterface/ifDescr on page 272• telindus1423Router/wanInterface/ifType on page 272• telindus1423Router/wanInterface/ifSpeed on page 272• telindus1423Router/wanInterface/ifMtu on page 272• telindus1423Router/wanInterface/ifLastChange on page 272• telindus1423Router/wanInterface/ifOperStatus on page 272



272

telindus1423Router/wanInterface/ifDescr


telindus1423Router/wanInterface/ifType


telindus1423Router/wanInterface/ifSpeed


telindus1423Router/wanInterface/ifMtu


telindus1423Router/wanInterface/ifLastChange


telindus1423Router/wanInterface/ifOperStatus

This attribute displays the current operational status of the interface. Possible values are:

Value Description

up The WAN interface is up, data transfer is possible.

down The WAN interface is down, data transfer is not possible.

The ifOperStatus attribute is down in case of …

• ATM, when …- the ATM synchronisation status is “not synched”.- the line is not in data state.- the bit pump is not synchronised.

• PPP(oA), when …- LCP is not open.- the line is not in data state.- the bit pump is not synchronised.

• Frame Relay, when …- LMI is not up.- the line is not in data state.- the bit pump is not synchronised.



273

Important remarks

• Whether the Telindus 1423 SHDSL Router is configured in bridging or routing has no effect on the value of the attributes wanInterface/ifOperStatus:Status and wanInterface/alarmInfo/linkDown:Alarms.

• In case of ATM, if the configuration element pvcTable/atm/oamF5Loopback is set to disabled, then the ifOp-erStatus of the PVC becomes up when the ATM is synchronised globally. However, this does not guar-antee that the PVC is configured (correctly) on the remote side. However, the other conditions as stated in the table above remain.

• In case of PPP(oA), if the configuration element linkMonitoring/operation is set to disabled, then it is pos-sible that the wanInterface/ifOperStatus value does not go down even if the link quality is too bad for a proper data link. This because the link monitoring mechanism is the only PPP mechanism that will start a renegotiation of the LCP layer.

• In case of Frame Relay, if the configuration element lmi/auto is set to noLmi, then the value of the status element lmi/status:Status is always up. However, the other conditions as stated in the table above remain.



274

MR-2.5 Encapsulation status attributes

This section discusses the status attributes of the encapsulation protocols that can be used on the Tel-indus 1423 SHDSL Router.



• MR-2.5.1 - ATM status attributes on page 275• MR-2.5.2 - Frame Relay status attributes on page 280• MR-2.5.3 - PPP status attributes on page 285• MR-2.5.4 - HDLC status attributes on page 293• MR-2.5.5 - Error test status attributes on page 295



275

MR-2.5.1 ATM status attributes


• telindus1423Router/wanInterface/channel[wan_1]/atm/atmSync on page 276• telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable on page 276• telindus1423Router/wanInterface/channel[wan_1]/atm/vp on page 279



276

telindus1423Router/wanInterface/channel[wan_1]/atm/atmSync

This attribute displays the ATM synchronisation status. Possible values are: synced, notSynced.


This attribute gives the complete status information of all known PVCs.

The pvcTable table contains the following elements:

Element Description

name This is the name of the PVC as you configured it. If you did not configure a name, then this element displays: <interface name> “vpi” <vpi number> “vci” <vci number>.

E.g. wan vpi 102 vci 102

ifOperStatus This is the current operational status of the PVC.

In case OAM F5 …

• LoopBack (LB) or Continuity Check (CC) is disabled, i.e. no OAM F4 LB/CC cells are sent, then the ifOperStatus of the PVC becomes up when the ATM is syn-chronised globally. However, this does not guarantee that the PVC is config-ured (correctly) on the remote side.

• LoopBack (LB) is enabled, i.e. OAM F5 loopback cells are sent at regular inter-vals, then the ifOperStatus of the PVC becomes up when the loopback cells are returned and down when the loopback cells are not returned by the remote side.

ifLastChange This is the system-up time on the moment the PVC entered its current operational state. I.e. the moment the value of the ifOperStatus element changes (from up to down or vice versa), the system-up time value is written into the ifLastChange element.

ip This displays the IP information of the PVC.

Refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/ip on page 277 for a detailed description of the ip structure.

bridging This displays the bridging information of the PVC.


atm This displays the specific ATM related status information of the PVC.

Refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm on page 278 for a detailed description of the atm structure.



277

telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/ip

The ip structure in the pvcTable displays the IP information of the PVC.


Element Description

address This is the IP address of the PVC. It is either configured or retrieved automatically.

netMask This is the IP subnet mask of the PVC. It is either configured or retrieved automat-ically.

remote This is the IP address of the remote end of the PVC. It is either configured or retrieved automatically.



278


The atm structure in the pvcTable displays the specific ATM related status information of the PVC.


Element Description

vpi This displays the Virtual Path Identifier (VPI).

vci This displays the Virtual Channel Identifier (VCI).

The VPI in conjunction with the VCI identifies the next destination of a cell as it passes through a series of ATM switches on the way to its destination.

peakCellRate This displays the Peak Cell Rate (PCR) of the PVC in bps.

sustCellRate This displays the Sustainable Cell Rate (SCR) of the PVC in bps.

maxBurstSize This displays the Maximum Burst Size (MBS) of the PVC in cell times.

pppOverEth When the Telindus 1423 SHDSL Router wants to initiate a PPP over Ethernet (PPPoE) session, it must first perform a discovery to identify the Ethernet MAC address of the host and to establish a PPPoE session ID. The pppOverEth structure displays information on the PPPoE discovery.

The pppOverEth structure contains the following elements:

• discState. This is the state of the discovery. The discovery goes as follows:- The Telindus 1423 SHDSL Router sends a PADI packet (PPPoE Active Dis-

covery Initiation).- When the host receives a PADI that it can serve, it replies by sending a

PADO packet (PPPoE Active Discovery Offer).- The Telindus 1423 SHDSL Router then sends one PADR packet (PPPoE

Active Discovery Request) to the host that it has chosen.- When the host receives a PADR packet, it prepares to begin a PPP session.

It generates a unique session ID for the PPPoE session and replies to the Telindus 1423 SHDSL Router with a PADS packet (PPPoE Active Discov-ery Session-confirmation).

So possible discState values are: idle, waitForPADO, waitForPADS, established.• remoteMacAddress. This is the MAC address of the remote system as learned dur-

ing the discovery.

ppp This displays the PPP information of the PVC.

Refer to MR-2.5.3 - PPP status attributes on page 285 for a detailed description of the elements in the ppp structure.



279


Whereas the pvcTable gives the current operational status for each Virtual Channel, the vp table gives the current operational status of a complete Virtual Path.


Element Description

vpi This is the Virtual Path Identifier (VPI).

ifOperStatus This is the current operational status of the Virtual Path.

In case OAM F4 …

• LoopBack (LB) or Continuity Check (CC) is disabled, i.e. no OAM F4 LB/CC cells are sent, then the ifOperStatus of the VP becomes up when the ATM is syn-chronised globally. However, this does not guarantee that the VP is configured (correctly) on the remote side.

• LoopBack (LB) is enabled, i.e. OAM F4 loopback cells are sent at regular inter-vals, then the ifOperStatus of the VP becomes up when the loopback cells are returned and down when the loopback cells are not returned by the remote side. In case a VP goes down, also all VCs belonging to the VP go down.



280

MR-2.5.2 Frame Relay status attributes


• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/ip on page 281• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable on page 281• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi on page 283• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/cllmLastCongestionCause on page 284



281

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/ip

This attribute displays the IP information of the Frame Relay link.

Refer to telindus1423Router/lanInterface/ip on page 264 for a detailed description of the ip structure.


This attribute gives the complete status information of all known DLCIs.

The dlciTable table contains the following elements:

Element Description

name This is the name of the DLCI as you configured it. If you did not configure a name, then this element displays: <interface name> “dlci” <dlci number>.

E.g. wan dlci 16

ifOperStatus This is the current operational status of the DLCI.

ifLastChange This is the system-up time on the moment the DLCI entered its current operational state. I.e. the moment the value of the ifOperStatus element changes (from up to down or vice versa), the system-up time value is written into the ifLastChange element.

ip This displays the IP information of the DLCI.


bridging This displays the bridging information of the DLCI.


frameRelay This displays the specific Frame Relay related status information of the DLCI.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable/frameRelay on page 282 for a detailed description of the frameRelay structure.



282


The frameRelay structure in the dlciTable displays the specific Frame Relay related status information of the DLCI.


Element Description

dlci This is the DLCI identification number.

active This indicates whether the corresponding DLCI is active (on) or not (off).

new This is set to on if the DLCI has just been created, else it is off.

deleted This is set to on if the DLCI has been deleted, else it is off.

rr This element is only relevant for LMI revision 1. It is the flow control flag. If it is on, then no traffic can be sent on this DLCI. Else it is off.

bandwidth This element is only relevant for LMI revision 1 (in all other cases this value is 0). It is the CIR value, in bps, as it is configured on the remote.

cllmLastCongestion-Cause

CLLM (Consolidated Link Layer Management) is a Frame Relay protocol used for traffic management. The cllmLastCongestionCause element indicates the last reason, which was received from the network, for congestion on the corresponding DLCI.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/cllmLastCongestion-Cause on page 284 for the possible values of the cllmLastCongestionCause element.



283


This attribute gives a complete LMI status information overview.


Element Description

mode This displays the Frame Relay mode. Possible values are: noLmi, user, network, auto.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi on page 52 for more information on these values.

type This displays the LMI variant. Possible values are: lmiRev1, ansiT1-617-d, q933-Annex-A, frf1-2.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi on page 52 for more information on these values.

status This displays the current state of LMI. Possible values are:

• up. LMI messages can and are exchanged.• down. No LMI messages can be exchanged.

lastStatusChange This is the system-up time when the LMI status entered its current state. I.e. the moment the value of the status element changes (from up to down or vice versa), the system-up time value is written into the lastStatusChange element.

lastError This displays the last error condition reported by LMI. Possible values are: none, protocol error, unknown information element, sequence error, unknown report, timer expired, invalid report type, unsolicited status.

netTxSeqNum This is the sequence number of the last LMI Status Response frame that was sent.

Since only a Frame Relay network or DCE can transmit Status Responses, the value of this element only changes in case the Telindus 1423 SHDSL Router is defined as a Frame Relay network or both user and network. I.e. in case the mode element is set to network, auto or nni.

netRxSeqNum This is the sequence number of the last LMI Status Enquiry frame that was received.

Since only a Frame Relay network or DCE can receive Status Enquiries, the value of this element only changes in case the Telindus 1423 SHDSL Router is defined as a Frame Relay network or both user and network. I.e. in case the mode element is set to network, auto or nni.

netErrors This is the number of errors on LMI commands issued by the Frame Relay network or DCE during the last monitoredEvents period.

userTxSeqNum This is the sequence number of the last LMI Status Enquiry frame that was sent.

Since only a Frame Relay user or DTE can transmit Status Enquiries, the value of this element only changes in case the Telindus 1423 SHDSL Router is defined as a Frame Relay user or both user and network. I.e. in case the mode element is set to user, auto or nni.



284

telindus1423Router/wanInterface/channel[wan_1]/frameRelay/cllmLastCongestionCause

This attribute indicates the last reason, which was received from the network, for congestion on any of the DLCIs. Possible values are:

• none• short term, excessive traffic• long term, excessive traffic• short term, equipment failure• long term, equipment failure• short term, maintenance action• long term, maintenance action• short term, unknown cause• long term, unknown cause• unknown cause

userRxSeqNum This is the sequence number of the last LMI Status Response frame that was received.

Since only a Frame Relay user or DTE can receive Status Responses, the value of this element only changes in case the Telindus 1423 SHDSL Router is defined as a Frame Relay user or both user and network. I.e. in case the mode element is set to user, auto or nni.

userErrors This is the number of errors on LMI commands issued by the Frame Relay user or DTE during the last monitoredEvents period.

userWaitFullEnquiry This is the number of LMI frames still to be sent before a Full Status Enquiry will be requested.

userLastReport-TypeSent

This displays the type of the most recent report that was sent. Possible values are:

• full status. The last report contained the full status.• link integrity. The last report only contained the link integrity information.

Element Description



285

MR-2.5.3 PPP status attributes


• telindus1423Router/wanInterface/channel[wan_1]/ppp/ip on page 286• telindus1423Router/wanInterface/channel[wan_1]/ppp/bridging on page 286• telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpState on page 287• telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpState on page 287• telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpState on page 287• telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpState on page 287• telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpMyOptions on page 288• telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpHisOptions on page 288• telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpMyOptions on page 289• telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpHisOptions on page 289• telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpMyOptions on page 290• telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpHisOptions on page 290• telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpMyOptions on page 291• telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpHisOptions on page 291• telindus1423Router/wanInterface/channel[wan_1]/ppp/myCompressionRatio on page 291• telindus1423Router/wanInterface/channel[wan_1]/ppp/hisCompressionRatio on page 291• telindus1423Router/wanInterface/channel[wan_1]/ppp/myAuthenticationStatus on page 292• telindus1423Router/wanInterface/channel[wan_1]/ppp/hisAuthenticationStatus on page 292



286

telindus1423Router/wanInterface/channel[wan_1]/ppp/ip

This attribute displays the IP information of the PPP link.


telindus1423Router/wanInterface/channel[wan_1]/ppp/bridging

This attribute displays the bridging status of the PPP link.


Element Description

status This is the current operational status of the IP layer (layer 3) of the PPP link.

address This is the IP address of the PPP link. It is either configured or retrieved automat-ically.

netMask This is the IP subnet mask of the PPP link. It is either configured or retrieved auto-matically.

remote This is the IP address of the remote end of the PPP link. It is either configured or retrieved automatically.



287

telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpState

This attribute reflects the status of the LCP (Link Control Protocol) protocol. Possible values are:

telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpState

This attribute reflects the status of the IPCP (Internet Protocol Control Protocol) protocol. The possible values are the same as those of the lcpState attribute.

Refer to telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpState on page 287.

telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpState

This attribute reflects the status of the BCP (Bridging Control Protocol) protocol. The possible values are the same as those of the lcpState attribute.


telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpState

This attribute reflects the status of the CCP (Compression Control Protocol) protocol. The possible val-ues are the same as those of the lcpState attribute.


Value Description

Initial LCP handshake has not started yet.

Starting, Closed, Stopped, Closing, Stopping

These values correspond with the transient states in the LCP state diagram.

Req-Sent The local side of the PPP link has sent an LCP request. The remote side did not answer yet.

Ack-Rcvd The local side of the PPP link has received an LCP acknowledge from the remote side. This is a transient state.

Ack-Sent The local side of the PPP link has acknowledged the LCP request from the remote side.

Opened The LCP handshake succeeded.



288

telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpMyOptions

During the LCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the LCP options for the router at this side (local side) of the link.

The lcpMyOptions table contains the following elements:

telindus1423Router/wanInterface/channel[wan_1]/ppp/lcpHisOptions

This attribute lists the LCP options for the router at the other side (remote side) of the link. The lcpHisOptions table contains the same elements as the lcpMyOptions table. Refer to telindus1423Router/wanIn-terface/channel[wan_1]/ppp/lcpMyOptions on page 288.

Other option values than the ones supported by the Telindus 1423 SHDSL Router may be present.

Element Description

option The Telindus 1423 SHDSL Router supports the following LCP options:

• 3: the Authentication-Protocol option.• 5: the Magic-Number option.

For more information on the LCP configuration options, refer to RFC 1661.

length This is the length of the option field.

value This is the option value represented as an octet string (hexadecimal ASCII repre-sentation).



289

telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpMyOptions

During the IPCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the IPCP options for the router at this side (local side) of the link.

The ipcpMyOptions table contains the following elements:

telindus1423Router/wanInterface/channel[wan_1]/ppp/ipcpHisOptions

This attribute lists the IPCP options for the router at the other side (remote side) of the link. The ipcpHisOptions table contains the same elements as the ipcpMyOptions table. Refer to telindus1423Router/wan-Interface/channel[wan_1]/ppp/ipcpMyOptions on page 289.


Element Description

option The Telindus 1423 SHDSL Router supports the following IPCP option:

• 3: the IP-Address option.• ip-vso: the IP-Vendor Specific option. This is used to negotiate the netmask.

For more information on the IPCP configuration options, refer to RFC 1332.





290

telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpMyOptions

During the BCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the BCP options for the router at this side (local side) of the link.

The bcpMyOptions table contains the following elements:

telindus1423Router/wanInterface/channel[wan_1]/ppp/bcpHisOptions

This attribute lists the BCP options for the router at the other side (remote side) of the link. The bcpHisOptions table contains the same elements as the bcpMyOptions table. Refer to telindus1423Router/wanIn-terface/channel[wan_1]/ppp/bcpMyOptions on page 290.


Element Description

option The Telindus 1423 SHDSL Router supports the following BCP options:

• 1: the Bridge-Identification option.• 2: the Line-Identification option.• 3: the MAC-Support option.• 4: the Tinygram-Compression option.• 5: the LAN-Identification option.• 6: the MAC-Address option.• 7: the Spanning-Tree-Protocol option.

For more information on the BCP configuration options, refer to RFC 2878.





291

telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpMyOptions

During the CCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the CCP options for the router at this side (local side) of the link.

The ccpMyOptions table contains the following elements:

telindus1423Router/wanInterface/channel[wan_1]/ppp/ccpHisOptions

This attribute lists the CCP options for the router at the other side (remote side) of the link. The ccpHisOptions table contains the same elements as the ccpMyOptions table. Refer to telindus1423Router/wanIn-terface/channel[wan_1]/ppp/ccpMyOptions on page 291.


telindus1423Router/wanInterface/channel[wan_1]/ppp/myCompressionRatio

When PPP compression is enabled, this attribute displays the compression ratio achieved by the router at this side (local side) of the link.

telindus1423Router/wanInterface/channel[wan_1]/ppp/hisCompressionRatio

When PPP compression is enabled, this attribute displays the compression ratio achieved by the router at the other side (remote side) of the link.

Element Description

option The Telindus 1423 SHDSL Router supports the following CCP option:

• 1: the Predictor1 option.

For more information on the CCP configuration options, refer to RFC 1962.





292

telindus1423Router/wanInterface/channel[wan_1]/ppp/myAuthenticationStatus

This attribute displays the authentication state of the router at this side (local side) of the link. I.e. the state of the authenticator. Possible values are:

telindus1423Router/wanInterface/channel[wan_1]/ppp/hisAuthenticationStatus

This attribute displays the authentication state of the router at the other side (remote side) of the link. I.e. the state of the peer. Possible values are:

Value Description

No-Authentication The local side does not request PPP authentication or still has to start the CHAP authentication (LCP handshake is busy).

Wait-On-Response The local side has sent a challenge packet and is waiting for an answer.

Authen-Successful The response packet is found to be correct. This is the state when authentication succeeded.

Authen-Failure The response packet is found to be incorrect. This is a transient state since the router starts the LCP handshake again after a failing authentication.

Value Description

No-Authentication This is the start-up state.

Wait-On-Challenge During the LCP handshake the authenticator already indicates it wants to authen-ticate. From that moment on, the peer awaits a challenge packet.

Wait-On-Success Once the peer has sent a response, it awaits a success or failure message.

Authen-Successful The peer has received a success packet. It remains in this state during data trans-fer.

Authen-Failure The peer has received a failure packet. This is a transient state since the router starts the LCP handshake again after a failing authentication.

Authen-Not-Allowed This state only occurs when the peer does not accept the authentication request during the LCP handshake. A possible reason might be that the peer router does not support CHAP.



293

MR-2.5.4 HDLC status attributes


• telindus1423Router/wanInterface/channel[wan_1]/hdlc/bridging on page 294



294

telindus1423Router/wanInterface/channel[wan_1]/hdlc/bridging

This attribute displays the bridging status of the HDLC link.




295

MR-2.5.5 Error test status attributes


• telindus1423Router/wanInterface/channel[wan_1]/errorTest/status on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/type on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/startSysUpTime on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/duration on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/blockSize on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/programmablePattern on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/receiveSample on page 296


• telindus1423Router/wanInterface/channel[wan_1]/errorTest/startTest on page 296• telindus1423Router/wanInterface/channel[wan_1]/errorTest/stopTest on page 296



296

telindus1423Router/wanInterface/channel[wan_1]/errorTest/status

This attribute displays the status of the error test.

Due to RAM limitations, it is possible that not all test patterns are supported. In that case the string ram-Limit is displayed as value of the status attribute telindus1423Router/wanInterface/channel[wan_1]/errorTest/status.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/type

This attribute displays the type of error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/startSysUpTime

This attribute displays the value of the sysUpTime attribute at the moment the error test was started.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/duration

This attribute displays the duration of the error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/blockSize

This attribute displays the size of the test blocks.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/programmablePattern

This attribute displays the bit string pattern as you configured it in the programmablePattern configuration attribute.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/receiveSample

This attribute displays the received test pattern.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/startTest

Use this action to start an error test.


telindus1423Router/wanInterface/channel[wan_1]/errorTest/stopTest

Use this action to stop an error test.



297

MR-2.6 SHDSL line status attributes

This section describes the following line status attributes:

• telindus1423Router/wanInterface/line/ifDescr on page 298• telindus1423Router/wanInterface/line/ifType on page 298• telindus1423Router/wanInterface/line/ifOperStatus on page 298• telindus1423Router/wanInterface/line/ifSpeed on page 298• telindus1423Router/wanInterface/line/region on page 298• telindus1423Router/wanInterface/line/maxSpeedSearch on page 298• telindus1423Router/wanInterface/line/maxSpeedResult on page 298• telindus1423Router/wanInterface/line/linePairsSwapped on page 299• telindus1423Router/wanInterface/line/numDiscoveredRepeaters on page 299• telindus1423Router/wanInterface/line/eocAlarmThresholds on page 299

This section describes the following line pair status attributes:

• telindus1423Router/wanInterface/line/linePair[ ]/ifOperStatus on page 301• telindus1423Router/wanInterface/line/linePair[ ]/ifSpeed on page 301• telindus1423Router/wanInterface/line/linePair[ ]/status on page 301• telindus1423Router/wanInterface/line/linePair[ ]/timeSinceLastRetrain on page 301• telindus1423Router/wanInterface/line/linePair[ ]/lineAttenuation on page 301• telindus1423Router/wanInterface/line/linePair[ ]/signalNoise on page 301• telindus1423Router/wanInterface/line/linePair[ ]/actualBitRate on page 301


• telindus1423Router/wanInterface/line/maximumSpeedSearch on page 300



298

telindus1423Router/wanInterface/line/ifDescr


telindus1423Router/wanInterface/line/ifType


telindus1423Router/wanInterface/line/ifOperStatus

This attribute displays the current operational status of the line. Possible values are:

telindus1423Router/wanInterface/line/ifSpeed

This attribute displays the current line speed in bits per second (bps).

In case of a Telindus 1423 SHDSL Router 2 pair version, the line/ifSpeed attribute displays the sum of the speed of line pair 1 and 2.

telindus1423Router/wanInterface/line/region

This attribute displays the SHDSL standard currently used. Possible values are: auto, annexA, annexB. Refer to telindus1423Router/wanInterface/line/region on page 67 for more information on these values.

telindus1423Router/wanInterface/line/maxSpeedSearch

This attribute displays the status of the maximumSpeedSearch action. Possible values are:

telindus1423Router/wanInterface/line/maxSpeedResult

This attribute displays the maximum speed, in bits per second (bps), that was achieved during the exe-cution of the maximumSpeedSearch action.

Value Description

up The line is up, data transfer is possible.

down The line is down, data transfer is not possible.

testing A line test is active.

Value Description

idle No maximumSpeedSearch action has been performed.

progressing The maximumSpeedSearch action is running.

aborted The maximumSpeedSearch action stopped without result.

completed The maximumSpeedSearch action is finished. The result is displayed in the maxSpeedResult attribute.



299

telindus1423Router/wanInterface/line/linePairsSwapped

This attribute is only present on the Telindus 1423 SHDSL Router 2 pair version.

This attribute indicates whether the line pairs have been swapped when connecting the central with the remote device. Possible values are:

telindus1423Router/wanInterface/line/numDiscoveredRepeaters

This attribute displays the number of Crocus SHDSL repeaters that the Telindus 1423 SHDSL Router discovered on the SHDSL line.

telindus1423Router/wanInterface/line/eocAlarmThresholds

What this attribute displays depends on the setting of the telindus1423Router/wanInterface/line/eocHandling attribute:

The eocAlarmThresholds structure contains the following elements:

• lineAttenuation• signalNoise

Value Description

yes The line pairs are swapped.

no The line pairs are not swapped.

unknown The Telindus 1423 SHDSL Router is unable to determine whether the line pairs have been swapped (e.g. because it is still training).

If eocHandling is set to …

then …

none the eocAlarmThresholds attribute does not display relevant information. It always dis-plays 0.0.

discovery • on the central1 device, the eocAlarmThresholds attribute displays the values as set in the telindus1423Router/wanInterface/line/linkAlarmThresholds attribute.

• on the remote2 device, the eocAlarmThresholds attribute does not display relevant information. It always displays 0.0.

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.

inventory

info

alarmConfiguration the eocAlarmThresholds attribute displays the values as set in the telindus1423Router/wanInterface/line/linkAlarmThresholds attribute on the central device.



300

telindus1423Router/wanInterface/line/maximumSpeedSearch

Use this action to determine the highest possible line speed that can be achieved between the central and remote Telindus 1423 SHDSL Router.

When you execute this test, the following happens:

Important remarks

• The Telindus 1423 SHDSL Router has to be in data state (i.e. after a successful training sequence and when the data connection is up) before you can execute the maximumSpeedSearch action.

• While the maximumSpeedSearch action is running, no data transmission is possible.• In case of a Telindus 1423 SHDSL Router 2 pair version, you can not execute the maximumSpeedSearch

action because you can not define a speed range on both the central and remote Telindus 1423 SHDSL Router.

Phase Action

1 The Telindus 1423 SHDSL Router interrupts the normal data transfer.

2 Both local and remote Telindus 1423 SHDSL Router go to auto speed mode in order to determine the highest possible line speed. Meanwhile, the status of the test can be mon-itored with the maxSpeedSearch attribute.

3 When the test ends, the result is displayed by the maxSpeedResult attribute.

4 The Telindus 1423 SHDSL Router resumes normal data transfer at the speed that was selected before the test.



301

telindus1423Router/wanInterface/line/linePair[ ]/ifOperStatus

This attribute displays the current operational status of the line pair. Possible values are:

telindus1423Router/wanInterface/line/linePair[ ]/ifSpeed

This attribute displays the line pair speed, in bits per second (bps), when the line pair is in data state.

telindus1423Router/wanInterface/line/linePair[ ]/status

This attribute displays the current status of the line pair. Possible values are:

telindus1423Router/wanInterface/line/linePair[ ]/timeSinceLastRetrain

This attribute displays the elapsed time since the last retrain cycle.

telindus1423Router/wanInterface/line/linePair[ ]/lineAttenuation

This attribute displays the current line pair attenuation in dB.

The lineAttenuation attribute does not display meaningful information when the line is not trained. It is only relevant for a line that is in data state for at least 5 minutes.

telindus1423Router/wanInterface/line/linePair[ ]/signalNoise

This attribute displays the current signal to noise ratio on the line pair in dB.

The signalNoise attribute does not display meaningful information when the line is not trained. It is only relevant for a line that is in data state for at least 5 minutes.

telindus1423Router/wanInterface/line/linePair[ ]/actualBitRate

This attribute displays the maximum speed, in bits per second (bps), that could be negotiated on the line pair during the training sequence.

Value Description

up The line pair is up, data transfer is possible. This is the case when the value of the linePair[ ]/status attribute is dataState.

down The line pair is down, data transfer is not possible.

testing A line test is active.

Value Description

idle No link is present.

training A training cycle is in progress.

dataState A data link is present.



302

MR-2.7 End and repeater status attributes


• telindus1423Router/wanInterface/end/vendorId on page 303• telindus1423Router/wanInterface/end/vendorModel on page 303• telindus1423Router/wanInterface/end/vendorSerial on page 303• telindus1423Router/wanInterface/end/vendorSoftVersion on page 303• telindus1423Router/wanInterface/end/eocSoftVersion on page 303• telindus1423Router/wanInterface/end/shdslVersion on page 303• telindus1423Router/wanInterface/end/eocState on page 304• telindus1423Router/wanInterface/end/eocAlarmThresholds on page 304• telindus1423Router/wanInterface/end/linePair[ ]/lineAttenuation on page 304• telindus1423Router/wanInterface/end/linePair[ ]/signalNoise on page 304


• telindus1423Router/wanInterface/repeater/loopbackActivation on page 305

• Exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. Refer to MU-5.4.4 - eocHandlingQuelles informations EOC standard sont-elles récupérées ? on page 82 for an overview.

• The repeater[ ] and end objects contain the same attributes, therefore only the attributes of the end object are listed here.



303

telindus1423Router/wanInterface/end/vendorId

This attribute is only retrieved in case the eocHandling attribute is set to discovery, inventory, info or alarmCon-figuration.

This attribute displays information about the vendor of the repeater or end device. The vendorId structure contains the following elements:

• countryCode E.g. 65295 for Belgium.• providerCode E.g. TLS_ for OneAccess.• vendorSpecific

telindus1423Router/wanInterface/end/vendorModel

This attribute is only retrieved in case the eocHandling attribute is set to inventory, info or alarmConfiguration.

This attribute displays the model of the repeater or end device. E.g. SHDSL TT 2P for a Crocus SHDSL Table Top 2 pair version.

telindus1423Router/wanInterface/end/vendorSerial


This attribute displays the serial number of the repeater or end device. For a OneAccess devices this is the deviceId attribute (refer to telindus1423Router/deviceId on page 261).

telindus1423Router/wanInterface/end/vendorSoftVersion


This attribute displays the version of the firmware used on the repeater or end device. For a OneAccess device this is the part after “/” of the T-code string displayed in the flashVersion attribute (refer to telindus1423Router/flash1Version on page 259).

telindus1423Router/wanInterface/end/eocSoftVersion


This attribute displays the EOC software version used on the repeater or end device.

telindus1423Router/wanInterface/end/shdslVersion


This attribute displays the SHDSL version used on the repeater or end device.



304

telindus1423Router/wanInterface/end/eocState


This attribute displays the state of the EOC channel.

telindus1423Router/wanInterface/end/eocAlarmThresholds

This attribute is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration.

What this attribute displays depends on the setting of the telindus1423Router/wanInterface/line/eocHandling attribute:

The eocAlarmThresholds structure contains the following elements:

• lineAttenuation• signalNoise

telindus1423Router/wanInterface/end/linePair[ ]/lineAttenuation


This attribute displays the line attenuation, in dB, as it is measured on the line pair of the repeater or end device.

telindus1423Router/wanInterface/end/linePair[ ]/signalNoise


This attribute displays the noise margin, in dB, as it is measured on the line pair of the repeater or end device.

If eocHandling is set to …

then …

info the eocAlarmThresholds attribute displays the values as set in the telindus1423Router/wanInterface/line/linkAlarmThresholds attribute on the remote1 device.

1. The remote device is the device on which the channel attribute is set to remote.

alarmConfiguration the eocAlarmThresholds attribute displays the values as set in the telindus1423Router/wanInterface/line/linkAlarmThresholds attribute on the central2 device.

2. The central device is the device on which the channel attribute is set to central.



305

telindus1423Router/wanInterface/repeater/loopbackActivation

This action is only present in the repeater[ ] object.

Use this action to set up a loop at the network side of the Crocus SHDSL Repeater:

Set the loop by selecting the action argument value initiateNetworkLoopback and executing the action (in TMA, double-click the loopbackActivation string). Stop the loop by selecting the action argument value clearAllMaintenanceStates and executing the action (in TMA, double-click the loopbackActivation string).

Important remarks

• You can only set up a loop at the network side of the Crocus SHDSL Repeater. Not at the customer side.

• You can only start the loopbackActivation action on the central device. Not on the remote device.• You can only start the loopbackActivation action in case the telindus1423Router/wanInterface/line/eocHandling

attribute is set to alarmConfiguration.

networkside

customer side

repeatercentral device

loop-back



306

MR-2.8 BRI status attributes

This section discusses the status attributes of the BRI interface. First it describes the status attributes of the BRI interface in general. Then it describes more specifically the status attributes of the B-channels and of the leasedLine[ ] object that can be added under the bri[ ] object.


• MR-2.8.1 - General BRI status attributes on page 307• MR-2.8.2 - B-channel status attributes on page 313• MR-2.8.3 - ISDN leased line status attributes on page 315



307

MR-2.8.1 General BRI status attributes


• telindus1423Router/bri[ ]/ifDescr on page 308• telindus1423Router/bri[ ]/ifType on page 308• telindus1423Router/bri[ ]/ifOperStatus on page 308• telindus1423Router/bri[ ]/ifLastChange on page 308• telindus1423Router/bri[ ]/ifMtu on page 308• telindus1423Router/bri[ ]/l1Status on page 309• telindus1423Router/bri[ ]/lapdLinks on page 310• telindus1423Router/bri[ ]/bChannelUsage on page 311• telindus1423Router/bri[ ]/testType on page 311• telindus1423Router/bri[ ]/testStatus on page 311


• telindus1423Router/bri[ ]/loopbackActivation on page 312• telindus1423Router/bri[ ]/clearIsdnCall on page 312



308

telindus1423Router/bri[ ]/ifDescr

This attribute displays the interface description of the BRI interface.

telindus1423Router/bri[ ]/ifType

This attribute displays the interface type of the BRI interface.

telindus1423Router/bri[ ]/ifOperStatus

This attribute displays the current operational status of the LAPD (Link Access Protocol - Channel D, which is layer 2) of the BRI interface.

Possible values are:

telindus1423Router/bri[ ]/ifLastChange


telindus1423Router/bri[ ]/ifMtu

This attribute displays the BRI interface its Maximum Transfer Unit, i.e. the maximum number of bytes that one packet can contain on this interface.

Value Description

up LAPD is up.

down LAPD is down.



309

telindus1423Router/bri[ ]/l1Status

This attribute displays the status of ISDN layer 1, i.e. the physical connection with the telecom operator ISDN switch, of the BRI interface. The most common states are f7Activated and f3Deacivated. Possible val-ues are:

Value Description

f1Inactive In this inactive (powered-off) state, the TE1 is not transmitting and cannot detect the presence of any input signals.

1. TE: Terminal Equipment

f2Sensing This state is entered after the TE has been powered on but has not determined the type of signal (if any) that the TE is receiving.

f3Deacivated This is the deactivated state of the physical protocol. Neither the NT2 nor the TE is transmitting.

2. NT: Network Termination device

f4AwaitingSignal When the TE wishes to initiate activation, it sends an activation signal to the NT and awaits a response.

f5IdentifyingInput At first receipt of any signal from the NT, the TE ceases sending activation signals and awaits the activation signal or synchronized frame from the NT.

f6Synchronized When the TE has received an activation signal from the NT, it responds with a syn-chronized frame and is awaiting a synchronized frame from the NT.

f7Activated This is the normal active state with the protocol activated in both directions. Both the NT and TE are transmitting normal frames. State F7 is the only state where B- and D-channel contain operational data.

f8LostFraming This is the condition when the TE has lost frame synchronization and is awaiting re-synchronization.



310

telindus1423Router/bri[ ]/lapdLinks

This attribute displays the status of ISDN layer 2 with Terminal Endpoint Identifier (TEI) number and multi-frame structure state of the BRI interface.

The lapdLinks table contains the following elements:

Element Description

l2State This is the multi-frame structure state. The most common states are multiple-FrameEstablished and teiAssigned:

• multipleFrameEstablished. This indicates there is data link connectivity to the tele-com operator ISDN switch. This is the state that you should see under normal operations. Any other state usually indicates a problem on the circuit.

• teiAssigned. This indicates that the router has lost connectivity to the switch. This is normal if the telecom operator deactivates layers 1 and 2 when there are no active calls.

Refer to ITU Q.921 Annex B for more information on all the other possible layer 2 states such as: teiUnassigned, assignAwaitingTei, establishAwaitingTei, awaitingEstablish-ment, awaitingRelease, timerRecovery.

tei This is the Terminal Endpoint Identifier.



311

telindus1423Router/bri[ ]/bChannelUsage

This attribute displays the usage of the B-channels on the BRI interface.

The bChannelUsage table contains the following elements:

telindus1423Router/bri[ ]/testType

This attribute displays which BRI loop is currently active.

Refer to telindus1423Router/bri[ ]/loopbackActivation on page 312 for more information on BRI loops.

telindus1423Router/bri[ ]/testStatus

This attribute displays the status of the active BRI loop. Possible values are:

Refer to telindus1423Router/bri[ ]/loopbackActivation on page 312 for more information on BRI loops.

Element Description

channel This displays the B-channel number: 1 or 2.

dialMapEntry This indicates which dial map uses this B-channel.

localTelNr This displays which local telephone number is entered in the dial map for this B-channel.

remoteTelNr This displays which remote telephone number is entered in the dial map for this B-channel.

callDirection This displays the call direction of the B-channel. Possible values are: incall, outcall or undefined.

Value Description

progressing The loop is started.

running The loop is active.

ending The loop is ended.

unknown There are two possibilities:

• No loop is active.• For some reason it is not possible to retrieve the status of the loop.



312

telindus1423Router/bri[ ]/loopbackActivation

Use this action to activate a loop on the BRI interface of the Telindus 1423 SHDSL Router. These loops are useful to trace possible problems. First select a loop type (i.e. an argument value), then execute the loopbackActivation action.

The loopbackActivation action has the following argument values:

If a loop is active, then deactivate this loop before starting a new loop.

The following figure gives an overview of the different loops:

telindus1423Router/bri[ ]/clearIsdnCall

Use this action to break off an ISDN call. Do this by typing the dial map name of the corresponding ISDN call as argument value and executing the action.

For example, suppose the ISDN call is initiated by an entry in the dialMaps/mapping table called myMap, then type myMap as argument value of the clearIsdnCall action and execute the action.

Value Description

noLoopback No loop is activated. In case you want to stop a loop, then select this value and execute the loopbackActivation action.

internalLoopback The data coming from the remote side is looped back to the remote side on the BRI interface.

externalLoopback The data coming from the Telindus 1423 SHDSL Router is looped back into the Telindus 1423 SHDSL Router on the BRI interface.



313

MR-2.8.2 B-channel status attributes


• telindus1423Router/bri[ ]/bChannel[ ]/ifDescr on page 314• telindus1423Router/bri[ ]/bChannel[ ]/ifType on page 314• telindus1423Router/bri[ ]/bChannel[ ]/ifOperStatus on page 314• telindus1423Router/bri[ ]/bChannel[ ]/ifLastChange on page 314• telindus1423Router/bri[ ]/bChannel[ ]/ifMtu on page 314• telindus1423Router/bri[ ]/bChannel[ ]/dialMapEntry on page 314• telindus1423Router/bri[ ]/bChannel[ ]/localPhoneNr on page 314• telindus1423Router/bri[ ]/bChannel[ ]/remotePhoneNr on page 314• telindus1423Router/bri[ ]/bChannel[ ]/callDirection on page 314

For the status attributes of the ppp object which is located under the bChannel object, refer to MR-2.5.3 - PPP status attributes on page 285.



314

telindus1423Router/bri[ ]/bChannel[ ]/ifDescr

This attribute displays the interface description of the B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/ifType

This attribute displays the interface type of the B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/ifOperStatus

This attribute displays the current operational status of the B-channel.


telindus1423Router/bri[ ]/bChannel[ ]/ifLastChange

This attribute shows the system-up time on the moment the B-channel entered its current operational state. I.e. the moment the value of the ifOperStatus status attribute changes (from up to down or vice versa), the system-up time value is written into the ifLastChange status attribute.

telindus1423Router/bri[ ]/bChannel[ ]/ifMtu

This attribute displays the B-channel its Maximum Transfer Unit, i.e. the maximum number of bytes that one packet can contain on this B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/dialMapEntry

This attribute displays which dial map uses this B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/localPhoneNr

This attribute displays which local telephone number is entered in the dial map for this B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/remotePhoneNr

This attribute displays which remote telephone number is entered in the dial map for this B-channel.

telindus1423Router/bri[ ]/bChannel[ ]/callDirection

This attribute displays the call direction of the B-channel. Possible values are: incall, outcall or undefined.

Value Description

up The B-channel is up, data transfer is possible.

down The B-channel is down, data transfer is not possible.



315

MR-2.8.3 ISDN leased line status attributes


• telindus1423Router/wanInterface/ifDescr on page 272• telindus1423Router/wanInterface/ifType on page 272• telindus1423Router/wanInterface/ifSpeed on page 272• telindus1423Router/wanInterface/ifMtu on page 272• telindus1423Router/wanInterface/ifLastChange on page 272• telindus1423Router/wanInterface/ifOperStatus on page 272

For the status attributes of the encapsulation objects (frameRelay, ppp, hdlc and errorTest) which are located under the leasedLine[ ] object, refer to MR-2.5 - Encapsulation status attributes on page 274.



316

telindus1423Router/bri[ ]/leasedLine[ ]/ifDescr


telindus1423Router/bri[ ]/leasedLine[ ]/ifType


telindus1423Router/bri[ ]/leasedLine[ ]/ifSpeed


telindus1423Router/bri[ ]/leasedLine[ ]/ifMtu


telindus1423Router/bri[ ]/leasedLine[ ]/ifLastChange


telindus1423Router/bri[ ]/leasedLine[ ]/ifOperStatus

This attribute displays the current operational status of the interface. Possible values are:

Value Description

up The leased line ISDN connection is up, data transfer is possible.

down The leased line ISDN connection is down, data transfer is not possible.

The ifOperStatus attribute is down in case of …

• Frame Relay, when …- LMI is not up.- the line is not in data state.- the bit pump is not synchronised.

• PPP, when …- LCP is not open.- the line is not in data state.- the bit pump is not synchronised.



317

Important remarks

• Whether the Telindus 1423 SHDSL Router is configured in bridging or routing has no effect on the value of the attributes wanInterface/ifOperStatus:Status and wanInterface/alarmInfo/linkDown:Alarms.

• In case of PPP, if the configuration element linkMonitoring/operation is set to disabled, then it is possible that the wanInterface/ifOperStatus value does not go down even if the link quality is too bad for a proper data link. This because the link monitoring mechanism is the only PPP mechanism that will start a renegotiation of the LCP layer.

• In case of Frame Relay, if the configuration element lmi/auto is set to noLmi, then the value of the status element lmi/status:Status is always up. However, the other conditions as stated in the table above remain.



318

MR-2.9 AUX status attributes


• telindus1423Router/aux/ifDescr on page 319• telindus1423Router/aux/ifType on page 319• telindus1423Router/aux/ifOperStatus on page 319• telindus1423Router/aux/ifLastChange on page 319• telindus1423Router/aux/ifSpeed on page 319• telindus1423Router/aux/ifMtu on page 319• telindus1423Router/aux/txdItu103 on page 319• telindus1423Router/aux/rxdItu104 on page 319• telindus1423Router/aux/rtsItu105 on page 319• telindus1423Router/aux/ctsItu106 on page 319• telindus1423Router/aux/dsrItu107 on page 319• telindus1423Router/aux/dtrItu108 on page 319• telindus1423Router/aux/dcdItu109 on page 320• telindus1423Router/aux/riItu125 on page 320

For the status attributes of the dialPpp object which is located under the aux object, refer to MR-2.5.3 - PPP status attributes on page 285.



319

telindus1423Router/aux/ifDescr


telindus1423Router/aux/ifType


telindus1423Router/aux/ifOperStatus

This attribute displays the current operational status of the interface.

telindus1423Router/aux/ifLastChange


telindus1423Router/aux/ifSpeed


telindus1423Router/aux/ifMtu


telindus1423Router/aux/txdItu103

This attribute displays the status (on / off) of the transmit data signal (circuit 103). The txdItu103 attribute only indicates the presence of the TxD signal, it does not monitor the real data signal.

telindus1423Router/aux/rxdItu104

This attribute displays the status (on / off) of the receive data signal (circuit 104). The rxdItu104 attribute only indicates the presence of the RxD signal, it does not monitor the real data signal.

telindus1423Router/aux/rtsItu105

This attribute displays the status (on / off) of the request to send signal (circuit 105).

telindus1423Router/aux/ctsItu106

This attribute displays the status (on / off) of the clear to send signal (circuit 106).

telindus1423Router/aux/dsrItu107

This attribute displays the status (on / off) of the data set ready signal (circuit 107).

telindus1423Router/aux/dtrItu108

This attribute displays the status (on / off) of the data terminal ready signal (circuit 108).



320

telindus1423Router/aux/dcdItu109

This attribute displays the status (on / off) of the data carrier detect signal (circuit 109).

telindus1423Router/aux/riItu125

This attribute displays the status (on / off) of the Ring Indicator signal (circuit 125).



321

MR-2.10 Profile status attributes


• telindus1423Router/profiles/<profile>/profileUsers on page 322



322

telindus1423Router/profiles/<profile>/profileUsers

This attribute shows which profile is applied on which dial map.

The profileUsers table contains the following elements:

Example

Suppose you created an ISDN dial profile (myIsdn) and you applied this profile on 3 dial maps (myMap, yourMap and ourMap), then the profileUsers attribute of the ISDN dial profile displays the following:

Element Description

type This always displays dialmap.

name This is the dial map name. It is the name as you configured it in the name element of the dial map.



323

MR-2.11 Dial maps status attributes





324


This attribute displays the status of all the dial maps. The mapping table contains the following elements:

Element Description

name This displays the dial map name. It is the name as you configured it in the name element of the dial map.

status This displays the dial map status. Possible values are:

• invalidProfile. This means that the dial map refers to a nonexistent profile. In this case, the dial map is not activated.

• standBy. This means the dial map its configuration is valid.

Note that the status element says something about the configuration of the dial map, not about the status of the connections that are defined by this dial map!

connections This displays the status of the active ISDN connection(s) that are defined by the dial map.

Refer to telindus1423Router/dialMaps/mapping/connections on page 325 for a detailed description of the connections table.



325

telindus1423Router/dialMaps/mapping/connections

The connections table in the mapping table displays the status of the active ISDN connection(s) that are defined by the dial map.

The connections table contains the following elements:

Element Description

interface This displays on which interface the connection has been set up.E.g. bri1-bChannel1.

localTelNr This displays the local telephone number of the connection.

remoteTelNr This displays the remote telephone number of the connection.

callDirection This displays the call direction of the connection. Possible values are: incall, outcall or undefined.

connectState This displays the status of the connection. Possible values are:

• notConnected. There is no connection.• callSetup. The call is being set up.• connected. The call was set up successfully.• encapsUp. The encapsulation protocol was set up successfully.• callClear. The call is being cleared.

When a connection is …

• established, the normal procedure is: notConnected → callSetup → connected → encapsUp.

• terminated, the normal procedure is: encapsUp → callClear → notConnected.



326

MR-2.12 Bundle status attributes

This section describes the status attributes of the different bundles that can be set up on the Telindus 1423 SHDSL Router. The following gives an overview of this section:

• MR-2.12.1 - PPP bundle status attributes on page 327



327

MR-2.12.1 PPP bundle status attributes


• telindus1423Router/bundle/pppBundle[ ]/ifDescr on page 328• telindus1423Router/bundle/pppBundle[ ]/ifType on page 328• telindus1423Router/bundle/pppBundle[ ]/ifOperStatus on page 328• telindus1423Router/bundle/pppBundle[ ]/ifSpeed on page 328• telindus1423Router/bundle/pppBundle[ ]/members on page 328• telindus1423Router/bundle/pppBundle[ ]/ip on page 329• telindus1423Router/bundle/pppBundle[ ]/ipcpState on page 329• telindus1423Router/bundle/pppBundle[ ]/ipcpMyOptions on page 330• telindus1423Router/bundle/pppBundle[ ]/ipcpHisOptions on page 330• telindus1423Router/bundle/pppBundle[ ]/bridging on page 331• telindus1423Router/bundle/pppBundle[ ]/bcpState on page 331• telindus1423Router/bundle/pppBundle[ ]/bcpMyOptions on page 331• telindus1423Router/bundle/pppBundle[ ]/bcpHisOptions on page 331• telindus1423Router/bundle/isdnBundle[ ]/bacpState on page 332• telindus1423Router/bundle/isdnBundle[ ]/bacpMyOptions on page 332• telindus1423Router/bundle/isdnBundle[ ]/bacpHisOptions on page 332• telindus1423Router/bundle/isdnBundle[ ]/inBandwidth on page 332• telindus1423Router/bundle/isdnBundle[ ]/outBandwidth on page 332• telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces on page 333



328

telindus1423Router/bundle/pppBundle[ ]/ifDescr

This attribute displays the interface description of the PPP bundle.

telindus1423Router/bundle/pppBundle[ ]/ifType

This attribute displays the interface type of the PPP bundle.

telindus1423Router/bundle/pppBundle[ ]/ifOperStatus

This attribute displays the current operational status of the PPP bundle.

telindus1423Router/bundle/pppBundle[ ]/ifSpeed

This attribute displays the current speed of the PPP bundle in bits per second (bps). It is the sum of the speeds of all the bundle links in the bundle.

telindus1423Router/bundle/pppBundle[ ]/members

This attribute displays the status of the different bundle links in the PPP bundle.

The members table contains the following elements:

Element Description

ifDescr This element displays the name of the bundle link as you entered it in the members configuration attribute.

Refer to MU-7.4.11 - Configuration PPP multiliaisons on page 179 for more infor-mation.

memberStatus This element displays the member status of the bundle link in the bundle. Possible values are:

• notJoined. The bundle link is currently not an active member of the bundle. E.g. because the bundle link is down.

• joined. The bundle link is currently an active member of the bundle.• notFound. The bundle link that you specified in the members configuration attribute

could not be found. E.g. because you entered a wrong channel index name or because you did not create a channel yet.Refer to MU-7.4.11 - Configuration PPP multiliaisons on page 179 for more information on the channels and channel index names.

ifLastChange This element displays the system-up time on the moment the bundle link entered its current operational state. I.e. the moment the value of the memberStatus status element changes (from notJoined to joined or vice versa), the system-up time value is written into the ifLastChange status element.

ifSpeed This element displays the current speed of the bundle link in bits per second (bps).



329

telindus1423Router/bundle/pppBundle[ ]/ip

This attribute displays the IP information of the PPP bundle.


telindus1423Router/bundle/pppBundle[ ]/ipcpState

This attribute reflects the status of the IPCP (Internet Protocol Control Protocol) protocol. Possible val-ues are:

Element Description

status This is the current operational status of the IP layer (layer 3) of the PPP bundle.

address This is the IP address of the PPP bundle. It is either configured or retrieved auto-matically.

netMask This is the IP subnet mask of the PPP bundle. It is either configured or retrieved automatically.

remote This is the IP address of the remote end of the PPP bundle. It is either configured or retrieved automatically.

Value Description

Initial IPCP handshake has not started yet.

Starting, Closed, Stopped, Closing, Stopping

These values correspond with the transient states in the IPCP state diagram.

Req-Sent The local side of the PPP link has sent an IPCP request. The remote side did not answer yet.

Ack-Rcvd The local side of the PPP link has received an IPCP acknowledge from the remote side. This is a transient state.

Ack-Sent The local side of the PPP link has acknowledged the IPCP request from the remote side.

Opened The IPCP handshake succeeded.



330

telindus1423Router/bundle/pppBundle[ ]/ipcpMyOptions

During the IPCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the IPCP options for the router at this side (local side) of the link.

The ipcpMyOptions table contains the following elements:

telindus1423Router/bundle/pppBundle[ ]/ipcpHisOptions

This attribute lists the IPCP options for the router at the other side (remote side) of the link. The ipcpHisOptions table contains the same elements as the ipcpMyOptions table. Refer to telindus1423Router/bun-dle/pppBundle[ ]/ipcpMyOptions on page 330.


Element Description

option The Telindus 1423 SHDSL Router supports the following IPCP option:

• 3: the IP-Address option.• ip-vso: the IP-Vendor Specific Option. This is used to negotiate the netmask.

For more information on the IPCP configuration options, refer to RFC 1332.





331

telindus1423Router/bundle/pppBundle[ ]/bridging

This attribute is not present in the PPP bundle of the ISDN interfaces.

This attribute displays the bridging status of the PPP bundle.


telindus1423Router/bundle/pppBundle[ ]/bcpState


This attribute reflects the status of the BCP (Bridging Control Protocol) protocol. The possible values are the same as those of ipcpState attribute. Refer to telindus1423Router/bundle/pppBundle[ ]/ipcpState on page 329.

telindus1423Router/bundle/pppBundle[ ]/bcpMyOptions


During the BCP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the BCP options for the router at this side (local side) of the link.

The bcpMyOptions table contains the following elements:

telindus1423Router/bundle/pppBundle[ ]/bcpHisOptions


This attribute lists the BCP options for the router at the other side (remote side) of the link. The bcpHisOptions table contains the same elements as the bcpMyOptions table. Refer to telindus1423Router/bundle/pppBundle[ ]/bcpMyOptions on page 331.


Element Description

option The Telindus 1423 SHDSL Router supports the following BCP options:

• 1: the Bridge-Identification option.• 2: the Line-Identification option.• 3: the MAC-Support option.• 4: the Tinygram-Compression option.• 5: the LAN-Identification option.• 6: the MAC-Address option.• 7: the Spanning-Tree-Protocol option.

For more information on the BCP configuration options, refer to RFC 2878.





332

telindus1423Router/bundle/isdnBundle[ ]/bacpState

This attribute is only present in the PPP bundle of the ISDN interfaces.

This attribute reflects the status of the BACP (Bandwidth Allocation Control Protocol) protocol. The pos-sible values are the same as those of ipcpState attribute. Refer to telindus1423Router/bundle/pppBundle[ ]/ipcp-State on page 329.

telindus1423Router/bundle/isdnBundle[ ]/bacpMyOptions


During the BACP handshake, a number of options can be exchanged between the local and remote side of the link. This attribute lists the BACP options for the router at this side (local side) of the link.

The bacpMyOptions table contains the following elements:

telindus1423Router/bundle/isdnBundle[ ]/bacpHisOptions


This attribute lists the BACP options for the router at the other side (remote side) of the link. The bacpHisOptions table contains the same elements as the bacpMyOptions table. Refer to telindus1423Router/bun-dle/isdnBundle[ ]/bacpMyOptions on page 332.


telindus1423Router/bundle/isdnBundle[ ]/inBandwidth


In case BAP is enabled, this attribute shows the amount of bandwidth, in percent, of the total amount of available bandwidth that is currently used.

telindus1423Router/bundle/isdnBundle[ ]/outBandwidth


In case BAP is enabled, this attribute shows the amount of bandwidth, in percent, of the total amount of available bandwidth that is currently not used.

Element Description

option The Telindus 1423 SHDSL Router supports the following BACP options:

• 1: the Favored-Peer option.

For more information on the BACP configuration options, refer to RFC 2125.





333

telindus1423Router/bundle/pppBundle[ ]/multiclassInterfaces


This attribute displays the status of the different multiclass PPP links in the PPP bundle.

The multiclassInterfaces table contains the following elements:

Element Description

name This element displays the name of the multiclass PPP link as you defined it in the multiclassInterfaces configuration attribute.

ifOperStatus This element displays the current operational status of the multiclass PPP link.

ifLastChange This element shows the system-up time on the moment the multiclass PPP link entered its current operational state. I.e. the moment the value of the ifOperStatus status attribute changes (from up to down or vice versa), the system-up time value is written into the ifLastChange status attribute.

ip This element displays the IP information of the multiclass PPP link.


bridging This element displays the bridging information of the multiclass PPP link.


ppp This element displays the PPP information of the multiclass PPP link.

Refer to for a detailed description of the elements in the ppp structure.

multiclass This element displays the multiclass identifier of the multiclass PPP link.



334

MR-2.13 Router status attributes

This section discusses the status attributes concerned with routing. First it describes the general routing status attributes. Then it explains the status attributes of the extra features as there are NAT, L2TP tun-nelling, etc…


• MR-2.13.1 - General router status attributes on page 335• MR-2.13.2 - NAT status attributes on page 345• MR-2.13.3 - L2TP tunnel status attributes on page 347• MR-2.13.4 - IKE SA status attributes on page 352• MR-2.13.5 - OSPF status attributes on page 354• MR-2.13.6 - VRRP status attributes on page 372• MR-2.13.7 - Firewall status attributes on page 374



335

MR-2.13.1 General router status attributes


• telindus1423Router/ip/router/routingTable on page 336• telindus1423Router/ip/router/igmpTable on page 339• telindus1423Router/ip/router/dhcpBinding on page 341• telindus1423Router/ip/router/dhcpStatistics on page 341• telindus1423Router/ip/router/dhcpRelayInfo on page 342• telindus1423Router/ip/router/dhcpBlackList on page 342• telindus1423Router/ip/router/radius on page 343• telindus1423Router/ip/router/dns on page 343• telindus1423Router/ip/router/dnsServers on page 343• telindus1423Router/ip/router/addrPools on page 344


• telindus1423Router/ip/router/unBlacklist on page 344



336


This attribute lists all known routes (both static and learned routes) with their operating status.

The routingTable contains the following elements:

Element Description

network This is the IP address of the destination network.

mask This is the network mask of the destination network.

gateway This is the IP address of the next router on the path to the destination network.

interface This is the interface through which the destination network can be reached. Pos-sible values are:

• internal. The own protocol stack is used.• <name>. The destination network can be reached through this particular inter-

face. The <name> of the interface is the name as you configured it.Note that the “interface” can also be a DLCI, an ATM PVC, a tunnel, etc.

• discard. Packets for this destination are discarded.

encapsulation This is the used encapsulation. It is related to the interface for this route. Possible values are:

• none. The IP packets are not encapsulated.• ethernet. The IP packets are encapsulated with the ARPA MAC header.• frameRelay. The IP packets are encapsulated in Frame Relay.• ppp. The IP packets are encapsulated in PPP.• atm. The IP packets are encapsulated in ATM.



337

status This is the route status. Possible values are:

• up. The route is up, data transfer is possible.• down. The route is down, data transfer is not possible.• discard. Packets for this destination are discarded.• spoofing. This applies on routes over an ISDN dial-up connection or through an

L2TP outgoing dial tunnel.It means that the route is available, but that it is not truly up (yet). I.e. the (dial) connection can be made, but is currently not up. As soon as a connection is established, then the status of the route changes from spoofing to up.

• holdDown. This applies on RIP routes.A route enters into a hold-down state when an update packet is received that indicates the route is unreachable. The route is marked inaccessible and adver-tised as unreachable. However, the route is still used for forwarding packets. When hold-down expires, routes advertised by other sources are accepted and the route is no longer inaccessible.Refer to telindus1423Router/ip/router/ripHoldDownTime on page 131 for more informa-tion.

• closed. This applies on L2TP tunnels and VRRP. In case of …- L2TP tunnels where you configure a main and a backup tunnel (refer to MU-

10.5.4 - Configuration d’un tunnel principal et de secours on page 351) and the main tunnel goes down, then it is not desirable that the route to the main tunnel its status returns from up to spoofing because in that case the Telindus 1423 SHDSL Router will keep trying to send data across the main route/tun-nel. That is why in such a case the route to the main tunnel is “artificially” blocked. I.e. its status is set to closed.

- VRRP (refer to MU-8.9 - Configuration de VRRP on page 270), it is some-times desirable that the IP address on an Ethernet interface no longer answers to pings, even if the Ethernet interface is up. That is why in such a case the host route is “artificially” blocked. I.e. its status is set to closed.

preference This displays the route preference. If more than one route matches the IP destina-tion address, this attribute determines which route is used. The route with the low-est preference value will be used.

type This is the type of the route. Possible values are:

• host. This is a host route, i.e. a route to a single IP address instead of a complete network. This is also used for the router its own IP address.

• internal. A route with this status is irrelevant.• local. This is a route to a directly connected network.• rip. This is a route that has been received via a RIP update.• static. This is a route that has been configured, i.e. it is a static route.• float. This is a route that has been added for a PPP link for which no local or

remote IP address was configured. These were learned from the other side. Refer to MU-7.4.4 - Imposition d’adresses IP au terminal distant dans PPP on page 169 for more information.

Element Description



338

Example

The following figure displays an example of a routing table:

The lines in the routing table depicted above represent the following:

• Line 1 represents the default gateway, which is not defined.• Lines 2 and 5 represent the subnets on the LAN and WAN interface respectively.• Lines 3 and 6 represent the interface its IP addresses.• Line 7 represents the static route to the remote LAN.• Finally, line 4 represents the multicast address for RIP version 2.

Remark

If the LAN is not connected to the Telindus 1423 SHDSL Router, it is still possible to contact the Telindus 1423 SHDSL Router with e.g. TMA or Telnet over the WAN link by using the IP address of the LAN inter-face. This means that the status attribute telindus1423Router/lanInterface/ip/status still indicates up, although in the routingTable the corresponding route to the network is down. This implementation seems not logical but is necessary to insure correct operation with HP OpenView.

metric If two routes exist with the same preference, then the route with the lowest metric value is chosen. The metric attribute serves as a cost for using the route. In most cases it indicates the number of hops (= routers) required to reach a destination.

timeOut In case of a RIP route, the timeOut attribute displays the time the route will remain in the routing table if no RIP updates are received anymore. For other routes this attribute always displays 00000d 00h 00m 00s.

Element Description



339

telindus1423Router/ip/router/igmpTable

This attribute shows the multicast address, reported by one or more clients. The igmpTable is always updated, even if no proxy is configured.

The igmpTable contains the following elements:

What is IGMP?

Internet Group Management Protocol (IGMP) is defined in RFC 1112 as the standard for IP multicasting in the Internet.

It is used to establish host memberships in particular multicast groups on a single network. The mecha-nisms of the protocol allow a host to inform its local router, using Host Membership Reports, that it wants to receive messages addressed to a specific multicast group.

All hosts conforming to level 2 of the IP multicasting specification require IGMP.

IGMP topology

Consider the following multicasting topology:

In this topology …

• Client 1 and Client 2 are multicast clients.• Router 1, 2 and 3 are multicast enabled routers.• Server 1 is a multicast server.

Element Description

multicast This is the multicast address.

interface This is the interface name of the client(s). In case of multiple interface names, they are separated from each other by a comma.



340

The following are some characteristics of an IGMP topology:

• Only 1 IGMP proxy can be defined per device.• The TTL of an IGMP frame is always 1. IGMP messages are never forwarded.• An IGMP frame contains an IP router alert option.• IGMPv1 routers may be present in the network.

The multicasting IGMP protocol can be configured on every IP interface. Refer to the igmp element in MU-5.2.3 - Explication de la structure ip on page 63.

A client can leave or join a multicast group by erasing or adding a multicast address from a table, defined in the client application. A list of multicast group addresses is maintained in the routers. The reported multicast addresses can be seen in the igmpTable. Refer to telindus1423Router/ip/router/igmpTable on page 339.

On a router interface, IGMP join and leave messages are interpreted and the multicast member list is adapted accordingly. Multicast frames are forwarded if they are present in the multicast member list. On a proxy interface, IGMP join and leave messages are transmitted according to the multicast member list. Multicast frames are always forwarded.

Since IGMP is send in UDP (join/leave can be lost), the clients (proxies) are polled every 125 seconds:

• A general query is send to 224.0.0.1 (poll all systems).• A leave group message is send to 224.0.0.2 (all routers).



341

telindus1423Router/ip/router/dhcpBinding

This attribute contains a list of dynamically assigned (i.e. leased) IP addresses.

The dhcpBinding table contains the following elements:

telindus1423Router/ip/router/dhcpStatistics

This attribute contains the statistics of all IP address ranges that have been specified in the configuration attribute telindus1423Router/ip/router/dhcpDynamic.

The dhcpStatistics table contains the following elements:

During power-down of the DHCP server, some leased IP addresses can still be active. Because the duration of the power-down can not be known, all timer information about lease and hold time becomes meaningless. Therefore, the DHCP server incorporated in the Telindus 1423 SHDSL Router sends a ping to all leased addresses after a warm boot. When the client responds to this ping, the DHCP server resets all timers to their default value and keeps the lease with this client.

Element Description

ipAddress This is the IP address that is dynamically assigned to a client.

macAddress This is the MAC address of the client.

leaseTime This is the remaining lease time.

hostName This is the hostname of the client.

interface This is the name of the interface on which the client has been bound.

state This is the state of the lease. Possible values are leased and onHold.

Element Description

startRange Displays the IP start address of an IP address range.

endRange Displays the IP end address of an IP address range.

interface For the corresponding IP address range, this is the name of the interface on which the clients have been bound.

free For the corresponding IP address range, this displays the number of IP addresses that are still free.

leased For the corresponding IP address range, this displays the number of IP addresses that are leased.

hold For the corresponding IP address range, this displays the number of IP addresses that are on hold.



342

telindus1423Router/ip/router/dhcpRelayInfo

This attribute displays the status information of the DHCP relay process in case the Telindus 1423 SHDSL Router is configured to act as DHCP relay agent.

The dhcpRelayInfo table contains the following elements:

telindus1423Router/ip/router/dhcpBlackList

This attribute displays the MAC and IP address of blacklisted clients and the reason why they are on the black list.

The dhcpBlackList table contains the following elements:

Element Description

sourceIntf This is the name of the interface on which the DHCP request has been received.

mac This is the MAC address of the client.

assignedIp This is the IP address that has been dynamically assigned to the client by the remote DHCP server.

serverIp This is the IP address of the remote DHCP server.

dhcpStatus This is the status of the DHCP process. Possible values are: discover, offer, request, decline, ack, nack, release, inform, idle.

leaseTime This is the remaining lease time.

Element Description

ipAddress This is the IP address of the blacklisted client.

macAddress This is the MAC address of the blacklisted client.

reason This is the reason why the client is on the black list. Possible values are:

• arp. The ARP request probing indicated that the IP address is already in use by a client on the network. Refer to telindus1423Router/ip/router/dhcpCheckAddress on page 141.

• ping. The ICMP Echo Request (ping) probing indicated that the IP address is already in use by a client on the network. Refer to telindus1423Router/ip/router/dhcp-CheckAddress on page 141.

• alienAck. Another DHCP server assigned an IP address to the client.• declined. The client explicitly declined the IP address that was assigned.• networkOrBroadcast. The DHCP server tried to assign a network or broadcast

address to a client. This indicates that the IP address ranges in the DHCP server have been misconfigured.



343

telindus1423Router/ip/router/radius

This attribute shows some RADIUS status information. Refer to Qu'est-ce que le RADIUS ? on page 376 for more information.

The radius structure contains the following elements:

telindus1423Router/ip/router/dns

This attribute shows some DNS status information. Refer to What is DNS? on page 509 for more infor-mation.

The dns table contains the following elements:

telindus1423Router/ip/router/dnsServers

This attribute displays the IP address(es) of the DNS server(s) that have been configured or learned.

The dns table contains the following elements:

Element Description

authServer This is the IP address of the authentication server the Telindus 1423 SHDSL Router is connected to.

acctServer This is the IP address of the accounting server the Telindus 1423 SHDSL Router is connected to.

pendingRequests This is the amount of pending requests on these servers.

Element Description

ipAddress This is the IP address of the DNS server.

hostname This is the hostname of the DNS server.

ttl This is the time-to-live of the cached DNS data.

infiniteTimeOut This indicates that the DNS record has an infinite TTL or at least longer than 24 days.

Element Description

primaryDns This is the IP address of the primary DNS server.

secondaryDns This is the IP address of the secondary DNS server.



344

telindus1423Router/ip/router/addrPools

This attribute shows which IP addresses have already been picked out of the IP address pool. Refer to Qu'est-ce qu'un pool d'adresses IP ? on page 65 for more information.

The addrPools table contains the following elements:

telindus1423Router/ip/router/unBlacklist

This action removes an entry from the blacklist.

The unBlacklist action contains the following argument values:

Element Description

name This is the name of the IP address pool, as you configured it, from which the IP addresses have been picked.

type This is the type of IP address pool from which the IP addresses have been picked. Possible values are: list or interval.

local This is the local IP address that has been picked out of the IP address pool.

remote This is the remote IP address that has been picked out of the IP address pool.

netMask This is the subnet mask that has been picked out of the IP address pool.

interface This is the name of the interface on which the IP addresses are used.

Element Description

startIp Use this element to specify an IP address (range) that has to be removed from the blacklist.

If you want to specify …

• a single IP address, then just enter the IP address in the startIp element and leave the stopIp element at its default value (<opt>).

• an IP address range, then enter the first IP address of the range in the startIp element and the last IP address of the range in the stopIp element.

stopIp Use this element to specify the last IP address of an IP address range that has to be removed from the blacklist.

mac Use this element to specify a MAC address of an entry that has to be removed from the blacklist.



345

MR-2.13.2 NAT status attributes


• telindus1423Router/ip/router/defaultNat/addresses on page 346



346

telindus1423Router/ip/router/defaultNat/addresses

This attribute displays the status of each official IP address that is configured in the configuration attribute telindus1423Router/ip/router/defaultNat/addresses.

The addresses table contains the following elements:

Element Description

officialAddress This is the official IP address as you entered it in the addresses configuration attribute.

privateAddress This is the private IP address that is currently linked with the official IP address.

status This is the status of the official IP address. Possible values are:

• free. This official IP address is currently not in use.• fixed. This address has a pre-configured mapping between the official and pri-

vate IP address.• allocated. This official IP address is currently assigned to a private IP address,

but it is not fixed.

uses This indicates how many sessions are currently used by this official IP address.

If the attribute value becomes zero, the assigned official IP address becomes free again and can be assigned to another private IP address.



347

MR-2.13.3 L2TP tunnel status attributes





348


This attribute displays status information of the L2TP tunnels.


Element Description

name This is the name of the tunnel as you configured it. If you did not configure a name, then this element displays: “tunnel” <local IP address of the tunnel>.

E.g. tunnel 192.168.5.1

ifOperStatus This displays the operational status of the tunnel. Possible values are:

• up. The tunnel is up, data transfer is possible.• down. The tunnel is down, data transfer is not possible.• dormant. The tunnel is "stand-by". As soon as data has to be sent over the tun-

nel, control connect messages are exchanged and the operational status of the tunnel becomes up.

ifLastChange This is the system-up time on the moment the tunnel entered its current opera-tional state. I.e. the moment the value of the ifOperStatus status element changes (from up to down or vice versa), the system-up time value is written into the ifLastChange status element.

ip This displays the IP information of the tunnel.


bridging This displays the bridging information of the tunnel.


l2tp This displays the specific L2TP related status information of the tunnel.

Refer to the telindus1423Router/ip/router/tunnels/l2tpTunnels/l2tp on page 349 for a detailed description of the l2tp structure.

ppp This displays the PPP information of the tunnel.

Refer to MR-2.5.3 - PPP status attributes on page 285 for a detailed description of the elements in the ppp structure.



349

telindus1423Router/ip/router/tunnels/l2tpTunnels/l2tp

The l2tp structure in the l2tpTunnels table displays the specific L2TP related status information of the tun-nel.

The l2tp structure contains the following elements:


This attribute displays status information of the IPSEC L2TP tunnels.

The ipsecL2tpTunnels table contains the same elements as the l2tpTunnels table. Refer to telindus1423Router/ip/router/tunnels/l2tpTunnels on page 348.

Element Description

sendingSeqNum In case sequence numbering on the data messages is enabled (dataChannelSequen-ceNumbering = on), then this displays the transmit data sequence numbers.

receivingSeqNum In case sequence numbering on the data messages is enabled (dataChannelSequen-ceNumbering = on), then this displays the receive data sequence numbers.

l2tpType This displays which L2TP server type the Telindus 1423 SHDSL Router currently is: LAC or LNS.

If you set the configuration attribute l2tpMode to auto, then the status attribute l2tpType displays the auto value until the Telindus 1423 SHDSL Routers have mutually decided who will be the LAC and who the LNS.

controlState This displays the states associated with the LNS or LAC control connection estab-lishment. Refer to L2TP status - control states on page 350 for more information.

callState This displays the states associated with the LNS or LAC incoming or outgoing calls. Refer to L2TP status - call states on page 350 for more information.

deliveryState This displays the states associated with the LNS or LAC packet delivery. Refer to L2TP status - delivery states on page 351 for more information.

authenState This displays the states associated with the LNS or LAC authentication. Refer to L2TP status - authentication states on page 351 for more information.



350

L2TP status - control states

The states associated with the LNS or LAC for control connection establishment are:

L2TP status - call states

The states associated with the LNS or LAC incoming or outgoing calls are:

Value Description

idle No control connection is present.

Both initiator and recipient start from this state. An initiator transmits a Start Control Connection Request, while a recipient remains in the idle state until receiving a Start Control Connection Request.

waitCtlReply This is the state where a Start Control Connection Reply is awaited.

waitCtlConn This is the state where a Start Control Connection Connected is awaited. Upon receipt, the challenge response is checked. The tunnel either is established, or is torn down if an authorisation failure is detected.

established The control connection is established.

An established connection may be terminated by either a local condition or the receipt of a Stop Control Connection Notification. The session then returns to the idle state.

Value Description

idle No data is exchanged over the tunnel.

waitTunnel This is the state in which is waited …

• either for the control connection to be opened,• or for verification that the tunnel is already open.

Once an indication is received that the tunnel has/was opened, session control messages may be exchanged. The first of these is the Incoming Call Request.

waitReply This is the state where an Incoming or Outgoing Call Reply message is awaited. If an Incoming or Outgoing Call Reply message is received, an incoming or Outgoing Call Connected message is sent and the session moves to the established state.

waitConnect This is the state where an Incoming or Outgoing Call Connected message is awaited. If an Incoming or Outgoing Call Connected message is received, the call was successful and the session moves to the established state.

established Data is exchanged over the tunnel.

The session is terminated when receiving or sending a Call Disconnect Notify mes-sage. The session then returns to the idle state.



351

L2TP status - delivery states

The states associated with the packet delivery are:

L2TP status - authentication states

The states associated with the LNS or LAC authentication are:

Value Description

operating The Telindus 1423 SHDSL Router has sent a packet, but has not received an acknowledgement on this packet yet.

idle All transmitted packets have been acknowledged.

Value Description

noAuthentication Authentication is not enabled. This is also the start-up state for the authentication process.

authenSuccessful Authentication was successful. The Telindus 1423 SHDSL Router remains in this state during data transfer.

authenFailure Authentication failed. This is a transient state since the Telindus 1423 SHDSL Router starts the handshake again after a failing authentication.



352

MR-2.13.4 IKE SA status attributes


• telindus1423Router/ip/router/ikeSA[ ]/phase1 on page 353• telindus1423Router/ip/router/ikeSA[ ]/phase2 on page 353


• telindus1423Router/ip/router/ikeSA[ ]/clearSAs on page 353



353


This attribute displays status information of phase 1 in the IKE negotiation process.

The phase1 table contains the following elements:


This attribute displays status information of phase 2 in the IKE negotiation process.


telindus1423Router/ip/router/ikeSA[ ]/clearSAs

Use this action to clear all SAs.

Element Description

remoteIp This element displays the IP address of the remote.

remainingSecs This element displays the time the IKE SA will remain active for.

Element Description

tunnel This element displays the L2TP tunnel name.

direction This element displays the direction of the IPSEC SA. Possible values are: inbound or outbound.

spi This element displays the Security Parameter Index of the IPSEC SA.

protocol This element displays which protocol is used in the IPSEC SA. Possible values are: esp or ah.

localIp This element displays the local IP address.

remoteIp This element displays the remote IP address.

encryptionAlgorithm This element displays which encryption algorithm is used on the IPSEC SA. Pos-sible values are: null, des, 3des or disabled.

authenticationAlgo-rithm

This element displays which authentication algorithm is used on the IPSEC SA. Possible values are: hmac_md5, hmac_sha-1 or disabled.

age This element displays the age of the IPSEC SA.

softLifeTime This element displays the soft life time of the IPSEC SA.

When the soft life time expires, the IKE peers know that the hard lifetime is about to expire. This gives them the time to rekey the SA without disrupting communica-tion before the hard lifetime expires.

hardLifeTime This element displays the hard life time of the IPSEC SA.

When the hard life time expires, the IPSEC SA is actually disconnected.



354

MR-2.13.5 OSPF status attributes

This section discusses the status attributes concerned with OSPF. First it describes the general OSPF status attributes. Then it explains the OSPF area status attributes.


• General OSPF status attributes on page 355• Area status attributes on page 360



355

General OSPF status attributes


• telindus1423Router/ip/router/ospf/type on page 356• telindus1423Router/ip/router/ospf/routes on page 357• telindus1423Router/ip/router/ospf/externalRoutes on page 358• telindus1423Router/ip/router/ospf/asExtLsas on page 359



356

telindus1423Router/ip/router/ospf/type

This attribute indicates the kind of router link being described.

The type structure contains the following elements

Element Description

areaBorder This element indicates whether the router is an Area Border Router.

asbr This element indicates whether the router is an Autonomous System Border Router.

Refer to MU-8.6.1 - Introduction à OSPF on page 220 for more information.

virtualLink This element indicates whether a virtual link is present on the router.

wildCardMulticast This element indicates whether multicast extensions are supported by the router.

Note that wildcard multicast is not yet supported by the Telindus 1423 SHDSL Router.

nssaTranslator This element indicates whether the router is an NSSA border router translator.



357

telindus1423Router/ip/router/ospf/routes

This attribute displays all detected routes in the OSPF network. All detected routes are transferred to the routing table of this router as type OSPF.

The routes table contains the following elements:

Element Description

network This element displays the IP address of the sub network.

mask This element displays the network mask.

type This element displays the type of the network. Possible values are:

• direct. This value indicates a direct route. This is a route to a host connected directly to the router.

• intra. This value indicates an intra-area route. This is a route with destinations belonging to one of the router's attached areas.

• inter. This value indicates an inter-area route.This is a route with destinations in other OSPF areas.

• extType1. This value indicates an external route of type 1.• extType2. This value indicates an external route of type 2.• reject. This value indicates a rejected route.• static. This value indicates a static route.• none. This value indicates a non-existing route.

cost This element displays the cost of the route.

There are two exceptions, when another value is displayed. These are:

• unknown. This value indicates that the cost of the route is unknown.• infinite. This value indicates that the route is not available.

gateway This element displays the IP address of the next interface on the path to the des-tination network.

outgoingIp This element displays the IP address of the outgoing router interface.

interface This element displays the administrative name of the interface.



358

telindus1423Router/ip/router/ospf/externalRoutes

This attribute displays all external routes which are injected into the OSPF network by this router.

The externalRoutes table contains following elements:

Element Description

network This element displays the IP address of the sub network.

mask This element displays the network mask.

gateway This element displays the IP address of the next interface on the path to the des-tination network.

interface This element displays the administrative name of the interface.

costType This element displays the type of cost of the external route. Possible values are:

• type1. The type of cost of the external route is type 1.• type2. The type of cost of the external route is type 2.

Also refer to telindus1423Router/ip/router/ospf/importFilter on page 182.


There are two exceptions, when another value is displayed. These are:

• unknown. This value indicates that the cost of the route is unknown.• infinite. This value indicates that the route is not available.

tag This element displays the 32-bit field attached to each external route. This is not used by the OSPF protocol itself. It is used to communicate information between AS boundary routers.

advertise This element displays whether the router advertises the external route to the rest of the OPSF network. Possible values are:

• yes. The router advertises the external route to the rest of the OPSF network.• no. The router does not advertise the external route to the rest of the OPSF net-

work.

routeType This element displays how the external route is injected into OSPF. Possible val-ues are:

• static. Static route configured by the user.• rip. This route was learned through the rip protocol.



359

telindus1423Router/ip/router/ospf/asExtLsas

This attribute displays the database entries for all external routes in the OSPF network.

The asExtLsas table contains following elements:

Element Description

linkStateId This element displays the portion of the network that is being described by the LSA. The contents of this field depend on the type of LSA.

advRouterId This element displays the router ID of the router that originated the LSA.

age This element displays the time in seconds since the LSA was originated.

sequenceNr This element displays the LS sequence number (successive instances of an LSA are given successive LS sequence numbers).

options This element indicates if the advertising router supports optional OSPF capabili-ties. Routers of differing capabilities can be mixed within an OSPF routing domain.

The options structure contains the following elements:

• floodExternal. Entire OSPF areas can be configured as "stubs". AS-external-LSAs will not be flooded into stub areas. This capability is represented by the element floodExternal.

• multicast. This element indicates whether IP multicast datagrams are forwarded.• nssa. This element indicates whether the router supports nssa area‘s.• externalAttributes. This element indicates the router's willingness to receive and

forward external LSAs.• demandCircuit. This element indicates the router's handling of demand circuits.• opaque. This element indicates if the router can handle opaque-LSAs.

netMask This element displays the IP address mask for the advertised destination.



Also refer to telindus1423Router/ip/router/ospf/importFilter on page 182.

cost This element displays the cost of this route.

tag This element displays a 32-bit field attached to each external route. This is not used by the OSPF protocol itself. It is used to communicate information between AS boundary routers.

forwardAddress This element displays the address to which data traffic for the advertised destina-tion is forwarded to.



360

Area status attributes


• telindus1423Router/ip/router/ospf/area[ ]/interfaces on page 361• telindus1423Router/ip/router/ospf/area[ ]/hosts on page 363• telindus1423Router/ip/router/ospf/area[ ]/neighbors on page 363• telindus1423Router/ip/router/ospf/area[ ]/routers on page 365• telindus1423Router/ip/router/ospf/area[ ]/routerLsas on page 366• telindus1423Router/ip/router/ospf/area[ ]/networkLsas on page 368• telindus1423Router/ip/router/ospf/area[ ]/summLsas on page 369• telindus1423Router/ip/router/ospf/area[ ]/asbrLsas on page 370• telindus1423Router/ip/router/ospf/area[ ]/nssaLsas on page 371



361

telindus1423Router/ip/router/ospf/area[ ]/interfaces

This attribute displays all interfaces available in the area. If an interface is part of more than one network, the interface belongs to the network with the most significant subnet mask.

The interfaces table contains following elements:

Element Description

name This element displays the name of the interface.

address This element displays the IP address of the interface.

netMask This element displays the subnet mask.

network This element displays the name of the sub network the interface is part of.

type This element displays the interface type. Possible values are:

• pointToPoint: The interface is a point-to-point interface.• broadcast: The interface is a broadcast interface.• virtualLink: The interface is a virtual link interface.• loopback: The interface is a loopback interface.

cost This element displays the cost of the link.

priority This element displays the priority of the network.

status This element displays the status of the router interface.

Refer to telindus1423Router/ip/router/ospf/area[ ]/interfaces/status on page 362 for more infor-mation.

dr This element displays the IP address of the Designated Router of the sub network.

backupDr This element displays the IP address of the Backup Designated Router.

neighbors This element displays the amount of neighbors of the router.

adjNeighbors This element displays the amount of adjacent neighbors of the router.

bandwidth This element displays the bandwidth of the link.



362

telindus1423Router/ip/router/ospf/area[ ]/interfaces/status

The states are listed in order of progressing functionality. For example, the inoperative state is listed first, followed by a list of intermediate states before the final, fully functional state is achieved.


Value Description

unknown The router status is unknown.

down This is the initial interface state. No protocol traffic at all will be sent or received.

loopback The router's interface to the network is looped back. The interface will be unavail-able for regular data traffic.

waiting The router is trying to determine the identity of the (Backup) Designated Router for the network. To do this, the router monitors the Hello Packets it receives. The router is not allowed to elect a Backup Designated Router nor a Designated Router until it transitions out of Waiting state. This prevents unnecessary changes of (Backup) Designated Router.

pointToPoint The interface is operational, and connects either to a physical point-to-point net-work or to a virtual link. Upon entering this state, the router attempts to form an adjacency with the neighbouring router. Hello Packets are sent to the neighbour every helloInterval seconds.

drOther The interface is connected to a broadcast or NBMA network on which another router has been selected to be the Designated Router. In this state, the router itself has not been selected Backup Designated Router either. The router forms adja-cencies to both the Designated Router and the Backup Designated Router (if they exist).

backupDr The router itself is the Backup Designated Router on the attached network. It will be promoted to Designated Router when the present Designated Router fails. The router establishes adjacencies to all other routers attached to the network.

dr In this state, this router itself is the Designated Router on the attached network. Adjacencies are established to all other routers attached to the network. The router must also originate a network-LSA for the network node.



363

telindus1423Router/ip/router/ospf/area[ ]/hosts

This attribute displays all hosts in the OSPF network.

Loopback interfaces that are added to the OSPF network are referred to as hosts. The loop-back inter-face is a software interface which can be used for management purposes. This interface is always up, regardless of the state of the physical interfaces.

The hosts table contains following elements

telindus1423Router/ip/router/ospf/area[ ]/neighbors

This attribute displays the neighbours of the router.

Routers that share a common segment become neighbours on that segment. Neighbours are discov-ered via the Hello protocol. Bidirectional communication is indicated when the router sees itself listed in the neighbour’s Hello Packet.

The neighbors table contains following elements:

Element Description

intfName This element displays the administrative name of the loop-back interface.

address This element displays the IP address of the loop-back interface.

netMask This element displays the subnet mask of the loop-back interface.

network This element displays the administrative name of the network that the loop-back interface is part of.

cost This element displays the cost of the loop-back interface link.

Element Description

interface This element displays the administrative name of the neighbouring interface.

routerId This element displays the unique sequence number for the router in the OSPF net-work.

routerPriority This element displays the priority of the neighbouring router.

ipAddress This element displays the IP address of the neighbouring interface.

status This element displays the status of the neighbouring router.

Refer to telindus1423Router/ip/router/ospf/area[ ]/neighbors/status on page 364 for more infor-mation.



364

telindus1423Router/ip/router/ospf/area[ ]/neighbors/status

The states are listed in order of progressing functionality. For example, the inoperative state is listed first, followed by a list of intermediate states before the final, fully functional state is achieved.


Value Description

down This is the initial state of a neighbour conversation. It indicates that there has been no recent information received from the neighbour.

attempt This state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbour, but that a more con-certed effort should be made to contact the neighbour. This is done by sending the neighbour Hello packets at intervals of helloInterval

init An Hello packet has recently been seen from the neighbour. However, bidirec-tional communication has not yet been established with the neighbour (i.e., the router itself did not appear in the neighbour’s Hello packet). All neighbors in this state (or higher) are listed in the Hello packets sent from the associated interface.

2way Communication between the two routers is bidirectional. This has been assured by the operation of the Hello Protocol.

exchangeStart This is the first step in creating an adjacency between the two neighbouring rout-ers. The goal of this step is to decide which router is the master. Neighbour con-versations in this state or greater are called adjacencies.

exchange The router is describing its entire link state database by sending Database Description packets to the neighbour. Link State Request Packets may also be sent asking for the neighbour’s more recent LSAs.

loading Link State Request packets are sent to the neighbour asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state.

fullAdjacency The neighbouring routers are fully adjacent. These adjacencies will now appear in router-LSAs and network-LSAs.



365

telindus1423Router/ip/router/ospf/area[ ]/routers

This attribute displays all routers in the current area.

The routers table contains following elements:

Element Description

routerId This element displays the unique sequence number for the router in this OSPF autonomous system.

gateway This element displays the IP address of the next interface on the path to reach this router.


routerType This element indicates which type of router is detected.

The routerType structure contains the following elements:

• areaBorder. This element indicates that the detected router is an Area Border Router (ABR).

• asbr. This element indicates that the detected router is an Autonomous System Border Router (ASBR).

• virtualLink. This element indicates that the link to the detected router is a virtual link.

• wildCardMulticast. This element indicates if multicast extensions are supported by the router.



366

telindus1423Router/ip/router/ospf/area[ ]/routerLsas

This attribute displays the router-LSAs.

Each router in an area originates router-LSAs. The LSA describes the state and cost of the router's links (i.e., interfaces) to the area. All of the router's links to the area must be described in a single router-LSA.

The routerLsas table contains following elements:

Element Description

linkStateId This element displays the router's OSPF Router ID.

It displays the portion of the network that is being described by the LSA. The con-tents of this field depend on the type of LSA.

advRouterId This element displays the router ID of the router that originated the LSA.




The options structure contains following elements:




routerType This element indicates the kind of router link being described. The routerType struc-ture contains following elements:

• areaBorder. This element indicates a link to an ABR.• asbr. This element indicates a link to an ASBR.• virtualLink. This element indicates a virtual link.• wildCardMulticast. This element indicates a multicast link.

linkNr This element displays the number of router links described in this LSA.

linkId This element identifies the object that this router link connects to. When connecting to an object that also originates an LSA (i.e., another router or a transit network) the Link ID is equal to the neighbouring LSAs Link State ID. This provides the key for looking up the neighbouring LSA in the link state database during the routing table calculation.



367

linkData The value of this element depends on the linkType:

• For connections to stub networks, linkData specifies the network's IP address mask.

• For unnumbered point-to-point connections, it specifies the interface's MIB-II interface Index value.

• For the other link types it specifies the router interface's IP address.

This latter piece of information is needed during the routing table build process, when calculating the IP address of the next hop.

linkType This element displays the type of the link. Possible values are:

• pointToPoint. The link is a point-to-point connection.• transit. The link is a transit connection.• stub. The link is a connection within a stub area.• virtualLink. The link is a virtual link.

cost This element displays the cost of this link.

Element Description



368

telindus1423Router/ip/router/ospf/area[ ]/networkLsas

This attribute displays the network-LSAs.

A network-LSA is originated for each network in the area which supports two or more routers. The net-work-LSA is originated by the network's Designated Router. The LSA describes all routers attached to the network, including the Designated Router itself.

The networkLsas table contains following elements:

Element Description

linkStateId This element displays the IP interface address of the Designated Router.

It displays the portion of the network that is being described by the LSA. The con-tents of this field depend on the type of LSA.

AdvRouterId This element displays the router ID of the router that originated the LSA.








netMask This element displays the IP address mask for the network.

linkNr This element displays the number of router links described in this LSA.

routerId This element displays the router IDs of each of the routers attached to the network. Only those routers that are fully adjacent to the Designated Router are listed. The Designated Router itself is included in this list.



369

telindus1423Router/ip/router/ospf/area[ ]/summLsas

This attribute displays the Summary-LSAs. Summary-LSAs are originated by area border routers and describe inter-area destinations.

The summLsas table contains following elements:

Element Description

linkStateId If the destination is an IP network, then the linkStateId element is an IP network number. If the destination is an AS boundary router, then the linkStateId element is the AS boundary router's OSPF Router ID.

This element displays the portion of the network that is being described by the LSA. The contents of this field depend on the type of LSA.









netMask This element displays the IP address mask for the destination network.




370

telindus1423Router/ip/router/ospf/area[ ]/asbrLsas

This attribute displays the ASBR-LSAs.

The asbrLsas table contains following elements:

Element Description













371

telindus1423Router/ip/router/ospf/area[ ]/nssaLsas

This attribute displays the NSSA-LSAs.

The nssaLsas table contains following elements:

Element Description










netMask This element displays the IP address mask for the advertised destination.




tag This element displays a 32-bit field attached to each external route. This is not used by the OSPF protocol itself. It is used to communicate information between AS boundary routers.

forwardAddress This element displays the address to which data traffic for the advertised destina-tion is forwarded to.



372

MR-2.13.6 VRRP status attributes


• telindus1423Router/ip/router/vrrp[ ]/macAddress on page 373• telindus1423Router/ip/router/vrrp[ ]/interfaces on page 373• telindus1423Router/ip/router/vrrp[ ]/criticals on page 373



373

telindus1423Router/ip/router/vrrp[ ]/macAddress

This attribute displays the for VRRP reserved MAC address. The first 5 bytes are fixed (00:00:5e:00:01). The last byte is the virtual router ID.

telindus1423Router/ip/router/vrrp[ ]/interfaces

This attribute displays the status of the virtual router its interfaces.

The interfaces table contains the following elements:

telindus1423Router/ip/router/vrrp[ ]/criticals

This attribute displays the status of the virtual router interfaces that you defined as critical (refer to telindus1423Router/ip/router/vrrp[ ]/criticals on page 196).

The criticals table contains the following elements:

Element Description

name This element displays the interface name.

priority This element displays the interface priority.

status This element displays the interface status. Possible values are:

• initial: The virtual router interface is in an initial state (e.g. during the master/backup election process).

• master: The virtual router interface is elected master after the master/backup election process.

• backup: The virtual router interface is elected backup after the master/backup election process.

• inactive: The virtual router interface is inactive (e.g. because VRRP is not active).

Element Description

interface This element displays the name of the critical interface.

status This element displays the operational status (e.g. up, down, etc.) of the critical interface.



374

MR-2.13.7 Firewall status attributes


• telindus1423Router/ip/router/firewall/sessions on page 375• telindus1423Router/ip/router/firewall/reverseSessions on page 375• telindus1423Router/ip/router/firewall/log on page 376• telindus1423Router/ip/router/firewall/sNet on page 376


• telindus1423Router/ip/router/firewall/clearLog on page 376



375

telindus1423Router/ip/router/firewall/sessions

This attribute displays the status of the sessions that are currently going through the firewall.

The sessions table contains the following elements:

telindus1423Router/ip/router/firewall/reverseSessions

This attribute displays the status of the reverse sessions that are currently going through the firewall.

You do not have to set up policies to allow the reverse session (i.e. the return path) of a session that was initiated. These reverse sessions are set up and allowed automatically.

For example, if you define an outbound policy from the corporate network to the Internet to allow web browsing (HTTP) and if a HTTP session from the corporate network to the Internet is set up, then a reverse session from the Internet to the corporate network is set up and allowed automatically.

The reverseSessions table contains the same elements as the sessions table. Refer to telindus1423Router/ip/router/firewall/sessions on page 375.

Element Description

sNet This element displays the name of the source SNet. I.e. the SNet in which the orig-inator of the session is located.

policyDirection This element displays the direction of the policy that applies on the session. Pos-sible values are: inbound or outbound.

sourceIp This element displays the source IP address.

destIp This element displays the destination IP address.

protocol This element displays the protocol that is used. Possible values are: icmp, tcp, udp, esp, ah, other.

destPort This element displays the destination port number.

bytesTransferred This element displays the number of bytes transferred in this session.

natIp This element displays the IP address of the NAT gateway (if NAT is enabled for this session).

name This element displays the name of the policy that applies on the session.



376

telindus1423Router/ip/router/firewall/log

This attribute displays the firewall log.

The sessions table contains the following elements:

telindus1423Router/ip/router/firewall/sNet

This attribute displays the SNets that are available (standard and custom). However, it says nothing about which SNets are actually in use (i.e. assigned to an interface).

telindus1423Router/ip/router/firewall/clearLog

Use this action to clear the log.

Element Description

date This element displays the date and time the event was logged.

sysUpTime This element displays the system-up time at the moment the event was logged.

priority This element displays the priority of the event. Possible values are: debug, info, notice, warning, error, critical, alert, emergency.

event This element displays a description of the event.

E.g. “access policy not found, dropping packet from corp n/w”.

sourceIp This element displays the source IP address.

destIp This element displays the destination IP address.

sourcePort This element displays the source port number.

destPort This element displays the destination port number.

protocol This element displays the protocol that is used. Possible values are: icmp, tcp, udp, esp, ah, other.



377

MR-2.14 Bridge status attributes


• telindus1423Router/bridge/bridgeGroup/ifDescr on page 378• telindus1423Router/bridge/bridgeGroup/ifType on page 378• telindus1423Router/bridge/bridgeGroup/ifOperStatus on page 378• telindus1423Router/bridge/bridgeGroup/ifMtu on page 378• telindus1423Router/bridge/bridgeGroup/ip on page 378• telindus1423Router/bridge/bridgeGroup/macAddress on page 378• telindus1423Router/bridge/bridgeGroup/arpCache on page 379• telindus1423Router/bridge/bridgeGroup/bridgeCache on page 380• telindus1423Router/bridge/bridgeGroup/bridging on page 381• telindus1423Router/bridge/bridgeGroup/spanningTree on page 381


• telindus1423Router/bridge/bridgeGroup/clearArpCache on page 383• telindus1423Router/bridge/bridgeGroup/clearBridgeCache on page 383



378

telindus1423Router/bridge/bridgeGroup/ifDescr


telindus1423Router/bridge/bridgeGroup/ifType


telindus1423Router/bridge/bridgeGroup/ifOperStatus

This attribute displays the current operational status of the bridge group.

telindus1423Router/bridge/bridgeGroup/ifMtu


telindus1423Router/bridge/bridgeGroup/ip

This attribute displays the IP information of the bridge.


telindus1423Router/bridge/bridgeGroup/macAddress

This attribute displays the MAC address of the bridge group.

Element Description

address This is the IP address of the bridge. It is either configured or retrieved automati-cally.

netMask This is the IP subnet mask of the interface. It is either configured or retrieved auto-matically.



379

telindus1423Router/bridge/bridgeGroup/arpCache

This attribute displays all the MAC address - IP address pairs from ARP requests and replies received on the LAN interface. Refer to What is the ARP cache? on page 22 for more information.

The arpCache table contains the following elements:

Element Description

macAddress This is the MAC address.

ipAddress This is the associated IP address.

type This is the ARP cache entry type. Possible values are:

• dynamic. The MAC - IP address pair is retrieved from an ARP request or reply message.

• static. The MAC - IP address pair is configured.There is only one static entry, i.e. the Telindus 1423 SHDSL Router its own IP and MAC address.

timeOut This is the time the entry will remain in the ARP cache. For the static entry, this value is 0.



380


When a port of the bridge enters the learning state, it stores the MAC addresses of the stations situated on the network that is connected to this port. The MAC addresses are stored in a MAC address database or bridge cache. The bridgeCache attribute visualises this address database. Refer to What is the bridge cache? on page 225 for more information.

The bridgeCache table contains the following elements:

Example

The following figure shows part of a bridge cache table as an example:

Element Description

interface This is the interface through which the station can be reached.

macAddress This is the MAC address of the station situated on the network connected to the interface.

type This displays whether the MAC address entry is static or dynamic:

• dynamic. The corresponding MAC address is learned on one of the interfaces.• static. There are only two static entries:

- the Telindus 1423 SHDSL Router its own MAC address.- a MAC address used for Spanning Tree.

age This is the elapsed time since a frame was received from the station.



381

telindus1423Router/bridge/bridgeGroup/bridging

The bridging attributes or elements in the individual interface objects display the bridging information for that particular interface. This bridging attribute, however, displays the bridging information of all the (bridged) interfaces of the Telindus 1423 SHDSL Router.

Refer to telindus1423Router/lanInterface/bridging on page 266 for a detailed description of the bridging structure. Note however that the bridge group bridging structure contains one extra element: name. This is the name of the interface as you configured it. Note that the interface can also be a DLCI, an ATM PVC, a tunnel, etc.

telindus1423Router/bridge/bridgeGroup/spanningTree

This attribute gives you the Spanning Tree status information of the bridge.

The spanningTree structure contains the following elements:

Element Description

designatedPriority Together, these two elements form the unique bridge identifier.

They display the unique bridge identifier of the root bridge as it is indicated in the root identifier parameter of the Configuration BPDUs. These BPDUs are transmit-ted by the designated bridge for the LAN that is currently connected to this port.

This bridge identifier is used to test the value of the root identifier parameter con-veyed in received Configuration BPDUs.

designatedMAC

rootPathCost This is the cost of the path from this bridge to the root bridge.

If this bridge is the root bridge, the rootPathCost value equals 0. Else, the rootPathCost value equals the sum of …

• the path cost as it is up to the designated bridge for the LAN that is currently connected to this port (this cost is transmitted in Configuration BPDUs by the designated bridge)

and• the path cost as it is configured for the root port.

The rootPathCost element is used …

• to test the value of the root path cost parameter conveyed in received Config-uration BPDUs.

• as the value of the root path cost parameter in transmitted Configuration BPDUs.

The total cost of the path to the root bridge should not exceed 65500.

rootPort This is the port identifier of the port that offers the lowest cost path to the root.

If two or more ports offer equal least cost paths to the root bridge, then the root port is selected to be that with the highest designatedPriority (i.e. the lowest numerical value).

If two or more ports offer equal least cost paths to the root bridge and the same designatedPriority, then the root port is selected to be that with the highest designatedPortPriority (i.e. the lowest numerical value).



382

bridgePriority Together, these two attributes form the unique bridge identifier of this bridge.

bridgeMAC

maxAge This is the time-out value to be used by all bridges in the bridged LAN for discard-ing bridging information.

The maxAge element displays the value as it is set by the root bridge. This informa-tion is conveyed by the root bridge to ensure that each bridge in the bridged LAN has a consistent value against which to test the age of stored configuration infor-mation.

helloTime This is the interval between the generation of Configuration BPDUs by the root bridge.

The helloTime element displays the value as it is set by the root bridge. This attribute is not directly used by the Spanning Tree algorithm, but it is conveyed by the root bridge to facilitate the monitoring of protocol performance by the management sys-tem.

forwardDelay This is the time-out value to be used by all bridges in the bridged LAN for …

• a bridge port applies to move from listening state to learning state or from learn-ing state to forwarding state.

• time-out (or ageing) for purging MAC addresses from the bridge cache in case a topology change is detected.

The forwardDelay element displays the value as it is set by the root bridge. This infor-mation is conveyed by the root bridge to ensure that each bridge in the bridged LAN has a consistent value for the forward delay timer.

topologyChange This is a Boolean value (0 or 1) to report …

• for a bridge that is not a root bridge, whether or not the most recently accepted Configuration BPDU indicates a change in the active topology.

• for the root bridge, whether or not a change in topology has been detected within the preceding topologyChangeTime period.

The topologyChange element is used to …

• propagate the topology change indication in transmitted Configuration BPDUs.• determine whether the short (bridgeForwardDelay) or long (bridgeTimeOut) time-out

(or ageing) value is used to purge dynamic MAC addresses from the bridge cache.

topologyChange-Detection

This is a Boolean value (0 or 1) to report that a topology change has been detected by or notified to the bridge.

topologyChange-Time

This displays the time during which the root bridge transmits Configuration BPDUs indicating a topology change, after it detected this topology change.

The topologyChangeTime element value is equal to the sum of the root bridge its bridgeMaxAge element value and bridgeForwardDelay element value.

Refer to telindus1423Router/bridge/bridgeGroup/spanningTree on page 226 for more informa-tion on the latter two elements.

Element Description



383

telindus1423Router/bridge/bridgeGroup/clearArpCache

Use this action to clear the ARP cache table.

telindus1423Router/bridge/bridgeGroup/clearBridgeCache

Use this action to clear the bridge cache table.



384

MR-2.15 Management status attributes


• telindus1423Router/management/cms2Address on page 385• telindus1423Router/management/timeServer on page 385• telindus1423Router/management/alarmLog on page 385• telindus1423Router/management/accessLog on page 386• telindus1423Router/management/loopback/ifDescr on page 388• telindus1423Router/management/loopback/ifType on page 388• telindus1423Router/management/loopback/ifOperStatus on page 388• telindus1423Router/management/loopback/ifMtu on page 388• telindus1423Router/management/loopback/ipAddress on page 388• telindus1423Router/management/loopback/mask on page 388



385

telindus1423Router/management/cms2Address

This attribute displays the absolute device address as you configured it.

telindus1423Router/management/timeServer

This attribute displays the status of the SNTP function.

The timeServer structure contains the following elements:

telindus1423Router/management/alarmLog

This attribute displays the alarm log. It displays the 32 most recent alarms that occurred on the Telindus 1423 SHDSL Router.

The alarmLog table contains the following elements:

Element Description

state This is the state of the Telindus 1423 SHDSL Router its clock. Possible values are:

• notConfigured. The Telindus 1423 SHDSL Router is not configured for SNTP.• notSynchronised. The Telindus 1423 SHDSL Router its clock is not synchronised

with the time server.• synchronised. The Telindus 1423 SHDSL Router its clock is synchronised with

the time server.

connection This is the state of the connection with the time server. Possible values are:

• notConfigured. The Telindus 1423 SHDSL Router is not configured for SNTP.• notSynchronised. The connection with the time server is not synchronised.• synchronised. The connection with the time server is synchronised.• noContact. The connection with the time server is lost.

stratum This is the stratum level of the time server its reference clock. Possible values are:

• 0: unspecified or unavailable• 1: primary reference (e.g. radio clock)• 2 - 15: secondary reference (via SNTP)

delay This is the total roundtrip delay of the time server with its reference clock.

Element Description

timeStamp This is the value of the real time clock at the moment the alarm was generated.

sysUpTime This is the system up-time of the Telindus 1423 SHDSL Router at the moment the alarm was generated.

totalAlarmLevel This is the total alarm level of the Telindus 1423 SHDSL Router.

alarmLevel This is the alarm level of the alarm.

alarm This is the alarm itself in the format path.alarmName on|off (e.g. telindus1423Router/lanIn-terface.linkDown on).



386

telindus1423Router/management/accessLog

This attribute displays the access log. It displays the 32 most recent login events that occurred on the Telindus 1423 SHDSL Router.

The accessLog table contains the following elements:

Element Description

timeStamp This element displays the value of the real time clock at the moment the access event occurred.

sysUpTime This element displays the system up-time of the Telindus 1423 SHDSL Router at the moment the access event occurred.

type This element displays the type of access event. Possible values are:

• login. A successful login was detected.• loginFailure. A failed login was detected.• accessFailureOn. The number of failed logins exceeded the access failure thresh-

old within the access failure period. Refer to telindus1423Router/management/login-Control on page 246.

• accessFailureOff. After an accessFailureOn event was logged, the number of failed logins dropped below the access failure threshold within the access failure period. Refer to telindus1423Router/management/loginControl on page 246.

user This element displays the name of the user who caused the access event. If you entered a …

• password string only in the password element of the security table, then the user element displays nothing.

• user/password string in the password element of the security table (of the type "username:password"), then the user element displays the username part of the user/password string. Also see telindus1423Router/security on page 16.

application This element displays the type of application that caused the access event. Possi-ble values are:

• cms2. The access event is caused by any maintenance application. For exam-ple, TMA, TMA CLI, CLI or ATWIN (via a Telnet or terminal session), WebInter-face, etc.

• ftp. The access event is caused by FTP.• fileSystem. The access event is caused by any maintenance application access-

ing the file system. For example, FTP, TFTP, TML, etc. when downloading firmware.

• snmp. The access event is caused by SNMP. Note that since SNMP is not ses-sion oriented, each successful SNMP request would result in an access event. So an SNMP walk would result in thousands of access events being logged. Therefore, in case of SNMP, only the failed requests are logged.

• proxy. The access event is caused by any maintenance application accessing a CMS device through the Telindus 1423 SHDSL Router (i.e. the Telindus 1423 SHDSL Router acts as proxy). This since the password of the Telindus 1423 SHDSL Router is used to control the access to the CMS devices.



387

Note that some applications may cause more than one access event. For example, suppose you access the Telindus 1423 SHDSL Router with FTP and download a file to the file system. In that case two events are logged in the accessLog table:1. One event logging the access of the FTP application to the Telindus 1423 SHDSL Router.2. One event logging the access of the FTP application to the file system when downloading the file.

accessRights This element displays the access rights that are associated with the access event.

Element Description



388

telindus1423Router/management/loopback/ifDescr


telindus1423Router/management/loopback/ifType


telindus1423Router/management/loopback/ifOperStatus

This attribute displays the current operational status of the loopback interface.

The loopback interface is always up.

telindus1423Router/management/loopback/ifMtu


telindus1423Router/management/loopback/ipAddress

This attribute displays the IP address of the loopback interface as you configured it.

telindus1423Router/management/loopback/mask

This attribute displays the subnet mask of the loopback interface as you configured it.



389

MR-2.16 File system status attributes


• telindus1423Router/fileSystem/fileList on page 390• telindus1423Router/fileSystem/freeSpace on page 390• telindus1423Router/fileSystem/status on page 390• telindus1423Router/fileSystem/corruptBlocks on page 390• telindus1423Router/fileSystem/trustedCertificates on page 391• telindus1423Router/fileSystem/selfCertificates on page 391


• telindus1423Router/fileSystem/Delete File on page 392• telindus1423Router/fileSystem/Rename File on page 392• telindus1423Router/fileSystem/loadTrustedCertificate on page 392• telindus1423Router/fileSystem/generateSelfCertificateRequest on page 393• telindus1423Router/fileSystem/loadSelfCertificate on page 394• telindus1423Router/fileSystem/getTrustedCertificateScep on page 395• telindus1423Router/fileSystem/getSelfCertificateScep on page 396• telindus1423Router/fileSystem/getCrlScep on page 398• telindus1423Router/fileSystem/saveCertificates on page 398



390

telindus1423Router/fileSystem/fileList

Part of the flash memory of the Telindus 1423 SHDSL Router is organised as a file system and a number of files are stored in it. The fileList attribute shows all the files that are present on the file system. Usually, the following files are present:

• The configuration file of the Telindus 1423 SHDSL Router (file config1.db).• Up to two application software files of the Telindus 1423 SHDSL Router (files CONTROL1 and CON-

TROL 2).

The fileList table contains the following elements:

telindus1423Router/fileSystem/freeSpace

This attribute displays the number of free bytes on the file system.

telindus1423Router/fileSystem/status

This attribute displays the status of the file system. Possible values are:

telindus1423Router/fileSystem/corruptBlocks

The file system of the Telindus 1423 SHDSL Router consists of several blocks. When a block can not be erased, the corruptBlocks count is incremented. This block can no longer be used to store data.

Element Description

name This is the filename. Maximum length of the filename is 24 characters. All charac-ters are allowed (including spaces). The filename is case sensitive.

length This is the length of the file in bytes.

Value Description

ready Normal situation.

formatting The file system is being formatted. This can be triggered when the file system is found to be corrupt at boot.

corrupt The file system is in a state were no guarantee can be given about the correct operation of the file system. The file system will be formatted at the following boot.

corruptBlocks A certain block can not be erased.



391

telindus1423Router/fileSystem/trustedCertificates

This attribute displays the trusted certificates that are currently loaded.

The trustedCertificates table contains the following elements:

telindus1423Router/fileSystem/selfCertificates

This attribute displays the signed self-certificates that are currently loaded.

The selfCertificates table contains the following elements:

Element Description

name This element displays the certificate name. Possible values are: ca-0, ca-1, ca-2.

expiry This element displays when the certificate expires.

issuer This element displays who issued the certificate.

subject This element displays the subject information of the certificate. In case of a trusted certificate this is information of the CA.

Element Description

name This element displays the certificate name. In this case, this is the same string as entered in the privateKeyName element of the loadSelfCert action.

expiry This element displays when the certificate expires.

issuer This element displays who issued the certificate.

subject This element displays subject information of the certificate. In case of a self-certif-icate this is information of the device (e.g. the IP address).



392

telindus1423Router/fileSystem/Delete File

Use this action to remove obsolete files from the file system. You have to enter the filename you want to delete as argument value.

Filenames are case sensitive!

telindus1423Router/fileSystem/Rename File

Use this action to rename a file on the file system. You have to enter the old and new filename in a struc-ture.

Filenames are case sensitive!

telindus1423Router/fileSystem/loadTrustedCertificate

This action is used in the procedure where security certificates are obtained and loaded manually in order to set up an L2TP tunnel secured with IPSEC using an IKE certificate SA. Refer to MU-10.6.3 - Configuration d’un tunnel L2TP sécurisé IPSEC en utilisant une SA manuelle on page 362.

Use this action to load the trusted certificate you obtained from your Certificate Authority (CA) into the memory of the Telindus 1423 SHDSL Router. Enter the filename of the trusted certificate as argument value and execute the action.

• The trusted certificate file has to be present on the file system of the Telindus 1423 SHDSL Router.• The filename is case sensitive.• The saveCerts action has to be executed after the loadTrustedCert action so that the trusted certificate is

also loaded every time the Telindus 1423 SHDSL Router reboots.



393

telindus1423Router/fileSystem/generateSelfCertificateRequest


Use this action to create a request for a signed self-certificate. Then this request has to be submitted to your Certificate Authority (CA) which signs it and returns a signed self-certificate. Fill in the elements in the argument value structure and execute the action.

The argument value structure of the generateCertReq action contains the following elements:

Element Description

fileName Use this element to specify the name of the self-certif-icate request file.

After you filled in all the elements and executed the generateCertReq action, a file is written to the file system of the Telindus 1423 SHDSL Router. The name of this file is the name you specified using the fileName element.

type Use this element to set the authentication algorithm.

The type element has the following values: rsa-md5, rsa-sha1, dss-sha1.

subjectName Use this element to specify the subject name.

privateKeyName Use this element to specify the name of the private key.

Remember the private key name. You need it to load the associated signed self-certificate into the memory of the Telindus 1423 SHDSL Router. Refer to telindus1423Router/fileSystem/loadSelfCertificate on page 394.

ipAddress Use this element to specify the IP address that will be used in the self-certificate. This is then used for authentication purposes.

hostname Use this element to specify the hostname that will be used in the self-certificate. This is then used for authentication purposes.

The hostname has to be of the form “host.domain.com”.

user Use this element to specify the username that will be used in the self-certificate. This is then used for authentication purposes.

The username has to be of the form “[email protected]”.

keyLength Use this element to specify the length of the public/pri-vate keys. Note that the longer the key length, the longer it takes to generate the keys.


Default:rsa-md5Range: enumerated, see below






Default:512Range: 512 / 1024 / 2048



394

telindus1423Router/fileSystem/loadSelfCertificate


Use this action to load the signed self-certificate you first submitted and then retrieved from your Certif-icate Authority (CA) into the memory of the Telindus 1423 SHDSL Router. Fill in the elements in the argu-ment value structure and execute the action.

The argument value structure of the loadSelfCert action contains the following elements:

• The signed self-certificate file has to be present on the file system of the Telindus 1423 SHDSL Router.

• The filename is case sensitive.• The saveCerts action has to be executed after the loadSelfCert action so that the signed self-certificate

is also loaded every time the Telindus 1423 SHDSL Router reboots.

Element Description

fileName Use this element to specify the name of the signed self-certificate file.


This has to be exact the same name as you specified in the privateKeyName element of the generateCertReq action. Refer to telindus1423Router/fileSystem/generateSelfCertifica-teRequest on page 393.





395

telindus1423Router/fileSystem/getTrustedCertificateScep

This action is used in the procedure where security certificates are obtained and loaded through SCEP in order to set up an L2TP tunnel secured with IPSEC using an IKE certificate SA. Refer to MU-10.6.3 - Configuration d’un tunnel L2TP sécurisé IPSEC en utilisant une SA manuelle on page 362.

Use this action to obtain and load the trusted certificate from a SCEP server. Fill in the elements in the argument value structure and execute the action.

The argument value structure of the getTrustedCertScep action contains the following elements:

The saveCerts action has to be executed after the getTrustedCertScep action so that the trusted certificate is also loaded every time the Telindus 1423 SHDSL Router reboots.

Element Description

server Use this element to specify the IP address of the SCEP server.

Together with the url element this makes up the complete path to which the SCEP requests are submitted.

url Use this element to specify the URL to which the SCEP requests have to be submitted.

Together with the server element this makes up the complete path to which the SCEP requests are submitted. Consult the manual of your SCEP server to find out which URL you have to specify.

Example

Suppose you set the server element to 172.31.127.6 and the url element to certsrv/mscep/mscep.dll, then the SCEP requests are submitted to http://172.31.127.6/certsrv/mscep/mscep.dll.

caName Use this element to set the name of the CA.

This element is more for information purposes. It may be omitted.

port Use this element to set the port on which the SCEP requests are sent. By default, this is port 80.







396

telindus1423Router/fileSystem/getSelfCertificateScep

This action is used in the procedure where security certificates are obtained and loaded through SCEP in order to set up an L2TP tunnel secured with IPSEC using an IKE certificate SA. Refer to MU-10.6.3 - Configuration d’un tunnel L2TP sécurisé IPSEC en utilisant une SA manuelle on page 362.

Use this action to obtain and load the self-certificate from a SCEP server. Fill in the elements in the argu-ment value structure and execute the action.

The argument value structure of the getSelfCertScep action contains the following elements:

Element Description




Together with the server element this makes up the complete path to which the SCEP requests are submitted.

Example


type Use this element to set the authentication algorithm.

subjectName Use this element to specify the subject name.

challenge Use this element to specify the challenge phrase.

When installing a SCEP server, you usually have the possibility to specify a challenge phrase. If you specify a challenge phrase on the SCEP server, then also enter this phrase in the challenge element. If you do not specify a challenge phrase, then any user can enrol for a certificate.

caName Use this element to select a certificate.


ipAddress Use this element to specify the IP address that will be used in the self-certificate. This is then used for authentication purposes.



Default:rsa-md5Range: rsa-md5 / rsa-sha1



Default:ca-0Range: ca-0 / ca-1 / ca-2





397

The saveCerts action has to be executed after the getSelfCertScep action so that the signed self-certificate is also loaded every time the Telindus 1423 SHDSL Router reboots.

hostname Use this element to specify the hostname that will be used in the self-certificate. This is then used for authentication purposes.

The hostname has to be of the form “host.domain.com”.

user Use this element to specify the username that will be used in the self-certificate. This is then used for authentication purposes.

The username has to be of the form “[email protected]”.


keyLength Use this element to specify the length of the public/pri-vate keys. Note that the longer the key length, the longer it takes to generate the keys.

Element Description




Default:512Range: 512 / 1024 / 2048



398

telindus1423Router/fileSystem/getCrlScep

Use this action to get the Certificate Revocation List (CRL). A CRL is a list of certificates that have been revoked before their scheduled expiration date. Fill in the elements in the argument value structure and execute the action.

The argument value structure of the getCertRevListScep action contains the following elements:

telindus1423Router/fileSystem/saveCertificates

This action is used in the procedure where security certificates are obtained and loaded in order to set up an L2TP tunnel secured with IPSEC using an IKE certificate SA. Refer to MU-10.6.3 - Configuration d’un tunnel L2TP sécurisé IPSEC en utilisant une SA manuelle on page 362.

Use this action to save the trusted certificate and the signed self-certificate that were either obtained and loaded manually or by using SCEP. Saving the certificates ensures that they are loaded every time the Telindus 1423 SHDSL Router reboots.

Element Description




Together with the server element this makes up the complete path to which the SCEP requests are submitted.

Example


caName Use this element to select a certificate.




Default:ca-0Range: ca-0 / ca-1 / ca-2




399

MR-2.17 Operating system status attributes


• telindus1423Router/operatingSystem/taskInfo on page 400



400

telindus1423Router/operatingSystem/taskInfo

This attribute displays status information about the operating system.

The taskInfo table contains the following elements:

Element Description

taskName This is the name of the task.

taskStatus This is the current status of the task. Possible values are:

• awake. This task is actually running.• asleep. This task is waiting on an event.• inactive. This task slot is not active, i.e. no task has been assigned to this slot.

load30s This is the load on the processor, in percent, during the last 30 seconds.

load5m This is the load on the processor, in percent, during the last 5 minutes.

runningInMedium Each task can be running with a low, medium or high priority. This element gives the percentage of time this task has been running with medium priority during the last 30 seconds.

runningInHigh Each task can be running with a low, medium or high priority. This element gives the percentage of time this task has been running with high priority during the last 30 seconds.

The percentage of time this task has been running with low priority can be calcu-lated using the following formula:

running in low priority = 100% - runningInMedium - runningInHigh

programCounter This is the current value of the program counter. The program counter is the mem-ory address for the current instruction of this task.



401


User manual Performance attributes

402

MR-3 Performance attributes

This chapter discusses the performance attributes of the Telindus 1423 SHDSL Router. The following gives an overview of this chapter:

• MR-3.1 - Performance attributes overview on page 403• MR-3.2 - General performance attributes on page 410• MR-3.3 - LAN interface performance attributes on page 412• MR-3.4 - WAN interface performance attributes on page 417• MR-3.5 - Encapsulation performance attributes on page 418• MR-3.6 - SHDSL line performance attributes on page 431• MR-3.7 - End and repeater performance attributes on page 435• MR-3.8 - BRI performance attributes on page 436• MR-3.9 - AUX performance attributes on page 441• MR-3.10 - Dial maps performance attributes on page 442• MR-3.11 - Bundle performance attributes on page 444• MR-3.12 - Router performance attributes on page 447• MR-3.13 - IP traffic policy performance attributes on page 469• MR-3.14 - Bridge performance attributes on page 471• MR-3.15 - Management performance attributes on page 477• MR-3.16 - Operating system performance attributes on page 480



403

MR-3.1 Performance attributes overview

> telindus1423RouterAction: resetAllCounters

>> lanInterfaceifInOctetsifInUcastPktsifInNUcastPktsifInDiscardsifInErrorsifInUnknownProtosifOutOctetsifOutUcastPktsifOutNUcastPktsifOutDiscardsifOutErrorsifOutQLenh2Performanceh24PerformanceifOutPQLenifDropLevelExceededvlanmibCounters1

Action: resetCounters

>> wanInterfaceifInOctetsifInUcastPktsifInNUcastPktsifInDiscardsifInErrorsifInUnknownProtosifOutOctetsifOutUcastPktsifOutNUcastPktsifOutDiscardsifOutErrorsifOutQLenifOutPQLenifDropLevelExceededh2Performanceh24PerformanceAction: resetCounters

1. Only present on the 4 port LAN interface.



404

>>> atmpvcTableunknownCellsvpAction: resetCounters

>>> frameRelaydlciTablelmicllmInFramesAction: resetCounters

>>> errorTeststatusdurationifUpTimeifDownCountrxBitErrorsrxBlockErrorsrxBlocksrxAllOneBlocksrxAllZeroBlocksrxPatternSliprxShiftCountrxSyncLosstxBlockstxInjectErrorsAction: startTestAction: stopTestAction: injectErrorAction: clearCounters

>>> lineh2Lineh24Lined7LinelineAction: retrainAction: resetCounters

>>>> linePair[ ]h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformanceAction: resetCounters



405

>>> repeater[ ]

>>>> networkLinePair[ ]h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformanceAction: resetCounters

>>>> customerLinePair[ ]h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformanceAction: resetCounters

>>> end

>>>> linePair[ ]h2LineParametersh2Performanceh24LineParametersh24Performanced7LineParametersd7PerformancelineParametersperformanceAction: resetCounters

>> bri[1]2

h2DialupStatsh24DialupStatsd7DialupStatsAction: resetCounters




406

>>> bChannel[1]ifInOctetsifInUcastPktsifInNUcastPktsifInDiscardsifInErrorsifInUnknownProtosifOutOctetsifOutUcastPktsifOutNUcastPktsifOutDiscardsifOutErrorsifOutQLenifOutPQLenifDropLevelExceededh2Performanceh24PerformanceAction: resetCounters


>> bri[2]2


>> dialMaps2

mappingAction: resetCounters

>> profiles

>>> policy

>>>> traffic

>>>>> ipTrafficPolicy[ ]discardstrafficShapingAction: resetCounters



407

>> bundle

>>> pppBundle[ ]3

ifInOctetsifInUcastPktsifInNUcastPktsifInDiscardsifInErrorsifInUnknownProtosifOutOctetsifOutUcastPktsifOutNUcastPktsifOutDiscardsifOutErrorsifOutQLenh2Performanceh24PerformancemulticlassinterfacesAction: resetCounters

>>> isdnBundle[ ]4

ifInOctetsifInUcastPktsifInNUcastPktsifInDiscardsifInErrorsifInUnknownProtosifOutOctetsifOutUcastPktsifOutNUcastPktsifOutDiscardsifOutErrorsifOutQLenh2Performanceh24PerformanceAction: resetCounters

3. This is the PPP bundle in case of MLPPP on the WAN interface.4. This is the PPP bundle in case of MLPPP on the ISDN interfaces.



408

>> routerroutingTableradiusAuthradiusAcctpingResultstracertResultsAction: startPingAction: stopPingAction: startTracertAction: stopTracertAction: clearTracertAction: resetCounters

>>> defaultNatsocketsFreeallocFailsdiscardsaddressesAvailabletcpSocketsUsedudpSocketsUsedicmpSocketsUsedtcpAllocsudpAllocsicmpAllocsAction: resetAction: resetCounters

>>> tunnelsl2tpTunnelsipsecL2tpTunnelsAction: resetCounters

>>> manualSA[ ]inPacketsoutPacketsespAuthenticationFailureespDecryptionFailureespSequenceNrReplayespDroppedFramesAction: resetCounters

>>> ikeSA[ ]phase2Negotiationsphase2SessionsAction: resetCounters



409

>>> firewallh24Generald7Generalh24Attackd7AttackAction: resetCounters

>> bridge

>>> bridgeGroupbridgeCachebridgeDiscardsbridgeFloodsmultiVlansAction: resetCounters

>>> accessList[ ]bridgeAccessListAction: resetCounters

>> managementcms2SessionCounttftpSessionCountcliSessionCounttcpSessionCountipStackEventsAction: resetCounters

>> operatingSystemcurrUsedProcPowerusedProcPowerfreeDataBufferstotalDataBufferslargestFreeBlockSizefreeBlockCountfreeMemorytotalMemorytaskInfoAction: resetCounters



410

MR-3.2 General performance attributes

There are no general performance attributes. However, there is one general performance action:

• telindus1423Router/resetAllCounters on page 411



411

telindus1423Router/resetAllCounters

Use this action to reset all counters in all objects in the containment tree of the Telindus 1423 SHDSL Router.

You can also reset the counters per object. To do so, use the resetCounters action located in the corre-sponding object.



412

MR-3.3 LAN interface performance attributes

This section describes the following performance attributes:

• telindus1423Router/lanInterface/ifInOctets on page 413• telindus1423Router/lanInterface/ifInUcastPkts on page 413• telindus1423Router/lanInterface/ifInNUcastPkts on page 413• telindus1423Router/lanInterface/ifInDiscards on page 413• telindus1423Router/lanInterface/ifInErrors on page 413• telindus1423Router/lanInterface/ifInUnknownProtos on page 413• telindus1423Router/lanInterface/ifOutOctets on page 414• telindus1423Router/lanInterface/ifOutUcastPkts on page 414• telindus1423Router/lanInterface/ifOutNUcastPkts on page 414• telindus1423Router/lanInterface/ifOutDiscards on page 414• telindus1423Router/lanInterface/ifOutErrors on page 414• telindus1423Router/lanInterface/ifOutQLen on page 414• telindus1423Router/lanInterface/h2Performance on page 415• telindus1423Router/lanInterface/h24Performance on page 415• telindus1423Router/lanInterface/ifOutPQLen on page 415• telindus1423Router/lanInterface/ifDropLevelExceeded on page 415• telindus1423Router/lanInterface/vlan on page 416• telindus1423Router/lanInterface/mibCounters on page 416



413

telindus1423Router/lanInterface/ifInOctets

This attribute displays the number of octets (bytes) received on this interface.

telindus1423Router/lanInterface/ifInUcastPkts

This attribute displays the number of unicast packets received on this interface and delivered to a higher-layer protocol. Unicast packets are all non-multicast and non-broadcast packets.

telindus1423Router/lanInterface/ifInNUcastPkts

This attribute displays the number of non-unicast packets received on this interface and delivered to a higher-layer protocol. Non-unicast packets are all the multicast and broadcast packets.

telindus1423Router/lanInterface/ifInDiscards

This attribute displays the number of incoming packets that were discarded, to prevent their deliverance to a higher-layer protocol. This even though no errors were detected in these packets.

telindus1423Router/lanInterface/ifInErrors

This attribute displays the number of incoming packets that could not be delivered to a higher-layer pro-tocol because they contained errors.

telindus1423Router/lanInterface/ifInUnknownProtos

This attribute displays the number of incoming packets that were discarded because they contained an unknown or unsupported protocol.



414

telindus1423Router/lanInterface/ifOutOctets

This attribute displays the total number of octets (bytes) transmitted by the interface, including framing characters.

telindus1423Router/lanInterface/ifOutUcastPkts

This attribute displays the total number of packets that higher-level protocols requested to be transmitted to a unicast address, including those that were discarded or not sent.

telindus1423Router/lanInterface/ifOutNUcastPkts

This attribute displays the number of non-unicast packets that higher-level protocols requested to be transmitted to a non-unicast (i.e. a broadcast or multicast) address, including those that were discarded or not sent.

telindus1423Router/lanInterface/ifOutDiscards

This attribute displays the number of outgoing packets that were discarded, to prevent they are transmit-ted by the interface. This could be due to, for instance, the presence of an access list.

telindus1423Router/lanInterface/ifOutErrors

This attribute displays the number of outgoing packets that could not be transmitted by the interface because they contained errors. On the LAN interface ifOutErrors are also generated in case of extensive collisions.

telindus1423Router/lanInterface/ifOutQLen

This attribute displays the length, expressed in packets, of the output packet queue on the interface.



415

telindus1423Router/lanInterface/h2Performance

This attribute displays the 2 hours performance summary of the LAN interface.

The h2Performance table contains the following elements:

telindus1423Router/lanInterface/h24Performance

This attribute displays the 24 hours performance summary of the LAN interface. The h24Performance table contains the same elements as the telindus1423Router/lanInterface/h2Performance table.

telindus1423Router/lanInterface/ifOutPQLen

In case an overload condition occurs and priority queuing is activated, then this attribute displays how many packets the different queues contain.

Refer to MU-8.8.1 - Présentation de la politique de trafic et de priorité on page 250 for more information on the priority queues.

telindus1423Router/lanInterface/ifDropLevelExceeded

This attribute displays how many times the drop levels of the user configurable queues have been exceeded (and hence packets have been dropped).

Refer to telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/dropLevels on page 106 for more information on the drop levels.

Element For the corresponding period, this element displays …

sysUpTime the elapsed time since the last cold boot.

ifUpTime the time during which the interface was up.

ifStatusChanges the number of times the ifOperStatus value of the interface changed (from up to down or vice versa).

ifInOctets the number of octets (bytes) received on this interface.

ifInPackets the number of packets received on this interface.

ifInErrors the number of packets received on this interface that could not be delivered to a higher-layer protocol because they contained errors.

ifOutOctets the number of octets (bytes) transmitted by the interface, including framing char-acters.

ifOutPackets the number of packets transmitted by the interface.

ifOutDiscards the number of outgoing packets that were discarded, to prevent they were trans-mitted by the interface. This could be due to, for instance, the presence of an access list.

ifOutErrors the number of packets that could not be transmitted by the interface because they contained errors.



416


This attribute displays the SNMP MIB2 performance parameters of the VLANs that are present on the LAN interface.


telindus1423Router/lanInterface/mibCounters


Whereas the previous performance attributes show the SNMP MIB2 performance parameters of the complete 4 port Ethernet interface, this attribute displays the SNMP MIB2 performance parameters for each port (including the local port, refer to Qu’est-ce que le commutateur Ethernet à 4 ports ? on page 335).

Element Description

name This element displays the name of the VLAN as you configured it.

vlan This element displays the VLAN ID.

mibCounters This element displays the SNMP MIB2 performance parameters of the VLAN.

Refer to MR-3.3 - LAN interface performance attributes on page 412 for an expla-nation of the individual SNMP MIB2 performance parameters.



417

MR-3.4 WAN interface performance attributes

All performance attributes of the WAN interface are the same as on the LAN interface. Therefore, they are not explained here again. Refer to MR-3.3 - LAN interface performance attributes on page 412 for a complete description of these attributes.



418

MR-3.5 Encapsulation performance attributes

This section discusses the performance attributes of the encapsulation protocols that can be used on the Telindus 1423 SHDSL Router.



• MR-3.5.1 - ATM performance attributes on page 419• MR-3.5.2 - Frame Relay performance attributes on page 424• MR-3.5.3 - Error test performance attributes on page 428



419

MR-3.5.1 ATM performance attributes


• telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable on page 420• telindus1423Router/wanInterface/channel[wan_1]/atm/unknownCells on page 423• telindus1423Router/wanInterface/channel[wan_1]/atm/vp on page 423



420


This attribute lists the complete performance information of all known PVCs.

The pvcTable table contains the following elements:

Element Description

name This is the name of the PVC as you configured it.

mibCounters This displays the SNMP MIB2 parameters of the PVC.

These are the same as the SNMP MIB2 parameters on the LAN interface. Refer to MR-3.3 - LAN interface performance attributes on page 412.

priorityQLengths In case an overload condition occurs and priority queuing is activated, then this elements displays how many packets the different queues contain.

Refer to MU-8.8.1 - Présentation de la politique de trafic et de priorité on page 250 for more information on the priority queues.

atm This displays the specific ATM related performance information of the PVC.

Refer to telindus1423Router/wanInterface/channel[wan_1]/atm/pvcTable/atm on page 421 for a detailed description of the atm structure



421


The atm structure in the pvcTable displays the specific ATM related performance information of the PVC.


Element Description

vpi This displays the Virtual Path Identifier (VPI).

vci This displays the Virtual Channel Identifier (VCI).

The VPI in conjunction with the VCI identifies the next destination of a cell as it passes through a series of ATM switches on the way to its destination.

oamF5 This displays the performance information of the OAM F5 loopback cells.

The oamF5 structure contains the following elements:

• rxLoopback. This displays the number of received loopback cells.• txLoopback. This displays the number of transmitted loopback cells.• rxCC. This displays the number of received continuity check cells.• txCC. This displays the number of transmitted continuity check cells.• rxAD. This displays the number of received and accepted continuity check acti-

vator/deactivator cells.• rxADdrop. This displays the number of received continuity check activator/deac-

tivator cells that were dropped (e.g. because the correlation tag was wrong).• txAD. This displays the number of transmitted continuity check activator/deacti-

vator cells.• rxSegAis. This displays the number of received segment Alarm Indication Sig-

nals.• txSegAis. This displays the number of transmitted segment Alarm Indication Sig-

nals.• rxSegRdi. This displays the number of received segment Remote Defect Indica-

tions.• txSegRdi. This displays the number of transmitted segment Remote Defect Indi-

cations.• rxEteAis. This displays the number of received end-to-end Alarm Indication Sig-

nals.• txEteAis. This displays the number of transmitted end-to-end Alarm Indication

Signals.• rxEteRdi. This displays the number of received end-to-end Remote Defect Indi-

cations.• txEteRdi. This displays the number of transmitted end-to-end Remote Defect

Indications.



422

What is OAM segment/end-to-end VP/VC AIS and RDI?

OAM VP/VC AIS (Alarm Indication Signal) and RDI (Remote Defect Indication) are cells that are used for identifying and reporting VP/VC defects on a segment/end-to-end level. When a physical link or interface failure occurs, intermediate nodes insert AIS cells into all the downstream VP/VCs affected by the failure. Upon receiving an AIS cell on a VP/VC, the router marks the logical interface down and sends an RDI cell on the same VP/VC to let the remote end know the error status. When an RDI cell is received on a VP/VC, the router sets the logical interface sta-tus to down.

Element Description



423

telindus1423Router/wanInterface/channel[wan_1]/atm/unknownCells

This attribute displays the number of received cells that are not in-band for a certain PVC.

Example

Suppose router A sends OAM F4 loopback cells on VPI 5. On router B no VPI 5 is configured or no OAM F4 loopback cells are configured for VPI 5. In that case, the unknownCells value on router B will increase.


Whereas the atm structure in the pvcTable displays the OAM F5 loopback cell performance information for each Virtual Channel, the vp table displays the OAM F4 loopback cell performance information of a com-plete Virtual Path.


Element Description

vpi This is the Virtual Path Identifier (VPI).

oamF4 This displays the performance information of the OAM F4 loopback cells.

The oamF4 structure contains the following elements:

• rxLoopback. This displays the number of received OAM F4 loopback cells.• txLoopback. This displays the number of transmitted OAM F4 loopback cells.



424

MR-3.5.2 Frame Relay performance attributes


• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable on page 425• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/lmi on page 427• telindus1423Router/wanInterface/channel[wan_1]/frameRelay/cllmInFrames on page 427



425


This attribute lists the complete performance information of all known DLCIs.

The dlciTable table contains the following elements:

Element Description

name This is the name of the DLCI as you configured it.

mibCounters This displays the SNMP MIB2 parameters of the DLCI.


frameRelay This displays the specific Frame Relay related performance information of the DLCI.

Refer to telindus1423Router/wanInterface/channel[wan_1]/frameRelay/dlciTable/frameRelay on page 426 for a detailed description of the frameRelay structure.



426


The frameRelay structure in the dlciTable displays the specific Frame Relay related performance information of the DLCI.


Element Description

dlci This is the DLCI identification number.

inFecn This is the number of frames received from the network indicating forward conges-tion and this since the virtual circuit was created.

inBecn This is the number of frames received from the network indicating backward con-gestion and this since the virtual circuit was created.

inDe This is the number of frames received with the Discard Eligibility bit set.

inOctets This is the number of octets received over this virtual circuit since it was created.

inFrames This is the number of frames received over this virtual circuit since it was created.

outFecn This is the number of frames sent to the network indicating forward congestion and this since the virtual circuit was created.

outBecn This is the number of frames sent to the network indicating backward congestion and this since the virtual circuit was created.

outDe This is the number of frames sent to the network with the Discard Eligibility bit set.

outOctets This is the number of octets sent over this virtual circuit since it was created.

outFrames This is the number of frames sent over this virtual circuit since it was created.



427


This attribute gives a complete LMI performance overview.


telindus1423Router/wanInterface/channel[wan_1]/frameRelay/cllmInFrames

This attribute displays the total number of received CLLM (Consolidated Link Layer Management) frames.

Element Description

inStatusEnquiry This is the number of Status Enquiries received from the network.

inStatus This is the number of Status Reports received from the network.

inStatusUpdate This is the number of unsolicited Status Updates received from the network.

outStatusEnquiry This is the number of Status Enquiries sent to the network.

outStatus This is the number of Status Reports sent to the network.

outStatusUpdate This is the number of unsolicited Status Updates sent to the network.

netPollNotRcvd This is the number of times the expectedPollInterval expired without an incoming sta-tus enquiry.

userNoResponse-Rcvd

This is the number of times a response was not received.

userBadResponses-Rcvd

This is the number of times an invalid response was received.



428

MR-3.5.3 Error test performance attributes


• telindus1423Router/wanInterface/channel[wan_1]/errorTest/status on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/duration on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/ifUpTime on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/ifDownCount on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBitErrors on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBlockErrors on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBlocks on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxAllOneBlocks on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxAllZeroBlocks on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxPatternSlip on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxShiftCount on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxSyncLoss on page 429• telindus1423Router/wanInterface/channel[wan_1]/errorTest/txBlocks on page 430• telindus1423Router/wanInterface/channel[wan_1]/errorTest/txInjectErrors on page 430


• telindus1423Router/wanInterface/channel[wan_1]/errorTest/startTest on page 430• telindus1423Router/wanInterface/channel[wan_1]/errorTest/stopTest on page 430• telindus1423Router/wanInterface/channel[wan_1]/errorTest/injectError on page 430• telindus1423Router/wanInterface/channel[wan_1]/errorTest/clearCounters on page 430



429

telindus1423Router/wanInterface/channel[wan_1]/errorTest/status

This attribute displays the status of the error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/duration

This attribute displays the duration of the error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/ifUpTime

This attribute displays the time during which the interface was up, since the start of the error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/ifDownCount

This attribute displays the amount of times the interface went down, since the start of the error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBitErrors

This attribute displays the amount of received bit errors.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBlockErrors

This attribute displays the amount of received block errors.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxBlocks

This attribute displays the amount of received test blocks.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxAllOneBlocks

This attribute displays the amount of received blocks in which all bits were set to “1”.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxAllZeroBlocks

This attribute displays the amount of received blocks in which all bits were set to “0”.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxPatternSlip

This attribute displays the amount of received pattern slips.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxShiftCount

This attribute displays the amount of received shifts.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/rxSyncLoss

This attribute displays the amount of received synchronisation losses.



430

telindus1423Router/wanInterface/channel[wan_1]/errorTest/txBlocks

This attribute displays the amount of transmitted test blocks.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/txInjectErrors

This attribute displays the amount of transmitted errors that were injected using the injectError action.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/startTest

Use this action to start an error test.


telindus1423Router/wanInterface/channel[wan_1]/errorTest/stopTest

Use this action to stop an error test.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/injectError

Use this action to inject an error.

telindus1423Router/wanInterface/channel[wan_1]/errorTest/clearCounters

Use this action to clear the counters.



431

MR-3.6 SHDSL line performance attributes

This section describes the following line performance attributes:

• telindus1423Router/wanInterface/line/h2Line on page 432• telindus1423Router/wanInterface/line/h24Line on page 432• telindus1423Router/wanInterface/line/d7Line on page 432• telindus1423Router/wanInterface/line/line on page 432

This section describes the following line pair performance attributes:

• telindus1423Router/wanInterface/line/linePair[ ]/h2LineParameters on page 433• telindus1423Router/wanInterface/line/linePair[ ]/h24LineParameters on page 433• telindus1423Router/wanInterface/line/linePair[ ]/d7LineParameters on page 433• telindus1423Router/wanInterface/line/linePair[ ]/lineParameters on page 433• telindus1423Router/wanInterface/line/linePair[ ]/h2Performance on page 434• telindus1423Router/wanInterface/line/linePair[ ]/h24Performance on page 434• telindus1423Router/wanInterface/line/linePair[ ]/d7Performance on page 434• telindus1423Router/wanInterface/line/linePair[ ]/performance on page 434


• telindus1423Router/wanInterface/line/retrain on page 432



432

telindus1423Router/wanInterface/line/h2Line

This attribute displays the 2 hours performance information summary of the line.

The h2Line table contains the following elements:

telindus1423Router/wanInterface/line/h24Line

This attribute displays the 24 hours performance information summary of the line. The h24Line table con-tains the same elements as the telindus1423Router/wanInterface/line/h2Line table.

telindus1423Router/wanInterface/line/d7Line

This attribute displays the 7 days performance information summary of the line. The d7Line table contains the same elements as the telindus1423Router/wanInterface/line/h2Line table.

telindus1423Router/wanInterface/line/line

This attribute displays the performance information summary of the line since the last cold boot. Except for the sysUpTime, the line structure contains the same elements as the telindus1423Router/wanInterface/line/h2Line table.

telindus1423Router/wanInterface/line/retrain

Use this action to force a retrain on the line.



linkDownCount the number of times the link went down.

linkDownTime the total amount of time the link was down.



433

telindus1423Router/wanInterface/line/linePair[ ]/h2LineParameters

This attribute displays the 2 hours line parameter summary.

The h2LineParameters table contains the following elements:

telindus1423Router/wanInterface/line/linePair[ ]/h24LineParameters

This attribute displays the 24 hours line parameter summary. The h24LineParameters table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2LineParameters table.

telindus1423Router/wanInterface/line/linePair[ ]/d7LineParameters

This attribute displays the 7 days line parameter summary. The d7LineParameters table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2LineParameters table.

telindus1423Router/wanInterface/line/linePair[ ]/lineParameters

This attribute displays the line parameter summary since the last cold boot. Except for the sysUpTime, the lineParameters table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2LineParameters table.



lineAttenuationMin the minimum line attenuation that was measured.

lineAttenuationAvrg the average line attenuation that was calculated

lineAttenuationMax the maximum line attenuation that was measured.

signalNoiseMin the minimum signal to noise ratio that was measured.

signalNoiseAvrg the average signal to noise ratio that was calculated.

signalNoiseMax the maximum signal to noise ratio that was measured.



434

telindus1423Router/wanInterface/line/linePair[ ]/h2Performance

This attribute displays the 2 hours performance summary of the line.

The h2Performance table contains the following elements:

• Errors are counted based on the SHDSL frame CRC.• For the correct and unambiguous definition of code violations, errored and severely errored seconds,

unavailability and lost synchronisation words seconds, refer to the recommendation G.826.

telindus1423Router/wanInterface/line/linePair[ ]/h24Performance

This attribute displays the 24 hours performance summary of the line. The h24Performance table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2Performance table.

telindus1423Router/wanInterface/line/linePair[ ]/d7Performance

This attribute displays the 7 days performance summary of the line. The d7Performance table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2Performance table.

telindus1423Router/wanInterface/line/linePair[ ]/performance

This attribute displays the performance summary of the line since the last cold boot. Except for the sysUp-Time, the performance table contains the same elements as the telindus1423Router/wanInterface/line/linePair[ ]/h2Performance table.



codeViolations the number of line errors that was counted.

errSec the number of erroneous seconds that was counted.

sevErrSec the number of severely erroneous seconds that was counted.

unavailSec the number of unavailable seconds that was counted.

loswSec the number of lost synchronisation words seconds that was counted.

moniSec the number of monitored seconds.



435

MR-3.7 End and repeater performance attributes

Exactly which information is retrieved from the remote SHDSL device(s) through the EOC channel depends on the setting of the eocHandling attribute. Refer to MU-5.4.4 - eocHandlingQuelles informations EOC standard sont-elles récupérées ? on page 82 for an overview.

The performance information of the line pairs of the repeater and end device is only retrieved in case the eocHandling attribute is set to info or alarmConfiguration. Other than that, the repeater[ ]/linePair[ ] and end/linePair[ ] objects contain the same performance attributes as the line/linePair[ ] object. Refer to MR-3.6 - SHDSL line performance attributes on page 431 for more information on these attributes.

Note that the sysUpTime in the performance attributes of the repeater[ ]/linePair[ ] and end/linePair[ ] objects is not the elapsed time since the last cold boot, but the elapsed time since the creation of the repeater[ ] or end object.



436

MR-3.8 BRI performance attributes

This section discusses the performance attributes of the BRI interface. First it describes the performance attributes of the BRI interface in general. Then it describes more specifically the performance attributes of the B-channels and of the leasedLine[ ] object that can be added under the bri[ ] object.


• MR-3.8.1 - General BRI performance attributes on page 437• MR-3.8.2 - B-channel performance attributes on page 439• MR-3.8.3 - ISDN leased line performance attributes on page 440



437

MR-3.8.1 General BRI performance attributes


• telindus1423Router/bri[ ]/h2DialupStats on page 438• telindus1423Router/bri[ ]/h24DialupStats on page 438• telindus1423Router/bri[ ]/d7DialupStats on page 438



438

telindus1423Router/bri[ ]/h2DialupStats

This attribute displays the 2 hours dial-up statistics of the BRI interface. The h2DialupStats table contains the following elements:

telindus1423Router/bri[ ]/h24DialupStats

This attribute displays the 24 hours dial-up statistics of the BRI interface. The h24DialupStats table contains the same elements as the telindus1423Router/bri[ ]/h2DialupStats table.

telindus1423Router/bri[ ]/d7DialupStats

This attribute displays the 7 days dial-up statistics of the BRI interface. The d7DialupStats table contains the same elements as the telindus1423Router/bri[ ]/h2DialupStats table.



sucDialOuts the number of successful dial-out calls.

sucDialIns the number of successful dial-in calls.

failDialOuts the number of failed dial-out calls.

failDialIns the number of failed dial-in calls.

onlineSec the number of seconds that both the dial-in and dial-out calls were active.

outOnlineSec the number of seconds that the dial-out calls were active.



439

MR-3.8.2 B-channel performance attributes

The performance attributes of the B-channels are the same as on the LAN interface. Therefore, they are not explained here again. Refer to MR-3.3 - LAN interface performance attributes on page 412 for a com-plete description of these attributes.



440

MR-3.8.3 ISDN leased line performance attributes

The performance attributes of the ISDN leased line are the same as on the LAN interface. Therefore, they are not explained here again. Refer to MR-3.3 - LAN interface performance attributes on page 412 for a complete description of these attributes.

The performance attributes of the encapsulation objects (frameRelay, ppp, hdlc and errorTest) which are located under the leasedLine[ ] object are explained in MR-3.5 - Encapsulation performance attributes on page 418.



441

MR-3.9 AUX performance attributes

All performance attributes of the AUX interface are the same as on the LAN interface. Therefore, they are not explained here again. Refer to MR-3.3 - LAN interface performance attributes on page 412 for a complete description of these attributes.



442

MR-3.10 Dial maps performance attributes





443


This attribute displays the dial-up statistics of all the dial maps. The mapping table contains the following elements:

Element Description

name This displays the dial map name. It is the name as you configured it in the name element of the dial map.

h2DialupStats This displays the 2 hour dial-up statistics of the dial map.

Refer to telindus1423Router/bri[ ]/h2DialupStats on page 438 for a detailed description of the h2DialupStats table.

h24DialupStats This displays the 24 hour dial-up statistics of the dial map.

Refer to telindus1423Router/bri[ ]/h24DialupStats on page 438 for a detailed description of the h24DialupStats table.

d7DialupStats This displays the 7 days dial-up statistics of the dial map.

Refer to telindus1423Router/bri[ ]/d7DialupStats on page 438 for a detailed description of the d7DialupStats table.



444

MR-3.11 Bundle performance attributes

This section describes the performance attributes of the different bundles that can be set up on the Tel-indus 1423 SHDSL Router. The following gives an overview of this section:

• MR-3.11.1 - PPP bundle performance attributes on page 445



445

MR-3.11.1 PPP bundle performance attributes

All performance attributes, except one, of the PPP bundle are the same as those of the LAN interface. Therefore, they are not explained here again. Refer to MR-3.3 - LAN interface performance attributes on page 412 for a complete description of these attributes.

However, the following attribute is only present in the PPP bundle object and therefore explained in this section:

• telindus1423Router/bundle/pppBundle[ ]/multiclassinterfaces on page 446



446

telindus1423Router/bundle/pppBundle[ ]/multiclassinterfaces

This attribute displays the performance of the different multiclass PPP links in the PPP bundle.

The multiclassinterfaces table contains following elements:

Element Description

name This element displays the name of the multiclass PPP link as you defined it in the multiclassInterfaces configuration attribute.

mibCounters This element displays the SNMP MIB2 parameters of the multiclass PPP link.

These are the same as the SNMP MIB2 parameters of the LAN interface. Refer to MR-3.3 - LAN interface performance attributes on page 412.



447

MR-3.12 Router performance attributes

This section discusses the performance attributes concerned with routing. First it describes the general routing performance attributes. Then it explains the performance attributes of the extra features as there are NAT, filtering, L2TP tunnelling, etc…


• MR-3.12.1 - General router performance attributes on page 448• MR-3.12.2 - NAT performance attributes on page 455• MR-3.12.3 - L2TP tunnel performance attributes on page 458• MR-3.12.4 - Manual SA performance attributes on page 460• MR-3.12.5 - IKE SA performance attributes on page 462• MR-3.12.6 - Firewall performance attributes on page 465



448

MR-3.12.1 General router performance attributes


• telindus1423Router/ip/router/routingTable on page 449• telindus1423Router/ip/router/radiusAuth on page 450• telindus1423Router/ip/router/radiusAcct on page 450• telindus1423Router/ip/router/pingResults on page 451• telindus1423Router/ip/router/tracertResults on page 451


• telindus1423Router/ip/router/startPing on page 452• telindus1423Router/ip/router/stopPing on page 452• telindus1423Router/ip/router/startTracert on page 453• telindus1423Router/ip/router/stopTracert on page 454• telindus1423Router/ip/router/clearTracert on page 454



449


This attribute lists all known routes and how many times they are used.

The routingTable contains the following elements:

Element Description

network This element displays the IP address of the destination network.

mask This element displays the network mask of the destination network.

gateway This element displays the IP address of the next router on the path to the destina-tion network.

interface This element displays the interface through which the destination network can be reached. Possible values are:

• internal. The own protocol stack is used.• <name>. The destination network can be reached through this particular inter-

face. The <name> of the interface is the name as you configured it.Note that the “interface” can also be a DLCI, an ATM PVC, a tunnel, etc.

• discard. Packets for this destination are discarded.

uses This element displays how many times the route has been used since it is listed in the routing table.

For each IP packet that matches this route, the attribute value is incremented by one. RIP routes may disappear from the routing table, and re-appear afterwards. The attribute value is reset when a RIP route disappears from the routing table.



450

telindus1423Router/ip/router/radiusAuth

This attribute lists the RADIUS authentication server performance information.

The radiusAuth table contains the following elements:

telindus1423Router/ip/router/radiusAcct

This attribute lists the RADIUS accounting server performance information.

The radiusAcct structure contains the following elements:

Element Description

server This element displays the IP address of the authentication server.

requests This element displays the number of access requests that is sent to the authenti-cation server.

accepts This element displays the number of access accepts that is received from the authentication server.

rejects This element displays the number of access rejects that is received from the authentication server.

challenges This element displays the number of access challenges that is received from the authentication server.

badAuthenticators This element displays the total number of packets that contained invalid Message-Authenticator attributes.

timeOuts This element displays the authentication time-out.

droppedPackets This element displays the number of incoming packets dropped for reasons other than being malformed, bad authenticators, or unknown types.

Element Description

server This element displays the IP address of the accounting server.

requests This element displays the number of accounting requests that is sent to the accounting server.

responses This element displays the number of accounting responses that is received from the accounting server.

badAuthenticators This element displays the number of packets that contained invalid Signature attributes.

timeOuts This element displays the accounting time-out.

droppedPackets This element displays the number of incoming packets dropped for reasons other than being malformed, bad authenticators, or unknown types.



451

telindus1423Router/ip/router/pingResults

This attribute displays the results of a ping to an IP address started with the startPing action.

The pingResults structure contains the following elements:

telindus1423Router/ip/router/tracertResults

This attribute displays the results of a traceroute to an IP address/host started with the startTracert action.

The tracertResults table contains the following elements:

Element Description

ipAddress This element displays the IP address of the host that is being pinged.

numOfTxPackets This element displays the number of transmitted pings.

numOfRxPackets This element displays the number of correct answers on the transmitted pings.

minReplyTime This element displays the lowest reply time of all correct answers.

maxReplyTime This element displays the highest reply time of all correct answers.

avrgReplyTime This element displays the average reply time of all correct answers.

Element Description

ttl This element displays the Time To Live.

ipAddress This element displays the IP address of the hop that has been passed.

hostName This element displays the hostname of the hop that has been passed. Note that this only displays

nrTx This element displays the number of traceroute queries that have been transmitted to the hop.

nrRx This element displays the number of correct answers on the transmitted traceroute queries that have been received from the hop.

minRtt This element displays the minimum Round-Trip Time that has been measured.

maxRtt This element displays the maximum Round-Trip Time that has been measured.

avrgRtt This element displays the average Round-Trip Time that has been calculated.

successRate This element displays the success rate. It is the ratio of nrRx/nrTx expressed in per-cents.

comment This element displays some comments. E.g. Destination reached, Maximum number of hops reached, etc.



452

telindus1423Router/ip/router/startPing

Use this action to start transmitting pings to an IP address or host. The result of the ping can be seen in the pingResults attribute. Refer to telindus1423Router/ip/router/pingResults on page 451.

The argument value structure of the startPing action contains the following elements:

telindus1423Router/ip/router/stopPing

Use this action to stop pending pings.

Argument Description

ipAddress Use this element to specify the IP address of the host you want to ping.

If you fill in the ipAddress element you may omit the hostName element.

hostName Use this element to specify the hostname of the host you want to ping.

If you fill in the hostName element you may omit the ipAddress element.

sourceIp Use this element to specify the source IP address.

This can be used to force the source address to be something other than the IP address of the interface on which the traceroute query is sent. If this IP address is not one of the Telindus 1423 SHDSL Router interface addresses, then nothing is sent.

iterations Use this element to specify the number of pings.

If you set the iterations element to 0, then the host is pinged an indefinite number of times. The only way to stop the ping session is by executing the stopPing action.

interval Use this element to specify the interval, in seconds, between consecutive pings.

dataLength Use this element to specify the length, in bytes, of the data transmitted in a ping.

timeOut Use this element to specify the time-out period.

If a ping is sent, the Telindus 1423 SHDSL Router waits during this time-out period on the answer. If the answer is received …

• within this time-out period, then ping is considered successful.• outside this time-out period, then the ping is considered unsuccessful.








24855d 03h 14m 07s



453

telindus1423Router/ip/router/startTracert

Use this action to start a traceroute to an IP address or host. The result of the traceroute can be seen in the tracertResults attribute. Refer to telindus1423Router/ip/router/tracertResults on page 451.

The argument value structure of the startTracert action contains the following elements:


ipAddress Use this element to specify the IP address of the host you want to trace.

If you fill in the ipAddress element you may omit the hostName element.

hostName Use this element to specify the hostname of the host you want to trace.

If you fill in the hostName element you may omit the ipAddress element.

sourceIp Use this element to specify the source IP address.

This can be used to force the source address to be something other than the IP address of the interface on which the traceroute query is sent. If this IP address is not one of the Telindus 1423 SHDSL Router interface addresses, then nothing is sent.

startTtl Use this element to specify from which TTL onwards you want to see the traceroute results.

For example, if you set the startTtl element to 5, then the traceroute result displayed in the tracertResult attribute starts from TTL number 5. 1 up to 4 is not displayed.

maxHops Use this element to specify the maximum number of hops.

If the maximum number of hops is reached but the destination host is still not reached, then the last traceroute result displays the comment “Maximum number of hops reached“.

The default of 30 hops is the same default used for TCP connections.

queriesPerHop Use this element to specify how many traceroute que-ries have to be sent to each hop.

resolveHosts Use this element to enable or disable the resolving of hop IP addresses to hostnames.

If you set the resolveHosts elements to …

• enabled (default), then the hostName element in the tracertResults attribute displays the hostname of the hop.

• disabled, then the hostName element in the tracertResults attribute remains empty.

dnsTimeOut Use this element to set the DNS time-out.

When hop IP addresses are resolved to hostnames, then the DNS replies are expected within this time-out period. Else they are no longer accepted.









24855d 03h 14m 07s



454

telindus1423Router/ip/router/stopTracert

Use this action to stop pending traceroute queries.

telindus1423Router/ip/router/clearTracert

Use this action to clear the tracertResults table.

icmpTimeOut Use this element to set the ICMP time-out.

When a hop is queried, then the ICMP replies are expected within this time-out period. Else they are no longer accepted.

tos Use this element to set the Type Of Service in the traceroute query.

This can be used to investigate whether different service types result in different paths. Useful values are 16 (low delay) and 8 (high throughput).

packetLength Use this element to set the traceroute query datagram length in bytes.



24855d 03h 14m 07s





455

MR-3.12.2 NAT performance attributes


• telindus1423Router/ip/router/defaultNat/socketsFree on page 456• telindus1423Router/ip/router/defaultNat/allocFails on page 456• telindus1423Router/ip/router/defaultNat/discards on page 456• telindus1423Router/ip/router/defaultNat/addressesAvailable on page 456• telindus1423Router/ip/router/defaultNat/tcpSocketsUsed on page 456• telindus1423Router/ip/router/defaultNat/udpSocketsUsed on page 456• telindus1423Router/ip/router/defaultNat/icmpSocketsUsed on page 456• telindus1423Router/ip/router/defaultNat/tcpAllocs on page 457• telindus1423Router/ip/router/defaultNat/udpAllocs on page 457• telindus1423Router/ip/router/defaultNat/icmpAllocs on page 457


• telindus1423Router/ip/router/defaultNat/reset on page 457



456

telindus1423Router/ip/router/defaultNat/socketsFree

This attribute shows the remaining number of new connections (i.e. sockets) that can be initiated. A socket is a set of source and destination IP addresses and port numbers.

Initially, 2048 simultaneous sockets can be initiated. Sockets are freed using a garbage mechanism. This means that every five minutes all sockets are checked. If a socket has been released by PAT or NAT, then this socket is returned to the pool of free sockets.

ICMP and UDP sockets are released when they have no data traffic during five minutes. TCP sockets are released after the TCP session has been closed or when the session has been idle for 24 hours.

telindus1423Router/ip/router/defaultNat/allocFails

If no sockets are available anymore but an attempt to set up a new connection is being made, then the natAllocFails attribute value is incremented by 1.

Because the sockets are distributed using a hashing function, it is possible that natAllocFails increases even though natSocketsFree still indicates free sockets.

ICMP requires a new socket for each transmitted packet. This implies that, for instance, a permanent ping or trace-route command may eventually use all free sockets.

telindus1423Router/ip/router/defaultNat/discards

This attribute indicates how many times a packet has been discarded for reasons other than a lack of free sockets. This could be, for instance, because an attempt was made to connect from the Internet to a service that was not present in the servicesAvailable table.

telindus1423Router/ip/router/defaultNat/addressesAvailable

This attribute displays the number of NAT addresses that are currently free.

telindus1423Router/ip/router/defaultNat/tcpSocketsUsed

This attribute displays the number of sockets currently in use by PAT and NAT for TCP applications.

telindus1423Router/ip/router/defaultNat/udpSocketsUsed

This attribute displays the number of sockets currently in use by PAT and NAT for UDP applications.

telindus1423Router/ip/router/defaultNat/icmpSocketsUsed

This attribute displays the number of sockets currently in use by PAT and NAT for ICMP applications.



457

telindus1423Router/ip/router/defaultNat/tcpAllocs

This attribute indicates how many TCP sockets have been allocated since cold boot. Together with the performance attributes natUdpAllocs and natIcmpAllocs it gives an indication of the type of traffic that is being routed.

telindus1423Router/ip/router/defaultNat/udpAllocs

This attribute indicates how many UDP sockets have been allocated since cold boot. Together with the performance attributes natTcpAllocs and natIcmpAllocs it gives an indication of the type of traffic that is being routed.

telindus1423Router/ip/router/defaultNat/icmpAllocs

This attribute indicates how many ICMP sockets have been allocated since cold boot. Together with the performance attributes natTcpAllocs and natUdpAllocs it gives an indication of the type of traffic that is being routed.

telindus1423Router/ip/router/defaultNat/reset

Use this action to release all sockets currently in use and return them to the free socket pool.

In other words, executing this action resets all NAT/PAT sessions that are currently established. It also releases all official IP addresses that are dynamically assigned to a private IP address. If any TCP ses-sions are still active, these sessions will be aborted.

Take care when using this action! All TCP information is lost when the sockets are released with this action. Any TCP sessions in use at the time of the reset will go into a hang-up state. These applications will need to restart.



458

MR-3.12.3 L2TP tunnel performance attributes





459


This attribute displays the performance information of the L2TP tunnels.



This attribute displays the performance information of the L2TP tunnels.

The ipsecL2tpTunnels table contains the same elements as the l2tpTunnels table. Refer to telindus1423Router/ip/router/tunnels/l2tpTunnels on page 459.

Element Description

name This is the name of the tunnel as you configured it.

mibCounters This displays the SNMP MIB2 parameters of the tunnel.




460

MR-3.12.4 Manual SA performance attributes


• telindus1423Router/ip/router/manualSA[ ]/inPackets on page 461• telindus1423Router/ip/router/manualSA[ ]/outPackets on page 461• telindus1423Router/ip/router/manualSA[ ]/espDecryptionFailure on page 461• telindus1423Router/ip/router/manualSA[ ]/espAuthenticationFailure on page 461• telindus1423Router/ip/router/manualSA[ ]/espSequenceNrReplay on page 461• telindus1423Router/ip/router/manualSA[ ]/espDroppedFrames on page 461



461

telindus1423Router/ip/router/manualSA[ ]/inPackets

Upon receipt of a (reassembled) packet containing an ESP Header, the receiver determines the appro-priate SA, based on the destination IP address, security protocol (ESP), and the SPI. Once the appro-priate SA is determined, the inPackets attribute is incremented for this SA.

telindus1423Router/ip/router/manualSA[ ]/outPackets

ESP is applied to an outbound packet only after it is determined that the packet is associated with an SA that calls for ESP processing. Once the appropriate SA is determined, the outPackets attribute is incre-mented for this SA.

telindus1423Router/ip/router/manualSA[ ]/espDecryptionFailure

This attribute displays the number of times the decryption of an incoming ESP packet failed.

telindus1423Router/ip/router/manualSA[ ]/espAuthenticationFailure

This attribute displays the number of times the authentication of an incoming ESP packet failed.

telindus1423Router/ip/router/manualSA[ ]/espSequenceNrReplay

For each incoming ESP packet, the receiver verifies that the packet contains a sequence number that does not duplicate the sequence number of any other packets received during the life of this SA. Should this be the case, then these packets are dropped and the espSequenceNrReplay attribute is incremented for this SA.

telindus1423Router/ip/router/manualSA[ ]/espDroppedFrames

This attribute displays the number of ESP packets that were successfully decrypted and authenticated, but that could not be delivered to the L2TP tunnel (e.g. because the tunnel was down) and had to be dropped.



462

MR-3.12.5 IKE SA performance attributes


• telindus1423Router/ip/router/ikeSA[ ]/phase2Negotiations on page 463• telindus1423Router/ip/router/ikeSA[ ]/phase2Sessions on page 463



463

telindus1423Router/ip/router/ikeSA[ ]/phase2Negotiations

This attribute displays performance information of the IKE phase 2 negotiation process.

The phase2Negotiations table contains the following elements:

telindus1423Router/ip/router/ikeSA[ ]/phase2Sessions

This attribute displays performance information of the IKE phase 2 sessions.


Element Description


initStarted This element displays the number of IKE phase 2 negotiation initiations that were started.

respStarted This element displays the number of IKE phase 2 negotiation responses that were started.

succeeded This element displays the number of IKE phase 2 negotiations that succeeded.

failed This element displays the number of IKE phase 2 negotiations that failed.

expiredSA This element displays the number of IKE SAs that expired.

Element Description


direction This element displays the direction of the IPSEC SA. Possible values are: inbound or outbound.

spi This element displays the Security Parameter Index of the IPSEC SA.

protocol This element displays which protocol is used in the IPSEC SA. Possible values are: esp or ah.

outPackets This element displays the number of outbound packets for which an appropriate SA could be determined.

Only after an appropriate SA could be determined, the security protocol (ESP or AH) is applied to the outbound packet.

outOctets This element displays the number of outbound octets (bytes) for which an appro-priate SA could be determined.

inPackets This element displays the number of inbound packets for which an appropriate SA could be determined.

Only after an appropriate SA could be determined, the inbound packet is accepted.

inOctets This element displays the number of inbound octets (bytes) for which an appropri-ate SA could be determined.

authenticationFail-ure

This element displays the number of times the authentication of an incoming packet failed.



464

decryptionFailure This element displays the number of times the decryption of an incoming packet failed.

sequenceNrReplay For each incoming packet, the receiver verifies that the packet contains a sequence number that does not duplicate the sequence number of any other pack-ets received during the life of this SA. Should this be the case, then these packets are dropped and the sequenceNrReplay attribute is incremented for this SA.

droppedFrames This element displays the number of packets that were successfully decrypted and authenticated, but that could not be delivered to the L2TP tunnel (e.g. because the tunnel was down) and had to be dropped.

Element Description



465

MR-3.12.6 Firewall performance attributes


• telindus1423Router/ip/router/firewall/h24General on page 466• telindus1423Router/ip/router/firewall/d7General on page 466• telindus1423Router/ip/router/firewall/h24Attack on page 467• telindus1423Router/ip/router/firewall/d7Attack on page 468



466

telindus1423Router/ip/router/firewall/h24General

This attribute displays the 24 hours general performance summary.

The h24General table contains the following elements:

telindus1423Router/ip/router/firewall/d7General

This attribute displays the 7 days general performance summary.

The d7General table contains same elements as the h24General table. Refer to telindus1423Router/ip/router/fire-wall/h24General on page 466.



maxConn the number of times that the maximum number of connections was reached.

maxResource the number of times that the used resources exceeded 80%. This could indicate flooding.

serviceAcc the number of service access requests that were successful.

noSrcRoute the number of times that no route to the source could be found.

srcBcast the number of source address broadcasts.

synUnable the number of times that no SYN packet could be sent.

finalAckFail the number of times that no final ACK could be sent.

denyPolicy the number of times that a deny policy matched.

connLimit the number of times that the maximum number of connections was reached.

srcRouteOpt the number of times that the source routing option was set for an IP packet.

policyDeleted the number of times that the policy was already deleted.

noDestRoute the number of times that no route to the destination could be found.

rejToSelf the number of times that packets to self were rejected.

destBcast the number of destination address broadcasts.

noInPol the number of times that no inbound policy could be found.

noOutPol the number of times that no outbound policy could be found.



467

telindus1423Router/ip/router/firewall/h24Attack

This attribute displays the 24 hours attack summary.

The h24Attack table contains the following elements:



landAttack the number of (possible) land attacks.

spoofedPacket the number of spoofed packets.

badTcpConnReq the number of invalid TCP connection requests.

badTcpAck the number of invalid TCP ACKs.

unexpUdpE-choResp

the number of received UDP echo responses for uninitiated requests.

unexpIcmpE-choResp

the number of received ICMP echo responses for uninitiated requests.

genAttack the number of general attacks.

minIpHdrLen the number of packets with an IP header length less than the minimum length.

emptyPacket the number of packets without data.

badTcpLen the number of times the TCP packet length was invalid.

shortTcpHdr the number of packets with short TCP header length.

tcpNullScan the number of TCP null scan attacks.

badUdpLen the number of times the UDP packet length was invalid.

shortUdpHdr the number of packets with short UDP header length.

shortIcmpLen the number of packets with short ICMP length.

synAttack the number of SYN attacks.

postTcpRst the number of data packets received after reset.

blindSpoofing the number of blind spoofing attacks.

zeroBytes the number of times zero bytes were transferred for a connection.

seqNumOutOf-Range

the number of packets with an out-of-range sequence number.

winNuke the number of WinNuke attacks.

badTcpSeqNumRst the number of invalid sequence numbers with reset.

zeroLenIpOpt the number of zero length IP options detected.

badIpTimeStamp the number of unaligned timestamp options detected.

unexpData the number of times unexpected data was received for uninitiated traffic.

unexpIcmpErr the number of received ICMP error messages for uninitiated requests.

badSrcIf the number of times the source interface was invalid.



468

telindus1423Router/ip/router/firewall/d7Attack

This attribute displays the 7 days attack summary.

The d7Attack table contains same elements as the h24Attack table. Refer to telindus1423Router/ip/router/firewall/h24Attack on page 467.



469

MR-3.13 IP traffic policy performance attributes


• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/discards on page 470• telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/trafficShaping on page 470



470

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/discards

This attribute indicates how many packets have been discarded based on the criteria that are defined by the IP traffic policy.

telindus1423Router/profiles/policy/traffic/ipTrafficPolicy[ ]/trafficShaping

This attribute shows the usage of each line in the traffic shaping table.

The trafficShaping table contains the following elements:

Element Description

name This is the name of the line in the traffic shaping table as you configured it.

uses This is the number of times this line in the traffic shaping table is used.

sourceIpStart-Address

This is the IP source address range as you configured it.

Packets that fall within the specified range are forwarded and queued if applicable.sourceIpEnd-Address

destinationIpStart-Address

This is the IP destination address range as you configured it.

Packets that fall within the specified range are forwarded and queued if applicable.destinationIpEnd-Address

tosStartValue This is the TOS range as you configured it.

Packets that fall within the specified range are forwarded and queued if applicable.tosEndValue

ipProtocol This is the protocol field as you configured it.

Packets that have the specified protocol field are forwarded and queued if applica-ble.

sourcePortStart This is the source port range as you configured it.

Packets that fall within the specified range are forwarded and queued if applicable.sourcePortEnd

destinationPortStart This is the destination port range as you configured it.

Packets that fall within the specified range are forwarded and queued if applicable.destinationPortEnd

newTosValue This is the new TOS value as you configured it.

priority This is the destination queue as you configured it.

In case an overload condition occurs, then a packet that matches an entry in the trafficShaping table is sent to the specified queue.



471

MR-3.14 Bridge performance attributes

This section discusses the performance attributes concerned with bridging. First it describes the general bridging performance attributes. Then it explains the performance attributes of the extra features as there are access listing, etc…


• MR-3.14.1 - Bridge group performance attributes on page 472• MR-3.14.2 - Bridge access list performance attributes on page 475



472

MR-3.14.1 Bridge group performance attributes


• telindus1423Router/bridge/bridgeGroup/bridgeCache on page 473• telindus1423Router/bridge/bridgeGroup/bridgeDiscards on page 473• telindus1423Router/bridge/bridgeGroup/bridgeFloods on page 473• telindus1423Router/bridge/bridgeGroup/multiVlans on page 473• telindus1423Router/bridge/bridgeGroup/vlanSwitching on page 474



473


When a port of the bridge enters the learning state, it stores the MAC addresses of the stations situated on the network that is connected to this port. The MAC addresses are stored in a MAC address database or bridge cache. The bridgeCache attribute visualises this address database. Refer to What is the bridge cache? on page 225 for more information.

The bridgeCache table contains the following elements:

telindus1423Router/bridge/bridgeGroup/bridgeDiscards

This attribute displays the number of times a frame was discarded because …

• it was received on the same interface as the one through which the destination address can be reached.

• it was received on an interface that is not in the forwarding state.

telindus1423Router/bridge/bridgeGroup/bridgeFloods

This attribute displays the number of times a frame was flooded on all interfaces because …

• it was a broadcast / multicast.• the position of the station with the destination MAC address was not known (yet).

telindus1423Router/bridge/bridgeGroup/multiVlans

This attribute displays the SNMP MIB2 performance parameters of the VLANs that are present on the bridge group.

The multiVlans table contains the following elements:

Element Description

interface This is the interface through which the station can be reached.

macAddress This is the MAC address of the station situated on the network connected to the interface.

rxCount This is the number of frames received from the corresponding MAC address.

txCount This is the number of frames forwarded to the corresponding MAC address.

Element Description

name This element displays the name of the VLAN as you configured it.

vlan This element displays the VLAN ID.

mibCounters This element displays the SNMP MIB2 performance parameters of the VLAN.

Refer to MR-3.3 - LAN interface performance attributes on page 412 for an expla-nation of the individual SNMP MIB2 performance parameters.



474

telindus1423Router/bridge/bridgeGroup/vlanSwitching

This attribute displays the performance information of the VLAN switching process.

The vlanSwitching table contains the following elements:

Element Description

sourceIntf This element displays the name of the source interface.

sourceVlan This element displays the VLAN ID of the source VLAN.

destinationIntf This element displays the name of the destination interface.

destinationVlan This element displays the VLAN ID of the destination VLAN.

uses This element displays the number of packets that have been switched.



475

MR-3.14.2 Bridge access list performance attributes


• telindus1423Router/bridge/accessList[ ]/bridgeAccessList on page 476



476

telindus1423Router/bridge/accessList[ ]/bridgeAccessList

This attribute shows information on the use of the bridge access list.

The bridgeAccessList table contains the following elements:

Element Description

macAddress This is the MAC address as configured in the configuration attribute telindus1423Router/bridge/accessList[ ]/bridgeAccessList.

uses This indicates the number of times a packet has been discarded for the corre-sponding MAC address.



477

MR-3.15 Management performance attributes


• telindus1423Router/management/cms2SessionCount on page 478• telindus1423Router/management/cliSessionCount on page 478• telindus1423Router/management/tftpSessionCount on page 479• telindus1423Router/management/tcpSessionCount on page 479• telindus1423Router/management/ipStackEvents on page 479



478

telindus1423Router/management/cms2SessionCount

This attribute displays the number of CMS2 sessions that are currently active on the Telindus 1423 SHDSL Router.

There are always minimum two fixed sessions active. Connecting with TMA, TMA CLI, Telnet, etc. opens additional sessions. This is explained in the following table:

telindus1423Router/management/cliSessionCount

This attribute displays the number of CLI sessions that are currently active on the Telindus 1423 SHDSL Router.

There are always minimum two fixed sessions active. Connecting with TMA CLI, the Web Interface, etc. opens additional sessions. This is explained in the following table:

Session count Purpose

1 fixed session A fixed session for SNMP.

1 fixed session A fixed session for O10.

+ 2 sessions When connecting with TMA.

+ 1 session When connecting with TMA for HP OpenView or the Alarm Manager.

+ 1 session When connecting with TMA CLI.

+ 2 sessions When downloading a config.cli or config.cms file.

+ 1 session When connecting with Telnet.

+ 1 session When downloading software.

+ 1 session When connecting with the Web Interface.


1 fixed session A fixed session for the control port.

1 fixed session A fixed session for Web Interface.

+ 1 session When connecting with TMA CLI or starting a CLI session.




479

telindus1423Router/management/tftpSessionCount

This attribute displays the number of TFTP sessions that are currently active on the Telindus 1423 SHDSL Router.

telindus1423Router/management/tcpSessionCount

This attribute displays the number of TCP sessions that are currently active on the Telindus 1423 SHDSL Router. The following table shows when a TCP session opens:

telindus1423Router/management/ipStackEvents

This attribute gives an indication of the internal load of the protocol stack.


+ 1 session When connecting with Telnet.




480

MR-3.16 Operating system performance attributes


• telindus1423Router/operatingSystem/currUsedProcPower on page 481• telindus1423Router/operatingSystem/usedProcPower on page 481• telindus1423Router/operatingSystem/freeDataBuffers on page 481• telindus1423Router/operatingSystem/totalDataBuffers on page 481• telindus1423Router/operatingSystem/largestFreeBlockSize on page 481• telindus1423Router/operatingSystem/freeBlockCount on page 481• telindus1423Router/operatingSystem/freeMemory on page 482• telindus1423Router/operatingSystem/totalMemory on page 482• telindus1423Router/operatingSystem/taskInfo on page 482



481

telindus1423Router/operatingSystem/currUsedProcPower

This attribute displays the amount of processing power used during the last 650 milliseconds, expressed as a percentage of the total available processing power.

telindus1423Router/operatingSystem/usedProcPower

This attribute lists the used processing power for the 11 most recent 30 seconds intervals. The process-ing power is expressed as a percentage of the total processing power.

The usedProcPower table contains the following elements:

telindus1423Router/operatingSystem/freeDataBuffers

The processor uses buffers for storing the packets during processing and/or queuing. Each buffer has a 256 byte size, headers included. This attribute is the number of data buffers currently not in use and available for e.g. incoming data.

telindus1423Router/operatingSystem/totalDataBuffers

This attribute displays the total number of available data buffers.

telindus1423Router/operatingSystem/largestFreeBlockSize

The processor uses RAM memory for storing internal information and buffering. The different tasks allo-cate RAM memory on request. Tasks may also free memory again. In this way the total RAM memory becomes fragmented. This attribute gives the size of the largest contiguous free memory block expressed in bytes.

telindus1423Router/operatingSystem/freeBlockCount

This attribute displays the number of free contiguous memory blocks.

Element Description

sysUpTime This is the elapsed time since the last cold boot. The next values are for the 30 seconds period before this relative time stamp.

min This is the minimum percentage of processing power in use during the last 30 sec-onds.

average This is the average percentage of processing power in use during the last 30 sec-onds.

max This is the maximum percentage of processing power in use during the last 30 sec-onds.



482

telindus1423Router/operatingSystem/freeMemory

This attribute displays the total free memory expressed in bytes.

telindus1423Router/operatingSystem/totalMemory

This attribute displays the total RAM memory expressed in bytes.

telindus1423Router/operatingSystem/taskInfo

This attribute contains status information concerning the different tasks running on the processor. It is a table grouping up to 31 task slots, which is the maximum number of parallel tasks running on the proc-essor's operating system.

This attribute contains the same elements as the status attribute telindus1423Router/operatingSystem/taskInfo on page 400.



483


User manual Alarm attributes

484

MR-4 Alarm attributes

This chapter discusses the alarm attributes of the Telindus 1423 SHDSL Router. The following gives an overview of this chapter:

• MR-4.1 - Alarm attributes overview on page 485• MR-4.2 - Introducing the alarm attributes on page 488• MR-4.3 - General alarms on page 491• MR-4.4 - LAN interface alarms on page 493• MR-4.5 - WAN interface alarms on page 494• MR-4.6 - SHDSL line alarms on page 495• MR-4.7 - SHDSL line pair alarms on page 496• MR-4.8 - End and repeater alarms on page 498• MR-4.9 - BRI alarms on page 500• MR-4.10 - B-channel alarms on page 501• MR-4.11 - AUX alarms on page 502• MR-4.12 - Bundle alarms on page 503• MR-4.13 - Router alarms on page 504



485

MR-4.1 Alarm attributes overview

> telindus1423RoutertotalAlarmLevelalarmInfo

notRespondingalarmSyncLossconfigChangedaccessunknownStatuscoldBootwarmBootcodeConsistencyFailconfigConsistencyFail

>> lanInterfacealarmInfo

linkDown

>> wanInterfacealarmInfo

linkDown

>>> linealarmInfo

linkDowninvalidNumRepeaters

>>>> linePair[ ]alarmInfo

linkDownlineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbbErrRatioExceeded

>>> repeater[ ]

>>>> networkLinePair[ ]alarmInfo

lineAttenuationsignalNoiseerrSecRatioExceededsevErrSecRatioExceededbbErrRatioExceeded



486

>>>> customerLinePair[ ]alarmInfo


>>> end

>>>> linePair[ ]alarmInfo


>> bri[1]1

alarmInfolinkDownsucDialOutsucDialInfailDialOutfailDialIn

>>> bChannel[1]alarmInfo

linkDown


>>> leasedLine[ ]alarmInfo

linkDown

>> bri[2]1


>> bundle

>>> pppBundlealarmInfo

linkDown




487

>> routeralarmInfo

pingActive



488

MR-4.2 Introducing the alarm attributes

Before discussing the alarm attributes of the Telindus 1423 SHDSL Router in detail, some general infor-mation on the alarm attributes of the Telindus 1423 SHDSL Router is given.

The following gives an overview of this chapter:

• MR-4.2.1 - Configuration alarm attributes on page 489• MR-4.2.2 - General alarm attributes on page 490



489

MR-4.2.1 Configuration alarm attributes

This section describes the following alarm attributes:

• telindus1423Router/…/alarmMask• telindus1423Router/…/alarmLevel

telindus1423Router/…/alarmMask

Use this attribute to mask or unmask the alarms of an object. This determines whether an active alarm is forwarded to the central management system (e.g. HP OpenView) or not.

The alarms in the alarmMask attribute have the following values:

Alarms are always seen in the alarmInfo alarm attribute of an object, regardless of the masking of the alarm. I.e. even if an alarm is set to disabled in the alarmMask of an object, if the alarm condition is fulfilled then the alarm will be set to on in the alarmInfo of that object. However, because this alarm is disabled it will not be sent to the central management system (e.g. HP OpenView).

Only the most important alarms are unmasked (i.e. enabled) by default. All other alarms are masked (i.e. disabled).

telindus1423Router/…/alarmLevel

Use this attribute to assign a priority level to each alarm of the corresponding object. The alarm level range goes from 0 to 254, where 0 is the lowest and 254 is the highest priority level.

The alarmLevel of an unmasked, active alarm is sent to the totalAlarmLevel alarm attribute of the top object telindus1423Router.

Value Is the active alarm being forwarded to the central management system?

enabled Yes. So the alarm is unmasked.

disabled No. So the alarm is masked.



490

MR-4.2.2 General alarm attributes

This section describes the following alarm attributes:

• telindus1423Router/totalAlarmLevel• telindus1423Router/…/alarmInfo

telindus1423Router/totalAlarmLevel

This attribute is only present in the top object of the containment tree of the Telindus 1423 SHDSL Router, being telindus1423Router.

It displays the priority level of an unmasked, active alarm. When several alarms are generated at the same time, the highest priority level is shown. If the alarm levels are set in a structured manner, one look at the totalAlarmLevel attribute enables the operator to make a quick estimation of the problem.

The value of the totalAlarmLevel attribute is also communicated to the central management system (e.g. HP OpenView) where it determines the colour of the icon. This colour is an indication of the severity of the alarm.

telindus1423Router/…/alarmInfo

This attribute contains the actual alarm information of the corresponding object.

The alarmInfo structure contains the following elements:

Element This element displays for the corresponding object …

discriminator the total alarm count since the last cold boot.

currentAlarms the current alarms.

previousAlarms the second most recent alarms.

alarmMask the alarmMask as you configured it.

alarmLevel the alarmLevel as you configured it.



491

MR-4.3 General alarms

This section describes the alarms of the alarm attribute telindus1423Router/alarmInfo.

Refer to MR-4.2 - Introducing the alarm attributes on page 488 for general information on the alarm attributes.

telindus1423Router/alarmInfo

The different alarms related to the telindus1423Router object together with their explanation and default alarmMask and alarmLevel value are given in the following table:

The alarm … is generated … Default value

alarmMask alarmLevel

notResponding by the management concentrator when the Telindus 1423 SHDSL Router does not respond on its polling ses-sion.

enabled 4

alarmSyncLoss when the internal alarm buffer overflows. enabled 4

configChanged when the local configuration has been changed. disabled 1

access when a management session is started on the Telindus 1423 SHDSL Router itself. This alarm is not activated when the management session is established through a management concentrator.

Example

The alarm is activated in case of …

• a TMA, TMA CLI, terminal (CLI or ATWIN) or Easy-Connect session via the control connector of the Tel-indus 1423 SHDSL Router.

• a TMA, TMA CLI, TMA for HP OpenView, Telnet (CLI or ATWIN), HTTP (Web Interface) or TFTP session using the LAN / WAN IP address of the Telindus 1423 SHDSL Router.

The alarm is not activated in case of …

• any management session (TMA, terminal, Telnet, HTTP, etc.) established through a management con-centrator on the Telindus 1423 SHDSL Router.

• SNMP management.

disabled 1

unknownState each time a new Telindus 1423 SHDSL Router is added to the network and before the management concentrator has completed a first successful polling session.

disabled 0

coldBoot each time the Telindus 1423 SHDSL Router performs a cold boot.

disabled 1

warmBoot each time the Telindus 1423 SHDSL Router performs a warm boot.

disabled 1



492

codeConsistency-Fail

when the software consistency imposed by the manage-ment concentrator on the Telindus 1423 SHDSL Router fails. For example, because of a loss of contact.

In the management concentrator that manages the Tel-indus 1423 SHDSL Router (e.g. the Orchid 1003 LAN, Telindus 1035 Orchid, etc.), check the status attribute nmsgroup/softConsistencyStatus to determine the problem.

disabled 1

configConsistency-Fail

when the configuration consistency imposed by the management concentrator on the Telindus 1423 SHDSL Router fails. For example, because of a loss of contact.

In the management concentrator that manages the Tel-indus 1423 SHDSL Router (e.g. the Orchid 1003 LAN, Telindus 1035 Orchid, etc.), check the status attribute status attributes nmsgroup/objectTable/configState and config-Diag to determine the problem.

disabled 1





493

MR-4.4 LAN interface alarms

This section describes the alarms of the alarm attribute telindus1423Router/lanInterface/alarmInfo.


telindus1423Router/lanInterface/alarmInfo

The alarm related to the lanInterface object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



linkDown when no valid LAN data is detected. I.e. when the con-nection between the interface and the LAN is down.

enabled 3



494

MR-4.5 WAN interface alarms

This section describes the alarms of the alarm attribute telindus1423Router/wanInterface/alarmInfo.


telindus1423Router/wanInterface/alarmInfo

The alarm related to the wanInterface object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



linkDown when an error situation is detected in the encapsulation protocol.

For instance, no ATM synchronisation, a failed PPP authentication, …

enabled 3



495

MR-4.6 SHDSL line alarms

This section describes the alarms of the alarm attribute telindus1423Router/wanInterface/line/alarmInfo.


telindus1423Router/wanInterface/line/alarmInfo

The alarms related to the line object together with their explanation and default alarmMask and alarmLevel value are given in the following table:



linkDown when the line is down. I.e. no data can be transmitted over the line.

enabled 3

invalidNum-Repeaters

if the number of repeaters you entered in the telindus1423Router/wanInterface/line/numExpectedRepeaters attribute does not match the actual number of repeaters discovered by the Telindus 1423 SHDSL Router.

The actual number of repeaters discovered by the Telin-dus 1423 SHDSL Router can be seen in the telindus1423Router/wanInterface/line/numDiscoveredRepeaters attribute.

disabled 1



496

MR-4.7 SHDSL line pair alarms

This section describes the alarms of the alarm attribute telindus1423Router/wanInterface/line/linePair[ ]/alarmInfo.


telindus1423Router/wanInterface/line/linePair[ ]/alarmInfo

The alarms related to the linePair[ ] object together with their explanation and default alarmMask and alarmLevel value are given in the following table:



linkDown when the line pair is down. I.e. no data can be transmit-ted over the line pair.

disabled 3

lineAttenuation when the line attenuation exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds for at least 10 seconds. The alarm is cleared when the line attenuation drops below this value for at least 10 seconds.

Note that in case the telindus1423Router/wanInterface/line/eocHandling attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/lineAttenuation as configured on the central device.

For more information, refer to …

• MU-5.4.3 - Contrôle d’échange de messages EOC standard on page 80

• MU-5.4.4 - eocHandlingQuelles informations EOC standard sont-elles récupérées ? on page 82

disabled 1

signalNoise when the signal noise exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds for at least 10 seconds. The alarm is cleared when the sig-nal noise drops below this value for at least 10 seconds.

Note that in case the telindus1423Router/wanInterface/line/eocHandling attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/signalNoise as configured on the central device.




disabled 1



497

errSecRatioEx-ceeded

when the amount of erroneous seconds exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds within a 15 minutes period1. The alarm is cleared when the amount of erroneous seconds drops below this value within a 15 minutes period.

disabled 1

sevErrSecRatioEx-ceeded

when the amount of severely erroneous seconds exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds within a 15 minutes period1. The alarm is cleared when the amount of severely erroneous seconds drops below this value within a 15 minutes period.

disabled 2

bbErrRatioEx-ceeded

when the background block error ratio exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds configuration attribute within a 15 minute period1. The alarm is cleared when the back-ground block error ratio drops below this value within a 15 minute period.

disabled 1

1. The 15 minutes periods run synchronous with the 15 minutes periods of the telindus1423Router/wanInterface/line/h2Line performance attribute.Because alarms are raised or cleared within 15 minutes periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minutes period the errSecOn value is exceeded, then the errSecExceeded alarm is raised. The alarm stays on for the remainder of the 15 minutes period. The alarm is only cleared if also in the next 15 minutes period the errSecOn value is not exceeded.





498

MR-4.8 End and repeater alarms

This section describes the alarms of the alarm attribute telindus1423Router/wanInterface/end/linePair[ ]/alarmInfo. The repeater[ ] and end objects contain the same attributes, therefore only the alarms of the end object are described.


telindus1423Router/wanInterface/end/linePair[ ]/alarmInfo

The alarm related to the end/linePair[ ] object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



lineAttenuation when the lineAttenuation value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds of the local device is exceeded for at least 10 seconds. The alarm is cleared when the line attenuation drops below this value for at least 10 seconds.

Note however that in case the telindus1423Router/wanInter-face/line/eocHandling attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/lineAttenuation as configured on the central device.




disabled 1

signalNoise when the signalNoise value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds of the local device is exceeded for at least 10 seconds. The alarm is cleared when the signal noise drops below this value for at least 10 seconds.

Note however that in case the telindus1423Router/wanInter-face/line/eocHandling attribute is set to alarmConfiguration, the central SHDSL device forces the remote SHDSL device to use the linkAlarmThresholds/signalNoise as configured on the central device.




disabled 1



499

errSecRatioEx-ceeded

when the errSecOn value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds of the local device is exceeded within a 15 minutes period1. The alarm is cleared when the amount of erroneous sec-onds drops below this value within a 15 minutes period.

disabled 1

sevErrSecRatioEx-ceeded

when the sevErrSecOn value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds of the local device is exceeded within a 15 minutes period1. The alarm is cleared when the amount of severely erro-neous seconds drops below this value within a 15 min-utes period.

disabled 2

bbErrRatioEx-ceeded

when the background block error ratio exceeds the value configured in the telindus1423Router/wanInterface/line/linkAlarmThresholds configuration attribute within a 15 minute period1. The alarm is cleared when the back-ground block error ratio drops below this value within a 15 minute period.

disabled 1

1. The 15 minutes periods run synchronous with the 15 minutes periods of the telindus1423Router/wanInterface/line/h2Line performance attribute.Because alarms are raised or cleared within 15 minutes periods, there is a delay in the alarm status. For example, suppose that in the first minute of a 15 minutes period the errSecOn value is exceeded, then the errSecExceeded alarm is raised. The alarm stays on for the remainder of the 15 minutes period. The alarm is only cleared if also in the next 15 minutes period the errSecOn value is not exceeded.





500

MR-4.9 BRI alarms

This section describes the alarms of the alarm attribute telindus1423Router/bri[ ]/alarmInfo.


telindus1423Router/bri[ ]/alarmInfo

The alarms related to the bri[ ] object together with their explanation and default alarmMask and alarmLevel value are given in the following table:



linkDown when ISDN layer 1 is down, i.e. there is no physical con-nection between the BRI interface and the telecom oper-ator ISDN switch.

disabled 2

sucDialOut when a dial-out call is established successfully. disabled 1

sucDialIn when a dial-in call is established successfully. disabled 1

failDialOut when a dial-out call failed. This can be due to a problem on the dial-up interface itself (e.g. no physical connec-tion, no answer to a call, etc.) or an error situation in the encapsulation protocol.

disabled 2

failDialIn when a dial-in call failed. This can be due to a problem on the dial-up interface itself (e.g. no physical connec-tion, no answer to a call, etc.) or an error situation in the encapsulation protocol.

disabled 2



501

MR-4.10 B-channel alarms

This section describes the alarms of the alarm attribute telindus1423Router/bri[ ]/bChannel[ ]/alarmInfo.


telindus1423Router/bri[ ]/bChannel[ ]/alarmInfo

The alarm related to the bChannel[ ] object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



linkDown when ISDN layer 2 is down, i.e. the B-channel is down. disabled 2



502

MR-4.11 AUX alarms

This section describes the alarms of the alarm attribute telindus1423Router/aux/alarmInfo.


telindus1423Router/aux/alarmInfo

The alarms related to the aux object together with their explanation and default alarmMask and alarmLevel values are given in the following table:



linkDown when layer 1 is down. disabled 2

sucDialOut when a dial-out call is established successfully. disabled 1

sucDialIn when a dial-in call is established successfully. disabled 1

failDialOut when a dial-out call failed. This can be due to a problem on the dial-up interface itself (e.g. no physical connec-tion, no answer to a call, etc.) or an error situation in the encapsulation protocol.

disabled 2

failDialIn when a dial-in call failed. This can be due to a problem on the dial-up interface itself (e.g. no physical connec-tion, no answer to a call, etc.) or an error situation in the encapsulation protocol.

disabled 2



503

MR-4.12 Bundle alarms

This section describes the alarms of the alarm attribute telindus1423Router/bundle/xxxBundle[ ]/alarmInfo.


telindus1423Router/bundle/xxxBundle[ ]/alarmInfo

The alarm related to the xxxBundle[ ] object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



linkDown when all the bundle links in the bundle are down. enabled 3



504

MR-4.13 Router alarms

This section describes the alarms of the alarm attribute telindus1423Router/ip/router/alarmInfo.


telindus1423Router/ip/router/alarmInfo

The alarm related to the router object together with its explanation and default alarmMask and alarmLevel value is given in the following table:



pingActive when a ping is pending (for example, an indefinite ping).

This notification is necessary because you can only transmit one ping at a time. Furthermore, there is no pro-tection when a new ping is started before the previous is stopped.

enabled 3



505


User manual TMA sub-system picture

506

MR-5 TMA sub-system picture

The sub-system picture is a TMA tool that visualises the status information of the Telindus 1423 SHDSL Router. This chapter explains how to display the sub-system picture, and how to interpret the visual indi-cations.

How to display the sub-system picture?

To display the sub-system picture of the Telindus 1423 SHDSL Router, click on the sub-system picture button located in the TMA toolbar: .

Structure of the sub-system picture

This paragraph displays and labels the different elements of the sub-system picture. It also explains how the visual indications should be interpreted.

Below, the Telindus 1423 SHDSL Router sub-system picture is displayed:

The following table gives an overview of the sub-system picture elements and what they indicate:

Element Description

LEDs These reflect the actual status of the device.

The LED indication on the sub-system picture corresponds with the LED indication on the Telindus 1423 SHDSL Router itself. Refer to MU-2.7 - Témoins à DEL du panneau avant on page 24 for more information on the interpretation of the LEDs.

LAN This reflects the status of the LAN interface. The possible indications are:

• green. There is no alarm active in the corresponding lanInterface object.• red. An alarm is active in the corresponding lanInterface object.

The colour of the LAN interface only changes if the alarms related to the lanInterface object are set to enabled in the alarmMask.


User manual TMA sub-system picture

507

LINE This reflects the status of the WAN interface and of the line pair(s). The possible indications are:

• green outside. There is no alarm active in the corresponding wanInterface object.

• red outside. An alarm is active in the corresponding wanInterface object.

• green inside, left. There is no alarm active in the corresponding linePair[1] object.• red inside, left. An alarm is active in the corresponding linePair[1] object.• green inside, right. There is no alarm active in the corresponding linePair[2]

object.• red inside, right. An alarm is active in the corresponding linePair[2] object.

The colours of the WAN interface / line pair(s) only change if the alarms related to the wanInterface / linePair[ ] objects are set to enabled in the alarm-Mask.

Element Description


User manual Auto installing the Telindus 1423 SHDSL Router

508

MR-6 Auto installing the Telindus 1423 SHDSL Router

Auto-install includes a number of features that allow you to partially or completely configure the Telindus 1423 SHDSL Router without on-site intervention. This is shown in this chapter.


• MR-6.1 - Introducing the auto-install protocols on page 509• MR-6.2 - Auto-install on the LAN interface on page 511• MR-6.3 - Auto-install on the WAN interface on page 516• MR-6.4 - Creating a configuration file on page 523• MR-6.5 - Restoring a configuration file on page 530



509

MR-6.1 Introducing the auto-install protocols

The Telindus 1423 SHDSL Router uses several protocols during its auto-install sequence. These are introduced below.

What is BootP?

BootP (RFC 951) is used by IP devices that have no IP address to obtain one.

The client IP device sends a limited broadcast request on its interfaces requesting an IP address. The request contains the client its MAC address, which is a unique identifier (refer to What is the ARP cache? on page 22 for more information).

A workstation with a BootP server interprets incoming BootP requests. You can configure a file on the server with MAC address and IP address/subnet mask pairs for all devices in the network you want to service. If the MAC address in the BootP request matches a MAC address in this file, the BootP server replies with the corresponding IP address and subnet mask.

Assigning an IP address in this way is done through a simple request - response handshake.

The Telindus 1423 SHDSL Router, being a router, always requests a static IP address.

What is DHCP?

DHCP (RFC 2131 and RFC 2132) is used by IP devices that have no IP address to obtain one.

The client IP device sends a limited broadcast request on its interfaces requesting an IP address. The request contains the client its MAC address, which is a unique identifier (refer to What is the ARP cache? on page 22 for more information).

A workstation with a DHCP server works in a similar way as with a BootP server. The difference with BootP is that you can additionally configure a list of IP addresses on the server. These IP addresses are dynamically assigned to the IP devices requesting an IP address, independently of their MAC address. Those address assignments are limited in time.

Assigning an IP address in this way is done through a 4-way handshake and with regular renewals.

The Telindus 1423 SHDSL Router, being a router, always requests a static IP address.

What is DNS?

The Domain Name Service (DNS) is an Internet service that translates domain names into IP addresses. Because domain names are alphabetic, they are easier to remember. The Internet however, is really based on IP addresses. Therefore, every time you use a domain name, a DNS service must translate the name into the corresponding IP address. For example, the domain name www.mywebsite.com might translate to 198.105.232.4.

The DNS system is, in fact, its own network. If one DNS server doesn't know how to translate a particular domain name, it asks another one, and so on, until the correct IP address is returned.



510

What is TFTP?

Trivial File Transfer Protocol (TFTP) is an Internet software utility for transferring files that is simpler to use than the File Transfer Protocol (FTP) but less capable. It is used where user authentication and directory visibility are not required. TFTP uses the User Datagram Protocol (UDP) rather than the Trans-mission Control Protocol (TCP). TFTP is described formally in Request for Comments (RFC) 1350.

TFTP is typically used in combination with BootP or DHCP to obtain the configuration of a device from a TFTP server. The configuration file on this TFTP can be in a binary or an ASCII (CLI) format. How to build such files is explained in MR-6.4 - Creating a configuration file on page 523.

The Telindus 1423 SHDSL Router as relay agent

Being broadcast packets, BootP, DHCP, DNS and TFTP requests can cross a router using IP helper addresses. The Telindus 1423 SHDSL Router is a relay agent for these protocols. This means it adds additional information to the request packets allowing servers on distant networks to send back the answer.



511

MR-6.2 Auto-install on the LAN interface

This section shows the auto-install sequence on the Telindus 1423 SHDSL Router its LAN interface.


• MR-6.2.1 - Set-up for auto-install on the LAN interface on page 512• MR-6.2.2 - Auto-install in case of Ethernet on page 513• MR-6.2.3 - Example of auto-install on the LAN interface on page 514



512

MR-6.2.1 Set-up for auto-install on the LAN interface

The following figure shows the set-up for auto-install on the LAN interface:



513

MR-6.2.2 Auto-install in case of Ethernet



514

MR-6.2.3 Example of auto-install on the LAN interface

Suppose you have the following situation:

• The Telindus 1423 SHDSL Router is still in its default configuration (absolutely nothing is configured). This means that the LAN interface …- is in bridging mode.- no IP address is configured on the LAN interface.- no IP address is configured on the bridge group.⇒This means that if an IP address is obtained through BootP/DHCP, then it will be assigned to the

bridge group, not to the LAN interface itself (since it is in bridging mode)!

• A BootP server is present on the LAN, containing the Telindus 1423 SHDSL Router MAC address (00:C0:89:00:94:6F) and a corresponding IP address (192.168.47.1).

• A DNS server is present on the LAN, containing the Telindus 1423 SHDSL Router its hostname “TlsRouter“.

• A TFTP server is present on the LAN, containing the Telindus 1423 SHDSL Router its binary config-uration file “TlsRouter.cms”.

• The Telindus 1423 SHDSL Router is plugged on to the LAN.



515

The following shows how the Telindus 1423 SHDSL Router obtains an IP address and its configuration file:

Note again that the obtained IP address is assigned to the bridge group, not to the LAN interface itself (since it is in bridging mode)! So if you check the status of the bridge group, you will see the IP address there:



516

MR-6.3 Auto-install on the WAN interface

This section shows the auto-install sequence on the Telindus 1423 SHDSL Router its WAN interface.


• MR-6.3.1 - Set-up for auto-install on the WAN interface on page 517• MR-6.3.2 - Auto-install in case of ATM on page 518• MR-6.3.3 - Auto-install in case of Frame-Relay on page 519• MR-6.3.4 - Example of auto-install on the WAN interface running ATM on page 520



517

MR-6.3.1 Set-up for auto-install on the WAN interface

The following figure shows the set-up for auto-install on the WAN interface:



518

MR-6.3.2 Auto-install in case of ATM



519

MR-6.3.3 Auto-install in case of Frame-Relay



520

MR-6.3.4 Example of auto-install on the WAN interface running ATM

Suppose you have the following situation:

• On the local OneAccess Router you add an ATM PVC to the atm/pvcTable. For this ATM PVC you spec-ify the VPI/VCI values 1/100. All other elements of the ATM PVC remain at their default value.

• On the central OneAccess Router you also add an ATM PVC to the atm/pvcTable. For this ATM PVC you specify …- the VPI/VCI values 1/100.- the helper IP addresses 192.168.47.251 (DHCP server) and 192.168.47.252 (TFTP server).- the helper protocols DHCP (68) and TFTP (69).

• A DHCP server is present on the remote network, containing the Telindus 1423 SHDSL Router MAC address (00:C0:89:00:94:6F), a corresponding IP address (192.168.100.1) and a corresponding con-figuration filename “TlsRouterConfig.cms”.

• A TFTP server is present on the remote network, containing the Telindus 1423 SHDSL Router its binary configuration file “TlsRouterConfig.cms”.

• The OneAccess Router is plugged on to the WAN.

So the initial configuration on the local OneAccess Router is as shown below:



521

In order for the auto-install of the local OneAccess Router to be successful, the following must be con-figured on the central OneAccess Router:



522

The following shows how the local OneAccess Router obtains an IP address and its configuration file:



523

MR-6.4 Creating a configuration file

In MR-6.2 - Auto-install on the LAN interface on page 511 and MR-6.3 - Auto-install on the WAN inter-face on page 516, you can see how the configuration file is retrieved using TFTP during the auto-install sequence. This section explains which two configuration file formats can be used for this purpose and how to create such a configuration file.


• MR-6.4.1 - The different configuration file formats on page 524• MR-6.4.2 - Creating a binary file using TMA on page 525• MR-6.4.3 - Creating an ASCII CLI file using TMA on page 526• MR-6.4.4 - Creating an ASCII CLI file using TFTP on page 528• MR-6.4.5 - Creating an ASCII CLI file using Telnet on page 529



524

MR-6.4.1 The different configuration file formats

In MR-6.2 - Auto-install on the LAN interface on page 511 and MR-6.3 - Auto-install on the WAN inter-face on page 516, you can see how the configuration file is retrieved using TFTP during the auto-install sequence. The two possible configuration file formats used for this purpose are:

File type Extension How to create the configuration file

binary .cms Use the TMA export utility and choose the CMS file type. This is the most compact format.

Refer to MR-6.4.2 - Creating a binary file using TMA on page 525.

ASCII CLI .cli • Use the TMA export utility and choose the CLI file type.• Use the TFTP get command.• Use the CLI get command.

Refer to …

• MR-6.4.3 - Creating an ASCII CLI file using TMA on page 526

• MR-6.4.4 - Creating an ASCII CLI file using TFTP on page 528

• MR-6.4.5 - Creating an ASCII CLI file using Telnet on page 529

When you download an ASCII CLI (*.cli) configuration file to the Telindus 1423 SHDSL Router, make sure that each line in this file contains no more than 500 charac-

ters.



525

MR-6.4.2 Creating a binary file using TMA

To create a configuration file in binary (*.cms) format using TMA, proceed as follows:

Step Action

1 Start a TMA session on the Telindus 1423 SHDSL Router.

2 Make changes to its configuration (if necessary) in order to obtain the desired configura-tion.

3 Click on the Export data to file button: .

4 In the Export configuration parameters window, select the following:

• Choose a directory where to save the file.• Enter a name for the file.• Make sure the file type is CMS.• Make sure the Full configuration option is selected.

5 Click on the Save button.

The edited configuration of the Telindus 1423 SHDSL Router is stored on the PC in binary format. The file contains the complete configuration including the Activate Config-uration command. As a result, the configuration is immediately activated if you download it to the device again.



526

MR-6.4.3 Creating an ASCII CLI file using TMA

To create a configuration file in ASCII CLI (*.cli) format using TMA, proceed as follows:

Step Action


2 Make changes to its configuration (if necessary) in order to obtain the desired configura-tion.

3 Click on the Export data to file button: .

4 In the Export configuration parameters window, select the following:

• Choose a directory where to save the file.• Enter a name for the file.• Make sure the file type is CLI.• Make sure the Full configuration option is selected.

Do not select the file extension for ASCII text (*.txt)! This is for documentation pur-poses only, not for configuration purposes.



527

5 Click on the Save button.

⇒The edited configuration of the Telindus 1423 SHDSL Router is stored on the PC in ASCII CLI format. The file contains the configuration attributes that differ from their default value including the Load Default Configuration command at the begin-ning of the file and the Activate Configuration command at the end of the file. As a result, the configuration is immediately activated if you download it to the device again.

Step Action



528

MR-6.4.4 Creating an ASCII CLI file using TFTP

To create a configuration file in ASCII CLI (*.cli) format using TFTP, proceed as follows:

Note that the procedure described above does not work with FTP.

Step Action

1 Start a TFTP session on the Telindus 1423 SHDSL Router.

For example by typing tftp 10.0.11.1 at the command prompt of your workstation, where 10.0.11.1 is the IP address of the Telindus 1423 SHDSL Router.

2 Get the configuration file of the Telindus 1423 SHDSL Router.

Example

tftp> get CONFIG.CLI dest_file.cli

Where …

• get is the TFTP command to retrieve a file.• CONFIG.CLI (in capitals!) is the source file (i.e. the Telindus 1423 SHDSL Router con-

figuration file).• dest_file.cli is the destination file.

3 When the file transfer is finished, close the TFTP session.



529

MR-6.4.5 Creating an ASCII CLI file using Telnet

To create a configuration file in ASCII CLI (*.cli) format using Telnet logging and the CLI get command, proceed as follows:

Step Action

1 Start a Telnet session on the Telindus 1423 SHDSL Router. You are automatically in CLI mode.

2 You are automatically located in the top object (telindus1423Router) and in the "Edit Config-uration" group. Check to make sure (just press the Enter key).

3 Log the CLI output to a file. Refer to the documentation of your Telnet software how to do so.

4 Execute the get -r -d command.

>get -r -d

5 Stop the logging.

6 The log file you now obtained, modify it as follows:

• At the beginning of the log file …- remove all logging before the get -r -d command.- remove the get -r -d command itself.- change the string GET into SET.- type the string action “Load Default Configuration” (case sensitive!) on the line

above the SET command.• At the end of the log file…

- remove all logging until the last character is a closing curled bracket “}”.- type the string action “Activate Configuration” (case sensitive!) on the line below

the closing curled bracket “}”.

7 Save this file to a file with an extension *.cli.



530

MR-6.5 Restoring a configuration file

In MR-6.2 - Auto-install on the LAN interface on page 511 and MR-6.3 - Auto-install on the WAN inter-face on page 516, you can see how the configuration file is retrieved using TFTP during the auto-install sequence. It is, however, also possible to restore previously saved configuration files by downloading them yourself to the Telindus 1423 SHDSL Router. You can do this by using various applications. This is explained in this section.


• MR-6.5.1 - Downloading a configuration file using TMA on page 531• MR-6.5.2 - Downloading a configuration file using (T)FTP on page 532• MR-6.5.3 - Downloading a configuration file using Telnet on page 533



531

MR-6.5.1 Downloading a configuration file using TMA

To download a configuration file using TMA, proceed as follows:

Step Action


2 Click on the Import data from file button: .

3 In the Import configuration window, select the following:

• Select the directory where the configuration file is located.• Select which type of configuration file you want to import: CMS or CLI.• Select the configuration file you want to import.

4 Click on the Open button.

⇒The configuration is downloaded to the Telindus 1423 SHDSL Router.



532

MR-6.5.2 Downloading a configuration file using (T)FTP

To download a configuration file using (T)FTP, proceed as follows:

Step Action

1 Start a (T)FTP session on the Telindus 1423 SHDSL Router.

For example by typing (t)ftp 10.0.11.1 at the command prompt of your computer, where 10.0.11.1 is the IP address of the Telindus 1423 SHDSL Router. If a write access password is configured on the Telindus 1423 SHDSL Router, then enter it as well.

2 Set the transfer mode to binary (octet) format. The syntax to do this is typically binary or octet.

3 Type the following command:

(t)ftp> put source_file.cli CONFIG.CLI

or(t)ftp> put source_file.cms CONFIG.CMS

Where …

• put is the (T)FTP command to send a file.• source_file.* is the source file. This may either be a CLI or CMS file1.• CONFIG.* (in capitals!) is the destination file (i.e. the Telindus 1423 SHDSL Router

configuration file). This may either be a CLI or CMS file1.

1. However, make sure that source and destination file format are both the same!

4 When the file transfer is finished, close the (T)FTP session.



533

MR-6.5.3 Downloading a configuration file using Telnet

To download a configuration file using Telnet, proceed as follows:

Step Action

1 Start a Telnet session on the Telindus 1423 SHDSL Router. You are automatically in CLI mode.

2 You are automatically located in the top object (telindus1423Router) and in the "Edit Config-uration" group. Check to make sure (just press the Enter key).

3 Use the “send” feature of your Telnet software to send the ASCII CLI configuration file to the Telindus 1423 SHDSL Router. Refer to the documentation of your Telnet software how to do so.


User manual Downloading software

534

MR-7 Downloading software

This chapter explains how to download application software to the Telindus 1423 SHDSL Router. It also shows how to download any other file to the file system of the Telindus 1423 SHDSL Router. But first it explains the difference between boot and application software.


• MR-7.1 - What is boot and application software? on page 535• MR-7.2 - Downloading application software using TMA on page 536• MR-7.3 - Downloading application software using TFTP on page 537• MR-7.4 - Downloading application software using TML on page 538• MR-7.5 - Downloading application software using FTP on page 539• MR-7.6 - Downloading application software in boot mode on page 540• MR-7.7 - Downloading files to the file system on page 541



535

MR-7.1 What is boot and application software?

What is boot software?

The boot software takes care of the initial phase in the start-up sequence of the Telindus 1423 SHDSL Router. It is located on the lowest software level. If the Telindus 1423 SHDSL Router only loads its boot software, then we say that the Telindus 1423 SHDSL Router runs in boot mode.

The Telindus 1423 SHDSL Router …

• runs in boot mode if no application software is present.• can be forced to run in boot mode by using a DIP switch. This may be necessary in case a software

download failed or a flash memory error occurred making the Telindus 1423 SHDSL Router inacces-sible or even inoperative. Refer to MR-7.6 - Downloading application software in boot mode on page 540.

• can temporarily be forced to run in boot mode by using the -b option of the TML command. Refer to MR-7.4 - Downloading application software using TML on page 538.

In boot mode …

• you can download application software (using TML).• you cannot establish a TMA session. You can only use TML to download application software.

What is application software

The application software, also called control software or firmware, completely controls the Telindus 1423 SHDSL Router. It is located on the highest software level. If the Telindus 1423 SHDSL Router loads its boot, loader and application software, then we say that the Telindus 1423 SHDSL Router runs in appli-cation mode.

In application mode …

• you can download application software (using TMA, TFTP or TML).• you can establish a TMA session.



536

MR-7.2 Downloading application software using TMA

To download application software to the Telindus 1423 SHDSL Router using TMA, proceed as follows:

Step Action

1 Establish a link between TMA and the Telindus 1423 SHDSL Router either over a serial or an IP connection. Refer to MU-4 - Maintenance du Routeur Telindus 1423 SHDSL on page 35.

2 In the TMA window select Tools → Download…

3 In case you made …

• an IP connection, skip this step.• a serial connection, select the Options tab in

the TMA - Download window. Then set the following:- Set the initial transfer speed to 9600 bps.- Select a maximum transfer speed. If you

select e.g. 57600 bps, then the actual transfer speed will be negotiated between 9600 bps and 57600 bps.

4 In the TMA - Download window, select the Configuration tab and click on Add…

5 In the Remote filename window, do the following:

1. Select the file you want to download (e.g. T1234001.00).

2. Type CONTROL in the Remote file field.

3. Click on Open.

6 If you are currently connected to the Telindus 1423 SHDSL Router without write access, then you can enter a password in the Password tab which gives you write access. Else leave the Password tab blank.

7 When the TMA - Download window reappears, click on OK.

⇒A window opens and shows the download progress.



537

MR-7.3 Downloading application software using TFTP

When downloading with TMA over an IP connection, you actually evoke TFTP (Trivial File Transfer Pro-tocol) through TMA. You can also use TFTP without opening TMA.

To download application software to the Telindus 1423 SHDSL Router using TFTP, proceed as follows:

Step Action

1 Start a TFTP session on the Telindus 1423 SHDSL Router.

For example by typing tftp 10.0.11.1 at the command prompt of your computer, where 10.0.11.1 is the LAN IP address of the Telindus 1423 SHDSL Router. If a write access password is configured on the Telindus 1423 SHDSL Router, you can either enter it now or when you actually download the application software (see step 3).

2 Set the following TFTP parameters:

• Set the retransmission time-out to at least 20 seconds. The syntax to do this is typi-cally rexmt 20.

• Set the total TFTP time-out sufficiently large (e.g. 40 seconds). The syntax to do this is typically timeout 40.

• Set the transfer mode to binary (octet) format. The syntax to do this is typically binary or octet.


tftp> put Txxxxxxx.00 CONTROL?my_pwd

Where …

• put is the TFTP command to send a file.• Txxxxxxx.00 is the application software file (e.g. T1234001.00).• CONTROL (in capitals!) specifies that the file being downloaded is an application soft-

ware file.• ?my_pwd is the write access password as configured in the Telindus 1423 SHDSL

Router. If no password has been configured or if you already entered one when start-ing the TFTP session (see step 1), you may omit the ? and the password.

4 When the file transfer is finished, close the TFTP session.



538

MR-7.4 Downloading application software using TML

When downloading with TMA over a serial connection, you actually evoke TML (OneAccess Memory Loader) through TMA. You can also use TML without opening TMA.

To download application software to the Telindus 1423 SHDSL Router using TML, proceed as follows:

Step Action

1 Connect a serial port of your com-puter (e.g. COM1) through a straight DB9 male - female cable with the control connector of the Telindus 1423 SHDSL Router.

2 Open a DOS window on your computer.

3 Go to the directory where the TML executable is located. Typically this is C:\Program Files\TMA.

4 Place the software file you want to download in this directory.

5 Type the following command to download application software:

tml -c1 -v -fTxxxxxxx.00@CONTROL?my_pwd

where …

• tml is the executable (OneAccess Memory Loader) to download files to the OneAc-cess devices through their control port.

• -c1 specifies the COM port of the computer connected to the Telindus 1423 SHDSL Router (in this example COM1).

• -v returns graphical information on the download status.• -fTxxxxxxx.00 is the software file you want to download (e.g. T1234001.00).• CONTROL (in capitals!) specifies that the file being downloaded is an application or

loader software file.• ?my_pwd is the write access password as configured in the Telindus 1423 SHDSL

Router. If no password has been configured, you may omit the ? and the password.

To see a list of all the possible TML options: type TML in your DOS windows and press the ENTER key.

6 If you press the ENTER key, the software download begins.

If you used the -v option together with the TML command, a graphical bar shows the download progress.



539

MR-7.5 Downloading application software using FTP

To download application software to the Telindus 1423 SHDSL Router using FTP, proceed as follows:

Step Action

1 Start an FTP session on the Telindus 1423 SHDSL Router.

For example by typing ftp 10.0.11.1 at the command prompt of your computer, where 10.0.11.1 is the LAN IP address of the Telindus 1423 SHDSL Router. If a write access password is configured on the Telindus 1423 SHDSL Router, you can either enter it now or when you actually download the application software (see step 3).

2 Make sure the transfer mode is set to binary (octet) format. The syntax to do this is typi-cally binary.


ftp> put Txxxxxxx.00 CONTROL?my_pwd

Where …

• put is the FTP command to send a file.• Txxxxxxx.00 is the application software file (e.g. T1234001.00).• CONTROL (in capitals!) specifies that the file being downloaded is an application soft-

ware file.• ?my_pwd is the write access password as configured in the Telindus 1423 SHDSL

Router. If no password has been configured or if you already entered one when start-ing the FTP session (see step 1), you may omit the ? and the password.

4 When the file transfer is finished, close the FTP session.



540

MR-7.6 Downloading application software in boot mode

When a software download failed or when a flash memory error occurs, it may be possible that the Tel-indus 1423 SHDSL Router becomes inaccessible or even inoperative. In that case, new software can still be downloaded by forcing the Telindus 1423 SHDSL Router in loader mode. Do this by means of the Boot mode DIP switch. Refer to MU-3.2 - Commutateurs DIP du Routeur Telindus 1423 SHDSL on page 31.

To download loader or application software to a Telindus 1423 SHDSL Router in loader mode, proceed as follows:

Step Action

1 Disconnect the power supply and open the housing as described in MU-3.4 - Ouverture et fermeture du boîtier on page 33.

2 Set the Boot mode DIP switch to off.

Refer to MU-3.1 - La carte mère du Routeur Telindus 1423 SHDSL on page 30 to locate this DIP switch.

3 Replace the cover without fastening the screws and reconnect the power supply.

⇒The Telindus 1423 SHDSL Router reboots in boot mode.

4 Now proceed as explained in the previous section, MR-7.4 - Downloading application software using TML on page 538.

5 When the software download is finished, again disconnect the power supply and open the housing.

6 Reset the Boot mode DIP switch to on.

7 Properly replace the cover as described in MU-3.4 - Ouverture et fermeture du boîtier on page 33 and reconnect the power supply.



541

MR-7.7 Downloading files to the file system

You might want to download other files than the firmware files only. In fact, any file can be downloaded to the file system of the Telindus 1423 SHDSL Router. You can do this using the same tools you use to download application software. These tools are:

• TMA (refer to MR-7.2 - Downloading application software using TMA on page 536).• TFTP (refer to MR-7.3 - Downloading application software using TFTP on page 537).• TML (refer to MR-7.4 - Downloading application software using TML on page 538).• FTP (refer to MR-7.5 - Downloading application software using FTP on page 539).

The major difference is that instead of specifying CONTROL as target filename for the application software, you now can specify any filename as target filename.

Tool Example

TMA In the Remote filename window, do the following:

1. Select the file you want to download (e.g. sdsltt.mod).

2. Type the target filename in the Remote file field (e.g. sdsltt.mod).

3. Click on Open.

(T)FTP and TML • tftp> put filename1.ext filename2.ext?my_pwd

• ftp> put filename1.ext filename2.ext?my_pwd

• tml -c1 -v [email protected]?my_pwd

Where …

• filename1.ext is the source filename. This is a file on your computer.• filename2.ext is the target filename. This is the filename the source file will

get when it is placed on the file system. Source and target filename may be the same, but if wanted, you may specify a different target filename.

Example:

• tftp> put models.nms models.nms?pwd123

• tml -c1 -v [email protected]?pwd123


User manual Technical specifications

542

MR-8 Technical specifications

This chapter gives the technical specifications of the Telindus 1423 SHDSL Router. The following gives an overview of this chapter:

• MR-8.1 - SHDSL line specifications on page 543• MR-8.2 - Basic Rate ISDN interface specifications on page 545• MR-8.3 - LAN interface specifications on page 546• MR-8.4 - 4 port Ethernet switch specifications on page 546• MR-8.5 - Control connector specifications on page 547• MR-8.6 - IP address assignment and auto-provisioning on page 548• MR-8.7 - ATM encapsulation specifications on page 549• MR-8.8 - Frame Relay encapsulation specifications on page 550• MR-8.9 - PPP encapsulation specifications on page 550• MR-8.10 - Other WAN encapsulation specifications on page 550• MR-8.11 - IP routing specifications on page 551• MR-8.12 - Bridging specifications on page 553• MR-8.13 - Network address translation specifications on page 554• MR-8.14 - Tunnelling and VPN specifications on page 555• MR-8.15 - Priority and traffic policy specifications on page 556• MR-8.16 - Routing and bridging performance specifications on page 558• MR-8.17 - Firewall specifications on page 558• MR-8.18 - Access security specifications on page 559• MR-8.19 - Maintenance and management specifications on page 559• MR-8.20 - Memory specifications on page 560• MR-8.21 - Power requirements on page 560• MR-8.22 - Dimensions on page 560• MR-8.23 - Safety compliance on page 561• MR-8.24 - Over-voltage and over-current protection compliance on page 561• MR-8.25 - EMC compliance on page 561• MR-8.26 - Environmental compliance on page 561



543

MR-8.1 SHDSL line specifications

• Single pair or dual pair line access• Connector: RJ45• Impedance: 135 ohm• Cable to be used: 2*2*CAT5E twisted pair• Coding: TC PAM, compliant to ITU-T G.991.2 (G.SHDSL)• Line speeds:

- Single pair: N x 64 kbps (N = 1 … 36)- Two pair: N x 128 kbps (N = 1 … 36)

• Handshaking: compliant G.994.1 (automatic speed negotiation) or fixed speed• Performance monitoring: compliant G.826 (errored seconds, severely errored seconds, unavailability

seconds)• Encapsulation: ATM, Frame Relay, PPP, HDLC (Note that not all encapsulation protocols are present

on all Telindus 1423 SHDSL Router versions.)

The line connector lay-out

The following table shows the connector layout of the RJ45 line connector:

Pin Signal Figure

1 not used

2 cable shield (optional)

3 line 21

1. For a Telindus 1423 SHDSL Router 2 pair version only.

4 line 1

5 line 1

6 line 21

7 cable shield (optional)

8 not used



544

Maximum covered distance

The following table gives the maximum covered distance over a noise-free line:

• These values are valid for all hardware and firmware revisions. Also note that these values are only valid when using the correct, properly twisted cable.

• A Signal to Noise ratio of 23dB matches a Noise Margin of 0dB. A Noise Margin of minimum 2dB is considered a minimum for an Error Ratio that matches at least 10E-7 (= a Signal to Noise ratio of 25dB). In performance tests with noise, usually a noise margin of 6dB is taken (= a Signal to Noise ratio of 29dB). Tests show that a Signal to Noise ratio of 27dB gives no errors and that at a Signal to Noise ratio of 25dB errors are rare.

Covered distance (km)

Line speed (kbps) Wire diameter (mm)

1 Pair 2 Pair 0.4 0.5 0.6 0.8 1.0 1.2

64 128 11,0 15,1 21,5 27,2 38,2 42,4

128 256 8,0 11,0 15,6 19,8 27,8 30,8

256 512 8,2 11,3 16,0 20,3 28,5 31,6

512 1024 7,2 9,9 14,0 17,8 25,0 27,7

1024 2048 5,5 7,6 10,7 13,6 19,1 21,2

1536 3072 4,0 5,5 7,8 9,9 13,9 15,4

2048 4096 4,2 5,8 8,2 10,4 14,6 16,2

2304 4608 4,0 5,5 7,8 9,9 13,9 15,4



545

MR-8.2 Basic Rate ISDN interface specifications

• Connector: RJ45 (DTE)• Impedance: 100 ohm or high impedance (DIP switch selectable)• Cable to be used: 4*2*CAT5E shielded twisted pair• ISDN type: Basic Rate• WAN encapsulation: in case of a …

- dial-up connection: PPP- leased line connection: PPP, Frame Relay, HDLC

• Basic Rate ISDN interface compliance: ITU-T I.420. This includes the following recommendations:- I.412: ISDN user-network interfaces - Interface structures and access capabilities- I.430: Basic user-network interface - Layer 1 specification- I.440 (= Q.920): ISDN user-network interface data link layer – General aspects- ETS 300 125 (≅ Q.921): ISDN user-network interface – Data link layer specification- I.450 (= Q.930): ISDN user-network interface layer 3 – General aspects- ETS 300 102 (≅ Q.931): ISDN user-network interface layer 3 specification for basic call control- I.452 (= Q.932): Digital Subscriber Signalling System No. 1 – Generic procedures for the control

of ISDN supplementary servicesNote that the supplementary services in I.452 are not supported.

• ISDN callback compliance: PPP LCP callback extension as defined in RFC 1570 (support of options 0, 1 and 3).

The following table shows the connector layout of the ISDN BRI interface connector:

Pin Signal DTE Figure

1 not connected -

2 not connected -

3 transmit A (+) output

4 receive A (+) input

5 receive B (-) input

6 transmit B (-) output

7 not connected -

8 not connected -



546

MR-8.3 LAN interface specifications

• Connector: RJ45 (EIA/TIA 568B)• Cable to be used: 4*2*CAT5E unshielded twisted pair• Applicable standards: IEEE 802.3 (10Mbps Ethernet), IEEE 802.3u (100Mbps Ethernet)• Speed: 10 / 100 Mbps auto-sense• VLAN support (up to 12 VLANs)

The following table shows the connector layout of the RJ45 Ethernet LAN interface connector:

MR-8.4 4 port Ethernet switch specifications

• Number of ports: 4• Connectors: RJ45 (EIA/TIA 568B)• Cable to be used: 4*2*CAT5E unshielded twisted pair• Applicable standards: IEEE 802.3 (10Mbps Ethernet), IEEE 802.3u (100Mbps Ethernet)• Speed: 10 / 100 Mbps auto-sense• VLAN support:

- maximum 16 VLANs- VLAN tagging per port- tagged, untagged or trunking VLAN operation

Pin Signal I/O Figure

1 transmit (+) output

2 transmit (-) output

3 receive (+) input

4 not used -

5 not used -

6 receive (-) input

7 not used -

8 not used -



547

MR-8.5 Control connector specifications

• Connector: female DB9 labelled CTRL• Applicable standards: ITU-T V.24, V.28, EIA/TIA 574• Data:

- asynchronous- 9600 bps- 8 data bits- no parity- 1 stop bit- no flow control

The control connector has the following pin layout:

Pin Signal DCE Figure

1 not used - -

2 Receive Data RxD output

3 Transmit Data TxD input

4 not used - -

5 GND GND -

6 not used - -

7 not used - -

8 not used - -

9 not used - -



548

MR-8.6 IP address assignment and auto-provisioning

• BOOTP/DHCP server (RFC 2131, RFC 2132) with static or dynamic address assignment• DHCP server major features:

- IP address ranges are configurable per interface- If no gateway is configured in the DHCP server, the router gives its own address- The DHCP server collects the DNS names of all DHCP clients and acts as a local DNS server for

these names• DHCP relay agent (RFC 2131, RFC 2132)• DNS proxy• Static IP address assignment• Possible assignment of secondary IP address on the LAN interface• Numbered or unnumbered mode on WAN interfaces• Automatic IP address assignment through:

- BootP client (RFC 951)- DHCP client (RFC 2131, RFC 2132)- IPCP

• Automatic IP gateway assignment through Inverse ARP (RFC 2390, in Frame-Relay and ATM)• Automatic default route assignment on remotely learned IP address in PPP• Automatic configuration file upload through DHCP client• DHCP client requests are transmitted if an interface is in routing mode and has no IP address yet• DHCP client requests can be blocked from being transmitted on the LAN interface and bridge groups



549

MR-8.7 ATM encapsulation specifications

• ATM cell format ITU-T I.311, I.321, I.361, I.432• ATM forum UNI 3.1/4.0 PVCs• ATM forum ILMI 3.1/4.0• OAM F4/F5 LB and CC support (ITU-T I.610)• Inverse ARP for automatic gateway configuration• ATM Forum Traffic Management 4.0 service type UBR, VBR and CBR• PCR, SCR and MBS configurable per ATM PVC• Support of up to 31 ATM PVCs• ATM VPI range 0 - 255• ATM VCI range 32 - 10000• Supported higher layer protocols:

- Classical IP (RFC 1577)- Ethernet (RFC 2684)- PPPoA (RFC 2364)- PPPoE (RFC 2516)

• Multi-protocol encapsulation:- LLC- VC



550

MR-8.8 Frame Relay encapsulation specifications

• Encapsulation compliant with RFC 1490, RFC 2427• LMI (revision 1 LMI, ANSI T1.617 D, ITU-T Q.933 Annex A and FRF 1&2)• CIR configurable per DLCI• EIR configurable per DLCI• Inverse ARP for automatic gateway configuration• Support of up to 40 Frame Relay PVCs (DLCIs)• Frame Relay DLCI range 16 - 1022• Multi-link Frame Relay (FRF.16)• Frame Relay fragmentation (FRF.12)

MR-8.9 PPP encapsulation specifications

• Encapsulation compliant with RFC 1661, RFC 1662• LCP• IPCP (RFC 1332)• BCP (RFC 2878)• CCP (RFC 1962) with Predictor compression algorithm (RFC 1978)• PAP authentication (RFC 1334), unidirectional or bi-directional authentication• CHAP authentication with MD5 hashing (RFC 1994), unidirectional or bi-directional authentication• MS-CHAP1 (RFC 2433) and MS-CHAP2 (RFC 2759) CHAP authentication protocol extension• MLPPP (RFC 1990)• MLPPP bundle name exchange• PPP fragmentation (RFC 1990), enabled to fixed size of 200 bytes or disabled• MCPPP (RFC 2686)

MR-8.10 Other WAN encapsulation specifications

• HDLC encapsulation in bridging mode (not interoperable with Cisco HDLC encapsulation)• Error test encapsulation for end-to-end error tests over TDM networks between OneAccess devices• Leased line operation on ISDN BRI interfaces (aka Standard FestVerbindung (SFV))



551

MR-8.11 IP routing specifications

The Telindus 1423 SHDSL Router complies to the router requirements as stated in RFC 1812 and sup-ports the routing of standard IP packets (RFC 791) between the different interfaces of the Telindus 1423 SHDSL Router according to the routing protocols listed below.

Static routing

• Routing is based on destination IP address• Routing is based on static routing entries in the routing table• Alternate routing is possible through the use of different preferences for different routes to the same

destination

Policy based routing

• Routing is based on additional higher layer information• Traffic is routed to a certain interface or gateway based on one or more of the following parameters:

- Source IP address range- Destination IP address range- Type Of Service (TOS) value range (8 bits in the IP header, also called DSCP bits)- IP protocol (examples are any (0), ICMP (1), IGMP (2), TCP (6), UDP (17))- Source port range for UDP / TCP packets- Destination port range for UDP / TCP packets

RIP

• RIP1 compliant with RFC 1058• RIP2 compliant with RFC 2453• Split horizon and selective router updates per interface• Broadcasting of selective RIP updates limited to information on specific network subnets• RIP2 authentication with MD5 hashing or clear text• Triggered RIP for ISDN interfaces

OSPF

• Compliant with RFC 2328 (OSPF version 2)• Import of statically configured routes• Route summarisation and route suppression through range definitions on areas• Encryption through simple password or MD5 encryption chains

ICMP

Support of ICMP messages (RFC 792):

• TTL exceeded• Destination unreachable



552

Multicasting and broadcasting

The Telindus 1423 SHDSL Router supports the handling of broadcasts and multicasts and includes the following related functionalities:

• IGMPv2 (Internet Group Management protocol, RFC 2236), as the standard for IP multicasting• IGMP proxy function• Forwarding of directed broadcasts can be enabled or disabled per interface• Helper address can be configured for broadcasts

Filtering

• Filtering of outgoing traffic on all interfaces based on extended access lists• Filtering of incoming traffic on all interfaces based on extended access lists• Filtering of incoming traffic on the IP protocol stack based on an extended access list• IP extended access lists filter on the following parameters:

- Source IP address range- Destination IP address range- Type Of Service (TOS) value range (8 bits in the IP header, also called DSCP bits)- IP protocol (examples are any (0), ICMP (1), IGMP (2), TCP (6), UDP (17))- Source port range for UDP / TCP packets- Destination port range for UDP / TCP packets

IP MTU

• The IP MTU can be configured on the WAN and LAN interfaces (between 500 and 1650 bytes)

VRRP

• Support of VRRP (RFC 2338)



553

MR-8.12 Bridging specifications

• Bridging can be enabled or disabled per interface• Bridging can be combined with routing on the same interface

Bridging protocols

• Self-learning bridging can be enabled or disabled• Cache of at least 10,000 MAC addresses• Support of Spanning Tree protocol (IEEE 802.1D)

Bridge groups

• Multiple bridge groups possible• IP address assignment per bridge group (for management purposes)• Secondary IP addresses can be configured per bridge group• MAC address configurable per bridge group• Routing between different bridge groups possible

VLANs

• Support of VLANs (IEEE 802.1Q)• Up to 255 VLANs per LAN interface• Support of VLAN priority tagging (IEEE 802.1P)• Multiple VLANs within a bridge group towards the IP router possible• IP TOS to 802.1P COS mapping and COS to TOS mapping are available on the LAN interface to

maintain priority information when changing from IP to VLAN or vice versa• IP TOS to 802.1P COS mapping and COS to TOS mapping are available on the data sent between

a bridge group and the IP router to maintain priority information when changing from IP to VLAN or vice versa

• MIB2 performance counters are available per VLAN

VLAN switching

• Bridge group can be configured as VLAN switch• Q in Q as defined in IEEE 802.1ad possible• No practical limit on the number of VLANs in VLAN switching mode• VLAN switching mode can be combined with bridging mode for packets on the same interface

Filtering

• Filtering of outgoing bridged traffic on all interfaces based on access lists• Bridge access lists filter on source MAC address• Limit broadcasts in a bridge group per interface• Proxy ARP cache



554

MR-8.13 Network address translation specifications

• Compliant with RFC 3022• NAT mode for one-to-one private to public IP address translation• PAT mode for many-to-one private to public IP address translation• NAT/PAT configurable on any interface (the interface with the public address(es))• Up to 5 NAT/PAT interfaces• Static and dynamic assignment of NAT official addresses• List of UDP/TCP port numbers that should not be translated• List of incoming UDP/TCP port numbers destined for a server• Easy NAT: CPE learns official IP address via PPP• Application Layer Gateway (ALG) support including:

- General: FTP, ICMP (Echo, Echo Response, Destination Unreachable, Time Exceed & Source Quench), SQLNet

- Microsoft Games- Video / Streaming applications: RTSP, QuickTime, Real Player (Real Audio / Real Video), H.323

(ASN1 PER encoding and decoding included), NetMeeting, Intel Video Phone, CuseeMe 5.0, SIP Audio

- Communication: Internet Chat, IRC, MIRC, AOL Instant Messenger, AOL enhanced chat, ICQ2000b, Net2Phone, Microsoft Messenger

- Security Related: PPTP, IPSec ESP (IPSec client from internal network), IKE, L2TP



555

MR-8.14 Tunnelling and VPN specifications

L2TP tunnelling

• Compliant with RFC 2661• Up to 10 L2TP tunnels• Available on LAN and WAN interfaces• Static and dynamic tunnels• Tunnel authentication• Available for IP and bridged PDUs• One L2TP tunnel between each pair of IP addresses• One PPP session per L2TP tunnel• L2TP tunnels can be set up from an interface running NAT/PAT• L2TP backup tunnels• RIP snapshot routing on L2TP tunnels

IPSEC security

• Compliant with RFC 2401 up to RFC 2406• L2TP transport mode (RFC 3193)• Up to 10 IPSEC tunnels (independently of the number of L2TP tunnels)• ESP (RFC 2406)• DES (56 bits; RFC 2405), 3DES (3 * 56 bits; RFC 2451) and NULL (RFC 2410) encryption• HMAC based on MD5 (RFC 2403) and SHA-1 (RFC 2404) for integrity and authentication• Manual SAs• IPSec Key management protocol framework compliant with:

- RFC 2408: Internet Security Association and Key Management Protocol- RFC 2407: IP Security Domain of Interpretation for ISAKMP- RFC 2409: Internet Key Exchange (IKE)



556

MR-8.15 Priority and traffic policy specifications

This section gives the specifications of the priority and traffic policies that are available on the Telindus 1423 SHDSL Router. The following gives an overview of this section:

• MR-8.15.1 - Priority policy on page 557• MR-8.15.2 - IP traffic policy on page 557• MR-8.15.3 - Bridge traffic policy on page 557



557

MR-8.15.1 Priority policy

• 7 forwarding queues per interface:- 5 standard, configurable queues- 1 low delay queue- 1 system queue

• Quotum and weight configurable per standard queue• Supported algorithms to empty the standard queues:

- FIFO- Round robin- Absolute priority- Weighted fair queueing- Low delay weighted fair queueing

• CIR configurable per standard queue

MR-8.15.2 IP traffic policy

Supported IP traffic policies:

Traffic shaping

• Traffic is forwarded to a certain priority queue based on the following parameters:- Source IP address range- Destination IP address range- Type Of Service (TOS) value range (8 bits in the IP header, also called DSCP bits)- IP protocol (examples are any (0), ICMP (1), IGMP (2), TCP (6), UDP (17))- Source port range for UDP / TCP packets- Destination port range for UDP / TCP packets

• TOS value can be changed during traffic shaping• Configurable maximum queue length• Performance information on classified traffic

TosDiffServ

• Traffic is forwarded to a certain priority queue based on DiffServ (RFCs 2474, 2475) regarding class and drop precedence

TosMapped

• Traffic is forwarded to a certain priority queue based on a user-defined range of the TOS field• Configurable maximum queue length

MR-8.15.3 Bridge traffic policy

• Traffic is forwarded to a certain priority queue based on the 802.1P tag of VLAN tagged Ethernet traf-fic



558

MR-8.16 Routing and bridging performance specifications

• Routing performance:1

- without IPSEC, without HWA: 60.000 pps- without IPSEC, with HWA: 85.000 pps- with IPSEC, with HWA: TBD

• Bridging performance:- without HWA: 75.000 pps- with HWA: 110.000 pps

MR-8.17 Firewall specifications

• Firewall with 3 zones (Internet, Corporate, DMZ) and IP protocol stack (Self)• Outbound and inbound policies based on …

- Source and destination IP address range- Application (IP protocol and port range)

• PAT can be applied per outbound / inbound policy• Outbound and inbound policies for the IP protocol stack (Self)• Protection again attacks: SYN flooding, Source Routing, WinNuke, FTP Bounce, IP Unaligned

Timestamp, MIME Flood, Sequence Number Prediction, Sequence Number Out Of Range, URL Fil-tering, ICMP Error Messages

• Firewall logging with different priorities

1. In case you enable encryption in IPSEC, then the routing performance decreases.



559

MR-8.18 Access security specifications

• Password protected• Several access levels possible:

- Read access- Write access- Security access- File system access

• Radius client (RFC 2865)• Management access can be enabled or disabled per interface• Overall management access can be prohibited (Telnet, HTTP, SNMP, FTP, TFP)

MR-8.19 Maintenance and management specifications

• Local console (Command Line Interface or ATWIN) via serial control port• TELNET (Command Line Interface or ATWIN) (RFC 854)• HTTP web interface1 (RFC 2616)• Easy Configurator (customisable JAVA based web interface)• TMA (OneAccess Maintenance Application) via serial control port or IP connection (UDP port 1728)• TMA CLI2

• TMA Element Management2

• TMA for HP OpenView2

• TML (OneAccess Memory Loader) for configuration and software download via serial control port• FTP configuration and software download (RFC 414)• TFTP configuration and software download (RFC 1350)• PING (RFC 792)• SNMP (RFC 1157)• SNMP MIB2 (RFC 1213), private MIB• SNMP traps (RFC 1215)• SYSLOG event logging (RFC 3164)• SNTP (RFC 2030)• IP loopback address

1. HTTP interfaces are available on both port 80 and port 8080. This allows connecting to the HTTP interfaces in case a NAT service is defined on port 80.

2. Not included.



560

MR-8.20 Memory specifications

• Flash memory: 8 Mb• RAM: 16 Mb

MR-8.21 Power requirements

• Power adapter to be used: Vout = 12 Vdc, Iout = 1000 mA• Maximum power consumption:

MR-8.22 Dimensions

• Height: 45 mm• Width: 220 mm• Depth: 130 mm• Weight: 500 g

Pmax Input power

Version 12 Vdc 230 Vac1

1. Using the Friwo AC/DC adapter, 230Vac → 12Vdc/1A, approx. 50% efficiency, sales code 199744.

48 Vdc2

2. Using the PST30 DC/DC adapter, 48Vdc → 9-12Vdc/1A, approx. 73% efficiency, sales code 191706.

basic3

3. OneAccess 1423 SHDSL: 1 SHDSL line interface, 1 Ethernet interface

4.5 W 9 W 6.25 W

full4

4. OneAccess 1423 SHDSL 2ETH-4P ISDN-BRI HWA: 1 SHDSL line interface, 1 Ethernet inter-face, 4 port Ethernet switch, 2 ISDN line interfaces, HWA chip

7.5 W 15 W 10.25 W



561

MR-8.23 Safety compliance

• EN60950-1• Class 1 equipment for Table Tops with 115/230 Vac internal power supply.• Class 3 equipment for …

- Table Tops with 115/230 Vac external power supply adapter- Table Tops with -48 Vdc internal power supply- Card Versions.

MR-8.24 Over-voltage and over-current protection compliance

The over-voltage and over-current protection complies with ITU-T K.44 and ETSI ETS 300 386-2 recom-mendations.

MR-8.25 EMC compliance

• EN55022 B Emissions• EN55024 Immunity• EN61000-3-2 Harmonics• EN61000-3-3 Voltage fluctuations and flicker• EN61000-4-2 ESD• EN61000-4-3 Radiated immunity• EN61000-4-4 EFT/burst• EN61000-4-5 Surge• EN61000-4-6 Conducted immunity• EN61000-4-8 Power magnetic field immunity• EN61000-4-11 Voltage dips & drops• ENV50204 Radiated immunity against digital radio telephone

MR-8.26 Environmental compliance

• Storage conditions: ETSI ETS 300 019-1-1 Class 1.1. In addition, the storage temperature has to be between -25 to +70°C

• Transport conditions: ETSI ETS 300 019-1-2 Class 2.3• Stationary use conditions: ETSI ETS 300 019-1-3 Class 3.2. In addition, a relative humidity between

0 to 95% non-condensing and an ambient operational temperature between -10 to 50°C is supported.• Maximum altitude: 3000m• International protection (IP) class of protection against solid and liquids: IP40


Annex

562

Annex


Annex

563

Telindus 1423 SHDSL Router Annex A:

Annex common TCP and UDP numbers

564

Annex A: common TCP and UDP numbers

The following table shows the port numbers for a number of common protocols using TCP and UDP as transport protocol. As far as possible, the same port numbers are used for TCP as for UDP. A complete list can be found on http://www.iana.org/assignments/port-numbers.

Port No Protocol UDP/TCP Description

20 ftp-data TCP File Transfer (Default Data)

21 ftp TCP File Transfer (Control)

23 telnet TCP Telnet

25 smtp TCP Simple Mail Transfer Protocol

37 time UDP/TCP Time Server

42 nameserver UDP Host Name Server

53 domain UDP/TCP Domain Name Server

65 tacacs-ds UDP/TCP TACACS-Database Service

67 bootps UDP Bootstrap Protocol Server

68 bootpc UDP Bootstrap Protocol Client

69 tftp UDP Trivial File Transfer

80 www-http TCP World Wide Web HTTP

119 nntp TCP Network News Transfer Protocol

137 netbios-ns UDP NETBIOS Name Service

138 netbios-dgm UDP NETBIOS Datagram Service

139 netbios-ssn UDP NETBIOS Session Service

161 snmp UDP SNMP

162 snmptrap UDP SNMPTRAP

1728 OneAccess UDP OneAccess Protocol used by TMA

http://www.iana.org/assignments/port-numbers

Telindus 1423 SHDSL Router Annex A:

Annex common TCP and UDP numbers

565

Telindus 1423 SHDSL Router Annex B:

Annex product information

566

Annex B: product information

The following table displays the product information of the Telindus 1423 SHDSL Router:

Sales code Product name Description

175590 PWR-PLUG (EUR VERSION)230VAC >9VDC

Wallplug power module European type, 230Vac -> 9Vdc for Desktop units delivered without power adapter. (xxx NPWR).

175592 PWR-PLUG (UK VERSION) 230VAC->9VDC Wallplug power module UK type, 230Vac -> 9Vdc for Desktop units delivered without power adapter. (xxx NPWR).

191706 PWR-PLUG +/-48/24VDC FOR 7,5/9VDC CPE DEVICES

Wallplug power module with input range: 18 to 72Vdc and output: 7,5 / 9Vdc for Desktop units delivered without power adapter. (xxx NPWR). Fully isolated input. Suitable for + & - DC voltages.

Telindus 1423 SHDSL Router Annex B:

Annex product information

567

Telindus 1423 SHDSL Router Index

Annex

568

Index

Numerics4 port Ethernet switch

specifications 546

Aabsolute and relative addressing 241

access securityspecifications 559

addressing, relative and absolute 241

alarm attributes 484configuration 489general 490introduction 488overview 485

alarmsAUX interface 502B-channel 501BRI 500bundle 503end 498general 491LAN interface 493line 495line pair 496MLPPP 503repeater 498router 504WAN interface 494

application mode, what is 535

application softwaredownloading

using FTP 539using TFTP 537using TMA 536using TML 538

what is 535

ARP cachehow works the 22proxy ARP 23time-out 23what is 22

ATMconfiguration attributes 38performance attributes 419specifications 549status attributes 275

attribute - actionActivate Configuration 18clearArpCache 270, 383clearBridgeCache 383clearCounters 430

clearIsdnCall 312clearSAs 353clearTracert 454Cold Boot 19Delete File 392generateSelfCertificateRequest 393getCrlScep 398getSelfCertificateScep 396getTrustedCertificateScep 395injectError 430Load Default Configuration 18Load Preconfiguration 18Load Saved Configuration 19loadSelfCertificate 394loadTrustedCertificate 392loopbackActivation 305, 312maximumSpeedSearch 300Rename File 392reset 457resetAllCounters 411resetCounters 411retrain 432saveCertificates 398Set Date 261Set Time 261startPing 452startTest 296, 430startTracert 453stopPing 452stopTest 296, 430stopTracert 454unBlacklist 344

attribute - alarmalarmInfo 490alarmLevel 489alarmMask 489totalAlarmLevel 490

attribute - configuration24hMaxCallTime 91accessList 242accessPolicy 243adapter 23addresses 154addrPools 145advertiseInterval 197alarmFilter 244alarmLevel

bChannel object 84BRI interface object 87bri object 82end object 78LAN interface object 34line object 76line pair object 76PPP bundle object 125repeater object 78router object 151top object 17


Annex

569

WAN interface object 36alarmMask

bChannel object 84BRI interface object 87bri object 82end object 78LAN interface object 34line object 76line pair object 76PPP bundle object 125repeater object 78router object 151top object 17WAN interface object 36

algorithm 112alternativeRoutes 130areaId 184arp 22, 224atm 46attacks 217atwinGraphics 245authenPeriod 60, 95authentication 60, 95bandwidth 115bcastStormProtection 33blockSize 65bootFromFlash 15bridgeCache 225bridgeTimeOut 226bridging 21, 57, 63, 123callback 97callInterval 90callTimeOut 90channel 67cms2Address 241compression 58, 95connection 95consoleNoTrafficTimeOut 244countingPolicy 114criticals 196ctrlPortProtocol 247defaultRoute 128delayOptimisation 55, 57dhcpCheckAddress 141dhcpDynamic 139dhcpStatic 137dialAllowed 82dialPktBufSize 90dialTimeTable 91dlciTable 49dmzHost 155dns 144dropLevels 106, 110dualPairMode 72encapsulation 36, 86eocHandling 75espAuthenticationAlgorithm 169espAuthenticationKey 169espEncryptionAlgorithm 167

espEncryptionKey 168fastIdleTimeOut 90filter 193fragmentation 55, 124ftp 243gateway 155helperProtocols 134idleTimeOut 90importMetrics 181, 182inboundPolicies 204inboundSelfPolicies 213inspection 199interfaces 196ip 21, 48, 57, 99, 123, 224ipAddress (loopback) 247ipAddresses 195ipNetMask (loopback) 247ipsecL2tpTunnels 162isdnInterfaces 90keyChains 180l2tpTunnels 157linkAlarmThresholds 74linkMonitoring 59, 95lmi 52localAccess 227log 219loginControl 246lowdelayQuotum 114macAddress 228, 234management 75mapping 117maxChannelsUsed 93maxFifoQLen 36, 86, 87, 99maxSpeed 71maxSpeed2P 72members 123method 101mib2Traps 236minChannelsFree 93minSpeed 71minSpeed2P 72mode 21, 57, 72, 123modeLearnedDlci 55mru 55, 57, 63multiclassInterfaces 124multiLink 96name 21, 36, 224networks 186numExpectedRepeaters 75outboundPolicies 199outboundSelfPolicies 209patAddress 153phase1 171phase2 175ports 30portTranslations 153pppSecretTable 133preemptMode 197priorityPolicy 22, 36, 86, 99


Annex

570

programmablePattern 65pvcTable 39queueConfigurations 114radius 142ranges 191refBandwidth 180region 67retrain 69ripHoldDownTime 131ripUpdateInterval 130ripv2SecretTable 132routerId 180routingProtocol 130routingTable 129security 16sendAdminUnreachable 136sendPortUnreachable 136sendTtlExceeded 135servicesAvailable 154sessionName 61sessionSecret 61snmp 243spanningTree 226spi 169startupMargin 71stub 184switchMode 30sysContact 15sysLocation 15sysLog 238sysName 15sysSecret 133tcpSockets 155tcpSocketTimeOut 155tei 81telephoneNrs 82telnet 243testType 65tftp 243timedStatsAvailability 244timeServer 240timeZone 240timingMode 68tos2QueueMapping 108trafficShaping 103trapDestinations 236udpSockets 155udpSocketTimeOut 155virtualLinks 189vlan 24, 229vlanPriorityMap 110vlanSwitching 231vp 45vrId 195

attribute - performanceaddressesAvailable 456allocFails 456bridgeAccessList 476

bridgeCache 473bridgeDiscards 473bridgeFloods 473cliSessionCount 478cllmInFrames 427cms2SessionCount 478currUsedProcPower 481d7Attack 468d7DialupStats 438d7General 466d7Line 432d7LineParameters 433d7Performance 434discards 456, 470dlciTable 425duration 429espAuthenticationFailure 461espDecryptionFailure 461espDroppedFrames 461espSequenceNrReplay 461freeBlockCount 481freeDataBuffers 481freeMemory 482h24Attack 467h24DialupStats 438h24General 466h24Line 432h24LineParameters 433h24Performance 415, 434h2DialupStats 438h2Line 432h2LineParameters 433h2Performance 415, 434icmpAllocs 457icmpSocketsUsed 456ifDownCount 429ifDropLevelExceeded 415ifInDiscards 413ifInErrors 413ifInNUcastPkts 413ifInOctets 413ifInUcastPkts 413ifInUnknownProtos 413ifOutDiscards 414ifOutErrors 414ifOutNUcastPkts 414ifOutOctets 414ifOutPQLen 415ifOutQLen 414ifOutUcastPkts 414ifUpTime 429inPackets 461ipStackEvents 479l2tpTunnels 459largestFreeBlockSize 481line 432lineParameters 433lmi 427mapping 443


Annex

571

mibCounters 416multiclassinterfaces 446multiVlans 473outPackets 461performance 434phase2Negotiations 463phase2Sessions 463pingResults 451pvcTable 420radiusAcct 450radiusAuth 450routingTable 449rxAllOneBlocks 429rxAllZeroBlocks 429rxBitErrors 429rxBlockErrors 429rxBlocks 429rxPatternSlip 429rxShiftCount 429rxSyncLoss 429socketsFree 456status 429taskInfo 482tcpAllocs 457tcpSessionCount 479tcpSocketsUsed 456tftpSessionCount 479totalDataBuffers 481totalMemory 482tracertResults 451trafficShaping 470txBlocks 430txInjectErrors 430udpAllocs 457udpSocketsUsed 456unknownCells 423usedProcPower 481vlan 416vlanSwitching 474vp 423

attribute - statusabrs 365accessLog 386activeFlash 260actualBitRate 301adapter 268addresses 346addrPools 344alarmLog 385arpCache 265, 379asbrLsas 370asExtLsas 359atmSync 276bacpHisOptions 332bacpMyOptions 332bacpState 332bChannelUsage 311bcpHisOptions 290, 331

bcpMyOptions 290, 331bcpState 287, 331blockSize 296bootVersion 260bridgeCache 380bridging 266, 286, 294, 331, 381callDirection 314ccpHisOptions 291ccpMyOptions 291clearLog 376cllmLastCongestionCause 284cms2Address 385configurationSaving 261corruptBlocks 390criticals 373ctsItu106 319date 261dcdItu109 320deviceId 261dhcpBinding 341dhcpBlackList 342dhcpStatistics 341, 342dialMapEntry 314dlciTable 281dns 343dnsServers 343dsrItu107 319dtrItu108 319duration 296eocAlarmThresholds 299, 304eocSoftVersion 303eocState 304externalRoutes 358fileList 390flash1Version 259flash2Version 259flashVersions 260freeSpace 390hisAuthenticationStatus 292hisCompressionRatio 291hosts 363ifDescr 263, 272, 298, 308, 314, 316, 319,

328, 378, 388ifLastChange 263, 272, 308, 314, 316, 319ifMtu 263, 272, 308, 314, 316, 319, 378, 388ifOperStatus 263, 272, 298, 301, 308, 314,

316, 319, 328, 378, 388ifSpeed 263, 272, 298, 301, 316, 319, 328ifType 263, 272, 298, 308, 314, 316, 319,

328, 378, 388igmpTable 339inBandwidth 332interfaces 361, 373ip 264, 281, 286, 329, 378ipAddress 388ipAdEntBcastAddr 269ipAdEntReasmMaxSize 269ipcpHisOptions 289, 330ipcpMyOptions 289, 330


Annex

572

ipcpState 287, 329ipsecL2tpTunnels 349l1Status 309l2tpTunnels 348lapdLinks 310lcpHisOptions 288lcpMyOptions 288lcpState 287lineAttenuation 301, 304lmi 283localPhoneNr 314log 376macAddress 264, 373, 378mapping 324mask 388maxSpeedResult 298, 299maxSpeedSearch 298members 328messages 260multiclassInterfaces 333myAuthenticationStatus 292myCompressionRatio 291neighbors 363networkLsas 368nssaLsas 371numDiscoveredRepeaters 299outBandwidth 332phase1 353phase2 353ports 269profileUsers 322programmablePattern 296pvcTable 276radius 343receiveSample 296region 298remotePhoneNr 314reverseSessions 375riItu125 320routerLsas 366routes 357routingTable 336rtsItu105 319rxdItu104 319selfCertificates 391sessions 375shdslVersion 303signalNoise 301, 304sNet 376spanningTree 381startSysUpTime 296status 296, 301, 390summLsas 369sysDescr 259sysObjectID 259sysServices 259sysUpTime 259taskInfo 400tdreVersion 260

testStatus 311testType 311time 261timeServer 385timeSinceLastRetrain 301trustedCertificates 391txdItu103 319type 296, 356vendorId 303vendorModel 303vendorSerial 303vendorSoftVersion 303vlan 268vp 279

auto-install 508on the LAN interface 511

example 514in case of Ethernet 513set-up 512

on the WAN interface 516example 520in case of ATM 518in case of Frame-Relay 519setup 517

protocols, introducing 509specifications 548

AUX interfacealarms 502performance attributes 441status attributes 318

BBasic Rate ISDN interface

configuration attributes 79configuration attributes, general 80performance attributes, general 437specifications 545status attributes, general 307

B-channelalarms 501configuration attributes 83performance attributes 439status attributes 313

boot mode, what is 535

boot software, what is 535

BootPwhat is 509

BRIalarms 500performance attributes 436status attributes 306

bridgeconfiguration attributes 222general configuration attributes 223performance attributes 471


Annex

573

specifications 553status attributes 377

bridge access listconfiguration attributes 233performance attributes 475

bridge cachetime-out 226what is 225

bridge filteringspecifications 553

bridge groupconfiguration attributes 223performance attributes 472specifications 553

broadcastingspecifications 552

bundlealarms 503configuration attributes 121performance attributes 444status attributes 326

Ccommon TCP and UDP numbers 564

configuration alarm attributes 489

configuration attributes 4ATM 38Basic Rate ISDN interface 79Basic Rate ISDN interface, general 80B-channel 83bridge 222bridge access list 233bridge group 223bundle 121dial maps 116encapsulation 37encapsulation profile 94end 77error test 64firewall 198forwarding profile 98Frame Relay 47general 14HDLC 62IKE SA 170ISDN dial profile 89ISDN leased line 85L2TP tunnel 156LAN interface 20line 66line pair 66management 237manual SA 166MLPPP 121NAT 152

OSPF 178OSPF area 183OSPF, general 179overview 5PPP 56PPP bundle 122priority policy 111profiles 88repeater 77router 126router, general 127routing filter 192SNMP 235traffic policy

bridging 109IP 100

VRRP 194WAN interface 35

configuration filecreating 523creating a binary file using TMA 525creating an ASCII CLI file

using Telnet 529using TFTP 528using TMA 526

downloading 530using (T)FTP 532using Telnet 533using TMA 531

formats 524restoring 530

control connector specifications 547

DDHCP

what is 509

dial mapsconfiguration attributes 116performance attributes 442status attributes 323

dimensions of the device 560

DMZwhat is 155

DNSwhat is 144, 509

DNS proxywhat is 144

downloading a configuration file 530using (T)FTP 532using Telnet 533using TMA 531

downloading application softwarein boot mode 540using FTP 539using TFTP 537


Annex

574

using TMA 536using TML 538

downloading files to the file system 541

downloading software 534

EEMC compliance 561

encapsulationconfiguration attributes 37performance attributes 418

encapsulation profileconfiguration attributes 94

endalarms 498configuration attributes 77performance attributes 435status attributes 302

environmental compliance 561

error testconfiguration attributes 64performance attributes 428status attributes 295

Ffile system

downloading files to 541status attributes 389

firewallconfiguration attributes 198performance attributes 465specifications 558status attributes 374

forwarding profileconfiguration attributes 98

Frame Relayconfiguration attributes 47performance attributes 424specifications 550status attributes 280

Ggeneral

alarm attributes 490alarms 491configuration attributes 14performance attributes 410status attributes 258

HHDLC

configuration attributes 62status attributes 293

IICMP

specifications 551

ICMP messagecommunication prohibited 136port unreachable 136TTL exceeded 135

IGMPtopology 339what is 339

IKE SAconfiguration attributes 170performance attributes 462status attributes 352

introducingalarm attributes 488

IP addressesspecifications 548

IP filteringspecifications 552

IP MTUspecifications 552

IP securityperformance attributes 460

IPSECspecifications 555

ISDN dial profileconfiguration attributes 89

ISDN leased lineconfiguration attributes 85performance attributes 440status attributes 315

LL2TP status

authentication states 351call states 350control states 350delivery states 351

L2TP tunnelconfiguration attributes 156performance attributes 458specifications 555status attributes 347

LAN interfacealarms 493configuration attributes 20performance attributes 412specifications 546status attributes 262

linealarms 495


Annex

575

configuration attributes 66performance attributes

performance attributesline pair 431

retrain criteria 69specifications 543

connector lay-out 543maximum covered distance 544

status attributes 297

line pairalarms 496configuration attributes 66performance attributes 431status attributes 297

Mmaintenance and management

specifications 559

managementconfiguration attributes 237performance attributes 477status attributes 384

manual SAconfiguration attributes 166performance attributes 460

memoryspecifications 560

MLPPPalarms 503configuration attributes 121

MRUwhat is 55, 57, 63

multicastingspecifications 552

NNAT

configuration attributes 152performance attributes 455specifications 554status attributes 345

OOAM AIS, what is 422

OAM RDI, what is 422

operating systemperformance attributes 480status attributes 399

OSPFconfiguration attributes 178configuration attributes, general 179specifications 551status attributes 354status attributes, general 355

OSPF areaconfiguration attributes 183status attributes 360

other WAN encapsulationsspecifications 550

overviewalarm attributes 485configuration attributes 5performance attributes 403status attributes 249

over-voltage and over-current protection compli-ance 561

Ppasswords

remarks on 17

PATspecifications 554

performance attributes 402ATM 419AUX interface 441Basic Rate ISDN interface, general 437B-channel 439BRI 436bridge 471bridge access list 475bridge group 472bundle 444dial maps 442encapsulation 418end 435error test 428firewall 465Frame Relay 424general 410IKE SA 462IP security 460ISDN leased line 440L2TP tunnel 458LAN interface 412line 431management 477manual SA 460NAT 455operating system 480overview 403PPP bundle 445repeater 435router 447router, general 448traffic policy

IP 469WAN interface 417

policies, traffic and priorityspecifications 556

policy based routing


Annex

576

specifications 551

power requirements 560

PPPconfiguration attributes 56specifications 550status attributes 285

PPP bundleconfiguration attributes 122performance attributes 445status attributes 327

priority policyconfiguration attributes 111specifications 557

product information 566

profilesconfiguration attributes 88status attributes 321

proxy ARP, what is 23

Rrelative and absolute addressing 241

relay agentthe Telindus Router as 510

remarks onaccessing a proxied device via its IP address

22channel attribute 67compression attribute 58dhcpStatistics attribute 341dialTimeTable attribute 92dualPairMode attribute 73error test, RAM limitations 296extended access list on the protocol stack

243helperProtocols attribute 134host routes to local interface IP address 338ifOperStatus of the WAN interface 273, 317IP address on the LAN interface in case of

bridging 21, 224ipIntervalPool attribute 149ipListPool attribute 146L2TP tunnels, auto element 159L2TP tunnels, type element 159loopbackActivation action 305, 312maximumSpeedSearch action 300messages attribute 260NAT in the ip structure versus NAT in the fire-

wall 203, 208passwords 17resetNat action 457ripv2SecretTable attribute 132routing update filter 193telnet attribute 243timingMode attribute 68trafficShaping table 103

VLAN ID 0 26

repeateralarms 498configuration attributes 77performance attributes 435status attributes 302

restoring a configuration file 530

RIPspecifications 551

RIP hold-down timer, what is 131

routeralarms 504configuration attributes 126general configuration attributes 127general performance attributes 448general status attributes 335performance attributes 447status attributes 334

routingspecifications 551

routing and bridging performance specifications 558

routing filterconfiguration attributes 192

Ssafety

compliance 561

sales codes 566

SNMPconfiguration attributes 235

SNTP, what is 240

softwaredownloading 534what is boot and application 535

specifications4 port Ethernet switch 546access security 559ATM encapsulation 549auto-install 548Basic Rate ISDN interface 545bridge group 553bridging 553broadcasting 552control connector 547dimensions 560EMC compliance 561environmental compliance 561firewall 558Frame Relay encapsulation 550ICMP 551IP filtering 552IP MTU 552


Annex

577

IPaddresses 548IPSEC 555L2TP tunnel 555LAN interface 546line 543

connector lay-out 543maximum covered distance 544

maintenance and management 559memory 560multicasting 552NAT 554OSPF 551other WAN encapsulations 550over-voltage and over-current protection

compliance 561PAT 554policies, traffic and priority 556policy based routing 551power requirements 560PPP encapsulation 550priority policy 557RIP 551routing 551routing and bridging performance 558safety compliance 561static routing 551traffic policy on the bridge 557traffic policy on the router 557tunnelling 555VLAN 553VLAN switching 553VPN 555VRRP 552

static routingspecifications 551

status attributes 248ATM 275AUX interface 318Basic Rate ISDN interface, general 307B-channel 313BRI 306bridge 377bundle 326dial maps 323end 302error test 295file system 389firewall 374Frame Relay 280general 258HDLC 293IKE SA 352ISDN leased line 315L2TP tunnel 347LAN interface 262line 297line pair 297management 384

NAT 345operating system 399OSPF 354OSPF area 360OSPF, general 355overview 249PPP 285PPP bundle 327profiles 321repeater 302router 334router, general 335VRRP 372WAN interface 271

syslog, what is 238

Ttarget margin, what is 71

technical specifications 542

TFTPwhat is 510

Time To Live (TTL), what is 135

TMA sub-system picture 506how to display 506structure 506

traffic policyconfiguration attributes of the bridge 109configuration attributes of the router 100performance attributes of the router 469specifications of the bridge 557specifications of the router 557

tunnellingspecifications 555

Uunique digits, what are 119

UTC, what is 240

VVLAN

local or global tag significance 29specifications 553

VLAN switchingspecifications 553stripping the VLAN tag 231

VPNspecifications 555

VRRPconfiguration attributes 194specifications 552status attributes 372


Annex

578

WWAN interface

alarms 494configuration attributes 35performance attributes 417status attributes 271


Annex

579

telindus1423(fr)

Documents