Hello Anthony,

That's what i've done, but restart vpc from ui give me these errors.

All rules are not reapplied.

Benoit.

2013/2/14 Anthony Xu <[email protected]>

> Try restart vpc from UI, it will reboot vpc VR and reapply all rules.
>
> Anthony
>
> > -----Original Message-----
> > From: benoit lair [mailto:[email protected]]
> > Sent: Thursday, February 14, 2013 9:53 AM
> > To: [email protected]
> > Subject: Re: VPC bug - no more vlan interfaces after reboot
> >
> > Hello Anthony,
> >
> > I rebooted my vpc vr with the UI, the cs mgmt server recreated an fresh
> > instance of my vpc, bu finally i got only one tier recreated, i dont't
> > recover my vlans interfaces.
> >
> > I got these errors messages :
> >
> > 2013-02-14 10:53:39,703 DEBUG [agent.transport.Request]
> > (DirectAgent-259:null) Seq 14-1794713198: Processing:  { Ans: , MgmtId:
> > 165013918770818, via: 14, Ver: v1, Flags: 110,
> > [{"SetupGuestNetworkAnswer":{"
> > result":false,"details":"Creating guest network failed due to
> > com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed
> > for
> > cmd: routerProxy with args args: vpc_guestnw.sh 169.254.3.22 -D -d eth2
> > -i
> > 172.28.2.1 -g 172.28.2.1 -m 24 -n 172.28.2.0 -s 195.7.111.30,x.x.x.x -e
> > z03.cloud.domain.tld <http://z03.cloud.web-et-solutions.com>,  due to
> > Failed to create input stream: Read timed out","wait":0}}] }
> > 2013-02-14 10:53:39,703 DEBUG [agent.manager.AgentAttache]
> > (DirectAgent-259:null) Seq 14-1794713202: Sending now.  is current
> > sequence.
> > 2013-02-14 10:53:39,703 DEBUG [agent.transport.Request]
> > (Network-Scavenger-1:null) Seq 14-1794713198: Received:  { Ans: ,
> > MgmtId:
> > 165013918770818, via: 14, Ver: v1, Flags: 110,
> > { SetupGuestNetworkAnswer } }
> > 2013-02-14 10:53:39,703 DEBUG [agent.transport.Request]
> > (DirectAgent-259:null) Seq 14-1794713202: Executing:  { Cmd , MgmtId:
> > 165013918770818, via: 14, Ver: v1, Flags: 100111,
> > [{"SetupGuestNetworkCommand":{"dhcpRange":"172.28.1.1","networkDomain":
> > "
> > z03.cloud.domain.tld <http://z03.cloud.web-et-solutions.com>
> > ","defaultDns1":"195.7.111.30","defaultDns2":"x.x.x.x","isRedundant":fa
> > lse,"add":false,"nic":{"deviceId":3,"networkRateMbps":200,"defaultNic":
> > false,"uuid":"f1c50f06-db19-4293-9842-
> > d37bb4d8bba2","ip":"172.28.1.1","netmask":"255.255.255.0","mac":"02:00:
> > 20:cc:00:08","dns1":"195.7.111.30","dns2":"x.x.x.x","broadcastType":"Vl
> > an","type":"Guest","broadcastUri":"vlan://2510","isolationUri":"vlan://
> > 2510","isSecurityGroupEnabled":false,"name":"ground1"},"accessDetails":
> > {"router.guest.ip":"172.28.1.1","guest.vlan.tag":"2510","guest.network.
> > gateway":"172.28.1.1","guest.bridge":"172.28.1.255","
> > router.name":"r-18183-VM","router.ip":"169.254.3.22"},"wait":0}}] }
> > 2013-02-14 10:53:39,703 WARN
> > [network.router.VpcVirtualNetworkApplianceManagerImpl]
> > (Network-Scavenger-1:null) Unable to destroy guest network on router
> > VM[DomainRouter|r-18183-VM]
> > 2013-02-14 10:53:39,703 WARN
> > [network.router.VpcVirtualNetworkApplianceManagerImpl]
> > (Network-Scavenger-1:null) Failed to destroy guest network config
> > Ntwk[239|Guest|12] on router VM[DomainRouter|r-18183-VM]
> > 2013-02-14 10:53:39,704 WARN  [network.element.VpcVirtualRouterElement]
> > (Network-Scavenger-1:null) Failed to unplug nic in network
> > Ntwk[239|Guest|12] for virtual router VM[DomainRouter|r-18183-VM]
> > 2013-02-14 10:53:39,704 WARN  [cloud.network.NetworkManagerImpl]
> > (Network-Scavenger-1:null) Unable to complete shutdown of the network
> > elements due to element: VpcVirtualRouter
> > 2013-02-14 10:53:39,703 DEBUG [agent.manager.DirectAgentAttache]
> > (DirectAgent-20:null) Seq 14-1794713202: Executing request
> > 2013-02-14 10:53:39,876 DEBUG [agent.manager.AgentAttache]
> > (RouterStatusMonitor-1:null) Seq 14-1794713256: Waited too long.
> > 2013-02-14 10:53:39,876 INFO  [utils.exception.CSExceptionErrorCode]
> > (RouterStatusMonitor-1:null) Could not find exception:
> > com.cloud.exception.OperationTimedoutException in error code list for
> > exceptions
> > 2013-02-14 10:53:39,876 WARN  [agent.manager.AgentAttache]
> > (RouterStatusMonitor-1:null) Seq 14-1794713256: Timed out on Seq
> > 14-1794713256:  { Cmd , MgmtId: 165013918770818, via: 14, Ver: v1,
> > Flags:
> > 100111,
> > [{"CheckS2SVpnConnectionsCommand":{"vpnIps":[],"accessDetails":{"router
> > .ip":"169.254.3.191","
> > router.name":"r-18165-VM"},"wait":30}}] }
> > 2013-02-14 10:53:39,876 DEBUG [agent.manager.AgentAttache]
> > (RouterStatusMonitor-1:null) Seq 14-1794713256: Cancelling.
> > 2013-02-14 10:53:39,877 WARN  [agent.manager.AgentManagerImpl]
> > (RouterStatusMonitor-1:null) Operation timed out: Commands 1794713256
> > to
> > Host 14 timed out after 30
> > 2013-02-14 10:53:39,877 WARN
> > [network.router.VirtualNetworkApplianceManagerImpl]
> > (RouterStatusMonitor-1:null) Unable to update router r-18165-VM's VPN
> > connection status
> > 2013-02-14 10:53:39,879 DEBUG [agent.manager.DirectAgentAttache]
> > (DirectAgent-20:null) Seq 14-1794713202: Response Received:
> > 2013-02-14 10:53:39,880 DEBUG [agent.transport.Request]
> > (DirectAgent-20:null) Seq 14-1794713202: Processing:  { Ans: , MgmtId:
> > 165013918770818, via: 14, Ver: v1, Flags: 110,
> > [{"SetupGuestNetworkAnswer":{"result":false,"details":"Can not find vif
> > with mac 02:00:20:cc:00:08 for VM r-18183-VM","wait":0}}]
> >
> > For info :
> > 172.28.1.1 is the LB tier network (id 240)
> > 172.28.2.1 is a tier network without LB (id 239)
> > 172.28.3.1 is a tier network without LB (id 241)
> >
> > Finally, i get the network 239 remounted as eth2 (172.28.2.1) into vpc
> > vr,
> > but no way to get back the others (240 and 241)
> >
> > The log entries show errors when trying to reboot others networks (also
> > when i rebooted the network with the UI dashboard, i finaly got an
> > error
> > pop message).
> >
> > Thanks for your help.
> >
> > Regards, Benoit.
> >
> >
> >
> > 2013/2/13 Anthony Xu <[email protected]>
> >
> > > Do you reboot VR through CloudStack UI or through hypervisor directly
> > or
> > > inside VR?
> > > Only reboot VR through CloudStack UI/API will trigger CloudStack to
> > hot
> > > plug tier's NICs and reapply all rules
> > >
> > > Anthony
> > >
> > > > -----Original Message-----
> > > > From: benoit lair [mailto:[email protected]]
> > > > Sent: Wednesday, February 13, 2013 9:43 AM
> > > > To: [email protected]
> > > > Subject: VPC bug - no more vlan interfaces after reboot
> > > >
> > > > Hi,
> > > >
> > > > I'm using a cs 4.0.0 deployment. I'm testing the VPC features.
> > > >
> > > > I've created a vpc with 3 tiers networks.
> > > >
> > > > I deployed 1 vm per tier network.
> > > >
> > > > My master CIDR is 172.28.0.0/16
> > > >
> > > > I created the tier1 : 172.28.1.1/24 with LB network offering
> > > > tier2 : 172.28.2.1/24
> > > > tier3 : 172.28.3.1/24
> > > >
> > > > When i create each vm, i got one interface created onto the vpc vr,
> > one
> > > > for
> > > > the tier1, one for the tier2 and one for the tier3.
> > > >
> > > > All seems to be okay, but if i reboot my vpc vr, all i have if i do
> > an
> > > > ifconfig is the control interface (169.254.0.193), the public
> > interface
> > > > (10.14.10.36) and the localhost interface one, but i have no more
> > other
> > > > interfaces concerning the tiers networks.
> > > >
> > > > How can i ragain access to my differents vlans and so my differents
> > > > vms ?
> > > >
> > > >
> > > > Thanks for any response.
> > > >
> > > > Regards, Benoit Lair.
> > >
>

Reply via email to