Service Virtualization

  • 1.  DevTest License Server is being Moved July 8, 9pm - 1am EDT

    Broadcom Employee
    Posted Jun 06, 2017 02:52 PM

    This On Line License Server IP change ONLY affects DevTest versions 7.x and below. 

     

    We are moving our DevTest 7.x and below On Line License Server starting July 8th at 9 pm EDT.  It will take 4 hours for the transfer to be complete.  At 1 am EDT the transfer is expected to be complete.

     

    Please make sure that if you need to modify your Firewall Rules; this notice should allow you time to get the work ticket in with your Services Organization.

     

    The current IP is 141.202.246.195

    The new IP will be 130.200.94.40

     

    You should "White List" both the above IP addresses and should not remove the existing one (141.202.246.195) until the migration is complete.

     

    It is important to note that the License Module in the DevTest components allows for a 3 day grace period.  If you do not get your firewall rules changed, you have until Tuesday, July 11th to get this done.  You will notice in the log files that your license has entered into the grace period. 

     

    With this move, we will not provide a parallel time period when both IPs are active.



  • 2.  Re: DevTest License Server is being Moved July 8, 9pm - 1am EDT

    Broadcom Employee
    Posted Jul 08, 2017 11:06 PM

    This move has been successfully done from an implementation view point.  The transfer went very smoothly, and the IP address is now propagating.  I can successfully ping license.itko.com and get the new IP 130.200.94.40 from a n internal CA network machine as well as an external to the CA network machine.

     

    If you have issues, I have created a cheat sheet for the Licensing Support people to assist you.

     

    1. Scenario 1:  The LISA component goes down.  The easiest thing to do is to simply restart the component.  It should simply come up. 
    2. Scenario 2:  Tried the restart and it fails.  You call to find out what happened.  Support will point you to the Communities DevTest License Server is being Moved July 8, 9pm - 1am EDT https://communities.ca.com/thread/241778775-devtest-license-server-is-being-moved-july-8-9pm-1am-edt
    3. Scenario 3:  You have white listed the new IP address and you still cannot connect.  Ping license.itko.com from the command line as well as ping 130.200.94.40 from the box that the LISA component resides on.  Do you get the same results?  If the ping to  license.itko.com does not give the 130.200.94.40 IP address, either the DSN Servers have not pushed out our update (propagated the new address over the old address) or it is hard coded on your system (such as the Hosts file).  While that is being sorted, you can hardcode the value 130.200.94.40 in your local.properties file.
    4. Scenario 4:  You have already read the Communities post, you have the new IP white listed, when you ping the license.itko.com, you are now receiving 103.200.94.40.  However, the LISA component is still not coming up.  Where to look?  Look in the local.properties file of the component and make sure that the old IP address is not in there.  If it is not, then check the Host file (it is in C:\Windows\System32\drivers\etc) and see if it is hardcoded in there to the old IP address.  If it is, change it to the new IP 130.200.94.40.
    5. Scenario 5:  After you have exhausted all of these, then you as the Client have to generate a GSC ticket and request a one month file based license.  Please provide your local.properties information in order to generate a proper file based license based on your current entitlements.

     

    Please note that the LISA components have a 3 day grace period before they will fail with an expired license notice.  There will be in the logs that they have gone into a license grace period.  As long as you do not restart the component and you do not have connection to the license.itko.com license server, the LISA components will be able to continue to operate.  This should get all of us through the weekend and into regular support hours starting late Sunday US hours (Monday morning for Australia and Japan).

     

    Cheers!
    Les