You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Antoine Boucher <an...@haltondc.com> on 2023/02/28 03:03:04 UTC

SSVM unable to connect to SecStorage via Storage Network

Following to my previous message I have decided to simplify my observations.

Looking at the SSVM network and routing.  My storage ip is defined on eth3 but the routing of the storage subnet is configured via eth1, the Management Network.

Is this an oversight or a desired behaviour?  The only way to solve the issue is for me to use the Management Network for SecStorage or change the routing through eth3. 

I’m assuming that this issue has been reported a number of times?

Regards,
Antoine

Re: SSVM unable to connect to SecStorage via Storage Network

Posted by Antoine Boucher <an...@haltondc.com>.
Yes,

Physical 1
Management is on cloudbr0
Storage on cloubr53

Physical 2
Guest and Public on cloudbr1





> On Feb 27, 2023, at 10:11 PM, Simon Weller <si...@gmail.com> wrote:
> 
> Antoine,
> 
> When you defined the  zone, did you place storage on its own traffic label?
> 
> Could you share your zone network config, along with your traffic labels
> and the associated services on each label?
> 
> -Si
> 
> On Mon, Feb 27, 2023, 9:03 PM Antoine Boucher <an...@haltondc.com> wrote:
> 
>> Following to my previous message I have decided to simplify my
>> observations.
>> 
>> Looking at the SSVM network and routing.  My storage ip is defined on eth3
>> but the routing of the storage subnet is configured via eth1, the
>> Management Network.
>> 
>> Is this an oversight or a desired behaviour?  The only way to solve the
>> issue is for me to use the Management Network for SecStorage or change the
>> routing through eth3.
>> 
>> I’m assuming that this issue has been reported a number of times?
>> 
>> Regards,
>> Antoine
>> 
>>

Re: SSVM unable to connect to SecStorage via Storage Network

Posted by Simon Weller <si...@gmail.com>.
Antoine,

When you defined the  zone, did you place storage on its own traffic label?

Could you share your zone network config, along with your traffic labels
and the associated services on each label?

-Si

On Mon, Feb 27, 2023, 9:03 PM Antoine Boucher <an...@haltondc.com> wrote:

> Following to my previous message I have decided to simplify my
> observations.
>
> Looking at the SSVM network and routing.  My storage ip is defined on eth3
> but the routing of the storage subnet is configured via eth1, the
> Management Network.
>
> Is this an oversight or a desired behaviour?  The only way to solve the
> issue is for me to use the Management Network for SecStorage or change the
> routing through eth3.
>
> I’m assuming that this issue has been reported a number of times?
>
> Regards,
> Antoine
>
>