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.
I have a site with MX68 and a MR44 attached. when site first boots up all user connecting to wifi on MR44 can talk to server connecting to MX68 but after a while, maybe 8 hr, it all stops. arp table on the MR44 looks like this below. it seems broadca...
we are testing version 3.3 p2 and when I point my existing user ,which are working fine on version 3.2 p5 , they start getting the action required that asking them to sign in to the network. this does not happen on verision 3.2 only on version 3.3. i...
i'm installing Cisco ISE 3.3 in Azure. after node is installed and I change the IP to static, I can not ssh to the node with public key or via the Azure Serial console and it seems ISE service won't start either. i've tried multiple times with new in...
HX data platform 2.1(1c) failed at cluster creation with the following error. I see the cluster created in vCenter. any help is appreciated.
Failure occurred during 'Cluster Creation' process: Some(VI SDK invoke exception:; nested exception is: j...
I have 2811 gateway running IOS 124.20-T6 (SRST V7.0) and 7942 phones. when the gateway was first installed and SRST enabled, 7942 were able to register to 2811 gateway during SRST. But after a while phone can not register to the ...
I feel your pain. upgraded to 3.2 with one onprem and one Azure node and the nightmare began. opened almost 10 TAC cases and can never found out the cause. finally we found a bug that is causing our issue that cisco can not figure out. went on for mo...
we have another azure ISE version 3.2 in the same azure vnet without this issue. that one has tons of other problems that's why we are trying to get rid of it by going to version 3.3.
I installed a vm version on one of my UCS server and the issue did not occur. so the problem is caused by Azure ISE and cisco TAC has no idea and don't even reply to any email anymore after I sent them the logs they asked. My advise to those thinking...
I thought that fixed the issue with limited testing but with more testing we still have the same issue with asking user to sign in. Cisco TAC has no idea either.
