Support Center > Search Results > SecureKnowledge Details
Inconsistency in "fw ctl affinity -l" command output
Symptoms
  • Output of "fw ctl affinity -l" command show different results when it is executed multiple times simultaneously.

    Example:

    1. [Expert@HostName:0]# fw ctl affinity -l
      Mgmt: CPU 0
      eth1-03: CPU 0
      eth1-04: CPU 0
      fw_0: CPU 6
      fw_1: CPU 5
      fw_2: CPU 4
      Interface Sync: has multi queue enabled
      Interface eth1-01: has multi queue enabled
      Interface eth1-02: has multi queue enabled
      
    2. [Expert@HostName:0]# fw ctl affinity -l
      Mgmt: CPU 0
      Sync: CPU 0
      eth1-01: CPU 0
      eth1-03: CPU 0
      eth1-04: CPU 0
      fw_0: CPU 6
      fw_1: CPU 5
      fw_2: CPU 4
      Interface eth1-01: has multi queue enabled
      
  • Occasionally, "fw ctl affinity -l -v" command fails with following error:

    [Expert@HostName:0]# fw ctl affinity -l -v
    fw: Failed to open file /tmp/fwaffinity_cmd_out.tmp: Unknown error 4294967295
    fw: Failed to acquire MQ interfaces
    Mgmt: CPU 0
    eth1-03: CPU 0
    eth1-04: CPU 0
    fw_0: CPU 6
    fw_1: CPU 5
    fw_2: CPU 4
    
  • Output of "cpmq get -a" command shows correct Multi-Queue configuration for all supported network interface cards.

Cause

"fw ctl affinity -l" command uses a temporary file /tmp/fwaffinity_cmd_out.tmp during its execution.

When running this command multiple times simultaneously, access to the temporary file might fail. As a result, multi-queue interfaces can be shown as non-multi-queue interfaces.


Solution
Note: To view this solution you need to Sign In .