RE: ssvm NFS public ip

2018-04-13 Thread Nicolas Bouige
Hi Swatisk,


Yep, here the repo/url :


KVM  (centos7):

[cloudstack]
name=cloudstack
baseurl=http://cloudstack.apt-get.eu/centos/7/4.11/
enabled=1
gpgcheck=0

MGMT-SRV (centos7) :

[cloudstack]
name=cloudstack
baseurl=http://cloudstack.apt-get.eu/centos/7/4.11/
enabled=1
gpgcheck=0

Systemvm-template :

http://cloudstack.apt-get.eu/systemvm/4.11/systemvmtemplate-4.11.0-kvm.qcow2.bz2


Best regards,
N.B



De : Swastik Mittal <mittal.swas...@gmail.com>
Envoyé : vendredi 13 avril 2018 10:19:03
À : users@cloudstack.apache.org
Objet : Re: ssvm NFS public ip

Hey Nicolas,

Can you mention the urls's you used finally to get everything working.

Regards
Swastik
<https://mailtrack.io/> Sent with Mailtrack
<https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail_medium=signature_campaign=signaturevirality>

On Thu, Apr 12, 2018 at 3:10 PM, Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> Hello All,
>
> With this new deployement my ssvm is now okay.
> I saw my mistake...the URLs were good for mgmt and systemvm template...but
> not for the cloudstack-agent installed on KVM...
>
> Best regards,
>
> N.B
>
> -Message d'origine-
> De : Nicolas Bouige [mailto:n.bou...@dimsi.fr]
> Envoyé : jeudi 12 avril 2018 09:56
> À : users@cloudstack.apache.org
> Objet : RE: ssvm NFS public ip
>
> Hi Paul,
>
> I used repository from shapeblue for mgmt-server and systemvm-template.
> Im going to make a new fresh install (again :/) and double check the URL.
>
> Thanks,
>
> Best regards,
> N.B
>
>
> -Message d'origine-
> De : Paul Angus [mailto:paul.an...@shapeblue.com] Envoyé : jeudi 12 avril
> 2018 09:12 À : users@cloudstack.apache.org Objet : RE: ssvm NFS public ip
>
> Hi Nicolas, this usually happens if you mix redist and noredist builds of
> mgmt. server and system vm code.
>
> What URLs did you use for the management server repo and the system VM
> templates?
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com<http://www.shapeblue.com>
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -Original Message-
> From: Nicolas Bouige <n.bou...@dimsi.fr>
> Sent: 11 April 2018 19:44
> To: users@cloudstack.apache.org
> Subject: RE: ssvm NFS public ip
>
> Hi ilya,
>
>
> Thanks for your answer
>
> Yes i did it already with no effect :/
>
>
> Best regards,
>
> N.B
>
> 
> De : ilya musayev <ilya.mailing.li...@gmail.com> Envoyé : mercredi 11
> avril 2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS
> public ip
>
> There is a global setting you have to set to use internal non public IP.
>
> Try setting sec.storage.allow.internal.site to an internal network cidr.
>
> You may need to destroy ssvm for settings to take effect. In my case there
> is some sort of minor bug where it takes upward of 5 minutes for ssvm to
> program the internal routes, but since this is onetime operation - I just
> live with it.
>
> On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:
>
> > a small update about my problem.
> >
> > I 've recreated the zone from scratch this morning and  one of my
> > "cloudbr" used for the secondary storage was misconfigured.
> >
> > So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM
> > and mount the nfs on them...but...the agent still not going up and the
> > ssvm_check.sh give me an ip public for the nfs instead of the private.
> >
> >
> > i got only this error in /var/log:cloud.log :
> >
> > 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource
> > class not found: com.cloud.storage.resource.
> PremiumSecondaryStorageResource due
> > to: java.lang.ClassNotFoundException:
> > com.cloud.storage.resource.PremiumSecondaryStorageReso
> >   urce
> > Unable to start agent: Resource class not found:
> > com.cloud.storage.resource.Prem
> > iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> > com.cloud.
> > storage.resource.PremiumSecondaryStorageResource
> >
> > i've tried to update a differente systemvm template with no success...
> > I 've compared the configuration of the ssvm with one of our
> > deployment and i juste noticed the "resource"
> > (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not
> > the same.
> > i changed it but still the same error...
> >
> > There is a way to find java binaries/script and  upload them on the ssvm
> ?
> >
> > If one of you have an idea, it would be appreciate.
> >
> > Thanks !
> >
> > Best regards,
> > N.B
> >
> >
>
>


Re: ssvm NFS public ip

2018-04-13 Thread Swastik Mittal
Hey Nicolas,

Can you mention the urls's you used finally to get everything working.

Regards
Swastik
<https://mailtrack.io/> Sent with Mailtrack
<https://chrome.google.com/webstore/detail/mailtrack-for-gmail-inbox/ndnaehgpjlnokgebbaldlmgkapkpjkkb?utm_source=gmail_medium=signature_campaign=signaturevirality>

On Thu, Apr 12, 2018 at 3:10 PM, Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> Hello All,
>
> With this new deployement my ssvm is now okay.
> I saw my mistake...the URLs were good for mgmt and systemvm template...but
> not for the cloudstack-agent installed on KVM...
>
> Best regards,
>
> N.B
>
> -Message d'origine-
> De : Nicolas Bouige [mailto:n.bou...@dimsi.fr]
> Envoyé : jeudi 12 avril 2018 09:56
> À : users@cloudstack.apache.org
> Objet : RE: ssvm NFS public ip
>
> Hi Paul,
>
> I used repository from shapeblue for mgmt-server and systemvm-template.
> Im going to make a new fresh install (again :/) and double check the URL.
>
> Thanks,
>
> Best regards,
> N.B
>
>
> -Message d'origine-
> De : Paul Angus [mailto:paul.an...@shapeblue.com] Envoyé : jeudi 12 avril
> 2018 09:12 À : users@cloudstack.apache.org Objet : RE: ssvm NFS public ip
>
> Hi Nicolas, this usually happens if you mix redist and noredist builds of
> mgmt. server and system vm code.
>
> What URLs did you use for the management server repo and the system VM
> templates?
>
>
>
> paul.an...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
>
>
>
>
> -----Original Message-
> From: Nicolas Bouige <n.bou...@dimsi.fr>
> Sent: 11 April 2018 19:44
> To: users@cloudstack.apache.org
> Subject: RE: ssvm NFS public ip
>
> Hi ilya,
>
>
> Thanks for your answer
>
> Yes i did it already with no effect :/
>
>
> Best regards,
>
> N.B
>
> 
> De : ilya musayev <ilya.mailing.li...@gmail.com> Envoyé : mercredi 11
> avril 2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS
> public ip
>
> There is a global setting you have to set to use internal non public IP.
>
> Try setting sec.storage.allow.internal.site to an internal network cidr.
>
> You may need to destroy ssvm for settings to take effect. In my case there
> is some sort of minor bug where it takes upward of 5 minutes for ssvm to
> program the internal routes, but since this is onetime operation - I just
> live with it.
>
> On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:
>
> > a small update about my problem.
> >
> > I 've recreated the zone from scratch this morning and  one of my
> > "cloudbr" used for the secondary storage was misconfigured.
> >
> > So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM
> > and mount the nfs on them...but...the agent still not going up and the
> > ssvm_check.sh give me an ip public for the nfs instead of the private.
> >
> >
> > i got only this error in /var/log:cloud.log :
> >
> > 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource
> > class not found: com.cloud.storage.resource.
> PremiumSecondaryStorageResource due
> > to: java.lang.ClassNotFoundException:
> > com.cloud.storage.resource.PremiumSecondaryStorageReso
> >   urce
> > Unable to start agent: Resource class not found:
> > com.cloud.storage.resource.Prem
> > iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> > com.cloud.
> > storage.resource.PremiumSecondaryStorageResource
> >
> > i've tried to update a differente systemvm template with no success...
> > I 've compared the configuration of the ssvm with one of our
> > deployment and i juste noticed the "resource"
> > (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not
> > the same.
> > i changed it but still the same error...
> >
> > There is a way to find java binaries/script and  upload them on the ssvm
> ?
> >
> > If one of you have an idea, it would be appreciate.
> >
> > Thanks !
> >
> > Best regards,
> > N.B
> >
> >
>
>


RE: ssvm NFS public ip

2018-04-12 Thread Nicolas Bouige
Hello All,

With this new deployement my ssvm is now okay.
I saw my mistake...the URLs were good for mgmt and systemvm template...but not 
for the cloudstack-agent installed on KVM...

Best regards,

N.B

-Message d'origine-
De : Nicolas Bouige [mailto:n.bou...@dimsi.fr] 
Envoyé : jeudi 12 avril 2018 09:56
À : users@cloudstack.apache.org
Objet : RE: ssvm NFS public ip

Hi Paul,

I used repository from shapeblue for mgmt-server and systemvm-template.
Im going to make a new fresh install (again :/) and double check the URL.

Thanks,

Best regards,
N.B


-Message d'origine-
De : Paul Angus [mailto:paul.an...@shapeblue.com] Envoyé : jeudi 12 avril 2018 
09:12 À : users@cloudstack.apache.org Objet : RE: ssvm NFS public ip

Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 


-Original Message-
From: Nicolas Bouige <n.bou...@dimsi.fr>
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev <ilya.mailing.li...@gmail.com> Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>



RE: ssvm NFS public ip

2018-04-12 Thread Nicolas Bouige
Hi Paul,

I used repository from shapeblue for mgmt-server and systemvm-template.
Im going to make a new fresh install (again :/) and double check the URL.

Thanks,

Best regards,
N.B


-Message d'origine-
De : Paul Angus [mailto:paul.an...@shapeblue.com] 
Envoyé : jeudi 12 avril 2018 09:12
À : users@cloudstack.apache.org
Objet : RE: ssvm NFS public ip

Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue
  
 


-Original Message-
From: Nicolas Bouige <n.bou...@dimsi.fr>
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev <ilya.mailing.li...@gmail.com> Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>



RE: ssvm NFS public ip

2018-04-12 Thread Paul Angus
Hi Nicolas, this usually happens if you mix redist and noredist builds of mgmt. 
server and system vm code.

What URLs did you use for the management server repo and the system VM 
templates?



paul.an...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Nicolas Bouige <n.bou...@dimsi.fr> 
Sent: 11 April 2018 19:44
To: users@cloudstack.apache.org
Subject: RE: ssvm NFS public ip

Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev <ilya.mailing.li...@gmail.com> Envoyé : mercredi 11 avril 
2018 20:26:34 À : users@cloudstack.apache.org Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there is 
some sort of minor bug where it takes upward of 5 minutes for ssvm to program 
the internal routes, but since this is onetime operation - I just live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my 
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM 
> and mount the nfs on them...but...the agent still not going up and the 
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource 
> class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource 
> due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our 
> deployment and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not 
> the same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>



RE: ssvm NFS public ip

2018-04-11 Thread Nicolas Bouige
Hi ilya,


Thanks for your answer

Yes i did it already with no effect :/


Best regards,

N.B


De : ilya musayev <ilya.mailing.li...@gmail.com>
Envoyé : mercredi 11 avril 2018 20:26:34
À : users@cloudstack.apache.org
Objet : Re: ssvm NFS public ip

There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there
is some sort of minor bug where it takes upward of 5 minutes for ssvm to
program the internal routes, but since this is onetime operation - I just
live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige <n.bou...@dimsi.fr> wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM and
> mount the nfs on them...but...the agent still not going up and the
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource class
> not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our deployment
> and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not the
> same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>


Re: ssvm NFS public ip

2018-04-11 Thread ilya musayev
There is a global setting you have to set to use internal non public IP.

Try setting sec.storage.allow.internal.site to an internal network cidr.

You may need to destroy ssvm for settings to take effect. In my case there
is some sort of minor bug where it takes upward of 5 minutes for ssvm to
program the internal routes, but since this is onetime operation - I just
live with it.

On Wed, Apr 11, 2018 at 10:50 AM Nicolas Bouige  wrote:

> a small update about my problem.
>
> I 've recreated the zone from scratch this morning and  one of my
> "cloudbr" used for the secondary storage was misconfigured.
>
> So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM and
> mount the nfs on them...but...the agent still not going up and the
> ssvm_check.sh give me an ip public for the nfs instead of the private.
>
>
> i got only this error in /var/log:cloud.log :
>
> 17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource class
> not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due
> to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageReso
>   urce
> Unable to start agent: Resource class not found:
> com.cloud.storage.resource.Prem
> iumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.
> storage.resource.PremiumSecondaryStorageResource
>
> i've tried to update a differente systemvm template with no success...
> I 've compared the configuration of the ssvm with one of our deployment
> and i juste noticed the "resource"
> (org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not the
> same.
> i changed it but still the same error...
>
> There is a way to find java binaries/script and  upload them on the ssvm ?
>
> If one of you have an idea, it would be appreciate.
>
> Thanks !
>
> Best regards,
> N.B
>
>


RE: ssvm NFS public ip

2018-04-11 Thread Nicolas Bouige
a small update about my problem.

I 've recreated the zone from scratch this morning and  one of my "cloudbr" 
used for the secondary storage was misconfigured.

So Now, I can ping the secondary storage from KVM host, CS-MGMT,  SSVM and 
mount the nfs on them...but...the agent still not going up and the 
ssvm_check.sh give me an ip public for the nfs instead of the private.


i got only this error in /var/log:cloud.log :

17:30:22,600 ERROR AgentShell:477 - Unable to start agent: Resource class not 
found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: 
java.lang.ClassNotFoundException: 
com.cloud.storage.resource.PremiumSecondaryStorageReso  
  urce
Unable to start agent: Resource class not found: 
com.cloud.storage.resource.Prem
iumSecondaryStorageResource due to: java.lang.ClassNotFoundException: 
com.cloud.
storage.resource.PremiumSecondaryStorageResource

i've tried to update a differente systemvm template with no success...
I 've compared the configuration of the ssvm with one of our deployment and i 
juste noticed the "resource" 
(org.apache.cloudstack.storage.resource.NfsSecondaryResource) was not the same.
i changed it but still the same error...

There is a way to find java binaries/script and  upload them on the ssvm ?

If one of you have an idea, it would be appreciate.

Thanks !

Best regards,
N.B



ssvm NFS public ip

2018-04-10 Thread Nicolas Bouige
Hello All,

I' m currently set up a fresh installation of cloucdstack 4.11 on CentOS7/KVM 
server.

All was working good until the systemvm installation...the ssvm is using the 
public ip to contact the nfs instead of the internal ip adresse.
I had this issue before and it was a ip route and/or arp records problem, but 
not this time.

>From ssvm_check script, i got two error

-  NFS not mounted

-  Java process not running

I don't know if the java process error is related to the NFS not mounted.

Here the result  :
First DNS server is  8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=48 time=54.150 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=48 time=45.959 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 45.959/50.055/54.150/4.096 ms
Good: Can ping DNS server

Good: DNS resolves cloudstack.apache.org

ERROR: NFS is not currently mounted
Try manually mounting from inside the VM
NFS server is  77.88.44.225
PING 77.88.44.225 (77.88.44.225): 56 data bytes
64 bytes from 77.88.44.225: icmp_seq=0 ttl=64 time=1.132 ms
64 bytes from 77.88.44.225: icmp_seq=1 ttl=64 time=1.123 ms
--- 77.88.44.225 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.123/1.127/1.132/0.000 ms
Good: Can ping nfs server

Management server is 172.16.22.60. Checking connectivity.
./ssvm-check.sh: line 121: warning: command substitution: ignored null byte in 
input
Good: Can connect to management server port 8250

ERROR: Java process not running.  Try restarting the SSVM.

>From the /var/log/cloud.log, i've noticed this error :
2018-04-10 10:24:22,062 INFO  [cloud.agent.AgentShell] (main:null) Agent started
2018-04-10 10:24:22,066 INFO  [cloud.agent.AgentShell] (main:null) 
Implementation Version is 4.11.0.0
2018-04-10 10:24:22,067 INFO  [cloud.agent.AgentShell] (main:null) 
agent.properties found at /usr/local/cloud/systemvm/conf/agent.properties
2018-04-10 10:24:22,077 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to using properties file for storage
2018-04-10 10:24:22,084 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to the constant time backoff algorithm
2018-04-10 10:24:22,114 INFO  [cloud.utils.LogUtils] (main:null) log4j 
configuration found at /usr/local/cloud/systemvm/conf/log4j-cloud.xml
2018-04-10 10:24:22,168 INFO  [cloud.agent.AgentShell] (main:null) Using 
default Java settings for IPv6 preference for agent connection
2018-04-10 10:24:22,323 ERROR [cloud.agent.AgentShell] (main:null) Unable to 
start agent: Resource class not found: 
com.cloud.storage.resource.PremiumSecondaryStorageResource due to: 
java.lang.ClassNotFoundException: 
com.cloud.storage.resource.PremiumSecondaryStorageResource


>From the host, i've created cloudbr0 (mgmt) and cloudbr1 with a bridge/vlan  
>connected to the secondary storage network.
###ifcfg-cloudbr1
DEVICE=cloudbr1
NM_CONTROLLED=no
TYPE=Bridge
BOOTPROTO=none
ONBOOT=yes
DEFROUTE=yes
ZONE=public

###ifcfg-cloudbr1.103
DEVICE=cloudbr1.103
ONBOOT=yes
TYPE=Bridge
IPADDR=172.16.3.217
NETMASK=255.255.255.0
GATEWAY=172.16.3.254
NM_CONTROLLED=no
BOOTPROTO=static
ZONE=public

###ifcfg-vlan103
VLAN=yes
TYPE=vlan
DEVICE=vlan103
PHYSDEV=teamTRUNK
VLAN_ID=103
NAME=VLAN103
ONBOOT=yes
BRIDGE=cloudbr1.103

###brctl show result###
bridge name bridge id   STP enabled interfaces
brteamTRUNK-500 8000.80c16e791e14   no  teamTRUNK.500

 vnet2

  vnet5
cloud0 8000.fe00a9fe0101   no   
  vnet0

vnet3
cloudbr0 8000.80c16e791e10   no  
teamMGMT

  vnet1

 vnet4
cloudbr1 8000.80c16e791e14   no  
teamTRUNK

  vnet6
cloudbr1.103  8000.80c16e791e14   no  vlan103
virbr0  8000.525400663967   yes virbr0-nic

>From the host i can ping and attached the NFS.

Im running out of idea, any help