Hey RadoslawDabrowski - sorry I didn't see this sooner. Notifications had issues
Are you doing this as part of an actual blueprint or are you creating a network to add to a network profile after the fact (provider infrastructure as code usecase). In the latter, it should be creating a Tier-1 router that links up to a Tier-0
Those settings are there for if you have multiple Tier-0 routers, and you want to specify the one to use for a given network profile. If you only have 1 Tier-0, it's "implied" within the profile as that being the one to use.
Can you share your blueprint that you're using here? I can confirm a few things in my environment.
I was doing it as a part of an blueprint which i was preparing. I wanted to create VM and network profile on demand to achieve VM connected to the network which was newly created and connected to T1 or T0 Logical Router. It was my understanding of this Tier-0 Logical Router purpose, but it is not working as it should, at least under my environment.
Blueprint is very simple:
You've chosen the networkType private. The private type isolates the VM from external connections. If you would like an on demand network, with connectivity to the deployed VM, you will want to choose networkType outbound or routed.
I'm in the process of writing a blog series on this topic. Take a look, if you get a chance: Network Automation with Cloud Assembly and NSX - part 1 - VMware Cloud Management
You are absolutely right, i made many tests there, with networkType set to Outbound and set to Routed as well...
When i was creating this topic, this functionality was not working correctly. Maybe something in CAS was failing, but now its working perfectly. T1 Logical Router is created as well as Logical switch. Network is assigned to the T1 LR, and this T1 Logical Router is now assigned to mentioned in Network Profile T0 Logical Router.
Perfect. Thanks everyone for help.