Table of Contents

1 Introduction· 1-1

Introduction to the Manual 1-1

Related Manuals· 1-1

Volume Introduction· 1-1

2 Feature Description· 2-1

Overview· 2-1

Feature Index· 2-1

Feature Description· 2-2

Access Volume· 2-3

IP Services Volume· 2-4

IP Routing Volume· 2-6

MPLS&VPN Volume· 2-8

QoS Volume· 2-9

Security Volume· 2-9

System Volume· 2-11

IP Multicast Volume· 2-14

OAA Volume· 2-16

3 Login Method and User Interface Overview·· 3-1

Local Login Through the Console Port 3-1

Telneting to the Router Through the Ethernet Interface· 3-3

Introduction to User Interface· 3-4

User Interface Supported on SR6600 Routers· 3-4

User Interface Numbering for the Router 3-4

4 Maintaining Software· 4-1

Router Software and Functions· 4-1

Files· 4-1

BootWare Program File· 4-1

Application Files· 4-1

Configuration Files· 4-2

Software Maintenance Methods· 4-3

BootWare Menu· 4-5

BootWare Main Menu· 4-5

Serial Sub-menu· 4-8

Ethernet Sub-menu· 4-8

File Control Sub-menu· 4-9

BootWare Operation Sub-menu· 4-10

Storage Device Operation Sub-menu· 4-10

Upgrading Applications and BootWare Through a Serial Interface· 4-11

Introduction to XMODEM·· 4-11

Modifying Serial Interface Parameters· 4-11

Upgrading an Application· 4-13

Upgrading BootWare· 4-15

Upgrading an Application and BootWare Using TFTP· 4-17

Upgrading an Application Using TFTP on the BootWare Menu· 4-18

Upgrading and Backing Up an Application Using TFTP Through Command Lines· 4-20

Upgrading an Application and BootWare Using FTP· 4-22

Upgrading an Application Using FTP Through the BootWare Menu· 4-23

Upgrading and Backing Up an Application Using FTP Through Command Lines· 4-24

Updating Applications for the Standby MPU (on an SR6616 Router) 4-29

Method I 4-29

Method II 4-30

Method III 4-30

Method IV· 4-32

Maintaining Application and Configuration Files· 4-33

Displaying All Files· 4-34

Setting Application File Attributes· 4-35

Setting Configuration File Attributes· 4-36

Deleting a File· 4-38

Dealing With Password Loss· 4-39

BootWare Password Loss· 4-39

User Password Loss· 4-40

BootWare Password Loss· 4-41

Super Password Loss· 4-42

Backing Up and Restoring BootWare· 4-42

Backing Up the Full BootWare· 4-43

Restoring the Full BootWare· 4-43

5 Arranging Slots and Numbering Interfaces· 5-1

SR6602 Slot Arrangement and Interface Sequence Number 5-1

Slot Arrangement 5-1

Numbering Interfaces· 5-1

Example· 5-1

SR6604/6608 Slot Arrangement and Interface Sequence Number 5-2

Slot Arrangement 5-2

Numbering Interfaces· 5-3

Examples· 5-3

SR6616 Slot Arrangement and Interface Sequence Number 5-4

Slot Arrangement 5-4

Slot Arrangement on the MPU and FIP· 5-6

Numbering Interfaces· 5-6

Examples· 5-6

 

 

 

Introduction to the Manual

You can get the contents of this manual by reading the following:

l          Feature Description: Introduces the main features of each module presented in this manual.

l          Login Method and User Interface Overview: Helps you know about the user interfaces supported on the H3C SR6600 routers and how to log in or telnet through the console port or the Ethernet interface.

l          Maintaining Software: Introduces software upgrade and maintenance methods of the SR6600 routers and how to deal with password loss, helping you familiar with software upgrade and configuration file maintenance in all modes.

l          Arranging Slots and Numbering Interfaces: Helps you find the slot position with a diagram when you are maintaining the router.

Related Manuals

l          For the installation, startup and configuration, software maintenance, hardware maintenance, functions of interface card and interface module, cable connection and troubleshooting of the router, refer to H3C SR6602 Router  Installation Manual, H3C SR6604/6608 Router  Installation Manual and H3C SR6616 Router  Installation Manual.

l          For all cable pinouts available with SR6600 routers, refer to LMR Series Routers  Cable Manual.

You can log in to http://www.h3c.com to get product documentation of the newest version in the following way:

On the homepage of H3C at http://www.h3c.com, select Technical Support & Document > Technical Documents from the navigation menu at the top. Then select a product for its documents.

Volume Introduction

Software features on the H3C SR6600 routers are introduced in ten volumes as the following:

l          Access Volume: Configuration of interfaces and link layer protocols supported on the router.

l          IP Services Volume: Configuration of IP-related features such as IP address, ARP, DNS, DHCP, IP performance, IP unicast routing, ACL, and IPv6.

l          IP Routing Volume: Configuration of routing protocols such as static route, RIP, RIPng, OSPF, OSPFv3, IS-IS, BGP, BGP4+ and routing policy.

l          MPLS&VPN Volume: Configuration of MPLS and VPN related protocols such as MPLS, MPLS TE, GRE, MPLS L3VPN, and MPLS L2VPN.

l          QoS Volume: Configuration of QoS related protocols and features supported on the router, such as traffic classification, policing, and shaping, QoS policy, congestion management, congestion avoidance, MPLS QoS and Frame Relay QoS.

l          Security Volume: Configuration of security protocols such as AAA, user management, firewall, NAT, IPsec, IKE, RADIUS, and HWTACACS.

l          System Volume: Configuration of system-related protocols and features such as basic system configuration, user login, file system management, system maintenance, NTP, SNMP, RMON, and VRRP.

l          IP Multicast Volume: Configuration of IP multicast-related protocols such as IGMP, PIM, MSDP, and multicast VPN.

l          OAA Volume: Configuration of OAA-related protocols such as ACFP and OAP module.

 

Overview

H3C SR6600 Routers include: SR6602, SR6604, SR6608 and SR6616. SR6602 are centralized devices which can be used as distribution and access devices for service gateways with high performance and commercial business networks, SR6604, SR6608 and SR6616 are distributed devices which can be used as core, distribution and access devices for large networks, and core devices for small to medium-sized enterprise networks.

Feature Index

Table 2-1 Feature index of SR6600 routers

Functional module	Feature
Access Volume	CPOS Interface	POS Interface	Ethernet Interface	WAN Interface
	Frame Relay	HDLC	PPP	Logical Interface
	MODEM Management	ATM Interface	ATM	E-CPOS Interface
	VLAN Termination
IP Services Volume	ARP	DHCP	DNS	IP Addressing
	IP Performance Optimization	IP Unicast Policy Routing	URPF	IPv6 Basics
	Adjacency Table	Flow Classification	IP Virtual Fragment Reassembly	Dual Stack
	Tunneling	UDP Helper	DHCPv6	IPv6 Unicast Policy Routing
	NAT-PT
IP Routing Volume	IP Routing Overview	BGP	IS-IS	OSPF
	RIP	Route Policy	Static Routing	IPv6 BGP
	IPv6 IS-IS	OSPFv3	RIPng	IPv6 Static Routing
	BFD
MPLS&VPN Volume	MPLS Basics	MPLS TE	MPLS L2VPN	MPLS L3VPN
	GRE	L2TP
QoS Volume	QoS	FR QoS
Security Volume	AAA	Firewall	ALG	PKI
	Session Management	NAT	ACL	IPsec
	SSH2.0	Portal	Public Key	Web Filtering
	Connection Limit	RSH
System Volume	GR	VRRP	HA	Device Management
	NQA	NetStream	NTP	RMON
	SNMP	File System Management	Basic System Configuration	System Maintaining and Debugging
	Information Center	User Interface	Track	IPv6 NetStream
	Sampler	Hotfix	Telnet	Flow Log
	User Profile
IP Multicast Volume	Multicast Overview	Multicast Routing and Forwarding	IGMP	MSDP
	PIM	Multicast VPN	MBGP	IPv6 Multicast Routing and Forwarding
	MLD	IPv6 PIM	IPv6 MBGP
OAA Volume	OAP Module	ACFP	ACSEI

 

Feature Description

 

 

Access Volume

Table 2-2 Features in access volume

Feature	Operation and command manual	Feature description
CPOS Interface	CPOS Interface Configuration CPOS Interface Commands	l      Introduction to CPOS interface l      CPOS interface configuration l      E1 channel configuration l      T1 channel configuration l      E3 channel configuration l      T3 channel configuration
POS Interface	POS Interface Configuration POS Interface Commands	POS configuration and introduction
Ethernet Interface	Ethernet Interface Configuration Ethernet Interface Commands	Combo and Layer 3 Ethernet interface introduction
WAN Interface	WAN Interface Configuration WAN Interface Commands	Introduction to WAN interfaces such as synchronous serial interface, AUX, and CE1
Frame Relay	Frame Relay Configuration Frame Relay Commands	l      FR DCE/DTE configuration l      Multilink FR configuration
HDLC	HDLC Configuration HDLC Commands	HDLC configuration
PPP	PPP and MP Configuration PPP and MP Commands	l      PPP configuration l      MP configuration l      PPP link efficiency mechanism configuration l      PPPoE configuration
Logical Interface	Logical Interface Configuration Logical Interface Commands	l      Loopback interface configuration l      Null interface configuration l      Sub-interface configuration l      MP-group interface configuration l      MFR interface configuration l      VT and VA interface configuration
Modem Management	Modem Management Configuration Modem Management Commands	l      Modem management configuration
ATM Interface	ATM Interface Configuration ATM Interface Commands	l      Introduction to interfaces such ATM OC-3c/STM-1 interface
ATM	ATM Configuration ATM Commands	l      ATM interface, ATM subinterface, PVC and VP policing configuration l      Overview of IPoA, IPoEoA, PPPoA and PPPoEoA applications
E-CPOS Interface	E-CPOS Interface Configuration E-CPOS Interface Commands	l      Introduction to E-CPOS interface l      E-CPOS interface configuration l      E-CPOS interface configuration example
VLAN Termination	VLAN Termination Configuration VLAN Termination Commands	l      Introduction to VLAN termination l      Configuring TPID for VLAN packets l      Enabling VLAN-termination-enabled subinterfaces to transmit broadcast/multicast packets l      Configuring Dot1q termination
Port Mirroring	Port Mirroring Configuration Port Mirroring Commands	l      Configuring Local Port Mirroring l      Configuring Layer 2 Remote Port Mirroring l      Traffic Mirroring Configuration
Return to Feature Index.

 

IP Services Volume

Table 2-3 Features in IP services volume

Feature	Operation and command manual	Feature description
ARP	ARP Configuration ARP Commands	Address resolution protocol, mainly used for resolution from IP address to Ethernet MAC address. l      ARP configuration l      Gratuitous ARP configuration l      Proxy ARP configuration
DHCP	DHCP Configuration DHCP Commands	Dynamic host configuration protocol, implements dynamic configuration for information such as IP address. l      DHCP server configuration l      DHCP relay configuration l      DHCP client configuration
DNS	DNS Configuration DNS Commands	DNS is a distributed database that applies to TCP/IP application programs. It functions to resolve between hostnames and IP addresses. l      Static DNS configuration l      Dynamic DNS configuration
IP Addressing	IP Addressing Configuration IP Addressing Commands	l      IP address configuration l      Assigning an IP address to an interface
IP Performance Optimization	IP Performance Optimization Configuration IP Performance Optimization Commands	In a specific network, IP parameters need to be adjusted to optimize the network performance. l      Enabling receiving and forwarding directed broadcasts l      Configuring TCP timer, buffer size, packet size and ICMP error packets l      Configuring the maximum TCP segment size (MSS) of an interface l      Configuring to send ICMP error packets
IP Unicast Policy Routing	IP Unicast Policy Routing Configuration IP Unicast Policy Routing Commands	Policy routing, selects routes according to policies defined by the user. l      Policy routing configuration
URPF	URPF Configuration URPF Commands	Unicast Reverse Path Forwarding (URPF) protects a network against source address spoofing attacks. l      Configuring URPF
IPv6 Basics	IPv6 Basics Configuration IPv6 Basics Commands	Internet protocol version 6 (IPv6) was designed by the Internet Engineering Task Force (IETF) as the successor to Internet protocol version 4 (IPv4). l      Configuring basic IPv6 functions l      IPv6 NDP configuration l      PMTU discovery configuration l      TCP6 configuration l      IPv6 FIB forwarding configuration l      Configuring the maximum ICMPv6 error packets sent in an interval l      IPv6 DNS configuration
Adjacency Table	Adjacency Table Configuration Adjacency Table Commands	An adjacency table manages the information on the neighbors that are both connected and active.
Flow Classification	Flow Classification Configuration Flow Classification Commands	Flow classification organizes packets with different characteristics into different classes using certain match criteria. It is the basis for providing differentiated services.
IP Virtual Fragment Reassembly	IP Virtual Fragment Reassembly Configuration IP Virtual Fragment Reassembly Commands	To prevent each service module (such as IPsec, NAT and firewall) from processing packet fragments that do not arrive in order, you can enable the virtual fragment reassembly feature, which can virtually reassemble the fragments of a datagram through fragment check, sequencing and caching, ensuring fragments arriving at each service module is in order.
Dual Stack	Dual Stack Configuration	A network node that supports both IPv4 and IPv6 is called a dual stack node. A dual stack node configured with an IPv4 address and an IPv6 address can have both IPv4 and IPv6 packets transmitted. l      Dual stack configuration
Tunneling	Tunneling Configuration Tunneling Commands	Tunneling is an encapsulation technology, which utilizes one network protocol to encapsulate packets of another network protocol and transfer them over the network. Tunneling refers to the whole process from data encapsulation to data transfer to data de-encapsulation. l      IPv6 manual tunnel configuration l      Automatic IPv4-compatible IPv6 tunnel configuration l      6to4 tunnel configuration l      ISATAP tunnel configuration l      IPv4 in IPv4 tunnel configuration l      IPv6 in IPv6 tunnel configuration l      IPv4 in IPv6 tunnel configuration l      6PE configuration
UDP Helper	UDP Helper Configuration UDP Helper Commands	UDP Helper functions as a relay agent that converts UDP broadcast packets into unicast packets and forwards them to a specified destination server. l      Introduction to UDP Helper l      UDP Helper configuration
DHCPv6	DHCPv6 Configuration DHCPv6 Commands	The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) was designed based on IPv6 addressing scheme and is used for assigning IPv6 addresses and other configuration parameters to hosts. l      Typical DHCPv6 network application l      Operation of DHCPv6 l      Configuring the DHCPv6 relay agent
IPv6 Unicast Policy Routing	IPv6 Unicast Policy Routing Configuration IPv6 Unicast Policy Routing Commands	Policy routing, also known as policy based routing (PBR), is a routing mechanism based on the user-defined policies. l      Introduction to IPv6 unicast policy routing l      Configuring IPv6 unicast policy routing
NAT-PT	NAT-PT Configuration NAT-PT Commands	Network Address Translation – Protocol Translation (NAT-PT) was introduced to realize translation between IPv4 and IPv6 addresses. l      NAT-PT mechanism l      Configuring NAT-PT
Return to Feature Index.

 

IP Routing Volume

Table 2-4 Features in IP routing volume

Feature	Operation and command manual	Feature description
IP Routing Overview	IP Routing Overview IP Routing Table Commands	IP routing overview l      IP routing overview l      IP routing and routing table l      Routing through a routing table
BGP	BGP Configuration BGP Commands	A dynamic inter-AS route discovery protocol l      Configuring BGP basic functions l      Configuring BGP routing attributes l      Configuring a large-scale BGP network
IS-IS	IS-IS Configuration IS-IS Commands	An interior gateway protocol (IGP) used within an Autonomous System. It adopts the Shortest Path First (SPF) algorithm for route calculation. l      Configuring ISIS basic functions l      Configuring ISIS routing information control
OSPF	OSPF Configuration OSPF Commands	An interior gateway protocol based on link state l      Configuring OSPF basic functions l      Configuring OSPF area parameters l      Configuring OSPF network types l      Configuring OSPF routing information management
RIP	RIP Configuration RIP Commands	A simple Interior Gateway Protocol mainly used in small-sized networks l      Configuring RIP basic functions l      Configuring RIP advanced functions
Route Policy	Route Policy Configuration Route Policy Commands	A route policy is used to change the route that network traffic passes. l      Defining filtering lists l      Configuring a route policy
Static Routing	Static Routing Configuration Static Routing Commands	A special route that is manually configured by the network administrator. The proper configuration and usage of static routes can improve a network’s performance and ensure bandwidth for important network applications. l      Configuring a static route l      Application
IPv6 BGP	IPv6 BGP Configuration IPv6 BGP Commands	BGP4+ puts IPv6 network layer information into the attributes of Network Layer Reachable Information (NLRI) and NEXT_HOP. l      Configuring BGP4+ basic functions l      Controlling route distribution and reception l      Configuring BGP4+ route attributes
IPv6 IS-IS	IPv6 IS-IS Configuration IPv6 IS-IS Commands	Supports multiple network protocols, including IPv6 and supports two Type-Length-Values (TLVs) and a new Network Layer Protocol Identifier (NLPID) l      Configuring IPv6-IS-IS basic functions l      Configuring IPv6-IS-IS routing information control
OSPFv3	OSPFv3 Configuration OSPFv3 Commands	OSPF protocol supporting IPv6 l      Configuring OSPFv3 basic functions l      Configuring OSPFv3 area parameters l      Configuring OSPFv3 routing information management
RIPng	RIPng Configuration RIPng Commands	An extension of RIP-2 for IPv4 l      Configuring RIPng basic functions l      Configuring RIPng advanced functions
IPv6 Static Routing	IPv6 Static Routing Configuration IPv6 Static Routing Commands	Special routes that are manually configured by network administrators work well in simple networks. l      Configuring IPv6 static routes
BFD	BFD Configuration BFD Commands	Bidirectional forwarding detection (BFD) provides a single mechanism to quickly detect and monitor the connectivity of links in networks. l      BFD basic functions configuration l      Protocol-based BFD configuration
Return to Feature Index.

 

MPLS&VPN Volume

Table 2-5 Features in MPLS&VPN volume

Feature	Operation and command manual	Feature description
MPLS Basics Configuration	MPLS Basics Configuration MPLS Basics Commands	l      MPLS configuration basics l      LDP overview l      Configuring MPLS basic capability l      Configuring PHP l      Configuring a static LSP l      Configuring MPLS LDP l      Configuring LDP instances l      Configuring MPLS TTL processing
MPLS TE	MPLS TE Configuration MPLS TE Commands	l      MPLS TE overview l      Configuring MPLS TE basic capabilities l      Creating MPLS TE tunnel over static CR-LSP l      Configuring MPLS TE tunnel with dynamic signaling protocol l      Configuring RSVP-TE advanced features l      Tuning CR-LSP setup l      Tuning MPLS TE tunnel setup l      Configuring traffic forwarding l      Configuring traffic forwarding tuning parameters l      Configuring automatic bandwidth adjustment l      Configuring CR-LSP backup l      Configuring FRR
MPLS L2VPN	MPLS L2VPN Configuration MPLS L2VPN Commands	Supports multiple link-layer protocols to provide L2VPN services based on different media on an MPLS network. l      Configuring MPLS L2VPN l      Configuring CCC MPLS L2VPN l      Configuring SVC MPLS L2VPN l      Configuring Martini MPLS L2VPN l      Configuring Kompella MPLS L2VPN
MPLS L3VPN	MPLS L3VPN Configuration MPLS L3VPN Commands	MPLS VPN is a L3VPN technology based on PE in a VPN solution for carriers. l      Configuring VPN instances l      Configuring basic BGP/MPLS VPN l      Configuring Inter-Provider VPN l      Configuring Multi-Role Host l      Configuring HoVPN l      Configuring OSPF Sham Link l      Configuring multi-VPN-instance CE l      Configuring BGP AS number substitution
GRE	GRE Configuration GRE Commands	A protocol designed for performing encapsulation of one network layer protocol over another network layer protocol. l      GRE overview l      Configuring a GRE over IPv4 tunnel
L2TP	L2TP Configuration L2TP Commands	Defines an encapsulation mechanism for transporting multiprotocol packets over Layer 2 (L2) point-to-point links l      LAC configuration l      LNS configuration
Return to Feature Index.

 

QoS Volume

Table 2-6 Features in QoS volume

Feature	Operation and command manual	Feature description
QoS	QoS Configuration QoS Commands	Quality of service, evaluates the service performance for those network core requirements during packet transmission process, such as: delay, jitter and packet loss ratio. Peak rate and hardware queues are not supported. l      Traffic classification, policing, and shaping l      QoS policy configuration l      Congestion management l      Congestion avoidance l      MPLS QoS configuration
FR QoS	FR QoS Configuration FR QoS Commands	On a FR interface, you can use general QoS services to provide the services such as TP, TS, congestion management, and congestion avoidance.
Return to Feature Index.

 

Security Volume

Table 2-7 Features in security volume

Feature	Operation and command manual	Feature description
AAA	AAA Configuration AAA Commands	Authentication, authorization and accounting (AAA) provide a uniform framework used for configuring these three security functions to implement the network security management. l      AAA configuration l      RADIUS configuration l      HWTACACS configuration
Firewall	Firewall Configuration Firewall Commands	Firewall can prevent unauthorized or unauthenticated users on the Internet from accessing a protected network while allowing the users on the internal network to access web sites on the Internet and transceive E-mails. l      Configuring a packet filter firewall l      Configuring an ASPF
ALG	ALG Configuration ALG Commands	The application level gateway (ALG) feature is used to process application layer packets.
PKI	PKI Configuration PKI Commands	Public key infrastructure (PKI) is a system which uses public key technology and digital certificate to protect system security and authenticate digital certificate users. l      Generating an RSA pair for PKI l      Configuring PKI certificate registration l      Submitting a PKI certificate request l      Configuring PKI certificate validation l      Configuring access control policy of certificate attribute
Session Management	Session Management Configuration Session Management Commands	The session management feature is a common feature designed to implement session-based services such as network address translation (NAT), application specific packet filter (ASPF), and intrusion protection. l      Session management configuration l      Specifying the permanent session ACL
NAT	NAT Configuration NAT Commands	Network Address Translation (NAT) is to translate the IP address in IP data packet header into another IP address, which is mainly used to implement private network accessing external network in practice. l      Configuring EASY IP l      Configuring static NAT l      Configuring many-to-many NAT l      Configuring many-to-one NAPT l      Configuring internal server l      Configuring NAT Log l      Configuring connection limit
ACL	ACL Configuration ACL Commands	Access Control List, used to implement flow identification. Flow template is not supported. l      Configuring effective period of an  IPv4 ACL l      Basic IPv4 ACL configuration l      Advanced IPv4 ACL configuration l      Basic IPv6 ACL configuration l      Advanced IPv6 ACL configuration
IPsec	IPsec Configuration IPsec Commands	Layer 3 tunnel encryption protocol defined by IETF, which provides security for IP data packets transmitted on the Internet. l      Configuring an IPsec proposal l      Configuring an IPsec policy l      Configuring an IPsec policy template l      Applying an IPsec policy l      Configuring an IKE proposal l      Configuring an IKE peer l      Configuring IKE keepalive timer
SSH2.0	SSH2.0 Configuration SSH2.0 Commands	Security shell. When routers are connected by remote users across insecure networks, secure shell (SSH) can provide them authentication and security. l      Configuring the SSH server l      Configuring the SSH client l      Configuring the device as an SSH client
Portal	Portal Configuration Portal Commands	Portal authentication is also called web authentication and a website implementing portal authentication is called a portal website.
Public Key	Public Key Configuration Public Key Commands	l      Local asymmetric key pair configuration l      The public key of a peer configuration
Web Filtering	Web Filtering Configuration Web Filtering Commands	l      URL address filtering l      URL parameter filtering l      Java blocking l      ActiveX blocking l      Filtering rule saving and loading
Connection Limit	Connection Limit Configuration Connection Limit Commands	To protect internal network resources (hosts or servers) and better utilize system resources of the device, you can configure connection limit policies to collect statistics on and limit the number of connections. l      Creating a connection limit policy l      Configuring the connection limit policy l      Applying the connection limit policy
RSH	RSH Configuration RSH Commands	Remote shell (RSH) allows you to execute the internal and external commands provided by the operating system (OS) on a remote host that runs the RSH daemon.
Return to Feature Index.

 

System Volume

Table 2-8 Features in system volume

Feature	Operation and command manual	Feature description
GR	GR Overview	Graceful restart. When routing protocol is restarted, the forwarding service will not be terminated. l      Supports only FIB6, IS-IS and BGP protocol-level GR
VRRP	VRRP Configuration VRRP Commands	Virtual routing redundancy protocol, with which the system can still provide highly reliable default links without changing configurations when a device fails.
HA	HA Configuration HA Commands	High Availability, used to implement high availability of the system.
Device Management	Device Management Configuration Device Management Commands	Through the device management function, users can view the current working state of devices, configure operation parameters, and perform daily device maintenance and management. Validity check of Boot ROM is not supported. l      Configuring device management
NQA	NQA Configuration NQA Commands	Network Quality Analyzer (NQA) analyzes network performance, services and service quality with probing tools and provides test results. It is an enhancement and extension of the Ping tool. Perform the following tasks to configure NQA: l      NQA tests configuration l      Optional NQA parameters configuration
NetStream	NetStream Configuration NetStream Commands	NetStream provides the packet statistics function. l      Configuring NetStream statistics l      Configuring NetStream aggregation statistics l      Configuring attributes of NetStream UDP packets l      Configuring NetStream statistics aging
NTP	NTP Configuration NTP Commands	Network time protocol, used for time synchronization between distributed time server and the client. l      Configuring the operation modes of NTP l      Configuring the local clock as a reference source l      Configuring optional parameters of NTP l      Configuring access-control rights l      Configuring NTP authentication
RMON	RMON Configuration RMON Commands	Remote monitoring, making SNMP monitor remote network devices more effectively and proactively. l      RMON configuration
SNMP	SNMP Configuration SNMP Commands	Simple network management protocol, a frame using TCP/IP protocol suite to manage devices on the Internet l      Configuring SNMP basic functions l      Configuring Trap
File System Management	File System Management Configuration File System Management Commands	Manages storage devices and store files in these devices. l      File system management configuration l      Configuring FTP l      Configuring TFTP
System Maintenance and Debugging	System Maintenance and Debugging Configuration System Maintenance and Debugging Commands	For the protocols and features supported on the device, the system provides corresponding debugging functions to help users diagnose and locate errors l      Configuring system debugging l      Configuring ping and tracert
Basic System Configuration	Basic System Configuration Basic System Configuration Commands	l      Basic system configuration
Information Center	Information Center Configuration Information Center Commands	Acting as the system information hub, information center classifies and manages system information. l      Configuring the information center
User Interface	User Interface Configuration User Interface Commands	User interface view is a feature that allows you to manage asynchronous serial interfaces that work in flow mode. By operating under user interface view, you can centralize the management of various configurations. l      Configuring asynchronous interface attributes l      Configuring terminal attributes l      Configuring modem attributes l      Configuring the auto-execute command l      Configuring user privilege level l      Configuring access restriction to VTY user interfaces l      Configuring supported protocols on VTY user interfaces l      Configuring redirection function on the asynchronous serial interface l      Configuring authentication mode at login
Track	Track Configuration Track Commands	The Track module is used to implement collaboration between different modules. The collaboration here involves three parts: the application modules, the Track module, and the detection modules. Perform the following tasks to configure track: l      Track overview l      Configuration of collaboration between the track module and NQA l      Configuration of collaboration between the track module and the application modules
IPv6 NetStream	IPv6 NetStream Configuration IPv6 NetStream Commands	IPv6 NetStream provides the packet statistics function. It differentiates IPv6 flows based on destination address, source IP address, destination port number, source port number, protocol number, stream tag, and/or inbound/outbound interface, it collects statistics on a per-flow basis. l      IPv6 NetStream statistics configuration l      IPv6 NetStream aggregation configuration l      Configuration of attributes of IPv6 NetStream data l      IPv6 NetStream flow aging configuration
Sampler	Sampler Configuration Sampler Commands	A sampler provides the packet sampling function, that is, a sampler selects a packet from a group of packets with fixed number, and sends it to the service module for processing.
Hotfix	Hotfix Configuration Hotfix Commands	Hotfix is a fast and cost-effective method to repair software defect of a device. Compared with another method, software version upgrade, hotfix can upgrade the software without interrupting the running services of the device, that is, it can repair the software defect of the current version without rebooting the device. This module introduces the configuration and application of Hotfix.
Telnet	Telnet Configuration Commands	This module introduces the command lines used in telnet.
Flow Log	Flow Log Configuration Flow Log Commands	Flow logs record the flow information about the users’ access to the extranet. l      Flow log versions configuration l      Configuration of the source address for flow log packets l      Exporting flow logs
User Profile	User Profile Configuration User Profile Commands	User profile provides a configuration template to save predefined configurations. Based on different application scenarios, you can configure different items for a user profile. l      Creating a user profile l      Configuring a user profile l      Enabling a user profile
Return to Feature Index.

 

IP Multicast Volume

Table 2-9 Features in IP Multicast Volume

Feature	Operation and command manual	Feature description
Multicast Overview	Multicast Overview	Multicast overview, and Layer 2 multicast is not supported. l      Multicast models l      Multicast architecture l      Multicast packet forwarding mechanism
Multicast Routing and Forwarding	Multicast Routing and Forwarding Configuration Multicast Routing and Forwarding Commands	Policies used for filtering the routing information used in the RPF check l      Multicast policy overview l      Configuring a multicast policy
IGMP	IGMP Configuration IGMP Commands	As a TCP/IP protocol responsible for IP multicast group member management, the Internet Group Management Protocol (IGMP) is used by IP hosts to establish and maintain their multicast group memberships to immediately neighboring multicast routers. l          Configuring basic functions of IGMP l      Adjusting IGMP performance
MSDP	MSDP Configuration MSDP Commands	Multicast source discovery protocol (MSDP) is an inter-domain multicast solution developed to address the interconnection of protocol independent multicast sparse mode (PIM-SM) domains. It is used to discover multicast source information in other PIM-SM domains. l          Configuring basic functions of MSDP l          Configuring an MSDP peer connection l          Configuring SA messages related parameters
PIM	PIM Configuration PIM Commands	Protocol Independent Multicast (PIM) provides IP multicast forwarding by leveraging static routes or unicast routing tables generated by any unicast routing protocol. l      Configuring PIM-DM l      Configuring PIM-SM l      Configuring PIM-SSM l      Configuring PIM command features
Multicast VPN	Multicast VPN Configuration Multicast VPN Commands	l      Multicast VPN overview l      How MD-VPN works l      Configuring MD-VPN
MBGP	MBGP Configuration MBGP Commands	BGP-4 is capable of carrying routing information for IPv4 only. IETF defined multiprotocol BGP extensions to carry routing information for multiple network layer protocols. l      Configuring MBGP basic functions l      Configuring MBGP route attributes l      Tuning and optimizing MBGP networks l      Configuring a large scale MBGP network
IPv6 Multicast Routing and Forwarding	IPv6 Multicast Routing and Forwarding Configuration IPv6 Multicast Routing and Forwarding Commands	l      Introduction to IPv6 multicast routing and forwarding l      Enabling IPv6 multicast routing l      Configuring IPv6 multicast routing and forwarding
MLD	MLD Configuration MLD Commands	The Multicast Listener Discovery protocol (MLD) is used by an IPv6 router to discover the presence of multicast listeners on the directly attached subnets. Multicast listeners are nodes wishing to receive IPv6 multicast packets. l      Configuring basic functions of MLD l      Adjusting MLD performance l      Configuring MLD SSM mapping l      Configuring MLD proxying
IPv6 PIM	IPv6 PIM Configuration IPv6 PIM Commands	Protocol Independent Multicast for IPv6 (IPv6 PIM) provides IPv6 multicast forwarding by leveraging static routes or IPv6 unicast routing tables generated by any IPv6 unicast routing protocol. l      Configuring IPv6 PIM-DM l      Configuring IPv6 PIM-SM l      Configuring IPv6 PIM-SSM l      Configuring IPv6 PIM common features
IPv6 MBGP	IPv6 MBGP Configuration IPv6 MBGP Commands	l      IPv6 MBGP overview l      IPv6 MBGP configuration task list l      Configuring IPv6 MBGP basic functions l      Controlling route distribution and reception l      Configuring IPv6 MBGP route attributes l      Tuning and optimizing IPv6 MBGP networks l      Configuring a large scale IPv6 MBGP network
Return to Feature Index.

 

OAA Volume

Table 2-10 Features in OAA Volume

Feature	Operation and command manual	Feature description
OAP Module	OAP Module Configuration OAP Module Commands	Open Application Platform (OAP) is an open application platform aimed at new services. Users can load software such as security and voice in the operating system as needed.
ACFP	ACFP Configuration ACFP Commands	The Application Control Forwarding Protocol (ACFP) is developed based on the OAA architecture.
ACSEI	ACSEI Configuration ACSEI Commands	As a private protocol, ACSEI provides a method for exchanging information between ACFP clients and ACFP server. It well supports Application Control Forwarding Protocol (ACFP) collaboration, ensuring valid information interaction between the ACFP clients and the ACFP server, so that the ACFP server and clients can cooperate to run a service.
Return to Feature Index.

 

You can log in to the SR6600 routers in the following ways:

l          Local login through console port

l          Telneting to the router through an Ethernet interface

l          Remote login through AUX port or TTY port using Modem dialup

l          Login through NMS

Local login through console port and telneting to the router through an Ethernet interface are the most frequently used login methods in application. In this manual we introduce these two login methods in detail.

Local Login Through the Console Port

Setting up local configuration environment

To set up the local configuration environment, RJ-45 connector of the console cable needs to be connected to the console port on the router, and DB-9 connector to the serial interface of a PC, as shown in the following figure.

Figure 3-1 Local login through the console port

(1) Console port (CONSOLE)	(2) DB9 (female) connector
(3) Serial interface of the terminal	(4) Console cable
(5) RJ-45 connector

 

Setting the parameters for the console terminal

Set terminal parameters, taking the hyper terminal on Windows as an example. In the Serial Attribute dialog box, set the baud rate to 9600, data bit to 8, no parity check, stop bit to 1, and flow control to none. As shown in the following figure:

Figure 3-2 Setting serial interface parameters

 

Select the terminal emulation type to be VT100 or auto detect.

Figure 3-3 Setting terminal type

 

After setting all parameters, click Enter, and you can configure the router.

Telneting to the Router Through the Ethernet Interface

Setting up configuration environment

Connect the router to a network through the Ethernet interface.

Figure 3-4 Telnet to the server

 

Configuring the router

Before you perform remote login to the router, you must configure the router. You must perform local configuration through Console port when you first configure the router.

Perform the following configuration on the router:

# Enter system view.

Press ENTER to get started.

<H3C>system-view

# Enable Telnet server.

[H3C]telnet server enable

% Start Telnet server

# Configure the IP address of the interface that connects to the Internet. You can change this IP address to what is in use.

[H3C]interface GigabitEthernet0/0

[H3C-GigabitEthernet0/0] ip address 192.168.0.1 24

# Enter VTY interface view.

[H3C]user-interface vty 0

# Set login password to 123456 and priority to 2.

[H3C-ui-vty0]set authentication password cipher 123456

[H3C-ui-vty0]user privilege level 2

Logging in to the router

Ensure the reachability between the terminal and the router, and then you can log in to the router remotely.

<H3C> telnet 192.168.0.1 24

Trying 192.168.0.1 ...

Press CTRL+K to abort

Connected to 192.168.0.1 ...

**************************************************************************

* All rights reserved (2004-2006)                                            *

* Without the owner's prior written consent,                                 *

* no decompiling or reverse-engineering shall be allowed.                    *

**************************************************************************

 

 

Login authentication

 

 

Password:

<H3C> system-view

[H3C]

Enter password 123456 when the system prompts entering the password. You can perform operations on the router after entering the correct password.

 

 

Introduction to User Interface

User Interface Supported on SR6600 Routers

Table 3-1 Introduction to user interface

User interface	Corresponding user	Port type	Description
Console user interface	User logging through console port	Console port	There is only one console user for each router
AUX user interface	User logging through AUX port	AUX port	There is only one AUX user for each router
VTY user interface	Telnet user and SSH user	Ethernet interface	Up to 5 VTY users can be supported by each router.

 

User Interface Numbering for the Router

User interfaces of the system falls into three categories, and is arranged in certain order:

They are console (CON), Auxiliary port (AUX), and virtual interface (VTY). There is only one user interface for console and auxiliary port, while multiple user interfaces for VTY interface, each type of these multiple user interfaces being arranged in order.

User interface is numbered in the following two ways: absolute number and relative number.

1)        Absolute number

The beginning number of absolute number is 0 (namely, console port), and the rest interfaces can be deduced by analogy. Console port and AUX port occupy one number respectively; For VTY interface, different products support different numbers of user interfaces. Use the display user-interface command to view them. Absolute number can uniquely specify one user interface or one group of user interfaces.

l          Console user interface is numbered 0.

l          AUX user interface is numbered 1.

l          VTY user interface is numbered after AUX user interface. Absolute number of the first VTY is 2 (namely, VTY 0), the absolute number of the (n+2) VTY is (n+1) (namely, VTY n-1), and so on.

2)        Relative number

Relative number, represented by “+ number” assigned to each type of user interface. It follows the rules below:

l          Console user interface is numbered CON 0.

l          AUX user interface is numbered AUX 0.

l          Number of VTY user interface: The first VTY user interface is designated as VTY0, the second one is designated as VTY1 and so on.

 

 

 

Router Software and Functions

Files

Three types of files need to be managed on the SR6608. They are:

l          BootWare program file

l          Application file

l          Configuration file

BootWare Program File

The BootWare program file is used for booting applications when a router starts and is saved on the Flash. A full BootWare program file includes two segments: basic and extended.

l          Basic segment is used to finish the basic system initialization.

l          Extended segment provides abundant human-computer interaction (HCI) functions and is used to initialize network interfaces, upgrade the applications, and boot the system.

l          After the basic segment is booted, you can load and upgrade the extended segment on the menu of the basic segment.

Application Files

The SR6608 supports the Dual Image function. By default, the system defines three application files for boot.

l          Main application file (with the attribute of M)

l          Backup application file (with the attribute of B)

l          Secure application file (with the attribute of S)

The three kinds of application files are stored on the CF card.

These three types of application files are stored in a CF card. By default, they are written into the built-in CF card before delivery.

If you have uploaded all the three types of application files into the CF card, the system will boot using these three files in order. For more information about application files, refer to section Maintaining Application and Configuration Files.

The following gives the default names and types of the application files and their priorities for booting.

l          Main application file. The default name is main.bin. It is the default application file used for booting.

l          Backup application file. The default name is backup.bin. When the boot using the main application file fails, the system boots using the backup application file.

l          Secure application file. The default name is secure.bin. When the boot using the main and backup application files fails, the system boots using the secure application file. If the boot using the secure application file fails, the system prompts a boot failure.

Note that:

l          An application file with the attribute of M, B, or S can be used to boot the system, but one with an attribute denoted by N/A (that is, an application file without a specific attribute assigned to it) cannot.

l          You can modify the name of an application file using a command after the application boots.

l          You can modify the attribute of application files using the BootWare menu or the command line interface (CLI) after the application is started. As the secure application file is the last resort for system boot, you cannot change its attribute, or turn another type of application file into a secure application file by means of attribute modification. You can only download it using the BootWare menu.

l          Only one application file of the same type (M, B, or S) can exist in the CF card. For instance, if an application file in the CF card has both M and B attributes, no other file with the attribute of M or B can exist in the CF card. If the attribute of another application file is changed from N/A to B, the existing file that has both M and B attributes will lose its B attribute.

Configuration Files

The configuration files are used to store the configuration information of the router and load the configuration information at system boot: If a system supports the main and backup attributes of configuration files, the system defines the following three types of configuration files by default:

l          Main configuration file (with the attribute of M)

l          Backup configuration file (with the attribute of B)

l          Default configuration file (with the attribute of S)

The main and backup configuration files are used as follows:

l          If the main configuration file is damaged or lost, the backup configuration file is used for loading the configuration information. This double protection mechanism enhances the reliability of the file system.

l          When saving the current configuration, you can specify to save it to the main configuration file, the backup configuration file, or a configuration file with the attribute denoted by N/A, namely a configuration file without a specific attribute assigned to it.

l          When deleting a configuration file, you can specify to delete the main or backup configuration file. For a configuration file with both M and B attributes, you can specify its M or B attribute to remove.

l          You can define a configuration file as the one to be used at the next boot by changing its attribute to M.

The secure configuration file is used when the system fails to boot using the main, and then the backup configuration file. Currently the system does not support boot with the secure configuration file.

The system will select the configuration files in order to load configuration information at startup:

l          Uses the main configuration file to initialize the configuration if the main file exists.

l          Uses the backup configuration file to initialize the configuration if the main file does not exist.

l          Boots using the null configuration (default settings) if the backup file does not exist either.

For more information about configuration files, refer to section Setting Configuration File Attributes.

Note that:

l          You can rename a configuration file through the CLI after the application program is loaded.

l          For a system that supports the main and backup configuration file attributes, you can modify file attributes through the BootWare menu or the CLI after the application program is loaded. For detailed information, refer to section Setting Configuration File Attributes.

l          A configuration file can have both M and B attributes; but there is only one file of the same attribute on the device at a time.

 

 

Software Maintenance Methods

You can maintain software of the device in the following two methods:

l          Upgrade BootWare and applications using the XMODEM protocol through a serial port.

l          Upgrade applications using TFTP/FTP through an Ethernet interface on the BootWare menu or through command lines.

Note that:

l          When updating the application file, if you select to overwrite the existing application file, make sure to secure the power supply during this process; any power failure during this process will cause application update to fail and will damage the existing application file. In this case, if there was only one application file for booting the system, the device will be unable to start normally.

l          When updating the basic BootWare section, make sure to secure power supply during this process; any power failure during this process will damage the basic BootWare section, resulting in failure of device startup.

l          When updating the extended BootWare section, you only update part of the BootWare program. Once an error occurs, you can retry updating the extended BootWare section.

 

 

Figure 4-1 BootWare and Comware programs upgrade flow

 

BootWare Menu

BootWare Main Menu

When the router is powered on, the system first runs the basic segment and then the extended segment of the BootWare. The following information is displayed on the console terminal:

System is starting.....

Booting Normal Extend BootWare....

*************************************************** ********

*                                                          *

*            H3C SR6608 BootWare, Version 1.19             *

*                                                          *

************************************************************

Copyright (c) 2004-2008 Hangzhou H3C Technologies Co., Ltd.

Compiled Date       : Apr  15 2008

CPU Type            : MPC8548E

CPU L1 Cache        : 32KB

CPU Clock Speed     : 1000MHz

Memory Type         : DDR2 SDRAM

Memory Size         : 1024MB

Memory Speed        : 400MHz

BootWare Size       : 1024KB

Flash Size          : 4MB

cfa0 Size           : 495MB

NVRAM Size          : 128KB

BASIC CPLD Version  : 134.0

EXTEND CPLD Version : 133.0

PCB Version         : Ver.B

 

BootWare Validating...

Press Ctrl+B to enter extended boot menu...

Starting to get the main application file--cfa0:/main.bin!...............

................................................................................

..................................................................

The main application file is self-decompressing

Press Ctrl+B to enter the extended BootWare menu; otherwise, the system enters the self extraction process of the main application file.

 

 

Press Ctrl+B when “Press Ctrl+B to enter extended boot menu...” appears, and the system prompts:

Please input BootWare password:

After you type the correct BootWare password, the system will display:

Note: The current operating device is cfa0

Enter < Storage Device Operation > to select device.

Note that:

l          The initial BootWare password is null.

l          You have three chances to enter the correct BootWare password. If you fail to enter the correct password three times in a row, the system will be halted and you need to restart the router to enter the correct password.

l          You can enter the extended BootWare menu only after you enter the correct BootWare password.

==================<EXTEND-BOOTWARE MENU>=====================

| <1> Boot System                                           |

| <2> Enter Serial SubMenu                                  |

| <3> Enter Ethernet SubMenu                                |

| <4> File Control                                          |

| <5> Modify BootWare Password                              |

| <6> Skip Current System Configuration                     |

| <7> BootWare Operation Menu                               |

| <8> Clear Super Password                                  |

| <9> Storage Device Operation                              |

| <0> Reboot                                                |

=============================================================

Enter your choice(0-9):   

The menu is described in the following table.

Table 4-1 BootWare main menu

Menu item	Description
<1> Boot System	Boot system applications from a CF card.
<2> Enter Serial SubMenu	Enter the serial sub-menu. For detailed description on this sub-menu, refer to Serial Sub-menu.
<3> Enter Ethernet SubMenu	Enter the Ethernet sub-menu. For detailed description on this sub-menu, refer to Ethernet Sub-menu.
<4> File Control	File control sub-menu For detailed description on this sub-menu, refer to File Control Sub-menu.
<5> Modify BootWare Password	Modify the BootWare password.
<6> Skip Current System Configuration	Boot the system with the system configuration ignored. This operation is valid for this time, and you need to configure it next time. This option is generally used when you lose the password.
<7> BootWare Operation Menu	BootWare operation sub-menu For detailed description on this sub-menu, refer to BootWare Operation Sub-menu.
<8> Clear Super Password	Clear the super password. The super password is used in user level switching. No super password is set by default. This setting is valid for the first reboot of the router only. The super password will be restored after a second reboot.
<9> Storage Device Operation	Device control sub-menu, used to select the storage medium, where you can select the application to boot the system.
<a> Reboot	Reboot the router.

 

 

Serial Sub-menu

Select 2 from the BootWare main menu to enter the serial sub-menu, where you can update application files through XMODEM.

The system displays:

======================<Enter Serial SubMenu>======================

|Note:the operating device is cfa0                          |

| <1> Download Application Program To SDRAM And Run         |

| <2> Update Main Application File                          |

| <3> Update Backup Application File                        |

| <4> Update Secure Application File                        |

| <5> Modify Serial Interface Parameter                     |

| <0> Exit To Main Menu                                     |

=============================================================

Enter your choice(0-5):

Items on this sub-menu are described in the following table.

Table 4-2 BootWare serial sub-menu

Menu item	Description
<1> Download Application Program To SDRAM And Run	Download an application to SDRAM through the serial interface and run the program.
<2> Update Main Application File	Upgrade the main application file.
<3> Update Backup Application File	Upgrade the backup application file.
<4> Update Secure Application File	Upgrade the secure application file.
<5> Modify Serial Interface Parameter	Modify serial interface parameters.
<0> Exit To Main Menu	Return to the BootWare main menu.

 

Ethernet Sub-menu

Select 3 from the BootWare main menu to enter the Ethernet sub-menu, where you can upgrade application files using FTP/TFTP.

The system displays:

====================<Enter Ethernet SubMenu>======================

|Note:the operating device is cfa0                          |

| <1> Download Application Program To SDRAM And Run         |

| <2> Update Main Application File                          |

| <3> Update Backup Application File                        |

| <4> Update Secure Application File                        |

| <5> Modify Ethernet Parameter                             |

| <0> Exit To Main Menu                                     |

| < Ensure The Parameter Be Modified Before Downloading! >  |

=============================================================

Enter your choice(0-5):

Items on the Ethernet sub-menu are described in the following table:

Table 4-3 Ethernet sub-menu

Menu item	Description
<1> Download Application Program To SDRAM And Run	Download an application to SDRAM and run the program.
<2> Update Main Application File	Upgrade the main application file.
<3> Update Backup Application File	Upgrade the backup application file.
<4> Update Secure Application File	Upgrade the secure application file.
<5> Modify Ethernet Parameter	Modify Ethernet parameters.
<0> Exit To Main Menu	Return to the BootWare main menu.

 

File Control Sub-menu

Select 4 from the BootWare main menu to enter the file control sub-menu, where you can view the application files, modify file types, and delete files.

The system displays:

========================<File CONTROL>=======================

|Note:the operating device is cfa0                          |

| <1> Display All File(s)                                   |

| <2> Set Application File type                             |

| <3> Set Configuration File type                           |

| <4> Delete File                                           |

| <0> Exit To Main Menu                                     |

=============================================================

Enter your choice(0-4):   

Items on this sub-menu are described in the following table:

Table 4-4 File control sub-menu

Menu item	Description
<1> Display All File	Display all files.
<2> Set Application File type	Set the application file type.
<3> Set Configuration File type	Set the configuration file type.
<4> Delete File	Delete a file.
<0> Exit To Main Menu	Return to the BootWare main menu.

 

BootWare Operation Sub-menu

Select 7 from the BootWare main menu to enter the BootWare operation sub-menu:

=====================<BOOTWARE Operation Menu>===============

|Note:the operating device is cfa0                          |

| <1> Backup Full BootWare                                  |

| <2> Restore Full BootWare                                 |

| <3> Update BootWare By Serial                             |

| <4> Update BootWare By Ethernet                           |

| <0> Exit To Main Menu                                     |

=============================================================

Enter your choice(0-4): 

Items on this sub-menu are described in the following table:

Table 4-5 BootWare operation sub-menu

Menu item	Description
<1> Backup Full BootWare	Back up the full BootWare.
<2> Restore Full BootWare	Restore the full BootWare.
<3> Update BootWare By Serial	Upgrade BootWare through a serial interface.
<4> Update BootWare By Ethernet	Upgrade BootWare through Ethernet.
<0> Exit To Main Menu	Return to the BootWare main menu.

 

Storage Device Operation Sub-menu

Select 9 from the BootWare main menu to enter the storage device operation sub-menu:

====================<DEVICE CONTROL>=========================

| <1> Display All Available Nonvolatile Storage Device(s)   |

| <2> Set The Operating Device                              |

| <3> Set The Default Boot Device                           |

| <0> Exit To Main Menu                                     |

=============================================================

Enter your choice(0-3):

Items on this sub-menu are described in the following table:

Table 4-6 Storage device operation sub-menu

Menu item	Description
<1> Display All Available Nonvolatile Storage Device(s)	Display all available storage device(s).
<2> Set The Operating Device	Configure the current operating device.
<3> Set The Default Boot Device	Configure the default boot device.
<0> Exit To Main Menu	Return to the BootWare main menu.

 

Upgrading Applications and BootWare Through a Serial Interface

Introduction to XMODEM

Use XMODEM when upgrading an application and BootWare through a serial interface.

XMODEM is a file transfer protocol that is widely used due to its simplicity and high performance. XMODEM transfers files through a serial interface. It supports two types of data packets (128 bytes and 1 KB), two check methods (checksum and CRC), and error packet retransmission mechanism (generally the maximum number of retransmission attempts is 10).

The XMODEM transmission procedure is completed by the cooperation of a receiving program and a sending program. The receiving program sends a negotiation character to negotiate a packet check method. After the negotiation, the sending program starts to transmit data packets. When receiving a complete packet, the receiving program checks the packet using the agreed method.

l          If the check succeeds, the receiving program sends an acknowledgement character and the sending program proceeds to send another packet.

l          If the check fails, the receiving program sends a negative acknowledgement character and then the sending program retransmits the packet.

Modifying Serial Interface Parameters

In actual applications, you need to make the serial interface baud rate higher to save upgrading time or make it lower to guarantee transmission reliability. This section introduces how to adjust the serial interface baud rate.

Enter the BootWare main menu and select 2 to enter the serial interface sub-menu, and then select 5 from the sub-menu to modify the baud rate. The system displays the following:

========================<BAUDRATE SET>=======================

|Note:'*'indicates the current baudrate                     |

|     Change The HyperTerminal's Baudrate Accordingly       |

|--------------------<Baudrate Available>-------------------|

| <1> 9600(Default) *                                       |

| <2> 19200                                                 |

| <3> 38400                                                 |

| <4> 57600                                                 |

| <5> 115200                                                |

| <0> Exit                                                  |

=============================================================

Enter your Choice(0-5):

Select a proper baud rate. For example, select 5 for a baud rate of 115200 bps and the system displays the following information:

Baudrate has been changed to 115200 bps.

Please change the terminal's baudrate to 115200 bps, press ENTER when ready.

At this time, the baud rate of the serial interface of the router is modified to 115200 bps, while that of the terminal is still 9600 bps. The router and the terminal cannot communicate with each other. Therefore, you need to make the baud rate on the terminal consistent with that on the router.

Perform the following operations on the terminal:

Figure 4-2 Disconnect the terminal

 

Select File > Properties, and then click Configure… to change the bits per second to 115,200.

Figure 4-3 Modify the baud rate on the terminal

 

Select Call > Call to establish a new connection.

Figure 4-4 Re-establish a call connection

 

Then, press the Enter key, and the system will prompt the current baud rate and return to the previous menu.

The system displays:

The current baudrate is 115200 bps

 

 

Upgrading an Application

The application upgrade through a serial interface is implemented on the serial sub-menu.

Select 2 on the BootWare main menu to enter the serial sub-menu. For detailed description on this sub-menu, refer to section Serial Sub-menu.

The following example shows how to upgrade the main application file main.bin:

To improve the upgrading speed, you can modify the serial port baud rate before upgrading the main application file (refer to section Modifying Serial Interface Parameters). Select 2 on the serial port sub-menu, and the system displays:

Please Start To Transfer File, Press <Ctrl+C> To Exit.

Waiting...CCCCCCCCCCCCCCCCCCCC

Select Transfer > Send file… in the terminal window. The following dialog box appears:

Figure 4-5 Send File dialog box

 

Click Browse… to select the application file to be downloaded, and select Xmodem from the Protocol drop-down list. Then click Send and the following dialog box appears:

Figure 4-6 Sending file dialog box

 

After the file is downloaded, the following information appears on terminal interface:

Download successfully!

24803072 bytes downloaded!

The system prompts you to enter the name of application file to be downloaded to the current storage medium.

Input the File Name:

1)        If the file name is different from that of any existing file on the storage medium, the application file will be saved as this file name, for example,

Input the File Name:main.bin

Updating File cfa0:/main.bin...........................................

........................................................................................

........................................................................................

.........................................Done!

After that, you need to return to the main menu, enter the file control sub-menu, and set the application file as the default boot program. The system will use this program for next system boot. For description of the default boot program, refer to section Setting Configuration File Attributes.

2)        If the file name already exists on the storage medium, the system prompts:

The file is exist,will you recover it? [Y/N]

l          If you enter Y, the existing application file will be overwritten and successfully updated. The system will use the new application file for next system boot.

l          If you enter N, the system prompts:

Cancel to overwrite the file.

Failed!

In this case, the existing application file will not be overwritten and the file updating will fail.

 

 

Upgrading BootWare

Enter the BootWare main menu, refer to section BootWare Main Menu. Select 7 to enter the BootWare operation sub-menu, where you can perform all BootWare operations. For detailed description on this sub-menu, refer to section BootWare Operation Sub-menu.

The following example shows how to upgrade the full BootWare:

To update the entire BootWare, you need to first update the basic segment and then the extended segment.

Select 3 from the main menu and the system displays:

=================<BOOTWARE OPERATION SERIAL SUB-MENU>================

|<1> Update Full BootWare                                           |

|<2> Update Extend BootWare                                         |

|<3> Update Basic BootWare                                          |

|<4> Modify Serial Interface Parameter                              |

|<0> Exit To Main Menu                                              |

=====================================================================

Enter your choice(0-4):

To improve the updating speed, select 4 to set the baud rate of the serial interface to 115200 bps. Meanwhile, set the baud rate of the terminal to 115200 bps. Otherwise, communication between them will fail. For the modification of the baud rate of the terminal, refer to section Setting Configuration File Attributes.

After setting the baud rate, return to the BootWare operation sub-menu and select 1. The system displays the following:

Waiting ...CCCCCCCCCCCCCCCCCCCCCCCCC...

Select Transfer > Send file… in the terminal window. The following dialog box appears:

Figure 4-7 Send File dialog box

 

Click Browse… to select the application file to be downloaded, and select Xmodem from the Protocol drop-down list. Then click Send and the following dialog box appears:

Figure 4-8 Sending file dialog box

 

After the file is downloaded, the following information appears on the terminal interface, indicating upgrade success.

24803072 bytes downloaded!

Updating Basic BootWare? [Y/N]

1)        If you enter N, the system displays:

Not update the Basic!

Updating Extend BootWare? [Y/N]

The system stops updating the basic segment and asks you whether to update the extended segment or not.

2)        If you enter Y, the system updates the basic segment:

Updating Basic BootWare...............Done!

Updating Extend BootWare? [Y/N]Y

The basic segment is successfully updated and the system asks you whether to update the extended segment:

l          If you enter N, the system stops updating the extended segment.

l          If you enter Y, the system continues to update the extended segment:

Updating Extend BootWare.................Done!

The extended segment is successfully updated.

By now, the entire BootWare has been updated successfully.

 

 

Upgrading an Application and BootWare Using TFTP

When the application file is large, you can upgrade it using TFTP to save upgrade and maintenance time.

Trivial File Transfer Protocol (TFTP), a protocol in the TCP/IP protocol suite, is used for trivial file transfer between client and server. It provides not-so-complex and low-cost file transfer services. TFTP provides unreliable data transfer services over UDP and does not provide any access authorization and authentication mechanism. It employs timeout and retransmission to guarantee successful data delivery.

The SR6608 can serve as the TFTP client. The file server serves as the TFTP server. You can upload/download the application file on the router to/from the file server.

There are two approaches to upgrading application files using TFTP:

l          Using the BootWare menu

l          Using command lines

Upgrading an Application Using TFTP on the BootWare Menu

1)        Set up a TFTP upgrade environment.

Figure 4-9 Set up a TFTP upgrade environment

 

l          The router serves as the TFTP client, and the PC serves as the TFTP server.

l          Connect the management Ethernet interface MANAGEMENT on the router to the PC using a crossover Ethernet cable. Ensure the connectivity between the router and the PC. In the example, the IP address of GigabitEthernet 0/0 is 192.168.80.10, and that of the PC is 192.168.80.200.

l          Enable TFTP Server on the PC and set the path where the application file is stored.

 

 

2)        Configure Ethernet interface parameters on the BootWare menu.

Enter the BootWare main menu and select 3 to enter the Ethernet sub-menu, where you can select 5 to enter the Ethernet Parameter Set menu to set the Ethernet interface parameters.

==================<ETHERNET PARAMETER SET>===================

 Note:       '.' = Clear field.

             '-' = Go to previous field.

           Ctrl+D = Quit.

=============================================================

Protocol (FTP or TFTP):tftp

Load File Name      :main.bin

                    :main.bin

Target File Name    :main.bin

                    :main.bin

Server IP Address   :192.168.80.200

Local IP Address    :192.168.80.10

Gateway IP Address  :

FTP User Name       :

FTP User Password   :  

Table 4-7 Description on the display information of setting Ethernet interface parameters

Display information	Description
'.' = Clear field	Shortcut key . is used to clear the current input.
'-' = Go to previous field	Shortcut key - is used to return to the previous field.
Ctrl+D = Quit	Shortcut key Ctrl+D is used to quit the parameter setting page.
Protocol (FTP or TFTP)	Choose to upgrade applications using TFTP/FTP
Load File Name	Name of the download file, which needs be the same with that of the actual file to be downloaded. At the same time, you need to set the download path in TFTP/FTP. Note that: l      The first main.bin is the file name automatically memorized by the system at the last update. l      The second main.bin is the source file name set by the user. l      An application file name including the extension such as .bin, cannot exceed 50 characters.
Target File Name	Name of the target file after the file is downloaded to the router. The extension of the target file needs to be same with that of the download file. Note that: l      The first main.bin is the file name automatically memorized by the system at the last update. l      The second main.bin is the source file name set by the user. l      An application file name including the extension such as .bin, cannot exceed 50 characters.
Server IP Address	IP address of the FTP/TFTP server.
Local IP Address	IP address of the interface connected with the FTP/TFTP server.
Gateway IP Address	IP address of the gateway. You need not configure this IP address.
FTP User Name	FTP username, which will be used in FTP download. TFTP download needs no username.
FTP User Password	FTP password, which will be used in FTP download. TFTP needs no password.

 

 

3)        After the above configuration, the system will automatically return to the BootWare Set sub-menu, where you can select 2 to upgrade the main application file.

Loading.........

................

...... .... done

24802996 bytes downloaded!

Updating File cfa0:/main.bin

.........Done!

4)        After the upgrade is finished, select 0 to return to the BootWare main menu, where you can select 1 to reboot the system from the CF card.

 

 

Upgrading and Backing Up an Application Using TFTP Through Command Lines

1)        Set up a TFTP upgrade environment.

l          Router serves as the TFTP client, and PC serves as the TFTP server.

l          For the procedure of setting up upgrade environment, refer to Upgrading an Application Using TFTP on the BootWare Menu.

l          Run the terminal emulation program on the PC, and then configure the IP addresses of the client and sever to be on the same network segment. Ensure the connectivity between the router and the PC. In this example, the IP address of the server is 192.168.80.10, and that of management Ethernet interface on the client is 192.168.80.200.

l          You can use the ping command to check whether the connection is successful.

 

 

2)        View the files saved on the storage medium and its available space.

Use the dir command on the console terminal to view the files contained in the current file system, and the available space of the storage device.

<H3C>dir

Directory of cfa0:/

 

   0     drw-         -  Oct 28 2000 04:09:30   logfile

   1     -rw-  24802996  Oct 21 2007 17:03:26   sr6608.bin

   2     -rw-      1355  Oct 04 2007 17:22:12   startup.cfg

   3     -rw-  24802996  Sep 13 2037 13:21:20   main.bin

 

505480 KB total (456576 KB free)

 

File system type of cfa0: FAT16 

Table 4-8 Description on the display information of the dir command

Display information	Description
Directory of cfa0:/	Name of the current directory.
505480 KB total (456576 KB free)	Used space of the CF card (available space) Insufficient CF card space may result in an upgrade failure.
File system type of cfa0: FAT16	File system type of the CF card.

 

3)        Upgrade an application.

Using TFTP, you can download an application file from the server to the router, and overwrite the original main application file to implement application upgrade. The upgraded application file takes effect when the router reboots.

# Download application file main.bin from the TFTP server to the router.

<H3C> tftp 192.168.80.200 get main.bin main.bin

The file main.bin exists. Overwrite it? [Y/N]:y

  Verifying server file...

  Deleting the old file, please wait...

 

  File will be transferred in binary mode

  Downloading file from remote TFTP server, please wait...|

  TFTP: 24802996  bytes received in 907 second(s)

File downloaded successfully.

 

 

4)        Back up an application file.

Using TFTP, you can back up an application file by uploading it to the server.

# Upload file main.bin on the router to the PC, and save it as main.bin.

<H3C> tftp 192.168.80.200 put main.bin main.bin

 

  File will be transferred in binary mode

  Sending file to remote TFTP server. Please wait...

  TFTP:     24802996 bytes sent in 32 second(s).

File uploaded successfully.

 

 

Upgrading an Application and BootWare Using FTP

When the application file is large, you can also upgrade it using FTP to save upgrade and maintenance time.

As an application layer protocol in the TCP/IP suite, File Transfer Protocol (FTP) is mainly used for file transfer between remote hosts. FTP provides reliable and connection-oriented data transfer service over TCP. Compared with TFTP, the FTP software is much bigger.

There are two approaches to upgrading an application file using FTP:

l          Using the BootWare menu. In this approach, the router can serve as the FTP client only.

l          Using command lines. In this approach, the router can serve as the FTP server or the FTP client.

Upgrading an Application Using FTP Through the BootWare Menu

1)        Set up an FTP upgrade environment.

Figure 4-10 Set up an FTP upgrade environment

 

l          The router serves as the FTP client, and the PC serves as the FTP server.

l          Connect the management Ethernet interface on the router to the PC using a crossover Ethernet cable. Ensure the connectivity between the router and the PC. In the example, the IP address of GigabitEthernet 0/0 is 192.168.80.10, and that of the PC is 192.168.80.200.

l          Enable FTP Server on the PC and set the path where the application file is stored.

l          Set the FTP username and password.

 

 

For steps 2 through 4, refer to the corresponding steps in TFTP upgrading.

Upgrading and Backing Up an Application Using FTP Through Command Lines

Router serves as the FTP client; PC serves as the FTP server

1)        Set up the upgrade environment. Refer to Upgrading an Application Using FTP Through the BootWare Menu.

2)        Use the dir command on the console terminal to view the files contained in the current file system, and the available space of the storage device. For details, refer to step 2 in Upgrading and Backing Up an Application Using TFTP Through Command Lines.

3)        Start FTP server on the PC and set the path where the application file is stored, the FTP username, and the password. In the example, the FTP username is guest and the password is 123456.

4)        Log in to the FTP server.

<H3C>ftp 192.168.80.200

Trying 192.168.80.200 ...

Press CTRL+K to abort

Connected to 192.168.80.200.

220 3Com 3CDaemon FTP Server Version 2.0

User(192.168.80.200:(none)):guest

331 User name ok, need password

Password:

230 User logged in

[ftp]

After you log in to the server, you can upgrade and backup an application file using command lines.

Table 4-9 Description on the information displayed when the FTP client logs in to the FTP server

Display information	Description
ftp 192.168.80.200	Log in to the FTP server, and enter FTP client view.
User(192.168.80.200:(none))	Input the username configured on the FTP server.
331 User name ok, need password	Input the password.
230 User logged in	You have logged in to the FTP server successfully.

 

5)        Upgrade an application file.

Using FTP, you can download an application file from the server to the router, and overwrite the original main application file to implement application upgrade. The upgraded application file takes effect when the router reboots.

# Download file main.bin from the PC to the router, and save it as main.bin.

[ftp]get main.bin main.bin

 cfa0:/main.bin has been existing. Overwrite it? [Y/N]:y

227 Entering passive mode (192,168,80,200,7,237)

125 Using existing data connection

226 Closing data connection; File transfer successful.

FTP: 24802996 byte(s) received in 467.570 second(s), 53.00K byte(s)/sec.

 

 

6)        Back up an application file.

Using FTP, you can back up an application file by uploading it to the server.

# Upload file main.bin on the router to the PC, and save it as main.bin.

[ftp]put main.bin main.bin

227 Entering passive mode (192,168,80,200,5,34)

125 Using existing data connection

226 Closing data connection; File transfer successful.

FTP: 24802996 byte(s) sent in 14.400 second(s), 1722.00Kbyte(s)/sec

[ftp]quit

221 Service closing control connection

 

 

Table 4-10 Description on the information displayed when you upgrade and back up an application file on the router

Display information	Description
[ftp]get main.bin main.bin	Download the file used for upgrade.
cfa0:/main.bin has been existing. Overwrite it? [Y/N]:y	The system prompts whether to overwrite the existing file.
FTP: 24802996  byte(s) received in 467.570 second(s), 53.00K byte(s)/sec	Download and upgrade of the application file is finished.
[ftp]put main.bin main.bin	Upload the file from the router to the PC and save it.
FTP: 24802996 byte(s) sent in 14.400 second(s), 1722.00Kbyte(s)/sec	Upload and backup of the application file is finished.
[ftp]quit	Quit FTP client view.
221 Service closing control connection	Close the service control connection.

 

Router serves as the FTP server; PC serves as the FTP client

1)        Set up an FTP upgrade environment.

Figure 4-11 Set up an FTP upgrade environment

 

l          Connect the management Ethernet interface on the router to the PC using a crossover Ethernet cable.

l          Configure the IP addresses of the server and client to be on the same network segment. In this example, the IP address of interface GigabitEthernet 0/0 is 192.168.80.10, and that of the PC is 192.168.80.200.

l          You can use the ping command to check whether the connection is successful.

 

 

2)        Enable the FTP service.

# Enable FTP server.

<H3C>system-view

[H3C] ftp server enable

# Add FTP username and password.

[H3C] local-user guest

New local user added.

[H3C-luser- guest] service-type ftp

[H3C-luser- guest] password simple 123456

[H3C-luser-guest] level 3 authorization-attribute level 3

Table 4-11 Description on the display information of enabling the FTP service

Display information	Description
ftp server enable	Enable the FTP server function.
local-user guest	Create a local user, and enter user view.
service-type ftp	Set the service type that can be used locally to FTP.
password simple 123456	Configure the user password.
authorization-attribute level 3	Set the user level to 3.

 

 

3)        Enable the FTP client program on the PC.

In the following example, the FTP client program is the built-in Windows XP FTP client:

Enter ftp in the DOS window:

C:\Documents and Settings\Administrator>ftp

ftp>

ftp> open 192.168.80.10

Connected to 192.168.80.10.

220 FTP service ready.

User (192.168.80.10:(none)): guest

331 Password required for guest

Password:

230 User logged in.

Table 4-12 Description on the display information of enabling FTP server

Display information	Description
C:\Documents and Settings\Administrator>ftp	Enable the FTP client program on the PC.
ftp> open 192.168.80.10	In FTP client view, log in to the IPv4 FTP server.
User (192.168.80.10:(none))	Input the username configured on the FTP server.
331 Password required for guest	Input the password.
230 User logged in	You have logged in to the FTP server successfully.

 

4)        Upgrade an application file.

Using FTP, you can upload an application file from the client to the server (router), and overwrite the original main application file to implement application upgrade. The upgraded application file takes effect when the router reboots.

# Upload file main_bac.bin from the PC to the router, and saves it as main.bin.

ftp> binary

200 Type set to I.

ftp> lcd d:\update

Local directory now D:\update.

ftp> put main.bin main.bin

200 Port command okay.

150 Opening BINARY mode data connection for main.bin.

226 Transfer complete.

 

 

5)        Back up an application file.

Using FTP, you can back up an application file by downloading it from the server to the client.

# Download file main.bin from the router to the PC, and save it as main.bin.

ftp> get main.bin main_bac.bin

200 Port command okay.

150 Opening BINARY mode data connection for main.bin.

226 Transfer complete.

 

 

Table 4-13 Description on the display information of enabling FTP server

Display information	Description
ftp> binary	Change the transmission mode to binary. The ASCII mode is adopted by default.
ftp> lcd d:\update	Change the local directory.
ftp> put main.bin main.bin	Upload the file from the PC to the router.
ftp> get main.bin main.bin	Download the file from the router to the PC.
ftp> quit	Quit the FTP server.
221 Server closing.	Close service control connection

 

Updating Applications for the Standby MPU (on an SR6616 Router)

When starting up the system with dual main processing units (MPUs), make sure that the main application files used by the active and standby MPUs for system booting have the same version; otherwise, the standby MPU fails to start up normally. Then, the mutual backup and file operations between the active and standby MPUs cannot be implemented and high reliability of the device cannot be ensured.

Through the following methods, you can update the version of the main application file on the standby MPU to that of the main application file on the active MPU. Before doing that, make sure that the main application file already exists in the CF card of the active MPU; otherwise, you need to download the main application file to the active MPU following the procedures mentioned above.

Method I

Execute the command in Table 4-14, which is similar to performing the following operations:

1)        Copy the main application file of the active MPU to the standby MPU.

2)        Specify the application file copied from the active MPU for the next boot of the standby MPU.

3)        Restart the standby MPU.

You can use this method no matter if the main application files of the active and standby MPUs have the same version.

Table 4-14 Update the main application file of the standby MPU

To do…	Use the command…	Remarks
Update the main application file of the standby MPU	boot-loader update slot slot-number	Required Available in user view.

 

 

Method II

Restart the standby MPU and update the main application file of the standby MPU through the BootWare main menu. For detailed update approaches, refer to Upgrading Applications and BootWare Through a Serial Interface, Upgrading an Application and BootWare Using TFTP, and Upgrading an Application and BootWare Using FTP (the latter two approaches are recommended because they are fast in operation).

If you do not know which file is the current main application file, upload the main application file from the CF card of the active MPU to the file server through TFTP/FTP, and then update the main application file of the standby MPU.

Method III

Use the tftp command to download the current main application file to the standby MPU and configure it as the main application file of the standby MPU. Then restart the standby MPU.

Note that:

l          The main application files of the active and standby MPUs must have the same version.

l          If you do not know which file is the current main application file, upload the main application file from the CF card of the active MPU to the file server through TFTP/FTP, and then update the main application file of the standby MPU.

Follow these steps to update the application file for the standby MPU:

Step1   Use the dir command to view the application file to be updated on the active MPU:

l          If any, proceed with operation in Step 2;

l          If not, upload the application file to the active MPU through XMODEM, FTP, or TFTP. For details about uploading an application file, refer to the procedures mentioned above.

Step2   Use the dir command to view the available space in the CF card on the standby MPU. Make sure there is enough space for the application file to be updated.

Step3   Use the tftp command to download the application file on the server to the standby MPU. For example,

l          When the MPU is an RPE-X1:

<H3C>tftp 192.168.80.200 get main.bin slot4#cfa0:/main.bin

 

 File will be transferred in binary mode

 Downloading file from remote TFTP server, please wait...|

 TFTP: 24384324 bytes received in 101 second(s)

 File downloaded successfully.

l          When the MPU is an RSE-X1:

<H3C>tftp 192.168.80.200 get main.bin slot6#cfa0:/main.bin

 

 File will be transferred in binary mode

 Downloading file from remote TFTP server, please wait...|

 TFTP: 24384324 bytes received in 101 second(s)

 File downloaded successfully.

Step4   Specify the application file on the standby MPU to be used for system rebooting. For example,

l          When the MPU is an RPE-X1:

<H3C>boot-loader file slot4#cfa0:/main.bin slot 4 main

  This command will set the boot file of the specified board. Continue? [Y/N]:y

  The specified file will be used as the main boot file at the next reboot on slot 4!

l          When the MPU is an RSE-X1:

<H3C>boot-loader file slot6#cfa0:/main.bin slot 6 main

  This command will set the boot file of the specified board. Continue? [Y/N]:y

  The specified file will be used as the main boot file at the next reboot on slot 6!

Step5   Use the display boot-loader [ slot slot-number ] command to view the application files to be used by the active and standby MPUs for booting the system. Make sure the application files are of the same version.

Step6   After rebooting the standby MPU using the slave restart command in system view, use the display version command to view the current version of the application file. If the application file is of the new version, you have succeeded in updating the application file on the standby MPU.

Step7   You can view the status of the active and standby MPUs using the display device command. If the statuses of both the active and standby MPUs are Normal, the two MPUs are in the normal status. For example,

l          When the MPU is an RPE-X1:

<H3C> display device

Slot No.  Board type    Status       Primary    SubSlots

 ---------------------------------------------------------------------

 0         N/A           Absent       N/A        N/A

 1         FIP-200       Normal       N/A        2

 2         N/A           Absent       N/A        N/A

 3         N/A           Absent       N/A        N/A

 4         RPE-X1        Normal       Slave      0

 5         RPE-X1        Normal       Master     0

 6         N/A           Absent       N/A        0

 7         N/A           Absent       N/A        N/A

 8         FIP-200       Normal       N/A        2

 9         N/A           Absent       N/A        N/A

l          When the MPU is an RSE-X1:

<H3C> display device

 Slot No.  Board type    Status       Primary    SubSlots

 ---------------------------------------------------------------------

 0         N/A           Absent       N/A        N/A

 1         FIP-210       Normal       N/A        2

 2         N/A           Absent       N/A        N/A

 3         N/A           Absent       N/A        N/A

 5         RSE-X1        Normal       Master     0

 6         RSE-X1        Normal       Slave      0

 7         N/A           Absent       N/A        N/A

 8         FIP-210       Normal       N/A        2

 9         N/A           Absent       N/A        N/A

Method IV

Use the copy command to copy the current main application file of the active MPU to the standby MPU and configure it as the main application file of the standby MPU. Then restart the standby MPU. Make sure that the main application files of the active and standby MPUs must have the same version.

Follow these steps to update the application file for the standby MPU:

Step1   Use the dir command to view the application file to be updated on the active MPU:

l          If any, proceed with operation in Step 2;

l          If not, download the application file to the active MPU through XMODEM, FTP, or TFTP. For details about downloading an application file, refer to the procedures mentioned above.

Step2   Use the dir command to view the available space in the CF card on the standby MPU. Make sure there is enough space for the application file to be updated.

Step3   Use the copy command to copy the application file on the active MPU to the standby MPU. For example,

l          When the MPU is an RPE-X1:

<H3C> copy b54D002main.bin slot41#cfa0:/

Copy cfa0:/mainb54d002.bin to slot14#cfa0:/mainb54d002.bin?[Y/N]:y

 

%Copy file cfa0:/mainb54d002.bin to slot14#cfa0:/mainb54d002.bin...Done.

l          When the MPU is an RSE-X1:

<H3C> copy main.bin slot6#cfa0:/

Copy cfa0:/main.bin to slot6#cfa0:/main.bin?[Y/N]:y

 

%Copy file cfa0:/main.bin to slot6#cfa0:/main.bin...Done.

 

 

Step4   Specify the application file on the standby MPU to be used for system rebooting. For example,

l          When the MPU is an RPE-X1:

<H3C> boot-loader file slot14#cfa0:/mainb54d002.bin slot 14 main

  This command will set the boot file of the specified board. Continue? [Y/N]:y

  The specified file will be used as the main boot file at the next reboot on slot 14!

l          When the MPU is an RSE-X1:

<H3C> boot-loader file slot6#cfa0:/main.bin slot 6 main

  This command will set the boot file of the specified board. Continue? [Y/N]:y

  The specified file will be used as the main boot file at the next reboot on slot 6!

 

Step5   Use the display boot-loader [ slot slot-number ] command to view the application files to be used by the active and standby MPUs for booting the system. Make sure the application files are of the same version.

Step6   After rebooting the standby MPU using the slave restart command in system view, use the display version command to view the current version of the application file. If the application file is of the new version, you have succeeded in updating the application file on the standby MPU.

Step7   You can view the status of the active and standby MPUs using the display device command.

l          When the MPU is an RPE-X1: If the status of the active MPU is master and that of the standby MPU is ok, the two MPUs are in the normal status. (By default, Board5 indicates the active MPU and Board4 indicates the standby MPU.) For example,

<H3C> display device

Slot No.  Board type    Status       Primary    SubSlots

 ---------------------------------------------------------------------

 0         N/A           Absent       N/A        N/A

 1         FIP-200       Normal       N/A        2

 2         N/A           Absent       N/A        N/A

 3         N/A           Absent       N/A        N/A

 4         RPE-X1        Normal       Slave      0

 5         RPE-X1        Normal       Master     0

 6         N/A           Absent       N/A        0

 7         N/A           Absent       N/A        N/A

 8         FIP-200       Normal       N/A        2

 9         N/A           Absent       N/A        N/A

l          When the MPU is an RSE-X1: If the statuses of both the active and standby MPUs are Normal, the two MPUs are in the normal status. (By default, Board5 indicates the active MPU and Board6 indicates the standby MPU.) For example,

<H3C> display device

 Slot No.  Board type    Status       Primary    SubSlots

 ---------------------------------------------------------------------

 0         N/A           Absent       N/A        N/A

 1         FIP-210       Normal       N/A        2

 2         N/A           Absent       N/A        N/A

 3         N/A           Absent       N/A        N/A

 5         RSE-X1        Normal       Master     0

 6         RSE-X1        Normal       Slave      0

 7         N/A           Absent       N/A        N/A

 8         FIP-210       Normal       N/A        2

 9         N/A           Absent       N/A        N/A

Maintaining Application and Configuration Files

You can modify a file type, display files, and so on, on the file control sub-menu.

Select 4 on the BootWare main menu to enter the file control sub-menu. The system displays:

========================<File CONTROL>=======================

|Note:the operating device is cfa0                          |

| <1> Display All File(s)                                   |

| <2> Set Application File type                             |

| <3> Set Configuration File type                           |

| <4> Delete File                                           |

| <0> Exit To Main Menu                                     |

=============================================================

Enter your choice(0-3): 

Displaying All Files

Displaying all files on the BootWare menu

Select 1 on the file control sub-menu, and the system displays:

Display all file(s) in cfa0:

 'M' = MAIN      'B' = BACKUP      'S' = SECURE   'N/A' = NOT ASSIGNED

======================================================================

NO. Size(B)   Time                 Type   Name

1   941352    Nov/26/2007 12:02:42 N/A    cfa0:/logfile/logfile.log

2   24802996  Nov/04/2007 17:03:26 N/A    cfa0:/sr6608.bin

3   1355      Nov/04/2007 17:22:12 N/A    cfa0:/startup.cfg

4   1597      Nov/04/2007 10:07:10 N/A    cfa0:/~/startup.cfg

5   24802996  Nov/11/2007 15:11:42 M      cfa0:/main.bin

======================================================================

Displaying all files using command lines

<H3C> dir

Directory of cfa0:/

 

   0     drw-         -  Nov 28 2000 04:09:30   logfile

   1     -rw-  24802996  Nov 04 2007 17:03:26   sr6608.bin

   2     -rw-      1355  Nov 04 2007 17:22:12   startup.cfg

   3     -rw-  24802996  Nov 13 2037 13:21:20   main.bin

 

505480 KB total (456576 KB free)

 

File system type of cfa0: FAT16

Table 4-15 Description on the display information of the dir command

Display information	Description
Directory of cfa0:/	Name of the current directory.
505480 KB total (456576 KB free)	Used space of the CF card (available space)
File system type of cfa0: FAT16	File system type of the CF card.

 

 

Setting Application File Attributes

Setting application file attributes through the BootWare menu

You can modify the attributes of the main, backup, and N/A application files through the BootWare menu or using commands after the application files boot; however, you cannot modify the attribute of an application file of type S. For details about application file attributes, refer to Setting Configuration File Attributes.

Select 2 from the file control sub-menu, and the system displays:

'M' = MAIN      'B' = BACKUP      'S' = SECURE   'N/A' = NOT ASSIGNED

=====================================================================

NO. Size(B)   Time                 Type   Name

|1   24802996  Nov/04/2007 17:03:26 B      cfa0:/main.bin           |

|2   24802996  Nov/11/2007 15:11:42 M      cfa0:/main_bak.bin       |

|0   Exit

=====================================================================

Enter file no:                                              

Enter the file number, select 2, and the system prompts:

Modify the file attribute:

======================================================================

| <1> +Main                                                          |

| <2> -Main                                                          |

| <3> +Backup                                                        |

| <4> -Backup                                                        |

| <0> Exit                                                           |

Enter your choice(0-4):     

You can set the file type to M (main) or B (backup), or cancel the setting by selecting 1 to 4. For details of each type of files, refer to Router Software and Functions.

In the example, 1 is selected and the system changes the attribute of the file main.bin from of B to M + B.

Set the file attribute success!

Now, the attribute of the file main_bak.bin automatically changes from M to N/A.

Setting application file attributes through the CLI

In the following description the files main.bin and main_bak.bin mentioned above are taken as examples.

# Change the attribute of the file main.bin from B to M + B.

<H3C> rename main.bin main.bak

Rename cfa0:/main.bin to cfa0:/main.bak? [Y/N]:y

% Renamed file cfa0:/ main.bin to cfa0:/ main.bak

Now the attribute of the file main.bin has changed from B to M + B and the file will be used as the main application file at the next boot, while the attribute of another existing file main_bak.bin has automatically changed from the original M to N/A.

You can verify the changes of the file attributes by viewing all the files through the file control sub-menu.

Select 2 from the file control sub-menu. The system displays the following information:

'M' = MAIN      'B' = BACKUP      'S' = SECURE   'N/A' = NOT ASSIGNED

=====================================================================

|NO. Size(B)   Time                 Type   Name                     |

|1   11673608  Nov/15/2007 05:39:50 M+B    cfa0:/main.bin           |

12   11673608  Nov/15/2007 05:39:50 N/A    cfa0:/main_bak.bin       |

|0   Exit                                                           |

=====================================================================

Enter file No:

 

 

Setting Configuration File Attributes

Setting configuration file attributes through the BootWare menu

You can modify the file attributes through the BootWare menu. For details about configuration file attributes, refer to Setting Configuration File Attributes.

Select 3 from the file control sub-menu. The system displays the following information:

'M' = MAIN      'B' = BACKUP      'S' = SECURE      'N/A' = NOT ASSIGNED

=========================================================================

|NO. Size(B)   Time                 Type   Name                         |

|1   734       Dec/17/2000 11:47:20 N/A    cfa0:/startup.cfg            |

|2   760       Dec/17/2000 18:49:50 N/A    cfa0:/startup_bak2.cfg       |

|3   810       Dec/17/2000 18:49:26 M      cfa0:/startup_bak1.cfg       |

|4   850       Dec/17/2000 18:50:08 N/A    cfa0:/startup_bak3.cfg       |

|0   Exit                                                               |

=========================================================================

Enter file No:

Select a file number, which is 1 in this example. The following information appears:

Modify the file attribute:

=========================================================================

|<1> +Main                                                              |

|<2> -Main                                                              |

|<3> +Backup                                                            |

|<4> -Backup                                                            |

|<0> Exit                                                               |

=========================================================================

Enter your choice(0-4):

You can set the file attribute to M (main) or B (backup), or cancel the setting by selecting a choice from 1 to 4.

In this example, 1 is selected and the system changes the file startup.cfg from type N/A to type M.

Set the file attribute success!

Now, the attribute of the file startup_bak1.cfg has automatically changed from M to N/A.

 

 

Setting configuration file attributes through the CLI

You can use the startup saved-configuration cfgfile [ backup | main ] command to define the configuration file to be used for the next boot and its attribute. In this command, use cfgfile argument to specify the configuration file name.

Note that:

l          You can use the startup saved-configuration cfgfile main command to change the attribute of an N/A-type configuration file to M.

l          You can use the startup saved-configuration cfgfile backup command to change the attribute of an N/A-type configuration file to B.

l          You can use the startup saved-configuration cfgfile backup command to change the attribute of an M-type configuration file to M + B.

l          You can use the startup saved-configuration cfgfile main command to change the attribute of a B-type configuration file to M + B.

l          If you use neither main nor backup in your command, you assign the M attribute to the specified configuration file.

l          If you assign the M attribute to a configuration file, the attribute of the existing main configuration file, if any, is automatically erased, because there can be only one main configuration file in the system at a time.

l          If you assign the B attribute to a configuration file, the attribute of the existing backup configuration file, if any, is automatically erased, because there can be only one backup configuration file in the system at a time.

l          You can use the undo startup saved-configuration command to erase the main and backup attributes of the configuration files. Namely, the system has no longer a main, nor a backup configuration file after this command.

# Define the file startup.cfg as the backup configuration file for the next system boot.

<H3C> startup saved-configuration startup.cfg backup

Please wait......Done!

 

 

Deleting a File

Deleting a file on the BootWare menu

Select 3 from the file control sub-menu, and the system displays:

Deleting the file in cfa0:

 'M' = MAIN      'B' = BACKUP      'S' = SECURE   'N/A' = NOT ASSIGNED

======================================================================

NO. Size(B)   Time                 Type   Name

1   941352    Nov/26/2000 12:02:42 N/A    cfa0:/logfile/logfile.log

2   24802996  Nov/04/2007 17:03:26 N/A    cfa0:/sr6608.bin

3   1355      Nov/04/2007 17:22:12 N/A    cfa0:/startup.cfg

4   1597      Nov/04/2007 10:07:10 N/A    cfa0:/~/startup.cfg

5   24802996  Nov/11/2055 15:11:42 M      cfa0:/main.bin

0   Exit

======================================================================

Enter file no:   

Enter the file number, select 4, and the system prompts:

The file you selected is cfa0:/~/startup.cfg,Delete it? [Y/N]

Enter Y.

If the system displays the following information, the file is successfully deleted:

Deleting.........Done!

 

 

Deleting a file using the command line

You can delete a file using the delete [ /unreserved ] file-url command in user view. file-url specifies the file to be deleted, and /unreserved indicates to delete the file permanently.

# Delete file test.txt in the root directory.

<H3C> delete test.txt

Delete cfa0:/test.txt?[Y/N]:y

%Delete file cfa0:/test.txt...Done.

At this time, file test.txt is removed to the recycle bin. If you want to restore the file, you can use the undelete command.

# Restore  the test.txt file in the recycle bin.

<H3C> undelete test.txt

Undelete cfa0:/test.txt? [Y/N]:y

% Undeleted file cfa0:/test.txt.

 

 

Dealing With Password Loss

When the BootWare password, user password or super password is lost, resort to the following methods:

BootWare Password Loss

Contact the agent or the technical support personnel to set a new password in the event of BootWare password loss.

The BootWare password is modified on the main menu. Select 5 from the main menu to modify the BootWare password.

The configuration terminal displays:

please input old password:

Enter the old password.

please input old password: ******

 

 

After you enter the correct old password, the system prompts you to enter a new password twice.

Please input new password: ******

Please input new password again: ******

If the system displays the following information, the password is successfully modified.

Password Set Successfully.

 

 

User Password Loss

If you lose your password, you cannot enter the system. In this case, you can boot the system by ignoring the system configuration. Perform the following operations.

1)        Enter the BootWare main menu, and select 6 to boot the system by ignoring the system configuration.

The system prompts:

Flag Set Success.

The system prompts that the setting succeeds.

2)        When the BootWare main menu appears again, select 0 to reboot the system.

System is rebooting now.

 

System start booting...

Booting Normal Extend BootWare....

3)        Set a new password in system view after system reboot.

<H3C> system-view

[H3C] user-interface console 0

[H3C-ui-console0] authentication-mode password

[H3C-ui-console0] set authentication password simple 123456

The above information indicates that the password authentication is adopted on the console interface and the password is set to 123456 and stored in plain text.

When setting a password using the set authentication password { cipher | simple } password command:

l          If the cipher keyword is specified, the password will be stored in cipher text. In this case, the password cannot be displayed with the display current-configuration command.

l          If the simple keyword is specified, the password will be stored in plain text. In this case, the password can be displayed with the display current-configuration command.

 

 

4)        Save the new password.

[H3C] save

 

 

BootWare Password Loss

Contact the agent or the technical support personnel to set a new password in the event of BootWare password loss.

The BootWare password is modified on the BootWare main menu. Select 5 on the BootWare main menu to modify the password.

The console terminal displays:

please input old password:

Enter the old password.

please input old password: ******

 

 

After you enter the correct old password, the system prompts you to enter the same new password twice.

Please input new password: ******

Please input new password again: ******

The system displays the following information indicating success of setting the new password.

Password Set Successfully.

 

 

Super Password Loss

The super password enables you to switch between four super levels. In the case of super password loss, you cannot perform higher level operations.

You can clear the super password by selecting 8 on the BootWare main menu.

==================<EXTEND-BOOTWARE MENU>=====================

| <1> Boot System                                           |

| <2> Enter Serial SubMenu                                  |

| <3> Enter Ethernet SubMenu                                |

| <4> File Control                                          |

| <5> Modify BootWare Password                              |

| <6> Skip Current System Configuration                     |

| <7> BootWare Operation Menu                               |

| <8> Clear Super Password                                  |

| <9> Storage Device Operation                              |

| <0> Reboot                                                |

=============================================================

Enter your choice(0-9):8

The system displays the following information indicating that you have successfully cleared the super password.

Clear Application Password Success

 

 

Backing Up and Restoring BootWare

You can back up and restore BootWare on the BootWare operation sub-menu.

Select 7 from the BootWare main menu to enter the BootWare operation sub-menu. Refer to BootWare Operation Sub-menu for details.

Backing Up the Full BootWare

To back up a full BootWare, you need to back up the basic segment and then the extended segment of the BootWare.

Select 1 on the BootWare operation sub-menu, and the system prompts:

Will you backup the Basic BootWare? [Y/N]

Select Y:

Begin to backup the Basic BootWare....................Done!

At this moment, backup for the basic segment is finished.

The system continues to prompt:

Will you backup the Extend BootWare? [Y/N]

Select Y:

Begin to backup the Extend BootWare....................

Done!

At this moment, backup for the extended segment is finished.

 

 

Restoring the Full BootWare

Select 2 on the BootWare operation sub-menu to overwrite the BootWare in the system with the BootWare stored on the Flash. To restore a full BootWare, you need to restore the basic segment and then the extended segment of the BootWare.

Will you restore the Basic BootWare? [Y/N]

Select Y:

Begin to restore Normal Basic BootWare....................Done!

At this moment, restoration of the basic segment is finished.

The system continues to prompt:

Will you restore the Extend BootWare? [Y/N]

Select Y:

Begin to restore Normal Extend BootWare....................Done!

At this moment, restoration of the extended segment is finished.