IBM Support

IJ32668: COMMANDS LIKE "MMCES STATE CLUSTER NFS" ALWAYS SHOW PARSEABLE OUTPUT, EVEN WITHOUT -Y

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • mmces state
    
    There's no more difference in format of stdout
    when running e.g. "mmces state cluster NFS"
    or "mmces state cluster NFS -Y".
    With former versions we used to
    have a nice table list when not using -Y.
    But, today, we get e.g. this:
    
    [root@nas22ces01-i ~]# mmces state cluster NFS
    mmcesstatecluster::HEADER:version:reserved:
    reserved:NODE:COMPONENT:STATE:EVENTS:
    mmcesstatecluster::0:1::::nas22ces01-i:NFS:HEALTHY:
    csm_resync_forced,no_longwaiters_found,
    ccr_quorum_nodes_ok,service_running,node_resumed,
    nfs_dbus_ok,node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces02-
    i:NFS:HEALTHY:csm_resync_forced,ccr_quorum_nodes_ok,
    nlockmgr_rpcinfo_ok,mountd_rpcinfo_ok,service_running,
    node_resumed,nfs_rpcinfo_ok,nfsd_up,nfs_dbus_ok,wnbd_up,
    node_resumed,ads_up,dns_found,
    dns_krb_tcp_dc_msdcs_up,dns_found,dns_query_ok:
    mmcesstatecluster::0:1::::nas22ces03-i:NFS:HEALTHY:
    csm_resync_forced,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces04-i:NFS:HEALTHY:
    service_running,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,service_running,
    node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces05-i:NFS:HEALTHY:
    service_running,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,service_running,
    node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces06-i:NFS:HEALTHY:
    service_running,nfs_exported_fs_chk,nlockmgr_rpcinfo_ok,
    mountd_rpcinfo_ok,service_running,nfs_rpcinfo_ok,nfsd_up,
    service_running,dns_found,dns_found
    

Local fix

Problem summary

  • mmces state
    
    There's no more difference in format of stdout
    when running e.g. "mmces state cluster NFS"
    or "mmces state cluster NFS -Y".
    With former versions we used to
    have a nice table list when not using -Y.
    But, today, we get e.g. this:
    
    [root@nas22ces01-i ~]# mmces state cluster NFS
    mmcesstatecluster::HEADER:version:reserved:
    reserved:NODE:COMPONENT:STATE:EVENTS:
    mmcesstatecluster::0:1::::nas22ces01-i:NFS:HEALTHY:
    csm_resync_forced,no_longwaiters_found,
    ccr_quorum_nodes_ok,service_running,node_resumed,
    nfs_dbus_ok,node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces02-
    i:NFS:HEALTHY:csm_resync_forced,ccr_quorum_nodes_ok,
    nlockmgr_rpcinfo_ok,mountd_rpcinfo_ok,service_running,
    node_resumed,nfs_rpcinfo_ok,nfsd_up,nfs_dbus_ok,wnbd_up,
    node_resumed,ads_up,dns_found,
    dns_krb_tcp_dc_msdcs_up,dns_found,dns_query_ok:
    mmcesstatecluster::0:1::::nas22ces03-i:NFS:HEALTHY:
    csm_resync_forced,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces04-i:NFS:HEALTHY:
    service_running,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,service_running,
    node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces05-i:NFS:HEALTHY:
    service_running,ccr_quorum_nodes_ok,service_running,
    node_resumed,nfs_dbus_ok,service_running,
    node_resumed,dns_found,dns_found:
    mmcesstatecluster::0:1::::nas22ces06-i:NFS:HEALTHY:
    service_running,nfs_exported_fs_chk,nlockmgr_rpcinfo_ok,
    mountd_rpcinfo_ok,service_running,nfs_rpcinfo_ok,nfsd_up,
    service_running,dns_found,dns_found
    

Problem conclusion

  • Benefits of the solution:
    mmces state cluster NFS should
    print human readable output.
    
    Work around:
    None
    
    Problem trigger:
    Parsing of the machine readablle
    output was not done correctly
    
    Platforms affected:
    ALL Linux OS environments (CES nodes)
    
    Functional Area affected:
    CES
    
    Customer Impact:
    Low
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ32668

  • Reported component name

    SPEC SCALE STD

  • Reported component ID

    5737F33AP

  • Reported release

    511

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-05-18

  • Closed date

    2021-05-18

  • Last modified date

    2021-05-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SPEC SCALE STD

  • Fixed component ID

    5737F33AP

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"511","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
19 May 2021