Explanation of situation. Currently were running out of ip address's.
were running on the 255.255.255.0 segment and such are limited to the 1-254 devices inclusive.
Options,
create a entire new scope with start address of
192.10.10.1 -> 192.10.11.254 with subnet 255.255.254.0
or leave the current scope of 192.10.10.1->192.10.10.254 with subnet of 255.255.255.0 in tact and create a new secondary child scope of 192.10.11.1->192.10.11.254 with subnet of 255.255.255.0
Create a superscope and add the new scope first and the old scope last which forced the old 192.10.10.0 segment to be issued entirely before the 192.10.11.0 segment. Add the second static ip address of the new segment to the server.(server only has one lan connection, two static ip's for the one card)
i like the second choice because it helps with overall configuration. We can implement choice two, 99% of the company will still be on the old segment. So if there is a problem it will be minimal. After we verify everything is good internally start changing our PIX configuration to include the new segment. In turn letting the new segment access external resources. (remember the pix is going to block this new segment until we add the new segment to the access list).
could you please fill me in on anything i may have missed. It was about 2 years ago since i the last time i undertook this task.
thanks in advance,
were running on the 255.255.255.0 segment and such are limited to the 1-254 devices inclusive.
Options,
create a entire new scope with start address of
192.10.10.1 -> 192.10.11.254 with subnet 255.255.254.0
or leave the current scope of 192.10.10.1->192.10.10.254 with subnet of 255.255.255.0 in tact and create a new secondary child scope of 192.10.11.1->192.10.11.254 with subnet of 255.255.255.0
Create a superscope and add the new scope first and the old scope last which forced the old 192.10.10.0 segment to be issued entirely before the 192.10.11.0 segment. Add the second static ip address of the new segment to the server.(server only has one lan connection, two static ip's for the one card)
i like the second choice because it helps with overall configuration. We can implement choice two, 99% of the company will still be on the old segment. So if there is a problem it will be minimal. After we verify everything is good internally start changing our PIX configuration to include the new segment. In turn letting the new segment access external resources. (remember the pix is going to block this new segment until we add the new segment to the access list).
could you please fill me in on anything i may have missed. It was about 2 years ago since i the last time i undertook this task.
thanks in advance,