Hey,
Had a closer look at the commands you requested and tried again. Looking better!
asa5545-fw/admin# changeto system
asa5545-fw# more system:running-config
: Saved
context admin
Part of the running-config
context ctxt-dmzout
config-url disk0:/ctxt-dmzout.cfg
!
context ctxt-dmzin
config-url disk0:/ctxt-dmzin.cfg
!
context ctxt-general
config-url disk0:/ctxt-general.cfg
!
[Implemented] ASA multiple contexts backup
That indeed looks better - at least we know "more..." works in the system context.
From reading Cisco ASA documentation and configuration references, it still however looks like we will need context awareness in the ASA backup driver to handle it all properly.
Would the SSH access I mentioned in the last post be possible?
From reading Cisco ASA documentation and configuration references, it still however looks like we will need context awareness in the ASA backup driver to handle it all properly.
Would the SSH access I mentioned in the last post be possible?
Hi Eduardo,
1.4.0 will be officially released Nov. 8th.
If you want to test multi-context support, here is a link to a dev build which contains it:
https://goo.gl/Hs5GCR
1.4.0 will be officially released Nov. 8th.
If you want to test multi-context support, here is a link to a dev build which contains it:
https://goo.gl/Hs5GCR
Hi Tomas,
I've tested the dev version and it works perfectley with multiple contexts ASA. On the other hand we have several ASA running on Cisco Firepower chassis and it is not able to discover it. Can I help you to make it work?
2017-11-06 09:35:11.395 TRACE 24396 --- [discovery-3] n.u.c.service.cli.CliDiscoveryService : Calling driver 'CiscoDiscoveryDriver' for initial data analysis on 'LRZBMEASAINT01'
2017-11-06 09:35:11.396 TRACE 24396 --- [discovery-3] n.u.c.d.v.cisco.CiscoDiscoveryDriver : Checking prompt
2017-11-06 09:35:11.396 DEBUG 24396 --- [discovery-3] n.u.c.service.cli.CliDiscoveryService : Driver 'CiscoDiscoveryDriver' returned partial potential for 'XXXXXXX'
Should I open this issue as a new requested feature?
Thanks!
Eduardo
I've tested the dev version and it works perfectley with multiple contexts ASA. On the other hand we have several ASA running on Cisco Firepower chassis and it is not able to discover it. Can I help you to make it work?
2017-11-06 09:35:11.395 TRACE 24396 --- [discovery-3] n.u.c.service.cli.CliDiscoveryService : Calling driver 'CiscoDiscoveryDriver' for initial data analysis on 'LRZBMEASAINT01'
2017-11-06 09:35:11.396 TRACE 24396 --- [discovery-3] n.u.c.d.v.cisco.CiscoDiscoveryDriver : Checking prompt
2017-11-06 09:35:11.396 DEBUG 24396 --- [discovery-3] n.u.c.service.cli.CliDiscoveryService : Driver 'CiscoDiscoveryDriver' returned partial potential for 'XXXXXXX'
Should I open this issue as a new requested feature?
Thanks!
Eduardo
-
- Posts: 1
- Joined: Tue Feb 18, 2020 1:10 pm
Hi Guys,
I too have the same issue.
I can only execute the following command in "System Context"
more system:running-config.
I can not run this command in any other contexts and I have VPNs configured in other contexts.
I want to see the pre-shared keys in the other contexts.
How can i see them in clear text??
Thanks
Kasun Rajapakse
I too have the same issue.
I can only execute the following command in "System Context"
more system:running-config.
I can not run this command in any other contexts and I have VPNs configured in other contexts.
I want to see the pre-shared keys in the other contexts.
How can i see them in clear text??
Thanks
Kasun Rajapakse