Re: [uanog] Как понять какой received clock на Serial ...

День добрый. Боюсь, что никак. :( Некоторые контроллеры выдают клоки, а некоторые - нет. Например: M4T: show controller: PAS unit 0, subunit 0, f/w version 1-45, rev ID 0x2800001, version 3 idb = 0x6412FBD4, ds = 0x64130CBC, ssb=0x64131078 Clock mux=0x0, ucmd_ctrl=0xC, port_status=0x74 Serial config=0x8, line config=0x200 maxdgram=1608, bufpool=78Kb, 120 particles DCD=up DSR=up DTR=up RTS=up CTS=up line state: up cable type : V.35 DTE cable, received clockrate 2047212 On Fri, 29 Feb 2008, Yury Yaroshevsky wrote:

Date: Fri, 29 Feb 2008 15:30:11 +0200 From: Yury Yaroshevsky To: UANOG Subject: [uanog] [UTF-8] Как понять какой received clock на Serial ...

Добрый день.

Столкнулся с проблемкой.

Есть клиент, включенный на необслуживаемой площадке по Serial. Скорость которая выставлена на модема - не известна. Площадка далеко ....

Как можно выудить о clock получаемом с модема из :

RA1#sh controllers serial 0/0/1 Interface Serial0/0/1 Hardware is GT96K DTE V.35idb at 0x46037DC8, driver data structure at 0x4603A0D4 wic_info 0x4603A700 Physical Port 0, SCC Num 0 MPSC Registers: MMCR_L=0x000304C0, MMCR_H=0x00000000, MPCR=0x00000100 CHR1=0x00FE007E, CHR2=0x00000000, CHR3=0x0000064A, CHR4=0x00000000 CHR5=0x00000000, CHR6=0x00000000, CHR7=0x00000000, CHR8=0x00000000 CHR9=0x00000000, CHR10=0x00001000 SDMA Registers: SDC=0x00002201, SDCM=0x00000080 CRDP=0x0F844E30, CTDP=0x0F8607E0, FTDB=0x0F8607E0 Main Routing Register=0x77770000 BRG Conf Register=0x00480000 Rx Clk Routing Register=0x00008888 Tx Clk Routing Register=0x00009999 GPP Registers: Conf=0x50055600, Io=0x50055600, Data=0xE7FBFBFB, Level=0x18181818 TDM FPGA Registers: vmcr[0] = 0x00034040, vmcr[1] = 0x00034000, vmcr[2] = 0x00000000, vmcr[3] = 0x00000000 ntrcr0 = 0x00000000, ntrcr1 = 0x00000000 tdmcr = 0x0000006A, labcr = 0x00000000, tpllr_cr = 0x00000000 nhr = 0x66660100, isr = 0x0000FFFF, imr = 0x00000000 1644 input aborts on receiving flag sequence 0 throttles, 0 enables 19 overruns 0 transmitter underruns 0 transmitter CTS losts 13277180 rxintr, 13777753 txintr, 0 rxerr, 0 txerr 22387151 mpsc_rx, 0 mpsc_rxerr, 58 mpsc_rlsc, 1668 mpsc_rhnt, 22385543 mpsc_rfsc 29 mpsc_rcsc, 0 mpsc_rovr, 0 mpsc_rcdl, 0 mpsc_rckg, 0 mpsc_bper 0 mpsc_txerr, 8516770 mpsc_teidl, 0 mpsc_tudr, 0 mpsc_tctsl, 0 mpsc_tckg 0 sdma_rx_sf, 0 sdma_rx_mfl, 19 sdma_rx_or, 1644 sdma_rx_abr, 48 sdma_rx_no 0 sdma_rx_de, 0 sdma_rx_cdl, 2271 sdma_rx_ce, 0 sdma_tx_rl, 0 sdma_tx_ur, 0 sdma_tx_ctsl 0 sdma_rx_reserr, 0 sdma_tx_reserr 0 rx_bogus_pkts, rx_bogus_flag FALSE 0 sdma_tx_ur_processed

Было мнение что это прольет свет:

RA1#sh controllers serial 0/0/1 | inc Clk Rx Clk Routing Register=0x00008888 Tx Clk Routing Register=0x00009999

Только получасовое рассматривание документации и output debugger пока результатов не дает. :(

Вот что пишет Output Debugger:

INFO: The show controller serial command does not enable you to view the line speed of the link. At the microcode level, the controller chipset takes the input of the received clock from the DCE/CSU device. The controller chipset then feeds the input back for data transmission. This action is transparent to the IOS. In order to inform the IOS about the real speed of the interface, use the bandwidth interface configuration command. Use this value to calculate the proper amount of queues or bandwidth that you require, for example, WRED, or custom queue calculation. Note: In order to troubleshoot serial interfaces further, paste the output of the show interfaces serial command to the Output Interpreter.

Какие будут советы? =================================================================== uanog mailing list. To Unsubscribe: send mail to majordomo@uanog.kiev.ua with "unsubscribe uanog" in the body of the message

-- WB, Maks Nefedchenko NM17-RIPE