| Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
| 5 | Troubleshooting |
| 6 | =============== |
| 7 | |
| 8 | Unknown MAC addresses |
| 9 | --------------------- |
| 10 | |
| 11 | Sometimes it's hard to find out all the MAC addresses assigned to network |
| 12 | cards. These can be found in a variety of ways: |
| 13 | |
| 14 | 1. On servers, the BMC webpage will list the built-in network card MAC |
| 15 | addresses. |
| 16 | |
| 17 | 2. If you login to a server, ``ip link`` or ``ip addr`` will show the MAC |
| 18 | address of each interface, including on add-in cards. |
| 19 | |
| 20 | 3. If you can login to a server but don't know the BMC IP or MAC address for |
| 21 | that server, you can find it with ``sudo ipmitool lan print``. |
| 22 | |
| 23 | 4. If you don't have a login to the server, but can get to the management |
| 24 | server, ``ip neighbor`` will show the arp table of MAC addresses known to |
| 25 | that system. It's output is unsorted - ``ip neigh | sort`` is easier to |
| 26 | read. |
| 27 | |
| 28 | Cabling issues |
| 29 | -------------- |
| 30 | |
| 31 | The system may not come up correctly if cabling isn't connected properly. |
| 32 | If you don't have hands-on with the cabling, here are some ways to check on the |
| 33 | cabling remotely: |
| 34 | |
| 35 | 1. On servers you can check which ports are connected with ``ip link show``:: |
| 36 | |
| 37 | $ ip link show |
| 38 | ... |
| 39 | 3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 |
| 40 | link/ether 3c:ec:ef:4d:55:a8 brd ff:ff:ff:ff:ff:ff |
| 41 | ... |
| 42 | 5: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 |
| 43 | link/ether 3c:ec:ef:4d:55:a9 brd ff:ff:ff:ff:ff:ff |
| 44 | |
| 45 | Ports that are up will show ``state UP`` |
| 46 | |
| 47 | 2. You can determine which remote ports are connected with LLDP, assuming that |
| 48 | the remote switch supports LLDP and has it enabled. This can be done with |
| 49 | ``networkctl lldp``, which shows both the name and the MAC address of the |
| 50 | connected switch on a per-link basis:: |
| 51 | |
| 52 | $ networkctl lldp |
| 53 | LINK CHASSIS ID SYSTEM NAME CAPS PORT ID PORT DESCRIPTION |
| 54 | eno1 10:4f:58:e7:d5:60 Aruba-2540-24…PP ..b........ 10 10 |
| 55 | eno2 10:4f:58:e7:d5:60 Aruba-2540-24…PP ..b........ 1 1 |