From: Leandro Roggerone <leandro@tecnetmza.com.ar>
To: PVE User List <pve-user@pve.proxmox.com>
Subject: [PVE-User] link down for network interface
Date: Wed, 7 Apr 2021 12:25:16 -0300 [thread overview]
Message-ID: <CALt2oz58fYYZSGwgCMops2Phh2q9SiYmproaE-SrTwj2+Ozyvg@mail.gmail.com> (raw)
Hi guys ...
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).
Here can I share some outputs:
root@pve2:~# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0
state UP mode DEFAULT group default qlen 1000
link/ether a0:d3:c1:f5:37:08 brd ff:ff:ff:ff:ff:ff
3: ens2f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1
state UP mode DEFAULT group default qlen 1000
link/ether a0:d3:c1:f5:37:09 brd ff:ff:ff:ff:ff:ff
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
5: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr3
state DOWN mode DEFAULT group default qlen 1000
as you can see eno1 is down ... while can see link up on the other
connected side.
I will change cable tomorrow, but wanted to share this experience with you.
BTW , already tryed autonegociation , and fixed 100, 1000Mb.
Regards.
Leandro.
<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>
next reply other threads:[~2021-04-07 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:25 Leandro Roggerone [this message]
2021-04-07 22:03 ` Chris Hofstaedtler | Deduktiva
2021-04-09 11:20 ` Leandro Roggerone
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=CALt2oz58fYYZSGwgCMops2Phh2q9SiYmproaE-SrTwj2+Ozyvg@mail.gmail.com \
--to=leandro@tecnetmza.com.ar \
--cc=pve-user@pve.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