From: Leandro Roggerone <leandro@tecnetmza.com.ar>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] link down for network interface
Date: Fri, 9 Apr 2021 08:20:59 -0300 [thread overview]
Message-ID: <CALt2oz7TF6_BKzTW3JYHBYg4040vkE=Qdcs8_ZsxFBbiS-Jk5A@mail.gmail.com> (raw)
In-Reply-To: <20210407220319.snhtabanjxcjfl6w@percival.namespace.at>
Veeeery strange.
After removing the vlan aware flag on the interface configuration could get
the link up.
Fortunately I have a second nic on this server so I will use it instead.
Have not much time to debug this.
Thanks.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
El mié, 7 abr 2021 a las 19:04, Chris Hofstaedtler | Deduktiva (<
chris.hofstaedtler@deduktiva.com>) escribió:
> * Leandro Roggerone <leandro@tecnetmza.com.ar> [210407 17:25]:
> > Hi guys ...
> Please consider that more than one gender exists.
>
> > Yesterday was working on my datacenter cabling my new proxmox network
> > interfaces.
> > I connected a network port to my mikrotik router.
> > Before coming home I checked network linked condition and physically was
> ok
> > , both leds blinking on both side , router and server nic. (eno1)
> > Now , working remotely can see that server interface has no link.
> > Very strange since interface at router is up.
> > Any idea ? I never seen something similar (one side link ok and the
> other
> > is down).
>
> > root@pve2:~# ip link
> [..]
> > 4: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master
> vmbr2
> > state DOWN mode DEFAULT group default qlen 1000
> > link/ether 40:a8:f0:2a:18:80 brd ff:ff:ff:ff:ff:ff
> >
> > as you can see eno1 is down ... while can see link up on the other
> > connected side.
>
> You did not tell us the brand and make or driver of that network
> card. Some Intel cards are known to be extremely picky about autoneg
> and power save settings, (short) cables, etc.
>
> Best luck,
> Chris
>
> --
> Chris Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien)
> www.deduktiva.com / +43 1 353 1707
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
>
prev parent reply other threads:[~2021-04-09 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:25 Leandro Roggerone
2021-04-07 22:03 ` Chris Hofstaedtler | Deduktiva
2021-04-09 11:20 ` Leandro Roggerone [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALt2oz7TF6_BKzTW3JYHBYg4040vkE=Qdcs8_ZsxFBbiS-Jk5A@mail.gmail.com' \
--to=leandro@tecnetmza.com.ar \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox