[c-nsp] CSCea21516...WHY no fix for 12.2T

[james edwards]

According to your TAC control plane is broken for 7206XVR in 123T.

james
----- Original Message ----- 
From: "Siva Valliappan" <svalliap at cisco.com>
To: "Daniel Roesen" <dr at cluenet.de>
Cc: <cisco-nsp at puck.nether.net>
Sent: Monday, October 11, 2004 3:49 PM
Subject: Re: [c-nsp] CSCea21516...WHY no fix for 12.2T


> we now support MQC service policies for control plane generated
> traffic in both input and output directions starting with 12.3(7)T
> and 12.2(25)S.
> 
> this means you can put an outbound service policy on the control
> plane interface, allowing you to acheive the result that you want
> below.  define a policy that will only permit inbound and outbound
> control plane traffic to specific loopbacks, etc.  so not quite
> clean, but at least with some configuration you can get most of
> the functionality you are looking for.
> 
> cheers
> .siva
> 
> On Mon, 11 Oct 2004, Daniel Roesen wrote:
> 
> > On Mon, Oct 11, 2004 at 03:20:39PM -0600, james edwards wrote:
> > > BUT, there is no control plane in 123 mainline.
> >
> > I'm waiting for the option to dedicate a specific interface /
> > subinterface as "management interface" and tie all the OAM stuff
> > (SNMP, RADIUS, SSH, telnet, rsh, TACACS, ...) to this interface
> > (instead of managing ACLs specifying IP ranges).
> >
> >
> > Best regards,
> > Daniel
> >
> > --
> > CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at 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 at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/