Cisco WT-2750 Multipoint Broadband Wireless System FAQ

Transcription

1 Cisco WT-2750 Multipoint Broadband Wireless System FAQ 목차 소개일반컨피그레이션 - 헤드엔드가입자단위 (SU) 관련정보 소개 이문서에는 Cisco WT-2750 Multipoint Broadband Wireless System 에대한자주묻는질문 (FAQ) 이포함되어있습니다.Multipoint Broadband Wireless 네트워크의구성요소다이어그램은하위채널이란무엇입니까? 를참조하십시오. 질문합니다. 문서규칙에대한자세한내용은 Cisco 기술팁표기규칙을참고하십시오. 일반 Q. Multipoint Broadband Wireless System 에필요한구성요소는무엇입니까? A. 헤드엔드 (HE): Cisco ubr7223/7246/7246vxr Universal Broadband 라우터 WT-2751 Multipoint Headend Line Card - 각 HE에대해최대 4개, 최대 1024명의동시사용자지원 WT-2781 Multipoint Quad Power Feed Panel - 최대 2개의라인카드용 1개 전원공급장치 (-48VDC) HE 트랜스버터 (ODU) - 다양성사용여부에따라라인카드당하나또는두개 HE 듀플렉서 - ODU마다하나씩참고 : 설치된듀플렉서의방향은컨피그레이션에서전송 (TX) 높음또는수신 (RX) 고주파수를결정합니다. 안테나 - 무지향성또는섹터화됨 피뢰자 SU( 가입자단위 ): Cisco 2600/3600 Series 라우터 (2610, 2611, 2612, 2613, 2620, 2621, 3620, 3640, 3661, 3662) WT-2755 NM(Multipoint Subscriber Network Module) 참고 : Cisco 3660 라우터를제외하고라우터의전원이꺼진경우 NM을설치해야합니다. DC Power Injector(-48VDC, 고전원 ODU의경우 + 24VDC, 표준전원 ODU의경우 ), 전원공급

2 장치포함 SU Transverter(ODU) - 다양성을사용하는경우 2개필요안테나와통합되거나통합되지않은상태에서높은전원또는표준전원공급참고 : 다양성안테나는 RX에만적용됩니다. SU 방향안테나 ( 통합 ODU를사용하지않는경우 ) 피뢰자 Q. Point-to-Multipoint 네트워크는일반적으로어떻게설계됩니까? 슈퍼셀 : 직경최대 20마일 ( 반경 10마일 ) 싱글 HE 미니셀 : 지름 4~10마일 ( 반경 2~5마일 ) 주파수재사용가능 마이크로셀 : 지름 (1마일반경 ) 최대 2마일SU는더낮은 TX 전원을사용할수있음지정된영역내에서최대 SU 수허용빈도재사용허용 Q. 이시스템에사용되는주파수대수는무엇입니까? MMDS: GHz MDS: GHz( 업스트림에만사용 ) ETSI: GHz(ODU는 2001년하반기제공예정 ) U-NII: GHz(ODU는 2001년 1/4분기에제공예정 ) Q. Cisco WT-2750 Multipoint Broadband Wireless System 에서사용하는변조체계는무엇입니까? A.64QAM over Vofdm(Vector Orthogonal Frequency Division Multiplexing) Q. VOFDM(Vector Orthogonal Frequency Division Multiplexing) 이란무엇이며, VOFDM 이그토록매력적인이유는무엇입니까? A. VOFDM 은멀티경로현상즉, 전자파전송에서실제구축이점에대한핵심억제력을활용합니다.VOFDM 기술은수신끝에서여러신호를조합하여전송신호강도를높입니다.VOFDM 은전반적인무선시스템성능, 링크품질및가용성을향상시킵니다. 또한 VOFDM 은 EOOF(Line-Of-Sight) 전송을통해통신사업자의시장범위를크게확대합니다. Q. 최대커버리지범위는얼마입니까? A. 다양한기성안테나설계에따라 3, 4, 6 섹터설계를선택할수있습니다. Q. OOB 전송이란무엇입니까? A. 비가시성전송의범위범위는다음매개변수에따라다릅니다. 경로손실가정 - 전송경로를따라손실되는신호수입니다. 링크신뢰성및가용성요구사항 - 무선링크를통해보장해야하는 9대서비스공급자의수가얼마나됩니까? CPE(Customer Premises Equipment) ODU 전송전원 - CPE 끝의표준전원 ODU 또는고전원 ODU입니다. 안테나게인 - CPE 끝에서사용되는안테나유형입니다.

3 Channelization and performance requirement( 채널및성능요구사항 ) - 각부문에필요한채널및성능유형 수신안테나수 - 1 또는 2입니다. WT-2750 Multipoint Broadband Wireless System은고게인안테나가있는표준전원 ODU를통해각 CPE에대해 2개의안테나 /ODU를사용하여 6마일, 단일안테나 /ODU를통해 3마일 (3마일) 의비손실신호 (LOS) 전송을달성할수있습니다. 단, 99.9% 링크가용성요구사항을충족하며 6MHz 채널다운스트림및각업스트림섹터에대해일반경로의 3MHz 채널을사용합니다. Q. HE(Headend) 및 SU(Subscriber Unit) 의중간빈도 (IFS) 는무엇입니까? 그 :324MHz TX, 420MHz RX CPE:330MHz TX, 426MHz RX Q. 현재어떤 Cisco IOS 릴리스가 Multipoint Broadband Wireless System 을지원합니까? 12.1(3)XQ1 12.1(3)XQ2 12.1(5)XM 12.2(1)T(2001년 2월 /3월제공 ) 연결된마이크로코드 Q. 어떤다운스트림주파수대역폭이허용됩니까? 이거바꿀수있나요? A. 6MHz, 3MHz, 1.5MHz 대역폭이허용됩니다. 이컨피그레이션을허용하지않는 RF(Radio Frequency) 변수가없는경우 HE 라인카드는단일채널 6MHz 폭을사용하도록구성됩니다. Q. 구성할수있는서로다른업스트림주파수대역폭은무엇입니까? A. 대역폭은 6MHz, 3MHz 및 1.5MHz 입니다. 서브채널화가가능하므로이러한채널화체계각각에대한조합을사용할수있습니다. 예를들어업스트림포트 3 개를사용하는경우 3MHz 에대해업스트림세트 1 개를, 1.5MHz 에대해나머지 2 개를설정할수있습니다. 이러한조합으로총 6MHz 를초과할수없습니다. Q. 이시스템의데이터처리량은어떻게됩니까? 다운스트림 대역폭 (Mhz) 처리량 (Mbps) 다중경로견고성 버스트길이 표준중간 표준중간 표준중간 표준중간 표준중간 표준중간

4 높음 중간 높음 중간 높음 중간 표준 중간 표준 중간 표준 중간 높음 중간 높음 중간 높음 중간 업스트림 대역폭 (Mhz) 처리량 (Mbps) 다중경로견고성 버스트길이 표준중간 표준중간 표준중간 높음중간 높음중간 높음중간 높음중간 높음중간 높음중간 Q. 하위채널이란무엇입니까? A. 하위채널은 6MHz, 3MHz 또는 1.5MHz 블록으로 6MHz 폭채널입니다. 하위채널을사용하면무선모뎀카드의여러업스트림포트를사용할수있습니다. 특정하위채널은사용할수있는 6MHz 대역내에배치됩니다. 모든하위채널에서사용하는총대역폭은해당채널에대해 6MHz 를초과할수없습니다. 예를들어 6MHz 인하위채널 1 만사용하는경우업스트림포트를하나만사용할수있습니다. 여러업스트림포트를사용하려는경우하위채널 2~7 에서는 3MHz 또는 1.5MHz 의대역폭할당을허용합니다. 하위채널 2~7 을사용하여변조프로파일을구성합니다. 그림 1 - 하위채널맵다이어그램

5 컨피그레이션 - 헤드엔드 Q. HE 라우터의샘플컨피그레이션은어떻게됩니까? A. 샘플구성은다음과같습니다. radio modulation-profile 1 bandwidth 6.0 throughput 22.0 multipath-robustness standard burst-length medium radio modulation-profile 2 bandwidth 6.0 throughput 19.0 multipath-robustness high burst-length medium!!--- To view acceptable inputs for these modulation profiles, use the!--- show radio capability modulation-profile command.!--- Change the throughput setting from high to medium to employ more!--- multipath-robustness, and change the throughput setting from medium! --- to low to employ more forward error correction (FEC) coding. interface Radio4/0 point-to-multipoint ip address secondary!--- IP address network used for hosts behind SUs. ip address !--- IP address network used for the SUs. no keepalive radio alc interval 96!--- Airline Control (ALC) ensures the TRP at the HE is maintained!--- over time, through power measurements of all subscribers!--- several times each second. radio cable-loss auto!--- Usually set to "auto." radio transmit-power 20!--- Acceptable range for Multichannel Multipoint Distribution Service (MMDS)!--- is 15 to 38 dbm. For Unlicensed National Information Infrastructure!--- (UNII), it is -5 to 15 dbm. radio upstream frequency width 6.0 radio upstream 0 subchannel 1 modulation-profile 2!--- Refer to modulation-profile and sub-channel chart above. radio upstream 0 target-receive-power -65 no radio upstream 0 shutdown no radio upstream 1 targetreceive-power radio upstream 1 shutdown no radio upstream 2 target-receive-power radio upstream 2 shutdown no radio upstream 3 target-receive-power radio upstream 3 shutdown radio downstream frequency width 6.0!--- Default width is 6 MHz. radio downstream subchannel 1 modulation-profile 1!--- Refer to the modulation-profile and sub-channel chart. radio dhcpgiaddr policy radio helper-address !--- IP address of the DHCP server, if you do not use DHCP on HE router!--- (see the next question). radio su-onoff-trap interval 600 Q. TOD, TFTP 및 DHCP 를모두하나로실행하도록 HE 를어떻게구성합니까?

6 A. 이구성을사용할때최신 "T" 코드가있는지확인하십시오.DISCOVER 패킷이다른컴퓨터에 " 도움 " 될필요가없으므로패킷이 HE 에있으므로컨피그레이션에서라디오헬퍼주소명령을활성화하지마십시오. service udp-small-servers max-servers no-limit! radio time-server! ip dhcp pool modems-c3!--- Modems-c3 is just a string.! network bootfile p2mp.cm nextserver !--- Radio interface.! default-router option 7 ip option 4 ip option 2 hex ! interface Radio3/0 point-to-multipoint ip address ! tftp server slot0:p2mp.cm alias p2mp.cm!--- Use this statement when.cm file is stored in "flash,"!--- not in the TFTP server..cm 파일을플래시에넣으려면다음단계를완료합니다. 1. tftp slot:0을복사하고 Enter 키를누릅니다. 2. 파서가원격호스트의이름을쿼리할때 TFTP 서버의주소를입력합니다. 3. 파서가소스파일이름을쿼리할때.cm 파일이름을입력하고 Enter 키를누릅니다. 또한 TFTP 서버대신 HE에있는 DOCSIS 컨피그레이션파일을구성할수있습니다. radio config-file p2mp.cm cpe max 4 service-class 1 priority 2 service-class 1 max-upstream 128 service-class 1 max-downstream 1000 timestamp 참고 :.cm 파일이없으므로 "tftp server slot0:p2mp.cm alias p2mp.cm" 명령문이필요하지않습니다. 구성내에상주합니다. Q. 기본프라이버시는어떻게구성합니까? A. 기본프라이버시를구성하려면다음단계를완료합니다. 1. HE 및 SU에 K1 이미지를로드합니다. 2. 구성파일편집기를사용하여 DOCSIS 구성파일을엽니다. 3. Class of Service Group 탭에서 Expand를클릭합니다. 4. Class-of-Service Privacy Enable(0/1)(Class-of-Service 프라이버시활성화 ) 아래에서 1을활성화합니다.1 필드기본적으로이값은 0이므로값을 1로변경합니다. 5. DOCSIS 구성파일을 TFTP 부트파일에저장합니다. 이파일은 HE의 FE(Fast Ethernet) 포트에연결된 TFTP 서버에있습니다. 재부팅후 SU는위의매개변수를사용하여새 DOCSIS 구성파일을로드합니다. 6. SU는 HE와 BPI(Baseline Privacy Interface) 를협상합니다.show radio subscriber 명령을사용하여 SU가 "online" 대신 "online(pt)" 으로등록되었는지확인합니다. "(PT)" 가표시되지않으면 SU 및 HE에 K1 이미지가있는지확인하고.cm 파일에서 "Class-of-Service Privacy" 가 1로활성화되었는지확인합니다.

7 Q. DOCSIS 구성파일과 IOS 구성파일의차이점은무엇입니까? A. DOCSIS 구성파일은이진파일이며, ISP 가프로비저닝하는것 ( 예 : Maximum Downstream and Upstream Rates, Maximum Upstream Burst Rate, Class of Service 또는 Baseline Privacy, MIB 및기타매개변수 ) 에따라무선 SU 가온라인상태가되도록하는매개변수가있습니다. Cisco IOS 컨피그레이션파일은 DOCSIS 컨피그레이션파일에서다운로드할수있는액세스목록, 비밀번호, NAT 컨피그레이션과같은특정컨피그레이션을포함할수있는텍스트파일입니다. Q. 헤드엔드를모니터링하고문제를해결하는데유용한명령은무엇입니까? show radio interface slot number/port number [{if rf}] show radio subscribers - 모든라디오가입자및현재상태를표시합니다. show radio flap-list - 무선모뎀카드의무선플랩목록을표시합니다. show interfaces radio slot number/port number hist-data SNR(signal-to-noise ratio) 을표시합니다. 출력을보려면라디오인터페이스에히스토그램이구성되어있어야합니다.SNR을표시하는유일한명령입니다. show interfaces radio slot number/port number link-metrics - 특정기간동안링크의모든코드워드오류를표시합니다. show controller radio slot number/port number [{if rf}] 특정모뎀카드의특성전체또는일부를표시합니다. show controllers radio slot/downstream-port downstream downstream - 무선모뎀카드의다운스트림포트정보를표시합니다. show controllers radio slot/upstream-port upstream - 무선모뎀카드의업스트림포트정보를표시합니다. radio loopback local main if( 라디오루프백로컬 main if) - 라인카드에결함이있는지표시합니다. radio loopback local main rf - 카드와 ODU 사이에케이블문제가있는지표시합니다. Q: show radio subscriber 명령출력은어떤형태이며각열은무엇을의미합니까? Headend# show radio flap-list MAC AddressUpstreamInsHitMissCRCP-AdjFlapTime b4f.bf90Radio4/0/U Oct 3 17:34:23 A. HE 의 show radio flap-list 명령출력입니다. 플랩목록은이벤트탐지기이며, 이벤트가계산되는세가지상황은다음과같습니다. 삽입 적중횟수 실패참고 : 이출력의 P-Adj(Power-Adjustment) 열을무시합니다.P-Adj 열은 show cable flap-list 명령의케이블네트워크에만적용됩니다. 삽입 먼저, SU 에등록문제가있고재등록을반복적으로시도하는경우삽입과함께플랩을볼수있습니다.P-Adj 열은낮을수있습니다.SU 가두개의초기유지보수재등록사이의시간이 180 초미만이

8 면 " 삽입 " 과함께 " 플랩 " 을얻고플랩탐지기가이를셉니다. 다음과같은경우이기본값 180 초를변경할수있습니다. Headend(config)# radio flap-list insertion-time? < > Insertion time interval in seconds 적중 / 누락 둘째, 플랩탐지기는 "Miss" 다음에 "Hit" 을볼때플랩을셉니다. 이벤트탐지는 Flap 열에서만계산됩니다. 이러한폴링은 30 초마다전송되는 hello 패킷입니다."miss" 다음에 "miss" 가올경우 16 초동안매초마다폴링이전송됩니다.16 초전에 " 적중 " 이발생하면플랩이발생하지만 16 개의폴링에 " 적중 " 이발생하지않으면모뎀이오프라인으로전환되어초기유지관리를다시시작합니다.SU 가마지막으로다시온라인상태가되면 SU 가다시활성상태로삽입되므로 " 삽입 " 이표시됩니다. 연속누락이 6 개인경우플랩카운트가증가합니다. 원하는경우이기본값을변경할수있습니다. Headend(config)# radio flap miss-threshold? <1-12> missing consecutive polling messages 참고 : 현재 P-Adj 열은 Point-to-Multipoint 시스템에사용되지않습니다. Q. show run 명령외에어떤 TX 및 RX 주파수가구성되었는지보여주는명령은무엇입니까? 이명령에서제공하는다른중요한정보는무엇입니까? A. show controller r4/0 rf 명령은어떤 TX 및 RX 주파수가구성되었는지보여줍니다. 다음은샘플출력이며이출력에서살펴보아야할몇가지중요한사항입니다. Headend# show controller r4/0 rf RF ODU# 1 Hardware Identification Info: PIC code version: 0.15!--- This shows the point in call (PIC) code version that is!--- currently on the ODU.!--- This is important if you encounter problems with the ODU. NVS checksum 0x69 NVS version: 0.0 Card type: 0x10 Vendor name: cisco Part number: Board number: HW rev code: 03 Serial number: JAB041904BZ Date code: RF ODU# 1 Hardware Capability Info: Capability flag1: 0x9F Capability flag2: 0x2C RF Diversity Head: Tx/Rx Tx Blanking Capable: Yes RF Power Level Mode Capable: Yes RF Power Gain Mode Capable: Yes RF Loopback Capable: Yes Tx Predistortor Capable: No Antenna Alignment Capable: No PA Temp Sensor Capable: Yes Tx Spectral Inversion: No Rx Spectral Inversion: No Rx Blanking Capable: Yes Rx Gain Cal. Capable: Yes Variable Gain Info Available: No Duplexor Field Replaceble: Yes Max chan. BW: 6 Mhz Tx frequency bands: 1, step: 600 Khz min: Khz, max: Khz!--- These TX and RX values show the ODU bandpass.!--- With this information, you will know what center!--- frequencies are available for use. Rx frequency bands: 2, step: 600 Khz min1: Khz, max1: Khz min2: Khz, max2: Khz IF Tx freq: Khz!--- These are the IF, TX, and RX frequencies that you can measure!--- for verification purposes from the front of the board out of!--- the monitor port. IF Rx freq: Khz Freq reference: 24 Mhz Tx power range min: 15 dbm, max: 41 dbm, step: 1 dbm Tx fixed gain min: 0 db, max: 0 db, step: 0 db Rx fixed gain min: 0 db, max: 0 db, step: 0 db Tx var gain min: 48 db, max: 56 db, step: 1 * db Rx var gain min: 30 db, max: 36 db, step: 1 * db Temp. threshold low: 95 deg. C, high: 98 deg. C BW adjusted max tx pwr: full:0 dbm half:0 dbm quarter:0 dbm RF ODU# 1 Status: TX Frequency: Khz!--- These are the TX and RX frequencies that are actually!--- configured on the HE. RX Frequency: Khz TX Output Power: 20 dbm!--- As well as the output power that is configured on the HE. TX Cable Loss: 15 db Q. 히스토그램을구성하고그로부터데이터출력을얻으려면어떻게해야합니까? A. 히스토그램은라디오인터페이스에구성됩니다. 구성할수있는히스토그램에는여러가지유형이있습니다. 가장일반적으로사용되는것은 SINR(signal-to-interference plus noise ratio) 및 RF

9 RX Power 입니다. 사용가능한히스토그램중일부는다음과같습니다. radio histogram sinr-ant1 0 bin-range duration 5 tone average update 5 sum false width coarse radio histogram timing-offset 0 bin-range duration 5 update 5 sum false width coarse radio histogram rf-rx-power-ant1 0 bin-range duration 5 update 5 sum false width coarse radio histogram chan-delay-spread-ant1 0 bin-range 0 22 duration 5 update 5 sum false width coarse radio histogram power-amb 0 bin-range duration 5 update 5 sum false width coarse 라디오인터페이스에히스토그램이구성된경우 show interface slot number/port number hist-data <specific histogram> global 명령을사용하여이의데이터를볼수있습니다. 예를보려면다음질문을참조하십시오. Q. show interface radio slot number/port number hist-data 명령출력은일반적으로 HE 에서어떻게나타납니까? 참고 : 히스토그램출력을볼때최소값, 평균및최대값에주의하십시오. Headend# show interface r4/0 hist-data sinr-ant1 0 % Radio4/0 Histogram captured at 17:42:58 UTC Mon Jan % radio histogram sinr-ant1 0 % bin dur 5 tone ave up 5 sum f width c % min= avg= max=30.500!--- This is the SNR value for the wireless modem card. % [1*=100 events] captured 0 seconds remain % 0 MININT<=x<10 % 0 10<=x<14 % 0 14<=x<18 % 0 18<=x<22 % 0 22<=x<26 % 2 26<=x<30 * % 3 30<=x<34 * % 0 34<=x<38 % 0 38<=x<42 % 0 42<=x<46 % 0 46<=x<50 % 0 50<=x<MAXINT Headend# show interface r4/0 hist-data chan 0 % Radio4/0 Histogram captured at 17:58:21 UTC Mon Jan % radio histogram chan-delay-spread-ant1 0 % bin 0 22 dur 5 up 5 sum f width c % min=2.500 avg=2.500 max=2.500!--- You want channel delay spread to be minimal. % [1*=100 events] captured 0 seconds remain % 0 MININT<=x<0 % 5 0<=x<4 * % 0 4<=x<8 % 0 8<=x<12 % 0 12<=x<16 % 0 16<=x<20 % 0 20<=x<24 % 0 24<=x<28 % 0 28<=x<32 % 0 32<=x<36 % 0 36<=x<40 % 0 40<=x<MAXINT Headend# show interface r4/0 hist-data power-amb 0 % Radio4/0 Histogram captured at 17:59:16 UTC Mon Jan % radio histogram power-amb 0 % bin dur 5 up 5 sum f width c % min= avg= max= % [1*=100 events] captured 0 seconds remain % 0MININT<=x<-101 % 1-101<=x<-93 * % 0-93<=x<-85 % 0-85<=x<-77 % 0-77<=x<-69 % 0-69<=x<-61 % 0-61<=x<-53 % 0-53<=x<-45 % 0-45<=x<-37 % 0-37<=x<-29 % 0-29<=x<-21 % 0-21<=x<MAXINT Headend# show interface r4/0 hist-data rf-rx-power-ant1 0 % Radio4/0 Histogram captured at 17:58:37 UTC Mon Jan

10 % radio histogram rf-rx-power-ant1 0 % bin dur 5 up 5 sum f width c % min= avg= max= !--- These are good values. % [1*=100 events] captured 0 seconds remain % 0 MININT<=x<-100 % 0-100<=x<-84 % 0-84<=x<-68 % 5-68<=x<-52 * % 0-52<=x<-36 % 0-36<=x<-20 % 0-20<=x<-4 % 0-4<=x<12 % 0 12<=x<28 % 0 28<=x<44 % 0 44<=x<60 % 0 60<=x<MAXINT Headend# show interfaces r4/0 hist-data timing-offset 0 % Radio4/0 Histogram captured at 17:58:48 UTC Mon Jan % radio histogram timing-offset 0 % bin dur 5 up 5 sum f width c % min=-1 avg=0 max=0 % [1*=100 events] captured 0 seconds remain % 0MININT<=x<-10 % 0-10<=x<-8 % 0-8<=x<-6 % 0-6<=x<-4 % 0-4<=x<-2 % 4-2<=x<0 * % 10<=x<2 * % 02<=x<4 % 04<=x<6 % 06<=x<8 % 08<=x<10 % 010<=x<MAXINT Q. 링크의무선부분을트러블슈팅하기위해 HE 에서어떤디버그를사용할수있습니까? A. debug radio p2mp phy cwrlog radio - 이명령을사용하여가입자단위모뎀카드에대한 DSP( 디지털신호처리 ) 동기화를볼수있습니다. 가입자단위 (SU) Q. SU 라우터의샘플컨피그레이션은어떻게표시됩니까? interface Radio1/0 point-to-multipoint ip address docsis docsis boot admin 2 docsis boot oper 5 docsis mac-timer t radio cable-loss radio downstream saved channel subchannel 0!--- This is an optional parameter that can be added to save!--- the SU time from scanning the digital signal DS upon initialization. Q. 가입자단위를모니터링하고문제를해결하는데유용한명령은무엇입니까? show interfaces radio slot number/port number link-metrics - 특정기간동안링크의모든코드워드오류를표시합니다. show interfaces radio slot number/port number hist-data - 출력을보려면인터페이스에히스토그램이구성되어있어야합니다. show controllers 라디오슬롯번호 / 포트번호 특정모뎀카드의특성전체또는일부를표시합니다. show controllers radio slot number/port number if( 컨트롤러라디오슬롯번호 / 포트번호표시 ) - 지정된라디오인터페이스의 IF 하드웨어정보를표시합니다. radio loopback local main if( 라디오루프백로컬 main if) - NM에오류가있는경우표시됩니다.

11 radio loopback local main rf - 카드와 ODU 사이에케이블문제가있는경우표시합니다. 참고 : 이명령을실행하려면도터보드가있어야합니다. Q. show interfaces radio slot number/port number link-metrics 명령출력은어떻게표시됩니까? show interface radio 1/0 link-metrics Radio link metrics.collected from: 00:12:00 - Fri Dec to: 00:12:00 - Fri Dec Availability of the physical link: Available seconds(efs+es-ses):00:00:00: % Unavailable seconds (SES+SLS): 00:00:00: % Total : 00:00:00: % Error characteristics of the physical link: Error free seconds(efs): 00:00:00: % Errored seconds(cwerr>=1) (ES): 00:00:00: % Degraded seconds ( >CWerr>= %)(DS): 00:00:00: % Severely errored seconds (CWerr>= %)(SES): 00:00:00: % Sync Loss secondssls): 00:00:00: % Synchronization event counters: Initial Synchronization seconds: 00:00:19 Time since last successful synchronization :00:00:00 Time since last synchronization failure: 00:00:00 Synchronization attempts - Successful: 1 : Unsuccessful : 0 Recovery attempts- Medium effort : 0 : High effort : 0 Physical link data rates: Effective data rate (PHY payload bits/sec) :0 Efficiency (PHY payload bits/total bits): % Q. show interfaces radio slot number/port number hist-data 명령출력은일반적으로 SU 에서어떤모습입니까? 참고 : 히스토그램출력을볼때최소값, 평균및최대값에주의하십시오. Subscriber# show interfaces r1/0 hist-spec data sinr-ant1 % Radio1/0 Histogram captured at 02:01:59 UTC Mon Mar % radio histogram sinr-ant1 % bin dur 5 tone ave up 5 sum f width c % min= avg= max= % [1*=1100events] captured 0 seconds remain % 0MININT<=x<10 % 010<=x<14 % 014<=x<18 % 018<=x<22 % 022<=x<26 % <=x<30 ********************* % <=x<34 ***************************** % 034<=x<38 % 038<=x<42 % 042<=x<46 % 046<=x<50 % 050<=x<MAXINT

12 Subscriber# sh int r1/0 hist-data timing-offset % Radio1/0 Histogram captured at 02:01:59 UTC Mon Mar % radio histogram timing-offset % bin dur 5 up 5 sum f width c % min=-1 avg=0 max=1 % [1*=100 events] captured 0 seconds remain % 0MININT<=x<-10 % 0-10<=x<-8 % 0-8<=x<-6 % 0-6<=x<-4 % 0-4<=x<-2 % 287-2<=x<0 *** % 12230<=x<2 ************* % 02<=x<4 % 04<=x<6 % 06<=x<8 % 08<=x<10 % 010<=x<MAXINT Subscriber# sh int r1/0 hist-data rf-rx-power-ant1 % Radio1/0 Histogram captured at 02:01:59 UTC Mon Mar % radio histogram rf-rx-power-ant1 % bin dur 5 up 5 sum f width c % min= avg= max= % [1*=100 events] captured 0 seconds remain % 0MININT<=x<-100 % 0-100<=x<-84 % 0-84<=x<-68 % 0-68<=x<-52 % <=x<-36 ********************************************** % 0-36<=x<-20 % 0-20<=x<-4 % 0-4<=x<12 % 012<=x<28 % 028<=x<44 % 044<=x<60 % 060<=x<MAXINT Subscriber# sh int r1/0 hist-data chan-delay-spread-ant1 % Radio1/0 Histogram captured at 02:01:59 UTC Mon Mar % radio histogram chan-delay-spread-ant1 % bin 0 22 dur 5 up 5 sum f width c % min=2.500 avg=2.500 max=2.500 % [1*=100 events] captured 0 seconds remain % 0MININT<=x<0 % 45290<=x<4 ********************************************** % 04<=x<8 % 08<=x<12 % 012<=x<16 % 016<=x<20 % 020<=x<24 % 024<=x<28 % 028<=x<32 % 032<=x<36 % 036<=x<40 % 040<=x<MAXINT Q. SU 에서어떤디버그를사용하여무선링크문제를해결할수있습니까? debug radio p2mp phy cwrlog radio - 이명령을사용하여가입자단위모뎀카드에대한 DSP( 디지털신호처리 ) 동기화를볼수있습니다.

13 debug docsis mac [log] - DOCSIS MAC 실시간로그에의해생성된디버그메시지를표시합니다. Q. debug radio p2mp phy cwrlog 명령의출력은정상적인초기화상태에서어떻게표시됩니까? Subscriber Unit# 01:48:27: SU RFSM: STATE CHANGE standby_state ====> if_hw_reset_state 01:48:27: SU RFSM: Debug PIC Timeouts occurred=0 01:48:27: SU RFSM: Debug PIC NAKs occurred=0 01:48:28: SU RFSM: Resetting IF HW 01:48:28: SU RFSM: STATE CHANGE if_hw_reset_state ====> if_hw_read_version_state 01:48:28: SU RFSM: Default IF Unsolicited Msg Processing 01:48:28: IFHW: PIC unsolicited msg received - IDU PIC Reset Event 01:48:28: IFHW: PIC boot loader version=1, vendor ID=0 01:48:28: IFHW: IF PIC code version=0.10, eeprom version=0 01:48:28: IFHW: IF EEPROM Checksum=0x87 01:48:28 : SU RFSM: STATE CHANGE if_hw_read_version_state ====> if_hw_read_eeprom_state 01:48:28: SU RFSM: Reading IF HW EEPROM 01:48:28: SU RFSM: IF Hardware Cached EEPROM okay 01:48:28: SU RFSM: STATE CHANGE if_hw_read_eeprom_state ====> rf_hw_reset_state 01:48:28: SU RFSM: Default RF Resp. Processing 01:48:28: SU RFSM: Default DSP Resp Processing 01:48:28: SU RFSM: Default DSP Ind Processing 01:48:28: SU RFSM: Default DSP Ind Processing 01:48:28: SU RFSM: Resetting RF/ODU1 01:48:28: %LINK-3-UPDOWN: Interface Radio1/0, changed state to up!--- The line above is out of place. This line often appears here.!--- You can ignore this line. You can get stuck in this state!--- if for some reason the SU cannot communicate with the ODU. 01:48:29: SU RFSM: STATE CHANGE if_hw_reset_state ====> if_hw_read_version_state 01:48:29: IFHW: IF PIC code version=0.11, NVS major version=0 01:48:29: IFHW: PIC boot loader version=1, vendor ID=0 01:48:29: IFHW: IF NVS Checksum=0x9D 01:48:29: SU RFSM: STATE CHANGE if_hw_read_version_state ====> if_hw_read_eeprom_state 01:48:29: SU RFSM: Re-using cached IF NVS data 01:48:29: SU RFSM: STATE CHANGE if_hw_read_eeprom_state ====> rf_hw_reset_state 01:48:29: RFHW: Unsolicited PIC msg - ODU PIC Reset Event (opcode=0x1a state=0x0) 01:48:29: SU RFSM: STATE CHANGE rf_hw_reset_state ====> rf_hw_read_version_state 01:48:29: RFHW: RF/ODU1 PIC code version=0.30, NVS major version=0 01:48:29: RFHW: RF/ODU1 PIC boot loader version=255, vendor ID=0 01:48:29: RFHW: RF/ODU1 NVS Checksum=0x48 01:48:29: SU RFSM: STATE CHANGE rf_hw_read_version_state ====> rf_hw_read_eeprom_state 01:48:30: SU RFSM: Re-using cached RF/ODU1 NVS data 01:48:30: SU RFSM: STATE CHANGE rf_hw_read_eeprom_state ====> rf_hw_reset_state 01:48:35: SU RFSM: RF/ODU2 not detected/operational 01:48:35: SU RFSM: STATE CHANGE rf_hw_reset_state ====> if_hw_cable_comp_state 01:48:35: IFHW: Rx1 cable loss=1 db compensation=12 db 01:48:35: SU RFSM: STATE CHANGE if_hw_cable_comp_state ====> rf_hw_cable_comp_state 01:48:35: RFHW: Tx cable loss=2 db compensation=11 db 01:48:35: SU RFSM: STATE CHANGE rf_hw_cable_comp_state ====> if_hw_config_state 01:48:35: IFHW: IF Tx Gain=16 db 01:48:35: SU RFSM: STATE CHANGE if_hw_config_state ====> rf_hw_config_state 01:48:35: RFHW: RF/ODU1 Rx Fixed Gain=0 db, Rx Var Gain=15 db 01:48:35: RFHW: RF/ODU1 Tx Fixed Gain=0 db, Tx Var Gain=20 db 01:48:35: RFHW: RF/ODU1 Auto updating cached NVS (Max Tx Pwr) for Standard Power ODU 01:48:35: SU RFSM: STATE CHANGE rf_hw_config_state ====> loopback_state 01:48:35: SU RFSM: STATE CHANGE loopback_state ====> ds_candidate_selection_state 01:48:35: SU RFSM: STATE CHANGE ds_candidate_selection_state ====> ds_hardware_init_state 01:48:35: SU RFSM: STATE CHANGE ds_hardware_init_state ====> dspinit_powerup_state 01:48:35: SU RFSM: STATE CHANGE dspinit_powerup_state ====> dspinit_ping_state 01:48:35: SU RFSM: STATE CHANGE dspinit_ping_state ====> dspinit_config_state 01:48:35: SU RFSM: STATE CHANGE dspinit_config_state ====> dspinit_agc_config_state 01:48:35: SU RFSM: STATE CHANGE dspinit_agc_config_state ====> dspinit_ifrf_config_state 01:48:35: SU RFSM: STATE CHANGE

14 dspinit_ifrf_config_state ====> dspinit_down_sync_config_state 01:48:35: SU RFSM: DS RF Freq = Down sync carrier for DSP = :48:35: SU RFSM: DS RF Freq = Down sync carrier for DSP = :48:35: SU RFSM: STATE CHANGE dspinit_down_sync_config_state ====> dspinit_down_sync_state_config_state 01:48:35: SU RFSM: STATE CHANGE dspinit_down_sync_state_config_state ====> dsp_sync_state 01:48:36: SU RFSM: Received DSP SYNC IND (0) 01:48:36: SU RFSM: Received DSP SYNC IND (2) 01:48:36: SU RFSM: Received DSP SYNC IND (4) 01:48:36: SU RFSM: Received DSP SYNC IND (5) 01:48:36: SU RFSM: Received DSP SYNC IND (7) 01:48:37: SU RFSM: Received DSP SYNC IND (4) 01:48:37: SU RFSM: Received DSP SYNC IND (5) 01:48:37: SU RFSM: Received DSP SYNC IND (8) 01:48:37: SU RFSM: DSP SYNC PASSED 01:48:37: SU RFSM: STATE CHANGE dsp_sync_state ====> fec_sync_state!--- You have found a valid downstream signal at this state. 01:48:37: SU RFSM: SYNC Timer 01:48:37: SU RFSM: FEC Sync State, Viterbi Sync SUCCESS!--- If you get stuck here, try a shut command and then a no shut command!--- on the SU first. Sometimes this state has intermittent failures.!--- Try again if you receive a failure response. 01:48:37: SU RFSM: STATE CHANGE fec_sync_state ====> trc_sync_state 01:48:38: SU RFSM: TRC Sync State, Successful TRC LOCK 01:48:38: SU RFSM: STATE CHANGE trc_sync_state ====> maintenance_state!--- This is where the SU MAC chip starts to communicate with the HE MAC chip. 01:48:38: SU RFSM: Received Advance DS Channel Msg 01:48:43: SU RFSM: Default RF Resp. Processing 01:48:43: SU RFSM: UCD US bw is Full, adjusted max RF tx gain is 37 01:48:43: SU RFSM: Default RF Resp. Processing 01:48:43: SU RFSM: Default RF Resp. Processing 01:48:43: SU RFSM: DSPMSG_TX_POWER_ADJ [-128 db], IF[-4 db], RF[-13 db] 01:48:45: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[-1 db], RF[-13 db]!--- Lines like the one above appear often in the debug messages.!--- This line says that the transmit power is being adjusted up 3 db,!--- and after the adjustment, the IF gain is -1 db, and the RF gain!--- is -13 db. 01:48:48: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[02 db], RF[-13 db] 01:48:49: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[05 db], RF[-13 db] 01:48:50: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[-11 db] 01:48:51: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[-8 db] 01:48:52: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[-5 db] 01:48:53: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[-2 db] 01:48:54: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[01 db] 01:48:55: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[04 db] 01:48:56: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[07 db] 01:48:57: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[10 db] 01:48:58: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[13 db] 01:48:59: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[16 db] 01:49:00: SU RFSM: DSPMSG_TX_POWER_ADJ [3 db], IF[06 db], RF[19 db] 01:49:01: SU RFSM: DSPMSG_TX_POWER_ADJ [2 db], IF[06 db], RF[21 db] 01:49:02: SU RFSM: Set ALC State Resp: alcstate 1, IFloopMode 0, RFloopMode 1, Tmin_IF 35 01:49:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface Radio1/0, changed state to up Q. debug docsis mac log 명령의출력은정상적인초기화상태에서어떻게표시됩니까? Subscriber Unit# 01:24:34: CMAC_LOG_LINK_DOWN 01:24:34: CMAC_LOG_LINK_UP 01:24:34: CMAC_LOG_STATE_CHANGE ds_channel_scanning_state 01:24:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface Radio1/0, changed state to down 01:24:42: CMAC_LOG_DS_TUNER_KEEPALIVE 01:24:45: CMAC_LOG_UCD_MSG_RCVD 1 01:24:45: CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED 01:24:45: CMAC_LOG_STATE_CHANGE wait_ucd_state!--- This is where the SU mac chip starts to communicate with the HE MAC chip. 01:24:47: CMAC_LOG_UCD_MSG_RCVD 1 01:24:49: CMAC_LOG_UCD_MSG_RCVD 1 01:24:49: CMAC_LOG_ALL_UCDS_FOUND 01:24:49: CMAC_LOG_STATE_CHANGE wait_map_state 01:24:49: CMAC_LOG_FOUND_US_CHANNEL 1 01:24:51: CMAC_LOG_UCD_MSG_RCVD 1 01:24:51: CMAC_LOG_UCD_NEW_US_FREQUENCY :24:51: CMAC_LOG_SLOT_SIZE_CHANGED 8 01:24:51: CMAC_LOG_UCD_UPDATED 01:24:51: CMAC_LOG_MAP_MSG_RCVD 01:24:51: CMAC_LOG_INITIAL_RANGING_MINISLOTS 18 01:24:51: CMAC_LOG_STATE_CHANGE ranging_1_state

15 !--- In ranging 1 state, the SU sends a message to the HE, and then waits!--- for a response. If it doesn't get a response, it tries again a little!--- louder (3 db more transmit power each attempt). This continues until!--- there is a response, or until the SU has used up its tries. 01:24:51: CMAC_LOG_RANGING_OFFSET_SET_TO :24:52: CMAC_LOG_POWER_LEVEL_IS 0.0 dbmv(commanded) 01:24:52: CMAC_LOG_STARTING_RANGING 01:24:52: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:52: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:52: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:53: CMAC_LOG_T3_TIMER!--- The T3 timer sets how long the SU waits before it decides that the HE!--- didn't hear the last message. The line above indicates that this timer!--- has expired, and now the SU will try retransmitting. The T3 timer can be set to a!--- very large value, so if you want the SU to receive downstream but never transmit anything,!--- use the docsis mac-timer t command. 01:24:53: CMAC_LOG_POWER_LEVEL_IS 0.25 dbmv(commanded) 01:24:53: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:53: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:53: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:53: CMAC_LOG_T3_TIMER 01:24:53: CMAC_LOG_POWER_LEVEL_IS 0.50 dbmv(commanded) 01:24:53: CMAC_LOG_RANGING_BACKOFF_SET 2 01:24:53: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:53: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:53: CMAC_LOG_T3_TIMER 01:24:53: CMAC_LOG_POWER_LEVEL_IS 0.75 dbmv(commanded) 01:24:53: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:54: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:54: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:54: CMAC_LOG_T3_TIMER 01:24:54: CMAC_LOG_POWER_LEVEL_IS 1.0 dbmv(commanded) 01:24:54: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:54: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:54: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:54: CMAC_LOG_T3_TIMER 01:24:54: CMAC_LOG_POWER_LEVEL_IS 1.25 dbmv(commanded) 01:24:54: CMAC_LOG_RANGING_BACKOFF_SET 3 01:24:54: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:55: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:55: CMAC_LOG_T3_TIMER 01:24:55: CMAC_LOG_POWER_LEVEL_IS 1.50 dbmv(commanded) 01:24:55: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:55: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:55: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:55: CMAC_LOG_T3_TIMER 01:24:55: CMAC_LOG_POWER_LEVEL_IS 1.75 dbmv(commanded) 01:24:55: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:55: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:55: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:55: CMAC_LOG_T3_TIMER 01:24:55: CMAC_LOG_POWER_LEVEL_IS 2.0 dbmv(commanded) 01:24:55: CMAC_LOG_RANGING_BACKOFF_SET 0 01:24:56: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:56: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:56: CMAC_LOG_T3_TIMER 01:24:56: CMAC_LOG_POWER_LEVEL_IS 2.25 dbmv(commanded) 01:24:56: CMAC_LOG_RANGING_BACKOFF_SET 7 01:24:56: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:56: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:57: CMAC_LOG_T3_TIMER 01:24:57: CMAC_LOG_POWER_LEVEL_IS 2.50 dbmv(commanded) 01:24:57: CMAC_LOG_RANGING_BACKOFF_SET 1 01:24:57: CMAC_LOG_RNG_REQ_QUEUED 0 01:24:57: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:57: CMAC_LOG_RNG_RSP_MSG_RCVD 01:24:57: CMAC_LOG_RNG_RSP_SID_ASSIGNED :24:57: CMAC_LOG_ADJUST_RANGING_OFFSET 61 01:24:57: CMAC_LOG_RANGING_OFFSET_SET_TO :24:57: CMAC_LOG_ADJUST_TX_POWER 20 01:24:57: CMAC_LOG_STATE_CHANGE ranging_2_state!--- The HE got the ranging message from the SU, and sent a response.!--- Now the SU enters the ranging 2 state. In this state, it sends!--- messages to the HE, and the HE sends back messages!--- that instruct the SU on how to adjust its transmit power.!--- The distance between the HE and SU is also measured, and the!--- SU is given a ranging offset to account for propagation delay. 01:24:57: CMAC_LOG_RNG_REQ_QUEUED :24:58: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:58: CMAC_LOG_RNG_RSP_MSG_RCVD 01:24:58: CMAC_LOG_ADJUST_TX_POWER 20 01:24:58: CMAC_LOG_RANGING_CONTINUE 01:24:59: CMAC_LOG_RNG_REQ_TRANSMITTED 01:24:59: CMAC_LOG_RNG_RSP_MSG_RCVD 01:24:59: CMAC_LOG_ADJUST_TX_POWER 20 01:24:59: CMAC_LOG_RANGING_CONTINUE 01:25:00: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:00: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:00: CMAC_LOG_ADJUST_TX_POWER 20 01:25:00: CMAC_LOG_RANGING_CONTINUE 01:25:01: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:01: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:01: CMAC_LOG_ADJUST_TX_POWER 16 01:25:01: CMAC_LOG_RANGING_CONTINUE 01:25:02: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:02: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:02: CMAC_LOG_RANGING_SUCCESS 01:25:02: CMAC_LOG_STATE_CHANGE dhcp_state!--- In this example, the SU was told to increase its power in the!--- ranging 2 state. In total, the SU increased its gain by 20 db!--- during this state. This is an indication that the channel is!- -- very clean - the HE was able to demodulate the signal from the SU,!--- even when it was 20 db below the optimal signal level. If the!--- opposite occurs, and the SU is told to decrease the power in this!--- state, then that is an indication that the upstream!--- channel is not very clean. At this point, the state machine has!--- reached the dhcp_state. The SU sends an IP broadcast request!--- looking for a DHCP server. 01:25:02: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:02: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:03:

16 CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:03: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:04: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:04: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:05: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:05: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:06: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:06: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:07: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:07: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:08: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:08: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:09: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:09: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:10: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:10: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:11: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:11: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:12: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:12: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:13: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:13: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:14: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:14: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:15: CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS :25:15: CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS :25:15: CMAC_LOG_DHCP_ERROR_ACQUIRING_TOD_ADDRESS 01:25:15: CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS 01:25:15: CMAC_LOG_DHCP_TZ_OFFSET 0 01:25:15: CMAC_LOG_DHCP_CONFIG_FILE_NAME p2mp.cm 01:25:15: CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR 01:25:15: CMAC_LOG_DHCP_ERROR_ACQUIRING_LOG_ADDRESS 01:25:15: CMAC_LOG_DHCP_COMPLETE!--- Other parameters that are required by the SU are the TFTP server!--- address, the Time of Day (TOD) server address, the Time Zone (TX)!--- offset value and DHCP config file name (also known as the DOCSIS!--- config file). These parameters must all be present!--- in the DHCP response from the DHCP server. 01:25:15: CMAC_LOG_STATE_CHANGE establish_tod_state 01:25:15: CMAC_LOG_TOD_NOT_REQUESTED_NO_TIME_ADDR 01:25:15: CMAC_LOG_STATE_CHANGE security_association_state 01:25:15: CMAC_LOG_SECURITY_BYPASSED 01:25:15: CMAC_LOG_STATE_CHANGE configuration_file_state 01:25:15: CMAC_LOG_LOADING_CONFIG_FILE p2mp.cm!--- The establish_tod_state is the point in which the SU tries to retrieve!--- the time of day from the TOD server. This is used to synchronize clocks!--- for alarms and logs, among other reasons. The security_association_state!--- is a placeholder for a state yet to be defined. In the future,!--- a security association with a security server would provide!--- IPsec-like security for the SUs. This is NOT the baseline privacy state.!--- The configuration_file_state is the main configuration and!--- administration interface to the SU DOCSIS subsystem.!--- The name of this file and the TFTP server address in which!--- this could be downloaded was originally provided in the DHCP state.!--- This configuration file contains downstream channel and upstream!--- channel identification, characteristics, Class of Service settings,!--- Baseline Privacy settings, and general operational settings. 01:25:15: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:15: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:16: %LINEPROTO- 5-UPDOWN: Line protocol on Interface Radio1/0, changed state to up 01:25:16: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:16: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:17: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:17: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:18: CMAC_LOG_RNG_REQ_TRANSMITTED 01:25:18: CMAC_LOG_RNG_RSP_MSG_RCVD 01:25:19: CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE 01:25:19: CMAC_LOG_STATE_CHANGE registration_state 01:25:19: CMAC_LOG_REG_REQ_MSG_QUEUED 01:25:19: CMAC_LOG_REG_REQ_TRANSMITTED 01:25:19: CMAC_LOG_REG_RSP_MSG_RCVD!--- The link is now up.!--- The link comes up and then the SU tries to register with the HE!- -- through the registration_state. After configuration, the modem sends!--- a registration request (REG-REQ) with a required subset!--- of the configuration settings received in the DOCSIS config file. 01:25:19: CMAC_LOG_COS_ASSIGNED_SID 1/138 01:25:19: CMAC_LOG_COS_ASSIGNED_SID 2/139 01:25:19: CMAC_LOG_RNG_REQ_QUEUED :25:19: CMAC_LOG_REGISTRATION_OK 01:25:19: CMAC_LOG_STATE_CHANGE establish_privacy_state 01:25:19: CMAC_LOG_PRIVACY_NOT_CONFIGURED 01:25:19: CMAC_LOG_STATE_CHANGE maintenance_state!--- At this point, the service identifier (SID), which designates the!--- MAP grants on which the SU is allowed to speak,!--- is assigned. The establish_privacy_state only comes into effect!--- if baseline privacy is turned on. At the current time,!--- this is not supported, but it will be in the future.

17 Q. SU 가 downstram_channel_scanning_state 를통과할수없는경우어떻게합니까? A. 아마도마이크로코드가로드되지않았다는의미일것입니다. 마이크로코드다운로드가실패하면다음메시지가나타납니다. 00:00:38: %CWRMP-3-UCODEFAIL: Radio 1/0: Loading slot1:/cod.001 failed 이메시지는부팅후바로표시되므로이메시지를쉽게찾을수있습니다.no shut 명령을통해문제를확인할수도있습니다. SU1(config-if)# no shut SU1(config-if)# 00:02:26: CMAC_LOG_LINK_DOWN 00:02:26: CMAC_LOG_LINK_UP 00:02:26: CMAC_LOG_STATE_CHANGE ds_channel_scanning_state 00:02:27: CMAC_LOG_RESET_CANT_START_DS_TUNER_PRCESS 00:02:27: CMAC_LOG_STATE_CHANGE reset_interface_state 00:02:27: SU RFSM: MAC FSM Stop Cmd 00:02:27: CMAC_LOG_STATE_CHANGE reset_hardware_state 00:02:27: CMAC_LOG_STATE_CHANGE wait_for_link_up_state 00:02:27: CMAC_LOG_LINK_DOWN 문제유형을수정하려면 end conf t microcode cwrsu [path to microcode] microcode reload 마이크로코드의경로는일반적으로 slot1 입니다. 이명령은다음과같습니다. microcode cwrsu slot1: 코드가성공적으로로드되면이메시지가표시됩니다. 00:06:06: %CWRMP-5-UCODE: Radio 1/0: Loaded slot1: 그래도작동하지않으면플래시카드가슬롯 1 에제대로삽입되었는지확인합니다. exec 프롬프트 (exec 프롬프트에도달하려면 end 를입력 ) 에서슬롯 0 또는 1 의카드또는플래시에있는항목의디렉토리를볼수있습니다. 유형 : dir flash: dir slot0: dir slot1: Q. SU 가 rf_hw_reset_state 를초과할수없는경우어떻게합니까?

18 A. 이문제의가능한원인은다음과같습니다. ODU가켜져있지않습니다.ODU에는자체전원공급장치가있으므로이기능은쉽게간과할수있습니다. 이는라우터와별도로켜야합니다. ODU가무선라인카드에올바르게연결되지않았습니다. 케이블이모두연결되어있고단단히조여져있는지확인합니다. 와이어링다이어그램은설치가이드를참조하십시오. ODU 내의프로세서인 PIC가잠겼습니다. 이문제를해결하려면 ODU를끄고몇초기다린다음 ODU를다시켜십시오. 라우터는 2개의 ODU에대해구성되지만하나만연결됩니다. SU가 rf_hw_reset_state를초과할수없는경우, 로그에는소프트웨어가두번째 ODU를재설정하려고시도함을보여줍니다. 10:26:43: SU RFSM: STATE CHANGE if_hw_read_eeprom_state ====> rf_hw_reset_state 10:26:43: SU RFSM: Resetting RF/ODU1 10:26:44: %LINK-3-UPDOWN: Interface Radio1/0, changed state to up 10:26:48: SU RFSM: STATE CHANGE rf_hw_reset_state ====> rf_hw_read_version_state 10:26:48: RFHW: RF/ODU1 PIC boot loader version=255, vendor ID=0 10:26:48: RFHW: RF/ODU1 PIC code version=0.5, eeprom version=0 10:26:48: RFHW: Error: RF/ODU1 EEPROM Checksum failed! 10:26:48: RFHW: RF/ODU1 EEPROM Checksum=0x61 10:26:48: SU RFSM: STATE CHANGE rf_hw_read_version_state ====> rf_hw_read_eeprom_state 10:26:48: SU RFSM: Reading RF HW EEPROM 10:26:48: SU RFSM: Loading RF/ODU1 HW EEPROM data... 10:26:52: SU RFSM: Re-using RF/ODU1 HW EEPROM cached data 10:26:52: SU RFSM: RF/ODU1 HW EEPROM load complete 10:26:52: SU RFSM: STATE CHANGE rf_hw_read_eeprom_state ====> rf_hw_reset_state 10:26:52: SU RFSM: Resetting RF/ODU2 10:27:00: SU RFSM: PIC RESP Timeout 10:27:00: SU RFSM: Error: PIC msg timeout during SU RFSM rf_hw_reset_state 10:27:00: %CWRMP-4-RF_IF_COMM: Radio1/0, IF-to-RF/ODU2 comm error (ODU Controller Reset cmd) 10:27:00: SU RFSM: STATE CHANGE rf_hw_reset_state ====> standby_state 이문제를해결하려면두번째 ODU 를연결하거나, 시스템이하나만사용하도록구성하십시오. 하나의 ODU 에대해구성하려면라디오인터페이스프롬프트에서 radio receive-antents 1 명령을입력합니다. Q. SU 가 dsp_sync_state 를넘을수없는경우어떻게합니까? A. 이상태에서 DSP 는유효한다운스트림신호를찾고해당신호주파수에따라잠그고신호역분석을시작합니다. 다운스트림신호가도착하면문제가나타날수있습니다. 문제를해결하는데도움이되도록 DSP 는동기화프로세스를진행하는동안메시지를전송합니다. 모든것이제대로작동하면다음메시지가전송됩니다. 09:55:54: SU RFSM: STATE CHANGE dspinit_down_sync_state_config_state ====> dsp_sync_state 09:55:54: SU RFSM: Received DSP SYNC IND (0) 09:55:54: SU RFSM: Received DSP SYNC IND (2) 09:55:54: SU RFSM: Received DSP SYNC IND (4) 09:55:54: SU RFSM: Received DSP SYNC IND (5) 09:55:54: SU RFSM: Received DSP SYNC IND (8)

19 09:55:54: SU RFSM: DSP SYNC PASSED 또는 09:55:54: SU RFSM: STATE CHANGE dspinit_down_sync_state_config_state ====> dsp_sync_state 09:55:54: SU RFSM: Received DSP SYNC IND (0) 09:55:54: SU RFSM: Received DSP SYNC IND (2) 09:55:54: SU RFSM: Received DSP SYNC IND (4) 09:55:54: SU RFSM: Received DSP SYNC IND (5) 09:55:54: SU RFSM: Received DSP SYNC IND (7) 09:55:54: SU RFSM: Received DSP SYNC IND (4) 09:55:54: SU RFSM: Received DSP SYNC IND (5) 09:55:54: SU RFSM: Received DSP SYNC IND (8) 09:55:54: SU RFSM: DSP SYNC PASSED 가능한 DSP 동기화표시기는다음과같습니다. 0 AGC_PASS - DSP에서수신한신호에약간의전원이표시됩니다. 1 AGC_FAIL - DSP에수신된신호에서전원이표시되지않습니다. 이표시기는얻기어렵습니다. 다운스트림빈도가올바르게설정되었는지확인합니다. 2 BURST_SIZE_PASS - DSP가유효한다운스트림신호가있다고가정합니다. 이 DSP 표시기가마지막수신 DSP 표시기인경우 DSP는다운스트림빈도로잠글수없습니다. 모든전원을껐다가다시시도하십시오. 그래도작동하지않으면 SU IF 카드를교체합니다. 3 BURST_SIZE_FAIL - DSP에서유효한다운스트림신호를찾을수없습니다. 이문제는신호가너무약하거나너무강하기때문에발생할수있습니다.HE가켜져있고제대로전송되는지, 안테나가올바른방향으로향하는지, 다운스트림주파수를올바르게설정했는지확인합니다. 이러한설정중하나라도문제가발생하면수신해야할신호가없거나신호가매우약합니다. 다른가능성은신호가너무많다는것이다. 이경우 ODU의증폭기가포화상태가됩니다. 스펙트럼분석기와스플리터를사용하여 ODU와라인카드사이의신호를확인합니다. 다운스트림신호는 423~429MHz 사이여야하며신호전원은 64~15dBm 사이여야합니다. 신호가너무강하면채도를확인합니다. 게인이낮은안테나를고려하십시오. 케이블구성요소가잘못설정되었을수도있습니다. 4 TIME_D_PASS - DSP가수신된신호의타이밍과동기화되었습니다. 5 COLAR_FREQ_PASS - 이표시기는항상표시기번호 4를따릅니다. 기본적으로의미가없습니다. 6 - 이번호는사용되지않습니다. 7 OSC_ADJ_PASS - DSP가큰주파수조정을수행하는데필요합니다. 큰빈도조정후 DSP는 TIME_D 상태로돌아가므로이메시지뒤에오는유일한메시지는지표번호 4입니다. 이메시지가여러번표시되면 IF 모듈이잘못보정되었을수있습니다.IF 카드를교체합니다. 8 DEMOD_TT_PASS - DSP가다운스트림신호의모든변조매개변수를발견했으며데이터변조를시작할준비가되었습니다. dsp_sync_state에진입했지만 DSP에서지표메시지가표시되지않으면마이크로코드가올바르게다운로드되지않았을수있습니다. 다음명령을입력합니다. shut end configure terminal microcode reload

20 Q. SU 가 fec_sync_state 를넘을수없는경우어떻게합니까? A. 이문제는보통 SNR 이낮기때문에발생합니다.DSP 는디모드할수있는것보다훨씬낮은 SNR 신호에서동기화할수있습니다. 이문제를해결하려면가입자에게더깨끗한신호를보내야합니다.cable-comp 값이올바르게설정되어있고모든케이블이긴밀하게연결되어있는지확인합니다. 안테나를리디렉션합니다. 참고 : 이상태는뚜렷한이유없이실패할수있습니다. 오류를찾기전에다시시도하고두번째로작동하는지확인하십시오. Q. SU 가 trc_sync_state 를넘을수없는경우어떻게합니까? A. 이문제는가입자대신 HE 에문제가있음을나타내는경우가많습니다. 가입자의전원을껐다가다시시도하십시오. 동일한문제가발생할경우다른가입자가이 HE 카드에성공적으로연결되었는지확인하십시오. 그렇지않은경우 HE 에서 shut/no shut 명령을시도합니다. 그래도작동하지않으면 HE 의전원을껐다가켜십시오. 문제는 HE 는가끔문을닫지않은것처럼보이지만사실 MAC 칩은결코시작되지않았다는것입니다. 따라서전송중인다운스트림신호가있지만신호에대한데이터가없습니다. Q. SU 가 wait_ucd_state 를넘을수없는경우어떻게합니까? A. 여기두가지가능성이있어. 첫번째방법은 DOCSIS 초기범위 - 오프셋설정이잘못되었다는것입니다. 실행중인컨피그레이션에이기능이있으며, show run 명령을사용하여 exec 프롬프트에서볼수있습니다. 이문제를해결하려면인터페이스프롬프트로이동하여 docsis initial-ranging-offset 을입력합니다. 두번째가능성은 HE 에문제가있을수있다는것입니다."SU 가 trc_sync_state 를넘을수없는경우어떻게합니까?" 를참조하십시오. 자세한내용은문의해주십시오. Q. SU 가 ranging_1_state 를초과할수없는경우어떻게합니까? A. 초기범위차감을잘못설정할수있습니다. 위의질문과대답을참조하십시오. 다른가능성은업스트림신호에문제가있을수있습니다. 업스트림빈도가올바르게설정되었는지확인합니다.ALC 가켜져있는지확인합니다. 이것이기본모드이지만 ALC 를비활성화하는전송게인을수동으로설정할수도있습니다. 일반적으로 ALC 를비활성화해서는안됩니다.ALC 가켜져있는지확인하려면인터페이스프롬프트에서 no radio diag transmit-gain 명령을입력합니다. Q. SU 가 ranging_2_state 를초과할수없는경우어떻게합니까? A. 이것은아마도 HE 가미국으로부터의너무많은또는너무적은힘을보거나, 가입자로부터나오는신호가너무열악해서일관성있게추정할수없다는것을의미합니다. 전송게인이설정되고있는것을알려주는메시지가있습니다.SU 가 3dB [-3 db] 까지이득을감소하도록지시받았음을의미하는명령이있습니다. 따라서 SU 는 IF gain 을 -4dB 로설정하고 RF gain 을 0dB 로설정합니다. 10:54:26: SU RFSM: DSPMSG_TX_POWER_ADJ [-3 db], IF[-4 db], RF[00 db] 전송게인설정의올바른범위를보려면 exec 프롬프트에서다음명령을입력합니다.

21 show cont r1/0 rf show cont r1/0 if 이러한명령은 IF 및 RF 카드에대한많은정보를보여주며, 표시되는필드중하나는 TX(Time Zone) 변수게인의범위입니다. 가입자가범위하단의이익만사용하는경우 HE 에너무많은전력이공급될수있습니다. 저전력 ODU 로전환하거나, 안테나를다르게정렬하거나, ODU 와안테나사이에연결기를놓습니다. 한편, 미국이모든이득을취하도록설정되어있고, 미국이계속미국에전력을증가하도록지시한다면, 이것은그가충분한권력을받지못하고있다는표시입니다.HE 의 RF 수신전력설정값을확인하고안테나의정렬을확인합니다. 게인안테나가높을수록도움이됩니다. 또는안테나를이동하거나더높게장착합니다. Q. SU 가 dhcp_state 에도달하지만 IP 주소를가져오지못하는경우어떻게합니까? A. dhcp_state 메시지가표시되고 IP 주소가 SU 에할당되지않은경우일반적으로이것은 DHCP 서버의잘못된구성이거나 DHCP 서버에대한 IP 경로가없음을나타냅니다.DHCP 서버의컨피그레이션을확인하고외부 DHCP 서버를실행하는경우 show running 명령을통해라디오인터페이스아래에올바른라디오헬퍼주소명령이구성되어있는지확인합니다. Q. SU 가 dhcp_state 에도달하여 IP 주소를수신하지만다른매개변수에서실패하는경우어떻게합니까? A. SU 에필요한기타매개변수는 TFTP 서버주소, TOD(Time of Day) 서버주소, 표준시간대 (TX) 오프셋값및 DHCP 구성파일이름 (DOCSIS 구성파일이라고도함 ) 입니다. 이러한매개변수는모두 DHCP 서버의 DHCP 응답에있어야합니다. 참고 : DHCP/TFTP 서버의일부를재생하도록 HE 를구성할수있습니다.HE 가 DHCP/TFTP 서버로구성되지않은경우 HE 라디오인터페이스에라디오헬퍼주소명령이구성되어있는지확인합니다. 이렇게하면 DHCP 브로드캐스트가올바른서버로전달됩니다. 외부 DHCP/TFTP 서버를사용하는경우, 서버는패킷을다시 SU 네트워크로보내는방법을지시하는경로또는기본게이트웨이를포함해야합니다. 이러한오류메시지는 DHCP 응답에선택적매개변수가없음을나타냅니다. DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR DHCP_ERROR_ACQUIRING_LOG_ADDRESS DHCP 서버에보조서버및로그서버주소를구성하여이러한오류를제거합니다. Q. SU 가 established_tod_state 에도달하지만 TOD_REPLY_RECEIVED 에도달하지못하는경우어떻게합니까? A. 이상태에서오류가발생하는일반적인이유는 TOD 서버가외부에또는 HE 에존재하지않기때문입니다.TOD 서버로작동하도록 HE 를구성할수있습니다. 전역컨피그레이션모드에서 radio time-server 명령을실행합니다. 다시한번외부 TOD 서버를사용하려면 TOD 서버에서응답을다시 SU 로보낼경로가있어야합니다. Q. configuration_file_state 에서 SU 가실패하면어떻게합니까?

22 A. configuration_file_state 는 SU DOCSIS 하위시스템에대한기본구성및관리인터페이스입니다. 이파일의이름과이파일을다운로드할수있는 TFTP 서버주소는원래 DHCP 상태로제공되었습니다. 이구성파일에는다음이포함되어있습니다. 다운스트림채널및업스트림채널식별 특성 서비스클래스설정 기본개인정보설정 일반운영설정이상태에서오류가발생하는일반적인이유는파일누락, 잘못된파일권한, 연결할수없는 TFTP 서버, 잘못된형식의파일, 필요한옵션이없는파일, 잘못된필수옵션또는잘못된옵션 ( 알수없거나잘못된 TLV(Type-Length-Values)) 입니다. Q. SU 가 registration_state 에서실패하면어떻게합니까? A. 등록상태의문제는거의항상구성파일오류를가리킵니다.SU 와 HE 모두구성파일의설정을지원하는지확인합니다.HE 에서서비스프로파일클래스를생성할수있는지또는 HE 에서생성하는프로파일을사용할수있는지확인합니다.HE 라디오인터페이스컨피그레이션및 DOCSIS 컨피그레이션파일에서인증문자열을확인합니다. Q. SU 가 establish_privacy_state 에서실패하면어떻게합니까? A. 이상황은 HE 또는 SU 가 BPI( 기본프라이버시 ) 를설정하려고시도하고다른하나는그렇지않음을의미할수있습니다.DOCSIS 구성파일에 BPI 가켜져있는지확인합니다.HE 에서 QoS 프로필에서 BPI 가켜져있는지확인합니다.show radio qos profile 명령을사용합니다. 또한 HE 와 SU 모두 K 이미지를사용해야합니다. Q. SU 가 maintenance_state 에도착하지만 ping 하지않는경우어떻게합니까? A. SU 무선라인카드에유효한 IP 주소가있는지확인합니다.ranging_2_state 를초과하기위해몇번시도해야한다면, 이것은다른어떤것이잘못되었다는표시입니다. 이는어찌됐든 SNR 이너무낮다는것을의미합니다.SU 의유니캐스트재시도카운터가 0 이아닌것으로설정된경우이는낮은 SNR 을나타냅니다.SNR 값을보려면 show controller r1/0 mac 명령을사용합니다. 관련정보 Cisco Aironet Wireless LAN Client Adapter Cisco ubr7200 Series Universal Broadband Router용 Multipoint Wireless 지원 기술지원및문서 Cisco Systems