Hi All,
Imported Device package---successfull
Added ASAV to Conroller-Successfull.
Applying service graph template error.
!
|
minor
|
||
|
2015-11-08T22:25:06.826+00:00
|
||
|
Raised
|
||
uni/tn-TENANT-WT-COE/GraphInst_C-[uni/tn-TENANT-WT-COE/brc-ASAV-APP-to-DB-Filter]-G-[uni/tn-TENANT-WT-COE/AbsGraph-ASAv-Firewall]-S-[uni/tn-TENANT-WT-COE]/NodeInst-Firewall/vnsConfIssue-missing-lif
|
||
|
Configuration is invalid due to no cluster interface found
|
||
Explanation: None set.
Recommended Action: None set.
++++++++++++++++++++++++++++++++++
|
ASAV-APP-to-DB-Filter
|
||
|
failed-to-apply
|
||
|
ASAv-Firewall
|
||
|
Tenant TENANT-WT-COE
|
||
Hello subashchandran, I have the same problem with the ASAv and ACI 1.2.1m release. I cannot find any clue why this is not working. Device package used is : ASA 1.2.4.8
Message :
uni/tn-DDNL_LAB/GraphInst_C-[uni/tn-DDNL_LAB/brc-WEB]-G-[uni/tn-DDNL_LAB/AbsGraph-SGT-ASAv-01]-S-[uni/tn-DDNL_LAB]/NodeInst-N1/vnsConfIssue-missing-lif
|
Hello,
Did you configure the cluster interface under the L4-7 Device? The configuration has changed a bit from 1.1 to 1.2. You can find it below outlined in red. Please ensure that you have properly configured the cluster interfaces.
If we cannot find an interface then service graph instantiation will fail giving a fault like you see above.
Thanks,
Mike Ripley
Hello Mike, i downgraded the apic software from 1.2.1m to 1.2.1i. The device package is supported on this version of apic. I still have problems. I removed all L4-L7 instances and create a new L4-L7 Device. When i create the device i already have error messages :
|
8589937012
|
|
L4-L7 Devices configuration Dev-ASAv-01 for tenant DDNL_LAB is invalid.
|
|
minor
|
|
uni/tn-DDNL_LAB/lDevVip-Dev-ASAv-01
|
|
2016-02-23T16:01:07.117+01:00
|
|
F0764
|
|
Config
|
|
configuration-failed
|
|
configIssues:missing-namespace, configSt:failed-to-apply, contextAware:single-Context, devtype:VIRTUAL, faultCode:0, faultSeverity:minor, funcType:GoThrough, managed:yes, mgmtType:oob, mode:legacy-Mode, name:Dev-ASAv-01, svcType:FW
|
|
creation
|
|
Tenant
|
|
Soaking
|
|
1
|
|
8589937012
|
|
L4-L7 Devices configuration Dev-ASAv-01 for tenant DDNL_LAB is invalid.
|
|
minor
|
|
uni/tn-DDNL_LAB/lDevVip-Dev-ASAv-01
|
|
2016-02-23T16:01:07.117+01:00
|
|
F0764
|
|
Config
|
|
configuration-failed
|
|
configIssues:missing-namespace, configSt:failed-to-apply, contextAware:single-Context, devtype:VIRTUAL, faultCode:0, faultSeverity:minor, funcType:GoThrough, managed:yes, mgmtType:oob, mode:legacy-Mode, name:Dev-ASAv-01, svcType:FW
|
|
creation
|
|
Tenant
|
|
Soaking
|
|
1
|
|
8589937010
|
|
Failed to form relation to MO uni/vmmp-VMware/dom-vCenter_LAB of class vmmDomP
|
|
warning
|
|
uni/tn-DDNL_LAB/lDevVip-Dev-ASAv-01/rsALDevToDomP
|
|
2016-02-23T16:01:07.108+01:00
|
|
F1081
|
|
Config
|
|
resolution-failed
|
|
forceResolve:no, rType:mo, state:missing-target, stateQual:none, tCl:vmmDomP, tDn:uni/vmmp-VMware/dom-vCenter_LAB, tType:mo
|
|
creation
|
|
Infra
|
|
Raised
|
|
1
|
In the mean time i see the next messages :
|
8589937008
|
|
Configuration is invalid due to no vlan/vxlan namespace found
|
|
minor
|
|
uni/tn-DDNL_LAB/lDevVip-Dev-ASAv-01/vnsConfIssue-missing-namespace
|
|
2016-02-23T16:01:07.094+01:00
|
|
F1690
|
|
Config
|
|
configuration-failed
|
|
issue:missing-namespace
|
|
creation
|
|
Tenant
|
|
Soaking
|
|
1
|
| missing-namespace | no vlan/vxlan namespace found | The namespace that is needed to allocate the VLAN or VXLAN is missing. Verify that the resolved vnsLDevVip has thephyDomp parameter or the vmmDomp parameter configured that has a relation to the resolved fvnsVlanInstp. |
