Available Languages

Updated:August 6, 2025

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Huawei NCE-IP Adapter

General information

Controller name: NCE-IP Adapter

Vendor: Cisco

Controller version: R23C10

HCO version: 11.0

Adapter version: 10.0.2

Adapter release date: 28/03/2025

Use cases

· Inventory discovery - yes

· Topology discovery - yes

· Service underlay discovery (LSP, tunnels) - yes

· Service discovery - yes

· Assurance - yes

· Service provisioning – yes

· RON – no

Discovery

Inventory

Details	Support	Additional information
Device types	OptiX PTN 910E-F OptiX PTN 905E OptiX PTN 970 OptiX PTN 990 OptiX PTN 7900-12
Shelf	Yes
Cards	Yes
Ports	Yes
Fans	Yes
Power	Yes
Pluggable transceivers	Yes
Notifications	Yes
Protocol	Proprietary RESTCONF SOAP	Port Soap IDs that are used in provisioning requests
Data Model	JSON
Behavior / Limitations
· For Equipment (port, card, chassis) Model number, serial number and part number are not modeled sometimes, depending on the API response. · For the Card/ SFP removal/in, Controller is not generating any card/SFP out/in notifications, only modification is generated for which HCO will attempt a modification of the entity · The SFP count in the controller API response is mismatching with the controller UI

Topology

Details	Support	Additional information
Link layers	IP physical, IP logical, LSP(MPLS-TP)
Cross links	No
Cross domain links	No
Notifications	Yes
Protocol	Proprietary RESTCONF SOAP	LSP Soap IDs that are used in provisioning requests
Data Model	JSON
Behavior / Limitations
Tunnel Protection information and Operational status is not modeled as these values are not present in the controller API response

Service underlay discovery

Details	Support	Additional information
Link layers	Yes	E-Line, Pseudo Wires and LSPs
Cross domain links	No
Notifications	Yes
Protocol	NA
Data Model	NA

Service discovery

Details	Support	Additional information
Service types	E-Line	Packet E-Lines
Service underlay	Yes	Static Tunnels only
Cross domain services	No
Notifications	Yes
Protocol	Proprietary RESTCONF SOAP	Service Soap IDs that are used in provisioning requests
Data Model	JSON
Behavior / Limitations
· The admin-status, oper-status and service health are not modeled. · Service to Service Intent mapping fails when tagged services are created over untagged port or vice versa. It is recommended not to create such configurations. · The notification processing takes a longer time due the time taken by the controller for o To respond to the create request o Create notification generation is taking time after the create request response o The export task to get the Service end points and the Underlay tunnels information

Assurance

Details	Support	Additional information
Performance Monitoring type	Yes	PACKET_IN PACKET_OUT OCTET_IN OCTET_OUT
Resource type	Yes	R_PHYSICAL
Live performance monitoring	No
Performance Monitoring collection method	SFTP Pull

Provisioning

Service type

Creation / Deletion

Modification

Brownfield

Packet E-Line

Yes

Yes (CIR and EIR Only)

Yes

(Modification & Deletion)

Protocol

SOAP

Data Model

Behavior / Limitations

1. Since the create notification processing is taking time the discovery step time in the Service Manager App need be increased.

e.g sedo config add service-manager-app_sm-configuration_global '"{\"discovery_timeout_ms\":1200000}"' --ro-access permission/hco/service-manager-app:ro --rw-access permission/admin --rw-access permission/hco/service-manager-app:rw

2. There are no notifications generated by the controller for CIR and EIR modification, So polling interval needs to be reduced to go through the discovery step of modification flow

3. Tagged and untagged services cannot/should not be created on the same endpoints

4. QoS parameters in payload are CIR and PIR whereas CIR and EIR are used in HCO. PIR=CIR+EIR will be sent in the create and modify payloads.

5. If given the CBS and EBS values will be discarded during the creation as the controller does not expect in payload

6. If CBS and EBS values are modified the Modification will be failed with a validation error as these are not expected by the controller

Configuration

Parameter name	Description	Default value	Range
Enabled	Enable/Disable the adapter	FALSE
Logging level	The logging level at which the discovery cycle will be reported in the adapter’s log	INFO
Adapter Properties
Polling Cycle [sec]	Poll every X seconds	7200	[360:]
Service Delegation	Allows ownership of existing Services for modification and deletion	FALSE
NCE-IP Server Configuration
Host (including protocol)	Protocol and host IP of inventory server. E.g. https://10.10.10.10
Port	Port Number
Credentials	Reference to the credentials defined in ‘Credentials’ tab of the Device Manager
Timeout	Request Timeout	60
Request Retries	Number of retries before returning connection failure	3
Collection Parameters
Enable Inventory Collection	Allow Adapter to collect inventory data	FALSE
Enable Topology Collection	Allow Adapter to collect topology data	FALSE
Provisioning Configuration
Enable Service Provisioning	Allow user to provision Services from HCO	FALSE
Host (including protocol)	Protocol and host IP of provisioning server. E.g. https://10.10.10.10
Port	Port Number
Credentials	Reference to the credentials defined in ‘Credentials’ tab of the Device Manager
Timeout [sec]	Provisioning Request Timeout	60
Request Retries	Number of retries before returning connection failure	3
Notifications Configuration
Enabled	Allow adapter to listen and process change notifications from the Controller	FALSE
Log Notifications	Log notifications received	TRUE
Log Level	Log notifications when adapter logging level is equals to this value	DEBUG
Congestion Control Period Sec	Maximum time in seconds allowed between successive notifications. If no notifications are received for this period, adapter collect cycle is initiated and the events currently present in the event log are processed	5
Max Notification Wait Period Sec	The maximum wait time in seconds to initiate adapter collect cycle and process notifications when there is a continuous stream of notifications	60
Notification Silent Period Sec	Maximum elapsed time during which no notifications are received by the adapter before restarting the notification listener	120
PM Configuration
Enabled	Allow adapter to collect PM Stats	FALSE
PM Data Fetch Interval [sec]	Time interval to fetch new statistics files from controller	900
SFTP Host (including protocol)	Protocol and host IP of the filer server. E.g. sftp://10.10.10.10
Port	SFTP server Port
SFTP Path	PM Stats File Path
Credentials	Reference to the credentials defined in ‘Credentials’ tab of the Device Manager for SFTP

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)