Introduction
This article is intended to help you work with the ZTE ZXR10 software on routers and switches. The ZTE ZXR10 software is a unified operating system that runs on various ZTE routers and switches, such as the ZXR10 M6000 series, the ZXR10 T8000 series, and the ZXR10 8900E series. It provides rich features and functions for network management, security, reliability, and performance optimization.
In this article, you will learn how to access the ZTE ZXR10 software and enter the configuration mode, how to use the basic and advanced commands and parameters to configure the system settings and the specific features and functions, and how to use the diagnostic commands and tools to monitor and troubleshoot the network performance and issues.
To follow this article, you need to have the basic knowledge and skills of IP networking and routing protocols, such as TCP/IP, VLANs, OSPF, BGP, ISIS and MPLS. The tips and tricks are organized in three different categories; Basic Configuration, Advanced Configuration, Monitoring and Troubleshooting.
Basic Configuration
Learn how to access the routers and switches, enter the configuration mode, use the basic commands and parameters to configure the system settings, such as the hostname, the password, the IP address, and the routing protocol.
Entering Configuration Mode:
R1#configure t
Enter configuration commands, one per line. End with CTRL/Z.
R1(config)#Static Default Route in a VRF (Virtual Routing and Forwarding) [e.g. Gateway = 10.10.10.1]
R1#configure t
R1(config)# ip route vrf TEST 0.0.0.0 0.0.0.0 10.10.10.1 name Put_Route_Label_HereAdvanced Configuration
Learn how to use the advanced commands and parameters to configure the specific features and functions of the ZTE ZXR10 software, such as the VLAN, the QoS, the firewall, and the VPN.
Access Control List (ACL) to manage which IP subnets are allowed SSH access to your system:
1. Enter Configuration Mode:
# configure t
2. Create the ACL:
(config)# ipv4-access-list SSH_ACCESS_MGT
rule 10 permit 10.0.0.0 0.255.255.255
rule 20 permit 172.16.0.0 0.15.255.255
rule 30 permit 192.168.0.0 0.0.255.255
rule 100 deny any
3. Exit the ACL config Level:
(config-ipv4-acl)# exit
4. Apply the ACL to the SSH server:
(config)# ssh server access-class ipv4 SSH_ACCESS_MGT
5. Commit and exit the configuration
(config)# commit
(config)# exit
7. Save the configuration persistently:
# writeAccess Control List (ACL) to manage which IP subnets are allowed SNMP access to your system:
1. Enter Configuration Mode:
# configure t
2. Create the ACL:
(config)# ipv4-access-list SNMP_ACCESS_MGT
rule 10 permit 10.0.0.0 0.255.255.255
rule 20 permit 172.16.0.0 0.15.255.255
rule 30 permit 192.168.0.0 0.0.255.255
rule 100 deny any
3. Exit the ACL config Level:
(config-ipv4-acl)# exit
4. Apply the ACL to the SNMP-Server:
(config)# snmp-server access-list ipv4 SNMP_ACCESS_MGT
5. Commit and exit the configuration
(config)# commit
(config)# exit
7. Save the configuration persistently:
# writeMonitoring and Troubleshooting
Learn how to use the diagnostic commands and tools to monitor and troubleshoot the network performance and issues, such as the ping, the traceroute, the show, and the debug commands.
View Running Configuration:
R1# show running-config
R1# show running-config | ?
begin - Begin with the line that matches
count - Show total count
exclude - Exclude lines that match
first - Show begin of output only
ignore-case - Ignore case when matching letters
include - Include lines that match
last - Show end of output only
one-line - Show table item in one lineViewing all the VRFs configured on the router:
R1# show ip vrf briefViewing the routing-table specific to a VRF
R1# show ip forwarding route vrf TEST_VRFViewing the Logs:
# show logfilePort Mirroring on a Switch using SPAN (Switch Port ANalyzer) a useful feature during troubleshooting that allows you to copy the traffic from one or more source ports or VLANs to a destination port for analysis (e.g using WireShark) or for monitoring. This example is tested on ZXR10 8902E switch and supports up to four span sessions, and each session can have multiple source ports or VLANs and one destination port. In this example, the traffic of interest is on port: gei-0/0/0/1 and the laptop collecting the traffic sample is connected to: gei-0/0/0/2
1. Enter Configuration Mode:
SW1# configure t
2. Define the SPAN session and give it a session ID:
SW1(config)# span session 1
3. Define the destination interface (where the laptop collecting the traffic is connected):
SW1(config-span-session-1)# default destination interface gei-0/0/0/2
SW1(config-span-session-1)# exit
4. Specify the mirrored source interfaces (traffic of interest, can be from multiple ports), both transmit (tx) and receive (rx) directions:
SW1(config)# span apply session 1 source interface gei-0/0/0/1 direction tx
SW1(config)# span apply session 1 source interface gei-0/0/0/1 direction rx
SW1(config)#commit5. View all active SPAN sessions on the switch:
SW1# show span session all
6. View Configuration specific to SPAN sessions:
SW1# show running-config span-sessionPort Mirroring on a Switch using PM-QoS traffic-mirror + ACL, tested on ZXR10 8905E Switch. In this example, the traffic of interest is to/from a specific host IP: 10.10.10.10 on port: gei-0/0/0/1 and the laptop collecting the traffic sample is connected to: gei-0/0/0/2. You can fine tune the ACL to fit your traffic of interest by applying more specific parameters like port numbers:
1. Enter Configuration Mode:
SW1# configure t
2. Create the ACL:
SW1(config)# ipv4-access-list MIRROR1
SW1(config-ipv4-acl)#rule 10 permit ip 10.10.10.10 0.0.0.0 any
SW1(config-ipv4-acl)#rule 15 permit ip any 10.10.10.10 0.0.0.0
SW1(config-ipv4-acl)#rule 20 permit ip any any
SW1(config-ipv4-acl)#exit
3. Apply the ACL to the source interface (i.e. the interface of interest connecting to the host you are investigating or monitoring, can also be applied to multiple ports):
SW1# configure t
SW1(config)# interface gei-0/0/0/1
SW1(config-if-gei-0/0/0/1)# ipv4-access-group ingress MIRROR1
SW1(config-if-gei-0/0/0/1)# exit
4. Configure the PM-QoS traffic-mirror session and specify the destination interface (i.e. the interface connected to the laptop with WireShark):
SW1# configure t
SW1(config)# pm-qos
SW1(config-pm-qos)# traffic-mirror in ipv4-access-list MIRROR1 rule-id 10 interface gei-0/0/0/2
SW1(config-pm-qos)# traffic-mirror in ipv4-access-list MIRROR1 rule-id 15 interface gei-0/0/0/2
SW1(config-pm-qos)# commit
SW1(config-pm-qos)# exit
SW1(config)#exit
SW1# writeRemember to bookmark this page and return often, as it will be updated frequently with fresh tricks and tips. If you have been working with ZTE software on routers and switches, i would love to hear from you and get more new tricks and tips.
About the Author
Joshua Makuru Nomwesigwa is a seasoned Telecommunications Engineer with vast experience in IP Technologies; he eats, drinks, and dreams IP packets. He is a passionate evangelist of the forth industrial revolution (4IR) a.k.a Industry 4.0 and all the technologies that it brings; 5G, Cloud Computing, BigData, Artificial Intelligence (AI), Machine Learning (ML), Internet of Things (IoT), Quantum Computing, etc. Basically, anything techie because a normal life is boring.