We have multiple stores that are set up as cookie cutter networks in order to simplify management and new store rollouts. This includes machine naming and local point of sale network addressing. Each location does have it's own public network that is routable to the main office. In basic testing, it was a bit confusing within LEM as all of the POS servers had the same name, but in most lists it also shows the node IP, which happens to include the store number in one of the octets.
The problem that we are having is in some of the logging. I set up a FIM connector to watch a specific file that we expect to get updated everyday at 5:45am. The problem is that the Node IP is showing up as the internal, non-routable, IP address instead of the routable IP leaving us where we have no idea what machine it was actually logging.
Anyone else have the same cookie cutter situation? How did you go about handling the issue? Is there a way to bind the client to a specific IP?
Thanks in advance.
