none
Moving from traditional DLC to OSA IP DLC RRS feed

  • Question

  •  I have a production pair of HIS on traditional DLC over Ethernet and I
    took the text cfg file output and converted the cfg to IP-DLC to OSA on
    a pair of VM test boxes both with the same HIS 2006. All accounts access
    etc are identical.
      I have tested the PU's to OSA on my VM pairs they work fine when the
    production server is off-line it has a testna sna domain name.
     
    My plan is to
     
    Back it all up
     
    open the test VM's SNA cfg off-line on the production server and rename
    the server names to my production boxes server names and save
      The question is should I delete the com.cfg file on production servers
    then open the new saved cfg from my VM's from the production management
    tool or is there a better way?
      Once I see all my PU's/LU's,users,printer,etc in the MMC on production
    with the new cfg. I will save it on production.
      Then I will go into the production cfg tool on the production server
    with the new cfg and change the SNA domain to the production domain name
    and save.
      Then reopen the MMC after I restart SNAServer etc. I would think all
    should be fine with the PU's now using IP-DLC to OSA ad my old server
    and SNA domain names. Anything I am missing anyone?
     
    Friday, January 6, 2012 4:34 PM

Answers

  • Stan,

     

    If you have been able to successfully test the desired configurationon your test servers, then you ahve verify that it works. At this point, you should be able to do the steps you mentioned to get this updated configuration applied to your production servers.

    I would save the existing COM.CFG on the production servers so that you have it as a fall back in case you run into problems. If you restore the old COM.CFG, you will be able to go back to the DLC connections to get your servers functionling again.

    After backing up (saving) the current production COM.CFG, copy the COM.CFG from the test servers (after changing the server names) onto the production server and run your test to make sure everything comes back up.

    You'll need to install the IP-DLC link service on the production servers (if you haven't already) so that the connections using the IP-DLC link service will have the link service available on the production servers when you bring that configuration online.

    Thanks...

     


    Stephen Jackson - MSFT
    Tuesday, January 10, 2012 1:55 PM

All replies

  • Hi Stan,

    I always use the command snacfg.exe to perform that kind of operations !

    With that command you can simple remove and add PUs/LUs .

    Best Regards,


    Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com
    Monday, January 9, 2012 6:53 AM
  • 5000 users? Not an option for me, it takes too long and if scripts fail
    trouble shooting would not allow me any leeway. Thanks but been there
    done that and its too slow for that many PU/LUs and users etc.
     On 1/8/2012 10:53 PM, Steve Melan wrote:
    > Hi Stan,
    >
    > I always use the command snacfg.exe to perform that kind of operations !
    >
    > With that command you can simple remove and add PUs/LUs .
    >
    > Best Regards,
    >
    > ------------------------------------------------------------------------
    > Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com
     
     
    Monday, January 9, 2012 4:02 PM
  • Stan,

     

    If you have been able to successfully test the desired configurationon your test servers, then you ahve verify that it works. At this point, you should be able to do the steps you mentioned to get this updated configuration applied to your production servers.

    I would save the existing COM.CFG on the production servers so that you have it as a fall back in case you run into problems. If you restore the old COM.CFG, you will be able to go back to the DLC connections to get your servers functionling again.

    After backing up (saving) the current production COM.CFG, copy the COM.CFG from the test servers (after changing the server names) onto the production server and run your test to make sure everything comes back up.

    You'll need to install the IP-DLC link service on the production servers (if you haven't already) so that the connections using the IP-DLC link service will have the link service available on the production servers when you bring that configuration online.

    Thanks...

     


    Stephen Jackson - MSFT
    Tuesday, January 10, 2012 1:55 PM
  •  Thanks Stephen once again, and yes I have the IP-DLC service already
    on my Production machines and a PU working to test the firewall rules
    etc. I am going to edit my test cfg offline and change the server names
    make stuff auto-start etc. Then I will restore my saved off-line cfg to
    my production boxes, then edit the SNA Domain Name in the cfg tool and
    save. Should be good and I do have the DLC fall-back just in case. I
    only have 2 servers but about 4000 users so I have to be quick!
     
    On 1/10/2012 5:55 AM, Stephen_R_Jackson [MSFT] wrote:
    > Stan,
    >
    > If you have been able to successfully test the desired configurationon
    > your test servers, then you ahve verify that it works. At this point,
    > you should be able to do the steps you mentioned to get this updated
    > configuration applied to your production servers.
    >
    > I would save the existing COM.CFG on the production servers so that you
    > have it as a fall back in case you run into problems. If you restore the
    > old COM.CFG, you will be able to go back to the DLC connections to get
    > your servers functionling again.
    >
    > After backing up (saving) the current production COM.CFG, copy the
    > COM.CFG from the test servers (after changing the server names) onto the
    > production server and run your test to make sure everything comes back up.
    >
    > You'll need to install the IP-DLC link service on the production servers
    > (if you haven't already) so that the connections using the IP-DLC link
    > service will have the link service available on the production servers
    > when you bring that configuration online.
    >
    > Thanks...
    >
    > ------------------------------------------------------------------------
    > Stephen Jackson - MSFT
     
     
    Thursday, January 12, 2012 3:42 PM