[uanog] Re: RE: Re: cisco 3620

10 Jan 2006

      Покажите sh isdn sta
Хотя уже видно, что не поднимается layer 2.

Значит проблема либо с e1 контроллером у Вас, либо стоит лупбек на 
удаленной стороне, либо на удаленной стороне надо поменять network/user 
side.

On Tue, 10 Jan 2006, Vitaly Puchkov wrote:
...
Date: Tue, 10 Jan 2006 15:15:33 +0200
From: Vitaly Puchkov 
Reply-To: uanog@uanog.kiev.ua
To: uanog@uanog.kiev.ua
Subject: [uanog] Re: RE: Re: cisco 3620
Здесь какую-то ошибку написало
cisco-36(config)#contr e1 0/0
cisco-36(config-controller)#no shut
cisco-36(config-controller)#exit
cisco-36(config)#
Jan 10 13:11:39.690: %CONTROLLER-5-UPDOWN: Controller E1 0/0, changed state 
to u
p
Jan 10 13:11:39.722: ISDN Se0/0:15 EVENT: service_queue_from_physical_layer: 
Rec
vd L1 prim 1 state is 3
Jan 10 13:11:39.722: ISDN Se0/0:15 **ERROR**: 
service_queue_from_physical_layer:
controller state isn't up, and got ISDN_PH_ACT_IND
Jan 10 13:11:39.722: %CSM-5-PRI: add ISDN at slot 0, unit 0, channel 15 with 
ind
ex 0
Jan 10 13:11:39.722: ISDN Se0/0:15 EVENT: isdn_pri_t1_state_change: setting 
Stat
e to 4
Jan 10 13:11:39.726: ISDN Se0/0:15 EVENT: service_queue_from_physical_layer: 
Rec
vd L1 prim 1 state is 3
Jan 10 13:11:39.726: ISDN Se0/0:15 EVENT: isdn_pri_t1_state_change: setting 
Stat
e to 4
Jan 10 13:11:39.730: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Jan 10 13:11:39.730: ISDN Se0/0:15 EVENT: service_queue_from_physical_layer: 
Rec
vd L1 prim 1 state is 1
Jan 10 13:11:39.734: ISDN Se0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Jan 10 13:11:39.742: ISDN Se0/0:15 Q921: User RX <- BAD FRAME(0x00017F)
Jan 10 13:11:40.734: ISDN Se0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Jan 10 13:11:40.738: ISDN Se0/0:15 Q921: User RX <- BAD FRAME(0x00017F)
----- Original Message ----- From: "maks nefedchenko" 
To: 
Sent: Tuesday, January 10, 2006 3:07 PM
Subject: [uanog] Re: RE: Re: cisco 3620
Сделайте пожалуйста:
1. conf t
contr e1 x/x
shut
2. deb isdn q921
deb isdn q931
deb isdn ev
ter mon
3. conf t
contr e1 x/x
no shut
И покажите _текущий_ конфиг контроллера, сигнального сериала и isdn..
On Tue, 10 Jan 2006, Vitaly Puchkov wrote:
...
Date: Tue, 10 Jan 2006 14:51:41 +0200
From: Vitaly Puchkov 
Reply-To: uanog@uanog.kiev.ua
To: uanog@uanog.kiev.ua
Subject: [uanog] Re: RE: Re: cisco 3620
Все меняе, все слушает. ISDN подыматся не хочет.
----- Original Message ----- From: "maks nefedchenko" 
To: 
Sent: Tuesday, January 10, 2006 2:44 PM
Subject: [uanog] Re: RE: Re: cisco 3620
On Tue, 10 Jan 2006, Vitaly Puchkov wrote:
...
Date: Tue, 10 Jan 2006 14:32:41 +0200
From: Vitaly Puchkov 
Reply-To: uanog@uanog.kiev.ua
To: uanog@uanog.kiev.ua
Subject: [uanog] Re: RE: Re: cisco 3620
Это еще что такое ?
Ой.
router#sh ver | i IOS
IOS (tm) 3600 Software (C3640-I-M), Version 12.2(6c), RELEASE SOFTWARE 
(fc1)
router#conf t
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#int se0/0:15
router(config-if)#isdn protocol-emulate ?
 network  ISDN protocol emulation network side
 user     ISDN protocol emulation user side (default)
...
----- Original Message ----- From: "&y0" 
To: 
Sent: Tuesday, January 10, 2006 2:08 PM
Subject: [uanog] RE: Re: cisco 3620
...
Пробовал менять нетворк/юзер парт на своей стороне?
-=.*.=- AO618-RIPE -='x'=-
-----Original Message-----
From: owner-uanog-outgoing@uanog.kiev.ua
[mailto:owner-uanog-outgoing@uanog.kiev.ua] On Behalf Of Vitaly Puchkov
Sent: Tuesday, January 10, 2006 1:56 PM
To: uanog@uanog.kiev.ua
Subject: [uanog] Re: cisco 3620
Перемычки не помогли.
debug isdn error - ничего не пишет
debug isdn event is             ON.
cisco-36#
Mar  1 00:07:38.460: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:07:42.468: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:07:47.468: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:07:51.476: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:07:56.476: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:00.484: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:08:05.484: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:09.492: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:08:14.492: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:18.500: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:08:23.500: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:27.508: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:08:32.508: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:36.512: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
Mar  1 00:08:41.516: ISDN Se0/0:15 EVENT: Pri_Activate_L2: states = 4, 4
Mar  1 00:08:45.524: ISDN Se0/0:15 EVENT: CCPRI_Go: received NL_REL_IND
----- Original Message ----- From: "Alexandre Snarskii" 

To: 
Sent: Tuesday, January 10, 2006 1:39 PM
Subject: [uanog] Re: cisco 3620
...
On Tue, Jan 10, 2006 at 01:28:08PM +0200, Dmitry A.Deineka wrote:
...
Vitaly Puchkov пишет:
>Не подходит. Привозили на другую площадку где стоит и работает 
>AS5300,
>там тоже не заводится.
>
лупбэк на кошке сделай (провода скрути). порт на кошке поменяй, если у
тебя там NM-1FE2CE1. дебаг посмотри, наконец. Что в дебаге контроллера 
и
ISDN ?
Кстати, если там NM-*CE1 - то там на модуле есть джампер
balanced/unbalanced.
Попробуй еще его поиметь в разных позициях.
У меня как-то было, что по доке - он в unbalanced, телефонисты дают
unbalanced, и не живет.. Переставил в balanced - зажило.
...
>----- Original Message ----- From: "Dmitry A.Deineka" 
>To: 
>Sent: Tuesday, January 10, 2006 1:19 PM
>Subject: [uanog] Re: cisco 3620
>
>
>>Кстати,
>>http://www.opennet.ru/openforum/vsluhforumID6/7867.html
>>
>>1) Проверь лупбэками порты и физику
>>2) Попроси на другой порт тебя повесить
>>3) Проверить, что тебе действительно дают сигнализацию в 15 тс.
>>
>>Да и на дебаг посмотри.
--
  Dmitry A.Deineka                DAD1-UANIC  DD518-RIPE
  iTL Company, Kharkov UA         phone: +380 57 7630001
  http://www.itl.ua               fax:   +380 57 7630004
===================================================================
uanog mailing list.
To Unsubscribe: send mail to majordomo@uanog.kiev.ua
with "unsubscribe uanog" in the body of the message
===================================================================
uanog mailing list.
To Unsubscribe: send mail to majordomo@uanog.kiev.ua
with "unsubscribe uanog" in the body of the message
===================================================================
uanog mailing list.
To Unsubscribe: send mail to majordomo@uanog.kiev.ua
with "unsubscribe uanog" in the body of the message
===================================================================
uanog mailing list.
To Unsubscribe: send mail to majordomo@uanog.kiev.ua
with "unsubscribe uanog" in the body of the message
===================================================================
uanog mailing list.
To Unsubscribe: send mail to majordomo@uanog.kiev.ua
with "unsubscribe uanog" in the body of the message
-- 
Maks Nefedchenko
Viaduk-Telecom, Inc.
NM17-RIPE