forked from docs/doc-exports
Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
10 KiB
10 KiB
Querying a VPC Route
Function
This API is used to query details about a route.
Request Parameters
None
Example Request
GET https://{Endpoint}/v2.0/vpc/routes/60c809cb-6731-45d0-ace8-3bf5626421a9
Response Parameters
Parameter |
Type |
Description |
|---|---|---|
route |
route object |
Specifies the route. For details, see Table 3. |
Attribute |
Type |
Description |
|---|---|---|
id |
String |
Specifies the route ID. |
destination |
String |
Specifies the destination address in the CIDR notation format, for example, 192.168.200.0/24. |
nexthop |
String |
Specifies the next hop. If the route type is peering, enter the VPC peering connection ID. |
type |
String |
Specifies the route type. Currently, the value can only be peering. |
vpc_id |
String |
Specifies the VPC of the route. Set this parameter to the existing VPC ID. |
tenant_id |
String |
Specifies the project ID. |
Example Response
{
"route": {
"type": "peering",
"nexthop": "60c809cb-6731-45d0-ace8-3bf5626421a9",
"destination": "192.168.200.0/24",
"vpc_id": "ab78be2d-782f-42a5-aa72-35879f6890ff",
"tenant_id": "6fbe9263116a4b68818cf1edce16bc4f",
"id": "3d42a0d4-a980-4613-ae76-a2cddecff054"
}
}
Status Code
See Status Codes.
Error Code
See Error Codes.
Parent topic: VPC Route