Notes 29 09
Notes 29 09
IPv4
DHCP Option 6 -> Length = 4 byte or 8 byte(opt) (IPv4)
Primary DNS IP
(opt)Secondary DNS IP.
IPv6
DHCP Option 23 -> Length = 16 byte or 32 bytes(opt) (Ipv6)
Primary DNS IP
(opt)Secondary DNS IP
Open: -
1. Without Additional trust anchor support, there is no need of multiple CMP server
to be supported.??
===========History=================================================
how to differentiate between Primary & Secondary CMP Server is there any parameter
required to mark it as primary or secondary
Parameter list should be identical for split A & split B.
CMP server configuration can be global for all RUs or each RU can have specific CMP
Server detail.
But not a mix and match of above.
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
Is following configuration is allowed or not ?
RU1 -- Prim (CMP1)
--Secon (CMP2)
RU2 -- Prim(CMP2)
-- Secon(CMP1)
CMPServer Manadatory parameters should be defined under a seprate MOC and this MOC
instance can be referenced by RU
as a Primary or Secondary CMP Server.(RMOD-Primary Server DN / RMOD-Secondary
Server DN)
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
For Global CMP Server Deployment :- Max two instances of CMP server MO should be
allowed. kind of CMPFH/CMPSERVER-1 or CMPFH/CMPSERVER-2 . Then in NIDD
configuration parameter detail CMPSERV-1 should be as Primary CMP Server and
CMPSERVER-2 should be as Secondary CMP Server
For Per RU CMP Server Deployment :- It can be more than two CMP server MO (linked
through RMOD-Primary Server DN/RMOD-Secondary Server DN)
******************************28th September*****************************
1)New Parameter to indicate position of CMPSERVER ..whether it can be behind DU or
RU can directly reach CMP server. This will decide upon requirement of bypass
policy and firewall/routing/natting rules at DU.
2)To be discussed New Parameter to indicate position of DNS Server -- -> in case of
external DNS server-- It can be reached by DU from Backhaul and RU from Fronthaul.
So in this scenerio firwall rule update is not required at DU.
To be checked with PDM -- -> Single location for CMP/CRL/DNS , so that we can have
only two options 1. CMP/DNS/CRL behind DU 2.CMP/DNS/CRL between DU & RU. In this
case , there can be single switch to toggle between these two option.
it will simplyfy solution .
RUCMPMAP-1 to 96
(if No NULL, this means DNS not required, PDL rule should ensure that in FQDN
case, DNS is always set)
This parameter is not needed.
-> 3. CRL Server DN --> MNL/CERTH/CRL
-> RMODDN -->
-> NAT --> Yes OR No.
NATing rule for RU initiated CMP traffic and Response from CMP Server:
28-09-2023:
IPv4
DHCP Option 6 -> Length = 4 byte or 8 byte(opt) (IPv4)
Primary DNS IP
(opt)Secondary DNS IP.
IPv6
DHCP Option 23 -> Length = 16 byte or 32 bytes(opt) (Ipv6)
Primary DNS IP
(opt)Secondary DNS IP
Open: -
4. Without Additional trust anchor support, there is no need of multiple CMP server
to be supported.??