Home> Support> Technical Documents>

Ruijie RG-Switch Implementation Cookbook (V1.2)

2020-02-15 View: 13408

Best Practice Solution Guide

4.1       Preparation

4.1.1      Preparation before Installation

Preparation before installation

To ensure the installation successfully, make sure the installation site meets the requirements including ventilation, temperature, humidity, sanitary, power, fiber, cable .etc

For Detail information ,see hardware installation and reference guide of corresponding products , such as RG-S8600E Series Switch Hardware Installation and Reference Guide,V1.10


On the other hand, double confirm following important infomation ahead of schedule:

1. The network topology, configuration, IP routing information, user scale, traffic information and running status of current production network.

2. Equipment list and pre-sale solution.

3. Customer's requirements and corresponding features

4. The campatibility with current devices, like STP, AP with switches of other vendors

5. Current link and interface status including optical connector, fiber etc.

6. Design the Network and acquire customer's agreement

7. Customer's network verification requirements

8. Customer's cut over plan requirements

9. Customer's acceptance inspection requirements

4.1.2      Check Switch Software/Hardware

Check software

This figure shows how to display soft and hardware version



Software selection rules:

1. We suggest you to update the new switch to the latest firmware

2. We suggest you to update the existing switch to the latest firmware also if they're running steady

3. For detail technical specification , see corresponding product configuration guide ,or visit our service portal



Confirm whether the project is a "expansion network" or "new network"

1) If the project is a expansion network ,focus on the compatibility as following :

Expansion module/line card

For detail infomation , see "Hardware Supported"  in corresponding product release notes


Expansion switch

Focus on the campatibility of different protols (especially MSTP) between Ruijie and other vendor.Do a full validation before implementation


2) If the project is a new network

Determine whether the current/latest firmware supports customer's requirement , see configuration guide of corresponding product


3)Read release notesand double confirm the matters need attention


Check hardware

Take S8600E series switches as example (see RG-S8600E Series Switch Hardware Installation and Reference Guide)

1. M8600E-CM


2. M8600E-24GT20SFP4XS-ED LED


3. M8600E-48GT-ED LED


4. M8600E-48GT-EF LED


4.2        Best Practic Scenario

4.2.1      Education

Dual core using VSU

I. Requirement

1. Core swtich Configure two S8600E chassis swithes as VSU , and connect VSU to WAN zone with double uplinks

2. Server farmConnect some Servers and storage  to data center switch S6220 and S6220 is also gateway for servers and storage .You can also connect other servers that have equiped with double NICs to VSU with double links

3. Aggregation switchFor Layer 3 Aggregation switches , they are user gateway and run OSPF  .Connect a aggregation switch to two VSU members independently . For Layer 2 aggregation switch , connect them  to two VSU members   independently ,and VSU is the user gateway.


II. Network Topology




III. Common requirements and features

Select features below base on requirements:


IV. Optional optimization

Select optional optimization below base on requirements:

V. Verification

1. For single feature verification, see verification method in each corresponding chapter

2. For total network running status, see Appendix

4.3 Appendix: Common Verification Command

4.3.1 Show version

The example shows the firmware version on a box switch:


This example shows the firmware version on a chassis switch:

Ruijie#show version slot





DevDevice ID, equal to 1 by default, and maybe 2 or more if it is a VSU.

SlotSlot ID slots number of different model vary, but all model has 2 engine slots --M1 and M2 and can plug in either M1 or M2 if there's only one engine.

PortPort number of the line card. Combo port caculates as one port only.

Configured Module Installed module, and must be the same to Online Module

Online ModuleWhether the module powers on and recognized

User StatusLine card status, installed or uninstalled

Software Status "OK" indicates working properly, Master indicates primary engine, backup indicates backup engine.

4.3.2 Show run

This example shows how to display switch configuration



4.3.3 Show CPU

 View cpu utilization every 5s, 1m or 5m by command "show cpu"




Usually, "CPU utilization in five minutes" shall be kept below 30% ; Pay attention if it exceeds 60%.

4.3.4 Show memory

This example shows current memory status 




Usually, "Used Rate" shall be kept below 75%; Pay attention if it exceeds 80%.

4.3.5 Show power

This example shows the power status on a chassis switch



4.3.6 Show fan

This example shows the fan status on a chassis switch






4.3.7 Show temperature

This example shows the temperature status on a chassis switch



4.3.8 Show clock




Ruijie#show clock                                                

18:01:03 beijing Tue, Dec 3, 2013


4.3.9 Show log

This example shows logs in buffer







This example shows how to read logs in flash




4.3.10 Verify flash

This example shows how to display file list in flash 





4.3.11 Verify local MAC address

You can enter "show arp" EXEC command to display Layer 3 MAC address.

This example shows the Layer 3 MAC address on S8600 switch. "--"indicates that this arp entry is a local one.





4.3.12 Verify MAC table

This example displays mac address table






This example displays mac address statistics

4.3.13 Verify ARP table






This example displays detail arp information including port, vlan etc






This example displays arp statistics





4.3.14 Verify route table

This example displays IP route table





This example displays IP route statistic





4.3.15 Verify interface IP address

This example displays IP address on Layer 3 port or SVI






4.3.16 Verify interface status and description

This example displays port status of all ports including link status, vlan, duplex, speed, medium type






This example displays interface description



This example displays port status of port G0/1

Ruijie#show interfaces gigabitEthernet 0/1

 Index(dec):1 (hex):1

GigabitEthernet 0/1 is DOWN  , line protocol is DOWN   

Hardware is marvell GigabitEthernet

Description: TO-ZGE-S8610-2_GE2/1

Interface address is: no ip address

  MTU 1500 bytes, BW 1000000 Kbit

  Encapsulation protocol is Bridge, loopback not set

  Keepalive interval is 10 sec , set

  Carrier delay is 2 sec

  RXload is 1 ,Txload is 1

  Queueing strategy: WFQ

  Switchport attributes:

    interface's description:"TO-ZGE-S8610-2_GE2/1"

    medium-type is copper

    lastchange time:0 Day: 0 Hour:45 Minute:26 Second

    Priority is 0

    admin duplex mode is AUTO, oper duplex is Unknown

    admin speed is AUTO, oper speed is Unknown

    flow control admin status is OFF,flow control oper status is Unknown

    broadcast Storm Control is ON,multicast Storm Control is OFF,unicast Storm Control is ON

  5 minutes input rate 0 bits/sec, 0 packets/sec            

  5 minutes output rate 0 bits/sec, 0 packets/sec         

    37167599 packets input, 2566418459 bytes, 45 no buffer, 45 dropped     ------>input direction dropping

    Received 58764 broadcasts, 0 runts, 0 giants

    0 input errors, 0 CRC, 0 frame, 0 overrun, 0 abort

    37210638 packets output, 2565322398 bytes, 0 underruns , 0 dropped    ------>output direction dropping

0        output errors, 0 collisions, 0 interface resets


4.3.17 Verify interface packets statistics

This example displays traffic counters on port F0/1




Ruijie#show int fastEthernet 0/1 counters

Interface : Fa0/1

5 minute input rate  : 0 bits/sec, 0 packets/sec

5 minute output rate : 0 bits/sec, 0 packets/sec

InOctets             : 68023600

InUcastPkts          : 92842   

InMulticastPkts      : 36700  

InBroadcastPkts      : 75636  

OutOctets            : 3630373 

OutUcastPkts         : 32053   

OutMulticastPkts     : 1059   

OutBroadcastPkts     : 13231  

[1] Undersize packets    : 0

[2] Oversize packets     : 0

[3] collisions           : 0

[4] Fragments            : 0

[5] Jabbers              : 0

[6] CRC alignment errors : 0

[7] AlignmentErrors      : 0

[8] FCSErrors            : 0

[9] dropped packet events (due to lack of resources): 0

[10] packets received of length (in octets):                                      

  64:119136, 65-127: 75769, 128-255: 12663,

  256-511: 3149, 512-1023: 1955, 1024-1518: 38849


[1] A packet which is shorter than Ethernet's minimum packet size of 64 bytes, but has correct checksum.

[2] A packet which is longer than Ethernet's maximum packet size of 1518 bytes, but has correct checksum.

[3] Collisions: multiple sites try to send traffic at the same time, leading to a collision, usually it's the duplex problem

[4] A packet which is shorter than Ethernet's minimum packet size of 64 bytes, but has wrong checksum.

[5] A packet which is shorter than Ethernet's minimum packet size of 1518 bytes, but has wrong checksum.

[6] CRC alignment errors: The same to FCS, CRC is the local checksum .Peer recalculates and compares with FCS after receiving the packet

[7] Alignment errorAlignment errors are caused by misaligned reads and writes

[8] Modified or missing fram: FCS checksum error

[9] Statistics for Dropped packets

[10] Statistics for received packets based on packet length (in octets)


This example displays traffic summary of all ports


This example displays traffic rate of all ports






Ruijie Networks