Is there any limitation with ISE interface bonding?

[Nate Zhang]

As of I know, not entire services are available with interface other than ge0 on ISE, like admin portal. (I mean when each of them is a standalone mode with their own IP).

How about if we use interface bonding? When the ge0 is down in bond0, is ge1 capable enough to take over entire service?

We are going to use a bunch of features such as Radius, TACACS+, Posture, Guest, BYOD, MDM etc in the production.

[Surendra · Accepted solution]

When you configure NIC bonding there is no Gig0 or Gig1 anymore. Synonymous to Gig0, Only Bond0 is capable of hosting the ISE management services like GUI and, all the other services that ISE offers can be over Bond0 or Bond1 for that matter. Even if Gig0 goes down, your Bond0 will still be active assuming that your Gig1 will be up and continues to perform the way it was before.