云服务器内容精选

  • 响应示例 返回状态码为200:站点解绑AP VLAN POOL成功,响应体参考ApVlanPoolResponse。 HTTP/1.1 200 OK Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive { "errcode" : "0", "errmsg" : "", "siteId" : "fbb684c8-0d37-496f-bafa-4b06d5151e2e", "data" : [ { "id" : "fbde1c5d-5b94-49e3-a912-48641015e45c", "name" : "VLANPOOLTemplate1", "range" : "3001", "type" : "even" } ] } 返回状态码为400:校验异常。 HTTP/1.1 400 Bad Request Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive 返回状态码为500:内部服务错误。 HTTP/1.1 500 Internal Server Error Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive
  • 请求示例 HTTP的示例 PUT /v1/networkconfig/wlan/ap/vlanpools/unbind HTTP/1.1 Host: 192.168.1.125:18002 Content-Type: application/json Accept: application/json Accept-Language: en-US X-AC CES S-TOKEN: x-yyyyyy { "siteId" : "00000000-0000-0000-0000-0000000", "templateIds" : ["00000000-0000-0000-0000-0000000"] }
  • URI /v1/networkconfig/wlan/ap/vlanpools 表1 query参数列表 参数名称 必选 类型 参数值域 默认值 参数说明 参数示例 siteId 是 string 36个字符。 - 站点ID。 "fbb684c8-0d37-496f-bafa-4b06d6151e2e" pageIndex 否 int32 [1-1500] 1 第几页的数据。 1 pageSize 否 int32 [1-100] 20 一页多少条数据。 1 vlanPoolName 否 string 0~32个字符。 - VLAN POOL名称。 "pool1"
  • 请求示例 HTTP的示例 GET /v1/networkconfig/wlan/ap/vlanpools?siteId=fbb684c8-0d37-496f-bafa-4b06d6151e2e&pageIndex=1&pageSize=1&vlanPoolName=pool1 HTTP/1.1 Host: 192.168.1.125:18002 Content-Type: application/json Accept: application/json Accept-Language: en-US X-ACCESS-TOKEN: x-yyyyyy
  • 响应示例 返回状态码为200:查询AP VLAN POOL成功,响应体参考GetApVlanPoolResponse。 HTTP/1.1 200 OK Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive { "errcode" : "0", "errmsg" : "", "siteId" : "fbb684c8-0d37-496f-bafa-4b06d5151e2e", "data" : [ { "id" : "fbde1c5d-5b94-49e3-a912-48641015e45c", "name" : "VLANPOOLTemplate1", "range" : "3001", "type" : "even" } ], "pageIndex" : 1, "pageSize" : 1, "totalRecords" : 1 } 返回状态码为400:校验异常。 HTTP/1.1 400 Bad Request Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive 返回状态码为500:内部服务错误 HTTP/1.1 500 Internal Server Error Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive
  • 响应示例 返回状态码为200:站点绑定AP VLAN POOL成功,响应体参考ApVlanPoolResponse。 HTTP/1.1 200 OK Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive { "errcode" : "0", "errmsg" : "", "siteId" : "fbb684c8-0d37-496f-bafa-4b06d5151e2e", "data" : [ { "id" : "fbde1c5d-5b94-49e3-a912-48641015e45c", "name" : "VLANPOOLTemplate1", "range" : "3001", "type" : "even" } ] } 返回状态码为400:校验异常。 HTTP/1.1 400 Bad Request Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive 返回状态码为500:内部服务错误。 HTTP/1.1 500 Internal Server Error Date: Sun,16 Feb 2025 10:00:00 GMT Server: example-server Content-Type: application/json;charset=UTF-8 Content-Length: 250 Connection: keep-alive
  • 请求示例 HTTP的示例 PUT /v1/networkconfig/wlan/ap/vlanpools/bind HTTP/1.1 Host: 192.168.1.125:18002 Content-Type: application/json Accept: application/json Accept-Language: en-US X-ACCESS-TOKEN: x-yyyyyy { "siteId" : "00000000-0000-0000-0000-0000000", "templateIds" : ["00000000-0000-0000-0000-0000000"] }
  • 响应参数 返回状态码为200:站点绑定AP VLAN POOL成功,响应体参考ApVlanPoolResponse。 表3 ApVlanPoolResponse对象的参数列表 参数名称 类型 参数值域 默认值 参数说明 参数示例 errcode string 1~32个字符。 0 错误码。 "0" errmsg string 0~256个字符。 - 错误信息。 "" siteId string 36个字符。 - 站点ID。 "fbb684c8-0d37-496f-bafa-4b06d5151e2e" data ARRAY_REFERENCE 0-100个列表项,详细请参见表3。 创建、更新或者删除成功的IP Subnet信息。 - 返回状态码为400:校验异常。 详细信息请参见实际响应消息体。 返回状态码为500:内部服务错误。 详细信息请参见实际响应消息体。