Joe
I guess the reason is you don't really let your customers know about your
physical ASA setup. Same stuff as the ability to hide physical interface
capabilities and even their names.
Regards,
Piotr Kaluzny : Sr Instructor : iPexpert http://www.ipexpert.com
CCIE # 25665 :: Security
*:: World-Class Cisco Certification Training*
Direct: +1-810-326-1444
:: Free Videos http://www.youtube.com/ipexpertinc
:: Free Training / Product Offerings https://www.facebook.com/IPexpert
:: CCIE Blog http://blog.ipexpert.com/
:: Twitter https://twitter.com/ipexpert
On Thu, Dec 12, 2013 at 7:25 PM, Joe Astorino joeastorino1...@gmail.comwrote:
Oh - to confuse me more, when I SSH directly to the admin context it looks
as I would expect - ASA/admin/pri/act#
So I am really wondering why when I SSH directly to the admin context I
get the full string but when I SSH to a user context I don't.
On Thu, Dec 12, 2013 at 1:23 PM, Joe Astorino
joeastorino1...@gmail.comwrote:
I have a somewhat silly question. I have a multiple context mode setup
here with the admin context and a second context called edge. In the
system context space, I configure failover and also use the command prompt
hostname context priority state.
If I SSH to the admin context then changeto context edge this works great
and I get this:
ASA/edge/pri/act#
However, if I SSH directly to the edge context it only gives me this
prompt: ASA/edge
I am wondering first, is this normal? Second, why is this and third is
there a way to see what ASA and the state when SSH directly to a context.
Thanks!
--
Regards,
Joe Astorino
CCIE #24347
http://astorinonetworks.com
He not busy being born is busy dying - Dylan
--
Regards,
Joe Astorino
CCIE #24347
http://astorinonetworks.com
He not busy being born is busy dying - Dylan
___
Free CCIE RS, Collaboration, Data Center, Wireless Security Videos ::
iPexpert on YouTube: www.youtube.com/ipexpertinc
___
Free CCIE RS, Collaboration, Data Center, Wireless Security Videos ::
iPexpert on YouTube: www.youtube.com/ipexpertinc
