Hello,We intend to use MACL to filter inbound traffic on SVI interfaces,my question is where would the mac-addresses for the MACL be stored? i hope not in the configuration because we have a large pool of mac addresses to use. Scenario: We use a GPO...
Hello, how do i increase the ssh timeout to 10mins or morewhen i use the show ip ssh....i could see the default has 120sec Is there a cisco command to increase the ssh timeout?
Please explain to me if this will not disruption in my network.I am trying to remove the dafault QoS on firewall interfaces on the cisco 9200 stack.I got this warning cisco-stack1(config)#interface te 1/1/1cisco-stack1(config-if)#no service-poli...
I have host within the same subnet unable to communicate with the server and subjected to ACL configured which should not be happening.Essentially,from the traffic capture we can see destination mac address of the svi vlan24 gateway,this is wrong its...
I noticed our switch randomly block phones on vlan 34 which is odd.Some of this communication are within the same subnet and should not be hitting the access list at all.Here is my log .29.132(48378) (Vlan34 004e.006e.0000) -> 10.20.28.13(80), 1 pack...
Thank you for your response.Currently the situation is :a. The phone has no arp entry for the server hence the phone by default sends traffic to its gatewayb. The phone for some reason is incorrectly mapping the arp resolution for the ip address of t...
Hello,The hosts are on the same switch( I meant several hosts within vlan 24 are are trying to communicate with the server( 10.20.28.X).Very Respectfully,TemiTraffic destined to 10.20.28.X should have the mac address of 10.20.28.X,"
Hello,Thank you for your response.The destination is not on the same switch the destination is a linux server(10.20.28.x)I noticed that when we removed/reconfigured the ACL on SVI vlan24 the server 10.20.28.1 send an arp reply to 10.20.29.233 and the...
The hosts are on the same switch,other host can connect to the server.Traffic destined to 10.20.28.X should have the mac address of 10.20.28.X, this issue could be caused by a possible corruption of the arp packets being distributed along the network...
