Strange problem with trunk interfaces after reboot

[auroranl]

Hello,

On a newly installed SPLAT/R60A firewall. I am using trunks (first time). With sysconfig I created 4 VLAN interfaces in a particular NIC and I configured the switch in trunk mode with the 4 VLANS allowed.

When I boot, or reboot, the system the 'normal' interfaces work fine, however I don't see any 2-way traffic on the trunk interface. I don't receive any ARP response when I try to ping from the firewall.

In a last resort, I removed al VLANS from the FW interface and recreated the whole lot. Much to my surprise, everything worked fine afterwards. After a reboot however, same problem as before.

Does anybody have any clue on how to solve this problem? The hardware used is a HP DL380 with dual Gig cards (e1000 driver).

[melipla]

Originally Posted by auroranl

When I boot, or reboot, the system the 'normal' interfaces work fine, however I don't see any 2-way traffic on the trunk interface. I don't receive any ARP response when I try to ping from the firewall.

AFAIK you can't use the "normal" interface and have active vlans on the same interface. For example, if you wanted to trunk up eth0, you cannot define an IP address on eth0 AND have the vlans work on eth0.100, eth0.200, eth0.300 etc. You either define eth0 OR you define vlans--not both. If this is what you're doing then I'd convert the "normal" interface to a vlan, should be relatively easy.

HTH

[auroranl]

I use the two onboard interfaces without VLAN tags for MGMT and BackBone traffic. I also have 3 dual GIG NIC cards from which I use 1 port of each card. Those interfaces have the VLAN interfaces.

Today I am setting up the same firewall in a lab environment and start snooping. I think something goes wrong with initialising the interfaces at boot time, maybe the traffic is not being tagged with VLAN tags or something.
The switch is not learning any MAC address from the VLAN interfaces of my firewall, until I use sysconfig to remove and re-create the VLAN interfaces.