If you did not save the running-config to the startup-config you can safely power-off the switch and reboot is. It will then load your previous configuration from the startup-config. NOTE: Keep in mind that any changes mades after your first save to the startup-config are lost. ... View more

I have this question as well. I want to use Cisco ASA 5506-X for my home lab. I have a 500/500Mbps connection through a 1GbE uplink. I can get around 530/530Mbps (66Mb/s). I only have a few servers, a laptop/desktop and a few wireless devices. I wonder if this model can take it. I am not going to use the FirePOWER services. I don't mind buying a ASA 5508-X, but is has a built-in fan with does make a lot of noise. So according to the specs I am currently a bit disappointed about the performance. ... View more

Excellent! ... View more

The last few days I have done a lot of research. Some things are different than we might expect. Just to point out one, the following quote comes straight from TechNet: Some Intel multi-core processors may use Intel Hyper-Some Intel multi-core processors may use Intel Hyper-Threading technology. When Hyper-Threading is enabled, the actual number of cores that are used by dVMQ should be half the total number of logical processors that are available in the system. This is because dVMQ spreads the processing across individual physical cores only, and it will not use hyper-threaded sibling cores. As an example, if the machine has an Intel processor with four physical cores, and Hyper-Threading is enabled, it will show a total of eight logical processors. Only four logical processors are available to VMQ. VMQ will use cores 0, 2, 4, and 6. technology. When Hyper-Threading is enabled, the actual number of cores that are used by dVMQ should be half the total number of logical processors that are available in the system. This is because dVMQ spreads the processing across individual physical cores only, and it will not use hyper-threaded sibling cores. As an example, if the machine has an Intel processor with four physical cores, and Hyper-Threading is enabled, it will show a total of eight logical processors. Only four logical processors are available to VMQ. VMQ will use cores 0, 2, 4, and 6. According the Cisco help information you should configure the Number of Interrupts (in the VMQ Connection Policy) to the number of logical processors in your server. But VMQ only applies to physical processors. Hmmm... ok. I also found the following quotes from TechNet and other resources: Changing number of available CPU may affect the number of RSS queues. When number of available CPUs is lower than currently configured number of RSS queues, Windows OS will silently lower number of RSS queue to match number of CPUs. This sounds to me that if you configure a larger Number of VMQs (in the VMQ Connection Policy) it is automatically downsized to the maximum number of CPUs available in your system or when manually limited with Set-NetAdapterVmq. With other words, number of VMQs never exceed the maximum available CPUs. This sounds quit logical to me, why should you have more queues than physical CPU's available. There may be situations where starting with logical processor 0 (which corresponds to core 0) as the RssBaseProcNumber is acceptable. However, general guidance is to avoid using core 0 as the base CPU because it is generally used for default network queues and workload processing in the root partition. Based on the root virtual processor utilization, the RSS base and maximum logical processors for a physical network adapter can be configured to define the set of root virtual processors that are available for VMQ processing. Selecting the set of VMQ processors can better isolate latency-centric or cache-sensitive virtual machines or workloads from root network processing. Use the Windows PowerShell cmdlet, Set-NetAdapterVmq, to set the correct base processor number and the maximum processor number. When a host has multiple network adapters, each for a different virtual switch instance, and it is using dVMQ, do not configure dVMQ to use overlapping processor sets. Ensure that each network adapter that is configured for dVMQ has its own set of cores. Otherwise performance results may be impaired and unpredictable. Ok, apparently VMQ tuning is a best-practice. All processing occurs on the base (e.g. 0:0) processor, until LP (Logical Processor) exceeds 90%. Then one VM traffic will be re-directed to another LP. I have tested this and indeed this is what happens. But by default, ALL your VMs will initially use the BaseProcessor until the LP/core/BaseProcessor exceeds 90%. If you have 16 LPs (with Hyper-Threating, but only counting the physical processor) and have 2 NIC's with a vSwitch it might be best-practice to assign 8 LPs to each NIC each. Each NIC with it's own BaseProcessor. ... View more

I configure the Number of Interrupts value to the number of 'threads' or 'logical processors' as shown by UCS Manager. The only question remains, should you device this value tot he number of vNICs (that host VMs) you configured on your Service Profile? Now, about the Number of VMQs. Cisco has different VICs. For example a VIC 1240 or 1280. But you can also have a VIC 1240 + Port Expander. A VIC 1240 + Port Expander seems to be capable of 256 VMQ's. Now that we know that, there is another thing to keep in mind. How many vNIC (vEth) do you provision in a Cisco UCS Service Profile. To give an example, I use the following: VM-Ethernet-A (connected to Fabric A, with FF to Fabric B) VM-Ethernet-B (connected to Fabric B, with FF to Fabric A) VM-iSCSI-A (connected to Fabric A, with FF to B) VM-iSCSI-B (connected to Fabric B, with FF to A) I am not sure you should divide the available VMQs to these vNIC (Service Profile). I am almost certain you should because I can't get above 256. But I don't think setting the number of VMQs to the maximum is a good thing. Because a VMQ is linked to an Interrupt which then seem to stack up. If you don't use all VMQs the load may not be equally divided. It sounds logical to look at the number of vNICs (Hyper-V) from all your VMs. The downside is this can vary a lot. Especially when you are doing maintenance and shutdown the cluster resource node (e.g. 3/4 up instead of 4/4). Any thoughts about this? ... View more

Any update? ... View more

I am having the the same issue with a Cisco ASA 5512-X. The alarm LED is solid amber. The commands "show environment" and "show controller pci" are all ok. We also have two Cisco ASA 5515-X in active/active multiple-context mode, their alarm LED is off. Any suggestions? ... View more

Hi Osama, I am familiar with that issue. You have to remove the driver CD-ROM (e.g. iSO), re-insert the Windows setup DVD. Then hit 'Refresh'. only then your disks will be recognized. If that ain't work either and use NetApp, make sure you have configured a LUN ID on your iGroup settings. But I think the DVD and refresh will probably work. ... View more