IBM Support

IJ33003: SLOT MAPPING REPORTS WRONG LOCATION CODES

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

  • While using Spectrum Scale Erasure Code Edition
    running on LSI MegaRaid adapters, if the slotmap.yaml
    file is edited directly several unintended consequences can
    arise that would not show up when using the drive mapping
    utility. This can include allowing several disallowed
    characters such as the hyphen in the location code name.
    

Local fix

  • Avoid using leading "0" when creating slot location codes.
    After editing a slotmap.yaml file,
    run tslsenclslot.lmr --check-slot-map
    to verify the mapped location codes are valid and
    have the expected form.
    

Problem summary

  • While using Spectrum Scale Erasure Code Edition
    running on LSI MegaRaid adapters, if the slotmap.yaml
    file is edited directly several unintended consequences can
    arise that would not show up when using the drive mapping
    utility. This can include allowing several disallowed
    characters such as the hyphen in the location code name.
    

Problem conclusion

  • Benefits of the solution:
    Checks have been added to make sure only alphanumeric
    characters are used when mapping location codes for slots.
    This should reduce the chances of an inappropriate slot location
    name. Care must still be taken when using numeric location codes
    with a leading "0," such as 017. These will be interpreted as
    if they were Octal (base 8) numbers.
    
    Work Around:
    Avoid using leading "0" when creating slot location codes.
    After editing a slotmap.yaml file,
    run tslsenclslot.lmr --check-slot-map
    to verify the mapped location codes are valid and
    have the expected form.
    
    Problem trigger:
    Users which edit the slotmap.yaml file on
    LSI MegaRAID systems may be affected.
    
    Symptom:
    Error output/message
    Unexpected Results/Behavior
    
    Platforms affected:
    Linux
    
    Functional Area affected:
    ESS/GNR
    
    Customer Impact:
    Suggested
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ33003

  • 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-06-09

  • Closed date

    2021-06-09

  • Last modified date

    2021-06-09

  • 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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"511"}]

Document Information

Modified date:
10 June 2021