WAE 612 Log

Hi,
Has anyone seen this message before??
Jun 2 07:37:44 Site-WAE-1 tcpproxy: %WAAS-RE-3-690422: (548714) conn-id: 5784671: RE Aggregation error: process_full_tree failed -1105 (Read failed: not found)
The message is not in the alarm book for version 4.0.17.b.14....should I be concerned?

Mike,
This message deals with a particular connection-id (5784671) and DRE aggregation information. I don't think you need to be concerned unless you start seeing this a lot in the syslogs.
Dan

Similar Messages

WAE 612 + ACNS 5.5.5 Help

I've been trying to setup a WAE 612 w/ ACNS 5.5.5, and I've run into a few problems. The goal is to setup a transparent forward proxy for WMT files. This is a standalone unit. The edge router that this device is hooked up to is a Cisco 7206VXR running IOS 12.4(12).
Initially, I configured WCCP outbound redirects on the WAN facing port of our edge router, and WCCP traffic seemed to be generated between the content engine and the router. `show statistics wccp gre,` it would return something like the following:
Transparent GRE packets received: 54919
Transparent non-GRE packets received: 0
Transparent non-GRE packets passed through: 0
Total packets accepted: 1134
Invalid packets received: 0
Packets received with invalid service: 0
Packets received on a disabled service: 0
Packets received too small: 0
Packets dropped due to zero TTL: 0
Packets dropped due to bad buckets: 0
Packets dropped due to no redirect address: 0
Packets dropped due to loopback redirect: 0
Connections bypassed due to load: 0
Packets sent back to router: 53785
Packets sent to another CE: 0
GRE fragments redirected: 0
Packets failed GRE encapsulation: 0
Packets dropped due to invalid fwd method: 0
Packets dropped due to insufficient memory: 0
Packets bypassed, no conn at all: 0
Packets bypassed, no pending connection: 53785
Packets due to clean wccp shutdown: 0
Packets bypassed due to bypass-list lookup: 0
Packets received with client IP addresses: 0
Conditionally Accepted connections: 0
Conditionally Bypassed connections: 0
L2 Bypass packets destined for loopback: 0
Packets w/WCCP GRE received too small: 0
Packets dropped due to IP access-list deny: 0
Packets fragmented for bypass: 21
Packet pullups needed: 21
Packets dropped due to no route found: 0
Unfortunately, when the clients attempted to call up a WMT video, it would go through the process of buffering, initializing, and going to a ready state; but the video would not play. The 'show statistics wmt all' would only increment the error counter with each play attempt; none of the other statistics from this command would change.
Next I attempted to just set this up as a non-transparent WMT proxy and configured an individual test Windows 9 Media client to reference the WAE as an RTSP proxy. It experienced the same problem as above. 'show statistics wmt all' would still only show error count increases with each attempted video, but nothing else would increment. This leads me to believe that the problem is not WCCP related, but something with my WAE configuration. I can successfully traceroute from my WAE to the video server; likewise, I can traceroute without problems from the WAE to my Windows media client machine.
Also, when I do commands such as 'show statistics mediafs,' the values for 'space used by WMT proxy' sometimes increments for an attempt to load a video; at best, the increase is about 12KB.
Here's the current WAE configuration file:
contentengine#show running-config
device mode content-engine
hostname contentengine
ip domain-name blah.domain.com
interface GigabitEthernet 1/0
ip address 172.16.0.1 255.255.255.248
exit
interface GigabitEthernet 2/0
shutdown
exit
ip default-gateway 172.16.0.6
wmt evaluate
wmt accept-license-agreement
wmt enable
wmt max-concurrent-sessions 2500
no auto-register enable
ip name-server 172.16.0.9
logging disk priority warning
transaction-logs enable
username admin password 1 jEy9iH6cH3x2s
username admin privilege 15
authentication login local enable primary
authentication configuration local enable primary
sshd enable
mediafs-division wmt-cache-space 100 real-cache-space 0
! End of ACNS configuration
Thanks -Mike

try this configuration link:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/acns/v53/configuration/local/guide/53ldg.html

WAAS 4.0.9 /WAE 612-K9 not accelerating

I have a central site and four remote sites connected via leased lines, I receive a demo with 3 WAE-612-K9 (4.0.9 s/w version)for testing purposes. I connect one WAE as a CM and one WAE as application acceleration at the central site and the another at the remote site. I want to have Web and MS Exchange acceleration at first but I don't see any improvement. The central site have one 3845 router and the remote 2811 both with IOS 12.4(13c) version. Any help please ?

Yes I see some connetions to be optmized, my problem/question is why I cannot see http optimization for my intranet site since the traffic is marked PT .
I am using the default policy in both WAEs , as I can see the policy marks http traffic to be full optimized.
On the cms I cannot see any Reduction taking place , all traffic marks as 0.
In both WAEs sh statistics dre shows all 0's
and no hard drive space used.
The mail servers are MS Exchange 2003 with smtp connectors between them , one server per site. It's possible to improve e-mail too ?
Topology
Central site->3845-->2811-->Remote Site
| |
WAE WAE

WAE-612-K9

Hello, I have the following problem, after finish the rebuild of my Raid-1 in the WAE-612-K9 equipment, it show a critical alert:
- CMS STATUS IS OFFLINE.
I try ACTIVATE the WAE via web interface , but this doesn´t work.
Please somebody have any ideas about what happend....???
The version of software is 4.1.3A.
Thanks very much for you help.
Regards
Fernando.

Do you have telnet/ssh access to the device? If so you need to deregister the device and then re register the device. I am no expert, but this will fix the issue at the expense of histrical data.
WAASName> cms deregister /force
WAASName> config terminal
WAASName#> cms enable
WAASName#> exit
wr mem
Rob

WAE 612 deployed in HA - how do I set it up????

Can anyone give me some advise of deploying WAE at a branch site in HA Mode?
Is it possible for them to work in some kind of HA mode?
I don't plan on having the devices inline - So they will both be connected to a switch and use WCCP (well that's the plan anyway)
Any advise is welcome

Hi,
Just make sure to configure all your WAEs at a given site to talk to the same set of WCCP routers using the same WCCP services (WAAS uses WCCP services 61 and 62 by default). In this case, WCCP will automatically load-balance between all WAEs available in the WCCP cluster. WCCP will also adapt the load-balancing scheme whenever a WAE leaves or joins the WCCP cluster, thus achieving HA (if only a single WAE remains in the cluster, all load will be sent to that remaining WAE).
Please find further information on WCCP here:
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v441/configuration/guide/traffic.html
Regards,
Michael

Marking SAP packets in WAE-612 v4.1.3a

Hi,
My client ask me if i could mark the SAP traffic with Precedence 1.
What did i done ? Figure "SAP cs1.JPG"
Application Classifier = Figure "SAP Ports.JPG"
When seeing Connection Statistics in CM GUI, filtering destination port 3201, i can see connections but not see the Classifier Name as SAP ....
I had defined as "Classifier" SAP in "Policy Definitions", and had set DSCP Marking as CS1 .
How can i see, if the packets is beeing marked for that specifically Classifier ?
SAP is one of the default Classifier of Enterprise-Applications.
I only want to mark the SAP packets ...
Did i do it right ??
Best Regards.
Bruno PetrÃ³nio

Old connections ->
"When seeing Connection Statistics in CM GUI, filtering destination port 3201, i can see connections but not see the Classifier Name as SAP .... "
New connections already had SAP as Classifier Name.
Marking Packets its working, althought the global policy application is configured to copy the packets, the Classifier Policy Definitions takes priority on behalf of Default Global Policy application.
But... how can i see, in gui or cli, if the packets is beeing marked... and how many ???
Best Regards,
PetrÃ³nio

WAE and filer latency

Hello, I can see some logs into our WAE (WAE-612-K9) but I cannot find any useful information to fix it:
Host X.X.X.X:445 was not discovered, bypass period: 60 sec, number of events: 1, reason: high/unknown Core<=>Filer latency
I don't understand this filer latency... I suppose the connection is not optimized? Thanks all for your help

Ping the server from the core WAE by name and Ip to ensure name resolution and connectivity.
By default, if an edge is under 5 ms or if a core WAE is over 25 ms from a file server, it will not use the CIFS AO. However, if the traffic is being intercepted, it should be using tfo, dre, and lz. This is by design as WAAS is engineered to have the cores sitting next to the file servers to eliminate the CIFS latency effects over a WAN link.
Dan

Add RAID 1 to WAE 574

I just received a brand new WAVE-574 for our branch office, and noticed that it was shipped with a single drive configuration. I just bought an additional hard drive from Cisco to go into this WAVE-574 so the disks are configured in a RAID 1 for redandancy.   I have been looking for configuration and setup instructions, but without any luck so far.
Could you please let me know the setup procedures?
Thanks in advance for your assistance!

Hi Rocky,
The links I provided are config guide links and you only need appropriate CCO id to access them. I do not think these are partner only links.
Let me paste some of the details from the links provided by me and Fabio here:
Replacing a Hard Disk Drive
The WAVE appliance supports as many as two 3.5-inch (Large Form Factor) SATA hard drives.
When replacing hard drives to the WAVE appliance, observe the following general guidelines:
•The system automatically sets all drive numbers.
•If only one hard drive is used, install it in the bay with the lowest drive number.
•Drives must be the same capacity to provide the greatest storage space efficiency when drives are grouped together into the same drive array.
Note All hard disk drives being used in the appliance must be identical.
Caution To maintain proper system cooling, do not operate the appliance for more than 10 minutes without either a hard disk drive or a filler panel installed in each bay.
To replace a hard disk drive in a bay, follow these steps:
Step 1 Review the information in the "Safety Warnings and Cautions" section on page 2-2 and the "Safety Guidelines" section on page 2-3.
Step 2 Make sure that the chassis cover is in place and fully closed.
Step 3 Power down the device and and disconnect the power cord and all external cables.
Step 4 Slide the latch and then pull out the handle (see Figure 4-4).
Figure 4-4     Removing a Hard Disk Drive
Step 5 Pull the drive assembly from the bay.
Step 6 Wait 1 minute and then insert the new drive into the same slot by aligning the replacement drive assembly with guide rails in the bay and sliding the drive assembly into the bay until it stops. Make sure that the drive is properly seated in the bay.
Step 7 Close the drive handle.
Step 8 Reboot the WAVE appliance.
Step 9 Check the hard disk drive status LED after the system has booted to verify that the hard disk drive is operating correctly. If the amber hard disk drive status LED for a drive is lit continuously, that drive is faulty and must be replaced. If the green hard disk drive activity LED is flashing, the drive is being accessed.
Step 10 Wait 1 minute and then verify that the replaced disk drive is in the Rebuilding state by using the show disks details command in EXEC mode.
Note The system automatically starts the rebuild operation when it detects the removal and reinsertion of a drive that is part of the logical RAID drive.
Step 11 Wait until the rebuild operation is complete. A disk rebuild operation may take several hours. You can check if the rebuild operation is complete by using the show disk details command in EXEC mode. The physical drive state will be Online and the RAID logical drive state will be Okay after the rebuild operation is completed.
Step 12 Use the show disk tech command in EXEC mode to verify that the firmware and BIOS information is correct for both hard drives.
If you have multiple disk failures and your RAID-1 logical status is Offline, you must recreate the RAID-1 array. For more information on disk removal and replacement procedures, see the Cisco Wide Area Application Services Configuration Guide, Chapter 15, "Maintaining Your WAAS System."
Performing Disk Maintenance for RAID-1 Systems
WAAS supports hot-swap functionality for both failed disk replacement and scheduled disk maintenance. When a disk fails, WAAS automatically detects the disk failure, marks the disk as bad, and removes the disk from the RAID-1 volume. To schedule disk maintenance, you must manually shut down the disk.
You must wait for the disk to be completely shut down before you physically remove the disk from the WAE. When the RAID removal process is complete, WAAS generates a disk failure alarm and trap. In addition, a syslog ERROR message is logged.
Note If the removal event (such as, a disk failure or software shutdown) occurs while the RAID array is in the rebuild process, the RAID removal process may take up to 1 minute to complete. The duration of this process depends on the size of the disk.
If the WAAS software removes a failed disk during the RAID rebuild process, a RAID rebuild failure alarm is generated. If you administratively shut down the disk during the RAID rebuild process, a RAID rebuild abort alarm is generated instead.
When you install a replacement disk, the WAAS software detects the replacement disk and performs compatibility checks on the disk, initializes the disk by creating partitions, and adds the disk to the software RAID to start the RAID rebuild process.
If the newly inserted disk has the same disk ID as a disk that was previously marked bad in the same physical slot, then the disk will not be mounted, and the post-replacement checks, initialization, and RAID rebuilding will not occur.
A newly installed disk must be of the same type as the old disk and it must meet the following compatibility requirements:
•If the replacement disk is for disk00, disk02, or disk04 of a RAID pair, the replacement disk must be the same size as the running disk in the array.
•If the replacement disk is for disk01, disk03, or disk05 of a RAID pair, then the replacement disk must have the same or greater RAID capacity as the running disk in the array.
Compatibility checks, which are part of the hot-swap process, check for capacity compatibility. Incompatibility generates an alarm and aborts the hot-swap process.
Table 15-3 shows the drive-type compatibility for the WAE-612. All drives must be the same type.
Table 15-3     WAE-612 Drive-Type Compatibility Matrix
Drive Types SAS1 SATA22
SAS
Ok
No
SATA2
No
Ok
1 Serial Attached SCSI
2 Serial Advanced Technology Attachment 2
To perform disk maintenance, follow these steps:
Step 1 Manually shut down the disk.
a. Enter the disk disk-name diskxx shutdown command in global configuration mode.
b. Wait for the disk to be completely shut down before you physically remove the disk from the WAE. When the RAID removal process is complete, WAAS generates a disk failure alarm and trap. In addition, a syslog ERROR message is logged.
Note We recommend that you disable the disk error-handling reload option, if enabled, because it is not necessary to power down the system to remove a disk.
Step 2 Insert a replacement disk into the slot in the WAE. The replacement disk must have a disk ID number that is different from the disk that it is replacing.
Step 3 Reenable the disk by entering the no disk disk-name diskxx shutdown global configuration command.

Process for Adding Additional WAE to 4.0.11 Cluster with CIFS

I will be adding an additional WAE 612 W/ 4GB of memory to an existing single WAE 612/4GB cluster in the future. What is the best practice process for adding the second WAE to the cluster. I would like to do the WCCP configuration last. Whats the easiest way to move the policies from the existing WAE to the second wae. Is it as simple as just creating a Cluster Device Group and then adding both devices to the group. Will the second WAE inherit the settings for WAFS as well? I am not concerned about the WAAS setup.
I don't have access to the credentials for the CIFS connection on the core WAE today so i would really like to know if i can complete this install by just copying settings from the existing WAE using the device group settings.
I am also going to reverse the 61 and 62 settings to ensure that the inbound client connections get load balanced across the WAE properly.
Any other things to consider?
Thanks in advance
Mike

Mike,
The edges will always reconnect to the same core unless it's not available. In 4.0.x, WCCP does not effect CIFS connections (4050 connections), only load balancing the TCP connections outside the 4050 connections. I have manually load balanced edges before via expert mode on the edge GUI, but it's fairly unwieldy. How many edges do you have? I can dig up the procedure if you want to use it.
You can get decent load balancing by setting up both cores so they are both taking edge connections, take the old core offline (stopping the service in the GUI) for several minutes and then bringing it back up. A good number of your edges should now be on the new core and some will still be on the old core.
Also, remember it's best practice to try and keep N+1 at your core. If you loose a core WAE in your cluster and a single Core can't handle the CIFS traffic, you will continue to get CIFS optimization.
Hope that helps,
Dan

WAAS exporting tfo logs via sftp

Hello
Running WAAS 4.0.19.
I've stuck an issue where the CLI command on an edge WAE:
transaction-logs export sftp-server 10.1.1.1 tst1wae01 password logs/raw
...is accepted but when you then try and use the Transaction Logs page of that WAE in the Central Manager's GUI and make a different change (say the interval), the GUI throws up an error:
"Directory1 must start with forward slash"
If I put a forward slash in at the GUI and save it, the export will fail.
The export works when I force the WAE to use the line specified as per the CLI. If I do this the GUI shows the path as "logs/raw" which is what I want.
Anyway, the work around works but it is annoying because I effectively cannot use the GUI page for transaction log changes.
Has anyone else seen this?
Cheers
Cameron

Hi Cameron,
Why does the export fail with a leading / in the path? Is that not a valid path on the target server?
Can you perform the following debug and send the syslog.txt file:
From config mode:
logg disk prior debug
From enable mode:
transaction-log force export
Thanks,
Zach

How do I upgrade from WAAS CM on WAE-7326 to vWAAS CM

My WAAS network comprises of WAE-612 and WAE-7326 Running Sotware version 4.3.3.1, these are old and we are now going to Cisco 3945 Routers with SRE WAAS and the vWAAS as Central Manager.
The problem is how do I get the configuration across from the 7326 that is a CM to the vWAAS CM?
Can the vWAAS run software version 4.4? if so my standyby CM is a WAE612 which can be upgraded to 4.4, so I would make that the primary CM the new vWAAS as standby, so then the configuration would go across to the new vWAAS. once done make the vWAAS primary again, then install a second vWAAS as standby.
is the above possible?
I can't find any documentation about upgrading the WAAS nework

Hi Edward,
For the upgrade process, you'll have to follow this procedure :
http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/waas/waas/v541/release/note/waas541xrn.html#pgfId-171257
So either down grade your vCM to 4.4.7 (this requires that it is a vCM-100 or -2000)
- there probably is a vCM 4.4.7 image out there somewhere, but these could be hard to get.
- or just use the "copy ... install" on your vCM, to get it downgraded.
or use the 294 method (same methodology applies)
But as I see it, there is no need to play around wit ha secondary CM, you don't need the CM to ensure optimization, when things are up and running.
You can easily change a CM to an accellerator by configuration and a reload, unless we're taking vWAAS, where the ova image is locked.
remember to take a backup of your CMS database and place it somewhere else, before starting upgrading.
Best Regards
Finn Poulsen

WAE and WAVE

Hi all, just wonder what is the difference between wide area application engine (WAE) and wide area virtualization engine (WAVE)? I read the data sheet for WAE and WAVE, both stating they provide :
• Improve employee productivity by enhancing the user experience for important business applications delivered over the WAN
• Reduce the cost of branch-office operations by centralizing IT resources in the data center and lowering the cost of WAN bandwidth
• Increase IT agility by reducing the time and resources required to deliver new IT services to the branch office
• Simplify branch-office data protection for regulatory compliance purposes
Really appreciate if anyone can explain to me about it.
Thanks

Hi Lieu,
The are some key differences.. for example:
-WAVE 574 and WAE 674 support virtual blades and WAE 512 and WAE 612 don't
-WAE 674 can support 8 inline ports ( using 2 4-port inline cards) and WAE 612 supports only 4ports.
-WAVE 574 and WAE 674 has better hard drive redundancy..etc
if you are working on a project that requires detailed info I suggest to contact your Cisco Account Manager or Cisco Partner as it is critical to choose the right device depending on your topology, applications, number of users..etc
cheers!

History active connections WAAS (WAE)

Hi Folks!
I need extract the history active connections from WAE-512 and WAE-612. For example, in hour XX:XX I was X number of active connections.How I can do this? It´s possible? Exist SNMP OID to collect this information if not is possible in Central Manager?
Thanks.

Hi Harrisson,
Thanks for marking this Answered.
You can use WAE Central Manager to export these numbers to any NetFlow analyzer.
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/planning.html#wp1041835
http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v421/configuration/guide/monitor.html#wp1163526
WAAS does flow the agent to any netflow collector / analyzer. NetQoS and NAM can understand this traffic directly where as you will need additional customized api if you want to export the stats from WAAS to others.
All these APIs are publicly available and listed here: http://www.cisco.com/en/US/products/ps6870/products_programming_reference_guides_list.html
Cisco WAAS reporting using NetFlow can be done with almost any NetFlow collector that supports both ingress and egress flows. One of the 3rd party has posted this on their website. Best Practices blog releated to Cisco WAAS and NetFlow.
http://www.plixer.com/blog/netflow/best-practices-for-cisco-waas-reporting-using-netflow/
Hope this helps.
Regards.

WAAS hardware is OE612, but Rescue Disk detects model as OE512

I've had this issue with 2 RMA'd OE612s already. They originally shipped with 4.0.19, which worked fine, but failed on upgrade to 4.2.1.
Recovery attempt #1 with 4.0.19 Rescue disk displayed :
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
   MODEL: UNKNOWN
   FLASH: found, directory validated
COOKIE: invalid
   IMAGE: NONE
FLASHDEV: /dev/hda
Installer Main Menu:
    1. Configure Network
    2. Manufacture flash
    3. Install flash cookie
    4. Install flash image from network
    5. Install flash image from cdrom
    6. Install flash image from disk
    7. Wipe out disks and install .bin image
    8. Exit (and reboot)
Choice [0]: 3
Unknown model, cannot create cookie.
Subsequent Recovery procedures using Rescue disks from 4.1.7 and 4.2.1 detected the Model as OE512. Option 2 creates a cookie as a MODEL OE512, which I wrote with option 3. Option 5 works, but trying to write the bin image on 4.1.7 displays this
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Choice [0]: 8
Enter full URL of .bin image to install.
   ftp://[user:pass@]ip_addr/path/to/file
http://[user:pass@]ip_addr/path/to/file
file:/local/path/to/to/file
URL for .bin image [file:/cdrom/images/WAAS41.bin]:
Continue? This will wipe out all disks! [n]: y
Scrogging done
Saving random seed...
dd: opening `/state/random-seed': No such file or directory
No volume groups found
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdown, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_open or media_open
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: open(/state/safestate, O_WRONLY|O_CREAT) failed: No such file or directory
ssmgr: op_create or media_init
SSMGR RETURNING: 10 (No such file or directory)
Reading and installing image, it may take a few minutes, please wait...
Error, image NOT installed.
   MODEL: OE512
   FLASH: found, directory validated
COOKIE: valid
   IMAGE: 4.1.7.11
FLASHDEV: /dev/sda
Installer Main Menu:
    1. Configure Network (done)
I suspect that the Installer program on the Rescue CD can't detect the Hardware properly, and thus can't find the proper drivers for the platform.
Is there any manual method of forcing the Rescue CD Installer to use a particular hardware model?
Thanks,
Tom

Hi Zach,
>What led you to change the Adaptec configuration?
I was directed to do so by TAC, although I wasn't sure why, since our other WAE-612-k9s didn't have this option enabled.
>What is the state of the device prior to upgrading? Does the WAAS software boot?
After disabling the hardware raid, the WAE could run any 4.0.x version, but could not upgrade to 4.1/4.2. I tried both the "rescue CDs" for 4.1/4.2, and the "copy ftp install" methods. "Rescue CDs" would work right up to the option for "wipe disks and install .bin" image, but would report "no disks" as shown above. The "copy ftp install" from version 4.0.27 would install the 4.2.1.38 image, but upon reboot, it would fail during the boot sequence
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
Frustrated, I looked at the boot logs and might have found an issue. On the "faulty" WAE-612, the boot script detects two SCSI adapters; only one shows up in BIOS POST.
The first adapter (Adaptec AIC79XX) has no drives, but is assigned the device name "scsi0"
Under the second adapter(Adaptec AIC94XX), the Hard disks are detected, and it's assigned a device name of "scsi1"
ACPI: PCI Interrupt 0000:03:03.0[A] -> GSI 17 (level, low) -> IRQ 17
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 2.0.30
        aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs
Adaptec aacraid driver 1.1-5[24495]custom-IBM
Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
Probing Adaptec AIC-94xx Controller(s)...
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
scsi1 : Adaptec AIC-9405W SAS/SATA Host Adapter
scsi 1:0:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
adp94xx:0:128:0: Tagged Queuing enabled. Depth 32
scsi 1:1:128:0: Direct-Access     IBM-ESXS ST3146755SS      BA33 PQ: 0 ANSI: 5
adp94xx:1:128:0: Tagged Queuing enabled. Depth 32
AIC-94xx controller(s) attached = 1.
To contrast, our functioning WAE-612s do not have this second detected Adaptec host adapter, and are properly assigned a "scsi0" for their device name.
Adaptec aacraid driver 1.1-5[24495]custom-IBM
Loading AIC-94xx Linux SAS/SATA Family Driver, Rev: 1.0.8-12
Probing Adaptec AIC-94xx Controller(s)...
ACPI: PCI Interrupt 0000:03:04.0[A] -> GSI 19 (level, low) -> IRQ 19
scsi0 : Adaptec AIC-9405W SAS/SATA Host Adapter
scsi 0:0:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
adp94xx:0:128:0: Tagged Queuing enabled. Depth 32
scsi 0:1:128:0: Direct-Access     IBM-ESXS MBA3300RC        SA06 PQ: 0 ANSI: 5
adp94xx:1:128:0: Tagged Queuing enabled. Depth 32
AIC-94xx controller(s) attached = 1.
On our faulty WAE-612, in the section that tries to mount the detected drives, it appears that the script is looking for the physical drives under the "scsi0" device name, using the AIC94XX driver.. .
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sda a
t scsi1, channel 0, id 128, lun 0
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi disk sdb a
t scsi1, channel 1, id 128, lun 0
2010 Jul 8 08:58:41 (none) kernel: %WAAS-SYS-3-900000: Attached scsi removable
disk sdc at scsi2, channel 0, id 0, lun 0
BOOT-100: disk apply
scan_612_disk_map: Can't open . Errno=2
change_disknum_612 failed!
/ruby/bin/ruby_disk: First disk is missing, bad, marked bad, disabled via shutdo
wn, or it has unknown data.
/ruby/bin/ruby_disk: Second disk is bad, missing, or shutdown; bailing out
I'm guessing this fails because there are no physical drives on "scsi0", they are assigned on "scsi1". If the disk mapping script would've tried , I think the drives would've been mounted properly.
I was hoping there was a modified script out there somewhere, but after our 3rd RMA'd WAE exhibited the same characteristics (these were all in Chennai India), I directed the onsite tech to remove the Adaptec 29320ALP UltrasSCSI adapter.
With the adapter removed, the 4.2.1.38 code installed and booted properly.
When I forwarded my results to TAC, our Rep mentioned that the WAE-612-k9 ships with both ACNS and WAE capabilities. He said that ACNS uses that additonal SCSI card.
I'm fairly sure our configuration is not unique; our environment consists of 32 WAEs, and this is the first time that I've encountered this issue.
I'm just happy it's resolved now.
Thanks for your insight, Zach
Tom

Core cluster in WAAS

We're attempting to configure a Core Cluster for the WAE-612 and got confused when entering the access information for the CIFS file server that his core cluster will export. The doc is saying that we can only enter access info for 1 file server. I was under the impression we can include more than 1 file server in the core cluster. Can someone please clarify this? thnx..

Thanks for the reply.
<>
I will double check this...
<< Also, to see if things are being optimized via CIFS, you should see the session in "sh cifs session list", not on the edge in the sessions as 139/445.>>
Yes, I have run this command on the edge wae and was seeing sessions as 139, so I am pretty sure the CIFS traffic is getting accelerated.
<>
Where in the edge GUI should I be seeing the 4050 tunnels? - in the WAFS log?
<>
yes..here is the ping from the core to the file server: 5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/mdev = 1.165/1.235/1.271/0.036 ms
<>
I have created 2 connectivities - one's for a T1 line connection and the other is for 2 T1's connection. I have exported the file server as part of the first connectivity, but not the second one (we're running 4.0.19 code level on our wae's). Exporting the file server did not seem to make much difference for performance.
<>
Dotted the i's and crossed the t's on the settings all the way from the core to the edge (MPLS on the WAN)..
Thanks again..

WAE 612 Log

Similar Messages

Maybe you are looking for