cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ilya musayev (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-599) DhcpEntryCommand fails on Router VM on CS4.0 and vSphere5 with Advanced Network Zone
Date Sat, 08 Dec 2012 04:27:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ilya musayev closed CLOUDSTACK-599.
-----------------------------------


https://reviews.apache.org/r/8420/#review14193
                
> DhcpEntryCommand fails on Router VM on CS4.0 and vSphere5 with Advanced Network Zone
> ------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-599
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-599
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.0
>         Environment: CS4.0 and vSphere5 with Advanced Network Zone
>            Reporter: ilya musayev
>              Labels: RouterVM
>             Fix For: 4.0.1, 4.1.0
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Identified and resolved issue for Router VM on vSphere 5.0 and CS 4.0 - where a router
VM would come up however the Link Local IP would be unreachable until you initiate a ping
request from Router VM itself. As the result - you are unable to deploy instances. The logs
display a problem with DhcpEntryCommand as Router VM is unreachable. The router VM does not
receive inbound communication, but outbound communication is fine.
> The ping updates the ARP table with additional MAC entry of the gateway. We are ping
the gateway of CS host specifically - as this is the major needed source of communication.
Once ARP table is updated - communication works in both directions.  

--
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