Limitations of MultiNICB and IPMultiNICB
Prev	Network agents	Next

---

Limitations of MultiNICB and IPMultiNICB

• No support for active/passive configuration: MultiNICB and IPMultiNICB do not support active/passive configurations in which physical interfaces can be configured as needed by the agent.
• No plumbing of physical interfaces: MultiNICB and IPMultiNICB rely on system initialization scripts to plumb and configure all physical interfaces. When a MultiNICB resource is enabled, the agent expects all physical interfaces under the resource to be plumbed and configured with the test IP addresses.
• Need for test addresses: Unique and dedicated test IP addresses are required for every interface under the MultiNICB resource. These addresses cannot be used for any other purpose or by any applications other than the agent.

  Note   Test IP addresses and the logical IP addresses do not have to be in the same IP subnet.

• A MultiNICB resource must represent all the interfaces of a single IP subnet: Group all interfaces of the same IP subnet under a single MultiNICB resource to enable MultiNICB and IPMultiNICB agents to function properly. A MultiNICB resource can only have an interface belonging to a single IP subnet under it.