Controller E1 3/2 Down Problemi
CLI Guru - Cisco Eğitim ve Danışmanlık Merkezi |

+ Konuyu Cevapla
Toplam 2 sonuçtan 1 ile 2 arasındakiler gösteriliyor.
Controller E1 3/2 Down Problemi

Gece kapattıysan onlar hattan AIS hata mesajı aldıkları için kapatmı�lardır. Hattı normal görüyor olmaları mümkün de�il senin tarafını down görüyor olmaları lazım:-) �nerim hatta loop verdirmen. Telekom loopu görüyorsa onların

  1. #1
    YAVUZ TEMIZKAN Guest

    Standart Controller E1 3/2 Down Problemi

    Gece kapattıysan onlar hattan AIS hata mesajı aldıkları için kapatmı�lardır.
    Hattı normal görüyor olmaları mümkün de�il senin tarafını down görüyor olmaları lazım:-)
    �nerim hatta loop verdirmen. Telekom loopu görüyorsa onların tarafında sorun yoktur


    -----Original Message-----
    From: Ã�smail" CAN [mailto:[email protected]]
    Sent: 03 A�ustos 2004 Salı 10:31
    To: [email][email protected][/email]
    Subject: Re: [cisco-ttl] controller e1 3/2 down problem

    Merhaba,

    Suan gw yi sadece PRI icin kullancam o yuzden aktif olmadýgý icin kapattim. Ama kesinlike ne fiziksel baglantýda ne de configte degisiklik yaptým. Configi save ettim copy run startup, sabah geldigimde de tek yaptýgým acmak oldu. Modem uzerindeki ledlere gore hersey normal gorunuyor. Ancak gw de yine ayný problemler. Telekomu aradým burdan hersey normal gorunuyor diyorlar.
    Nasýl bir yol izlemeliyim. Tesekkurler


    as5350#sh isdn status
    Global ISDN Switchtype = primary-net5
    ISDN Serial3/2:15 interface
    dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
    DEACTIVATED
    Layer 2 Status:
    TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
    0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask: 0x00000000
    Number of L2 Discards = 0, L2 Session ID = 0
    Total Allocated ISDN CCBs = 0

    Serhat Uslay <[email protected]> wrote:

    "gw kapattim" , niye GW 'yi kapatiyorsun ?? .. kapatmadan once bir degisiklik yapmadiysan calismasi lazim..
    tekrar boot ederken hic hata mesaji aldin mi ?
    eger kendi tarafindan emin sen Telekom'a bastir, loopback filan yapip kontrol etsinler...
    Serhat
    Please respond to [email][email protected][/email]
    To: [email][email protected][/email]
    cc:
    Subject: Re: [cisco-ttl] controller e1 3/2 down problem



    Merhaba,

    Dun aksam hersey normaldi yani sh isdn status ve sh controllers e1 3/2 yaptýgýmda hersey normaldi. Daha sonra aksam giderken gw kapattým bu sabah actim yine ayný problem Layer 1 Deactivated ve controller e1 3/2 down. Benim bu ise aklim ermedi. Sorun benim tarafta mi telekomda mi anlamadim. Telekomu ariyorum bizim tarafta hersey normal sizin tarafta sorun var diyorlar. Arkadaslar yardimci olabilirmisiniz. Tesekkurler...

    Serhat Uslay <[email protected]> wrote:

    Daha once calistimi yoksa yeni bir duzenleme mi ??
    1) su dokumani bir oku.. [url]http://www.cisco.com/warp/public/116/T1_pri.html[/url]
    2) Eger cablo ve modem den eminsen, carrier ile konus..
    boyle bir cikti gormen lazim hersey duzgun ise
    RTDC05>sh isdn stat
    Global ISDN Switchtype = primary-net5
    ISDN Serial4/0/0:15 interface
    dsl 0, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
    ! ACTIVE
    Layer 2 Status:
    TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
    Layer 3 Status:
    0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask: 0x801F7FFF
    Number of L2 Discards = 0, L2 Session ID = 0

    Serhat

    Please respond to [email][email protected][/email]

    To: [email][email protected][/email]
    cc:
    Subject: [cisco-ttl] controller e1 3/2 down problem



    Merhaba,

    Arkadaslar bu konuda yardýmcý olursanýz cok sevinirim. Lutfen bu konuda gercekten yardýma ihtiycým var. Cok tesekkur ederim....


    Layer 1 active hale getiremiyorum alcatel hdsl 1512 modem ile as5350 bagli birbirine,
    ayný zamanda "sh controllers e1 3/2" yaptýgýmda e1 3/2 down gorunuyor.
    "sh isdn status"
    as5350#sh isdn status
    Global ISDN Switchtype = primary-net5
    ISDN Serial3/2:15 interface
    dsl 1, interface ISDN Switchtype = primary-net5
    Layer 1 Status:
    DEACTIVATED
    Layer 2 Status:
    TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
    Layer 3 Status:
    0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask: 0x00000000
    Number of L2 Discards = 0, L2 Session ID = 98
    Total Allocated ISDN CCBs = 0ONT>
    "sh controllers e1 3/2 "

    as5350#sh controllers e1 3/2
    E1 3/2 is down.
    Applique type is Channelized E1 - balanced
    Far End Block Errors Detected
    Receiver has loss of signal.
    alarm-trigger is not set
    Version info of slot 3: HW: 519, PLD Rev: 1
    Framer Version: 0x8
    Manufacture Cookie Info:
    EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x05,
    Board Hardware Version 2.7, Item Number 73-5267-03,
    Board Revision A0, Serial Number JAE08083CU8,
    PLD/ISP Version <unset>, Manufacture Date 22-Feb-2004.
    Framing is CRC4, L! ine Code is HDB3, Clock Source is Line.
    Data in current interval (273 seconds elapsed):
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 273 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 273 Unavail Secs
    Data in Interval 1:
    344020 Line Code Violations, 61147 Path Code Violations
    1 Slip Secs, 660 Fr Loss Secs, 84 Line Err Secs, 0 Degraded Mins
    1 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 693 Unavail Secs
    Data in Interval 2:
    226022 Line Code Violations, 29065 Path Code Violations!
    0 Slip Secs, 229 Fr Loss Secs, 37 Line Err Secs, 0 Degraded Mins
    5 Errored Secs, 3 Bursty Err Secs, 17 Severely Err! Secs, 239 Unavail Secs
    Data in Interval 3:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 897 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 897 Unavail Secs
    Data in Interval 4:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 5:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 6:
    0 Line Code Violati! ons, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 7:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr L! oss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 8:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 9:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Sec! s, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 10:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 11:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 900 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 12:
    16384908 Line Code Violations, 196475 Path Code Violations
    244 Slip Secs, 850 Fr Loss Secs, 399 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs! , 0 Severely Err Secs, 900 Unavail Secs
    Data in Interval 13:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 148 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 148 Unavail Secs
    Data in Interval 14:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 15:
    0 Line Code Violat! ions, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 16:
    0 Li! ne Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 17:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely E! rr Secs, 0 Unavail Secs
    Data in Interval 18:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 19:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err ! Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 20:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 F! r Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 21:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 22:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Una! vail Secs
    Data in Interval 23:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 24:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 25:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    &nbs! p; 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Data in Interval 26:
    0 Line Code Violations, 0 Path Code Violations
    0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
    0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
    Total Data (last 26 15 minute intervals):
    16954950 Line Code Violations, 286687 Path Code Violations,
    245 Slip Secs, 9984 Fr Loss Secs, 520 Line Err Secs, 0 Degraded Mins,
    6 Errored Secs, 3 Bursty Err Secs, 17 Severely Err Secs, 10077 Unavail Secs
    as5350#

  2. #2
    İsmail CAN Guest

    Standart RE: controller e1 3/2 down problem cozuldu

    Merhabalar

    suan problem cozuldu. ilk aradıgımda hersey normal gorunuyordu sonra baska bir yeri aradim ordan rica ettim adamlar aynı yere bagladılar ve her seferinde de farkli biri cikiyor karsima bayagi kalabaliklar herhalde:) neyse anlattim derdimi nazikce yalvara yalvara bakti aksam bizden sinyal alamayinca alarm vermis ve kapatmislar.
    Yardımlarınız icin tesekkurler. Arkadaslar baska birsey danısabilirmiyim.
    Suan bize 2314500-2314549 kadar toplam 50 hat acilmis. gw uzerindeki config asagidaki gibi mi olcak? tesekkurler

    dial-peer voice 1 pots
    incoming called-number 23145T
    application prepaid
    port 3/2:D

    dial-peer voice 2 voip
    destination pattern .T
    session target ras
    dtmf-relay h245-signal h245-alphanumeric
    codec g729r8 bytes 40


    YAVUZ TEMIZKAN <[email protected]> wrote:


    v\:* {behavior:url(#default#VML);}o\:* {behavior:url(#default#VML);}w\:* {behavior:url(#default#VML);}.shape {behavior:url(#default#VML);}
    Gece kapattıysan onlar hattan AIS hata mesajı aldıkları için kapatmışlardır.

    Hattı normal görüyor olmaları mümkün değil senin tarafını down görüyor olmaları lazımJ

    Önerim hatta loop verdirmen. Telekom loopu görüyorsa onların tarafında sorun yoktur

+ Konuyu Cevapla

Bu Konuyu Paylaşın !

Bu Konuyu Paylaşın !

Yetkileriniz

  • Konu Acma Yetkiniz Yok
  • Cevap Yazma Yetkiniz Yok
  • Eklenti Yükleme Yetkiniz Yok
  • Mesajınızı Değiştirme Yetkiniz Yok