ok, i verified the bug id, but it is clearly related to VRFs. In my case, i am not yet using VRFs, so i should be safe: just verified on SXI1 code and SNMP ACL works (again: no VRFs configured).
regards, Geert 2009/11/20 Christophe Cardon <[email protected]> > Bug id is CSCee55603 > > We have found it in SXI2a and is still in SXI3. Cisco TAC says that the > fix for the bug will be integrated in SXI4 which is planned for 2010. > > ------------------------------ > *Fra:* Geert Nijs [mailto:[email protected]] > *Sendt:* 20. november 2009 08:39 > *Til:* Kevin Graham > *Cc:* Christophe Cardon; [email protected] > *Emne:* Re: [c-nsp] SXI(3) code status? > > i am also interested in a bug id. i am running the same setup, still > version SXI1, but has been running fine. > yet another thing for me on my to-do-list: verify this on sxi1 > > regards, > Geert > > 2009/11/20 Kevin Graham <[email protected]> > >> >> >> > Problem also with SNMP ACL bypass with SXI3 on VSS setup. If you >> configure ACL >> >> > to protect access to SNMP RO or RW, the ACL is not filtering and access >> is >> > granted to anyone (if you know the community string of course). >> >> Ouch, will want to track this before moving off of SXH rebuilds and >> SXI2a... Do >> you have the bugid for that (presumably not present pre-SXI3)? >> _______________________________________________ >> 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/
