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

VDOM Interface not visible in Routing Table

Hey Guys,

 

I'm using FortiGate 100F with v6.2.2 build6083 (GA). I added a new interface to a VDOM, put it in a VLAN, gave an IP and enabled it.

 

After that i tryed to ping the interface form the vlan. but it failed! I checked the routing tables and saw that the interface was no listed under the connected routes. 

 

did i miss something or is this a bug? this is a simple L2 connection nothing fancy...

 

Thanks in advance!

 

rafael

thanks in advanced Rafael

thanks in advanced Rafael
2 REPLIES 2
emnoc
Esteemed Contributor III

Did you check the  logs ? Also is  this a ACT-STD cluster and if vcluster is being used, you need to be on the active node for that vdom. So check the 2nd node in the cluster.

 

The diag debug flowwould also be helpful in diagnostics.

 

PCNSE 

NSE 

StrongSwan  

PCNSE NSE StrongSwan
dudarra
New Contributor

Hi emnoc,

 

i downloaded the debug log and saw this;

 

### diagnose ip router command show show int

Interface lo Hardware is Loopback index 1 link 0 metric 1 mtu 16436 <LOOPBACK> <3> VRF Binding: Not bound input packets 0, bytes 0, dropped 0, multicast packets 0 input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0 output packets 0, bytes 0, dropped 0 output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0 collisions 0 Interface dummy0 Hardware is Ethernet, address is 9acb.faa9.4127 index 2 link 0 metric 1 mtu 1500 <BROADCAST,NOARP> <3> VRF Binding: Not bound input packets 0, bytes 0, dropped 0, multicast packets 0 input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0 output packets 0, bytes 0, dropped 0 output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0 collisions 0 Interface nturbo_rx Hardware is Ethernet, address is 0000.0000.0000 index 3 link 0 metric 1 mtu 1500 <BROADCAST,MULTICAST> <3> VRF Binding: Not bound input packets 0, bytes 0, dropped 0, multicast packets 0 input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0 output packets 0, bytes 0, dropped 0 output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0 collisions 0 Interface nturbo_tx Hardware is Ethernet, address is 0000.0000.0000 index 4 link 0 metric 1 mtu 1500 <BROADCAST,MULTICAST> <3> VRF Binding: Not bound input packets 0, bytes 0, dropped 0, multicast packets 0 input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0 output packets 0, bytes 0, dropped 0 output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0 collisions 0 Interface T_V13_LOGG Hardware is Ethernet, address is 0009.0f09.0012 index 80 link 0 metric 1 mtu 1500 <UP,BROADCAST,RUNNING,MULTICAST> <2001> VRF Binding: Not bound inet 10.65.111.5/28 broadcast 10.65.111.15/28 input packets 0, bytes 0, dropped 0, multicast packets 0 input errors 0, length 0, overrun 0, CRC 0, frame 0, fifo 0, missed 0 output packets 0, bytes 0, dropped 0 output errors 0, aborted 0, carrier 0, fifo 0, heartbeat 0, window 0 collisions 0

 

 

the interface is showed there! but why? does it look like a loopback?

 

Raffa

thanks in advanced Rafael

thanks in advanced Rafael
Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors