IBM Support

IY50248: "Logical Network Interface [192.168.1.119] does not exist" messa ge when creating >17+ multiple webseald instances

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • TAM 4.1+fp5/Win2K
    
    Customer reported getting the error:
    
    "Logical Network Interface [192.168.1.117] does not exist"
    
    while trying to configure 17th webseald instance (using logical
    network interfaces).
    
    He then unconfigured the 16th webseald instance and tried to
    reconfigure it using the same IP (192.168.1.117) and got the
    same message.
    
    He tried to reconfigure the 16th webseald instance to the IP
    originally used (192.168.1.116).  It wouldn't reconfigure, and
    generated the same message:
    
    "Logical Network Interface [192.168.1.116] does not exist"
    
    ****************************************************************
    
    
    I encountered the same problem while performing a re-create in
    the lab (2-way P4-Xeons w/1GB RAM). However, I didn't encounter
    the error until the 19th webseald instance was configured,
    whereas the customer saw the error while configuring their 17th
    webseald instance.
    
    While configuring the 19th webseald instance (using unique
    logical network interfaces), encountered the error:
    
    "Logical Network Interface [192.168.1.119] does not exist"
    
    I unconfigured the 18th webseald instance and tried
    reconfiguring it using 192.168.1.119 and got the same error.
    
    Then I tried re-configuring the 18th webseald instance using
    it's original IP (192.168.1.118) and it wouldn't configure,
    showing the error
    
    "Logical Network Interface [192.168.1.118] does not exist"
    
    ****************************************************************
    
    FYI, I also did a re-create using a TAM 3.9/Win2K box (single
    processor w/ 392MB RAM), and have created 25 webseald
    instances without any problems.
    

Local fix

Problem summary

  •  see main problem description
    

Problem conclusion

  •  Fixed in 4.10-AWS-0010LA.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY50248

  • Reported component name

    ACCESS MGR WEBS

  • Reported component ID

    5724C0811

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2003-10-28

  • Closed date

    2004-03-12

  • Last modified date

    2004-03-12

  • 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

    ACCESS MGR WEBS

  • Fixed component ID

    5724C0811

Applicable component levels

  • R410 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPREK","label":"Tivoli Access Manager for e-business"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
12 March 2004