Problem with vlans on igb (was: fsck problem FreeBSD 8.3)
Коньков Евгений
kes-kes at yandex.ru
Fri Apr 13 18:54:24 UTC 2012
Здравствуйте, Damien.
Вы писали 13 апреля 2012 г., 4:42:31:
DF> Yes, I suggest you try with "-vlanhwtag" as well.
DF> If that stops your unwanted reboots, you may want to remove it and see
DF> if the situation changes.
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether a0:36:9f:00:66:a4
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether a0:36:9f:00:66:a5
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether a0:36:9f:00:66:a6
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=400b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWTSO>
ether a0:36:9f:00:66:a7
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan407: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a4
inet xxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 407 parent interface: igb0
vlan408: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a5
inet xxxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 408 parent interface: igb1
vlan492: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a5
inet xxxxxxxxxxxx netmask 0xfffffff8 broadcast xxxxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 492 parent interface: igb1
vlan70: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a7
inet xxxxxxxx netmask 0xfffffe00 broadcast xxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 70 parent interface: igb3
vlan71: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a7
inet xxxxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 71 parent interface: igb3
vlan72: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
vlan: 0 parent interface: <none>
vlan73: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a7
inet xxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 73 parent interface: igb3
vlan74: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
vlan: 0 parent interface: <none>
vlan75: flags=8002<BROADCAST,MULTICAST> metric 0 mtu 1500
ether 00:00:00:00:00:00
vlan: 0 parent interface: <none>
vlan76: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a7
inet xxxxxxxxxxx netmask 0xfffffe00 broadcast xxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 76 parent interface: igb3
vlan100: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan101: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
inet xxxxxxxxxx netmask 0xffffff00 broadcast xxxxxxxxxxx
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 101 parent interface: igb2
vlan102: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan103: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan104: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan105: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan106: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan107: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan108: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan109: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan110: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan111: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan112: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan113: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan114: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan115: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
vlan: 0 parent interface: <none>
vlan115: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether a0:36:9f:00:66:a6
vlan: 0 parent interface: <none>
With this config no 'REBOOT' happen
When just assign vlan100, 102-115 to igb2 and add IPs to those interfaces
(no any traffic on those vlans yet) server starts to reboot. In
evening time =)
You sugestion to disable 'vlanhwtag' I will try after holidays. Do not
want to risk now =). One more question: I must disable vlanhwtag on
all igbs, or only on igb2? (this is four head LAN)
--
С уважением,
Коньков mailto:kes-kes at yandex.ru
More information about the freebsd-questions
mailing list