Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
bluephoenix71
New Contributor

Fortigate 100D - How to see the mac-address of interfaces

Hi,

 

What command in gui or cli should I follow in order to see the mac-address of each interface of the fortigate firewall 100D?

 

Like show arp, then show mac-address in a cisco switch.

 

 

Thanks,

2 Solutions
Dave_Hall

bluephoenix71 wrote:

Hi I get to see the ip address but it's mostly the VIP or HSRP ip of the core switch...

 

Hi Blue. I don't think you will find a complete single list/page showing the MAC Address of all the Interfaces.  On the GUI you can find the MAC Address listed behind the Interface name (see pic). 

 

 

emnoc has already provided the CLI commands to get the mac address, which is diag  hardware deviceinfo nic <name>.  Use ? in place of <name> to get a list of interfaces.

 

If you just want the MAC-Address for an interface, use: diag hardware deviceinfo nic <name> | grep HWaddr

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

View solution in original post

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
AndreaSoliva
Contributor III

Hi

 

what has to be noted in this comunication is following:

 

ARP entries on a FortiGate configured as whatever on a physical interface can be seen with the corresponding commands shown here like:

 

# get sys arp

# diagnose ip arp list

 

ARP entries like VIP ones CAN NOT BE SEEN on the arp list because they are existing in the firewall deamon on layer 4. Example: if you have one public IP on the wan1 and it is physical configured you will see the arp no problem. If you use no a second one and you DO NOT configure the second one as secondary IP on the wan1 (not needed) but instead you configure a VIP based on the second one all works from scratch as long as the second public IP is routed to the wan1 from outsite perspective. If you look to the arp tabel you will NOT see the arp entry for the second public IP because the VIP which has enabled "arp-reply yes" is existing in layer 4 or within the firewall deamon and because of this you will not see a corresponding entry in the command shown here. All commands shown here are based on layer 2 and therefore firewall deamon layer 4 arp entries you will never see. As of information of the Support of Fortinet there is no possibility or a available command which shows this entries.

 

By the way the same issue/situation we have for routing entries depending client2site (dial-up). This means acutally following: If you create a dial-up and you define for this connection a Office IP Pool  (actually a dhcp server which gives after succesfull authentication a IP to the connecting client) you do not have actually to route this Office IP Pool to the IPSec client2site VPN because this entry is done within the IPSec deamon. Of course you can create a static entry which I really recommend because also here the routing is existing within IPSec deamon on layer 4 you will never see the routing entry on layer 3 with the corresponding routing command like:

 

# diagnose ip route list

 

Also here based on the information of Fortinet Support there is no command which shows the  routing based on layer 4. This circumstances that the dial-up VPN Office Pool has not to be anymore routed and in the background the routing entry is automatically done within the IPSec deamon is for FortiOS 5.0 and higher.

 

hope this helps

 

have fun....

 

Andrea

 

 

View solution in original post

17 REPLIES 17
emnoc
Esteemed Contributor III

The best cmd;

 

diag  hardware deviceinfo nic <name>

 

or

 

get hardware nic port  <name>

 

 

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
bluephoenix71

This command will not affect the box?  I mean do I need to issue this command during non-business hours?

 

emnoc wrote:

The best cmd;

 

diag  hardware deviceinfo nic <name>

 

or

 

get hardware nic port  <name>

 

 

ede_pfau
SuperUser
SuperUser

Methinks you are looking for the arp table, not the FGT's interfaces' MAC addresses (which can be easily seen in the GUI):

gate # get sys arp
Address Age(min) Hardware Addr Interface
192.168.234.11 0 00:1a:4d:48:35:8f internal
192.168.234.99 0 00:01:e6:03:0b:1f internal

Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
bluephoenix71

I am looking for the mac-address of each wan interface on the firewall.

 

ede_pfau wrote:

Methinks you are looking for the arp table, not the FGT's interfaces' MAC addresses (which can be easily seen in the GUI):

gate # get sys arp
Address Age(min) Hardware Addr Interface
192.168.234.11 0 00:1a:4d:48:35:8f internal
192.168.234.99 0 00:01:e6:03:0b:1f internal

patrick_z

Hi,

 

get hardware nic wan1

with get hardware nic ?

you will get a list of all interfaces you have.

It's save and you can do that any time!

 

Cheers, Patrick

bluephoenix71

Hi I get to see the ip address but it's mostly the VIP or HSRP ip of the core switch...

 

patrick z wrote:

Hi,

 

get hardware nic wan1

with get hardware nic ?

you will get a list of all interfaces you have.

It's save and you can do that any time!

 

Cheers, Patrick

Dave_Hall

bluephoenix71 wrote:

Hi I get to see the ip address but it's mostly the VIP or HSRP ip of the core switch...

 

Hi Blue. I don't think you will find a complete single list/page showing the MAC Address of all the Interfaces.  On the GUI you can find the MAC Address listed behind the Interface name (see pic). 

 

 

emnoc has already provided the CLI commands to get the mac address, which is diag  hardware deviceinfo nic <name>.  Use ? in place of <name> to get a list of interfaces.

 

If you just want the MAC-Address for an interface, use: diag hardware deviceinfo nic <name> | grep HWaddr

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C

NSE4/FMG-VM64/FortiAnalyzer-VM/6.0 (FWF30E/FW92D/FGT200D/FGT101E/FGT81E)/ FAP220B/221C
bluephoenix71

Hi all,

Thanks for the commands, I can see 2 mac-addresses on port15 and port 16

fwb01 # get hardware nic port15 | grep -A 2 "Current" Current_HWaddr 08:5b:0e:5d:33:12 Permanent_HWaddr 08:5b:0e:5d:33:12

 

fwb01 # get hardware nic port16 | grep -A 2 "Current" Current_HWaddr 08:5b:0e:5d:33:13 Permanent_HWaddr 08:5b:0e:5d:33:13

 

Now, what I need to is to exactly trace what port port 15 and port 16 connects to the switch, in this case a cisco switch.

 

If I do a show mac address-table add on core-sw1, I can see that it's in g4/21.

COR-1# show mac address-table add 08:5b:0e:5d:33:12 Unicast Entries vlan mac address type protocols port -------+---------------+--------+---------------------+-------------------- 108 085b.0e5d.3312 dynamic ip GigabitEthernet4/21

 

BUT...if I trace the second mac-address it is not showing on both core switches...

 

COR-1# show mac address-table add 08:5b:0e:5d:33:13 No entries present.

COR-2# sh mac add add 08:5b:0e:5d:33:13 No entries present.

 

Now, port 15 and 16 are configured as bonded or only having one IP address.

How can I now see what port in core-sw1 or core-sw2 is connected to fortigate por16?  Do I really need someone physically onsite to trace this??

 

Thanks,

 

 

 

Dave Hall wrote:

bluephoenix71 wrote:

Hi I get to see the ip address but it's mostly the VIP or HSRP ip of the core switch...

 

Hi Blue. I don't think you will find a complete single list/page showing the MAC Address of all the Interfaces.  On the GUI you can find the MAC Address listed behind the Interface name (see pic). 

 

[attachImg]https://forum.fortinet.com/download.axd?file=0;120904&where=message&f=Interface Mac Address.jpg[/attachImg]

 

emnoc has already provided the CLI commands to get the mac address, which is diag  hardware deviceinfo nic <name>.  Use ? in place of <name> to get a list of interfaces.

 

If you just want the MAC-Address for an interface, use: diag hardware deviceinfo nic <name> | grep HWaddr

Shawn_W

bump

Labels
Top Kudoed Authors