cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2209) added nics are not reachable from other VMs on the same network
Date Fri, 26 Apr 2013 14:12:15 GMT

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

Marcus Sorensen commented on CLOUDSTACK-2209:
---------------------------------------------

What do you see when you look for the forward delay setting on your bridges? e.g.

brctl showstp cloudbr0

With RHEL/CentOS it's common for the foward delays to be high, like 14.99. This means that
when a new NIC is plugged in, it doesn't work for 15 seconds, which may mean it's not getting
its DHCP address in time.

Bridges created by cloudstack should be getting a proper forward delay, so check that.

Is there a chance these two VMs ended up on different physical hosts and the issue may lie
there, or what does your environment look like? Just looking for additional clues.
                
> added nics are not reachable from other VMs on the same network
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2209
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2209
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: KVM 
> Build:CloudStack-non-OSS-MASTER-262-rhel6.3
>            Reporter: shweta agarwal
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Steps to reproduce
> 1 create a VM say vm1 with 1 network
> 2. add a new network say n2 to this vm
> 3. create a new vm say vm2 in network n2
> 5. ping  ip for n2 network  from vm2 for vm1
> Bug:
> n2 network IP is not pingable from vm2 and even vice versa
> Expectation:
> IP should be pingable
> Additional information
> ifconfig shows eth are assigned proper ips.

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