Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Anyone used vrack at OVH?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Anyone used vrack at OVH?

GalaxyHostPlusGalaxyHostPlus Member
edited April 2016 in Providers

Hello,

I'm trying to set vrack 1.5 on OVH but seems there is issue with it.
I have followed http://help.ovh.com/VrackInfrastructureServer but vrack keep getting disconnected and timeout.

Vrack is used for OpenVZ

This is my setup

ifcfg-eth1

BOOTPROTO=static

>

IPADDR=xxx.xx.xxx.169

>

NETMASK=255.255.255.248

>

ONBOOT=yes

>

BROADCAST=xxx.xx.xxx.175

>

DEVICE=eth1

rule-eth1

from xxx.xx.xxx.168/29 table 125

route-eth1

default via xxx.xx.xxx.175 dev eth1 table 125

And for eth1:0 I have up to eth1:2

BOOTPROTO=static

>

IPADDR=xx.xxx.xx.176

>

NETMASK=255.255.255.240
ONBOOT=yes
BROADCAST=xx.xxx.xx.xxx

And set all the same for route-eth1:0 rule-eth1:0 as before.

The issue is

Reply from xx.xxx.xxx.134: bytes=32 time=37ms TTL=58

>

Reply from xx.xxx.xxx.134: bytes=32 time=35ms TTL=58

>

Request timed out.

>

Request timed out.

>

Request timed out.

>

Request timed out.

>

Request timed out.

>

Request timed out.

>

Request timed out.

>

Reply from xx.xxx.xxx.134: bytes=32 time=35ms TTL=58

>

Reply from xx.xxx.xxx.134: bytes=32 time=34ms TTL=58

>

Reply from xx.xxx.xxx.134: bytes=32 time=42ms TTL=58

Or network goes down and never come back.

I never expected such issues with other DCs so not sure if it's configuration issue or something related to OVH.

Anyone else had such issue with OVH already opend ticket with OVH but that probably will take some time.

Comments

  • AshleyUkAshleyUk Member

    What IP's are you using for the two eth1 interfaces? Are they from an OVH IP block?

    Or is one a local IP?

    Thanked by 1GalaxyHostPlus
  • century1stopcentury1stop Member
    edited April 2016

    gateway seems to be wrong, should be xxx.xxx.xxx.175 (2nd last IP), broadcast xxx.xxx.xxx.176 (last IP)
    routing table in place?

    Thanked by 1GalaxyHostPlus
  • GalaxyHostPlusGalaxyHostPlus Member

    @AshleyUk said:
    What IP's are you using for the two eth1 interfaces? Are they from an OVH IP block?

    Or is one a local IP?

    We are using IP blocks from OVH as the OVH tutorial shown.

    Haven't really tried with private IPs I will give ago maybe that's the issue I skipped.

    @century1stop said:
    gateway seems to be wrong, should be xxx.xxx.xxx.175 (2nd last IP), broadcast xxx.xxx.xxx.176 (last IP)

    I have changed moment ago to 174 from 175 to test but gives same results with timeout.

  • century1stopcentury1stop Member

    routing table in place? can you ping the gateway .175?

    Thanked by 1GalaxyHostPlus
  • GalaxyHostPlusGalaxyHostPlus Member

    @century1stop said:
    routing table in place? can you ping the gateway .175?

    Yes I can Ping gateway as ping is back right now.

    I have set eth1 as local for vrack atm ping seems to be back.
    Normally it goes down after 6 hours so I will monitor it right now.

    Thanks for help everyone I will let in next 6 hours if new config is working :)

  • GalaxyHostPlusGalaxyHostPlus Member

    Hmm still vrack getting disconnected and timeout even with local connection. Looks like vrack issue as now can't get Ping back at all with same settings also nothing was changed from last 12 hours.

  • AshleyUkAshleyUk Member
    edited April 2016

    @GalaxyHostPlus said:
    Hmm still vrack getting disconnected and timeout even with local connection. Looks like vrack issue as now can't get Ping back at all with same settings also nothing was changed from last 12 hours.

    Id suggest to test if vRACK issue or config issue.

    Create a eth1 network device with the following :

    DEVICE=eth1
    BOOTPROTO=static
    IPADDR=172.16.0.10
    NETMASK=255.240.0.0
    ONBOOT=yes

    Removing any other network config apart from the standard eth0.

    If you then have another server on vRACK (I guess the point of having this server on vRACK), setup this with the same config apart from .11

    Then test if you can keep a ping running between the two servers, if this does not drop then the issue is with your config when you are then using an IPBlock.

    Stupid question but you have moved the IP Block to the vRACK in question?

  • GalaxyHostPlusGalaxyHostPlus Member
    edited April 2016

    @AshleyUk said:

    Sadly I have only x1 Server which support Vrack, My clients requires more IPs so vrack is required in this cause.

    IPs and server are moved in Ovh manager in Network settings.

    But it strange network was working non stop 4 h and than disconnected with no reason now ping is back for few sec and again same happens.

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Reply from xx.xxx.xx.188: bytes=32 time=36ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=37ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=397ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=34ms TTL=53

    >

    Reply from xx.xxx.xx.188: bytes=32 time=35ms TTL=53

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    >

    Request timed out.

    Probably best would be call OVH tomorrow at 9am let their tech look into this as if network works sometimes config seems to be fine just connection is lost from vrack

    Also on ifconfig eth1

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:416150924 errors:1904 dropped:0 overruns:311 frame:1904
      TX packets:368454110 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:140299742986 (130.6 GiB)  TX bytes:168831893608 (157.2 GiB)
      Memory:fb100000-fb11ffff

    There seems some errors so I will look into this now.

  • AshleyUkAshleyUk Member

    Feel free to PM me all your config files and I will give a quick check over them make sure nothing obvious before you chase OVH further.

  • century1stopcentury1stop Member

    did you setup "table 125"?

  • GalaxyHostPlusGalaxyHostPlus Member

    @century1stop said:
    did you setup "table 125"?

    We did, AshleyUk give us new way to do it atm we working to make it working so far we got gateway ping working we trying to make OpenVZ VPS working now on this network

  • GalaxyHostPlusGalaxyHostPlus Member

    Seems like OVH Vrack don't support OpenVZ network with venet

  • century1stopcentury1stop Member

    is your ovz node setup in vrack?

  • GalaxyHostPlusGalaxyHostPlus Member

    @century1stop said:
    is your ovz node setup in vrack?

    It was originally installed with eth0 after we are trying to add vrack but seems not working can't find solution on google either

  • century1stopcentury1stop Member

    vrack works with any NIC including dummy

  • linuxthefishlinuxthefish Member

    Never got it working for me either.

  • GalaxyHostPlusGalaxyHostPlus Member
    edited April 2016

    Seems we got it working.

    We have set in vz.conf eth1 as main Interface and restarted the vz

    Also added

    net.ipv4.conf.eth1.rp_filter = 2
net.ipv6.conf.eth1.disable_ipv6 = 1
net.ipv4.conf.eth1.proxy_arp = 1
net.ipv4.conf.eth1.forwarding = 1

    to sysctl.conf

    We will monitor it for next 6 h if it will go down or not.

  • AshleyUkAshleyUk Member
    edited April 2016

    @GalaxyHostPlus said:
    Seems we got it working.

    We have set in vz.conf eth1 as main Interface and restarted the vz

    Also added

    net.ipv4.conf.eth1.rp_filter = 2
net.ipv6.conf.eth1.disable_ipv6 = 1
net.ipv4.conf.eth1.proxy_arp = 1
net.ipv4.conf.eth1.forwarding = 1

    to sysctl.conf

    We will monitor it for next 6 h if it will go down or not.

    Did say in my PM you need to set eth1 as the main interface for openvz, as you have no routes you need to force traffic down the vRack port.

    Glad you have it working.

    Thanked by 1GalaxyHostPlus
  • GalaxyHostPlusGalaxyHostPlus Member

    @AshleyUk said:
    Glad you have it working.

    Thanks :)
    We still using the assign IP method eth1:xx as other method with local IP don't work.
    We will see if its fixed as normally vrack goes down after 4h sometime after few seconds we are monitoring atm but hope that was the issue and its fixed :)

  • GalaxyHostPlusGalaxyHostPlus Member

    Still vrack disconnected with no reason I will call OVH today about it.

Sign In or Register to comment.