Modeled Device Manager API

REST Resources

/api/space/device-management/modeled-device-management/create-connection-profile

The following operations are supported on this resource:

POST - Create Static Connection Profile
POST - Create DHCP Connection Profile
POST - Create PPPoE Connection Profile
POST - Create PPPoA Connection Profile

POST /modeled-device-management/create-connection-profile

Version 1

Create Static Connection Profile.

Sample Usage

POST /modeled-device-management/create-connection-profile

Content-Type Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-static-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-static-request+json;version=1;charset=UTF-8

Accept Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-static-response+xml;version=1
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-static-response+json;version=1

XML
JSON

Sample Input XML:

<create-connection-profile-static-request>

     	 <name>Connection_Profile_Static</name>

     	 <description>Connetion Profile Using static</description>

     	 <interface-type>ETHERNET</interface-type>

     	 <interface-name>ge-0/0/0</interface-name>

     	 <ip-type>IPv4</ip-type>

     	 <use-nat>false</use-nat>

 </create-connection-profile-static-request>

Sample Output XML:

<create-connection-profile-static-response uri="/api/space/device-management/modeled-device-management/create-connection-profile">

     	 <connection-profile

           	href="/api/space/device-management/modeled-device-management/connection-profiles/2686976" 

           	<id>2686976</id>

           	<name>Connection_Profile_Static</name>

     	 </connection-profile>

 </create-connection-profile-static-response>

Sample Input JSON:

{

   	"create-connection-profile-static-request" : {

     	"name" : "Connection_Profile_Static" ,

     	"interface-type" : "ETHERNET" ,

     	"interface-name" : "ge-0/0/0" ,

     	"ip-type" : "IPv4" ,

     	"use-nat" : "false" ,

   	}

 }

Sample Output JSON:

{

   	"create-connection-profile-static-response" : {

     	"@uri" : "/api/space/device-management/modeled-device-management/create-connection-profile"	,

     	"connection-profile" : {

       	"@href" :	"/api/space/device-management/modeled-device-management/connection-profiles/2686976"	,

       	"id" : 2686976 ,

       	"name" : "Connection_Profile_Static"

     	}

   	}

 }

Access Control

The following capabilities are required to access this API: CreateConnectionProfiles

POST /modeled-device-management/create-connection-profile

Version 1

Create DHCP Connection Profile.

Sample Usage

POST /modeled-device-management/create-connection-profile

Content-Type Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-dhcp-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-dhcp-request+json;version=1;charset=UTF-8

Accept Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-dhcp-response+xml;version=1
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-dhcp-response+json;version=1

XML
JSON

Sample Input XML:

<create-connection-profile-dhcp-request>

     	 <name>Connection_Profile_DHCP</name>

     	 <description>Connection Profile Using DHCP</description>

     	 <interface-type>ETHERNET</interface-type>

     	 <interface-name>ge-0/0/0</interface-name>

     	 <ip-type>Ipv4</ip-type>

     	 <use-nat>false</use-nat>

     	 <dhcp-retransmission-attempt>4</dhcp-retransmission-attempt>

     	 <dhcp-retransmission-interval>4</dhcp-retransmission-interval>

     	 <dhcp-server-address>1.1.1.1</dhcp-server-address>

     	 <dhcp-update-server>false</dhcp-update-server>

     	 <dhcp-default-lease>false</dhcp-default-lease>

     	 <dhcp-lease-never-expires>false</dhcp-lease-never-expires>

     	 <dhcp-lease-time>2</dhcp-lease-time>

 </create-connection-profile-dhcp-request>

Sample Output XML:

<create-connection-profile-dhcp-response uri="/api/space/device-management/modeled-device-management/create-connection-profile">

     	 <connection-profile

           	href="/api/space/device-management/modeled-device-management/connection-profiles/2686978" 

           	<id>2686978</id>

           	<name>Connection_Profile_DHCP</name>

     	 </connection-profile>

 </create-connection-profile-dhcp-response>

Sample Input JSON:

{

   	"create-connection-profile-dhcp-request" : {

     	"name" : "Connection_Profile_DHCP" ,

     	"description" : "Connection Profile Using DHCP" ,

     	"interface-type" : "ETHERNET" ,

     	"interface-name" : "ge-0/0/0" ,

     	"ip-type" : "Ipv4" ,

     	"use-nat" : "false" ,

     	"dhcp-retransmission-attempt" : "4" ,

     	"dhcp-retransmission-interval" : "4" ,

     	"dhcp-server-address" : "1.1.1.1" ,

     	"dhcp-update-server" : "false" ,

     	"dhcp-default-lease" : "false" ,

     	"dhcp-lease-never-expires" : "false" ,

     	"dhcp-lease-time" : "2"

   	}

 }

Sample Output JSON:

{

   	"create-connection-profile-dhcp-response" : {

     	"@uri" : "/api/space/device-management/modeled-device-management/create-connection-profile" ,

     	"connection-profile" : {

       	"@href" : "/api/space/device-management/modeled-device-management/connection-profiles/{id}" ,
 
       	"id" : 2686978 ,

       	"name" : "Connection_Profile_DHCP"

     	}

   	}

 }

Access Control

The following capabilities are required to access this API: CreateConnectionProfiles

POST /modeled-device-management/create-connection-profile

Version 1

Create PPPoE Connection Profile.

Sample Usage

POST /modeled-device-management/create-connection-profile

Content-Type Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoe-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoe-request+json;version=1;charset=UTF-8

Accept Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoe-response+xml;version=1
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoe-response+json;version=1

XML
JSON

Sample Input XML:

<create-connection-profile-pppoe-request>

     	 <name>Connection_Profile_PPPOE</name>

     	 <description>Connection Profile Using PPPoE</description>

     	 <interface-type>ETHERNET</interface-type>

     	 <interface-name>ge-0/0/0</interface-name>

     	 <ip-type>Ipv4</ip-type>

     	 <use-nat>false</use-nat>

     	 <auth-protocol-type>PAP</auth-protocol-type>

     	 <user-name>root</user-name>

     	 <password>********</password>

     	 <access-profile-user-name>root</access-profile-user-name>

     	 <access-profile-password>********</access-profile-password>

     	 <concentrator-name>test_concentrator</concentrator-name>

     	 <service-name>test_service</service-name>

     	 <time-interval>1</time-interval>

     	 <idle-period>1</idle-period>

 </create-connection-profile-pppoe-request>

Sample Output XML:

<create-connection-profile-pppoe-response uri="/api/space/device-management/modeled-device-management/create-connection-profile">

     	 <connection-profile

           	href="/api/space/device-management/modeled-device-management/connection-profiles/2686979"

           	<id>2686979</id>

           	<name>Connection_Profile_PPPOE</name>

     	 </connection-profile>

 </create-connection-profile-pppoe-response>

Sample Input JSON:

{

   	"create-connection-profile-pppoe-request" : {

     	"name" : "Connection_Profile_PPPOE" ,

     	"description" : "Connetion Profile Using PPPoE" ,

     	"interface-type" : "ETHERNET" ,

     	"interface-name" : "ge-0/0/0" ,

     	"ip-type" : "Ipv4" ,

     	"use-nat" : "false" ,

     	"auth-protocol-type" : "PAP" ,

     	"user-name" : "root" ,

     	"password" : "*******" ,

     	"access-profile-user-name" : "root" ,

     	"access-profile-password" : "********" ,

     	"concentrator-name" : "test_concentrator" ,

     	"service-name" : "test_service" ,

     	"time-interval" : "1" ,

     	"idle-period" : "1"

   	}

 }

Sample Output JSON:

{

   	"create-connection-profile-pppoe-response" : {

     	"@uri" : "/api/space/device-management/modeled-device-management/create-connection-profile"	,

     	"connection-profile" : {

       	"@href" : "/api/space/device-management/modeled-device-management/connection-profiles/2686979" ,

       	"id" : 2686979,

       	"name" : "Connection_Profile_PPPOE"

     	}

   	}

 }

Access Control

The following capabilities are required to access this API: CreateConnectionProfiles

POST /modeled-device-management/create-connection-profile

Version 1

Create PPPoA Connection Profile.

Sample Usage

POST /modeled-device-management/create-connection-profile

Content-Type Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoa-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoa-request+json;version=1;charset=UTF-8

Accept Headers:
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoa-response+xml;version=1
application/vnd.net.juniper.space.device-management.modeled-device-management.create-connection-profile-pppoa-response+json;version=1

XML
JSON

Sample Input XML:

<create-connection-profile-pppoa-request>

     	 <name>Connection_Profile_PPPOA</name>

     	 <description>Connection Profile Using PPPoA</description>

     	 <interface-type>ADSL</interface-type>

     	 <interface-name>test</interface-name>

     	 <ip-type>IPV4</ip-type>

     	 <use-nat>false</use-nat>

     	 <auth-protocol-type>PAP</auth-protocol-type>

     	 <user-name>root</user-name>

     	 <password>********</password>

     	 <access-profile-user-name>root</access-profile-user-name>

     	 <access-profile-password>********</access-profile-password>

     	 <vpi>2</vpi>

     	 <vci>2</vci>

     	 <encapsulation-type>atm-ppp-llc</encapsulation-type>

 </create-connection-profile-pppoa-request>

Sample Output XML:

<create-connection-profile-pppoa-response uri="/api/space/device-management/modeled-device-management/create-connection-profile">

     	 <connection-profile

           	href="/api/space/device-management/modeled-device-management/connection-profiles/2686980" 

           	<id>2686980</id>

           	<name>Connection_Profile_PPPOA</name>

     	 </connection-profile>

 </create-connection-profile-pppoa-response>

Sample Input JSON:

{

   	"create-connection-profile-pppoa-request" : {

     	"name" : "Connection_Profile_PPPOA" ,

     	"description" : "Connection Profile Using PPPoA" ,

     	"interface-type" : "ADSL" ,

     	"interface-name" : "test" ,

     	"ip-type" : "IPV4" ,

     	"use-nat" : "false" ,

     	"auth-protocol-type" : "PAP" ,

     	"user-name" : "root" ,

     	"password" : "********" ,

     	"access-profile-user-name" : "root" ,

     	"access-profile-password" : "********" ,

     	"vpi" : "2" ,

     	"vci" : "2" ,

     	"encapsulation-type" : "atm-ppp-llc"

   	}

 }

Sample Output JSON:

{

   	"create-connection-profile-pppoa-response" : {

     	"@uri" : "/api/space/device-management/modeled-device-management/create-connection-profile" ,

     	"connection-profile" : {

       	"@href" : "/api/space/device-management/modeled-device-management/connection-profiles/2686980" ,

       	"id" : 2686980,

       	"name" : "Connection_Profile_PPPOA"

     	}

   	}

 }

Access Control

The following capabilities are required to access this API: CreateConnectionProfiles