Thomasspace

PCI card dimensions

2012-10-26T10:45:00.001+08:00

http://lavalink.com/wp-content/uploads/newsletters/link_04_02.pdf

http://www.pcisig.com/specifications/conventional/conventional_pci/lowp_ecn.pdf

PCI card dimensions (low profile and standard height) MD1 and MD2

storage concept

2012-10-18T10:35:00.002+08:00

http://qing.weibo.com/tj/88ca09aa330005a4.html

網路文件共享系統(CIFS)

2012-10-18T09:10:00.001+08:00

網路文件共享系統(CIFS)
2009/03/04-鐘聖雄

http://www.digitimes.com.tw/tw/dt/n/shwnws.asp?rnrnCnlID=10&Cat=&Cat1=&id=124179

網路文件共享系統(Common Internet File System；CIFS)原先被稱為伺服器訊息區塊(Server Message Block；SMB)，該技術使得網路上的機器得以共享文件、周邊機器(如印表機)、串接阜等資源，也提供通過授權的程序間溝通(Inter- Process Communication；IPC)功能。

有別於網路文件系統(Network File System；NFS)，CIFS的訊息格式並沒有固定長度，且多數訊息都包含無固定長度的數據，也使得協議的複雜度增加。一般來說，CIFS會包括1個32位元組的訊息頭，以及1個或多個長度不固定的訊息體。

CIFS 最初是由IBM的Barry Feigenbaum所開發，目的是為了將DOS上的本地端文件介面，改造成為可供分享的網路文件系統。後來，微軟(Microsoft)接手了該計畫，為了修正第1版的DES錯誤，而使用了NTLM(NT Lan Manager)第2版，並將CIFS與微軟和3com共同合作的另1個網路管理程序結合，修改為當前的版本，並建立其分散式文件系統。也因為這樣的緣故，CIFS多半是用在安裝微軟作業系統的機器上，但後來CIFS在經過Unix伺服器廠商重新開發後，也可以被用在連接Unix伺服器和Windows 作業系統的客戶端機器上，並執行檔案分享，以及共用PC周邊的功能。

CIFS最早是被設計成運行於NetBIOS協議上；換言之，CIFS是建立在NetBEUI、IPX/SPX以及TCP/IP協議成立的前提之上。後來，微軟在Windows 2000作業系統中，將CIFS改造為可以直接運行在TCP/IP之上。

CIFS 的作業方式，基本上就是大家熟悉的客戶端－伺服器(Client - Server)模式，也就是先由客戶端發出請求，再由伺服器回應；在CIFS協定中，有一部分就是用來協調客戶端對伺服器發出的請求，也就是說，客戶端是藉由文件系統的中介，得以拜訪文件伺服器。在IPC部分，CIFS也允許利用網際網路功能，讓不同的局部子網路或虛擬私人網路(Virtual Private Network；VPN)得以互相連結，如此一來，不同的子網路之間就得以進行遠端協同作業，例如文件分享或是共用印表機等PC周邊設備功能，都是利用 CIFS協議運作。

CIFS最為人詬病的缺點，就是它會佔用過多頻寬，因為每1台子網路內的客戶端電腦，都必須要廣播其存在，才能共享服務，但是CIFS本身並不使用廣播功能，這樣的問題實際上是NetBIOS的服務定位協議所造成的。在使用微軟Windows伺服器時，都是透過 NetBIOS來協議與定位，而NetBIOS則會定時向特定伺服器廣播某個服務的存在，這樣的作業方式在伺服器較少時，並不會佔用過多的頻寬，但在伺服器超過一定數目時，網路大塞車的情況則會愈來愈明顯。

網路塞車會對CIFS的使用者帶來重大的影響，特別是在伺服器間的網路延遲時間過長時，透過網際網路拜訪VPN，進行文件分享與協同作業時，延遲會更加明顯。

為了改善頻寬問題，一般來說可以利用Windows Internet Name Service(WINS)定位協議緩和這樣的情況，也就是使用更高階的系統將服務集中化，但是這也相對地會造成訊息與網路保管問題。此外，使用動態網域名稱伺服器(Dynamic Domain Name Server；Dynamic DNS)也可以解決CIFS的問題。

CIFS伺服器可以向網路上的客戶端電腦提供文件系統與各種資源，但客戶端卻可以保留分享權限，這使得CIFS得到廣泛的採用。此外，CIFS採用NT網域協議與認證，而NT網域協議幾乎只能透過CIFS進行IPS認證，確定客戶端能否拜訪特定資源，所以CIFS所以才會如此廣泛地被採用。

在昇陽電腦(Sun)於1996年推出WebNFS時，微軟曾經提出將SMB改稱為現在的CIFS，並加入如軟連結、硬連結等功能，藉此提高文件大小。然而，微軟後來又在推出Vista作業系統時，提出了SMB 2.0的概念，因此目前CIFS與SMB，都是非常普遍的說法。

DIGITIMES中文網原文網址: 網路文件共享系統(CIFS) http://www.digitimes.com.tw/tw/dt/n/shwnws.asp?rnrnCnlID=10&Cat=&Cat1=&id=124179#ixzz29bnGeE00

Server Message Block

In computer networking, Server Message Block (SMB), also known as Common Internet File System (CIFS, /ˈsɪfs/) operates as an application-layer network protocol^[1] mainly used for providing shared access to files, printers, serial ports, and miscellaneous communications between nodes on a network. It also provides an authenticated inter-process communication mechanism. Most usage of SMB involves computers running Microsoft Windows, where it was known as "Microsoft Windows Network" before the subsequent introduction of Active Directory. Corresponding Windows services are the "Server Service" (for the server component) and "Workstation Service" (for the client component).
The Server Message Block protocol can run atop the Session (and lower) network layers in several ways:

directly over TCP, port 445;^[2]
via the NetBIOS API, which in turn can run on several transports:^[3]
- on UDP ports 137, 138 & TCP ports 137, 139 — see NetBIOS over TCP/IP;
- on several legacy protocols such as NBF (incorrectly referred to as NetBEUI).

History

Barry Feigenbaum originally designed SMB at IBM with the aim of turning DOS "Interrupt 33" (21h) local file access into a networked file system.^[4] Microsoft has made considerable modifications to the most commonly used version. Microsoft merged the SMB protocol with the LAN Manager product which it had started developing for OS/2 with 3Com c. 1990, and continued to add features to the protocol in Windows for Workgroups (c. 1992) and in later versions of Windows.
SMB was originally designed to run on top of the NetBIOS/NetBEUI API (typically implemented with NBF, NetBIOS over IPX/SPX, or NBT). Since Windows 2000, SMB runs, by default, with a thin layer, similar to the Session Message packet of NBT's Session Service, on top of TCP, using TCP port 445 rather than TCP port 139 — a feature known as "direct host SMB".^[2]
At around the time when Sun Microsystems announced WebNFS,^[5] Microsoft launched an initiative in 1996 to rename SMB to Common Internet File System (CIFS), and added more features, including support for symbolic links, hard links, larger file sizes, and an initial attempt at supporting direct connections over TCP port 445 without requiring NetBIOS as a transport (a largely experimental effort that required further refinement). Microsoft submitted some partial specifications as Internet-Drafts to the IETF,^[6] though these submissions have expired.
The Samba project originated with the aim of reverse engineering the SMB protocol and implementing an SMB server to allow MS-DOS clients to use SMB to access files on Sun Microsystems machines.^[7] Because of the importance of the SMB protocol in interacting with the widespread Microsoft Windows platform, Samba became a popular free implementation of a compatible SMB client and server for interoperating with non-Microsoft operating systems.
Microsoft introduced SMB2 with Windows Vista in 2006, and later improved on it in Windows 7.

Implementation

Client-server approach

SMB works through a client-server approach, where a client makes specific requests and the server responds accordingly. One section of the SMB protocol specifically deals with access to filesystems, such that clients may make requests to a file server; but some other sections of the SMB protocol specialize in inter-process communication (IPC). The Inter-Process Communication (IPC) share, or ipc$, is a network share on computers running Microsoft Windows. This virtual share is used to facilitate communication between processes and computers over SMB, often to exchange data between computers that have been authenticated.
Developers have optimized the SMB protocol for local subnet usage, but users have also put SMB to work to access different subnets across the Internet—exploits involving file-sharing or print-sharing in MS Windows environments usually focus on such usage.
SMB servers make their file systems and other resources available to clients on the network. Client computers may want access to the shared file systems and printers on the server, and in this primary functionality SMB has become best-known and most heavily used. However, the SMB file-server aspect would count for little without the NT domains suite of protocols, which provide NT-style domain-based authentication at the very least. Almost all implementations of SMB servers use NT Domain authentication to validate user-access to resources.

Samba

Main article: Samba (software)

Samba is a free software re-implementation of the SMB/CIFS networking protocol, originally developed by Andrew Tridgell. As of version 3, Samba provides file and print services for Microsoft Windows clients and can integrate with a Windows NT 4.0 server domain, either as a Primary Domain Controller (PDC) or as a domain member. Samba4 installations can act as an Active Directory domain controller or member server, at Windows 2008 domain and forest functional levels.^[8]

Performance issues

NetBIOS

The use of the SMB protocol has often correlated with a significant increase in broadcast traffic on a network. However the SMB itself does not use broadcasts—the broadcast problems commonly associated with SMB actually originate with the NetBIOS service location protocol. By default, a Microsoft Windows NT 4.0 server used NetBIOS to advertise and locate services. NetBIOS functions by broadcasting services available on a particular host at regular intervals. While this usually makes for an acceptable default in a network with a smaller number hosts, increased broadcast traffic can cause problems as the size of the network increases. The implementation of name resolution infrastructure in the form of Windows Internet Naming Service (WINS) or Domain Name System (DNS) resolves this problem. WINS was a proprietary implementation used with Windows NT 4.0 networks, but brought about its own issues and complexities in the design and maintenance of a Microsoft network.
Since the release of Windows 2000, the use of WINS for name resolution has been deprecated by Microsoft, with hierarchical Dynamic DNS now configured as the default name resolution protocol for all Windows operating systems. Resolution of (short) NETBIOS names by DNS requires that a DNS client expand short names, usually by appending a connection-specific DNS suffix to its DNS lookup queries. WINS can still be configured on clients as a secondary name resolution protocol for interoperability with legacy Windows environments and applications. Further, Microsoft DNS servers can forward name resolution requests to legacy WINS servers in order to support name resolution integration with legacy (pre-Windows 2000) environments that do not support DNS.

WAN performance issues

Network designers have found that latency has a significant impact on the performance of the SMB 1.0 protocol, that it performs more poorly than other protocols like FTP. Monitoring reveals a high degree of "chattiness" and a disregard of network latency between hosts.^[9] For example, a VPN connection over the Internet will often introduce network latency. Microsoft has explained that performance issues come about primarily because SMB 1.0 is a block-level rather than a streaming protocol, that was originally designed for small LANs; it has a block size that is limited to 64K, SMB signing creates an additional overhead and the TCP window size is not optimized for WAN links.^[10] Solutions to this problem include the updated SMB 2.0 protocol, Offline Files, TCP window scaling and WAN acceleration devices from various network vendors that cache and optimize SMB 1.0^[11] and 2.0.^[12]

Microsoft's modifications

Microsoft added several extensions to its own SMB implementation. For example, it added NTLM, then NTLMv2 authentication protocols in order to address security weakness in the original LanMan authentication. LanMan authentication derived from the original legacy SMB specification's requirement to use IBM "LanManager" passwords, but implemented DES in a flawed manner that allowed passwords to be cracked.^[13] Later, Kerberos authentication was also added. The NT 4.0 Domain logon protocols initially used 40-bit encryption outside of the United States of America, because of export restrictions on stronger 128-bit encryption^[14] (subsequently lifted in 1996 when President Bill Clinton signed Executive Order 13026^[15]). Opportunistic locking support has changed with each server release.

Opportunistic locking

This section does not cite any references or sources. (February 2011)

In the SMB protocol, opportunistic locking is a file locking mechanism designed to improve performance by controlling caching of network files by the client. Contrary to the traditional locks, OpLocks are not used in order to provide mutual exclusion. The main goal of OpLocks is to provide synchronization for caching. There are three types of opportunistic locks:

Batch Locks

Batch OpLocks were created originally to support a particular behavior of MS-DOS batch file execution operation in which the file is opened and closed many times in a short period, which is a performance problem. To solve this, a client may ask for an OpLock of type "batch". In this case, the client delays sending the close request and if a subsequent open request is given, the two requests cancel each other.

Exclusive Locks

When an application opens in "shared mode" a file hosted on an SMB server which is not opened by any other process (or other clients) the client receives an exclusive OpLock from the server. This means that the client may now assume that it is the only process with access to this particular file, and the client may now cache all changes to the file before committing it to the server. This is a performance improvement, since fewer round-trips are required in order to read and write to the file. If another client/process tries to open the same file, the server sends a message to the client (called a break or revocation) which invalidates the exclusive lock previously given to the client. The client then flushes all changes to the file.

Level 2 OpLocks

If an exclusive OpLock is held by a client and a locked file is opened by a third party, the client has to relinquish its exclusive OpLock to allow the other client's write/read access. A client may then receive a "Level 2 OpLock" from the server. A Level 2 OpLock allows the caching of read requests, but excludes write caching.

Breaks

In contrast with the SMB protocol's "standard" behavior, a break request may be sent from server to client. It informs the client that an OpLock is no longer valid. This happens, for example, when another client wishes to open a file in a way that invalidates the OpLock. The first client is then sent an OpLock break and required to send all its local changes (in case of batch or exclusive OpLocks), if any, and acknowledge the OpLock break. Upon this acknowledgment the server can reply to the second client in a consistent manner.

SMB2

Microsoft introduced a new version of the Server Message Block (SMB) protocol (SMB 2.0 or SMB2) with Windows Vista in 2006.^[16] Although the protocol is proprietary, its specification has been published to allow other systems to interoperate with Microsoft operating systems that use the new protocol.^[17]
SMB2 reduces the 'chattiness' of the SMB 1.0 protocol by reducing the number of commands and subcommands from over a hundred to just nineteen.^[9] It has mechanisms for pipelining, that is, sending additional requests before the response to a previous request arrives, thereby improving performance over high latency links. It adds the ability to compound multiple actions into a single request, which significantly reduces the number of round-trips the client needs to make to the server, improving performance as a result.^[9] SMB1 also has a compounding mechanism — known as AndX — to compound multiple actions, but Microsoft clients rarely use AndX.^{[citation needed]} It also introduces the notion of "durable file handles": these allow a connection to an SMB server to survive brief network outages, as are typical in a wireless network, without having to incur the overhead of re-negotiating a new session.
SMB2 includes support for symbolic links. Other improvements include caching of file properties, improved message signing with HMAC SHA-256 hashing algorithm and better scalability by increasing the number of users, shares and open files per server among others.^[9] The SMB1 protocol uses 16-bit data sizes, which amongst other things, limits the maximum block size to 64K. SMB2 uses 32 or 64-bit wide storage fields, and 128 bits in the case of file-handles, thereby removing previous constraints on block sizes, which improves performance with large file transfers over fast networks.^[9]
Windows Vista/Server 2008 and later operating systems use SMB2 when communicating with other machines also capable of using SMB2. SMB1 continues in use for connections with older versions of Windows, as well as systems like Samba and various vendors' NAS solutions. Samba 3.5 also includes experimental support for SMB2.^[18] Samba 3.6 fully supports SMB2, except the modification of user quotas using the Windows quota management tools.^[19]
When SMB2 was introduced it brought a number of benefits over SMB1 for third party implementers of SMB protocols. SMB1, originally designed by IBM, was reverse engineered, and later became part of a wide variety of non-Windows operating systems such as Xenix, OS/2 and VMS (Pathworks). X/Open standardised it partially; it also had draft IETF standards which lapsed. (See http://ubiqx.org/cifs/Intro.html for historical detail.) SMB2 is also a relatively clean break with the past. Microsoft's SMB1 code has to work with a large variety of SMB clients and servers. SMB1 features many versions of information for commands (selecting what structure to return for a particular request) because features such as Unicode support were retro-fitted at a later date. SMB2 involves significantly reduced compatibility-testing for implementers of the protocol. SMB2 code has considerably less complexity since far less variability exists (for example, non-Unicode code paths become redundant as SMB2 requires Unicode support).

SMB 2.1

SMB 2.1, introduced with Windows 7 and Server 2008 R2, introduced minor performance enhancements with a new opportunistic locking mechanism.^[20]

SMB 3.0

SMB 3.0 (previously named SMB 2.2)^[21] was introduced with Windows 8^[21] and Windows Server 2012.^[21] It will bring several significant changes that are aimed to add functionality and improve SMB2 performance, notably in virtualized data centers like SMB2 RDMA Transport Protocol and multichannel.^[22]

Features

The SMB "Inter-Process Communication" (IPC) system provides named pipes and was one of the first inter-process mechanisms commonly available to programmers that provides a means for services to inherit the authentication carried out when a client^{[clarification needed]} first connected to an SMB server.^{[citation needed]}
Some services that operate over named pipes, such as those which use Microsoft's own implementation of DCE/RPC over SMB, known as MSRPC over SMB, also allow MSRPC client programs to perform authentication, which over-rides the authorization provided by the SMB server, but only in the context of the MSRPC client program that successfully makes the additional authentication.
Since Windows domain controllers use SMB to transmit policies at login, they have packet-signing enabled by default to prevent man-in-the-middle attacks; the feature can also be turned on for any server running Windows NT 4.0 Service Pack 3 or later.^[23] The design of Server Message Block version 2 (SMB2) aims^{[citation needed]} to mitigate this performance-limitation by coalescing SMB signals into single packets.
SMB supports opportunistic locking — a special type of locking-mechanism — on files in order to improve performance.
SMB serves as the basis for Microsoft's Distributed File System implementation.

Security

Over the years, there have been many security vulnerabilities in Microsoft's implementation of the protocol or components that it directly relies on,^[24]^[25]^[26] with the most recent vulnerability (at time of writing) involving the SMB2 implementation.^[27] Other vendors' security vulnerabilities lie primary in a lack of support for newer authentication protocols like NTLMv2 and Kerberos in preference to broken protocols like NTLMv1, LanMan, or even plaintext passwords.

Specifications for SMB and SMB2 Protocols

The specifications for the SMB are proprietary and were originally closed, thereby forcing other vendors and projects to reverse-engineer the protocol in order to interoperate with it. The SMB 1.0 protocol was eventually published some time after it was reverse engineered, whereas the SMB 2.0 procotol was made available from Microsoft's MSDN Open Specifications Developer Center from the outset.^[28] There are a number of specifications that are relevant to the SMB protocol:

MS-CIFS [1] MS-CIFS is a recent replacement (2007) for the draft-leach-cifs-v1-spec-02.txt a document widely used to implement SMB clients, but also known to have errors of omission and commission.
MS-SMB [2] Specification for Microsoft Extensions to MS-CIFS
MS-SMB2 [3] Specification for the SMB 2 protocol
MS-FSSO [4] Describes the intended functionality of the Windows File Access Services System, how it interacts with systems and applications that need file services, and how it interacts with administrative clients to configure and manage the system.

Why IBM Turned Off Siri and Dropbox

2012-05-25T09:31:00.000+08:00

http://www.informationweek.com/byte/news/radio/personal-tech/240000962

Why IBM Turned Off Siri (and Dropbox and Lots Of Other Things)

Make a Comment | Serdar Yegulalp, BYTE | May 23, 2012 08:35 PM

If there's one company I didn't expect to have massive growing pains with BYOD, it's IBM. Then again, maybe they're more of a poster child for the promise and peril of BYOD than we might have expected.

MORE INSIGHTS

Their problems with Consumerization of IT are, in the abstract, no different from the same issue any other company has faced when they start a BYOD policy: access to potentially disruptive services; a proliferation of unwanted and unauthorized software within the organization; unclear consequences for many actions.

But everything I've heard about IBM's corporate culture tells me it's a place where IBM comes first--their tools, their software, their processes, their systems, their everything. Small wonder they get antsy when people bring in third-party solutions like Dropbox, even if those products and services provide valuable benefits to the business.

This might have worked in decades past, but it's becoming increasingly untenable for companies of its size -- or, for that matter, any size. Heterogeneity's the way IT works now, with BYOD only being one part of that picture. IBM may never have gotten fired for buying IBM -- along with plenty of other people, once upon a time, but what about now?

So what's behind IBM's sudden reassessment of BYOD?

They're worried about leaks. And rightfully so. One of the major challenges of any BYOD arrangement is how to keep insiders from walking out with the company's intellectual property -- which is the single biggest way corporate espionage continues to be committed. (It isn't hackers, Anonymous notwithstanding.) Shutting off access to Siri was apparently part of this, as they didn't know what happened to the queries once they were made.

But the newest trend in COIT, and a rising one, is professional versions of the same services with management policies built in. Box.com, for instance, has all this and more. I suspect just about every "personal" service launched from now on will come with a "professional" tier--and if it does, it better have disclaimers about what's done with data gathered from both regular and corporate customers.

Their BYOD policy wasn't as well-thought-out as they hoped. Based on what the above-linked article says, it sounds like IBM's BYOD initiative was rolled out with the expectations that end users would know how to deal with their own devices; but they didn't, for the most part, have that knowledge. (Says the article: "'We found a tremendous lack of awareness as to what constitutes a risk,' says Horan. So now, she says, 'we're trying to make people aware.'")

Their expectations were wrong. What you expect to get from BYOD is as important as how you go about implementing it. One telling quote from the piece: "The trend toward employee-owned devices isn't saving IBM any money" (according to IBM's CIO, Jeanette Horan). The problem, as I've seen elsewhere, is how you define savings. Perhaps for them the projected costs of supporting BYOD -- and especially, the cost of setting up retroactive protection measures -- exceed any imagined gains in productivity.

But until they produce some hard numbers to back that up, I'm going to go out on a limb and say the gains provided through BYOD (and everything that goes with it) are more than worth the hassle, if only in terms of employee satisfaction and comfort. Some of those things cannot be quantified easily or conventionally, especially if you're only looking at the current quarter or a season or two ahead.

I'm sure even IBM recognizes it can't keep its finger in the dyke forever. COIT is something you either make happen, or which happens to you -- and there's only so far they can turn their own clock back before it breaks. But if IBM gets it right, they could serve as one of the better models for others to follow, instead of a classic example of what not to do.

報導：IBM內部禁用Siri、Dropbox

文/陳曉莉 (編譯) 2012-05-24

此外，BYOD並沒有替IBM省下任何金錢，打破BOYD可降低企業成本的說法，因為企業可能要耗費更多的成本來支援BYOD或維持其安全性，IBM的例子恰巧展示了現今擁抱BOYD的企業所面臨的挑戰。

MIT Technology Review引述 IBM資訊長Jeanette Horan表示，許多受歡迎的行動應用程式可能造成內部的安全風險，因此已列出禁用的行動程式，諸如Dropbox，以及蘋果的iCloud與Siri等。

IBM禁用網路硬碟空間Dropbox或iCloud可能很合理，Horan說，該公司擔心員工以行動裝置使用公開的檔案分享服務可能會導致機密資料外洩。至於禁用Siri，則是擔心使用者的查詢可能被存在某處而不自知。Horan坦承，IBM可能太過保守，但保守是IBM的本質。

雖然IBM也是自帶裝置上班（Bring Your Own Device，BYOD）政策的擁護者，但對於BYOD亦進行了一定的規範。例如在員工裝置連網之前，IT部門會先設定該裝置，啟動遠端移除功能，以在裝置遺失或失竊時能移除裝置上的機密資訊；而且對不同品牌的裝置或是不同職位的員工設有不同的規範，例如某些員工只能透過自己的裝置存取IBM的電子郵件、行事曆與聯絡人名單，而有些人則能存取內部的應用程式與檔案，但後者的裝置上必須加上安全軟體以防資訊外洩。

BYOD符合了消費化IT的趨勢，思科最近的調查顯示，有95%的企業允許員工在職場上使用自己的裝置，以改善員工的生產力並提高工作滿意度。市場研究機構Gartner則預測該趨勢將使企業IT的預算脫離IT部門的掌控，而且IT部門必須具備更好的協調性。

有媒體評論指出，IBM除了擔心資訊外洩之外，也發現員工並不如原先所預期地知道如何進行裝置的安全管理，此外，Horan甚至還說，BYOD並沒有替IBM省下任何金錢，打破BOYD可降低企業成本的說法，因為企業可能要耗費更多的成本來支援BYOD或維持其安全性，IBM的例子恰巧展示了現今擁抱BOYD的企業所面臨的挑戰。（編譯/陳曉莉）

祖克柏

2012-05-23T09:36:00.002+08:00

http://tw.news.yahoo.com/%E7%A5%96%E5%85%8B%E6%9F%8F%E4%B8%AD%E6%96%87-%E5%9A%87%E5%9A%87%E5%8F%AB-%E6%AF%94%E8%8F%AF%E8%A3%94%E6%84%9B%E5%A6%BB%E9%82%84%E6%B5%81%E5%88%A9-043847667.html

祖克柏規定自己一天的時間中，至少要有1小時健身、1小時學中文、6小時睡覺，其他時間都專注在產品技術上，年僅28歲的他能讀寫法語、希伯來語、拉丁語、古希臘語和中文，即便年紀輕輕就坐擁上億身價，但祖克柏物質慾望卻極低，不開名車、崇尚簡單生活哲學。

據《財星》雜誌報導，祖克柏只吃自己親手宰殺的動物，曾在臉書上分享自己殺雞及料理後的食物照，祖克柏說，自從他開始執行這項挑戰後，每次邀朋友到家裡聚餐，大夥兒都變得不太敢吃肉。

一名住在離祖克柏住處不遠的廚師說：「他用割喉的方式殺羊，是最仁慈的宰殺方法。」祖克柏說：「因為我只吃自己殺的動物，所以我基本上成了素食主義者。我覺得很多人都忘了，為了你要吃肉，就有動物必須犧牲。」希望自己常存感謝的心。

Intel® Advanced Encryption Standard (AES)

2012-05-22T16:41:00.001+08:00

	January 24, 2010 10:00 PM PST

Introduction

Intel® AES instructions are a new set of instructions available beginning with the all new 2010 Intel® Core™ processor family based on the 32nm Intel® microarchitecture codename Westmere. These instructions enable fast and secure data encryption and decryption, using the Advanced Encryption Standard (AES) which is defined by FIPS Publication number 197. Since AES is currently the dominant block cipher, and it is used in various protocols, the new instructions are valuable for a wide range of applications.

The architecture consists of six instructions that offer full hardware support for AES. Four instructions support the AES encryption and decryption, and other two instructions support the AES key expansion.

The AES instructions have the flexibility to support all usages of AES, including all standard key lengths, standard modes of operation, and even some nonstandard or future variants. They offer a significant increase in performance compared to the current pure-software implementations.

Beyond improving performance, the AES instructions provide important security benefits. By running in data-independent time and not using tables, they help in eliminating the major timing and cache-based attacks that threaten table-based software implementations of AES. In addition, they make AES simple to implement, with reduced code size, which helps reducing the risk of inadvertent introduction of security flaws, such as difficult-to-detect side channel leaks.

This paper gives an overview of the AES algorithm and Intel's new AES instructions. It provides guidelines and demonstrations for using these instructions to write secure and high performance AES implementations. This version of the paper also provides a high performance library for implementing AES in the ECB/CBC/CTR modes, and discloses for the first time, the measured performance numbers.

Unified Storage

2012-05-22T12:00:00.001+08:00

unified storage (network unified storage or NUS)

Unified storage (sometimes termed network unified storage or NUS) is a storage system that makes it possible to run and manage files and applications from a single device. To this end, a unified storage system consolidates file-based and block-based access in a single storage platform and supports fibre channel SAN, IP-based SAN (iSCSI), and NAS (network attached storage).

A unified storage system simultaneously enables storage of file data and handles the block-based I/O (input/output) of enterprise applications. In actual practice, unified storage is often implemented in a NAS platform that is modified to add block-mode support. For example, Reldata Inc offers the SANnet universal IP storage system and Network Appliance Inc. offers a unified storage architecture. Numerous other products based on Microsoft's WUDSS (Windows Unified Data Storage Server) have been configured to support both block and file I/O.

One advantage of unified storage is reduced hardware requirements. Instead of separate storage platforms, like NAS for file-based storage and a RAID disk array for block-based storage, unified storage combines both modes in a single device. Alternatively, a single device could be deployed for either file or block storage as required.

In addition to lower capital expenditures for the enterprise, unified storage systems can also be simpler to manage than separate products. However, the actual management overhead depends on the full complement of features and functionality provided in the platform. Furthermore, unified storage often limits the level of control in file-based versus block-based I/O, potentially leading to reduced or variable storage performance. For these reasons, mission-critical applications should continue to be deployed on block-based storage systems.

Unified storage systems generally cost the same and enjoy the same level of reliability as dedicated file or block storage systems. Users can also benefit from advanced features such as storage snapshots and replication, although heterogeneous support between different storage platforms should be considered closely. While experts predict a bright outlook for unified storage products, it is likely that dedicated block-based storage systems will remain a popular choice when consistent high performance and fine control granularity are important considerations.

This was last updated in December 2006

Editorial Director: Margaret Rouse

2012-05-21T10:07:00.002+08:00

Web 2.0: Article

Citrix Buys Virtual Computer

It means to combine the acquisition’s NxTop widgetry with its XenClient hypervisor

BY MAUREEN O'GARA	ARTICLE RATING:	GIVE IT 1/5 GIVE IT 2/5 GIVE IT 3/5 GIVE IT 4/5 GIVE IT 5/5
MAY 20, 2012 12:00 PM EDT	READS:	1,025

Citrix has acquired Virtual Computer, a little Massachusetts outfit with enterprise-scale management solutions for client-side virtualization.

It means to combine the acquisition's NxTop widgetry with its XenClient hypervisor to create a new Citrix XenClient Enterprise edition that can manage "large fleets" of corporate laptops across a distributed enterprise and give users a virtual desktop "to go."

It's due this quarter as a standalone product at a reported $175 a user.

Citrix said it's getting the management piece faster by buying it.

Virtual Computer has historically focused on solutions for Xen-based client hypervisors. Its technology includes backup, disaster recovery, provisioning, security and monitoring capabilities. The merger also promises greater integration between XenClient and XenDesktop.

Citrix Announces XenClient Enterprise and Acquisition of Virtual Computer

New Offering Combines Power of XenClient Hypervisor with Enterprise-Class Management of Virtual Computer

San Francisco, CA » 5/9/2012 » Today, at Citrix Synergy™, the conference where mobile workstyles and cloud services meet, Citrix announced the acquisition of Virtual Computer, provider of enterprise-scale management solutions for client-side virtualization. Citrix will combine the newly-acquired Virtual Computer technology with its market-leading XenClient® hypervisor to create the new Citrix XenClient Enterprise edition. The new XenClient Enterprise will combine all the power of the XenClient hypervisor with a rich set of management functionality designed to help enterprise customers manage large fleets of corporate laptops across a distributed enterprise. The combined solution will give corporate laptop users the power of virtual desktops “to go”, while making it far more secure and cost-effective for IT to manage thousands of corporate laptops across today’s increasingly mobile enterprise.

The number of highly mobile workers as a segment of total employees is growing dramatically. IDC expects that by 2015 they are expected to make up nearly 40 percent of the workforce*. As a result, the number of laptops used by professional workers is exploding. Industry analysts see the growth in mobile devices like tablets and smartphones as complementary to PCs, making it more important than ever to have a holistic, enterprise-wide desktop virtualization strategy that enables anywhere, anytime access to desktops, applications and data from any device. IT will continue to invest in laptops for mobile and office-based workers, and must address the deployment, management and security challenges that go with these devices, while faced with the added demands mobile devices introduce to the enterprise.

CDN content delivery network

2012-05-21T10:06:00.000+08:00

A content delivery network (CDN) is a large distributed system of servers deployed in multiple data centers in the Internet. The goal of a CDN is to serve content to end users with high availability and high performance. CDNs serve a large fraction of the Internet content today, including web objects (text, graphics, URLs and scripts), downloadable objects (media files, software, documents), applications (e-commerce, portals), live streaming media, ondemand streaming media, and social networks.

A CDN operator gets paid by content providers such as media companies and e-commerce vendors for delivering their content to their audience of end users. In turn, a CDN pays ISPs, carriers, and network operators for hosting its servers in their datacenters. Besides better performance and availability, CDNs also offload the traffic served directly from the content provider's origin infrastructure, resulting in cost savings for the content provider.^[1] In addition, CDNs provide the content provider a degree of protection from DoS attacks by using their large distributed server infrastructure to absorb the attack traffic. While most early CDNs served content using dedicated servers owned and operated by the CDN, there is a recent trend^[2] to use a hybrid model that uses P2P technology. In the hybrid model, content is served using both the dedicated servers and other peer user-owned computers as applicable.

bring your own device (BYOD) phenomenon

2012-05-18T08:48:00.001+08:00

Will BYOD revive the network-access control idea? Gartner thinks it will

First integrated NAC/mobile-device management products announced; Gartner says expect others to follow

By Ellen Messmer, Network World
May 08, 2012 06:04 AM ET

1 Comment
Print

. What's this?

Is the BYOD craze going to bring a revival of NAC, the policy-based network-access control that was hyped a decade ago but didn't end up widely adopted for endpoint security?

Gartner, for one, is predicting the bring your own device (BYOD) phenomenon, in which employees are being allowed to use their own personal Apple iPads, iPhones, GoogleAndroid devices and other mobile-ware for business purposes, will lead to a revival of NAC.

CASE STUDY: BYOD policy bites vacationing CEO

BYOD BATTLE: A tale of two opposing IT viewpoints

NAC, you may recall, was supposed to be widely used for employee and guest worker computer access to enterprise networks, doing things like checking to make sure antivirus or patch updates were in place before allowing users on. Though a respected technology, NAC just didn't catch on to big effect. This time around though, NAC will be wedded to mobile-device management (MDM) software and the NAC function will be there to ensure MDM requirements are being met before allowing that Android and iPhone device or Windows mobile devices onto the networks -- at least that's the idea.

"NAC has been around for almost 10 years," says Gartner analyst Lawrence Orans, who acknowledges the "first wave" of NAC crested with a fairly modest adoption, mainly by financial institutions and some high-security situations, plus a few universities.

But NAC is getting a second chance to go mainstream because of BYOD, and this time it will gain much more ground as a security approach, Orans predicts. "BYOD is an unstoppable trend," he predicts, with businesses in ever greater numbers allowing employees to carry enterprise data on personal tablets.

It seems the software industry may be willing to bet on it, too. The first integrated NAC/MDM was announced today as Fiberlink, which provides MDM via its cloud-based MaaS360 mobile-device management service, detailed how it's partnering with ForeScout with its agentlessCounterAct appliance for NAC.

According to Scott Gordon, ForeScout vice president of worldwide marketing, anyone with the Fiberlink MDM will now be able to exert NAC controls for Apple iOS or Google Android devices with a CounterAct add-on module. And ForeScout in turn will soon be selling what it calls "ForeScout MDM powered by MaaS360" under a licensing arrangement with Fiberlink. ForeScout anticipates similar arrangement with other MDM vendors.

There are a lot of MDM vendors today -- London-based consultancy Ovum estimates there are about 70 MDM vendors of varying types angling for attention.

NAC being forged into MDM offers some advantages, says Orans, in terms of allowing IT managers to set policy-based controls on BYOD tablets and smartphones in the enterprise. In the mobile-device context, NAC might check to see if there's BYOD "containerization" in place, for instance, to make sure personal and business data is cordoned off in some way before granting network access.

Fiberlink and ForeScout say their approach for BYOD allows for a policy to isolate personally owned devices in a limited access zone, where they may access a subset of applications and data.

Employees may find advantages in the NAC/MDM controls, too, said Fiberlink's Neil Florio, vice president of marketing, because it will allow for the enforcement of privacy settings. "Employees have the fear that management will have the ability to see things on their devices they wish they wouldn't," he noted. But an IT organization can set that, determining not to look into personal data on a BYOD tablet.

Orans says the Fiberlink/ForeScout partnership may be the first to meld NAC and MDM but there are going to be several more to follow in the future.

Ellen Messmer is senior editor at Network World, an IDG publication and website, where she covers news and technology trends related to information security.

Read more about security in Network World's Security section.

1 Comment
Print

HP Converged Cloud and HP Public Cloud: Details Confirmed by Joe Panettieri on 4.10.12

2012-05-04T11:12:00.004+08:00

HP Converged Cloud and HP Public Cloud: Details Confirmed by Joe Panettieri on 4.10.12

Hewlett-Packard officially launched the HP Converged Cloud and HP Public Cloud strategies today. HP Converged Cloud seeks to offer channel partners and customers a hybrid delivery approach that spans traditional IT, private, managed and public clouds. Plus, the HP Public Cloud is built on OpenStack and will include a MySQL relational database service that competes with Microsoft SQL Azure and other cloud database platforms.

Missing from the HP Converged Cloud and HP Public Cloud announcements: A clear channel partner program message that describes margins and recurring revenue opportunities to cloud integrators, cloud consultants, cloud brokers, VARs and MSPs.

Still, let’s cut HP some slack. Today’s HP Converged Cloud and HP Public Cloud announcements were designed to deliver big-picture statements rather than deeper partner program details.

HP Converged Cloud Details

The HP Converged Cloud effort leverages OpenStack, the open source cloud platform. But this is far more than an OpenStack strategy. The HP Converged Cloud effort focuses on three core themes, according to the company:

Choice – through an open, standards-based approach supporting multiple hypervisors, operating systems and development environments as well as a heterogeneous infrastructure and an extensible partner ecosystem.

Confidence – through a management and security offering that spans information, applications and infrastructure.

Consistency – through a single common architecture.

HP Public Cloud Details

Also announced by HP today:

An HP Public Cloud that will focus on Infrastructure as a service. A public beta opens May 10. Plus, a private beta will allow partners and customers to test MySQL as a relational database service — essentially countering Microsoft SQL Azure and cloud database platforms from Amazon and Rackspace, among others.

To manage hybrid environments, HP has launched HP Cloud Maps, which offers pre-packaged application templates for “push-button” deployment, HP claims.

An HP Service Virtualization 2.0 platform will allow partners and customers to test cloud and mobile applications without disrupting production systems, HP claims.

HP Virtual Application networks, which claims to speed application deployment and automates management.

HP Virtual Network Protection Service provides security at the network virtualization management layer.

HP Network Cloud Optimization Service helps customers to enhance their network to improve cloud-based service delivery.

HP Enterprise Cloud Services will allow customers to outsource cloud management to HP

Gaining Clarity

The arrival of HP Public Cloud and HP Converged Cloud could help Hewlett-Packard to end confusion about the company’s cloud computing and cloud services strategy.

While still CEO of HP, Leo Apotheker in early 2011 delivered a rambling HP cloud strategy speech at the HP Americas Partner Conference in Las Vegas. Apotheker claimed the HP cloud effort would compete with everything from Apple iTunes to Rackspace. But he offered no details on actual cloud deliverables, and Apotheker ultimately was ousted in September 2011.

Fast forward to the present, and HP has unveiled a massive portfolio of cloud services for partners and customers. But how will the HP Cloud strategy play with partners and customers? Talkin’ Cloud expects to gain some early clues during the OpenStack Design Summit and Conference (April 16-20, San Francisco). HP is expected to speak at the conference, which will also include insights from Dell, IBM, Rackspace and other cloud rivals.

英特爾：2015年將是Scale-out儲存的天下文/鄭逸寧 2012-05-01

2012-05-04T11:01:00.000+08:00

英特爾：2015年將是Scale-out儲存的天下

文/鄭逸寧 2012-05-01

英特爾預言，Scale-out儲存系統將取代現有的Scale-up架構，並在2015年達到8成全球儲存網路市占率，解決巨量資料挑戰

整體而言，英特爾將企業儲存系統從過去到未來的演進分為3階段，分別為Scale-up架構、Scale-out架構，以及無所不在儲存服務（Ubiquitous Storage）。英特爾儲存事業部總經理David Tuhy表示，目前Scale-out架構正在取代現有的Scale-up架構，全球市占率將於2015年達到8成，成為主流的儲存架構。

儲存從Scale-up轉Scale-out，但高價仍是普及瓶頸
第一種是目前最普遍的Scale-up架構儲存系統，在這樣的架構之下，企業只能利用單臺安裝了儲存系統的控制器來擴充儲存容量，因而受限於單臺控制器的硬體規格，萬一儲存容量暴增，以至於超過單臺控制器的極限，企業就必須汰換舊有設備，新採購更高硬體規格的控制器。此外，全套儲存系統都要透過內網互相連結，導致企業難以跨不同儲存系統集中控管與調配資源。

基於這些特性，Scale-up儲存系統經常造成企業彈性擴充與管理上的限制。英特爾舉例，Scale-up架構難以在公有雲與私有雲資料中心之間傳遞資料，而且不利於快速擴充，若企業未來要擴充至PB等級的儲存容量，則被迫要不斷投資儲存的硬體設備。此外，IT人員只能獨立管理不同套的儲存系統，難以透過單一平臺集中控管多套系統，無法規畫為儲存資源池，來有效配置儲存資源。

為了解決Scale-up儲存系統的限制，Scale-out架構應運而生，而且英特爾認為，現階段Scale-out正在逐步取代Scale-up儲存系統。Scale-out儲存系統不受限於單臺控制器節點的硬體規格，每臺安裝儲存系統的控制器將如同資料中心儲存網路的模組化元件，透過外部網路互相連結，可視為單一套儲存系統來集中控管。更重要的是，當未來企業要擴充儲存容量時，只要添購儲存控制器的數量，就能繼續擴充同一套儲存系統的容量。

而且每臺控制器提供如同一臺伺服器的規格，來執行更高階的管理功能，包括熱抽換、壓縮、精簡配置（Provisioning）、資料重複刪除等，讓企業集中控管所有控制器節點的運作，利於企業擴充、配置儲存資源。

不過，目前Scale-out儲存系統的初期採購成本過高，導致企業難以普遍採用。臺灣IDC伺服器與儲存分析師高振偉表示，Scale-out儲存系統架構需要許多搭載更高規格處理器的控制器，才能提供高階的擴充與管理功能，導致整套Scale-out儲存系統的價格居高不下。此外，企業導入Scale-out儲存系統時，通常必須重新規畫儲存網路架構，因而需要搭配廠商的系統整合服務，來整合既有的儲存資源，這也成為另一筆成本負擔。

高振偉表示，近兩年來，主要是HP、IBM等大廠推出Scale-out儲存系統，目前台積電、聯發科等高科技製造業，以及教育研究機構、政府單位等產業陸續導入。這些企業主要是看重Scale-out架構的擴充彈性，不僅用來儲存與日俱增的結構化資料庫，高科技業者還用來儲存大量非結構化的客戶資料與晶圓設計資料，利於快速擴充儲存容量。他坦言，目前較小的儲存廠商仍主打傳統Scale-up產品，明年才會陸續推出Scale-out產品，可望壓低價格，降低企業的導入門檻。

到了2015年，儲存系統將基於Scale-out儲存系統，來提供Ubiquitous無所不在的儲存服務，將能夠支援混合雲型態、自動化與終端覺知。

透過這3項特性，企業的資料可以安全地在公、私有雲端基礎架構運作，並提供自動化管理功能，包括動態擴充、搜尋、復原系統內的資料等。此外，儲存系統還會具備終端覺知的功能，由於使用者的各種終端裝置將進行大量的資料產出與取用，像是上網、拍照、看影片等，不僅造成資料量暴增，還必須快速地存取與傳遞這些資料。因此，儲存系統必須有效控管終端裝置的資料產出與使用，才能實現無所不在的儲存服務。文⊙鄭逸寧

IDC：2011年臺灣伺服器市場成長2成文/鄭逸寧 2012-04-24

2012-04-26T13:23:00.001+08:00

IDC：2011年臺灣伺服器市場成長2成

文/鄭逸寧 2012-04-24

根據IDC調查，去年臺灣伺服器市場成長2成，趨動力來自高科技製造業擴建廠區、政府推動雲端專案與電信媒體擴建IT架構

臺灣IDC伺服器市場調查報告顯示，2011年臺灣伺服器市場的原廠營收（Factory Revenue）較2010年成長2成，維持從2009年以來的高成長。

臺灣IDC伺服器與儲存市場分析師高振偉表示，去年帶動伺服器市場成長的驅動力來自於政府、高科技與電信媒體等產業。政府的採購專案包括內政部的戶役政資訊系統、財政部電子發票系統、防救災系統等，都趁著雲端計畫而完成建置；不少高科技業者也在去年上半年開始擴建新廠房，像是台積電在南科擴建半導體廠區，到了年底經濟不景氣時，部份的擴建計畫才陸續停擺；多家電信業者建置雲端基礎架構，而媒體業者則是建置網站服務等，這些建置案帶動了去年伺服器市場的採購需求。

以不同的伺服器平臺來看，x86與non-x86市場都較2010年成長將近2成，相較歷年來的成長率，x86市場維持穩定成長，而non-x86市場的成長幅度則比前幾年更高。

2011年臺灣伺服器營收成長19.3%

一般而言，若檢視x86與non-x86廠商的市占排名，會以出貨量來看x86，以營收來看non-x86。一般而言，x86伺服器基本規格會遵照業界一定的標準，而且各廠牌售價差距不大，如果以營收來看廠牌市占，反而容易受到大量採購的折扣優惠影響，所以出貨量較能反映企業採購x86伺服器的需求。另外，不同類型的non-x86伺服器售價落差懸殊，而且企業單次採購的量也不多，所以較適合透過廠牌營收來觀察企業的需求。

各廠牌在2011年的表現方面，各x86伺服器廠商的出貨量市占排名依序為HP、IBM、Dell、華碩與宏碁。其中HP與Dell都比2010年成長近16%，成長幅度遙遙領先其他廠商，而IBM與華碩僅成長3.7%，宏碁甚至下滑了25%。

HP奪冠，x86市占超過3成

高振偉表示，去年HP的客戶來自電信與製造業大規模的建置案，Dell則來自既有的電信、網路服務與部分製造業擴建基礎架構，新增專案則是電子商務平臺的建置需求，這些產業在去年的採購需求很顯著，因而帶動這些廠牌x86出貨量的成長。另外，宏碁去年調整了公司內部的組織人力、產品線與通路，精簡部分的產品線，因而造成出貨量下滑。

至於各non-x86伺服器廠商的營收市占排名依序為IBM、HP、Oracle。相較於2010年，Oracle躍升6成，IBM成長3成，HP卻下滑將近1成。高振偉表示，IBM主要的營收來自既有用戶要汰換大型主機，而不是因為新用戶導入；Oracle在2010年併購昇陽後，在non-x86營收市占下滑3～4成，然而，在去年，除了彌補先前下滑的市占，還因為Oracle推出了整合雙方軟硬體產品的解決方案，獲得市場迴響，因而帶動營收的成長。

進一步來看不同伺服器平臺出貨量的市占率，機架式伺服器突飛猛進，去年的市占高達7成，已在過去4年內增加了13個百分比，工作站與刀鋒伺服器的出貨量市占率為3成，有逐年下滑的態勢，尤其是工作站從2008年的34%市占下滑為2011年的23%。

高振偉指出，機架式伺服器的基本規格已達標準化，在大規模的雲端資料中心當中，便於企業快速部署與汰換設備，同時較能簡化維運管理工作，因而帶動出貨量快速成長。

然而，工作站與刀鋒伺服器偏向專屬的應用環境，如工作站大多用來執行中小企業的小型系統，提供30～50位員工使用，隨著公有雲平臺興起，越來越多中小企業改採公有雲或線上租用服務，來節省自行維運的負擔，因而造成工作站的市占下滑，刀鋒伺服器市占大致持平，由於不同廠牌的刀鋒產品欠缺統一規格，價格也偏高，造成應用較難普及。文⊙鄭逸寧

機架式伺服器市占上看7成，排擠刀鋒與工作站

AMD伺服器平臺處理器文/林柏凱

2012-04-25T10:58:00.002+08:00

全面剖析2012 AMD伺服器平臺處理器

文/林柏凱 2012-04-05

AMD去年底推出的Opteron 6200系列與4200系列處理器，核心全面採用新的Bulldozer架構，以6200系列而言，最多內建16核心

在2011年11月，AMD推出了新一代伺服器專用，代號為Interlagos的Opteron 6200與4200系列處理器，接續先前的Opteron 6100及4100系列，並且一舉將最高的內含核心數增加到16核心。

除了Opteron 6200與4200系列之外，AMD在3月20日發表3款代號為Zurich 的Opteron 3200系列，主要針對微型伺服器、網站主機代管與網路伺服器等低功耗需求。這系列處理器也和上述Opteron處理器一樣，繼續採用Bulldozer架構，而且內建8或4核心，但處理器插槽是AMD在桌上型電腦處理器所採用的AM3+規格。

處理器全面使用32奈米製程，並採用Bulldozer核心架構
在核心架構上，新一代Opteron系列處理器最大的改變，就是Bulldozer核心架構，並且將製程從45奈米提高為32奈米，而且增加處理器核心數量的同時，也延續、加強前一代所擁有的HyperTransport，並新增動態超頻技術Turbo Core。在採用的插槽上，Opteron 6200系列處理器採用G34規格，而4200系列則採用C32規格，而採用G34插槽的6200系列處理器，在外觀上呈現特殊的長方形，而不是一般常見的正方形。

而主機板相容性部分，從上一代Opteron 6100與4100開始，就開始各自使用G34與C32處理器插槽，因此即使是採用上述處理器的伺服器，換CPU後可以直接升級，且根據AMD的規畫，目前這些插槽規格，會延續使用到下一代採用Piledriver核心架構的處理器，所以這段期間並不會因為採用不同的處理器插槽，讓伺服器無法升級。

Bulldozer核心架構
在新的Bulldozer核心架構下，每個處理器核心模組都內建兩個擁有獨立L1快取記憶體的整數運算核心，以及與浮點運算排程器（使用2個128位元乘法累加器），並共用讀取器、編譯器與L2快取記憶體，而L3快取記憶體是由整顆處理器共用。

AMD伺服器平臺處理器推出規畫（2012-2013）
在AMD規畫的下一代伺服器處理器，依然採用G34、C32與AM3+的處理器插槽，並採用Piledriver核心架構，現有的Bulldozer核心架構的伺服器不必擔心升級的問題，另外還新增針對網頁代管以及微型伺服器架構的Opteron 3000系列。

產品定位涵蓋範圍廣，選擇較單純
在AMD 的Opteron處理器定位中，4000系列向來是針對單路與2路伺服器所搭配的處理器，而6000系列則使用於2路與4路伺服器，而最新發表的3200系列則是單路，但主打的是低功耗的環境，這和Intel Xeon推出E3、E5與E7等系列處理器的分類方式不大相同。

如果將Opteron 6000系列與Intel Xeon E7相提並論，或許是比較恰當的，因為它們同樣都支援2路與4路伺服器的架構。不過，Xeon E7系列處理器在配置上，若要將它們安裝在2路或4路的伺服器上，必須選用針對2路或以上規格的處理器，也就是說必須選擇更高規的處理器，例如E7-2860就只能用在2路，E7-4820就可以用在4路以及2路的架構（4插槽僅安裝2顆處理器），而Opteron 6200系列沒有這種限制，因為全系列都支援4路架構，也同樣可向下相容2路、甚至單路架構，也就是同型號的處理器不論是裝2顆或4顆都可以，不必特定選用針對2路或4路架構的處理器。

在價格部分，較便宜一直都是AMD處理器的特色，根據去年發表時的價格，Opteron 6200與4200處理器中最高階、價位最貴為6282 SE，每千顆單位的報價為1,019美元，這樣的價格在Intel Xeon E5處理器中，僅有E5-2650與E5-2650L，或是更低階的處理器價格，才會接近，或低於這顆處理器。而Xeon E7處理器中，更是僅有2路的E7-2803與4路的E7-4807售價低於Opteron 6282 SE。從這結果可看出AMD Opteron處理器的價格相較於Intel Xeon處理器相對便宜許多。

綜觀伺服器廠商的產品型號與規格，可看出目前採用AMD Opteron 6200或4200處理器的產品數量，遠少於Intel Xeon系列伺服器，例如HP的20款機架式伺服器系列中，僅有6款採用AMD處理器的產品，而Dell的22款機架式伺服器中，僅有6款採用AMD Opteorn處理器，而直立式伺服器則是付之闕如。有些廠商僅推出採用Intel Xeon處理器平臺的機種，並沒有任何AMD平臺的產品（如NEC），不難看出，目前處理器市場的主流處理器平臺仍然是Intel。

最多內建16個實體核心
在這一代採用Bulldozer核心架構的AMD Opteron系列處理器，最主要的改變，就是實體核心數量的增加。

在Opteron 6100系列中，處理器內建核心數量為8核心和12核心，而4100系列處理器是4核心和6核心，到了現在，採用Bulldozer核心架構的Opteron 6200系列處理器，核心數最多16核心，且另外還有4、8、12核心的選擇，而4200系列最多到8核心。

與Intel Xeon處理器相比，「實體」核心數量較多，一直是AMD Opteron處理器所強調的，舉例來說，Intel Xeon上一代處理器中，主打2路伺服器的5600系列處理器，最多只有實體4核心與6核心。

雖然Intel在目前最新的Xeon E7系列處理器中，最高擁有10核心，且有超執行緒（Hyper Threading）使每個實體核心模擬為兩個虛擬核心，讓作業系統可運用到更多的核心，例如在2路伺服器架構下，搭配2顆4核心的處理器，你的系統就有16個運算核心，但AMD Opteron則是實體核心就可達到這個數量。

另一方面，目前Intel Xeon E7處理器中，最多擁有10核心，加上超執行緒技術，每顆處理器一共有20個執行緒，雖然同時可處理的執行緒數量上比AMD Opteron 6200系列的16核心處理器還多，不過內建10核心的處理器僅限4路以上的伺服器架構，例如E7-4850或4860以上，而AMD Opteron 6200在2路伺服器即可採用。

就時脈而言，比較特別的，是主打2路與4路的Opteron 6200系列處理器中，有一顆僅有4核心且沒有Turbo Core超頻技術的6204，雖然以這規格來看，這顆處理器規格較低，但是它的基礎時脈高達3.3GHz，居所有Opteron 6200系列處理之冠。

在I/O方面，AMD Opteron處理器從上一代6100系列開始，即採用了HyperTransport 3.1的技術，讓處理器與處理器之間可直接產生連結溝通（Direct Connect Architecture），且當中的傳輸速度達6.4GT/s。

近來因為虛擬化的需求與日漸提升，伺服器對記憶體的需求也越來越高，尤其是記憶體總容量的需求。

對AMD Opteron 6200而言，在記憶體容量的支援上，每顆處理器都可對應256GB，例如2路伺服器可支援24支記憶體（512GB），而4路伺服器的話，則可安裝32支記憶體（1TB）。另外，新一代的Opteron 6200系列處理器也繼續支援4條記憶體通道的存取方式、新支援DDR3 1600MHz的記憶體規格。

1個Bulldozer模組內建2個整數運算核心
新的Bulldozer架構與以往處理器設計的方式有很大不同，那就是它將兩個整數運算核心合併，而且這兩個核心共用一些編譯器（Decode）與讀取器（Fetch），同時共用一個浮點運算排程器（FP Scheduler）整合在同一個模組中。以16核心的Opteron而言，實際上是以8個Bulldozer所組成。

AMD認為，這種架構的好處，是在多執行緒的狀態下，可以使每個核心分別運算，並且在L2快取記憶體的部份共用運算結果，加快運算的速度。

除了前面提到的整數運算、浮點運算，以及提高處理器核心時時脈的Turbo Core技術之外，採用Bulldozer核心架構的Opteron系列處理器，也將多種常見的指令集內建其中，例如SSE4.1、SSE4.2、SSSE3等編碼標準，以及先進向量擴充指令集（AVX）與進階加密標準指令集（AES）等。

首度加入動態超頻技術
在時脈超頻的技術上，Bulldozer架構採用的是AMD 第二代的Turbo Core的技術，第一代Turbo Core技術首次出現在AMD產品，是在桌上型電腦處理器Phenom II X6上。這種超頻的方式和Intel的Turbo Boost類似，同樣可以動態調節核心的頻率，適合需要執行緒較少，但是需要高時脈來加速運算的工作。

AMD新一代核心超頻技術Turbo Core
AMD Turbo Core超頻技術，讓處理器可依工作內容與負載，動態調整全部核心的運作狀態，並可在特定需要高時脈工作的狀態下，降低部分核心，提高其餘核心的時脈。

而Turbo Core的處理器頻率，變化分為3階段：所有核心都運作在基礎時脈上、所有核心加速機制都啟動的狀態，以及部分核心最大加速機制啟動。

在一般狀態下，所有的處理器核心都只運作在基礎時脈上，而這種狀態下處理器的熱設計功耗（TDP）都還有餘裕。第二種是所有核心的加速機制都啟動的狀態，每個核心的時脈速度可提高300MHz到500MHz，而TDP已經處於最高負載狀態；第三種為最大加速模式，則是讓部分核心的時脈速再提升，最高可提高1GHz，其餘核心則是處於待機狀態。

看起來和Intel Turbo Boost有些類似，但是AMD Turbo Core在超頻時，僅能集中在一半的核心上，也就是如果是16核心處理器，在最大加速模式下，可以讓8個核心的時脈速度提高，不像Intel Turbo Boost2.0可集中在單一核心上，而且很可惜的是其他核心僅處於低速狀態，無法完全關閉，因此仍會有因運作而產生的耗能。反觀Turbo Boost在超頻時，可以集中在部分，甚至單一核心時脈上，而其他核心則處於關閉狀態。

整體而言，AMD的Turbo Core在運用彈性與效能供應上，都還有進步的空間。文⊙林柏凱

2012 AMD最新Opteron處理器的規格

產品線與定位	型號	核心數	時脈	超頻時脈	L3快取記憶體	TDP	支援記憶體規格	插槽類型
6200系列(Interlagos)針對4路與2路系統	6282 SE	16	2.6GHz	3.3GHz	16MB	140W	DDR3-1600 MHz	G34
	6276	16	2.3GHz	3.2GHz	16MB	115W	DDR3-1600 MHz	G34
	6274	16	2.2GHz	3.1GHz	16MB	115W	DDR3-1600 MHz	G34
	6272	16	2.1GHz	3.0GHz	16MB	115W	DDR3-1600 MHz	G34
	6262 HE	12	1.6GHz	2.9GHz	16MB	85W	DDR3-1600 MHz	G34
	6238	12	2.6GHz	3.2GHz	16MB	115W	DDR3-1600 MHz	G34
	6234	8	2.4GHz	3.0GHz	16MB	115W	DDR3-1600 MHz	G34
	6220	8	3.0GHz	3.6GHz	16MB	115W	DDR3-1600 MHz	G34
	6212	4	2.6GHz	3.2GHz	16MB	115W	DDR3-1600 MHz	G34
	6204	8	3.3GHz	N/A	16MB	115W	DDR3-1600 MHz	G34
4200系列(Valencia) 針對2路與單路系統	4284	8	3.0GHz	3.7GHz	8MB	95W	DDR3-1600 MHz	C32
	4280	8	2.8GHz	3.5GHz	8MB	95W	DDR3-1600 MHz	C32
	4274HE	8	2.5GHz	3.5GHz	8MB	65W	DDR3-1600 MHz	C32
	4256EE	8	1.6GHz	2.8GHz	8MB	35W	DDR3-1600 MHz	C32
	4228HE	6	2.8GHz	3.6GHz	8MB	65W	DDR3-1600 MHz	C32
	4238	6	3.3GHz	3.7GHz	8MB	95W	DDR3-1600 MHz	C32
	4234	6	3.1GHz	3.5GHz	8MB	95W	DDR3-1600 MHz	C32
	4226	6	2.7GHz	3.1GHz	8MB	95W	DDR3-1600 MHz	C32
3200系列(Zurich) 針對單路系統	3280	8	2.4GHz	3.5GHz	8MB	65W	DDR3-1866 MHz	AM3+
	3260	4	2.7GHz	3.7GHz	4MB	45W	DDR3-1866 MHz	AM3+
	3250	4	2.5GHz	3.5GHz	4MB	45W	DDR3-1866 MHz	AM3+

Dell併Wyse Wyse在臺市占超過4成

2012-04-24T08:56:00.002+08:00

Dell併Wyse，奪Thin Client龍頭

文/鄭逸寧 2012-04-23

Dell併購精簡型電腦廠商Wyse後，企業期待Dell推出全套桌面虛擬化方案

日前Dell併購臺灣市占第一的精簡型電腦（Thin Client）廠商Wyse，補足Dell桌面虛擬化方案在終端設備的缺口。Dell原本就有銷售精簡型電腦，但產品種類較少，這次併購了Wyse之後，預計將納入Wyse旗下針對大量精簡型裝置的管理軟體、桌面虛擬化軟體、網路傳輸優化的產品、精簡型電腦，以及Wyse在全球的經銷通路等。

企業規畫虛擬桌面架構（Virtual Desktop Infrastructure，VDI）的同時，還必須調整後端機房的系統架構。如今Dell併購Wyse之後，可搭配Dell資料中心的產品，推出整套桌面虛擬化解決方案。

華泰電子企業資訊管理部資訊長王金秋表示，透過近幾年的併購案，Dell後端基礎架構的產品線更完整，涵蓋伺服器、儲存與網通設備等產品，不過，精簡型電腦的產品相對較少，仍以銷售個人電腦為主，透過併購Wyse，可望補足Dell這一塊的產品線，提供企業一站購足的解決方案。

例如，華泰電子採用Dell伺服器安裝VMware View桌面虛擬化軟體，搭配Wyse精簡型電腦，來建構公司的VDI架構，待未來兩家廠商的銷售通路合併後，華泰電子希望能以更優惠的價格，一次買齊桌面虛擬化從後端到終端的整套解決方案。另一方面，華泰電子還期待，未來Dell與Wyse兩家產品技術能夠進一步整合，來改善後端系統與精簡型電腦之間的管理與傳輸技術。

臺灣IDC針對2011年精簡型電腦市場各廠牌營收市占率的調查顯示，Wyse以42.4%市占率奪冠，HP則以25.7%市占居後，第三名則是市占11.9%的NComputing，其餘2成市占則由眾多廠商瓜分，包括Dell、ASUS、聯想等，如今Dell併購Wyse後，將晉身精簡型電腦市占第一的寶座。

臺灣IDC伺服器與儲存分析師高振偉表示，由於台積電新廠的終端設備大多採用Wyse精簡型電腦，帶動上下游產業跟著採用，導致Wyse共有8～9成的臺灣企業用戶都是製造業，這次Dell併購Wyse後，若能推出整套方案，將利於這些企業擴大導入。文⊙鄭逸寧

Wyse在臺市占超過4成
臺灣IDC針對2011年精簡型電腦廠牌營收市占調查顯示，Wyse以超過4成的市占率奪冠，居次的HP也只有2成5市占。

Google彰濱工業園區30億元台幣資料中心4月3日動土

2012-04-02T11:28:00.000+08:00

Google資料中心明動土

-字
+字

作者：記者何英煒╱台北報導 | 中時電子報 – 2012年4月2日上午5:30

工商時報【記者何英煒╱台北報導】

Google評估多年、去年9月正式宣布要在台灣的彰濱工業園區，投資一億美元（約30億元台幣），興建大型資料中心，確定將於4月3日動土。Google表示，該資料中心將透過最新技術為台灣等亞洲網路用戶提供服務，而台灣也成為 Google的重要據點。

明日動土典禮在彰濱工業園區舉行，Google亞太區總裁Daniel Alegre和Google台灣董事總經理簡立峰將與政府部會首長，共同揭示該資料中心最新發展與計畫，並分享Google在台深耕計畫與重要里程。

而外電也報導Google本週可望正式宣布推出雲端儲存Google Drive服務。法人表示，相關雲端概念股可望成為本週股市亮點。

Google去年9月份宣布在新加坡、香港及台灣成立大型資料中心。其中台灣的資料中心將斥資一億美元，並且已經在彰濱工業園區購地15公頃。

法人表示，Google在全球各地興建大型資料中心，有助於台灣相關上游供應商的出貨。目前台灣的伺服器廠商及磁碟陣列業者，為Google資料中心的供應商，包括伺服器硬體產品為主的廣達、神達、緯創、英業達、鴻海等。

因應資料中心龐大的儲存空間需求，磁碟陣列業者也是值得關注的族群，包括，喬鼎、普安、世仰等，也都是Google資料中心的上游供應商。Google今年在亞太區的三大資料中心陸續動工興建，並在明年啟用，法人表示，上游業者的出貨可以被期待。

除了在全球各地興建資料中心外，外電則是報導，繼蘋果推出雲端服務iCloud之後，Google本週也會推出雲端儲存Google Drive的服務，外電報導Google將提供消費者5GB的網路免費儲存空間。

可以預見，Google、蘋果等國際大廠力推雲端服務，未來對於資料中心的需求量也會愈來愈大。對台灣上游相關供應鏈來說，包括伺服器、磁碟陣列、以及網通、機構件等需求也會愈來愈多。法人表示，雖然近期台股有不確定的政策因素，但雲端概念股長期來看是值得逢低布局的族群。

一個值得學習的觀念臺灣菸酒總經理林讚峰

2012-03-29T09:09:00.003+08:00

臺灣菸酒總經理林讚峰：CEO也要逼自己學IT

文/辜雅蕾 2012-03-28

臺灣菸酒從2009年開始斥資2億元在全臺上百據點導入SAP ERP，這個專案就是由臺灣菸酒總經理林讚峰所提議，而他認為，「導入ERP對臺灣菸酒最大的幫助是提高銷售端資料的透明度，以及管理銷售據點。」

公司小檔案
●企業名稱：台灣菸酒股份有限公司
●成立時間：1901年
營收規模/資本額： 644.36億元／350億元（2011年）
●員工人數：6,828人
●IT部門人數：88人（總部28人，分支機構60人）
●每年IT預算：近3年平均約1.6億元

一個CIO往往將資訊系統看做生產流程改善的工具，但對一個CEO來說，資訊系統要能解決的，應該是企業最核心的問題，這些問題往往都跟銷售或是業務有關。

臺灣菸酒從2009年開始斥資2億元在全臺上百據點導入SAP ERP，這個專案就是由臺灣菸酒總經理林讚峰所提議，而他認為，「導入ERP對臺灣菸酒最大的幫助是提高銷售端資料的透明度，以及管理銷售據點。」

這並不意味臺灣菸酒不在意生產端的管理，林讚峰表示，相對銷售端，臺灣菸酒生產端的流程單純許多，對資料和數據需求的急迫性也沒有銷售端來的高，除此之外，林讚峰對於臺灣菸酒所生產出來的產品有很高的信心，但，「現在這個時代，不是產品做得好就好，重要的是，要怎麼賣。」

這個觀念對臺灣菸酒來說，其實是很大的轉變。你很難想像，20年前，在臺灣菸酒還是臺灣省菸酒公賣局時，一個酒廠或是菸廠的廠長，必須具有公務人員簡任官職等，相當於地方政府最高職等的事務官位階，權力以及影響力可見一斑。不難想見，過去生產單位在臺灣菸酒是如何受到重視。不過，隨著臺灣菸酒公賣局改制成為臺灣菸酒公司，情況開始有所轉變，銷售端的重要性也與日俱增。

在CEO眼中，導入ERP的最終目的是幫助銷售，不是生產
臺灣菸酒有很複雜的通路體系，從大賣場、零售商、海產店、夜店等，都是通路商。過去，臺灣菸酒在全臺各地都設有營業所，再由這些營業所配銷產品給銷售據點，累積至今，臺灣菸酒現在總共擁有4萬多個銷售商。

這些為數甚多的銷售商，過去都由各個營業所負責管理，各自業務管理上的資料格式、表單設計和工作流程，通通都不一樣，因此也難以彙整，換句話說，總部想要掌握即時資訊根本是不可能的事情。

臺灣菸酒公司化以後，經營心態也跟著公司化。「導入ERP就是要增強我們的戰鬥力。」林讚峰認為，導入ERP的第一步就是要先統一資料，才能有即時反應的能力。

林讚峰說了一件很有意思的例子，啤酒的重量重、利潤低，再加上有產品品質責任歸屬的考量，北部廠生產的酒不可以到北部以外的地方販售，中部、南部廠所生產的酒也是如此。因此，各地酒廠就負責生產當地所需要的產品數量，過往，臺灣菸酒都是根據歷史資料來推估各廠生產數量。

不過，啤酒需要量其實跟氣溫有很大的關係。所以像是臺灣頭與臺灣尾，冬天啤酒的銷量可以差到3倍之多，就是受到氣溫的影響，導致臺中以北的人在冬天喝啤酒的量會大幅減少，因此不同的酒廠，在冬天的忙碌程度也不一樣。

麻煩的是，氣溫年年都會變化，林讚峰表示，用歷史資料來推估總會有誤差，導致每座工廠來不及因應市場的銷售。比如說，今年南部冬天的氣溫特別低，若只依照過往資料來生產，就造成生產過剩的問題。「這都是因為沒有辦法收集最新市場端的即時資訊，並依據正確資料反應。」

因此，林讚峰希望臺灣菸酒對銷售端資料的反應速度，「要做到像7-11的反應一樣，產品一賣完，補貨就到，不能有時間差。」這些，林讚峰都打算靠ERP來完成。

用資訊系統來跟其他世界大廠競爭
臺灣菸酒不是第一個導ERP的國營事業導，論規模，也不是最大的，可是，臺灣菸酒的業務性質肯定是最複雜，不僅跨越生產銷售，更重要的是，不同於其他國營事業通常經營的是獨占事業，「臺灣菸酒不僅要面對眾多競爭者，而且，競爭者是來自世界各地的廠商。」林讚峰說。

談到與世界競爭，林讚峰倒是很感慨，因為臺灣的菸廠中有三座，除了生產臺灣菸酒自營商品之外，還分別各自代工日本、英國、美國知名品牌菸廠的菸，令他吃驚的是，這三個不同國家菸廠資訊流的相似度，比臺灣自己三座菸廠的同質性還高。林讚峰認為，這是因為國際菸廠藉由資訊系統建立了標準化的流程。「所以，國際菸廠在全世界都可以清楚掌握當地市場對菸價的反應，並且隨時依銷售數據調整售價，跟他們一比，難怪我們的市占率年年下滑。」

對林讚峰來說，市占率下滑是事實，但國際廠商藉由資訊系統提供正確即時數據來協助企業營運決策的能力，讓他了解資訊系統對企業營運的重要性，也讓他在經營管理的路上特別重視資訊系統。

聽林讚峰談資訊系統，一時之間你會以為自己是跟一位從CIO升任CEO的人聊天，但是，林讚峰擁有的是美國麻省理工學院生化工程博士的學位，更是個紅?專家，一路求學就業之路，沒有任何IT的背景。

「我要逼別人，得先逼自己」林讚峰說。在這個轉型中的國營單位要推動資訊化改革，其中的難度外人很難想像，身為總經理的他，如果想輕鬆點，大可以把事情全交辦下去即可，可是，他把自己定位為「全方位問題解決者。」有問題，他一定跳下去解決，「我一定要跳下去跟大家玩一玩。」因為，這種跨部門的專案若是沒有總經理的角色跳下來玩一玩，肯定就無法順利推動。

很難，但還是很積極的學。這就是一個想要以資訊系統改造企業的CEO，所具有的態度。文⊙辜雅蕾

Internet Small Computer System Interface (iSCSI)

2012-03-27T15:54:00.001+08:00

In computing, iSCSI (ⁱ/aɪˈskʌzi/ eye-skuz-ee), is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities. By carrying SCSI commands over IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers. It is a Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.

Functionality

iSCSI uses TCP/IP (typically TCP ports 860 and 3260). In essence, iSCSI simply allows two hosts to negotiate and then exchange SCSI commands using IP networks. By doing this iSCSI takes a popular high-performance local storage bus and emulates it over wide-area networks, creating a storage area network (SAN). Unlike some SAN protocols, iSCSI requires no dedicated cabling; it can be run over existing switching and IP infrastructure. As a result, iSCSI is often seen as a low-cost alternative to Fibre Channel, which requires dedicated infrastructure except in its FCoE (Fibre Channel over Ethernet) form. However, the performance of an iSCSI SAN deployment can be severely degraded if not operated on a dedicated network or subnet (LAN or VLAN).

Although iSCSI can communicate with arbitrary types of SCSI devices, system administrators almost always use it to allow server computers (such as database servers) to access disk volumes on storage arrays. iSCSI SANs often have one of two objectives:

Storage consolidation: Organizations move disparate storage resources from servers around their network to central locations, often in data centers; this allows for more efficiency in the allocation of storage. In a SAN environment, a server can be allocated a new disk volume without any change to hardware or cabling.

Disaster recovery: Organizations mirror storage resources from one data center to a remote data center, which can serve as a hot standby in the event of a prolonged outage. In particular, iSCSI SANs allow entire disk arrays to be migrated across a WAN with minimal configuration changes, in effect making storage "routable" in the same manner as network traffic.

[edit]Network booting

For general data storage on an already-booted computer, any type of generic network interface may be used to access iSCSI devices. However, a generic consumer-grade network interface is not able to boot a diskless computer from a remote iSCSI data source. Instead it is commonplace for a server to load its initial operating system from a TFTP server or local boot device, and then use iSCSI for data storage once booting from the local device has finished.

A separate DHCP server may be configured to assist interfaces equipped with network boot capability to be able to boot over iSCSI. In this case the network interface looks for a DHCP server offering a PXE or bootp boot image. This is used to kick off the iSCSI remote boot process, using the booting network interface's MAC address to direct the computer to the correct iSCSI boot target.

Most Intel Ethernet controllers for servers support iSCSI boot. ^[1]

Network switch 網路交換器的功能種類

2012-03-27T15:11:00.003+08:00

Network switch

From Wikipedia, the free encyclopedia

50 port network switch

A network switch or switching hub is a computer networking device that connects network segments or network devices. The term commonly refers to a multi-port network bridge that processes and routes data at the data link layer (layer 2) of the OSI model. Switches that additionally process data at thenetwork layer (layer 3) and above are often referred to as layer-3 switches or multilayer switches.

The first Ethernet switch was introduced by Kalpana in 1990.^[1]

A switch is a telecommunication device which receives a message from any device connected to it and then transmits the message only to that device for which the message was meant. This makes the switch a more intelligent device than hub (which receives a message and then transmits it to all the other devices on its network.) The network switch plays an integral part in most modern Ethernet local area networks (LANs). Mid-to-large sized LANs contain a number of linked managed switches. Small office/home office (SOHO) applications typically use a single switch, or an all-purposeconverged device such as a residential gateway to access small office/home broadband services such as DSL or cable internet. In most of these cases, the end-user device contains a router and components that interface to the particular physical broadband technology. User devices may also include a telephone interface for VoIP.[edit]Function

An Ethernet switch operates at the data link layer of the OSI model to create a separate collision domain for each switch port. With 4 computers (e.g., A, B, C, and D) on 4 switch ports, A and B can transfer data back and forth, while C and D also do so simultaneously, and the two conversations will not interfere with one another. In the case of a hub, they would all share the bandwidth and run inhalf duplex, resulting in collisions, which would then necessitate retransmissions. Using a switch is called microsegmentation. This allows computers to have dedicated bandwidth on a point-to-point connections to the network and to therefore run in full duplex without collisions.

[edit]Role of switches in networks

Switches may operate at one or more layers of the OSI model, including data link and network. A device that operates simultaneously at more than one of these layers is known as a multilayer switch.

In switches intended for commercial use, built-in or modular interfaces make it possible to connect different types of networks, including Ethernet, Fibre Channel, ATM, ITU-T G.hn and 802.11. This connectivity can be at any of the layers mentioned. While layer-2 functionality is adequate for bandwidth-shifting within one technology, interconnecting technologies such as Ethernet and token ring is easier at layer 3.

Devices that interconnect at layer 3 are traditionally called routers, so layer-3 switches can also be regarded as (relatively primitive) routers.

In some service provider and other environments where there is a need for a great deal of analysis of network performance and security, switches may be connected between WAN routers as places for analytic modules. Some vendors provide firewall,^[2]^[3] network intrusion detection,^[4] and performance analysis modules that can plug into switch ports. Some of these functions may be on combined modules.^[5]

In other cases, the switch is used to create a mirror image of data that can go to an external device. Since most switch port mirroring provides only one mirrored stream, network hubs can be useful for fanning out data to several read-only analyzers, such as intrusion detection systems and packet sniffers.

[edit]Layer-specific functionality

Main article: Multilayer switch

A modular network switch with three network modules (a total of 24 Ethernet and 14 Fast Ethernet ports) and one power supply.

While switches may learn about topologies at many layers, and forward at one or more layers, they do tend to have common features. Other than for high-performance applications, modern commercial switches use primarily Ethernet interfaces.

At any layer, a modern switch may implement power over Ethernet (PoE), which avoids the need for attached devices, such as a VoIP phone or wireless access point, to have a separate power supply. Since switches can have redundant power circuits connected to uninterruptible power supplies, the connected device can continue operating even when regular office power fails.

[edit]Layer 1 hubs versus higher-layer switches

A network hub, or repeater, is a simple network device. Hubs do not manage any of the traffic that comes through them. Any packet entering a port is broadcast out or "repeated" on every other port, except for the port of entry. Since every packet is repeated on every other port, packet collisions affect the entire network, limiting its capacity.

There are specialized applications where a hub can be useful, such as copying traffic to multiple network sensors. High end switches have a feature which does the same thing called port mirroring.

By the early 2000s, there was little price difference between a hub and a low-end switch.^[6]

[edit]Layer 2

A network bridge, operating at the data link layer, may interconnect a small number of devices in a home or the office. This is a trivial case of bridging, in which the bridge learns the MAC address of each connected device.

Single bridges also can provide extremely high performance in specialized applications such as storage area networks.

Classic bridges may also interconnect using a spanning tree protocol that disables links so that the resulting local area network is a tree without loops. In contrast to routers, spanning tree bridges must have topologies with only one active path between two points. The older IEEE 802.1D spanning tree protocol could be quite slow, with forwarding stopping for 30 seconds while the spanning tree would reconverge. A Rapid Spanning Tree Protocol was introduced as IEEE 802.1w, but the newest edition of IEEE 802.1D adopts the 802.1w extensions as the base standard.

The IETF is specifying the TRILL protocol, which is the application of link-state routing technology to the layer-2 bridging problem. Devices which implement TRILL, called RBridges, combine the best features of both routers and bridges.

While layer 2 switch remains more of a marketing term than a technical term,^{[citation needed]} the products that were introduced as "switches" tended to use microsegmentation and Full duplex to prevent collisions among devices connected to Ethernet. By using an internal forwarding plane much faster than any interface, they give the impression of simultaneous paths among multiple devices.

Once a bridge learns the topology through a spanning tree protocol, it forwards data link layer frames using a layer 2 forwarding method. There are four forwarding methods a bridge can use, of which the second through fourth method were performance-increasing methods when used on "switch" products with the same input and output port bandwidths:

Store and forward: The switch buffers and verifies each frame before forwarding it.
Cut through: The switch reads only up to the frame's hardware address before starting to forward it. Cut-through switches have to fall back to store and forward if the outgoing port is busy at the time the packet arrives. There is no error checking with this method.
Fragment free: A method that attempts to retain the benefits of both store and forward and cut through. Fragment free checks the first 64 bytes of the frame, where addressing information is stored. According to Ethernet specifications, collisions should be detected during the first 64 bytes of the frame, so frames that are in error because of a collision will not be forwarded. This way the frame will always reach its intended destination. Error checking of the actual data in the packet is left for the end device.
Adaptive switching: A method of automatically selecting between the other three modes.

While there are specialized applications, such as storage area networks, where the input and output interfaces are the same bandwidth, this is not always the case in general LAN applications. In LANs, a switch used for end user access typically concentrates lower bandwidth and uplinks into a higher bandwidth.

[edit]Layer 3

Within the confines of the Ethernet physical layer, a layer-3 switch can perform some or all of the functions normally performed by a router. The most common layer-3 capability is awareness of IP multicast through IGMP snooping. With this awareness, a layer-3 switch can increase efficiency by delivering the traffic of a multicast group only to ports where the attached device has signaled that it wants to listen to that group.

[edit]Layer 4

While the exact meaning of the term layer-4 switch is vendor-dependent, it almost always starts with a capability for network address translation, but then adds some type of load distribution based onTCP sessions.^[7]

The device may include a stateful firewall, a VPN concentrator, or be an IPSec security gateway.

[edit]Layer 7

Layer-7 switches may distribute loads based on Uniform Resource Locator URL or by some installation-specific technique to recognize application-level transactions. A layer-7 switch may include aweb cache and participate in a content delivery network.^[8]

Layer 7 Switching & Load Balancing 第七層網路交換器與負載平衡器

2012-03-27T15:05:00.000+08:00

From F5

https://devcentral.f5.com/weblogs/macvittie/archive/2008/08/12/3529.aspx

Layer 7 Switching + Load Balancing = Layer 7 Load Balancing

posted on Tuesday, August 12, 2008 4:44 AM

Modern load balancers (application delivery controllers) blend traditional load-balancing capabilities with advanced, application aware layer 7 switching to support the design of a highly scalable, optimized application delivery network. Here's the difference between the two technologies, and the benefits of combining the two into a single application delivery controller.

LOAD BALANCING

Load balancing is the process of balancing load (application requests) across a number of servers. The load balancer presents to the outside world a "virtual server" that accepts requests on behalf of a pool (also called a cluster or farm) of servers and distributes those requests across all servers based on a load-balancing algorithm. All servers in the pool must contain the same content.

Load balancers generally use one of several industry standard algorithms to distribute request. Some of the most common standard load balancing algorithms are:

round-robin
weighted round-robin
least connections
weighted least connections

Load balancers are used to increase the capacity of a web site or application, ensure availability through failover capabilities, and to improve application performance.

LAYER 7 SWITCHING

Layer 7 switching takes its name from the OSI model, indicating that the device switches requests based on layer 7 (application) data. Layer 7 switching is also known as "request switching", "application switching", and "content based routing".

A layer 7 switch presents to the outside world a "virtual server" that accepts requests on behalf of a number of servers and distributes those requests based on policies that use application data to determine which server should service which request. This allows for the application infrastructure to be specifically tuned/optimized to serve specific types of content. For example, one server can be tuned to serve only images, another for execution of server-side scripting languages like PHP and ASP, and another for static content such as HTML , CSS , and JavaScript.

Unlike load balancing, layer 7 switching does not require that all servers in the pool (farm/cluster) have the same content. In fact, layer 7 switching expects that servers will have different content, thus the need to more deeply inspect requests before determining where they should be directed. Layer 7 switches are capable ofdirecting requests based on URI, host, HTTP headers, and anything in the application message.

The latter capability is what gives layer 7 switches the ability to perform content based routing for ESBs and XML/SOAP services.

LAYER 7 LOAD BALANCING

By combining load balancing with layer 7 switching, we arrive at layer 7 load balancing, a core capability of all modern load balancers (a.k.a. application delivery controllers).

Layer 7 load balancing combines the standard load balancing features of a load balancing to provide failover and improved capacity for specific types of content. This allows the architect to design an application delivery network that is highly optimized to serve specific types of content but is also highly available.

Layer 7 load balancing allows for additional features offered by application delivery controllers to be applied based on content type, which further improves performance by executing only those policies that are applicable to the content. For example, data security in the form of data scrubbing is likely not necessary on JPG or GIF images, so it need only be applied to HTML and PHP.

Layer 7 load balancing also allows for increased efficiency of the application infrastructure. For example, only two highly tuned image servers may be required to meet application performance and user concurrency needs, while three or four optimized servers may be necessary to meet the same requirements for PHP or ASP scripting services. Being able to separate out content based on type, URI, or data allows for better allocation of physical resources in the application infrastructure.

How Does Layer 7 Load Balancing Work?第七層網路交換器如何運作??

This post explains what is meant by layer 7 load balancing and an example of content switching using HTTP URL parsing is given later in the post. In the OSI model layer 7 is the applications layer and there are a number of application protocoals that are used this layer:

Hypertext Transport Protocol (HTTP) for web pages
File Transport Protocol (FTP) for file transfer
Real Time Streaming Protocol (RTSP) for streaming media such as video

A load balancing switch can be used at layer 7 to load balance in a number of different ways. These include:

HTTP header Inspection
HTTP URL Parsing
RTSP Parsing

One of the main reasons why layer 7 load balancing is used is that our company will want to ensure that differ web applications run on servers that are configured and set up to maximise the efficiency of those servers and also to minimise the cost in acquiring and running the servers.

Suppose that we are a web hosting company like Hostgator or Bluehost and we need to host many different types of website. These would include websites with just static pages, online shops with backend transaction processing, and even websites like youtube that are dedicated to providing video streaming to the world. If we did not load balance the incoming requests from the web based on content type (or application type) then we would have to make sure that all of the servers we use were of the same technical specification and capable of handling our most complex applications. This would be expensive and our finanical director would have constant headaches while us techies could gloat to our friends about all the massive servers we had. Our friends in turn would have data center envy :-). They would then give their financial director a headache from the constant requests to get bigger servers so they could gloat at us - and so on.

In reality what we would do is something like the following. First we would decide that we needed three different types of server, one for each application type:

a low spec server configured to run static websites
a higher spec server configured to run the online shops
an even higher spec server configured for video streaming

Then we would place a content switch in front of the three different types of servers/applications. And we would configure the content switch to send the different types of request to the different types of servers. Easy really!

HTTP URL Parsing

Lets say that on our smaller servers we only run static websites that consit mainly of html web pages and gig or jpeg images. On our medium sized servers we run complex shopping sites that use applications servers and datbase servers and so on. These are more dynamic websites and need to handle a high volume of transactions day and night (24/7).

Our content switch will need to insect incoming requests and make sure to send them to the right set of servers. It can do this by looking at the file extensions in the url. Extensions like html, gif and jpeg can go to the static website servers and the more complex (such as ASP or Java) can go to the dynamic servers.

What is Jenkins? autobuild/autotest

2012-03-27T09:34:00.000+08:00

What is Jenkins?

Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:

Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.

Features

Jenkins offers the following features:

Easy installation: Just java -jar jenkins.war, or deploy it in a servlet container. No additional install, no database.
Easy configuration: Jenkins can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help. There's no need to tweak XML manually anymore, although if you'd like to do so, you can do that, too.
Change set support: Jenkins can generate a list of changes made into the build from Subversion/CVS. This is also done in a fairly efficient fashion, to reduce the load on the repository.
Permanent links: Jenkins gives you clean readable URLs for most of its pages, including some permalinks like "latest build"/"latest successful build", so that they can be easily linked from elsewhere.
RSS/E-mail/IM Integration: Monitor build results by RSS or e-mail to get real-time notifications on failures.
After-the-fact tagging: Builds can be tagged long after builds are completed
JUnit/TestNG test reporting: JUnit test reports can be tabulated, summarized, and displayed with history information, such as when it started breaking, etc. History trend is plotted into a graph.
Distributed builds: Jenkins can distribute build/test loads to multiple computers. This lets you get the most out of those idle workstations sitting beneath developers' desks.
File fingerprinting: Jenkins can keep track of which build produced which jars, and which build is using which version of jars, and so on. This works even for jars that are produced outside Jenkins, and is ideal for projects to track dependency.
Plugin Support: Jenkins can be extended via 3rd party plugins. You can write plugins to make Jenkins support tools/processes that your team uses.

房仲：房貸低申貸前先試算

2012-03-27T08:52:00.001+08:00

房仲：房貸低申貸前先試算

-字
+字

中央社 – 2012年3月26日下午6:02

（中央社記者韋樞台北26日電）根據央行統計顯示，從五大銀行新承做購屋貸款利率已連續37個月跌破2%，相對有利低價區的首購民眾。房仲表示，一旦經濟重回復甦，利率可能再升，購屋人最好申貸前先試算。

為加速經濟擺脫金融海嘯的威脅，各國大舉實施寬鬆政策，除了直接將資金注入市場外，也將利率下調至罕見的低利水準。央行統計，從2009年2月五大銀行新承做購屋貸款利率跌破2%以來，已連續37個月低於2%。

信義房屋表示，央行五大銀行(台銀、合庫銀、土銀、華銀及一銀)新承做放款金額與利率統計顯示，新承做購屋貸款利率從最低的1.616%，已逐步調升至1.899%。

以2008年9月新承做購屋貸款2.859%試算，貸款新台幣500萬元，20年期推算，每月本息平均攤還2萬7378元；以最新的1.899%試算，每月本息平均攤還金額為2萬5056元，一年便可節省近2.8萬元。

信義房屋不動產企研室經理蘇啟榮指出，低利率有助大台北以外的房市，以整體房價水準來看，桃園的平均房價水準是新北市的一半，為台北市的1/4，其他都會區房價水準與桃園相似。在奢侈稅上路後，大台北以外的區域受影響相對有限，就是因為就業環境穩定，房價相對平穩，與低利率等條件。

信義房屋南崁忠孝店店長黃范銘指出，大台北地區與桃園房價相差甚多，台北客選擇到南崁地區購屋較偏好總價500萬元到800萬元的大樓產品；由於現在房貸利率相對低，且桃園地區房價不貴，一般住宅產品貸款金額並不會太高，經試算後，客戶普遍可以接受也負擔得起。

蘇啟榮認為，一旦國際金融情勢好轉，加上經濟回復成長，寬鬆貨幣政策可能趨緊，利率的確有可能反轉向上，建議購屋人最好先試算一旦利率走揚，每月會增加多少房貸金額支出。1010326

中南部找房賺更大

2012-03-27T08:51:00.002+08:00

當包租公中南部找房賺更大

-字
+字

作者：記者黃惠聆╱台北報導 | 中時電子報 – 2012年3月26日上午5:30

工商時報【記者黃惠聆╱台北報導】

房仲業統計，近一年北市和新北市租金漲幅比不上房價上漲率，北市、新北市各地區租金投資報酬率明顯下滑，多數地區租金年報酬率已掉到2％左右，但中南部的租金報酬率仍高，甚至可達10％，想當包租公者可往中南部尋找合適房。

現代人想買房當包租公理財前，要慎選地方，住商不動產企劃研究室主任徐佳馨表示，北市、新北市過去一段時間房價漲幅驚人，但租金上漲幅度有限，使北市、新北市租金投資報酬率近2年持續走低。

徐佳馨說，買房當包租公且要有高報酬率，要有二個要件：1是低購房成本，2是高出租率。因為即使買到低價房，房子租不出去或出租率低，也沒有租金投報率可言。

想置產當包租公，房仲業建議，可往中南部找房，如中南部或者知名大學附近。

永慶不動產南區業務副總經理楊政曉表示，想要到中南部購屋當包租公的民眾，選擇標的很重要，就目前來看，小套房的投報率最高，約70~80萬元就可以買到，每個月租金約4,000元，其中又以新成屋效果最佳。

中南部租金投報率高，但純住宅的二手屋多，如標的不恰當，有時可能賺了租金卻賠了總價。像高雄地區空地不少，舊大樓增值空間相對有限，且在地人買房比較偏愛透天厝，就算房價不漲，仍有土地增值空間可期。

楊政曉，在大學附近買房當包租公，雖然投報率不錯，還要考慮到維修費，一般來說，學生宿生維護費用相對較高，若是外地人還是得委託物價公司管理，須支出管理費。

總之，到南部買房當包租公須留意房價不能過高，每坪1字頭以下比較沒有投資風險，但若超過16~17萬元，投資風險就會逐漸加大。

How to connect an JBOD-System

2012-03-22T11:06:00.001+08:00

Your master system need to have external SAS ports
http://support.exustechnology.com/entries/20650337-how-to-connect-an-jbod-system-to-qstor-qmx

[中時電子報]英業達伺服器營收挑戰千億

2012-03-16T08:58:00.002+08:00

英業達伺服器營收挑戰千億

-字
+字

作者：記者楊玟欣╱台北報導 | 中時電子報 – 2012年3月15日上午5:30

工商時報【記者楊玟欣╱台北報導】

雲端運算商機興起，社群網站資料中心布建需求大增，惠普、戴爾伺服器出貨量成長，帶動主要代工廠英業達伺服器產品增溫。英業達董事長李詩欽昨（14）日表示，去年英業達伺服器業務年增率3成，今年產值成長縮小，但目標挑戰千億元。

李詩欽指出，原本市場預期，第1季總體經濟不佳，同時又有硬碟缺料衝擊，保守看待伺服器市況，不過，第1季伺服器產業優於預期，表現與去年第4季持平，年增率則平均有2成左右的成長率。

李詩欽指出，英業達今年伺服器出貨量仍會有明顯的成長，但成長主力在於伺服器主機板，由於主板單價比整機系統低，預期今年伺服器產值成長幅度較受限。根據了解，系統平均單價約1,100~1,200美元，主機板平均單價則僅約一半，約在500~600美元左右。

英業達伺服器最大客戶是惠普，其次則是戴爾。有別於廣達、緯創直接跳過品牌伺服器廠商，直接出貨給社群網站業者，以白牌伺服器方式進攻雲端商機；英業達則因伺服器代工金額龐大，為尊重客戶，仍是以代工模式進軍雲端。此外，李詩欽指出，維持代工模式同時也是考量到若直接面對終端客戶，恐無法完整提供後續維護、升級的服務。

李詩欽指出，社群網站現在多傾向自行開發自有的資料中心，因此有別於以往向伺服器品牌直接訂購整機系統，而是改成訂購主機板，再依自身的需求量身打造資料中心，帶動英業達伺服器主機板的出貨量明顯成長。

李詩欽指出，為因應市場需求變化，英業達也改變以往較不接主機板訂單的模式，今年主機板出貨量成長率將大於伺服器系統出貨，看好伺服器業務出貨量成長，但產值成長則相對有限。

Thomasspace

PCI card dimensions

storage concept

網路文件共享系統(CIFS)

網路文件共享系統(CIFS) 2009/03/04-鐘聖雄

Server Message Block

History

Implementation

Client-server approach

Samba

Performance issues

NetBIOS

WAN performance issues

Microsoft's modifications

Opportunistic locking

Batch Locks

Exclusive Locks

Level 2 OpLocks

Breaks

SMB2

SMB 2.1

SMB 3.0

Features

Security

Specifications for SMB and SMB2 Protocols

Why IBM Turned Off Siri and Dropbox

http://www.informationweek.com/byte/news/radio/personal-tech/240000962

Why IBM Turned Off Siri (and Dropbox and Lots Of Other Things)

MORE INSIGHTS

Webcasts

White Papers

Reports

祖克柏

Intel® Advanced Encryption Standard (AES)

Intel® Advanced Encryption Standard (AES) Instructions Set - Rev 3

Introduction

Unified Storage

unified storage (network unified storage or NUS)

Citrix Buys Virtual Computer

Citrix Announces XenClient Enterprise and Acquisition of Virtual Computer

New Offering Combines Power of XenClient Hypervisor with Enterprise-Class Management of Virtual Computer

CDN content delivery network

bring your own device (BYOD) phenomenon

Will BYOD revive the network-access control idea? Gartner thinks it will

First integrated NAC/mobile-device management products announced; Gartner says expect others to follow

HP Converged Cloud and HP Public Cloud: Details Confirmed by Joe Panettieri on 4.10.12

英特爾：2015年將是Scale-out儲存的天下 文/鄭逸寧 2012-05-01

IDC：2011年臺灣伺服器市場成長2成 文/鄭逸寧 2012-04-24

AMD伺服器平臺處理器 文/林柏凱

Dell併Wyse Wyse在臺市占超過4成

Google彰濱工業園區30億元台幣資料中心4月3日動土

Google資料中心 明動土

一個值得學習的觀念 臺灣菸酒總經理林讚峰

Internet Small Computer System Interface (iSCSI)

Functionality

[edit]Network booting

Network switch 網路交換器的功能種類

Network switch

[edit]Role of switches in networks

[edit]Layer-specific functionality

[edit]Layer 1 hubs versus higher-layer switches

[edit]Layer 2

[edit]Layer 3

[edit]Layer 4

[edit]Layer 7

Layer 7 Switching & Load Balancing 第七層網路交換器與負載平衡器

From F5

Layer 7 Switching + Load Balancing = Layer 7 Load Balancing

How Does Layer 7 Load Balancing Work?第七層網路交換器如何運作??

HTTP URL Parsing

What is Jenkins? autobuild/autotest

What is Jenkins?

Features

房仲：房貸低 申貸前先試算

房仲：房貸低 申貸前先試算

中南部找房賺更大

當包租公 中南部找房賺更大

How to connect an JBOD-System

[中時電子報]英業達 伺服器營收挑戰千億

英業達 伺服器營收挑戰千億

網路文件共享系統(CIFS)
2009/03/04-鐘聖雄

英特爾：2015年將是Scale-out儲存的天下文/鄭逸寧 2012-05-01

IDC：2011年臺灣伺服器市場成長2成文/鄭逸寧 2012-04-24

AMD伺服器平臺處理器文/林柏凱

Google資料中心明動土

一個值得學習的觀念臺灣菸酒總經理林讚峰

房仲：房貸低申貸前先試算

房仲：房貸低申貸前先試算

當包租公中南部找房賺更大

[中時電子報]英業達伺服器營收挑戰千億

英業達伺服器營收挑戰千億