Skip to main content

Prerequisit for Network Service

This documentation detail the Network need and prerequisite obligation if you want to request for any Core Service or Network service.

  • ZPA
  • Software Factory (Gitlab, Artifactory, Coverity)
  • Service private interconnection ( K8saas, LZ, Dbaas)

You will be required to respect these rules.

1. Virtual network IP Integration​

Regarding your offers the IP ad provisionning will be difrente You need to make a request for it.

  • Industrialise LZ : Have to request for IP with Corporate IP demande
  • Protect LZ : Automatically provisioned with the correct IP Plan
caution

K8saas and DBaas service are not concerned. IP plan is managed is part of the Offer

2. Virtual network peering​

Then request for a Peering in order to be properly integrate to TDP environment. Vnet peer demande

tip

Objectif is to integrate Peering directly at the LZ delivery

Azure Virtual network conditions​

  • Peering is not allowed when the source VNET has a GW Azure Virtual network gateway or NVA/Firewall
  • Please delete that GW & related Gateway Subnet before submitting your peering request
  • Only one peering for the virtual network can have this setting "Use remote gateways" enabled.
  • You cannot "use remote gateways" if you already have a gateway configured in your virtual network !
  • One TDP peer per Vnet (Only one transition/VWAN peering is allowed)
  • Please verify before if your VNET is already peered with the TDP transition / VWAN
  • Intervnet Peering isn't allowed. Please ask for an opening flow request Flow opening request

These peering rules apply to any peering request for :

  • Internal connectivity (inter-vNET) : between the Project (MVP / DP) and Coreservice(COS) of the Factory
  • Thales sites : RIE , EIP , Mobility (vNET-To-Branches) or any other Thales Branches (AMS, TAS, TPC , DIS ...)
  • ZPA : VPN Client solution

Azure Peering FAQ​

My virtual network peering connection is in an Initiated state, why can't I connect?

If your peering connection is in an Initiated state, it means you have created only one link. A bidirectional link must be created in order to establish a successful connection. For example, to peer VNet A to VNet B, a link must be created from VNet A to VNet B, and from VNet B to VNet A. Creating both links changes the state to Connected.

My virtual network peering connection is in a Disconnected state, why can't I create a peering connection?

If your virtual network peering connection is in a Disconnected state, it means one of the links created was deleted. In order to re-establish a peering connection, delete the link and recreate it.

If I peer VNet A to VNet B and I peer VNet B to VNet C, does that mean VNet A and VNet C are peered?

No. Transitive peering is not supported. You must peer VNet A and VNet C.