On May 15, 2009, at 4:12 AM, Elmar K. Bins wrote:
[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.
Not all of the above work on the mgmt, and i'm not talking about
netflow. You should ask these questions to Cisco directly.
- Jared
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
