ACE monitoring and troubleshooting

HI,
i am new to the ace and i am asking for some good websites or learning material with
-ace monitoring, troubleshooting, concepts
-how to create vips, server farms, real servers
we also need to be able to track sessions coming from the outside and see if they make it through or break somewhere along the way, is there a debug or logging feature that can help get this info

I am looking for onlite material, videos, training and white papers for troubleshooting, monitoring and maintaining the ace appliance. for example, how do I track a session to ensure it's not broken and making it all the way to the real server, etc.

Similar Messages

What happened to PDF document 22040 – "PIX/ASA: Monitor and Troubleshoot Performance Issues"?

Hi, does anyone knows what was happened to the following PDF notes in Cisco? The PDF file is only contains 1 page compared to the original notes in html format which is about a few pages.
If there is alternative link for this document, please let me know. Thanks.
Document ID: 22040
PIX/ASA: Monitor and Troubleshoot Performance Issues
http://www.cisco.com/image/gif/paws/22040/pixperformance.pdf <PDF Notes, but 1 page only?>
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a008009491c.shtml < HTML Notes>

Hi experts / marcin
can anyone of you let me know about my question related to vpn ?
Jayesh

Any tool to monitor and Troubleshoot existing Voice setup

Dear All,
Please any one assist on below given points
Existing setup facing performance and conference issue :
1> All of sudden I am facing the problem with conference calls between inter site as well as intra site, Is there any tool to troubleshoot the same?
2> Is there any tool to monitor and maintain the Voice setup?
3> Is there any tool to troubleshoot the every single problems in voice setup(CUCM / Unity connection)?
Every post would be highly appreciate.
Thank's
AT

Cisco has Unified Operations Manager. It has good monitoring capabilities and and some troubleshooting capabilities.
Check out the link below.
http://www.cisco.com/en/US/products/ps6535/index.html
HTH
Sent from Cisco Technical Support iPhone App

Monitoring and troubleshooting in-place distribution point upgrades

I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?

Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi

Advanced monitoring and report feature on ACS5.1

Hi !
I would like to know where I can find documentation about the "Advanced Monitoring and Report" feature on ACS server version 5.1.0.44-3. I would like find information about the installation, benefit of this feature, and how to use advanced monitoring and report feature.

In ACS 5.0 there was a separate licensed feature that enabled additional monitoring and troubleshooting features such as alarms, thresholds and additonal reports. In ACS 5.1 this functionality is included by default as part of the base product

Ask the Expert: Configuration and Troubleshooting the Cisco Application Control Engine (ACE) load balancer

With Ajay Kumar and Telmo Pereira
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about configuration and troubleshooting the Cisco Application Control Engine (ACE) load balancer with Cisco expert Ajay Kumar and Telmo Pereira. The Cisco ACE Application Control Engine Module for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers is a next-generation load-balancing and application-delivery solution. A member of the Cisco family of Data Center 3.0 solutions, the module: Helps ensure business continuity by increasing application availability Improves business productivity by accelerating application and server performance Reduces data center power, space, and cooling needs through a virtualized architecture Helps lower operational costs associated with application provisioning and scaling
Ajay Kumar is a customer support engineer in the Cisco Technical Assistance Center in Brussels, covering content delivery network technologies including Cisco Application Control Engine, Cisco Wide Area Application Services, Cisco Content Switching Module, Cisco Content Services Switches, and others. He has been with Cisco for more than four years, working with major customers to help resolve their issues related to content products. He holds DCASI and VCP certifications.
Telmo Pereira is a customer support engineer in the Cisco Technical Assistance Center in Brussels, where he covers all Cisco content delivery network technologies including Cisco Application Control Engine (ACE), Cisco Wide Area Application Services (WAAS), and Digital Media Suite. He has worked with multiple customers around the globe, helping them solve interesting and often highly complex issues. Pereira has worked in the networking field for more than 7 years. He holds a computer science degree as well as multiple certifications including CCNP, DCASI, DCUCI, and VCP
Remember to use the rating system to let Ajay know if you have received an adequate response.
Ajay and Telmo might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community discussion forum Application Networking shortly after the event.
This event lasts through July 26, 2013. Visit this forum often to view responses to your questions and the questions of other community members.

Hello Krzysztof,
Another set of good/interesting questions posted. Thanks!
I will try to clarify your doubts.
In the output below both resources (proxy-connections and ssl-connections rate) are configured with a min percentage of resources (column Min), while 'Max' is set to equal to the min.
ACE/Context# show resource usage
                                                     Allocation
        Resource         Current       Peak        Min        Max       Denied
-- outputs omitted for brevity --
proxy-connections             0      16358      16358      16358      17872
ssl-connections rate          0        626        626        626      23204
Most columns are self explanatory, 'Current' is current usage, 'Peak' is the maximum value reached, and the most important counter to monitor 'Denied' represents the amount of packets denied/dropped due to exceeding the configured limits.
On the resources themselves, Proxy-connections is simply the amount of proxied connections, in other words all connections handled at layer 7 (SSL connections are proxied, as are any connections with layer 7 load balance policies, or inspection).
So in this particular case for the proxy-connections we see that Peak is equal to the Max allocated, and as we have denies we can conclude that you have surpassed the limits for this resource. We see there were 17872 connections dropped due to that.
ssl-connections rate should be read in the same manner, however all values for this resource are in bytes/s, except for Denied counter, that is simply the amount of packets that were dropped due to exceeding this resource.
For your particular tests you have allocated a min percentage and set max equal to min, this way you make sure that this context will not use any other additional resources.
If you had set the max to unlimited during resource allocation, ACE would be allowed to use additional resources on top of those guaranteed, if those resources were available.
This might sound a great idea, but resource planning on ACE should be done carefully to avoid any sort of oversubscription, specially if you have business critical contexts.
We have a good reference for ACE resource planning that contains also description of all resources (this will help to understand the output better):
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A2/configuration/virtualization/guide/config.html#wp1008224
1) When a resource is utilized to its maximum limit, the ACE denies additional requests made by any context for that resource. In other words, the action is to Drop. ACE should in theory silently drop (No RST is sent back to the client). So unless we changed something on the code, this is what you should see.
To give more context, seeing resets with SSL connections is not necessarily synonym of drops. As it is usual to see them during normal transactions.
For instance Microsoft servers are usually ungracefully terminating SSL connections with RESET. Also when there is renegotiation during an SSL transaction you may see RESETS, but this will pass unnoticed for end users.
2) ACE will simply drop/ignore new connections when we reach the maximum amount of proxied connections for that context. Exisiting connections will continue there.
As ACE doesn't respond back, client would simply retransmit, and if he is lucky maybe in the next attempt he will be able to establish the connection.
To overcome the denies, you will definitely have to increase the resource allocation. This of course, assuming you are not reaching any physical limit of the box.
As mentioned setting max as unlimited might work for you, assuming there are a lot of unused resources on the box.
3) If a new connection comes in with a sticky value, that matches the sticky entry of a real server, which is already in MAXCONNS state, then both the ACE module/appliance should reject the connection and that sticky entry would be removed.
The client would at that point reestablish a new connection and ACE would associate a new sticky entry with the flow for a new RSERVER after the loadbalancing decision.
I hope this makes things clearer! Uff...
Regards,
Telmo

If I do not select F11 ( full screen ) a big part of the screen "falls" of the right hand side of my monitor and is not readable, I am not able to find the neccesary adjustments.

Question
If I do not select F11 ( full screen ) a big part of the screen "falls" of the right hand side of my monitor and is not readable, I am not able to find the neccesary adjustments.
Screen 2/3 blanco on the left side
With F11 all OK.

Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode
*https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Apple notebook batteries – maintenance and troubleshooting

Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Apple notebook batteries – maintenance and troubleshooting
Apple notebook computers use lithium-polymer (MacBooks and MacBook Pros) or lithium-ion (PowerBooks and iBooks) batteries as a portable power source. The newest members of the MacBook Pro lineup have built-in (non-removable) batteries, which are physically larger and use a modified charging scheme for a longer lifespan – you can read more about them on this linked page. The following tips should help you get the most use out of your battery, and help with troubleshooting if you are experiencing problems. A short list of do’s and don’ts is followed by more detailed information, for those who want the details.
*Do’s & Don’ts*
DO use your battery frequently and lightly, ideally completing 1-2 charge cycles per week (minimum one charge cycle per month).
DO properly calibrate your battery when new and approximately every 2-3 months thereafter.
DON’T fully discharge your battery frequently (the infrequent, periodic calibration is an exception).
DON’T store your battery (or your computer) in a high temperature environment, such as the trunk of a car, especially a fully-charged battery.
DON’T run your MacBook or MacBook Pro on AC power with the battery removed.
*Usage Pattern*
Lithium-based batteries function best when used fairly frequently but lightly. Apple states +"An ideal use would be a commuter who uses her MacBook Pro on the train, then plugs it in at the office to charge. This keeps the battery juices flowing."+ Note that there is no "memory effect" for lithium-based batteries, unlike nickel-based batteries (NiCd, NiMH) which perform best when fully discharged then fully charged. It is best not to completely discharge your battery, with the exception of calibrating it (see below). It is also not a good idea to run on AC power all the time. Note that when you are running on AC power, there is no danger of "overcharging" your battery – the Mac will not initiate charging of the battery if the current charge is 95% or higher, as described in this kbase article. Basically, a good rule to thumb is to run on AC power much of the time, but run on battery power for a while a few times per week. Using the battery for 2 full charge cycles per week equates to 300 cycles in 3 years, which is the optimal use. An explanation of a "full charge cycle" can be found on this page. Note that for Apple portables with a removable battery, you _should not_ run a MacBook or MacBook Pro on AC power with the battery removed - Apple strongly recommends against this for two reasons: first, the risk of lost data and damage to the hard disk directory structure if the MagSafe plug is accidentally disconnected, and second, the computer will reduce the CPU processor speed. The latter is due to the fact that the CPU will sometimes (for brief periods) require more power than the AC adapter can provide, and the additional power is drawn from the battery; the OS throttles back the CPU to avoid this situation.
Calibration
The battery has an integrated microchip that acts as a "fuel gauge." Calibration resets this gauge, which allows the OS to better determine times to charge and discharge the battery. Calibration should be done approximately every two months. Failure to do so for a long period of time can result in the microchip "fuel gauge" in the battery losing the ability to accurately determine the remaining charge, and it will report that there is more charge in the battery than is actually present. As a result, the computer will not initiate Safe Sleep at the proper time, and instead undergo a hard shut down, one of the main causes of hard drive directory damage. Once the battery is in the state resulting from a failure to calibrate, it is not possible to calibrate the battery, and it will need to be replaced. For Apple portables with removable batteries, note that Apple specifies, +"A _properly maintained_ Apple notebook battery is designed to retain up to 80% of its original capacity at 300 full charge and discharge cycles."+ For MacBook Pros with built-in batteries, the battery should maintain 80% of it’s original capacity for 1000 cycles. Calibration is considered part of proper maintenance.
*Battery Life and Battery Lifespan*
Battery life is how long the battery will power the computer on a full charge. To maximize battery life, consider turning down the brightness of the display, which is one of the major power consumers in a notebook computer, and if you don’t need Bluetooth and/or Airport connectivity, consider turning those off as well. Apple offers these suggestions for maximizing notebook battery life. In practice, battery life is usually somewhat less that stated in the specifications for the various Apple notebook computer models – Apple’s testing of ‘wireless productivity’ is likely limited to browsing simple websites and basic word processing. During ‘real world’ use, battery life will normally be in the range of 1-3 hours less than the specified battery life, depending on model, usage and activity. If life is shorter than expected, see the Health and Troubleshooting sections below. Battery lifespan is how many cycles/years the battery will hold sufficient charge to power the computer for a reasonable time. For Apple portables with removable batteries, a properly maintained lithium-based battery will last approximately 400-500 charge cycles or 3-4 years, +whichever comes first+. Note that this means even an unused battery loses capacity, due to the continuous nature of the chemical reaction and the buildup of oxidation in the cells. For MacBook Pros with built-in batteries, Apple’s ‘adaptive charging’ results in a significantly longer battery lifespan.
*Battery Health*
You can check the condition of your battery using System Profiler (Apple menu > About this Mac > More Info > Power section). The relevant numbers are Full Charge Capacity and Cycle Count. Mac OS 10.5 Leopard also provides a readout of battery Condition (not available in 10.4 Tiger), based on those parameters. “Health” refers to the full charge capacity of a battery relative to the nominal full charge capacity of a new battery, expressed as a percentage. Programs such iStat and CoconutBattery report the health, or you can calculate it manually: full charge capacity from System Profiler / nominal new full charge capacity * 100. For Intel-based Mac portables, nominal new full charge capacities are:
MacBook (Original, removable battery) - 5093 mAh
MacBook (Late 2008, removable battery) - 4167 mAh
13” Macbook Pro (Mid-2009, built-in battery) - 5478 mAh
15" MacBook Pro (Original, removable battery) - 5556 mAh
15" MacBook Pro (Late 2008, removable battery) - 4630 mAh
15” Macbook Pro (Mid-2009, built-in battery) - 6665 mAh
17" MacBook Pro (Original, , removable battery) - 6296 mAh
17” Macbook Pro (Mid-2009, built-in battery) - 13015 mAh
Note that health-reporting widgets (iStat Pro, CoconutBattery) use rounded values for the denominator of ‘health’. The above values are calculated from the wattage of the batteries (45 Wh to 95 Wh, see the specifications for each model, which can be found here or here) and their voltage (10.8 V for all removable batteries, 10.95 V for the 13” and 15” built-ins, and 7.3 V for the 17” built-in; those values are printed on the batteries); these capacities are nominal, and in practice new batteries will have full charge capacities that are slightly higher or lower than those values. PowerBooks and iBooks have batteries ranging from 45 Wh to 61 Wh - specs for individual models can be found here or here); these Li-ion batteries are all 10.8 V, so nominal new full charge capacity can be calculated by multiplying battery Wh x 92.6. (For the curious or algebraically-inclined, 92.6=1000/10.8, which converts Wh to mWh and divides by voltage to yield mAh, based on I=P/V derived from Ohm’s law). When Apple specifies, +"A properly maintained Apple notebook battery is designed to retain up to 80% of its original capacity at 300 full charge and discharge cycles,"+ they are referring to 80% health. Please note that health fluctuates from cycle to cycle, depending on factors such as the pattern of charging within recent cycles, ambient temperatures during use, and time since last calibration. It is normal for health to move up and down within a range of ~10% (e.g. between 86% and 96% over time).
*Troubleshooting – short battery life and sudden shutdowns*
If battery life is unacceptably short, it may be due to a background process that is running a high percentage of CPU activity. Check Utilities > Activity Monitor > CPU tab, set the pop-up menu to Active Processes, click on the CPU column to sort, and see if anything is using a high amount of CPU capacity. Short life and sudden shutdowns may also be due to a defective or an old battery - check the battery health and cycle count. If the cycle count is in the 400-500 range (or higher) for removable batteries, the battery has exceeded its useful life, and needs to be replaced. This does not indicate a defective battery - batteries are considered a consumable part, and need to be replaced at the end of their useful life. If the cycle count is less than 300, and the health is less than 80%, the battery may be defective - this applies primarily to the newer, Intel-based Mac portables. For a certain period of time (a rather long period, in fact), Sony produced defective batteries (both Li-polymer and Li-ion) - this issue affected many laptops (Apple, Toshiba, Dell, etc.) that use batteries manufactured by Sony. Apple officially acknowledged these defects for Intel-based notebook computers, as stated on this page, and extended the battery warranty to two years from date purchase for all Core Duo machines bought between February 2006 and April 2007. Battery Update 1.2 was designed to test batteries and expose defects. Note that there were actually two battery replacement programs from Apple concerning Intel-based Macs – both programs are _now officially closed_. One was an exchange/recall for specific serial numbers, and applied only to a relatively small number of 15” MacBook Pros; the other was the more general replacement program for the defective Sony batteries. There was also an exchange/recall for battteries in the 12" iBook G4 and 12"/15" PowerBook G4, also due to manufacturing problems at Sony (these were the batteries with a safety risk).
Following the above steps should ensure a long and useful life for the battery in your Apple notebook computer. Hope this helps...
This is the 2nd version of this tip. It was submitted on July 13, 2009 by neuroanatomist.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

Disclaimer: Apple does not necessarily endorse any suggestions, solutions, or third-party software products that may be mentioned in the topic below. Apple encourages you to first seek a solution at Apple Support. The following links are provided as is, with no guarantee of the effectiveness or reliability of the information. Apple does not guarantee that these links will be maintained or functional at any given time. Use the information below at your own discretion.
Apple notebook batteries – maintenance and troubleshooting
Apple notebook computers use lithium-polymer (MacBooks and MacBook Pros) or lithium-ion (PowerBooks and iBooks) batteries as a portable power source. The newest members of the MacBook Pro lineup have built-in (non-removable) batteries, which are physically larger and use a modified charging scheme for a longer lifespan – you can read more about them on this linked page. The following tips should help you get the most use out of your battery, and help with troubleshooting if you are experiencing problems. A short list of do’s and don’ts is followed by more detailed information, for those who want the details.
*Do’s & Don’ts*
DO use your battery frequently and lightly, ideally completing 1-2 charge cycles per week (minimum one charge cycle per month).
DO properly calibrate your battery when new and approximately every 2-3 months thereafter.
DON’T fully discharge your battery frequently (the infrequent, periodic calibration is an exception).
DON’T store your battery (or your computer) in a high temperature environment, such as the trunk of a car, especially a fully-charged battery.
DON’T run your MacBook or MacBook Pro on AC power with the battery removed.
*Usage Pattern*
Lithium-based batteries function best when used fairly frequently but lightly. Apple states +"An ideal use would be a commuter who uses her MacBook Pro on the train, then plugs it in at the office to charge. This keeps the battery juices flowing."+ Note that there is no "memory effect" for lithium-based batteries, unlike nickel-based batteries (NiCd, NiMH) which perform best when fully discharged then fully charged. It is best not to completely discharge your battery, with the exception of calibrating it (see below). It is also not a good idea to run on AC power all the time. Note that when you are running on AC power, there is no danger of "overcharging" your battery – the Mac will not initiate charging of the battery if the current charge is 95% or higher, as described in this kbase article. Basically, a good rule to thumb is to run on AC power much of the time, but run on battery power for a while a few times per week. Using the battery for 2 full charge cycles per week equates to 300 cycles in 3 years, which is the optimal use. An explanation of a "full charge cycle" can be found on this page. Note that for Apple portables with a removable battery, you _should not_ run a MacBook or MacBook Pro on AC power with the battery removed - Apple strongly recommends against this for two reasons: first, the risk of lost data and damage to the hard disk directory structure if the MagSafe plug is accidentally disconnected, and second, the computer will reduce the CPU processor speed. The latter is due to the fact that the CPU will sometimes (for brief periods) require more power than the AC adapter can provide, and the additional power is drawn from the battery; the OS throttles back the CPU to avoid this situation.
Calibration
The battery has an integrated microchip that acts as a "fuel gauge." Calibration resets this gauge, which allows the OS to better determine times to charge and discharge the battery. Calibration should be done approximately every two months. Failure to do so for a long period of time can result in the microchip "fuel gauge" in the battery losing the ability to accurately determine the remaining charge, and it will report that there is more charge in the battery than is actually present. As a result, the computer will not initiate Safe Sleep at the proper time, and instead undergo a hard shut down, one of the main causes of hard drive directory damage. Once the battery is in the state resulting from a failure to calibrate, it is not possible to calibrate the battery, and it will need to be replaced. For Apple portables with removable batteries, note that Apple specifies, +"A _properly maintained_ Apple notebook battery is designed to retain up to 80% of its original capacity at 300 full charge and discharge cycles."+ For MacBook Pros with built-in batteries, the battery should maintain 80% of it’s original capacity for 1000 cycles. Calibration is considered part of proper maintenance.
*Battery Life and Battery Lifespan*
Battery life is how long the battery will power the computer on a full charge. To maximize battery life, consider turning down the brightness of the display, which is one of the major power consumers in a notebook computer, and if you don’t need Bluetooth and/or Airport connectivity, consider turning those off as well. Apple offers these suggestions for maximizing notebook battery life. In practice, battery life is usually somewhat less that stated in the specifications for the various Apple notebook computer models – Apple’s testing of ‘wireless productivity’ is likely limited to browsing simple websites and basic word processing. During ‘real world’ use, battery life will normally be in the range of 1-3 hours less than the specified battery life, depending on model, usage and activity. If life is shorter than expected, see the Health and Troubleshooting sections below. Battery lifespan is how many cycles/years the battery will hold sufficient charge to power the computer for a reasonable time. For Apple portables with removable batteries, a properly maintained lithium-based battery will last approximately 400-500 charge cycles or 3-4 years, +whichever comes first+. Note that this means even an unused battery loses capacity, due to the continuous nature of the chemical reaction and the buildup of oxidation in the cells. For MacBook Pros with built-in batteries, Apple’s ‘adaptive charging’ results in a significantly longer battery lifespan.
*Battery Health*
You can check the condition of your battery using System Profiler (Apple menu > About this Mac > More Info > Power section). The relevant numbers are Full Charge Capacity and Cycle Count. Mac OS 10.5 Leopard also provides a readout of battery Condition (not available in 10.4 Tiger), based on those parameters. “Health” refers to the full charge capacity of a battery relative to the nominal full charge capacity of a new battery, expressed as a percentage. Programs such iStat and CoconutBattery report the health, or you can calculate it manually: full charge capacity from System Profiler / nominal new full charge capacity * 100. For Intel-based Mac portables, nominal new full charge capacities are:
MacBook (Original, removable battery) - 5093 mAh
MacBook (Late 2008, removable battery) - 4167 mAh
13” Macbook Pro (Mid-2009, built-in battery) - 5478 mAh
15" MacBook Pro (Original, removable battery) - 5556 mAh
15" MacBook Pro (Late 2008, removable battery) - 4630 mAh
15” Macbook Pro (Mid-2009, built-in battery) - 6665 mAh
17" MacBook Pro (Original, , removable battery) - 6296 mAh
17” Macbook Pro (Mid-2009, built-in battery) - 13015 mAh
Note that health-reporting widgets (iStat Pro, CoconutBattery) use rounded values for the denominator of ‘health’. The above values are calculated from the wattage of the batteries (45 Wh to 95 Wh, see the specifications for each model, which can be found here or here) and their voltage (10.8 V for all removable batteries, 10.95 V for the 13” and 15” built-ins, and 7.3 V for the 17” built-in; those values are printed on the batteries); these capacities are nominal, and in practice new batteries will have full charge capacities that are slightly higher or lower than those values. PowerBooks and iBooks have batteries ranging from 45 Wh to 61 Wh - specs for individual models can be found here or here); these Li-ion batteries are all 10.8 V, so nominal new full charge capacity can be calculated by multiplying battery Wh x 92.6. (For the curious or algebraically-inclined, 92.6=1000/10.8, which converts Wh to mWh and divides by voltage to yield mAh, based on I=P/V derived from Ohm’s law). When Apple specifies, +"A properly maintained Apple notebook battery is designed to retain up to 80% of its original capacity at 300 full charge and discharge cycles,"+ they are referring to 80% health. Please note that health fluctuates from cycle to cycle, depending on factors such as the pattern of charging within recent cycles, ambient temperatures during use, and time since last calibration. It is normal for health to move up and down within a range of ~10% (e.g. between 86% and 96% over time).
*Troubleshooting – short battery life and sudden shutdowns*
If battery life is unacceptably short, it may be due to a background process that is running a high percentage of CPU activity. Check Utilities > Activity Monitor > CPU tab, set the pop-up menu to Active Processes, click on the CPU column to sort, and see if anything is using a high amount of CPU capacity. Short life and sudden shutdowns may also be due to a defective or an old battery - check the battery health and cycle count. If the cycle count is in the 400-500 range (or higher) for removable batteries, the battery has exceeded its useful life, and needs to be replaced. This does not indicate a defective battery - batteries are considered a consumable part, and need to be replaced at the end of their useful life. If the cycle count is less than 300, and the health is less than 80%, the battery may be defective - this applies primarily to the newer, Intel-based Mac portables. For a certain period of time (a rather long period, in fact), Sony produced defective batteries (both Li-polymer and Li-ion) - this issue affected many laptops (Apple, Toshiba, Dell, etc.) that use batteries manufactured by Sony. Apple officially acknowledged these defects for Intel-based notebook computers, as stated on this page, and extended the battery warranty to two years from date purchase for all Core Duo machines bought between February 2006 and April 2007. Battery Update 1.2 was designed to test batteries and expose defects. Note that there were actually two battery replacement programs from Apple concerning Intel-based Macs – both programs are _now officially closed_. One was an exchange/recall for specific serial numbers, and applied only to a relatively small number of 15” MacBook Pros; the other was the more general replacement program for the defective Sony batteries. There was also an exchange/recall for battteries in the 12" iBook G4 and 12"/15" PowerBook G4, also due to manufacturing problems at Sony (these were the batteries with a safety risk).
Following the above steps should ensure a long and useful life for the battery in your Apple notebook computer. Hope this helps...
This is the 2nd version of this tip. It was submitted on July 13, 2009 by neuroanatomist.
Do you want to provide feedback on this User Contributed Tip or contribute your own? If you have achieved Level 2 status, visit the User Tips Library Contributions forum for more information.

Ask the Expert: Global Site Selector Configuration and Troubleshooting

Welcome to this Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about configuring and troubleshooting the Global Site Selector (GSS) with expert Swati Chopra.
GSS devices represent the next generation of application switches and global server load balancing (GSLB) appliances. Working together with the Cisco ACE Module and Cisco ACE 4710 appliance, these devices form an application-fluent networking solution that improves availability, acceleration, and security for data center applications.
The primary role of Cisco GSS is to implement the business continuance and disaster recovery policies of a business by optimizing and securing the Domain Name System (DNS) infrastructure of the data center. It does this by integrating with the DNS infrastructure and responding to the client DNS requests, thereby directing the client to the site that is best able to serve its needs.
Swati Chopra is a CCNA, CCNP, and VCP certified customer support engineer for content switching, covering technologies such as Cisco Application Control Engine, Cisco Wide Area Application Services, Global Site Selector, Cisco Content Services Switches, and Digital Media Suite. She has been with Cisco for more than three years and has worked with most of the high-end customers on content-related complex cases. She completed her master’s degree in finance, was heading an online education project in collaboration with e-Sylvan, and later moved to technical services because of her love for technology. She is actively involved with diverse Cisco initiatives such as Connected Women, WISE, and Cisco Career Connections and recently hosted a “Birds of Feather” table at Cisco’s Women of Impact conference.
Remember to use the rating system to let Swati know if you have received an adequate response.
Because of the volume expected during this event, Swati might not be able to answer every question. Remember that you can continue the conversation in the Data Center community under subcommunity Application Networking shortly after the event. This event lasts through April 25, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Sarah,
The load balancing mechanism for GSS requests is done via different methods. We can use these methods to define how the load is shared for different balance clauses within the same rule. The 6 methods we use are:
–round-robin—The GSS cycles through the list of answers that are available as requests are received. Each resource within an answer group is tried in turn. The GSS cycles through the list of answers, selecting the next answer in line for each request. This is the default.
eg: if we have 2 answers in answer group then GSS will provide them alternatively.
–least-loaded—The GSS selects an answer based on the load reported by each VIP in the answer group. The answer reporting the lightest load is chosen to respond to the request.The least-loaded option is available only for VIP-type answer groups that use a KAL-AP or Scripted keepalive, as they provide the GSS with detailed information on the SLB load and availability.
eg: if one answer has higher load than the other, than first answer will not be provided until its load goes down the other answers
–ordered—The GSS selects an answer from the list based on precedence; answers with a lower order number are tried first, while answers further down the list are tried only if preceding answers are unavailable to respond to the request.
for eg: answer with ordered number 1 will be provided first till it becomes unavailable. Once it is unavailable then answer with ordered list number 2 will be provided
–weighted-round-robin—The GSS cycles through the list of answers that are available as the requests are received, but sends requests to favored answers in a ratio determined by the weight value assigned to that resource.
eg: if one answer has more weight(80%) than the other answer(20%), then it will be used 8 times out of 10.
–hashed— When the GSS uses the hashed balance method, elements of the client's DNS proxy IP address and the requesting client's domain are extracted to create a unique value, referred to as a hash value. The unique hash value is attached to and used to identify a VIP that is chosen to serve the DNS query.
The use of hash values makes it possible to "stick" traffic from a particular requesting client to a specific VIP, ensuring that future requests from that client are routed to the same VIP. This type of continuity can be used to facilitate features, such as online shopping baskets, in which client-specific data is expected to persist even when client connectivity to a site is terminated or interrupted.
The GSS supports the following two hashed balance methods. You can apply one or both hashed balance methods to the specified answer group.
• By Source Address—The GSS selects the answer based on a hash value created from the source address of the request.
• By Domain Name—The GSS selects the answer based on a hash value created from the requested domain name.
for eg: a user using same source ip will get the same answer from GSS if we do source address hashing.
-DNS Race (Boomerang) Method-The GSS supports the DNS race (boomerang) method of proximity routing, which is a type of DNS resolution initiated by the GSS to load balance 2 to 20 sites.
The boomerang method is based on the concept that instantaneous proximity can be determined if a CRA within each data center sends an A-record (IP address) at the exact same time to the client's D-proxy. The DNS race method of DNS resolution gives all CRAs (Cisco content engines or content services switches) a chance at resolving a client request and allows for proximity to be determined without probing the client's D-proxy. The first A-record received by the D-proxy is, by default, considered to be the most proximate.
Use case is mainly with CRA's.
Hope this helps. Please feel free to revert if you have follow-up questions.
Thanks,
Swati

FWSM interface monitoring and best practices documentation.

Hello everyone
I have a couple of questions regarding vlan interface monitoring and best practices specifically for this service module.
I couldn’t find a suggestion or guideline as for how to define a VLAN interface on a management station. The FWSM total throughput is 5.5gbs and the interfaces are mapped to vlans carried on trunks over 10gb etherchannels. Is there a common practice, or past experience, to set some physical parameters to logical interfaces? "show interface" command states BW as unknown.
Additionally, do any of you have a document addressing best practices for FWSM? I have this for other platforms and general recommendations based on newer ASA versions but nothing related to FWSM.
Thanks a lot!
Regards
Guido

Hi,
If you are looking for some more command to check for the throughput through the module:-
show firewall module <number> traffic
Also , I think as this is End of life , you might have to check for some old documentation from Cisco on the best practices.
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/prod_white_paper0900aecd805457cc.html
https://supportforums.cisco.com/discussion/11540181/ask-expertconfiguring-troubleshooting-best-practices-asa-fwsm-failover
Thanks and Regards,
Vibhor Amrodia

Content Engine transaction logs -- monitoring and analysis

At our remote sites there's a local Cisco CE511 to ease our WAN bandwidth. I have been tasked to find a method to gather CE usage for trending and troubleshooting.
From my search on the internet I decided to go with the Webalizer application. I setup the CEs to export their transaction logs every hour to my FTP server. After a test of Webalizer on a log file, it produced a nice HTML report for that hour.
I would like to discuss with anyone on bringing this up to a new level. I would like webalizer to run as a cron job, but the log file names changes every hour. So that's a hurdle I need to figure out. Also keeping track of user web hits is important. I would like to make sure my reports are accurate in reporting what IP address is the top talker.
I hope this will start a productive exchange of ideas. Thanks.

Simple Network Management Protocol (SNMP) is an interoperable standards-based protocol that allows for external monitoring of the Content Engine through an SNMP agent.
An SNMP-managed network consists of three primary components: managed devices, agents, and management systems. A managed device is a network node that contains an SNMP agent and resides on a managed network. Managed devices collect and store management information and use SNMP to make this information available to management systems that use SNMP. Managed devices include routers, access servers, switches, bridges, hubs, computer hosts, and printers.
An SNMP agent is a software module that resides in a managed device. An agent has local knowledge of management information and translates that information into a form compatible with SNMP. The SNMP agent gathers data from the Management Information Base (MIB), which is the repository for information about device parameters and network data. The agent can also send traps, or notification of certain events, to the manager.
http://www.cisco.com/en/US/products/sw/conntsw/ps491/products_configuration_guide_chapter09186a0080236630.html#wp1101506

Configuring and Troubleshooting Virtual Switching System (VSS)

With Anand Ganesan
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to monitor, configure, and troubleshoot the Virtual Switching System (VSS) in Cisco Catalyst 6500 Series Switches with expert Anand Ganesan.
VSS is network system virtualization technology that pools multiple Cisco Catalyst 6500 Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop communications, and scaling system bandwidth capacity to 1.4 Tbps. At the initial phase, a VSS will allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch called a virtual switching system 1440 (VSS1440).
For more information, visit: www.cisco.com/en/US/prod/collateral/switches/ps5718/ps9336/prod_qas0900aecd806ed74b.html
The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
Anand Ganesan is a customer support engineer in the High-Touch Technical Service team at Cisco specializing in switching protocols. He has been supporting major service providers and enterprise customers in switching and all other switching technologies for more than two years with Cisco. He has a total of eight years of experience in the IT industry. He holds a bachelor of engineering degree from Bharathiyar University, Coimbatore.
Remember to use the rating system to let Anand know if you have received an adequate response.
Because of the volume expected during this event, Anand might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure subcommunity, LAN Switching & Routing shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Okay..they are two different /30 networks.
my BFD interfaces are GigabitEthernet1/3/48 and GigabitEthernet2/3/48 and they work fine.
interface GigabitEthernet1/3/48
description Switch 1 BFD Interface
no switchport
ip address 10.48.0.17 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
interface GigabitEthernet2/3/48
description Switch 2 BFD Interface
no switchport
ip address 10.48.0.21 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
switch virtual domain 1
switch mode virtual
switch 1 priority 110
dual-active pair interface GigabitEthernet1/3/48 interface GigabitEthernet2/3/48 bfd
show switch virtual dual-active bfd
Bfd dual-active detection enabled: Yes
Bfd dual-active interface pairs configured:
interface-1 Gi1/3/48 interface-2 Gi2/3/48
router eigrp 1
network 10.0.0.0
network 10.1.201.0 0.0.0.255
network 10.48.0.12 0.0.0.3
network 10.48.177.0 0.0.0.255
network 97.0.0.0
network 99.0.0.0
network 100.0.0.0
network 100.7.7.0 0.0.0.255
network 192.34.145.0
network 192.168.15.0
show ip ei in
EIGRP-IPv4 Interfaces for AS(1)
                       Xmit Queue   Mean   Pacing Time   Multicast   Pending
Interface       Peers Un/Reliable SRTT   Un/Reliable   Flow Timer   Routes
Gi1/2/40           1       0/0         1       0/1           50           0
Gi1/2/41           0       0/0         0       0/1           0           0
Vl1               1       0/0         1       0/1           50           0
Vl7               0       0/0         0       0/1           0           0
Vl13               0       0/0         0       0/1           0           0
Vl15               0       0/0         0       0/1           0           0
Vl21               0       0/0         0       0/1           0           0
Vl25               0       0/0         0       0/1            0           0
Vl26               0       0/0         0       0/1           0           0
Vl134             0       0/0         0       0/1           0           0
Vl135             0       0/0         0       0/1           0           0
Vl140             0       0/0         0       0/1           0           0
Vl300             0       0/0         0       0/1           0           0
Vl400             0       0/0         0       0/1           0           0
Vl199             0       0/0         0       0/1           0           0
Vl6               0       0/0         0       0/1           0           0
Vl20               0       0/0         0       0/1           0           0
Vl24               0        0/0         0       0/1           0           0
Vl30               0       0/0         0       0/1           0           0
Vl31               0       0/0         0       0/1           0           0
Vl37               0       0/0         0       0/1           0           0
Vl2               0       0/0         0       0/1           0           0
Gi1/3/48           0       0/0         0       0/1           0           0
Gi2/3/48           0       0/0         0       0/1           0           0
Vl17               0       0/0         0       0/1           0           0
Gi2/6/40           0       0/0         0       0/1           0           0
Gi2/6/41           0       0/0         0       0/1           0           0
Gi2/1/45           1        0/0         1       0/1           50           0
Gi1/1/33           1       0/0         1       0/1           50           0
My questions revolve around the same point.
Are there any significance in running eigrp or any other routing protocol over this BFD link?
Is the Dual active scenario detected by BFD or BFD notifies a routing protocol like eigrp and in turn dual active is detected?
Should I suppress the eigrp HELLOs on these interfaces to get rid of the log message?
Regards
Vinayak

VoIP Monitoring and Management Tools

Does anyone have suggestion on VoIP monitoring and management tools for large enterprise voip infrastructure?
We are in the final phase of 8000 phone cut-over across 2 location (2clusters) and need some advice on choosing the right monitoring system.
I saw Qovia have Cisco approved monitoring tools.
Does anyone ever use this? any suggestions or advice?
Thanks in advance
Bonaldi Kresnanto

Bonaldi,
Monitoring voice quality is just one aspect of ongoing operations. It is equally (if not more) important to have the ability to remotely troubleshoot end-user problems, manage configuration changes, and perform active testing on a regular basis before users are impacted.
In addition, whenever you make changes to your IPT system (e.g. CallManager upgrades/patches, IOS upgrades, power outages) you'll definitely want the ability to verify the system is still operating as design. Using the active tests you can do this easily and in an automated fashion.
ClarusIPC Operations is the only product that addresses these needs. It is also just as valuable during the deployment as ongoing operations to help you make changes and deploy new phones with the same product you day-to-day.
I'd like to talk to you more about the product and how it can be used in your environment.
David Roberts
[email protected]

Silent Monitor and Call record with voice vlan

We are pretty new to CCX, and want to get silent monitor and call recording working. I've read a bunch of troubleshooting docs, and a bunch of the discussions here, but I am still unable to get it to work the way that I want.
Heres the setup. The phones are all set to the recommended settings, and the agent pc is plugged into the phone. The data vlan is 111 and the voice vlan is 222. When I run the nicq prog on the agent pc, it can not find the phone, but I can enter the ip in , and it sees the phone. The supervisor laptop can not monitor or record.
If I change the voice vlan to 111, nicq still can not find the phone, but the supervisor can record and monitor with no problem. Is is an issue with 802.1q and perhaps my nics do not support it?
CCX Ver:
8.5.1.11004-25

Hi
It could be, but it's pretty rare.
Have you enabled 'PC Port Voice VLAN Access' and 'SPAN to PC Port' on the phone?
Have you tried alternate PCs/laptops on the back of that phone?
Aaron

AE CC loses connection with second monitor and audio mixer (BLACKMAGIC) when switching to desktop

specifications:
Mac OsX 10.7.5
AE cc (part of creative cloud, up-to-date) NOT TRIAL VERSION
software for connecting monitor and adui mix panel: Blackmagic Desktop Video 10.0
second monitor: Sony Trimaster EL PVM 2541
audio mix panel: Behringer Xenyx x1204USB audio mixer
Blackmagic connects the Sony screen + Behringer Xenyx x1204USB audio mixer to the mac computer.
the problem:
When working in after effects, we link the program to show the video preview on the second screen (the sony one)
While the work area is still visible on the Mac screen.
The audio is also regulated through Blackmagic so we can mix on the xenyx mix panel.
Everything works fine as long as we stay in after effects.
If, for a brief moment, even a second, we swhitch to the desktop, or an other program (internet, acrobat reader, etc) After effects looses the connection to Blackmagic (forgets it exists). So we suddenly have no audio, or no longer a seperate video preview image.
The option to select Blackmagic in the dropdown menu is also gone.
If we restart After effects though, it's connected again.
Any ideas?
I added two screenshots to clarify.
The screenshots is when it does work, and after effects still recognizes blackmagic.
Cheers,
Andreas

When this happens, open Activity Monitor. Is Adobe QT32 Server running? That is required for QuickTime video preview. If it is not running, this is the troubleshooting you want to do:
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html
In the next update to After Effects CC, the old QuickTime video preview (on Mac; DirectShow video preview on Windows) is being replaced by Mercury Transmit:
http://bit.ly/AE_video_preview

ACE monitoring and troubleshooting

Similar Messages

Maybe you are looking for