-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Open
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamNetworkaz network vnet/lb/nic/dns/etc...az network vnet/lb/nic/dns/etc...potential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Milestone
Description
Following sample below:
az network vhub route-table route add -n MyRouteTable -g MyResourceGroup --vhub-name MyVhub --destination-type CIDR --destinations "10.4.0.0/16" "10.6.0.0/16" --next-hop-type ResourceId --next-hop /subscriptions/MySub/resourceGroups/MyResourceGroup/providers/Microsoft.Network/azureFirewalls/MyFirewall
Outputs below error:
Usage error: --next-hop and --route-name must be provided as you are adding route to v3 route table.
Therefore, command is missing the --route-name parameter/input.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 7c572a40-459c-4dc0-0664-226f3ce37eaa
- Version Independent ID: b823f80d-9831-bcb3-7baf-766f7c95a0e5
- Content: az network vhub route-table route
- Content Source: latest/docs-ref-autogen/network/vhub/route-table/route.yml
- Service: virtual-network
- GitHub Login: @rloutlaw
- Microsoft Alias: routlaw
Metadata
Metadata
Assignees
Labels
Auto-AssignAuto assign by botAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamThe command of the issue is owned by Azure CLI teamNetworkaz network vnet/lb/nic/dns/etc...az network vnet/lb/nic/dns/etc...potential-pruningquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that