LKT-MICRO-25Microbase station transceiver

4Motion ® System Manual Release Version: 3.0 June 2010 P/N 215697 Document History 4Motionii System Manual Document History TopicDescriptionDate Issued First Release for GAJuly 2008 Rate Limiting for the NPU Section 3.4.7.2 Rate limits are configurable only by the vendor. May 2009 Configuring ACLs Section 3.4.10 Updated default ACLs.May 2009 Configuring Performance Data Collection Section 3.4.14 Added support for new counters groups, updated names. May 2009 Configuring the Power Control Required C/N Level Parameters Section 3.9.4.2.2 Updated Defaults for cqi, cdma, qam64-1by2, qam64-2by3, qam64-3by4, qam64-5by6. May 2009 Managing the BS Keep-Alive Functionality Section 3.9.22 Updated commands’ syntax.May 2009 Managing the BS Idle Mode Parameters Section 3.9.23 New featureMay 2009 Managing BS ServicesAdded new parameters: paging-cycle, paging-offset, lm-traffic-idle-period, dl-def-rate. Updated range and default value for max-subburst. May 2009 Managing Ranging Parameters Section 3.9.19 The following tables were removed from operator CLI: Bandwidth Request, Handover Ranging, Initial Ranging, Periodic Ranging, Timing Correction. contbased-rsrvtimeout was removed from Ranging General table. May 2009 Airframe General Parameters Sections 3.9.12.2.1, 3.9.12.3.1, 3.9.12.5.1 Updated parameters: Removed: enable-ul-scrotation. Added: auto-diversity, auto-rx-enable. Corrected name: ul-duration. May 2009 Airframe Cyclic Delay Parameters Section 3.9.12.2.4 Updated descriptions.May 2009 Airframe Linear Delay Parameters Previously Section 4.8.16.2.5 Updated descriptions.May 2009 Document History 4Motioniii System Manual Airframe Mapping Parameters Previously Section 4.8.16.2.6 Updated descriptions.May 2009 Airframe Receive Parameters Previously Section 4.8.16.2.7 Updated descriptions.May 2009 Airframe Downlink Diversity Parameters Section 3.9.12.2.3 Changed value range and default for the MIMO parameter. May 2009 Airframe MIMO Parameters Sections 3.9.12.2.7, 3.9.12.3.4, 3.9.12.5.7 New Airframe parameters table.May 2009 Neighbor BS General Parameters Sections 3.9.9.2.1, 3.9.9.3.1, 3.9.9.7.1 Updated parameters: Removed: restartcount ucd-configchangecount and dcd-configchangecount must be set to 0. Added: paging-grp-id, nbr-strt-rng-codes. Updated range and description: preamble-idx May 2009 Service Mapping Rule R1 Profile Parameters Removed: sdu-length, sdu-size. All possible values of datadeliverytype are supported (including rTVR and nRTVR). Updated descriptions of cir, mir, latency. Updated range for cir, mir. May 2009 Service Mapping Rule R6 Profile Parameters, Updated range for cir, mir.May 2009 Feedback Allocation Parameters Section 3.9.5 Removed: pr-cdma, ert-poll-enable. Default value of ir-cdma changed from 20 to 2. Updated description of max-cqi. May 2009 Trigger Setup ParametersRemoved: hysteresismargin, timetotrigger Updated description of avgduration-rssi. May 2009 Neighbor BS Trigger Setup Parameters Removed: hysteresismargin, timetotriggerMay 2009 Rate Adaptation Parameters (was previously Section 4.8.20) All Rate Adaptation parameters were removed. May 2009 Scan Negotiation Parameters Section 3.9.8 Removed: all parameters except enable-modify. May 2009 TopicDescriptionDate Issued Document History 4Motioniv System Manual Handover Negotiation at SBS (was previously 4.8.12) All Handover Negotiation at SBS parameters were removed. May 2009 UCD Parameters (was previously 4.8.15) All UCD parameters were removed.May 2009 DCD Parameters (was previously 4.8.16) All DCD parameters were removed.May 2009 Authentication Relay Parameters Section 3.9.14 Removed: nonauth-macctrlratethrshld, nonauth-pduratethrshld Updated the default value of maxeaproundsthrshld to 100. Updated the default value of suspendedeapprocthrshld to 10000. Updated the description. Updated the default value of activemsthrshld to 1024. May 2009 Handover Control Parameters Section 3.9.19 All configurable (read-write) parameters were removed. A new read-only parameter added: CINRReuse. May 2009 BS Management Alarm Thresholds (was previously 4.8.26) All BS Management Alarm Thresholds parameters were removed. May 2009 BS Alarm Threshold Parameters Section 3.9.20 Removed: dl-droppedpackets, unalloc-slots, dl-retransmissions, ul-retransmissions, dl-subburstdrop, ul-subburstdrop. Updated description, range and default for ul-mednoise, ul-99prcntnoise. Added: Be-exc-dl-drop-thr, rt-exc-dl-drop-thr, nrt-exc-dl-drop-thr, ugs-exc-dl-drop-thr, ert-exc-dl-drop-thr. May 2009 Managing the Site General Information Section 3.4.16.7 Added section on displaying the site general information. Address parameter value was changed to up to 70 characters. Removed: AsnName, Region. May 2009 Managing the Unique Identifier Section 3.4.16.8 Added section on displaying the site ID.May 2009 Displaying the Vendor Identifier Section 3.4.16.9 New feature.May 2009 TopicDescriptionDate Issued Document History 4Motionv System Manual AU Connectivity Parameters Sections 3.6.2.3, 3.6.3.3, 3.6.6.3 Added new parameters: service-ip, service-mask, service-next-hop. Updated possible values of bearervlanid and the read-only InternalManagementVLANID parameters. May 2009 Configuring Physical and IP Interfaces Section 3.4.2 AU Fast Ethernet interfaces are not configurable. May 2009 AAA Client Configuration Section 3.4.12.9.1 Updated with new parameters/commands and additional changes related to support of multiple AAA clients and AAA Redundancy. 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. Updated default and presence requirement for rad-sharedsecret. Updated description, default, possible values and presence requirement for src-intf. Added comment: If the bearer interface IP address is being modified after aaa-client configuration, you must re-con…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration of the Macro BTSManaging Software Upgrade 4Motion101 System Manual 3.2.2.1.2Step 2: Triggering Software Download After the TFTP server is configured, run the following command to trigger the download of the shadow image to be used for software upgrade: npu(config)# load to shadow <shadow image name> After you execute this command, the shadow image is downloaded to the NPU flash, and the shadow image that is currently residing in the flash is overwritten. Command Modes Global configuration mode NOTE After you have configured the TFTP server, you can, at any time, view the TFTP server configuration information. For more details, refer to “Displaying the TFTP Configuration Information” on page 104 . IMPORTANT An error may occur if you execute this command when: „Another software download is already in progress. „The shadow image to be downloaded is already residing in the NPU flash as the shadow or operational image. „The TFTP server is not configured. For more information about configuring the TFTP server, refer to “Step 1: Configuring the TFTP Server” on page 100. „The name of the shadow image to be downloaded is incorrect or the format of the file name is incorrect. Because the file to be downloaded is a compressed file, always be suffix the file name with .tgz. „The NPU is running with the shadow image. „The system does not have enough memory available for software download. Command Syntax npu(config)# load to shadow <shadow image name> Chapter 3 - Operation and Administration of the Macro BTSManaging Software Upgrade 4Motion102 System Manual 3.2.2.1.3Step 3: Resetting and Booting the NPU Using the Shadow Image After the shadow image is downloaded to the NPU flash, run the following command to reboot the NPU with the downloaded shadow image: npu(config)# reboot from shadow [<shadow image name>] In the above command, you can specify the shadow image name that is to be used for NPU reboot. If you do not specify a value for the shadow image name parameter, the shadow image that was last downloaded is used for rebooting the NPU. Syntax Description ParameterDescriptionPresenceDefault Value Possible Values <shadow image name> Denotes the name of the shadow image that is to be downloaded to the NPU flash. The name of this file should always be suffixed with .tgz. MandatoryN/A<Valid shadow image name>.tgz Command Modes Global configuration mode NOTE After you have triggered the download procedure, you can at any time, obtain information about the download status. For more details, refer to “Displaying the Download Status Information” on page 105 . Command Syntax npu(config)# reboot from shadow [<shadow image name>] Syntax Description ParameterDescriptionPresenceDefault Value Possible Value <shadow image name> Denotes the name of the shadow image that is to be used for rebooting the NPU. If you do not specify a value for this parameter, the last downloaded shadow image is used for rebooting the NPU. OptionalN/AValid shadow image name Chapter 3 - Operation and Administration of the Macro BTSManaging Software Upgrade 4Motion103 System Manual 3.2.2.1.4Step 4: Making the Shadow Version Operational After you reset the NPU with the shadow image, and ensure that the NPU is functioning correctly with the shadow image, you can make the shadow version as the operational version. The next time you reset the system, the shadow image that you make operational is used for rebooting the NPU. To make the shadow version as the operational version, run the following command. npu(config)# switchover npu After you run this command, the operational image is swapped with the shadow image. The next time you reset the NPU, the system boots up with the swapped image. 3.2.2.2Displaying the Operational, Shadow, and Running Versions You can, at any time (during or after the software download procedure), run the following command to view the operational, shadow, and running versions of the NPU software: npu# show software version npu Command Modes Global configuration mode IMPORTANT If you reset the NPU before running this command, the NPU boots up with the image that is currently the operational image. IMPORTANT An error may occur if you run this command when the NPU is not running with the shadow image. Command Syntax npu(config)# switchover npu Command Modes Global configuration mode Chapter 3 - Operation and Administration of the Macro BTSManaging Software Upgrade 4Motion104 System Manual 3.2.2.3Displaying the TFTP Configuration Information You can, at any time (during or after the download procedure), run the following command to view the configuration information about the TFTP server that is used for the NPU software upgrade: npu# show software version server NOTE The operational version is the default software version that is used for rebooting the NPU after system reset. The shadow version is the downloaded software version that you can use to boot up the NPU. However, it is the operational software version that is used to boot up the NPU after the next system reset. The running version is the software version (can be either the operational or shadow version) that is currently running on the system. Command Syntax npu# show software version npu Display Format Mananged Object : NPU Operational Version : <Operational Version> Shadow Version : <Shadow Version> Running Version : <Running Version> Command Modes Global command mode IMPORTANT An error may occur if configuration information is requested for a TFTP server that is not configured. For more information about configuring the TFTP server to be used for software download, refer to “Step 1: Configuring the TFTP Server” on page 100. Command Syntax npu# show software version server Display Format Software version server <Server IP Address> Chapter 3 - Operation and Administration of the Macro BTSManaging Software Upgrade 4Motion105 System Manual 3.2.2.4Displaying the Download Status Information After initiating software downl…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion250 System Manual 3.4.12.7.3Restoring the Default Configuration Parameters for the Bearer Plane QoS Output Marking Rules Run the following command to restore the default configuration for this bearer plane QoS marking rule: npu(config-bqos)# no {outer-dscp | vlan-priority | qos enable} When you execute this command, it automatically disables this QoS marking rule. [vlan-priority <integer(0-7>] Denotes the VLAN priority to be assigned to the packets if the packet meets the requirements of the marking rules specified in Section 3.4.12.7.1. Optional00-7, where 7 is the highest [qos enable]Indicates whether this QoS marking rule should be enabled. The absence of this flag indicates that this QoS flag is disabled. By default, a bearer plane QoS marking rule is disabled. If you enable this QoS marking rule, packets on bearer plane that were created using the parameters in Section 3.4.12.7.1, the Outer DSCP and VLAN Priority fields in the IP header and Ethernet header, respectively are populated with the values you specify for the outer-dscp and vlan-priority parameters. OptionalBy default, the QoS marking rule is disabled. The presence/abse nce of this flag indicates that this QoS flag is enabled/disabl ed. Command Modes Bearer plane QoS marking rules configuration mode NOTE Refer to Section 3.4.12.7.2 for a description and default values of these parameters. Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion251 System Manual 3.4.12.7.4Terminating the QoS Marking Rules Configuration Mode Run the following command to terminate the marking rules configuration mode: npu(config-bqos)# exit 3.4.12.7.5Deleting Bearer Plane QoS Marking Rules Run the following command to delete the a QoS marking rule: npu(config)# no bearerqos [<qos-alias>] Command Syntax npu(config-bqos)# no {outer-dscp | vlan-priority | qos enable} Privilege Level 10 Command Modes Bearer plane QoS marking rules configuration mode Command Syntax npu(config-bqos)# exit Privilege Level 10 Command Modes Bearer plane QoS marking rules configuration mode CAUTION Specify the QoS alias if you want to delete a specific bearer plane qoS marking rule. Otherwise all the configured bearer plane QoS marking rules are deleted except "int_default" and "ext_default" which cannot be deleted. Command Syntax npu(config)# no bearerqos [<qos-alias>] Privilege Level 10 Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion252 System Manual 3.4.12.7.6Displaying Configuration Information for the Bearer Plane QoS Marking Rules To display configuration information for specific or all bearer plane QoS marking rules, run the following command: npu# show bearerqos [<qos-alias>] Specify the QoS alias if you want to display configuration information for a particular bearer plane QoS marking rule. Do not specify a value for this parameter if you want to view configuration information for all bearer plane QoS marking rules. Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [<qos-alias>]Denotes the QoS alias of the bearer QoS marking rule that you want to delete. Specify a value for this parameter if you want to delete a specific bearer QoS marking rule. Do not specify a value for this parameter if you want to delete all bearer QoS marking rules except "int_default" and "ext_default". OptionalN/AString Command Modes Global configuration mode Command Syntax npu# show bearerqos [<qos-alias>] Privilege Level 1 Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion253 System Manual 3.4.12.8Managing Service Interfaces A Service Interface defines the parameters of the interface used by the ASN-GW on the network side for services specified in the applicable Service Group. The following types of Service Interface are available: „IP-IP: The Service Interface defines the parameters on the ASN-GW side of a point-to-point tunnel to be used for the applicable traffic. „VLAN: The Service Interface defines the VLAN ID to be added/removed by the ASN-GW to/from the applicable traffic. „QinQ: Applicable only for special applications requiring local support of unauthenticated mode. The QinQ Service Interface is applicable only for supporting VLAN CS Service Flows associated with a QinQ Service Group. Up to 10 Service Interfaces may be defined. Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [<qos-alias>]Denotes the QoS alias of the bearer QoS marking rule that you want to display. Specify a value for this parameter if you want to display a specific bearer QoS marking rule. Do not specify a value for this parameter if you want to display all bearer QoS marking rules. OptionalN/AString Display Format Bearer QoS Configuration : qos-alias intf-type srvc-type trfc-priority media-type inner-dscp outer-dscp vlan-priority status voip <value> <value> <value> <value> <value> <value> enabled Command Modes Global command mode Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion254 System Manual 1Enable the Service Interface configuration mode for the selected Service Interface (refer to Section 3.4.12.8.1) 2You can now execute any of the following tasks: »Configure one or more of the parameters of the Service Interface (refer to Section 3.4.12.8.2) »Restore the default values of the Service Interface parameters (refer to Section 3.4.12.8.3) » Terminate the Service Interface configuration mode (refer to Section 3.4.12.8.4) In addition, you can, at any time, display configuration information for one or all existing Service Interfaces (refer to Section 3.4.12.8.6) or delete an existing Service Interface (refer to Section 3.4.12.8.5). 3.4.12.8.1Enabling the Service Interface Configuration Mode\Creating a Service Interface To configure the parameters of a Service Interface, first enable the Service Interface configuration mode for the specific Service…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion399 System Manual Specify the module name if you want to configure the severity level separately for this module. If you do not specify the name of the module, the severity level that you configure in this command is applied to all modules. For example, run the following command if you want logs to be created for WiMAX signaling protocols when the severity level is Error or higher: npu(config)# log level SIGASN ERROR Or run the following command to set the severity level to Error for all modules: npu(config)# log level ERROR FaultMgrFault management procedures ShelfMgrShelf management procedures SIGASNWiMAX signaling protocols UserIFUser-initiated procedures AUMgrInternal processes used for managing AU PerfMgrPerformance management procedures NOTE You can display the currently configured severity levels for each module. For details, refer Section 3.4.13.2.2. Command Syntax npu(config)# log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}] {ALERT|ERROR|INFO} Privilege Level 10 Table 3-24: Modules for which Logging can be Enabled Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion400 System Manual 3.4.13.2.2Displaying Configuration Information for Module-level Logging To display the log level configured for one or all modules, run the following command. npu(config)# show log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AU Mgr}] Specify the module for which you want to view the configured severity level. If you do not specify the name of the module, the log level configured for all modules is displayed. Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [{StartupMgr |S WDownload |Faul tMgr|PerfMgr| ShelfMgr|SIGAS N |UserIF|AUMg r}] Indicates the name of the module for which the severity level is to be specified. If you do not specify any value for this parameter, the severity level that you specify is applied for all modules. For more information about these parameters, refer Table 3-24. OptionalN/A „StartupMgr „SWDownloa d „FaultMgr „PerfMgr „ShelfMgr „SIGASN „UserIF „AUMgr {ALERT |ERROR| INFO} Indicates the severity level to be applied to a particular or all modules. MandatoryError „ALERT „ERROR „INFO Command Modes Global configuration mode Command Syntax npu(config)# show log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}] Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion401 System Manual 3.4.13.2.3Disabling Module-level Logging To disable logging for one or all system modules, run the following command: npu(config)# no log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AU Mgr}] Specify the name of the module if you want to disable logging for a specific module. If you do not specify the module name, logging is disabled for all modules. Privilege Level 1 Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [{StartupMgr |S WDownload|Faul tMgr |PerfMgr| ShelfMgr|SIGAS N|UserIF|AUMg r}] Indicates the name of the module for which you want to view the configured severity level. For more information about these parameters, refer Table 3-24. If you do not specify any value for this parameter, the severity level is displayed for all modules. OptionalN/A „StartupMgr „SWDownloa d „FaultMgr „PerfMgr „ShelfMgr „SIGASN „UserIF „AUMgr Display Format Module Name : Log level <Module Name> : <Log Level> Command Modes Global configuration mode Command Syntax npu(config)# no log level [{StartupMgr |SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}] Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion402 System Manual 3.4.14 Configuring Performance Data Collection You can configure 4Motion to periodically collect and store performance counters.For details on the counters groups and the performance data counters collected for each group refer to the relevant 4Motion Performance Management document. You can specify the group for which performance data is to be stored and collected. The data is stored in an XML file called, prf_<SiteID>_yyyymmddhhmm.xml.gz in the path,/tftpboot/management/performance. The system maintains this data for a maximum of 24 hours after which it is deleted. It is recommended that you periodically make a backup of these files on an external server. You can enable/disable collection of performance data for each group separately. This section describes: „“Enabling Collection and Storage of Historical Performance Data” on page 403 Privilege Level 10 Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [{StartupMgr |S WDownload|Faul tMgr |PerfMgr| ShelfMgr|SIGAS N|UserIF|AUMg r}] Indicates the name of the module for which logging is to be disabled. If you do not specify any value for this parameter, logging is disabled for all parameters. For more information about these modules, refer Table 3-24. OptionalN/A „StartupMgr „SWDownloa d „FaultMgr „PerfMgr „ShelfMgr „SIGASN „UserIF „AUMgr Command Modes Global configuration mode Chapter 3 - Operation and Administration of the Macro BTSNPU Configuration 4Motion403 System Manual „“Disabling Collection and Storage of Performance Data” on page 404 „“Displaying the Status of Performance Data Collection” on page 405 3.4.14.1Enabling Collection and Storage of Historical Performance Data 4Motion collects and stores performance data for the a number of system groups (refer to Section 3.4.14). To enable collection and storage of performance data for a group, run the following command: To enable collection and storage of performance data for an NPU counters group: npu(config)# pm-group enable npu {BckhlPort | CascPort | IntMgmtIf | ExtMgmtIf | BearerIf | R6InterfaceTotal | R6InterfaceBs | ProvisionedQOS | R3Interface | LoadBalancing | InitialNe} To enable collection and storage of performance data…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration of the Macro BTSManaging BSs 4Motion548 System Manual 3.9.9.7.2Displaying Configuration Information for Neighbor BS Required C/N Level Parameters To display configuration for the Neighbor BS Required C/N Level parameters, run the following command: npu# show nbr-requiredcnr bs [<(1 to 16777215 StepSize 1)> bs-id-lsb <(1 to 16777215 StepSize 1)>] Specify the BS ID and the Neighbor BS ID (bs-id-lsb) if you want to display configuration for a particular Neighbor BS in a particular BS. For example, to display the Required C/N Level parameters of Neighbor BS 68000 in BS 66503, run the following command: npu# show nbr-requiredcnr bs 66053 bs-id-lsb 68000 Do not specify these parameters if you want to view configuration information for all existing Neighbor BSs in all existing BSs. To display information for all Neighbor BSs in all BSs, run the following command: Display Format (for each existing Neighbor BS in each of the existing BSs if requested for all) BSIDLSB :<value> NeighborBSIDLSB :<value> SynchronizationIndicator :<value> EIRP :<value> Bandwidth(MHz) :<value> UplinkFeedbackZonePermutationBase :<value> PreambleIndex :<value> UCDConfigurationChangeCount :<value> DCDConfigurationChangeCount :<value> IsotropicrecpwrforInitrang :<value> CenterFrequency(MHz) :<value> PagingGroupId :<value> neighborStartRangeCodes :<value> NeighborBsDlDataMIMOMode :<value> Command Modes Global command mode Chapter 3 - Operation and Administration of the Macro BTSManaging BSs 4Motion549 System Manual npu# show nbr-requiredcnr bs Command Syntax npu# show nbr-requiredcnr bs [<(1 to 16777215 StepSize 1)> bs-id-lsb <(1 to 16777215 StepSize 1)> ] Privilege Level 1 Syntax Description ParameterDescriptionPresenceDefault Value Possible Values <(1 to 16777215 StepSize 1)> The BS ID Specify a value for this parameter if you want to display the Required C/N Level parameters of a specific Neighbor BS in a specific BS. Do not specify a value for this parameter if you want to display the Required C/N Level parameters of all Neighbor BSs in all BSs. OptionalN/A1-16777215 bs-id-lsb <(1 to 16777215 StepSize 1)> The Neighbor BS ID. Specify a value for this parameter if you want to display the Required C/N Level parameters of a specific Neighbor BS in a specific BS. Do not specify a value for this parameter if you want to display the Required C/N Level parameters of all Neighbor BSs in all BSs. OptionalN/A1-16777215 Chapter 3 - Operation and Administration of the Macro BTSManaging BSs 4Motion550 System Manual 3.9.9.7.3Displaying Configuration Information for Neighbor BS Triggers Parameters To display configuration information for Neighbor BS Triggers parameters, run the following command: npu# show nbr-triggers bs [<(1 to 16777215 StepSize 1)> bs-id-lsb <(1 to 16777215 StepSize 1)> TrigName {scnReqCinrMin | scnReqRssiMin | scnReqRtdMax | scnRepCinrMaxNbs | scnRepRssiMaxNbs | scnRepCinrMargin | scnRepRssiMargin | scnRepRtdMax | scnRepCinrMinSbs | scnRepRssiMinSbs | hoReqCinrMaxNbs | hoReqRssiMaxNbs | hoReqCinrMargin | hoReqRssiMargin | hoReqRtdMax | hoReqCinrMinSbs | hoReqRssiMinSbs}] Specify the BS ID, Neighbor BS ID (bs-id-lsb) and Trigger name if you want to display configuration for a particular Trigger. For example, to display the scnReqCinrMin parameters of BS Neighbor 68000 in BS 66053, run the following command: npu# show nbr-triggers bs 66053 bs-id-lsb 68000 TrigName scnReqCinrMin Display Format (for each existing Neighbor BS in each of the existing BSs if requested for all) BSIDLSB :<value> NeighborBSIDLSB :<value> RequiredCNRforACK :<value> RequiredCNRforCQI :<value> RequiredCNRforCDMA :<value> RequiredCNRforQPSK1/2 :<value> RequiredCNRforQPSK3/4 :<value> RequiredCNRfor16QAM1/2 :<value> RequiredCNRfor16QAM3/4 :<value> RequiredCNRfor64QAM1/2 :<value> RequiredCNRfor64QAM2/3 :<value> RequiredCNRfor64QAM3/4 :<value> RequiredCNRfor64QAM5/6 :<value> Command Modes Global command mode Chapter 3 - Operation and Administration of the Macro BTSManaging BSs 4Motion551 System Manual Do not specify these parameters if you want to view configuration information for all existing Neighbor BSs in all BSs. To display information for all Neighbor BSs in all BSs, run the following command: npu# show nbr-triggers bs Command Syntax npu# show nbr-triggers bs [<(1 to 16777215 StepSize 1)> bs-id-lsb <(1 to 16777215 StepSize 1)> TrigName {scnReqCinrMin | scnReqRssiMin | scnReqRtdMax | hoReqCinrMaxNbs | hoReqRssiMaxNbs | hoReqCinrMargin | hoReqRssiMargin | hoReqRtdMax | hoReqCinrMinSbs | hoReqRssiMinSbs} ] Privilege Level 1 Syntax Description ParameterDescriptionPresenceDefault Value Possible Values <(1 to 16777215 StepSize 1)> The BS ID Specify a value for this parameter if you want to display a specific Trigger in a specific Neighbor BS of a specific BS. Do not specify a value for this parameter if you want to display the Triggers of all Neighbor BSs in all BSs. OptionalN/A1-16777215 bs-id-lsb <(1 to 16777215 StepSize 1)> The Neighbor BS ID. Specify a value for this parameter if you want to display a specific Trigger in a specific Neighbor BS of a specific BS. Do not specify a value for this parameter if you want to display the Triggers of all Neighbor BSs in all BSs. OptionalN/A1-16777215 Chapter 3 - Operation and Administration of the Macro BTSManaging BSs 4Motion552 System Manual 3.9.9.7.4Displaying Configuration Information for Neighbor BS Specific BS Triggers Parameters To display configuration information for Neighbor BS Specific BS Triggers parameters, run the following command: npu# show nbr-specific bs [<(1 to 16777215 StepSize 1)> bs-id-lsb <(1 to 16777215 StepSize 1)> TrigName {hoReqCinrMaxNbs | hoReqRssiMaxNbs | hoReqCinrMargin | hoReqRssiMargin} ] Specify the BS ID, Neighbor BS ID (bs-id-lsb) and Specific BS Trigger name if you want to display configuration for a particular Trigger. For example, to display the hoReqRssiMaxNbs parameters of BS Neighbor 68000 in BS 66053, run the following co…

Text truncated - open the document above for the full version.