Hi guys :
I have a question about the RCP-ID and from the CableLabs official release " CM-SP-MULPIv3.0-I21-130404.pdf ".
We see the explanation of RCP-ID ( C. 1.5.3.1 ) and summarized as below :
Type Length Value
48.1 5 Bytes 0,1,2: Organization Unique ID
Bytes 3,4: OUI-specific profile ID
Here with an example of RCP-ID: rcp-id 00 10 18 80 61
Anyone know what the organization meaning for the first three bytes " 00 10 18 " and also what OUI-specific profile for last two bytes " 80 61 " ?
Or, Do you guys has the corresponding table for these Organization - OUI mapping ?
Looking for your reply !
Best Regards
Maclang
Hi Hinzoo,
Appreciated your help !!
And any further information about the RCP -ID of last two bytes as " 80 61 " ?
Is that mean any hex code transfer to decimal or else ?
BRs
Mac
Yes I agree with you, information on this topic is pretty scarce.
Here is what I know :
The CableLabs MULPI doc talks about about this topic (note the doc is up to v27 now, rather than v21 you quote above)
Firstly read through the information in section 8.2.4
There are some "standard RCP", which are shown in Annex E. These are usually sufficient for most applications, particularly for newer modems which are full spectrum tuner.
Cable modem manufacturers can also create their own RCP. Some vendors I have seen :
00 10 00 = CableLabs standard RCP
00 00 CA = Arris
00 50 F1 = TI / Intel
My guess is the 00 10 18 you quote is probably Broadcom
For the profile IDs, there doesn't seem to be much of a pattern there, the vendor will just seem to use a pattern of their own choice
If you want to sniff out a bit more information, you can jump on the CMTS and turn on some debugs :
"debug cable mac-address xxxx.xxxx.xxxx"
"debug cable tlv"
will show the RCP offered by your modem eg
SLOT 6/0: Jul 22 14:30:58 AEST: Found Modem Capabilities TLV
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 10 00 00 08
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 10 00 00 05
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 10 00 00 04
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 00 CA 00 04
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 10 00 00 03
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 50 F1 0D 06
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 50 F1 0D 07
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 50 F1 0D 08
SLOT 6/0: Jul 22 14:30:58 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:30:58 AEST: RCP ID:
SLOT 6/0: Jul 22 14:30:58 AEST: 0x0000: 00 10 00 00 02
If you activate "cable rcp-control verbose" in your cable interface, the debug will give a lot more detail about each profile. In fact so much detail the debug output unfortunately gets truncated. eg :
SLOT 6/0: Jul 22 14:37:33 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:37:33 AEST: RCP ID:
SLOT 6/0: Jul 22 14:37:33 AEST: 0x0000: 00 10 00 00 08
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Name : CLAB-6M-008
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Frequency Spacing : 6 Mhz
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Module Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Adjacent Channels: 10
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Minumum center Frequency: 111000000
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Maximum center Frequency: 999000000
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Primary Capable: 1
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 4
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 4
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 5
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 5
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 6
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 6
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 7
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 7
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 8
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:37:33 AEST: RCP ID:
SLOT 6/0: Jul 22 14:37:33 AEST: 0x0000: 00 10 00 00 05
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Name : CLAB-6M-005
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Frequency Spacing : 6 Mhz
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Module Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Adjacent Channels: 10
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Minumum center Frequency: 111000000
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Maximum center Frequency: 999000000
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Primary Capable: 1
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 4
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:37:33 AEST: RCP ID:
SLOT 6/0: Jul 22 14:37:33 AEST: 0x0000: 00 10 00 00 04
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Name : CLAB-6M-004
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Frequency Spacing : 6 Mhz
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Module Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Module Adjacent Channels: 10
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 0
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Primary Capable: 1
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 1
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 2
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Receive Channel Information TLV - 3
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Index: 4
SLOT 6/0: Jul 22 14:37:33 AEST: RCP Channel Connectivity: 0x40
SLOT 6/0: Jul 22 14:37:33 AEST: Found RCP TLV
SLOT 6/0: Jul 22 14:37:33 AEST: RCP ID:
SLOT 6/0: Jul 22 14:37:33 AEST: Found CM Reinit Reason TLV 57
The CMTS will auto-generate some RCC for each MAC domain. And you can also see any which you have manually assigned eg
"show cable mac-domain cable 5/0/0 rcc"
RCC-ID RCP RCs MD-DS-SG CMs WB/RCC-TMPL
1 00 00 00 00 00 8 0 103 WB (Wi5/0/0:0)
2 00 00 00 00 00 4 0 4 WB (Wi5/0/0:1)
You can view more detail for them with "show cable modem mac-domain cable 5/0/0 rcc "
RCC ID : 1
RCP : 00 00 00 00 00
Created Via : Wideband - Wi5/0/0:0
Receive Channels : 8
Receive Channel : 1
Center Frequency : 303000000
Primary Capability : YES
Receive Channel : 2
Center Frequency : 309000000
Primary Capability : YES
Receive Channel : 3
Center Frequency : 315000000
Primary Capability : YES
Receive Channel : 4
Center Frequency : 321000000
Primary Capability : YES
Receive Channel : 5
Center Frequency : 327000000
Primary Capability : NO
Receive Channel : 6
Center Frequency : 333000000
Primary Capability : NO
Receive Channel : 7
Center Frequency : 339000000
Primary Capability : NO
Receive Channel : 8
Center Frequency : 345000000
Primary Capability : NO
Receive Modules : 1
Receive Module : 1
First Frequency : 303000000
You can see which RCP was selected in the "show cable modem xxxx.xxxx.xxxx verbose" eg
RCP Index : 3
RCP ID : 00 10 00 00 08
So in summary, the RCP stuff used to be pretty important when modems had limited tuner capabilities. But the more modern gear has removed all these limitations and you shouldn't need to manipulate/force this stuff any more if you follow these rules (Cablelabs standard RCP) :
* 4x4 modems, keep the DS channels contiguous
* 8x4 modems, keep the DS channels within a 60MHz window
* 16 and 24 and 32 channel modems, you probably dont need to follow any rules
Hope that helps!
https://www.google.pl/search?q=001018+oui&ie=utf-8&oe=utf-8&gws_rd=cr&ei...
should help. Maybe U can check online?