Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3462

February 10th, 2016 13:00

How to determine MAC address of WAN interface on physical RPA via CLI?

I am troubleshooting an issue at a remote site where I believe that the WAN interface on one of our RPAs has had it's switchport set to the wrong VLAN. I am trying to find the MAC address of the interface from within the CLI but am having no luck. Is there a way for me to do this?

18 Posts

February 10th, 2016 15:00

Hi trev2hi,

You should be able to get the MAC address from the RPA by doing the following depending on the version of RP you have:

  • SSH to the RPA in question as boxmgmt
    • username: boxmgmt
    • password: boxmgmt
  • Option 3 - Diagnostics
  • Option 1 - IP Diagnostics
  • Option 2 - View IP details

This is the equivalent of an ifconfig and should show you the interface along with HWaddr (MAC) address. You would want to locate the interface that relates to your WAN interface.

This is a sample output from my test vRPA on my lapcolor: #ff0000;">[3] Diagnostics

[4] Cluster operations

[5] Shutdown / Reboot operations

Quit

Chris-Test RPA 1: 3

** Diagnostics **

[1] IP diagnostics

[2] SAN diagnostics

[3] Synchronization diagnostics

[4] Collect system information

Main Menu

Back

Quit

Chris-Test RPA 1: 1

** IP diagnostics **

[1] Cluster connectivity tests

[2] View IP details

[3] View routing table

[4] Ports diagnostics

[5] System connectivity

Main Menu

Back

Quit

Chris-Test RPA 1: 2

eth0      Link encap:Ethernet  HWaddr 00:0c:29:29:cf:a5

          inet addr:192.168.136.132  Bcast:192.168.136.255  Mask:255.255.255.0

          inet6 addr: fe80::20c:29ff:fe29:cfa5/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2702 errors:0 dropped:0 overruns:0 frame:0

          TX packets:1234 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:250118 (244.2 KiB)  TX bytes:134871 (131.7 KiB)

eth0:1    Link encap:Ethernet  HWaddr 00:0c:29:29:cf:a5

          inet addr:10.77.77.77  Bcast:10.77.77.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 00:0c:29:29:cf:af

          inet addr:192.168.136.130  Bcast:192.168.136.255  Mask:255.255.255.0

          inet6 addr: fe80::20c:29ff:fe29:cfaf/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:3546 errors:0 dropped:0 overruns:0 frame:0

          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:317488 (310.0 KiB)  TX bytes:2250 (2.1 KiB)

eth2      Link encap:Ethernet  HWaddr 00:0c:29:29:cf:b9

          inet addr:192.168.136.150  Bcast:192.168.136.255  Mask:255.255.255.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth3      Link encap:Ethernet  HWaddr 00:0c:29:29:cf:c3

          inet addr:192.168.136.151  Bcast:192.168.136.255  Mask:255.255.255.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

5 Posts

February 10th, 2016 16:00

Thanks, I'm not sure how I missed that. Much appreciated.

No Events found!

Top