This article from Mainland China revealed the secret of the latest Equallogic hardware architecture.
PS6100 uses 64bits RISC CPU which provided by NetLogic XLS616, it has 4 MIPS cores with 4 threads per core at 1Ghz each (ie, 16 total threads per CPU), and 1MB L2 Cache.
In contrast, PS4100 uses its younger brother NetLogic XLS608, which has 2 MIPS cores with 4 threads per core at 800Mhz each (ie, total 8 threads per CPU), and 1MB L2 Cache, so the processing speed has been cut at least 50%.
Everything else is the same except the above processor speed and number of cores. It is also interesting to learn about the super conductor instead of traditional BBU cache for data.
I was told Power Connect 52xx/54xx series switches are optimized for VoIP and they are no longer recommended by Equallogic as 50% of the available buffers are reserved for VoIP unless you change the setting and REBOOT the switch.
I haven’t tried the following VoIP setting recommended by EQL as I don’t want to mess around my optimized configuration file.
Besides, I think there is an alternative way which I’ve completely disabled VoIP setting using PowerConnect 5448 GUI. There is a check for you to disable VoIP in the Switch session under the GUI.
Go to each switch and do the following:
Put the switch into admin and configuration mode.
enable
configure
Disable/remove iSCSI and VoIP optimization
voice vlan oui-table remove 00036b
voice vlan oui-table remove 00096e
voice vlan oui-table remove 0001e3
voice vlan oui-table remove 000fe2
voice vlan oui-table remove 0060b9
voice vlan oui-table remove 00d01e
voice vlan oui-table remove 00e075
voice vlan oui-table remove 00e0bb
Exit from configuration mode
exit
Save the configuration
copy running-config startup-config
When ready, type ‘reload’ to reboot
reload
這次回溫哥華，竟然給我找到了不少的珍貴文物。
那年留學英倫，有幸第一次去看溫布頓，那天親眼見到了正在冒起的網壇天王Pete Sampras，還有兩JIM大戰:Jimmy Connors vs Jim Courier, it was a classic match!
City of Montreal, this was the view from my apartment window almost 20 years ago, it is just like yesterday…
* Just in case you wonder, the white spot near IBM tower is NOT an UFO, it’s a commercial airship.
Just came back from my trip to Vancouver. It was such a paradise with nice weather, beautiful scenery, wonderful food and most importantly free tennis courts with deep forest nearby. 
I used to be a cheese cake lover, the best one I remember was the New York cheese cake from Mandarin Oriental (HK) cake shop. Then I had too much of it, so I quit.
This little shop in downtown Vancouver was definitely a rediscovery of cheese cake for me, especially the unique taste of this Maple Walnut one and the double chips chocolate cookie as the compliment!
This latest brief review compared the pros and cons of the leading backup vendors for VMware ESX. (In Chinese).
It only touched the surface, not technical oriented and in fact not detail at all, sounds more like a marketing material to me.
我總覺得攝影就是簡單地把自己那一刻的感覺捕捉下來，什麼學院派攝影技巧都是其次。
這幅照片表達的就是這種與生俱來的感覺，面對諾大的紐約中央公園模特完全釋放自己的一剎那，攝影師Patrick Lichfield的靈感油然而生，然後喀嚓按下了快門，經典由此而生。
VMware ESX source code has been stolen and posted online, but the company said its virtualization platform doesn’t necessarily pose an increased risk to customers.
The stolen code amounts to a single file from sometime around 2003 or 2004, the company said in a blog post.
“The fact that the source code may have been publicly shared does not necessarily mean that there is any increased risk to VMware customers,” according to the blog written by Iain Mulholland, director of the company’s Security Response Center.
The code was stolen from a Chinese company called China Electronics Import & Export Corporation (CEIEC) during a March breach, according to a posting on the Kaspersky Threat Post blog.
The code along with internal VMware emails were posted online three days ago.
VMware didn’t respond immediately to a request for more information about the impact of the breach on customers.
Eric Chiu, president of virtualization security firm Hytrust, said it’s hard to say what VMware customers should do because there’s not enough detail about how the exposed code is being used in current products.
In general, though, customers should review the security for virtual environments to address the fact that a compromised hypervisor exposes multiple virtual machines.
While the incident is reminiscent of the breach last year of RSA source code, the circumstances differ. An RSA partner was breached and that breach was used to send a malware-laced email to an RSA staffer who opened it.
In VMware’s case, the CEIEC network was hacked and finding the source code was fortuitous.
This is what VMware posted in a blog: “Yesterday, April 23, 2012, our security team became aware of the public posting of a single file from the VMware ESX source code and the possibility that more files may be posted in the future. The posted code and associated commentary dates to the 2003 to 2004 timeframe.
“The fact that the source code may have been publicly shared does not necessarily mean that there is any increased risk to VMware customers. VMware proactively shares its source code and interfaces with other industry participants to enable the broad virtualization ecosystem today. We take customer security seriously and have engaged internal and external resources, including our VMware Security Response Center, to thoroughly investigate. We will continue to provide updates to the VMware community if and when additional information is available.”
Network World (US)
These treasure were from the past…used to be at least, now all went to recycle bin, probably will turn into a plastic cup later on.
Comments (0) 