Hi Thanks,

I did read that but am still confused.

I am doing separate interfaces. 1 for internal data, 1 for internal management.

If I set the internal data metric with a lower cost, wont that that influence traffic leaving the internal management interface?

Thanks,

Justin

If you have two interfaces:

Inside

Management

route inside 0 0 x.x.x.x 10

route management 0 0 y.y.y.y 100

Then, all traffic that the ASA receives for which it does not have a matching entry in the IP routing table, will be sent through the inside interface. If this interface fails, the traffic will be sent through the management interface (there will be no load-balancing). You could have some problems with this if not having the IP SLA tracking feature as well.

Normally, you have a deafult route out the outside interface (to the Internet) and only static routes or an IGP running on the rest of the interfaces.

Federico.

Thanks again,

So traffic destined to the management interface will be replied to by the internal interface?

To me that is odd and not optimal. I want the management interface to respond to management traffic. If the internal NIC goes haywire (but isnt down) I want to be able to manage through the management interface.

Justin

It is a 6500 but I dont want to do NAT.

Thanks for your help. I think I'm just going to leave the MGMT int unplugged and plug directly in it if trouble occurs. I'll enable management on the internal NIC.

Seems odd to me as this typically is not how a management port works.