The real advantage of ASR's management port is the ability to use it regardless of the IOS
condition.
Other than that, i don't know how QFP marketing was supposed to solve all things, but
netflow functionality in ASR (CPU bound?) is in infant phase.
--
Tassos
Elmar K. Bins wrote on 15/05/2009 11:12:
[email protected] (Benny Amorsen) wrote:
The mgmt port should perhaps be thought of as an ethernet version of the
console port? Personally, I would prefer that to be the case; the more
it looks like a serial port + a terminal server + a power control bar,
the better.
Which is of not much use. Initial configuration happens over the console,
and from then on, the Mgt port is supposed to be the out-of-band
management transfer, used for
- AAA (Tacacs etc)
- Logging
- ssh
- NTP
- SNMP
- SW updates
- Netflow
What's the use of deliberately disabling part of the management
functionality, just because "it might not be able to keep up
with the bandwidth"? I can easily saturate the bw with SW updates.
This forces everyone with out-of-band management and monitoring
equipment to sacrifice one of the "power ports" for management
and again run ACL based security there. Just like in the olden
days...
I think I'll also take this up with the BU, since implementation
might be two keystrokes. Yet, with the release policy on XE, we
will probably not see such a feature for quite a while.
Life sucks sometimes...
Elmar.
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
