Routing problem

Discussion in 'Proxmox VE: Installation and configuration' started by bizzarrone, Nov 29, 2016.

Tags:
  1. bizzarrone

    bizzarrone Member

    Joined:
    Nov 27, 2014
    Messages:
    42
    Likes Received:
    1
    I have routing problem. No one of my VM and CT can go out after the latest upgrade.

    Code:
    root@bluehub-prox02:~# pveversion -v
    proxmox-ve: 4.3-72 (running kernel: 4.4.24-1-pve)
    pve-manager: 4.3-12 (running version: 4.3-12/6894c9d9)
    pve-kernel-4.4.6-1-pve: 4.4.6-48
    pve-kernel-4.4.21-1-pve: 4.4.21-71
    pve-kernel-4.4.24-1-pve: 4.4.24-72
    pve-kernel-4.4.19-1-pve: 4.4.19-66
    lvm2: 2.02.116-pve3
    corosync-pve: 2.4.0-1
    libqb0: 1.0-1
    pve-cluster: 4.0-47
    qemu-server: 4.0-96
    pve-firmware: 1.1-10
    libpve-common-perl: 4.0-83
    libpve-access-control: 4.0-19
    libpve-storage-perl: 4.0-68
    pve-libspice-server1: 0.12.8-1
    vncterm: 1.2-1
    pve-docs: 4.3-17
    pve-qemu-kvm: 2.7.0-8
    pve-container: 1.0-85
    pve-firewall: 2.0-31
    pve-ha-manager: 1.0-38
    ksm-control-daemon: 1.2-1
    glusterfs-client: 3.5.2-2+deb8u2
    lxc-pve: 2.0.6-1
    lxcfs: 2.0.5-pve1
    criu: 1.6.0-1
    novnc-pve: 0.5-8
    smartmontools: 6.5+svn4324-1~pve80
    zfsutils: 0.6.5.8-pve13~bpo80
    
     
  2. bizzarrone

    bizzarrone Member

    Joined:
    Nov 27, 2014
    Messages:
    42
    Likes Received:
    1
    Solved. It was a link agregation configuration server side.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice