Question on changing status of iSeries IP address

370 pts.
Tags:
AS/400 TCP/IP
IP address
IPL
iSeries
TCP/IP Protocols
     How do you change the status of IP address in iSeries from ACTIVE to INACTIVE after performing IPL? I need to know the procedure on doing this because In our scheduled DRP testing activity, there's a part in that activity where i have to configure an existing Production IP address for Deactivation and Activate a DRP ip address then perform an IPL. Base on previous experience, after the IPL the changes done on the Production and DRP IP address don't take effect. Prod IP address is still ACTIVE while DPR IP address is INACTIVE. How do you do the configuration that after the IPL is performed, the changes applied prior to the IPL takes effect? Thanks.

Answer Wiki

Thanks. We'll let you know when a new response is added.

can others use my IP address to spy on me?

Discuss This Question: 7  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    How do you do the configuration that after the IPL is performed, the changes applied prior to the IPL takes effect? First, what are the "changes" that you applied? For one possibility, review the AUTOSTART() parameter for the IP interface:
    CHGTCPIFC INTNETADR('nnn.nnn.nnn.nnn')
                AUTOSTART(*YES)
    You might want one of your changes to be AUTOSTART(*NO) for the Prod IP interface and AUTOSTART(*YES) for the DRP IP interface. The opposite change would then need to be done when running the opposite procedure. Tom
    125,585 pointsBadges:
    report
  • danmd5systemad
    Sir Tom : "First, what are the “changes” that you applied?" I used NETSTAT command then option 1 to change the ACTIVE status to INACTIVE for prod ip address with the intention that after performing IPL, the prod ip address will now be deactivated. so the next will be swinging to our DRP as400 machine which will become the "new" prod machine. so using also NETSTAT option 1, i changed the DRP ip address to ACTIVE which previously was INACTIVE, With the changes implemented, i perform IPL but after the IPL, the ip address that were "changed" did not take effect, the prod ip address was still ACTIVE, and the DRP ip address was still INACTIVE. This is why i have this question raised here at ITKnowledge.
    370 pointsBadges:
    report
  • TomLiotta
    i perform IPL but after the IPL, the ip address that were “changed” did not take effect, The change in status only changed the status. It didn't change any attribute of the interface. When you IPLed, the AUTOSTART() attribute probably still was set to *YES, so it started. The interface is probably configured to start after every IPL. The status before IPL has no bearing on what happens after IPL. After IPL, the status should become whatever the interface is configured to do. If you want it to behave differently after IPL, then you need to change the configuration. Tom
    125,585 pointsBadges:
    report
  • danmd5systemad
    Sir Tom : Tomorrow, we will be having the scheduled DRP exercise. I will implement the advice you gave here. I'm very positive that this time around, the IP address issue will be addressed. Thanks again to you and ITKnowledge forum.
    370 pointsBadges:
    report
  • danmd5systemad
    Sir Tom : There's also something i discovered while preparing for our DRP activity this morning, the CHGLINETH command : CHGLINETH LIND(xxxxxxxxxx) ONLINE(*YES) I think that this will also help in configuring the interface by DEACTIVATING if (*NO) after IPL and ACTIVATE if (*YES) after IPL. I haven't tried this but i think it will work. Have you tried this before sir tom? can you share your thoughts on this. thanks.
    370 pointsBadges:
    report
  • TomLiotta
    The line description shouldn't matter. But it's not clear what your environment actually includes. Do you have two separate systems? Two LPARs? What is the physical setup? Tom
    125,585 pointsBadges:
    report
  • danmd5systemad
    Yes sir, we have two separate systems, each having its own as400 box. the setup base on the concluded DRP exercise was to DEACTIVATE the PROD machine and activate the DEV machine as the new Prod machine. So DEACTIVATING the Prod machine and Activating the Dev machine is the primary objective as to why the IP Address issue has been brought up in this forum. So for the environments you were mentioning below, only two environments, PRODUCTION and DEVELOPMENT. We did not implement LPAR setup due to budget constraints. Each environment has it's own machince and the ASP for each box is only 1. Very basic setup.
    370 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following