4Motion® System Manual Release 2.
Document History Document History Topic Description Date Issued Preliminary Release for Early Field Trials New System Manual January 2008 Preliminary Release for Beta May 2008 Release for GA July 2008 SDR Section 1.3.1.3 Removed August 2008 Template Changed September 2008 Power Feeder Section 1.3.4 Supported in release 2.5 December 2008 7 MHz Channel Bandwidth Table 1-4, relevant sections in Chapter 4. Supported in release 2.
Document History Topic Description Date Issued Managing BS Services Added new parameters: paging-cycle, paging-offset, lm-traffic-idle-period, dl-def-rate. May 2009 Section 3.8.4 Updated range and default value for max-subburst. Managing Ranging Parameters Section 3.8.23 The following tables were removed from operator CLI: Bandwidth Request, Handover Ranging, Initial Ranging, Periodic Ranging, Timing Correction. May 2009 contbased-rsrvtimeout was removed from Ranging General table.
Document History Topic Description Date Issued Service Mapping Rule R1 Profile Parameters Sections 3.8.5.2.3, 3.8.5.6.3 Removed: sdu-length, sdu-size. May 2009 All possible values of datadeliverytype are supported (including rTVR and nRTVR). Updated descriptions of cir, mir, latency. Updated range for cir, mir. Service Mapping Rule R6 Profile Parameters Section 3.8.5.2.4, Updated range for cir, mir. May 2009 Feedback Allocation Parameters Removed: pr-cdma, ert-poll-enable. May 2009 Section 3.
Document History Topic Description Date Issued Handover Control Parameters All configurable (read-write) parameters were removed. May 2009 Section 3.8.23 A new read-only parameter added: CINRReuse. BS Management Alarm Thresholds (was previously 4.8.26) All BS Management Alarm Thresholds parameters were removed. May 2009 BS Alarm Threshold Parameters Removed: dl-droppedpackets, unalloc-slots, dl-retransmissions, ul-retransmissions, dl-subburstdrop, ul-subburstdrop. May 2009 Section 3.8.
Document History Topic Description Date Issued AAA Client Configuration Updated with new parameters/commands and additional changes related to support of multiple AAA clients and AAA Redundancy. May 2009 Section 3.3.11.13.1 In addition: Removed the auth-port and acct-port parameters. Added command for configuring the format of the Calling Station ID MAC Address. Added configuration rules for primary-serveraddr and alternate-serveraddr. Updated default and presence requirement for primary-serveraddr.
Document History Topic Description Date Issued Bearer Plane QoS Marking Rules qos-alias possible values changed to 1-30 characters, May 2009 Section 3.3.11.11.1 media-type possible values changed to 1-30 characters, file-name possible values changed to 1-50 characters, May 2009 Section 3.3.12.1.5 AU Maintenance VLAN ID New feature May 2009 Added service interface parameters. May 2009 Neighbor BS Triggers/Specific BS Triggers Sections 3.8.13.2.4, 3.8.13.7.5, 3.8.13.
Document History Topic Description Date Issued AU Properties Sections 3.5.2.1, 3.5.3.1, Updated possible values for required-type. May 2009 3.5.6.1 Removed: required-ports, required-bandwidth (and the corresponding InstalledPorts and InstalledBandwidth). Updated options for port-3 power and port-4-power parameters (removed the NA option). Sector Parameters Section 3.9.1 Antennas Section 3.7 heading is not mandatory when creating a new sector. The default value is 0.
Document History Topic Description Date Issued Data Path Function Parameters Configurable only by the vendor. Updated display format. May 2009 Configurable only by the vendor. Updated display format. May 2009 Configurable only by the vendor. Updated display format. May 2009 Section 3.3.11.9 Connectivity Service Network (CSN) Parameters Configurable only by the vendor. Updated display format. May 2009 Added default (disable). May 2009 Removed: ulSfQosSduSize, dlSfQosSduSize.
Document History Topic Description Date Issued Dry Contact Input Alarms Sections 3.3.15.4, 3.3.15.6 Added alarmPolarity May 2009 Displaying the Active Clear Timer and Event Rate Limit New command May 2009 Added new ODUs: ODU-HP-2.3-WCS, ODU-2340-2400-000N-36-1X1-N-0, ODU-2480-2690-000N-38-4X2-N-0. May 2009 Section 3.3.14.2.6 ODUs Sections 1.3.3, 2.1.3, 3.6.1.1, 3.6.1.2, 3.6.1.6, 3.6.2. Tables 1-3, 1-7, 1-11, 1-21. Removed: 2x1 ODUs.
Document History Topic Description Date Issued IP-IP Service Interface Parameters Sections 3.3.11.12.2.1, Updated syntax of commands for better support of commands auto-completion. May 2009 Updated May 2009 Updated syntax of commands for better support of commands auto-completion. May 2009 3.3.11.12.3.1 Displaying Configuration Information for the Service Interface Section 3.3.11.12.6 VLAN Service Interface Parameters Sections 3.3.11.12.2.2, 3.3.11.12.3.
Document History Topic Description Date Issued Privilege Levels Sections 3.1.5.5, 3.1.6 The highest privilege level available for users is 10. May 2009 DGW Profile Sections 3.3.11.15.3.1, Added a note (parameters related to DGW profile are not applicable in current release). May 2009 Required only in configurations with 6 AUs where each AU is connected to 4 2.x GHz or 3.5 GHz 1x1 ODUs. May 2009 Section 2.3.3.
Document History Topic Description Date Issued Commissioning-Completing the Site Configuration Using AlvariSTAR-BS Configuration Removed the requirement for clicking Apply on Radio Advanced screen and Connectivity Advanced screen. May 2009 Commissioning-Completing the Site Configuration Using AlvariSTAR-ASNGW Configuration It is not mandartory to define AAA client (the default client can be used).
Document History Topic Description Date Issued Attaching/De-attaching ACLs to/from an Interface Removed paragraph on Standard ACL 1 which was previously available by default. June 2009 By default, all traffic destined towards the AUs is denied and all traffic towards the NPU is permitted. June 2009 nw-id parameter is optional. June 2009 Updated descriptions for eapTimerTransfer and eapCounterTransferMax.
Document History Topic Description Date Issued Configuring Parameters for VLAN Service Interface vlan-id and dflt-gw-ip are mandatory. June 2009 vlan-id is mandatory. June 2009 rad-CallingStationId parameter added to AAA Client parameters config command (instead of config aaaserverMACFormat command added in a previous version of this release). June 2009 Updated command syntax and description. June 2009 “default” client cannot be deleted.
Document History Topic Description Date Issued Configuring the Trap Manager Added note: A route to forward traps to a configured Trap Manager IP address must exist. June 2009 Section 3.3.14.2 Displaying the Trap Rate Limit Updated description. June 2009 Corrected the presence of UTC to Optional. June 2009 Added note on error condition. June 2009 Corrected command’s syntax. June 2009 Updated description.
Document History Topic Description Date Issued Deleting Source Addresses Updated command syntax. June 2009 Updated command syntax. June 2009 Added Privilege Level definition. June 2009 Updated Privilege Level (10) June 2009 Added to manual.
Document History Topic Description Date Issued Enabling the Destination Port Configuration Mode\ Creating a New Destination Port Added consistency rules for start-port and end-port. June 2009 Added consistency rules-impact of enabling destination port range June 2009 Added consistency rules-impact on parameters of IP protocol lists June 2009 Added consistency rules-impact on parameters of IP protocol lists June 2009 Section 3.3.11.15.4.7.
Document History Topic Description Date Issued Managing Service Groups Added explanations on the different service group types. June 2009 Section 3.3.11.14 Added new type (VPWS-Mapped). Added acctInterimTmr parameter and updated range/default for acct parameter in IP Service Group configuration. Updated description for ms-loop. Changed structure/headings and added new sections for configuring VPWS service groups. Updated description of dhcp-ownaddr.
Document History Topic Description Date Issued Displaying the Status of the last File Download Operations New section June 2009 Updated range for paging-cycle, paging-offset and lm-traffic-idle-period. August 2008 Section 3.8.4.2 4x2 ODU Installation Guidelines Updated August 2008 Updated value range for cir and mir parameters. August 2008 Updated value range for cir and mir parameters.
Document History Topic Description Date Issued Configuring Airframe Cyclic Delay Parameters Updated dependencies. The values are set by internal logic. August 2008 Configuring Airframe Linear Delay Parameters Previousely Section 4.8.16.2.5 Updated dependencies. The values are set by vendor file. August 2008 Configuring Airframe Mapping Parameters Previousely Section 4.8.16.2.6 Updated dependencies. The values are set by internal logic.
Document History Topic Description Date Issued Configuring the Power Control Required C/N Level Parameters All parameters cannot be modified. August 2008 max-subburst is not relevant. August 2008 Section 3.8.6.2.2 Configuring Service Parameters Section 3.8.4.2 Configuring the Unique Identifier for the 4Motion Shelf Section 3.3.15.8.1 Managing the IP Connectivity Mode Section 3.3.1 Configuring Physical and IP Interfaces trgt-err-rate cannot be modified.
Document History Topic Description Date Issued Radio Standards Added FCC part 25 August 2008 QinQ Service Interface is supported (for special needs) August 2008 VLAN CS Service Flows can be configured for the Default Service Profile August 2008 Section 3.3.11.15.3 1x1 ODU LEDs ETH connector is functional August 2008 Updated range for frequency August 2008 Updated range for frequency August 2008 Updated range for srvcflow-datadeliverytype.
Document History Topic Description Date Issued Commissioning No need to configure ACL August 2008 Removed sections related to Cyclic Delay Parameters, Linear Delay Parameters, Mapping Parameters and Receive Parameters. In General Parameters, auto-diversity and auto-rx-enable were removed. August 2008 Section 2.1 Configuring Airftame Parameters Section 3.8.16.
Document History Topic Description Date Issued Managing Power Control Levels Removed sections related to configuring or restoring the default value of Maximum EIRxP. Added a note that this command is not applicable for the current release. Updated the description for displaying configuration values of the parameter. August 2008 Section 3.8.6 Added a note regarding nilevels cqi-ack-ranging parameter that cannot be modified. Required C/N Levels are configurable.
Document History Topic Description Date Issued Configuring the 4Motion Shelf Updated descriptions of components. September 2009 Updated general description September 2009 Updated range for pusc. September 2009 Changed the mapping of the Macro Outdoor BTS AUs to Slot January 2010 Updated: 4x2 ODUs and also NAU, DAU, and SAU units of the Macro Outdoor BTS may come with a sun-guard pre-installed January 2010 Chapter 2 - Installation Removed from the manual.
Legal Rights Legal Rights © Copyright 2010 Alvarion Ltd. All rights reserved. The material contained herein is proprietary, privileged, and confidential and owned by Alvarion or its third party licensors. No disclosure thereof shall be made to third parties without the express written permission of Alvarion Ltd. Alvarion Ltd. reserves the right to alter the equipment specifications and descriptions in this publication without prior notice.
Legal Rights (b) With respect to the Firmware, Alvarion warrants the correct functionality according to the attached documentation, for a period of fourteen (14) month from invoice date (the "Warranty Period")". During the Warranty Period, Alvarion may release to its Customers firmware updates, which include additional performance improvements and/or bug fixes, upon availability (the "Warranty"). Bug fixes, temporary patches and/or workarounds may be supplied as Firmware updates.
Legal Rights FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET FORTH IN THIS AGREEMENT ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES, TERMS OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY, CORRESPONDENCE WITH DESCRIPTION, NON-INFRINGEMENT, AND ACCURACY OF INFORMATION GENERATED.
Legal Rights FCC Radiation Hazard Warning To comply with FCC RF exposure requirements in Section 1.1307 and 2.1091 of FCC Rules, the antenna used for this transmitter must be fixed-mounted on outdoor permanent structures with a separation distance of at least 2 meter from all persons. R&TTE Compliance Statement This equipment complies with the appropriate essential requirements of Article 3 of the R&TTE Directive 1999/5/EC.
Legal Rights The equipment must be connected directly to the DC Supply System grounding electrode conductor. All equipment in the immediate vicinity must be grounded in the same way, and not be grounded elsewhere. The DC supply system is to be local, i.e. within the same premises as the equipment. There shall be no disconnect device between the grounded circuit conductor of the DC source (return) and the point of connection of the grounding electrode conductor.
Legal Rights regulation violations associated with or caused by installation, grounding or lightning protection. Disposal of Electronic and Electrical Waste Disposal of Electronic and Electrical Waste Pursuant to the WEEE EU Directive electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product.
Important Notice Important Notice This user manual is delivered subject to the following conditions and restrictions: This manual contains proprietary information belonging to Alvarion Ltd. Such information is supplied solely for the purpose of assisting properly authorized users of the respective Alvarion products.
Important Notice damage and/or bodily harm and/or void the user's authority to operate the equipment and/or revoke the warranty provided by such manufacturer.
About This Manual About This Manual This manual describes the 4Motion solution, and details how to install, operate and manage the BTS system components. This manual is intended for technicians responsible for installing, setting and operating the 4Motion BTS equipment, and for system administrators responsible for managing the system. This manual contains the following chapters and appendices: Chapter 1 - System description: Describes the 4Motion BTS and its components.
Contents Contents Chapter 1 - System Description 1.1 About WiMAX................................................................................................................3 1.2 4Motion Solution ..........................................................................................................4 1.2.1 4Motion Solution Highlights.................................................................................4 1.2.2 WiMAX Network Reference Model.....................................................
Contents 1.5.9 Mechanical and Electrical .................................................................................41 1.5.10 Antennas ...........................................................................................................46 Chapter 2 - Commissioning 2.1 Initial NPU Configuration...........................................................................................54 2.1.1 Introduction ...........................................................................................
Contents 3.1.4 Interpreting the Command Syntax ....................................................................74 3.1.5 Using the CLI ....................................................................................................75 3.1.6 Managing Users and Privileges ........................................................................78 3.1.7 Managing Secure Shell (SSH) Parameters.......................................................87 3.1.8 Managing the Session...............................
Contents 3.4.2 Displaying MS Information ..............................................................................413 3.5 Managing AUs ..........................................................................................................414 3.5.1 Enabling the AU Configuration Mode\Creating an AU Object.........................415 3.5.2 Configuring AU Parameters ............................................................................416 3.5.
Contents 3.8.8 Managing Neighbor Advertisement Parameters .............................................508 3.8.9 Managing Triggers Parameters.......................................................................510 3.8.10 Managing Trigger Setup Parameters ..............................................................514 3.8.11 Managing Scan Negotiation Parameters ........................................................517 3.8.12 Managing Handover Negotiation at TBS Parameters .............................
Contents 3.10.1 Monitoring Hardware Components .................................................................656 3.10.2 Monitoring Software Components...................................................................662 3.10.3 Displaying Statistics for Physical and IP Interfaces ........................................663 3.10.4 Displaying System Files ..................................................................................664 3.11Troubleshooting ..............................................
Contents B.3.6 Deleting AU Images from the NPU Flash........................................................709 B.3.7 Displaying Images Residing in the AU Flash ..................................................710 Glossary ................................................................................................
Chapter 1 System Description
Chapter 1 - System Description In This Chapter: “About WiMAX” on page 3 “4Motion Solution” on page 4 “The Base Transceiver Station” on page 13 “Element Management Systems” on page 24 “Specifications” on page 26 4Motion 2 System Manual
Chapter 1 - System Description 1.1 About WiMAX About WiMAX Emanating from the broadband world and using all-IP architecture, mobile WiMAX is the leading technology for implementing personal broadband services. With huge market potential and affordable deployment costs, mobile WiMAX is on the verge of a major breakthrough.
Chapter 1 - System Description 4Motion Solution 1.2 4Motion Solution 1.2.1 4Motion Solution Highlights Leveraging its extensive experience in Broadband Wireless Access (BWA) systems, leading technology and current favorable economics for broadband and mobile services, Alvarion's 4Motion mobile WiMAX solution represents the next evolution in communications. With 4Motion, Alvarion offers a diversified range of products and services for all operators.
Chapter 1 - System Description 4Motion Solution BTS (Base Transceiver Station) equipment with an optional localized access service network gateway (ASN-GW): » Indoor modular Macro BTS. » All-outdoor modular Macro BTS.
Chapter 1 - System Description 4Motion Solution architecture and interfaces according to the WiMAX Forum networking working group (NWG) profile C, which supports openness and enables flat as well as hierarchical topologies. In addition, by keeping the radio resource management functionality in the Base Transceiver Station only, Profile C delivers a faster, optimized handover mechanism. 1.2.
Chapter 1 - System Description 4Motion Solution Figure 1-3: ASN Reference Model containing Multiple ASN-GWs The various components and entities involved in the networking architecture are: 1.2.2.1 Access Service Network (ASN) An ASN is defined as a complete set of network functions needed to provide radio access to a WiMAX subscriber.
Chapter 1 - System Description 4Motion Solution An ASN is comprised of network elements such as one or more base transceiver stations and one or more ASN gateways. An ASN may be shared by more than one connectivity service network (CSN). 1.2.2.2 Connectivity Service Network (CSN) A CSN is defined as a set of network functions that provide IP connectivity services to WiMAX subscribers.
Chapter 1 - System Description 4Motion Solution third-party application providers (e.g. ASP, ISP) for the delivery of WiMAX services to subscribers. From a WiMAX subscriber standpoint, an NSP may be classified as a home or visited NSP. 1.2.2.5 Base Station (BS) The WiMAX BS is an entity that implements the WiMAX MAC and PHY in compliance with the IEEE 802.16e standard. A BS operates on one frequency assignment, and incorporates scheduler functions for uplink and downlink resources.
Chapter 1 - System Description 4Motion Solution QoS service flow authorization entity AAA accounting client The basic EP functionality of the ASN-GW includes: Classification of downlink data into generic routing encapsulation (GRE) tunnels Packet header suppression functionality DHCP functionality Handover functionality The WIMAX Forum NWG has adopted two different approaches for ASN architecture - centralized and distributed: In the centralized approach there is at least one central ASN-GW, a
Chapter 1 - System Description 4Motion Solution In the distributed approach, the NPU operates in ASN-GW mode, as shown in Figure 1-5. Figure 1-5: Distributed Network Reference Model Alvarion believes in providing operators with the flexibility to select the mobile WiMAX network topology that best suits their needs and existing network architecture. Therefore, 4Motion is designed to support both distributed and centralized topology approaches according to WiMAX Forum NWG profile C. 1.2.2.
Chapter 1 - System Description 4Motion Solution Reference point R3 consists of the set of control plane protocols between the ASN and CSN to support AAA, policy enforcement and mobility management capabilities. It also encompasses the bearer plane methods (e.g. tunneling) to transfer user data between the ASN and CSN.
Chapter 1 - System Description 1.3 The Base Transceiver Station The Base Transceiver Station The 4Motion solution features a multi-carrier, high-power Base Transceiver Station (BTS). Designed for high availability and redundancy, it utilizes a central networking and management architecture, and a range of diversity schemes. The BTS main features include: R1 support - 802.16e interface handling (e.g.
Chapter 1 - System Description The Base Transceiver Station 1.3.1 The Indoor Macro BTS 1.3.1.1 The BreezeMAX Shelf The BreezeMAX shelf is an indoor -48 VDC powered 8U cPCI PICMG 2.x standard shelf prepared for installation in a 19" or 21" (ETSI) rack. This chassis has a total of nine double-Euro (6U high) slots and six single-Euro (3U high) slots. All the modules are hot swappable, and high availability can be provided through multiple redundancy schemes.
Chapter 1 - System Description The Base Transceiver Station Table 1-1: BreezeMAX Shelf Modules Module Description AU 6U high access unit, 4-channel, 802.16e MAC-modem-baseband IF card AVU 2U high air ventilation unit, 9+1 redundancy fans with alarm control The six single-Euro slots are intended for one or two redundant Power Interface Units (PIUs) and up to four redundant Power Supply Units (PSUs).
Chapter 1 - System Description The Base Transceiver Station L2 switch forwarding capabilities Internal and external traffic VLAN encapsulation QoS marking Overall operation, control and shelf management, including AU diagnostics and control, PSU monitoring, AVU management and redundancy support Local and remote extensive management support via CLI (Telnet, SSH) and SNMP, including software download, fault and performance management Alarm management, including external alarm inputs and activati
Chapter 1 - System Description The Base Transceiver Station Handover functionality GRE encapsulation/decapsulation IP-in-IP encapsulation/decapsulation Transparent VLAN (single tag) and QinQ (dual tag) encapsulation Fragmentation/reassembly R4/R6/R3 interfaces implementation Keep-alive signaling towards the relevant BSs and other ASN-GWs for enhanced management of service availability When several shelves are collocated, the NPU cascade interface can be used for shelf interconnection.
Chapter 1 - System Description The Base Transceiver Station Wide variety of reuse patterns Advanced channel coding (CTC) HARQ Rate adaptation High-performance CDMA detector IF interface to RF ODU MAC-PHY interface Link management (network entry, basic capabilities negotiation, authentication and registration, connection management) Fragmentation/ reassembly QoS PEP for air interface traffic QoS DSCP marking Scheduling - connections quota computation for all data delivery types Fr
Chapter 1 - System Description The Base Transceiver Station Context client/server ID to IP address resolution for ASN entities IP and Ethernet convergence sublayers Keep-alive signaling towards the relevant ASN-GWs for enhanced management of service availability The AU design is based on Alvarion's programmable, off-the-shelf, cutting-edge components, in order to provide a future-proof solution with excellent cost and performance.
Chapter 1 - System Description The Base Transceiver Station Table 1-2: PSU Requirements, Configurations with one NPU (excluding PSU redundancy) 1.3.1.6 Number of AUs Minimum Required Number of PSUs 1-4 2 5-6 3 AVU The 2U-high AVU includes a 1U-high integral chamber for inlet airflow and a 1U-high fan tray with an internal alarm module. To support high availability, the fan tray includes 10 brushless fans (9 fans are sufficient for cooling a fully-loaded shelf).
Chapter 1 - System Description 1.3.3 The Base Transceiver Station ODU The outdoor unit (ODU) is a high-power, multi-carrier radio unit that connects to one or more external antennas. It is designed to provide high system gain and interference robustness utilizing high transmit power and low noise figure. It is HW-ready for supporting a bandwidth of up to 20 MHz, enabling future options such as increased capacity through the use of a multiplexer or wider frequency channels.
Chapter 1 - System Description The Base Transceiver Station Table 1-3: ODU Types Band (GHz) ODU Frequency Range (MHz) ODU Port Configuration ODU Bandwidth (MHz) ODU Max Tx Power (dBm) 2.
Chapter 1 - System Description The Base Transceiver Station complement the 4Motion solution, Alvarion works closely with several antenna suppliers to ensure availability of antennas that comply with its requirements. In cases where the operator prefers other antenna vendors, Alvarion can provide a recommended antenna specification based on the required antennas types. For more information on recommended antenna configurations and required antennas refer to “Antenna Configurations” on page 681. 1.3.
Chapter 1 - System Description 1.4 Element Management Systems Element Management Systems The end-to-end IP-based architecture of the system enables full management of all components, using standard management tools. An SNMP agent in the NPU implements proprietary MIBs for remote setting of operational modes and parameters of the Base Transceiver Station equipment. Security features incorporated in the equipment restrict the access for management purposes.
Chapter 1 - System Description Element Management Systems Device embedded software upgrade BTS duplication and template-based configuration modification of multiple BTS simultaneously. Security Management Event Forwarding to other Network Management Systems.
Chapter 1 - System Description Specifications 1.5 Specifications 1.5.1 Modem & Radio Table 1-4: General Modem & Radio Specifications Item Description Operation Mode TDD Channel Bandwidth 5 MHz 7 MHz 10 MHz 1.5.2 Central Frequency Resolution 0.
Chapter 1 - System Description Specifications 1.5.3 ODUs 1.5.3.1 2.0 GHz Band Table 1-6: 2.0 GHz Band 1x1 ODU Specifications Item Description Frequency Band ODU-2020-2220-000N-36-1x1-N-0: 2020-2220 MHz Ports Configuration 1x1 (1Rx, 1Tx) Bandwidth Support Up to 10 MHz Maximum Tx Power ) 36 dBm Tx Power Control Range 6 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.6 dB typical, 6.
Chapter 1 - System Description Specifications 1.5.3.2 2.3 GHz Band 1.5.3.2.1 2.3 GHz Band 1x1 ODUs Table 1-7: 2.3 GHz Band 1x1 ODUs Specifications Item Description Frequency Band ODU-HP-2.3: 2300-2360 MHz ODU-HP-2.3-WCS: 2305 - 2317, 2348 - 2360 MHz (incliudes WCS filter) ODU-HP-2.
Chapter 1 - System Description 1.5.3.2.2 Specifications 2.3 GHz Band 2x2 ODU Table 1-8: 2.3 GHz Band 2x2 ODU Specifications Item Description Frequency Band ODU-2300-2400-000N-38-2X2-N-0: 2300-2400 MHz* Ports Configuration 2x2 (2Rx, 2Tx) Bandwidth Support Up to 30 MHz Beam Forming Support Yes Maximum Tx Power ) 38 dBm* Tx Power Control Range 10 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.
Chapter 1 - System Description Specifications 1.5.3.3 2.5 GHz Band 1.5.3.3.1 2.5 GHz Band 1x1 ODUs Table 1-9: 2.5 GHz Band 1x1 ODUs Specifications Item Description Frequency Band ODU-HP-2.5A: 2496-2602 MHz (Band A) ODU-HP-2.
Chapter 1 - System Description 1.5.3.3.2 Specifications 2.5 GHz Band 2x2 ODUs Table 1-10: 2.
Chapter 1 - System Description 1.5.3.3.3 Specifications 2.5 GHz Band 4x2 ODUs Table 1-11: 2.
Chapter 1 - System Description 1.5.3.4 Specifications 3.3 GHz Band Table 1-12: 3.3 GHz Band 1x1 ODU Specifications Item Description Frequency Band ODU-3300-3355-000N-32-1x1-N-0: 3300-3355 MHz Ports Configuration 1x1 (1Rx, 1Tx) Bandwidth Support Up to 14 MHz Maximum Tx Power 32 dBm Tx Power Control Range 10 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.5 dB typical, 5.
Chapter 1 - System Description Specifications 1.5.3.5 3.5 GHz Band 1.5.3.5.1 3.5 GHz Band 1x1 ODUs Table 1-13: 3.5 GHz Band 1x1 ODUs Specifications Item Description Frequency Band ODU-HP-TDD-3.4a: 3400-3455 MHz ODU-HP-TDD-3.4b: 3445-3500 MHz ODU-HP-TDD-3.5a: 3500-3555 MHz ODU-HP-TDD-3.
Chapter 1 - System Description 1.5.3.5.2 Specifications 3.5 GHz Band 2x2 ODUs Table 1-14: 3.5 GHz Band 2x2 ODUs Specifications Item Description Frequency Band ODU-3400-3600-000N-37-2x2-N-0: 3400-3600 MHz Ports Configuration 2x2 (2Rx, 2Tx) Bandwidth Support Up to 30 MHz Beam Forming Support Yes Maximum Tx Power ) 37 dBm Tx Power Control Range 10 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.
Chapter 1 - System Description 1.5.3.5.3 Specifications 3.5 GHz Band 4x2 ODUs Table 1-15: 3.5 GHz Band 4x2 ODUs Specifications Item Description Frequency Band ODU-3400-3600-000N-37-4x2-N-0: 3400-3600 MHz Ports Configuration 4x2 (4Rx, 2Tx) Bandwidth Support Up to 20 MHz Maximum Tx Power ) 37 dBm Tx Power Control Range 10 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.5 dB typical, 5.
Chapter 1 - System Description 1.5.3.6 Specifications 3.6 GHz Band Table 1-16: 3.6 GHz Band 4x2 ODU Specifications Item Description Frequency Band ODU-3600-3800-000N-36-4x2-N-0: 3600-3800 MHz Ports Configuration 4x2 (4Rx, 2Tx) Bandwidth Support Up to 20 MHz Maximum Tx Power ) 36 dBm Tx Power Control Range 10 dB, in 1 dB steps Tx Power Accuracy +/- 1 dB Maximum Input Power @ antenna port -60 dBm before saturation, -8 dBm before damage Noise Figure 4.5 dB typical, 5.
Chapter 1 - System Description 1.5.4 Specifications AU - ODU Communication Table 1-17: AU - ODU Communication Item Description IF Frequency Tx: 240 MHz Rx: 140 MHz Ref Synchronization Frequency 64 MHz Bi-Directional Control Frequency 14 MHz IF cable Impedance 50 Ohm Maximum IF cable Attenuation 10 dB @ 240 MHz 7.
Chapter 1 - System Description 1.5.
Chapter 1 - System Description 1.5.7 Specifications Standards Compliance, General Table 1-20: Standards Compliance, General Type Standard EMC ETSI EN 301 489-1/4 FCC Part 15 EN60950-1 Safety UL 60950-1 Environmental ETS 300 019: Part 2-1 T 1.2 & part 2-2 T 2.3 for indoor & outdoor Part 2-3 T 3.2 for indoor Part 2-4 T 4.1E for outdoor ETSI EN 302 326 Radio ETSI EN 302 544 FCC part 15, part 27, part 25 1.5.
Chapter 1 - System Description 1.5.9 Specifications Mechanical and Electrical 1U = 44.45 mm (1.75”). 1HP = 5.08 mm (0.2”) 1.5.9.1 BreezeMAX Shelf Table 1-22: BreezeMAX Shelf, Mechanical & Electrical Specifications 1.5.9.2 Item Description Dimensions 8U ETSI type shelf, 8U x 43.2 x 24 cm Weight 6.9 Kg (excluding AVU) AVU Table 1-23: AVU, Mechanical & Electrical Specifications 1.5.9.3 Item Description Dimensions 2U x 84HP x 16 cm Weight 1.
Chapter 1 - System Description 1.5.9.4 Specifications PSU Table 1-25: PSU, Mechanical & Electrical Specifications Item Description Dimensions 3U x 5HP x 16 cm Weight 0.7 Kg Power Output 300W maximum output power Efficiency: 80% minimum 1.5.9.5 NPU Table 1-26: NPU, Mechanical & Electrical Specifications Item Description Dimensions 6U x 7HP x 16 cm Weight 0.7 Kg Power Consumption 68W maximum, 61W typical Connectors 1.5.9.
Chapter 1 - System Description 1.5.9.7 Specifications NAU Table 1-28: NAU, Mechanical & Electrical Specifications Item Description Dimensions 420 x 340 x 280 mm Weight 15 Kg Power Source -40.5 to -60 VDC Power Consumption 140W maximum NPU Connectors AU Connectors 1.5.9.
Chapter 1 - System Description 1.5.9.9 Specifications DAU Table 1-30: DAU, Mechanical & Electrical Specifications Item Description Dimensions 420 x 340 x 280 mm Weight 15 Kg Power Source -40.
Chapter 1 - System Description 1.5.9.10 Specifications GPS Receiver Table 1-31: GPS Receiver, Mechanical & Electrical Specifications 1.5.9.11 Item Description Dimensions Tubular enclosure, 15.5 D x 12.7 H cm Weight 0.363 Kg Power Source 12 VDC from the NPU Power Consumption 6W maximum Connector 12-pin round plug ODU Power Feeder Table 1-32: ODU Power Feeder, Mechanical & Electrical Specifications Item Description Dimensions 15.7 x 14.6 x 3.17 cm Weight 0.6 Kg Power Source -40.
Chapter 1 - System Description Specifications 1.5.10 Antennas 1.5.10.1 2.x GHz Antennas Table 1-33: BS-RET-DP-ANT 2.3-2.7 Specifications 4Motion Item Description Frequency Band (MHz) 2300-2700 Number of Elements 2 Polarization Linear, +/-45° Gain (dB) 17.3 @ 2.4 GHz 18 @ 2.6 GHz Azimuth Beamwidth (degrees) 65 Elevation Beamwidth (degrees) 6.
Chapter 1 - System Description Specifications Table 1-34: BS-RET-DDP-ANT 2.3-2.7 Specifications 4Motion Item Description Frequency Band (MHz) 2300-2700 Number of Elements 4 Polarization Linear, 2 x +/-45° Gain (dB) 17.3 @ 2.4 GHz 18 @ 2.6 GHz Azimuth Beamwidth (degrees) 65 Elevation Beamwidth (degrees) 6.
Chapter 1 - System Description Specifications Table 1-35: ANT.2.3-2.7GHz, D/S,65°,16±0.5dBi Specifications Item Description Frequency Band (MHz) 2300-2700 Number of Elements 2 Polarization Linear, +/-45° Gain (dB) 16 +/- 0.
Chapter 1 - System Description 1.5.10.2 Specifications 3.5 GHz Antennas Table 1-36: BS-RET-DP-ANT 3.3-3.8 Specifications 4Motion Item Description Frequency Band (MHz) 3300-3800 Number of Elements 2 Polarization Linear, +/-45° Gain (dB) 18 Azimuth Beamwidth (degrees) 65 Elevation Beamwidth (degrees) 6.
Chapter 1 - System Description Specifications Table 1-37: BS-RET-DDP-ANT 3.3-3.8 Specifications 4Motion Item Description Frequency Band (MHz) 3300-3800 Number of Elements 4 Polarization Linear, 2 x +/-45° Gain (dB) 18 Azimuth Beamwidth (degrees) 65 Elevation Beamwidth (degrees) 6.
Chapter 1 - System Description Specifications Table 1-38: ANT.3.5GHz, D/S,65°,16±0.5dBi Specifications Item Description Frequency Band (MHz) 3300-3800 Number of Elements 2 Polarization Linear, +/-45° Gain (dB) 16 +/- 0.
Chapter 2 Commissioning
Chapter 2 - Commissioning In This Chapter: “Initial NPU Configuration” on page 54 “Completing the Site Configuration Using AlvariSTAR” on page 58 4Motion 53 System Manual
Chapter 2 - Commissioning Initial NPU Configuration 2.1 Initial NPU Configuration 2.1.1 Introduction After completing the installation process, as described in the preceding chapter, some basic NPU parameters must be configured locally using the CLI via the MON port of the NPU. Refer to “Using the Command Line Interface for Management” on page 68 for information on how to access the CLI either via the MON port or via Telnet and how to use it.
Chapter 2 - Commissioning Initial NPU Configuration The default connectivity mode is In-Band (IB) via the Data port. Alternatively, the NPU can be managed Out-Of-Band (OOB) via the dedicated Management port. To view the current and configured connectivity mode, use the command: npu# show connectivity mode To change the connectivity mode to Out-Of-Band, use the command: npu(config)# connectivity mode outband (for details refer to “Configuring the IP Connectivity Mode” on page 100). 2.1.3.
Chapter 2 - Commissioning 2 Initial NPU Configuration Configure the IP address (x.x.x.x) and subnet mask (y.y.y.y). For details refer to “Assigning an IP address to an interface” on page 121: npu(config-if)# ip address x.x.x.x y.y.y.y 2.1.3.
Chapter 2 - Commissioning Initial NPU Configuration for UDP and TCP ports 161 and 162 from Outside IP (connected to the managed device’s LAN) to Inside IP (connected to the management system’s LAN). 2.1.6 Mapping the AU Software Version To define the software version to be used by all AUs run the command: npu(config)# map au default , where image name is the required AU software version (to view the AU software versions available in the NPU run the command npu# show au image repository). 2.
Chapter 2 - Commissioning Completing the Site Configuration Using AlvariSTAR 2.2 Completing the Site Configuration Using AlvariSTAR 2.2.1 Introduction After completion of the initial configuration you should be able to manage the new Site using AlvariSTAR and continue configuring (at least) all mandatory parameters to enable the necessary services. For details on how to use AlvariSTAR for managing 4Motion sites refer to the AlvariSTAR and 4Motion Device Manager User Manuals.
Chapter 2 - Commissioning 2.2.2 Site Configuration 2.2.2.1 General Tab Completing the Site Configuration Using AlvariSTAR ASN Topology - the default is Distributed ASNGW. If you change it to Centralized ASNGW click Apply for the device to accept the change. 2.2.3 Connectivity Configuration (optional) 2.2.3.1 IP Interface Screen Configure the IP address of the Bearer interface: 2.2.3.2 8 Change the IP and/or any other parameter value, except VLAN ID. 9 Click on Apply to accept the changes.
Chapter 2 - Commissioning 2 2.2.4.2 Completing the Site Configuration Using AlvariSTAR In the New AU definition window, define the following: » AU number (AU Slot) » Type (in current release only AU 4x4 Modem is applicable) 3 Click Apply. 4 Repeat the process for all required AU entities. ODU ODU entities must be created for all installed ODUs (you may create an ODU entity also for ODUs that are not installed yet).
Chapter 2 - Commissioning 2.2.4.4 Completing the Site Configuration Using AlvariSTAR 3 Click Apply. 4 Repeat the process for all required Antenna entities. GPS The default GPS Type is Trimble. If there is no GPS, the value should be changed to None. Click Apply for the device to accept the change. 2.2.5 ASNGW Configuration NOTE ASNGW screens are available only for Distributed ASNGW topology (see also “Site Configuration” on page 59. 2.2.5.
Chapter 2 - Commissioning 2 2.2.5.2.2 Completing the Site Configuration Using AlvariSTAR Click Apply for the device to accept the configuration. Service Groups Tab At least one Service Group associated with a defined Service Interface for data must be defined. If a dedicated management station for CPEs is being used, a suitable Service Group associated with the defined Service Interface for management must also be defined.
Chapter 2 - Commissioning 3 Completing the Site Configuration Using AlvariSTAR The new Service Profile added to the list of available Service Profiles in the navigation tree. Select it to continue the configuration process. 4 Click Add in the Service Flow area. 5 Configure the applicable general parameters of the Service Flow.
Chapter 2 - Commissioning Completing the Site Configuration Using AlvariSTAR 2 Click Apply for the device to accept the configuration. 3 You will be prompted to properly configure some additional parameters. 4 Click Apply for the device to accept the configuration. 5 Select the Radio Advanced screen and click Apply to complete the configuration. 2.2.6.3 Connectivity 2.2.6.3.1 Basic Screen - Bearer Tab 1 2 2.2.6.3.2 2.2.
Chapter 2 - Commissioning 4 Completing the Site Configuration Using AlvariSTAR At least one Site Sector Association must be defined for each Site Sector. Click on the Add Sector Association button and configure all the parameters in the applicable line of the Sector site Association table: 5 2.2.8 » BS ID LSB » AU Slot Number » AU Port Number » ODU Number » ODU Port Number » Antenna Number » Antenna Port Number Click Apply for the device to accept the configuration.
Chapter 3 Operation and Administration Using the CLI
Chapter 3 - Operation and Administration Using the CLI In This Chapter: “Using the Command Line Interface for Management” on page 68 “Shutting Down/Resetting the System” on page 94 “NPU Configuration” on page 97 “Managing MS in ASN-GW” on page 412 “Managing AUs” on page 414 “Managing ODUs” on page 429 “Managing Antennas” on page 444 “Managing BSs” on page 452 “Managing Sectors” on page 642 “Monitoring Performance of Hardware and Software Components” on page 656 “Troubleshooting” on pa
Chapter 3 - Operation and Administration Using the CLI 3.1 Using the Command Line Interface for Management Using the Command Line Interface for Management All 4Motion system components are managed via the NPU module. The AU is not accessed directly: any configuration change or status enquiry is sent to the NPU that communicates with other system components.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management “Managing Users and Privileges” on page 78 “Managing Secure Shell (SSH) Parameters” on page 87 “Managing the Session” on page 89 3.1.1 Managing the Macro Outdoor BTS The following section describe the CLI when using it to manage the Indoor Macro BTS equipment. The same CLI is used also to manage the Macro Outdoor BTS equipment, with the following changes: 3.1.1.
Chapter 3 - Operation and Administration Using the CLI 3.1.1.5 Using the Command Line Interface for Management Power Feeder Power Feeders are not applicable for the Macro Outdoor BTS 3.1.1.6 AUs Up to a maximum of six AUs can be supported in the Macro Outdoor BTS. The following table details the mapping of Macro Outdoor BTS AUs to Slot numbers: Table 3-1: Mapping of Macro Outdoor BTS AUs to Slot # 3.1.1.
Chapter 3 - Operation and Administration Using the CLI 1 Using the Command Line Interface for Management Use the MON cable to connect the MON connector of the NPU to the COM port of your ASCII ANSI terminal or PC. The COM port connector of the Monitor cable is a 3-pin to 9-pin D-type plug. 2 Run a terminal emulation program, such as HyperTerminal™.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management To access the CLI from a remote terminal, execute the following procedure: IMPORTANT The in-band connectivity mode is the default connectivity mode; the DATA port and external-management VLAN are the default Etherent port and IP interface that are configured for the in-band connectivity mode. The following procedure can be used for accessing the CLI when the in-band connectivity mode is selected.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management NOTE The default login ID and password are: Login ID: admin Password: admin123 After you provide your login information, the following command prompt is displayed: npu# This is the global command mode. For more information about different command modes, refer to Section 3.1.3. 3.1.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management Table 3-4: Commands to Enter/Exit a Command Mode Enter the interface configuration mode npu(config)# interface npu(config-if)# { |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au} Exit the configuration mode and enter the global command mode.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management Table 3-5: Conventions Used in the 4Motion Command Syntax [] <> | Indicates that the parameter enclosed within these brackets is optional. npu(config)# reboot from shadow [] Indicates that the parameter is mandatory and requires a user-defined value (and not a discrete value).
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management “Using the CLI Help” on page 76 “Using the History Feature” on page 77 “Using Miscellaneous Commands” on page 77 “Privilege Levels” on page 78 3.1.5.1 Using Control Characters Control characters refer to special characters that you can use to recall or modify previously-executed commands.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management Specify the command name as the parameter to view help for this command. For example, to obtain help for the show resource limits command, run the following command: npu# help “show resource limits” The help for the show resource limits command is displayed. If you do not provide the command name as the parameter, all commands that can be executed in the current command mode are displayed. 3.1.5.
Chapter 3 - Operation and Administration Using the CLI 3.1.5.5 Using the Command Line Interface for Management Privilege Levels All commands that can be executed using the CLI are assigned privilege levels between 0 and 10, where 0 is the lowest, and 10 is the highest. In addition, each user is assigned a privilege level; the user can access only those commands for which the privilege level is the same or lower than the user’s privilege level. The default user, admin, is assigned privilege level 10.
Chapter 3 - Operation and Administration Using the CLI 3.1.6.1 Using the Command Line Interface for Management Managing Users You can add/modify/delete one or more users for accessing the CLI either through a local or remote terminal. IMPORTANT Only users who have logged in as admin can add/modify/delete users. This section describes the commands for: “Adding/Modifying Users” on page 79 “Deleting a User” on page 80 3.1.6.1.
Chapter 3 - Operation and Administration Using the CLI Syntax Description Command Modes 3.1.6.1.2 Using the Command Line Interface for Management Parameter Description Presence Default Value Possible Values username Indicates the user name of the user to be added. Mandatory N/A String (up to 20 characters and case-sensitive) password Indicates the password to be assigned to the user to be added.
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description Command Modes 3.1.6.2 Using the Command Line Interface for Management 10 Parameter Description Presence Default Value Possible Values username Indicates the username of the user to be deleted.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management IMPORTANT After you execute this command, any user can use this password to enable the (higher) privilege level for which you have configured the password. For more information about using passwords for enabling higher privilege levels, refer Section 3.1.6.3. IMPORTANT An error may occur if: You are trying to configure a password for a privilege level that is higher than your default privilege level.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management npu(config)# no enable password [Level <0-10>] IMPORTANT An error may occur if: The privilege level that you have specified is not within the range, 0-10. You are trying to delete a password for a privilege level that is higher than your default privilege level. Command Syntax npu(config)# no enable password [Level <0-10>] Privilege Level 10 Syntax Description Command Syntax 3.1.6.
Chapter 3 - Operation and Administration Using the CLI 3.1.6.3.1 Using the Command Line Interface for Management Enabling a Higher Privilege Level To enable a higher privilege level: 1 Log in to the CLI. 2 Run the following command to specify the privilege level and password: npu(config)# enable [Level <0-10>] 3 At the password prompt, specify the password configured for the privilege level that you have specified.
Chapter 3 - Operation and Administration Using the CLI Syntax Description Command Modes 3.1.6.3.2 Using the Command Line Interface for Management Parameter Description Presence Default Value Possible Values [Level <0-10>] Indicates the privilege level you want to enable.
Chapter 3 - Operation and Administration Using the CLI Command Syntax npu# show users Privilege Level 1 Display Format Line Command Syntax Global command mode 3.1.6.5 0 con Using the Command Line Interface for Management User Peer Address Displaying All Users To display all users, run the following command: npu# listuser Command Syntax npu# listuser Privilege Level 1 Display Format User Mode User 1 User 2 User 3 Command Syntax 3.1.6.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management Command Syntax npu# show privilege Privilege Level 1 Display Format Current privilege level is Command Syntax Global command mode 3.1.7 Managing Secure Shell (SSH) Parameters The SSH parameters define the parameters used for establishing remote secure access to the device using SSH protocol rather than the plaintext-based insecure Telnet protocol.
Chapter 3 - Operation and Administration Using the CLI Syntax Description Using the Command Line Interface for Management Parameter Description Presence Default Value Possible Values version compatibility The SSH version that can be used: The default is SSH version 2. The command Optional SSH2 version compatibility des-cbc des-cbc npu(config)# ip ssh version compatibility enables compatibility with both SSH version 1 and SSH version 2. Command Modes 3.1.7.
Chapter 3 - Operation and Administration Using the CLI 3.1.7.3 Using the Command Line Interface for Management Displaying the SSH Parameters To display the current configuration of the SSH parameters, run the following command: npu# show ip ssh Command Syntax npu# show ip ssh Privilege Level 1 Display Format Version Cipher Algorithm : Authentication Command Modes 3.1.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management To resume the session, you must enter the password used for initiating it. Command Syntax npu# lock Privilege Level 10 Command Modes Global command mode 3.1.8.2 Managing the Session Timeout The session timeout parameter defines the maximum allowed inactivity time after which the session will be terminated automatically. The default timeout is 1800 seconds.
Chapter 3 - Operation and Administration Using the CLI Using the Command Line Interface for Management “Configuring the Session Timeout” on page 91 “Restoring the Default Value of the Session Timeout” on page 92 Command Syntax npu(config)# line {console | vty} Privilege Level 10 Syntax Description Parameter Description Presence Default Value Possible Values console | vty The terminal running the session to be managed: Mandatory N/A console Select console if you are connected via the
Chapter 3 - Operation and Administration Using the CLI Syntax Description Command Modes 3.1.8.2.3 Using the Command Line Interface for Management Parameter Description Presence Default Value Possible Values The session timeout, in seconds.
Chapter 3 - Operation and Administration Using the CLI Syntax Description Using the Command Line Interface for Management Parameter Description Presence Default Value Possible Values console | vty The session for which the timeout should be displayed: Mandatory N/A console console: a session via the MON port (even if there is currently no active session via the MON port). vty #: An active Telnet/SSH session number #.
Chapter 3 - Operation and Administration Using the CLI 3.2 Shutting Down/Resetting the System Shutting Down/Resetting the System This section describes the commands for: “Shutting Down the System” on page 94 “Managing System Reset” on page 95 3.2.1 Shutting Down the System You can, at any time, use the CLI to shut down the 4Motion system. When you execute the shutdown command, the system and all its processes are gracefully shut down.
Chapter 3 - Operation and Administration Using the CLI Command Modes 3.2.2 Shutting Down/Resetting the System Global command mode Managing System Reset System reset refers to a complete shutdown and reboot of the 4Motion system. You can use the CLI to manually reset the system. It is also possible that the system may be reset because of an internal or external error, or after the NPU is upgraded.
Chapter 3 - Operation and Administration Using the CLI 3.2.2.2 Shutting Down/Resetting the System Displaying the Reason for the Last System Reset The 4Motion system may be reset because of any of the following reasons. NPU upgrade Health failure (an internal module does not respond to the periodic health messages sent by the system) Internal error: » A system module did not initialize correctly » The software image to be used for rebooting the system is invalid or inaccessible.
Chapter 3 - Operation and Administration Using the CLI 3.3 NPU Configuration NPU Configuration After installing, commissioning, and powering up 4Motion, you can use the CLI to configure 4Motion and make it completely operational in the network. Configuration information is stored in a configuration file that resides in the NPU flash. When you power up 4Motion for the first time after installation, the system boots up using the factory default configuration.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration “Configuring the SNMP/Trap Manager” on page 370 “Configuring the 4Motion Shelf” on page 379 3.3.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration To enable separation of the bearer IP and NMS IP domains, the following (user-configurable) connectivity modes are defined: Out-of-band connectivity mode: In this connectivity mode, the bearer and external NMS IP domains are separated at the Ethernet interface. The DATA port and bearer VLAN is used for the bearer IP domain, and the MGMT port and external-management VLAN is used for external NMS connectivity.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Table 3-9: Ethernet and IP Domain VLAN-to-Connectivity Mode Configuration Connectivity Mode Bearer IP Domain External-Management IP Domain Local-management IP Domain Out-of-band DATA port MGMT port CSCD port Bearer VLAN External-management Local-management VLAN DATA port In-band DATA port VLAN CSCD and MGMT ports Bearer VLAN External-management VLAN Local-management VLAN Unified DATA por
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values {inband | outband | unified} Indicates the connectivity mode to be configured. Mandatory inband inband outband unified Command Modes 3.3.1.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration of two or more 4Motion chassis. (Concatenation is not supported in the current release.) MGMT port: A Fast Ethernet interface that provides a dedicated Ethernet interface for external EMS server connectivity. In some configurations the MGMT port is used for connecting the local NMS server (IP-based craft terminal). You can configure the speed, duplex, and MTU for these interfaces.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Table 3-10: Default VLAN IDs Interface Default VLAN ID Local-management 9 Internal-management 10 (non-configurable) Bearer 11 External-management 12 AU Maintenance 14 In addition to the physical and IP interfaces, 4Motion defines the following virtual interfaces. These interfaces are used only for applying Access Control Lists (ACLs) for filtering traffic destined towards the NPU or AUs.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Table 3-11: Ethernet Interfaces - Types, Port Numbers, and Member VLANs Interface Type Physical Interfaces Port Number Member VLANs Fast Ethernet MGMT 0/8 Local-management (in the in-band or unified connectivity modes) External-management (only in the out-of-band connectivity mode) Gigabit Ethernet CSCD 0/9 Local-management DATA 0/10 Bearer· External-management (only in-band connectivity mode) Multiple Serv
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Table 3-12: Parameters for Configuring the Interface Configuration Mode (Ethernet Interfaces) Interface Parameter Example Fast Ethernet npu(config)# interface fastethernet 0/8 Gigabit Ethernet npu(config)# interface gigabitethernet 0/9 npu(config)# interface gigabitethernet 0/10 IMPORTANT To enable the interface configuration mode for physical interfaces, sp
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values Indicates the type of physical interface (Gigabit Ethernet or Fast Ethernet) for which the configuration mode is to be enabled. Mandatory N/A fastethernet Indicates the port number of the physical interface for which the configuration mode is to be enabled.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration “Configuring the MTU for physical interfaces” on page 109 NOTE There is no need to shut down the interface for configuring its parameters. 3.3.2.1.2.1 Shutting down the interface Run the following command to shut down this physical interface: npu(config-if)# shutdown IMPORTANT Beware from shutting down the interface you use for accessing the device.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration After you disable auto-negotiation, you can manually configure the port speed and duplex status. For details, refer to Section 3.3.2.1.2.3 and Section 3.3.2.1.2.4 Command Syntax npu(config-if)# auto-negotiate Privilege Level 10 Command Modes Interface configuration mode 3.3.2.1.2.3 npu(config-if)# no auto-negotiate Specifying the Duplex Status The duplex status for an interface can be either full-duplex or half duplex.
Chapter 3 - Operation and Administration Using the CLI 3.3.2.1.2.4 NPU Configuration Specifying the port speed If you have disabled the auto-negotiation feature, you can run the following command configure the port speed to be used for this physical interface. npu(config-if)# speed {10 | 100 | 1000} By default, the port speed for the Fast Ethernet interfaces is 100 Mbps, and for the Gigabit Ethernet interfaces is 1000 Mbps.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration npu(config-if)# mtu Command Syntax npu(config-if)# mtu Privilege Level 10 Syntax Description Parameter Description Presence Default Value Possible Values Indicates the MTU (in bytes) to be configured for the physical interface. mandatory For the DATA interface the default is 1664. 1518-9000 for the DATA interface.
Chapter 3 - Operation and Administration Using the CLI 3.3.2.1.3.1 NPU Configuration Enabling/Disabling VLAN Translation By default, VLAN translation is disabled. Run the following command to enable/disable VLAN translation on the DATA (gigabitethernet 0/10) interface: npu(config-if)# vlan mapping {enable|disable} IMPORTANT An error may occur when you run this command: For an interface other than the DATA port (0/10).
Chapter 3 - Operation and Administration Using the CLI NPU Configuration IMPORTANT An error may occur if: The original and/or translated VLAN ID that you have specified is not within the allowed range. The translated VLAN ID that you have specified is already a member VLAN for this port. You are trying to create a VLAN translation entry for a VLAN that is not a member of DATA port. A VLAN translation mapping already exists for the original VLAN IDs that you have specified.
Chapter 3 - Operation and Administration Using the CLI 3.3.2.1.3.3 NPU Configuration Deleting a VLAN Translation Entry To delete an existing VLAN translation entry, run the following command: npu(config-if)# no vlan mapping {all | } Specify all if you want to delete all the VLAN translation mapping entries. Specify the VLAN identifiers of the translation entry if you want to delete a specific VLAN entry.
Chapter 3 - Operation and Administration Using the CLI Command Modes 3.3.2.1.4 NPU Configuration Global command mode Terminating the Interface Configuration Mode To terminate the interface configuration mode, run the following command: npu(config-if)# exit Command Syntax npu(config-if)# exit Privilege Level 10 Command Modes Interface configuration mode 3.3.2.1.
Chapter 3 - Operation and Administration Using the CLI Syntax Description Display Format Command Modes 3.3.2.1.6 NPU Configuration Parameter Description Presence Default Value Possible Values [id ] Indicates the VLAN ID for which membership information is to be displayed. Do not specify any value for this parameter if you want to view VLAN membership information for all VLANs.
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values Indicates the type of physical interface for which VLAN membership information is to be displayed. Optional N/A fastethernet Indicates the ID of the physical interface for which VLAN membership information is to be displayed.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Command Syntax npu# show interface gigabitethernet vlan mapping Privilege Level 1 Syntax Description Parameter Description Presence Default Value Possible Values Indicates the identifier of the Gigabit Ethernet interface for which VLAN translation entries are to be displayed. Mandatory N/A 0/10 In current release VLAN Mapping is supported only on the DATA port (interface-id 0/10).
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description NPU Configuration 10 Parameter Description Presence Default Value Possible Values {8100 | 88A8 | 9100 | 9200} Indicates the type of Ether Type. Mandatoryl 88A8 8100 88A8 9100 9200 Command Modes 3.3.2.2.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Internal-management External-management Bearer IMPORTANT You cannot modify the IP address and VLAN identifier for the internal-management interface. To configure an IP interface: 1 Enable the interface configuration mode (refer Section 3.3.2.3.1). 2 You can now: » Shut down/Enable the Interface (refer to Section 3.3.2.3.2). » Assign an IP address to an interface (refer to Section 3.3.2.3.3).
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Table 3-13: Parameters for Configuring the Interface Configuration Mode (IP Interfaces IP Interface Parameter Example Internal-management internal-mgmt npu(config)# interface internal-mgmt External-management external-mgmt npu(config)# interface external-mgmt Bearer bearer npu(config)# interface bearer Local-management local-mgmt npu(config)# interface local-mgmt IMPORTANT To enable the interface configuration mode for
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values internal-mgmt |external-mgmt | bearer | local-mgmt Indicates the IP interface for which the configuration mode is to be enabled. Mandatory N/A internal-mgmt external-mgmt bearer local-mgmt Command Modes 3.3.2.3.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration IMPORTANT You can configure the IP address and subnet mask for only the external-management, local-management, and bearer interfaces. The bearer interface IP address is used also in other interfaces such as the ASN and CSN interfaces. If you change the bearer interface IP address, you must save the configuration (run the command npu# write) and reboot the NPU to apply changed IP address on ASN and CSN interfaces.
Chapter 3 - Operation and Administration Using the CLI Command Modes 3.3.2.3.4 NPU Configuration Indicates the subnet mask to be assigned to this IP interface. Mandatory 255.255. 255.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration IMPORTANT An error may occur if: The VLAN ID you have specified is not within the specified range, or is in use by another interface. Refer the syntax description for the VLAN ID range. The VLAN ID is already used as a translated VLAN or a VLAN translation entry already exists for this VLAN. You are trying to run this command for the internal-management interface.
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description Command Modes 3.3.2.3.7 NPU Configuration 10 Parameter Description Presence Default Value Possible Values Indicates the MTU (in bytes) to be configured for the IP interface.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Command Syntax npu# show ip interface [{internal-mgmt | external-mgmt | bearer | local-mgmt}] Privilege Level 1 Syntax Description Parameter Description Presence Defaul t Value Possible Values {internal-mgmt | external-mgmt | bearer | local-mgmt} Indicates the interface for which configuration information is to be displayed.
Chapter 3 - Operation and Administration Using the CLI 3.3.2.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Command Syntax npu# show interfaces [{[ ] | internal-mgmt | external-mgmt | bearer | local-mgmt | npu-host | all-au}] Privilege Level 1 Syntax Description Parameter Description Presence Default Value Possible Values [{[ ] | internal-mgmt | external-mgmt | bearer | local-mgmt | npu-host | all-au}] Indicates the type of interface (physical, IP, or virtual) for which
Chapter 3 - Operation and Administration Using the CLI Display Format (Physical Interfaces) , line protocol is (connected) MTU bytes, duplex, Mbps, Display Format (IP Interfaces) NPU Configuration Auto-Negotiation Octets : Unicast Packets : Broadcast Packets : Multicast Packets : Discarded Packets : Error Packets : Unknown Packets : Octets : Unicast Packets :
Chapter 3 - Operation and Administration Using the CLI 3.3.3 NPU Configuration Managing the AU Maintenance VLAN ID The service interface of the AU is used for uploading maintenance reports to an external server. Most of the service interface parameters except the VLAN ID are configured separately for each AU (see Section 3.5.2.3). The AU maintenance VLAN ID is the VLAN ID used by all au service interfaces.
Chapter 3 - Operation and Administration Using the CLI 3.3.3.2 NPU Configuration Displaying the AU Maintenance VLAN ID To display the current value configured for the au maintenance VLAN ID, run the following command: npu# show aumaintenanceVlanId Command Syntax npu# show aumaintenanceVlanId Privilege Level 1 Display Format aumaintenanceVlanId Command Modes Global command mode 3.3.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Transparent mode: In this mode, the NPU transparently relays R6 and R8 reference-point traffic between AU/BSs (intra- or inter-shelf). This section describes the commands to be used for: “Configuring the Next Boot Mode” on page 132 “Displaying the Current and Next Boot Mode Information” on page 133 3.3.4.
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values {asngwStatic | Indicates the mode that is to be used for rebooting the NPU. Mandatory asngwSt atic asngwStatic: transparent} Indicates that the ASN-GW boot mode without HA support. That is, the system will not implement MIP services. This is the default mode of operation. transparent: Indicates transparent boot mode. Command Modes 3.3.
Chapter 3 - Operation and Administration Using the CLI Command Modes 3.3.5 NPU Configuration Global command mode Managing the 4Motion Configuration File 4Motion configuration parameters are stored in a default configuration file that resides in the NPU flash. When you start 4Motion for the first time after installation, the system boots up with the factory default configuration.
Chapter 3 - Operation and Administration Using the CLI 3.3.5.1 NPU Configuration Saving the Current Configuration When you reset the 4Motion system, it always boots up using the last saved configuration. If you are starting 4Motion for the first time after installation and commissioning, it boots up using the factory default configuration. Thereafter, any changes to configuration (made at runtime using the CLI) should be saved; all unsaved changes are lost after system reset.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration You can download a file from an external server, and use this file for booting up 4Motion. After downloading this file, reset the system. The system boots up with the downloaded configuration.
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description Command Modes 3.3.5.3 NPU Configuration 10 Parameter Description Presence Default Value Possible Values Indicates the IP address of the TFTP server. Mandatory N/A Valid IP address Indicates the name of the configuration file to be downloaded using the TFTP server. The file to be downloaded should be a compressed xml file in the format is .xml.gz.
Chapter 3 - Operation and Administration Using the CLI 3.3.5.4 NPU Configuration Making a Backup/Restoring the Configuration File You can make a backup of the current system configuration. You can either manually make a backup or configure the system to automatically make a daily backup of the current configuration. You can, at any time, restore configuration from the backup configuration file or revert to the factory default configuration.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration IMPORTANT To enable the system to automatically make a backup of the current configuration, everyday, refer to Section 3.3.5.4.3. Command Syntax npu# manual-backup Command Modes Global command mode 3.3.5.4.
Chapter 3 - Operation and Administration Using the CLI 3.3.5.4.3 NPU Configuration Making Automatic Backups of the Current Configuration You can enable the system to automatically make daily backups of the current configuration at a specific time. (You can also manually make a backup of the configuration. For details, refer to Section 3.3.5.4.1.) NOTE By default, the system makes a daily backup of the current configuration, at 00:00 hours.
Chapter 3 - Operation and Administration Using the CLI 3.3.5.4.4 NPU Configuration Displaying the Automatic Backup Time To display the current time configured for the automatic backup procedure, run the following command: npu# show auto-backup-time Command Syntax npu# show auto-backup-time Privilege Level 10 Display Format Automatic Backup time is Command Modes Global command mode 3.3.5.4.
Chapter 3 - Operation and Administration Using the CLI Syntax Description NPU Configuration Parameter Description Presence Default Value Possible Values Indicates the name of the backup configuration file to be used for restoring configuration. Mandatory N/A Valid file name The format of the backup configuration file name iz YYYYMMDDHHMM.xml.gz, where YYYYMMDDHHMM indicates the creation date and time of the zipped XML configuration file. Command Modes 3.3.5.4.
Chapter 3 - Operation and Administration Using the CLI 3.3.5.4.7 NPU Configuration Restoring the Factory Default Configuration With Connectivity You can, at any time, run the following command to restore factory default configuration without changing any of the parameters required for maintaining management connectivity to the unit: npu# restore-factory-default-with-connectivity IMPORTANT After executing this command, reset the system to apply the configuration change.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Applied Successfully with few exceptions” message. You can then view the failed CLIs using the following command: npu# show apply fail details According to the failures details you can perform the necessary corrective actions. The intent to have this feature is to address scenarios when migration tool can not determine consistency checks/rules between parameters/tables.
Chapter 3 - Operation and Administration Using the CLI Command Modes 3.3.6 NPU Configuration Global command mode Batch-processing of CLI Commands You can use the CLI to batch-process commands to be executed for configuring and monitoring 4Motion. IMPORTANT Before initiating batch-processing of commands, remember that: If an error occurs while executing any command, the batch-processing operation is aborted; all subsequent commands are not executed.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration config terminal nextbootmode asngwStatic limit cpu softlimit 80 hardlimit 85 bearerqos rule_1 0 3 5 data 1 config outer-dscp 3 vlan-priority 4 qos enable exit write reset Command Syntax npu# batch-run tftp:/// Privilege Level 10 Syntax Description Command Modes 3.3.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration protect the from hostile applications, the type and rate of traffic destined towards the NPU is limited by default. This section describes the commands to be executed for: “Configuring CPU and Memory Utilization Thresholds for the NPU” on page 147 “Rate Limiting for the NPU” on page 149 3.3.7.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Command Syntax npu(config)# limit {cpu | memory} ([softlimit ] [hardlimit ]) Privilege Level 10 Syntax Description Parameter Description Presence Default Value Possible Values {cpu | memory} Indicates whether the threshold is to be specified for CPU or memory utilization.
Chapter 3 - Operation and Administration Using the CLI Command Syntax npu# show resource limits Privilege Level 1 Display Format Resource Command Modes 3.3.7.2 softlimit NPU Configuration hardlimit CPU Memory Global configuration mode Rate Limiting for the NPU The rate limiting feature enables limiting the type and rate of traffic destined towards the NPU.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration NOTECAUTION When you disable rate limiting for the entire system, it is disabled for all applications, pre-defined, user-defined, and all others, and any application can use 100% of the NPU’s capacity, thereby making it vulnerable to attack from hostile applications.
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description NPU Configuration 1 Parameter Description Presence Default Value Possible Values {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | | all} Indicates the application for which rate limiting is to be displayed.
Chapter 3 - Operation and Administration Using the CLI Display Format NPU Configuration CPU Rate Limiting Status : Enabled PRE-DEFINED RATELIMIT CONFIGURATION: ----------------------------------Application DestPort Rate(Kbps) Status USER-DEFINED RATELIMIT CONFIGURATION: Application Srcport L2type Rate Dst
Chapter 3 - Operation and Administration Using the CLI NPU Configuration separate DSCP and/or VLAN priority bits for QoS handling of each flow. Extended ACL 199 is used for configuring QoS classification rules and associating each rule with a class-map. IMPORTANT By default, QoS marking rules are disabled. You are required to enable a QoS marking rule before it is applied on host originating traffic matching the QoS classification rules.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration You can, at any time, delete an existing class-map (refer to Section 3.3.8.1.5) or view the configuration information for an existing class-map (refer to Section 3.3.8.1.6). 3.3.8.1.1 Enabling the QoS Class-map Configuration Mode/ Creating a New Class Map To specify the 802.1p VLAN priority and/or DSCP values for a class-map, first enable the QoS class-map configuration mode.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration IMPORTANT An error may occur if: You specify a class-map number that is not within the range, 1- 65535. The class-map configuration mode for the class-map you have specified is already enabled. Command Syntax npu(config)# class-map Privilege Level 10 Syntax Description Command Modes 3.3.8.1.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration npu(config-cmap)# set {[cos ] [ip dscp ]} Command Syntax npu(config-cmap)# set {[cos ] [ip dscp ]} Privilege Level 10 Syntax Description Command Modes 3.3.8.1.3 Parameter Description Presence Default Value Possible Values [cos ] Indicates the 802.1p VLAN priority value to be applied for this class-map.
Chapter 3 - Operation and Administration Using the CLI Privilege Level Syntax Description Command Modes 3.3.8.1.4 NPU Configuration 10 Parameter Description Presence Default Value Possible Values [cos ] Indicates the 802.1p VLAN priority to be deleted for this class-map. Optional N/A 0-7 [ip dscp ] Indicates the DSCP to be deleted for this class-map.
Chapter 3 - Operation and Administration Using the CLI NPU Configuration Command Syntax npu(config)# no class-map Privilege Level 10 Syntax Description Command Modes 3.3.8.1.6 Parameter Description Presence Default Value Possible Values Indicates the identifier of the QoS class-map number to be deleted.
