DOCSIS Training - Admin

1
TOSHIBA
DOCSIS Cable Modem Training

Administration and Management
Network Products Division
Toshiba America Information Systems Confidential and Proprietary

2
TOSHIBA
1 - Outline
• DOCSIS Overview
– Introduction
– Architecture
– Components
• Communication Protocols
– Protocol Stack
– MAC Forwarder
– Network Layer and Above
– Data Link Layer
– Physical Layer

3
TOSHIBA
Outline (cont’d)
• Cable Modem
– Components
– Front & Rear Views
– Features & Specifications
• CMTS (Cable Modem Termination System)
– Components
– Features & Specifications
• DOCSIS HFC Environment

4
TOSHIBA
Outline (cont’d)
• Physical Layer
– Upstream
• Modulation & Rates
• Forward Error Correction (FEC)
• Scambler (Randomizer)
• Burst Profiles & Timing
• Power & Fidelity
• Frame Structure
– Downstream (ITU-T Recommendations J.83, Annex B)
• Modulation & Rates
• Scalable Interleaving
• Power & Fidelity

5
TOSHIBA
Outline (cont’d)
• Cable Modem Initialization and Operation
– Overview & Detailed Description
• Scanning and Synchronization to Downstream
• Obtain Upstream Parameters
• Ranging and Automatic Adjustments
• DHCP (Dynamic Host Configuration Protocol) Service
• TOD (Time and Date) Service
• TFTP (Trivial File Transfer Protocol) Service
• Registration
• Ranging Maintenance
– Software Upgrade
• Review Questions I

6
TOSHIBA
Outline (cont’d)
• Cable Modem Initialization and Operation (cont’d)
– Data Transfer
• Downstream Transmission Convergence Sub-layer
• Media Access Control (MAC) Sub-layer
– Overview
– Frame Formats & Headers
– Error-Handling
– Upstream - Allocation MAP’s
– Upstream - Contention Resolution
• Service Classes
• Rate Control Mechanism
• Filtering Mechanism
• Multicast Operation

7
TOSHIBA
Outline (cont’d)
• Baseline Privacy
– Overview
– Operational Overview
– Privacy Key Management
• Cable Modem Configuration Information
– Configuration File
• Format, Creation and Parameters
• Configuration File Editor
– Headend Equipment
• CMTS, Provisioning
– Examples

8
TOSHIBA
Outline (cont’d)
• Review Questions II
• Installation
– Subscriber installation procedure
– Monitoring LED’s during installation
– Installation & Testing Wizard
• Cable Modem Trouble Shooting
– Normal Toshiba Cable Modem Operation
– Installation & Testing Wizard
– Advanced Diagnostics
• Toshiba MSO Support Web Page
• Use of SNMP
9
TOSHIBA
Outline (cont’d)
• Toshiba Serial Diagnostic Port
• DOCSIS Parameters and Constants
• DOCSIS Error Codes and Messages
• Review Questions III
• DOCSIS v1.1 and Packet Cable
• Hands-on
– Configuration
• CMTS, provisioning and cable modem
– Physical Layer
• RF signals, noise and interference
– Networking Management & Performance

10
TOSHIBA
2 - DOCSIS Overview
• Data-Over-Cable Service Interface Specification
(DOCSIS)
– Defines interface requirements for cable modems involved in high-
speed data distribution over a cable television network
– On November 17, 1997, CableLabs® and its members established a
formal path of certification for cable modem equipment suppliers
– By March of 1999 the first products were certified and cable
modems are now becoming available on the retail market

11
TOSHIBA
DOCSIS Services Goals

• Cable operators are interested in deploying high-speed packet-based
communications systems over cable systems
– Services to be deployed include Internet access service, packet telephony
service and video conferencing service
• DOCSIS allows transparent bi-directional transfer of IP traffic,
between the cable system Headend and customer locations, over an all-
coaxial or hybrid fiber/coax (HFC) CATV systems
Cable
Modem
Wide-Area
Termination
Netw ork
System Cable CM-Customer Premises
CMTS Netw ork
(CMTS) Netw ork Equipment Interface
Side Interface
Cable Modem (CMCI)
(CMTS-NSI) Customer
(CM) [MCNS4]
[MCNS3] Premises
Equipment
Transparent IP Traffic Through the System

12
TOSHIBA
DOCSIS Reference Architecture

Distribution Hub or Headend
Operations Support System

Data Over Cable System OSS
Interface (DOCS-OSSI)
[MCNS5]
CM-Customer Premises
Cable Modem Equipment Interface (CMCI)
Termination System [MCNS4]
Downstream CMTS to
HFC Interface [MCNS1]
Generic
Headend
WAN Mod TX
Switch or Network O/E
Data Fiber
Backbone Termination Node
Demod RX
Transport
Adapter Customer
Upstream CMTS to HFC
Cable Modem to HFC Premises
Interface [MCNS1]
Network Interface Equipment
[MCNS1]
CMTS Network
Side Interface
Data Over Cable
Backbone (CMTS-NSI)
Security System
Local [MCNS3] Security
Network Server & Access
(DOCSS) [MCNS2]
Facility Controller
Remote
WAN
Server
Facility

13
TOSHIBA
DOCSIS Documents
Designa tion Title

SP-BPI [MCNS8] Baseline Privacy Interface Specification
SP-CMCI [MCNS4] Cable Modem-to-Customer Premises Equipment Interface Specification
SP-CMTRI [MCNS6] Cable Modem Telephony Return Interface Specification
SP-CMTS-NSI [MCNS3] Cable Modem Termination System Network Side Interface Specification
SP-OSSI [MCNS5] Operations Support System Interface Specification
SP-OSSI-RF Operations Support System Interface Radio Frequency MIB
SP-OSSI-TR Operations Support Systems Interface Telephony Return MIB
SP-RFI [MCNS1] Radio Frequency Interface Specification
TR-OSSF Operations Support System Framework
Note: SP = Specification
TR Technical Report (provides a context for understanding and applying the specification.)

14
TOSHIBA
DOCSIS Components
Provisioning RF
Server
Router
CIF HFC
Network 100BASE-T
CMTS
Internet
CM

15
TOSHIBA
DOCSIS Components (cont’d)

• Cable Modem
– Subscriber device, connects a subscriber PC or LAN to
a data network (such as Internet) via the cable TV plant
(HFC)
• Cable Modem Termination System (CMTS)
– Head-end equipment that concentrates communication
to/from all subscribers’ cable modems
– Controls the data access to all cable modem, and also
return power level, frequency, etc.

16
TOSHIBA
DOCSIS Components (cont’d)

• DOCSIS Provisioning Server
– Provides network configuration (IP address, etc), date
and time and cable modem configuration (MD5 file).
– Provides also downloadable code image (software) for
cable modems, for software upgrade.
– Support the following network services:
• DHCP (Dynamic Host Configuration Protocol)
• TOD (Time and Date Service)
• TFTP (Trivial File Transfer Protocol)

17
TOSHIBA
3 - Communication Protocols
• The main function of the DOCSIS system is
transmitting IP packets transparently between the
Headend and the subscriber location.
– management functions also ride on IP, including
spectrum management functions and the downloading
of software
• The DOCSIS implements
– Physical and Data Link layer for packet forwaring
– Network, Transport and Application layer for
management functions
18
TOSHIBA
DOCSIS Protocol Stack

Application Layer SNMP TFTP DHCP
Security
Management
Transport Layer UDP
Network Layer IP, ICMP
ARP
LLC/DIX
Link Security
Data Link Layer
Media Access Control

(MAC)
Transmission Conv ergence

(Downstream Only )
Physical Layer
Physical Media Control
(PMD)

19
TOSHIBA
Data Forwarding
Through CM and CMTS
• Data forwarding through the CMTS may be:
– transparent bridging,
– or may employ network-layer forwarding (routing, IP
switching)
• Data forwarding through the CM is link-layer
transparent bridging

20
TOSHIBA
Data Forwarding
CMTS Stack CM Stack
IP IP
802.2/ 802.2/ Transparent
Forwarding
DIX LLC DIX LLC Bridging 802.2/
Data
Link Link DIX LLC
Link Security Security
Layer
Cable Cable 802.3/
MAC MAC DIX MAC
Dow nsteam Dow nsteam
PHY Trans Conv Trans Conv 802.3
Layer Cable Cable 10Base-T
PMD PMD
Cable Network CMCI

CMTS-NSI
Interface
Interface Transmission to/from
to/from
Customer
Network
Premises
Equipment
Equipment

21
TOSHIBA
CMTS Forwarding Rules

• If link-layer forwarding is used, then the following rules
are used (based on 802.1d):
– Link-layer frames between a given pair of end-stations will be
delivered in order.
– Link-layer frames will not be duplicated.
– Stale frames (those that cannot be delivered in a timely fashion)
will be discarded.
– Address-learning & address-aging mechanisms used are vendor-
dependent.
• If network-layer forwarding is used, then the CMTS
should conform to IETF Router Requirements [RFC-
1812].
22
TOSHIBA
CPE MAC Address Acquisition

• CM will acquire Ethernet MAC addresses of connected
CPE devices, either from the provisioning process or from
learning, until the CM acquires its maximum number of
CPE addresses (up to 16 on Toshiba CM).
• The CM will allow configuration of CPE addresses during
the provisioning process.
– Addresses provided during the CM provisioning will take
preference over learned addresses.
• CPE addresses will not be aged out.
• On a CM reset (e.g., a power cycle), all learned addresses
will be discarded.

23
TOSHIBA
CM Forwarding Rules
• CM forwarding in both directions conforms to the
general 802.1d guidelines and the following
specific rules:
– Cable to Ethernet
• Frames addressed to unknown destinations not be forwarded
from the cable port to the Ethernet port.
• Broadcast frames will be forwarded to the Ethernet port.
• Multicast frames will be forwarded to the Ethernet ports in
accordance with filtering configuration settings.

24
TOSHIBA
CM Forwarding Rules (cont’d)

– Ethernet to Cable
• Frames addressed to unknown destinations will be forwarded
from the Ethernet port to the cable port.
• Broadcast frames will be forwarded to the cable port.
• Multicast frames will be forwarded to the cable port in
accordance with filtering configuration settings.
• Frames from source addresses other than those provisioned or
learned as supported CPE devices will not be forwarded.

25
TOSHIBA
4 - Toshiba DOCSIS Cable Modem

26
TOSHIBA
Components - DOCSIS v1.0
HFC
LBT 4030 MDP 1.0
Tuner StrongARM
w/DES
• A/D Converter
• Sync
• 64/256 QAM
Demodulator • CRC
• FEC • Packet Flash
• QPSK/16QAM
Burst Modulator
•D/A Converter
SRAM SRAM
CPE
Ethernet
Controller

27
TOSHIBA
Components (cont’d)
• RF Tuner
– Tune in the downstream channel (6 MHz) and amplify the signal
– Designed by Toshiba specially for DOCSIS cable modem resulting
in high RF performance
• Libit PHY chip (LBT 4030)
– Integrated Downstream/Upstream (LBT4030)
– Based on advanced Signal Processing Technology
– Provide several statistics such as SNR, Error Correction and Power
Level

28
TOSHIBA
• MAC chip
– Implements medium access protocol and handles MPEG frames
– Supports DMA for high data transfer performance
– Built-in 3-DES (encryption/decryption engine) and IP and
Ethernet/LLC filtering
• StrongARM CPU (200 MHz)
– High performance packet processing (up to 9.9 Mbps downstream
throughput using 10BaseT)

29
TOSHIBA
• Flash Memory
– Two independent banks of flash memory
– Downloads new code image in one bank, while operates normally
on the other bank
• Other Components
– SRAM Memory
– Ethernet Controller

30
TOSHIBA
Front View POWER
Cable CABLE
Modem
PC
DATA
TEST
Diagnostic LEDs
• Power
• Cable
• PC
• Data
• Test

31
TOSHIBA
Rear View
Connectors
• 10 BaseT (RJ 45)
• Power (DC 12V)
• RF (F connector)
Switches
• Reset

32
TOSHIBA
Features of Cable Modem

• CableLabs® Certified™ DOCSIS v1.0
– receiver: 64/256 QAM (max. 43Mbps), 88 MHz to 860 MHz and -
15dBmV to +15dBmV
– transmitter: QPSK/16QAM (max. 10Mbps), 5MHz to 42 MHz and
+8dBmV to +58dBmV
– frequency agile
• Support packet filtering
– up to thirty two (32) IP filter
– up to thirty two (32) Ethernet and LLC filter
• Support up to 16 CPE’s connected to Ethernet Port

33
TOSHIBA
Features of Cable Modem (cont’d)

• Support DOCSIS Baseline Privacy
• Support multicast, including encrypted multicast
• Software downloadable for remote firmware mgmt
• Five (5) diagnostic LEDs
• SNMP Manageable
• Small Size and Low Power Consumption
– 1.96” (W) x 8.07” (D) x 5.96” (H); 8W
• Retail Packaging
– including end-user documentation and self-installation & test
wizard software

34
TOSHIBA
Cable Modem Specs.

Receiver Specification
 Physical speed: 30Mbps (64QAM) / 43Mbps (256QAM)

 Symbol rate: 5.056941 Msym/sec (64QAM)
5.360537 Msym/sec (256QAM)
 Modulation technique: 64QAM and 256QAM
 Bandwidth: 6 MHz
 Roll-off ratio: root 18% cosine (64QAM)
root 12% cosine (256QAM)
 Frequency range: 88 to 860 MHz (edge-to-edge) in 62.5 KHz steps
 Frequency channel: HRC, IRC or STD
 Frequency selection: automatic scanning
 Input signal level: -15 to +15 dBmV
(Automatically Gain Controlled by CM)
 Input impedance 75 ohms
 Carrier lock range: +/-30 KHz
 Return loss: > 6 dB

35
TOSHIBA
Cable Modem Specs.

Transmitter Specifications
 Physical speed: 320, 640, 1280, 2560 ,5120 Kbps (QPSK)

640, 1280, 2560, 5120, 10240 Kbps (16QAM)
 Symbol rate: 160, 320, 640, 1280, 2560 Ksym/sec
 Modulation technique: QPSK and 16QAM
 Bandwidth: 200, 400, 800, 1600, 3200 KHz
 Roll-off ratio: root 25% cosine
 Frequency range: 5 to 42 MHz (edge-to-edge) in 1Hz steps
 Frequency channel: voluntary frequency (1Hz step)
 Frequency selection: controlled by CIF
 Output signal level: (*1)
Range: +8 to 55 dBmV (16QAM)
+8 to 58 dBmV (QPSK)
Step: 1dB
Control: controlled by CMTS

36
TOSHIBA
Cable Modem Specs.

 Frequency stability: ±50 parts per million
 Carrier ON/OFF ratio: > 72dB
 Spurious level:
(measured in 160kHz) Inband: -40dBc
Adjacent Band: -45dBc
3 or Fewer Carrier-Related Frequency Bands
(such as second harmonic, if<42MHz): -47dBc
Bands within 5 to 42 MHz (excluding assigned
channel, adjacent channels, and carrier-related
channels): -53dBc
(measured in 4MHz) 42 to 54MHz: -40dBc
54 to 88MHz: -30dBmV
88-860MHz: -45dBmV
 Protection circuit: Open/Short, prevents irregular continuous transmission
*1: Output signal level of CM is automatically controlled by power ranging function.

37
TOSHIBA
Cable Modem Specs.

Interfaces
 PC interface: IEEE802.3/Ethernet 10BASE-T

 Cable interface: F type female 75 
Other Specifications
 Front indicator (LED): Power, Cable, PC Link, Data and Test

 Power supply: AC-DC adapter.
AC Input; 120V +/-10 percent 60Hz
DC Output, 12V @ 1A
 Power consumption: 8W
 Dimensions(without AC-DC Adapter):
height: 5.96"
width: 1.96"
depth: 8.07"
 Weight: 2.1 lb.
 Safety: UL1950, UL1310(AC-DC adapter)
 Emissions: FCC part15 classB
 Environment: Operating temperature: 32°F(0°C) to 104°F(40°C)
Operating humidity: 10% to 90% Non condensing
Storage temperature: -4°F (-20°C) to 140°F(60°C)

38
TOSHIBA
5 - Cable Modem Termination System

(CMTS)
• CMTS Features
– DOCSIS compliant RF, MAC and management functions
– Quality of Service (QoS)
• Rate control
• Bandwidth guarantee
– IP and Ether/LLC filtering
– Multicast
– DOCSIS Privacy
– Spectrum management
– Network management (SNMP-based)

39
TOSHIBA
CMTS Components
Cable Interface
Switch/ Down- Up
Up
IP filter/ stream Conver
Conver--
Control Process. ter Down
Process. ter
Up- Up
Router stream
Up
Process.
(Gigabit Ethernet, .
POS,
ATM or
100BASE-T)
Cable Interface

40
TOSHIBA
Pa ra meter Va lue
Center Frequency (fc) 91 to 857 MHz 30 kHz

Level Adjustable over the range 50 to 61 dBmV
Specs. Modulation Type

Symbol Rate (nominal)
64QAM and 256QAM
64QAM 5.056941 Msym/sec

256QAM 5.360537 Msym/sec
Nominal Channel Spacing 6 MHz
Frequency response
64QAM ~18% Square Root Raised Cosine shaping
256QAM ~12% Square Root Raised Cosine shaping
Total Discrete Spurious Inband (fc 3 MHz) < -57dBc
Inband Spurious and Noise (fc 3 MHz) < -48dBc; where channel spurious and noise includes all discrete
spurious, noise, carrier leakage, clock lines, synthesizer products, and
other undesired transmitter products. Noise within +/- 50kHz of the
carrier is excluded.
Adjacent channel (fc 3.0 MHz) to (fc 3.75 MHz) < -58 dBc in 750 kHz
Adjacent channel (fc 3.75 MHz) to (fc 9 MHz) < -62 dBc, in 5.25 MHz, excluding up to 3 spurs, each of which must
be <-60 dBc when measured in a 10 kHz band
Next adjacent channel (fc 9 MHz) to (fc 15 MHz) Less than the greater of -65 dBc or -12dBmV in 6MHz, excluding up to
three discrete spurs. The total power in the spurs must be < -60dBc
when each is measured with 10 kHz bandwidth.
Other channels (47 MHz to 1,000 MHz) < -12dBmV in each 6 MHz channel, excluding up to three discrete
spurs. The total power in the spurs must be < -60dBc when each is
measured with 10kHz bandwidth.
Phase Noise 1 kHz - 10 kHz: -33dBc double sided noise power
10 kHz - 50 kHz: -51dBc double sided noise power
50 kHz - 3 MHz: -51dBc double sided noise power
Output Impedance 75 ohms
Output Return Loss > 14 dB within an output channel up to 750 MHz; > 13 dB in an output
channel above 750 MHz
Connector F connector per [IPS-SP-406]

41
TOSHIBA
HFC Environment - Upstream

Carrier to noise ratio: Not less than 25dB
Carrier to ingress power ratio: Not less than 25dB
Carrier to interference ratio: Not less than 25dB
Carrier hum modulation: Not greater than -23dBc
Burst noise: Not longer than 10usec at a
1kHz average rate
Amplitude ripple: 0.5dB/MHz
Group delay ripple: 200nsec/MHz
Micro-reflections—single echo: -10dBc@<=0.5usec
-20dBc@<=1.0usec
-30dBc@>1.0usec
Seasonal & diumal signal level variation: Not greater than 8dB min to max

42
TOSHIBA
HFC Environment - Downstream

Frequency range: 88 - 860MHz
Occupied bandwidth: 6MHz
Carrier to noise ratio: Not less than 35dB
Carrier to interference ratio for total power: Not less than 35dB
Composite second order distortion: Not greater than -50dBc
Composite triple beat distortion: Not greater than -50dBc
Cross-modulation level: Not greater than -40dBc
Amplitude ripple: 0.5dB/6MHz
Group delay ripple: 75nsec/6MHz
Micro-reflections bound for dominant echo: -10dBc@<=0.5usec
-15dBc@<=1.0usec
-20dBc@<=1.5usec
-30dBc@>1.5usec

43
TOSHIBA
HFC Environment - Downstream

Carrier hum modulation: Not greater than -26dBc
Burst noise: Not longer than 25usec at a
10Hz average rate
Seasonal and diumal signal level variation: 8dB
Signal level slope, 50-750MHz: 16dB
Maximum analog video carrier level at the CM
input, inclusive of above signal level variation: 17dBmV
Lowest analog video carrier level at the CM
input, inclusive of above signal level variation: -5dBmV

44
TOSHIBA
6 - Physical Layer
• Upstream
– It uses a FDMA/TDMA burst modulation format, which provides:
• five symbol rates and two modulation formats (QPSK and 16QAM).
• modulation format includes pulse shaping for spectral efficiency, it is
carrier-frequency agile, and it has selectable output power level.
– It also includes a variable-length modulated burst with precise
timing beginning at boundaries spaced at integer multiples of 6.25
msec apart (which is 16 symbols at the highest data rate).
• Each burst supports a flexible modulation, symbol rate, preamble,
randomization of the payload, and programmable Forward error
Correction (FEC) encoding.
– Transmission parameters associated with burst transmission
outputs are configurable by the CMTS via MAC messaging.

45
TOSHIBA
Upstream Modulation & Symbol Rates

• Modulation technique:
– QPSK and 16QAM
• Symbol rate:
– 160, 320, 640, 1280, 2560 Ksym/sec
• Physical speed:
– 320, 640, 1280, 2560 ,5120 Kbps (QPSK)
– 640, 1280, 2560, 5120, 10240 Kbps (16QAM)
• Channel Width (-30 dB bandwidth):
– 200, 400, 800, 1600, 3200 KHz
• Frequency range:
– 5MHz - 42 MHz edge to edge

46
TOSHIBA
Upstream Symbol Mapping
QPSK Symbol Mapping
Q1
01 11
I1
00 10

47
TOSHIBA
16QAM Gray-Coded Symbol Mapping
0111 0101 1101 1111
0110 0100 1100 1110

I
0010 0000 1000 1010
0011 0001 1001 1011

48
TOSHIBA
16QAM Differential-Coded Symbol Mapping
0111 0110 1101 1111
0101 0100 1100 1110

I
0010 0000 1000 1001
0011 0001 1010 1011

49
TOSHIBA
Forward Error Correction (FEC)

• The upstream modulator provides the following selections:
– Reed-Solomon codes over GF(256) with T = 1 to 10 or no FEC
coding.
• The following Reed-Solomon generator polynomial is
supported:
– g(x) = (x + a0) (x + a1)...(x + a2T-1) where the primitive element
alpha is 0x02 hex.
• The upstream modulator provides codewords:
– from a minimum size of 18 bytes (16 information bytes [k] plus
two parity bytes for T = 1 error correction)
– to a maximum size of 255 bytes (k-bytes plus parity-bytes).

50
TOSHIBA
Scambler (Randomizer)
• The upstream modulator implements a scrambler where the
15-bit seed value is arbitrarily programmable.
– At the beginning of each burst, the register is cleared and the seed
value is loaded.
– The seed value is used to calculate the scrambler bit, which is
combined in an XOR with the first bit of data of each burst (which
is the MSB of the first symbol following the last symbol of the
preamble).

51
TOSHIBA
Burst Profiles
• CM generates each burst at the appropriate time as
conveyed in the mini-slot grants provided by the CMTS
Maps
• The CM supports all burst profiles commanded by the
CMTS:
– via the Burst Descriptors in the Upstream Channel Descriptor
(UCD),
– and subsequently assigned for transmission in a Bandwidth
Allocation Map.

52
TOSHIBA
Burst Profiles Attributes

Burst Profile Attributes Configuration Settings
Modulation QPSK, 16 QAM

Diff Enc On/Off
Preamble Length 0-1024 bits
Preamble Value offset 0 to 1022
FEC Error Correction (T bytes) 0 to 10 (0 implies FEC = off)
FEC Codeword Information Bytes (k) Fixed: 16 to 253 (assuming FEC on)
Shortened: 16 to 253 (assuming FEC on)
Scrambler Seed 15 bits
Maximum Burst Length (bytes) Up to 1522
Guard Time 5 to 255 symbols
Last Codeword Length Fixed, shortened
Scrambler On/Off On/Off

53
TOSHIBA
User Unique Burst Parameters

User Unique Parameter Configuration Settings
Power Level +8 to +55 dBmV (16QAM)

+8 to +58 dBmV (QPSK)
1-dB steps
Offset Frequency Range = 32 kHz; increment = 1 Hz;
implements within 10 Hz
Ranging Offset 0 to (216 - 1), increments of 6.25 msec/64
Burst Length (bytes) if variable on this 1 to 1522bytes
channel (changes burst-to-burst)
Transmit Equalizer Coefficients Up to 64 coefficients; 4 bytes per coefficient:
(advanced modems only) 2 real and 2 complex

54
TOSHIBA
Burst Timing
A) Nominal Burst Profile (no timing errors): 8
symbol guard band is illustrated; 10 symbol ramp
up and ramp down is illustrated.
Data First Last FEC
Symbol Parity Symbol
Ramp Up Ramp Down
Preamble Preamble
First Symbol Last Symbol
10
Symbols
B) Timing is referenced to the
symbol center of the first
symbol of each burst 8
Symbols
Center of Preamble First

Minislot
Symbol = Minislot Boundary
Boundary
Burst N Burst N+1
Preamble
First Symbol
Note: Ramp dow n of one burst can overlap

ramp up of the follow ing burst even w ith
one transmitter assigned both bursts.

55
TOSHIBA
Output Power Agility and Range

• The output transmit power in the design
bandwidth is variable over the range of:
– +8 dBmV to +55 dBmV (16 QAM) or +58 dBmV
(QPSK), in 1-dB steps.
– The absolute accuracy of the transmitted power is ±
2dB, and the step size accuracy ± 0.4dB.

56
TOSHIBA
Frame Structure
Example 1. Packet length = number of information bytes in codew ord = k
One Codew ord
Guard Empty up to Next

Preamble Packet Data FEC Parity
Time Mini-Slot Boundary
Example 2. Packet length = k = remaining information bytes in 2nd codew ord = k + k'  k + k"  2k
Guard mini-slot
Preamble Tw o Codew ords
Time boundaary
First k Bytes Last k' Bytes k"-k' Bytes of

FEC Parity FEC Parity
of Packet of Packet zero-fill

57
TOSHIBA
Physical Layer
• Downstream
– The downstream PMD sublayer conforms to ITU-T
Recommendations J.83, Annex B for Low-Delay Video
Applications [ITU J.83-B]
– Modulation technique:
• 64QAM and 256QAM
– Physical speed:
• 30Mbps (64QAM) / 43Mbps (256QAM)
– Symbol rate:
• 5.056941 Msym/sec (64QAM) / 5.360537 Msym/sec (256QAM)
– Channel Width (-30dB bandwidth):
• 6 MHz

58
TOSHIBA
ITU Recommendation J.83, Annex B

• ITU Recommendation defines:
– Framing structure (MPEG-2)
– Channel coding (RS FEC, Interleaving, Randomization and Trellis)
– Channel modulation (64/256 QAM)
• The transport is based on a MPEG-2 transport framing.
– 188 bytes packets (1-byte sync., 3-byte header and 184 bytes payload)
Transmitter Receiver
MPEG FEC QAM QAM FEC MPEG

Framing Encoder Mod.
Channel Demod. Decoder Framing

59
TOSHIBA
Downstream Scalable Interleaving

• Downstream supports a variable-depth interleaver
providing low latency
I J Burst Protection Latency

(Number of Taps) (Increment) 64QAM/ 256QAM 64QAM/ 256QAM
8 16 5.9 µsec/4.1 µsec 0.22 msec/0.15 msec

16 8 12 µsec/8.2 µsec 0.48 msec/0.33 msec
32 4 24 µsec/16 µsec 0.98 msec/0.68 msec

60
TOSHIBA
Downstream Frequency Plan

• The downstream frequency plan should comply
with:
– Harmonic Related Carrier (HRC), Incremental Related
Carrier (IRC) or Standard (STD) North American
frequency plans.
• Frequency range:
– 88 to 860 MHz (edge-to-edge) in 62.5 KHz steps

61
TOSHIBA
Downstream Power Requirements

• Input signal level at CM:
– -15 to +15 dBmV
• Output signal level at CMTS:
– Adjustable over the range +50 to +61 dBmV

62
TOSHIBA
7 - Cable Modem Initialization

• Cable modem initialization is composed of two phases:
– Initial Ranging
– Registration
• Initial Ranging
– Cable modem searches for a forward DOCSIS QAM signal
• Starting at 860 MHz and goes down until 88 MHz (entire cycle takes
about 4 minutes)
– Once finds, starts to adjust its return power level and timing until
CMTS acknowledges the CM
• Adjusts power from min. to max. level (+ 8 dBmV to +58 dBmV)
– CMTS grants a temporary ID to the modem, this ID is used for the
Registration phase

63
TOSHIBA
Initial Ranging
Provisioning
Server
CMTS CM
Power-on
Search DOCSIS QAM
Found DOCSIS QAM

Start Ranging (min. power)
Increase Power until

CMTS acknowledge
Obtain temporary ID

64
TOSHIBA
Cable Modem Initialization (cont’d)

• Registration
– Cable Modem requests network configuration to DHCP server (IP
address, network mask, Router address, DNS server address, TFTP
server address, etc)
– Cable Modem requests network time and date to TOD server
– Cable Modem requests configuration file (MD5 file) to TFTP
server
• If indicated into configuration file, Cable Modem downloads a new
code image from TFTP server
– Cable Modem negotiates with CMTS final registration (including
QOS, encryption, etc), if successful receives a Service
Identification (SID)

65
TOSHIBA
Registration
Provisioning
Server
CMTS CM
Request network
configuration from
DHCP server
Request time and

date to TOD server
Request configuration
File from TFTP server
Negotiate final
registration and obtain
a Service ID (SID)

66
TOSHIBA
Cable Modem Normal Operation

• During normal operation the cable modem
performs Ranging Maintenance
– Cable modem periodically receives information from
the CMTS regarding to power level and timing
• It adjusts its power level and timing if necessary
– Cable modem has to reset itself in the event of no
ranging maintenance is received
• An internal timer on the cable modem is used to time-out
ranging maintenance

67
TOSHIBA
Scanning and Synchronization with

Downstream
• On initialization or after signal loss,
– CM will try to acquire a downstream channel.
– CM has cached 5 (five) previously used downstream frequency
(stored as MRU - more recent used),
– It tries to acquire the downstream from the cached frequencies first
– If fails, will begin to continuously scan the 6-MHz channels of the
downstream frequency band of operation (from 860 MHz to 88
MHz) until it finds a valid downstream signal

68
TOSHIBA
Scanning and Synchronization with

Downstream (cont’d)
• A downstream signal is considered to be valid when the
modem has achieved the following steps:
– synchronization of the QAM symbol timing
– synchronization of the FEC framing
– synchronization of the MPEG packetization
– recognition of SYNC downstream MAC messages
• The cable modem remains in “SYNC” as long as it
continues to successfully receive the SYNC messages

69
TOSHIBA
Obtaining Upstream Parameters

• After synchronization,
– the CM will wait for an upstream channel descriptor message
(UCD) from the CMTS in order to retrieve transmission
parameters for the upstream channel.
– UCD messages are transmitted periodically from the CMTS for all
available upstream channels and they are addressed to the MAC
broadcast address.
– The CM will determine whether it can use the upstream channel
from the channel description parameters.
– If the channel is not suitable, then the CM will wait for a channel
description message for a channel that it can use.
– If no channel can be found after a suitable timeout period, then the
CM will continue scanning to find another downstream channel.

70
TOSHIBA
Ranging and Automatic Adjustments

• Ranging is the process of acquiring the correct timing
offset such that the cable modem’s transmissions are
aligned to the correct mini-slot boundary.
• First, the cable modem synchronizes to the downstream
and learns the upstream channel characteristics through the
Upstream Channel Descriptor MAC management message.
At this point, the cable modem will start ranging.

71
TOSHIBA
CMTS CM
[time to send the Initial Maintenance
opportunity]
send map containing Initial -----------MAP-------------->
Ranging Maintenance information element
with a broadcast/multicast Service ID
<---------RNG-REQ------- transmit ranging packet in contention
mode with Service ID parameter = 0
<---------RNG-REQ------- transmit ranging packet repeatedly

with
increasing power until ranging
response
is received.
[receive recognizable ranging packet]

allocate temporary Service ID
send ranging response ----------RNG-RSP------->
add temporary Service ID to poll list store temporary Service ID & adjust
other
parameters
[time to send the next map]
send map with Station Maintenance -----------MAP--------------> recognize own temporary Service ID in
information element to modem using map
temporary SID
<---------RNG-REQ------- reply to Station Maintenance
opportunity
poll
send ranging response ----------RNG-RSP------->
adjust local parameters
[time to send an Initial Maintenance
opportunity] send map containing
Initial Maintenance information
element with a broadcast/multicast
Service ID
send periodic transmit opportunity to ------------MAP------------>
broadcast address

72
TOSHIBA
DHCP (Dynamic Host Configuration

Protocol) Service
CM DHCP
send DHCP request to
broadcast address
----------------DHCP discover------------>
check CM MAC address & respond
<--------------DHCP offer ------------------
choose server
----------------DHCP request------------->
process request
<--------------DHCP response-------------
set up IP parameters from
DHCP response

73
TOSHIBA
TOD (Time and Date) Service
CM Time Server
send request to time
server
----------------time of day request------------>
process request
<--------------time of day response------------
set up / correct time of
day from response

74
TOSHIBA
TFTP (Trivial File Transfer Protocol)

Service
CM CMTS TFTP
Server
request parameter file
-------------- -----TFTP REQ---- -------------->
process request
<------------ ----- TFTP RSP---- ---------------
set up operational
parameters
inform CMTS ---REG-REQ-->
provision modem
<---REG-RSP---
set up Service IDs

75
TOSHIBA
Registration
• A CM must be authorized to forward traffic into the
network once it is initialized, authenticated and configured.
• The CM must forward the operational parameters to the
CMTS as part of a registration request. The CMTS must
perform the following operations to confirm the CM
authorization:
– Check the Message Integrity Check (MIC) and the authentication
signature on the parameter list.
– Assign a Service ID based on the classes of service supported.
– Reply to the modem registration request.

76
TOSHIBA
Software Upgrade
• Using Provisioning
– Config File contains:
• New software download image file name
• Software upgrade TFTP server
– Once CM resets, it will load the new software image
• Using SNMP
– Set MIB Objects:
• docsDevSwFilename: new software download image file name
• docsDevSwServer: software upgrade TFTP server
• docsDevSwAdminStatus: upgradeFromMgt(1), to start immediately
the software upgrade.

77
TOSHIBA
Review Questions I
• What are the DOCSIS service goals?
• Describe the DOCSIS components.
• List the different protocol layer/sublayer on the DOCSIS
architecture.
• Describe the different data forwarding mode for the CMTS
and CM.
• How does a CM acquire CPE MAC address?
• List two differences between the CM forwarding rules
between cable-to-ethernet and ethernet-to-cable?
• List the internal components of the Toshiba cable modem.
78
TOSHIBA
Review Questions I
• How many LED’s the Toshiba cable modem has on its
front panel.
• How many IP filter does the cable modem support?
• List the main components of a CMTS.
• What is the expected C/N ratio for normal DOCSIS
operation on the downstream and upstream?
• How many symbol rates are supported by DOCSIS
upstream? List them.
• How many bits does a 16QAM symbol represents? And
QPSK?

79
TOSHIBA
Review Questions I
• Which options of FEC coding are provided on the DOCSIS
upstream?
• List Five (5) attributes defined by a burst profile.
• What are the output transmit power on the upstream? What
is the accuracy?
• What are the modulation techniques used on the DOCSIS
downstream?
• List the frequency plans supported by DOCSIS downstream.
• Describe the main phases on the cable modem initialization.

80
TOSHIBA
Review Questions I
• Describe the scanning and synchronization with the
Downstream.
• What is a UCD?
• When does a cable modem conclude the initial ranging
process?
• Which DHCP messages are sent by a cable modem during
its initialization?
• How does the CMTS confirm the cable modem
authentication?
• Describe the two ways to upgrade a cable modem
software.
81
TOSHIBA
Transmission Covergence Sublayer

• Transmission Convergence Sublayer:
– created to improve demodulation robustness, facilitate common
receiving hardware for both video and data, and provide an
opportunity for the possible future multiplexing of video and data
over the PMD sublayer bitstream
– located between the downstream Physical layer and the MAC
sublayer.
• The downstream bitstream is defined as a continuous series
of 188-byte MPEG [ITU-T H.222.0] packets.
– These packets consist of a 4-byte header followed by 184 bytes of
payload

82
TOSHIBA
MPEG Header for DOCSIS
Field Length (bits) Description

sync_byte 8 0x47; MPEG Packet Sync byte
transport_error_indicator 1 Indicates an error has occurred in the reception of the packet. This bit is
reset to zero by the sender, and set to one whenever an error occurs in
transmission of the packet
payload_unit_start_indicator 1 A value of one indicates the presence of a pointer_field as the first byte of
the payload (fifth byte of the packet)
transport_priority 1 Reserved; set to zero
PID 13 MCNS Data-Over-Cable well-known PID (0x1FFE)
transport_scrambling_control 2 Reserved, set to ‘00’
Adaptation_field_control 2 ‘01’; use of the adaptation_field is NOT ALLOWED on the MCNS PID
Continuity_counter 4 cyclic counter within this PID

83
TOSHIBA
MPEG Payload for DOCSIS

• The MPEG payload portion of the MPEG packet will carry
the DOCSIS MAC frames.
– The first byte of the MPEG payload will be a ‘pointer_field’ if the
payload_unit_start_indicator (PUSI) of the MPEG header is set.
– The pointer_field contains the number of bytes in this packet that
immediately follow the pointer_field that the CM decoder must
skip past before looking for the beginning of an DOCSIS MAC
frame.
– The standard defines a stuff_byte pattern having a value (0xFF)
that is used within the DOCSIS payload to fill any gaps between
the DOCSIS MAC frames

84
TOSHIBA
Interaction with the MAC Sublayer
MPEG Header pointer_field MAC Frame stuff_byte(s)

(PUSI = 1) (= 0) up to 183 bytes) (0 or more)
Packet Format Where a MAC Frame Immediately Follows the pointer_field
MPEG Header pointer_field Tail of MAC Frame #1 stuff_byte(s) Start of MAC Frame #2
(PUSI = 1) (= M) (M bytes) (0 or more)
Packet Format with MAC Frame Preceded by Stuffing Bytes
MPEG Header pointer_field MAC Frame MAC Frame stuff_bytes MAC Frame
(PUSI = 1) (= 0) #1 #2 (0 or more) #3
Packet Format Showing Multiple MAC Frames in a Single Packet

85
TOSHIBA
DOCSIS Medium Access Control

(MAC)
• Main Features
– Bandwidth allocation controlled by CMTS.
– A stream of mini-slots in the upstream.
– Dynamic mix of contention-based and reservation-based upstream
transmit opportunities.
– Bandwidth efficiency through support of variable-length packets.
– Extensions provided for future support of ATM or other Data
PDU.
– Class of service support.
– Extensions provided for security at the Data Link layer.
– Support for a wide range of data rates.

86
TOSHIBA
MAC Definitions
• Service ID (SID)
– The concept of Service IDs is central to the operation of the MAC
protocol. Service IDs provide both device identification and class-
of-service management.
– The length of the Service ID is 14 bits.
– Four types of Service IDs are defined:
• 0x3FFF - broadcast, intended for all stations.
• 0x2000-0x3FFE - multicast, intended for a defined group of stations.
• 0x0001-0x1FFF - unicast, intended for a particular CM or a particular
service within a CM.
• 0x0000 - null address, addressed to no station.

87
TOSHIBA
MAC Definitions (cont’d)

• Upstream Intervals, Mini-slots
– The upstream transmission time-line is divided into intervals by the
upstream bandwidth allocation mechanism. Each interval is an
integral number of mini-slots. A “mini-slot” is the unit of
granularity for upstream transmission opportunities.
– A mini-slot is a power-of-two multiple of 6.25- ms increments, i.e.,
1, 2, 4, 8, 16, 32, 64, or 128 times 6.25 ms.

88
TOSHIBA
MAC Frame Format

• A MAC frame is the basic unit of transfer between MAC
sublayers at the CMTS and the cable modem. The same
basic structure is used in both the upstream and
downstream directions. MAC frames are variable in
length.
• Generic MAC Frame Format
PMD Overhead
(upstream)
Data PDU
MAC Header
(optional)
MPEG PSI Header MAC Frame

(downstream)

89
TOSHIBA
Upstream MAC/Physical Layer

Convergence
Uper Layer
MAC Frame MAC Frame MAC Frame
MAC Sublayer
PMD Sublayer
Start of Burst Start of Burst Start of Burst
at Mini-slot at Mini-slot at Mini-slot
boundary boundary boundary
PMD F PMD F PMD F F F

Over- Data E Over- Data E Over- Data E Data E Data E
head C head C head C C C
PMD Overhead

90
TOSHIBA
MAC Header Format
FC MAC_PARM LEN (SID) EHDR HCS

(1 byte) (1 byte) (2 bytes) (0-240 bytes) (2 bytes)
FC TYPE FC PARM EHDR_ON

(2 bits) (5 bits) (1 bit)

91
TOSHIBA
MAC Header Format (cont’d)

MAC Header Field Usage Size
FC Frame Control: Identifies type of MAC Header 8 bits

MAC_PARM Parameter field whose use is dependent on FC: 8 bits
if EHDR_ON=1; used for EHDR field length (ELEN)
else if for concatenated frames used for MAC frame count
else (for Requests only) indicates the number of mini-slots and/or ATM
cells requested
LEN (SID) The length of the MAC frame. The length is defined to be the sum of the 16 bits
number of bytes in the extended header (if present) and the number of bytes
following the HCS field. (For a REQ Header, this field is the Service ID instead)
EHDR Extended MAC Header (where present; variable size). 0-240 bytes
HCS MAC Header Check Sequence 2 bytes
Length of a MAC Header 6 bytes + EHDR

92
TOSHIBA
FC Field Format
FC Field Usage Size
FC_TYPE MAC Frame Control Type field: 2 bits

00: Packet PDU MAC Header
01: ATM PDU MAC Header
10: Reserved PDU MAC Header
11: MAC Specific Header
FC_PARM Parameter bits, use dependent on FC_TYPE. 5 bits
EHDR_ON When = 1, indicates that EHDR field is present. 1 bit
[Length of EHDR (ELEN) determined by MAC_PARM field]

93
TOSHIBA
Error Handling
• The cable network is a potentially harsh environment that may cause
several different error conditions to occur.
– This may be a result of noise on the network or possibly by collisions in
the upstream channel.
– Framing recovery on the downstream channel is performed by the MPEG
transmission convergence sublayer.
– In the upstream channel, framing is recovered on each transmitted burst,
such that framing on one burst is independent of framing on prior bursts.
Hence, framing errors within a burst are handled by simply ignoring that
burst; i.e., errors are unrecoverable until the next burst.
• For every MAC transmission, The HCS is verified. When a bad HCS is
detected, the MAC Header and any payload is dropped.

94
TOSHIBA
Upstream MAC
• The upstream channel is modeled as a stream of mini-slots.
– The CMTS generates the time reference for identifying these slots, it also
controls access to these slots by the cable modems (through grants).
– The CM must time its transmission so that the CMTS receives it in the
time reference specified.
• The basic mechanism for assigning bandwidth management is the
allocation map.
– The allocation map is a MAC Management message transmitted by the
CMTS on the downstream channel that describes, for a specif interval, the
uses of the upstream mini-slots.
– A map may describe:
• some slots as grants for particular stations to transmit data in,
• other slots as available for contention transmission, and
• other slots as an opportunity for new stations to join the link.

95
TOSHIBA
Allocation Map
Map PDU Transmitted on downstream channel by the CMTS
mini-slots
CM tx request CM tx CM tx
maintenance
opportunity contention area opportunity opportunity
previous map current map as yet unmapped

area

96
TOSHIBA
Allocation Map Message

• The allocation map is a varying-length MAC Management
message that is transmitted by the CMTS to define
transmission opportunities on the upstream channel.
– It includes a fixed-length header followed by a variable number of
information elements (IEs). Each information element defines the
allowed usage for a range of mini-slots.
• Each Information Element (IE) consists of a 14-bit Service
ID, a 4-bit type code, and a 14-bit starting offset.
• CMTS vendors may associate a specific pre-defined burst
profile with each type of Information Element (IE).

97
TOSHIBA
Types of Information Elements

• Request IE
– The Request IE provides an upstream interval in which requests may be
made for bandwidth for upstream data transmission.
• Request/Data IE
– The Request/Data IE provides an upstream interval in which requests for
bandwidth or short data packets may be transmitted.
• Initial Maintenance IE
– The Initial Maintenance IE provides an interval in which new stations
may join the network.
• Station Maintenance IE
– The Station Maintenance IE provides an interval in which stations are
expected to perform some aspect of routine network maintenance, such as
ranging or power adjustment.

98
TOSHIBA
Types of Information Elements (cont’d)

• Long and Short Data Grant IEs
– The Data Grant IE provides an opportunity for a CM to transmit one or
more upstream PDUs.
• Data Acknowledge IE
– The Data Acknowledge IE acknowledges that a data PDU was received.
• Expansion IE
– The Expansion IE provides for extensibility, if more than 16 code points
or 32 bits are needed for future IEs.
• Null IE
– A Null IE terminates all actual allocations in the IE list.

99
TOSHIBA
Upstream Requests
• Only one type of upstream request is inherent to the
allocation protocol:
– request for upstream bandwidth.
– the request may be transmitted any time that either a request or a
data PDU is allowed from the particular station (Request IE,
Request/Data IE or Data Grant IE).
– In addition, it may be piggybacked on a data transmission.
– A request includes:
• The Service ID making the request.
• The number of mini-slots requested.

100
TOSHIBA
Contention Resolution
• The CMTS controls assignments on the upstream channel
through the MAP and determines which mini-slots are
subject to collisions.
– The CMTS may allow collisions on either Requests or Data PDUs.
• The mandatory method of contention resolution that must
be supported is based on a truncated binary exponential
back-off, with the initial back-off window and the
maximum back-off window controlled by the CMTS.
– The values are specified as part of the Bandwidth Allocation Map
(MAP) MAC message and represent a power-of-two value.
• For example, a value of 4 indicates a window between 0 and 15; a
value of 10 indicates a window between 0 and 1023.

101
TOSHIBA
Contention Resolution (cont’d)

• CM wants to transmit upstream data:
– Sets the back-off windows based on the information provided by
the CMTS (through MAP message).
– Randomly selects a number within its back-off window.
• This random value indicates the number of contention transmit
opportunities which the CM must defer before transmitting.
– After a contention transmission, the CM waits for a Data Grant
(Data Grant Pending) or Acknowledgment in a subsequent MAP.
• Once either is received the contention resolution is completed.
• If does not received either; the CM determines that the contention
transmission was lost.
– CM must now increase its back-off window by a factor of two, as long as it
is less than the maximum back-off window and repeat the process. The
maximum number of retries is 16.

102
TOSHIBA
Class of Service
• DOCSIS supports different user defined classes of
services.
• Variables associated with class of service:
– Class ID: identifier for the class of service; range 1 to 16.
– Service ID; associated to a class of service
– Maximum Downstream Rate (bit/sec)
– Maximum Upstream Rate (bit/sec)
– Upstream Channel Priority (0-7)
– Guaranteed Minimum Upstream Channel Rate (bit/sec)
– Maximum Upstream Transmit Burst (bytes)
– Class-of-Service Privacy Enable (0 or 1)

103
TOSHIBA
Rate Control Mechanism

• The traffic rate is controlled by a token-bucket mechanism.
– The token bucket is controlled by parameters R and B.
– R is expressed in bits per second, and must take into account all
MAC frame data PDUs of the Service Flow.
– B is expressed in bytes.
Token Generation Rate = Max Rate (R)

Token Token Bucket Size = Max Burst Size (B)
Bucket

104
TOSHIBA
Filtering Mechanism
• The Cable Device MIB provides objects for both LLC and IP protocol
filters.
– The LLC protocol filter entries can be used to limit CM forwarding to a
restricted set of network-layer protocols (such as IP, IPX, NetBIOS, and
Appletalk).
– The IP protocol filter entries can be used to restrict upstream or
downstream traffic based on source and destination IP addresses,
transport-layer protocols (such as TCP, UDP, and ICMP), and source and
destination TCP/UDP port numbers.
– The MIB objects can be set using either SNMP or the CM Config File.
– The cable modem supports multiple filtering entries; 32 IP filtering
entries, 16 Ethernet filtering entries and 16 LLC filtering entries.

105
TOSHIBA
Setting up a Filtering
• Example using SNMP:
– Discard any inbound UDP/bootp packet from the Ethernet interface. This
filtering will be set up as the third entry on the cable modem IP filtering table.
MIB Object ID Value Description Comments
docsDevFilterIpDefault 2 (accept) for accepting new entries on the filtering
table
docsDevFilterIpStatus.3 1 (active) for activating the new filtering entry
docsDevFilterIpControl.3 1 (discard) for discarding packets
docsDevFilterIpIfIndex.3 1 (Ethernet) for Ethernet side
docsDevFilterIpDirection.3 1 (inbound) for inbound traffic
docsDevFilterIpBroadcast.3 2 (false) unicast, broadcast and multicast packets will
be filtered
docsDevFilterIpSaddr.3 0.0.0.0 (all) source IP address
docsDevFilterIpSmask.3 0.0.0.0 (all) source IP mask
docsDevFilterIpDaddr.3 0.0.0.0 (all) destination IP address
docsDevFilterIpDmask.3 0.0.0.0 (all) destination IP mask
docsDevFilterIpProtocol.3 17 (UDP) protocol
docsDevFilterIpSourcePortLow.3 67 (bootps) source port low (first on a range)
docsDevFilterIpSourcePortHigh.3 67 (bootps) source port high (last on a range)
docsDevFilterIpDestPortLow.3 68 (bootpc) destination port low (first on a range)
docsDevFilterIpDestPortHigh.3 68 (bootpc) destination port high (last of a range)
docsDevFilterIpMatches.3 0 (set to 0) counter for events
docsDevfilterIpDefault 1 (discard) for finishing accept new entries
Note that the .3 on all set commands above represents the third entry on the cable modem’s IP filtering
table.

106
TOSHIBA
Setting up a Filtering (cont’d)

• Example using CM Config File:
– Discard any inbound UDP/bootp packet from the Ethernet interface. This
filtering will be set up as the third entry on the cable modem IP filtering table.
MIB Object ID Value Description Comments

docsDevFilterIpStatus.3 1 (active) for activating the new filtering entry
The following value will be added on the configuration file as part of the Type/Length/Value (TLV)
"SNMP MIB Object (11)" you inserted: (note that all values are hexadecimal)
30.10.06.0B.2B.06.01.03.53.01.06.04.01.02.03.02.01.01
This entry is composed of Type, Length and Value fields.
The entry starts with a Type 30 hex, which indicates the start up of a SNMP MIB set command, followed by
the Length which is 10 hex (16 decimal), then by the actual entry Value.
The value is in fact other entries that will be again composed of Type, Length and Value fields. The entry
starts with a Type 06 hex, which indicates the MIB Object ID (OID), followed by the Length which is 0B
hex (11 decimal), then by the actual entry Value, a mandatory value of 2B hex followed by the MIB OID
06.01.03.53.01.06.04.01.02.03 (this points to docsDevFilterIpStatus.3). The next entry defines the value to
be set on the MIB Object ID (OID). The entry starts with a Type 02 hex, which indicates an integer decimal
value, followed by the Length which is 01 hex (1 decimal), then by the actual entry Value, to be set on the
MIB OID, 01.

107
TOSHIBA
Multicast
• Cable modem supports multicast operation based on either
the DOCSIS v1.0 or DOCSIS v1.1 specification.
– The factory default for the multicast operation is the DOCSIS v1.0
specification, however, it can be changed through SNMP.
– DOCSIS v1.0 multicast operation mode forward all multicast
packets, unless blocked by IP filtering
– DOCSIS v1.1 multicast operation mode supports IGMP Proxy
function
• only required multicast packets are forwarded, improving bandwidth
utilization.

108
TOSHIBA
Baseline Privacy
• Baseline Privacy provides cable modem users with data privacy across
the RF network.
– It provides user data privacy by encrypting traffic flows between CM and
CMTS.
• Baseline Privacy uses the Cipher Block Chaining (CBC) mode of the
US Data Encryption Standard (DES) algorithm (known as 3-DES) to
encrypt the Packet PDU field in both upstream and downstream RF
MAC Packet Data PDUs.
– The MAC headers of these Packet Data PDUs must not be encrypted.
– The payloads, as well as headers, of MAC management messages must be
sent in the clear to facilitate registration, ranging, and normal operation of
the MAC sublayer.

109
TOSHIBA
Baseline Privacy (cont’d)

• Baseline Privacy’s key management protocol runs between CM and
CMTS
– CMs use the protocol to obtain authorization and traffic keying material
(pertaining to a particular SID) from the CMTS, and to support periodic
reauthorization and key refresh.
– The key management protocol uses Rivest Shamir Adleman (RSA), a
public-key encryption algorithm, and the Electronic Codebook (ECB)
mode of DES to secure key exchanges between CM and CMTS.
– CMs must have factory-installed RSA private/public key pairs, or provide
an internal algorithm to generate such key pairs dynamically.

110
TOSHIBA
Operational Overview
• Baseline Privacy initialization begins with the CM sending the CMTS
an authorization request.
– It contains data identifying the CM (e.g., MAC address), the CM’s RSA
public key, and a list of zero or more assigned unicast SIDs that have been
configured to run Baseline Privacy.
• If the CMTS determines the requesting CM is authorized for these
services.
– The CMTS responds with an authorization reply containing a list of SIDs
(both unicast and multicast) that the CM is permitted to run Baseline
Privacy on.
• The reply also includes an authorization key from which CM and CMTS derive
the keys needed to secure a CM’s subsequent requests for per-SID traffic
encryption keys, and the CMTS’s responses to these requests. The
authorization key is encrypted with the receiving cable modem’s public key.

111
TOSHIBA
Privacy Key Management

• DOCSIS Privacy uses two encryption keys:
– The KEK is a DES encryption key that the CMTS uses to encrypt the
traffic encryption keys (TEKs) it sends to the modem.
– Traffic encryption keys (TEKs) are used for encrypting user data traffic.
– CM and CMTS use message authentication keys to authenticate, via a
keyed message digest, the key requests and responses they exchange.
• After achieving authorization, a cable modem periodically seeks re-
authorization with the CMTS
– A CM must maintain its authorization status with the CMTS in order to be
able to refresh aging traffic encryption keys.

112
TOSHIBA
9 - Cable Modem Configuration

Information
• CM (MD5) Configuration File
– The CM parameters are contained in configuration files located in
the Headend Provisioning Server. These files must be created and
made available before any customer cable modems can be used.
– Configuration settings are divided into three types:
• Standard configuration settings which must be present
• Standard configuration settings which may be present
• Vendor-specific configuration settings.
– CMs must be capable of processing all standard configuration
settings. Authentication of the provisioning information is
provided by two message integrity check (MIC) configuration
settings, CM MIC and CMTS MIC.

113
TOSHIBA
Configuration File Format

• It must consist of a number of configuration
settings (1 per parameter) each of the form (TLV)
type: length: value:
– where:
• type is a single-octet identifier which defines the parameter,
• length is a single octet containing the length of the value field
in octets (not including type and length fields).
• value is from one to 254 octets containing the specific value for
the parameter.

114
TOSHIBA
Configuration File Format (cont’d)
type, length, value for parameter 1

type, length, value for parameter 2
type, length, value for parameter n

type, length, value for CM MIC
type, length, value for CMTS MIC
end of data marker

115
TOSHIBA Type Length Description If Not Present
1 1 Downstream Frequency The locked receive frequency should be used.
2 1 Upstream Channel ID 2-way RFI CM: default=current upstream channel
Telephony Return CM: parameter is mandatory and
Config. 3
4-X
1
n
(0/1) Network Access Control Object
Class of Service Encodings
must be set to 0 (zero).
(Mandatory)
The only subclass defined is 0 2-way RFI CM:
default=NO SERVICE Note: should be logged as error
Parameters
in the event log. Telephony Return CM: default=Best
Effort Svc. Note: telephony upstream is independent of
CoS
4-1 1 [1.16] Class ID (Optional)
4-2 4 Maximum Downstream Data Rate No maximum downstream data rate
4-3 4 Maximum Upstream Data Rate No maximum upstream data rate
4-4 1 [0.7] Upstream Channel Priority 0 (Lowest Priority)
4-5 4 Guaranteed Minimum Upstream Data Rate 0 (No guaranteed minimum upstream data rate)
4-6 * 2 Maximum Upstream Channel Burst Use value from Upstream Channel Descriptor
4-7 1 (0/1) C-o-S Privacy Enabled 0 (Privacy not enabled)
5 n Modem Capabilities No optional features
6 16 CM MIC (Mandatory)
7 16 CMTS MIC (Mandatory)
8 3 Vendor ID Configuration Setting Vendor ID = All Zeros (this might be any CM)
9 n Software Upgrade Filename Software upgrade is not needed
10 n (0/1) SNMP Write Access Control 0 (No SNMP Write Access Control)
11 n SNMP MIB Object No SNMP objects set
15-X n Service Provider (Refer to SP-CMTRI-I01-970804)
15-2 n Service Providers (Refer to SP-CMTRI-I01-970804)
15-3 n Phone Number (1) (Refer to SP-CMTRI-I01-970804)
15-6 1 Retry Connection (Refer to SP-CMTRI-I01-970804)
15-7 n Username (Refer to SP-CMTRI-I01-970804)
15-8 n Password (Refer to SP-CMTRI-I01-970804)
15-9 1 DHCP Authenticate (Refer to SP-CMTRI-I01-970804)
15-10 4 DHCP Server IP Address (Refer to SP-CMTRI-I01-970804)
15-11 n RADIUS Realm (Refer to SP-CMTRI-I01-970804)
15-12 1 PPP Authentication (Refer to SP-CMTRI-I01-970804)
15-13 4 Demand Dial Timer (Refer to SP-CMTRI-I01-970804)
16 4 SNMP IP Address (Refer to SP-CMTRI-I01-970804)
17 n Baseline Privacy Configuration Settings
17-1 4 Authorized Timeout (Refer to SP-BPI-I01-970922)
17-2 4 Re-authorize Wait Timeout (Refer to SP-BPI-I01-970922)
17-3 4 Authorization Wait Timeout (Refer to SP-BPI-I01-970922)
17-4 4 Operational Wait Timeout (Refer to SP-BPI-I01-970922)
17-5 4 Re-key Wait Timeout (Refer to SP-BPI-I01-970922)
17-6 4 TEK Grace Time (Refer to SP-BPI-I01-970922)
18 1 Maximum # of CPEs 1
19 4 TFTP Server Timestamp (Optional)
20 4 TFTP Server Provisioned Modem Address (Optional)
0 N/A Pad Not Applicable
255 N/A End-of-Data (Mandatory)
* Note: TBA

116
TOSHIBA
Configuration File Editor

• This editor allows the administrator to create or to modify
a DOCSIS cable modem configuration file.
• List of Commands
Load Load Config file
Save Save Config file
Insert Here Insert TLV Data
Insert Child Insert TLV Child Data
Delete Delete TLV Data
About About Config Editor
Quit Quit Config Editor

117
TOSHIBA
Configuration File Editor (cont’d)

• Type/Length/Value (TLV) Data Entries supported by the Editor
– Downstream Frequency(1)
– Upstream Channel ID(2)
– Network Access Control(3)
– Class of Service Encodings(4)
• Class ID(4-1)
• Max.Downstream Rate(4-2)
• Max.Upstream Rate(4-3)
• Upstream Channel Priority(4-4)
• Min.Upstream Rate(4-5)
• Max.Upstream Tx. Burst(4-6)
• CoS BP Enable(4-7)

118
TOSHIBA

– Software Upgrade Filename(9)
– SNMP Write Access Control(10)
– SNMP MIB Object(11)
– CPE Ethernet MAC Address(14)
– Baseline Privacy Configuration(17)
• Authorize Wait(17-1)
• Reauthorize Wait(17-2)
• Authorization Grace(17-3)
• Operational Wait(17-4)
• Rekey Wait(17-5)
• TEK Grace(17-6)
• Authorize Reject(17-7)

119
TOSHIBA

– Maximum Number of CPEs(18)
– TFTP Server Timestamp(19)
– TFTP Server Provisioned Modem Address (20)
– Software Upgrade TFTP Server(21)
– Vendor Specific Info(43)
• Vendor ID(8)

120
TOSHIBA

121
TOSHIBA
DHCP Configuration
• The following fields are expected in the DHCP response
returned to the CM.
– The IP address to be used by the CM (yiaddr).
– The IP address of the TFTP server for use in the next phase of the
bootstrap process (siaddr).
– If the DHCP server is on a different network (requiring a relay
agent), then the IP address of the relay agent (giaddr). Note: this
may differ from the IP address of the first hop router.
– The name of the CM configuration file to be read from the TFTP
server by the CM (file).
– The subnet mask to be used by the CM (Subnet Mask, option 1).

122
TOSHIBA
DHCP Configuration (cont’d)

– The time offset of the CM from Universal Coordinated Time
(UTC) (Time Offset, option 2). This is used by the CM to calculate
the local time for use in time-stamping error logs.
– A list of addresses of one or more routers to be used for forwarding
CM-originated IP traffic (Router Option, option 3). The CM is not
required to use more than one router IP address for forwarding.
– A list of [RFC-868] time-servers from which the current time may
be obtained (Time Server Option, option 4).
– A list of SYSLOG servers to which logging information may be
sent (Log Server Option, option 7).

123
TOSHIBA
Configuration Example
• DHCP Example (Join)
[dhcpcap (Solaris2.6) see www.join.com for more information ]
modemhome:\
:nw=192.168.1.0:\ # Network or subnet Address
:gw=192.168.1.252:\ # Routers option
:sm=255.255.255.0:\ # Subnet Mask
:ba=192.168.1.255:\ # Broadcast Address
:ts=209.80.15.61:\ # Time Server Address
:nt=209.80.15.61:\ # Boot File Server Address (TFTP Server)
:lg=209.80.15.61:\ # Log Server Address
:cm=209.80.15.61:\ #
:to=32400:\ #
:bf="modem.cfg":\ # Boot file (Cable modem Configuration file name)
:sa=209.80.15.61:\ # Server Address
:dn=npdc.tais.com:\ # Domain name
:hd="/tftpboot":\ #Home directory
:td="/tftpboot":\ #TFTP root directory
:ds=204.182.160.1: # DNS Server Address

124
TOSHIBA
• DHCP Example (CNR)
[Policies (Solaris2.6) see www.cisco.com for more information ]

Required Parameters for DOCSIS provisioning
boot-file: modem.cfg # Boot file (Configuration file name)
log-servers : 209.80.15.61 # Log Server Address
ntp-servers : 209.80.15.61 # NTP Servers
root-path : /tftpboot # Root Path(TFTP root directory)
routers : 192.168.1.252 # Routers
tftp-server : 209.80.15.61 # TFTP Server
time-servers: 209.80.15.61 # Time Server Address
packet-siaddr : 209.80.15.61 # DHCP Server Identifier

125
TOSHIBA
• DHCP Example (WindowsNT)
[Scope (WindowsNT DHCP Manager w/Service Pack4.0)]

Required Parameters for DOCSIS provisioning
003 Router --- 192.168.1.252 #Routers
004 Time Server --- 209.80.15.61 # Time Server Address
007 Log Servers --- 209.80.15.61 # Log Server Address
017 Root Path --- /tftpboot # Root Path(TFTP root directory)
028 Broadcast Address --- 192.168.1.255 # Broadcast address
066 Boot Server Host Name --- 209.80.15.61 # TFTP Server
067 Bootfile Name --- modem.cfg # Boot file (Configuration file name)

126
TOSHIBA
• Cisco uBR Example
[uBR configuration example]
ubr7223#show running-conf
interface FastEthernet0/0
ip address 209.80.15.61 255.255.255.0
!
interface Cable2/0
ip address 192.168.1.252 255.255.255.0
no keepalive
cable helper-address 209.80.15.61
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream frequency 633000000
cable upstream 0 frequency 7008000
cable upstream 0 channel-width 3200000
cable upstream 0 minislot-size 4
no cable upstream 0 shutdown
!

127
TOSHIBA
Review Questions II
• What are the functions of Transmission Convergence
sublayer? Do downstream and upstream support this
sublayer?
• Describe the function of the pointer_field on the MPEG
payload.
• List five (5) main features of the DOCSIS Medium Access
Control (MAC).
• What is the definition for a Service ID (SID)?
• List the possible size of mini-slots (in msec)?
• What is the maximum size of a MAC Header?

128
TOSHIBA
Review Questions II
• Which types of slots are described by a MAC allocation
map message?
• List all types of Information Elements (IE).
• What information is included on a upstream request
message?
• Describe the contention resolution protocol used by
DOCSIS MAC.
• List 5 (five) variables associated with class of services.
• Which token bucket parameter is used to define the
maximum transmission rate?

129
TOSHIBA
Review Questions II
• Describe the two ways to set filtering on the cable modem.
• What is the function of the Baseline Privacy?
• Which security protocol is used to key management?
• Describe the encryption keys used by Baseline Privacy?
• Where the cable modem Configuration File is located?
• Describe the TLV.
• List 5 (five) parameters of Configuration File.
• When using the Configuration File Editor which command
you need to set the Max. Upstream Rate parameter.

130
TOSHIBA
10 - Cable Modem Installation

Assumption: Single cable drop for both TV and Cable Modem
• Connect the Cable TV coax to the IN connector of a coupler.
• Connect a coaxial cable from the OUT connectors of the splitter to the
input connector of the television set.
• Connect a coaxial cable from the TAP connector of the splitter to the
RF input connector on the cable modem rear panel.
• Connect the 10BaseT signal cable from your computer to the
10BASE-T connector on the cable modem rear panel.
• Connect the AC adapter to the 12VDC 1A IN jack on the cable
modem rear panel. Then plug in the AC adapter to the wall electrical
outlet.

131
TOSHIBA
Installation - Overview
Couple r
IN OUT
TAP
Cable
TV
Coax
Te le vis ion
AC Ethe rne t
Adapte r Cable
Cable Pe rs onal Com pute r

M ode m

132
TOSHIBA
Monitoring LED’s
Function Color Definition
Power Green - dark for power off
- solid for power on
Cable Green - dark for no downstream RF carrier
present or power off
- flashing slowly for downstream RF
carrier present and ranging in progress
- flashing fast for registration in progress
- solid for the Cable Modem registered
and ready to transfer data

133
TOSHIBA
Monitoring LED’s (cont’d)

PC Green - dark for no Ethernet carrier present or
power off
- solid for Ethernet carrier present
Data Green - dark for no user data going through the
Cable Modem or power off
- flashing for user data going through
the Cable Modem

134
TOSHIBA
Monitoring LED’s (cont’d)

Test Amber - dark for initial self-test of the Cable
Modem OK or power off
- flashing for initial self-test of the Cable
Modem in progress or software downloading
of the Cable Modem in progress
- solid for self-test failure of
the Cable Modem

135
TOSHIBA
Installation & Test Wizard

• Java-based application
– Platform independent, interactive GUI interface
– Designed to support subscriber ‘self-install’
– Helps subscriber/MSO to diagnose problems
– Easily customized to specific needs of cable operators (logo,
troubleshooting sequence, add specific contact numbers, etc.)
• Includes two modules:
– Self-Installation Guide
– Troubleshooting Tool

136
TOSHIBA
Installation & Testing Wizard (cont’d)

137
TOSHIBA

138
TOSHIBA

139
TOSHIBA
11 - Cable Modem Trouble Shooting

Problem Action
No Power Check power outlet, replace power supply or
cable modem if necessary
No Downstream Verify cabling, check for presence of video
signal, verify power levels, verify CMTS
Ranging Failed Verify power levels, verify CMTS
Registration Failed Verify DOCSIS Provisioning Server and CMTS
No Ethernet Carrier Check cabling, verify Ethernet and network
configuration on subscriber’s PC
Self-test Failed Replace cable modem

140
TOSHIBA
Normal Cable Modem Operation

• When power is applied, the cable modem automatically tries to enter
operational state by performing the following operations:
– Power-up tests
– Downstream channel acquisition
– Upstream channel acquisition / Ranging
– Establishing IP connectivity using DHCP
– Obtain Time of Day
– Transfer operational parameters using TFTP
– Registration to authorize traffic forwarding
– Baseline Privacy Initialization if enabled
– Operational State

141
TOSHIBA
Installation & Testing Wizard

142
TOSHIBA

143
TOSHIBA

144
TOSHIBA
Advanced Diagnostics
• Advanced Diagnostics
– Java-based Application
– Communicates using SNMP
– Support for Trouble Shooting and Performance Analysis
• Throughput Analysis
• CMTS Statistics
• Power, SNR, Error Statistics and Logs
– Continuously polls a specific modem to obtain statistics
– Support for DOCSIS and Toshiba specific MIB’s
– Allows print and save as text the collected statistics

145
TOSHIBA
Advanced Diagnostics (cont’d)

• Operation Modes
– Private IP
• Communicates with the modem’s private IP (192.168.100.1)
• Only works on the Ethernet port
• Informs the DHCP-provided modem’s IP
– Specific IP
• Communicates with the DHCP-provided modem’s IP
– MAC Search
• Search for the modem MAC address on a list of CMTS’s
• Find the DCHP-provided modem’s IP
• Communicates with the DHCP-provided modem’s IP

146
TOSHIBA
View Menu

147
TOSHIBA
Cable Modem Info

148
TOSHIBA
Event Log

149
TOSHIBA
Power Monitor

150
TOSHIBA
RF Channel Table

151
TOSHIBA
Signal Noise Ratio (SNR) Monitor

152
TOSHIBA
LED Panel

153
TOSHIBA
Headend Information

154
TOSHIBA
Data Performance Monitor

155
TOSHIBA
CMTS Panel

156
TOSHIBA
CPE Info

157
TOSHIBA
Advanced Diagnostics Options

• Options/Tools are available on the Advanced Diagnostics to controls it:
– Set Gauge Ranges
• Controls the ranges (green/yellow/red) for all gauges
– Set MIB community
• Sets the MIB community for the CMTS and CM SNMP access
– CMTS Search List
• Defines a list of CMTS for MAC search mode
– Set Password
• Create/Modify the password request on tool’s startup
– Ping
• Allows the user to send continuously ping (ICMP) messages to any IP address.
User also can control the ping message size.
– Packet Generator
• Sends continuously ping packets for the modem under testing.

158
TOSHIBA
Set Gauge Ranges

159
TOSHIBA
Ping

160
TOSHIBA
Advance Diagnostics Help

• Help menu contains the following information:
– User Guide
– DOCSIS Error Codes
– Link to Toshiba MSO Support Web Page
• Setting Information
– All settings are stored on a file called settings.ini

161
TOSHIBA
12 - MSO Support Web Page

• How to Access:
http://www.toshiba.com/taisnpdc/downloads
username: cablemodem
password: intouch
• What is available:
– Modem Features & Specifications
– Modem Software Image
– Training Material
– Documentation
• Manuals, MIB files and FAQ
– Tools
• Wizard, Advance Diagnostics and Config File Editor

162
TOSHIBA
13 - Using SNMP
• Cable Modem supports Simple Network Management
Protocol (SNMP)
– It supports standard MIB objects, DOCSIS MIB objects
and Toshiba proprietary MIB objects
• DOCSIS MIB files
– bpi-mib-00.mib
– cable-04.mib
– brfmib-04.mib
– Refer to Cable Modem System Admin. Manual for list
of DOCSIS and Toshiba MIB Objects

163
TOSHIBA
SNMP
• SNMP entities
– Manager: executes network management operations which monitor and
control agent systems (e.g. HP Open View Network Node Manager).
– Agent: device (such as host, router, switch or hub) that has an agent
responsible for performing network management operations requested by
a manager.
• Management Information Base (MIB): information hold by an agent
• Community
– defines which object can be access in a MIB
• Actions allowed by SNMP:
– Manager can retrieve management information from a agent
– Manager can alter, or set, management information on an agent
– Agent can send information to a manager without an explicit request from
the manager (called trap or notification)

164
TOSHIBA
SNMP (cont’d)
• Manager-Agent Communication through SNMP
Manager Agent
MIB
SNMP Request
Alter Information
SNMP Reply
Retrieve Information
SNMP Trap

165
TOSHIBA
14 - Serial Diagnostic Port

• A special version of the Toshiba Cable Modem with a
serial port can be used for detailed diagnosis.
– a PC operating in terminal mode can be attached to the modem to
monitor messages generated by the modem and to enter diagnostic
commands.
RF
DC IN
10 BaseT 12 V, 1A
Serial Port

166
TOSHIBA
Connecting to Serial Diagnostic Port
• Connect one end of the diagnostic serial cable to the serial connector
on the top of the modem.
• Connect the other end of the diagnostic serial cable to a free serial port
on a PC.
• Use HyperTerminal or another communications package to
communicate with the cable modem.
– The serial port parameters are: 8 data bits, 1 stop bit, no parity, 38.4 kbps,
and no flow control.
• The cable modem will not echo back typed characters so you should
enable “local echo” in HyperTerminal.

167
TOSHIBA
Using Serial Diagnostic Port

• You will be able to observe:
– Power up built-in self-testing sequence
– Channel Scanning
– Normal Acquisition and Registration
– Ranging Maintenance
> 00000A46: <134>Cablemodem[Toshiba]: Downstream acquired. Frequency = 507000000 Hz.
00000C58: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.

00000DD4: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.
00000F14: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.
00001252: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.
00001496: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.
00001B58: <134>Cablemodem[Toshiba]: R02.0 No ranging response received. T3 time-out.
000031EC: <134>Cablemodem[Toshiba]: dhcpWork: Starting.
000031EC: <134>Cablemodem[Toshiba]: dhcp: Received DHCP_EVT_MSG_TO_GO message.
0000320A: <134>Cablemodem[Toshiba]: dhcp: Received DHCP_EVT_GOT_RESPONSE message.
0000320A: <134>Cablemodem[Toshiba]: dhcp: Received DHCP_EVT_MSG_TO_GO message.
00003228: <134>Cablemodem[Toshiba]: dhcp: Received DHCP_EVT_BOUND message.
00003228: <134>Cablemodem[Toshiba]: DHCP complete. IP address = 209.218.82.151.
00003228: <134>Cablemodem[Toshiba]: CM_time_server (209.218.82.203)
000039E4: <134>Cablemodem[Toshiba]: Network time received. Local time = 910765572.
000039F8: <134>Cablemodem[Toshiba]: Config file dnld: Starting configuration file
download.
00003A52: <134>Cablemodem[Toshiba]: REG-RSP success. Registration SID = 174.
00003A52: <134>Cablemodem[Toshiba]: Upstream concatenation not supported.
00003A52: <134>Cablemodem[Toshiba]: Entering operational (data forwarding) state.
00003A8E: <134>Cablemodem[Toshiba]: Config file dnld: Download complete.
00003A98: <132>Cablemodem[Toshiba]: lCosMaxUpRate(2560000) sCosMaxUpTxBurst(2000)

168
TOSHIBA
Using Serial Diagnostic Port

• Commands
– ?; help
– rs; performs a software reset of the cable modem.
– rev; displays hardware and software version.
– Setmac; displays cable modem MAC address.
– getIp; displays cable modem DHCP-provided IP address.
– ls; displays Libit 4030 PHY chip status.
– ds; displays downstream (HFC) statistics.
– do; displays downstream (Ethernet) statistics.
– us; displays upstream statistics.
– ucdShow; displays contents of the UCD.
– dumplog; displays event log.
– sdf; displays downstream cached frequencies.
– sdc; displays downstream cached channels.

169
TOSHIBA System Name Time Reference Minimum Value Default Maximum
Value Value
DOCSIS CMTS
CMTS
Sync Interval
UCD Interval
Nominal time between transmission
of SYNC messages
Time between transmission of UCD
messages
200 msec
2 sec
Parameters CMTS
CMTS
Max MAP Pending
Ranging Interval
The number of mini-slots that a
CMTS is allowed to map into the
future
Time between transmission of
4096 mini-
slot times
2 sec
& Constants CM Lost Sync Interval

broadcast Ranging
Time since last received Sync
message before synchronization is
considered lost
600 msec
CM Contention Number of Retries on contention 16

Ranging Retries Ranging Requests
CM, CMTS Invited Ranging Number of Retries on inviting 16
Retries Ranging Requests
CM Request Retries Number of retries on bandwidth 16
allocation requests
CM Registration Number of retries on registration 3
Request Retries requests
CM Data Retries Number of retries on immediate data 16
transmission
CMTS CM MAP Time provided between arrival of the 200 ms
processing time last bit of a MAP at a CM and
effectiveness of that MAP
CMTS CM Ranging Minimum time allowed for a CM 1 msec
Response following receipt of a ranging
processing time response before it is expected to
reply to an invited ranging request
CMTS CM Configuration The maximum time allowed for a 3 minutes
CM, following receipt of a
configuration file, to send a
Registration Request to a CMTS.
CM T1 Wait for UCD timeout 5 * UCD
interval
maximum
value
CM T2 Wait for broadcast ranging timeout 5 * ranging
interval
CM T3 Wait for ranging response 50 msec 200 msec 200 msec
CM T4 Wait for unicast ranging opportunity. 30 sec 35 sec
If the pending-till-complete field was
used earlier by this modem, then the
value of that field must be added to
this interval.
CMTS T5 Wait for Upstream Channel Change 2 sec
response
CM T6 Wait for registration response 3 sec
CM, CMTS Mini-slot size Size of mini-slot for upstream 32 symbol times
transmission. Must be a power of 2
(in units of the Timebase Tick)
CM, CMTS Timebase Tick System timing unit 6.25 msec

170
TOSHIBA
DOCSIS Error Codes & Messages

Error Code Error Message
T00.0 SYNC Timing Synchronization
T01.0 Failed to acquire QAM/QPSK symbol timing.
T02.0 Failed to acquire Forward Error Correction (FEC) framing.
T02.1 Acquired FEC framing. Failed to acquire MPEG2 Sync.
T03.0 Failed to acquire MAC framing.
T04.0 Failed to Receive MAC SYNC frame within time-out period.
T05.0 Loss of Sync. (Missed 5 in a row, after having SYNC'd at one time)
U00.0 UCD Upstream Channel Descriptor
U01.0 No UCD's Received. Time-out.
U02.0 UCD invalid or channel unusable.
U03.0 UCD valid, BUT no SYNC received. Time-out.
U04.0 UCD, & SYNC valid, NO MAPS for this Channel.
U05.0 UCD received with invalid or out of order Configuration Change Count.
U06.0 Upstream Channel wide parameters not set before Burst Descriptors
M00.0 MAP Upstream Bandwidth Allocation
M01.0 A transmit opportunity was missed because the MAP arrived too late.
R00.0 RNG-REQ Ranging Request
R01.0 NO Maintenance Broadcasts for Ranging opportunities Received T2 time-out.
R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance
opportunities received. T4 time-out.
R101.0 No Ranging Requests received from POLLED CM (CMTS generated polls)
R102.0 Retries exhausted for polled CM (report MAC address). After 16 R101.0 errors.
R103.0 Unable to Successfully Range CM (report MAC address) Retries Exhausted. Note: this is
different from R102.0 in that it was able to try, i.e. got REQ's but failed to Range properly.
R104.0 Failed to receive Periodic RNG-REQ from modem (SID X), timing-out SID.
R00.0 RNG-RSP Ranging Response
R02.0 No Ranging Response received, T3 time-out
R03.0 Ranging Request Retries exhausted.
R05.0 Started Unicast Maintenance Ranging no Response received. T3 time-out.
R06.0 Unicast Maintenance Ranging attempted. No Response. Retries exhausted.
R07.0 Unicast Ranging Received Abort Response. Re-initializing MAC.

171
TOSHIBA

I00.0 REG-REQ Registra tion Request
I04.0 Service not available. Reason: Other.
I04.1 Service not available. Reason: Unrecognized configuration setting.
I04.2 Service not available. Reason: Temporarily unavailable.
I04.3 Service not available. Reason: Permanent.
I101.0 Invalid MAC header.
I102.0 Invalid SID, not in use.
I103.0 Required Type/Length/Value (TLV's) out of order.
I104.0 Required Type/Length/Value (TLV's) not present.
I105.0 Downstream Frequency format invalid.
I105.1 Downstream Frequency not in use.
I105.2 Downstream Frequency invalid, not a multiple of 62500Hz.
I106.0 Upstream Channel invalid, unassigned.
I106.1 Upstream Channel Change followed with (RE-) Registration REQ.
I107.0 Upstream Channel overloaded.
I108.0 Network Access configuration has invalid parameter.
I109.0 Class of Service configuration is invalid.
I110.0 Class of Service ID unsupported.
I111.0 Class of Service ID invalid or out of range.
I112.0 Max Downstream Bit Rate configuration is invalid format.
I112.1 Max Downstream Bit Rate configuration setting is unsupported.
I113.0 Max Upstream Bit Rate configuration setting invalid format.
I113.1 Max Upstream Bit Rate configuration setting unsupported.
I114.0 Upstream Priority configuration invalid format.
I114.1 Upstream Priority configuration setting out of range.
I115.0 Guaranteed Min Upstream Channel Bit Rate configuration setting invalid format.
I115.1 Guaranteed Min Upstream Channel Bit Rate configuration setting exceeds Max Up Stream Bit
Rate.
I115.2 Guaranteed Min Upstream Channel Bit Rate configuration setting out of range.
I116.0 Max Upstream Channel Transmit Burst configuration setting invalid format.

172
TOSHIBA

I116.1 Max Upstream Channel Transmit Burst configuration setting out of range.
I117.0 Modem Capabilities configuration setting invalid format.
I117.1 Modem Capabilities configuration setting.
I00.0 REG-RSP Registration Response
I01.0 Registration RSP invalid format or not recognized
I02.0 Registration RSP not received.
I03.0 Registration RSP with bad SID.
C00.0 UCC-REQ Upstream Channel Change Request
C01.0 UCC-REQ received with invalid or out of range US channel ID.
C02.0 UCC-REQ received unable to send UCC-RSP, no TX opportunity.
C100.0 UCC-RSP Upstream Channel Change Response
C101.0 UCC-RSP not received on previous channel ID.
C102.0 UCC-RSP received with invalid channel ID.
C103.0 UCC-RSP received with invalid channel ID on new channel.
D00.0 DHCP CM Net Configuration download and Time of Day
D01.0 Discover sent no Offer received, No available DHCP Server.
D02.0 Request sent, no Response.
D03.0 Requested Info not supported.
D03.1 DHCP response doesn't contain ALL the valid fields as describe in the RF spec.
D04.0 Time of Day, none set or invalid data.
D04.1 Time of Day Request sent no Response received
D04.2 Time of Day Response received but invalid data/format.
D05.0 TFTP Request sent, No Response/No Server.
D06.0 TFTP Request Failed, configuration file NOT FOUND.
D07.0 TFTP Failed, OUT OF ORDER packets.
D08.0 TFTP complete, but failed Integrity Check (MIC).
B00.0 Baseline Privacy
B01.0 Auth. Reject, Auth. Invalid; Unauthorized CM
B02.0 Auth. Reject, Key Reject; Unauthorized SID
B03.0 Auth. Invalid; Unsolicited
B04.0 Auth. Invalid, TEK Invalid; Invalid Key Sequence Number
B05.0 Auth. Invalid; Message (Key Request) authentication failure

173
TOSHIBA
DOCSIS v1.1
• DOCSIS 1.1 is a revision of the DOCSIS 1.0 Specification.
– The major changes and extensions are intended to support
enhanced Quality of Service (QoS). The major driver for these
changes is the Packet Cable initiative.
• QoS Extensions
• Fragmentation
• Baseline Privacy Enhancements (Authentication/Digital Certificates)
• IGMP (Internet Group Management Protocol) requirements
• DOCSIS 1.1 does not impact the DOCSIS 1.0 physical
layer. The DOCSIS 1.1 enhancements involve
functionality above the physical layer, particularly at the
DOCSIS Medium Access Control (MAC) layer.

174
TOSHIBA
Packet Classification & Service

Flow Identification
• The principal mechanism for providing enhanced QoS is to
classify packets traversing the RF-MAC interface into
Service Flow
• A Service Flow is a unidirectional flow of packets that is
provided a particular Quality of Service
• The classifier can examine the LLC header of the packets,
the IP/TCP/UDP header of the packet or some combination
of the two.

175
TOSHIBA
Scheduling Services
• Scheduling services are designed to improve the
efficiency of the poll/grant process
– Unsolicited Grant Service (UGS)
– Real-Time Polling Service (rtPS)
– Unsolicited Grant Service with Activity Detection
– Non Real-Time Polling Service
– Best Effort Service
– Other services
• Such as Committed Information Rate (CIR)

176
TOSHIBA
Classification (MAC Layer)

CM
Upstream MAC Mgnt.

Service Flows Msgs
Primary SID
SID 2
Upstream Upstream
… Classifier
SID n

177
TOSHIBA
Packet Cable
• Set of specifications created by CableLabs® to support the deployment
of voice-over-IP (VoIP) services
• Packet Cable uses DOCSIS v1.1 as basic transport for the voice traffic,
since DOCSIS v1.1 provides quality-of-service (QoS) guarantee
– Voice traffic uses unsolicited grant service (UGS)
• It provides support to all telephone class features and multiple rate
codes
– Features such as Caller ID, Call Waiting, Call Forwarding, etc.
– Codecs such as G.711 (64Kbps), G.728 (16Kbps) and G.729a/e (8Kbps)
• Packet Cable allows a very cost effective deployment for telephone
services
– Share existing DOCSIS infrastructure with data services

178
TOSHIBA
Packet Cable Overview
RF RF
CM + MTA CMTS Network CMTS CM + MTA
To PSTN
Provisioning
PSTN
(DOCSIS & Call Agent
Interface
Packet Cable)

179
TOSHIBA
Packet Cable Architecture
MTA - Multimedia CMS SS7

Terminal Adapter
CM - Cable Modem
RKS SG Network
CMS - Call Management CA GC MGC
Server
CA - Call Agent
GC - Gate Controller
MGC - Media Gateway
Controller MTA/CM
SG - Signaling Gateway
CMTS - Cable Modem
Termination System MTA/CM
CMTS Media Class 5

MTA/CM
Gateway Switch
MTA/CM
MTA/CM
Announcement Server

180
TOSHIBA
Packet Cable 1.0

• Commercial Products by early 2001
• Features
– Single Domain
• Local On-Net calls
• On-Net to PSTN calls
– Network Call Signalling (NCS)
• Call is controlled by the Call Agent
• Light software on the MTA (Multimedia Terminal Adapter) for rapid
deployment - based on MGCP - Media Gateway Control Protocol)
• Provisioned Quality of Service (pre-defined)
– Subscriber Features
• Minimum 2 lines
• Call Waiting, Forwarding, Collect, Credit Card, Call Blocking, etc.

181
TOSHIBA
Packet Cable 1.1

• Features
– Single Domain (same as PC 1.0)
– Network Call Signalling (NCS) - same as PC 1.0
– Client-based Signalling (Distributed Call Signalling - DCS)
• Call is controlled by MTA
• Complex software on the MTA for supporting of advanced services - based on
SIP - Session Initialization Protocol
• Dynamic Quality of Service (extra support of on the CMTS)
• Primary Line Support
• Enhanced Privacy (IP Address Privacy)

182
TOSHIBA
Packet Cable 1.2

• Features
– Multiple Domains
• Local On-Net calls
• On-Net to PSTN calls
• Long haul On-Net calls (across different MSO’s)
– Standardized MCU (Multipoint Control Unit) Interfaces
• Multi-way Calling using MCU (conference calling and 3 way calling)

183
TOSHIBA
Packet Cable Timeline
PC 1.0 Specs.
PC 1.0 Interop. PC 1.0 Qualif.
PC 1.1 Specs.
PC 1.1 Interop.
PC 1.2 Specs.
PC 1.2 Interop.
1998 1999 2000 2001

184
TOSHIBA
Review Questions III

• List the basic steps to install a cable modem.
• Describe the states of the Cable LED.
• Which modules are available on the Installation and
Testing Wizard?
• Which action should be taken when No Downstream
condition is detected?
• Which action should be taken when the PC LED is off?
• List the operations performed by a cable modem since it is
powered on until achieve operational state.

185
TOSHIBA

• Describe the operation modes of the Advance Diagnostics
program.
• List the different view windows available on the Advance
Diagnostics program
• Where in the Advance Diagnostics can be found the cable
modem hardware and software version?
• If you want to find out the rate limiting used in a cable
modem, which view window of the Advance Diagnostics
can be used?
• List the information available on the CMTS panel of the
Advance Diagnostics.

186
TOSHIBA

• List the Options/Tools available as part of the Advance
Diagnostics program.
• What are the basic entities on the SNMP?
• What is MIB?
• List the possible actions on the SNMP.
• Describe the procedure to connect to the cable modem
Serial Diagnostic Port.
• List (five) commands of the Serial Diagnostic Port.
• What is the Maximum Ranging Interval allowed?
• Define T3 time-out.

187
TOSHIBA
Hands-on
• Configuration
– CMTS, provisioning and cable modem
• Physical Layer
– RF signals, noise and interference
• Networking & Performance
• Management

188
TOSHIBA
TAIS LAB Cable Modem Test System
Sun Server
Hub/Switch Cisco CMTS Cable Modem Client PC
WinNT Server
Sun Server NT Server Cisco(e0/0) Cisco(c2/0) Cable Modem ClientPC
8:0:20:7f:e9:21 00:a0:c9:55:92:b 00:50:54:68:b0:00 00:50:54:68:b0:38

209.80.15.61 209.80.15.60 209.80.15.62 10.0.1.252

189
TOSHIBA
Ranging Process
UpConverter H
Cisco CMTS Cable Modem Client PC
L
192.168.100.1 192.168.100.2
Down s t r ea Down s t r ea Up s t r ea m Up s t r ea m Rem a r k

m m (Dia g Tool) (Mea s u r e)
(Dia g Tool) (Mea s u r e)
Ch a n n el ID
Frequency
Mod u la t ion
Power level
C/ N

190
TOSHIBA
Registration Process
Sun Server
Hub/Switch Cisco CMTS Cable Modem Client PC
Dia g Tool Rem a r k
WinNT Server DHCP S er ver
TFTP Server
Tim e S er ver
CMTS (Ca b le I/ F)
Ca lb e Mod em
Clien t PC
Con fig file

191
TOSHIBA
Carrier/Noise Ratio
Noise Generator Step ATT
UpConverter H
L
Ca r eer to Collected Un collecta b le Rem a r k

Nois e E r r or E r r or
2 3 .5 d B
2 4 .5 d B

192
TOSHIBA
Continuous Wave (CW) Interference
Signal Generator
UpConverter H
L
Ca r eer t o Collect ed Un collect a b le Rem a r k

Nois e E r r or E r r or
2 3 .5 d B
2 4 .5 d B

193
TOSHIBA
If trouble happened ?
• Diag Tool log
– Save Report
• Cable Modem LED
– Cable LED : Off, Slow Blinking, Fast Blinking
• Config file
– Try to use sample configuration file
• CMTS log
– #Show cable modem
– #Show tech-support
• Check MSO Support Page
– http://www.toshiba.com/taisnpdc/downloads

194
TOSHIBA
Performance Comparison by SmartBit
10BASE-T SmartBit Throughput(Mbps)

SmartBit
100BASE-Tx 10
Throughput (Mbps)
CMTS 8
Cable Modem
Cisco uBR7223 RF
6 64Byte
64QAM,QPSK(1.6MHz)
4 1518Byte
Vendor Throughput (PPS) 2

64Byte 1518Byte
0
Toshiba 13206 800
3COM 1500 787 Toshiba 3COM Philips Com21
Philips 2300 600 Vendor
Com21 14500 810

195
TOSHIBA
SNMP Management
1. Specify the IP address of the cable modem.
2. Specify the Community Name if available.

3. Select the MIB Object ID
( Go up and down MIB Object ID)
4. Click “Describe” to see the definition of MIB

< Read the values>
5. Click “Start Query” to see the values
< write the values>
6. Specify the MIB instance
7. Set the SNMP Set Value
8. Click “Set” to set the new value

196
TOSHIBA
Cable Modem DHCP Parameters
1. IP address to used by the CM (yiaddr)
2. IP address of TFTP server (siaddr)
3. IP address of relay agent (giaddr)
- if the DHCP server is on a different network -
4. The name of the CM configuration file (file)
5. The subnet mask to be used by CM (Subnet Mask,option1)
6. The time offset of the CM from UCT (Time Offset,option2)
- UCT:Universal Coordinated Time -
7. A list of addresses of one or more routers to be used for forwarding
CM- originated IP traffic (Router Option,option3)
8. A list of time-servers from which the current time may be
obtained(Time Server Option,option4)
9. A list of SYSLOG servers to which logging information may be
sent(Log Server Option,option 7)

197
TOSHIBA
DHCP configuration Example (Join)
[dhcpcap (Solaris2.6) see www.join.com for more information ]
modemhome:\
:nw=192.168.1.0:\ # Network or subnet Address
:gw=192.168.1.252:\ # Routers option
:sm=255.255.255.0:\ # Subnet Mask
:ba=192.168.1.255:\ # Broadcast Address
:ts=209.80.15.61:\ # Time Server Address
:nt=209.80.15.61:\ # Boot File Server Address (TFTP Server)
:lg=209.80.15.61:\ # Log Server Address
:cm=209.80.15.61:\ #
:to=32400:\ #
:bf="modem.cfg":\ # Boot file (Cable modem Configuration file name)
:sa=209.80.15.61:\ # Server Address
:dn=npdc.tais.com:\ # Domain name
:hd="/tftpboot":\ #Home directory
:td="/tftpboot":\ #TFTP root directory
:ds=204.182.160.1: # DNS Server Address
198
TOSHIBA
uBR7200 configuration Example
[uBR configuration example]
ubr7223#show running-conf
interface FastEthernet0/0
ip address 209.80.15.61 255.255.255.0
!
interface Cable2/0
ip address 192.168.1.252 255.255.255.0
no keepalive
cable helper-address 209.80.15.61
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream frequency 633000000
cable upstream 0 frequency 7008000
cable upstream 0 channel-width 3200000
cable upstream 0 minislot-size 4
no cable upstream 0 shutdown
199
TOSHIBA
Server network configuration Example
[Server network configuration example]
# ifconfig -a
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 209.80.15.61 netmask ffffff00 broadcast 209.80.15.255
ether 8:0:20:7f:e9:21
# netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
209.80.15.0 209.80.15.61 U 3 169 hme0
224.0.0.0 209.80.15.61 U 3 0 hme0
default 209.80.15.62 UG 0 7824
127.0.0.1 127.0.0.1 UH 0 96909 lo0

200
TOSHIBA
“ show cable modem “ command
[“show cable modem” command on uBR7200 ]
ubr#show cable modem
Interface SID Online Timing Receive QoS IP address MAC address
State Offset Power
Cable5/0/U0 1 offline 2248 0.25 2 192.168.1.133 0090.8330.01c8
Cable5/0/U0 2 offline 2289 -0.00 2 192.168.1.134 0090.8330.0245
Cable5/0/U0 3 offline 2282 -0.00 2 192.168.1.130 0090.8330.0247
Cable5/0/U0 4 offline 2257 0.25 2 192.168.1.136 0090.8330.0246
Cable5/0/U0 5 offline 2270 0.50 2 192.168.1.129 0090.8330.0248
Cable5/0/U0 6 online 2234 0.25 4 192.168.1.131 0090.8330.01eb
Cable5/0/U0 7 online 2249 -0.25 4 192.168.1.132 0090.8330.021b
Cable5/0/U0 8 offline 2265 -1.00 2 192.168.1.138 0090.8330.0249
Cable5/0/U0 9 offline 2256 -0.00 2 192.168.1.139 0090.8330.0174
Cable5/0/U0 10 offline 2262 -0.00 2 192.168.1.140 0090.8330.0266
Cable5/0/U0 11 init(r2) 2259 -11.00 2 0.0.0.0 0090.8330.021c

201
TOSHIBA
“ debug ip udp “ command on uBR7200
[CM Provisioning success log ]
ubr7223#debug ip udp
UDP packet debugging is on
ubr7223#
ubr7223#
05:47:25: UDP: rcvd src=0.0.0.0(68), dst=255.255.255.255(67), length=556
05:47:25: BOOTP: opcode 1 from host 0.0.0.0 on Cable2/0, 0 secs, 0 hops
05:47:25: UDP: forwarded broadcast 67 from 192.168.1.252 to 209.80.15.61 on FastEthernet0/0
05:47:25: BOOTP: opcode 2 from host 209.80.15.61 on FastEthernet0/0, 0 secs, 0 hops
05:47:25: BOOTP: Forwarding response 209.80.15.61 -> 192.168.1.66 (Cable2/0)
05:47:25: BOOTP: opcode 1 from host 0.0.0.0 on Cable2/0, 0 secs, 0 hops
05:47:25: UDP: forwarded broadcast 67 from 192.168.1.252 to 209.80.15.61 on FastEthernet0/0
05:47:25: BOOTP: opcode 2 from host 209.80.15.61 on FastEthernet0/0, 0 secs, 0 hops
05:47:25: BOOTP: Forwarding response 209.80.15.61 -> 192.168.1.66 (Cable2/0)

202
TOSHIBA
“ snoop “ command on Solaris2.6
[CM Provisioning success log ]
# snoop -d hme0
192.168.1.254 -> demo-server1 DHCP/BOOTP BOOTREQUEST
server -> 192.168.1.131 IP D=192.168.1.131 S=209.80.15.61 LEN=28,ID=41701
? -> * ETHER Type=9000 (Loopback), size = 60 bytes
server -> 192.168.1.254 DHCP/BOOTP BOOTREPLY
192.168.1.254 -> demo-server1 DHCP/BOOTP BOOTREQUEST
server -> 192.168.1.254 DHCP/BOOTP BOOTREPLY
192.168.1.131 -> demo-server1 TIME C port=1024
server -> 192.168.1.131 TIME R port=1024
192.168.1.131 -> demo-server1 TFTP Read "modem.cfg" (octet)
server -> 192.168.1.131 TFTP Data block 1 (90 bytes) (last block)
192.168.1.131 -> demo-server1 TFTP Ack block 1

203
TOSHIBA
Spectrum Analyzer Setup

• Forward (Downstream)
– Continuos QAM Carrier
– Set Analyzer:
• Center Carrier Frequency
• Power within -15dBmV to +15dBmV (normal operation)
• Normal Sweep

204
TOSHIBA
Spectrum Analyzer Setup (cont’d)

• Reverse (Upstream)
– Burst QPSK(or QAM) Carrier
– Set Analyzer:
• Center Carrier Frequency
• Power within +8dBmV to +58dBmV (normal operation)
• Very Slow Sweep (may require Max. Hold or Zero Span)

DOCSIS Training - Admin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DOCSIS Training - Admin

Uploaded by

Copyright:

Available Formats

1

DOCSIS Cable Modem Training

Network Products Division

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

DOCSIS Services Goals

Transparent IP Traffic Through the System

Toshiba America Information Systems Confidential and Proprietary

DOCSIS Reference Architecture

Operations Support System

Toshiba America Information Systems Confidential and Proprietary

Designa tion Title

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

DOCSIS Components (cont’d)

Toshiba America Information Systems Confidential and Proprietary

DOCSIS Components (cont’d)

Toshiba America Information Systems Confidential and Proprietary

DOCSIS Protocol Stack

Transport Layer UDP

Network Layer IP, ICMP

Media Access Control

Transmission Conv ergence

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Cable Network CMCI

Toshiba America Information Systems Confidential and Proprietary

CMTS Forwarding Rules

CPE MAC Address Acquisition

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

CM Forwarding Rules (cont’d)

Toshiba America Information Systems Confidential and Proprietary

4 - Toshiba DOCSIS Cable Modem

Toshiba America Information Systems Confidential and Proprietary

Components - DOCSIS v1.0

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Front View POWER

Toshiba America Information Systems Confidential and Proprietary

Toshiba America Information Systems Confidential and Proprietary

Features of Cable Modem

Toshiba America Information Systems Confidential and Proprietary

Features of Cable Modem (cont’d)

Toshiba America Information Systems Confidential and Proprietary

Cable Modem Specs.

 Physical speed: 30Mbps (64QAM) / 43Mbps (256QAM)

Toshiba America Information Systems Confidential and Proprietary

Cable Modem Specs.

 Physical speed: 320, 640, 1280, 2560 ,5120 Kbps (QPSK)

Toshiba America Information Systems Confidential and Proprietary

Cable Modem Specs.

Toshiba America Information Systems Confidential and Proprietary

Cable Modem Specs.

 PC interface: IEEE802.3/Ethernet 10BASE-T