>From what I've read, the netflow export is the only thing you can't do on the management port. Everything else (ntp, tacacs, snmp, syslog, ssh, file copy, whatever) should work. Granted you need to put it in a VRF, but that's trivial since it's local.
Chuck -----Original Message----- From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Andrew Miehs Sent: Thursday, May 29, 2014 7:53 PM To: Mike Cc: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] purpose of asr management port? Out of band management network instead of the console port. Sent from a mobile device > On 30 May 2014, at 5:04, Mike <mike-cisconspl...@tiedyenetworks.com> wrote: > > Hi, > > The more I look at it, the value of the onboard management port seems to be zero. While I love the idea of out of band and so forth, there are things like aaa / netflow / snmp / ssh and so forth that I want to be able to do but apparently can't be done with the build-in port, and so I'm going to burn an official gig port to do those jobs instead. > > Can anyone give me a concrete use case for the built in management gig port or should I just treat it like an unwanted appendage and move on? > > Mike- > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/