IP Integrity Checks...

[SQLePO]

Hi, I am using ePO 2.5 to manage a rather large network consisting of numerous subnets spread across the country. I have started to look at the IP management section and have only just started playin with it trying to get it to add any server or workstation that I add to the network into my specified area's. I run an IP integrity check and get errors teling me to "Delete the entry from the first node and add it to the second" Can anyone shed any light on this situation, does anyone out there use the IP management feature or can anyone recomend any best practices to adhere to.. any info whatsoever would be great.

Thanks in advance

 

[Eyas]

Hi

We're running with IP-sorting to populate our sites and groups. The basic setup is as follows.

You should only have the same range on one group per level. Let me exemplify:

Site 1 192.168.0.1/24, 192.168.0.3/24, 192.168.0.6/24, 192.168.0.8/24

|_
Group 1 192.168.0.1/24, 192.168.0.3/24
|_
Group 1_1 192.168.0.1/24
|_
Group 1_2 192.168.0.3/24
|_
Group 2 192.168.0.6/24, 192.168.0.8/24
|_
Group 2_1 192.168.0.6/24
|_
Group 2_2 192.168.0.8/24

If you would enter 192.168.0.3 on group 2_2 you'll get a IP integrity failure. You'll also get one if you don't list the IP on the higher levels.

HIH

/Eyas

 

[SQLePO]

Thanks for your response, I was going to go down the route of specifying an IP range. We currently have Servers using IP addresses as follows: DC's use the format of 40.1 as their last two octets for example, for one area the IP address will be 173.1.40.1, for the next area, 129.1.40.1. Then we have the DHCP workstations which will use an address range 173.1.60.xx, you get the picture. I wanted to specify a range which would include all of the workstations and servers, ie. 173.1.1.1 - 173.1.255.255 is this possible to specify all the ranges that I want at the top level and then at the appropriate child site scpecify its corresponding range.. Is this method going to work or will i need to make some adjustments,

Thanks in advance,

SQLePO

 

[Eyas]

Hi

I haven't tried it but with the correct mask it should work I guess. I guess you could set 173.1.1.1/16 on your top level and then adjust the mask as you go down your hierarchy. For your server group you should be able to set IP 173.1.40.0/24 etc.

Should work but haven't tried it myself.

/eyas