Yes these commands should work and they should not disturb exisiting ASA setup but you should always make these sort of changes out of hours just in case.
Is there a particular reason why you don't want this server on the inside of your ASA. The other solution is use a hub/switch between your inside interface of your 1841 and the external interface of the pix and then address the server with the public ip address - no need for NAT.
If you have any spare interfaces on the ASA then you could put it there. It depends on how much protection you want for the device.
You can attach it to the router but then you won't have a firewall protecting it just a stateless access-list. It comes down to which directions the connections to and from this server will be initiated. And whether this server will have to talk to clients on the inside of your ASA device.
So if connections are initiated from the Internet to this device you definitely don't want it on the inside of your ASA device.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...