Security

 View Only
Expand all | Collapse all

Query on NAD Device renaming using XML API in 6.12

This thread has been viewed 5 times
  • 1.  Query on NAD Device renaming using XML API in 6.12

    Posted May 27, 2025 05:57 AM

    Until CPPM 6.11.x the device renaming using XML was working fine and from version 6.12.x when trying to update name for the IP already existing throws error stating device ip already exists.
    XML payload:

     <NadClients>
       <NadClient description="test" name="Nad Devices update1" coaPort="3799" radsecEnabled="false" coaCapable="true" vendorName="Aruba" tacacsSecret="" radiusSecret="xxxx" ipAddress="192.168.1.10"/>

      </NadClients>
    Response:
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <TipsApiResponse xmlns="http://www.avendasys.com/tipsapiDefs/1.0">
        <TipsHeader exportTime="Tue May 27 02:45:32 CDT 2025" version="6.12"/>
        <StatusCode>Failure</StatusCode>
        <TipsApiError>
            <ErrorCode>InvalidXml</ErrorCode>
            <Message>Device with IP address 192.168.1.10 already exists</Message>
        </TipsApiError>
    </TipsApiResponse>

    how to rename using XML api for NAD CPPM version 6.12 and above



  • 2.  RE: Query on NAD Device renaming using XML API in 6.12

    Posted May 30, 2025 09:51 AM

    I'd recommend to use the REST API instead of the deprecated and legacy XML API.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------