Congrats to my dearest friend for say 'goodbye' to single

#1

Dedicate to my dear friend - E.H Tan. Wish him have a sweet & romance marriage forever. :-)

Symantec BackupExec: 0xe000fe29 - Authentication failed on connection to the server

This error occur even you had logged in as administrator. Don't panic, it might not due to your daily login username & password incorrect, but may due to some compatibility between BackupExec remote agent with Microsoft Windows.

You may try the following workaround which proposed from Symantec to resolve the issue.

Additional error message as below:

Make sure that the user account has the appropriate permissions and that the password was typed correctly.
Final error category: Security Errors

To correct this, change the service account information as follows:

1. In Backup Exec, click Tools | Backup Exec Services.

2. Make sure no jobs are running and close the main Backup Exec window while leaving the Backup Exec Services Manager window open.

3. Click Services credentials.

4. Select the Change Service Account Information check box.

5. Type in all of the correct up-to-date information in the fields so that the credentials match the username that is supplied to the SYSTEM LOGON ACCOUNT.

6. Do not select the Change startup options check box.

7. Click OK.

8. Once the process is complete, choose to Stop and then Start all services in the Backup Exec Services Manager window (select Restart Services in Backup Exec version 10.0 or later).

9. Check the Backup Exec server and the servers with the Backup Exec Remote Agent for Windows Servers to determine the logon account associated with the Backup Exec Remote Agent for Windows Servers service.

10. Make sure that if the Backup Exec Remote Agent for Windows Servers service is using anything other than Local System Account, change it to use the Local System Account so that Backup Exec will function correctly.

More Info

*the above info obtain from Symantec Knowledge Base with ID:328478

Dell Software RAID Controller S100/S300 not compatible in Linux OS

Recently, Dell offered new software RAID card, with code name: S100/S300. Beware that currently this RAID card just compatible to Windows OS, and yet to see for future improvement that can work with Linux OS as well.

Specification	PERC S100 controller	PERC S300 controller
SAS technology	No	Yes
SATA technology	Yes	Yes
eSATA technology	Yes	No
SSD technology	Yes	No
Support for x8 PCI-E Host Interface	No	Yes
I/O Controller	Intel™ ICH10R or Intel™ Ibex Peak chipsets	Dell 3Gb/s SAS Adapter
Communication to the system	Integrated	PCI-E lanes
Communication to end devices	SATA links	SAS/SATA links
SAS connectors	No	Two 4-port connectors on all systems
SATA connectors	Discrete on the motherboard	Two 4-port connectors on all systems
Lead-free	Yes	Yes
Supported operating systems	Microsoft Windows Server 2003 Family, Microsoft Windows Server 2008 Family, Microsoft Windows Server 2008 R2
Dell-compliant SATA compatibility	Yes	Yes
Dell-compliant SAS compatibility	No	Yes
Dell-supported direct-connected end devices	Dell-compliant physical disks	Dell-compliant physical disks
SMART error support through management applications	No	No
Backplane supported systems	No	Yes
Software-based RAID	Volume, RAID 1, RAID 0, RAID 5, RAID 10	Volume, RAID 1, RAID 0, RAID 5, RAID 10
Maximum number of virtual disks	8	8
Support for internal tape drive	Yes	No
Support for global hot spare	Yes	Yes
Maximum number of hot spares	Varies (by the number of free disks in the system)	Varies (by the number of free disks in the system)

Reference: http://support.dell.com/support/edocs/storage/Storlink/PERC_S100_S300/en/HTML/a5_sectd.htm#wp1201881

Symantec BackupExec: A brand new cleaning tape reports an error "Cleaning Media has expired"

According to my previous sharing, a cleaning tape can be use up to 50 times depending on the type of the cleaning tape (LTO, SDLT & etc) that you have.

However, you may encounter a 'funny' error that system will prompt you 'Cleaning Media has expired' error message when you putting in a brand new cleaning tape.

Solution:

Navigate to the Media tab on the Backup Exec (tm) console and delete the cleaning media from All Media.

Run the inventory of the slot again.

The number of cleanings performed will show up as 1 now and the cleaning media can be used until theMaximum number of cleanings.

Reference: http://support.veritas.com/docs/271613

Dell Remote Access Card (DRAC5) not able to send alerts to IT Assistant

If you wish to configure Dell Remote Access Card (DRAC5) to send alert to IT Assistant, there is one option that you need to take note in order to make it works.

1. Log into Remote Access Web Interface, click [System], then go to [Alert Management] tab.

2. Check the [Enable Platform Event Filter alerts] checkbox. (Default Setting is unchecked).

3. Then, perform the hardware reset of the DRAC as below:

i. Click the Start button, and then click Run.The Run window appears.

ii. In the Open text box, type Command, and then click OK.
The Command Prompt screen appears.

At the C:\ prompt, type racadm racreset, and then press the key.

*before you're able to perform this configuration, please ensure your SNMP Services is in working condition

Dell PowerEdge: T310 failed to install Windows Small Business Server 2008

Last week, one customer from Singapore called up and blame Dell Server again. According to this customer, he said Dell had posted up a false info over the internet. This is because he failed to install Windows Small Business Server 2008 to Dell PowerEdge T310, and documentation written that this OS is actually supported on this platform.

This customer had done a lot of research before ring me up, and wanted to send me the T310 documentation link to prove he is right.

I knew he was right, so I check his server's hardware specification, found that he only having 2GB RAM for this server. At first I really didn't know what's wrong with this, inform customer that I will need to call 1 hour later, and I google for more info about this.

I'm lucky enough to remind myself that one of my colleague share this info before. Then I read through the article, confirm this is the answer that I can share with this demanding customer.

Cause:

He didn't meet one of the minimum requirement of having at least 4GB to complete the OS installation.

Plan to switch to Windows Small Business Server 2008 Standard/Premium? Please refers to below minimum requirements.

For more information, please visit Microsoft site as below:

http://www.microsoft.com/sbs/en/us/system-requirements.aspx

Life span of the LTO Cleaning Tape

Many IT personnel/specialist didn't really know when to use the Tape Backup Unit (TBU) cleaning tape. If you google about this topic, I'm pretty sure you can't find any exact instruction about this but only some suggestion from many experienced IT specialist.

For me, I will suggest you to clean the TBU at least once in a fortnight. If you are a heavy user, and every day you need to backup at last 400GB of data, then you might need to consider clean it at least once in a week.

Few weeks ago, I noticed even some of the IT personnel did schedule the drive cleaning, but they didn't know how many times that a cleaning tape can be used, and they just keep cleaning the drive with a cleaning media which already exceed its life span.

Please take a look from the below description:

An LTO cleaning cartridge can be used approximately 50 times, and the inventory count shows 50 cleans remaining until you load the tape into a drive for the first time. An SDLT-320 cleaning cartridge can be used approximately 20 times

For more information, you may refers to below URL:

http://support.euro.dell.com/support/edocs/stor-sys/132TLTO2/en/ug_tl/faq.htm

Dell PowerEdge: Why R410 only 4 DIMM slots are usable?

Many customers didn't really know what to ask before confirm the order, but rather accept what Sales person had suggest to them.

No one is wrong in this situation but I just share it out for those who like to research before buy the product.

I would like to share about Dell PowerEdge R410's Memory Configuration.

Two days ago, I received one inquiry from a customer.

Problem:

He bought R410 with 2x 2GB DIMM. After that, he purchase 4x 2GB DIMM from another sales. After he connect all the DIMMs, found that system BIOS only detect 8GB, in other words, only 4 slots are working.

Then he is blaming me why the new server (just arrive for less than 7 days) already having hardware issue. I check the correct memory population, and take a look at the hardware component that he order, then I know the answer.

Cause:

This is due to customer only purchase with 1x Processor. This is why only 4 slots are working.

Workaround:

I suggest him to keep the DIMMs for standby purpose, or consider to add in another processor to get all slots detected.

Dell PowerVault: Initial Log-in Name & Password for Dell NX3000

I notice that many customer didn't know about Initial log-in name & password for Power Vault NX3000. Actually it is included in the Manual, but not much people will actually go through once before they start to configure.

The funniest thing is what customer will do is call in and blame Dell that didn't inform customer about this info. Usually I will share them the Online documentation about NX3000 as below:

Username: administrator

Password: Stor@ge!

You may refers to Dell Online Documentation which available 24/7:

http://support.ap.dell.com/support/edocs/stor-sys/NX3000/en/ag/html/initial_.htm#wp1193528

Dell PowerEdge: R610 / R710 only detect my 1333MHZ DDR3 RAM as 1067MHZ in System BIOS

Nowadays server already using DDR3 Memory in most of the platform regardless it is Dell, IBM or HP. For this new technology, it have two types: Registered (RDIMM) & Unbuffered (UDIMM) ECC DDR3.

The primary differences between UDIMMs and RDIMMs are:

• RDIMMs have a register used as a pass through for address and command signals. This allows servers to support more RDIMMs per channel than UDIMMs.
• RDIMMs consume more power than UDIMMs but are available in larger capacities and higher ranks.
• RDIMMs also provide additional data protection and reliability features.

(Reference: Memory Selection Guidelines for High Performance Computing with Dell™ PowerEdge™ 11G Servers)

I'm not going to go into detail of the difference of RDIMM & UDIMM, but I would like to share the situation below:

Customer contact me and request my explanation about why new server's motherboard is faulty. Then he share me the screen from System BIOS, that all 1333Mhz Memory are detected as 1067Mhz only.

I checked the Intel Processor that he ordered (Intel Xeon E5520 2.26Ghz), then I get the answer.

This is nothing about the motherboard, or the design of Dell platform, but this is due to the Limitation of Intel Xeon Processor.

Whitepaper (Page.11)

From the chat above, it is clearly stated that only X5550 and above able to support/detect 1333Mhz of DDR3 RAM (but still depends on processor model, DIMM speed, and DIMM population).

I hope my sharing over here can avoid further misunderstanding towards Dell platform. :-)

Dell PowerEdge: Intel Nehalem Processor cause Blue Screen: STOP 0x00000101

When 11th Gen Dell PowerEdge Server being introduce to the market, it face a lot of challenge from other manufacturer that make customer have concern about part quality and server stability.

One of that challenge is Intel Nehalem series processor can cause blue screen "STOP 0x00000101 - Clock_watchdog_timeout" when you activate Hyper-V from Windows Server 2008 R2.

Two months back, I have customer called in not only scolding me like hell but would like to know why Dell server always cause blue screen, and not stable as what its described from Sales person.

You can see the below information from Event Viewer:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7600.2.0.0.274.10

Locale ID: 1033

Additional information about the problem:

BCCode: 101

BCP1: 000000000000000D

BCP2: 0000000000000000

BCP3: FFFFF88001F46180

BCP4: 0000000000000004

OS Version: 6_1_7600

Service Pack: 0_0

Product: 274_3

Files that help describe the problem:

C:\Windows\Minidump\021110-36363-01.dmp

C:\Users\administrator.PANDALOG\AppData\Local\Temp\2\WER-1299472-0.sysdata.xml

I have no choice but get the stop code error from customer, and start my research from Microsoft Knowledge Base(KB), as well as using WinDebugger to analyze the Dump file.

Finally, I found one KB from Microsoft that explain the same STOP error, but it pointed to Intel Nehalem Processor's limitation. It simply explained this is due to serious interrupts generated from Intel code-named Nehalem Processors. For more information, can refers to below Intel document:

http://www.intel.com/assets/pdf/specupdate/321324.pdf

Microsoft KB:

http://support.microsoft.com/kb/975530

"Don't judge a person by his appearance."

Dell Server: How to capture hardware log if using VMWare or Open Linux?

Good news to all Dell Customer who using VMWare or other Linux OS which not compatible with Dell OpenManage Server Administrator (OMSA).

Now, you can use Dell LiveCD to boot up during POST, and access to Embedded Server Management (ESM) to gather the hardware log.

LiveCD ISO Download:

http://linux.dell.com/files/openmanage-contributions/omsa-601-live/omsa601uk.iso

How to use?

1. It is a bootable CD, after you burn the ISO into CD, just boot the CD or change the boot sequence in BIOS settings.

2. Log in User Name= root ; Password = dell

3. After logged in, it will display the current IP Address, copy down as you may need it later for remote access connection.

4. Next, just type 'startx' to access the GUI

5. Then you'll be able to see one browser icon with the name "OMSA".

6. Double click to open, and you'll be able to see the hardware status as the normal OMSA in Windows environment.

How to Create RAID0 with single HDD by using Dell SAS5iR / SAS6iR?

If you ever go into SAS5iR / SAS6iR configuration BIOS, you will notice that it require at least 2x Hard Disks to configure RAID0. I have to say this is just as per design, and it is not refers to bug or limitation.

Some of you may wondering if you're using Windows Small Business Server 2003/2008, which have the limitation of having 2TB for C:\ , and yet you don't want to convert it into Dynamic Disk; or you totally don't need that huge space for your C:\, and the server already in front of you. Stop to blame the design or the Sales person of not inform you about this, but refers to below workaround.

Workaround (I):

1. Go to SAS5iR /SAS6iR Configuration BIOS which is Ctrl +C, delete all RAID0 or RAID1 configuration.

2. Exit the BIOS, then proceed the OS installation through:

11th Gen Server:

~ Unified Server Configurator (USC) or Installation DVD (Dell System Tools & Documentation)

8th - 9th Gen Server:

~ for this generation, do not support USC, so we need to depend on Installation CD/DVD which can ease the installation process of end user.

3. However, with treated this card as a 'pass-through' SAS interface controller card, you will notice one of the HDD LED light (status LED) will not light up.

Dell did explain that in their Knowledge base:

Drive Status LED Functionality When Attached to SAS5iR and SAS6iR

Explanation:

When hard disk drives are attached to a SAS5/iR or SAS6/iR as a single disk (not part of a RAID0 or RAID1) the status Light Emitting Diode (LED) will not illuminate. The LED is not a representation of power to the drive. It is a representation of the drive status or availability within an array. Since a single drive Redundant Array of Independent Disks0 (RAID0) cannot be created on a SAS5/iR or SAS6/iR, the status light will remain off for single drive usage.

Workaround (II):

1. Check with Technical Support or Sales whether the Model of the server that you own is support PERC series of SAS RAID card or not.

2. If so, you may consider change the card to PERC6i (for 11th Gen) or PERC5i (for 9th & 10th Gen).

3. PERC series able to create RAID0 with single HDD.

*However, the price of PERC series is much more expensive than SAS5iR/ SAS6iR.

Dell Server: PowerEdge R710 with Hyper-V will hang/freeze

Recently I encounter a case with below situation:

Product: Dell PowerEdge R710

RAM: 12GB ECC DIMM

Processor: 2x Quad Core Intel Processor

OS: Windows Server 2008 Enterprise R2 x64

Others: Hyper-V activated

Problem:

Customer mentioned that he have total 5 VMs running in this server. 4 of it will running all the time. He allocate 8.5GB for 5 VMs, and after 2-3 days, server will hang. He monitor this issue by his own, and found that Memory usage will reach 100% before it hang.

He submit this issue to me, and cause me study a lot of whitepaper, forum from Microsoft site to look for more information.

VMs Resource Allocation:

1. VM1 Memory=512MB HDD Space=80GB

2. VM2 Memory=2GB HDD Space=200GB

2. VM3 Memory=4GB HDD Space=300GB

2. VM4 Memory=2GB HDD Space=150GB

In a nutshell, he left 3.5GB RAM for Host which is totally insufficient to run in a optimal environment.

Maybe you'll ask: "Where is the 5th VMs?"

I ask the same to customer, but he told me the 5th VM in OFF mode all the time, will use when its needed. -.-"

Research:

After 1 day of studies, research, I manage to obtain the below info to customer. To configure Hyper-V with Optimal state, we have to follow the below formula:

To calculate the host RAM = (VMRamRequirementMB x #ofVMs) + (#of VMs x 32MBVMOverhead ) + (512MBHost)

To calculate VMRamRequirementMB, I found 1 statement from one of the Microsoft White Paper:

...the root partition must have sufficient memory (leave at least 512 MB available) to provide services such as I/O virtualization, snapshot, and management to support the child partitions.

A good standard for the memory overhead of each VM is 32 MB for the first 1 GB of virtual RAM plus another 8 MB for each additional GB of virtual RAM. This should be factored in the calculations of how many VMs to host on a physical server. The memory overhead varies depending on the actual load and amount of memory that is assigned to each VM.

Reference:

http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/Perf-tun-srv-R2.docx

(Search for “Correct Memory Sizing”)

Therefore, I manage to come out the optimal resources allocation with above-mentioned formula:

1. VM1 = (1 x 32MB) + (79 x 8MB) = 664MB

2. VM1 = (1 x 32MB) + (198 x 8MB) = 1616MB

3. VM1 = (1 x 32MB) + (299 x 8MB) = 2424MB

4. VM1 = (1 x 32MB) + (149 x 8MB) = 1224MB

Total RAM for VMs = 5928MB

= 5.8GB

Host RAM = (5928MB) + (4 x 32MB) + 512MB

= 6.41GB

Result:

According to calculation, obviously server (host) doesn't have sufficient Memory because it need at least 6.4GB, and VMs already occupied 5.8GB (maybe more as I didn't count in the 5th VM that customer turn on when it is needed).

Temporary workout:

1. Reserved at least 6.4GB for Host. This can only avoid the Host from hang/freeze issue, but it may cause VMs couldn't run in Optimal state.

2. Reduce the size of HDD Space for the VMs.

Permanent solution:

1. Add in more RAMs as Widows Server 2008 Enterprise R2 able to support up to 32GB memory space.

2. Move at least 1 or 2 VMs to other Host to reduce the loads in this server.