cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-4416) [DOC] Need to document about vservice command and Nexus vSwitch versions (Failed to implement guest network with Cisco VNMC provided offering when vservice command is not present)
Date Wed, 21 Aug 2013 11:43:52 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745963#comment-13745963
] 

ASF subversion and git services commented on CLOUDSTACK-4416:
-------------------------------------------------------------

Commit 2db1f3b1340f149c43fdfee1966988b8a0404449 in branch refs/heads/master from [~radhikap]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2db1f3b ]

CLOUDSTACK-4416 and CLOUDSTACK-906 cisco vnmc doc reviews

                
> [DOC] Need to document about vservice command and Nexus vSwitch versions (Failed to implement
guest network with Cisco VNMC provided offering when vservice command is not present)
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4416
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4416
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc
>    Affects Versions: 4.2.0
>            Reporter: Sailaja Mada
>            Assignee: Radhika Nair
>             Fix For: 4.2.0
>
>
> Observation:
> 1. VNMC requires vservice command to be available with Nexus 1000v switch 
> With Nexus 100v  system:    version 4.2(1)SV1(5.1)  , vservice command was not available,
So guest network deployment failed while using this Nexus 1000v)
> 2. nexus-1000v.4.2.1.SV1.5.2b.bin  has vservice command.
> So we need to document about the working Nexus 1000v version  with VNMC and also about
the vservice command availability @ Nexus before using it in CloudStack for VNMC.
> Additional details about the issue : 
> Steps:
> 1. Upgraded from 2.2.16 to 4.2 .
> 2  I have added Nexus cluster here . Now I am trying to implement network with VNMC offering
. It is failing while adding vservice node :
> I could not vservice command in my nexus 1000v 
> 2013-08-09 16:12:26,922 DEBUG [cloud.storage.StorageManagerImpl] (StorageManager-Scavenger-1:null)
Secondary storage garbage collector found 0 volumes to cleanup on volume_store_ref for store:
newSS1
> 2013-08-09 16:12:27,048 ERROR [network.resource.CiscoVnmcResource] (DirectAgent-133:null)
ConfigureVSMForASACommand failed due to  Severity: error, Error code: InvalidValue, Error
type: application, Error Message: Syntax error while parsing 'vservice node ASA_792 type asa'
> com.cloud.utils.exception.CloudRuntimeException:  Severity: error, Error code: InvalidValue,
Error type: application, Error Message: Syntax error while parsing 'vservice node ASA_792
type asa'
>         at com.cloud.utils.cisco.n1kv.vsm.NetconfHelper.parseOkReply(NetconfHelper.java:286)
>         at com.cloud.utils.cisco.n1kv.vsm.NetconfHelper.addVServiceNode(NetconfHelper.java:179)
>         at com.cloud.network.resource.CiscoVnmcResource.execute(CiscoVnmcResource.java:668)
>         at com.cloud.network.resource.CiscoVnmcResource.execute(CiscoVnmcResource.java:657)
>         at com.cloud.network.resource.CiscoVnmcResource.executeRequest(CiscoVnmcResource.java:108)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-08-09 16:12:27,050 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-133:null)
Seq 19-231211014: Response Received:
> 2013-08-09 16:12:27,050 DEBUG [agent.transport.Request] (DirectAgent-133:null) Seq 19-231211014:
Processing:  { Ans: , MgmtId: 90310994128556, via: 19, Ver: v1, Flags: 10, [{"com.cloud.agent.api.Answer":{"result":false,"details":"ConfigureVSMForASACommand
failed due to  Severity: error, Error code: InvalidValue, Error type: application, Error Message:
Syntax error while parsing 'vservice node ASA_792 type asa'\n\n","wait":0}}] }
> 2013-08-09 16:12:27,051 DEBUG [agent.transport.Request] (Job-Executor-7:job-168 = [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8
]) Seq 19-231211014: Received:  { Ans: , MgmtId: 90310994128556, via: 19, Ver: v1, Flags:
10, { Answer } }
> 2013-08-09 16:12:27,051 DEBUG [agent.manager.AgentManagerImpl] (Job-Executor-7:job-168
= [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Details from executing class com.cloud.agent.api.ConfigureNexusVsmForAsaCommand:
ConfigureVSMForASACommand failed due to  Severity: error, Error code: InvalidValue, Error
type: application, Error Message: Syntax error while parsing 'vservice node ASA_792 type asa'
> 2013-08-09 16:12:27,051 ERROR [network.element.CiscoVnmcElement] (Job-Executor-7:job-168
= [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Failed to configure Cisco Nexus VSM 10.102.192.75
for ASA device for network vnmcnw1
> 2013-08-09 16:12:27,051 DEBUG [db.Transaction.Transaction] (Job-Executor-7:job-168 =
[ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Rolling back the transaction: Time = 1220 Name =
 -AsyncJobManagerImpl$1.run:494-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:679;
called by -Transaction.rollback:898-CiscoVnmcElement.implement:414-NetworkManagerImpl.implementNetworkElementsAndResources:2003-NetworkManagerImpl.implementNetwork:1908-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-NetworkManagerImpl.prepare:2089-VirtualMachineManagerImpl.advanceStart:882-VirtualMachineManagerImpl.start:574-VMEntityManagerImpl.deployVirtualMachine:237-VirtualMachineEntityImpl.deploy:209-UserVmManagerImpl.startVirtualMachine:3402-UserVmManagerImpl.startVirtualMachine:2962
> 2013-08-09 16:12:27,064 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-7:job-168
= [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Cleaning up because we're unable to implement
the network Ntwk[215|Guest|17]
> 2013-08-09 16:12:27,069 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-7:job-168
= [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Lock is acquired for network Ntwk[215|Guest|17]
as a part of network shutdown
> 2013-08-09 16:12:27,073 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-7:job-168
= [ 5be627ca-9bf8-44f3-94f3-4cd1cee248c8 ]) Releasing 0 port forwarding rules for network
id=215 as a part o

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message