為什麼選擇我們的解決方案呢?
整體規劃能力>
我們協助客戶於整個測試計畫中,從研發測試到測試中新的建構以及工廠測試皆能提共相關的解決方案!
更具競爭力的價格>
為了協助客戶建置更符合預算的測試,我們為客戶爭取更好的價格為彼此創造雙贏!
|
|
| |
|
 |
Domain Name System (DNS) is an Internet directory service that translates domain names into IP addresses.
Prior to the advent of DNS (when the Internet was still ARPAnet), each host on the network periodically retrieved a HOSTS.TXT file from SRI Inc. (now SRI International) which contained the mappings of host names to IP addresses for every host on the network. While adequate for a small network, the main drawback to this system was that whenever a host's address changed, the HOSTS file on every other host had to be updated. Also, it was not very scalable; as the network grew, the HOSTS.TXT file would eventually become very large, taking a long time to process.
DNS uses a different approach: a host's name-to-address mapping is recorded in one only place, and a notification system informs hosts about changes to address mappings.
DNS consists of a hierarchical set of DNS servers. For each domain or subdomain, there is one or more authoritative DNS servers that publish information about that domain and the name servers of any domains below it in the hierarchy. The hierarchy of authoritative DNS servers matches the hierarchy of domains. At the top of the hierarchy are the root servers, which are the servers that are queried when resolving a top-level domain name.
IxLoad DNS Client and Server
Creating a DNS Test
Configuring a DNS Server
Configuring a DNS Client
Sequence Generators
DNS Statistics
IxLoad DNS Client and Server
IxLoad 包括兩種作業模式進行 DNS connections測試: 單個 DNS client 及單個 DNS server. 你可以一起利用IxLoad DNS client 及 server 去測試一待測物(DUT's)的能力於 forward DNS requests 以及 responses, 或者你可以利用 IxLoad DNS client 去測試一 DNS server's 的 respond 到 DNS queries能力。
參閱DNS Client 及DNS Server.
DNS Client
IxLoad DNS client 為一個 DNS 解析器; 他可以產生詢問 (queries) 代表模擬的用戶們試圖去訪問一主機列表。 IxLoad DNS client 透過模擬的用戶們必須要獲得及轉發發出要求主機的IP位址。 你可以設定 IxLoad DNS client 去取得任何一個遞迴(recursive) 或是反覆的回應( iterative responses)。
要造成 IxLoad client 去產生一個詢問 (query), 你要設定一個命令給他。 命令是由詢問端的主機所組成包含詢問的主題(subject of the query)、詢問的種類 (query type), 以及 IP address 或 詢問的DNS伺服器的主機名。 你可以任意的設定文字列於其中當作 IxLoad DNS client 應該回應的回報值。
你可以選擇任一個 UDP 或 TCP 作為傳輸的通信協定 (Transport protocol) 來進行 DNS 詢問(queries)。假使你選擇 TCP, IxLoad DNS client 開啟一個新的connection 每一個詢問 (query)。 假使你選擇 UDP, 你可以設定 retransmissions的數量。
兩個元件都不支援逆向詢問。
DNS Server
IxLoad DNS server 模擬一個主要名稱伺服器(Name Server)。 具備可信賴的 domain. 你可以設定多個區域(zones) 給 IxLoad DNS Server. 針對每個區域(zone), 你可以設定一系列的來源紀錄來定義區域(series of resource records that define the zone) IxLoad DNS server 根據區域資源紀錄提供DNS詢問服務。
你可以從一個名稱區域設定檔案中(the Unix/Linux DNS service)匯入 (import)一區域設定 。
你可以執行多個 DNS Servers 於IXIA主機的任一個單 port上。 你可以設定這個埠為 IxLoad DNS server 監聽在(listens on)哪一個埠上。 (預設值為 53, 眾所周知的 DNS 預設埠).
兩個元件都不支援逆向詢問。
Creating a DNS Test
產生一 DNS 測試, 請參照使用手冊程序 Creating and Running an IxLoad Test 去產生一基本 IxLoad 測試設定, 然後點選到相對應的區塊。
|
產生一 DNS 測試步驟如下: |
- 假使IxLoad 尚未啟動請先啟動它。 Starting IxLoad.
- 針對 DNS activities 產生 NetTraffics Creating a NetTraffic.
- 產生一 DNS client Activity, 設定 client NetTraffic activity 為DNS client.
- 產生一 DNS server Activity, 設定 server NetTraffic activity 為DNS server.
- 放置 DUT 到這是環境中 Creating a DUT.
- 連線 DUT 到 NetTraffics. Connecting a NetTraffic to a DUT.
- 設定 client 或 server 作業方式(Activities):
- 設定 timeline 及 objectives 針對每個 NetTraffic (或每一個 Activity). Timeline and Objective.
- 選擇統計 (statistics) 你想要紀錄的資訊 Selecting Statistics.
- 選擇你要使用的PORT Port Assignments.
- 執行測試 Running a Test.
- 觀察圖形及測試結果 Viewing the Test Results.
|
注意: 假如目的地的client traffic 會是一 server Activity時, 你應該先行設定 server Activity. |
Configuring a DNS Server
|
設定DNS server, 設定相關控制在下列 tabs: |
Zone Config tab(區域設定)
Zone Config tab 列出 DNS server 要進行認證的區域。你可以開啟 Zone Manager 去匯入從其他名稱區域檔案 (the Unix/Linux DNS service) zone 的區域, 或者你可以使用建置的方式 (Zone Builder)去設定一個區域 (zone)。
Advanced Options tab(進階選項)
DNS server 進階選項 tab 包含一 command:
Listening Port: DNS server 在哪一個PORT上作為監聽 queries. 預設值 53, DNS的通用PORT。
Configuring a DNS Client
設定 DNS client, 設定相關控制在下列 tabs:
DNS Config tab
DNS Config tab 包含DNS client 命令列 (command list) 。 client 依照表列順序送出詢問 (queries (commands))。
|
新增一詢問(query): |
- 點選 Add 按鈕。
- IxLoad 增加一新的 row 到命列中。
- 設定詢問的參數(query parameters)。 請參照下列表格了解每個參數的敘述。
- 去更改命令列的順序, 選擇一個 query, 然後點選上下箭頭去移動這個命列於表中。欲刪除一個 command, 選擇他然後點選 Delete 按鈕。
- 當你完成了新增 queries 到命列表中後, 選擇一項設定 Repeat Command List 按鈕。 Repeat Command List 控制 client 於整個命令列中需要多久的時間完成單一測試。
- 假如 Repeat Command List 為 enabled, client 運作穿過整個命令列反覆經過直到運作時間屆滿。
- 假如 Repeat Command List 為 disabled, client 運作穿過整個命令列只有一次, 其他為 idle.
DNS Client Config tab 包下列參數。
Parameter |
Description |
Host Name |
All Query Types Except PTR and ENUM: 主機名稱針對名稱伺服器都必須要回應一個回覆。
注意: 根據 RFC 1034, 最大 host name 長度為 63 bytes. IxLoad 並不會堅持只在這個限度而已，而且允許你去產生比 63 bytes還要大的長度。
假如你的設定 DNS client 去送一 query 給 host name 大於 63 bytes長度時, DNS server 應該要回應一個 Format Error.
PTR Query Type: DNS server 必須回覆一個IP位置給host name.
ENUM Query Type: 電話號碼轉換到一 host name. 轉換過後, e164.arpa(這個zone分層授權去建立號碼對應的機制) 會附加到 host name. 號碼必須要包含國家和城市碼 (country and city codes), 並且不能包含非數位字元像是國際撥號字首 (+) 或連接字元 (-).
號碼可以是超過 64 數位長度。 你可以包含序列產生器 (sequence generators) 去產生多個特殊電話號碼。 序列產生器(sequence generators) 必須是只有單一數位寬度，舉例來說:
1 818 555 [0-9]234 為可允許
1 818 555 [00-99]34 為不可允許
請參考Sequence Generators, 取得如何使用sequence generators更多資訊 。 |
Query Type |
要被回覆的位址類型紀錄(Type of address record to be returned). 你可以定義下列詢問的種類:
1818555{0-9}{0-9}{0-9}{0-9}
(returned addresses)回覆的位置將會是:
00005558181
10005558181
20005558181
30005558181
諸如此類.
Sequence Generators(序列產生器)
Sequence generators 是能夠變量的機制，你可以利用他在某些區域下進行數量增加，並且IXLOAD會置換掉成你所產生的植在你進行測試時。例如: 你可以利用sequence generators 去造成 DNS client 產生多個登入query types. 每個欄位都會敘述你是否可以使用 sequence generators 於當下的欄位。
下列圖表清楚說明有哪些你可以使用sequence generators.
|
|
|
Sequence Generator |
Type |
Description |
[0 - 9] |
Numbers |
Creates a numeric range. |
[a - z], [A - Z] |
Letters |
Creates an alphabetic range. |
更完整說明請參閱 Using Automatic Sequence Generators. |
|
DNS Server |
DNS server 的IP 位置到那些 client 送的詢問 query. 假使 DNS server 監聽再有別於預設的 (53), 增加一個 (:) 在IP位址的右方然後會到指定的 port number. |
Recursion
|
Queries contain a bit called Recursion Desired (RD). 這個 bit 載明任一個requester 或 client 針對詢問想要遞迴的服務
Recursion 意指假如一個名稱伺服器接收詢問 (query) 它不能夠回答, 它可以轉發詢問到其他名稱伺服器去做網域解析。
Clients 可以從其他名稱伺服器要求 recursive 服務, 但是個別伺服器有可能不支援recursion.
- On: 設定 RD bit. 假如伺服器不能回答 query 但是支援 recursion功能時, 它可以轉發 query 到其他伺服器尋求解析。
- Off: 清除 RD bit. client 預期直接透過名稱伺服器回應。
請注意: IxLoad DNS Server 不支援 recursion. |
Expect |
String to be matched in the response from the DNS server.
non-ENUM queries: 針對所有的 queries 期望 ENUM queries, the string matched is the object of the query. 舉例, 針對 A 及 AAAA queries, 回覆的 IP Address 是配對好了的。針對 PTR queries, 回覆的 host name 是配對好的。 針對 MX queries, mailserver 是以經配好的。 針對 CNAME, 真實名稱配對好了。
ENUM queries: 針對 ENUM queries, 只有一 string 在 "SERVICES" 欄位中的 "Answer" 片段是配好的。 |
DNS Client Advanced Options tab
Advanced Options tab
Advanced Options tab 包含控制影響所有的DNS CLIENT詢問發行作業
Command |
Description |
Response Timeout |
時間的總量(在幾秒鐘內) 允許從伺服器收到回應。 |
Lower Layer Transport |
傳輸通信協定用來傳送 DNS queries. 假如你選擇的是 UDP, 指定 Retries 欄位時間數值 client 將會重傳一個 query. 假使client 應回應期間內未回應時會重送一個queries. |
Don't Wait for Response |
如果 enabled, client 再傳送下一個query前不會等待一個回應。
如果 disabled, client 在傳下一個之前會等待回應。
這項參數只會影響到當你設定 client's 目的種類(Objective Type)去詢問 (Queries/Second). 假如 objective 不是 Queries/Second, 這個參數不會有任何影響。
還有, 這個參數影響整個測試期間模擬用戶產生的數量, 有一個相對應影響在目標值 (objective value)上或許會觸及到:
- Enabled: 少數的模擬用戶的產生, 即一較高的目標值(objective value (更多 Queries/Second)) 可能早就達到。
- Disabled: 更多模擬用戶的產生, 即一較低目標值 (objective value (fewer Queries/Second)) 可能早就達到。
注意: 如果你 enable這個參數的話, 統計的計算回覆, 像是Total Queries Successful 及 Total Queries Failed, 會是零 (zero)因為 client 再傳送完詢問以後不等待一個回覆。
|
IP Version Preferences |
假如你有混合 IPv4 及 IPv6 subnets 設定在 client network上的話, DNS client 這個欄位選擇順序將會使用 subnets.
- IPv4: client 只會使用從 IPv4 subnets 的 addresses 而已。
- IPv6: client 只會使用從 IPv6 subnets 的 addresses 而已。
- Both, IPv4 first: client 會使用從 IPv4 subnets 的 addresses 第一優先 , 然後假如它需要更多addresses 的話, 會使用從 IPv6 subnets 的 addresses
- Both, IPv6 first:client 會使用從 IPv6 subnets 的 addresses 第一優先 , 然後假如它需要更多addresses 的話, 會使用從 IPv4 subnets 的 addresses
|
Sequence Generators
Sequence generators 為一個可變機制你可以將它包含在某些欄位上, 當你執行一個測試時IXLOAD會將產生的數值替換上去。例如: 你可以使用 sequence generators 去造成 DNS client 來產生多個登入以多種query types. 每個欄位的敘述皆會只是你是否可以採用sequence generators 來進行輸入當下的欄位。
下列表格說明哪些 sequence generators 你可以應用的。
|
|
|
Sequence Generator |
Type |
Description |
[0 - 9] |
Numbers (數字) |
Creates a numeric range. |
[a - z], [A - Z] |
Letters (字串) |
Creates an alphabetic range. |
需要更完整的敘述你可以參照 Using Automatic Sequence Generators. |
DNS Statistics (統計資料)
DNS Client Statistics
下列表格描述 DNS client 統計資料.
|
|
Statistic |
Description |
General Statistics (一般統計資料) |
DNS Total Queries Sent |
Client傳送多少數量的queries |
DNS Total Queries Successful |
經過DNS queries 後有多少有效的回應數量被接收到 |
DNS Total Queries Retried |
經過DNS queries 後有多少需要最少一次被重送 |
DNS Total Queries Failed |
DNS queries 有多少數量失敗沒有回應 |
DNS Total Queries Failed (Format Error) |
有多少數量失敗是因為DNS SERVER無法解釋詢問的格式。
注意: 根據 RFC 1034, 最大的 host name length 為 63 bytes. IxLoad 不會侷限在這限制而已, 並且允許你產生 queries 針對 host names 大於 63 bytes.
假如你設定 DNS client 去傳送一query超過大於63 bytes 的host name, DNS server 回應一個 Format Error. |
DNS Total Queries Failed (Server Failure) |
有多少數量的DNS queries 失敗是因為 DNS server有錯誤。
注意:根據 RFC 1034, 最大的 host name length 為 63 bytes. IxLoad 不會侷限在這限制而已, 並且允許你產生 queries 針對 host names 大於 63 bytes.
假如你設定 DNS client 去傳送一 query 到 server zone 做為一資源紀錄包含一個 host name 超過 63 bytes, DNS server 回應一Server Failure. |
DNS Total Queries Failed (Name Error) |
有多少數量的DNS queries 失敗是因為 DNS name 不存在 |
DNS Total Queries Failed (Not Implemented) |
有多少數量的DNS queries 失敗是因為 DNS server 不支援DNS request |
DNS Total Queries Failed (Refused) |
有多少數量的DNS queries 失敗是因為 DNS server 拒絕要求 (refused the request) |
DNS Total Queries Failed (Other) |
有多少數量的DNS queries 失敗是因為不知道的原因
|
DNS Total Queries Failed (Timeout) |
有多少數量的DNS queries 失敗是因為限制時間內到了沒有回應 |
DNS Total Queries Failed (Aborted) |
中止DNS queries 的數量
|
A Record Statistics |
DNS (Type A) Queries Sent |
紀錄Type A queries 已傳的數量 |
DNS (Type A) Queries Successful With Match |
Type A queries 針對DNS client 接收預期應有的IP address 數量 |
DNS (Type A) Queries Successful Without Match |
A record queries 進行過後沒有錯誤但回應不包含預期的IP address 數量 |
DNS (Type A) Queries Failed |
A record queries 針對一無效的回應被接收，或無回應被接收的數量 |
AAAA Record Statistics |
DNS (Type AAAA) Queries Sent |
有多少的AAAA 紀錄的queries被傳送 |
DNS (Type AAAA) Queries Successful With Match |
有多少的AAAA 紀錄queries針對DNS client 接收到預期的IP address 數量 |
DNS (Type AAAA) Queries Successful Without Match |
AAAA record queries 進行過後沒有錯誤但回應不包含預期的IP address 數量 |
DNS (Type AAAA) Queries Failed |
AAAA record queries針對一無效的回應被接收，或無回應被接收的數量 |
CNAME Record Statistics |
DNS (Type CNAME) Queries Sent |
canonical name紀錄queries 送出的數量 |
DNS (Type CNAME) Queries Successful With Match |
canonical name record queries DNS server回覆預期的host name 數量 |
DNS (Type CNAME) Queries Successful Without Match |
canonical name record queries 進行過後沒有錯誤但回應不包含預期的host name 數量 |
DNS (Type CNAME) Queries Failed |
canonical name record queries 針對一無效的回應被接收，或無回應被接收的數量 |
MX Record Statistics |
DNS (Type MX) Queries Sent |
多少的mail exchange record queries 已送出 |
DNS (Type MX) Queries Successful With Match |
mail exchange record queries.回覆預期的mail server host name 數量 |
DNS (Type MX) Queries Successful Without Match |
mail exchange record queries 進行過後沒有錯誤但回應不包含預期的mail server host name 數量 |
DNS (Type MX) Queries Failed |
Number of mail exchange record queries 針對一無效的回應被接收，或無回應被接收的數量 |
PTR Record Statistics |
DNS (Type PTR) Queries Sent |
多少數量的 pointer record queries 已送出 |
DNS (Type PTR) Queries Successful With Match |
多少數量的 pointer record queries 針對 DNS client 接收到預期canonical host name 成為供應的 IP address. |
DNS (Type PTR) Queries Successful Without Match |
多少數量的 pointer record queries 進行工作正確的但是回應不包含預期的 canonical host name. |
DNS (Type PTR) Queries Failed |
多少數量的 pointer record queries 針對一無效的回應被接收，或無回應被接收的數量 |
NS Record Statistics |
DNS (Type NS) Queries Sent |
多少數量的 name server record queries 已送出 |
DNS (Type NS) Queries Successful With Match |
多少數量的 name server record queries 針對 DNS server 回覆 name server 預期供應了 domain. |
DNS (Type NS) Queries Successful Without Match |
多少數量的 name server record queries 進行工作正確的但是回應不包含預期的 name server. |
DNS (Type NS) Queries Failed |
多少數量的 name server record queries 針對一無效的回應被接收，或無回應被接收的數量 |
SOA Record Statistics |
DNS (Type SOA) Queries Sent |
多少的起始授權紀錄 queries 被送出. |
DNS (Type SOA) Queries Successful With Match |
多少數量的 Start of Authority record queries 針對 DNS client 接收到預期的 DNS server 所供應的 domain. |
DNS (Type SOA) Queries Successful Without Match |
多少數量的 Start of Authority record queries w進行工作正確的但是回應不包含預期的 DNS server名稱. |
NAPTR (ENUM) Query Statistics |
DNS (Type NAPTR) Queries Sent |
多少數量的 Naming Authority Pointer (ENUM) 紀錄queries已傳送. |
DNS (Type NAPTR) Queries Successful With Match |
多少數量的 Naming Authority Pointer (ENUM) queries 針對那些回應有包含對應到預期的欄位string |
DNS (Type NAPTR) Queries Successful Without Match |
Number of Naming Authority Pointer (ENUM) queries進行工作正確的但是回應不包含預期的對應欄位 a string |
DNS (Type NAPTR) Queries Failed |
多少數量的 Naming Authority Pointer (ENUM) queries 針對一無效的回應被接收，或無回應被接收的數量 |
Bytes Transmitted and Received Statistics |
DNS Total Bytes Transmitted |
所有DNS queries 傳送總共的 bytes, 包括重傳 queries. |
DNS Total Bytes Received |
所有DNS 回應的接收總共的bytes |
Test Objective Statistics |
DNS Bytes |
DNS bytes傳送的和接收的總數相加來的 |
DNS Throughput |
client 所接收的及傳送的 DNS bytes所相加的速率 |
DNS Transactions |
DNS 完成交易的總數
一 DNS 交易組成是由一個 query 及一個 response . |
DNS Transaction Rate |
這些CLIENT完成DNS 全部交易的速率 |
DNS Simulated Users |
多少的模擬用戶產生 DNS queries. |
DNS Server Statistics
.
|
|
Statistic |
Description |
General Statistics |
DNS Total Queries Received |
Total number of DNS queries received by the server. |
DNS Total Queries Responded Successfully |
Total number of DNS queries for which the server returned a valid response. |
DNS Total Queries Failed |
Total number of DNS queries which the server could not process for any reason. |
DNS Total Queries Failed (Format Error) |
Number of DNS queries which the server could not process because it could not parse the query format.
Note: According to RFC 1034, the maximum host name length is 63 bytes. IxLoad does not enforce this limit, and allows you to create queries for host names larger than 63 bytes.
If you configure the DNS client to send a query to a host name that is larger than 63 bytes, the DNS server responds with a Format Error. |
DNS Total Queries Failed (Server Failure) |
Number of DNS queries that failed due to an error on the server.
Note: According to RFC 1034, the maximum host name length is 63 bytes. IxLoad does not enforce this limit, and allows you to create Resource Records that include host names larger than 63 bytes.
If you configure the DNS client to send a query to server zone for a Resource Record that contains a host name that is larger than 63 bytes, the DNS server responds with a Server Failure. |
DNS Total Queries Failed (Name Error) |
Number of DNS queries that failed because the DNS name does not exist. |
DNS Total Queries Failed (Not Implemented) |
Number of DNS queries that failed because the name server does not support the DNS request. |
DNS Total Queries Failed (Refused) |
Number of DNS queries that failed because the server refused to serve the query. |
DNS Total Queries Failed (Other) |
Number of DNS queries that failed for unknown reasons. |
A Record Statistics |
DNS (Type A) Queries Received |
Number of A record queries received. |
DNS (Type A) Queries Responded Successfully |
Number of A record queries for which the DNS server returned a valid response. |
DNS (Type A) Queries Failed |
Number of A record queries that failed for any reason. |
CNAME Record Statistics |
DNS (Type CNAME) Queries Received |
Number of canonical name record queries received. |
DNS (Type CNAME) Queries Responded Successfully |
Number of canonical name record queries for which the DNS server returned a valid response. |
DNS (Type CNAME) Queries Failed |
Number of canonical name record queries that failed for any reason. |
MX Record Statistics |
DNS (Type MX) Queries Received |
Number of mail exchange record queries received. |
DNS (Type MX) Queries Responded Successfully |
Number of mail exchange record queries for which the DNS server returned a valid response. |
DNS (Type MX) Queries Failed |
Number of mail exchange record queries that failed for any reason. |
PTR Record Statistics |
DNS (Type PTR) Queries Received |
Number of pointer record queries received. |
DNS (Type PTR) Queries Responded Successfully |
Number of pointer record queries for which the DNS server returned a valid response. |
DNS (Type PTR) Queries Failed |
Number of pointer record queries that failed for any reason. |
NS Record Statistics |
DNS (Type NS) Queries Received |
Number of name server record queries received. |
DNS (Type NS) Queries Responded Successfully |
Number of name server record queries for which the DNS server returned a valid response. |
DNS (Type NS) Queries Failed |
Number of name server record queries that failed for any reason. |
SOA Record Statistics |
DNS (Type SOA) Queries Received |
Number of Start of Authority record queries received. |
DNS (Type SOA) Queries Responded Successfully |
Number of Start of Authority record queries for which the DNS server returned a valid response. |
DNS (Type SOA) Queries Failed |
Number of Start of Authority record queries that failed for any reason. |
Bytes Transmitted and Received Statistics |
DNS Total Bytes Transmitted |
Total bytes transmitted for all DNS queries, including re-tried queries. |
DNS Total Bytes Received |
Total bytes received for all DNS responses. |
DNS Total Bytes Transmitted and Received |
Combined total of bytes received in DNS queries and transmitted in DNS responses. |
|
| Copyright 2006 Linkwen Electronics, Inc.