To resolve this issue I had to assign the Tenant "Cloud9" to the security domain of the AVS in APIC.
After adding the tenants security domain to the AVS I am able to select the AVS from the Cloud9 handle and not from the admin handle. The problem now seems to have changed and now its complaining about an unknown attribute :
[2016-10-19 11:14:39.049] [I] Calling - Add Tenant Shared network
[2016-10-19 11:14:39.051] [I] Tenant: Cloud9
[2016-10-19 11:14:39.052] [I] Network/EPG: ben
[2016-10-19 11:14:39.053] [I] Domain: ACI
[2016-10-19 11:14:39.054] [I] Vmm Domain ? true
[2016-10-19 11:14:39.055] [I] Default BD ? true
[2016-10-19 11:14:39.056] [I] Enacp Mode: Auto
[2016-10-19 11:14:39.057] [I] Tenant handles: 1
[2016-10-19 11:14:39.058] [I] @@@ Processing Apic-handle[0] Name: 10.221.108.101, 10.221.108.102, 10.221.108.103 Brian ExperianPoC
[2016-10-19 11:14:39.393] [I] Add tenant shared network failed network: ben
[2016-10-19 11:14:39.394] [E] Error in (Workflow:Add Tenant Network - Shared Plan / Scriptable task (item1)#88) Error: Add Tenant shared network failed, Error code: 400 Error desc: unknown attribute 'encapMode' in element 'fvRsDomAtt'
[2016-10-19 11:14:39.401] [E] Workflow execution stack:
***
item: 'Add Tenant Network - Shared Plan/item1', state: 'failed', business state: 'null', exception: 'Error: Add Tenant shared network failed, Error code: 400 Error desc: unknown attribute 'encapMode' in element 'fvRsDomAtt' (Workflow:Add Tenant Network - Shared Plan / Scriptable task (item1)#88)'
workflow: 'Add Tenant Network - Shared Plan' (44c6cb03-e5e5-4b99-af74-1c8e9cbd28f8)
| 'attribute': name=validTierNumber type=boolean value=true
| 'input': name=tenant type=string value=Cloud9
| 'input': name=network type=string value=ben
| 'input': name=domType type=string value=VmmDomain (Dynamic Binding)
| 'input': name=dom type=APIC:hvsLNode value=dunes://service.dunes.ch/CustomSDKObject?id='ExperianPoC:comp/prov-VMware/ctrlr-%5BACI%5D-V_server/sw-dvs-587'&dunesName='APIC:hvsLNode'
| 'input': name=tierNum type=number value=1
| 'input': name=intraEpgDeny type=boolean value=false
| 'input': name=allowUseg type=boolean value=false
| 'input': name=defaultBdFlag type=boolean value=true
| 'input': name=customBd type=APIC:fvBD value=null
| 'input': name=encapMode type=string value=Auto
| 'output': name=epgObjects type=Array/APIC:fvAEPg value=null
*** End of execution stack.
I followed the virtualization guidelines shown below, as you can see the encapMode field is only applicable if the AVS is enabled to local switching
| Step 3 |
In the Tenant Shared Plan pane, choose Add Tenant Network - Shared Plan and perform the following actions:
- View the Service Blueprint Information for the input fields and click Request.
- In the Request Information pane, add the description and click Next.
- In the Step pane, perform the following actions:
- In the NetworkEPG name field, enter the name of the new shared network (new-shared-network).
- In the Domain/DVS field, click Add, expand and select the DVS.
- From the encapMode drop-down list, choose either Auto, VLAN, or VXLAN for the encapsulation mode.
| Note |
The encapMode field is applicable only if the VMMdomain type is Cisco AVS (Local Switching). Selecting VLAN or VXLAN for vDS VMM Domain, may lead into unpredictable results.
|
- In the Application Tier Number field, enter a numeric value from 1-10.
- In the Intra EPG Deny field, select a value either Yes or No.
- In the Allow Microsegmentation field, select a value either Yes or No.
| Note |
The Allow Microsegmentation field is applicable only if the VMMdomain type is vDS VMM Domain.
|
- In the Use Default BD? field, select a value either Yes or No.
If you selected No, choose a custom bridge domain by clicking on Add.
- Click Submit.
|
I have left this as default (AUTO).
Thanks
Ben
