Confused about shdsl

[mhcnetadmin]

Hi all

I have 2 shdsl modems connected to cisco 2821 router via serial interface, and another shdsl routers that is configured as bridge (not connected to cisco).

so I have 3 branches that is connected via shdsl. I want to  replace these modems/router with Cisco Hwic- 4shdsl 

What is confusing me is that on the shdsl modem the configuration

=============
|   sysName              =
|   sysContact           =
|   sysLocation          =
|   security             [Empty table]
|   forwardTmaToCtrlPort = enabled
|   forwardTmaToLine     = enabled
|   alarmMask            = 0000000011
|   alarmLevel         
|       notResponding         = 4
|       alarmSyncLoss         = 4
|       configChanged         = 1
|       access                = 1
|       remoteAlarm           = 0
|       unknownState          = 0
|       coldBoot              = 1
|       warmBoot              = 1
|       codeConsistencyFail   = 1
|       configConsistencyFail = 1
|   remoteAlarmMask      = 0000000000
|
+-- line
|   |   channel                    = remote
|   |   region                     = auto
|   |   asymmetricPsd              = disabled
|   |   retrain                  
|   |       enabled              = yes
|   |       errorPersistenceTime = 10 seconds
|   |       errorThreshold       = 10 proMille
|   |       snrThreshold         = 23.0dB
|   |       stepupMargin         = disabled
|   |   management                 = o10-PathManagement
|   |   endAlarmMask               = 0
|   |   endAlarmLevel            
|   |       linkDown = 3
|   |   endLinePairAlarmMask       = 00000
|   |   endLinePairAlarmLevel    
|   |       lineAttenuation        = 1
|   |       signalNoise            = 1
|   |       errSecRatioExceeded    = 1
|   |       sevErrSecRatioExceeded = 2
|   |       bBErrRatioExceeded     = 1
|   |   repeaterAlarmMask          = 0
|   |   repeaterAlarmLevel       
|   |       linkDown = 3
|   |   repeaterLinePairAlarmMask  = 00000
|   |   repeaterLinePairAlarmLevel
|   |       lineAttenuation        = 1
|   |       signalNoise            = 1
|   |       errSecRatioExceeded    = 1
|   |       sevErrSecRatioExceeded = 2
|   |       bBErrRatioExceeded     = 1
|   |   name                       =
|   |   timingMode                 = plesiochronous
|   |   startupMargin              = 2dB
|   |   eocChannel                 = itu-G.991.2
|   |   testDuration               = 00000d 00h 03m 00s
|   |   alarmMask                  = 001
|   |   alarmLevel               
|   |       linkDown            = 3
|   |       invalidNumRepeaters = 1
|   |       testActive          = 1
|   |   remoteAlarmMask            = 000
|   |   linkAlarmThresholds      
|   |       lineAttenuation        =  0.0 dB
|   |       signalNoise            =  0.0 dB
|   |       errSecRatioExceeded    = 0.040 ratio
|   |       sevErrSecRatioExceeded = 0.002 ratio
|   |       bBErrRatioExceeded     = 0.000200 ratio
|   |   numExpectedRepeaters       = 0
|   |   eocHandling                = none
|   |   minLinePairSpeed           = 512kbps
|   |
|   +-- linePair[1]
|           alarmMask       = 000000
|           alarmLevel    
|               linkDown               = 3
|               lineAttenuation        = 1
|               signalNoise            = 1
|               errSecRatioExceeded    = 1
|               sevErrSecRatioExceeded = 2
|               bBErrRatioExceeded     = 1
|           remoteAlarmMask = 000000
|
+-- v35
|       name                =
|       speed               = 512kbps
|       rtsControl          = internal
|       ctsDelay            = 0 ms
|       rdlDetect           = enabled
|       tests             
|           interfaceRdl = disabled
|           interfaceAl  = disabled
|       alarmMask           = 011
|       alarmLevel        
|           linkDown     = 3
|           lossOfTiming = 3
|           backupTiming = 2
|       remoteAlarmMask     = 000
|       clocking            = slaveRcvAlternative
|       transmitSampleClock = normal
|
+-- management
|       cms2Address             = 0
|       consoleNoTrafficTimeOut = 00000d 00h 30m 00s
|       ctrlPortProtocol        = console
|
+-- operatingSystem

there is no atm, pvc or authentication or anything, according to cisco configuration when configuring shdsl controller  an ATM interface is created and a pvc (vpn/vci) is configured , encapsulation,...etc

and on the router  which is bridged :

============
|   sysName              =
|   sysContact           =
|   sysLocation          =
|   security             [Empty table]
|   bootFromFlash        = Auto
|   forwardTMAToNMSPort  = enabled
|   forwardTMAToLine     = enabled
|   alarmMask            = 000000011
|   alarmLevel         
|       NotResponding         = 4
|       AlarmSyncLoss         = 4
|       StrapChanged          = 1
|       Access                = 1
|       RemoteAlarm           = 0
|       UnknownState          = 0
|       Boot                  = 1
|       CodeConsistencyFail   = 1
|       ConfigConsistencyFail = 1
|   alarmContactHighMask = 000000000
|   alarmContactLowMask  = 000000000
|
+-- modem
|   |   tests              
|   |       keyboardET  = enabled
|   |       keyboardAL  = enabled
|   |       keyboardRDL = enabled
|   |       keyboardDL  = enabled
|   |       detectRDL   = enabled
|   |       aLDuration  = 00000d 00h 03m 00s
|   |   retrain            
|   |       averagingPeriod = 10 seconds
|   |       threshold       = 1e-003
|   |   alarmMask            = 001
|   |   alarmLevel         
|   |       LinkDown   = 3
|   |       TestActive = 1
|   |       SyncLoss   = 3
|   |   alarmContactHighMask = 000
|   |   alarmContactLowMask  = 000
|   |   syncLossAlarmTimeout = 00000d 00h 00m 10s
|   |   highBitErrorAlarm  
|   |       averagingPeriod = 60 seconds
|   |       onThreshold     = 1e-003
|   |       offThreshold    = 1e-004
|   |   lowBitErrorAlarm   
|   |       averagingPeriod = 10 minutes
|   |       onThreshold     = 1e-006
|   |       offThreshold    = 1e-007
|   |   channel              = remote
|   |
|   +-- line
|           speed                = 2048000 bps
|           alarmMask            = 000000
|           alarmLevel         
|               LinkDown              = 3
|               Retrain               = 2
|               HighBitError          = 2
|               LowBitError           = 1
|               SeverelyErroredSecond = 2
|               Unavailability        = 2
|           alarmContactHighMask = 000000
|           alarmContactLowMask  = 000000
|
+-- nMS
|       cms2Address = 0
|
+-- bridge
|       lANFilter            = enabled
|       alarmMask            = 1
|       alarmLevel         
|           LinkDown = 3
|       alarmContactHighMask = 0
|       alarmContactLowMask  = 0
|       clocking             = Slave-rcv Alternative
|
+-- powerOffDetection
        mode                 = disabled
        alarmMask            = 000
        alarmLevel         
            Open line         = 3
            Remote power fail = 3
            Short circuit     = 3
        alarmContactHighMask = 000
        alarmContactLowMask  = 000

how would I configure the Cisco Hwic- 4shdsl in order to connect these three branches??

[Peter Paluch]

Hello,

Hmm, the information you currently have is closely related to the Layer1 only. It does not say anything about the PVCs and the additional encapsulation (PPPoE, PPPoA).

However, can you describe the SHDSL modems you have? What is their exact type? What are their interfaces? It may actually be possible that these are leased-line modems that are just using the SHDSL line encoding to carry data. This way, they can probably talk to each other but perhaps they are not supposed to talk to a generic SHDSL device - just my opinion, please do not take me for granted here. Disclosing their exact type and describing their interfaces could help a lot.

Best regards,

Peter

[mhcnetadmin]

Hi thanks fory your reply

I have  telindus crocusShdsl it has V.35 interface and RJ11

Telindus Crocus SHDSL 9V TT  RS530  and RJ11

the third one is Telindus crocusSDSL Router RJ45 and RJ11

Thanks again

[Peter Paluch]

Hello,

Thank you for the additional information. I have tried to locate and read the datasheets and manuals about the SHDSL modems you are using. Unofrtunately, it looks to me that these modems are true modems only. They do not use ATM encapsulation, rather, they simply seem to take the data from the input port and convey it through the 2-wire or 4-wire using the SHDSL-alike line coding (similar to what all our old analogue V.34bis/V.90/V.92 modems do).

That would mean that these modems are actually unable to talk to a classic DSLAM speaking ATM, rather, they are only able to speak to themselves or to other SHDSL devices that are transparent, not ATM-based. Also, it would be incorrect to pair two similar modems, one having a V.35 interface and other having, say, Ethernet. That would mean that you would try to emit an Ethernet frame through a V.35 interface obviously using a different framing (HDLC, PPP, LAPB) which would not work.

So the bottom line is... I am afraid that these modems are not suitable to be used with a regular SHDSL service using ATM encapsulation. These modems seem to be intended for use on a leased line in pairs.

Best regards,

Peter

[mhcnetadmin]

Thank you very much