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.
On ASA5520 with 7.2(2) does WRITE MEMORY command apply changes made in NAMES and/or associated outlined ACL/ACE/OBJECTGROUPS or is re-entry of any associated access-group command such as below required? If re-entry required, should NO paramenter be ...
Our network managment system is consistently reporting a reoccurrence in performance degradation on a nightly basis. Our core/dist layer is 2-6506E and access layer is 2960G's. Between the 10:20 pm and 10:30 pm CST, RTA for the same multiple device...
Retiring subnet 172.16.24.x 255.255.252.0 in phases, moving devices to 172.17.24.0 255.255.252.0. Current phase - move Messaging server devices. Senior stating that currently proposed command set for move does not make sense in terms of subnet mask...
I am migrating a Bay Accelar routing/switch which is the default gateway 172.16.24.1 for the internal network to a 3550 cluster with additional attached 2950's for server farm. Being the Accelar represented one default route, what is the simplest co...
Just had this same problem on a AIP-SSM 20 in an ASA 5520. Password-reset command would not work for me because I only had IPS version 5.x, 6.x along with ASA IOS 7.3 is requirement for command to work successfully. Therefore I performed a reimage/...
I stand corrected...my ip address change was to the ip address for each associated network-object host. So with such change would the associated interface have to be rebound/executed to activate the change:Eg. fw# access-group acl-dmz4 in interface ...
Issue was that I performed ip address changes on several devices in NAMES area related to subnet relocations and associated ACLs. After it was confirmed that communication to new subnet was working, I was later informed that it was not and that this...
Was this problem ever resolved. My users are experiencing the same problems with an Interactive page on Dow Jones. We thought the problem was our Websense content filtering software, but their tech support directed us to Cisco where they heard the ...
