DS7.5 KNOWN ISSUE: Images may be captured to, or deployed from, remote package servers instead of to the local SMP

book

Article ID: 158963

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

The problem is that you may have a system sitting right next to the SMP, and images, instead of coming from the SMP (or worse, being captured to it), are being pulled/pushed across the WAN to a remote package server.  Other packages might be pulling from the SMP, or not, but the DS images will not no matter what.

This used to work in DS 7.1.

Cause

This is actually working by design, mostly.  To explain, we need to describe how Package Server logic works, AND explain that unlike DS 7.1, we now use package-server logic (we ignored it back then).

How to Package Servers work?

Whenever you need a package of any kind, the client goes to the NS and says "where can I find this?"  The NS looks at it's vast store of ultimate knowledge and determines what package server "near" you can service that request, and sends you up to 10 package servers to try.

But there are rules around this process, as follows:

  • If there is ONLY an SMP/NS server and no site servers, the SMP is returned as a source for the package.
  • If there is at LEAST ONE PS site server, then the SMP will ONLY return the PS.  There is logic now that says "I don't WANT to be your package server if at all possible, so if there's a package server out there, I'm going to send you to it!
  • IF there are multiple package servers configured, up to 10 of those package servers for you to try.
  • IF you have sites defined, ONLY the package servers in your site will be returned - up to 10.
  • IF all your package servers in that site are down, the NS/SMP will be returned.
  • IF you are in a site where there are NO package servers, but the NS/SMP is actually residing locally, THEN we'll relent and again, return the SMP as an option.

 

The last bullet seems to be our problem.  DS seems to ignore that logic, and simply pulls any package server it can, OR possibly, it also may ignore site bondaries all-together.  Full testing has not been done to verify this.

 

Why did this work in DS 7.1 then?

DS 7.1 didn't use Package Servers.  It used Task Servers.  Granted, package services were required, and package was often used for replication, but the KEY to DS 7.1 was task server.  We connected to your task server and hoped and prayed the image was there.  Since the SMP is a task server by default, it would be mapped to.  You may recall that images captured OFF the SMP would not replicate back to the NS, but that is largely forgotten in light of this issue.  The reason is that the SMP is NOT a package server by default.

And, now that we are appropriately (mostly) using Package Servers, the SMP is ONLY used as a fail-over/last resort.

Resolution

As a general rule, it is a "Best Practice" - a well known one for several reasons including hierarchy - to make your first Package Server in the same location/site as the SMP.

If you do not already have one, get a site server near your SMP so you don't pull packages across the WAN.

 

The issue is being looked into by Development.