ISE 2.6: Multiple interfaces on the same subnet

[jorgquin]

Team

I have the following scenario, Having same subnet on 2 interfaces seems totally doable from CLI point of view. 

interface GigabitEthernet 0
ip address 192.168.1.250 255.255.255.0
ipv6 address autoconfig
ipv6 enable
!
interface GigabitEthernet 1
ip address 192.168.1.244 2 55.255.255.0
ipv6 address autoconfig
ipv6 enable
!

 My question is, are there any drawbacks / issues with this approach? The ones I could think is asymmetric routing or issues with the linux routing table itself, but wondering if anyone had deploy like this and if it has worked or had any issues?

Warm regards,

Jorge

[Mohammed al Baqari]

Hi,

asym routing won't be a problem here because the gateway will be same for
both interfaces being in the same subnet.

I just don't see why this is needed, if you need HA then NIC bonding is the
way to go as below

https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/install_guide/b_ise_InstallationGuide24/b_ise_InstallationGuide24_chapter_0101.html

*** please remember to rate useful posts

[jorgquin]

Thanks for your reply.

in this case is not exactly HA but for physical limitations (1gb switches) customer wants to have dedicated management and dedicated radius separates (not to overwhelm with management and radius request one single interface)

i do agree that this approach is probably not the best one but wanted to check if someone has done this and if there are drawbacks/trade off