Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    PIMD related errors during boot

    Scheduled Pinned Locked Moved
    2.5 Development Snapshots (Retired)
    1
    1
    208
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      louis2
      last edited by

      Hello,

      At this moment I am running built on Wed Jun 03 13:09:01 EDT 2020. Given some issues, I cleared the error log and dit a reboot. After doing so, I looked at the log for "strange things". Here some issues affecting or related to PIMD.

      Reading bottum up I notice:

      Strange but not necessary related
      Jun 10 11:53:46 pfSense kernel: module_register_init: MOD_LOAD (iwm8000Cfw_fw, 0xffffffff80747820, 0) error 6
      Jun 10 11:53:46 pfSense kernel: firmware_register: cannot register image iwm8000Cfw, firmware table full!

      Below the kernel starting the VLAN's, not OK some how
      Jun 10 11:53:54 pfSense kernel:
      >>> PIMD does not get VIFS for the vlans below !!! (up to my next remark) <<<
      Jun 10 11:53:54 pfSense kernel: vlan11: changing name to 'ix1.116'
      Jun 10 11:53:53 pfSense kernel: vlan10: changing name to 'ix0.18'
      Jun 10 11:53:53 pfSense kernel: vlan9: changing name to 'ix0.14'
      Jun 10 11:53:53 pfSense kernel: vlan8: changing name to 'lagg0.88'
      Jun 10 11:53:52 pfSense kernel: vlan7: changing name to 'lagg0.100'
      Jun 10 11:53:52 pfSense kernel: igb1: link state changed to DOWN
      Jun 10 11:53:52 pfSense check_reload_status[404]: Linkup starting $igb1
      Jun 10 11:53:52 pfSense kernel: igb0: link state changed to DOWN
      Jun 10 11:53:52 pfSense check_reload_status[404]: Linkup starting $igb0
      Jun 10 11:53:52 pfSense kernel: vlan6: changing name to 'lagg0.16'
      Jun 10 11:53:52 pfSense kernel: igb1: link state changed to UP
      Jun 10 11:53:52 pfSense check_reload_status[404]: Linkup starting $igb1
      Jun 10 11:53:51 pfSense kernel: vlan5: changing name to 'em0.7'
      Jun 10 11:53:51 pfSense kernel: igb0: link state changed to UP
      Jun 10 11:53:51 pfSense check_reload_status[404]: Linkup starting $igb0
      Jun 10 11:53:50 pfSense kernel: vlan4: changing name to 'em0.4'
      Jun 10 11:53:49 pfSense kernel: vlan3: changing name to 'em0.6'
      Jun 10 11:53:47 pfSense sshd[11688]: Server listening on 0.0.0.0 port 22.
      Jun 10 11:53:47 pfSense sshd[11688]: Server listening on :: port 22.
      >>> after starting PIMD the three vlan’s below provide a VIF the ones above DO NOT, so some thing wrong here ! <<
      Jun 10 11:53:47 pfSense kernel: vlan2: changing name to 'lagg0.13'
      Jun 10 11:53:47 pfSense kernel: vlan1: changing name to 'lagg0.26'
      Jun 10 11:53:47 pfSense kernel: vlan0: changing name to 'lagg0.10'
      Jun 10 11:53:46 pfSense kernel: lagg0: IPv6 addresses on igb1 have been removed before adding it as a member to prevent IPv6 address scope violation.
      Jun 10 11:53:46 pfSense kernel: lagg0: link state changed to DOWN
      Jun 10 11:53:46 pfSense kernel: lagg0: IPv6 addresses on igb0 have been removed before adding it as a member to prevent IPv6 address scope violation.
      Jun 10 11:53:46 pfSense kernel:
      Jun 10 11:53:46 pfSense check_reload_status[404]: Linkup starting $lagg0

      And then PIMD booting ^twice^ :) and some other problems
      Jun 10 11:54:11 pfSense root[54530]: Bootup complete
      >> the result "no vifs to forward too <<
      Jun 10 11:54:11 pfSense pimd[52647]: Cannot forward: no enabled vifs
      Jun 10 11:54:11 pfSense pimd[52368]: Cannot forward: no enabled vifs
      >> see below PIMD running twice, only VIFS for tree VLAN/s, Invalid phyint messages <<
      Jun 10 11:54:11 pfSense pimd[52368]: Local static RP: 169.254.0.1, group 232.0.0.0/8
      Jun 10 11:54:11 pfSense pimd[52647]: Local static RP: 169.254.0.1, group 232.0.0.0/8
      Jun 10 11:54:11 pfSense pimd[52368]: Local static RP: 192.168.14.1, group 224.0.0.0/4
      Jun 10 11:54:11 pfSense pimd[52647]: Local static RP: 192.168.14.1, group 224.0.0.0/4
      Jun 10 11:54:11 pfSense pimd[52368]: /var/etc/pimd/pimd.conf:12 - Invalid phyint address 'ix1.116'
      Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:12 - Invalid phyint address 'ix1.116'
      Jun 10 11:54:11 pfSense pimd[52368]: /var/etc/pimd/pimd.conf:11 - Invalid phyint address 'lagg0.16'
      Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:11 - Invalid phyint address 'lagg0.16'
      Jun 10 11:54:11 pfSense pimd[52368]: /var/etc/pimd/pimd.conf:10 - Invalid phyint address 'ix0.14'
      Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:10 - Invalid phyint address 'ix0.14'
      Jun 10 11:54:11 pfSense pimd[52368]: Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23
      Jun 10 11:54:11 pfSense pimd[52647]: Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23
      Jun 10 11:54:11 pfSense pimd[52368]: Getting vifs from /var/etc/pimd/pimd.conf
      Jun 10 11:54:11 pfSense pimd[52647]: Getting vifs from /var/etc/pimd/pimd.conf
      Jun 10 11:54:11 pfSense pimd[52647]: Disabling all vifs from kernel
      Jun 10 11:54:11 pfSense pimd[52368]: Disabling all vifs from kernel
      >> see here that only from three vlan's there are vifs, exactly the ones from the beginning of the kernel startup and not the once starting a bit later <<
      Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #2 - rate 0
      Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #2 - rate 0
      Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0
      Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0
      Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
      Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
      Jun 10 11:54:11 pfSense pimd[52368]: Getting vifs from kernel
      Jun 10 11:54:11 pfSense pimd[52647]: Getting vifs from kernel
      Jun 10 11:54:11 pfSense pimd[52368]: pimd version 2.3.2 starting ...
      Jun 10 11:54:11 pfSense pimd[52647]: pimd version 2.3.2 starting ...

      Hope this helps to get things fixed !

      Sincerely,

      Louis

      1 Reply Last reply Reply Quote 0
      • First post
        Last post