I've searched the forums and docs and I find some different answers so I'm looking to try and confirm what I'm seeing.
I'm looking to use mgmt 0/RSP0/CPU0/0 for OOB mgt. and running 5.3.3.
My control-plane config leverages 'interface all' for config simplicity.
However this seems to catch the mgmt interface as well.
I could create/leverage a group config but the # of interfaces and needed addresses create a much larger config when I consider
Gig*, TenGig*, Hundred*, Loop* interfaces.
a) am I correct that 'interface all' is capturing my mgmt interface?
b) if so, a feature request here to change it so that any specific interface config'd as OOB would override that behavior. This would allow for a simpler, more maintainable config. Would there be any reason not to take this approach?
Secondly,
When my mgmt interface is up, it's prefix is added to the global table.
I see docs that differ on whether the vrf statement is needed or not.
I'd thought by default, that mgmt interfaces were not involved with any forwarding decisions.
With or without it, when up, my mgmt interface prefix ends up in the global table - is this behavior I'm seeing related to the inband 'interface all' issue above?
thanks,
