The command line interface is divided into many different modes, The commands available to you depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a list of commands available for each command mode. Table following describes the main command modes, how to access each one, the prompt you see in that mode, and how to exit the mode. The examples in the table use the hostname SWITCH. Table Command Mode Summary<\/p>\n
SWITCH><\/code><\/pre>\nEnter exit to quit<\/h2>\n
Use this mode to: Perform basic tests. Display system information.<\/p>\n
Privileged Mode<\/h2>\nSWITCH#<\/code><\/pre>\nWhile in user EXEC mode, enter the enable command. Enter disable to exit. Use this mode to: Exec network utilities. Display module information. System management operation.<\/p>\n
Global Configuration<\/h2>\nSWITCH(config)#<\/code><\/pre>\nWhile in Privileged mode, enter the configuration terminal command. Enter exit or end to return. Use this mode to: configure parameters that apply to the entire switch.<\/p>\n
Interface Configuration<\/h2>\nSWITCH(config-if)#<\/code><\/pre>\nWhile in global configuration mode, e interface command (with a specific interface). Enter exit or end to return. Use this mode to: configure parameters for the Ethernet ports.<\/p>\n
Configuring<\/h2>\n\n- Manually Assigning IPv4 Information<\/li>\n<\/ul>\n
SWITCH(config)#management vlan VLANID ip address IPADDR\/MASKLEN gateway IPADDR<\/code><\/pre>\nSWITCH(config)#no management vlan<\/code><\/pre>\nManually assigning switch management IPv4 information.<\/p>\n
SWITCH(config)#management vlan VLANID ip address dhcp<\/code><\/pre>\nSWITCH(config)#no management vlan<\/code><\/pre>\nConfiguring DHCP-Based IPv4 information autoconfiguration.<\/p>\n
SWITCH(config)#management vlan VLANID ipv6 address IPV6ADDR\/MASKLEN gateway IPV6ADDR<\/code><\/pre>\nSWITCH(config)#no management vlan<\/code><\/pre>\nManually assigning switch management IPv6 information.<\/p>\n
SWITCH(config)#management vlan VLANID ipv6 address dhcp<\/code><\/pre>\nSWITCH(config)#no management vlan<\/code><\/pre>\nConfiguring DHCP-Based IPv6 information autoconfiguration.<\/p>\n
SWITCH#show management summary<\/code><\/pre>\nDisplay IP information.<\/p>\n
Examples<\/h2>\n
Example 1: Manually assigning IPv4 information. The following examples shows how to configure management IPv4 address, The management VLAN is 1, the management IP is 192.168.64.200\/24, and the gateway address is 192.168.64.1. Manually assigning IPv4 information\uff1a<\/p>\n
SWITCH#configure terminal<\/code><\/pre>\nSWITCH(config)#management vlan 1 ip address 192.168.64.200\/24 gateway 192.168.64.1<\/code><\/pre>\nDisplay IP information\uff1a<\/p>\n
SWITCH#show management summary<\/code><\/pre>\nManagement interface with Ipv4: Type: Static Vlan: 1 Ip address: 192.168.64.200\/24 Gateway: 192.168.64.1 Backup\/Restore Configuration<\/p>\n
Configuring<\/h2>\n\n- Backup Configuration<\/li>\n<\/ul>\n
SWITCH#write<\/code><\/pre>\nSave your entries in the configuration file.<\/p>\n
SWITCH#copy default-config startup-config<\/code><\/pre>\nSWITCH#reload<\/code><\/pre>\nRestore the system default configuration, which will take effect after the device restarts.<\/p>\n
SWITCH#copy tftp tftp:\/\/A.B.C.D\/FILE startup-config<\/code><\/pre>\nSWITCH#reload<\/code><\/pre>\nA.B.C.D\uff1aremote tftp server ip address FILE\uff1aFile name of configuration Import the remote configuration into the device through the tftp protocol, replacing the existing configuration. Take effect after device restart.<\/p>\n
SWITCH#copy startup-config tftp tftp:\/\/A.B.C.D\/FILE<\/code><\/pre>\nA.B.C.D\uff1aremote tftp server ip address FILE\uff1aFile name of configuration Through the tftp protocol, the configuration is saved to the specified folder of the remote tftp server.<\/p>\n
SWITCH#copy ftp ftp:\/\/A.B.C.D\/FILE startup-config<\/code><\/pre>\nSWITCH#reload<\/code><\/pre>\nA.B.C.D\uff1aremote tftp server ip address FILE\uff1aFile name of configuration Import the remote configuration into the device through the ftp protocol, replacing the existing configuration. Take effect after device restart.<\/p>\n
SWITCH#copy startup-config ftp ftp:\/\/A.B.C.D\/FILE<\/code><\/pre>\nA.B.C.D\uff1aremote tftp server ip address FILE\uff1aFile name of configuration Through the ftp protocol, the configuration is saved to the specified folder of the remote tftp server.<\/p>\n
Examples<\/h2>\n
Example 1\uff1aExport the configuration to the folder specified by the remote tftp server, the file name is startup.conf. Environment construction\uff1a The remote PC starts the tftp server and selects the tftp current directory. The IP address of the remote PC is 192.168.64.1, and the management IP of the switch is configured as 192.168.64.100, and the remote PC can be pinged. Execute the configuration export command\uff1a<\/p>\n
SWITCH#<\/code><\/pre>\nSWITCH# copy startup-config tftp tftp:\/\/192.168.64.1\/startup.conf<\/code><\/pre>\n% Total % Received % Xferd Average Speed Time Time Time Current<\/p>\n
Dload Upload Total Spent Left Speed<\/h2>\n
100 1230 0 0 100 1230 0 151k –:–:– –:–:– –:–:– 240k 100 1230 0 0 100 1230 0 144k –:–:– –:–:– –:–:– 144k<\/p>\n
Copy Success<\/h2>\n
In the test directory of the remote PC, you can view the newly created startup.conf file. Example 2\uff1aImport the configuration file startup.conf under the folder specified by the remote ftp server into the device. Environment construction\uff1a Start the ftp server on the remote PC, select the current directory of ftp, and place the startup.conf file. The IP address of the remote PC is 192.168.64.1, and the switch management IP is configured as 192.168.64.100, and the remote PC can be pinged. Execute the configuration import command\uff1a<\/p>\n
SWITCH#<\/code><\/pre>\nSWITCH# #copy ftp ftp:\/\/192.168.64.1\/startup.conf startup-config<\/code><\/pre>\nEnter Username:xxxxxx Enter Password:xxxxxx % Total % Received % Xferd Average Speed Time Time Time Current<\/p>\n
Dload Upload Total Spent Left Speed<\/h2>\n
100 973 100 973 0 0 42572 0 –:–:– –:–:– –:–:– 48650<\/p>\n
Copy Success<\/h2>\n
After the configuration is imported, restart to take effect.<\/p>\n
Clearing Log<\/h2>\n\n- Clearing system log<\/li>\n<\/ul>\n
SWITCH# clear logging<\/code><\/pre>\nSystem Warm Restart<\/h2>\n\n- System Warm Restart<\/li>\n<\/ul>\n
SWITCH#reload<\/code><\/pre>\nSystem warm restart.<\/p>\n
User Management<\/h2>\n\n- Configuring Username and Password<\/li>\n<\/ul>\n
SWITCH(config)# username NAME password LINE<\/code><\/pre>\nSWITCH(config)# no username NAME<\/code><\/pre>\nIf the user name does not exist, add a new user, if it exists, modify the user's password. By default, the device has its own user "admin" and password "admin", which supports password modification and deletion operations. The length of the user and password is 0-32 bytes. Password display is encrypted. Password characters are case sensitive. The delete operation does not support deleting the user itself; to delete an online user, the user must be kicked off the line first.<\/p>\n
Configuring<\/h2>\nService Enablement Management<\/h2>\n\n- Configure and Enable WEB Management<\/li>\n<\/ul>\n
SWITCH(config)# web-server enable { all | http | https }<\/code><\/pre>\nSWITCH(config)# no web-server enable<\/code><\/pre>\nConfigure and enable WEB management. Default disabled state. Support IPv4 and IPv6.<\/p>\n
SWITCH(config)# telnet-server enable<\/code><\/pre>\nSWITCH(config)# no telnet-server enable<\/code><\/pre>\nConfigure and enable telnet management. Default disabled state. Support IPv4 and IPv6.<\/p>\n
SWITCH(config)# ssh-server enable<\/code><\/pre>\nSWITCH(config)# no ssh-server enable<\/code><\/pre>\nConfigure and enable SSH management. Default disabled state. Support IPv4 and IPv6.<\/p>\n
ACL Applied to Services<\/h2>\n\n- IPv4 ACL Applied to Services<\/li>\n<\/ul>\n
SWITCH(config)# ip { telnet | ssh | http | https } access-class {<1-199> | <1300-2699> | ACLNAME}<\/code><\/pre>\nSWITCH(config)# no ip { telnet | ssh | http | https } access-class<\/code><\/pre>\nIPv4 ACL is applied to telnet, ssh, http, https and other services. Users who meet the ACL permit rules are allowed to access the device, otherwise users cannot access the device.<\/p>\n
SWITCH(config)# ipv6 { telnet | ssh | http | https } access-class { ACLNAME }<\/code><\/pre>\nSWITCH(config)# no ipv6 { telnet | ssh | http | https } access-class<\/code><\/pre>\nIPv6 ACL is applied to telnet, ssh, http, https and other services. Users who meet the ACL permit rules are allowed to access the device, otherwise users cannot access the device.<\/p>\n
ACL Applied to Vty<\/h2>\n\n- ACL Applied to Vty<\/li>\n<\/ul>\n
SWITCH(config-line)# access-class {<1-199> | <1300-2699> | ACLNAME } in<\/code><\/pre>\nSWITCH(config-line)# no access-class {<1-199> | <1300-2699> | ACLNAME } in<\/code><\/pre>\nACL applied to vty. For telnet, ssh and other servers on vty. Users who meet the ACL permit rules are allowed to login by this line.<\/p>\n
Service Management Based on Line<\/h2>\n\n- Configure Services Supported on Line Vty<\/li>\n<\/ul>\n
SWITCH(config-line)# transport input { telnet | ssh | all | none }<\/code><\/pre>\nSWITCH(config-line)# no transport input<\/code><\/pre>\nConfigure services supported on vty. telnet: only supports telnet service. ssh: only supports ssh service. all: supports telnet and ssh services. none: No services are supported. Supports telnet and ssh services by default.<\/p>\n
Other Commands<\/h2>\n\n- Kick Online Users Offline<\/li>\n<\/ul>\n
SWITCH# clear line { vty | console } LINE<\/code><\/pre>\nVty represents the remote login user. Console represents the serial port login user. LINE information can be viewed in the show users command. Kicking the user itself is not supported.<\/p>\n
SWITCH#show users<\/code><\/pre>\nType Line User Idle Host<\/h2>\n
con 0 admin 00:00:03 — vty 0 admin 00:00:11 192.168.64.1 Users display elements are as follows:<\/p>\n
Field<\/h2>\n
illustrate<\/p>\n
Type<\/h2>\n
console or vty<\/p>\n
Line<\/h2>\n
console: fixed 0 vty : 0-7<\/p>\n
User<\/h2>\n
username<\/p>\n
Idle<\/h2>\n
Time in idle state, if the timeout time is exceeded, the terminal automatically exits. Host Login user ip address<\/p>\n
Examples<\/h2>\n
Case 1 : The device enables the telnet service. Only users with the IP address 192.168.64.100 are allowed to access the device through telnet, and other users are denied access.<\/p>\n
SWITCH(config)#telnet-server enable<\/code><\/pre>\nSWITCH(config)#ip-access-list standard 1<\/code><\/pre>\nSWITCH(config-std-acl)#permit host 192.168.64.100<\/code><\/pre>\nSWITCH(config-std-acl)#exit<\/code><\/pre>\nSWITCH(config)#ip telnet access-class 1<\/code><\/pre>\nCase 2 : The device enables the telnet service, and the device only allows one user to log in to the device through telnet at the same time.<\/p>\n
SWITCH(config)#telnet-server enable<\/code><\/pre>\nSWITCH(config)#line vty 1 7<\/code><\/pre>\nSWITCH(config-line)#transport input none<\/code><\/pre>\nSystem Hostname Configuration<\/h2>\n\n- Configuring Hostname<\/li>\n<\/ul>\n
SWITCH(config)# hostname WORD<\/code><\/pre>\nThe name must consist of printable characters and the length cannot exceed 63 bytes. This configuration takes effect immediately.<\/p>\n
Firmware Upgrade<\/h2>\n\n- Firmware Upgrade<\/li>\n<\/ul>\n
SWITCH# upgrade firmware tftp:\/\/SERVER\/FILENAME<\/code><\/pre>\nYou need to build a TFTP server on the terminal, and ensure the two-way interconnection between the terminal and the device network. SERVER: TFTP server IP and the relative address of the server window and the firmware upgrade file. FILENAME: Firmware upgrade file. The firmware upgrade process will take 5-6 minutes, reboot the device to complete the firmware upgrade. Do not power off the device during the upgrade process. Example 1\uff1aThe following examples shows firmware upgrade via tftp. Step 1: As shown in the figure below, SWITCH-A is the device to be upgraded, and the telnet function is enabled; USER-A is the host on the same network segment in the LAN, and USER-B is the management device in the LAN, both of which can log in to SWITCH-A by telnet.<\/p>\n
Firmware upgrade connection diagram<\/h2>\n
Step 2: Select USER-B to perform the version upgrade operation. Open the TFTP server on USER-B and place the upgrade file xcat-release-3.2.0.bin in the Y:\/workspace directory.TFTP server as shown in the figure below.<\/p>\n
TFTP Server<\/h2>\n
Step 3: USER-B telnet logs in to SWITCH-A and executes the upgrade command in privileged mode. Upgrade information as shown in the figure below.<\/p>\n
Upgrade Information<\/h2>\n
Step 4: After the upgrade is over, select "y" to restart the device to complete the upgrade, select "n" to continue running the device, and the upgrade operation will be completed after restart.<\/p>\n
System Data And Time Configuration<\/h2>\n\n- Setting the System Clock<\/li>\n<\/ul>\n
SWITCH# clock set HH:MM:SS DAY MON YEAR<\/code><\/pre>\nSetting the system clock. For example\uff1aClock set 15:30:00 1 october 2017.<\/p>\n
SWITCH(config)# ntp server {A.B.C.D | ipv6 X.X::X.X }<\/code><\/pre>\nConfigure the IP address of the NTP server (domain name configuration is not supported). After the configuration is complete, if the device and the server are connected to the network, the device will automatically synchronize the time information from the server. It takes about 4-8 minutes to complete the time synchronization for the first time.<\/p>\n
SWITCH(config)# clock timezone ZONE<\/code><\/pre>\nConfigure the system time zone. The default timezone is UTC. Supports standard time zone configuration, such as Shanghai time zone keyword "Shanghai", Hong Kong time zone keyword "Hong_Kong", etc.<\/p>\n
SWITCH# show clock<\/code><\/pre>\nDisplay system clock.<\/p>\n
SWITCH# show ntp status<\/code><\/pre>\nDisplay ntp status.<\/p>\n","protected":false},"excerpt":{"rendered":"
Networking \u203a Switching \u203a Edge \u203a Synapse<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":6349,"menu_order":1,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[115,119,116],"class_list":["post-6350","docs","type-docs","status-publish","hentry","doc_tag-connexite","doc_tag-network","doc_tag-synapse-cli-documentation","no-post-thumbnail"],"acf":[],"_links":{"self":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6350","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/comments?post=6350"}],"version-history":[{"count":1,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6350\/revisions"}],"predecessor-version":[{"id":6398,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6350\/revisions\/6398"}],"up":[{"embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/docs\/6349"}],"wp:attachment":[{"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/media?parent=6350"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/docs.connexite.co.uk\/index.php\/wp-json\/wp\/v2\/doc_tag?post=6350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}