Hi The no. of MAC´s per port is not something that can be modified by a policy. The question for me would be to what policy/role the additional MAC´s should be allocated to ? I could envision some very interesting tricks with NAC 3.2 and its notification engine for this. But this has pro´s and con´s too.
Regards Markus -----Original Message----- From: Andy Middlehurst [mailto:[email protected]] Sent: Freitag, 5. Juni 2009 10:10 To: Enterasys Customer Mailing List Subject: RE: [enterasys] Policy Manager problem Garry, Others more experience with PM than I may well provide better advice, but my initial thought is stick the developers into a different role and when they authenticate, they're allowed more macs. Not sure if this is this even possible but worth a look. Regards, Andy Middlehurst -----Original Message----- From: garry crothers [mailto:[email protected]] Sent: 05 June 2009 09:02 To: Enterasys Customer Mailing List Subject: [enterasys] Policy Manager problem I am using policy manager on N3's to limit the number of authenticated macs on a port to 2. Under port properties I have the set the unauthenticated behaviour to discard and the authenticated behaviour to active. Authenticated users count is set to 2 and number of MAC users allowed is 2. I have a modified default role that does some threat management and some VLAN allocation for voip services. My question is, how can I make an exception for some developers who need multiple macs to be allowed. But without having to do this on an individual port level. I.E I would like something like an L3 policy that identifies these users and creates an exception to the 2 MAC authentication behaviour. -- Regards garry crothers --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected] --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
