ASA X-series firewalls difference & multi context features

Does anyone have a quick guide to show the feature differences between the X and regular ASA series firewalls?
And does this still hold true WRT multi-context ASA in the X-series?
No multi-context.....
- If you need to provide VPN services such as remote access or site-to-site VPN tunnels.
- If you need to use dynamic routing protocols. With multiple context mode, you can use only static routes.
- If you need to use QoS.
- If you need to support multicast routing.
- If you need to provide Threat Detection.
tia,
Will

A few changes in the new ASA version 9.0 (supported on both ASA and ASA-X series):
http://www.cisco.com/en/US/docs/security/asa/asa90/release/notes/asarn90.html#wp586890
In multiple context mode, it does support the following:
- Site to site VPN tunnels only.
- Dynamic routing protocols: EIGRP and OSPFv2 only.
- QoS is not supported.
- Multicast routing is not supported.
- Thread Detection is not supported
Here is the unsupported feature on multiple context as off Version 9.0:
http://www.cisco.com/en/US/docs/security/asa/asa90/configuration/guide/ha_contexts.html#wp1382237

Similar Messages

BVI doesn't show up in multi context ASA

I have an ASA 5585 in transparent mode, multi-context. It seems that the option to configure a BVI in one of the traffic contexts isn't there. In other words, while I see the option to configure a bridge group interface in the admin context, no such option comes up in the traffic context.
ciscoasa/admin(config)# interface ?
configure mode commands/options:
BVI         Bridge-Group Virtual Interface
Management Prefix of interface Management0/0
ciscoasa/admin(config)#
ciscoasa/admin(config)# changeto context dmz
ciscoasa/dmz(config)#
ciscoasa/dmz(config)# interface ?
configure mode commands/options:
Port-channel Prefix of interface Port-channel30.411, 30.412, 30.413, 30.414
ciscoasa/dmz(config)#
I thought that maybe I need to first allocate BVI interface(s) in the system context (in order to seem them in the traffic context) but that doesn't seem to be an option either.
ciscoasa/dmz(config)# ch system
ciscoasa(config)# interface ?
configure mode commands/options:
GigabitEthernet     GigabitEthernet IEEE 802.3z
Management          Management interface
Port-channel        Ethernet Channel of interfaces
Redundant           Redundant Interface
TenGigabitEthernet Ten GigabitEthernet
<cr>
ciscoasa(config)#
Has anyone seen this or know what the issue is? Thanks.

I think I figured it out. It seems that when you create a context, it is created in routed mode by default. So you have to explicitly go in and change it to transparent mode. Then the BVI interface shows up of course.

Wwan 3G/4G 4G LTE HWIC VPN (with dynamic ip)Configuration assistance to multi context asa

Hello All
I have a customer that has several sites all over the world and they want to use 3G and possibly 4G (where available) as a backup vpn solution.
I need some assistance/ guidance in configuring the cellular radio and configuring the vpn (dynamic ip)to work over the wwan.
Countries involved are France, Spain, Australia, Thailand and Malaysia.
I understand that I will need the APN credentials from the service provider. Is this normally the same for 3g and 4g?
Do I get chat scripts from them too?
My vpn gateway in the HQ is a Cisco multi-context asa so I can't configure remote access as its not supported yet. Can I possibly use the 1921 router(4lte hwic installed) at the sites as a hardware client?
I have seen the following urls. One has the 3g router as a "remote access" vpn but I guess this won't work in my scenario.
The other is between ios router and asa which I think will work. I don't need nat on the 3g/4g router as all traffic will be using the vpn.
http://www.networking-forum.com/blog/?p=708 . Will I need this for all the sub-interfaces I configure on the router
interface Vlan1
description LAN
ip address 10.0.0.14 255.255.255.240
no ip redirects
no ip proxy-arp
ip tcp adjust-mss 1452
crypto ipsec client ezvpn ASA inside <--is this needed per interface????
Remote access reference in config:
group-policy 3GPolicy attributes
vpn-tunnel-protocol IPSec
password-storage enable
nem enable
tunnel-group 3GRAGroup type remote-access <---Remote access config
tunnel-group 3GRAGroup general-attributes
authorization-server-group LOCAL
default-group-policy 3GPolicy
tunnel-group 3GRAGroup ipsec-attributes
pre-shared-key **Same key as the ASA profile on the 881**
http://www.cisco.com/c/en/us/support/docs/security/asa-5500-x-series-next-generation-firewalls/112075-dynamic-ipsec-asa-router-ccp.html
Anyone got a helpful configuration and guide?
Thanks
Feisal

How many default virtual context counts with ASA 5585 Series

Hi All:
I prepare replace FWSM to ASA 5585 Series,but I confuse the default virtual context counts on ASA 5585.
I used 3 virtual contexts on my old FWSM(1 admin context with 2 contexts).According the ASA configuration guide below.
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1188797
It state the ASA 5585 have default 2 contexts,Does it state the ASA 5585 just have 2 contexts or 1 admin context plus "2" context (3 contexts available)
thks fot your reply

Hi,
To my understanding the ASA with the most default lisence lets you use 2 Security Contexts to your own purposes. Admin context will always be there on the ASA when running in multiple context mode. Its created when you change your ASA from its default mode (single) to "mode multiple".
In my original post the latter part was just to mention that to my understanding if you use 2 ASAs (almost any model) in failover with a software 8.3 and above the ASA will combine their lisences regarding some values. For example connecting 2 ASAs in Failover which have limit of 2 Security Contexts, they will get combined and the failover will have 4 Security Context limit.
Atleast that is what I see with the "show version" command and this is also what we have been told by a Cisco employee. Ive also been told that if I for example (running 8.3+ OS) buy a 5 Security Context license for the other unit, It will combine the others base license (2 SC) to the others units new license (5 SC) resulting in the combined Security Context limit of 7.
This is what Cisco documentation mentions about Active/Standby and Active/Active Failover Licensing at version 8.3 and above:
Or you have two ASA 5540 adaptive security appliances, one with 20 contexts and the other with 10 contexts; the combined license allows 30 contexts. For Active/Active failover, for example, one unit can use 18 contexts and the other unit can use 12 contexts, for a total of 30; the combined usage cannot exceed the failover cluster license.
I've have had 2 ASA5585-X ASAs combined in A/A Failover running 8.4(2) and they have atleast showed that they have the combined Security Context limit of 4 Security Contexts
Heres a partial output of the "show version" command on the ASAs in question when they were just out of the box combined in Failover with no other configurations other than running in multiple context mode and management configuration in admin context.
Licensed features for this platform:Maximum Physical Interfaces : Unlimited perpetualMaximum VLANs : 1024 perpetualInside Hosts : Unlimited perpetualFailover : Active/Active perpetualVPN-DES : Enabled perpetualVPN-3DES-AES : Enabled perpetualSecurity Contexts : 2 perpetualGTP/GPRS : Disabled perpetualAnyConnect Premium Peers : 2 perpetualAnyConnect Essentials : Disabled perpetualOther VPN Peers : 10000 perpetualTotal VPN Peers : 10000 perpetualShared License : Disabled perpetualAnyConnect for Mobile : Disabled perpetualAnyConnect for Cisco VPN Phone : Disabled perpetualAdvanced Endpoint Assessment : Disabled perpetualUC Phone Proxy Sessions : 2 perpetualTotal UC Proxy Sessions : 2 perpetualBotnet Traffic Filter : Disabled perpetualIntercompany Media Engine : Disabled perpetual10GE I/O : Disabled perpetualFailover cluster licensed features for this platform:Maximum Physical Interfaces : Unlimited perpetualMaximum VLANs : 1024 perpetualInside Hosts : Unlimited perpetualFailover : Active/Active perpetualVPN-DES : Enabled perpetualVPN-3DES-AES : Enabled perpetualSecurity Contexts : 4 perpetualGTP/GPRS : Disabled perpetualAnyConnect Premium Peers : 4 perpetualAnyConnect Essentials : Disabled perpetualOther VPN Peers : 10000 perpetualTotal VPN Peers : 10000 perpetualShared License : Disabled perpetualAnyConnect for Mobile : Disabled perpetualAnyConnect for Cisco VPN Phone : Disabled perpetualAdvanced Endpoint Assessment : Disabled perpetualUC Phone Proxy Sessions : 4 perpetualTotal UC Proxy Sessions : 4 perpetualBotnet Traffic Filter : Disabled perpetualIntercompany Media Engine : Disabled perpetual10GE I/O : Disabled perpetual
Though I still suggest confirming all these things from the people/company that youre acquiring the ASA(s) from so you get what youre asking for. Or someone from Cisco could confirm this on these forums.

Add multi context asa to mars

when I try to add a multi context asa to MARS, I get error
Error occured during PIX multicontext discovery. More detailed info may be available under View Error button of individual context devices.
If you can not find detailed error info, please make sure 'hostname.domain-name' for each context device is unique"
So this mean I should change host name of each context in the ASA differrent to add to MARS ?
thank you,
Duyen

Hi duyendaica,
I try to answer, maybe you just need to add domain-name configuration in every context, not to change the hostname.
Thanks

X Series is here – New Counter Features!

Hey All,
The new X Series Multifunction DAQ devices have been announced – check them out here.
I’m posting here because I think X Series has several new counter features that many on this forum have been looking for. The user manual
will have all of these details and more with timing diagrams but I
thought I’d summarize a few of the sexier features and open it up for
comments/feedback.
First off – what stayed the same between
M Series/TIO counters and X series counters? The pinouts between M and
X series are the same so the PFI lines and default counter pinouts are
the same. The DAQmx programming is the same (you’ll need DAQmx 9.0, it
should be up this afternoon) and all the functionality that was
supported by M Series is supported by X Series, though a few behaviors
may have changed. Counters are still 32 bit.
Now on to
the fun stuff – the big one that I tend to overlook: X Series has 4
counters per board! They all have the same features and Freq Out is
still there too (with an additional 20MHz timebase).
Timebases:
X Series devices have 100MHz, 20MHz and 100kHz timebases. Note the
difference between 80MHz on M series and 100MHz on X series. DAQmx will
take care of the difference for you, unless you were programming in
terms of ticks and hardcoded in numbers based off of a 80MHz clock.
Counter
FIFOs: X Series has a 127 sample FIFO per counter. When combined with
PCIe/PXIe, our benchmarked buffered counter rates went from ~350k on M series
(with a 2 sample FIFO) with a single counter to 10MHz on all four
counters (160MB/s streaming rate). The FIFO also allows us to implement…
Buffered Counter Output: Probably my favorite new feature. You can
now use a multi point write on counters and write out a buffer of pulse
values. There are two timing modes for this: implicit and sample
clocked. With implicit timing, every idle/active pair you write is
generated as a pulse. You can vary the idle/active time for every pulse
in your pulse train. Check out the "Gen Dig Pulse
Train-Buff-Implicit-Cont.vi" shipping example. With sample clock
timing, the idle/active time are updated every time a sample clock is
received. Check out the "Gen Dig Pulse Train-Buff-Ext Clk-Cont.vi"
shipping example. These modes give you much more control over your
waveform – now everything about it can be hardware timed. Also, I’ve
benchmarked the output rates at 10MHz on all four counters at the same
time.
Finite pulse train with one counter: Each X Series
counter has an Embedded counter paired with it. The embedded counter
isn’t directly programmable, but it does allow you to do counter
operations on one counter that used to take two. A finite pulse train
used to take two counters – one to generate the pulse train and one to
gate it. Now a counter generates the pulse train, and its embedded
counter counts the TCs and disables the counter when it reaches the
number of pulses to generate.
More sample clocked
measurement modes: Edge counting and encoder measurements always
supported sample clocks, all other counter measurements were implicitly
(timed by the measurement waveform) timed. With the addition of the
sample clock terminal to the counters now all counter measurements
(except for semi-period) support sample clock timing. You can now get
the pulse width of the pulse just before the sample clock rather than
getting all the pulse widths and figuring out where they happened in
time. Why not semi period? We added a new “pulse” measurement instead
that returns a sample that contains the high and low time (or high and
low ticks, or frequency and duty cycle) so for each sample clock edge
you get a full pulse spec. Semi period still supports the same
measurements it used to, just not sample clocked. Speaking of sample
clocked…
Sample clocked frequency/period measurement
with averaging: X Series still supports the three frequency modes: Low
frequency 1 counter, 2 counter High Frequency and 2 counter Large
Range. In addition it supports sample clocked averaging. This is
essentially a method that is high accuracy method based on the sample
clock rate. With the same measurement time it has the same accuracy as
the Large range mode but it doesn’t take two counters. Note, counters
do not have their own internal sample clock so you have to provide them
with an external signal.
Hope this helps,
Andrew S
National Instruments
Multifunction DAQ Product Support Engineer
Getting Started with NI-DAQmx
Measurement Fundamentals

Hi guys,
I drew up a schematic of one of the applications I need to get running in our lab. To recap:
1)      We have several piezo controllers for nanopositioning of samples under a microscope, some of them driven by a digital circuit that handles coordinate programming and trigger line programming (for syncing detectors to the piezo motion), other controllers are analog and need to be driven by voltages.
2)      We would like to emulate the behavior of the digital controller using the analog HW (we have much more analog controllers than digital ones).
3)      The basic implementation is like this (see also slide one in the attached pdf file) and runs perfectly:
a.       A global pulsetrain ticks with a certain frequency
b.      At each tick a voltage is written on an AO line and this tick is also sent to an RTSI line to sync multiple detectors
4)      To fully emulate the digital controller we also need to implement 4 trigger lines that exist on the digital controller. These trigger lines allow for fully programmable pulsetrain output that is in sync with the movement of the piezo. Slide two in the attached pdf illustrates what is needed. These trigger lines allow for much more intricate syncing of our detectors (only measure during certain parts of the motion instead of all the time).
After a lot of thinking and experimenting with the existing M series boards back here I came to the conclusion that the desired behavior is not possible with an M series board since they only allow for the output of “simple” pulsetrains with a given frequency.
Looking at this webpage (http://zone.ni.com/devzone/cda/tut/p/id/9384#toc3) however, I think that the X series board would offer exactly what we need since it allows for buffered counter output that enables definition of very complex pulstrain “shapes”.
Looking at the schemes I provided, could someone confirm that the X-series covers our needs? If this is the case, we would be interested in purchasing these kinds of boards.
Cheers,
Kris Janssen
Attachments:
Raman Imaging Timing Implementation.pdf ‏76 KB

Multi Context IPSec VPN limitations

Hello,
We are looking to deploy mult-context IPSec lan to lan VPNs on ASA 9.x now that the functionality is available and I'm trying to understand if there are limitations to the number of tunnels that can be deployed per context? The below link may seem to indicate that there is a limit of 5 "IPSec sessions" per context but I can't see any reference to such limitations anywhere else.
http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/contexts.html#wp1147166
Does anybody know if there is a hard limit of number of IPSec connections per context or is it down to the general capabilities of the hardware (i.e. we're looking initially to deploy on 5520 so we'd get a throughput capability of 225Mb based on the datasheet -obviously depending on crypto parameters)?
Thanks

Hey found the updated document
http://www.cisco.com/en/US/docs/security/asa/command-reference/l1.html#wp1697181
Ok, this is the real document:
By default, all security contexts have unlimited access to the resources of the ASA, except where maximum limits per context are enforced; the only exception is VPN resources, which are disabled by default. If you find that one or more contexts use too many resources, and they cause other contexts to be denied connections, for example, then you can configure resource management to limit the use of resources per context. For VPN resources, you must configure resource management to allow any VPN tunnels.
vpn burst other
Concurrent
N/A
The Other VPN session amount for your model minus the sum of the sessions assigned to all contexts for vpn other.
The number of site-to-site VPN sessions allowed beyond the amount assigned to a context withvpn other. For example, if your model supports 5000 sessions, and you assign 4000 sessions across all contexts with vpn other, then the remaining 1000 sessions are available for vpn burst other. Unlike vpn other, which guarantees the sessions to the context, vpn burst othercan be oversubscribed; the burst pool is available to all contexts on a first-come, first-served basis.
vpn other
Concurrent
N/A
See the "Supported Feature Licenses Per Model" section in the CLI configuration guide for the Other VPN sessions available for your model.
Site-to-site VPN sessions. You cannot oversubscribe this resource; all context assignments combined cannot exceed the model limit. The sessions you assign for this resource are guaranteed to the context.
Value our effort and rate the assistance!

What happened to the multi-vlan feature?

I've read cisco documentation that discusses the multi-vlan feature on the 2900 XL series, but not for the 2950s. Is this functionality provided in a different way on the 2950s?

The short answer is yes, via trunking.
The multi-vlan feature was originally supported on the early 2900XL hardware since the asics used at the time did not support ISL or dot1q encapsulation. When the updated 2900XL and the 3500XL were released they had asics that did support ISL and dot1q encapsulation and so multi-vlan support was no longer required. A decision was made to keep the multi-vlan feature available for these platforms... I assume... so that customers with a mix of 'old' and 'new' hardware could configure them the same.
When the 2950 and 3550 were released a decision was made to no longer support the multi-vlan feature since the hardware of both already supported either ISL and dot1q (3550) or dot1q (2950).
HTH,
Bobby

SharePoint 2013 Multi-tenant Feature Packs

I have not seen any information in regards to multi-tenancy feature packs for SharePoint 2013. Currently it seems, with the new end user licencing, when you install the Enterprise bits you can license a user for either Standard or Enterprise but not
Foundation. In SharePoint 2010 you could use the Enterprise bits then create defined feature packs to give a site collection Foundation, Standard or Enterprise features. Do updated defined feature packs exist for 2013?
There is mention of them here http://www.harbar.net/articles/sp2013mt.aspx
"Feature Packs provide the ability to constrain the Features available for a given tenant. The fundamental capability
isn’t changed in any way here, but of course the Features in the product have. Thus the old Feature Pack definitions for SKUs are no longer valid. A new set of feature pack definitions are required encompassing all of the new Features in SharePoint 2013."
But nothing else anywhere on the net, anyone have any ideas?

Hi all,
I thought I'd give an update. I too have worked through official channels and I believe I'm making progress but not a solution unfortunately. When you run Get-SPFeature, you get 409 different features. One thing I noticed, was the features
ending with Stapler that Spence didn't add to his foundation features suggests that adding these could be erroneous. This led me to believe that my ignorance in the above message was bliss and that my idea was not going to fly. Take for example
this:
AutohostedAppLicensing
AutohostedAppLicensingStapling
So is AutohostedAppLicensingStapling a Standard or Enterprise Feature, or something internal that should not be added as it gives bad results? What about the others I don't find?
Then I posed the question - what do the ID's with EDU* in them mean? They don't exist in product info - perhaps it's education specific SKU's? Does that expose customers to use SharePoint for Internet Sites without the SKU as we assume Enterprise
would be the baseline for all 409 features and we work our way back?
Or even this - MS Access Services is a feature, yet there are 10 Feature ID's associated with it. With Exchange, there are PS commands that refer to MS Internal only and for O365 use only. What
if the 209 features Microsoft sent me as a descriptor for onprem cannot correlate to the 409 Get-SPFeature ID's I have in my bag that render my farm useless?
I've also done research around the net and it looks like everyone went the inefficient, non-multitenant way - that is, either do foundation and try to compete with O365, or offer dedicated VM farms for clients with Standard or Enterprise installs and centralise
the SQL back-end.
Surely noone has done true multitenant... Have they?
Question. If i provision a client with no -Featurepack ID, do they get nothing or the default which is Enterprise Edition? I'd presume I will get nothing or an error for not specifying a switch but I would have to build another environment to
test.... which brings me to my last point. Based on the way Std and Ent can be enabled for on-prem customers on an individual basis and I installed Standard edition on its own VM then enumerated the Get-SPFeature cmdlet, surely I'd see all the features,
not just the standard edition install features. right? If not then I'll build it, enumerate the list and my 2013 Feature pack is sorted.
The biggest fear I have on this is going it alone and if I stuff up, having a non-compliant licensing solution for every user on the system and MS banging down my door for noncompliance on something they didn't provide guidance on in the first place.
Jason.
Consultant | Nerd | Visionary. http://www.ethertech.com.au/ | http://www.deeperstates.com.au

Need help with the new Multi-cam feature in CC

Hi,
I'm trying to use the Multi-cam feature in CC and have a few questions, so would be happy with help/advice for any of the issues below. The platform is Windows 7 Pro 64bit.
The first question is what am I doing wrong? This question relates to the fact I'm trying to use Multi-cam and encountering a lot of frustrating glitches, as sometimes it seems to work and at others it doesn't.
The video I'm trying to edit comes from a dance show so I created a sequence called Act 1. I then highlighted the six clips of Act 1 with Cam 01 at the top, as I wanted the audio from this clip and made a Multi-cam feature using the audio synch. I dragged it to the sequence, set the prog window to Multi-cam and was amazed at how well it had synchronised all clips, as I could see all six clips with great audio synch from Cam 01. So far so good and after thinking how brilliant it was, things went downhill from there
I started by using ripple delete to drag to the start of Act one and then tried editing with Multi-cam. That's where I encountered the first problem, as sometimes it seemed to toggle between cams but didn't put edit points in and the selected cam had a yellow border and not a red one. At other times it inserted edit points when I changed cams and the selected cam has a red border. I can't work out what I'm doing, or not doing for this to happen. Can anyone help please?
The second question is how do I cut audio and video at exactly the same point, as I want to edit out pauses in between the different elements of the actual dance show. When I use the razor tool in Multi-cam it only cuts the video. I tried highliting audio and video using shift, but to no effect. If it matters audio and video are shown as linked when I right click. I thought I might get it to work if I revealed all original clips within the MC nest using the technique shown in "Adobe Learn." This was Ctrl double click, but it resulted in the third problem.
When I tried Ctrl double click I ended up with only Cam 02 showing in the V2 track and after some frustrating attempts at resolving this issue I decided to start all over again. I deleted the PP project and created a new one, importing everything again. I followed exactly the same procedure as I originally did to create a Multi-cam nest, but when I dragged it to the new sequence I saw Cam 02 in V2 of the sequence, which is the same as it was before I deleted the original project. Premiere Pro seems to have annoyingly remembered the actions that went wrong, so please can anyone tell me how to tell Premiere Pro not to do this?
Thanks if anyone can help me on any of the issues.

In Premiere Pro, multi-camera is accomplished by nesting a sequence. There's a new, more automated way of doing this in CC. View the steps here: http://blogs.adobe.com/premierepro/2013/04/a-quick-walkthrough-of-editing-a-multi-camera-s equence-with-clips-synchronized-by-audio.html
HOWEVER, you must be warned that multi-cam in CC is currently broken. A patch is in the works, but until it is released you should not use multi-cam in CC.

Multi-context active-active etherchannel failover

Hi All,
Is there a way to monitor individual interfaces on a box doing multicontext etherchannel failover?
I can understand on an individual box you can add monitor-interface to the physical interface, but in multi context mode, there is only one interface (the logical etherchannel subinterface) pushed through from the system context to each of the other contexts. I've been looking around and can't work out how to get a context failover to fail if only one of the etherchannel fails.
If the other box has more active etherchannels then that's the one I want active, but can't see it at the moment.
Possibly missed something somewhere. Any ideas?
Thanks,
Gaz

monitor-interface will only work on "named" interfaces. So, what you are looking to do is not possible.
The member interfaces on a port-channel will not have "nameif" associated with them.
-Kureli

What is the difference in the features between Cisco prime 1.2 and Cisco prime 1.4 ?

Dears,
Please i need to know what is the difference in the features between Cisco prime infrastructure 1.2 and Cisco prime 1.4.
Already i see the release note for each one but the release indicate only the New feature for every one. so i need to know the difference between them not new features.
Wait your kind feedback plz
Regards,

Hi,
New Features and Enhancements
The following topics describe new features and enhancements in Cisco Prime Infrastructure 1.4.
Management Support for WLC Release 7.5
Support for 802.11ac Module
Support for Cisco AP 700
Policy Classification Engine
FlexConnect Audit Support
Autonomous AP Support
Client Stateful Switchover
Cable Modem Monitoring
Support for Secure File Transfer Protocol
and please go through the link and check the data sheet for further clearance.
http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-infrastructure/datasheet-c78-729879.html

Is the multi shoots feature for the new iso 7 camera supports iphone 5 or just the 5S

Is the multi shoots feature for the new iso 7 camera supports iphone 5 or just the 5S

The 10 fps burst mode will only be available on the iPhone 5s. I believe all of the other features for sharpening photos from multiple shots are iPhone 5s only as well.

How we archieve configuration for Cisco ASA 5500 series appliances

Hi,
We need to archieve configuration for Cisco ASA 5500 series appliances.
We have Cisco works LMS 3.0.1.
Device package installed is 4.2
Any help would be appricated.
Thanks in advance.
Samir

Hi ,
Thanks for your answer.
Right now we are using TACAS to login in to the ASA. That means we need single username and password to login via
Cisoworks. Am I correct ?
Waiting for your reply.
thanks,
Samir

How does the servlet implement the multi-thread feature?

There is only one instance of every servlet in one wep application.
When several clients invoke the doPost() method of the same servlet,the servlet can process their request respectively.
So there much multi threads of one servelt.
But the Servlet doesn't implement the Runnable interface of extends the Thread class.
I wan't to know,how does the servlet/servlet container implement the multi-thread feature?

Hi johnnylzb
There is only one servlet instance existing.
(assuming u have <load-on-startup>1</load-on-startup>)
The server creates a thread for every request ..
and all the threads access the same servlet instance.
For this its not necessary for the Servlet to extend Thread or Runnable.
hope this helps

ASA X-series firewalls difference & multi context features

Similar Messages

Maybe you are looking for