CN109039818B - Method for testing stability of AOC link between TOR and node - Google Patents
Method for testing stability of AOC link between TOR and node Download PDFInfo
- Publication number
- CN109039818B CN109039818B CN201810896864.4A CN201810896864A CN109039818B CN 109039818 B CN109039818 B CN 109039818B CN 201810896864 A CN201810896864 A CN 201810896864A CN 109039818 B CN109039818 B CN 109039818B
- Authority
- CN
- China
- Prior art keywords
- node
- netperf
- tool
- vlan
- nodes
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 43
- 238000000034 method Methods 0.000 title claims abstract description 19
- 230000002457 bidirectional effect Effects 0.000 claims description 20
- 238000013461 design Methods 0.000 description 2
- 108091064702 1 family Proteins 0.000 description 1
- 241000109849 Leopardus jacobita Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a method for testing the stability of an AOC link between a TOR and a node, which comprises the following steps: connecting the server node with a cabinet top switch to perform topology configuration; deploying a program on a server node, and starting a test; and carrying out flow deployment and checking analysis test results. The method comprises the following steps of connecting a server node with a counter top switch for topology configuration, and comprises the following steps: s11: the server node is connected to each network port of the switch; s12: the vlan and ip addresses are configured on the switch, and the ip addresses and gateway routes are configured on each node of the server, so that the nodes can communicate with each other.
Description
Technical Field
The invention relates to the technical field of network testing between server nodes, in particular to a system and a method for testing stability of an AOC link between a TOR and a node.
Background
With the rapid development of server products, the application range is more and more wide, the number of required server nodes is more and more huge, a RACK (RACK) is developed, the stability of the connection between each node server of the RACK becomes the central importance of the characteristics of the server products, and a tor (top of rank) top-of-cabinet switch.
Disclosure of Invention
In order to overcome the defects in the prior art, the present invention provides a system and a method for testing the stability of an AOC link between a TOR and a node, so as to solve the above technical problems.
A method for testing the stability of an AOC link between a TOR and a node comprises the following steps:
connecting the server node with a cabinet top switch to perform topology configuration;
deploying a program on a server node, and starting a test;
and carrying out flow deployment and checking analysis test results.
Further, the step of connecting the server node with the counter top switch for topology configuration includes:
s11: the server node is connected to each network port of the switch;
s12: the vlan and ip addresses are configured on the switch, and the ip addresses and gateway routes are configured on each node of the server, so that the nodes can communicate with each other.
Further, in step S12, configuring a vlan and an ip address on the switch, including:
s121: creating two vlans and respectively setting the name and the ID number of the vlan, wherein the two vlans are vlan100 and vlan200 respectively;
s122: associating the ID of each vlan with the corresponding vlan interface;
s123: respectively setting ip and a network mask of the vlan;
s124: and adding each net opening into the set vlan.
Further, step S121 is preceded by:
s210: logging on the switch, configuring the syslog server local disk file and setting the time zone, and submitting for storage.
Further, in step S12, configuring an ip address and a gateway route on each node of the server, including: server node configuration is performed under the vlan100 and the vlan200, respectively, wherein,
the server node configuration is performed under the vlan100, and includes:
configuring an ip and a gateway added to a network port of each server node in the vlan 100;
adding a routing table;
the server node configuration is performed under the vlan200, and includes:
configuring an ip and a gateway added to a network port of each server node in the vlan 200;
a routing table is added.
Further, the step of deploying the program on the server node and starting the test includes the following steps:
s21: detecting whether netperf tools are installed on all server nodes; if so, executing step S52, otherwise, executing step S22 after installing the netperf tool;
s22: and running the netserver command on all the server nodes to serve as a receiving end.
Further, the step of deploying the traffic on the server node and checking the analysis test result includes the following steps:
s31: each two nodes are mutually a sending end and a receiving end to send a packet to the other end through a netperf tool;
s32: and after the test is finished, checking test results at the switch end and the server node end respectively.
Further, the total number of the server nodes is 10, and the total number is N1-N10; each two nodes are a mutually sending end and a receiving end to send a packet to each other through a netperf tool;
bidirectional 10G flow is established between N1 and N6, N1 sends packets to N6 through a netperf tool, and N6 sends packets to N1 through the netperf tool;
bidirectional 10G flow is established between N2 and N10, N2 sends packets to N10 through a netperf tool, and N10 sends packets to N2 through the netperf tool;
bidirectional 10G flow N3 between N3 and N7 sends packets to N7 through a netperf tool, and N7 sends packets to N3 through the netperf tool;
a bidirectional 10G flow Node4 between N4 and N5 sends a packet to N5 through a netperf tool, and N5 sends a packet to N4 through the netperf tool;
bidirectional 10G traffic N8 between N8 and N9 is transmitted to N9 through a netperf tool, and N9 is transmitted to N8 through the netperf tool.
Further, step S32 includes:
checking the detailed information of the switch port through a show interface + interface name command;
checking the exchanger log through a show log date command;
further, step S32 further includes:
the checking server receives the information of the packets of various protocols;
checking statistical information of server network card receiving packets;
and checking the server log.
According to the technical scheme, the invention has the following advantages: the design is suitable for a scene of network link of multiple server nodes, and the deployment has the advantages that a closed loop of a network can be formed, so that the test result is more complete and strict, the operation is simple, the usability is strong, the requirement on the stability of the network link of the server can be more effectively met, and the product can be better optimized.
In addition, the invention has reliable design principle, simple structure and very wide application prospect.
Therefore, compared with the prior art, the invention has prominent substantive features and remarkable progress, and the beneficial effects of the implementation are also obvious.
Drawings
FIG. 1 is a flowchart of a method for testing the stability of an AOC link between a TOR and a node
FIG. 2 is a schematic diagram of a server node connected to a counter top switch;
fig. 3 is a schematic flow chart of the configuration of vlan and ip addresses on the switch.
Detailed Description
The present invention will be described in detail below with reference to the accompanying drawings by way of specific examples, which are illustrative of the present invention and are not limited to the following embodiments.
Example one
As shown in fig. 1-2, a method for testing the stability of an AOC link between a TOR and a node includes the following steps:
s1: connecting the server node with a cabinet top switch to perform topology configuration;
s11: the server node is connected to each network port of the switch;
s12: the vlan and ip addresses are configured on the switch, and the ip addresses and gateway routes are configured on each node of the server, so that the nodes can communicate with each other.
S2: deploying a program on a server node, and starting a test;
s3: and carrying out flow deployment and checking analysis test results.
Step S121 includes:
s210: logging on the switch, configuring the syslog server local disk file and setting the time zone, and submitting for storage.
As shown in fig. 3, in step S12, a vlan and an ip address are configured on the switch, and the specific steps include:
s121: creating two vlans and respectively setting the name and the ID number of the vlan, wherein the two vlans are vlan100 and vlan200 respectively;
s122: associating the ID of each vlan with the corresponding vlan interface;
s123: respectively setting ip and a network mask of the vlan;
s124: and adding each net opening into the set vlan.
Step S12, configuring ip addresses and gateway routes on each node of the server, including: server node configuration is performed under the vlan100 and the vlan200, respectively, wherein,
the server node configuration is performed under the vlan100, and includes:
configuring an ip and a gateway added to a network port of each server node in the vlan 100;
adding a routing table;
the server node configuration is performed under the vlan200, and includes:
configuring an ip and a gateway added to a network port of each server node in the vlan 200;
a routing table is added.
The method comprises the following steps of carrying out program deployment on a server node, and starting a test, wherein the program deployment comprises the following steps:
s21: detecting whether netperf tools are installed on all server nodes; if so, executing step S52, otherwise, executing step S22 after installing the netperf tool;
s22: and running the netserver command on all the server nodes to serve as a receiving end.
The steps of carrying out traffic deployment on the server node and checking the analysis test result comprise the following steps:
s31: each two nodes are mutually a sending end and a receiving end to send a packet to the other end through a netperf tool;
s32: and after the test is finished, checking test results at the switch end and the server node end respectively.
The total number of the server nodes is 10, and the number of the server nodes is N1-N10; each two nodes are a mutually sending end and a receiving end to send a packet to each other through a netperf tool;
bidirectional 10G flow is established between N1 and N6, N1 sends packets to N6 through a netperf tool, and N6 sends packets to N1 through the netperf tool;
bidirectional 10G flow is established between N2 and N10, N2 sends packets to N10 through a netperf tool, and N10 sends packets to N2 through the netperf tool;
bidirectional 10G flow N3 between N3 and N7 sends packets to N7 through a netperf tool, and N7 sends packets to N3 through the netperf tool;
a bidirectional 10G flow Node4 between N4 and N5 sends a packet to N5 through a netperf tool, and N5 sends a packet to N4 through the netperf tool;
bidirectional 10G traffic N8 between N8 and N9 is transmitted to N9 through a netperf tool, and N9 is transmitted to N8 through the netperf tool.
Step S32 includes:
checking the detailed information of the switch port through a show interface + interface name command;
checking the exchanger log through a show log date command;
step S32 further includes:
the checking server receives the information of the packets of various protocols;
checking statistical information of server network card receiving packets;
and checking the server log.
Example two
A method for testing the stability of AOC link between TOR and node,
testing software: netperf-2.4.5; the tested device: 1 switchboard, there are 10 nodes on 1 complete cabinet, adopt AOC link connection between switchboard and the node;
and (3) testing conditions are as follows: room temperature 25 + -5 deg.C, relative humidity 50% + -20%. The test is carried out without being placed in a thermal chamber, and the temperature is normal.
Setting the rotating speed of the fan: according to the auto speed of the whole cabinet or the server, the auto speed does not need to be set specially.
And (3) testing the topology: N1-N10 are 10 nodes in the whole cabinet, wherein N3, N4, N5 and N6 are connected below one fourth port of the TOR, and the rest nodes are connected below the common ten-million ports. N1 and N2 are in the Vlan1, N3-N10 are in the Vlan2, and gateway routing direction TOR is configured on each node, so that the vlans can intercommunicate.
The switch is configured as follows:
the vlan and ip addresses are configured on the switch, and the ip addresses and gateway routes are configured on each node of the server, so that the nodes can communicate with each other.
Logging in the ruijie switch, and executing the following commands:
set system syslog local-file disk
set system timezone Asia/Shanghai
commit
set vlans vlan-id 100
set vlans vlan-id 200
set vlans vlan-id 100 l3-interface vlan100
set vlans vlan-id 200 l3-interface vlan200
commit
set vlan-interface interface vlan100 address 192.168.100.1 prefix-length 24
set vlan-interface interface vlan200 address 192.168.200.1 prefix-length 24
commit
set interface gigabit-ethernet te-1/1/1 family ethernet-switching native-vlan-id 200
set interface gigabit-ethernet te-1/1/2 family ethernet-switching native-vlan-id 200
set interface gigabit-ethernet te-1/1/3 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/4 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/5 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/6 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/49 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/50 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/51 family ethernet-switching native-vlan-id 100
set interface gigabit-ethernet te-1/1/52 family ethernet-switching native-vlan-id 100
commit
the server is configured as follows:
IP addresses and gateway routes are configured on all nodes of the server, so that all nodes can communicate with each other.
vlan100 lower node configuration:
ifconfig xgbe0 192.168.100.x netmask 255.255.255.0
route add -net 192.168.200.0/24 gw 192.168.100.1
vlan200 lower node configuration:
ifconfig xgbe0 192.168.200.x netmask 255.255.255.0
route add -net 192.168.100.0/24 gw 192.168.200.1
program deployment
Copying the netperf tool to all nodes;
installing netperf software
# tar zxvf netperf-2.4.5.tar.gz a decompression netperf tool
# cd netperf-2.4.5 a into netperf installation directory
#./configure
#make
#make install
The netperf server end program Netserver is started on all nodes and all nodes run Netserver commands as the receiving end.
Traffic deployment
The test pack length was selected to be 1500B and the test time was 7 days, i.e., 7 × 24 × 3600=604800 seconds.
Bidirectional 10G traffic between N1 and N6, the destination address is the host address of the other party
N1:
netperf-H192.168.100.106-l 604800-m 1500 & a N1 are packaged to N6 through netperf tool
N6:
netperf-H192.168.200.201-l 604800-m 1500 & a N6 are packaged to N1 through netperf tool
In the same way, every two nodes are a sending end and a receiving end, so that any node is prevented from being omitted;
bidirectional 10G traffic between N2 and N10, the destination address is the host address of the other party
N 2:
netperf –H 192.168.100.110 –l 604800 -- -m 1500 &
N10:
netperf –H 192.168.200.202 –l 604800 -- -m 1500 &
Bidirectional 10G traffic between N3 and N7, the destination address is the host address of the other party
N 3:
netperf –H 192.168.100.107 –l 604800 -- -m 1500 &
N 7:
netperf –H 192.168.100.103 –l 604800 -- -m 1500 &
Bidirectional 10G traffic between N4 and N5, the destination address is the host address of the other party
N 4:
netperf –H 192.168.100.105 –l 604800 -- -m 1500 &
N 5:
netperf –H 192.168.100.104 –l 604800 -- -m 1500 &
Bidirectional 10G traffic between N8 and N9, the destination address is the host address of the other party
N8:
netperf –H 192.168.100.109 –l 604800 -- -m 1500 &
N9:
netperf –H 192.168.100.108 –l 604800 -- -m 1500 &
Observation results
Observing whether a network card on a server loses packets or has error codes or not in the running process;
and in the running process, observing whether a network card up/down log exists on the server/var/log/messages.
The switch end:
after the test is finished, the detailed information of the switch port is checked through a show interface + interface name command, and information such as the number of lost packets and the number of error packets is concerned.
After the test is finished, the exchanger log is checked through a show log date command, no port down event exists in the log, and no other exception or error exists.
After the test is finished, the following information at the end of the exchanger is checked
a.show log date or show log last-rows
Checking information of packets received by server in various protocols
V/view by date
XorPlus> show log date
Possible completions:
<time> format: YEAR.MM.DD
XorPlus>
v/View by rows
XorPlus> show log last-rows
Possible completions:
<rows> The outputted rows of log
XorPlus> 。
A server side:
after the test is finished, the following information of the server side is checked
a.cat /proc/net/snmp
Checking information of packets received by server in various protocols
ethtolol-S + interface name
Checking statistical information of server network card receiving packet
c.tail -f /var/log/messages
The server log is viewed regarding the presence or absence of link up/down time and other anomalies and errors.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims, as well as in the drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (4)
1. A method for testing the stability of an AOC link between a cabinet top switch and a node is characterized by comprising the following steps:
connecting the nodes with a cabinet top switch to perform topology configuration; the method specifically comprises the following steps: s11: the nodes are connected to each network port of the switch;
s12: the method comprises the steps that vlan and ip addresses are configured on a switch, and ip addresses and gateway routes are configured on nodes, so that the nodes can be communicated; in step S12, a vlan and an ip address are configured on the switch, and the specific steps include:
s210: logging in the switch, configuring a local disk file of the syslog node, setting a time zone, and submitting and storing;
s121: creating two vlans and respectively setting the name and the ID number of the vlan, wherein the two vlans are vlan100 and vlan200 respectively; wherein vlan100 is a first vlan and vlan200 is a second vlan;
s122: associating the ID of each vlan with the corresponding vlan interface;
s123: respectively setting ip and a network mask of the vlan;
s124: adding each network port into the set vlan;
program deployment is carried out on the nodes, and testing is started;
performing traffic deployment, and checking analysis test results, specifically including: s31: each two nodes are mutually a sending end and a receiving end to send a packet to the other end through a netperf tool; s32: after the test is finished, the test results are respectively checked at the switch end and the node end; step S32 specifically includes: checking the detailed information of the switch port through a show interface + port name command; the detailed information comprises the number of lost packets and the number of error packets; the check node receives the information of the packets of various protocols; checking the statistical information of the node network card receiving packet; and checking the node log.
2. The method for testing the stability of the AOC link between the counter top switch and the node according to claim 1, wherein in step S12, configuring the ip address and the gateway route on each node includes: node configuration is performed under the vlan100 and the vlan200, respectively, wherein,
node configuration is performed under the vlan100, including:
configuring an ip and a gateway added to each node network port in the vlan 100;
adding a routing table;
node configuration is performed under the vlan200, including:
configuring an ip and a gateway added to each node network port in the vlan 200;
a routing table is added.
3. The method for testing the stability of the AOC link between the counter top switch and the node according to claim 2, wherein in the step of deploying the program on the node and starting the test, the step of deploying the program comprises the steps of:
s21: detecting whether netperf tools are installed on all nodes; if so, executing step S22, otherwise, executing step S22 after installing the netperf tool;
s22: the netserver command is run at all nodes as the receiver.
4. The method for testing the stability of the AOC link between the cabinet top switch and the node as claimed in claim 3, wherein the total number of the nodes is 10, which are respectively N1-N10; the specific steps of sending the packet to each other by each two nodes in the S31 through the netperf tool by the sending end and the receiving end each other include:
bidirectional 10G flow is opened between N1 and N6, N1 sends packets to N6 through a netperf tool, and N6 sends packets to N1 through the netperf tool;
bidirectional 10G flow is opened between N2 and N10, N2 sends packets to N10 through a netperf tool, and N10 sends packets to N2 through the netperf tool;
bidirectional 10G flow is opened between N3 and N7, N3 sends packets to N7 through a netperf tool, and N7 sends packets to N3 through the netperf tool;
bidirectional 10G flow is opened between N4 and N5, N4 sends packets to N5 through a netperf tool, and N5 sends packets to N4 through the netperf tool;
bidirectional 10G traffic is opened between N8 and N9, N8 packages to N9 through the netperf tool, and N9 packages to N8 through the netperf tool.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810896864.4A CN109039818B (en) | 2018-08-08 | 2018-08-08 | Method for testing stability of AOC link between TOR and node |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810896864.4A CN109039818B (en) | 2018-08-08 | 2018-08-08 | Method for testing stability of AOC link between TOR and node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109039818A CN109039818A (en) | 2018-12-18 |
| CN109039818B true CN109039818B (en) | 2022-03-04 |
Family
ID=64649645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810896864.4A Active CN109039818B (en) | 2018-08-08 | 2018-08-08 | Method for testing stability of AOC link between TOR and node |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109039818B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102549972A (en) * | 2009-10-09 | 2012-07-04 | 微软公司 | Flyways in data centers |
| CN106027407A (en) * | 2016-08-05 | 2016-10-12 | 广州市香港科大霍英东研究院 | Adjusting method of congestion windows in network, network congestion control method and interchanger |
| US9705798B1 (en) * | 2014-01-07 | 2017-07-11 | Google Inc. | Systems and methods for routing data through data centers using an indirect generalized hypercube network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8929377B2 (en) * | 2011-03-15 | 2015-01-06 | Futurewei Technologies, Inc. | Systems and methods for automatic rack detection |
-
2018
- 2018-08-08 CN CN201810896864.4A patent/CN109039818B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102549972A (en) * | 2009-10-09 | 2012-07-04 | 微软公司 | Flyways in data centers |
| US9705798B1 (en) * | 2014-01-07 | 2017-07-11 | Google Inc. | Systems and methods for routing data through data centers using an indirect generalized hypercube network |
| CN106027407A (en) * | 2016-08-05 | 2016-10-12 | 广州市香港科大霍英东研究院 | Adjusting method of congestion windows in network, network congestion control method and interchanger |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109039818A (en) | 2018-12-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100733020B1 (en) | Customer MAC Frame Forwarding Method, Edge Bridge, And Storage Medium Registering Program | |
| JP5846221B2 (en) | Network system and topology management method | |
| KR101495226B1 (en) | Method and system for looping back traffic in qiq ethernet rings and 1:1 protected pbt trunks | |
| CN102422600B (en) | Method provided in mixed nodes, network thereof and network units thereof | |
| EP2677691A1 (en) | Connectivity Fault Notification | |
| US8274911B2 (en) | Network monitoring system and path extracting method | |
| US8750135B2 (en) | Communication node, method, and maintenance point for handling encapsulated data frames | |
| US20080298258A1 (en) | Information transfer capability discovery apparatus and techniques | |
| CN103457756B (en) | A kind of loop path detection, Apparatus and system | |
| US7881207B2 (en) | Method and system for loop-back and continue in packet-based network | |
| CN114598626A (en) | Message processing method and gateway equipment | |
| CN109039818B (en) | Method for testing stability of AOC link between TOR and node | |
| CN104125079B (en) | A kind of method and device for determining two-node cluster hot backup configuration information | |
| JP2019117972A (en) | Network management device, network system, method, and program | |
| US7626937B2 (en) | System and method for network connection detection | |
| CN109412851B (en) | Link layer path detection method, device and system | |
| Cisco | Release Notes for Catalyst 4000 Family Software Release 4.x | |
| CN107347014A (en) | A kind of network fault detecting method and system | |
| Cisco | Troubleshooting WAN Connectivity | |
| Cisco | Release Notes for Catalyst 5000 Family Software Release 4.x | |
| Cisco | Debug Command Reference Software Release 9.21 | |
| Cisco | 1.1.24 Software Release Notes Cisco WAN MGX 8850, 8230, and 8250 Software | |
| Cisco | Troubleshooting Bridging Connectivity | |
| Cisco | Troubleshooting WAN Connectivity | |
| Cisco | Troubleshooting WAN Connectivity |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |