Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We have a Lab environment with IE5000 running a Portchannel (LACP) between the both.
SW Version is IOS15.2(8) . In this version PTP should work togehter with Portchannel.
In our setup it seems that still not working PTP and LACP together.
Can anybody...
Hi together,has anyone an idea about the limitations with L2 flooding ?Our customer has a separate infrastructure with lots of L2 broacast domains (~100). This construct ist used for various sensors, terminals, ip-cams, etc...and some devices which m...
Hi togehter,
we have an ISE installation with integration to an AD (join) as external identtity store.
When we sniffer the connection from ISE to the DC we can see that there is Port 389 for ldap in use.
The customer wants to remove all unsecure prot...
Hi all,following scenario:for a user to authnticate we make an ldap query quering also the groups where the user is in.The user can be in multiple groups and for every group where the user is in, we want to send a separate class-attribute example:use...
Hi together, I have a customer who uses still ACS 4.2.0 and after some security updates on various windows machines the login page doesnt display user/password fields because of Java failure.I suggested the customer to change the Java settings in win...
Hi together,
cisco docu ist not very clear on this point. In the Rel. 3.0 cli reference guide you find the following:
Changing the Time Zone on Cisco ISE Nodes
Changing the time zone on a Cisco ISE appliance after installation causes the Cisco IS...
Hi Scott,thanks for the information, so far.But is there a practical limitation of clients within the L2 Flooding VN and is there a practicle number of max. VN´s to be useed for that ?In our case we speak about ~ actual 100 L2 domains.
Hi Edward,thanks for your comment.I know that ACS 4.x is EOS. But the customer uses Rel. 4.2.0.x and there is still the possibility to update to 4.2.1.xxx but I dont want to make an upgrade without the hope that this problem will not occur again.:-)
