PTP is not something we use. Although by looking at the cli documentation for CX switches. A profile needs to be created first which will enable it globally, then its enabled on an interface.
I did not see the ptp config on the "switch port profile" configs other then LAG. I did see it in the "interface ethernet" config. Generally I would suggest to get a working template or sample and then compare the running config in switch to a known working switch.
I was also looking for the swagger documentation but the URL's I used on CNX seem to be broken. I would probably defer to the swagger documentation over the developer as I felt it was more useful in specific examples. I am willing to help as I have used a fair amount of API's and helped others get started. We dont use our switches in central and I dont have any licensing either.
Original Message:
Sent: Jul 10, 2026 04:33 AM
From: JL-BHw358
Subject: CNX API
One simple question needs to be answered:
To existing SW Port profile (the ones which is available for "end user" through UI) how can I add:
"ptp": {
"enable": true
}
to it? If there is several steps, fine, I can do that.. Just need direction how to proceed.
If i try to inject it directly to existing config I'll get error, if I'll test to inject it into lag, success but not ideal because connecting links are not lags..
I have sold the idea of Central to customer with that it is possible to make system "client usable" by having port profiles containing all configurations needed which they can use to change port configuration from mac-authenticated port to ptp enabled access port or other kind of static port config and back without need to run this'n'that script here'n'there and do some river dance between.
------------------------------
Regards
Jori Luoto / RockNET
------------------------------
Original Message:
Sent: Jul 09, 2026 12:59 PM
From: JK-90898a
Subject: CNX API
If you need help with API's or doing something along those lines. I am more then happy to help via private message. Its probably to much going back and forth to post to the forum. We are waiting for orchestration and topology to be ported over into CNX. As I have been informed to use classic due to the focus on workflow changes. I hope by the time this year the features will be supported. We are in the process of migrating around 70 branches, and the hope was not to go back to move them from classic to cnx.
PM me if you want some assistance. I am happy to provide guidance.
Original Message:
Sent: Jul 09, 2026 12:32 PM
From: JL-BHw358
Subject: CNX API
Classic central had one big advantage to cnx: Change to inject CLI data to devices through MultiEdit but there seemed to be downside too: after a while you'll might get situation where central visible configs are different than local configs in switches.. Yeah it sounds like bug but I don't have strength to open up tac case because it's so time consuming and nobody pays my salary to struggle through process.
As you can see from previous messages (plus possibly few others I have already added to forums) I have already worked with API's to add proper configs to devices and I have tried to get proper information how to use Interface Ethernet endpoint which contains the configuration elements I need to succeed but I'll get only abstract answers which gets me nowhere (sorry I'm quite frustrated about situation...)
------------------------------
Regards
Jori Luoto / RockNET
------------------------------
Original Message:
Sent: Jul 09, 2026 08:53 AM
From: JK-90898a
Subject: CNX API
CNX is being worked on for work flows. There is a fair amount of items that you need to use API's if you want features that existed with classic central. We are still some of early adopters at this time. You will need to use API most likely.
Original Message:
Sent: Jul 08, 2026 03:22 AM
From: JL-BHw358
Subject: CNX API
Hello,
Is this now case closed?
I have checked out release notes of CNX and they seems to concentrate heavily to monitoring features... Is there overall roadmap for development of CNX to see when things will have such status where there is proper amount of features available or at least there is configuration available in cnx which can be used to enable (non-existing) "do not overwrite unknown CLI configurations"-feature.
------------------------------
Regards
Jori Luoto / RockNET
------------------------------
Original Message:
Sent: Jul 03, 2026 09:46 AM
From: JL-tvd358
Subject: CNX API
Hello
Thank you for your reply but as you can notice that PTP is under LAG configuration. Yes I'll need that too but without access port "ptp enable" which is located in Interface Ethernet this feature is useless.
(Secondly to change between "LAG PTP Enabled" profile and "standard access port" profile seemed to have something weird issues while changing between non-lag and lag profile)
Why I asked about to attach this configuration to Port Profiles is that "selected bulk users" has change to make easy changes to ports when they need to do changes.
------------------------------
Regards
-Jori Luoto-
AV-IT networking
------------------------------
Original Message:
Sent: Jul 03, 2026 05:34 AM
From: DN-eac0fa
Subject: CNX API
Hi Jori,
our Central Team is working with pressure on all open GUI Elements. We have not yet the GUI for PTP in interfaces and port profiles (July26) - but we have the APIs for a long time. So Port Profiles are a summary of commands for a common port-usecase. f.E. Clientport, CameraPort, PrinterPort etc. you can configure these "Templates" everywhere in the "hirachy". Check your Device Persona and in Interfaces -> Port Profiles you can configure them - even also in the Lib. Lib elements. (today w/o ptp).
If you had noch checked the documentation for configuration: https://developer.arubanetworks.com/new-central/docs/introduction-to-configuration-apis - https://developer.arubanetworks.com/new-central/docs/working-with-library-profiles
You will see that in the Port Profiles are also your ptp configs in the API (not yet in GUI) so you can modify them today with API.
- from Postmal Collection (See also the guide how to get and work with Postman)
Then you have a "template" with your config and the question was how to bind that on interfaces?
The GUI way on a particular switch (is the fastest way) :
f.E. Configuration:
Then your port profile config gets applied to that port and you can reuse that profile (test1) on any other switch (when the sw port profile is created at the right site level or in lib - then assigned to the right level)
But working with port profiles is optional. You can configure interface ptp settings also directly in the interface if you have just one port - this makes sense, if you have many the hirachy and port-profiles would make sense - depends on the overall goal and usecase. So like in the CLI, you have global PTP commands and interface PTP commands and you have to choose if it does make sense to configure a single switch or many.
Hope that helps
BR Dennis
------------------------------
LG Dennis
------------------------------
Original Message:
Sent: Jul 03, 2026 03:45 AM
From: JL-tvd358
Subject: CNX API
Local SE had no idea how to proceed... (Is there somebody out there to pass this question to API development and also to CNX UI development to hurry up getting ptp configurations finally available to CNX..)
I found way to create proper ptp profile to group (or device/site/etc) so this part is solved.
I'm planning to use Port Profiles to give users easy and quite solid way to change port configurations so next problem is how to enable ptp in physical port?!?
PTP configuration is in Interface Ethernet endpoint (https://xxx.api.central.arubanetworks.com/network-config/v1alpha1/ethernet-interfaces) and Sw Port Profiles (https://xxx.api.central.arubanetworks.com/network-config/v1alpha1/sw-port-profiles) has all other Port Profile data.
Interface Ethernet API manual page says:
"Supported scopes: Device. This configuration relies on Port Profile configurations (sw-profile for switches <snip>) for template-based settings"
What does this mean? As far as I have understood all library elements are "templates" more or less?!?
While port configurations are kind-of dynamic configurations and it's not possible for users to run API script every time they change port profile,
How can I add Interface Ethernet profile to Sw Port Profile?
------------------------------
Regards
-Jori Luoto-
AV-IT networking
------------------------------
Original Message:
Sent: Jun 25, 2026 08:07 AM
From: JL-tvd358
Subject: CNX API
Hello Dennis,
Thanks for reply.
Found linked page about half hour after I sent message but I have no slightest idea how to attach it to devices/groups/sites...
Dropped mail to local SE if he had idea about it.
Additional issue against API is that Device level seems to NOT have scope_id (which is mandatory in LOCAL scope) and API query needs to have integer scope_id (Got error "debugId": "0a876622e722eadf632e71d9fa2c40fa",
"errorCode": "HPE_GL_ERROR_BAD_REQUEST",
"httpStatusCode": 400,
"message": "invalid literal for int() with base 10: <SerialNumber>")
------------------------------
-Jori Luoto-
AV-IT networking
------------------------------
Original Message:
Sent: Jun 25, 2026 07:53 AM
From: DN-eac0fa
Subject: CNX API
Hi Jori,
If you search for CNX then use the API Browser at https://developer.arubanetworks.com/new-central-config/ you will see a Search button in the upper Right.
then search for ptp and you will find your APIs.
------------------------------
BR Dennis
------------------------------