all new accounts go into VRF by default now
Closed this issue · 1 comments
Did you know you can also submit a pull request to update any IBM Cloud documentation topic by clicking the Edit Topic link on any page? For more information, see Providing a content update with a pull request: https://cloud.ibm.com/docs/overview?topic=overview-feedback#feedback-pr.
-
What are the details of the issue you're experiencing?
customers opening support ticket requesting to enable VRF on their account -
Is this issue in reference to a specific page? If so, please provide a link.
https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint&interface=ui#service-endpoint -
Do you have a suggestion about how to resolve the issue?
Starting Nov 30, 2023, any newly created account, or an account that has no Classic infrastructure deployed, will now be automatically converted to a VRF-style account when the first Classic Private VLAN is deployed. Whether they order a server, a solution that deploys a Classic Private VLAN, or they just directly order a Classic Private VLAN from the catalog, the account will be converted. This will not impact accounts that have current Classic infrastructure deployments, unless they cancel/reclaim everything, and start from scratch; those accounts will still need a manual support case for conversion.
That has been done already. https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint
Attention: By default, classic accounts that were established before 30 November 2023, are included in the IBM Cloud general routing table. Previously, if you wanted to convert a classic account to a VRF-style account, you were required to open a support case with IBM® Support. Beginning 30 November 2023, any new classic account or any existing classic account that is “empty” (for example, without any provisioned VLANs), will be automatically converted to a VRF-style account the next time that account initiates a private network connection. For more information, see FAQs about VRF account migration.