• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

Error during creation of NAT Routed network via VMware vCloud Director (vCD)

Duncan Epping · Sep 10, 2010 ·

Internally I have seen this one a couple of times so I knew what the issue was, but outside of VMware not many people have played with VMware vCloud Director (vCD) yet. Here’s the full error that is shown when you create a NAT Router Org network of vApp network:

Error creating Shield network appliance.
– vClould-Shield edge error: Creating/configuring the VR failed: vsmHandle.initializeEdge() net:1948253845/dvportgroup-218 vse:vm-220 VSM IP:10.0.0.10 failed.
– HTTP/1.1 403 Forbidden – The user does not have permission to perform this operation.

This usually means that the vShield Edge license key has not been added to vCenter. You can simply add it as follows:

  1. From a vSphere Client host that is connected to a vCenter Server system, select Home > Licensing.
  2. For the report view, select Asset.
  3. Right‐click a vShield asset and select Change license key.
  4. Select Assign a new license key and click Enter Key.
  5. Enter the license key, enter an optional label for the key, and click OK.
  6. Click OK.
  7. Repeat these steps for each vShield component for which you have a license.

That should resolve this issue. Yes I agree, the error could have been more “user friendly” and I will ask the Engineering team if they can change this.

Related

cloud, Various edge, Howto, vcd, vcloud, vshield

Reader Interactions

Comments

  1. Naresh says

    17 September, 2010 at 13:10

    This tip really saved me lot of time. Just with the error message i would have gone crazy searching all my settings. Thanks for the post.

  2. Marco says

    4 October, 2010 at 11:43

    same here 🙂

  3. Viktor says

    3 February, 2011 at 10:28

    Great tip Duncan! Saved me a lot of time as well!

  4. Prasenjit says

    7 March, 2011 at 19:56

    Hi Duncan,

    Thanks for this article. I am having one of a known issue while trying to add Org network with vCNI Pool. What happens is I have both the external network and vCNI pool on the same network.

    I know that this is not the supported configuration to have both on the same subnet. But due to the LAB limitation I have to have this.

    I know there is a parameter to change in the CONFIG table inside the Oracle database to tweak this but can’t find a script or method to achieve this.

    In the partner training they provided the script and method to do this but I forgot how to achieve this. Below is the error message I am getting.

    IP Subnet of network “XXX_EXT_NAT_NW” overlaps with that of the external network “XXX-vCD-External”. This is an unsupported configuration.

    Can you please help me with this.

  5. Nacho says

    27 October, 2011 at 05:37

    It turned out that when you upgrade from vCD 1.0 to 1.5 if you don’t upgrade your vShield environment after going along with vCenter 5.0 the vShield Edge license assignment at the vCenter level gets unlinked.

    After that, it’s impossible to deploy new NAT routed external networks: they get deployed and they get unprovisioned after several minutes. Thanks for this article: it saved literally the day for me.

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist in the Office of the CTO in the Cloud Infrastructure Business Group (CIBG) at VMware. Besides writing on Yellow-Bricks, Duncan co-authors the vSAN Deep Dive book series and the vSphere Clustering Deep Dive book series. Duncan also co-hosts the Unexplored Territory Podcast.

Follow Me

  • Twitter
  • LinkedIn
  • Spotify
  • YouTube

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2023 · Log in