10-10-2024 02:42 AM
Hi,
one of our clients runs a 2 Node ISE Deployment in a lets call it "very specific" environment.
New reqirements should be be fulfilled by keeping the IP Address on one of the nodes but
move from /27 to a /31 subnet mask on the ISE Eth0 interfaces.
First experiments on a test machine look promising:
Configuring an IP with /31 as mask on interface eth1 is possibe
Setting the default gateway to the other address in this subnet as well.
I know /31 is intended to be used on P2P links only and it is neiter best practice
for hosts and nor may it be supported on all Operating Systems.
But fortunately ISE is based on Linux and I do not see another approach to fulfill the new requirements.
Anyone running an ISE node with 255.255.255.254 subnet mask here ?
Would this be TAC supported as well ?
Thanks & BR
Frank
10-10-2024 02:23 PM
I don't see any issues with this. ISE only talking to the default gateway and nothing else - there is no requirement for ISE to have other stations on the same subnet.
10-10-2024 06:18 PM
not running ISE with /31 mask, but I don't think there should be any issue with TAC supporting this provided you have active support contract.
other ISE node and network devices, just need to be able to reach this subnet via routing, that's all.
10-11-2024 02:57 AM
Did some more tests on my lab VM... (ISE 3.2) on eth1:
results:
while testing 2 restarts of ISE services observerd:
1) change of network mask
2) change of default gw
Thanks for your opinions.
Based on them and on my test results
we will give this try in the live environment.
Will come back with our final findings here....
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide