‫ةكبشلا لوكوتوربو مداخلا دنع ‪ FEC‬ءاطخأ‬

‫تانايبلا ةدوج نامضل قرطك )‪ (SNR‬طيسبلا‬

‫ةيجاتنإلاو‬

‫ﺍﻟﻤﺤﺘﻮﻳﺎﺕ‬
‫ﺍﻟﻤﻘﺪﻣﺔ‬
‫ﻧﺴﺒﺔ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺍﻟﻀﺠﻴﺞ‬
‫ﻛﻴﻔﻴﺔ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﻗﺮﺍﺀﺍﺕ ‪ SNR‬ﻭ ‪CNR‬‬
‫ﻛﻴﻔﻴﺔ ﻋﺮﺽ ﺃﺭﺿﻴﺔ ﺍﻟﻀﻮﺿﺎﺀ‬
‫ﻧﺎﻗﻼﺕ ﺍﻟﺨﺎﺩﻡ ﺑﻔﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ ﺻﻔﺮ‬
‫ﺗﺼﺤﻴﺢ ﺍﻟﺨﻄﺄ ﻟﻸﻣﺎﻡ‬
‫ﻛﻴﻔﻴﺔ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﻣﻦ ﺧﻼﻝ ‪SNMP‬‬
‫ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﻟﻜﻞ ﻣﻮﺩﻡ‬
‫ﻋﺪﺍﺩﺍﺕ ﺣﺰﻡ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ‬
‫ﺍﻟﻘﺮﺍﺭ‬
‫ﺍﻟﻤﻠﺤﻖ‬
‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻝ ‪ FEC‬ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻋﻨﺪ ﺍﻹﺗﺠﺎﻩ ﺍﻟﻌﻠﻮﻱ‬
‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻝ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺃﺛﻨﺎﺀ ﺍﻟﺘﺸﻐﻴﻞ‬
‫‪ SNR‬ﻟﻠﺘﺪﻓﻖ‬
‫ﻣﺜﺎﻝ ﻋﻠﻰ ﻛﻴﻔﻴﺔ ﺳﺤﺐ ‪ OIDs‬ﻟﻌﺪﺩ ‪ FEC‬ﻟﻜﻞ ﻣﻮﺩﻡ ﻋﻠﻰ ﺑﻄﺎﻗﺔ ﺧﻂ ‪ MC28U‬ﺃﻭ ‪5x20‬‬
‫ﻣﻌﻠﻮﻣﺎﺕ ﺫﺍﺕ ﺻﻠﺔ‬

‫ﺍﻟﻤﻘﺪﻣﺔ‬
‫ﻳﺘﻄﻠﺐ ﺗﺸﻐﻴﻞ ﺷﺒﻜﺔ ﺑﻴﺎﻧﺎﺕ ﻋﺎﻟﻴﺔ ﺍﻟﺴﺮﻋﺔ )‪ (HSD‬ﻋﺒﺮ ﻣﺼﻨﻊ ﻛﺒﻼﺕ ﻫﺠﻴﻦ ﺑﺎﻷﻟﻴﺎﻑ‪/‬ﻣﺘﺤﺪﺓ ﺍﻟﻤﺤﻮﺭ ﻣﺴﺘﻮﻯ ﻫﺎﻣﺎ ﻣﻦ‬
‫ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﺠﻮﺩﺓ ﻟﻀﻤﺎﻥ ﺳﻼﻣﺔ ﺍﻟﺒﻴﺎﻧﺎﺕ ﺑﺄﻋﻠﻰ ﻣﺴﺘﻮﻯ ﻣﻦ ﺳﻌﺔ ﻣﻌﺎﻟﺠﺔ ﺍﻟﺒﻴﺎﻧﺎﺕ‪ .‬ﺍﻟﻮﺳﻴﻠﺘﺎﻥ ﺍﻟﻤﻘﺒﻮﻟﺘﺎﻥ ﺑﺸﻜﻞ ﻋﺎﻡ‬
‫ﻭﺍﻟﺘﻲ ﻳﻤﻜﻦ ﻣﻦ ﺧﻼﻟﻬﺎ ﻟﻤﺸﻐﻠﻲ ﺍﻟﻜﺒﻼﺕ ﻗﻴﺎﺱ ﺟﻮﺩﺓ ﺍﻟﺒﻴﺎﻧﺎﺕ ﻫﻲ ﻣﺮﺍﻗﺒﺔ ﻣﻌﺪﻝ ﺧﻄﺄ ﺍﻟﺒﺖ )‪ (BER‬ﺃﻭ ﻣﻌﺪﻝ ﺧﻄﺄ‬
‫ﺍﻟﺤﺰﻣﺔ )‪.(PER‬‬

‫ﺍﻟﺒﻴﺎﻧﺎﺕ ﻋﺒﺮ ﻣﻮﺍﺻﻔﺎﺕ ﻭﺍﺟﻬﺔ ﺧﺪﻣﺔ ﺍﻟﻜﺒﻼﺕ )‪ (DOCSIS‬ﺗﺤﺪﺩ ﺍﻟﻤﺘﻄﻠﺒﺎﺕ ﺍﻟﺘﻲ ﻳﺠﺐ ﻋﻠﻰ ﻛﻞ ﻣﺸﻐﻞ ﻛﺒﻞ ﺻﻴﺎﻧﺘﻬﺎ ﻟﻨﻘﻞ‬
‫ﺣﺮﻛﺔ ﻣﺮﻭﺭ ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﺑﺸﻜﻞ ﻣﻮﺛﻮﻕ‪ .‬ﺗﻌﺎﻟﺞ ﻣﻴﺰﺓ ﻣﻬﻤﺔ ﻣﻦ ‪ DOCSIS‬ﺍﻟﺤﺎﺟﺔ ﺇﻟﻰ ﺣﻤﺎﻳﺔ ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﺿﺪ ﺍﺿﻤﺤﻼﻝ‬
‫ﺗﺸﻮﻳﺶ ﺗﺮﺩﺩ ﺍﻟﺮﺍﺩﻳﻮ )‪ .(RF‬ﺗﺴﺘﺨﺪﻡ ﻣﻴﺰﺓ ‪ DOCSIS‬ﻟﻠﻤﺴﺎﻋﺪﺓ ﻓﻲ ﺍﻟﺤﻔﺎﻅ ﻋﻠﻰ ﺳﻼﻣﺔ ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﻋﺒﺮ ﻣﺼﺎﻧﻊ ﻛﺒﻼﺕ‬
‫‪ HFC‬ﻫﻲ ﺗﺮﻣﻴﺰ ﺗﺼﺤﻴﺢ ﺧﻄﺄ ‪ Reed-Solomon‬ﺍﻷﻣﺎﻣﻲ )‪.(FEC‬‬

‫ﻓﻲ ﺍﻷﺳﺎﺱ‪ ،‬ﻳﺤﻤﻲ ﺗﺸﻔﻴﺮ ‪ FEC‬ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﻭﺭﺳﺎﺋﻞ ﺇﺩﺍﺭﺓ ‪ DOCSIS‬ﺿﺪ ﺃﺧﻄﺎﺀ ﺍﻟﺮﻣﺰ ﺍﻟﺘﻲ ﻳﺴﺒﺒﻬﺎ ﺍﻟﻀﻮﺿﺎﺀ ﻭﺣﺎﻻﺕ‬
‫ﺍﻟﻀﻌﻒ ﺍﻷﺧﺮﻯ‪ .‬ﺍﻟﻤﻴﺰﺓ ﺍﻟﻔﺮﻳﺪﺓ ﺍﻟﺨﺎﺻﺔ ﺏ ‪ FEC‬ﻫﻲ ﺃﻧﻪ ﻳﻤﻜﻨﻪ ﺍﻟﻜﺸﻒ ﻋﻦ ﺃﺧﻄﺎﺀ ﺍﻟﺮﻣﺰ ﻭﺗﺼﺤﻴﺤﻬﺎ ﺃﻳﻀﺎ‪ .‬ﻭﺑﺎﻟﺘﺎﻟﻲ‪،‬‬
‫ﻳﺤﺪﺩ ‪ DOCSIS‬ﺃﻥ ﺟﻤﻴﻊ ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﺍﻟﺘﻲ ﻳﺘﻢ ﺇﺭﺳﺎﻟﻬﺎ ﻋﺒﺮ ﻣﺼﻨﻊ ‪ HFC‬ﻳﺠﺐ ﺃﻥ ﺗﻤﺮ ﻣﻦ ﺧﻼﻝ ﺟﻬﺎﺯ ﺗﺸﻔﻴﺮ ‪Reed-‬‬
‫‪ ،Solomon‬ﺣﻴﺚ ﺗﺘﻢ ﺇﺿﺎﻓﺔ ﻭﺣﺪﺍﺕ ﺑﺎﻳﺖ ﺍﻟﺘﻤﺎﺛﻞ ﺍﻹﺿﺎﻓﻴﺔ ﺇﻟﻰ ﺇﻃﺎﺭﺍﺕ ﺍﻟﺒﻴﺎﻧﺎﺕ ﻟﻠﺘﺄﻛﺪ ﻣﻦ ﺃﻧﻬﺎ ﻣﺤﻤﻴﺔ ﻣﻦ ﺍﻷﺧﻄﺎﺀ ﻭﺃﻗﻞ‬
‫ﻋﺮﺿﺔ ﻟﻠﻀﺮﺭ‪.‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻻ ﻳﻌﻤﻞ ﻧﻈﺎﻡ ‪ FEC‬ﺑﺸﻜﻞ ﺟﻴﺪ ﺟﺪﺍ ﺇﺫﺍ ﻛﺎﻧﺖ ﺍﻷﺧﻄﺎﺀ ﺗﺤﺪﺙ ﺑﺴﺒﺐ ﺿﺠﻴﺞ ﺍﻟﻨﺒﻀﺎﺕ ﺍﻟﺬﻱ ﻳﺆﺩﻱ ﺇﻟﻰ ﺣﺪﻭﺙ‬
 ‫ﺍﻟﻌﺪﻳﺪ ﻣﻦ ﺍﻷﺧﻄﺎﺀ ﻋﻠﻰ ﺍﻟﺘﻮﺍﻟﻲ‪ .‬ﻳﺘﻢ ﺍﻟﺘﻌﺎﻣﻞ ﻣﻊ ﺍﻷﺧﻄﺎﺀ ﺍﻟﻨﺎﺗﺠﺔ ﻋﻦ ﺍﻟﻨﺒﻀﺎﺕ ﻭﺍﻟﻀﻮﺿﺎﺀ ﻋﻠﻰ ﺍﻟﺠﺎﻧﺐ ﺍﻟﺴﻔﻠﻲ‬
‫ﺑﺎﺳﺘﺨﺪﺍﻡ ﺍﻟﺘﺸﺎﺑﻚ ﻟﺘﺠﻌﻞ ﺍﻷﺧﻄﺎﺀ ﺗﻈﻬﺮ ﻣﻨﺘﺸﺮﺓ‪ ،‬ﻭﻫﻮ ﺃﻣﺮ ﻓﻌﺎﻝ ﻓﻲ ﺍﻹﺻﻼﺡ‪ .‬ﻗﺎﻡ ‪ DOCSIS 2.0‬ﺑﺈﺿﺎﻓﺔ ﺗﺪﺍﺧﻞ‬
‫ﺍﻟﺨﺎﺩﻡ‪ ،‬ﻣﻤﺎ ﻳﺴﺎﻋﺪ ﻋﻠﻰ ﻫﺬﺍ ﺍﻟﻨﻮﻉ ﻣﻦ ﺍﺿﻤﺤﻼﻝ ﺗﺪﻓﻖ ﺍﻟﺨﺎﺩﻡ )ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ(‪ ،‬ﻭﻟﻜﻨﻪ ﻏﻴﺮ ﻣﺘﻮﻓﺮ ﻋﻠﻰ ﺃﺟﻬﺰﺓ‬
‫ﻣﻮﺩﻡ ﻛﺒﻞ ‪.(x (CMs.1‬‬

‫ﻣﻦ ﺩﻭﻥ ﺷﻚ‪ ،‬ﻳﻜﻮﻥ ﻣﺴﺎﺭ ﺇﺭﺟﺎﻉ ﺷﺒﻜﺔ ﺍﻟﻜﺒﻼﺕ ﺃﻭ ﺍﻟﺨﺎﺩﻡ ﻋﺮﺿﺔ ﺑﺸﻜﻞ ﺧﺎﺹ ﻟﻠﺘﺸﻮﻳﺶ ﻭﻣﺎ ﻳﺘﺼﻞ ﺑﻪ ﻣﻦ ﺇﻋﺎﻗﺎﺕ‪ .‬ﺍﻥ‬
‫ﺿﺠﻴﺠﺎ ﻛﻬﺬﺍ ﻳﻤﻜﻦ ﺍﻥ ﻳﻜﻮﻥ ﻧﺒﻀﺎ‪ ،‬ﺿﺠﻴﺠﺎ ﻋﻨﺪ ﺍﻟﺪﺧﻮﻝ‪ ،‬ﺿﺠﻴﺠﺎ ﺣﺮﺍﺭﻳﺎ‪ ،‬ﻗﺼﺎﺻﺔ ﻟﻴﺰﺭ‪ ،‬ﻭﻫﻠﻢ ﺟﺮﺍ‪ .‬ﺑﺪﻭﻥ ﺗﺸﻔﻴﺮ ‪،FEC‬‬
‫ﺗﻜﻮﻥ ﻓﺮﺹ ﺇﺳﻘﺎﻁ ﺍﻟﺤﺰﻣﺔ ﺑﺴﺒﺐ ﺃﺧﻄﺎﺀ ﺍﻟﺒﺖ ﻛﺒﻴﺮﺓ‪ .‬ﻻ ﺗﻌﺪ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻓﻲ ﺗﺠﻬﻴﺰﺍﺕ ﺍﻟﻜﺒﻼﺕ ﻣﻘﻴﺎﺱ ﺍﻟﺠﻮﺩﺓ ﺍﻟﻮﺣﻴﺪ‪.‬‬
‫ﻫﻨﺎﻙ ﻣﺘﻐﻴﺮﺍﺕ ﺃﺧﺮﻯ ﻳﺠﺐ ﻣﺮﺍﻋﺎﺗﻬﺎ‪ ،‬ﻣﺜﻞ ﻧﺴﺒﺔ ﺍﻟﺤﺎﻣﻞ ﺇﻟﻰ ﺍﻟﺘﺸﻮﻳﺶ )‪.(CNR‬‬

‫ﻳﺘﻀﻤﻦ ﻣﻌﻴﺎﺭ ‪ DOCSIS‬ﺍﻟﻤﻌﻠﻤﺎﺕ ﺍﻟﻤﻮﺻﻰ ﺑﻬﺎ ﻟﻜﻞ ﻣﻦ ﺃﺩﺍﺀ ﺗﺮﺩﺩ ﺍﻟﺮﺍﺩﻳﻮ ﺍﻟﺨﺎﺹ ﺑﻜﺒﻞ ﺍﻟﺨﺎﺩﻡ ﻭﺍﻟﻨﻬﻀﻢ‪ .‬ﻭﻋﻠﻰ ﻭﺟﻪ‬
‫ﺍﻟﺘﺤﺪﻳﺪ‪ ،‬ﻳﻨﺺ ﺍﻟﻘﺴﻢ ‪ 2.3.2‬ﻣﻦ ﻣﻮﺍﺻﻔﺎﺕ ﺗﺪﺍﺧﻞ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ )‪ (RFI‬ﻋﻠﻰ ﺧﺼﺎﺋﺺ ﺍﻹﺭﺳﺎﻝ ﺍﻟﻤﺘﺼﻮﺭﺓ ﻟﻘﻨﺎﺓ ﺍﻟﺘﺮﺩﺩ‬
‫ﺍﻟﻼﺳﻠﻜﻲ ﻓﻲ ﺍﻟﺨﺎﺩﻡ ﻣﺎ ﻳﻠﻲ‪:‬‬

‫ﺍﻟﻨﺎﻗﻞ ﺇﻟﻰ ﺍﻟﺘﺪﺍﺧﻞ ﺑﺎﻹﺿﺎﻓﺔ ﺇﻟﻰ ﺍﻟﻤﺪﺧﻞ )ﻣﺠﻤﻮﻉ ﺍﻟﻀﻮﺿﺎﺀ ﻭﺍﻟﺘﺸﻮﻩ‬

‫ﻭﺗﺸﻮﻩ ﺍﻟﻤﺴﺎﺭ ﺍﻟﺸﺎﺋﻊ ﻭﺗﻌﺪﻳﻞ ﺍﻟﻤﺴﺎﺭ ﺍﻟﺘﺒﺎﺩﻟﻲ ﻭﻣﺠﻤﻮﻉ ﺇﺷﺎﺭﺍﺕ‬
‫ﺍﻟﺪﺧﻮﻝ ﺍﻟﻤﻨﻔﺼﻠﺔ ﻭﺇﺷﺎﺭﺍﺕ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﺍﻟﻌﺮﻳﺾ‪ ،‬ﻣﻊ ﺇﺳﺘﺒﻌﺎﺩ‬
‫ﺗﺸﻮﻳﺶ ﺍﻟﻨﺒﻀﺎﺕ( ﻧﺴﺒﺔ ]ﻟﻦ ﺗﻜﻮﻥ[ ﺃﻗﻞ ﻣﻦ ‪ 25‬ﺩﻳﺴﻴﺒﻞ‪.‬‬

‫ﺑﻤﻌﻨﻰ ﺁﺧﺮ‪ ،‬ﺍﻟﺤﺪ ﺍﻷﺩﻧﻰ ﻝ ‪ DOCSIS‬ﺍﻟﻤﻮﺻﻰ ﺑﻪ ﻝ ‪ US CNR‬ﻫﻮ ‪ 25‬ﺩﻳﺴﻴﺒﻞ‪ .‬ﻷﻏﺮﺍﺽ ﻫﺬﺍ ﺍﻟﻤﺴﺘﻨﺪ‪ ،‬ﻳﺘﻢ ﺗﻌﺮﻳﻒ‬
‫‪ CNR‬ﻋﻠﻰ ﺃﻧﻪ ﻧﺴﺒﺔ ﺍﻟﺤﺎﻣﻞ ﺇﻟﻰ ﺍﻟﻀﻮﺿﺎﺀ ﻗﺒﻞ ﺃﻥ ﺗﺼﻞ ﺇﻟﻰ ﺷﺮﻳﺤﺔ ﺍﻟﻤﺴﺘﺨﺮﺝ )ﻣﺠﺎﻝ ‪ ،(RF‬ﻣﻘﺎﺳﺔ ﺑﻮﺍﺳﻄﺔ ﻣﺤﻠﻞ‬
‫ﺍﻟﻄﻴﻒ‪ .‬ﻭﻋﻠﻰ ﺍﻟﻌﻜﺲ ﻣﻦ ﺫﻟﻚ‪ ،‬ﻳﺘﻢ ﺗﻌﺮﻳﻒ ﺑﺮﻭﺗﻮﻛﻮﻝ ﻃﺒﻘﺔ ﺍﻷﻣﺎﻥ )‪ (SNR‬ﻋﻠﻰ ﺃﻧﻪ ﻧﺴﺒﺔ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺍﻟﺘﺸﻮﻳﺶ ﻣﻦ‬
‫ﺷﺮﻳﺤﺔ ﺟﻬﺎﺯ ﺍﻻﺳﺘﻘﺒﺎﻝ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ )‪ (CMTS‬ﻟﻨﻈﺎﻡ ﺗﻮﺻﻴﻞ ﺍﻟﻤﻮﺩﻡ ﻟﻠﻜﺒﻞ ﺑﻌﺪ ﺃﻥ ﺗﻢ ﺗﺨﻔﻴﺾ ﻣﺴﺘﻮﻯ ﺍﻟﻨﺎﻗﻞ‬
‫ﻹﻋﻄﺎﺀ ﻧﻄﺎﻕ ﺃﺳﺎﺳﻲ ﻧﻘﻲ‪ ،‬ﻧﺴﺒﺔ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺍﻟﺘﺸﻮﻳﺶ‪.‬‬

‫ﻭﺑﺎﻟﺘﺎﻟﻲ‪ ،‬ﻋﻨﺪﻣﺎ ﻳﻨﻈﺮ ﺍﻟﻤﺮﺀ ﺇﻟﻰ ﻗﺮﺍﺀﺓ ‪ SNR‬ﻋﻠﻰ ‪ Cisco uBR7246‬ﻭﻳﺮﻯ ﺭﻗﻤﺎ ﻣﺜﻞ ‪ 30‬ﺩﻳﺴﻴﺒﻞ‪ ،‬ﻓﻤﻦ ﺍﻟﺴﻬﻞ ﺃﻥ‬
‫ﻳﻔﺘﺮﺽ ﺃﻥ ﺍﻟﺨﺎﺩﻡ ﻳﻔﻲ ﺃﻭ ﻳﺘﺠﺎﻭﺯ ‪ DOCSIS‬ﻭﺃﻥ ﺍﻷﻣﻮﺭ ﻓﻲ ﻋﺎﻟﻢ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ ﻻ ﺑﺄﺱ ﺑﻬﺎ‪ .‬ﻭﻟﻜﻦ ﻫﺬﺍ ﻟﻴﺲ ﻫﻮ‬
‫ﺍﻟﺤﺎﻝ ﺩﺍﺋﻤﺎ‪ .‬ﻻ ﻳﺤﺪﺩ ‪ ،DOCSIS SNR‬ﻭﺗﻘﺪﻳﺮ ‪ SNR‬ﻝ ‪ CMTS‬ﻟﻴﺲ ﻧﻔﺲ ﺍﻟﺸﻲﺀ ﻣﺜﻞ ‪ CNR‬ﺍﻟﺬﻱ ﻳﻘﻴﺴﻪ ﻭﺍﺣﺪ‬
‫ﺑﺎﺳﺘﺨﺪﺍﻡ ﻣﺤﻠﻞ ﺍﻟﻄﻴﻒ‪.‬‬

‫ﻭﻳﻨﺎﻗﺶ ﻫﺬﺍ ﺍﻟﻤﺴﺘﻨﺪ ﺣﺴﺎﺑﺎﺕ ‪ SNR‬ﺍﻟﺘﻘﺪﻳﺮﻳﺔ ﺍﻟﺨﺎﺻﺔ ﺑﺎﻟﺠﻬﺎﺯ ﺍﻟﺨﺎﺩﻡ ﻟﻠﻄﺮﺍﺯ ‪ uBR‬ﻭﻛﺬﻟﻚ ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﺍﻟﺨﺎﺻﺔ‬
‫ﺑﻮﺣﺪﺓ ﺑﻴﺎﻧﺎﺕ ﺍﻻﻋﺘﻤﺎﺩ ﻋﻠﻰ ﺍﻟﺨﺎﺩﻡ )‪ (FEC‬ﺍﻟﺨﺎﺻﺔ ﺑﻮﺣﺪﺓ ﺑﻴﺎﻧﺎﺕ ﺍﻟﻨﻈﺎﻡ ﺍﻷﺳﺎﺳﻲ )‪ ،(uBR‬ﻛﻤﺎ ﻳﻮﺿﺢ ﺍﻟﺴﺒﺐ ﻭﺭﺍﺀ‬
‫ﺿﺮﻭﺭﺓ ﺗﻘﻴﻴﻢ ﻫﺬﻳﻦ ﺍﻟﻤﺘﻐﻴﺮﻳﻦ ﺑﺎﺳﺘﻤﺮﺍﺭ ﻟﻀﻤﺎﻥ ﺟﻮﺩﺓ ‪ HSD‬ﻋﺒﺮ ﺑﻴﺌﺎﺕ ‪.HFC‬‬

‫ﻧﺴﺒﺔ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺍﻟﻀﺠﻴﺞ‬

‫ﻭﻗﺪ ﺗﻜﻮﻥ ﺗﻘﺪﻳﺮﺍﺕ ﺗﻘﺮﻳﺮ ﻣﻴﺰﺍﻥ ﺍﻟﻘﻮﻯ )‪ (SNR‬ﻓﻲ ﺑﻌﺾ ﺍﻷﺣﻴﺎﻥ ﻣﻀﻠﻠﺔ‪ ،‬ﻭﻻ ﻳﻨﺒﻐﻲ ﺍﻋﺘﺒﺎﺭﻫﺎ ﺳﻮﻯ ﻧﻘﻄﺔ ﺑﺪﺍﻳﺔ ﻋﻨﺪﻣﺎ‬
‫ﻳﺘﻌﻠﻖ ﺍﻷﻣﺮ ﺑﺎﻟﺘﺤﻘﻖ ﻣﻦ ﺳﻼﻣﺔ ﻃﻴﻒ ﺗﺮﺩﺩ ﺍﻟﺮﺍﺩﻳﻮ ﻋﻨﺪ ﺃﻋﻠﻰ ﺍﻟﺨﺎﺩﻡ‪ .‬ﻳﺘﻢ ﺗﻮﻓﻴﺮ ﻗﺮﺍﺀﺓ ‪ SNR‬ﻋﻠﻰ ﺧﻂ ‪uBR MC16C‬‬
‫ﺑﻮﺍﺳﻄﺔ ﺍﻟﺮﻗﺎﻗﺔ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ‪ ،‬ﻭﻟﻜﻦ ﺍﻟﻘﺮﺍﺀﺓ ﻟﻴﺴﺖ ﺑﺎﻟﻀﺮﻭﺭﺓ ﻣﺆﺷﺮﺍ ﻳﻤﻜﻦ ﺍﻻﻋﺘﻤﺎﺩ ﻋﻠﻴﻪ ﻟﻀﻌﻒ ﺍﻟﺘﺮﺩﺩ‬
‫ﺍﻟﻼﺳﻠﻜﻲ ﻓﻲ ﺍﻟﻌﺎﻟﻢ ﺍﻟﺤﻘﻴﻘﻲ ﻣﺜﻞ ﺿﺠﻴﺞ ﺍﻟﻨﻤﻂ ﺍﻟﻤﻨﺪﻓﻊ‪ ،‬ﻭﺍﻟﻤﺪﺧﻞ ﺍﻟﻤﻨﻔﺼﻞ‪ ،‬ﻭﻣﺎ ﺇﻟﻰ ﺫﻟﻚ‪ .‬ﻫﺬﺍ ﻻ ﻳﻌﻨﻲ ﺃﻥ ﻗﺮﺍﺀﺓ‬
‫ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﻋﻠﻰ ﺷﺒﻜﺔ ﺍﻹﻧﺘﺮﻧﺖ ﻟﻴﺴﺖ ﺩﻗﻴﻘﺔ‪ .‬ﻭﻓﻲ ﺍﻟﺒﻴﺌﺎﺕ ﺍﻟﺘﻲ ﺗﻌﺎﻧﻲ ﻣﻦ ﻗﻠﺔ ﻣﻦ ﺍﻟﻌﺎﻫﺎﺕ ﻋﻠﻰ ﻣﺴﺘﻮﻯ ﺍﻟﻤﻨﺒﻊ‬
‫)ﻋﻠﻰ ﺳﺒﻴﻞ ﺍﻟﻤﺜﺎﻝ‪ ،‬ﺍﻟﻀﻮﺿﺎﺀ ﺍﻟﻨﺎﺗﺠﺔ ﻋﻦ ﺍﻟﻨﺒﻀﺎﺕ‪ ،‬ﻭﺍﻟﻤﺪﺧﻞ‪ ،‬ﻭﺗﺸﻮﻩ ﺍﻟﻤﺴﺎﺭ ﺍﻟﺸﺎﺋﻊ‪ ،‬ﻭﻣﺎ ﺇﻟﻰ ﺫﻟﻚ(‪ ،‬ﻳﺘﻌﻘﺐ ﻧﻈﺎﻡ ‪SNR‬‬
‫ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﺭﻗﻤﻴﺎ ﺍﻟﻨﺒﻀﺎﺕ ﺍﻟﻤﺴﺘﻤﺮﺓ ﻟﻔﺘﺮﺓ ﻻ ﺗﺘﺠﺎﻭﺯ ﺿﻌﻒ ﺍﻟﺪﺳﻴﺒﻞ‪ ،‬ﻋﻨﺪﻣﺎ ﻳﻜﻮﻥ ﻣﻌﺪﻝ ﺗﻜﺮﺍﺭ ﺍﻟﻨﺒﻀﺎﺕ ﻓﻲ‬
‫ﻧﻄﺎﻕ ﻳﺘﺮﺍﻭﺡ ﺑﻴﻦ ‪ 15‬ﺇﻟﻰ ‪ 25‬ﺩﻳﺴﻴﺒﻞ‪ .‬ﺍﻧﻪ ﺩﻗﻴﻖ ﻣﻊ ﺍﻟﻀﺠﻴﺞ ﺍﻟﻀﺒﺎﺑﻲ ﺍﻻﺑﻴﺾ ﺍﻟﻤﻀﺎﻑ )‪ (AWGN‬ﺑﺼﻔﺘﻪ ﺍﻟﻌﺎﻫﺔ‬
‫ﺍﻟﻮﺣﻴﺪﺓ؛ ﻭﻟﻜﻦ ﻓﻲ ﺍﻟﻌﺎﻟﻢ ﺍﻟﺤﻘﻴﻘﻲ‪ ،‬ﻳﻤﻜﻦ ﺍﻥ ﺗﺨﺘﻠﻒ ﺩﻗﺔ ﻫﺬﻩ ﺍﻻﺭﻗﺎﻡ‪ .‬ﻭﻫﺬﺍ ﻳﺘﻮﻗﻒ ﻋﻠﻰ ﻃﺒﻴﻌﺔ ﺍﻟﻌﺎﻫﺎﺕ ﻭﻳﻌﻜﺲ‬
‫ﻋﻠﻰ ﻧﺤﻮ ﺃﻓﻀﻞ ﻧﺴﺒﺔ ﺍﻟﺨﻄﺄ ﻓﻲ ﺍﻟﺘﻨﻐﻴﻢ )‪ (MER‬ﺑﺪﻻ ﻣﻦ ‪.CNR‬‬

‫ﻛﻴﻔﻴﺔ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﻗﺮﺍﺀﺍﺕ ‪ SNR‬ﻭ ‪CNR‬‬

‫ﻳﻮﺿﺢ ﻫﺬﺍ ﺍﻟﻘﺴﻢ ﺑﻌﺾ ﺍﻷﻣﺜﻠﺔ ﻋﻠﻰ ﻛﻴﻔﻴﺔ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﺗﻘﺪﻳﺮ ‪ SNR‬ﻟﻠﺘﺤﻤﻴﻞ ﻣﻦ ‪ Cisco uBR7200‬ﻭ ‪uBR10K‬‬
‫)ﺭﺍﺟﻊ ﺃﻳﻀﺎ ﺍﻟﻤﻠﺤﻖ(‪ .‬ﻳﺘﻢ ﺃﺧﺬ ﺟﻤﻴﻊ ﺃﻭﺍﻣﺮ ﻭﺍﺟﻬﺔ ﺳﻄﺮ ﺍﻷﻭﺍﻣﺮ )‪ (CLI‬ﻭﻣﺨﺮﺟﺎﺕ ﺍﻷﻭﺍﻣﺮ ﻣﻦ ﺑﺮﻧﺎﻣﺞ ‪®Cisco IOS‬‬
 ‫ﺍﻹﺻﺪﺍﺭ ‪ ،BC2a(15)12.2‬ﻣﺎ ﻟﻢ ﻳﺘﻢ ﺗﺤﺪﻳﺪ ﺧﻼﻑ ﺫﻟﻚ‪.‬‬

‫ﻻﺣﻆ ﺃﻥ "ﺑﻄﺎﻗﺔ ‪ "S‬ﺗﺸﻴﺮ ﺇﻟﻰ ﺑﻄﺎﻗﺔ ﺧﻂ ﻛﺒﻞ ﻣﺰﻭﺩﺓ ﺑﺈﻣﻜﺎﻧﺎﺕ ﻣﺪﻣﺠﺔ ﻟﺘﺤﻠﻴﻞ ﻧﻄﺎﻕ ﺍﻷﺟﻬﺰﺓ‪ ،‬ﺑﻴﻨﻤﺎ ﺗﺸﻴﺮ "ﺑﻄﺎﻗﺔ ‪"C‬‬
‫ﺇﻟﻰ ﺑﻄﺎﻗﺔ ﺧﻂ ﻛﺒﻞ ﺩﻭﻥ ﻫﺬﻩ ﺍﻹﻣﻜﺎﻧﻴﺔ‪ .‬ﻭﻓﻲ ﻇﻞ ﺇﻋﺪﺍﺩﺍﺕ ﻣﻌﻴﻨﺔ‪ ،‬ﺗﻘﺪﻡ ﺍﻟﺒﻄﺎﻗﺔ ‪ S‬ﺗﻘﺮﻳﺮﺍ ﻋﻦ ‪ CNR‬ﺑﺪﻻ ﻣﻦ ‪،SNR‬‬
‫ﻷﻧﻬﺎ ﺗﺤﺘﻮﻱ ﻋﻠﻰ ﺃﺟﻬﺰﺓ ﻣﻀﻤﻨﺔ ﻟﺘﻨﻔﻴﺬ ﻭﻇﺎﺋﻒ ﺗﺤﻠﻴﻞ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ‪.‬‬

‫ﺗﻠﻤﻴﺢ‪ :‬ﻋﻨﺪ ﺗﺠﻤﻴﻊ ﺇﺧﺮﺍﺝ ﺃﻭﺍﻣﺮ ‪ CLI‬ﻟﺒﺮﻧﺎﻣﺞ ‪ Cisco IOS Software‬ﻷﻏﺮﺍﺽ ﺃﺳﺘﻜﺸﺎﻑ ﺍﻷﺧﻄﺎﺀ ﻭﺇﺻﻼﺣﻬﺎ ﺃﻭ ﺇﻋﺎﺩﺓ‬
‫ﺍﻟﺘﻮﺟﻴﻪ ﺇﻟﻰ ﺩﻋﻢ ‪ Cisco‬ﺍﻟﺘﻘﻨﻲ‪ ،‬ﺗﺬﻛﺮ ﺗﻤﻜﻴﻦ ﺍﻟﻄﺎﺑﻊ ﺍﻟﺰﻣﻨﻲ ﻟﻤﻄﺎﻟﺒﺔ ‪ EXEC‬ﻟﻠﻤﺤﻄﺔ ﺍﻟﻄﺮﻓﻴﺔ‪ ،‬ﺑﺤﻴﺚ ﻳﻜﻮﻥ ﻛﻞ ﺳﻄﺮ‬
‫ﻣﻦ ﺇﺧﺮﺍﺝ ﺃﻣﺮ ‪ CLI‬ﻣﺼﺤﻮﺑﺎ ﺑﻄﺎﺑﻊ ﺯﻣﻨﻲ ﻭﺑﺤﻤﻞ ﻭﺣﺪﺓ ﺍﻟﻤﻌﺎﻟﺠﺔ ﺍﻟﻤﺮﻛﺰﻳﺔ ﺍﻟﺤﺎﻟﻲ ﻋﻠﻰ ‪.CMTS‬‬

‫ﻟﺒﻄﺎﻗﺎﺕ ‪:S‬‬

‫‪ubr7246# show controller cable6/0 upstream 0‬‬

‫‪Load for five secs: 5%/1%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
‫‪Cable6/0 Upstream 0 is up‬‬
‫‪Frequency 21.810 MHz, Channel Width 3.2 MHz, 16-QAM Symbol Rate 2.560 Msps‬‬
‫‪This upstream is mapped to physical port 0‬‬
‫‪(Spectrum Group 1, Last Frequency Hop Data Error: NO(0‬‬
‫‪MC28U CNR measurement - 38 dB‬‬

‫ﻟﻠﺒﻄﺎﻗﺎﺕ ‪ C‬ﺃﻭ ‪ S‬ﺑﺪﻭﻥ ﻣﺠﻤﻮﻋﺎﺕ ﺍﻟﻄﻴﻒ ﺍﻟﻤﻌﻴﻨﺔ‪:‬‬

‫‪ubr7246vxr# show controller cable3/0 upstream 0‬‬

‫‪Load for five secs: 10%/1%; one minute: 7%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
‫‪Cable3/0 Upstream 0 is up‬‬
‫‪Frequency 25.392 MHz, Channel Width 3.200 MHz, QPSK Symbol Rate 2.560 Msps‬‬
‫‪Spectrum Group is overridden‬‬
‫‪BroadCom SNR_estimate for good packets - 26.8480 dB‬‬
‫‪Nominal Input Power Level 0 dBmV, Tx Timing Offset 2035‬‬
‫ﻣﻦ ﺍﻟﻤﺴﺘﺤﺴﻦ ﺃﻥ ﺗﺒﻘﻲ ﻋﻠﻰ ﻣﺴﺘﻮﻯ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﻣﻀﺒﻮﻃﺎ ﻋﻠﻰ ﺍﻟﻘﻴﻤﺔ ﺍﻻﻓﺘﺮﺍﺿﻴﺔ ‪ 0‬ﺩﻳﺴﻴﺒﻞ ‪ BmV‬ﻭﺃﻥ ﺗﺴﺘﺨﺪﻡ‬
‫ﻣﻀﻌﻔﺎﺕ ﺧﺎﺭﺟﻴﺔ ﻹﺟﺒﺎﺭ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﻋﻠﻰ ﺍﻹﺭﺳﺎﻝ ﺇﻟﻰ ﻣﺴﺘﻮﻳﺎﺕ ﺃﻋﻠﻰ‪ ،‬ﺇﺫﺍ ﻟﺰﻡ ﺍﻷﻣﺮ‪.‬‬

‫‪ubr7246# show cable modem phy‬‬

‫‪MAC Address‬‬ ‫‪I/F‬‬ ‫‪Sid USPwr USSNR Timing MicrReflec DSPwr DSSNR Mode‬‬
‫)‪(dBmV) (dB‬‬ ‫)‪Offset (dBc‬‬ ‫)‪(dBmV) (dB‬‬
‫‪0002.8a8c.6462 C6/0/U0 9 46.07 35.42 2063‬‬ ‫‪31‬‬ ‫‪-1.05 39.05 tdma‬‬
‫‪000b.06a0.7116 C6/0/U0 10 48.07 36.12 2037‬‬ ‫‪46‬‬ ‫‪0.05 41.00 atdma‬‬
‫ﺗﻠﻤﻴﺢ‪ :‬ﻳﻤﻜﻦ ﺇﺳﺘﺨﺪﺍﻡ ﺍﻷﻣﺮ ‪ phy‬ﻟﻺﺑﻼﻍ ﻋﻦ ‪ SNR‬ﺣﺘﻰ ﺇﺫﺍ ﺗﻢ ﺍﻹﺑﻼﻍ ﻋﻦ ‪ CNR‬ﻓﻲ ﺍﻷﻣﺮ ‪ .show controllers‬ﻭﻫﺬﺍ‬
‫ﻣﻔﻴﺪ ﺑﺸﻜﻞ ﺧﺎﺹ ﻷﻥ ‪ SNR‬ﻳﺘﻢ ﺍﻹﺑﻼﻍ ﻋﻨﻪ ﺑﻌﺪ ﺇﻟﻐﺎﺀ ﺍﻟﺪﺧﻮﻝ ﻭﻳﺘﻢ ﺍﻹﺑﻼﻍ ﻋﻦ ‪ CNR‬ﻗﺒﻞ ﺇﻟﻐﺎﺀ ﺍﻟﺪﺧﻮﻝ‪.‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻳﺘﻢ ﺇﺩﺭﺍﺝ ‪ SNR‬ﻟﻜﻞ ﻣﻮﺩﻡ ﻓﻲ ﺭﻣﺰ ‪ EC‬ﻣﻊ ﺗﻔﺎﺻﻴﻞ ﻣﻮﺩﻡ ‪.show cable‬‬

‫ﻛﻤﺎ ﻳﺴﺮﺩ ﺍﻷﻣﺮ ‪ phy‬ﺳﻤﺎﺕ ﺍﻟﻄﺒﻘﺔ ﺍﻟﻤﺎﺩﻳﺔ ﺍﻷﺧﺮﻯ ﻓﻲ ﺣﺎﻟﺔ ﺗﻜﻮﻳﻦ ﺍﻻﺳﺘﻌﻼﻡ ﻋﻦ ﺑﻌﺪ‪ .‬ﻳﻤﻜﻦ ﺇﺩﺧﺎﻝ ﻫﺬﻩ ﺍﻷﺳﻄﺮ‬
‫ﺍﻟﺜﻼﺛﺔ ﻟﻠﺘﻌﻠﻴﻤﺎﺕ ﺍﻟﺒﺮﻣﺠﻴﺔ ﻟﺘﻨﺸﻴﻂ ﺍﻻﺳﺘﻌﻼﻡ ﻋﻦ ﺑﻌﺪ‪:‬‬

‫‪snmp-server manager‬‬
‫‪snmp-server community public ro‬‬
‫‪cable modem remote-query 3 public‬‬
 ‫ﺗﻢ ﺇﺳﺘﺨﺪﺍﻡ ﺛﻼﺙ ﺛﻮﺍﻥ ﻟﻼﺳﺘﺠﺎﺑﺔ ﺍﻟﺴﺮﻳﻌﺔ‪ ،‬ﻭﺍﻟﺘﻲ ﻗﺪ ﻻ ﻳﻮﺻﻰ ﺑﻬﺎ ﻓﻲ ‪ CMTS‬ﺍﻟﻤﺤﻤﻠﺔ ﺑﺸﺪﺓ‪ .‬ﺳﻠﺴﻠﺔ ﺍﻟﻤﺠﺘﻤﻊ‬
‫ﺍﻻﻓﺘﺮﺍﺿﻴﺔ ﻟﻠﻘﺮﺍﺀﺓ ﻓﻘﻂ ﻓﻲ ﻣﻌﻈﻢ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﻫﻲ ‪.‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻋﺪﻡ ﻣﺮﺍﻋﺎﺓ ﺇﺩﺧﺎﻝ ﺍﻻﻧﻌﻜﺎﺱ ﺍﻟﺠﺰﺋﻲ‪ ،‬ﻷﻥ ﻫﺬﺍ ﻣﻦ ﺃﺟﻞ ‪ DS‬ﻭﻳﺤﺪ ﻣﻦ ﺩﻗﺔ ﺗﻨﻔﻴﺬ ﻣﻮﺭﺩ ‪.CM‬‬

‫‪ubr7246# show cable modem 000b.06a0.7116 cnr‬‬

‫‪MAC Address‬‬ ‫‪IP Address‬‬ ‫‪I/F‬‬ ‫‪MAC‬‬ ‫‪Prim snr/cnr‬‬

‫‪(State‬‬ ‫‪Sid‬‬ ‫‪(dB‬‬
‫‪000b.06a0.7116 10.200.100.158 C6/0/U0 online 10‬‬ ‫‪38‬‬

‫ﻳﺴﺮﺩ ﻫﺬﺍ ﺍﻷﻣﺮ ‪ SNR‬ﻋﻨﺪ ﺇﺳﺘﺨﺪﺍﻡ ﺑﻄﺎﻗﺔ ‪ .C‬ﻋﻨﺪ ﺇﺳﺘﺨﺪﺍﻡ ﺑﻄﺎﻗﺔ ‪ S‬ﻭﺗﺨﺼﻴﺺ ﻣﺠﻤﻮﻋﺎﺕ ﺍﻟﻄﻴﻒ‪ ،‬ﻳﺘﻢ ﺍﻹﺑﻼﻍ ﻋﻦ‬
‫‪ .CNR‬ﻛﻤﺎ ﻳﻌﻤﻞ ﺍﻷﻣﺮ ‪ show cable modem mac-address verbose‬ﺃﻳﻀﺎ‪.‬‬

‫ﻛﻴﻔﻴﺔ ﻋﺮﺽ ﺃﺭﺿﻴﺔ ﺍﻟﻀﻮﺿﺎﺀ‬

‫ﻛﻤﺎ ﺗﺘﻴﺢ ﻟﻚ ﺑﻄﺎﻗﺎﺕ ‪ s٪‬ﻋﺮﺽ ﺃﺭﺿﻴﺔ ﺍﻟﻀﻮﺿﺎﺀ ﺑﺎﺳﺘﺨﺪﺍﻡ ﻫﺬﺍ ﺍﻷﻣﺮ‪:‬‬

‫‪? ubr7246-2# show controller cable6/0 upstream 0 spectrum‬‬

‫‪start frequency in MHz‬‬ ‫>‪<5-55‬‬

‫‪start frequency in KHz‬‬ ‫>‪<5000-55000‬‬
‫>‪start frequency in Hz <5000000-55000000‬‬
‫‪A.B.C.D‬‬ ‫‪IP address of the modem‬‬
‫‪H.H.H‬‬ ‫‪MAC address of the modem‬‬
‫ﻳﺆﺩﻱ ﺇﺿﺎﻓﺔ ﻋﻨﻮﺍﻥ ‪ IP‬ﺃﻭ ‪ MAC‬ﻟﻠﻤﻮﺩﻡ ﺇﻟﻰ ﺍﻷﻣﺮ ﺇﻟﻰ ﺇﻇﻬﺎﺭ ﻗﻮﺓ ﺍﻧﻔﺠﺎﺭ ﺍﻟﻤﻮﺩﻡ ﻭﻋﺮﺽ ﺍﻟﻘﻨﺎﺓ‪.‬‬

‫‪? ubr7246-2# show controller cable6/0 upstream 0 spectrum 5 55‬‬

‫‪resolution frequency in MHz‬‬ ‫>‪<1-50‬‬

‫‪ubr7246-2# show controller cable6/0 upstream 0 spectrum 5 55 3‬‬

‫‪:Spect DATA(@0x61359914) for u0: 5000-55000KHz(resolution 3000KHz, sid 0‬‬

‫‪Freq(KHz) dBmV Chart‬‬
‫‪-60‬‬ ‫‪: 5000‬‬
‫‪**************** -23‬‬ ‫‪: 8000‬‬
‫‪***** -45‬‬ ‫‪:11000‬‬
‫‪***** -46‬‬ ‫‪:14000‬‬
‫‪-55‬‬ ‫‪:17000‬‬
‫‪-60‬‬ ‫‪:20000‬‬
‫‪-60‬‬ ‫‪:23000‬‬
‫‪-55‬‬ ‫‪:26000‬‬
‫‪******************* -18‬‬ ‫‪:29000‬‬
‫‪-60‬‬ ‫‪:32000‬‬
‫‪-60‬‬ ‫‪:35000‬‬
‫‪-60‬‬ ‫‪:38000‬‬
‫‪-55‬‬ ‫‪:41000‬‬
‫‪***** -45‬‬ ‫‪:44000‬‬
‫‪-60‬‬ ‫‪:47000‬‬
‫‪-60‬‬ ‫‪:50000‬‬
‫‪******* -41‬‬ ‫‪:53000‬‬
‫ﻫﺬﺍ ﺍﻟﻤﺨﺮﺝ ﻳﻈﻬﺮ ﺍﻟﻀﻮﺿﺎﺀ ﺗﺤﺖ ﺍﻟﻨﺎﻗﻞ ﻭﺑﺘﺮﺩﺩﺍﺕ ﺃﺧﺮﻯ‪.‬‬

‫ﺑﺎﻹﺿﺎﻓﺔ ﺇﻟﻰ ﻭﺍﺟﻬﺔ ﺳﻄﺮ ﺍﻷﻭﺍﻣﺮ )‪ ،(CLI‬ﻳﻤﻜﻦ ﺇﺳﺘﺨﺪﺍﻡ ﺃﺩﻭﺍﺕ ﺇﺩﺍﺭﺓ ﺍﻟﺸﺒﻜﺔ ﺍﻟﻤﺴﺘﻨﺪﺓ ﺇﻟﻰ ﺑﺮﻭﺗﻮﻛﻮﻝ ‪ SNMP‬ﻣﺜﻞ‬
 ‫ﻣﺴﺘﻜﺸﻒ ﺃﺧﻄﺎﺀ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﺍﻟﻌﺮﻳﺾ )‪ (CBT‬ﻣﻦ ‪ Cisco‬ﻟﻌﺮﺽ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ‬
‫ﻭﺍﻟﺨﺼﺎﺋﺺ ﺍﻷﺧﺮﻯ‪ .‬ﺃﻳﻀﺎ‪ ،‬ﻳﻤﻜﻦ ﺇﺳﺘﺨﺪﺍﻡ ‪ CiscoWorks‬ﻟﻤﺮﺍﻗﺒﺔ ‪ SNR‬ﻛﻤﺎ ﺗﻢ ﺍﻹﺑﻼﻍ ﻋﻨﻪ ﺑﻮﺍﺳﻄﺔ ﺳﻼﺳﻞ ﺍﻟﻜﺒﻼﺕ‬
‫ﺑﺎﺳﺘﺨﺪﺍﻡ ﻛﺎﺋﻦ ‪:docsiIfSigQSignalNoise‬‬

‫‪DOCS-IF-MIB‬‬
‫‪docsIfSigQSignalNoise.1.3.6.1.2.1.10.127.1.1.4.1.5‬‬
‫‪.Signal/Noise ratio as perceived for this channel‬‬
‫‪At the CM, describes the Signal/Noise of the downstream‬‬
‫‪channel. At the CMTS, describes the average Signal/Noise‬‬
‫‪.of the upstream channel‬‬
‫ﻣﻼﺣﻈﺔ‪ :‬ﺗﺘﻮﻓﺮ ﻗﺮﺍﺀﺍﺕ ‪ CM SNR‬ﺍﻟﻔﺮﺩﻳﺔ ﻓﻘﻂ ﻋﻠﻰ ﻋﻼﻣﺘﻲ ‪ MC5x20S‬ﻭ ‪ .MC28U‬ﻭﺗﺘﻀﻤﻦ ﻫﺬﻩ ﺍﻷﺳﻄﺮ ﺍﻟﺠﺪﻳﺪﺓ‬
‫ﺇﻟﻐﺎﺀ ﺍﻟﻤﺪﺧﻞ ﺍﻟﺬﻱ ﻗﺪ ﻳﺤﺴﻦ ﺍﻷﺩﺍﺀ ﻭﻟﻜﻦ ﻳﻤﻜﻦ ﺃﻥ ﺗﻌﻄﻲ ﻗﺮﺍﺀﺍﺕ ﻣﻀﻠﻠﺔ ﻟﻠﺨﺎﺩﻡ ﺍﻵﻣﻦ‪ .‬ﺗﻜﻮﻥ ﻗﺮﺍﺀﺍﺕ ‪ SNR‬ﺑﻌﺪ‬
‫ﺇﻟﻐﺎﺀ ﺍﻟﺪﺧﻮﻝ‪ ،‬ﻟﺬﻟﻚ ﺇﺫﺍ ﻗﺎﻡ ﺇﻟﻐﺎﺀ ﺍﻟﻤﺪﺧﻞ ﺭﻳﺎﺿﻴﺎ ﺑﺈﺯﺍﻟﺔ ﺍﻟﻤﺪﺧﻞ‪ ،‬ﻓﻴﻤﻜﻦ ﻝ ‪ SNR‬ﺍﻹﺑﻼﻍ ﻋﻦ ﺃﻓﻀﻞ ﺑﻜﺜﻴﺮ ﻣﻦ ﻧﺴﺒﺔ‬
‫ﺍﻟﻨﻘﻞ ﺇﻟﻰ ﺍﻟﺘﺪﺍﺧﻞ ﺍﻟﻔﻌﻠﻴﺔ‪.‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻋﻨﺪ ﺇﺳﺘﺨﺪﺍﻡ ﻣﺠﻤﻮﻋﺎﺕ ﺍﻟﻄﻴﻒ ﻋﻠﻰ ﺑﻄﺎﻗﺔ ‪ ،S‬ﻳﺤﺪﺩ ﺍﻷﻣﺮ ‪ show controllers‬ﻗﺮﺍﺀﺍﺕ ‪ CNR‬ﺑﺸﻜﻞ ﻋﺸﻮﺍﺋﻲ‬
‫ﻣﻦ ﺟﻤﻴﻊ ﺑﻄﺎﻗﺎﺕ ‪ CMs‬ﺍﻟﻤﻮﺟﻮﺩﺓ ﻋﻠﻰ ﺫﻟﻚ ﺍﻟﻤﻮﺟﻮﺩ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ‪ ،‬ﻭﺍﻟﺬﻱ ﻗﺪ ﻳﻜﻮﻥ ﻣﺨﺘﻠﻔﺎ ﻗﻠﻴﻼ‪ ،‬ﻣﻤﺎ ﻳﻌﻄﻲ‬
‫ﻣﻈﻬﺮ ﻣﻨﻔﺬ ‪ US‬ﻏﻴﺮ ﻣﺴﺘﻘﺮ ﺃﻭ ‪.CNR‬‬

‫ﻧﺎﻗﻼﺕ ﺍﻟﺨﺎﺩﻡ ﺑﻔﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ ﺻﻔﺮ‬

‫ﺻﻴﻐﺔ ﺗﺴﺘﺤﻖ ﺇﺳﺘﺨﺪﺍﻡ ﻓﻲ ﻣﺤﻠﻞ ﻃﻴﻒ ﻫﻲ ﺻﻴﻐﺔ ﺻﻔﺮ ﻓﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ‪ .‬ﻫﺬﺍ ﻫﻮ ﺍﻟﻮﺿﻊ ﺍﻟﺰﻣﻨﻲ ﻟﻠﻤﺠﺎﻝ ﺣﻴﺚ‬
‫ﺍﻟﻌﺮﺽ ﻫﻮ ﺍﻻﺗﺴﺎﻉ ﻣﻘﺎﺑﻞ ﺍﻟﺰﻣﻦ ﺑﺪﻻ ﻣﻦ ﺍﻻﺗﺴﺎﻉ ﻣﻘﺎﺑﻞ ﺍﻟﺘﺮﺩﺩ‪ .‬ﻭﻳﻜﻮﻥ ﻫﺬﺍ ﺍﻟﻮﺿﻊ ﻣﻔﻴﺪﺍ ﻟﻠﻐﺎﻳﺔ ﻋﻨﺪ ﻋﺮﺽ ﺣﺮﻛﺔ ﻣﺮﻭﺭ‬
‫ﺍﻟﺒﻴﺎﻧﺎﺕ ﺍﻟﻤﺘﻘﻄﻌﺔ ﻓﻲ ﻃﺒﻴﻌﺘﻬﺎ‪ .‬ﺍﻟﺸﻜﻞ ‪ 1‬ﻳﻌﺮﺽ ﻣﺤﻠﻞ ﻧﻄﺎﻕ ﻓﻲ ﺻﻔﺮ ﻓﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ )ﻣﺠﺎﻝ ﺍﻟﻮﻗﺖ( ﺃﺛﻨﺎﺀ ﺍﻟﻨﻈﺮ‬
‫ﻓﻲ ﺣﺮﻛﺔ ﻣﺮﻭﺭ ﺑﻴﺎﻧﺎﺕ ﺍﻟﻤﻨﺒﻊ ﻣﻦ ‪.CM‬‬

‫ﺷﻜﻞ ‪ - 1‬ﻋﺮﺽ ﺻﻔﺮ‪-‬ﻓﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ ﻋﻠﻰ ﻣﺤﻠﻞ ﻃﻴﻒ‬

‫ﻳﻤﻜﻦ ﻣﺸﺎﻫﺪﺓ ﺣﺰﻡ ﺍﻟﺒﻴﺎﻧﺎﺕ ﻓﻲ ﺍﻟﺸﻜﻞ ‪ ،1‬ﺑﺎﻹﺿﺎﻓﺔ ﺇﻟﻰ ﻃﻠﺒﺎﺕ ﺍﻟﻤﻮﺩﻡ ﻭﺍﻟﻀﻮﺿﺎﺀ ﺍﻟﻨﺎﺗﺠﺔ ﻋﻦ ﺍﻟﻨﺒﻀﺎﺕ‪ .‬ﻭﻫﺬﺍ ﻣﻔﻴﺪ‬
‫ﺟﺪﺍ ﻟﻘﻴﺎﺱ ﺍﻟﻤﺴﺘﻮﻳﺎﺕ ﺍﻟﺮﻗﻤﻴﺔ ﺍﻟﻤﺘﻮﺳﻄﺔ ﻭﻣﺮﺍﻗﺒﺔ ﺍﻟﻀﻮﺿﺎﺀ ﻭﺍﻟﻤﺪﺧﻞ‪ ،‬ﻛﻤﺎ ﻳﻈﻬﺮ ﻓﻲ ﺍﻟﺸﻜﻞ ‪.2‬‬

‫ﺷﻜﻞ ‪ - 2‬ﻗﻴﺎﺱ ﺻﻔﺮ ﻟﻠﻔﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ ﻟﻠﺘﺪﻓﻖ ﻣﻌﺪﻝ ﺭﻗﻤﻴﺎ ﻣﻊ ﺍﻟﻨﺎﻗﻞ‬
‫ﻛﻤﺎ ﻳﻤﻜﻦ ﺇﺳﺘﺨﺪﺍﻡ ﺍﻟﻔﺴﺤﺔ ﺑﻴﻦ ﺩﻋﺎﻣﺘﻴﻦ ﺻﻔﺮ ﻟﻤﻌﺮﻓﺔ ﻣﺎ ﺇﺫﺍ ﻛﺎﻧﺖ ﺍﻟﺤﺰﻡ ﺗﺘﺼﺎﺩﻡ ﻣﻊ ﺑﻌﻀﻬﺎ ﺍﻟﺒﻌﺾ ﻣﻦ ﺗﻮﻗﻴﺖ ﺳﻴﺊ ﺃﻭ‬
‫ﻣﻘﺴﻢ ﻭﺣﺪﺓ ﺍﻻﺳﺘﻘﺒﺎﻝ ﻭﺍﻟﺒﺚ ﺃﻭ ﻋﺰﻝ ﻭﺣﺪﺓ ﺍﻻﺳﺘﻘﺒﺎﻝ ﻭﺍﻟﺒﺚ ﺍﻟﻀﻌﻴﻔﺔ‪ .‬ﺍﻟﺤﺰﻣﺔ ﺍﻟﻤﻮﺟﻬﺔ ﻟﻤﻨﻔﺬ ‪ CMTS‬ﻟﻠﺘﺤﻤﻴﻞ ﻫﻲ‬
‫ﺗﺴﺮﺏ ﻋﻠﻰ ﺁﺧﺮ ﻟﻠﺘﺤﻤﻴﻞ‪ .‬ﺭﺍﺟﻊ ﺍﻟﻮﺛﺎﺋﻖ ﻭﺍﻟﻮﺛﺎﺋﻖ ﺍﻟﻤﺪﺭﺟﺔ ﻓﻲ ﻗﺴﻢ ﺍﻟﻤﻌﻠﻮﻣﺎﺕ ﺫﺍﺕ ﺍﻟﺼﻠﺔ ﻓﻲ ﻫﺬﺍ ﺍﻟﻤﺴﺘﻨﺪ‪ .‬ﺭﺍﺟﻊ‬
‫ﺗﻮﺻﻴﻞ ﻣﻮﺟﻪ ‪ Cisco uBR7200 Series‬ﺑﻤﻮﺟﻪ ﺭﺃﺱ ﺍﻟﻜﺒﻞ ﻟﻠﺤﺼﻮﻝ ﻋﻠﻰ ﻭﺻﻒ ﻹﺟﺮﺍﺀ ﺍﻟﻘﻴﺎﺱ ﺻﻔﺮﻱ ﺍﻟﻔﺴﺤﺔ ﺑﻴﻦ‬
‫ﺩﻋﺎﻣﺘﻴﻦ‪.‬‬

‫ﻳﻤﻜﻦ ﺃﻥ ﺗﺆﺩﻱ ﺗﻘﺮﻳﺒﺎ ﺟﻤﻴﻊ ﺃﻭﺟﻪ ﺍﻟﻘﺼﻮﺭ ﻓﻲ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ ﺍﻟﻤﺬﻛﻮﺭﺓ ﺣﺘﻰ ﺍﻵﻥ ﻓﻲ ﻫﺬﺍ ﺍﻟﻤﺴﺘﻨﺪ ﺇﻟﻰ ﺗﺪﻫﻮﺭ ﺍﻷﺩﺍﺀ‬
‫ﻓﻲ ﺍﻟﻤﺮﺣﻠﺔ ﺍﻟﺘﻤﻬﻴﺪﻳﺔ ﻭﺗﻈﻬﺮ ﻧﻔﺴﻬﺎ ﻋﻠﻰ ﺃﻧﻬﺎ ﻣﻌﺪﻝ ﻧﻘﻞ ﺑﻴﺎﻧﺎﺕ ﺿﻌﻴﻒ ﺩﻭﻥ ﺃﻥ ﺗﻨﻌﻜﺲ ﺑﺎﻟﻀﺮﻭﺭﺓ ﻋﻠﻰ ﻣﻌﺪﻝ ﺗﻜﺮﺍﺭ‬
‫ﺗﺮﺩﺩﻱ ﻣﻨﺨﻔﺾ‪ .‬ﺇﻥ ﻣﻼﺣﻈﺔ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ )ﻭﺍﻟﺘﻲ ﺗﻤﺎﺛﻞ ﺃﺧﻄﺎﺀ ‪ BER‬ﻭ ‪ PER‬ﺍﻟﻀﻌﻴﻔﺔ( ‪ -‬ﺣﺘﻰ‬
‫ﺑﺮﻏﻢ ﺃﻥ ‪ SNR‬ﻳﺒﺪﻭ ﻭﻛﺄﻧﻪ ﺃﻋﻠﻰ ﻣﻦ ﺍﻟﺤﺪ ﺍﻷﺩﻧﻰ ﻟﻤﻌﻴﺎﺭ ‪ -DOCSIS‬ﻳﻤﻜﻦ ﺃﻥ ﺗﺸﻴﺮ ﺇﻟﻰ ﻗﻀﺎﻳﺎ ﻣﺆﻗﺘﺔ ﺃﺧﺮﻯ ﺗﺤﺘﺎﺝ ﺇﻟﻰ‬
‫ﻣﻌﺎﻟﺠﺔ‪ .‬ﻗﺪ ﻳﻜﻮﻥ ﻫﻨﺎﻙ ﺃﻳﻀﺎ ‪ CM‬ﻣﺎﺭﻕ ﻳﺴﺒﺐ ﺃﺧﻄﺎﺀ ﻭﻗﺮﺍﺀﺓ ‪ SNR‬ﻟﺠﻤﻴﻊ ‪ CMs‬ﺍﻷﺧﺮﻯ ﻋﻠﻰ ﻧﻔﺲ ﺍﻟﻮﻻﻳﺎﺕ‪ .‬ﻭﻓﻲ‬
‫ﻫﺬﻩ ﺍﻟﺤﺎﻟﺔ‪ ،‬ﻳﺒﺪﻭ ‪ CNR‬ﻋﻠﻰ ﺍﻟﻨﺤﻮ ﺍﻟﺬﻱ ﻳﻘﺎﺱ ﻋﻠﻰ ﻣﺤﻠﻞ ﺍﻟﻄﻴﻒ ﺟﻴﺪﺍ‪ ،‬ﻭﻟﻜﻦ ‪ CMTS‬ﺳﺘﺒﻠﻎ ﻋﻦ ﺧﻼﻑ ﺫﻟﻚ‪.‬‬

‫ﺗﺼﺤﻴﺢ ﺍﻟﺨﻄﺄ ﻟﻸﻣﺎﻡ‬

‫ﺗﺬﻛﺮ ﺃﻥ ﺗﺮﻣﻴﺰ ‪ Reed-Solomon FEC‬ﻳﺴﺘﺨﺪﻡ ﻹﺿﺎﻓﺔ ﻭﺣﺪﺍﺕ ﺑﺎﻳﺖ ﺗﻤﺎﺛﻞ ﻣﺘﻜﺮﺭﺓ ﺇﻟﻰ ﺣﺰﻡ ﺍﻟﺒﻴﺎﻧﺎﺕ‪ ،‬ﻟﻠﺴﻤﺎﺡ ﺑﺎﻛﺘﺸﺎﻑ‬
‫ﺃﺧﻄﺎﺀ ﺍﻻﻧﺪﻓﺎﻉ ﺍﻟﺘﻲ ﺗﻢ ﺇﺩﺧﺎﻟﻬﺎ ﻣﻦ ﻗﺒﻞ ﻣﺼﻨﻊ ﺍﻟﻜﺒﻼﺕ ﻭﺗﺼﺤﻴﺤﻬﺎ‪.‬‬

‫ﻓﻲ ﻋﺎﻟﻢ ﻣﺜﺎﻟﻲ‪ ،‬ﻧﺎﺩﺭﺍ ﻣﺎ ﺗﺤﺪﺙ ﺃﺧﻄﺎﺀ ﺑﺖ ﻗﺎﺑﻠﺔ ﻟﻠﻘﻴﺎﺱ ﺃﺑﺪﺍ‪ ،‬ﺇﻣﺎ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺃﻭ ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪.‬‬
‫ﻭﻣﻊ ﺫﻟﻚ‪ ،‬ﻋﻨﺪﻣﺎ ﺗﻮﺟﺪ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪ ،‬ﻳﻤﻜﻦ ﺃﻥ ﺗﻜﻮﻥ ﺍﻟﺘﺄﺛﻴﺮﺍﺕ ﺷﺪﻳﺪﺓ ﻭﻳﻤﻜﻦ ﺃﻥ ﻳﺴﺒﺒﻬﺎ ﺃﻱ ﻋﺪﺩ ﻣﻦ‬
‫ﺍﻟﻌﻮﺍﻣﻞ ﺍﻟﻤﺨﺘﻠﻔﺔ‪ .‬ﻫﺬﻩ ﻗﺎﺋﻤﺔ ﺑﺎﻷﺣﺪﺍﺙ ﺍﻟﻤﻌﺮﻭﻓﺔ ﺍﻟﺘﻲ ﻳﻤﻜﻦ ﺃﻥ ﺗﻘﺪﻡ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻋﻠﻰ ﺍﻟﺨﺎﺩﻡ‬
‫ﻭﺍﻟﺘﻲ ﻳﺠﺐ ﻣﺮﺍﻋﺎﺗﻬﺎ ﻋﻨﺪ ﺃﺳﺘﻜﺸﺎﻑ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻭﺇﺻﻼﺣﻬﺎ‪:‬‬

‫ﺗﺪﺍﺧﻞ ﻧﺎﻗﻞ ﺍﻟﻜﻨﺲ‬ ‫●‬

‫ﺗﺤﻤﻴﻞ ﻣﻀﺨﻢ )ﺿﻐﻂ‪ ،‬ﻭﻫﻮ ﺷﻜﻞ ﻣﻦ ﺃﺷﻜﺎﻝ ﺍﻟﻘﻄﻊ(‬ ‫●‬

‫ﻗﻄﻊ ﻟﻴﺰﺭﻱ‬ ‫●‬

‫ﺿﻮﺿﺎﺀ ﺣﺎﺩﺓ ﺃﻭ ﺗﺪﺍﺧﻞ ﺍﻟﺪﺧﻮﻝ‬ ‫●‬

 ‫ﻭﺻﻼﺕ ﻣﺘﻘﻄﻌﺔ ﺃﻭ ﻏﻴﺮ ﻣﺤﻜﻤﺔ‬ ‫●‬

‫ﻋﺰﻝ ﺃﻭ ﻋﺰﻝ ﻣﺠﻤﻌﻲ ﺃﻭ ﻣﻘﺴﻢ ﻋﻨﺪ ﺍﻟﻤﻨﺒﻊ ﺑﺸﻜﻞ ﺿﻌﻴﻒ‬ ‫●‬

‫ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﺍﻟﻤﻌﻴﺒﺔ‬ ‫●‬

‫ﻫﻨﺎﻙ ﻃﺮﻳﻘﺘﺎﻥ ﻳﻤﻜﻦ ﻣﻦ ﺧﻼﻟﻬﻤﺎ ﺟﻤﻊ ﻣﻌﻠﻮﻣﺎﺕ ﻣﺮﻛﺰ ﻓﻴﻴﻨﺎ ﺍﻟﺪﻭﻟﻲ‪:‬‬

‫‪CLI‬‬ ‫●‬

‫ﺍﻟﺘﺤﻘﻖ ﻣﻦ ﻣﻌﺮﻑ ﻛﺎﺋﻦ ‪(SNMP (OID‬‬ ‫●‬

‫ﻫﺬﺍ ﻣﺜﺎﻝ ﻋﻠﻰ ﻛﻴﻔﻴﺔ ﺗﺠﻤﻴﻊ ﻣﻌﻠﻮﻣﺎﺕ ‪ FEC‬ﺑﺎﺳﺘﺨﺪﺍﻡ ﻭﺍﺟﻬﺔ ﺳﻄﺮ ﺍﻷﻭﺍﻣﺮ )ﺭﺍﺟﻊ ﺃﻳﻀﺎ ﺍﻟﻤﻠﺤﻖ(‪:‬‬

‫‪ubr7246vxr# show controller cable3/0‬‬

‫‪Load for five secs: 5%/1%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
‫‪Interface Cable3/0‬‬
‫‪Hardware is MC16C‬‬
‫!‪Output suppressed. Slots 937882 NoUWCollNoEngy 82 FECorHCS 4 HCS 4 Req 1160824263 ReqColl ---‬‬
‫‪350 ReqNoise 96 ReqNoEnergy 1160264889 ReqData 0 ReqDataColl 0 ReqDataNoise 0 ReqDataNoEnergy 0‬‬
‫‪Rng 609652 RngColl 0 RngNoise 76 FECBlks 1638751 UnCorFECBlks 7 CorFECBlks 4‬‬

‫‪ — FECBlks‬ﺍﻟﻌﺪﺩ ﺍﻹﺟﻤﺎﻟﻲ ﻟﻜﺘﻞ ‪) FEC‬ﺍﻟﺠﻴﺪﺓ ﻭﺍﻟﺴﻴﺌﺔ ﻋﻠﻰ ﺣﺪ ﺳﻮﺍﺀ( ﺍﻟﺘﻲ ﻳﺘﻢ ﺗﻠﻘﻴﻬﺎ ﻣﻦ ﻗﺒﻞ ﺟﻤﻴﻊ ﻣﻨﺎﻓﺬ‬ ‫●‬

‫ﺍﻟﻤﻨﺒﻊ ﺍﻟﻤﺮﺗﺒﻄﺔ ﺑﻨﻘﻄﺔ ﻭﺻﻮﻝ ﻣﻌﻴﻨﺔ ﺇﻟﻰ ﺍﻟﺨﺎﺩﻡ‪.‬‬

‫‪ — UnCorFECBlks‬ﺍﻟﻌﺪﺩ ﺍﻹﺟﻤﺎﻟﻲ ﻟﻜﺘﻞ ‪ FEC‬ﺍﻟﺘﻲ ﺗﻢ ﺍﺳﺘﻘﺒﺎﻟﻬﺎ ﺑﻮﺍﺳﻄﺔ ﺟﻤﻴﻊ ﻣﻨﺎﻓﺬ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ ﺇﻟﻰ ﺍﻟﺨﺎﺩﻡ‬ ‫●‬

‫ﺍﻟﻤﺮﺗﺒﻄﺔ ﺑﺘﺪﻓﻖ ﺑﻴﺎﻧﺎﺕ ﻣﺤﺪﺩ ﻭﺍﻟﺘﻲ ﻛﺎﻧﺖ ﺗﺎﻟﻔﺔ ﺑﺴﺒﺐ ﺍﻟﻀﻮﺿﺎﺀ ﺃﻭ ﺍﻟﺪﺧﻮﻝ ﺇﻟﻰ ﺣﺪ ﺗﻌﺬﺭ ﻣﻌﻪ ﺗﺼﺤﻴﺤﻬﺎ ﺃﻭ‬
‫ﺇﺳﺘﺮﺩﺍﺩﻫﺎ ﺑﻮﺍﺳﻄﺔ ﺧﻮﺍﺭﺯﻣﻴﺔ ‪.FEC‬‬
‫‪ — CorFECBlks‬ﺍﻟﻌﺪﺩ ﺍﻹﺟﻤﺎﻟﻲ ﻟﻜﺘﻞ ‪ FEC‬ﺍﻟﺘﻲ ﺗﻢ ﺍﺳﺘﻘﺒﺎﻟﻬﺎ ﺑﻮﺍﺳﻄﺔ ﺟﻤﻴﻊ ﻣﻨﺎﻓﺬ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ ﺇﻟﻰ ﺍﻟﺨﺎﺩﻡ‬ ‫●‬

‫ﺍﻟﻤﺮﺗﺒﻄﺔ ﺑﺘﺪﻓﻖ ﺑﻴﺎﻧﺎﺕ ﻣﺤﺪﺩ ﻭﺍﻟﺘﻲ ﻛﺎﻧﺖ ﺗﺎﻟﻔﺔ ﻗﻠﻴﻼ ﺑﺴﺒﺐ ﺍﻟﻀﻮﺿﺎﺀ ﺃﻭ ﺍﻟﺪﺧﻮﻝ ﻭﺍﻟﺘﻲ ﻳﻤﻜﻦ ﺗﺼﺤﻴﺤﻬﺎ ﻭﺍﺳﺘﺮﺩﺍﺩﻫﺎ‬
‫ﺑﻮﺍﺳﻄﺔ ﺧﻮﺍﺭﺯﻣﻴﺔ ‪.FEC‬‬
‫ﺗﺰﻳﺪ ﻋﻤﻠﻴﺎﺕ ﺻﻴﺎﻧﺔ ﺍﻟﻤﺤﻄﺔ ﻋﺪﺍﺩ ‪ FECBs‬ﺑﻤﻘﺪﺍﺭ ‪ 2‬ﺗﻘﺮﻳﺒﺎ ﻟﻜﻞ ‪ x‬ﺛﺎﻧﻴﺔ‪ ،‬ﺣﻴﺚ ‪ x‬ﻫﻮ ﺍﻟﺤﺪ ﺍﻷﺩﻧﻰ ﻟﻠﻔﺎﺻﻞ ﺍﻟﺰﻣﻨﻲ‬
‫ﻟﻼﺳﺘﻄﻼﻉ )ﻛﻤﺎ ﻫﻮ ﻣﻌﺮﻭﺽ ﻓﻲ ﺍﻷﻣﺮ ‪ (show cable hop‬ﻣﻘﺴﻮﻣﺎ ﻋﻠﻰ ‪ .1000‬ﻛﻤﺎ ﻳﺰﻳﺪ ﺍﻻﺳﺘﻌﻼﻡ ﻋﻦ ﺑﻌﺪ ﻫﺬﺍ‬
‫ﺍﻟﻌﺪﺍﺩ‪ ،‬ﻭﻛﺬﻟﻚ ﺍﻟﺼﻴﺎﻧﺔ ﺍﻷﻭﻟﻴﺔ ﻋﻨﺪ ﺍﺗﺼﺎﻝ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﺑﺎﻹﻧﺘﺮﻧﺖ‪ .‬ﻧﻈﺮﺍ ﻷﻥ ﺍﻟﺼﻴﺎﻧﺔ ﺍﻷﻭﻟﻴﺔ ﺗﺤﺪﺙ ﺃﺛﻨﺎﺀ ﻭﻗﺖ ﺍﻟﺘﺨﺎﻟﻒ‪،‬‬
‫ﻓﻘﺪ ﺗﻜﻮﻥ ﻫﻨﺎﻙ ﺗﺼﺎﺩﻣﺎﺕ ﻭﺃﺧﻄﺎﺀ ‪ FEC‬ﻻﺣﻘﺔ ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪.‬‬

‫ﺗﻠﻤﻴﺢ‪ :‬ﺗﺄﻛﺪ ﻣﻦ ﺃﻥ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﻻ ﺗﺼﻞ ﺇﻟﻰ ﺍﻟﻤﺪﻯ ﺃﻭ ﺗﺼﻞ ﺇﻟﻰ ﺍﻹﻧﺘﺮﻧﺖ ﻗﺒﻞ ﺍﻓﺘﺮﺍﺽ ﺃﻥ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﻏﻴﺮ‬
‫ﻣﺴﺘﻘﺮﺓ ﻓﻘﻂ ﻷﻥ ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﻏﻴﺮ ﺍﻟﺼﺤﻴﺤﺔ ﺁﺧﺬﺓ ﻓﻲ ﺍﻟﺰﻳﺎﺩﺓ‪ .‬ﻛﻤﺎ ﻗﺪ ﺗﺰﻳﺪ ﻗﻴﻤﺔ ‪ NoUwCollNoEngy‬ﺇﺫﺍ ﻛﺎﻧﺖ ﻫﻨﺎﻙ‬
‫ﺃﺟﻬﺰﺓ ﻣﻮﺩﻡ ﺑﻬﺎ ﻣﺸﺎﻛﻞ ﻓﻲ ﺍﻟﺘﻮﻗﻴﺘﺎﺕ‪ Word .‬ﺍﻟﻔﺮﻳﺪ ﺧﺎﺹ ﺏ ‪ ،BRCM‬ﻭﻟﻴﺲ ‪ ،DOCSIS‬ﻭﻫﻮ ﺁﺧﺮ ﻋﺪﺩ ﻣﻦ ﻭﺣﺪﺍﺕ‬
‫ﺍﻟﺒﺎﻳﺖ ﻣﻦ ﺍﻟﺘﻤﻬﻴﺪ‪.‬‬

‫ﻳﻤﻜﻦ ﺗﻘﺪﻳﺮ ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﺑﺎﺳﺘﺨﺪﺍﻡ ‪ .UNcorrFECBlks / FECBlks × 100‬ﻋﺪﺍﺩ ‪ FECBlks‬ﻫﻮ ﺇﺟﻤﺎﻟﻲ ﻛﺘﻞ ‪ FEC‬ﺍﻟﺘﻲ ﺗﻢ‬
‫ﺇﺭﺳﺎﻟﻬﺎ‪ ،‬ﺳﻮﺍﺀ ﻛﺎﻧﺖ ﺟﻴﺪﺓ ﺃﻭ ﺳﻴﺌﺔ‪ .‬ﻫﺬﺍ ﺍﻟﻤﺨﺮﺝ ﻟﻜﻞ ﻣﺠﺎﻝ ‪) MAC‬ﻛﻞ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ(‪ .‬ﻣﻦ ﺍﻻﻓﻀﻞ ﺍﻟﻨﻈﺮ ﺇﻟﻰ‬
‫ﺍﻟﻌﺪﺍﺩﺍﺕ ﺑﻴﻦ ﻓﺘﺮﺓ ﺯﻣﻨﻴﺔ ﻣﺤﺪﺩﺓ ﻟﺘﺮﻯ ﺍﻟﺪﻟﺘﺎ‪.‬‬

‫‪UnCorFECBlks‬‬ ‫ﻣﻼﺣﻈﺔ‪ :‬ﻣﻦ ﺑﻴﻦ ﻋﻴﻮﺏ ﺟﻤﻊ ﻣﻌﻠﻮﻣﺎﺕ ‪ FEC‬ﺑﺎﺳﺘﺨﺪﺍﻡ ﻭﺍﺟﻬﺔ ﺳﻄﺮ ﺍﻷﻭﺍﻣﺮ ﻫﻮ ﻋﺪﻡ ﻓﺼﻞ‬
‫ﻭ‪ CorFECBlks‬ﻭﺇﺟﻤﺎﻟﻲ ‪ FECBlks‬ﻓﻲ ﻛﻞ ﺇﺗﺠﺎﻩ ﻟﻠﺘﺤﻤﻴﻞ‪.‬‬

‫ﻟﻠﻨﻈﺮ ﺇﻟﻰ ﻣﻌﻠﻮﻣﺎﺕ ‪ FEC‬ﻟﻜﻞ ﺗﺪﻓﻖ‪ ،‬ﻳﺠﺐ ﺇﺳﺘﺨﺪﺍﻡ ﻣﻌﺮﻓﺎﺕ ‪ .SNMP OIDs‬ﻳﻤﻜﻨﻚ ﺃﻳﻀﺎ ﺇﺳﺘﺨﺪﺍﻡ ﺍﻷﻣﺮ ‪show cable‬‬
‫‪ hop‬ﻟﻌﺮﺽ ﺃﺧﻄﺎﺀ ‪ FEC‬ﺍﻟﺘﻲ ﻳﻤﻜﻦ ﺗﺼﺤﻴﺤﻬﺎ ﺃﻭ ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻟﻜﻞ ﻣﻨﻔﺬ ﻟﻠﺘﺪﻓﻖ‪ ،‬ﻭﻟﻜﻦ ﻟﻴﺲ ﺇﺟﻤﺎﻟﻲ ﻛﺘﻞ ‪.FEC‬‬

‫‪ubr7246# show cable hop‬‬

‫‪Load for five secs: 5%/1%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
 ‫‪Upstream‬‬ ‫‪Port‬‬ ‫‪Poll Missed Min‬‬ ‫‪Missed Hop‬‬ ‫‪Hop‬‬ ‫‪Corr‬‬ ‫‪Uncorr‬‬
‫‪Port‬‬ ‫‪Status‬‬ ‫‪Rate Poll‬‬ ‫‪Poll‬‬ ‫‪Poll‬‬ ‫‪Thres Period FEC‬‬ ‫‪FEC‬‬
‫‪ms) Count Sample Pcnt‬‬ ‫)‪Pcnt (sec) Errors Errors‬‬
‫‪Cable6/0/U0 21.810 MHz 1000 0‬‬ ‫‪10‬‬ ‫‪0%‬‬ ‫‪75%‬‬ ‫‪15‬‬ ‫‪2664305 3404‬‬
‫* * * ‪Cable6/0/U1 admindown 1000‬‬ ‫‪frequency not set‬‬ ‫‪* * * 0‬‬ ‫‪0‬‬
‫‪Cable6/0/U2 10.000 MHz 1000 * * *set to fixed frequency * * * 0‬‬ ‫‪0‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻳﻌﻤﻞ ﺍﻷﻣﺮ ‪ clear counters‬ﻋﻠﻰ ﻣﺴﺢ ‪ show interface‬ﻭ‪ show cable hop counters‬ﻓﻘﻂ‪ ،‬ﻭﻟﻜﻦ ﻟﻴﺲ‬
‫‪ .show controllers‬ﻻ ﻳﻤﻜﻦ ﻣﺴﺢ ﻋﺪﺍﺩﺍﺕ ﻭﺣﺪﺓ ﺍﻟﺘﺤﻜﻢ ﺇﻻ ﻓﻲ ﺣﺎﻟﺔ ﺇﻋﺎﺩﺓ ﺗﺤﻤﻴﻞ ‪ CMTS‬ﺃﻭ ﺇﻋﺎﺩﺓ ﺗﺪﻭﻳﺮ ﺍﻟﻮﺍﺟﻬﺔ‬
‫ﺑﺎﺳﺘﺨﺪﺍﻡ ﻫﺬﺍ ﺍﻷﻣﺮ‪:‬‬

‫‪ubr# cable power off slot/card‬‬

‫ﻟﻠﺘﺄﻛﻴﺪ‪ ،‬ﺗﺠﺪﺭ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺃﻥ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻳﻨﺘﺞ ﻋﻨﻬﺎ ﺣﺰﻡ ﻣﺴﻘﻄﺔ ﻭﺳﻮﻑ ﺗﺘﺴﺒﺐ ﻋﻠﻰ ﺍﻷﺭﺟﺢ ﻓﻲ‬
‫ﺍﻧﺨﻔﺎﺽ ﺇﻧﺘﺎﺟﻴﺔ ﺑﻴﺎﻧﺎﺕ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ‪ .‬ﻭﻟﻜﻦ ﻗﺒﻞ ﺃﻥ ﺗﺼﻞ ﺍﻷﺣﺪﺍﺙ ﺇﻟﻰ ﻫﺬﻩ ﺍﻟﻤﺮﺣﻠﺔ ﺍﻟﺤﺮﺟﺔ‪ ،‬ﻫﻨﺎﻙ ﻣﻦ ﺍﻟﻤﺆﺷﺮﺍﺕ‬
‫ﻭﺍﻟﺘﻨﺒﺆﺍﺕ ﻣﺎ ﻳﺸﻴﺮ ﺇﻟﻰ ﺃﻥ ﺃﺩﺍﺀ ﺍﻟﻤﻨﺒﻊ ﺁﺧﺬ ﻓﻲ ﺍﻟﺘﺪﻫﻮﺭ‪ .‬ﺗﻌﻤﻞ ﺃﺧﻄﺎﺀ ‪ FEC‬ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻛﻤﺆﺷﺮ ﻋﻠﻰ ﺃﻥ ﻣﻌﺪﻝ‬
‫ﺇﺧﺮﺍﺝ ﺍﻟﺒﻴﺎﻧﺎﺕ ﻣﻦ ﺍﻟﺨﺎﺩﻡ ﻣﻬﻴﻦ‪ ،‬ﻛﻤﺎ ﺗﻌﻤﻞ ﻛﻌﻼﻣﺔ ﺗﺤﺬﻳﺮ ﻻﺣﺘﻤﺎﻝ ﺣﺪﻭﺙ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻓﻲ‬
‫ﺍﻟﻤﺴﺘﻘﺒﻞ‪.‬‬

‫ﺗﻠﻤﻴﺢ‪ :‬ﺇﺫﺍ ﺯﺍﺩ ﻋﺪﺍﺩ ‪ Uncorr‬ﺃﺳﺮﻉ ﺑﻜﺜﻴﺮ ﻣﻦ ﻋﺪﺍﺩ ‪ ،Corr‬ﻓﻘﺪ ﺗﻜﻮﻥ ﺍﻟﻤﺸﻜﻠﺔ ﻣﺘﻌﻠﻘﺔ ﺑﻀﻮﺿﺎﺀ ﺍﻟﻨﺒﻀﺎﺕ‪ .‬ﺇﺫﺍ ﻛﺎﻥ ﺍﻟﻌﺪﺍﺩ‬
‫‪ Corr‬ﻳﺘﺰﺍﻳﺪ ﺑﻨﻔﺲ ﺍﻟﺴﺮﻋﺔ )ﺃﻭ ﺃﺳﺮﻉ ﻣﻦ( ﻋﺪﺍﺩ ‪ ،Uncorr‬ﻓﺈﻧﻪ ﻣﻦ ﺍﻟﻤﺤﺘﻤﻞ ﺃﻥ ﻳﻜﻮﻥ ﻣﺮﺗﺒﻄﺎ ﺏ ‪ AWGN‬ﺃﻭ ﺃﻥ ﺗﻜﻮﻥ‬
‫ﻣﺸﻜﻠﺔ ﺍﻟﺪﺧﻮﻝ ﻓﻲ ﺣﺎﻟﺔ ﻣﺴﺘﻘﺮﺓ ﻣﺜﻞ ‪ ،(Citizen Band (CB‬ﺭﺍﺩﻳﻮ ﻗﺼﻴﺮ ﺍﻟﻤﻮﺟﺔ‪ ،‬ﺗﺸﻮﻩ ﺍﻟﻤﺴﺎﺭ ﺍﻟﺸﺎﺋﻊ )‪،(CPD‬‬
‫ﻭﻫﻜﺬﺍ‪.‬‬

‫ﻛﻴﻔﻴﺔ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﻣﻦ ﺧﻼﻝ ‪SNMP‬‬

‫ﻳﺘﻢ ﺇﺳﺘﺨﺪﺍﻡ ﻣﻌﺮﻓﺎﺕ ‪ SNMP‬ﺍﻟﺜﻼﺛﺔ ﻫﺬﻩ ﻣﻦ ﻣﻠﻒ ﻗﺎﻋﺪﺓ ﻣﻌﻠﻮﻣﺎﺕ ﺍﻹﺩﺍﺭﺓ )‪ (MIB‬ﻝ ‪ DOCS-IF-MIB‬ﻟﺘﺠﻤﻴﻊ ﺃﺧﻄﺎﺀ‬
‫‪ FEC‬ﻭﺗﺤﻠﻴﻠﻬﺎ )ﺍﻟﺘﻲ ﻟﻢ ﻳﺘﻢ ﺗﺼﺤﻴﺤﻬﺎ ﻭﺗﺼﺤﻴﺤﻬﺎ ﻭ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻞ ﻟﻠﺘﺼﺤﻴﺢ—ﺭﺍﺟﻊ ﺃﻳﻀﺎ ﺍﻟﻤﻠﺤﻖ (‪:‬‬

‫‪DOCS-IF-MIB‬‬
‫‪docsIfSigQUnerroreds‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.2‬‬
‫‪.Codewords received on this channel without error‬‬
‫‪This includes all codewords, whether or not they‬‬
‫‪.were part of frames destined for this device‬‬

‫‪docsIfSigQCorrecteds‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.3‬‬
‫‪Codewords received on this channel with correctable‬‬
‫‪errors. This includes all codewords, whether or not‬‬
‫‪.they were part of frames destined for this device‬‬

‫‪docsIfSigQUncorrectables‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.4‬‬
‫‪Codewords received on this channel with uncorrectable‬‬
‫‪errors. This includes all codewords, whether or not‬‬
‫‪.they were part of frames destined for this device‬‬
‫ﻭﻧﻈﺮﺍ ﻷﻥ ﻗﻮﺍﻋﺪ ﻣﻌﻠﻮﻣﺎﺕ ﺍﻹﺩﺍﺭﺓ ﺍﻟﺜﻼﺙ ﻫﺬﻩ ﺗﻤﺜﻞ ﻗﻴﻤﺎ ﻣﻄﻠﻘﺔ )ﺍﺳﺘﻨﺎﺩﺍ ﺇﻟﻰ ﺍﻟﻌﺪﺩ ﺍﻹﺟﻤﺎﻟﻲ ﻟﻤﺠﻤﻮﻋﺎﺕ ﺑﻴﺎﻧﺎﺕ ‪FEC‬‬
‫ﺍﻟﺘﻲ ﻳﺘﻠﻘﺎﻫﺎ ﻧﻈﺎﻡ ﺇﺩﺍﺭﺓ ﺍﻟﺘﻬﻴﺌﺔ )‪ ،((CMTS‬ﻓﺈﻥ ﺣﺴﺎﺏ ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻳﻮﻓﺮ ﺻﻮﺭﺓ ﺃﻓﻀﻞ ﻷﺩﺍﺀ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ ﺍﻟﻔﻌﻠﻲ‪.‬‬
‫ﻳﺠﺐ ﺇﺳﺘﺨﺪﺍﻡ ﻫﺬﻩ ﺍﻟﺼﻴﻎ‪:‬‬

‫‪ CX = docsIfSigQUnerroreds‬ﻓﻲ ‪time x‬‬ ‫●‬

‫‪ ECX = docsIfSigQCorrecteds‬ﻓﻲ ‪time x‬‬ ‫●‬

‫‪ Eux = docsIfSigQUncorrectables‬ﻓﻲ ‪time x‬‬ ‫●‬

‫‪ ٪‬ﺗﺼﺤﻴﺢ = ])‪EC1 - EC0)/ [(EU1 - EU0) + (EC1 - EC0) + (C1 - C0)] * 100‬‬
 ‫‪ ٪‬ﻏﻴﺮ ﻗﺎﺑﻞ ﻟﻠﺘﺼﺤﻴﺢ = ])‪EU1 - EU0)/ [(EU1 - EU0) + (EC1 - EC0) + (C1 - C0)] * 100‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﺗﺴﺎﻭﻱ ‪ Uncorrectables plus unerroreds plus correcetds‬ﺍﻟﻌﺪﺩ ﺍﻹﺟﻤﺎﻟﻲ ﻟﻠﻜﻠﻤﺎﺕ ﺍﻟﺒﺮﻣﺠﻴﺔ )‪CWs‬؛‬
‫ﺍﻟﻤﻌﺮﻭﻓﺔ ﺃﻳﻀﺎ ﺑﺎﺳﻢ ﻛﺘﻞ ﺑﻴﺎﻧﺎﺕ ‪ (FEC‬ﺍﻟﺘﻲ ﺗﻢ ﺗﻠﻘﻴﻬﺎ ﻋﻠﻰ ﻫﺬﻩ ﺍﻟﻮﻻﻳﺎﺕ‪ ،‬ﺑﻤﺎ ﻓﻲ ﺫﻟﻚ ﺟﻤﻴﻊ ﻣﺠﻤﻮﻋﺎﺕ ‪ ،CW‬ﺳﻮﺍﺀ‬
‫ﻛﺎﻧﺖ ﺟﺰﺀﺍ ﻣﻦ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﻤﻮﺟﻬﺔ ﻝ ‪ CMTS‬ﺃﻡ ﻻ‪ .‬ﻳﺘﻢ ﺗﺤﺪﻳﺪ ﺣﺠﻢ ﻭﺯﻥ ﺍﻟﺘﻌﺒﺌﺔ ﺑﻮﺍﺳﻄﺔ ﻣﻠﻒ ﺗﻌﺮﻳﻒ ﺍﻟﺘﻌﺪﻳﻞ‪.‬‬

‫ﻋﺪﺍﺩﺍﺕ ‪ FEC‬ﻟﻜﻞ ﻣﻮﺩﻡ‬

‫ﺇﺫﺍ ﺗﻢ ﺇﺳﻘﺎﻁ ﺣﺰﻣﺔ ‪ ،US‬ﻓﺈﻧﻬﺎ ﺗﺰﻳﺪ ﻣﻦ ﻋﺪﺍﺩ ‪ .FEC Uncorr‬ﻫﺬﺍ ﻳﺤﺪﺙ ﻓﻲ ﺍﻟﻄﺒﻘﺔ ﺍﻟﻤﺎﺩﻳﺔ‪ .‬ﻗﺪ ﺗﺴﺄﻝ ﻋﻦ ﻛﻴﻔﻴﺔ ﺗﻤﻴﻴﺰ‬
‫‪ CMTS‬ﻟﻠﺤﺰﻣﺔ ﺍﻟﻤﺴﻘﻄﺔ‪ ،‬ﺇﺫﺍ ﻟﻢ ﺗﻜﻦ ﻫﻨﺎﻙ ﻓﺮﺻﺔ ﻟﺮﺅﻳﺔ ﻣﻌﺮﻑ ﺍﻟﺨﺪﻣﺔ )‪ (SID‬ﺃﻭ ﻋﻨﻮﺍﻥ ﺍﻟﻤﺼﺪﺭ )ﺍﻟﻄﺒﻘﺔ ‪ .(2‬ﻭﻣﻊ‬
‫ﺫﻟﻚ‪ ،‬ﻳﺘﻢ ﺗﻀﻤﻴﻦ ﻣﻌﺮﻑ ﺃﻣﺎﻥ ‪ CM‬ﻓﻲ ﺭﺃﺱ ‪.DOCSIS‬‬

‫ﻣﺜﺎﻝ ﺍﻧﻔﺠﺎﺭ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ‪:‬‬

‫)ﺍﻟﺪﻳﺒﺎﺟﺔ( ‪ docsis hdr = 6)} +‬ﺑﺎﻳﺖ( ‪ BPI+، DOCSIS extended hdr = 4) +‬ﺇﻟﻰ ‪ 7‬ﺑﺎﻳﺖ( ‪ 1500 +‬ﺇﻳﺜﺮﻧﺖ ‪18 +‬‬
‫ﺭﺃﺱ ﺇﻳﺜﺮﻧﺖ{ ‪) +‬ﻧﻄﺎﻕ ﺍﻻﻟﺘﻔﺎﻑ(‬

‫ﺗﺘﻢ ﺇﺿﺎﻓﺔ ﻛﻞ ﺷﻲﺀ ﺑﻴﻦ } ﻭ {‪ ،‬ﻭﻗﻄﻌﻪ ﺇﻟﻰ ﻭﺣﺪﺍﺕ ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ )‪ (CWs‬ﺍﺳﺘﻨﺎﺩﺍ ﺇﻟﻰ ﻣﻠﻒ ﺗﻌﺮﻳﻒ ﺍﻟﺘﻌﺪﻳﻞ‪ ،‬ﺛﻢ‬
‫ﺗﺘﻢ ﺇﺿﺎﻓﺔ ‪ T×2‬ﺇﻟﻰ ﻛﻞ ﻭﺣﺪﺓ ﺗﺤﻜﻢ‪ .‬ﻟﺬﻟﻚ ﻣﻦ ﺍﻟﻨﺎﺣﻴﺔ ﺍﻟﻔﻨﻴﺔ‪ ،‬ﺇﺫﺍ ﺗﻢ ﺇﺳﻘﺎﻁ ﺍﻟﻜﻠﻤﺔ ﺍﻟﻤﺸﻔﺮﺓ ﺍﻟﻤﺤﺪﺩﺓ ﺍﻟﺘﻲ ﺗﺤﻤﻞ‬
‫ﻣﻌﺮﻑ ﺍﻷﻣﺎﻥ‪ ،‬ﻓﻜﻴﻒ ﻳﻤﻜﻦ ﻝ ‪ CMTS‬ﺍﻟﺘﻤﻴﻴﺰ ﻣﻦ ﺃﻱ ﻣﻮﺩﻡ ﺗﻢ ﺇﺭﺳﺎﻟﻪ؟ ﺗﺘﻤﺜﻞ ﺇﺣﺪﻯ ﺍﻟﻄﺮﻕ ﻟﺘﺤﻘﻴﻖ ﺫﻟﻚ ﻓﻲ ﺇﺳﺘﺨﺪﺍﻡ‬
‫ﻣﺠﺪﻭﻝ ‪ ،CMTS‬ﺍﻟﺬﻱ ﻳﻌﺮﻑ ﺍﻟﻮﻗﺖ ﺍﻟﺬﻱ ﺳﻴﺘﻢ ﻓﻴﻪ ﻭﺻﻮﻝ ﺣﺰﻡ ﻣﻌﻴﻨﺔ ﻣﻦ ﺃﺟﻬﺰﺓ ﻣﻮﺩﻡ ﻣﻌﻴﻨﺔ‪.‬‬

‫ﻳﻤﻜﻨﻚ ﻋﺮﺽ ﻗﻴﻢ ‪ FEC‬ﺍﻟﻤﺪﺭﺟﺔ ﻟﻜﻞ ﻣﻮﺩﻡ ﺑﺎﺳﺘﺨﺪﺍﻡ ﺍﻷﻣﺮ ‪show interface cablePort/slot sid sid-number‬‬
‫‪ .counter verbose‬ﻛﻤﺎ ﻳﻤﻜﻨﻚ ﺇﺳﺘﺮﺩﺍﺩﻫﺎ ﻣﻦ ﺧﻼﻝ ﺑﺮﻭﺗﻮﻛﻮﻝ ‪ SNMP‬ﺑﺎﺳﺘﺨﺪﺍﻡ ﻣﻌﺮﻓﺎﺕ ﺍﻟﻬﻮﻳﺔ ﻫﺬﻩ‪:‬‬

‫ﺗﻢ ﺇﺳﺘﻼﻡ ﻛﻠﻤﺎﺕ ﺍﻟﺘﺮﻣﻴﺰ ﺍﻟﺠﻴﺪﺓ )‪(docsIfCmtsCmStatusUnerroreds‬‬ ‫●‬

‫ﻛﻠﻤﺎﺕ ﺍﻟﺘﺮﻣﻴﺰ ﺍﻟﻤﺼﺤﺤﺔ ﺍﻟﺘﻲ ﺗﻢ ﺗﻠﻘﻴﻬﺎ )‪(docsIfCmtsCmStatusCorrecteds‬‬ ‫●‬

‫ﺗﻢ ﺗﻠﻘﻲ ‪ CodeWords‬ﻏﻴﺮ ﻣﺼﺤﺢ )‪(docsIfCmtsCmStatusUncorrectables‬‬ ‫●‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻻ ﻳﻨﻄﺒﻖ ﻫﺬﺍ ﺍﻷﻣﺮ ﺣﺎﻟﻴﺎ ﺇﻻ ﻋﻠﻰ ﻋﻼﻣﺘﻲ ‪ MC28U‬ﻭ ‪.MC5x20‬‬

‫‪ubr7246-2# show interface cable6/0 sid 10 counter verbose‬‬

‫‪Load for five secs: 5%/1%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
‫‪Sid‬‬ ‫‪: 10‬‬
‫‪Request polls issued‬‬ ‫‪: 0‬‬
‫‪BWReqs {Cont,Pigg,RPoll,Other} : 1, 527835, 0, 0‬‬
‫‪No grant buf BW request drops : 0‬‬
‫‪Rate exceeded BW request drops : 0‬‬
‫‪Grants issued‬‬ ‫‪: 1787705‬‬
‫‪Packets received‬‬ ‫‪: 959478‬‬
‫‪Bytes received‬‬ ‫‪: 1308727992‬‬
‫‪Fragment reassembly completed : 0‬‬
‫‪Fragment reassembly incomplete : 0‬‬
‫‪Concatenated packets received : 0‬‬
‫‪Queue-indicator bit statistics : 0 set, 0 granted‬‬
‫‪Good Codewords rx‬‬ ‫‪: 7412780‬‬
‫‪Corrected Codewords rx‬‬ ‫‪: 186‬‬
‫‪Uncorrectable Codewords rx‬‬ ‫‪: 11‬‬
‫‪Concatenated headers received : 416309‬‬
‫‪Fragmentation headers received : 1670285‬‬
‫‪Fragmentation headers discarded: 17‬‬
‫ﻭﻫﺬﺍ ﺧﺎﺹ ﺑﻬﺬﺍ ﺍﻟﻤﻮﺩﻡ ﻭﻳﺘﻢ ﺗﺤﺪﻳﺚ ﺍﻟﻌﺪﺍﺩﺍﺕ ﻛﻞ ‪ 10‬ﺛﻮﺍﻥ ﺗﻘﺮﻳﺒﺎ‪.‬‬
 ‫‪ubr7246-2# show cable hop cable6/0‬‬

‫‪Load for five secs: 5%/1%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 00:17:13.552 UTC Sat Feb 7 2004‬‬
‫‪Upstream‬‬ ‫‪Port‬‬ ‫‪Poll Missed Min‬‬ ‫‪Missed Hop‬‬ ‫‪Hop‬‬ ‫‪Corr‬‬ ‫‪Uncorr‬‬
‫‪Port‬‬ ‫‪Status‬‬ ‫‪Rate Poll‬‬ ‫‪Poll Poll‬‬ ‫‪Thres Period FEC‬‬ ‫‪FEC‬‬
‫‪ms) Count Sample Pcnt‬‬ ‫)‪Pcnt (sec) Errors Errors‬‬
‫‪Cable6/0/U0‬‬ ‫‪23.870 MHz 1000 0‬‬ ‫‪10‬‬ ‫‪0%‬‬ ‫‪75%‬‬ ‫‪15‬‬ ‫‪186‬‬ ‫‪12‬‬

‫ﻻﺣﻆ ﺃﻥ ﺍﻷﻣﺮ ‪ show cable hop‬ﻳﻘﻮﻡ ﺑﺎﻹﺑﻼﻍ ﻋﻦ ‪ FEC‬ﺃﺧﺮﻯ‪ .‬ﻗﺪ ﻳﺮﺟﻊ ﺍﻟﺴﺒﺐ ﻓﻲ ﺫﻟﻚ ﺇﻟﻰ ﺇﺳﻘﺎﻁ ﻭﺯﻥ ﺍﻟﺘﻌﺒﺌﺔ‬
‫ﺍﻟﺬﻱ ﺻﺎﺩﻑ ﺃﻧﻪ ﻳﻨﺘﻤﻲ ﺇﻟﻰ ﻣﻮﺩﻡ ﺁﺧﺮ‪.‬‬

‫ﻗﺪ ﻳﻜﻮﻥ ﻣﻦ ﺍﻟﻤﺜﻴﺮ ﺃﻥ ﺗﺮﻯ ﺭﺳﻤﺎ ﺑﻴﺎﻧﻴﺎ ﻷﺧﻄﺎﺀ ‪ FEC‬ﻟﻜﻞ ‪ CM‬ﻋﻦ ﻃﺮﻳﻖ ﻓﺤﺺ ﻗﺎﻋﺪﺓ ﻣﻌﻠﻮﻣﺎﺕ ﺍﻹﺩﺍﺭﺓ ﻭﺍﺳﺘﺨﺪﺍﻡ‬
‫ﺭﺍﺳﻢ ﺣﺮﻛﺔ ﺍﻟﻤﺮﻭﺭ ﻣﺘﻌﺪﺩ ﺍﻟﻤﻮﺟﻬﺎﺕ )‪ (MRTG‬ﺃﻭ ﺑﺮﺍﻣﺞ ﺃﺧﺮﻯ ﻣﺜﻞ ‪ .Cisco BT‬ﻳﻤﻜﻦ ﺇﺳﺘﺨﺪﺍﻡ ﻫﺬﺍ ﻟﻤﻌﺮﻓﺔ ﻣﺎ ﺇﺫﺍ‬
‫ﻛﺎﻧﺖ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﻣﻌﻴﻨﺔ ﻟﺪﻳﻬﺎ ﺗﺄﺧﺮ ﻣﺠﻤﻮﻋﺔ ﺿﻌﻴﻒ‪ ،‬ﺇﻧﻌﻜﺎﺳﺎﺕ ﺻﻐﻴﺮﺓ‪ ،‬ﻭﻫﻠﻢ ﺟﺮﺍ‪ .‬ﺳﻴﻜﻮﻥ ﻫﺬﺍ ﺷﻴﺌﺎ ﻳﺆﺛﺮ ﻓﻘﻂ ﻋﻠﻰ‬
‫ﻣﻮﺩﻡ ﻣﻌﻴﻦ‪.‬‬

‫ﻋﺪﺍﺩﺍﺕ ﺣﺰﻡ ﺗﺪﻓﻖ ﺍﻟﺒﻴﺎﻧﺎﺕ‬

‫ﺃﻣﺮ ﺁﺧﺮ ﻳﺴﺮﺩ ﺍﻷﺧﻄﺎﺀ ﻫﻮ ﺍﻷﻣﺮ ‪ .show interface cable5/1/0 upstream‬ﻫﺬﻩ ﺣﺰﻡ‪ ،‬ﻭﺍﻟﺘﻲ ﺗﺨﺘﻠﻒ ﻋﻦ ‪.FEC CWs‬‬
‫ﻳﻤﻜﻦ ﺃﻥ ﺗﺘﺄﻟﻒ ﺍﻟﺤﺰﻣﺔ ﻣﻦ ﺍﻟﻌﺪﻳﺪ ﻣﻦ ‪.CWs‬‬

‫‪ubr10k# show interface cable5/1/0 upstream‬‬

‫‪Load for five secs: 4%/0%; one minute: 5%; five minutes: 5%‬‬
‫‪Time source is NTP, 03:53:43.488 UTC Mon Jan 26 2004‬‬
‫‪Cable5/1/0: Upstream 0 is up‬‬
‫‪Received 48 broadcasts, 0 multicasts, 14923 unicasts‬‬
‫‪discards, 32971 errors, 0 unknown protocol 0‬‬
‫‪packets input, 72 uncorrectable 14971‬‬
‫‪noise, 0 microreflections 4‬‬
‫‪(Total Modems On This Upstream Channel: 12 (12 active‬‬
‫ﻫﺬﻩ ﻫﻲ ﺗﻌﺮﻳﻔﺎﺕ ﺍﻟﻤﺼﻄﻠﺤﺎﺕ‪:‬‬

‫—ﺇﻃﺎﺭﺍﺕ ﺍﻟﺒﺚ ﺍﻟﻤﺴﺘﻠﻤﺔ‪.‬‬ ‫●‬

‫—ﺇﻃﺎﺭﺍﺕ ﺍﻟﺒﺚ ﺍﻟﻤﺘﻌﺪﺩ ﺍﻟﻤﺴﺘﻠﻤﺔ‪.‬‬ ‫●‬

‫‪ — unicasts‬ﺇﻃﺎﺭﺍﺕ ﺍﻟﺒﺚ ﺍﻷﺣﺎﺩﻱ ﺍﻟﻤﺴﺘﻠﻤﺔ‪.‬‬ ‫●‬

‫— ﺯﻳﺎﺩﺍﺕ ﻓﻘﻂ ﻓﻲ ﺑﻄﺎﻗﺔ ﺍﻟﺨﻂ ‪ .MC5x20S‬ﻳﺴﺮﺩ ﺍﻟﺤﺰﻡ ﺍﻟﺘﻲ ﺗﻢ ﺗﺠﺎﻫﻠﻬﺎ ﺑﺴﺒﺐ ﺣﺎﻻﺕ ﺍﻟﺨﻄﺄ ﺍﻟﻤﺨﺘﻠﻔﺔ‬ ‫●‬

‫ﺍﻟﺨﺎﺻﺔ ﺑﺎﻟﺒﻄﺎﻗﺔ‪ ،‬ﻭﻟﻴﺲ ﺑﺎﻹﻃﺎﺭ ﺍﻟﻔﻌﻠﻲ‪.‬‬

‫— ﻣﺠﻤﻮﻉ ﻣﺠﻤﻮﻋﺔ ﻛﺎﻣﻠﺔ ﻣﻦ ﺍﻻﺧﻄﺎﺀ‪ ،‬ﻭﺍﻟﻜﺜﻴﺮ ﻣﻨﻬﺎ ﻻ ﻳﻬﻢ‪ .‬ﺍﻷﺧﻄﺎﺀ ﺍﻟﺘﻲ ﺗﻌﺪﻫﺎ ﻫﺬﻩ ﺍﻟﻘﻴﻤﺔ ﻫﻲ ﻟﻠﺒﻄﺎﻗﺎﺕ‬ ‫●‬

‫ﺍﻟﻤﺴﺘﻨﺪﺓ ﺇﻟﻰ ‪ BCM3210‬ﻣﺜﻞ ‪ MC16C‬ﻭ ‪:MC28C‬ﻋﺪﺩ ﻓﺘﺤﺎﺕ ﺍﻟﺘﺤﻤﻴﻞ ﺍﻟﻤﺨﺼﺼﺔ ﺣﻴﺚ ﻟﻢ ﻳﺘﻢ ﺇﺳﺘﻼﻡ ﺍﻟﺪﻳﺒﺎﺟﺔ‬
‫ﻭ ‪ Unique Word‬ﺑﺸﻜﻞ ﺻﺤﻴﺢ‪.‬ﻋﺪﺩ ﺍﻹﻃﺎﺭﺍﺕ ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺍﻟﺘﻲ ﺗﻢ ﺗﻠﻘﻴﻬﺎ‪.‬ﺍﻟﺘﺼﺎﺩﻣﺎﺕ ﻓﻲ ﻓﺮﺹ "ﻃﻠﺐ"‬
‫ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ‪.‬ﺗﺼﺎﺩﻣﺎﺕ ﻓﻲ ﻓﺘﺤﺎﺕ "ﻃﻠﺐ‪/‬ﺑﻴﺎﻧﺎﺕ" )ﻻ ﺗﺤﺪﺙ ﻫﺬﻩ ﺍﻷﻧﻮﺍﻉ ﻣﻦ ﺍﻟﻔﺘﺤﺎﺕ ﻋﻠﻰ ‪Cisco‬‬
‫‪.(CMTS‬ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﺎﻟﻔﺔ ﺍﻟﺘﻲ ﻳﺘﻢ ﺗﻠﻘﻴﻬﺎ ﺃﺛﻨﺎﺀ ﻓﺮﺹ "ﻃﻠﺐ" ﻋﺮﺽ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ‪.‬ﺗﻢ ﺇﺳﺘﻼﻡ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﺎﻟﻔﺔ‬
‫ﺃﺛﻨﺎﺀ ﻓﺘﺤﺎﺕ "ﺍﻟﻄﻠﺐ‪/‬ﺍﻟﺒﻴﺎﻧﺎﺕ"‪.‬ﻋﺪﺩ ﻃﻠﺒﺎﺕ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺎﻟﻔﺔ ﺍﻟﺘﻲ ﺗﻢ ﺳﻤﺎﻋﻬﺎ‪.‬ﻟﺨﻄﻮﻁ ﻣﺴﺘﻨﺪﺓ ﺇﻟﻰ ﺟﻴﺐ ﻣﺜﻞ ‪MC5x20‬‬
‫ﻭ ‪:MC28U‬ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﻤﻨﺠﺰﺓ ﺍﻟﺘﻲ‪ ،‬ﻟﺴﺒﺐ ﻣﺎ‪ ،‬ﻻ ﻳﺘﻢ ﺗﺼﻨﻴﻔﻬﺎ ﻛﺘﺴﻠﺴﻞ ﺍﻟﺘﺤﻘﻖ ﻣﻦ ﺍﻟﺮﺃﺱ )‪ (HCS‬ﺃﻭ ﺍﻟﺘﺤﻘﻖ‬
‫ﺍﻟﺪﻭﺭﻱ ﻣﻦ ﺍﻟﺘﻜﺮﺍﺭ )‪ (CRC‬ﺧﺎﻃﺌﺔ‪.‬ﺇﻃﺎﺭﺍﺕ ﺍﻟﻤﻨﺒﻊ ﺍﻟﺘﻲ ﺑﻬﺎ ﻣﺸﺎﻛﻞ ﻓﻲ ‪.HCS‬ﺇﻃﺎﺭﺍﺕ ﺍﻟﻤﻨﺒﻊ ﻣﻊ ﺃﺧﻄﺎﺀ ‪.CRC‬ﺗﻢ‬
‫ﺗﻠﻘﻲ ﻭﺣﺪﺍﺕ ﺗﺨﺰﻳﻦ ﻣﺆﻗﺖ )‪ (CW‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻺﺻﻼﺡ‪.‬ﺍﻟﺘﺼﺎﺩﻣﺎﺕ ﻓﻲ ﻃﻠﺐ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ‪.‬‬
‫—ﻋﺪﺩ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﻤﺴﺘﻠﻤﺔ ﺍﻟﺘﻲ ﻟﻢ ﺗﻜﻦ ‪ IP‬ﺃﻭ ﺑﺮﻭﺗﻮﻛﻮﻝ ﺗﺤﻠﻴﻞ ﺍﻟﻌﻨﻮﺍﻥ )‪ (ARP‬ﺃﻭ ﺑﺮﻭﺗﻮﻛﻮﻝ ﻧﻘﻄﺔ ﺇﻟﻰ ﻧﻘﻄﺔ‬ ‫●‬

‫ﻋﺒﺮ ﺍﻹﻳﺜﺮﻧﺖ )‪ .(PPPoE‬ﻛﻤﺎ ﻳﺘﻀﻤﻦ ﻫﺬﺍ ﺍﻟﻌﺪﺍﺩ ﺇﻃﺎﺭﺍﺕ ﺫﺍﺕ ﺭﺅﻭﺱ ‪ DOCSIS‬ﻣﻜﻮﻧﺔ ﺑﺸﻜﻞ ﻏﻴﺮ ﺻﺤﻴﺢ ﺃﻭ‬
‫ﺧﻴﺎﺭﺍﺕ ﺭﺃﺱ ﻏﻴﺮ ﺻﺤﻴﺤﺔ‪.‬‬
 ‫— ﺇﺟﻤﺎﻟﻲ ﻭ ﻭ‪.‬‬ ‫●‬

‫—ﺇﺟﻤﺎﻟﻲ ﻋﺪﺩ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﻲ ﺗﺤﺘﻮﻱ ﻋﻠﻰ ﻭﺣﺪﺓ ﺗﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ )‪ (FEC‬ﻭﺍﺣﺪﺓ ﻏﻴﺮ ﺻﺤﻴﺤﺔ ﻋﻠﻰ ﺍﻷﻗﻞ‬ ‫●‬

‫ﺩﺍﺧﻠﻬﺎ‪ .‬ﻳﻈﻬﺮ ﻫﺬﺍ ﺍﻟﺤﻘﻞ ‪ N/A‬ﻝ ‪ MC5x20‬ﻭ ‪ .28U‬ﺃﺳﺘﺨﺪﻡ ﻋﻤﻮﺩ ‪ Uncorr FEC‬ﻓﻲ ﺇﺧﺮﺍﺝ ‪show cable hop‬‬
‫ﺑﺪﻻ ﻣﻦ ﺫﻟﻚ‪ ،‬ﻟﻠﺤﺼﻮﻝ ﻋﻠﻰ ﻓﻜﺮﺓ ﺣﻮﻝ ﺍﻷﺧﻄﺎﺀ ﻏﻴﺮ ﺍﻟﺼﺤﻴﺤﺔ‪.‬‬
‫— ﺑﺎﻟﻨﺴﺒﺔ ﻟﻠﺒﻄﺎﻗﺎﺕ ﺍﻟﻘﺎﺋﻤﺔ ﻋﻠﻰ ﻣﻌﻴﺎﺭ ‪ BCM3210‬ﻣﺜﻞ ‪ MC16C‬ﻭ ‪ ،MC28C‬ﻫﺬﺍ ﻫﻮ ﻋﺪﺩ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﺎﻟﻔﺔ‬ ‫●‬

‫ﺍﻟﺘﻲ ﺗﻢ ﺇﺳﺘﻼﻣﻬﺎ ﻓﻲ ﻓﻮﺍﺻﻞ "ﻃﻠﺐ" ﻋﺮﺽ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﺃﻭ "ﺍﻟﻤﺪﻯ"‪ .‬ﻭﻫﺬﺍ ﻳﺠﻌﻞ ﻫﺬﺍ ﺍﻟﺮﻗﻢ ﻣﺠﻤﻮﻋﺔ ﻓﺮﻋﻴﺔ‬
‫ﻣﻦ ﺍﻷﺭﻗﺎﻡ ﻓﻲ ‪.‬ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﺎﻟﻔﺔ ﺍﻟﺘﻲ ﻳﺘﻢ ﺗﻠﻘﻴﻬﺎ ﺃﺛﻨﺎﺀ ﻓﺮﺹ "ﻃﻠﺐ" ﻋﺮﺽ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻳﺘﻢ ﺇﺳﺘﻼﻡ ﺍﻹﻃﺎﺭﺍﺕ‬
‫ﺍﻟﺘﺎﻟﻔﺔ ﺃﺛﻨﺎﺀ ﻓﺘﺤﺎﺕ "ﺍﻟﻄﻠﺐ‪/‬ﺍﻟﺒﻴﺎﻧﺎﺕ"‪.‬ﻋﺪﺩ ﻃﻠﺒﺎﺕ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺎﻟﻔﺔ ﺍﻟﺘﻲ ﺗﻢ ﺳﻤﺎﻋﻬﺎ‪.‬ﺑﺎﻟﻨﺴﺒﺔ ﻟﻠﺒﻄﺎﻗﺎﺕ ﺍﻟﻤﺴﺘﻨﺪﺓ ﺇﻟﻰ‬
‫ﻣﺠﻤﻮﻋﺔ ﺍﻟﻨﻈﺮﺍﺀ ﻣﺜﻞ ‪ ،MC5x20‬ﻻ ﻳﺘﺰﺍﻳﺪ ﻫﺬﺍ ﺍﻟﻌﺪﺍﺩ ﻋﻠﻰ ﺍﻹﻃﻼﻕ‪.‬‬
‫ﺍﻟﺼﻐﺮﻳﺔ — ﻋﺪﺩ ﺍﻻﻧﻌﻜﺎﺳﺎﺕ ﺍﻟﺼﻐﺮﻳﺔ؛ ﻳﺠﺮﻱ ﺩﺍﺋﻤﺎ ﺗﻌﻴﻴﻨﻬﺎ ﺇﻟﻰ ‪.0‬‬ ‫●‬

‫ﻭ ﺑﺘﻌﺪﺍﺩ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﺘﺎﻟﻔﺔ ﻓﺤﺴﺐ‪ ،‬ﺑﻞ ﺗﻘﻮﻡ ﺃﻳﻀﺎ ﺑﺘﻌﺪﺍﺩ ﺃﺷﻴﺎﺀ ﻣﺜﻞ ﺗﺼﺎﺩﻣﺎﺕ ﻃﻠﺐ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﺍﻷﻭﻟﻲ‬
‫ﻭﺗﺼﺎﺩﻣﺎﺕ ﻃﻠﺐ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ‪ .‬ﻟﺬﻟﻚ‪ ،‬ﻻ ﻳﻌﻨﻲ ﺍﻟﻀﺠﻴﺞ ﺍﻟﻤﺘﺰﺍﻳﺪ ﺩﺍﺋﻤﺎ ﺍﻥ ﻫﻨﺎﻟﻚ ﻣﺸﻜﻠﺔ‪ .‬ﻭﻗﺪ ﻳﻌﻨﻲ ﺫﻟﻚ ﺃﻥ ﺍﻟﻌﻤﻴﻞ‬
‫ﻟﺪﻳﻪ ﺍﻟﻜﺜﻴﺮ ﻣﻦ ﺃﺟﻬﺰﺓ ﺍﻟﻤﻮﺩﻡ ﺗﺤﺎﻭﻝ ﺍﻻﺗﺼﺎﻝ ﺑﺎﻹﻧﺘﺮﻧﺖ ﺃﻭ ﻟﺪﻳﻪ ﺃﺟﻬﺰﺓ ﻣﻮﺩﻡ ﺗﺤﺎﻭﻝ ﺇﺟﺮﺍﺀ ﺍﻟﻤﺰﻳﺪ ﻣﻦ ﻋﻤﻠﻴﺎﺕ ﺍﻹﺭﺳﺎﻝ‬
‫ﻋﺪﺍﺩ ﻷﻥ ﺗﺘﻀﻤﻦ ﺍﻟﻤﻜﻮﻧﺎﺕ ﺍﻟﺜﻼﺛﺔ ﺍﻷﺧﻴﺮﺓ ﻣﻦ ﻋﺪﺍﺩ ‪.‬‬ ‫)ﻣﻤﺎ ﻳﺆﺩﻱ ﺇﻟﻰ ﻣﺰﻳﺪ ﻣﻦ ﺍﻟﺘﺼﺎﺩﻣﺎﺕ ﺍﻟﻤﺬﻛﻮﺭﺓ(‪ .‬ﻋﺪﺍﺩ‬

‫ﺍﻟﻘﺮﺍﺭ‬
‫ﻣﻦ ﺧﻼﻝ ﺍﻟﺘﺠﺮﺑﺔ ﻭﺍﻻﺧﺘﺒﺎﺭﺍﺕ ﺍﻟﻤﻌﻤﻠﻴﺔ ﺍﻟﺘﻲ ﺗﻢ ﺇﺟﺮﺍﺅﻫﺎ ﺑﻮﺍﺳﻄﺔ ﺍﻟﺨﺪﻣﺎﺕ ﺍﻟﻤﺘﻘﺪﻣﺔ ﻣﻦ ‪ Cisco‬ﻭﻣﺠﻤﻮﻋﺔ ﺍﻻﺳﺘﺠﺎﺑﺔ‬
‫ﺍﻟﺴﺮﻳﻌﺔ‪ ،‬ﺗﻜﻮﻥ ﻫﺬﻩ ﺑﻌﺾ ﺍﻟﻤﻼﺣﻈﺎﺕ ﺍﻟﻤﺘﻌﻠﻘﺔ ﺏ ‪ FEC‬ﻭﺍﻷﺩﺍﺀ ﺍﻟﻀﻌﻴﻒ ﻟﻠﺒﺪﺍﻳﺔ‪:‬‬

‫ﺇﻥ ﻭﺟﻮﺩ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻳﻌﺘﺒﺮ ﻣﻘﻴﺎﺳﺎ ﺟﻴﺪﺍ ﻋﻨﺪﻣﺎ ﺗﺼﻞ ﺍﻟﻀﻮﺿﺎﺀ ﺇﻟﻰ ﻣﺴﺘﻮﻯ ﻻ ﻳﻤﻜﻦ ﺗﺤﻤﻠﻪ ﺃﻭ‬ ‫●‬

‫ﻋﻨﺪﻣﺎ ﺗﺘﺼﺎﺩﻡ ﺍﻟﺤﺰﻡ ﻣﻊ ﺑﻌﻀﻬﺎ ﺍﻟﺒﻌﺾ ﻣﻦ ﺗﻮﻗﻴﺖ ﺳﻴﺊ ﺃﻭ ﻣﻘﺴﻢ ﻭﺣﺪﺓ ﺍﻻﺳﺘﻘﺒﺎﻝ ﻭﺍﻟﺒﺚ ﺍﻟﻀﻌﻴﻒ ﺃﻭ ﻋﺰﻝ‬
‫ﺍﻟﻤﺸﺒﻚ‪ .‬ﻭﻓﻴﻤﺎ ﻳﺘﻌﻠﻖ ﺑﺎﻟﻤﻨﻔﺬ ﺍﻷﺧﻴﺮ‪" ،‬ﺗﺘﺴﺮﺏ" ﺣﺰﻣﺔ ﻣﻮﺟﻬﺔ ﻟﻤﻨﻔﺬ ‪ CMTS‬ﻭﺍﺣﺪ ﻓﻲ ﺃﻋﻠﻰ ﺍﻟﻤﺠﺮﻯ ﺇﻟﻰ ﺁﺧﺮ ﺃﻋﻠﻰ‬
‫ﺍﻟﻤﺠﺮﻯ ﺑﺴﺒﺐ ﺿﻌﻒ ﺍﻟﻌﺰﻝ‪.‬‬
‫ﺗﺆﺩﻱ ﺯﻳﺎﺩﺓ ﻛﺒﻴﺮﺓ ﻓﻲ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺇﻟﻰ ﺣﺪﻭﺙ ﻣﺸﺎﻛﻞ ﻓﻲ ﺟﻮﺩﺓ ﺍﻟﺼﻮﺕ‪.‬‬ ‫●‬

‫ﺗﻈﻬﺮ ﺃﺧﻄﺎﺀ ‪ FEC‬ﺍﻟﺘﻲ ﻳﻤﻜﻦ ﺗﺼﺤﻴﺤﻬﺎ ﻣﻊ ﺯﻳﺎﺩﺓ ﻣﺴﺘﻮﻯ ﺍﻟﺘﺸﻮﻳﺶ‪ .‬ﻻ ﻳﻨﺘﺞ ﻋﻦ ﺃﺧﻄﺎﺀ ‪ FEC‬ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‬ ‫●‬

‫ﺣﺎﻻﺕ ﺇﺳﻘﺎﻁ ﺍﻟﺤﺰﻡ ﺃﻭ ﺟﻮﺩﺓ ﺻﻮﺕ ﺭﺩﻳﺌﺔ‪ ،‬ﻃﺎﻟﻤﺎ ﻻ ﺗﻮﺟﺪ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪.‬‬
‫ﻗﺪ ﺗﺴﺎﻋﺪ ﺯﻳﺎﺩﺓ ﺑﺎﻳﺖ ‪ FEC‬ﻓﻲ ﻣﻠﻒ ﺗﻌﺮﻳﻒ ﺗﻌﺪﻳﻞ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﺣﺘﻰ ﻧﻘﻄﺔ ﻣﻌﻴﻨﺔ‪ ،‬ﻭﻟﻜﻨﻬﺎ ﺗﻌﺘﻤﺪ ﻋﻠﻰ ﻣﺼﺪﺭ‬ ‫●‬

‫ﺍﻟﻀﻮﺿﺎﺀ‪ .‬ﻭﺗﺒﺪﻭ ﺗﻐﻄﻴﺔ ﻣﺮﻛﺰ ﻓﻴﻴﻨﺎ ﺍﻟﺪﻭﻟﻲ ﺑﻨﺴﺒﺔ ﺳﺒﻌﺔ ﺇﻟﻰ ﻋﺸﺮﺓ ﻓﻲ ﺍﻟﻤﺌﺔ ﻣﺜﺎﻟﻴﺔ‪.‬‬
‫ﻣﻦ ﺍﻟﻤﻼﺣﻈﺎﺕ ﺍﻟﺴﺎﺑﻘﺔ‪ ،‬ﻣﻦ ﺍﻟﻮﺍﺿﺢ ﺃﻥ ﺇﺳﺘﺠﻮﺍﺏ ‪ CMTS‬ﻷﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﺼﺤﻴﺤﺔ ﻟﻪ ﻗﻴﻤﺔ‪ .‬ﻳﻜﻮﻥ ﺍﻟﺼﻮﺕ ﻋﺒﺮ ‪IP‬‬
‫‪ ((VoIP‬ﻋﺒﺮ ﺍﻟﻜﺒﻞ ﺣﺴﺎﺳﺎ ﺑﺸﻜﻞ ﺧﺎﺹ ﻷﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪ .‬ﺇﺫﺍ ﻛﺎﻧﺖ ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻷﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ‬
‫ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻛﺒﻴﺮﺓ ﺑﻤﺎ ﻳﻜﻔﻲ‪ ،‬ﻓﻬﺬﺍ ﻳﻌﻨﻲ ﻭﺟﻮﺩ ﻣﺸﻜﻼﺕ ﻓﻲ ﺟﻮﺩﺓ ﺍﻟﺼﻮﺕ‪ ،‬ﻓﻲ ﺣﻴﻦ ﻗﺪ ﺗﺘﺄﺛﺮ ﺑﻴﺎﻧﺎﺕ ‪ IP‬ﺑﺸﻜﻞ ﺃﻗﻞ‬
‫ﻓﻘﻂ‪.‬‬

‫ﺃﺧﻴﺮﺍ‪ ،‬ﺇﺫﺍ ﻛﺎﻧﺖ ﻗﺮﺍﺀﺓ ‪ SNR‬ﻟﺮﻗﺎﻗﺔ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﻣﻀﻠﻠﺔ ﻋﻨﺪﻣﺎ ﻳﺘﻢ ﺇﺩﺧﺎﻝ ﺇﻋﺎﻗﺎﺕ ﺳﺮﻳﻌﺔ ﻣﺆﻗﺘﺔ ﻓﻲ ﺍﻟﺘﺮﺩﺩ‬
‫ﺍﻟﻼﺳﻠﻜﻲ )ﻛﻤﺎ ﺫﻛﺮ ﺳﺎﺑﻘﺎ( ﻭﻟﻜﻦ ﻻ ﺗﺰﺍﻝ ﻫﻨﺎﻙ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪ ،‬ﻓﺈﻥ ﺃﺳﺘﻜﺸﺎﻑ ﺍﻟﻤﺸﻜﻠﺔ ﻭﺇﺻﻼﺣﻬﺎ ﻗﺪ‬
‫ﻳﺼﺒﺢ ﺃﻛﺜﺮ ﺗﻌﻘﻴﺪﺍ‪.‬‬

‫ﺍﻟﺸﻜﻞ ‪ 3‬ﻳﺴﻠﻂ ﺍﻟﻀﻮﺀ ﻋﻠﻰ ﻣﺜﺎﻝ ﻋﻠﻰ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﺍﻟﺘﻲ ﺗﻌﺎﻧﻲ ﻣﻦ ﺍﻧﺨﻔﺎﺽ ‪ SNR‬ﻓﻲ ﻧﻔﺲ ﺍﻟﻮﻗﺖ ﺍﻟﺬﻱ ﺗﻌﺎﻧﻲ‬
‫ﻓﻴﻪ ﻣﻦ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻭﻳﻤﻜﻦ ﺗﺼﺤﻴﺤﻬﺎ‪ ،‬ﻣﻊ ﺍﻟﺘﺸﺪﻳﺪ ﻋﻠﻰ ﺍﻟﻌﻼﻗﺔ ﺍﻟﻮﺛﻴﻘﺔ ﺑﻴﻦ ﻫﺬﻳﻦ ﺍﻟﻤﻌﻠﻤﺎﺕ ﻋﻨﺪ‬
‫ﻗﻴﺎﺱ ﺃﺩﺍﺀ ﺍﻟﺨﺎﺩﻡ‪.‬‬

‫ﺷﻜﻞ ‪ - 3‬ﺃﺧﻄﺎﺀ ‪ SNR‬ﻭ ‪ FEC‬ﻋﺒﺮ ﺍﻟﻮﻗﺖ‬

 ‫ﻳﻌﺮﺽ ﺍﻟﺮﺳﻢ ﺍﻟﺒﻴﺎﻧﻲ ﺍﻷﻭﻝ ﻧﺴﺒﺔ ﺃﺧﻄﺎﺀ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻭﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪ ،‬ﺑﻴﻨﻤﺎ ﻳﺸﻴﺮ ﺍﻟﺮﺳﻢ ﺍﻟﺒﻴﺎﻧﻲ‬
‫ﺍﻟﺴﻔﻠﻲ ﺇﻟﻰ ﻗﺮﺍﺀﺍﺕ ‪ SNR‬ﺿﻌﻴﻔﺔ ﻓﻲ ﻧﻔﺲ ﺍﻟﻤﺜﻴﻞ ﻓﻲ ﺍﻟﻮﻗﺖ‪ .‬ﻣﻦ ﺍﻟﻤﺤﺘﻤﻞ ﺃﻥ ﻳﺆﺩﻱ ﺍﻟﻔﺤﺺ ﺍﻟﺴﺮﻳﻊ ﻟﻠﻨﺎﻗﻞ ﺍﻷﻣﺎﻣﻲ‬
‫ﺍﻟﻤﻐﻴﺮ ﺭﻗﻤﻴﺎ ﻋﻠﻰ ﻣﺤﻠﻞ ﺍﻟﻄﻴﻒ )ﻣﺜﻞ ‪ (Agilent HP8591C‬ﺇﻟﻰ ﻇﻬﻮﺭ ﺿﻮﺿﺎﺀ ﺩﺍﺧﻞ ﺍﻟﻘﻨﺎﺓ ﺑﻤﺴﺘﻮﻳﺎﺕ ﻋﺎﻟﻴﺔ ﺟﺪﺍ‪ .‬ﻳﻤﻜﻦ‬
‫ﺗﺄﻛﻴﺪ ﻣﺸﺎﻛﻞ ﺗﺮﺩﺩ ﺍﻟﺮﺍﺩﻳﻮ ﺍﻟﻤﻨﻄﻠﻘﺔ ﺫﺍﺕ ﺍﻟﻄﺒﻴﻌﺔ ﺍﻟﻤﻨﺪﻓﻌﺔ ﺑﺎﺳﺘﺨﺪﺍﻡ ﺃﺟﻬﺰﺓ ﺇﺧﺘﺒﺎﺭ ﻣﻦ ﻃﺮﻑ ﺛﺎﻟﺚ )ﻣﺜﻞ ‪Hukk‬‬
‫‪—CM1000‬ﺍﺭﺟﻊ ﺇﻟﻰ ﻣﻮﻗﻊ ‪ SunRise Telecom‬ﻋﻠﻰ ﺍﻟﻮﻳﺐ—ﺃﻭ ‪ (Acterna DSAM‬ﺍﻟﺘﻲ ﻳﻤﻜﻨﻬﺎ ﻗﻴﺎﺱ ﻣﻌﺪﻝ‬
‫ﺃﺧﻄﺎﺀ ﻛﺘﻠﺔ ﺍﻟﻤﻨﺒﻊ )ﻣﺜﻞ ‪ .(BER‬ﻭﻫﺬﺍ ﻣﻦ ﺷﺄﻧﻪ ﺃﻥ ﻳﺆﻛﺪ ﻋﻠﻰ ﻭﺟﻮﺩ ﻣﺸﻜﻠﺔ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ‪ ،‬ﺣﺘﻰ ﻋﻨﺪﻣﺎ ﺗﺒﺪﻭ ﺍﻟﻘﺮﺍﺀﺓ‬
‫ﻋﻠﻰ ﺷﺒﻜﺔ ﺍﻹﻧﺘﺮﻧﺖ ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﺟﻴﺪﺓ‪.‬‬

‫ﺍﻟﺨﻼﺻﺔ ﻫﻨﺎ ﻫﻲ ﺃﻧﻪ ﺇﺫﺍ ﻛﺎﻧﺖ ﻗﺮﺍﺀﺓ ‪ SNR‬ﻓﻲ ﺍﻟﻮﻻﻳﺎﺕ ﺍﻟﻤﺘﺤﺪﺓ ﺗﺒﺪﻭ ﺟﻴﺪﺓ ﻓﻼ ﺗﻔﺘﺮﺽ ﺗﻠﻘﺎﺋﻴﺎ ﺃﻥ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ ﻋﻠﻰ‬
‫ﻣﺎ ﻳﺮﺍﻡ‪ .‬ﻭﻗﺪ ﻳﻠﺰﻡ ﺇﺟﺮﺍﺀ ﺑﺤﺚ ﻗﻠﻴﻞ ﻣﻊ ﻣﻌﺪﺍﺕ ﺇﺧﺘﺒﺎﺭ ﻣﻼﺋﻤﺔ ﻟﺘﺤﺪﻳﺪ ﻣﺎ ﻳﺠﺮﻱ ﺑﺎﻟﻀﺒﻂ ﻓﻲ ﻣﺠﺎﻝ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ‪.‬‬
‫ﻭﺍﻻﺣﺘﻤﺎﻻﺕ ﺟﻴﺪﺓ ﺟﺪﺍ ﻷﻥ ﻃﻴﻒ ﺍﻟﺘﺮﺩﺩﺍﺕ ﺍﻟﻼﺳﻠﻜﻴﺔ ﻟﻴﺲ ﻧﻈﻴﻔﺎ ﻛﻤﺎ ﻛﺎﻥ ﻣﻔﺘﺮﺿﺎ ﻓﻲ ﺍﻟﺒﺪﺍﻳﺔ‪.‬‬

‫ﺍﻟﻤﻠﺤﻖ‬
‫ﻳﻮﺿﺢ ﻫﺬﺍ ﺍﻟﻘﺴﻢ ﺗﻔﺎﺻﻴﻞ ﻣﻌﻠﻤﺎﺕ ﺍﻟﺒﺚ ﺍﻟﻤﻄﻠﻮﺏ ﻣﺮﺍﻗﺒﺘﻬﺎ‪.‬‬

‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻝ ‪ FEC‬ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﻋﻨﺪ ﺍﻹﺗﺠﺎﻩ ﺍﻟﻌﻠﻮﻱ‬

‫ﺍﻟﻮﺻﻒ‬

‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻟﺘﺮﺍﺧﻴﺺ ‪ CWs‬ﺍﻟﻤﺴﺘﻠﻤﺔ ﻋﻠﻰ ﻫﺬﻩ ﺍﻟﻘﻨﺎﺓ ﻣﻊ ﺃﺧﻄﺎﺀ ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‪ .‬ﻳﺘﻀﻤﻦ ﺫﻟﻚ ﺟﻤﻴﻊ ﻭﺣﺪﺍﺕ‬
‫ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ )‪ ،(CWs‬ﺳﻮﺍﺀ ﻛﺎﻧﺖ ﺟﺰﺀﺍ ﻣﻦ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﻤﻮﺟﻬﺔ ﻟﻬﺬﺍ ﺍﻟﺠﻬﺎﺯ ﺃﻡ ﻻ‪.‬‬

‫ﺻﻴﻐﺔ‬

‫‪Correctable = [(EC1 - EC0)/ [(EU1 - EU0) + (EC1 - EC0) + (C1 - C0)] * 100٪‬‬

‫‪C = docsIfSigQUnerroreds‬‬ ‫●‬

 EC
= docsIfSigQCorrecteds ●

Eu
= docsIfSigQUncorrectables ●

‫ﻗﺎﻋﺪﺓ ﺻﺎﻓﻴﺔ‬

.‫ ﻣﻦ ﺍﻟﺤﺰﻡ ﺍﻟﻤﺴﺘﻠﻤﺔ ﻳﺘﻢ ﺗﻤﻴﻴﺰﻫﺎ ﺑﺎﻟﻠﻮﻥ ﺍﻷﺻﻔﺮ‬٪2.5< ‫ﺍﻟﻘﻴﻢ‬

.‫ ﻣﻦ ﺍﻟﺤﺰﻡ ﺍﻟﻤﺴﺘﻠﻤﺔ ﻫﻲ ﺑﺎﻷﺣﻤﺮ ﺍﻟﻐﺎﻣﻖ‬٪5=< ‫ﺍﻟﻘﻴﻢ‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺍﻟﺼﺎﻓﻲ‬

‫ ﻧﺴﺒﺔ ﺇﻟﻰ ﺇﺟﻤﺎﻟﻲ ﻋﺪﺩ‬،‫ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‬FEC ‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻟﻮﺣﺪﺍﺕ ﺍﻟﺬﺍﻛﺮﺓ ﺍﻟﻤﺆﻗﺘﺔ ﻟﻺﺩﺧﺎﻝ ﺍﻟﺘﻲ ﺗﺤﺘﻮﻱ ﻋﻠﻰ ﺃﺧﻄﺎﺀ‬
٪5 ‫ ﻭﻣﻦ ﺍﻟﻤﻘﺘﺮﺡ ﺃﻥ ﺗﻜﻮﻥ ﻫﺬﻩ ﺍﻟﻨﺴﺒﺔ ﺃﻗﻞ ﻣﻦ‬.‫( ﺍﻟﺘﻲ ﺗﻢ ﺗﻠﻘﻴﻬﺎ ﻋﻠﻰ ﻫﺬﻩ ﺍﻟﻮﺍﺟﻬﺔ‬CWs) ‫ﻭﺣﺪﺍﺕ ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ‬
.‫ﻣﻦ ﺟﻤﻴﻊ ﻭﺣﺪﺍﺕ ﺍﻟﺘﻌﺒﺌﺔ ﻟﻺﺩﺧﺎﻝ‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺗﻔﺼﻴﻠﻴﺔ‬

DOCS-IF-MIB
docsIfSigQUnerroreds .1.3.6.1.2.1.10.127.1.1.4.1.2
.Codewords received on this channel without error
This includes all codewords, whether or not they
.were part of frames destined for this device

docsIfSigQCorrecteds .1.3.6.1.2.1.10.127.1.1.4.1.3
Codewords received on this channel with correctable
errors. This includes all codewords, whether or not
.they were part of frames destined for this device

docsIfSigQUncorrectables .1.3.6.1.2.1.10.127.1.1.4.1.4
Codewords received on this channel with uncorrectable
errors. This includes all codewords, whether or not
.they were part of frames destined for this device

‫ ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺃﺛﻨﺎﺀ ﺍﻟﺘﺸﻐﻴﻞ‬FEC ‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻝ‬

‫ﺍﻟﻮﺻﻒ‬

‫ ﻳﺘﻀﻤﻦ ﺫﻟﻚ ﺟﻤﻴﻊ ﻭﺣﺪﺍﺕ‬.‫ ﺍﻟﻤﺴﺘﻠﻤﺔ ﻋﻠﻰ ﻫﺬﻩ ﺍﻟﻘﻨﺎﺓ ﻣﻊ ﺃﺧﻄﺎﺀ ﻏﻴﺮ ﻗﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ‬CWs ‫ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻟﺘﺮﺍﺧﻴﺺ‬
.‫ ﺳﻮﺍﺀ ﻛﺎﻧﺖ ﺟﺰﺀﺍ ﻣﻦ ﺍﻹﻃﺎﺭﺍﺕ ﺍﻟﻤﻮﺟﻬﺔ ﻟﻬﺬﺍ ﺍﻟﺠﻬﺎﺯ ﺃﻡ ﻻ‬،(CWs) ‫ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ‬

‫ﺻﻴﻐﺔ‬

EU1 - EU0)/ [(EU1 - EU0) + (EC1 - EC0) + (C1 - C0)] * 100)] = ‫ﻏﻴﺮ ﻗﺎﺑﻞ ﻟﻠﺘﺼﺤﻴﺢ‬٪

C = docsIfSigQUnerroreds ●

EC
= docsIfSigQCorrecteds ●

Eu
= docsIfSigQUncorrectables ●

‫ﻗﺎﻋﺪﺓ ﺻﺎﻓﻴﺔ‬
 ‫ﺍﻟﻘﻴﻢ <‪ ٪0.5‬ﻣﻦ ‪ CWs‬ﺍﻟﻤﺴﺘﻠﻤﺔ ﻳﺘﻢ ﺇﺑﺮﺍﺯﻫﺎ ﺑﺎﻷﺻﻔﺮ‪.‬‬

‫ﺍﻟﻘﻴﻢ <=‪ ٪1‬ﻣﻦ ‪ CWs‬ﺍﻟﻤﺴﺘﻠﻤﺔ ﺣﻤﺮﺍﺀ ﻏﺎﻣﻘﺔ‪.‬‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺍﻟﺼﺎﻓﻲ‬

‫ﺗﻌﺮﺽ ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻟﻌﻤﻠﻴﺎﺕ ﺇﺳﻘﺎﻁ ﻭﺣﺪﺍﺕ ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ )‪ (CWs‬ﻟﻺﺩﺧﺎﻝ ﺍﻟﻨﺴﺒﺔ ﺍﻟﻤﺌﻮﻳﺔ ﻟﻮﺣﺪﺍﺕ ﺍﻟﺘﺤﻜﻢ ﻓﻲ‬
‫ﺍﻟﻮﺻﻮﻝ )‪ (CWs‬ﺍﻟﺘﻲ ﺗﻢ ﺇﺳﻘﺎﻃﻬﺎ ﻋﻠﻰ ﺍﻹﺩﺧﺎﻝ‪ ،‬ﻭﺫﻟﻚ ﺑﺎﻟﻨﺴﺒﺔ ﻹﺟﻤﺎﻟﻲ ﻋﺪﺩ ﻭﺣﺪﺍﺕ ﺍﻟﺘﺤﻜﻢ ﻓﻲ ﺍﻟﻮﺻﻮﻝ )‪ (CWs‬ﺍﻟﺘﻲ‬
‫ﺗﻢ ﺍﺳﺘﻘﺒﺎﻟﻬﺎ ﻋﻠﻰ ﻫﺬﻩ ﺍﻟﻮﺍﺟﻬﺔ‪ .‬ﻭﻣﻦ ﺍﻟﻤﻘﺘﺮﺡ ﺃﻥ ﺗﻜﻮﻥ ﻫﺬﻩ ﺍﻟﻨﺴﺒﺔ ﺃﻗﻞ ﻣﻦ ‪ ٪0.5‬ﻣﻦ ﺟﻤﻴﻊ ﻭﺣﺪﺍﺕ ﺍﻟﺘﺰﻭﻳﺪ ﺑﺎﻟﻄﺎﻗﺔ‬
‫)‪ (CW‬ﺍﻟﻤﺪﺧﻠﺔ‪.‬‬

‫ﻣﻼﺣﻈﺔ‪ :‬ﻗﺪ ﺗﺘﻄﻠﺐ ﺧﺪﻣﺎﺕ ﻣﺤﺪﺩﺓ "ﻓﻲ ﺍﻟﻮﻗﺖ ﺍﻟﻔﻌﻠﻲ"‪ ،‬ﻣﺜﻞ ﻧﻘﻞ ﺍﻟﺼﻮﺕ ﻋﺒﺮ ﺑﺮﻭﺗﻮﻛﻮﻝ ﺍﻹﻧﺘﺮﻧﺖ )‪ ،(VoIP‬ﺭﺻﺪﺍ ﺃﻛﺜﺮ‬
‫ﺻﺮﺍﻣﺔ‪ .‬ﻗﺪ ﻻ ﺗﺰﺍﻝ ﻗﻴﻤﺔ ‪ FEC‬ﻏﻴﺮ ﺍﻟﻘﺎﺑﻠﺔ ﻟﻠﺘﺼﺤﻴﺢ ﺑﻨﺴﺒﺔ ‪ ٪1‬ﺗﻤﺜﻞ ﺧﺴﺎﺭﺓ ﻛﺎﻓﻴﺔ ﻟﻠﺤﺰﻡ ﻟﻠﺘﺴﺒﺐ ﻓﻲ ﻣﺸﺎﻛﻞ ﻓﻲ ﺟﻮﺩﺓ‬
‫ﺍﻟﺼﻮﺕ‪ ،‬ﻭﺫﻟﻚ ﺣﺴﺐ ﻣﺎ ﺇﺫﺍ ﻛﺎﻥ ﺍﻟﻔﻘﺪ ﻗﺪ ﻗﺪ ﺗﻢ ﺩﻓﻌﻪ ﺃﻭ ﺑﺸﻜﻞ ﻋﺸﻮﺍﺋﻲ‪.‬‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺗﻔﺼﻴﻠﻴﺔ‬

‫‪DOCS-IF-MIB‬‬
‫‪docsIfSigQUnerroreds‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.2‬‬
‫‪.Codewords received on this channel without error‬‬
‫‪This includes all codewords, whether or not they‬‬
‫‪.were part of frames destined for this device‬‬

‫‪docsIfSigQCorrecteds‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.3‬‬
‫‪Codewords received on this channel with correctable‬‬
‫‪errors. This includes all codewords, whether or not‬‬
‫‪.they were part of frames destined for this device‬‬

‫‪docsIfSigQUncorrectables‬‬ ‫‪.1.3.6.1.2.1.10.127.1.1.4.1.4‬‬
‫‪Codewords received on this channel with uncorrectable‬‬
‫‪errors. This includes all codewords, whether or not‬‬
‫‪.they were part of frames destined for this device‬‬

‫‪ SNR‬ﻟﻠﺘﺪﻓﻖ‬

‫ﺍﻟﻮﺻﻒ‬

‫‪ SNR‬ﻛﻤﺎ ﻫﻮ ﻣﻮﺿﺢ ﻟﻬﺬﻩ ﺍﻟﻘﻨﺎﺓ‪ .‬ﻓﻲ ‪ ،CMTS‬ﻳﺼﻒ ﻣﺘﻮﺳﻂ ﺍﻹﺷﺎﺭﺓ ﺇﻟﻰ ﺍﻟﻀﻮﺿﺎﺀ ﻟﻘﻨﺎﺓ ﺍﻟﻤﻨﺒﻊ‪.‬‬

‫ﺻﻴﻐﺔ‬

‫‪SNR = docsIfSigQSignalNoise / 10‬‬

‫ﻗﺎﻋﺪﺓ ﺻﺎﻓﻴﺔ‬

‫ﻳﺘﻢ ﺗﻤﻴﻴﺰ ﺍﻟﻘﻴﻢ >‪ 27‬ﺩﻳﺴﻴﺒﻴﻞ ﺑﺎﻷﺻﻔﺮ‪.‬‬

‫ﺍﻟﻘﻴﻢ >‪ 23‬ﺩﻳﺴﻴﺒﻞ ﻫﻲ ﺃﺳﻮﺩ ﺃﺣﻤﺮ‪.‬‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺍﻟﺼﺎﻓﻲ‬
‫ ﺍﺳﺘﻨﺎﺩﺍ ﺇﻟﻰ ﻣﻠﻒ ﺗﻌﺮﻳﻒ ﺍﻟﺘﻌﺪﻳﻞ ﻋﻨﺪ‬.‫ ﺩﻳﺴﻴﺒﻞ‬25 ‫( ﻣﻦ‬SNR ‫ )ﺍﻟﻤﻌﺎﺩﻝ ﺭﻗﻤﻴﺎ ﻝ‬CNR ‫ ﺍﻟﺤﺪ ﺍﻷﺩﻧﻰ ﻝ‬DOCSIS ‫ﻳﺤﺪﺩ‬
.‫ ﺩﻳﺴﻴﺒﻞ‬25 ‫ ﺍﻟﺬﻱ ﻳﺒﻠﻎ‬SNR ‫ ﻗﺪ ﻳﻠﺰﻡ ﺯﻳﺎﺩﺓ ﺍﻟﺤﺪ ﺍﻷﺩﻧﻰ ﻝ‬،(QAM-16 ‫ ﺃﻭ‬QPSK) ‫ﺍﻟﺒﺚ ﺍﻟﺬﻱ ﺗﻢ ﺗﻜﻮﻳﻨﻪ‬

‫ﻣﻌﻠﻮﻣﺎﺕ ﺗﻔﺼﻴﻠﻴﺔ‬

ubr7246vxr# show controller cable3/0 upstream 0

Cable3/0 Upstream 0 is up
Frequency 25.392 MHz, Channel Width 3.200 MHz, QPSK Symbol Rate 2.560 Msps
Spectrum Group is overridden
BroadCom SNR_estimate for good packets - 26.8480 dB
Nominal Input Power Level 0 dBmV, Tx Timing Offset 2035

DOCS-IF-MIB
docsIfSigQSignalNoise .1.3.6.1.2.1.10.127.1.1.4.1.5
.Signal-to-Noise ratio as perceived for this channel
At the CM, describes the Signal-to-Noise of the downstream
channel. At the CMTS, describes the average Signal-to-Noise
.of the upstream channel

5x20 ‫ ﺃﻭ‬MC28U ‫ ﻟﻜﻞ ﻣﻮﺩﻡ ﻋﻠﻰ ﺑﻄﺎﻗﺔ ﺧﻂ‬FEC ‫ ﻟﻌﺪﺩ‬OIDs ‫ﻣﺜﺎﻝ ﻋﻠﻰ ﻛﻴﻔﻴﺔ ﺳﺤﺐ‬

ubr7246# show cable modem 10.200.100.115

MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (dBmV) Offset CPE Enb
0005.5e25.bdfd 10.200.100.115 C6/0/U0 online 50 0.50 2077 0 N

ubr7246# show interface cable 6/0 sid 50 counters verbose | incl Sid|Codeword

Sid : 50
Good Codewords rx : 7580
Corrected Codewords rx : 0
Uncorrectable Codewords rx : 2
:‫ ﺗﺤﺘﺎﺝ ﺃﻭﻻ ﺇﻟﻰ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ ﻣﻌﻠﻮﻣﺘﻴﻦ‬،‫ ﻟﻬﺬﺍ ﺍﻟﻤﻮﺩﻡ‬Codeword ‫ﻟﻠﻌﺜﻮﺭ ﻋﻠﻰ ﻋﺪﺍﺩﺍﺕ‬

.0/6 ‫ ﻟﻮﺍﺟﻬﺔ ﺍﻟﻜﺒﻞ‬SNMP ‫ﻓﻬﺮﺱ ﻭﺍﺟﻬﺔ‬ ●

.‫ ﻟﻠﻤﻮﺩﻡ‬docsIfCmtsServiceNewCmStatusIndex ●

:‫ ﺑﺎﺳﺘﺨﺪﺍﻡ ﻫﺬﺍ ﺍﻷﻣﺮ‬0/6 ‫ ﻟﻠﻜﺎﺑﻞ‬ifIndex ‫ﺍﺑﺤﺚ ﻋﻦ‬

snmpwalk -cpublic 172.18.73.167 ifDescr | grep Cable6/0 %

"RFC1213-MIB::ifDescr.10 = STRING: "Cable6/0

ifIndex of cable 6/0 is "10". RFC1213-MIB::ifDescr.36 = STRING: "Cable6/0-upstream0" ---!
RFC1213-MIB::ifDescr.37 = STRING: "Cable6/0-upstream1" RFC1213-MIB::ifDescr.38 = STRING:
"Cable6/0-upstream2" RFC1213-MIB::ifDescr.39 = STRING: "Cable6/0-upstream3" RFC1213-
"MIB::ifDescr.40 = STRING: "Cable6/0-downstream
(0/6 ‫ )ﺍﻟﻜﺒﻞ‬ifIndex 10 ‫ ﻋﻠﻰ ﺍﻟﻮﺍﺟﻬﺔ ﻣﻊ‬SID 50 ‫ ﻟﻠﻤﻮﺩﻡ ﻣﻊ‬docsIfCmtsServiceNewCmStatusIndex ‫ﺍﺑﺤﺚ ﻋﻦ‬
:‫ﺑﺎﺳﺘﺨﺪﺍﻡ ﻫﺬﺍ ﺍﻷﻣﺮ‬

snmpwalk -cpublic 172.18.73.167 docsIfCmtsServiceNewCmStatusIndex.10.50 %

DOCS-IF-MIB::docsIfCmtsServiceNewCmStatusIndex.10.50 = INTEGER: 983090

FEC ‫ ﻳﻤﻜﻨﻚ ﺍﻟﻌﺜﻮﺭ ﻋﻠﻰ ﻋﺪﺍﺩﺍﺕ‬،(983090) ‫ ﻟﻠﻤﻮﺩﻡ‬docsIfCmtsServiceNewCmStatusIndex ‫ﺍﻵﻥ ﺑﻌﺪ ﺃﻥ ﺃﺻﺒﺢ ﻟﺪﻳﻚ‬
:‫ﻫﺬﻩ‬

(docsIfCmtsCmStatusUnerroreds) ‫ﺗﻢ ﺇﺳﺘﻼﻡ ﻛﻠﻤﺎﺕ ﺍﻟﺘﺮﻣﻴﺰ ﺍﻟﺠﻴﺪﺓ‬ ●

snmpget -cpublic 172.18.73.167 docsIfCmtsCmStatusUnerroreds.983090 %

DOCS-IF-MIB::docsIfCmtsCmStatusUnerroreds.983090 = Counter32: 8165

.show interface cable ‫ ﺇﻟﻰ ﺣﺪ ﻣﺎ ﻓﻲ ﺍﻟﻮﻗﺖ ﻣﻨﺬ ﺇﺻﺪﺍﺭ ﺍﻷﻣﺮ‬Unerroreds ‫ ﺯﺍﺩ ﻋﺪﺍﺩ‬:‫ﻣﻼﺣﻈﺔ‬
● (docsIfCmtsCmStatusCorrecteds) ‫ﻛﻠﻤﺎﺕ ﺍﻟﺘﺮﻣﻴﺰ ﺍﻟﻤﺼﺤﺤﺔ ﺍﻟﺘﻲ ﺗﻢ ﺗﻠﻘﻴﻬﺎ‬
snmpget -cpublic 172.18.73.167 docsIfCmtsCmStatusCorrecteds.983090 %

DOCS-IF-MIB::docsIfCmtsCmStatusCorrecteds.983090 = Counter32: 0

● (docsIfCmtsCmStatusUncorrectables) ‫ ﻏﻴﺮ ﻣﺼﺤﺢ‬CodeWords ‫ﺗﻢ ﺗﻠﻘﻲ‬

snmpget -cpublic 172.18.73.167 docsIfCmtsCmStatusUncorrectables.983090 %

DOCS-IF-MIB::docsIfCmtsCmStatusUncorrectables.983090 = Counter32: 2

‫ﻣﻌﻠﻮﻣﺎﺕ ﺫﺍﺕ ﺻﻠﺔ‬

DOCSIS ‫ﻓﻬﻢ ﻣﻌﺪﻝ ﺍﻹﻧﺘﺎﺟﻴﺔ ﻓﻲ ﻋﺎﻟﻢ‬ ●

‫ﻣﻠﻔﺎﺕ ﺗﻌﺮﻳﻒ ﺍﻟﺘﻌﺪﻳﻞ ﻟﻠﺘﺪﻓﻖ ﻷﺳﻄﺮ ﺍﻟﻜﺒﻼﺕ‬ ●

DOCSIS ‫ﻣﻮﺍﺻﻔﺎﺕ ﻭﺍﺟﻬﺔ ﺍﻟﺘﺮﺩﺩ ﺍﻟﻼﺳﻠﻜﻲ‬ ●

‫ﺩﻋﻢ ﺗﻘﻨﻴﺔ ﻛﺎﺑﻞ ﺍﻟﻨﻄﺎﻕ ﺍﻟﺘﺮﺩﺩﻱ ﺍﻟﻌﺮﻳﺾ‬ ●

Cisco Systems - ‫ﺍﻟﺪﻋﻢ ﺍﻟﻔﻨﻲ‬ ●

‫ةمجرتلا هذه لوح‬
‫ةيلآلا تاينقتلا نم ةعومجم مادختساب دنتسملا اذه ‪ Cisco‬تمجرت‬
‫ملاعلا ءاحنأ عيمج يف نيمدختسملل معد ىوتحم ميدقتل ةيرشبلاو‬
‫امك ةقيقد نوكت نل ةيلآ ةمجرت لضفأ نأ ةظحالم ىجرُي ‪.‬ةصاخلا مهتغلب‬
‫‪ Cisco‬يلخت ‪.‬فرتحم مجرتم اهمدقي يتلا ةيفارتحالا ةمجرتلا عم لاحلا وه‬
‫ىلإ اًمئاد عوجرلاب يصوُتو تامجرتلا هذه ةقد نع اهتيلوئسم ‪Systems‬‬
‫‪).‬رفوتم طبارلا( يلصألا يزيلجنإلا دنتسملا‬