Alvarion Technologies BMAX-OR-25 BreezeMax 4Motion Broadband Wireless System User Manual 4Motion System Manual
Alvarion Technologies Ltd. BreezeMax 4Motion Broadband Wireless System 4Motion System Manual
Contents
- 1. Manual 1
- 2. Manual 2
- 3. Manual 3
- 4. Manual 4
- 5. Manual
Manual 2
![3ChapterCommissioning](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-1.png)
![Chapter 3 - Commissioning4Motion 98 System ManualIn This Chapter:“Initial NPU Configuration” on page 99“Completing the Site Configuration Using AlvariSTAR” on page 103](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-2.png)
![Chapter 3 - Commissioning Initial NPU Configuration4Motion 99 System Manual3.1 Initial NPU Configuration3.1.1 IntroductionAfter 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 4Motion System Management” on page 114 for information on how to access the CLI either via the MON port or via Telnet and how to use it.The following sections describe the minimum mandatory configuration actions required to allow remote configuration of the site and to enable discovery by the EMS system:1”NPU Local Connectivity”2”Site Connectivity”3”ACL Definition”4”Static Route Definition”5”SNMP Manager Definition”6”Site ID Definition”For a configuration example, refer to Appendix C.3.1.2 NPU Local ConnectivityRefer to “Accessing the CLI from a Local Terminal” on page 115 for details on connecting locally to the NPU. Clear existing site configuration (must be executed for "used” NPUs). Restore to factory default and reboot using the following command: npu# restore-factory-defaultThe system will reset automatically.3.1.3 Site Connectivity3.1.3.1 Connectivity ModeThe connectivity mode determines how traffic is to be routed between the NPU and the BSs, AAA server and external Management System servers.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-3.png)
![Chapter 3 - Commissioning Initial NPU Configuration4Motion 100 System ManualThe 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 modeTo 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 138).3.1.3.2 VLANs Translation (Outband Connectivity Mode)When using In-Band connectivity via the Data port, the default VLAN ID for management packets is 12. The default VLAN ID for data packets is 11. If different VLAN IDs are used in the backbone, the VLANs should be translated accordingly. To enable VLAN translation and configure the required VLANs translation, run the following commands (the examples are for backhaul Data VLAN ID 30 and Management VLAN ID 31):1Enable the Data port configuration mode (for details refer to “Enabling the Interface configuration mode” on page 142):npu(config)# interface gigabitethernet 0/102Enable VLAN translation (for details refer to “Enabling/Disabling VLAN Translation” on page 150): npu(config-if)# vlan mapping enable3Translate data VLAN 11 to the backhaul data VLAN 30 (for details refer to “Creating a VLAN Translation Entry” on page 150): npu(config-if)# vlan mapping 11 304Translate management VLAN 12 to the backhaul management VLAN 31: npu(config-if)# vlan mapping 12 315Exit the interface configuration mode: npu(config-if)# exit6To view the VLAN mapping parameters, run the command:npu# show interface gigabitethernet 0/10 vlan mapping3.1.3.3 External Management InterfaceTo configure the necessary parameters of the External Management interface used for connectivity with the EMS system, run the following commands:1Enable the External Management interface configuration mode (for details refer to “Enabling the Interface configuration mode” on page 142): npu(config)# interface external-mgmt](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-4.png)
![Chapter 3 - Commissioning Initial NPU Configuration4Motion 101 System Manual2Disable the interface to allow configuring its parameters: npu(config-if)# shutdown3Configure 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 161:npu(config-if)# ip address x.x.x.x y.y.y.y4Configure the MTU of the interface to 1500 bytes: npu(config-if)# mtu 15005Enable the interface: npu(config-if)# no shutdown6Exit the interface configuration mode: npu(config-if)# exit7Exit the configuration mode: npu(config)# exit3.1.3.4 Save and Apply Changes in Site Connectivity Configuration1Save the configuration: npu# write (otherwise, after the next time reset you will lose the configuration changes).2Reset the system to apply the changes: npu# reset3.1.4 ACL DefinitionFor details on ACLs refer to “Configuring ACLs” on page 215.1Create a standard ACL (number 1) and enable the ACL configuration mode: npu(config)# "ip access-list standard 12For initial configuration, permit traffic from any source address to any destination address: npu(config-std-nacl)# "permit any any.3Terminate the ACL configuration mode: npu(config-std-nacl)# exit4Enable the AUs virtual interface configuration mode:npu(config)# "interface all-au5Attach the ACL to the AUs virtual interface: npu(config-acl)# "ip access-group 16Terminate the AUs virtual interface configuration mode: npu(config-acl)# exit3.1.5 Static Route DefinitionStatic Route must be configured whenever the EMS server and the NPU are on different subnets. For more details refer to “Adding a Static Route” on page 212.Run the following command: npu(config)# "ip route 0.0.0.0 0.0.0.0 x.x.x.x" (x.x.x.x is the next hop IP address, 0.0.0.0 0.0.0.0 define the IP address and mask](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-5.png)
![Chapter 3 - Commissioning Initial NPU Configuration4Motion 102 System Manualas “any destination”. Depending on your backhaul network, you may define different IP address and mask to allow only specific destinations).3.1.6 SNMP Manager DefinitionTo define the communities to be used by the SNMP manager, run the command: npu(config)# snmp-mgr ReadCommunity public ReadWriteCommunity private.For more details refer to “Adding an SNMP Manager” on page 422.For proper operation of the manager you should configure also the Trap Manager parameters and enable sending traps to the defined Trap Manager (this can also be done later via the management system):1npu(config)# trap-mgr ip-source x.x.x.x port 162 TrapCommunity public( x.x.x.x is the IP address of the EMS server). For more details refer to “Adding/Modifying a Trap Manager entry” on page 4252npu(config)# trap-mgr enable ip-source x.x.x.xNote that if the management system is behind a NAT router, the NAT Outside IP address (the IP of the router’s interface connected to the managed device LAN) must also be defined in the device as a Trap Manager, with traps sending enabled. In the NAT router, Port Forwarding (NAT Traversal) must be configured 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).3.1.7 Mapping the AU Software VersionTo define the software version to be used by all AUs run the command:npu(config)# map au default <image name>, 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).3.1.8 Site ID DefinitionTo define the site ID (Site Number): npu(config)# site identifier x (x is the unique site identifier, a number in the range from 1 to 999999)For more details refer to “Configuring the Unique Identifier for the 4Motion Shelf” on page 462.3.1.9 Saving the ConfigurationTo save the configuration run the command: npu# write (otherwise, after the next time reset you will lose the configuration changes).](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-6.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 103 System Manual3.2 Completing the Site Configuration Using AlvariSTAR3.2.1 IntroductionAfter 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.Verify that the Site is included in the list of devices that can be managed by AlvariSTAR. It can be added to the list of managed devices either through the Equipment Manager (by creating a New managed device) or through the Managed Network window (by inclusion in a range to be discovered and activation of the Network Scan Task from the Task Manager).To complete the minimal configuration, open the Site’s Device Manager from the Equipment Manager and perform the following configuration steps:1“Site Configuration” on page 1042“Connectivity Configuration (optional)” on page 1043“Equipment Configuration” on page 1044“ASNGW Configuration” on page 106 (only for Distributed ASNGW topology)5“BS Configuration” on page 1086“Site Sector Configuration” on page 1107“Apply All Changes” on page 111NOTEThe following sections list the minimum actions that must be performed for completing basic configuration of the Site. Additional parameters may also be configured in order to complete the entire configuration of the Site.After configuring the mandatory parameters in each screen, click on the Apply button. Click Apply even if you did not change any of the screen’s default parameters.In some of the screens in the following sections there are no mandatory parameters but still you must click on the Apply button to activate the default values.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-7.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 104 System Manual3.2.2 Site Configuration3.2.2.1 General TabASN Topology - the default is Distributed ASNGW. If you change it to Centralized ASNGW click Apply for the device to accept the change.3.2.3 Connectivity Configuration (optional)3.2.3.1 IP Interface ScreenConfigure the IP address of the Bearer interface:1Change the Administrative State to Down.2Click Apply.3Change the IP and/or any other parameter value, except VLAN ID.4Click Apply.5Change the Administrative State to Up.6Click on Apply to accept the changes.3.2.3.2 IP Routing ScreenThe IP Routing screen is used to define the static routes for traffic originating from the NPU.The static route for management traffic was already configured (see “Static Route Definition” on page 101). If necessary (depending on your specific backhaul network) you may configure additional static route(s) for Bearer Traffic and/or Control Traffic. If additional static routes were defined (or if you made any changes in the already configured static route), click on the Apply button.3.2.4 Equipment Configuration3.2.4.1 AUAU entities must be created for all installed AUs (you may create an AU entity also for AUs that are not installed yet).To create a new AU entity:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-8.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 105 System Manual1Right click on the AU lnode in the Navigation Pane and select Create. The New AU definition window will open. You can also double-click on an empty slot in the Site Equipment View Page to open the New AU window for the selected slot.2In the New AU definition window, define the following:»AU number (AU Slot)»Type»Ports (in current release only 4 Ports AUs are applicable)»Bandwidth3Click Apply.4Repeat the process for all required AU entities.3.2.4.2 ODUODU entities must be created for all installed ODUs (you may create an ODU entity also for ODUs that are not installed yet).1Right click on the ODU node in the Navigation Pane and select Create. The New ODU definition window will open.2In the New ODU definition window, define the following:»ODU number »ODU Type3Click Apply.4In the ODU General screen of the applicable ODU, in the Ports Configuration section, configure the Tx Power for the relevant Tx/Rx port(s) . Click on the Apply button for the device the accept the configuration. 5Repeat the process for all required ODU entities.To create a new ODU entity:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-9.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 106 System Manual3.2.4.3 AntennaAntenna entities must be created for all installed and connected antennas (you may create an Antenna entity also for antennas that are not installed/connected yet).1In the Anteena screen, click on the Add New Antenna button.2In the Antenna Parameters section, define the following:»Number of Ports»Heading3Click Apply.4Repeat the process for all required Antenna entities.3.2.4.4 GPSThe 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.3.2.5 ASNGW Configuration3.2.5.1 AAA Screen1Configure the following mandatory parameters:»Primary AAA Server (IP address)»RADIUS Shared Secret»ASNGW NAS ID2Click Apply for the device to accept the configuration.To create a new Antenna entity:NOTEASNGW screens are available only for Distributed ASNGW topology (see also “Site Configuration” on page 104.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-10.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 107 System Manual3.2.5.2 Service Screen3.2.5.2.1 Service Interface TabAt least one Service Interface for data must be defined. If a dedicated management station for CPEs is being used, a suitable Service Interface for management must also be defined.1Click on the Add Service Interface button and configure the following mandatory parameters:»Service Interface Name»Type»Tunnel Destination IP (IP-in-IP Service Interface)»Service VLAN ID (VLAN and QinQ Service Interface)»Default Gateway IP Address (VLAN Service Interface)2Click Apply for the device to accept the configuration.3.2.5.2.2 Service Groups TabAt 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.1Click on the Add Service Group button and configure at least the following mandatory parameters:»Name»Type»Service Interface Name»DHCP Function Mode»DHCP Own IP Address»External DHCP Server IP Address (Relay mode)»IP Address Pool From (Server mode)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-11.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 108 System Manual»IP Address Pool To (Server mode)»Subnet Mask (Server mode)»DNS Server IP Address (Proxy mode)2Click Apply for the device to accept the configuration.3.2.5.3 SFA Screen -Classification Rules TabCreate the necessary Classification Rule(s) according to the relevant type of traffic, and click Apply.3.2.5.4 Service Profiles At least one Service Profile must be defined and associated with an already defined Service Group.1Right-click on the Service Profile node and select Create. The New Service Profile window is displayed.2Define the Name of the New Service Profile and click Apply.3The new Service Profile added to the list of available Service Profiles in the navigation tree. Select it to continue the configuration process.4Click Add in the Service Flow area.5Configure the applicable general parameters of the Service Flow.6Configure the applicable QoS parameters of Service Flow for UL and DL (for Data deleivery type=BE it will be Maximum Sustained Traffic Rate and Traffic Priority)7Associate this Service Flow with previously created Classification Rule(s).8Change the Profile Status to Enable9Click Apply for the device to accept the configuration.3.2.6 BS Configuration3.2.6.1 Creating a New BS Entity1Right click on the BS level entry in the Navigation Pane. The New BS definition window will open.To create a new BS entity:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-12.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 109 System Manual2In the New BS definition window, define the following:»BS ID LSB»Operator ID3Click Apply.4Complete the BS configuration as described in the following sections.3.2.6.2 Radio3.2.6.2.1 Basic Screen3.2.6.2.1.1 General Tab1Configure the following mandatory parameters:»Name»Bandwidth»Center Frequency2Click Apply for the device to accept the configuration.3You will be prompted to properly configure some or all of the following parameters:aTotal Uplink Duration (Air Frame Structure General Tab)bMajor Map Groups (Air Frame Structure Zones Tab)cDownlink Data Zone Number of Sub-Channels (Air Frame Structure Zones Tab)dUplink Feedback Zone Number of Sub-Channels (Air Frame Structure Zones Tab): ◊For a Bandwidth of 7 or 10 MHz, configure this parameter to the default value of 35.◊For a Bandwidth of 5 MHz, configure this parameter to the default value of 17.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-13.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 110 System ManualeUplink Data Zone Number of Sub-Channels (Air Frame Structure Zones Tab):◊For a Bandwidth of 7 or 10 MHz, configure this parameter to the default value of 35.◊For a Bandwidth of 5 MHz, configure this parameter to the default value of 17.4Click Apply for the device to accept the configuration.3.2.6.2.2 Advanced ScreenAll the parameters in the Advanced screen should be left with their default values. However, the Apply button must be clicked once (in any tab) for the device to accept the default configuration.3.2.6.3 Connectivity3.2.6.3.1 Basic Screen - Bearer Tab1Configure the following mandatory parameters:»IP Address»IP Subnet Musk»Default Gateway2Click Apply for the device to accept the configuration.3.2.6.3.2 Basic Screen - Authentication Tab1Configure the mandatory Default Authenticator IP Address parameter.2Click Apply for the device to accept the configuration.3.2.6.3.3 Advanced ScreenAll the parameters in the Advanced page should be left with their default values. However, the Apply button must be clicked for the device to accept the default configuration.3.2.7 Site Sector Configuration1Right click on the Site Sector level entry in the Navigation Pane. The New Site Sector definition window will open.To create a new Site Sector entity:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-14.png)
![Chapter 3 - Commissioning Completing the Site Configuration Using AlvariSTAR4Motion 111 System Manual2In the New Site Sector definition window, define the Site Sector Number3Click Apply.4At 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:»BS ID LSB»AU Slot Number»AU Port Number»ODU Number»ODU Port Number»Antenna Number»Antenna Port Number5Click Apply for the device to accept the configuration.3.2.8 Apply All ChangesIf you changed any of the parameters that are applied only after reset of the NPU such as ASN Topology or Configured GPS Type (indicated by a pop-up message after applying the change), you must reset the NPU (in the NPU screen select the Reset option in the Shutdown Operation parameter). This will cause also automatic reset of all AUsTo fully apply all the Site Sector configuration changes, reset all the relevant AUs (in the Control tab of each applicable AU screen select the Reset option in the Shutdown Operation parameter). It is not necessary to reset each of the AUs if you reset the NPU.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-15.png)
![4ChapterOperation and Administration Usingthe CLI](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-16.png)
![Chapter 4 - Operation and Administration Using the CLI4Motion 113 System ManualIn This Chapter:“Using the Command Line Interface for 4Motion System Management” on page 114“Shutting Down/Resetting the System” on page 132“NPU Configuration” on page 135“Managing MS in ASN-GW” on page 463“Managing AUs” on page 465“Managing ODUs” on page 483“Managing Antennas” on page 505“Managing BSs” on page 514“Managing Sectors” on page 764“Monitoring Performance of Hardware and Software Components” on page 778“Troubleshooting” on page 821](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-17.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 114 System Manual4.1 Using the Command Line Interface for 4Motion System ManagementAll 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.The following system management options are available:Accessing the Command Line Interface (CLI) locally via the MON portUsing Telnet/Secure Shell (SSH) to access the CLIThe CLI is a configuration and management tool that you can use to configure and operate the 4Motion system, either locally or remotely, via Telnet/SSH. The following are some administrative procedures to be executed using the CLI:Specifying the boot mode to be used at the next system resetSelecting the connectivity modeShutting down/resetting 4MotionConfiguring and operating 4MotionMonitoring hardware and software componentsExecuting debug proceduresExecuting software upgrade proceduresThis section provides information about:“Accessing the CLI” on page 115“Command Modes” on page 117“Interpreting the Command Syntax” on page 118“Using the CLI” on page 120](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-18.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 115 System Manual“Managing Users and Privileges” on page 1224.1.1 Accessing the CLIYou can access the CLI, locally, via an ANSI ASCII terminal or PC that is connected via the DATA port of the NPU. You can also use Telnet/SSH to remotely access the CLI.This section describes the procedures for:“Accessing the CLI from a Local Terminal” on page 115“Accessing the CLI From a Remote Terminal” on page 1164.1.1.1 Accessing the CLI from a Local Terminal1Use 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.2Run a terminal emulation program, such as HyperTerminal™.3Set the communication parameters listed in the following table:4The login prompt is displayed. (Press Enter if the login prompt is not displayed.) Enter your login ID and password to log in to the CLI.To access the CLI via the MON connector:Table 4-1: COM Port ConfigurationParameter ValueBaud rate 115200Data bits 8Stop bits 1Parity NoneFlow control Xon/XoffPort Connected COM port](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-19.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 116 System ManualAfter 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 4.1.2.4.1.1.2 Accessing the CLI From a Remote TerminalThe procedure for accessing the CLI from a remote terminal differs with respect to the IP connectivity mode. The Ethernet port and IP interface you are required to configure for enabling remote connectivity is different for each connectivity mode. For more information about connectivity modes, and Ethernet ports and IP interface used for operating the 4Motion system, refer “Managing the IP Connectivity Mode” on page 136.1Assign an IP address to the external-management interface. For this, execute the following procedure. (Refer Table 4-8 for more information about the IP interface to be configured for the connectivity mode you have selected). aRun the following command to enable the interface connectivity mode for the external-management interface:npu(config)# interface external-mgmtbRun the following command to disable the interface:NOTEThe default login ID and password are:Login ID: rootPassword: admin123To access the CLI from a remote terminal, execute the following procedure:IMPORTANTThe 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. This procedure is identical for all other connectivity modes. However, the Ethernet port, VLAN, and IP interface to be configured will differ for the out-of-band and unified connectivity modes, as listed in Table 4-8.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-20.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 117 System Manualnpu(config-if)# shutdowncRun the following command to assign an IP address to this interface:npu(config-if)# ip address <ip-address> <subnet-mask>dRun the following command to enable this interface:npu(config-if)# no shutdown2Connect the Ethernet cable to the DATA connector on the front panel of the NPU. (Refer Table 4-8 for more information about the Ethernet port to be used for the connectivity mode you have selected). 3To enable exchange of packets, create IP-level connectivity between the remote machine and the external-management interface.4From the remote terminal, execute the following command to use Telnet/SSH to access the IP address of the external-management interface:telnet <ip address of external-management interface>ssh <ip address of external-management interface>5At the prompt, enter your login ID and password.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 4.1.2.4.1.2 Command ModesThe CLI provides a number of command modes, some of which are listed in the following table for executing different types of commands:NOTEThe default login ID and password are:Login ID: rootPassword: admin123](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-21.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 118 System ManualThe following table lists the commands to be executed for entering/exiting a particular command mode:4.1.3 Interpreting the Command SyntaxThe following table lists the conventions used in the command syntax for all 4Motion commands:Table 4-2: CLI Command ModesMode Used for... Command PromptGlobal configuration mode Executing all configuration commandsnpu(config)#Global command mode Executing all other commands such as show and delete commandsnpu#Interface configuration mode Executing all commands for configuring physical and IP interfaces.npu(config-if)#Standard/extended ACL mode Executing commands for configuring standard and extended ACLsnpu(config-std-nacl)# npu(config-ext-nacl)# Table 4-3: Commands to Enter/Exit a Command ModeTo... Run the Command... The Command Mode is Now...Enter the global configuration modenpu# config terminal npu(config)#Enter the interface configuration modenpu(config)# interface {<interface-type> <interface-id> |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au}npu(config-if)# Exit the configuration mode and enter the global command mode.npu(config)# endnpu (config-if)# endnpu#npu#Exit the current configuration mode by one levelnpu (config-if)# exit npu(config)#](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-22.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 119 System ManualTable 4-4: Conventions Used in the 4Motion Command SyntaxConvention Description Example{ } Indicates that the parameters enclosed in these brackets are mandatory, and only one of these parameters should be specified.npu(config)# limit { cpu | memory} ([softlimit <limit>] [hardlimit <limit>])This command is used for specifying the soft and hard limits for memory and CPU utilization. The cpu/memory parameters are enclosed within {} brackets, indicating that their presence is mandatory, and that only one of these parameters is required. ( ) Indicates that one or all parameters enclosed within these brackets are optional. However, the presence of at least one parameter is required to successfully execute this command.npu(config)# limit { cpu | memory} ([softlimit <limit>] [hardlimit <limit>])This command is used for specifying the soft and hard limits for memory and CPU utilization. The softlimit and hardlimit parameters are enclosed within () brackets, indicating that you are required to specify the value of at least one of these parameters to successfully execute this command.[ ] Indicates that the parameter enclosed within these brackets is optional.npu(config)# reboot from shadow [<shadow image name>]This command is used to reboot the system with the shadow image. The shadow image name parameter is enclosed with the [ ] brackets, indicating that it is optional. If you do not specify the value of this parameter, the system automatically boots up with the last downloaded shadow image.< > Indicates that the parameter is mandatory and requires a user-defined value (and not a discrete value).npu(config)# load to shadow <shadow image name>This command is used to load the system with a particular shadow image. It is mandatory to specify a value for the shadow image name parameter; otherwise an error is raised by the system. The value of this parameter is not a discrete value; you are required to specify a value for this parameter.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-23.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 120 System Manual4.1.4 Using the CLITo help you use the CLI, this section provides information about:“Using Control Characters” on page 120“Using the CLI Help” on page 121“Using the History Feature” on page 121“Using Miscellaneous Commands” on page 122“Privilege Levels” on page 1224.1.4.1 Using Control CharactersControl characters refer to special characters that you can use to recall or modify previously-executed commands. The following table lists the control characters to be used for executing commands on the CLI:| Indicates the OR conditional operator that is used between two or more parameters. The presence of this parameter indicates that only one of the parameters separated by the I conditional parameter should be specified in the command.npu(config)# group enable {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}This command is used to specify the group for which performance data collection and storage is to be enabled. The | conditional operator indicates that only one parameter should be specified.NOTEIn this document, all discrete values are specified in boldface, and all user-defined values are not bold.Table 4-4: Conventions Used in the 4Motion Command Syntax](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-24.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 121 System Manual4.1.4.2 Using the CLI HelpThe CLI provides help that you can access while using the CLI. Execute the following command to obtain help for a specific command:help [“<text>”]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.4.1.4.3 Using the History FeatureThe history feature of the CLI maintains a sequential list of all previously executed commands. The following table lists the commands that you can run to access, edit or execute a command from the command history list:Table 4-5: Control Characters for Using the CLIPress To...Up/Down arrow keys Scroll the previously executed CLI commands. Press Enter if you want to select and execute a particular command.Right/Left arrow keys Navigate to the right/left of the selected character in a command.Home key Navigate to the first character of a command.End key Navigate to the last character of a command.Backspace key Delete the characters of a command.TAB key Prompt the CLI to complete the command for which you have specified a token command. Remember that the CLI that is the nearest match to the token command that you have specified is displayed.? key View the list of commands available in the current mode. If you press ? after a command, a list of parameters available for that command is displayed.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-25.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 122 System Manual4.1.4.4 Using Miscellaneous CommandsThe following table lists other miscellaneous commands that you can execute while using the CLI:4.1.4.5 Privilege LevelsAll commands that can be executed using the CLI are assigned privilege levels between 0 and 15, where 0 is the lowest, and 15 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, root, is assigned privilege level 15. However, if you are logging in as root, you can execute certain additional commands for managing users and enabling passwords for privilege levels. For more information about managing users and privileges, refer to Section 4.1.5.4.1.5 Managing Users and PrivilegesTo enable multi-level access to the CLI, you can create and manage multiple users, and assign privilege levels for each user. The privilege level determines whether a user is authorized to execute a particular command. The privilege level is pre-configured for each command, and can be between 0 and 15, where 0 is the lowest and 15 is the highest. The user can execute all commands for which the Table 4-6: Commands for Using the History FeatureRun the command... To...show history Obtain a list of previously executed commands.!! Execute the last command displayed in the list of previously executed commands.!<n> Execute the nth command in the list of previously-executed commands. !<string> Execute the most recent command in the CLI history that starts with the string entered as the value for the string parameter.Table 4-7: Miscellaneous CommandsEnter the command... To...exit Exit the CLI. After you run this command, provide your login ID and password to access the CLI.clear screen Clear the screen.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-26.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 123 System Manualprivilege level is equal to or lower than the default privilege level assigned to the user.You can also configure passwords for each privilege level. Users with lower privilege levels can enter this password to enable higher privilege levels.This section describes the commands for:“Managing Users” on page 123“Managing Privileges” on page 126“Enabling/Disabling Higher Privilege Levels” on page 128“Displaying Active Users” on page 130“Displaying All Users” on page 130“Displaying the Privilege Level” on page 1314.1.5.1 Managing UsersYou can add/modify/delete one or more users for accessing the CLI either through a local or remote terminal.This section describes the commands for:“Adding/Modifying Users” on page 124“Deleting a User” on page 125IMPORTANTBy default, the privilege level of users logging in with root privileges is 15. However, the root user can execute some additional commands for adding users and enabling passwords for different privilege levels. IMPORTANTOnly users who have logged in as root can add/modify/delete users.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-27.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 124 System Manual4.1.5.1.1 Adding/Modifying UsersTo add/modify a user, and assign a username, password, and privilege level, run the following command:npu(config)# username <name> password <password> privilege <0-15>IMPORTANTOnly users who have logged in as root can execute this task.IMPORTANTAn error may occur if:You are not logged in as the root.The username or password that you have specified is more than 20 characters.The privilege level that you have specified is not within the range, 0-15.Command Syntaxnpu(config)# username <name> password <password> privilege <0-15>Privilege LevelrootSyntax Description Parameter Description Presence Default ValuePossible Valuesusername <name>Indicates the user name of the user to be added.Mandatory N/A String (up to 20 characters and case-sensitive)password <password>Indicates the password to be assigned to the user to be added.Optional passwordString (up to 20 characters and case-sensitive)privilege <0-15>Indicates the privilege level to be assigned to a user. The user will be permitted to execute all commands for which the privilege level is equal to or lower than the value of this parameter.Mandatory N/A 0-15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-28.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 125 System Manual4.1.5.1.2 Deleting a UserTo delete a user, run the following command:npu(config)# no user <username>Command ModesGlobal command modeIMPORTANTOnly users who have logged in as root can execute this task.IMPORTANTAn error may occur if:You are not logged in as root user.The username that you have specified does not exist. Remember that user names are case-sensitive.You are trying to delete an active user or the root user. Command Syntaxnpu(config)# no user <username>Privilege LevelrootSyntax Description Parameter Description Presence Default ValuePossible Valuesusername <name>Indicates the username of the user to be deleted.Mandatory N/A String (upto 20 characters and case-sensitive)Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-29.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 126 System Manual4.1.5.2 Managing PrivilegesTo enable users to execute commands that require a higher privilege level (than their currently configured default level), you can configure a password for each privilege level. Other users can then use the password you have specified to enable a higher privilege level. This section describes the commands for:“Assigning a Password for a Privilege Level” on page 126“Deleting a Password for a Privilege Level” on page 1274.1.5.2.1 Assigning a Password for a Privilege LevelTo assign a password for a privilege level, run the following command:npu(config)# enable password [Level <0-15>] <password> IMPORTANTOnly users who have logged in as root can assign or delete passwords for any privilege level.IMPORTANTOnly users who have logged in as root can execute this command.IMPORTANTAfter 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 4.1.5.3.IMPORTANTAn error may occur if:You are trying to configure a password for a privilege level that is higher than your default privilege level. The password that you have specified is more than 20 characters.The privilege level that you have specified is not within the range, 0-15.Command Syntaxnpu(config)# enable password [Level <0-15>] <password>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-30.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 127 System Manual4.1.5.2.2 Deleting a Password for a Privilege LevelTo delete a password for a privilege level, run the following command:npu(config)# no enable password [Level <0-15>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[Level <0-15>] Indicates the privilege level for which a password is to be enabled.Optional 15 0-15<password> Denotes the password to be assigned for the current privilege level.Mandatory N/A String (up to 20 characters and case-sensitive)Command ModesGlobal configuration modeIMPORTANTOnly users who have logged in as root can execute this command.IMPORTANTAn error may occur if:The privilege level that you have specified is not within the range, 0-15.You are trying to delete a password for a privilege level that is higher than your default privilege level.Command Syntaxnpu(config)# no enable password [Level <0-15>]Privilege Levelroot](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-31.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 128 System Manual4.1.5.3 Enabling/Disabling Higher Privilege LevelsYou can execute commands that require higher privilege levels. If the root user has configured a password for that level, you can use that password to enable higher privilege levels.For example, if your privilege level is 1, you can provide the password configured for privilege level 10 to execute all commands that require privilege level 10.This section describes the commands for:“Enabling a Higher Privilege Level” on page 128“Returning to the Default Privilege Level” on page 1294.1.5.3.1 Enabling a Higher Privilege Level1Log in to the CLI.2Run the following command to specify the privilege level and password:npu(config)# enable [Level <0-15>]3At the password prompt, specify the password configured for the privilege level that you have specified.If you specify the correct password, you are logged in to the CLI with the privilege level that you had specified. You can now execute all commands that require the current privilege level.Syntax Description Parameter Description Presence Default ValuePossible Values[Level <0-15>] Indicates the privilege level for which a password is to be disabled.Optional 10 015Command SyntaxGlobal configuration modeTo enable a higher privilege level:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-32.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 129 System ManualYou can, at any time, return to your default privilege level. For details, refer Section 4.1.5.3.2.4.1.5.3.2 Returning to the Default Privilege LevelRun the following command to disable the current privilege level, and return to your default privilege level:npu(config)# disable [Level <0-15>]After you run this command, you automatically return to your default privilege level. You can display your current privilege level, using the following command:npu# show privilege NOTEYou can display your current privilege level, using the following command:npu# show privilege NOTEAn error may occur if:You have specified an incorrect password. Remember that all passwords are case-sensitive.No password is not configured for the privilege level you are trying to access.Command Syntaxnpu(config)# enable [Level <0-15>]Privilege Level0Syntax Description Parameter Description Presence Default ValuePossible Values[Level <0-15>] Indicates the privilege level you want to enable.Mandatory N/A 0-15Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-33.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 130 System Manual4.1.5.4 Displaying Active UsersTo display all active users, run the following command:npu# show users4.1.5.5 Displaying All UsersTo display all users, run the following command:npu# listuserCommand Syntaxnpu(config)# disable [Level <0-15>]Privilege Level0Syntax Description Parameter Description Presence Default ValuePossible Values[Level <0-15>] Indicates the privilege level you want to disable.Mandatory N/A 0-15Command ModesGlobal configuration modeCommand Syntaxnpu# show usersPrivilege Level1Display FormatLine User Peer Address0 con <user name> <value>Command SyntaxGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-34.png)
![Chapter 4 - Operation and Administration Using the CLI Using the Command Line Interface for 4Motion System 4Motion 131 System Manual4.1.5.6 Displaying the Privilege LevelTo display your current privilege level, run the following command:npu# show privilegeCommand Syntaxnpu# listuserPrivilege Level1Display FormatUser ModeUser 1 <value>User 2 <value>User 3 <value>Command SyntaxGlobal command modeCommand Syntaxnpu# show privilegePrivilege Level1Display FormatCurrent privilege level is <value>Command SyntaxGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-35.png)
![Chapter 4 - Operation and Administration Using the CLI Shutting Down/Resetting the System4Motion 132 System Manual4.2 Shutting Down/Resetting the SystemThis section describes the commands for:“Shutting Down the System” on page 132“Managing System Reset” on page 1334.2.1 Shutting Down the SystemYou 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. It is also possible that the system may initiate self shutdown if an internal error has occurred.To shut down the 4Motion system, run the following command:npu# npu shutdownA few seconds after you run this command, the system is shut down.IMPORTANTBefore shutting down the system, it is recommended that you:Save the configuration file. The last saved configuration is used for rebooting the system. For more information about saving the current configuration, refer to Section 4.3.4.1.Periodically make a backup of log and trace files on the NPU flash if you have configured logs and traces to be written to file. This file does not store log and trace messages after the system is reset or shut down. For details, refer to Section 4.3.11.1.5.NOTECAUTIONThe system does not display any warning or request for verification; it immediately shuts down after you execute this command. To start up the NPU (after shut down), either switch off and then switch on the -48V power supply, or disconnect and then reconnect the PIU power cable. Command Syntaxnpu# npu shutdownPrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-36.png)
![Chapter 4 - Operation and Administration Using the CLI Shutting Down/Resetting the System4Motion 133 System Manual4.2.2 Managing System ResetSystem 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. After the system is reset and boots up, you can use the CLI to retrieve the reason for the last system reset. For more information about using the CLI to display the reason for system reset, refer to “Displaying the Reason for the Last System Reset” on page 134.4.2.2.1 Resetting the systemTo reset the system, run the following command:npu(config)# resetA few seconds after you run this command, the 4Motion system is shut down, and then boots up with the last saved configuration. Command ModesGlobal command modeIMPORTANTBefore resetting the system, it is recommended that you:Save the configuration file. For more information about saving the current configuration, refer to Section 4.3.4.1. Periodically make a backup of log and trace files on the NPU flash if you have configured logs and traces to be written to file. This file does not store log and trace messages after the system is reset or shut down. For details, refer to Section 4.3.11.1.5.Command Syntaxnpu(config)# resetPrivilege Level10Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-37.png)
![Chapter 4 - Operation and Administration Using the CLI Shutting Down/Resetting the System4Motion 134 System Manual4.2.2.2 Displaying the Reason for the Last System ResetThe 4Motion system may be reset because of any of the following reasons.NPU upgradeHealth 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.System initialization failure after last rebootUser-initiated system resetGeneric (unknown error)To display the reason for the last system reset, run the following command:npu# show reset reasonAfter you run this command, the reason for the last system reset is displayed.Command Syntaxnpu# show reset reasonPrivilege Level1Display FormatReset reason : <Reason For Last Reset>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-38.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 135 System Manual4.3 NPU ConfigurationAfter 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. You can then use the CLI to modify these configuration parameters. This section provides information about the following configuration-specific tasks:“Managing the IP Connectivity Mode” on page 136“Configuring Physical and IP Interfaces” on page 139“Managing the NPU Boot Mode” on page 169“Managing the 4Motion Configuration File” on page 172“Batch-processing of CLI Commands” on page 180“Configuring the CPU” on page 181“Configuring QoS Marking Rules” on page 196“Configuring Static Routes” on page 211“Configuring ACLs” on page 215“Configuring the ASN-GW Functionality” on page 246“Configuring Logging” on page 395“Configuring Performance Data Collection” on page 411“Configuring the SNMP/Trap Manager” on page 421NOTEFor more information about accessing the CLI from a local terminal or remotely via Telnet/SSH, refer to, Section 4.1.1.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-39.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 136 System Manual“Configuring the 4Motion Shelf” on page 4294.3.1 Managing the IP Connectivity ModeThe following are the various types of traffic originating or terminating from/to the NPU: Subscriber data flows ASN/CSN control messages Network Management System (NMS) traffic (external management traffic)Local management trafficInternal management traffic4Motion has defined separate IP domains for each traffic type: Bearer IP domain: Enables connectivity between ASN-GW (NPU), Base Station (BS), AAA server and the Home Agent (HA) for managing transport for subscriber data and the ASN/CSN control traffic.NMS IP domain (external management IP domain): Defines the connectivity between NMS agent of the NPU and external NMS server.Local management IP domain: Defines the connectivity between the NMS agent of NPU and IP-based local craft terminal. Internal management IP domain: Enables connectivity between the NPU NMS agent and management agents for the AU cards.Subscriber IP domain: NPU supports subscriber IP domain through multiple VLAN service interfaces.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.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-40.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 137 System ManualIn-band connectivity mode: In this connectivity mode, the VLAN is used to differentiate between the bearer and external NMS IP domains on the DATA port. The bearer VLAN is used for the bearer IP domain and the external-management VLAN is used for the external NMS IP domain. The MGMT port is assigned to the local-management VLAN in this connectivity mode.Unified connectivity mode: In this connectivity mode, the bearer IP domain and external NMS IP domain are unified. That is, the same IP address and VLAN are used to connect to the NMS server, AAA server, HA, and BS. (The MGMT port is assigned to the local-management VLAN in this connectivity mode.For more information about the VLANs that are configured for 4Motion, refer the section, “Configuring Physical and IP Interfaces” on page 139.The following table lists the physical interface and VLAN configuration with respect to the connectivity mode:IMPORTANTFor all connectivity modes, the CSCD port enabled in VLAN-transparent bridging mode, and is assigned to local-management VLAN.IMPORTANTIn addition to the bearer IP domain, local-mangement IP domain, and external-management IP domain, each NPU has an internal NMS IP domain. The internal NMS IP domain is used for separating the IP domain for management traffic between the BS and NPU card. Table 4-8: Ethernet and VLAN-to-Connectivity Mode ConfigurationConnectivity Mode Bearer IP Domain External-Management IP Domain Local-management IP DomainOut-of-band DATA portBearer VLANMGMT portExternal-management VLANCSCD portLocal-management VLANIn-band DATA portBearer VLANDATA portExternal-management VLANCSCD and MGMT portsLocal-management VLAN](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-41.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 138 System ManualThis section describes the commands for:“Configuring the IP Connectivity Mode” on page 138“Displaying the IP connectivity Mode” on page 1394.3.1.1 Configuring the IP Connectivity ModeTo configure the IP connectivity mode, run the following command:npu(config)# connectivity mode {inband | outband | unified}In-band is the default connectivity mode. You can display the currently configured connectivity mode. For details, refer Section 4.3.1.2.Unified DATA portBearer VLANDATA portBearer VLANCSCD and MGMT portsLocal-management VLANIMPORTANTReset the system for the change in connectivity mode to take effect.Command Syntaxnpu(config)# connectivity mode {inband | outband | unified}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{inband | outband | unified}Indicates the connectivity mode to be configured.Mandatory inband inbandoutbandunifiedTable 4-8: Ethernet and VLAN-to-Connectivity Mode ConfigurationConnectivity Mode Bearer IP Domain External-Management IP Domain Local-management IP Domain](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-42.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 139 System Manual4.3.1.2 Displaying the IP connectivity ModeTo display the IP connectivity mode, run the following command:npu# show connectivity mode4.3.2 Configuring Physical and IP InterfacesThe following Ethernet interfaces are provided on the front panel of the NPU for enabling connectivity with external entities:DATA port: A Gigabit Ethernet interface that connects the NPU with the operator network.CSCD port: A Gigabit Ethernet interface that provides a dedicated Ethernet connectivity to the local management NMS Server, or supports concatenation 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.Command ModesGlobal configuration modeCommand Syntaxnpu# show connectivity modePrivilege Level1Display Formatconnectivity mode is <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-43.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 140 System ManualThe following table lists the default (non-configurable) VLAN ID for each physical interface:In addition to these Ethernet interfaces, you can also configure seven Fast Ethernet interfaces from the NPU towards the AUs. These interfaces are internal NPU interfaces, and are not accessible to user.Based on the connectivity mode, 4Motion initializes the following pre-configured IP interfaces:Local-management: Used for enabling connectivity with the local NMS server that is connected via the MGMT port when 4Motion is operating in the in-band connectivity mode; or via CSCD port when 4Motion is operating in the out-of-band connectivity mode. The IP address used for the local-management interface is intended for "back-to-back" connection between NPU and Local NMS Server.Internal-management: Used for enabling the NMS connectivity between the AU and NPU. This interface is used internally by 4Motion and is not reachable from user-visible ports. The IP address and VLAN identifier used for the internal-management interface are not user-configurable.External-management: Used for enabling connectivity with the NMS server that is connected via the DATA port when 4Motion is operating in the in-band connectivity mode, or via MGMT port when 4Motion is operating in the out-of-band connectivity mode.Bearer: Used for enabling bearer IP domain connectivity. When the Unified connectivity mode is selected, the NMS server is also connected using bearer interface.You can configure the IP address for bearer, external-management and local-management interfaces. You can also modify the VLAN ID for bearer and Table 4-9: Default VLAN IDs For Ethernet interfacesPhysical Port Default VLAN IDMGMT 9CSCD 9DATA 117 AU Fast Ethernet interfaces11](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-44.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 141 System Manualexternal-management interfaces. The following table lists the default VLAN IDs assigned to pre-configured IP interfaces.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.NPUAll AUsThis section describes the commands for:“Configuring Physical Interfaces” on page 141“Managing the External Ether Type” on page 157“Configuring IP interfaces” on page 158“Configuring Virtual Interfaces” on page 166“Displaying Status and Configuration Information for Physical, IP, and Virtual Interfaces” on page 1664.3.2.1 Configuring Physical InterfacesThe NPU contains seven AU-facing Fast Ethernet interfaces, and three Ethernet interfaces on the front panel: one Fast Ethernet interface (MGMT port) and two Gigabit Ethernet interfaces (DATA and CSCD ports). Each of these interfaces is a Table 4-10: Default VLAN IDsInterface Default VLAN IDLocal-management 9 Internal-management 10 (non-configurable)Bearer 11External-management 12](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-45.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 142 System Manualmember of one or more VLANs. The following table lists the physical interfaces, and their type, port numbers and member VLANs:1Enable the interface configuration mode (refer Section 4.3.2.3.1).2You can now enable any of the following tasks:»Modify the physical properties of an interface (refer Section 4.3.2.1.2).»Manage VLAN translation (refer Section 4.3.2.1.3).3Terminate the interface configuration mode (refer Section 4.3.2.3.7).You can, at any time, display VLAN membership information (refer Section 4.3.2.1.5), and VLAN translation entries for the DATA port (refer Section 4.3.2.1.7).4.3.2.1.1 Enabling the Interface configuration modeTo configure a physical interface, run the following command to enable the interface configuration mode. Table 4-11: Ethernet Interfaces - Types, Port Numbers, and Member VLANsInterface Type Physical Interfaces Port Number Member VLANsFast Ethernet Seven Fast Ethernet interfaces towards the AU (internal to the NPU)0/1-0/7 BearerInternal-managementMGMT 0/8 Local-management (in the in-band or out-of-band connectivity modes)External-management (only in the out-of-band connectivity mode)Gigabit Ethernet CSCD 0/9 Local-managementDATA 0/10 Bearer·External-management (only in-band connectivity mode)Multiple Service VLANTo configure a physical interface:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-46.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 143 System Manualnpu(config)# interface {<interface-type> <interface-id> |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au}After enabling the interface configuration mode, you can:Modify the physical properties of an interface (refer to Section 4.3.2.1.2)Manage VLAN translation (refer to Section 4.3.2.1.3)Table 4-12: Parameters for Configuring the Interface Configuration Mode (Ethernet Interfaces)Interface Parameter ExampleFast Ethernet <interface-type> <interface-id>npu(config)# interface au fastethernet 0/1npu(config)# interface au fastethernet 0/2npu(config)# interface au fastethernet 0/3npu(config)# interface au fastethernet 0/4npu(config)# interface au fastethernet 0/5npu(config)# interface au fastethernet 0/6npu(config)# interface au fastethernet 0/7npu(config)# interface fastethernet 0/8Gigabit Ethernet<interface-type> <interface-id>npu(config)# interface gigabitethernet 0/9npu(config)# interface gigabitethernet 0/10IMPORTANTTo enable the interface configuration mode for physical interfaces, specify values for the interface-type and interface-id parameters only. The internal-mgmt, external-mgmt, bearer, local-mgmt parameters are used for enabling the interface configuration mode for IP interfaces; the npu-host and all-au parameters are used for enabling the interface configuration mode for virtual interfaces. For more information about configuring IP interfaces, refer to Section 4.3.2.3; refer to Section 4.3.2.4 for configuring virtual interfaces.IMPORTANTAn error may occur if the interface type and ID that you have specified is in an invalid format or does not exist. Refer to the syntax description for more information about the correct format for specifying the interface type and name.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-47.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 144 System ManualCommand Syntaxnpu(config)# interface {<interface-type> <interface-id> |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<interface-type>Indicates the type of physical interface (Gigabit Ethernet or Fast Ethernet) for which the configuration mode is to be enabled.Mandatory N/A au fastethernetfastethernetgigabitethernet<interface-id> Indicates the port number of the physical interface for which the configuration mode is to be enabled.Mandatory N/A AU Fast Ethernet:0/10/20/30/40/50/60/7Fast Ethernet0/8Gigabit Ethernet:0/90/10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-48.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 145 System Manual4.3.2.1.2 Configuring the Properties of the Physical InterfaceAfter you enable the interface configuration mode, you can configure the following properties for this interface:Auto-negotiation modeDuplex (full/half) modePort speedMTUBefore you modify the properties of a physical interface, first shut down the interface. This section describes the commands to be used for:“Shutting down the interface” on page 145“Defining the auto-negotiation mode” on page 146“Specifying the Duplex Status” on page 147“Specifying the port speed” on page 147“Configuring the MTU for physical interfaces” on page 1484.3.2.1.2.1 Shutting down the interfaceRun the following command to shut down this physical interface:npu(config-if)# shutdownRun the following command to enable this physical interface:npu(config-if)# no shutdownCommand ModesGlobal configuration modeIMPORTANTBeware from shutting down the interface you use for accessing the device.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-49.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 146 System Manual4.3.2.1.2.2 Defining the auto-negotiation modeThe auto-negotiation feature enables the system to automatically negotiate the port speed and the duplex (half or full) status with the link partner. If you disable auto-negotiation, you are required to manually configure the port speed and duplex status.Run the following command to enable the auto-negotiation mode:npu(config-if)# auto-negotiateEnter the following command if you want to disable the auto-negotiation mode:npu(config-if)# no auto-negotiateAfter you disable auto-negotiation, you can manually configure the port speed and duplex status. For details, refer to Section 4.3.2.1.2.3 and Section 4.3.2.1.2.4Command Syntaxnpu(config-if)# shutdownnpu(config-if)# no shutdownPrivilege Level10Command ModesInterface configuration modeIMPORTANTBy default, auto-negotiation is enabled.IMPORTANTAn error may occur if you run this command when the physical interface is enabled. Command Syntaxnpu(config-if)# auto-negotiatenpu(config-if)# no auto-negotiatePrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-50.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 147 System Manual4.3.2.1.2.3 Specifying the Duplex StatusThe duplex status for an interface can be either full-duplex or half duplex. If you have disabled the auto-negotiation feature, specify whether data transmission should be half or full duplex.Run the following command to configure the full duplex mode for this interface:npu(config-if)# full-duplexRun the following command to configure the half duplex mode for this interface:npu(config-if)# half-duplex4.3.2.1.2.4 Specifying the port speedIf 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}Command ModesInterface configuration modeIMPORTANTBy default, full-duplex is enabled if auto-negotiation is disabled.IMPORTANTAn error may occur if you run this command when:The physical interface is enabled. Auto-negotiation is enabled.Command Syntaxnpu(config-if)# full-duplexnpu(config-if)# half-duplexPrivilege Level10Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-51.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 148 System ManualBy default, the port speed for the Fast Ethernet interfaces is 100 Mbps, and for the Gigabit Ethernet interfaces is 1000 Mbps.4.3.2.1.2.5 Configuring the MTU for physical interfacesYou can configure the MTU for the physical interface. If the port receives packets that are larger than the configured MTU, packets are dropped. Run the following command to configure the MTU of the physical interface:npu(config-if)# mtu <frame-size(1518-9000)>IMPORTANTAn error may occur if you run this command when:The physical interface is enabled. Auto-negotiation is enabled.The interface does not support the specified speed.Command Syntaxnpu(config-if)# speed {10 | 100 | 1000}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{10 | 100 | 1000}Indicates the speed, in Mbps, to be configured for this physical interface. A value of 1000 is not applicable for Fast Ethernet interfaces.Mandatory N/A 101001000Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-52.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 149 System Manual4.3.2.1.3 Managing VLAN Translation4Motion supports translation of the VLAN ID for packets received and transmitted on the DATA port to a configured VLAN ID. Before starting VLAN translation, first enable VLAN translation, and then create one or more VLAN translation entries.This section describes the commands for:“Enabling/Disabling VLAN Translation” on page 150“Creating a VLAN Translation Entry” on page 150“Deleting a VLAN Translation Entry” on page 152IMPORTANTAn error may occur if you run this command when the physical interface is enabled.Command Syntaxnpu(config-if)# mtu <frame-size(1518-9000)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<frame-size(1518-9000)>Indicates the MTU (in bytes) to be configured for the physical interface.For the Backhaul interface the range is from 1518 to 9000.For all other interfaces the following values are supported by the hardware: 1518, 1522, 1526, 1536, 1552, 1664, 2048, 9022.mandatory For the Backhaul and AU interfaces the default is 1664.For all other physical interfaces the default is 1522.1518-9000 for the Backhaul interface.1518, 1522, 1526, 1536, 1552, 1664, 2048, 9022 for all other interfaces.Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-53.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 150 System Manual4.3.2.1.3.1 Enabling/Disabling VLAN TranslationBy 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}4.3.2.1.3.2 Creating a VLAN Translation EntryA VLAN translation entry contains a mapping between the original and translated VLANs. To create a VLAN translation entry, run the following command:npu(config-if)# vlan mapping <integer(11-4094)> <integer(11-4094)>Specify the original VLAN ID and the translated VLAN ID. IMPORTANTAn error may occur when you run this command:For an interface other than the DATA port (0/10).Command Syntaxnpu(config-if)# vlan mapping {enable|disable}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{enable|disable}Indicates whether VLAN translation should be enabled or disabled for this interface.Mandatory disable enabledisableCommand ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-54.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 151 System ManualIMPORTANTAn error may occur if:The original and translated VLAN ID that you have specified is not within the range, 11-4094.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.VLAN translation is disabled.Command Syntaxnpu(config-if)# vlan mapping <integer(11-4094)> <integer(11-4094)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<integer(11-4094)>The first VLAN ID Indicates the VLAN ID of the VLAN for which VLAN translation is required.Legitimate values include:The Bearer VLAN ID (default 11).The External Management VLAN ID (default 12) - only in In-Band Connectivity Mode. Mandatory N/A 11-4094<integer(11-4094)>Indicates the translated VLAN ID that is being mapped to the original VLAN ID.Mandatory N/A 11-4094Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-55.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 152 System Manual4.3.2.1.3.3 Deleting a VLAN Translation EntryTo delete an existing VLAN translation entry, run the following command:npu(config-if)# no vlan mapping {all | <integer(11-4094)> <integer(11-4094)>}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.IMPORTANTAn error may occur if: The VLAN ID or mapping that you have specified is not within the range, 11-4094 or it does not exist.You are trying to delete a VLAN translation entry for a VLAN that is not a member of this physical interface.Command Syntaxnpu(config-if)# no vlan mapping {all | <integer(11-4094)> <integer(11-4094)>}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-56.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 153 System Manual4.3.2.1.4 Terminating the Interface Configuration ModeTo terminate the interface configuration mode, run the following command:npu(config-if)# exitSyntax Description Parameter Description Presence Default ValuePossible Values{all | <integer(11-4094)> <integer(11-4094)>}Indicates the VLAN translation entry to be deleted. Mandatory N/A all: Indicates that all VLAN translation entries are to be deleted.<integer(11-4094)> <integer(1-4094)>: Indicates the original and translated VLAN IDs for the translation entry to be deleted.Command ModesGlobal command modeCommand Syntaxnpu(config-if)# exitPrivilege Level10Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-57.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 154 System Manual4.3.2.1.5 Displaying VLAN Membership InformationRun the following command to display Ethernet interfaces that are members of a particular or all VLAN:npu# show vlan [id <vlan-id(11-4094)>]Do not specify the VLAN ID if you want to view membership information for all VLANs.4.3.2.1.6 Displaying VLAN Configuration Information for Physical InterfacesTo display the configuration information for a VLAN that is bound to a particular physical interface, run the following command:npu# show vlan port config [port <interface-type> <interface-id>]Command Syntaxnpu# show vlan [id <vlan-id(11-4094)>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[id <vlan-id(11-4094)>]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.Mandatory N/A 11-4096Display FormatVlan Name Ports ---- ---- ----- <VLAN ID <>VLAN Name> <member ports><VLAN ID <>VLAN Name> <member ports>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-58.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 155 System ManualDo not specify the port number and type if you want to display configuration information for all physical interfaces. IMPORTANTAn error may occur if you specify an interface type or ID that does not exist.Command Syntaxnpu# show vlan port config [port <interface-type> <interface-id>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values<interface-type>Indicates the type of physical interface for which VLAN membership information is to be displayed.Optional N/A fastethernetgigabitethernet<interface-id> Indicates the ID of the physical interface for which VLAN membership information is to be displayed.Optional N/A Fast Ethernet:0/10/20/30/40/50/60/70/8Gigabit Ethernet:0/90/10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-59.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 156 System Manual4.3.2.1.7 Displaying the VLAN Translation EntriesRun the following command to display VLAN translation entries for a Gigabit Ethernet interface:npu# show interface gigabitethernet <interface-id> vlan mappingDisplay FormatVlan Port configuration table----------------------------------------Port <port number> Port Vlan ID : <value> Port Acceptable Frame Type : <value> Port Ingress Filtering : <Enabled/Disabled>Command ModesGlobal command modeIMPORTANTAn error may occur if you specify an interface ID that does not exist.Command Syntaxnpu# show interface gigabitethernet <interface-id> vlan mappingPrivilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values<interface-id> Indicates the identifier of the Gigabit Ethernet interface for which VLAN translation entries are to be displayed.In current release VLAN Mapping is supported only on the DATA port (interface-id 0/10).Mandatory N/A 0/10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-60.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 157 System Manual4.3.2.2 Managing the External Ether TypeThe External Ether Type parameter defines the EtherType in outer VLAN header of uplink Q-in-Q traffic. The External Ether Type parameter is not applicable the device operates in Transparent (Centralized ASN Topology) mode. This section includes:“Configuring the External Ether type”“Displaying the Ether Type”4.3.2.2.1 Configuring the External Ether typeTo configure the Ether Type run the following command: npu(config)# config npuEtherType {8100 | 88A8 | 9100 | 9200}Command ModesGlobal command modeCommand Syntaxnpu(config)# config npuEtherType {8100 | 88A8 | 9100 | 9200}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{8100 | 88A8 | 9100 | 9200}Indicates the type of Ether Type.Mandatoryl 88A8 810088A891009200Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-61.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 158 System Manual4.3.2.2.2 Displaying the Ether TypeRun the following command to display the current Ether Type value:npu# show npuetherType4.3.2.3 Configuring IP interfacesThe following IP interfaces are pre-configured in the system:Local-managementInternal-managementExternal-managementBearer1Enable the interface configuration mode (refer Section 4.3.2.3.1).2Shut down the IP interface (if you are modifying configuration information for this interface) (refer to Section 4.3.2.3.2).Command Syntaxnpu# show npuetherTypePrivilege Level1Display FormatEthertype: <value>Command ModesGlobal command modeIMPORTANTYou cannot modify the IP address and VLAN identifier for the internal-management interface. You also cannot modify the VLAN identifier for the local-management.To configure an IP interface:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-62.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 159 System Manual3You can now:»Assign an IP address to an interface (refer to Section 4.3.2.3.3).»Remove an IP address associated with an interface (refer to Section 4.3.2.3.4).»Modify the VLAN ID (refer to Section 4.3.2.3.5).»Modify the MTU (refer to Section 4.3.2.3.6).4Enable the IP interface (refer to Section 4.3.2.3.2).5Terminate the interface configuration mode (refer to Section 4.3.2.3.7).You can, at any time, display configuration information for an IP interface (refer to Section 4.3.2.3.8).4.3.2.3.1 Enabling the Interface Configuration ModeTo configure an IP interface, run the following command to enable the interface configuration mode:npu(config)# interface {<interface-type> <interface-id> |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au}The following table lists the IP interfaces that each parameter represents: After enabling the interface configuration mode for this interface, you can:Table 4-13: Parameters for Configuring the Interface Configuration Mode (IP InterfacesIP Interface Parameter ExampleInternal-management internal-mgmt npu(config)# interface internal-mgmtExternal-management external-mgmt npu(config)# interface external-mgmtBearer bearer npu(config)# interface bearerLocal-management local-mgmt npu(config)# interface local-mgmtIMPORTANTTo enable the interface configuration mode for IP interfaces, specify values for the for internal-mgmt, external-mgmt, bearer, local-mgmt only. The interface-type and interface-id parameters are used for enabling the interface configuration mode for physical interfaces; the npu-host and all-au parameters are used for enabling the interface configuration mode for virtual interfaces. For more information about configuring physical interfaces, refer Section 4.3.2.1; refer Section 4.3.2.4 for configuring virtual interfaces.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-63.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 160 System ManualAssign an IP address to an interface (refer Section 4.3.2.3.3).Remove an IP address associated with an interface (refer Section 4.3.2.3.4).Modify the VLAN ID (refer Section 4.3.2.3.5).Modify the MTU (refer to Section 4.3.2.3.6).4.3.2.3.2 Shutting down/Enabling an IP InterfaceTo modify configuration for an IP interface, first shut down the IP interface, using the following command:npu(config-if)# shutdownAfter you have modified configuration for this interface, run the following command to enable the interface: npu(config-if)# no shutdownCommand Syntaxnpu(config)# interface {<interface-type> <interface-id> |internal-mgmt |external-mgmt | bearer | local-mgmt | npu-host | all-au}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesinternal-mgmt |external-mgmt | bearer | local-mgmtIndicates the IP interface for which the configuration mode is to be enabled.Mandatory N/A internal-mgmtexternal-mgmtbearerlocal-mgmtCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-64.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 161 System Manual4.3.2.3.3 Assigning an IP address to an interfaceRun the following command to assign an IP address and subnet mask for an IP interface. Shut down this interface before executing this command:npu(config-if)# ip address <ip-address> <subnet-mask>For example, run the following command to assign the IP address, 172.10.1.0, and subnet mask, 255.255.255.0 to the external-management interface:npu (config-if)# ip address 172.10.1.0 255.255.255.0Command Syntaxnpu(config-if)# shutdownnpu(config-if)# no shutdownPrivilege Level10Command ModesInterface configuration modeIMPORTANTYou can configure the IP address and subnet mask for only the external-management, local-management, and bearer interfaces. IMPORTANTAn error may occur if:The IP address you have specified is already configured for another interface.You are trying to assign an IP address for an interface for which IP address configuration is not permitted. This error is caused only for the internal-management interface (the pre-configured IP address for this interface is 10.0.0.254).The IP interface is enabled. Shut down the IP interface before executing this command.Command Syntaxnpu(config-if)# ip address <ip-address> <subnet-mask>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-65.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 162 System Manual4.3.2.3.4 Removing an IP Address from an InterfaceTo remove an IP address from an interface, run the following command. Shut down this interface before executing this command:npu(config-if)# no ip addressSyntax Description Parameter Description Presence Default ValuePossible Values<ip-address> Indicates the IP address to be assigned to this IP interface.The defaults are:External Management: 192.168.1.1Beare: 172.16.0.1Local Management: 172.31.0.1Mandatory Depends on interface type.Valid IP address<subnet-mask> Indicates the subnet mask to be assigned to this IP interface.Mandatory 255.255.255.0Valid subnet maskCommand ModesInterface configuration modeIMPORTANTAn error may occur if you run this command when this IP interface is enabled. Shut down the IP interface before executing this commandCommand Syntaxnpu(config-if)# no ip addressPrivilege Level10Command ModesInterface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-66.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 163 System Manual4.3.2.3.5 Configuring/Modifying the VLAN ID for an IP InterfaceRun the following command to modify the VLAN ID for this interface:npu(config-if)# if_vlan <vlanid(9 | 11-100 | 110-4094)>IMPORTANTYou can modify the VLAN ID for only the bearer, local-management and external-management interfaces.NOTERefer Table 4-10 for the default VLAN IDs assigned to the bearer, local-management and external-management interfaces.IMPORTANTAn error may occur if:The VLAN ID you have specified is not within the specified, or is in use by another VLAN. 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. You can modify the VLAN ID for only the external-management, local-management or bearer interfaces.Command Syntaxnpu(config-if)# if_vlan <vlanid(9 | 11-100 | 110-4094)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<vlanid(9 | 11-100 | 110-4094)Indicates the VLAN ID to be assigned to this interface.Note: The VLAN IDs, 1-8, 10, 101-109 are reserved.Mandatory N/A 911-100110-4094](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-67.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 164 System Manual4.3.2.3.6 Configuring the MTU for IP InterfacesYou can configure the MTU for the IP interface. Received packets that are larger than the configured MTU will be dropped. Run the following command to configure the MTU of the IP interface:npu(config-if)# mtu <frame-size(68-1500)>4.3.2.3.7 Terminating the Interface Configuration ModeTo terminate the interface configuration mode, run the following command:npu(config-if)# exitCommand ModesGlobal command modeIMPORTANTAn error may occur if you run this command when the interface is enabled.Command Syntaxnpu(config-if)# mtu <frame-size(68-1500)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<frame-size(68-1500)>Indicates the MTU (in bytes) to be configured for the IP interface.mandatory 1500 68-1500Command ModesInterface configuration modeCommand Syntaxnpu(config-if)# exit](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-68.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 165 System Manual4.3.2.3.8 Displaying IP Interface Status and Configuration InformationTo display the status and configuration information for an IP interface, run the following command:npu# show ip interface [{internal-mgmt | external-mgmt | bearer | local-mgmt}]Do not specify the interface if you want to view configuration information for all IP interfaces.Privilege Level10Command ModesInterface configuration modeIMPORTANTAn error may occur if the IP interface does not exist for the configured connectivity and boot mode.Command Syntaxnpu# show ip interface [{internal-mgmt | external-mgmt | bearer | local-mgmt}]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values{internal-mgmt | external-mgmt | bearer | local-mgmt}Indicates the interface for which configuration information is to be displayed.Do not specify any value for this parameter if you want to view configuration information for all IP interfaces.Optional N/A internal-mgmtexternal-mgmtbearerlocal-mgmt](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-69.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 166 System Manual4.3.2.4 Configuring Virtual InterfacesIn addition to physical and IP interfaces, 4Motion defines the following virtual interfaces. All ACLs configured for filtering traffic destined towards the NPU or AUs, are attached to either of these interfaces.NPU-host: Used for configuring ACLs to filter traffic destined towards the NPU.All-AU: Used for configuring ACLs to filter traffic destined towards the AUs in the 4Motion shelf. For more information about attaching ACLs to the NPU or all-AUs, refer the section, “Attaching/De-attaching ACLs to/from an Interface” on page 241.4.3.2.5 Displaying Status and Configuration Information for Physical, IP, and Virtual InterfacesTo display the status and configuration information for physical, IP and/or virtual interfaces, run the following command:npu# show interfaces [{[<interface-type> <interface-id>] | internal-mgmt | external-mgmt | bearer | local-mgmt | npu-host | all-au}]To display the configuration information for all interfaces, do not specify a value for any parameter.The following table lists parameters to be specified with respect to the type of interface for which configuration information is to be displayed:Display Format<Interface Name> is <up/down> Internet Address is <value>Broadcast Address <value>Command ModesGlobal command modeTable 4-14: Parameters for Displaying Configuration Information for Physical, IP, and Virtual InterfacesInterface Parameters ExampleAll Interfaces None npu# show interfaces](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-70.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 167 System ManualPhysical InterfacesFast Ethernet:<interface-type> <interface-id>npu# show interfaces fastethernet 0/1 npu# show interfaces fastethernet 0/2 npu# show interfaces fastethernet 0/3 npu# show interfaces fastethernet 0/4 npu# show interfaces fastethernet 0/5 npu# show interfaces fastethernet 0/6 npu# show interfaces fastethernet 0/7npu# show interfaces fastethernet 0/8 Gigabit Ethernet<interface-type> <interface-id>npu# show interfaces gigabitethernet 0/9 npu# show interfaces gigabitethernet 0/10 IP Interfaces internal-mgmt npu# show interfaces internal-mgmt external-mgmt npu# show interfaces external-mgmt bearer npu# show interfaces bearer local-mgmt npu# show interfaces local-mgmt Virtual Interfacesnpu-host npu# show interfaces npu-hostall-au npu# show interfaces all-auIMPORTANTAn error may occur if:The interface type or ID that you have specified does not exist.The IP interface does not exist for the configured connectivity and boot mode.Command Syntaxnpu# show interfaces [{[<interface-type> <interface-id>] | internal-mgmt | external-mgmt | bearer | local-mgmt | npu-host | all-au}]Privilege Level1Table 4-14: Parameters for Displaying Configuration Information for Physical, IP, and Virtual InterfacesInterface Parameters Example](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-71.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 168 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values[{[<interface-type> <interface-id>] | internal-mgmt | external-mgmt | bearer | local-mgmt | npu-host | all-au}]Indicates the type of interface (physical, IP, or virtual) for which configuration information is to be displayed. Do not specify any value for this parameter if you want to display configuration information for all physical, IP, and virtual interfaces.Optional N/A Refer Table 4-14Display Format (Physical Interfaces)<Port Number> <up/down>, line protocol is <up/down> (connected) MTU <value >bytes,<Full/half> duplex,<value> Mbps, Auto-NegotiationOctets : <value>Unicast Packets : <value>Broadcast Packets : <value>Multicast Packets : <value>Discarded Packets : <value>Error Packets : <value>Unknown Packets : <value>Octets : <value>Unicast Packets : <value>Broadcast Packets : <value>Multicast Packets : <value>Discarded Packets : <value>Error Packets : <value>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-72.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 169 System Manual4.3.3 Managing the NPU Boot ModeThe NPU boot mode refers to the mode of operation to be used for operating the NPU. You can configure the NPU to be operated in any of the following boot modes:ASN-GW mode: In this mode, the NPU implements ASN-GW functionalities, that is, it implements R3 Reference Point (RP) towards the CSN, R4 reference point toward other ASN-GWs, and R6 reference point toward AU/BSs. The R8 reference point traffic is transparently relayed between AU/BSs (intra- or inter-shelf). The ASN-GW mode operates:»With HA support, that is, the NPU implements Mobile IP services (MIP) Not supported in the current release.»Without HA support, that is, the NPU does not implement MIP servicesTransparent mode: In this mode, the NPU transparently relays R6 and R8 reference-point traffic between AU/BSs (intra- or inter-shelf).Display Format (IP Interfaces)<IP Interface Name> <up/down>, MTU <value> bytes, <value> InBytes, <value> InUnicast Packets <value> InDiscarded Packets<value> InError Packets <value> OutBytes, <value> OutUnicast Packets Display Format (Virtual Interfaces)<Virtual Interface Name> interfaceAcls attached <No. of attached ACLs>Command ModesGlobal command modeIMPORTANTThe ASN-GW mode without HA support is the default boot mode that is used when the NPU boots up for the first time.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-73.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 170 System ManualThis section describes the commands to be used for:“Configuring the Next Boot Mode” on page 170“Displaying the Current and Next Boot Mode Information” on page 1714.3.3.1 Configuring the Next Boot ModeThe next boot mode refers to the boot mode that should be used for booting up the NPU the next time it is shut down or reset. The default boot mode is the ASN-GW mode without HA support.The following are the possible boot modes for operating the NPU:ASN-GW mode without HA support (does not implement MIP services)Transparent modeTo configure the next boot mode, run the following command:npu(config)# nextbootmode {asngwStatic | transparent}NOTETo view the NPU current and next boot mode, refer to “Displaying the Current and Next Boot Mode Information” on page 171.IMPORTANTIt is recommended that you run this command to specify the boot mode to be used after the next NPU reset. If you do not specify the next boot mode, the NPU boots up using the last configured boot mode.Command Syntaxnpu(config)# nextbootmode {asngwStatic | transparent}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-74.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 171 System Manual4.3.3.2 Displaying the Current and Next Boot Mode InformationTo display the current and next boot modes, run the following command:npu# show bootmodeSyntax Description Parameter Description Presence Default ValuePossible Values{asngwStatic | transparent}Indicates the mode that is to be used for rebooting the NPU. Mandatory asngwStaticasngwStatic: 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 ModesGlobal configuration modeCommand Syntaxnpu# show bootmodePrivilege Level1Display Formatcurrent bootmode : <Current Boot Mode>next bootmode : <Configured Next Boot Mode>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-75.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 172 System Manual4.3.4 Managing the 4Motion Configuration File4Motion 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 and commissioning, the system boots up with the factory default configuration. After the system boots up, you can use the CLI to modify the values of parameters (for which default values exist), and specify values for the remaining parameters. You can also download the configuration file from an external TFTP server, and use the configuration parameters in this file to boot up the 4Motion system. In addition, you can batch-process commands.It is recommended that you make periodic backups of the configuration file. You can either manually make a backup of this file or configure the system to automatically make a daily backup. You can, at any time, restore the configuration specified in the backup file or the factory default configuration.This section describes the commands for:“Saving the Current Configuration” on page 173“Downloading the Configuration File from an External Server” on page 173“Making a Backup/Restoring the Configuration File” on page 175Command ModesGlobal command modeIMPORTANTYou can, at any time, restore factory default configuration parameters. If you have not saved configuration since the first time the system was started (after installation and commissioning), the system boots up with the factory default parameters at the next system reset.IMPORTANTIt is recommended that you periodically save changes to configuration. (The saved configuration is written to a file that resides in the NPU flash.) If you have modified any configuration parameters at runtime, it is recommended that you save configuration before resetting/shutting down 4Motion. Unsaved configuration is lost after system reset or shut down.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-76.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 173 System Manual4.3.4.1 Saving the Current ConfigurationWhen 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.Run the following command to save the current configuration:npu# writeThe next time you reset the system, it boots up with the last saved configuration.4.3.4.2 Downloading the Configuration File from an External ServerIMPORTANTYou can, at any time, revert to the factory default configuration. For more information about restoring factory default configuration, refer to Section 4.3.4.3.5. If you do not save configuration after first time start up of 4Motion, it boots up with the factory default configuration the next time the system is reset.IMPORTANTIt is recommended that you save the current configuration before shutting down or resetting the system. The last saved configuration is used during system startup. Unsaved configuration is lost after system reset/shutdown. For more information about shutting down/resetting the system, refer to Section 4.2.Command Syntaxnpu# writePrivilege Level10Command ModeGlobal command modeIMPORTANTBefore downloading the configuration file from an external server, you are required to configure the IP interfaces, internal-management, external-management, bearer, and local-management. For more information about configuring IP interfaces, refer the section, “Configuring Static Routes” on page 211.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-77.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 174 System ManualYou can download the configuration 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.Run the following command to download the configuration file from an external server:npu# configfile download tftp://<ip-address>/<filename>Reset 4Motion after you run this command. The system boots up with the downloaded configuration. To reset the system, run the following command:npu(config)# resetFor more information about resetting 4Motion, refer to Section 4.2.2.1.IMPORTANTAs soon as the system boots up with the downloaded configuration, the downloaded configuration file is deleted from the NPU flash. The system continues to operate using the downloaded configuration until the next system reset. After the system is reset, it boots up using the last saved configuration. To ensure that the downloaded configuration is used to boot up the system after reset, save the downloaded configuration using the following command:npu# writeFor more information about saving configuration, refer to Section 4.3.4.1.NOTEAn error may occur if:The file to be downloaded is not present in the appropriate path on the TFTP server.The file name that you have provided is in an invalid format. (The file to be downloaded should be a compressed zip file with the .gz extension.)Command Syntaxnpu# configfile download tftp://<ip-address>/<filename>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-78.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 175 System Manual4.3.4.3 Making a Backup/Restoring the Configuration FileYou 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. This section describes the commands for:“Making a Manual Backup of the Current Configuration” on page 176“Displaying the Status of the Manual Backup Procedure” on page 176“Making Automatic Backups of the Current Configuration” on page 177“Restoring the Configuration Defined in the Backup Configuration File” on page 178“Restoring the Factory Default Configuration” on page 179Syntax Description Parameter Description Presence Default ValuePossible Values<ip-address> Indicates the IP address of the TFTP server.Mandatory N/A Valid IP address<filename> Indicates the name of the configuration file to be downloaded using the TFTP server. The file to be downloaded should be a compressed zip file. Always suffix the file name with .gz.Mandatory N/A <filename>.gzCommand ModesGlobal command modeNOTEThe system makes a backup (automatic daily backups or manual backup) of the current configuration. The backup files are stored in the path, tftpboot\management\configuration. The naming convention used for the backup configuration files is, YYYYMMDDHHMM.cfg.gz.You can display the three most recent backup configuration files residing in the NPU flash. For details, refer to Section 4.3.4.3.6.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-79.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 176 System Manual“Displaying the Currently Stored Backup Configuration Files” on page 1794.3.4.3.1 Making a Manual Backup of the Current ConfigurationTo manually make a backup of the current configuration, run the following command:npu# manual-backupYou can, at any time, view the status of the manual backup procedure. For details, refer to Section 4.3.4.3.2.4.3.4.3.2 Displaying the Status of the Manual Backup ProcedureTo display the current status of the manual backup procedure, run the following command:npu# show manual-backup-statusIMPORTANTTo enable the system to automatically make a backup of the current configuration, everyday, refer to Section 4.3.4.3.3.Command Syntaxnpu# manual-backupCommand ModesGlobal command modeCommand Syntaxnpu# show manual-backup-statusPrivilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-80.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 177 System Manual4.3.4.3.3 Making Automatic Backups of the Current ConfigurationYou 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 4.3.4.3.1.) To enable the system to make automatic backups of the current configuration, run the following command:npu(config)# auto-backup-time <hh:mm>Specify the time in the 24-hour format. The system will automatically make a backup of the current configuration, everyday, at the time that you have specified. Display FormatThe Status of the File Backup operation is: <status-value>Where <status value> may be any of the following:Generating (1)Copying (2)Compressing (3)Compression Failure (4)Copying Failed (5)Completed (6)Command ModesGlobal command modeNOTEBy default, the system makes a daily backup of the current configuration, at 00:00 hours.IMPORTANTYou can restore the configuration from any of the backup configuration files residing in the NPU flash. For details refer to Section 4.3.4.3.4.Command Syntaxnpu(config)# auto-backup-time <hh:mm>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-81.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 178 System Manual4.3.4.3.4 Restoring the Configuration Defined in the Backup Configuration FileYou can, at any time, restore configuration from the backup configuration file. (To display a list of currently stored backup files, refer to Section 4.3.4.3.6.) Run the following command to specify the backup file to be restored:npu# restore-from-local-backup <local-restore-filename>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<hh:mm> Indicates the time at which the system should automatically create a backup of the current configuration, everyday.Mandatory 00:00 HH:MM(Enter the time in the 24-hour format)Command ModesGlobal configuration modeIMPORTANTAfter executing this command, reset the system to restore configuration from the backup configuration file. For more information about resetting the system, refer to Section 4.2.2.1.IMPORTANTIf you have stored the backup file on an external server, you can download the backup file from the external server, and reset the system to apply the configuration defined in the downloaded file. For details about downloading the configuration file from an external server, refer Section 4.3.4.2.Command Syntaxnpu# restore-from-local-backup <filename>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-82.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 179 System Manual4.3.4.3.5 Restoring the Factory Default ConfigurationYou can, at any time, run the following command to restore factory default configuration:npu# restore-factory-default4.3.4.3.6 Displaying the Currently Stored Backup Configuration FilesTo display a list of backup configuration files that are currently residing on the NPU flash, run the following command:npu# show backup-configuration-filesThe three most recent backup configuration files are displayed.Syntax Description Parameter Description Presence Default ValuePossible Values<filename> Indicates the name of the backup configuration file to be used for restoring configuration.Mandatory N/A Valid file nameCommand ModesGlobal command modeCommand Syntaxnpu# restore-factory-defaultPrivilege Level10Command ModesGlobal command modeCommand Syntaxnpu# show backup-configuration-filesPrivilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-83.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 180 System Manual4.3.5 Batch-processing of CLI CommandsYou can use the CLI to batch-process commands to be executed for configuring and monitoring 4Motion.1Ensure that the text file comprising the commands to be batch processed is present on the TFTP server to be used for downloading the batch file. 2Run the following command to download the text file and initiate batch-processing of commands specified in this file:npu# batch-run tftp://<ip-address>/<file name>After you execute this command, the file is downloaded from the TFTP server, and the commands in the file are executed sequentially. After batch-processing of all commands in this file is complete, the downloaded file is deleted from the 4Motion system.The following is a sample text file that contains a list of commands to be batch-processed:Display Format1.<file name>.gz2. <file name>.gz3. <file name>.gzCommand ModesGlobal command modeIMPORTANTBefore 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.If you want to execute a command that requires system reset, specify the save configuration and system reset commands at the end of the batch file. (For more details about saving configuration and resetting the system, refer to “Saving the Current Configuration” on page 173 and “Resetting the system” on page 133.To batch-process CLI commands:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-84.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 181 System Manual4.3.6 Configuring the CPUTo ensure optimal utilization of the NPU resources, you are required to configure the thresholds for the CPU and memory utilization for the NPU. In addition, to config terminalnextbootmode asngwStaticlimit cpu softlimit 80 hardlimit 85bearerqos rule_1 0 3 5 data 1config outer-dscp 3 vlan-priority 4 qos enableexitwriteresetCommand Syntaxnpu# batch-run tftp://<ip-address>/<file name>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ip-address> Indicates the IP address of the TFTP server to be used for batch-processing commands to be used for configuring and monitoring 4Motion.Mandatory N/A Valid IP address<file name> Indicates the configuration file to be used for batch-processing the CLI commands. Always suffix the file name with .txt.Mandatory N/A <filename>.txtCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-85.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 182 System Manualprotect the from hostile applications, you can limit the type and rate of traffic destined towards the NPU. This section describes the commands to be executed for:“Configuring CPU and Memory Utilization Thresholds for the NPU” on page 182“Configuring the Rate Limiting for the NPU” on page 1844.3.6.1 Configuring CPU and Memory Utilization Thresholds for the NPUThis section describes the commands for:“Specifying Thresholds for CPU and Memory Utilization for the NPU” on page 182“Displaying CPU and Memory Utilization Limits for the NPU” on page 1834.3.6.1.1 Specifying Thresholds for CPU and Memory Utilization for the NPUYou can use the CLI to configure the thresholds (soft and hard limits) for CPU and memory utilization for the NPU. When the soft or hard limit for either CPU or memory utilization is reached, an alarm is raised.To configure the thresholds (soft and hard limits) for CPU and memory utilization for the NPU, run the following command:npu(config)# limit {cpu | memory} ([softlimit <limit>] [hardlimit <limit>])For example, run the following command if you want to configure the soft and hard limits for CPU utilization to be 78 and 85 percent, respectively.npu(config)# limit cpu softlimit 80 hardlimit 85NOTETo display the current thresholds that are configured for CPU and memory utilization for the NPU, refer to Section 4.3.6.1.2.NOTEAn error may occur if the value of the softlimit parameter is higher than the hardlimit parameter.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-86.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 183 System Manual4.3.6.1.2 Displaying CPU and Memory Utilization Limits for the NPUTo display the configured CPU and memory utilization limits for the NPU, run the following command:npu# show resource limitsCommand Syntaxnpu(config)# limit {cpu | memory} ([softlimit <integer (1-99>] [hardlimit <integer (1-99>])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{cpu | memory} Indicates whether the threshold is to be specified for CPU or memory utilization.Mandatory N/A cpu/ memory[softlimit <integer (1-99>]Indicates the soft limit, as a percentage, for CPU/memory utilization. When this limit is reached, the system raises a Minor or Major alarm.Optional 70 (for CPU and memory utilization)1-99[hardlimit <integer (1-99>])Indicates the hard limit, as a percentage, for CPU/memory utilization. When this limit is reached, the system raises a Critical alarm.The value of this parameter should always be greater than the softlimit parameter.Optional 90 (for CPU and memory utilization)1-99Command ModesGlobal configuration modeNOTETo configure the CPU and memory utilization limits for the NPU, refer to Section 4.3.6.1.2.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-87.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 184 System Manual4.3.6.2 Configuring the Rate Limiting for the NPUThe rate limiting feature enables you to limit the type of traffic destined towards the NPU. This feature is used to protect the NPU from hostile applications or Denial of Service (DoS) attacks because packets that exceed an allowed rate are dropped and not queued to the NPU.The following are pre-defined applications for which rate limiting is already configured:File Transfer protocol (FTP)TelnetTrivial File Transfer Protocol (TFTP)SSHInternet Control Protocol Message (ICMP)Simple Network Management Protocol (SNMP)R6, R4Internet Group Management Protocol (IGMP)Extensible Authentication Protocol (EAP)Command Syntaxnpu# show resource limitsPrivilege Level1Display FormatResource softlimit hardlimitCPU <limit> <limit> Memory <limit> <limit> Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-88.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 185 System ManualAddress Resolution Protocol (ARP)You can, at any time, modify the rate limit parameters for pre-defined applications. Besides the pre-defined applications, you can also configure rate limiting for other applications.You can, at any time, view configuration information for the rate limiting feature. 1Enable the rate limiting configuration mode (refer to Section 4.3.6.2.1)2You can now execute any of the following tasks:»Modify default rate limiting configuration for pre-defined applications (refer to Section 4.3.6.2.2)»Configure rate limiting for user-defined applications (refer to Section 4.3.6.2.3)»Disable rate limiting for specific applications (refer to Section 4.3.6.2.4)You can, at any time, enable or disable rate limiting (refer to Section 4.3.6.2.5). In addition, you can also display configuration information for the rate limiting feature (refer to Section 4.3.6.2.6).NOTERate limiting for pre-defined applications is only configured for control traffic from FTP, Telnet, and TFTP applications. You need to configure rate limiting separately for data traffic from FTP, Telnet, and TFTP. For details, refer to “Configuring Rate Limiting for User-defined Applications” on page 189. IMPORTANT100 Kbps is the default rate limit that is configured for pre-defined and user-defined applications. In addition, 100 Kbps is the default rate limit that is specified for all other applications that may send packets to the NPU (but are not in the list of pre-defined or user-defined applications).If you disable rate limiting for a specific pre-defined or user-defined application, the rate limit that you have configured for all other applications will be applicable for the application (for which rate-limiting is disabled.To configure rate limiting for the NPU:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-89.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 186 System Manual4.3.6.2.1 Enabling the Rate Limiting Configuration ModeTo enable the rate limiting configuration mode, run the following command:npu(config)# rate-limit configAfter you run this command, you can:Modify default rate limiting configuration parameters for pre-defined applications (refer to Section 4.3.6.2.2)Configure rate limiting for user-defined applications (refer to Section 4.3.6.2.3)Disable rate limiting for specific applications (refer to Section 4.3.6.2.4)4.3.6.2.2 Modifying Configuration Parameters for Pre-defined ApplicationsRate limiting is configured and enabled for the following pre-defined applications:FTPTelnetTFTPSSHICMPSNMPNOTEIn addition, you can also display the number of non-conforming packets dropped by the rate limiting feature. For details, refer to Section 4.10.1.3.Command Syntaxnpu(config)# rate-limit configPrivilege Level10Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-90.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 187 System ManualR6, R4IGMPEAPARPRun the following command to modify the rate limiting configuration parameters for a pre-defined application. You can also use this command to configure rate limiting for all other applications that may send packets to the NPU. npu(config-ratelmt)# set rate-limit {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | all-others} [dstport <port_num>] <rate-Kbps>For example, run the following command to specify that NPU should listen for FTP packets on port 1024 a packet rate of 300 Kbps.npu(config-ratelmt)# set rate-limit ftp dstport 1024 300NOTETo configure user-defined applications, refer to Section 4.3.6.2.3.IMPORTANTRate limiting for pre-defined applications is only configured for control traffic from FTP, Telnet, and TFTP applications. You need to configure rate limiting seaparately for data traffic from FTP, Telnet, and TFTP applications. For details, refer to “Configuring Rate Limiting for User-defined Applications” on page 189.NOTEBy default, the NPU listens for packets from pre-defined applications on standard ports.Command Syntaxnpu(config-ratelmt)# set rate-limit {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | all-others} [dstport <port_num>] <rate-Kbps>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-91.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 188 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values{ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | all-others}Indicates the application for which the rate limiting is to be configured. Mandatory N/A ftptelnettftpsshicmpsnmpR4-R6igmpeaparpall-others: Refers to all other applications that may send packets to the NPU, and are not in the list of pre-defined or user-defined applications.[dstport <port_num>]Indicates the TCP/UDP port on which the NPU listens for packets from a pre-defined application.Optional Standard ports1-65535[rate-Kbps] Indicates the rate, in Kbps, at which a pre-defined application can send packets to the NPU.Mandatory 100 for all specific applications.1000 for all-others1-1000000](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-92.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 189 System Manual4.3.6.2.3 Configuring Rate Limiting for User-defined ApplicationsBesides the pre-defined applications (refer to Section 4.3.6.2.2), you can also configure other applications that can send packets to the NPU. Run the following command to configure rate limiting for a user-defined application. npu(config-ratelmt)# set rate-limit <user-defined-app> {[srcport <port_num>] [dstport <port_num>] [protocol <protocol_num>] [srcaddr <ip_addr>] [dstaddr <ip_addr>] [ethertype <protocol_num>]} <rate-Kbps>In the above command, it is recommended that you configure at least one of the following parameters. The more parameters you configure, the higher the granularity of the rate limiting definition for that application.L4 source port L4 destination portL3 protocol fieldSource IP addressDestination IP addressL2 protocol type fieldCommand ModesRate limiting configuration modeNOTETo display the rate limiting parameters defined for user-defined and other applications, refer to Section 4.3.6.2.6](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-93.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 190 System ManualIMPORTANTWhile configuring rate limiting for user-defined applications, remember that:Configuration for user-defined applications is applied with respect to the sequence in which you configure these values. It is recommended that you specify the more granular definitions before the less granular ones. For example, if you are creating a definition that configures the source port 200 and destination port 500, create this definition before creating a generic configuration for applications with source port 200. Otherwise, packets with source port 200 and destination port 500 will be limited according to the rate configured for source port 200.Packets are classified and identified by the hardware with respect to the depth of the fields that are configured. Specify the values of the rate limiting parameters for user-defined applications exactly as these appear in the packet header.You cannot modify rate limiting definitions for a user-defined application. To modify rate limiting configuration for a user-defined application, disable and delete that definition, and then create a new one using the command described in this section. To disable an application definition, refer to Section 4.3.6.2.4.L2 protocols cannot be defined with any of the other L4 or L3 fields mentioned above.The destination IP address that you specify should be the IP address that you have configured for the external-management, internal-management, bearer, and local-management interface.IMPORTANTAn error may occur when you run this command and:The destination port, protocol fields, or Ethernet type that you have configured for the user-defined application is identical to the destination port of the pre-defined application.Rate limiting is completely disabled for the NPU.Command Syntaxnpu(config-ratelmt)# set rate-limit <user-defined-app> {[srcport <port_num>] [dstport <port_num>] [protocol <protocol_num>] [srcaddr <ip_addr>] [dstaddr <ip_addr>] [ethertype <protocol_num>]} <rate-Kbps>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<user-defined-app>Indicates the name of the application.Mandatory N/A String (up to 20 characters)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-94.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 191 System Manual4.3.6.2.4 Disabling and Deleting Rate Limiting Configuration for an ApplicationTo disable and delete rate limiting configuration for an application, run the following command:[srcport <port_num>]Indicates the L4 source port of the user-defined application. specify the value of this parameter exactly as this field appears in the TCP/UDP header.Optional N/A 1-65535[dstport <port_num>]Indicates the L4 destination port of the user-defined application. This parameter should be specified exactly as it appears in the TCP/UDP header.Optional N/A 1-65535[protocol <protocol_num>]Indicates the L3 protocol field of the user-defined application. This parameter should be specified exactly as it appears in the IP headerOptional N/A 0-255[srcaddr <ip_addr>]Indicates the source IP address of the user-defined application.Optional N/A Valid unicast IP address[dstaddr <ip_addr>]Indicates the pre-configured destination IP address for the NPU for which rate limiting for this user-defined application is to be configured. Specify the IP address that is assigned to the external-management, internal-management, local-management or bearer interface.Optional N/A Valid unicast IP address[ethertype <protocol_num>]Indicates the Ethernet type field of the user-defined L2 protocol.Optional N/A 1536-65535[rate-Kbps] Indicates the rate, in Kbps, at which an application can send packets to the NPU.Mandatory 100 1-1000000 Command ModesRate limiting configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-95.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 192 System Manualnpu(config-ratelmt)# no rate-limit {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | <user-defined-app>}IMPORTANTWhile disabling rate limiting for user-defined applications, remember that:Rate limiting configuration specified for applications categorized as ‘all-others’ is applicable for all pre-defined/user-defined applications for which you have disabled rate limiting. (However, if you disable rate-limiting for the entire system, it is disabled completely across pre-defined, user-defined, and all other applications. For details, refer to Section 4.3.6.2.5.)After rate limiting is disabled for an application, the application traffic is identical to that of other applications (applications other than pre-defined and user defined applications.)You cannot disable rate limiting for EAP and ARP.An error may occur if you try disabling rate limiting for an application when this feature is already disabled for the entire system. For details, refer to Section 4.3.6.2.5.Command Syntaxnpu(config-ratelmt)# no rate-limit {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | <user-defined-app>}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-96.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 193 System Manual4.3.6.2.5 Enabling/Disabling the Rate Limiting for the NPUYou can disable or enable the rate limiting feature for the NPU. When this feature is disabled, rate-limiting for all applications is in the "not-in-service" state. When you enable this feature, the last saved configuration parameters for all applications (pre-defined, user-defined, and all others) is used. By default, this feature is enabled for the NPU.Syntax Description Parameter Description Presence Default ValuePossible Values{ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | <user-defined-app>}Indicates the application for which rate limiting is to be disabled. Mandatory N/A ftptelnettftpsshicmpsnmpR4-R6igmpeaparpuser-defined-app: Refers to user-defined applications for which rate limiting is to be disabled.Command ModesRate limiting configuration modeNOTECAUTIONWhen 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. To disable rate limiting for a specific user-defined and pre-defined application, refer Section 4.3.6.2.2 and Section 4.3.6.2.3.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-97.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 194 System ManualTo enable/disable the rate limiting feature, run the following command:npu(config)# set cpu rate-limit {enable | disable}4.3.6.2.6 Displaying the Rate Limiting Configuration Information for an ApplicationTo display rate limiting parameters that are configured for specific or all user-defined and pre-defined applications, run the following command:npu# show rate-limit config {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | all-others | <user-defined-app> | all}Command Syntaxnpu(config)# set cpu rate-limit {enable | disable}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{enable | disable}Indicates whether this feature should be enabled or disabled for the NPU. Mandatory N/A enabledisableCommand ModesGlobal configuration modeIMPORTANTAn error may occur if you want to run this command to display configuration information for an application for which rate limiting is disabled.Command Syntaxnpu# show rate-limit config {ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | all-others | <user-defined-app> | all}Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-98.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 195 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values{ftp | telnet | tftp | ssh | icmp | snmp | R4-R6 | igmp | eap | arp | <user-defined-app> | all}Indicates the application for which rate limiting is to be displayed. Optional N/A ftptelnettftpsshicmpsnmpR4-R6igmpeaparpuser-defined-app: Refers to user-defined applications for which rate limiting is to be displayed.all](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-99.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 196 System Manual4.3.7 Configuring QoS Marking RulesQoS marking rules refer to the classification of traffic originating from the NPU into different flows. You can then apply DiffServ Code Points (DSCP) and/or 802.1p priority bits for appropriate QoS handling of each flow. The NPU generates the following types of traffic:R4/R6 control trafficR3 control traffic such as RADIUS or MIPManagement traffic To define QoS marking for traffic generated by NPU, you are required to configure:Class-maps: Define the DSCP and/or VLAN priority bits to be applied for signaling and management traffic originating from the NPU.QoS classification rules: Classify packets into flows, based on the IP address of the host interface, transport protocol, and the source port number of the application traffic. A class-map can be associated with each flow to define Display FormatCPU Rate Limiting Status : EnabledPRE-DEFINED RATELIMIT CONFIGURATION:-----------------------------------Application DestPort Rate(Kbps) Status<Application> <Port Number> <Configured Rate> <Current Status> <Application> <Port Number> <Configured Rate> <Current Status> <Application> <Port Number> <Configured Rate> <Current Status> USER-DEFINED RATELIMIT CONFIGURATION:Application Srcport Dstport Proto SrcIPAddr DstIPAddr L2type Rate<Application> <Port Number> <Port Number> <Protocol> IP address> <IP Address> <value> <Configured Rate>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-100.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 197 System Manualseparate 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.1Create one or more class-maps (refer to Section 4.3.7.1) 2Use extended ACL 199 to configure QoS classification rules, and apply the appropriate class-map for each classifcation rule (refer to Section 4.3.7.2).3Enable the QoS marking rule to classify packets based on the QoS classifcation criteria, and apply the apprpriate class-map (refer to Section 4.3.7.3)You can, at any time, display configuration information for a particular class-map (refer to Section 4.3.7.1.6).4.3.7.1 Managing Class-mapsA class-map refers to the DSCP and/or 802.1p VLAN priority bits to be applied on host-originating traffic that match the criteria defined by the applicable QoS classification rules. Each class-map is assigned a class-identifier, which you can use to reference a class-map (while associating it with the QoS classification rule). 1Enable the QoS class-map configuration mode (refer to Section 4.3.7.1.1)2You can now:»Configure the 802.1p VLAN priority and/or DSCP for this class-map (refer to Section 4.3.7.1.2).»Delete the 802.1p VLAN priority and/or DSCP for this QoS class-map (refer to Section 4.3.7.1.3).»Terminate the QoS class-map configuration mode (refer to Section 4.3.7.1.4).IMPORTANTBy 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.To configure QoS marking rules:To configure a class-map:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-101.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 198 System ManualYou can, at any time, delete an existing class-map (refer to Section 4.3.7.1.5) or view the configuration information for an existing class-map (refer to Section 4.3.7.1.6).4.3.7.1.1 Enabling the QoS Class-map Configuration Mode/ Creating a New Class MapTo specify the 802.1p VLAN priority and/or DSCP values for a class-map, first enable the QoS class-map configuration mode. Run the following command to enable the QoS class-map configuration mode. You can use this command to create a new QoS class-mapnpu(config)# class-map <class-map-number(1-65535)>If you run the above command to create a new QoS class-map, the configuration mode for this QoS class-map is automatically enabled.By default, class-maps 1-8 are pre-configured. Refer to Table 4-15 for details on these class-maps and the QoS classification rules to which they are associated.After you enable the QoS class-map configuration mode, you can:Configure the 802.1p VLAN priority and/or DSCP for this class-map (refer to Section 4.3.7.1.2).Delete the 802.1p VLAN priority and/or DSCP for this QoS class-map (refer to Section 4.3.7.1.3).Terminate the QoS class-map configuration mode (refer to Section 4.3.7.1.4).IMPORTANTIf you want to modify the 802.1p VLAN priority and/or DSCP values for a class-map that is already associated with a QoS classification rule, first disable the QoS classification rule. For more information about disabling QoS classification rules, refer to Section 4.3.7.3.NOTEThe QoS class-map number is used to reference the QoS class-map that you want to associate with a QoS classification rule, which defines the classification rule to be applied for host-originating traffic. For more information about creating QoS classification rules, refer Section 4.3.7.2.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-102.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 199 System Manual4.3.7.1.2 Specifying 802.1p VLAN priority and/or DSCP for a Class-mapAfter enabling the QoS class-map configuration mode, you can configure one or both of the following values for this QoS class-map:DSCP value in the IPv4 packet header to indicate a desired service.802.1p VLAN priority in the VLAN header of the packet.Run the following command to configure the 802.1p VLAN priority and/or DSCP: IMPORTANTAn 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 Syntaxnpu(config)# class-map <class-map-number(1-65535)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<class-map-number(1-65535)>Indicates the identifier of the QoS class-map for which the QoS class-map configuration mode is to be enabled.Mandatory N/A 1-65535Command ModesGlobal configuration modeIMPORTANTIf you are modifying the 802.1p VLAN priority and/or DSCP for a class-map that is associated with a QoS classification rule, first disable the QoS classification rules for that ACL. For details, refer to Section 4.3.7.3.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-103.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 200 System Manualnpu(config-cmap)# set {[cos <new-cos(0-7)>] [ip dscp <new-dscp(0-63)>]}4.3.7.1.3 Deleting 802.1p and/or DSCP Values from a Class-mapRun the following command to delete the 802.1p VLAN priority and/or DSCP for this class-map.npu(config-cmap)# no {[cos <new-cos(0-7)>] [ip dscp <new-dscp(0-63)>]}Command Syntaxnpu(config-cmap)# set {[cos <new-cos(0-7)>] [ip dscp <new-dscp(0-63)>]}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[cos <new-cos(0-7)>]Indicates the 802.1p VLAN priority value to be applied for this class-map.Optional N/A 0-7 where 0 is the lowest and 7 is the highest[ip dscp <new-dscp(0-63)>]Indicates the DSCP value to be applied for this class-map.Optional N/A 0-63Command ModesClass-map configuration modeIMPORTANTIf you are deleting the 802.1p VLAN priority and/or DSCP for a class-map that is associated with a QoS classification rule, first disable the QoS classification rules for that ACL. For details, refer to Section 4.3.7.3.IMPORTANTAn error may occur if the 802.1p or DSCP that you have specified do not exist for this class-map.Command Syntaxnpu(config-cmap)# no {[cos <new-cos(0-7)>] [ip dscp <new-dscp(0-63)>]}](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-104.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 201 System Manual4.3.7.1.4 Terminating the QoS Class-map Configuration ModeTo terminate the QoS class-map configuration mode, run the following command:npu(config-cmap)# exit4.3.7.1.5 Deleting a QoS Class-mapRun the following command to delete an existing QoS class-map:npu(config)# no class-map <class-map-number(1-65535)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[cos <new-cos(0-7)>]Indicates the 802.1p VLAN priority to be deleted for this class-map.Optional N/A 0-7[ip dscp <new-dscp(0-63)>]Indicates the DSCP to be deleted for this class-map.Optional N/A 0-63Command ModesQoS class-map configuration modeCommand Syntaxnpu(config-cmap)# exitPrivilege Level10Command ModesQoS class-map configuration modeIMPORTANTAn error may occur if you specify a class-map number that does not exist or is not within the range, 1-65535.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-105.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 202 System Manual4.3.7.1.6 Displaying Configuration Information for a Class-mapRun the following command to view the configuration information for a class-map:npu# show class-map [<class-map-num(1-65535)>]Specify the class-map number if you want to view configuration information for a specific class-map. If you do not specify the class-map number, configuration information for all class-maps is displayed.Command Syntaxnpu(config)# no class-map <class-map-number(1-65535)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<class-map-number(1-65535)>Indicates the identifier of the QoS class-map number to be deleted.Mandatory N/A 1-65535Command ModesGlobal configuration modeIMPORTANTAn error may occur if you specify a class-map number that does not exist or is not within the range, 1-65535.Command Syntaxnpu# show class-map [<class-map-num(1-65535)>]Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-106.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 203 System Manual4.3.7.2 Managing QoS Classification RulesQoS classification rules classify packets into flows, based on the following parameters:IP address of the host originating the traffic (the IP address assigned to the bearer, internal-management or external-management interface)Layer 3 protocol indicating either TCP or UDPLayer 4-source port for the application that needs to be marked (for example, FTP, Telnet, SNMP, MIP, or RADIUS)A class-map can be associated with each flow to define separate DSCP and/or VLAN priority bits for QoS handling of each flow. 1Enable the ACL configuration mode for ACL 199 (refer to Section 4.3.7.2.1).Syntax Description Parameter Description Presence Default ValuePossible Values[<class-map-num(1-65535)>]Indicates the identifier of the class-map for which configuration information is to be displayed. Do not specify a value for this parameter if you want to view the configuration information for all class-maps.Optional N/A 1-65535Display Format (for each class-map if requested for all class-maps)Class map <class map number>----------------------------------------------CoS Value : <value>DSCP Value : <value>Command ModesGlobal command modeTo configure a QoS classification rule:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-107.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 204 System Manual2You can now:»Configure one or more QoS classification rules (refer to Section 4.3.7.2.2)»Delete one or more QoS classification rules (refer to Section 4.3.7.2.3)»Terminate the ACL configuration mode (refer to Section 4.3.7.2.4)You can, at any time, enable/disable QoS marking (refer to Section 4.3.7.3) or view the configuration information for ACL 199 (refer to Section 4.3.7.4).4.3.7.2.1 Enabling the ACL Configuration Mode for ACL 199To configure QoS classification rules for host-originating traffic, first enable the extended ACL 199 configuration mode.Run the following command to enable the extended ACL configuration mode for ACL 199. npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [name<string>]After you enable the ACL 199 configuration mode, you can one or several QoS classification rules, and associate them with the appropriate class-maps.IMPORTANTQoS classification rules can be associated only with ACL 199.IMPORTANTQoS classification rules can be added only to extended ACL 199Command Syntaxnpu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [name <string>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-108.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 205 System Manual4.3.7.2.2 Configuring a QoS Classification RuleYou can configure the QoS classification rules for the ACL with respect the following parameters:Source IP address for the host-originating application trafficApplication protocol (TCP or UDP)L4 source port of the application trafficQoS class-map identifier By default, there are 8 pre-configured QoS classification rules associated with the 8 pre-configured QoS class-maps:Syntax Description Parameter Description Presence Default ValuePossible Valuesextended <access-list-number (100-199)>Indicates the identifier of the extended ACL for which the ACL configuration mode is to be enabled. You must specify 199 to enable configuration of QoS classification rules.Mandatory N/A 199[name <string>]Indicates the name of the ACL for which the ACL configuration mode is to be enabled. Note: If you do not specify the ACL name, the ACL number is used as the default ACL name.Optional N/A String (upto 20 characters)Command ModesGlobal configuration modeTable 4-15: Pre-Configured QoS Classification Rules and Class-MapsIP Interface Type of Traffic Protocol Source Port Class Map DSCP 802.1p Bearer RADIUS UDP 1812 1 7 7](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-109.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 206 System ManualAfter configuring QoS classification rules for this ACL, enable QoS marking for this ACL. By default, QoS marking is disabled. For details, refer to Section 4.3.7.3.Run the following command to configure a QoS classification rule for this ACL:npu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>}When you execute this command, a new QoS classification rule is added to the ACL for which the configuration mode is enabled. Bearer MobileIP-Agent UDP 434 2 7 7Bearer WiMAX ASN Control Plane ProtocolUDP 2231 3 7 7Internal-Management OBSAI message exchange between NPU and AUUDP 10009 4 0 0Internal-Management Trivial File Transfer ProtocolUDP 69 5 0 0External-Management Telnet TCP 23 6 0 0External-Management SSH Remote Login ProtocolTCP 22 7 0 0External-Management SNMP UDP 161 8 0 0IMPORTANTAn error may occur if:You have specified a source port that is not within the range, 1-65535.The host IP address or class-map identifier that you have specified do not exist.Command Syntaxnpu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>}Privilege Level10Table 4-15: Pre-Configured QoS Classification Rules and Class-MapsIP Interface Type of Traffic Protocol Source Port Class Map DSCP 802.1p](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-110.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 207 System Manual4.3.7.2.3 Deleting a QoS Classification RuleTo delete a QoS classification rule for an ACL, run the following command:npu(config-ext-nacl)# no qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>}Syntax Description Parameter Description Presence Default ValuePossible Values{host <src-ip-address>}Indicates the IP address of the host interface that generates the traffic for which this classification rule is to be configured. Specify the IP address that you have assigned to the internal-management, external-management or bearer IP interface.Mandatory N/A Valid IP address (assigned to the internal-management, external-management or bearer IP interface){tcp | udp} Indicates the transport protocol.Mandatory N/A tcpudpsrcport <short (1-65535)>Indicates the source port number of the application traffic for which this QoS classification rule is to be applied.Mandatory N/A 1-65535qosclassifier <class-map-number (1-65535)>Indicates the identifier of the QoS class-map to be associated with this classification rule. For more information about configuring class-maps, refer Section 4.3.7.1.Mandatory N/A 1-65535Command ModesExtended ACL configuration modeIMPORTANTYou can delete a QoS classification rule only if the associated ACL is INACTIVE. For more information, refer Section 4.3.9.3.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-111.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 208 System ManualWhen you execute this command, the QoS classification rule is deleted from the ACL. IMPORTANTAn error may occur if you specify a combination of parameters that do not match any of the existing QoS classification rules.:Command Syntaxnpu(config-ext-nacl)# no qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[host <src-ip-address>]Indicates the IP address of the host interface that generates the traffic for which this classification rule is to be deleted.Mandatory N/A Valid IP address (assigned to the internal-management, external-management or bearer IP interface){tcp | udp} Indicates the transport protocol.Mandatory N/A tcpudpsrcport <short (1-65535)>Indicates the source port number of the application traffic for which this QoS classification rule is to be deleted.Mandatory N/A 1-65535qosclassifier <class-map-number (1-65535)>Indicates the identifier of the QoS class-map associated with the classification rule to be deleted. For more information about class-maps, refer Section 4.3.7.1.Mandatory N/A 1-65535](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-112.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 209 System Manual4.3.7.2.4 Terminating the ACL Configuration ModeTo terminate the ACL configuration mode, run the following command:npu(config-ext-nacl) # exit4.3.7.3 Enabling/Disabling QoS Marking for ACL 199You can enable/disable the QoS marking for the ACL. The class-map is applied on traffic matching a QoS classification rule only after you enable the QoS marking for the ACL).Run the following command to enable/disable the QoS marking for the specified ACL:npu(config)# set qos {enable | disable} 199 Command ModesExtended ACL configuration modeCommand Syntaxnpu(config-ext-nacl) # exitPrivilege Level10Command ModesExtended ACL configuration modeNOTEIf you want to modify a QoS class-map, first disable the QoS marking rules for the associated ACL. By default, QoS marking is disabled for the ACL. Command Syntaxnpu(config)# set qos {enable | disable} 199Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-113.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 210 System Manual4.3.7.4 Displaying ACL 199 Configuration InformationRun the following command to display the configuration information for ACL 199:npu# show access-lists [{199 | <access-list-199-name}]Syntax Description Parameter Description Presence Default ValuePossible Values{enable | disable}Indicates whether QoS marking should be enabled or disabled for a specific ACL.Mandatory disable enabledisable199 Indicates the identifier of the ACL for which the QoS marking is to be activated. You musr specify 199.Mandatory N/A 199Command ModesGlobal configuration modeIMPORTANTAn error may occur if the ACL name you have specified does not exist.Command Syntaxnpu# show access-lists [199| <access-list-199-name}]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[199 | <access-list-199-name}]To view configuration information for ACL 199, specify 199 or the name configured for this ACL.Mandatory for viewing information for ACL 199.N/A 199String; the name configured for ACL 199.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-114.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 211 System Manual4.3.8 Configuring Static RoutesUsing the CLI, you can configure the static routes for traffic originating from the NPU. For each static route, you can configure the destination IP address, address mask, and the next hop IP address. The following are the types of traffic originating from the NPU:R4/R6 control trafficR3 control traffic such as RADIUS or MIPNMS traffic This section describes the commands for:“Adding a Static Route” on page 212“Deleting a Static Route” on page 213Display Format (Standard)Extended IP Access List 199Access List Name(Alias) : 199 Interface List : NIL Status : <Active|Inactive> Admin-Status : <Up|Down> Filter Protocol Type : <UDP|TCP> Source IP address : <IP address> Filter Source Port : <value> Rule Action : QoS Marking QoS Classifier ID : <value> Marking rule status : <ACTIVE|INACTIVE>...............Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-115.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 212 System Manual“Displaying the IP Routing Table” on page 214There are four automatically created static route with the IP addresses of the directly connected Bearer, External Management, Local Management and Internal Management interfaces (the IP address of the Internal Management interface is set to 10.0.0.254. Note that availability of certain interfaces depend on the connectivity mode). These routes cannot be modified or deleted.In addition, the “Any Destination” entry with Destination 0.0.0.0 and Mask 0.0.0.0 must be created during initial setup and should not be deleted. The Next Hop IP address of this route must be in the same subnet with the interface used for remote management.4.3.8.1 Adding a Static RouteTo add a static route, run the following command:npu(config)# ip route <ip_address> <ip_mask> <ip_nexthop>For example, run the following command to add an entry for a static route with the destination IP address, 11.0.0.2, and the address mask, 255.255.255.255, and next-hop IP address, 192.168.10.1.npu(config)# ip route 11.0.0.2 255.255.255.255 192.168.10.1NOTERefer to Section 4.3.8.3 to display the IP routing table.IMPORTANTAn error may occur if:The IP address, address mask or the next-hop IP address are invalid.A route with the parameters that you have specified already exists. The IP address that you have specified is being used for another interface.The next-hop IP address that you have specified is either unreachable or is down.Command Syntaxnpu(config)# ip route <ip_address> <ip_mask> <ip_nexthop>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-116.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 213 System Manual4.3.8.2 Deleting a Static RouteTo delete a static route, run the following command:npu(config)# no ip route <ip_address> <ip_mask> <ip_nexthop>For example, run the following command to delete an entry for a static route with the destination IP address, 11.0.0.2, and the address mask, 255.255.255.255, and next-hop IP address, 192.168.10.1.npu(config)# no ip route 11.0.0.2 255.255.255.255 192.168.10.1Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ip_address> Indicates the destination host or network IP address, for which the route is to be added. Mandatory N/A Valid IP address<ip_mask> Indicates the address mask for the static route to be added.Mandatory N/A Valid address mask<ip_nexthop> Indicates the next hop IP address, for the route to be added.Mandatory N/A Valid IP addressCommand ModesGlobal configuration modeIMPORTANTAn error may occur if a route matching the specified parameters does not exist.Command Syntaxnpu(config)# no ip route <ip_address> <ip_mask> <ip_nexthop>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-117.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 214 System Manual4.3.8.3 Displaying the IP Routing TableTo display the IP routing table, run the following command:npu# show ip routeSyntax Description Parameter Description Presence Default ValuePossible Values<ip_address> Indicates the destination host or network IP address, for which the route is to be deleted.Mandatory N/A Valid IP address<ip_mask> Indicates the address mask for the static route to be deleted.Mandatory N/A Valid address mask<ip_nexthop> Indicates the next hop IP address, for the route to be deleted.Mandatory N/A Valid IP addressCommand ModesGlobal configuration modeCommand Syntaxnpu(config)# show ip routePrivilege Level1Display Format<IP address/mask> is directly connected<IP address/mask> is directly connected<IP address/mask> is directly connected<IP address/mask> via <Next-hop IP address><IP address/mask> via <Next-hop IP address> via <Next-hop IP address><IP address/mask> via <Next-hop IP address><IP address/mask> via <Next-hop IP address>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-118.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 215 System Manual4.3.9 Configuring ACLsACLs are applied on traffic received from the DATA, MGMT or CSCD ports, and destined towards the following virtual interfaces:AUsNPUBy default, all traffic destined towards the AUs or NPU is denied. To enable initial access to the device, the factory default configuration includes a standard ACL (ACL 1) with a pre-configured rule permitting unrestricted access to the Local-Management interface. You can use the CLI to configure ACLs for permitting or denying traffic destined towards the NPU or AUs.You can create the following types of ACLs:Standard: Allows you to filter traffic based on the source and destination IP addresses.Extended: Allows you to filter traffic based on the source and destination IP addresses, source and destination ports, and protocol.You can create the following types of rules for an ACL:Permit: Indicates that traffic matching the filter criteria is allowed to reach the NPU or AUs.Deny: Indicates that traffic matching the filter criteria is dropped, and not allowed to reach the NPU or AUs.You can configure multiple rules for each ACL; the priority for these rules is applied with respect to the sequence in which these rules are configured. After Command ModesGlobal command modeIMPORTANTYou can use extended ACL 199 to configure QoS classification rules for classifying traffic originating from the NPU into different flows. For details, refer “Configuring QoS Marking Rules” on page 196).](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-119.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 216 System Manualyou configure an ACL, you can attach the ACL to either the NPU or the AUs or both NPU and AUs. All ACLs are either in the ACTIVE or INACTIVE state. The ACTIVE state indicates that the ACL is attached to one or more interfaces; the INACTIVE state indicates that the ACL is not attached to any interface.This section describes the commands for:“Configuring an ACL in the Standard/Extended Mode” on page 216“Deleting an ACL” on page 240“Attaching/De-attaching ACLs to/from an Interface” on page 241“Displaying ACL Configuration Information” on page 2444.3.9.1 Configuring an ACL in the Standard/Extended ModeYou can configure an ACL in either of the following modes:Standard mode: Use this mode if you want to create Permit or Deny rules for traffic based on source and destination IP addresses. Extended mode: Use this mode if you want to create Permit or Deny rules with based on source and destination IP addresses, source and destination ports, protocol.1Enable the standard or extended ACL configuration mode (refer Section 4.3.9.1.1).2After you enter the ACL configuration mode, you can:»Configure ACLs in the standard mode (refer Section 4.3.9.1.2).»Configure ACLs in the extended mode (refer Section 4.3.9.1.3).3Terminate the ACL configuration mode (refer Section 4.3.9.1.4).IMPORTANTBy default, all ACLs are INACTIVE, and are ACTIVE only after you attach the ACL to an interface to make ACTIVE.That is, all traffic destined to the NPU or AUs is denied until you configure ACLs for permitting specific connections. To configure an ACL:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-120.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 217 System Manual4After you have configured the ACL, you can attach the ACL with the AUs or NPU refer Section 4.3.9.3.4.3.9.1.1 Enable the ACL Configuration Mode/Creating an ACLTo configure an ACL, first enable either of the following ACL configuration modes: StandardExtendedTo apply this ACL to traffic destined towards the AUs or the NPU, you are required to activate this ACL. (for details refer Section 4.3.9.3). Run the following command to enable the ACL configuration mode. You can also use this command to create a new ACL.npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>}[name<string>]When you run this command, the ACL configuration mode for the newly-created ACL is automatically enabled. If the name is not specified when creating a new ACL, the default name will be the specified ACL number.For example, run the following command to create ACL 22 in the standard mode:npu(config)# ip access-list standard 22Standard ACL 22 will be created with the default name 22.For example, run the following command to create ACL 111 in the extended mode, with the name ACL-111:npu(config)# ip access-list extended 111 ACL-111After you create an ACL or enable the ACL configuration mode, you canConfigure the ACL in the standard mode (refer Section 4.3.9.1.2)IMPORTANTACL 199 is the default extended ACL that is pre-configured in the system, and is not attached to any interface, that is, it is INACTIVE. However, ACL 199 is reserved for QoS classification rules. You cannot configure Permit/Deny rules for ACL 199.To view the default configuration information for ACL 199, you can run the following command:npu# show access-lists 199For details on using ACL 199 refer to Section 4.3.7.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-121.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 218 System ManualConfiguring the ACL in the extended mode (refer Section 4.3.9.1.3)IMPORTANTAn error may occur if:·You specify an invalid ACL number. The ACL number should be between 1 and 99 in the standard mode, and between 100 and 199 in the extended mode.The ACL name you have specified is already used for another ACL or is more than 20 characters.Command Syntaxnpu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>}[name<string>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesstandard <access-list-number (1-99)> | extended <access-list-number (100-199)>Denotes the number of the standard or extended ACL that is to be created or for which the ACL configuration mode is to be enabled. If you are creating a new ACL, the ACL configuration mode is automatically enabled when you execute this command.Note: ACL 199 is reserved for QoS classification rules and cannot be used for creating Permit/Deny rules.Mandatory N/A standard 1-99extended (100-198)[name<string>] Indicates the name of the ACL to be created or for which the ACL configuration mode is to be enabled. Optional ACL nameString (upto 20 characters)Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-122.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 219 System Manual4.3.9.1.2 Configuring ACLs in the Standard ModeAfter you have enabled the standard ACL configuration mode, you can create or delete the Permit/Deny rules for forwarding traffic from/to a particular source/destination IP address.To enable initial access to the NPU, the Standard ACL 1 is available by default, with a Permit rule allowing unrestricted access to the Local Management interface (Destination IP Address = 172.31.0.1, Source IP Address = Any).This section describes the commands for:“Creating a Permit/Deny Rule (Standard Mode)” on page 219“Deleting a Permit/Deny Rule (Standard Mode)” on page 2214.3.9.1.2.1 Creating a Permit/Deny Rule (Standard Mode)Run the following commands to create the Permit/Deny rules for forwarding traffic from/to a particular source/destination IP address:npu(config-std-nacl)# permit {any | host <src-ip-address> | <network-src-ip> <mask>} [{any | host <dest-ip-address> | <network-dest-ip> <mask>}]npu(config-std-nacl)# deny {any | host <src-ip-address> | <network-src-ip> <mask>} [{any | host <dest-ip-address> | <network-dest-ip> <mask>}] The following table lists the parameters and their descriptions in these commands.IMPORTANTYou cannot create Permit or Deny rules for an ACL that is associated with a Qos marking rule. You can either associate QoS marking rules or permit/deny rules with an ACL.IMPORTANTAfter you have configured the rules to be applied on an ACL, you can attach the ACL to the NPU or AUs. The ACL enables filtering of traffic destined to these interfaces. For more information, refer to Section 4.3.9.3.IMPORTANTIn the above commands, it is mandatory to specify the source IP address for which the Permit/Deny rule is to be created. If you do not specify the destination IP address/subnet mask, by default, traffic to all destination IP addresses configured for the NPU is permitted/denied.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-123.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 220 System ManualTable 4-16: Parameters for Configuring Permit/Deny Rules in the Standard ACL ModeParameter Description ExampleSource IP any Indicates that incoming traffic from any source IP address is permitted or denied.npu(config-std-nacl)# permit anynpu(config-std-nacl)# deny anyhost <src-ip-address>Indicates that incoming traffic from a specific source IP address is permitted or denied. npu(config-std-nacl)# permit host 1.1.1.1npu(config-std-nacl)# deny host 1.1.1.1<network-src-ip> <mask>Indicates that incoming traffic is to be permitted or denied for a particular subnet.npu(config-std-nacl)# permit 1.1.1.0 255.255.255.0npu(config-std-nacl)# deny 1.1.1.0 255.255.255.0Destination IP addressany Indicates that traffic destined to all NPU IP addresses is permitted or denied.npu(config-std-nacl)# permit host 1.1.1.1 anynpu(config-std-nacl)# deny host 1.1.1.1 anyhost <src-ip-address>Indicates that traffic destined to a specific destination IP address is permitted or denied. npu(config-std-nacl)# permit any host 1.1.1.1npu(config-std-nacl)# deny any host 1.1.1.1<network-src-ip> <mask>Indicates that traffic destined to a particular subnet is to be permitted or denied.npu(config-std-nacl)# permit any 1.1.1.0 255.255.255.0npu(config-std-nacl)# deny any 1.1.1.0 255.255.255.0Command Syntaxnpu(config-std-nacl)# permit { any | host <src-ip-address> | <network-src-ip> <mask> } [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ]npu(config-std-nacl)# deny { any | host <src-ip-address> | <network-src-ip> <mask> } [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-124.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 221 System Manual4.3.9.1.2.2 Deleting a Permit/Deny Rule (Standard Mode)Run the following commands to delete the Permit/Deny rule for incoming traffic from/to a specific IP address/subnet.npu(config-std-nacl)# no permit {any | host <src-ip-address> | <network-src-ip> <mask>} [{any | host <dest-ip-address> | <network-dest-ip> <mask>}]npu(config-std-nacl)# no deny {any | host <src-ip-address> | <network-src-ip> <mask>} [{any | host <dest-ip-address> | <network-dest-ip> <mask>}] Syntax Description Parameter Description Presence Default ValuePossible Values{ any | host <src-ip-address> | <network-src-ip> <mask> }Indicates the source IP address/subnet for which incoming traffic is permitted/denied.Mandatory N/A For details, refer Table 4-16 [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ]Indicates the destination IP address/subnet for which traffic is permitted/denied Optional any For details, refer Table 4-16Command ModesStandard ACL configuration modeCommand Syntaxnpu(config-std-nacl)# no permit { any | host <src-ip-address> | <network-src-ip> <mask> } [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ]npu(config-std-nacl)# no deny { any | host <src-ip-address> | <network-src-ip> <mask> } [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ] Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-125.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 222 System Manual4.3.9.1.3 Configuring ACLs in the Extended ModeAfter you have enabled the extended ACL configuration mode, you can create Permit/Deny rules based on source/destination IP address, protocol and source/destination port numbers.This section describes the commands to be used for:“Configuring Permit/Deny Rules from/to a Specific Protocol and Source/Destination IP Addresses” on page 223“Configuring Permit/Deny Rules for TCP/UDP Traffic” on page 227“Configuring Permit/Deny Rules for ICMP Traffic” on page 236Syntax Description Parameter Description Presence Default ValuePossible Values{ any | host <src-ip-address> | <network-src-ip> <mask> }Indicates the source IP address/subnet for which the Permit/Deny rule is to be deleted.Mandatory N/A For details, refer Table 4-16 [ { any | host <dest-ip-address> | <network-dest-ip> <mask> } ]Indicates the destination IP address/subnet for which the Permit/Deny rule is to be deleted.Optional any For details, refer Table 4-16Command ModesStandard ACL configuration modeIMPORTANTYou cannot create Permit or Deny rules for an ACL that is associated with a Qos marking rule. You can either associate QoS marking rules or permit/deny rules with an ACL.IMPORTANTAfter you have configured the rules to be applied on an ACL, you can attach the ACL to the NPU or AUs. The ACL enables filtering of traffic destined to these interfaces. For more information, refer to Section 4.3.9.3.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-126.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 223 System Manual4.3.9.1.3.1 Configuring Permit/Deny Rules from/to a Specific Protocol and Source/Destination IP AddressesAfter you have created an ACL, you can configure Permit/Deny rules to be applied for traffic from/to a particular source/destination IP address/subnet, with respect to a specific protocol. This section describes the commands to be used for:“Creating a Permit/Deny Rule for Specific Protocols/IP Addresses (Extended Mode)” on page 223“Deleting a Permit/Deny Rule for Specific Protocols/IP Addresses (Extended Mode)” on page 2264.3.9.1.3.1.1Creating a Permit/Deny Rule for Specific Protocols/IP Addresses (Extended Mode)You can create the Permit or Deny rule for traffic from/to a source/ destination IP address/subnet with respect to the following protocols:IPOSPFProtocol Independent Multicast (PIM)Any other protocolRun the following commands to create the Permit/Deny rule for traffic from and to a specific IP address/subnet for a particular protocol:npu(config-ext-nacl)# permit {ip | ospf | pim | <protocol-type (1-255)>} {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}npu(config-ext-nacl)# deny {ip | ospf | pim | <protocol-type (1-255)>} {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}IMPORTANTYou cannot configure Permit or Deny rules for an ACL that is associated with a Qos marking rule. You can either associate QoS marking rules or permit/deny rules with an ACL.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-127.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 224 System ManualIn the above commands, it is mandatory to specify the protocol and source IP address for which the Permit/Deny rule is to be created. If you do not specify the destination IP address/subnet mask, by default, traffic to all destination IP addresses is permitted/denied.The following table lists the parameters and their descriptions in these commands:Table 4-17: Parameters for Configuring Permit/Deny Rules for Traffic from/to Specific IP AddressesParameter Description ExampleProtocol ip Indicates that the Permit/Deny rule to be created is to be applied for the IP-in-IP packets.npu(config-ext-nacl)# permit ip anyospf Indicates that the Permit/Deny rule to be created is to be applied to OSPF packets.npu(config-ext-nacl)# permit ospf anypim Indicates that the Permit/Deny rule to be created is to be applied to the PIM packets.npu(config-ext-nacl)# permit pim any<protocol-type (1-255)>Indicates that the Permit/Deny rule to be created is to be applied to traffic from/to any protocol (other than IP, OSPF, PIM). Use standard IANA values to specify the values of these protocolsnpu(config-ext-nacl)# permit 11 anySource IP addressany Indicates that incoming traffic from any source IP address is permitted or denied.npu(config-std-nacl)# permit ip anynpu(config-std-nacl)# deny ip anyhost <src-ip-address>Indicates that incoming traffic from a specific source IP address is permitted or denied.npu(config-std-nacl)# permit ip host 1.1.1.1npu(config-std-nacl)# deny ip host 1.1.1.1<network-src-ip> <mask>Indicates that incoming traffic is to be permitted or denied for a particular source IP address and subnet mask.npu(config-std-nacl)# permit ip 1.1.1.0 255.255.255.0npu(config-std-nacl)# deny ip 1.1.1.0 255.255.255.0](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-128.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 225 System ManualDestination IP addressany Indicates that traffic to any destination IP address is permitted or denied. any is the default destination IP address. npu(config-std-nacl)# permit ip host 1.1.1.1 anynpu(config-std-nacl)# deny ip host 1.1.1.1 anyhost <dst-ip-address>Indicates that traffic destined to a specific destination IP address is permitted or denied. npu(config-std-nacl)# permit ip any host 1.1.1.1npu(config-std-nacl)# deny ip any host 1.1.1.1<network-dst-ip> <mask>Indicates that traffic destined to a particular subnet is to be permitted or denied.npu(config-std-nacl)# permit ip any 1.1.1.0 255.255.255.0npu(config-std-nacl)# deny ip any 1.1.1.0 255.255.255.0Command Syntaxnpu(config-ext-nacl)# permit { ip | ospf | pim | <protocol-type (1-255)>} { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-addresq> | <dest-ip-address> <mask> }npu(config-ext-nacl)# deny { ip | ospf | pim | <protocol-type (1-255)>} { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-addresq> | <dest-ip-address> <mask> }Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{ ip | ospf | pim | <protocol-type (1-255)>}Indicates the type of protocol for which incoming traffic is permitted. Mandatory N/A For details, refer Table 4-17{ any | host <src-ip-address> | <src-ip-address> <mask> }Indicates the source IP address/subnet for which incoming traffic is permitted/denied.Mandatory N/A For details, refer Table 4-17Table 4-17: Parameters for Configuring Permit/Deny Rules for Traffic from/to Specific IP AddressesParameter Description Example](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-129.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 226 System Manual4.3.9.1.3.1.2Deleting a Permit/Deny Rule for Specific Protocols/IP Addresses (Extended Mode)Run the following commands to delete the Permit/Deny rule for traffic from to a specific IP address/subnet for a particular protocol:npu(config-ext-nacl)# no permit {ip | ospf | pim | <protocol-type (1-255)>} {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}npu(config-ext-nacl)# no deny {ip | ospf | pim | <protocol-type (1-255)>} {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}{ any | host <dest-ip-addresq> | <dest-ip-address> <mask> }Indicates the destination IP address/subnet for which traffic is permitted/denied Optional any For details, refer Table 4-17Command ModesExtended ACL configuration modeCommand Syntaxnpu(config-ext-nacl)# no permit { ip | ospf | pim | <protocol-type (1-255)>} { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-addresq> | <dest-ip-address> <mask> }npu(config-ext-nacl)# no deny { ip | ospf | pim | <protocol-type (1-255)>} { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-addresq> | <dest-ip-address> <mask> }Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{ ip | ospf | pim | <protocol-type (1-255)>}Indicates the type of protocol for which the Permit/Deny rule is to be deleted. Mandatory N/A For details, refer Table 4-17](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-130.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 227 System Manual4.3.9.1.3.2 Configuring Permit/Deny Rules for TCP/UDP TrafficAfter you have created an ACL, you can configure Permit/Deny rules for TCP and UDP traffic from/to specific source and destination IP address and port. This section describes the commands to be used for:“Creating a Permit/Deny Rule for TCP/UDP Traffic (Extended Mode)” on page 227“Deleting a Permit/Deny Rule for TCP/UDP Traffic (Extended Mode)” on page 2334.3.9.1.3.2.1Creating a Permit/Deny Rule for TCP/UDP Traffic (Extended Mode)Run the following commands to specify the Permit rule for TCP/UDP traffic from/to a specific source/destination IP address/port:npu(config-ext-nacl)# permit tcp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]{ any | host <src-ip-address> | <src-ip-address> <mask> }Indicates the source IP address/subnet for which the Permit/Deny rule is to be deleted.Mandatory N/A For details, refer Table 4-17{ any | host <dest-ip-addresq> | <dest-ip-address> <mask> }Indicates the destination IP address/subnet for which the Permit/Deny rule is to be deleted.Optional any For details, refer Table 4-17Command ModesExtended ACL configuration modeIMPORTANTYou cannot configure Permit or Deny rules for an ACL that is associated with a Qos marking rule. You can either associate QoS marking rules or permit/deny rules with an ACL.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-131.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 228 System Manualnpu(config-ext-nacl)# permit udp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Run the following commands to specify the Deny rule for TCP/UDP traffic from/to a specific source/destination IP address/port:npu(config-ext-nacl)# deny tcp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]npu(config-ext-nacl)# deny udp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]In the above commands, it is mandatory to specify the source and destination IP address for which the Permit/Deny rule is to be created.The following table lists the parameters and their descriptions in these commands:IMPORTANTTo increase the granularity of the Permit/Deny rule you are creating, specify the source and destination port numbers for the source and destination IP addresses.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-132.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 229 System ManualTable 4-18: Parameters for Configuring Permit/Deny Rules for TCP/UDP TrafficParameter Description ExampleSource IP addressany Indicates that incoming TCP/UDP traffic from any source IP address is permitted or denied.npu(config-ext-nacl)# permit tcp any anynpu(config-ext-nacl)# deny udp any host <src-ip-address>Indicates that incoming TCP/UDP traffic from a specific source IP address is permitted or denied.npu(config-ext-nacl)# permit tcp host 1.1.1.1 anynpu(config-ext-nacl)# deny udp host 1.1.1.1 <network-src-ip> <mask>Indicates that incoming TCP/UDP traffic is to be permitted or denied for a particular subnet.npu(config-ext-nacl)# permit tcp 1.1.1.0 255.255.255.0 anynpu(config-ext-nacl)# deny udp 1.1.1.0 255.255.255.0 Source port [{gt <port-number (1-65535)> Indicates that incoming TCP/ UDP traffic is to be permitted or denied from the source port for which the port number is greater than the value of this parameter.npu(config-ext-nacl)# permit tcp 1.1.1.0 255.255.255.0 gt 1111npu(config-ext-nacl)# deny udp host 1.1.1.1 gt 1010 [{lt <port-number (1-65535)> Indicates that incoming TCP/ UDP traffic is to be permitted or denied from the source port for which the port number is less than the value of this parameter.npu(config-ext-nacl)# permit tcp 1.1.1.0 255.255.255.0 lt 1111npu(config-ext-nacl)# deny udp host 1.1.1.1 lt 1010[{eq <port-number (1-65535)> Indicates that incoming TCP/ UDP traffic is to be permitted or denied from the source port for which the port number is equal to the value of this parameter.npu(config-ext-nacl)# permit tcp 1.1.1.0 255.255.255.0 eq 8080npu(config-ext-nacl)# deny udp host 1.1.1.1 eq 4040range <port-number (1-65535)> <port-number (1-65535)>}]Indicates that incoming TCP/ UDP traffic is to be permitted or denied from the source port for which the port number is within the range specified by this parameter.npu(config-ext-nacl)# permit tcp 1.1.1.0 255.255.255.0 range 1010 8080npu(config-ext-nacl)# deny udp host 1.1.1.1 range 1010 4040](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-133.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 230 System ManualDestination IP addressany Indicates that TCP/UDP traffic to all NPU interface IP addresses is permitted or denied.npu(config-ext-nacl)# permit tcp 1.1.1.1 host any npu(config-ext-nacl)# deny udp any anyhost <src-ip-address>Indicates that TCP/UDP traffic to a specific NPU interface IP address is permitted or denied. npu(config-ext-nacl)# permit tcp any host 1.1.1.1 host host 1.1.1.1npu(config-ext-nacl)# deny udp any host 1.1.1.1<network-src-ip> <mask>Indicates that TCP/UDP traffic is to be permitted or denied for a particular NPU interface subnet.npu(config-ext-nacl)# permit tcp any host 1.1.1.0 255.255.255.0npu(config-ext-nacl)# deny udp any host 1.1.1.0 255.255.255.0Table 4-18: Parameters for Configuring Permit/Deny Rules for TCP/UDP TrafficParameter Description Example](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-134.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 231 System ManualDestination port[{gt <port-number (1-65535)> Indicates that TCP/ UDPtraffic is to be permitted or denied to the NPU interface source port for which the port number is greater than the value of this parameter.npu(config-ext-nacl)# permit tcp host 1.1.1.1 host any gt 8080npu(config-ext-nacl)# deny udp any any[{lt <port-number (1-65535)> Indicates that TCP/ UDP traffic is to be permitted or denied to the NPU interface source port for which the port number is less than the value of this parameter.npu(config-ext-nacl)# permit tcp host 1.1.1.0 255.255.255.0 any lt 1111npu(config-ext-nacl)# deny udp any host 1.1.1.1 lt 1010[{eq <port-number (1-65535)> Indicates that TCP/ UDP traffic is to be permitted or denied to the NPU interface source port for which the port number is equal to the value of this parameter.npu(config-ext-nacl)# permit tcp any 1.1.1.0 255.255.255.0 eq 8080npu(config-ext-nacl)# deny udp any host 1.1.1.1 eq 4040range <port-number (1-65535)> <port-number (1-65535)>}]Indicates that TCP/ UDP traffic is to be permitted or denied the NPU interface source port for which the port number is within the range specified by this parameter.npu(config-ext-nacl)# permit tcp host 1.1.1.1 host 1.1.1.0 255.255.255.0 range 1010 8080npu(config-ext-nacl)# deny udp host 1.1.1.1 any range 1010 4040Command Syntaxnpu(config-ext-nacl)# deny tcp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]npu(config-ext-nacl)# deny udp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Table 4-18: Parameters for Configuring Permit/Deny Rules for TCP/UDP TrafficParameter Description Example](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-135.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 232 System ManualPrivilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesany | host <src-ip-address> | <src-ip-address> <src-mask>Indicates the source host for which incoming TCP/UDP traffic is permitted/denied.Mandatory N/A For details, refer Table 4-18[{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Indicates the source port from which incoming TCP/UDP traffic is permitted/denied.Optional 0-65535 For details, refer Table 4-18any | host <dest-ip-address> | <dest-ip-address> <dest-mask>Indicates the destination IP address/subnet for which TCP/UDP traffic is permitted/denied.Mandatory N/A For details, refer Table 4-18](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-136.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 233 System Manual4.3.9.1.3.2.2Deleting a Permit/Deny Rule for TCP/UDP Traffic (Extended Mode)Run the following commands to delete a Permit rule for TCP/UDP traffic from/to a specific IP address/port:npu(config-ext-nacl)# no permit tcp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]npu(config-ext-nacl)# no permit udp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Run the following commands to delete a Deny rule for TCP/UDP traffic from/to a specific IP address/port:{gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Indicates the destination port to which TCP/UDP traffic is permitted/denied.Optional 0-65535 For details, refer Table 4-18Command ModesExtended ACL configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-137.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 234 System Manualnpu(config-ext-nacl)# no deny tcp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]npu(config-ext-nacl)# no deny udp {any | host <src-ip-address> | <src-ip-address> <src-mask>} [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Command Syntax (for Permit Rule)npu(config-ext-nacl)# no permit tcp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]npu(config-ext-nacl)# no permit udp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-138.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 235 System ManualCommand Syntax (for Deny Rule)npu(config-ext-nacl)# no deny tcp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <deny-number (1-65535)>}]npu(config-ext-nacl)# no deny udp {any | host <src-ip-address> | <src-ip-address> <src-mask> } [{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}] {any | host <dest-ip-address> | <dest-ip-address> <dest-mask>} {gt <port-number (1-65535)> | lt <port-number (1-65535)> | eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesany | host <src-ip-address> | <src-ip-address> <src-mask>Indicates the source host for which the Permit/Deny rule for incoming TCP/UDP traffic is to be deleted.Mandatory N/A For details, refer Table 4-18[{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Indicates the source port for which the Permit/Deny rule for incoming TCP/UDP traffic is to be deleted.Optional 1-65535 For details, refer Table 4-18](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-139.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 236 System Manual4.3.9.1.3.3 Configuring Permit/Deny Rules for ICMP TrafficAfter you have created an ACL, you can configure Permit/Deny rules for ICMP traffic from/to specific a source and destination IP address/subnet. This section describes the commands to be used for:“Creating a Permit/Deny Rule for ICMP Traffic (Extended Mode)” on page 236“Deleting a Permit/Deny Rule for ICMP Traffic (Extended Mode)” on page 2394.3.9.1.3.3.1Creating a Permit/Deny Rule for ICMP Traffic (Extended Mode)Run the following commands to specify the Permit/Deny rule for ICMP traffic from/to a specific source/destination IP address/subnet:any | host <dest-ip-address> | <dest-ip-address> <dest-mask>Indicates the NPU IP address/subnet for which the Permit/Deny rule for TCP/UDP traffic is to be deleted.Mandatory N/A For details, refer Table 4-18[{gt <port-number (1-65535)> | lt <port-number (1-65535)> |eq <port-number (1-65535)> | range <port-number (1-65535)> <port-number (1-65535)>}]Indicates the NPU interface port for which the Permit/Deny rule for incoming TCP/UDP traffic is to be deleted.Optional 1-65535 For details, refer Table 4-18Command ModesExtended ACL configuration modeIMPORTANTYou cannot configure Permit or Deny rules for an ACL that is associated with a Qos marking rule. You can either associate QoS marking rules or permit/deny rules with an ACL.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-140.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 237 System Manualnpu(config-ext-nacl)# permit icmp {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}npu(config-ext-nacl)# deny icmp {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}In the above commands, it is mandatory to specify the source IP address for which the Permit/Deny rule is to be created. If you do not specify the destination IP address/subnet mask, by default, traffic to all destination IP addresses is permitted/denied.The following table lists the parameters and their descriptions in these commands:Table 4-19: Parameters for Configuring Permit/Deny Rules for ICMP TrafficParameter Description ExampleSource IP any Indicates that incoming ICMP traffic from any source IP address is permitted or denied.npu(config-ext-nacl)#permit icmp anynpu(config-ext-nacl)#deny icmp anyhost <src-ip-address>Indicates that incoming ICMP traffic from a specific source IP address is permitted or denied. npu(config-ext-nacl)#permit icmp host 1.1.1.1npu(config-ext-nacl)#deny icmp host 1.1.1.1<network-src-ip> <mask>Indicates that incoming ICMP traffic is to be permitted or denied for a particular subnet.npu(config-ext-nacl)#permit icmp 1.1.1.0 255.255.255.0npu(config-ext-nacl)#deny icmp host 1.1.1.0 255.255.255.0](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-141.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 238 System ManualDestination IP addressany Indicates that ICMP traffic destined to the NPU interface IP address is permitted or denied.npu(config-ext-nacl)#permit icmp host 1.1.1.1 any npu(config-std-nacl)# deny host 1.1.1.1 host anyhost <src-ip-address>Indicates that ICMP traffic destined to the NPU interface destination IP address is permitted or denied. npu(config-std-nacl)# permit host any host 1.1.1.1npu(config-ext-nacl)#deny icmp any host 1.1.1.1<network-src-ip> <mask>Indicates that ICMP traffic to the NPU interface subnet is to be permitted or denied.npu(config-ext-nacl)#permit icmp host any host 1.1.1.0 255.255.255.0npu(config-ext-nacl)#deny icmp host any host 1.1.1.0 255.255.255.0Command Syntaxnpu(config-ext-nacl)# permit icmp { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-address> | <dest-ip-address> <mask> }npu(config-ext-nacl)# deny icmp { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-address> | <dest-ip-address> <mask> }Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{ any | host <src-ip-address> | <src-ip-address> <mask> }Indicates the source IP address/subnet for which incoming ICMP traffic is permitted/denied.Mandatory N/A For details Table 4-19{ any | host <dest-ip-address> | <dest-ip-address> <mask> }Indicates the destination IP address/subnet for which ICMP traffic is permitted/denied.Optional any For details Table 4-19Table 4-19: Parameters for Configuring Permit/Deny Rules for ICMP TrafficParameter Description Example](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-142.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 239 System Manual4.3.9.1.3.3.2Deleting a Permit/Deny Rule for ICMP Traffic (Extended Mode)Run the following commands to delete a Permit/Deny rule for ICMP traffic from/to a specific IP address/subnet:npu(config-ext-nacl)# no permit icmp {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}npu(config-ext-nacl)# no deny icmp {any | host <src-ip-address> | <src-ip-address> <mask>} {any | host <dest-ip-address> | <dest-ip-address> <mask>}Command ModesGlobal command modeCommand Syntaxnpu(config-ext-nacl)# no permit icmp { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-address> | <dest-ip-address> <mask> }npu(config-ext-nacl)# no deny icmp { any | host <src-ip-address> | <src-ip-address> <mask> } { any | host <dest-ip-address> | <dest-ip-address> <mask> }Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{ any | host <src-ip-address> | <src-ip-address> <mask> }Indicates the source IP address/subnet for which the Permit/Deny rule for incoming ICMP traffic is to be deleted.Mandatory N/A For details Table 4-19{ any | host <dest-ip-address> | <dest-ip-address> <mask> }Indicates the destination IP address/subnet for which the Permit/Deny rule for ICMP traffic is to be deleted.Optional any For details Table 4-19Command ModesExtended ACL configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-143.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 240 System Manual4.3.9.1.4 Terminating the ACL Configuration ModeTo terminate the standard ACL configuration mode and return to the global configuration mode, run the following command:npu(config-std-nacl)# exitTo exit the extended ACL configuration mode and return to the global configuration mode, run the following command:npu(config-ext-nacl)# exit4.3.9.2 Deleting an ACL1Check if the ACL is attached to the interface. For more information about this command, refer Section 4.3.9.4.2Enable the interface configuration mode and de-attach the ACL. For details, refer Section 4.3.9.3.3Terminate the interface configuration mode to return to the global configuration mode (refer Section 4.3.9.3.4).4Run the following command to delete the ACL:npu(config)# no ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>}Command Syntaxnpu(config-std-nacl)# exitnpu(config-ext-nacl) # exitPrivilege Level10Command ModesStandard/Extended ACL configuration modeTo delete an ACL:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-144.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 241 System Manual4.3.9.3 Attaching/De-attaching ACLs to/from an InterfaceYou can attach or de-attach an ACL to/from the following virtual interfaces.NPUAll the AU interfacesWhen an ACL is attached to an interface, it is in the ACTIVE state; it is in the INACTIVE state when it is de-attached from an interface.To enable initial access to the NPU, the Standard ACL 1 is available by default, with a Permit rule allowing unrestricted access to the Local Management interface (Destination IP Address = 172.31.0.1, Source IP Address = Any). By default this ACL is attached to both the NPU and AUs.IMPORTANTAn error may occur if:The ACL you are trying to delete is INACTIVE.The ACL number you have specified does not exist.Command Syntaxnpu(config)# no ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{ standard <access-list-number (1-99)> | extended <access-list-number (100-199)> }Indicates the ACL number of the standard or extended ACL to be deleted. Mandatory N/A Standard (1-99)Extended (100-199)Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-145.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 242 System Manual1Enable the interface configuration mode (refer Section 4.3.9.3.1).2You can now execute either of the following tasks:»Attach an ACL to an interface (refer Section 4.3.9.3.2).»De-attach an ACL from an interface (refer Section 4.3.9.3.3).3Terminate the interface configuration mode (refer Section 4.3.9.3.4).4.3.9.3.1 Enabling the Interface Configuration ModeACLs are applied on traffic received from the DATA, MGMT or CSCD ports, and destined towards the following virtual interfaces:AUsNPUBy default, all traffic destined towards the AUs or the NPU is denied. Apply specific Permit ACLs to allow traffic to reach the AUs or the NPU. Run the following command to enable the interface configuration mode for the NPU:npu(config)# interface npu-hostRun the following command to enable the interface configuration mode for all AUs:npu(config)# interface all-auAfter you have enabled the interface configuration mode, you can:Attach an ACL to an interface (Section 4.3.9.3.2)De-attach an ACL from an interface (Section 4.3.9.3.3)4.3.9.3.2 Attaching an ACL to an interface After you have enabled the interface configuration mode, run the following command to attach an ACL with an interface:npu(config-if)# ip access-group {<access-list-number (1-199)> | <access-list-name>}To attach/de-attach an ACL:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-146.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 243 System Manual4.3.9.3.3 Deattaching an ACL from an InterfaceRun the following command to de-attach an ACL from an interface:npu(config-if)# no ip access-group {<access-list-number (1-199)> | <access-list-name>}IMPORTANTAn error may occur if:The ACL number/name that you have specified does not exist or is already attached to this interface.You are trying to attach an ACL to an interface (other than the NPU/all AUs).Command Syntaxnpu(config-if)# ip access-group {<access-list-number (1-199)> | <access-list-name>}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{<access-list-number (1-199)> | <access-list-name>}Indicates the number or name of the ACL to be attached to this interface.Mandatory N/A 1-99StringCommand ModesInterface configuration modeIMPORTANTAn error may occur if the ACL number/name that you have specified does not exist or is already attached to this interface.Command Syntaxnpu(config-if)# no ip access-group {<access-list-number (1-199)> | <access-list-name>}](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-147.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 244 System Manual4.3.9.3.4 Terminating the Interface Configuration ModeTo exit the interface configuration mode and return to the global configuration mode, run the following command:npu(config-if)# exit4.3.9.4 Displaying ACL Configuration InformationRun the following command to display the configuration information for a specific ACL:npu# show access-lists [{<access-list-number (1-199)> | <access-list-name}]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{<access-list-number (1-199)> | <access-list-name>}Indicates the number/name of the ACL to be deattached from this interface.Mandatory N/A 1-99StringCommand ModesInterface configuration modeCommand Syntaxnpu(config-if)# exitPrivilege Level10Command ModesInterface configuration modeIMPORTANTAn error may occur if the ACL number/name you have specified does not exist.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-148.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 245 System ManualCommand Syntaxnpu# show access-lists [{<access-list-number (1-199)> | <access-list-name}]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[{<access-list-number (1-199)> | <access-list-name}]Indicates the number or name of the ACL for which configuration information is to be displayed. If you do not provide the ACL number or name, configuration information is displayed for all ACLs.Optional N/A 1-199StringDisplay Format (Standard)Standard IP Access List <ACL number>---------------------------------------------------------------------Access List Name(Alias) :<ACL Name> Interface List : <Interface Name>, <Interface Name> Status : <value> Source IP address : <value> Source IP address mask : <value> Destination IP address : <value>Destination IP address mask : <value> Rule Action : <value> Packet Match Count : <value> Rule Row Status : <value>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-149.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 246 System Manual4.3.10 Configuring the ASN-GW FunctionalityThe ASN-GW functionality indicates that the NPU executes the following functions:Display Format (Extended)Extended IP Access List <ACL Number>-----------------------------Access List Name(Alias) : <ACL Name>Interface List : <Interface>, <Interface>Status : <value>Filter Protocol Type : <value>Source IP address : <value>Filter Source Port : <value>Rule Action : <value>QoS Classifier ID : <value>Marking rule status : <value>Command ModesGlobal command modeIMPORTANTExecute the procedures described in this section only if you are operating the NPU in the ASN-GW mode. Skip this section if you are operating the NPU in the Transparent mode.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-150.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 247 System ManualNetwork Decision Point (NWDP): Includes the following non-bearer plane functions:»Implementation of EAP Authenticator and AAA client»Termination of RADIUS protocol against the selected CSN AAA server (home or visited AAA server) for MS authentication and per-MS policy profile retrieval »Storage of the MS policy profile for as long as the MS is authenticated/authorized and remains in the ASN controlled by the specific ASN-GW»Generation of authentication key material»QoS service flow authorization entity»AAA accounting clientNetwork Enforcement Point (NWEP) functions: Includes the following bearer plane functions:»Classification of downlink data into generic routing encapsulation (GRE) tunnels»Packet header suppression functionality»DHCP functionality»Handover functionalityThe ASN-GW functionality is disabled if you are operating the NPU in the Transparent mode. If you are operating the NPU in the ASN-GW mode, you can choose to operate the NPU in either of the following modes:With HA support, that is, MIP services are implemented (not supported in the current release)Without HA support, that is, MIP services are not implemented.IMPORTANTThe ASN-GW mode with HA support is not implemented because MIP services are not supported in the current release.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-151.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 248 System ManualThe following table lists the tasks for configuring the ASN-GW functionality. Table 4-20: Tasks to be Executed for Configuring the ASN-GW FunctionalityTask Required for Operating the NPU with HA Support Required for Operating the NPU without HA Support“Configuring the Next-hop IP Address-Network ID Mapping” on page 249Yes Yes“Configuring the IGMP Functionality” on page 252Note: This feature is not supported in the current release.Yes Yes“Configuring the MIP-Foreign Agent Functionality” on page 256Note: This feature is not supported in the current release.Yes No“Configuring the Proxy-MIP Client Functionality” on page 258Note: This feature is not supported in the current release.Yes No“Configuring the ASN Interface” on page 261Yes Yes“Managing the Authenticator Function” on page 263Yes Yes“Configuring the Data Path Function” on page 268Yes Yes“Configuring the Context Function” on page 272Yes Yes“Configuring the MS State Change Functionality” on page 275Yes Yes](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-152.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 249 System Manual4.3.10.1 Configuring the Next-hop IP Address-Network ID MappingThe NPU maintains the mapping of the BS network ID to the next-hop IP address. The next-hop IP address can be the IP address of an intermediate ASN-GW or the destination BS. Using this mapping, the NPU resolves the BS-ID to IP address. This section describes the commands to be used for: “Configuring the Next-hop IP Address” on page 250“Displaying the Next-hop IP Address-Network ID Mapping” on page 251“Displaying the Next-hop IP Address-Network ID Mapping” on page 251“Configuring the Connectivity Service Network Interface” on page 279Yes Yes“Configuring Bearer Plane QoS Marking Rules” on page 281Yes Yes“Managing Service Interfaces” on page 290Yes Yes“Configuring the AAA Client Functionality” on page 301Yes Yes“Managing Service Groups” on page 310Yes Yes“Configuring the Service Flow Authorization Functionality” on page 335Yes (Configure only DHCP Proxy for a service group)Yes (Configure DHCP server, proxy or relay for a service group)“Configuring PHS Rules” on page 386Yes Yes“Managing the ASN-GW Keep-Alive Functionality” on page 391Yes YesTable 4-20: Tasks to be Executed for Configuring the ASN-GW FunctionalityTask Required for Operating the NPU with HA Support Required for Operating the NPU without HA Support](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-153.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 250 System Manual4.3.10.1.1 Configuring the Next-hop IP AddressTo map the next-hop IP address for a specific network ID, run the following command:npu(config)# idip <nw-id> <next-hop-ipaddr>For example, run the following command to map the MAC address of the BS with the next-hop IP address:npu(config)# idip 112233445566 10.0.0.14.3.10.1.2 Deleting Next-hop IP Address-Network ID MappingsTo delete a specific or all next-hop IP address-network ID mappings, run the following command:npu(config)# no idip [<nw-id>]NOTERefer to Section 4.3.10.2.1 for a list of existing next-hop IP address-network ID mappings.Command Syntaxnpu(config)# idip <nw-id> <next-hop-ipaddr>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<nw-id> Denotes the BS ID. This parameter is a MAC address, and should be specified without colons.Mandatory N/A 6-byte ID<next-hop-ipaddr>Denotes the next hop IP address for a particular BS.Mandatory N/A Valid IP AddressCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-154.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 251 System Manual4.3.10.1.3 Displaying the Next-hop IP Address-Network ID MappingTo display the next-hop-IP address mapped to a network ID or all network IDs, run the following command:npu# show idip [<nw-id>]Specify the network ID if you want to display a particular the next-hop-IP address-network ID mapping. Do not specify a value for this parameter if you want to view all the next-hop-IP address-network ID mappings.CAUTIONSpecify the network ID if you want to delete a specific next-hop IP address-network ID mapping. Otherwise all the configured mappings are deleted.Command Syntaxnpu(config)# no idip [<nw-id>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<nw-id> Denotes the network ID(s) for which an IDIP context is to be removed.Specify this parameter only if you want to delete a specific network ID. If you do not specify a value for this parameter, all configured network IDs are deleted.Mandatory N/A 6-byte IDCommand ModesGlobal configuration modeCommand Syntaxnpu# show idip [<nw-id>]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-155.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 252 System Manual4.3.10.2 Configuring the IGMP FunctionalityThe NPU serves as the IGMP proxy server between a group of MSs and the multicast router. In addition, it serves as a router for all MSs that are connected to it. It receives periodic IGMP reports for all MSs that are members of a multicast group. Based on these reports, the NPU maintains a database of members. Each time there is a change in the membership database, because of a member leaving or joining the group, the NPU sends a report to the multicast router. The NPU also Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<nw-id>] Denotes the network ID (s) for which you want to view the next-hop IP addresses already mapped to it. Specify a value for this parameter if you want to view the next-hop IP address(es) defined for a specific network ID. If you do not specify any value for this parameter, all the existing entries for mappings of network IDs- next-hop IP addresses are displayed.Optional N/A 6-byte IDDisplay Formatnw-id next-hop-ip address<Network ID 1> <Ip Address><Network ID 2> <Ip Address>Command ModesGlobal command modeIMPORTANTThe IGMP functionality is not supported in the current release.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-156.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 253 System Manualserves as a host for the multicast router and sends membership reports in response to membership queries.This section describes the commands to be used for: “Configuring IGMP Parameters” on page 253“Restoring the Default Configuration Parameters for the IGMP Functionality” on page 254“Displaying IGMP Configuration Information” on page 255“Displaying IGMP Membership Information” on page 2554.3.10.2.1 Configuring IGMP ParametersTo configure the IGMP functionality, run the following command:npu(config)# igmp [mcastrouter-version <version>] [robustness <retransmissions>] [unsolicit-report-interval <timeout>] [query-delaytime <timeout>]NOTEYou can display configuration information for the IGMP functionality. For details, refer to Section 4.3.10.2.3.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# igmp [mcastrouter-version <version>] [robustness <retransmissions>] [unsolicit-report-interval <timeout>] [query-delaytime <timeout>]Privilege Level15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-157.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 254 System Manual4.3.10.2.2 Restoring the Default Configuration Parameters for the IGMP FunctionalityTo restore the default configuration for the IGMP functionality, run the following command:npu(config)# no igmp [mcastrouter-version] [robustness] [unsolicit-report-interval] [query-delaytime]Syntax Description Parameter Description Presence Default ValuePossible Values[mcastrouter-version <version>]Denotes the IGMP version of the multicast router.Optional IGMPv3 IGMPv2IGMPv3[robustness <retransmissions>]Determines the number of retransmissions of the IGMP reports sent by the NPU. Optional 2 1 - 2^8[unsolicit-report-interval <timeout>]Denotes the interval, in seconds, between successive retransmissions of unsolicited IGMP reports sent by the NPU.Optional 1 1 - 100[query-delaytime <timeout>]Denotes the interval, in seconds, between general queries sent by the multicast router. Optional 125 1 - 200Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.2.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no igmp [mcastrouter-version] [robustness] [unsolicit-report-interval] [query-delaytime]Privilege Level15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-158.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 255 System Manual4.3.10.2.3 Displaying IGMP Configuration InformationTo display configuration information for the IGMP functionality, run the following command:npu# show igmp4.3.10.2.4 Displaying IGMP Membership InformationTo display dynamic multicast group membership information, run the following command:npu# show igmp-membershipCommand ModesGlobal configuration modeCommand Syntaxnpu(config)# show igmpPrivilege Level1Display FormatIGMP Configuration:mcastrouter-version = <value> robustness = <value>unsolicit-report-interval = <value>query-delaytime = <value>Command ModesGlobal command modeCommand Syntaxnpu# show igmp-membershipCommand Syntax1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-159.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 256 System Manual4.3.10.3 Configuring the MIP-Foreign Agent FunctionalityWhen the MS is MIP-enabled, the NPU serves as the Foreign Agent (FA) for transferring mobile IP messages between the MS and the HA. As the FA, the NPU is responsible for registering the MS in the network. It provides security by using the security associations (MIP keys) between the MS and FA, and FA and HA. This section describes the commands to be used for: “Configuring Parameters for the MIP-FA Functionality” on page 256“Restoring the Default Configuration Parameters for the MIP-FA Functionality” on page 257“Displaying Configuration Information for the MIP-FA Functionality” on page 2584.3.10.3.1 Configuring Parameters for the MIP-FA FunctionalityTo configure MIP-FA parameters, run the following command:npu(config)# mip-fa [allowed-mslifetime <timeout>] [agent-advertisements <no of agent advertisement>] [advertisement-interval <timeout>]Display FormatIGMP Membership :GrpMulticast-addr Src-addrlist<value> <value> <value> ….Command ModesGlobal configuration modeIMPORTANTThe MIP-Foreign Agent functionality is not supported in the current release.NOTEYou can display configuration information for the MIP-FA functionality. For details, refer to Section 4.3.10.3.3.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-160.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 257 System Manual4.3.10.3.2 Restoring the Default Configuration Parameters for the MIP-FA FunctionalityTo restore the default configuration for the MIP-FA functionality, run the following command:npu(config)# no mip-fa [allowed-mslifetime] [agent-advertisements] [advertisement-interval]Command Syntaxnpu(config)# mip-fa [allowed-mslifetime <timeout>] [agent-advertisements <no of agent advertisement>] [advertisement-interval <timeout>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[allowed-mslifetime <timeout>]Denotes the maximum period, in seconds, for which the IP address allocated to the MS is active.Optional 9000 0-9000[agent-advertisements <no of agent advertisement>]Denotes the maximum number of initial agent advertisements sent to the MS.Optional 3 0-5[advertisement-interval <timeout>]Denotes the interval, in seconds, between successive agent advertisements.Optional 10 5-100Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.3.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no mip-fa [allowed-mslifetime] [agent-advertisements] [advertisement-interval]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-161.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 258 System Manual4.3.10.3.3 Displaying Configuration Information for the MIP-FA FunctionalityTo display configuration information for the MIP-FA functionality, run the following command:npu# show mip-fa4.3.10.4 Configuring the Proxy-MIP Client FunctionalityWhen the MS is MIP-incapable, the NPU provides the Proxy-MIP (MIP FA) client functionality, and manages MIP registration between the MS and the HA. This section describes the commands to be used for: “Configuring Parameters for the PMIP Client Functionality” on page 259Privilege Level15Command ModesGlobal configuration modeCommand Syntaxnpu# show mip-faPrivilege Level1Display FormatMIP-FA Configuration :allowed-mslifetime = <value>agent-advertisements = <value>advertisement-interval = <value>Command ModesGlobal command modeIMPORTANTThe Proxy-MIP client functionality is not supported in the current release.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-162.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 259 System Manual“Restoring the Default Configuration Parameters for the PMIP Client Functionality” on page 260“Displaying Configuration Information for the PMIP Client Functionality” on page 2614.3.10.4.1 Configuring Parameters for the PMIP Client FunctionalityRun the following command to configure the PMIP client functionality to specify how registration of a MIP-incapable MS should be managed:npu(config)# mip-client [mslifetime <timeout>] [mslifetime-guard <percent>] [registration-retries <retransmissions>] [registration-interval <timeout>]NOTEYou can display configuration information for the PMIP client functionality. For details, refer to Section 4.3.10.4.3.IMPORTANTAn error may occur if you provide an invalid for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# mip-client [mslifetime <timeout>] [mslifetime-guard <percent>] [registration-retries <retransmissions>] [registration-interval <timeout>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[mslifetime <timeout>]Denotes the maximum period, in seconds, for which the HA will maintain the MIP binding. This information is sent in the MIP registration message. At the end of this period, the NPU de-registers the MS.Optional 9000 0-9000](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-163.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 260 System Manual4.3.10.4.2 Restoring the Default Configuration Parameters for the PMIP Client FunctionalityTo restore the default configuration for the PMIP client functionality, run the following command:npu(config)# no mip-client [mslifetime] [mslifetime-guard] [registration-retries] [registration-interval][mslifetime-guard <percent>]Denotes the period for which the PMIP remains active. The value of this parameter should be a percentage of the mslifetime parameter. At the end of this period, the PMIP attempts re-registration.Optional 65% 0-100[registration-retries <retransmissions>] Denotes the maximum number of registration requests that can be sent by the NPU.Optional 3 0-5[registration-interval <timeout>]Denotes the interval between successive requests of an MS, in seconds, within which the MIP registration response should be sent by the HA.Optional 10 5-100Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.4.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no mip-client [mslifetime] [mslifetime-guard] [registration-retries] [registration-interval]Privilege Level15Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-164.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 261 System Manual4.3.10.4.3 Displaying Configuration Information for the PMIP Client FunctionalityTo display PMIP client configuration information, run the following command:npu# show mip-client4.3.10.5 Configuring the ASN InterfaceThe ASN interface is the NPU interface that is exposed towards the BS or another ASN gateway. You can configure ASN interface-specific information, such as the IP address to be used for the NPU to communicate with the BS and other ASN gateways.This section describes the commands to be used for: “Assigning a Pre-configured IP Interface” on page 261“Displaying Configuration Information for the ASN Interface” on page 2634.3.10.5.1 Assigning a Pre-configured IP InterfaceTo assign a pre-configured IP interface to the ASN side, that is, the R4/R6 interface, run the following command:npu(config)# asnif <ip-intf>Command Syntaxnpu# show mip-clientPrivilege Level1Display FormatPMIP-Client Configuration :mslifetime = <value>mslifetime-guard = <value>registration-retries = <value>registration-interval = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-165.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 262 System ManualFor the current release, specify bearer as the value of the ip-intf parameter. However, the IP address should already be configured for the bearer interface. For details, refer to “Configuring Static Routes” on page 211.NOTEYou can display configuration information for ASN interface. For details, refer to Section 4.3.10.5.2.IMPORTANTAn error may occur if you provide an invalid value for this parameter. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# asnif <ip-intf>Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Valuesasnif <ip-intf>Denotes the IP interface that is to be exposed towards the BS and other ASN gateways. Ensure that the IP address for the bearer interface is configured before executing this command.Note: If you are modifying the ASN interface, save the current configuration (refer Section 4.3.4.1) and reset the NPU (Section 4.2.2.1) for the change to take effect. Mandatory N/A bearer (only the bearer interface is supported in the current release)Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-166.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 263 System Manual4.3.10.5.2 Displaying Configuration Information for the ASN InterfaceTo display the IP interface (R4/R6) of the ASN interface, run the following command:npu# show asnif4.3.10.6 Managing the Authenticator FunctionThe Authenticator function of the NPU manages MS authentication for accessing WiMAX network resources. It also maintains context information for each MS that has accessed or is trying to access the network. For this, it handles all key derivations and distribution. In addition, it uses AAA client functions to send RADIUS messages on the R3 interface.This section describes the commands to be used for:“Configuring Parameters for the Authenticator Function” on page 263“Restoring the Default Configuration Parameters for the Authenticator Function” on page 266“Displaying Configuration Information for the Authenticator Function” on page 2674.3.10.6.1 Configuring Parameters for the Authenticator FunctionTo configure the parameters of the Authenticator function, run the following command:Command Syntaxnpu# show asnifPrivilege Level1Display FormatASN Interface Configuration :ASN IP Interface = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-167.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 264 System Manualnpu(config)# authenticator [eapidreq-retries <retransmissions>] [eapidreq-interval <timeout>] [ntwentry-holdtime <timeout>] [eaptransfer-retries <retransmissions>] [eaptransfer-interval <timeout>] [reauth-attempts <counter>] [reauthcmplt-holdtime <timeout>] [eaptransfer-roundtrips <counter>] [pmk-lifetime <timeout>] [pmk-guardtime <timeout>] [authfailure-holdtime <timeout>] [max-ntwentry <counter>]NOTEYou can display configuration information for the Authenticator function. For details, refer to Section 4.3.10.6.3IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# authenticator [eapidreq-retries <retransmissions>] [eapidreq-interval <timeout>] [ntwentry-holdtime <timeout>] [eaptransfer-retries <retransmissions>] [eaptransfer-interval <timeout>] [reauth-attempts <counter>] [reauthcmplt-holdtime <timeout>] [eaptransfer-roundtrips <counter>] [pmk-lifetime <timeout>] [pmk-guardtime <timeout>] [authfailure-holdtime <timeout>] [max-ntwentry <counter>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[eapidreq-retries <retransmissions>]Denotes the number of times the NPU can retransmit the EAP ID request until it receives a EAP ID response.Optional 3 0-5[eapidreq-interval <timeout>]Denotes the period, in milliseconds, for which the NPU should wait for the response to the request for the EAP ID.Optional 500 10-100000](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-168.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 265 System Manual[ntwentry-holdtime <timeout>] Denotes the period, in seconds, within which the MS should be authenticated for initial entry into the network. If the MS is not authenticated within this period, the NPU terminates the request for network entry.Optional 5 0-100[eaptransfer-retries <retransmissions>] Denotes the maximum number of times the MS can attempt for initial entry to the network. If the number of EAP transfers exceeds the value of this parameter, the NPU de-registers the MS.Optional 3 0-5[eaptransfer-interval <timeout>] Denotes the period, in milliseconds, the NPU waits for the EAP identity response.Optional 500 10 - 100000[reauth-attempts <counter>] Denotes the maximum number of times the NPU may handle a an MS/network-initiated re-authentication request. When the number of re-authentication attempts exceeds the value of this parameter, the MS is de-registered.Optional 3 0-10[reauthcmplt-holdtime <timeout>] Denotes the period, in milliseconds, within which, re-authentication of the MS should be complete. If the MS is not authenticated within this period, the NPU reinitiates MS authentication.Optional 5000 10 - 100000[eaptransfer-roundtrips <counter>] Denotes the number EAP roundtrips in one authentication/re-authentication process.Optional 42949672950 - 4294967295[pmk-lifetime <timeout>] Denotes the period, in seconds, for which the MS authentication key is valid. At the end of this period, the NPU de-registers the MS.Optional 3600 60-86400](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-169.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 266 System Manual4.3.10.6.2 Restoring the Default Configuration Parameters for the Authenticator FunctionTo restore the default configuration for the Authenticator function, run the following command:npu(config)# no authenticator [eapidreq-retries] [eapidreq-interval] [ntwentry-holdtime] [eaptransfer-retries] [eaptransfer-interval] [reauth-attempts] [reauthcmplt-holdtime] [eaptransfer-roundtrips] [pmk-lifetime] [pmk-guardtime] [authfailure-holdtime] [max-ntwentry][pmk-guardtime <timeout>] Denotes the duration of the guard timer for the MS authentication keys. the NPU initiates re-authentication for the MS after the pmk guard timer has expired. (The value of this timer is pmk-lifetime - pmk-guardtime.)If the value of this parameter is 0, the guard timer is not started.Optional 0 0-86400[authfailure-holdtime <timeout>] Denotes the period, in seconds, for which the MS context is retained after authentication failure.Optional 0 1-1024[max-ntwentry <counter>]Denotes the maximum number of times that the NPU may handle a network entry request from an MS, after prior attempts for that MS has already failed. After the NPU has handled max-ntwentry number of attempts and its value is 0, the MS is assigned the unauthenticated mode.Optional 3 0-10Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-170.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 267 System Manual4.3.10.6.3 Displaying Configuration Information for the Authenticator FunctionTo display configuration information for the Authenticator function, run the following command:npu# show authenticatorNOTERefer to Section 4.3.10.6.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no authenticator [eapidreq-retries] [eapidreq-interval] [ntwentry-holdtime] [eaptransfer-retries] [eaptransfer-interval] [reauth-attempts] [reauthcmplt-holdtime] [eaptransfer-roundtrips] [pmk-lifetime] [pmk-guardtime] [authfailure-holdtime] [max-ntwentry]Privilege Level15Command ModesGlobal configuration modeCommand Syntaxnpu# show authenticatorPrivilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-171.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 268 System Manual4.3.10.7 Configuring the Data Path FunctionThe Data Path function controls the creation, maintenance, and deletion of data paths within the NPU. This section describes the commands to be used for: “Configuring Parameters for the Data Path Function” on page 268“Restoring the Default Parameters for the Data Path Function” on page 271“Displaying Configuration Information for the Data Path Function” on page 2724.3.10.7.1 Configuring Parameters for the Data Path FunctionTo configure the parameters for the data path function, run the following command:npu(config)# datapath [initpathregreq-retries <retransmissions>] [initpathregreq-interval <timeout>] [msderegreq-retries <retransmissions>] [msderegreq-interval <timeout>] [pathregreq-retries <retransmissions>] [pathregreq-interval <timeout>] [pathregrsp-retries <retransmissions>] Display FormatAuthenticator Function Configuration :eapidreq-retries = <value>eapidreq-interval = <value>ntwentry-holdtime = <value>eaptransfer-retries = <value>eaptransfer-interval = <value>reauth-attempts = <value>reauthcmplt-holdtime = <value>eaptransfer-roundtrips = <value>pmk-lifetime = <value>pmk-guardtime = <value>authfailure-holdtime = <value>max-ntwentry = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-172.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 269 System Manual[pathregrsp-interval <timeout>] [pathregstart-interval <timeout>] [mipwaitdhcp-holdtime <timeout>]NOTEYou can display configuration information for the data path function. For details, refer to Section 4.3.10.7.3.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# datapath [initpathregreq-retries <retransmissions>] [initpathregreq-interval <timeout>] [msderegreq-retries <retransmissions>] [msderegreq-interval <timeout>] [pathregreq-retries <retransmissions>] [pathregreq-interval <timeout>] [pathregrsp-retries <retransmissions>] [pathregrsp-interval <timeout>] [pathregstart-interval <timeout>] [mipwaitdhcp-holdtime <timeout>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[initpathregreq-retries <retransmissions>] Denotes the maximum number of initial path registration request retransmissions that may be sent by the NPU. After the number of retransmissions has exceeded the value of this parameter, the MS de-registration procedure is initiated.Optional 3 0-5](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-173.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 270 System Manual[initpathregreq-interval <timeout>] Denotes the interval, in milliseconds, after which the request for initial path registration should be complete. If the initial path registration request is not completed within this period, the NPU may retransmit the initial path registration request.Optional 1 10 - 3000[msderegreq-retries <retransmissions>] Denotes the maximum number of MS deregistration request retransmissions, after which the MS is de-registered.Optional 3 0-5[msderegreq-interval <timeout>]Denotes the MS deregistration response timeout, in milliseconds.Optional 30 5-500[pathregreq-retries <retransmissions>]Denotes the maximum number of times the NPU may retransmit the path registration request.Optional 3 0-5[pathregreq-interval <timeout>]Denotes the period, in milliseconds, with which the NPU should wait for the path registration response. If a response is not received within this period, the NPU retransmits the request.Optional 10 5- 100[pathregrsp-retries <retransmissions>]Denotes the maximum number of times the NPU may retransmit the path response.Optional 3 0-5[pathregrsp-interval <timeout>]Denotes the period, in milliseconds, within which the NPU should wait for an acknowledgement for the registration response. If a response is not received within this period, the NPU retransmits the response.Optional 10 5- 100](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-174.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 271 System Manual4.3.10.7.2 Restoring the Default Parameters for the Data Path FunctionTo restore the default configuration for the data path function, run the following command:npu(config)# no datapath [initpathregreq-retries] [initpathregreq-interval] [msderegreq-retries] [msderegreq-interval] [pathregreq-retries] [pathregreq-interval] [pathregrsp-retries] [pathregrsp-interval] [pathregstart-interval] [mipwaitdhcp-holdtime][pathregstart-interval <timeout>]Indicates the period, in milliseconds, within which the path registration procedure is initiated, after the path pre-registration procedure is complete. If the path registration procedure is not completed within the period specified by this parameter, the MS is de-registered.Optional 1000 5- 2000[mipwaitdhcp-holdtime <timeout>]Denotes the period, in seconds, for allocating the IP address, after the path registration procedure is complete. Optional 0 0 - 120Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.7.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no datapath [initpathregreq-retries] [initpathregreq-interval] [msderegreq-retries] [msderegreq-interval] [pathregreq-retries] [pathregreq-interval] [pathregrsp-retries] [pathregrsp-interval] [pathregstart-interval] [mipwaitdhcp-holdtime]Privilege Level15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-175.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 272 System Manual4.3.10.7.3 Displaying Configuration Information for the Data Path FunctionTo display configuration information for the Data Path function, run the following command:npu# show datapath4.3.10.8 Configuring the Context FunctionThe context function manages the contexts of various authenticated MSs. You can specify parameters pertaining to context creation and reports. This section describes the commands to be used for:“Configuring the Parameters for the Context Function” on page 273Command ModesGlobal configuration modeCommand Syntaxnpu# show datapathPrivilege Level1Display FormatData Path Function Configuration :initpathregreq-retries = <value>initpathregreq-interval = <value>msderegreq-retries = <value>msderegreq-interval = <value>pathregreq-retries = <value>pathregreq-interval = <value>pathregrsp-retries = <value>pathregrsp-interval = <value>pathregstart-interval = <value>mipwaitdhcp-holdtime <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-176.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 273 System Manual“Restoring the Default Configuration Parameters for the Context Function” on page 274“Displaying Configuration Information for the Context Function” on page 2754.3.10.8.1 Configuring the Parameters for the Context FunctionTo configure the parameters for the context function, run the following command:npu(config)# contextfn [contextreq-retries <retransmissions>] [contextreq-interval <timeout>] [contextrprt-retries <retransmissions>] [contextrprt-interval <timeout>]NOTEYou can display configuration information for the context function. For details, refer to Section 4.3.10.8.3IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# contextfn [contextreq-retries <retransmissions>] [contextreq-interval <timeout>] [contextrprt-retries <retransmissions>] [contextrprt-interval <timeout>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[contextreq-retries <retransmissions>]Denotes the maximum number of times the NPU will retransmit a context request. Optional 3 1-5](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-177.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 274 System Manual4.3.10.8.2 Restoring the Default Configuration Parameters for the Context FunctionTo restore the default configuration for the context function, run the following command:npu(config)# no contextfn [contextreq-retries] [contextreq-interval] [contextrprt-retries] [contextrprt-interval][contextreq-interval <timeout>]Denotes the period, in milliseconds, for which the NPU waits for a response to the context request. If the NPU does not receive a response to this request within the period specified by this timer, the NPU retransmits this request.Optional 10 5 - 100[contextrprt-retries <retransmissions>]Denotes the maximum number of times, the NPU retransmits the context report.Optional 3 0-5[contextrprt-interval <timeout>]Denotes the period, in milliseconds, for which the NPU waits for the context report acknowledgement. At the end of this period, the NPU retransmits the context report.Optional 3 0-5Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.8.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no contextfn [contextreq-retries] [contextreq-interval] [contextrprt-retries] [contextrprt-interval]Privilege Level15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-178.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 275 System Manual4.3.10.8.3 Displaying Configuration Information for the Context Function To display configuration information for the context function, run the following command:npu# show contextfn4.3.10.9 Configuring the MS State Change FunctionalityThe MS state change functionality manages MS states within an MS context. This section describes the commands to be used for: “Configuring Parameters for the MS State Change Functionality” on page 276“Restoring the Default Configuration Parameters for the MS State Change Functionality” on page 277“Displaying Configuration Information for the MS State Change Functionality” on page 278Command ModesGlobal configuration modeCommand Syntaxnpu# show contextfnPrivilege Level1Display FormatContext Function Configuration :contextreq-retries = <value>contextreq-interval = <value>contextrprt-retries = <value>contextrprt-interval = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-179.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 276 System Manual4.3.10.9.1 Configuring Parameters for the MS State Change Functionality To configure the parameters for the MS State Change functionality, run the following command:npu(config)# msscfn [msscrsp-retries <retransmissions>] [msscrsp-interval <timeout>] [sbc-holdtime <timeout>] [reg-holdtime <timeout>] [msscdrctv-retries <retransmissions>] [msscdrctv-interval <timeout>]NOTEYou can display configuration information for the MS state change functionality. For details, refer to Section 4.3.10.9.3.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# msscfn [msscrsp-retries <retransmissions>] [msscrsp-interval <timeout>] [sbc-holdtime <timeout>] [reg-holdtime <timeout>] [msscdrctv-retries <retransmissions>] [msscdrctv-interval <timeout>]Privilege Level15Syntax Description Parameter Description Presence Default ValuePossible Values[msscrsp-retries <retransmissions>]Denotes the maximum number of times, the NPU retransmits the MS state change response.Optional 3 1-5[msscrsp-interval <timeout>]Denotes the period, in milliseconds for which the NPU waits for an acknowledgement for the MS state change response. If the NPU does not receive an acknowledgement within this period, it retransmits the MS state change response. Optional 10 5- 500](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-180.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 277 System Manual4.3.10.9.2 Restoring the Default Configuration Parameters for the MS State Change FunctionalityTo restore the default configuration for the MS State Change functionality, run the following command:npu(config)# no msscfn [msscrsp-retries] [msscrsp-interval] [sbc-holdtime] [reg-holdtime] [msscdrctv-retries] [msscdrctv-interval][sbc-holdtime <timeout>]Denotes the period, in milliseconds, within which the basic capabilities negotiation procedure should be completed. At the end of this period, the NPU starts the authentication/ registration procedure for the MS, depending on accepted authentication policy.Optional 5 0-100[reg-holdtime <timeout>]Denotes the interval, in seconds, for the MS registration procedure timeout. After this interval, the NPU changes the MS state to the registered state, and initiates the data path creation procedure (for authenticated MSs).Optional 5 0-100[msscdrctv-retries <retransmissions>]Denotes the maximum number of times, the NPU may retransmit the MS state change directive.Optional 3 0-5[msscdrctv-interval <timeout>Denotes the period, in milliseconds, for which the NPU waits for an acknowledgement for the MS state change directive. If the NPU does not receive an acknowledegment within this period, it retransmits the state change directive.Optional 10 0-500Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-181.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 278 System Manual4.3.10.9.3 Displaying Configuration Information for the MS State Change FunctionalityTo display configuration information for the MS state change functionality, run the following command:npu# show msscfnNOTERefer to Section 4.3.10.9.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no msscfn [msscrsp-retries] [msscrsp-interval] [sbc-holdtime] [reg-holdtime] [msscdrctv-retries] [msscdrctv-interval]Privilege Level15Command ModesGlobal configuration modeCommand Syntaxnpu# show msscfnPrivilege Level1Display FormatMS State Change Function Configuration :msscrsp-retries = <value>msscrsp-interval = <value>sbc-holdtime = <value>reg-holdtime = <value>msscdrctv-retries = <value>msscdrctv-interval = <valueCommand ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-182.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 279 System Manual4.3.10.10 Configuring the Connectivity Service Network InterfaceThe Connectivity Service Network (CSN) interface provides IP connectivity services for a set of subscribers. The gateway uses the CSN interface for R3 control traffic and R3 data traffic towards the core network. You can configure the parameters for the IP interface to be used as the network interface for R3 control traffic. This section describes the commands to be used for: “Configuring Parameters for the CSN Interface” on page 279“Restoring the Default Configuration Parameters of the CSN Interface” on page 280“Displaying Configuration Information for the CSN Interface” on page 2814.3.10.10.1 Configuring Parameters for the CSN InterfaceTo configure the CSN parameters, run the following command:npu(config)# csnif [ip-intf <ip-intf>] [tun-mtu <size>] [tun-chksm]IMPORTANTSkip this task. The MIP functionality is not supported in the current release.NOTEYou can display configuration information for the CSN Interface. For details, refer to Section 4.3.10.10.3.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# csnif [ip-intf <ip-intf>] [tun-mtu <size>] [tun-chksm]Privilege Level15](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-183.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 280 System Manual4.3.10.10.2 Restoring the Default Configuration Parameters of the CSN InterfaceTo restore the default configuration for the CSN interface, run the following command. This command can also be used to disable the tunnel-checksum feature.npu(config)# no csnif [tun-mtu] [tun-chksm]Syntax Description Parameter Description Presence Default ValuePossible Values[ip-intf <ip-intf>]Denotes a pre-defined IP interface to be used as a network interface for R3 control traffic and R3 data traffic.Note: If you are modifying the CSN interface, save the current configuration (refer Section 4.3.4.1) and reset the NPU (Section 4.2.2.1) for the change to take effect. Mandatory N/A bearer[tun-mtu <size>]Denotes the MTU for the IP-in-IP tunnel (used for R3 data traffic) on this interface.Optional 1450 1 - 232 -1[tun-chksm] Indicates that the tunnel checksum feature is enabled. If this feature is enabled, the checksum of the inner header is to be verified.Optional By default, this feature is disabled.The presence/absence of this parameter indicates that the tunnel checksum feature is enabled/disabled. Command ModesGlobal configuration modeNOTERefer to Section 4.3.10.10.1 for a description and default values of these parameters.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-184.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 281 System Manual4.3.10.10.3 Displaying Configuration Information for the CSN InterfaceTo display configuration information for the CSN interface, run the following command:npu# show csnif4.3.10.11 Configuring Bearer Plane QoS Marking RulesThe bearer plane consists of tunnels between the ASN and CSN, and the BS and the NPU. R3 includes the bearer plane methods such as tunneling for enabling data transfer between the CSN and the ASN. R6 consists of the bearer plane protocols that implement the intra-ASN data path between the BS and the NPU. You can define QoS marking rules for the bearer plane, based on parameters such as traffic priority, and the type of service, media, and interface.Command Syntaxnpu(config)# no csnif [tun-mtu] [tun-chksm]Privilege Level15Command ModesGlobal configuration modeCommand Syntaxnpu# show csnifPrivilege Level1Display FormatCSN Interface Configuration :ip-intf = <value>tun-mtu = <value>tun-chksm = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-185.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 282 System ManualUp to a maximum of 21 Bearer Plane QoS Marking Rules can be defined. 1Enable the bearer plane QoS marking rules configuration mode (refer to Section 4.3.10.11.1)2You can now execute any of the following tasks:»Configure the output parameters for bearer plane QoS marking rules (refer to Section 4.3.10.11.2)»Restore the default parameters for bearer plane QoS marking rules (refer to Section 4.3.10.11.3)3Terminate the bearer plane QoS marking rules configuration mode (refer to Section 4.3.10.11.4)In addition, you can, at any time, display configuration information (refer to Section 4.3.10.11.6)or delete an existing bearer plane QoS marking rule (refer to Section 4.3.10.11.5). 4.3.10.11.1 Enabling the Bearer Plane QoS Marking Rule Configuration Mode\Creating a Bearer Plane QoS Marking RuleTo configure the parameters for the bearer plane QoS marking rules, first enable the bearer plane QoS marking rule configuration mode. Run the following command to enable the bearer plane QoS marking rules configuration mode. You can also use this command to create and enable the configuration mode for a new bearer plane QoS marking rule.npu(config)# bearerqos <qos-alias> [<intf-type((1<R3> - 0<R6> )| 255<ANY>)> <srvc-type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)> <trfc-priority((0-7)|255)> <media-type> ]To configure one or more QoS bearer plane marking rules:NOTEYou can display configuration information for the bearer plane QoS marking rules. For details, refer to Section 4.3.10.11.6.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-186.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 283 System ManualIf you use this command to create a new QoS marking rule, the configuration mode for this rule is automatically enabled, after which you can execute any of the following tasks:Configure the output parameters for bearer plane QoS marking rules (refer to Section 4.3.10.11.2)Restore the default parameters for bearer plane QoS marking rules (refer to Section 4.3.10.11.3)After executing the above tasks, you can terminate the bearer plane QoS marking rules configuration mode (refer to Section 4.3.10.11.4) and return to the global configuration mode.NOTEThe granularity of the QoS definition to be applied to packets transmitted on the bearer plane depends upon the number of parameters that you specify. If any parameter is to be excluded from the definition, specify the value 255 for that parameter.Command Syntaxnpu(config)# bearerqos <qos-alias> [<intf-type((1<R3> - 0<R6>)| 255<ANY>)> <srvc-type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)> <trfc-priority((0-7)|255)> <media-type>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<qos-alias> Denotes the QoS alias of the QoS marking rule for which you want to enable the bearer plane QoS marking rules configuration mode. If you want to create a new QoS marking rule, specify a new alias and define the type of interface, service, and traffic priority that is applicable for that rule.Mandatory N/A String (1 to 11 characters)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-187.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 284 System Manual<intf-type((1<R3> - 0<R6>)| 255<ANY>)>Denotes the type of interface for which you are defining the bearer plane QoS rule.Mandatory when creating a new Bearer Plane QoS Rule.N/A 0: Indicates the R6 (internal) interface1: Indicates the R3 (external interface))255: Indicates that the parameter should be ignored for packets transmitted on both internal and external interfaces.<srvc-type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>Denotes the service type of the service flow (see “Specifying Service Flow Configuration Parameters” on page 341) provided as an input classification parameter for the bearer plane QoS rule. This parameter is used to match the outer-DSCP and VLAN-priority values for a service flowMandatory when creating a new Bearer Plane QoS RuleN/A 0 (UGS)1 (RTVR)2 (NRTVR)3 (BE)4 ERTVR255 (ANY): Indicates that the parameter should be ignored for packets transmitted on both internal and external interfaces.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-188.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 285 System Manual4.3.10.11.2 Configuring the Output Parameters for Bearer Plane QoS Marking RulesAfter enabling the bearer plane QoS marking rules configuration mode you can configure the output parameters that should be applied on packets (that are created using the parameters specified in Section 4.3.10.11.1). Output parameters are a combination of the Outer-DSCP and VLAN priority values. These are populated in the outer DSCP and VLAN priority fields in the IP and Ethernet headers of these packets.<trfc-priority((0-7)|255)>Denotes the traffic priority of the service flow (see “Specifying Service Flow Configuration Parameters” on page 341) provided as an input classification parameter for the bearer plane QoS rule. This parameter is used to match the outer-DSCP and VLAN-priority values for a service flow. Mandatory when creating a new Bearer Plane QoS RuleN/A 0-7, where 7 is highest255 (ANY): Indicates that the parameter should be ignored for packets transmitted on both internal and external interfaces.<media-type> Denotes the media type of the service flow (see “Specifying Service Flow Configuration Parameters” on page 341) provided as an input classification parameter for the bearer plane QoS rule. This parameter is used to match the outer-DSCP and VLAN-priority values for a service flow.Mandatory when creating a new Bearer Plane QoS RuleN/A String (1 to 14 characters) ANY: Indicates that the parameter should be ignored for packets transmitted on both internal and external interfaces.Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-189.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 286 System ManualRun the following command to configure the output parameters for this bearer plane QoS marking rule:npu(config-bqos)# config [ outer-dscp <integer(0-63>] [vlan-priority <integer(0-7>] [qos enable]IMPORTANTEnable the bearer plane QoS marking rule that you are configuring. By default, all bearer plane QoS marking rules are disabled.NOTEYou can display configuration information for the bearer plane QoS marking rules. For details, refer to Section 4.3.10.11.6.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-bqos)# config [outer-dscp <integer(0-63>] [vlan-priority <integer(0-7>] [qos enable]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[outer-dscp <integer(0-63>]Denotes the Differentiated Service Code Point (DSCP) value to be used for marking the packets, if the packet complies with the marking rules specified in Section 4.3.10.11.1.Optional 0 0-63[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 4.3.10.11.1.Optional 0 0-7, where 7 is the highest](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-190.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 287 System Manual4.3.10.11.3 Restoring the Default Configuration Parameters for the Bearer Plane QoS Output Marking RulesRun 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.[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 4.3.10.11.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.Optional By default, the QoS marking rule is disabled.The presence/absence of this flag indicates that this QoS flag is enabled/disabled. Command ModesBearer plane QoS marking rules configuration modeNOTERefer to Section 4.3.10.11.2 for a description and default values of these parameters. Command Syntaxnpu(config-bqos)# no {outer-dscp | vlan-priority | qos enable}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-191.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 288 System Manual4.3.10.11.4 Terminating the QoS Marking Rules Configuration ModeRun the following command to terminate the marking rules configuration mode:npu(config-bqos)# exit4.3.10.11.5 Deleting Bearer Plane QoS Marking RulesRun the following command to delete the a QoS marking rule:npu(config)# no bearerqos [<qos-alias>]Command ModesBearer plane QoS marking rules configuration modeCommand Syntaxnpu(config-bqos)# exitPrivilege Level10Command ModesBearer plane QoS marking rules configuration modeCAUTIONSpecify 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.Command Syntaxnpu(config)# no bearerqos [<qos-alias>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-192.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 289 System Manual4.3.10.11.6 Displaying 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 Parameter Description Presence Default ValuePossible 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.Optional N/A StringCommand ModesGlobal configuration modeCommand Syntaxnpu# show bearerqos [<qos-alias>]Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-193.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 290 System Manual4.3.10.12 Managing Service InterfacesA Service Interface defines the parameters of the interface used by the NPU on the network side for services using the applicable Service Interface.Up to 10 Service Interfaces may be defined. 1Enable the Service Interface configuration mode for the selected Service Interface (refer to Section 4.3.10.12.1)Syntax Description Parameter Description Presence Default ValuePossible 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.Optional N/A StringDisplay FormatBearer QoS Configuration :qos-alias intf-type srvc-type trfc-priority media-type inner-dscp outer-dscp vlan-priority statusvoip <value> <value> <value> <value> <value> <value> enabledCommand ModesGlobal command modeTo configure a Service Interface:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-194.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 291 System Manual2You can now execute any of the following tasks:»Configure one or more of the parameters of the Service Interface (refer to Section 4.3.10.12.2)»Restore the default values of the Service Interface parameters (refer to Section 4.3.10.12.3)» Terminate the Service Interface configuration mode (refer to Section 4.3.10.12.4)In addition, you can, at any time, display configuration information for one or all existing Service Interfaces (refer to Section 4.3.10.12.6) or delete an existing Service Interface (refer to Section 4.3.10.12.5). 4.3.10.12.1 Enabling the Service Interface Configuration Mode\Creating a Service InterfaceTo configure the parameters of a Service Interface, first enable the Service Interface configuration mode for the specific Service Interface. Run the following command to enable the Service Interface configuration mode. You can also use this command to create a new Service Interface. npu(config)# srvc-intf [<string>] [{IP-IP|VLAN|QinQ}]For example, to define a new IP-IP Service Interface named SI1, run the following command: npu(config)# srvc-intf SI1 IP-IPTo enable the configuration mode for an existing Service Interface named SI1, run the following command: npu(config)# srvc-intf SI1If you use this command to create a new Service Interface, the configuration mode for this Service Interface is automatically enabled.After enabling the configuration mode for a Service Interface you can execute any of the following tasks:Configure one or more of the Service Interface parameters (refer to Section 4.3.10.12.2)NOTEThe Bearer IP Interface (refer to “Configuring IP interfaces” on page 158) must be configured prior to creating IP-IP or VLAN service interfaces.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-195.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 292 System ManualRestore the default values of non-mandatory parameters of the Service Interface (refer to Section 4.3.10.12.3)After executing the above tasks, you can terminate the Service Interface configuration mode (refer to Section 4.3.10.12.4) and return to the global configuration mode.4.3.10.12.2 Configuring Service Interface ParametersThis section describes the commands for:“Configuring Parameter for IP-IP Service Interface”“Configuring Parameter for VLAN Service Interface”“Configuring Parameter for QinQ Service Interface”Command Syntaxnpu(config)# srvc-intf [<string>] [{IP-IP|VLAN|QinQ}]Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values[<string>] The Service Interface alias of the Service Interface for which you want to enable the configuration mode. If you want to create a new Service Interface, specify a new alias and define the type of service interface (see below).Mandatory N/A String (1 to 15 characters)[{IP-IP|VLAN|QinQ}]The Service Interface’s type. Optional IP-IP IP-IPVLANQinQCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-196.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 293 System Manual4.3.10.12.2.1 Configuring Parameter for IP-IP Service InterfaceAfter enabling the IP-IP Service Interface configuration mode, run the following command to configure the IP-IP service interface parameters:This command shall configure one or more parameters of the IP-IP Service Interface.npu(config-srvcif-ipip)# config ([descr <string>] [tun-srcaddr <ip4addr>] {tun-dstaddr <ipv4addr>} [tun-mtu <size(556-1804)>] [tun-chksm])Command Syntaxnpu(config-srvcif-ip-ip)# config ([descr <string>] [tun-srcaddr <ip4addr>] {tun-dstaddr <ipv4addr>} [tun-mtu <size(556-1804)>] [tun-chksm])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesconfig ([descr <string>]A description of the Service Interface.Optional null String (up to 70 characters)[tun-srcaddr <ip4addr>]The source IP address that indicates the point of origination of the tunnel for the service interface.Must be the same as the Bearer IP Address.Optional 0.0.0.0 Valid IP Address.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-197.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 294 System Manual4.3.10.12.2.2 Configuring Parameter for VLAN Service InterfaceAfter enabling the VLAN Service Interface configuration mode, run the following command to configure the VLAN service interface parameters:This command shall configure one or more parameters of the VLAN Service Interface.npu(config-srvcif-vlan)# config ([descr <string>] [ServiceIfVlanId <integer(1-4094>] [ServiceIfDfltGwIp <ipv4addr>] [tun-mtu <integer(556-1804)>]){tun-dstaddr <ipv4addr>}The destination IP address that indicates the point of termination of the tunnel for the service interface. Shall be unique among all the Host Interfaces IP's (Bearer, Local-Management, Internal-Management, External-Management) and existing instances of Service Interface’s Tunnel Destination IP Address and Default Gateway IP Address. Shall not be in the subnet of any Mgmt interface (ie. Local, External and Internal).Optional 0.0.0.0 Valid IP Address.[tun-mtu <size(556-1804)>]Denotes the MTU. Optional 1480 556-1804[tun-chksm] Indicates that end-to-end checksumming mechanism on ServiceTunnel Interface is enabled.Optional By default, this feature is disabled.The presence/absence of this flag indicates that this feature is enabled/ disabled.Command ModesIP-IP Service Interface configuration modeCommand Syntaxnpu(config-srvcif-vlan)# config ([descr <string>] [ServiceIfVlanId <integer(1-4094>] [ServiceIfDfltGwIp <ipv4addr>] [tun-mtu <integer(556-1804)>])](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-198.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 295 System ManualPrivilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesconfig [descr <string>] Aa description of the service interface.Optional null String (up to 70 characters)ServiceIfVlanId <integer(1-4094>]A Service Interface VLAN ID shall not conflict with other instances of Service Interface VLAN ID and VLAN IDs of Bearer, Local-Management and External-Management interaces. Shall also not conflict with CVID of any transparent MS.Optional 0 0-9, 11-4094[ServiceIfDfltGwIp <ipv4addr>]The IP Address of the Default Gateway.Shall be unique among all the Host Interfaces IP's (Bearer, Local-Management, Internal-Management, External-Management) and existing instances of Service Interface’s Tunnel Destination IP Address and Default Gateway IP Address.Should be in the same subnet.with the IP Address of the DHCP server/proxy/relay to be assigned to a service group using this service interface. Subnet mask is taken as default subnet mask i.e 255.255.255.0.Optional 0.0.0.0 valid IP address[tun-mtu <integer(556-1804)>] The MTU Optional 1480 556-1804Command ModesVLAN Service Interface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-199.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 296 System Manual4.3.10.12.2.3 Configuring Parameter for QinQ Service InterfaceAfter enabling the QinQ Service Interface configuration mode, run the following command to configure the QinQ service interface parameters:This command shall configure one or more parameters of the QinQ Service Interface.npu(config-srvcif-QinQ)# config ([descr <string>] [ServiceIfVlanId <integer(1-4094>])4.3.10.12.3 Restoring the Default Configuration Parameters for a Service InterfaceThis section describes the commands for:“Restoring the Default Configuration Parameters for an IP-IP Service Interface”“Restoring the Default Configuration Parameters for a VLAN Service Interface”Command Syntaxnpu(config-srvcif-QinQ)# config ([descr <string>] [ServiceIfVlanId <integer(1-4094>]])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesconfig [descr <string>] A description of the service interface.Optional null String (up to 70 characters)ServiceIfVlanId <integer(1-4094>]A Service Interface VLAN ID shall not conflict with other instances of Service Interface VLAN ID and VLAN IDs of Bearer, Local-Management and External-Management interaces. Shall also not conflict with CVID of any transparent MS.Optional 0 0-9, 11-4094Command ModesQinQ Service Interface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-200.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 297 System Manual4.3.10.12.3.1 Restoring the Default Configuration Parameters for an IP-IP Service InterfaceRun the following command to restore the default configuration for IP-IP service interface tun-mtu and/or tun-chksm parameters:npu(config-srvcif-ipip)# no [tun-mtu] [tun-chksm]You can restore only one parameter to its default values by specifying only that parameter. To restore both parameters to their default value, run the command npu(config-srvcif-ipip)# no.4.3.10.12.3.2 Restoring the Default Configuration Parameters for a VLAN Service InterfaceRun the following command to restore the default configuration for a VLAN service interface tun-mtu parameter:npu(config-srvcif-vlan)# no [tun-mtu]NOTERefer to Section 4.3.10.12.2.1 for a description and default values of these parameters. Command Syntaxnpu(config-srvcif-ipip)# no [tun-mtu] [tun-chksm]Privilege Level10Command ModesIP-IP Service Interface configuration modeNOTERefer to Section 4.3.10.12.2.2 for a description and default values of this parameter. Command Syntaxnpu(config-srvcif-vlan)# no [tun-mtu]Privilege Level10Command ModesVLAN Service Interface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-201.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 298 System Manual4.3.10.12.4 Terminating a Service Interface Configuration ModeThis section describes the commands for:“Terminating the IP-IP Service Interface Configuration Mode”“Terminating the VLAN Service Interface Configuration Mode”“Terminating the QinQ Service Interface Configuration Mode”4.3.10.12.4.1 Terminating the IP-IP Service Interface Configuration ModeRun the following command to terminate the IP-IP service interface configuration mode:npu(config-srvcif-ipip)# exit4.3.10.12.4.2 Terminating the VLAN Service Interface Configuration ModeRun the following command to terminate the vlan service interface configuration mode:npu(config-srvcif-vlan)# exitCommand Syntaxnpu(config-srvcif-ipip)# exitPrivilege Level10Command ModesIP-IP Service interface configuration modeCommand Syntaxnpu(config-srvcif-vlan)# exitPrivilege Level10Command ModesVLAN Service interface configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-202.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 299 System Manual4.3.10.12.4.3 Terminating the QinQ Service Interface Configuration ModeRun the following command to terminate the QinQ service interface configuration mode:npu(config-srvcif-QinQ)# exit4.3.10.12.5 Deleting a Service InterfaceYou can, at any time, run the following command to delete service interface:npu(config)# no srvc-intf [<intf-alias>]Command Syntaxnpu(config-srvcif-QinQ)# exitPrivilege Level10Command ModesQinQ Service interface configuration modeNOTEA Service Interface cannot be deleted if it is assigned to any Service Group.A QinQ Service Interface cannot be deleted if it is assigned to a Service Flow (with a VPWS-QinQ Service Group). For details refer to “Configuring Service Flows” on page 339.Command Syntaxnpu(config)# no srvc-intf [intf-alias>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[intf-alias>]The alias of the Service interface which needs to be deletedMandatory N/A String](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-203.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 300 System Manual4.3.10.12.6 Displaying Configuration Information for the Service Interface To display configuration information for one or all service interfaces, run the following command:npu# show srvc-intf <intf-alias>Specify a value for the intf-alias parameter if you want to display configuration information for a particular service interface. Do not specify a value for this parameter if you want to view configuration information for all service interfaces.Command ModesGlobal configuration modeCommand Syntaxnpu# show srvc-intf intf-alias>Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values<intf-alias> The alias of the service interface that you want to display. If you do not specify a value for this parameter, all the services interfaces that are configured, are displayed.Optional N/A StringDisplay FormatIP-IP Service Interface% Asn-gateway Srvc Intf config Srvcif-Alias <string> SrvcifDescr <string> intf-type IP-IP SrvcifTunSrcIpAddr <IP address> SrvcifTunDstIpAddr <IP address> Tunnel-Chksum is <Disable/Enable> TunIPIPMTU <size>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-204.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 301 System Manual4.3.10.13 Configuring the AAA Client FunctionalityThe AAA client functionality enables configuration of one RADIUS client. The RADIUS client encapsulates the messages destined for the AAA server in RADIUS messages or decapsulates messages sent by the AAA server for the MS. The RADIUS client can be assigned an independent self address, primary AAA server address, alternate AAA server address, shared secret, and protocol port. In addition, you can also configure certain RADIUS parameters such as the NAS ID and the time zone offset that are applicable for all AAA clients.This section describes the commands for:“Managing AAA Client Configuration” on page 301“Managing Global RADIUS Configuration Parameters” on page 3074.3.10.13.1 Managing AAA Client Configuration1Enable the AAA client configuration mode (refer to Section 4.3.10.13.1.1)Display FormatVLAN Service Interface% Asn-gateway Srvc Intf config Srvcif-Alias <string> SrvcifDescr <string> intf-type VLAN SrvcifVlanId <vlan id> SrvcifDfltGwIpAddr <IP address> TunIPIPMTU <size>Display FormatQinQ Service Interface% Asn-gateway Srvc Intf config Srvcif-Alias <string> SrvcifDescr <string> intf-type QinQ Q-in-Q SrvcifVlanId <vlan id>Command ModesGlobal command modeTo configure one or more AAA clients:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-205.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 302 System Manual2You can now execute any of the following tasks:»Configure the AAA client parameters (refer to Section 4.3.10.13.1.2)»Restore the default parameters for the AAA client (refer to Section 4.3.10.13.1.3)3Terminate the AAA client configuration mode (refer to Section 4.3.10.13.1.4)In addition, you can, at any time, display configuration information (refer to Section 4.3.10.13.1.6)or delete an existing AAA client (refer to Section 4.3.10.13.1.5). The following example illustrates the (sequence of) commands for enabling the AAA client configuration mode, configuring the parameters of the AAA client, and then terminating the AAA client configuration mode:npu(config)# aaa-client wimaxnpu(config-aaa)# config src-intf eth0 primary-serveraddr 172.16.104.61 auth-port 5678npu(config-aaa)# exit4.3.10.13.1.1 Enabling the AAA Client Configuration Mode\ Creating a New AAA ClientTo configure the AAA client parameters, first enable the AAA client configuration mode. Run the following command to enable the AAA client configuration mode. You can also use this command to create a new AAA client configuration mode.npu(config)# aaa-client <client-alias>In the current release only one AAA client can be created.If you use this command to create a new AAA client, the configuration mode for this AAA client is automatically enabled, after which you can execute any of the following tasks:Configure the AAA client parameters (refer to Section 4.3.10.13.1.2)Restore the default parameters for the AAA client (refer to Section 4.3.10.13.1.3)After executing these tasks, you can terminate the AAA client configuration mode and return to the global configuration mode (refer to Section 4.3.10.13.1.4).](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-206.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 303 System Manual4.3.10.13.1.2 Configuring Parameters for the AAA ClientAfter enabling the AAA client configuration mode, run the following command to configure the parameters for the AAA client:npu(config-aaa)# config [src-intf <ip-intf>] [primary-serveraddr <ipv4addr>] [alternate-serveraddr <ipv4addr>] [rad-sharedsecret <string>] [auth-port <port>] [acct-port <port>]Command Syntaxnpu(config)# aaa-client <client-alias>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<client-alias> Denotes the client-alias of the AAA client for which the configuration mode is to be enabled. If you want to create a new AAA client, specify the client-alias for the AAA client that you want to create.Mandatory N/A StringCommand ModesGlobal configuration modeNOTEYou can display configuration information for a specific or all AAA clients. For details, refer to Section 4.3.10.13.1.6.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-207.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 304 System ManualCommand Syntaxnpu(config-aaa)# config [src-intf <ip-intf>] [primary-serveraddr <ipv4addr>] [alternate-serveraddr <ipv4addr>] [rad-sharedsecret <string>] [auth-port <port>] [acct-port <port>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[src-intf <ip-intf>]Indicates the IP address of the interface providing RADIUS client functionality. Must be the IP address of the Bearer interface.Note: If you are modifying the service interface for the AAA client, save the current configuration (refer Section 4.3.4.1) and reset the NPU (Section 4.2.2.1) for the change to take effect. Mandatory N/A IP address of bearer interface[primary-serveraddr <ipv4addr>]Denotes IPv4 address of the primary AAA server. It is mandatory to specify a value for this parameter if you do not configure an alternate server.Optional 0.0.0.0 Valid IP Address[alternate-serveraddr <ipv4addr>]Denotes IPv4 address of the alternate AAA server.It is mandatory to specify a value for this parameter if you do not configure a primary server.Optional N/A Valid IP Address[rad-sharedsecret <string>]Denotes the shared secret between the AAA client and the AAA server. Mandatory N/A String (1 to 49 characters)[auth-port <port>]Denotes the Authenticator port on which the AAA client listens to and sends RADIUS authentication messages. Optional 1812 0-65535](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-208.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 305 System Manual4.3.10.13.1.3 Restoring the Default Configuration Parameters for the Authentication PortRun the following command to restore the default configuration for the authentication port.npu(config-aaa)# no [primary-serveraddr] [alternate-serveraddr] [auth-port] [acct-port <port>]When you execute this command for restoring the default values, it also deletes the current values for the primary-server and alternate-server address.4.3.10.13.1.4 Terminating the AAA Client Configuration ModeRun the following command to terminate the AAA client configuration mode:npu(config-aaa)# exit[acct-port <port>]Denotes the accounting port on which the AAA client listens to and sends RADIUS accounting messages.Optional 1813 0-65535Command ModesAAA client configuration modeNOTERefer to Section 4.3.10.2.1 for a description and default values of these parameters. Command Syntaxnpu(config-aaa)# no [primary-serveraddr] [alternate-serveraddr] [auth-port] [acct-port <port>]Privilege Level10Command ModesAAA client configuration modeCommand Syntaxnpu(config-aaa)# exitPrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-209.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 306 System Manual4.3.10.13.1.5 Deleting the AAA ClientRun the following command to delete the AAA client:npu(config)# no aaa-client [<client-alias>]4.3.10.13.1.6 Displaying Configuration Information for the AAA Client To display one or all AAA clients, run the following command:npu# show aaa-client [<client-alias>]Specify the AAA client alias if you want to display configuration information for a particular AAA client. Do not specify a value for this parameter if you want to view configuration information for all AAA clients.Command ModesAAA client configuration modeCAUTIONSpecify the AAA client alias if you want to delete a specific AAA client. Otherwise all the configured AAA clients are deleted.In the current release, only one AAA client can be configured.Command Syntaxnpu(config)# no aaa-client [<client-alias>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<client-alias>]Denotes the AAA client that is to be deleted. If you do not specify a value for this parameter, all the existing AAA clients, are deleted.Optional N/A StringCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-210.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 307 System Manual4.3.10.13.2 Managing Global RADIUS Configuration ParametersGlobal RADIUS configuration parameters for AAA clients determine how AAA clients should send access requests. This section describes the commands to be used for: “Configuring Global RADIUS Parameters” on page 308“Restoring the Default Global RADIUS Configuration Parameters” on page 309Command Syntaxnpu# show aaa-client [<client-alias>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<client-alias>]Denotes the client-alias for which the associated AAA client information is to be displayed. Specify a value for this parameter if you want to display information about a specific AAA client.If you want to display information about all AAA clients, do not specify any value for this parameter. Optional N/A StringDisplay FormatAAA Client Configuration :client-alias src-intf primary-servweraddr alternate-serveraddr rad-sharedsecret auth-port acct-port<value> <value> <value> <value> <value> <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-211.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 308 System Manual“Displaying Global RADIUS Configuration Parameters” on page 3104.3.10.13.2.1 Configuring Global RADIUS ParametersTo configure the global RADIUS configuration parameters to be used for all AAA clients, run the following command:npu(config)# radius <[accessreq-retries <retransmissions>] [accessreq-interval <timeout>] [nasid <nas-identifier>] [timezone-offset <time-offset(0-86400)>] [mtu <framed mtu size(1020-2000)>][RadiusAtrbtTypeServiceProfileName <AtrbtTypeId(1-255)>]>NOTEYou can display configuration information for global RADIUS parameters. For details, refer to Section 4.3.10.13.2.3IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# radius <[accessreq-retries <retransmissions>] [accessreq-interval <timeout>] [nasid <nas-identifier>] [timezone-offset <time-offset(0-86400)>] [mtu <framed mtu size(1020-2000)>] [RadiusAtrbtTypeServiceProfileName <AtrbtTypeId(1-255)>]>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[accessreq-retries <retransmissions>]Denotes the maximum number of times the AAA client can resend the access request.Optional 3 0-5[accessreq-interval <timeout>]Denotes the interval, in seconds, after which the AAA client can resend the access request.Optional 500 10-100000](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-212.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 309 System Manual4.3.10.13.2.2 Restoring the Default Global RADIUS Configuration ParametersTo restore the default global RADIUS configuration used for AAA clients, run the following command:npu(config)# no radius [accessreq-retries] [accessreq-interval] [nasid] [timezone-offset] [mtu][nasid <nas-identifier>]Denotes the unique identifier of the ASNGW NAS. Sent in Access Request message only if configured. Should be in FQDN format.Optional null String (up to 64 characters)[timezone-offset <time-offset(0-86400)>]Denotes the time zone offset, in seconds, from GMT at the NAS.Optional 0 0-86400[mtu <framed mtu size(1020-2000)>]Denotes the MTU to be used for the AAA client functionality.Optional 2000 1020-2000[RadiusAtrbtTypeServiceProfileName <AtrbtTypeId(1-255)>]Denotes the RADIUS attribute in which the ASN-GW shall expect to get the service profile name. For example, configure 11 if AAA uses Filter ID as the container of service profile name,Use only unassigned freetext-type RADIUS attributes.Optional 11 1-255Command ModesGlobal configuration modeNOTERefer Section 4.3.10.13.2.1 for a description and default values of these parameters. Command Syntaxnpu(config)# no radius [accessreq-retries] [accessreq-interval] [nasid] [timezone-offset] [mtu]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-213.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 310 System Manual4.3.10.13.2.3 Displaying Global RADIUS Configuration ParametersTo display global RADIUS configuration parameters used for all AAA clients, run the following command:npu# show radius4.3.10.14 Managing Service GroupsA service group is a group of MSs that are served by the same service provider or belong to the same service class. You can configure up to 10 service groups, where each of them is:Associated with a separate service interface (IP Service Groups only).Privilege Level10Command ModesGlobal configuration modeCommand Syntaxnpu# show radiusPrivilege Level1Display FormatRadius Configuration :accessreq-retries = <value>accessreq-interval = <value>nasid = <value>timezone-offset = <value>mtu = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-214.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 311 System ManualConfigured as any one of the following:»DHCP server that allocates an IP address to the MS from the local pool (in the non-HA mode).»DHCP relay that obtains the IP address using an external DHCP server (in the non-HA mode).»DHCP proxy for either of the following boot modes:◊Non-HA mode: The DHCP proxy assigns the MS, the IP address that was received from AAA in the MS profile or ◊HA mode: The DHCP proxy assigns the MS, the IP address received in the MS profile or obtains the IP address from HA using the mobile IP1Enable the service group configuration mode (refer to Section 4.3.10.14.1)2You can now execute any of the following tasks:»Configure the common parameters of a service group (refer to Section 4.3.10.14.2)»Enable the service group operation mode and configure the DHCP server/proxy/relay-specific parameters (refer to Section 4.3.10.14.4.1)3Terminate the service group configuration mode (refer to Section 4.3.10.14.5)In addition, you can, at any time, display configuration information (refer to Section 4.3.10.15.2) or delete an existing service group (refer to Section 4.3.10.14.6). 4.3.10.14.1 Enabling the Service Group Configuration Mode\ Creating a New Service GroupTo configure the parameters for the service group, first enable the service group configuration mode. Run the following command to enable the service group configuration mode or create the service group.npu(config)# srvc-grp <grp-alias> [ServiceGrpType {IP | VPWS-QinQ | VPWS-Transparent}]If you use this command to create a new service group, the configuration mode for this group is automatically enabled after which you can configure or restore the default parameters for this service group.To configure a service group:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-215.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 312 System ManualAfter enabling the service group configuration mode, you can execute any of the following tasks:Configure the common parameters for the service group (refer to Section 4.3.10.14.2)Enable the service group operation mode and configure the DHCP server/proxy/relay-specific parameters (refer to Section 4.3.10.14.4.1)After executing these tasks, you can terminate the service group configuration mode (refer to Section 4.3.10.14.5).NOTEYou can display configuration information for specific or all service groups. For details, refer to Section 4.3.10.15.2.Command Syntaxnpu(config)# srvc-grp <grp-alias> [ServiceGrpType {IP | VPWS-QinQ | VPWS-Transparent}]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<grp-alias> Denotes the group-alias of the service group for which the service group configuration mode is to be enabled. If you want to create a new service group, specify the group alias to be assigned to the srevice group.Mandatory N/A String (1 to 15 characters)[ServiceGrpType {IP | VPWS-QinQ | VPWS-Transparent} ]The Service group’s type. Optional IP IPVPWS-QinQVPWS-Transparent](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-216.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 313 System Manual4.3.10.14.2 Configuring Common Parameters of a Service GroupAfter enabling the service group configuration mode, run the following command to configure common parameters for the service group:npu(config-srvcgrp)# config {{[srvcif-alias <service interface>] [waitdhcp-holdtime <timeout>] [dhcp-ownaddr <ipv4addr>]} | {dhcp-server|dhcp-proxy|dhcp-relay} |{[<ServiceGrpIfAccounting (enable|disable)>]}|{[<ServiceGrpIfMSLoopBack (enable|disable)>]}}This commands comprises 4 sub-commands:1npu(config-srvcgrp)# config {[srvcif-alias <service interface>] [waitdhcp-holdtime <timeout>] [dhcp-ownaddr <ipv4addr>]} 2npu(config-srvcgrp)# config {dhcp-server|dhcp-proxy|dhcp-relay}3npu(config-srvcgrp)# config {[<ServiceGrpIfAccounting (enable|disable)>]}4npu(config-srvcgrp)# config {[<ServiceGrpIfMSLoopBack (enable|disable)>]}Command ModesGlobal configuration modeNOTEThis command is applicable for an IP Service Group. In VPWS-QinQ and VPWS-Transparent Service Groups only the accounting option (ServiceGrpIfAccounting (enable|disable)) is available.NOTEYou can display configuration information for the service group. For details, refer to Section 4.3.10.15.2.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-srvcgrp)# config {{[srvcif-alias <service interface>] [waitdhcp-holdtime <timeout>] [dhcp-ownaddr <ipv4addr>]} | {dhcp-server|dhcp-proxy|dhcp-relay} |{[<ServiceGrpIfAccounting (enable|disable)>]}|{[<ServiceGrpIfMSLoopBack (enable|disable)>]}}](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-217.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 314 System ManualPrivilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[srvcif-alias <service interface>]Denotes the pre-defined service interface alias to be used as the data path for traffic towards the core network.Note that a Service Interface alias can be associated only to a single Service Group.Mandatory N/A String[waitdhcp-holdtime <timeout>]Denotes the period, in seconds, for which the NPU waits for an IP address allocation trigger (MIP registration request / DHCP discover) from the MS. If you specify the value of this parameter as 0, no timer is started and the NPU will wait infinitely for the IP address allocation trigger.Optional 0 0-86400](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-218.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 315 System Manual4.3.10.14.3 Enabling/Disabling VLAN Service InterfaceRun the following commands to enable/disable the creation of a data-path for a VLAN Service:To enable: npu(config-srvcgrp)# config {[serviceVlanEnable]}To disable: npu(config-srvcgrp)# no serviceVlanEnable[dhcp-ownaddr <ipv4addr>]Denotes the IPv4 address of the DHCP server/ relay/ proxy.For a service group using a VLAN service interface, should be in same subnet with the Default Gateway configured for the service interface associated with the service group. Subnet mask is taken as the default subnet mask i.e 255.255.255.0.Note: In DHCP Server mode, the DHCP server IP address must be in the same subnet but outside the range allocated for users address pool as provisioned in the DHCP Server.Mandatory N/A Valid IP Address{dhcp-server|dhcp-proxy|dhcp-relay}Mode of IP address allocation used for subscribers: DHCP Server/ Proxy/ Relay.Mandatory N/A dhcp-serverdhcp-proxydhcp-relay{ServiceGrpIfAccounting {enable| disable}}Denotes whether accounting is enabled or disabled for the service interface.Optional Enable EnableDisable{ServiceGrpIfMsLoopBack {enable| disable}}Denotes whether MS loopback is enabled or disabled for the service interfaceOptional Disable EnableDisableCommand ModesService group configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-219.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 316 System Manual4.3.10.14.4 Configuring the DHCP Server/Proxy/Relay 1Enable the service group operation mode for DHCP server/relay/proxy (refer to Section 4.3.10.14.4.1)2You can now execute one of the following tasks according to the selected DHCP mode:»Configure the DHCP server (refer to Section 4.3.10.14.4.2)»Configure the DHCP proxy (refer to Section 4.3.10.14.4.3)»Configure the DHCP relay (refer to Section 4.3.10.14.4.4)4.3.10.14.4.1 Enabling the Service Group Operation Mode for DHCP Server//Proxy/RelayRun the following command enable the DHCP (server/relay/proxy) configuration mode.npu(config-srvcgrp)# config {dhcp-server|dhcp-proxy|dhcp-relay}When you run this command, the DHCP server/proxy/relay configuration mode is enabled, after which you can execute the following tasks:Configure the DHCP server (refer to Section 4.3.10.14.4.2)Configure the DHCP proxy (refer to Section 4.3.10.14.4.3)Configure the DHCP relay (refer to Section 4.3.10.14.4.4)Command Syntaxnpu(config-srvcgrp)# config {[serviceVlanEnable]}npu(config-srvcgrp)# no [<servicevlanEnable>Privilege Level10Command ModesService group configuration modeTo configure the DHCP server/proxy/relay:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-220.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 317 System Manual4.3.10.14.4.2 Configuring the DHCP ServerAfter enabling the service group operation mode for the DHCP server, you can execute any of the following tasks:“Configuring DHCP Server Parameters” on page 318“Restoring Configuration Parameters for the DHCP Server” on page 320“Configuring Exclude IP Addresses for the DHCP Server” on page 321“Deleting Exclude IP Addresses for the DHCP Server” on page 322NOTEYou cannot modify the configured DHCP mode. To change the DHCP mode you should first delete the Service Group and configure it again.Command Syntaxnpu(config-srvcgrp)# config {dhcp-server|dhcp-proxy|dhcp-relay}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{dhcp-server|dhcp-proxy|dhcp-relay}Indicates whether the service group operation mode is to be enabled for the DHCP server, proxy or relay.Mandatory N/A dhcp-serverdhcp-proxydhcp-relayCommand ModesService group configuration modeNOTEBefore executing these tasks, ensure that you have enabled the DHCP server configuration mode. For details, refer to “Enabling the Service Group Operation Mode for DHCP Server//Proxy/Relay” on page 316.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-221.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 318 System Manual4.3.10.14.4.2.1Configuring DHCP Server ParametersRun the following command to configure the DHCP server:npu(config-srvcgrp-dhcpserver)# config ([pool-minaddr <string>] [pool-maxaddr <string>] [pool-subnet <string>] [dflt-gwaddr <string>] [lease-interval <integer(24-2147483647)>] [renew-interval <integer>] [rebind-interval <integer>] [dnssrvr-addr <string>] [offerreuse-holdtime <integer>] [opt60 <string(30)>] [opt43 {[Name <string(64)>] [Value <string(64)>]}] [Sname <string(64)>] [File <string(128)>])NOTEIf DHCP IP pool (pool-minaddr and/or pool-maxaddr) need to be changed, the service group should be deleted and reconfigured with the new DHCP IP pool.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-srvcgrp-dhcpserver)# config ([pool-minaddr <string>] [pool-maxaddr <string>] [pool-subnet <string>] [dflt-gwaddr <string>] [lease-interval <integer(24-2147483647)>] [renew-interval <integer>] [rebind-interval <integer>] [dnssrvr-addr <string>] [offerreuse-holdtime <integer>] [opt60 <string(30)>] [opt43 {[Name <string(64)>] [Value <string(64)>]}] [Sname <string(64)>] [File <string(128)>])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[pool-minaddr <string>]Denotes the minimum (lowest) IP address of the address pool to be used for address allocation for MSs from this Service Group.Optional 0.0.0.0 Valid IP Address](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-222.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 319 System Manual[[pool-maxaddr <string>] Denotes the maximum (highest) IP address of the address pool configuration.Optional 255.255.255.255Valid IP Address[pool-subnet <string>]The IP subnet mask to be provided by local DHCP Service with IP address for MSs from this Service Group.Optional 255.255.255.255IP subnet[dflt-gwaddr <string>]IP address of Default Gateway to be provided by local DHCP Service with IP address for MS from this Service Group.Optional 0.0.0.0 Valid IP Address[lease-interval <integer(24-2147483647)>]Lease time in seconds of IP address allocated for MS from this Service Group.Optional 86400 24-2147483647[renew-interval <integer>]Denotes the period, after which, the MS can request for renewal of the lease which has expired. Specify the value of this parameter as a percentage of the lease-interval parameterOptional 50 1-100[rebind-interval <integer>] Denotes the rebind interval maintained as a percentage of the lease interval. This is passed to the MS (DHCP client).Optional 75 1-99[dnssrvr-addr <string>]IP Address of the first DNS Server to be provisioned to MS from this Group.tOptional 0.0.0.0 Valid IP Address[offerreuse-holdtime <integer>]Denotes the Offer Reuse time in seconds of IP address offered to MS from this Service Group.Optional 5 1-120[opt60 <string(30)>]Configures option 60.An empty string (null) means that DHCP Option 60 is disabled.Optional <dslforum.org>String (up to 30 characters).Null (empty string) disables Option 60.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-223.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 320 System Manual4.3.10.14.4.2.2Restoring Configuration Parameters for the DHCP Server Run the following command to restore the default values of one or several DHCP server parameters. This command can be used to delete the DNS server address configuration (if specified).npu(config-srvcgrp-dhcpserver)# no [lease-interval] [renew-interval] [rebind-interval] [dnssrvr-addr] [offerreuse-holdtime]Specify one or several parameters to restore the specified parameters to their default values. Do not specify any parameter to restore all of these parameters to their default values.[opt43 {[Name <string(64)>]Configures option 43 Name Optional InternetGatewayDevice.ManagementServer.URLString (up to 64 characters)[Value <string(64)>]Configures option 43 Value Optional empty stringString (up to 64 characters)[Sname <string(64)>]Configures the server host name. This parameter is sent in dhcp-offer / dhcp-ack messages and may be used by certain CPEs.Optional empty stringString (up to 64 characters)[File <string(128)>]Configures the boot file name. This parameter is sent in dhcp-offer / dhcp-ack messages and may be used by certain CPEs.Optional empty stringString (up to 128 characters)Command ModesService Group-DCHP server configuration modeNOTERefer to Section 4.3.10.14.4.2.1 for a description and default values of these parameters. Command Syntaxnpu(config-srvcgrp-dhcpserver)# no [lease-interval] [renew-interval] [rebind-interval] [dnssrvr-addr] [offerreuse-holdtime]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-224.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 321 System Manual4.3.10.14.4.2.3Configuring Exclude IP Addresses for the DHCP ServerRun the following command to configure exclude IP addresses for the DHCP server:npu(config-srvcgrp-dhcpserver)# exclude-addr <no. of Addrs (1-9)> <ipv4addr> [<ipv4addr>] ….In each command you may add up to 9 IP addresses to be excluded. The total number of excluded IP addresses is up to a maximum of 16384.Privilege Level10Command ModesService group-DHCP server configuration modeIMPORTANTAn error may occur if you provide an invalid IP address. Refer the syntax description for more information about the appropriate values and format for configuring this parameters.Command Syntaxnpu(config-srvcgrp-dhcpserver)# exclude-addr <no. of Addrs (1-9)> <ipv4addr> [<ipv4addr>] ….Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<no. of Addrs (1-9)>The number of IP addresses to be excludedMandatory N/A 1-9<ipv4addr> Denotes the exclude IP address that will not be assigned to an MS by the DHCP server.The number of IP address entries must match the value defined by the no. of Addrs parameter.Mandatory N/A Valid IP address](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-225.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 322 System Manual4.3.10.14.4.2.4Deleting Exclude IP Addresses for the DHCP ServerRun the following command to delete one or several excluded IP addresses for the DHCP server: npu(config-srvcgrp-dhcpserver)# no exclude-addr <no. of Addrs (1-9)> <ipv4addr> [<ipv4addr>] …Run the following command (without specifying the parameters) to delete all excluded IP addresses for the DHCP server: npu(config-srvcgrp-dhcpserver)# no exclude-addrThe deleted exclude IP addresses are no longer excluded when the DHCP server allocates the IP addresses. That is, the server may allocate these IP addresses to the MS.Command ModesService group-DCHP server configuration modeCommand Syntaxnpu(config-srvcgrp-dhcpserver)# no exclude-addr no. of Addrs (1-9)> <ipv4addr> [<ipv4addr>] …Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-226.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 323 System Manual4.3.10.14.4.2.5Terminating the DHCP Server Configuration ModeRun the following command to terminate the DHCP server configuration mode: npu(config-srvcgrp-dhcpserver)# exitSyntax Description Parameter Description Presence Default ValuePossible Values<no. of Addrs (1-9)>The number of excluded IP addresses to be deleted.Do not specify any value if you want to remove all the exclude IP addresses specified for that DHCP server.Optional N/A 1-9<ipv4addr> Denotes an IP address that you want to remove from the list of exclude IP addresses. The number of IP address entries must match the value defined by the no. of Addrs parameter.Do not specify any value if you want to remove all the exclude IP addresses specified for that DHCP server.Optional N/A Valid IP addressCommand ModesService group-DHCP server configuration modeCommand Syntaxnpu(config-srvcgrp-dhcpserver)# exitPrivilege Level10Command ModesService group-DHCP server configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-227.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 324 System Manual4.3.10.14.4.3 Configuring the DHCP ProxyAfter enabling the service group operation mode for the DHCP proxy, you can execute the following tasks:“Specifying DHCP Proxy Configuration Parameters” on page 324“Restoring the Default Configuration Parameters for the DHCP Proxy” on page 327“Terminating the DHCP Proxy Configuration Mode” on page 3274.3.10.14.4.3.1Specifying DHCP Proxy Configuration ParametersRun the following command to configure the DHCP proxy:npu(config-srvcgrp-dhcpproxy)# config ([offerreuse-holdtime <integer>] [lease-interval <integer>] [dnssrvr-addr <string>] [pool-subnet <string>] [dflt-gwaddr <string>] [renew-interval <integer>] [rebind-interval <integer>] [opt60 <string(30)>] [opt43 {[Name <string(64)>] [Value <string(64)>]}] [Sname <string(64)>] [File <string(128)>])IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-srvcgrp-dhcpproxy)# config ([offerreuse-holdtime <integer>] [lease-interval <integer>] [dnssrvr-addr <string>] [pool-subnet <string>] [dflt-gwaddr <string>] [renew-interval <integer>] [rebind-interval <integer>] [opt60 <string(30)>] [opt43 {[Name <string(64)>] [Value <string(64)>]}] [Sname <string(64)>] [File <string(128)>])Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-228.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 325 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values[offerreuse-holdtime <integer>] Denotes the duration in seconds within which the MS should send a DHCP request to accept the address sent by the NPU.If the MS does not accept the address within this period, the MS is deregistered.Optional 5 0-120[lease-interval <integer>]Lease time in seconds of IP address allocated for MS from this Service Group. In the Proxy mode, this value is used if appropriate parameter is not received in RADIUS Access-Accept.Optional 86400 24 - 4294967295[dnssrvr-addr <string>]IP Address of the first DNS Server to be provisioned to MS from this Group. In the Proxy mode, this value is used if appropriate parameter is not received in RADIUS Access-AcceptOptional 0.0.0.0 Valid IP Address[pool-subnet <string>]The IP subnet mask to be provided by local DHCP Service with IP address for MSs from this Service Group. In the Proxy mode, this value is used if appropriate parameter is not received in RADIUS Access-Accept.Optional 255.255.255.255IP subnet[dflt-gwaddr <string>]IP address of Default Gateway to be provided by local DHCP Service with IP address for MS from this Service Group. In theProxy mode, this value is used if appropriate parameter is not received in RADIUS Access-Accept.Optional 0.0.0.0 Valid IP Address](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-229.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 326 System Manual[renew-interval <integer>]Denotes the period, after which, the MS can request for renewal of the lease which has expired. Specify the value of this parameter as a percentage of the lease-interval parameter.This value is used if appropriate parameter is not received in RADIUS Access-Accept.Optional 50 1-100[rebind-interval <integer>]Denotes the rebind interval maintained as a percentage of the lease interval. This is passed to the MS (DHCP client).This value is used if appropriate parameter is not received in RADIUS Access-Accept.Optional 75 1-99[opt60 <string(30)>]Configures option 60. Optional <dslforum.org>String (up to 30 characters)[opt43 {[Name <string(64)>]Configures option 43 Name Optional InternetGatewayDevice.ManagementServer.URLString (up to 64 characters)[Value <string(64)>]Configures option 43 Value Optional empty stringString (up to 64 characters)[Sname <string(64)>]Configures the proxy host name. This parameter is sent in dhcp-offer / dhcp-ack messages and may be used by certain CPEs.Optional empty stringString (up to 64 characters)[File <string(128)>]Configures the boot file name. This parameter is sent in dhcp-offer / dhcp-ack messages and may be used by certain CPEs.Optional empty stringString (up to 128 characters)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-230.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 327 System Manual4.3.10.14.4.3.2Restoring the Default Configuration Parameters for the DHCP ProxyRun the following command to restore the default values of one or several DHCP proxy parameters. This command can also be used to delete the configured DNS server address (if specified).npu(config-srvcgrp-dhcpproxy)# no [offerreuse-holdtime] [lease-interval] [dnssrvr-addr][renew-interval] [rebind-interval]Specify one or several parameters to restore the specified parameters to their default values. Do not specify any parameter to restore all of these parameters to their default values.4.3.10.14.4.3.3Terminating the DHCP Proxy Configuration ModeRun the following command to terminate the DHCP proxy configuration mode: npu(config-srvcgrp-dhcpproxy)# exitCommand ModesService group-DHCP proxy configuration modeNOTERefer Section 4.3.10.14.4.3.1 for a description and default values of these parameters. Command Syntaxnpu(config-srvcgrp-dhcpproxy)# no [offerreuse-holdtime] [lease-interval] [dnssrvr-addr][renew-interval] [rebind-interval]Privilege Level10Command ModesService group-DHCP proxy configuration modeCommand Syntaxnpu(config-srvcgrp-dhcpproxy)# exitPrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-231.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 328 System Manual4.3.10.14.4.4 Configuring the DHCP RelayAfter enabling the service group operation mode for the DHCP relay, you can execute any of the following tasks:“Configuring the DHCP Relay Parameters” on page 328“Terminating the DHCP Relay Configuration Mode” on page 3324.3.10.14.4.4.1Configuring the DHCP Relay ParametersRun the following command to configure the DHCP server address for the DHCP relay:npu(config-srvcgrp-dhcprelay)# config ([server-addr <ipV4Addr>] [{EnableOpt82|DisableOpt82}])Command ModesService group-DHCP proxy configuration modeIMPORTANTAn error may occur if you provide an invalid value for the DHCP server address. Refer the syntax description for more information about the appropriate values and format for configuring this parameters.Command Syntaxnpu(config-srvcgrp-dhcprelay)# config ([server-addr <ipV4Addr>] [{EnableOpt82|DisableOpt82}])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[server-addr <ipv4addr>]Denotes the IP address of the external DHCP server,Mandatory N/A Valid IP Address[{EnableOpt82|DisableOpt82}]Denotes whether DHCP option 82 is enabled or disabled.Optional DisableOpt82EnableOpt82DisableOpt82](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-232.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 329 System Manual4.3.10.14.4.4.2Configuring the DHCP Relay Option 82 ParametersIf Option 82 for the DHCP Relay is enabled, run the following command to configure suboptions of option 82 of DHCP messages:npu(config-srvcgrp-dhcprelay-Opt82)# config ([Subopt1value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [Subopt2value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [Subopt6value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [{Subopt7value [service-type] [vendor-specific] [session-timeout]}] [{EnableUnicast|DisableUnicast}])Command ModesService group-DHCP relay configuration modeIMPORTANTFor DhcpRlOpt82SubOpt1BinFrstrng value, enter hex string without spaces. If Opt82Unicast is enabled then DHCP relay agent appends option 82 to all DHCP messages (unicast and broadcast). If Opt82Unicast is disabled (default) then DHCP relay agent appends option 82 only to broadcast DHCP request messages.Command Syntaxnpu(config-srvcgrp-dhcprelay-Opt82)# config ([Subopt1value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [Subopt2value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [Subopt6value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] [{Subopt7value [service-type] [vendor-specific] [session-timeout]}] [{EnableUnicast|DisableUnicast}])Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-233.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 330 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values[Subopt1value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}]Configures the suboption 1 (Agent Circuit ID) of DHCP option 82.For AsciiFrStrng (string enter up to 32 characters,For BinFrStrng (string enter a string of up to 32 hexadecimal digits (no spaces).Optional Not Set DefaultMSIDBSIDNASIDNASIPFull-NAI Domain AsciiFrStrng (string32)BinFrStrng (string32)[Subopt2value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}Configures the suboption 2 (Agent Remote ID) of DHCP option 82. For AsciiFrStrng (string enter up to 32 characters,For BinFrStrng (string enter a string of up to 32 hexadecimal digits (no spaces).Optional Not Set DefaultMSIDBSIDNASIDNASIPFull-NAI Domain AsciiFrStrng (string32)BinFrStrng (string32)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-234.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 331 System Manual[Subopt6value {Default|MSID|BSID|NASID|NASIP|Full-NAI|Domain|AsciiFrStrng <string(32)>|BinFrStrng <string(32)>}] Configures the suboption 6 (Agent Subscriber ID )of DHCP option 82.For AsciiFrStrng (string enter up to 32 characters,For BinFrStrng (string enter a string of up to 32 hexadecimal digits (no spaces).Optional Not Set DefaultMSIDBSIDNASIDNASIPFull-NAI Domain AsciiFrStrng (string32)BinFrStrng (string32)[{Subopt7value [service-type] [vendor-specific] [session-timeout]}]Configures the suboption 7 of DHCP option 82.Allows enabling/disabling the use of suboption 7 by specifying it. In addition, allows enabling/disabling the following attributes (by specifying attributes to be enabled) if suboption 7 is enabled:service-type (attribute 6)vendor-specific (attribute 26)session-timeout (attribute 27)Optional[{EnableUnicast|DisableUnicast}])Indicates whether the Unicast parameter is enabled or disabled.Optional Disable EnableDisableCommand ModeService group-DHCP relay-option 82 configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-235.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 332 System Manual4.3.10.14.4.4.3Removing the DHCP Relay suboption valuesRun the following command to remove one, several or all of the Suboption values configured by the user for DHCP Option 82.npu(config-srvcgrp-dhcprelay-opt82)# no [Subopt1value] [Subopt2value] [Subopt6value] [Subopt7value]4.3.10.14.4.4.4Terminating the DHCP Relay Configuration ModeRun the following command to terminate the DHCP relay configuration mode for this service group: npu(config-srvcgrp-dhcprelay)# exitCommand Syntaxnpu(config-srvcgrp-dhcprelay-opt82)# no [Subopt1value] [Subopt2value] [Subopt6value] [Subopt7value]Privilage Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesno [Subopt1value] [Subopt2value] [Subopt6value] [Subopt7value]Indicates the removal status of DHCP Option 82 suboptions.If no suboption is specified, the values of all suboptions will be removed.Optional N/A N/ACommand ModeService group-DHCP relay-Option 82 configuration modeCommand Syntaxnpu(config-srvcgrp-dhcprelay)# exitPrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-236.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 333 System Manual4.3.10.14.5 Terminating the Service Group Configuration ModeRun the following command to terminate the service group configuration mode:npu(config-srvcgrp)# exit4.3.10.14.6 Deleting a Service GroupYou can, at any time, run the following command to delete a service group:npu(config)# no srvc-grp <grp-alias>Command ModesService group-DHCP relay configuration modeCommand Syntaxnpu(config-srvcgrp)# exitPrivilege Level10Command ModesService group configuration modeNOTEA Service Group cannot be deleted if it is assigned to a Service Flow. For details refer to “Configuring Service Flows” on page 339.Command Syntaxnpu(config)# no srvc-grp <grp-alias>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-237.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 334 System Manual4.3.10.14.7 Displaying Configuration Information for the Service Group To display configuration information for one service group or for all service groups, run the following command:npu# show srvc-grp [<grp-alias>]Syntax Description Parameter Description Presence Default ValuePossible Values<grp-alias> Denotes the group-alias for which the service group to be deleted. Mandatory N/A StringCommand ModesGlobal configuration modeCommand Syntaxnpu# show srvc-grp [<grp-alias>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<grp-alias>] Denotes the group-alias for which the service group to be displayed. If no grp-alias is specified, the parameters of all service groups will be displayed.Optional N/A StringDisplay FormatAccording to configured DHCP mode and other parameters.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-238.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 335 System Manual4.3.10.15 Configuring the Service Flow Authorization FunctionalityThe Service Flow Authorization (SFA) functionality handles creation/ maintenance of pre-provisioned service flows for MS. It maps the AAA parameters (service profile name) received from the AAA server to pre-configured WiMAX-specific QoS parameters in the NPU. The SFA functionality enables you to configure multiple service profiles with multiple service flows and classification rules.This section describes the commands to be used for:“Configuring the SFA PHS Functionality” on page 335“Displaying Configuration Information for the SFA PHS Functionality” on page 336“Configuring Service Profiles” on page 336“Configuring Classification Rules” on page 3554.3.10.15.1 Configuring the SFA PHS Functionality To configure the SFA functionality with respect to PHS Rules, run the following command:To enable PHS: npu(config)# sfa phs-enableTo disable PHS: npu(config)# no sfa phs-enableThe default configuration is PHS Disable. NOTEYou can display configuration information for the SFA functionality. For details, refer Section 4.3.10.15.2.For details on PHS Rules, refer to “Configuring PHS Rules” on page 386.Command Syntaxnpu(config)# sfa phs-enablenpu(config)# no sfa phs-enablePrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-239.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 336 System Manual4.3.10.15.2 Displaying Configuration Information for the SFA PHS FunctionalityTo display the current configuration information for the SFA PHS functionality, run the following command:npu# show sfa4.3.10.15.3 Configuring Service ProfilesThe NPU allows for guaranteed end-to-end QoS for user traffic across the ASN. The QoS approach is connection-oriented, whereby user traffic is classified into "service flows." A service flow is a unidirectional stream of packets, either in the downlink or uplink direction, associated with a certain set of QoS requirements such as maximum latency. The QoS requirements for service flows are derived from "service profiles" defined by the operator. A service profile is a set of attributes shared by a set of service flows. For instance, an operator might define a service profile called "Internet Gold" that will include QoS and other definitions to be applied to service flows associated with users subscribed to the operator's "Internet Gold" service package.The factory default configuration includes an ‘empty” (no defined Service Flows) Service Profile with the name Default. If enabled, it will be used if profile descriptor is missing in service provisioning or if received profile descriptor is disabled. Up to 63 additional Service Profiles may be created.Command ModesGlobal configuration modeCommand Syntaxnpu# show sfaPrivilege Level1Display FormatSFA Configuration :PHS <Enable/Disable>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-240.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 337 System Manual1Enable the service profile configuration mode (refer to Section 4.3.10.15.3.1)2You can now execute any of the following tasks:»Configure the parameters for this service profile (refer to Section 4.3.10.15.3.2)»Manage service flow configuration for this service profile (refer to Section 4.3.10.15.3.3)»Delete service flows (refer to Section 4.3.10.15.3.3.7)3Terminate the service profile configuration mode (refer to Section 4.3.10.15.3.4)You can, at any time, display configuration information (refer to Section 4.3.10.15.3.5) or delete an existing service profile (refer to Section 4.3.10.15.3.6). 4.3.10.15.3.1 Enabling the Service Profile Configuration Mode\Creating a New Service ProfileTo configure the parameters for a service profile, first enable the service profile configuration mode. Run the following command to enable the service profile configuration mode. You can also use this command to create a new service profile.npu(config)# srvc-profile <profile-name>If you use this command to create a new service profile, the configuration mode for this rule is automatically enabled, after which you can execute any of the following tasks:Configure the parameters for this service profile (refer to Section 4.3.10.15.3.2)Manage service flow configuration for this service profile (refer to Section 4.3.10.15.3.3)Delete service flows (refer to Section 4.3.10.15.3.3.7)After you have executed these tasks, terminate the service profile configuration mode (refer to Section 4.3.10.15.3.4) to return to the service group configuration mode.To configure one or more service profiles:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-241.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 338 System Manual4.3.10.15.3.2 Enabling/Disabling the Service ProfileAfter enabling the service profile configuration mode, run the following command to enable this service profile:npu(config-srvcprfl)# config profile-enableA service profile can be enabled only if at least one service flow is configured.To disable this service profile, run the following command:npu(config-srvcprfl)# no profile-enable The default mode is Disabled.Command Syntaxnpu(config)# srvc-profile <profile-name>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<profile-name> Denotes the name of the service profile for which the configuration mode is to be enabled. If you are creating a new service profile, specify the name of the new service profile. The configuration mode is automatically enabled for the new service profile.Mandatory N/A String (1 to 11 characters)Command ModesGlobal configuration modeNOTEYou can display configuration information for specific or all service profiles. For details, refer to Section 4.3.10.15.3.5.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-242.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 339 System Manual4.3.10.15.3.3 Configuring Service Flows Service flows are unidirectional stream of packets, either in the downlink or uplink direction, associated with a certain set of QoS requirements such as maximum latency and minimum rate. Based on certain classification rules, service flows are transported over the R1 air interface in 802.16e connections, identified by connection IDs, and identified by GRE keys over the R6 interface in GRE tunnels. In addition, the ASN-GW can mark outgoing traffic in the R3 interface for further QoS processing within the CSN. Up to 12 Service Flows can be defined for each Service Profile.1Enable the service flow configuration mode (refer to Section 4.3.10.15.3.3.1)2You can now execute any of the following tasks:»Configure the parameters for this service flow (refer to Section 4.3.10.15.3.3.2)»Restore the default parameters for this service flow (refer to Section 4.3.10.15.3.3.3)»Configure uplink/downlink classification rule names (refer to Section 4.3.10.15.3.3.4)3Terminate the service flow configuration mode (refer to Section 4.3.10.15.3.3.6)You can, at any time delete an existing service flow (refer to Section 4.3.10.15.3.3.7). Command Syntaxnpu(config-srvcprfl)# config profile enablenpu(config-srvcprfl)# config profile enablePrivilege Level10Command ModesService profile configuration modeAfter enabling the service profile configuration mode, execute the following tasks to configure service flows within this service profile:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-243.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 340 System Manual4.3.10.15.3.3.1Enabling the Service Flow Configuration Mode\ Creating a New Service FlowTo configure the parameters for a service flow, first enable the service flow configuration mode. Run the following command to enable the service flow configuration mode. You can also use this command to create a new service flow.npu(config-srvcprfl)# flow [<flow-id (1-255)] [ServiceGrpAlias <srvc-grp-alias>] [ServiceIfAlias <string>]If you use this command to create a new service flow, the configuration mode for this service flow is automatically enabled, after which you can execute any of the following tasks:Configure the parameters for this service flow (refer to Section 4.3.10.15.3.3.2)Restore the default parameters for this service flow (refer to Section 4.3.10.15.3.3.3)Configure uplink/downlink classification rule names (refer to Section 4.3.10.15.3.3.4)After you have executed these tasks, you can terminate the service flow configuration mode, and return to the service profile configuration mode (refer to Section 4.3.10.15.3.3.6).Command Syntaxnpu(config-srvcprfl)#flow [<flow-id (1-255)] [ServiceGrpAlias <srvc-grp-alias>] [ServiceIfAlias <string>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-244.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 341 System Manual4.3.10.15.3.3.2Specifying Service Flow Configuration ParametersAfter enabling the service flow configuration mode, run the following command to configure the parameters for this service flow:npu(config-srvcprfl-flow)# config ([flow-type <type (1)>] [cs-type <type (1 | 4)>] [media-type <string>] [uldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>] Syntax Description Parameter Description Presence Default ValuePossible Valuesflow [<flow-id (1-255)]Denotes the flow ID of the service flow for which the service flow configuration mode is to be enabled. If you are creating a new service flow, specify the service flow ID of the new service flow. The configuration mode is automatically enabled for the new service flow. Mandatory N/A 1-255[ServiceGrpAlias <srvc-grp-alias>]Indicates the Reference Name for an existing service group to be used by the service flow. VPWS-QinQ and VPWS Transparent Service Groups are applicable only for Service Flows of the Default Service Profile.Mandatory when creating a new flowN/A An existing Service Group Alias.[ServiceIfAlias <string>]Indicates the Reference Name for an existing QinQ service interface.Applicable only if the assigned Service Group is of type VPWS-QinQ (in a VLANCS Service Flow of the Default Service Profile).Mandatory when creating a new flow, only if the type of the specified ServiceGrpAlias is VPWS-QinQ.N/A An existing QinQ Service Interface.Command ModesService profile configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-245.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 342 System Manual[ulqos-maxsustainedrate <value(10000-10000000)>] [ulqos-trafficpriority <value(0-7)>] [dldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>] [dlqos-maxsustainedrate <value(10000-10000000)>] [dlqos-trafficpriority <value(0-7)>] [ulSfQosMinReservedRate <integer>] [ulSfQosMaxLatency <integer>] [ulSfQosToleratedJitter <integer)>] [ulSfQosUnsolicitedGrantInterval <integer(0-65535)>] [ulSfQosSduSize <integer(0-255)>] [dlSfQosMinReservedRate <integer>] [dlSfQosMaxLatency <integer>] [dlSfQosToleratedJitter <integer>] [dlSfQosSduSize <integer(0-255)>])IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-srvcprfl-flow)# config ([flow-type <type (1)>] [cs-type <type (1 | 4)>] [media-type <string>] [uldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>] [ulqos-maxsustainedrate <value(10000-10000000)>] [ulqos-trafficpriority <value(0-7)>] [dldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>] [dlqos-maxsustainedrate <value(10000-10000000)>] [dlqos-trafficpriority <value(0-7)>] [ulSfQosMinReservedRate <integer>] [ulSfQosMaxLatency <integer>] [ulSfQosToleratedJitter <integer)>] [ulSfQosUnsolicitedGrantInterval <integer(0-65535)>] [ulSfQosSduSize <integer(0-255)>] [dlSfQosMinReservedRate <integer>] [dlSfQosMaxLatency <integer>] [dlSfQosToleratedJitter <integer>] [dlSfQosSduSize <integer(0-255)>])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[flow-type <type (1)>] Denotes the type of flow, that is, bi-directional (1) or multicast (2).multicast (2) is not supported in current release.Optional 1 1: Indicates bi-directional](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-246.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 343 System Manual[cs-type <type (1 | 4)>]Convergence Sublayer Type. This parameter is applied to both UL and DL Service Flows.Must match the type of service group referenced by ServiceGrpAlias during creation of the flow: IPv4CS should be selected if the assigned Service Group is .of type IP. VLANCS should be selected if the assigned Service Group is either VPWS-Transparent or VPWS-QinQ.Optional 1 (IPv4CS)1: IPv4CS. 4: VLANCS [media-type <string>]Describes the type of media carried by the service flow.Optional Null String, up to 32 characters[uldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>]Denotes the data delivery type for uplink traffic carried by the service flow. Optional 3 (BE) 0-4 or 255 for ANY.[ulqos-maxsustainedrate <value(10000-10000000)>]Denotes the maximum sustained traffic rate, in bps, for uplink traffic carried by the service flow.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (NRTVR, RTVR, BE, ERTVR, ANY)Optional 250000 10000-10000000 bps[ulqos-trafficpriority <value(0-7)>]Denotes the traffic priority to be applied to the uplink traffic carried by the service flow.Optional 0 0-7, where 0 is lowest and 7 is highest](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-247.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 344 System Manual[dldatadlvry-type <type(0<UGS> | 1<RTVR> | 2<NRTVR> | 3<BE> | 4<ERTVR> | 255<ANY>)>]Denotes the data delivery type for the downlink traffic carried by the service flow. Optional 3 (BE) 0-4 or 255 for ANY.[dlqos-maxsustainedrate <value(10000-10000000)>]Denotes the maximum sustained traffic rate, in bps, for the downlink traffic carried by the service flow.Although available for all service flows, applicable only for service flows with the appropriate downlink data delivery type (NRTVR, RTVR, BE, ERTVR, ANY)Optional 250000 10000-10000000 bps[dlqos-trafficpriority <value(0-7)>]Denotes the traffic priority to be applied to the downlink traffic carried by the service flow.Optional 0 0-7, where 7 is highest[ulSfQosMinReservedRate <integer>]tthe minimum rate in bps reserved for this uplink service flow.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (UGS, NRTVR, RTVR, ERTVR).For NRTVER, RTVR and ERTVR-cannot be higher than ulqos-maxsustainedrate.Optional 250000 0- 10000000](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-248.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 345 System Manual[ulSfQosMaxLatency <integer>]The maximum latency in ms allowed in the uplink.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (UGS, RTVR, ERTVR).If uplink data delivery type is ERTVR or UGS,the default value should be 90ms.Optional 500 0- 4294967295[ulSfQosToleratedJitter <integer)>]the maximum delay variation (jitter) in milliseconds for this uplink service flow.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (UGS, ERTVR)Optional 0 0- 4294967295[ulSfQosUnsolicitedGrantInterval <integer(0-65535)>]The nominal interval in ms between successive data grant opportunities for this uplink service flow.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (UGS, RTVR, ERTVR).Must be lower than ulSfQosMaxLatency.Optional 20 0-65535[ulSfQosSduSize <integer(0-255)>]Represents the number of bytes in the fixed size SDU. This parameter may be used for a UGS service flow when the length of IP packets on the data plane is fixed and known in advance.Although available for all service flows, applicable only for service flows with the appropriate uplink data delivery type (UGS).Optional 49 0-255](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-249.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 346 System Manual[dlSfQosMinReservedRate <integer>]tthe minimum rate in bps reserved for this downlink service flow.Although available for all service flows, applicable only for service flows with the appropriate downlink data delivery type (UGS, NRTVR, RTVR, ERTVR)For NRTVER, RTVR and ERTVR-cannot be higher than dlqos-maxsustainedrate.Optional 250000 0- 10000000[dlSfQosMaxLatency <integer>]The maximum latency in ms allowed in the downlink.Although available for all service flows, applicable only for service flows with the appropriate downlink data delivery type (UGS, RTVR, ERTVR).If uplink data delivery type is ERTVR or UGS,the default value should be 90ms.Optional 500 0- 4294967295[dlSfQosToleratedJitter <integer)>]the maximum delay variation (jitter) in milliseconds for this downlink service flow.Although available for all service flows, applicable only for service flows with the appropriate downlink data delivery type (UGS, ERTVR)Optional 0 0- 4294967295[dlSfQosSduSize <integer(0-255)>]Represents the number of bytes in the fixed size SDU. This parameter may be used for a UGS service flow when the length of IP packets on the data plane is fixed and known in advance.Although available for all service flows, applicable only for service flows with the appropriate downlink data delivery type (UGS).Optional 49 0-255](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-250.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 347 System Manual4.3.10.15.3.3.3Restoring the Default Service Flow Configuration ParametersRun the following command to restore the default values of one or several parameters for this service flow:npu(config-srvcprfl-flow)# no [cs-type] [media-type] [uldatadlvry-type] [ulqos-maxsustainedrate] [ulqos-trafficpriority] [dldatadlvry-type] [dlqos-maxsustainedrate] [dlqos-trafficpriority][ulSfQosMinReservedRate] [ulSfQosMaxLatency] [ulSfQosToleratedJitter] [ulSfQosUnsolicitedGrantInterval] [ulSfQosSduSize] [dlSfQosMinReservedRate] [dlSfQosMaxLatency] [dlSfQosToleratedJitter] [dlSfQosSduSize]Do not specify ant parameter to restore all parameters to their default values.Command ModesService profile-service flow configuration modeNOTERefer to Section 4.3.10.15.3.3.2 for a description and default values of these parameters. Command Syntaxnpu(config-srvcprfl-flow)# no [cs-type] [media-type] [uldatadlvry-type] [ulqos-maxsustainedrate] [ulqos-trafficpriority] [dldatadlvry-type] [dlqos-maxsustainedrate] [dlqos-trafficpriority][ulSfQosMinReservedRate] [ulSfQosMaxLatency] [ulSfQosToleratedJitter] [ulSfQosUnsolicitedGrantInterval] [ulSfQosSduSize] [dlSfQosMinReservedRate] [dlSfQosMaxLatency] [dlSfQosToleratedJitter] [dlSfQosSduSize]Privilege Level10Command ModesService profile-service flow configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-251.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 348 System Manual4.3.10.15.3.3.4Configuring Uplink/Downlink Classification Rule NamesAfter enabling the service flow configuration mode, run the following commands to configure up to a maximum of 6 uplink and 6 downlink classification rules:npu(config-srvcprfl-flow)# ulclsf-rulename <num_of_rule_names (1-6)> <rulename> [<rulename>] [...]npu(config-srvcprfl-flow)# dlclsf-rulename <num_of_rule_names (1-6)> <rulename> [<rulename>] [...]After you have executed these tasks, you can terminate the service flow configuration mode, and return to the service profile configuration mode (Section 4.3.10.15.3.3.6). For more information about configuring classification rules, refer “Configuring Classification Rules” on page 355.Command Syntaxnpu(config-srvcprfl-flow)# ulclsf-rulename <num_of_rule_names (1-6)> <rulename> [<rulename>] [...]npu(config-srvcprfl-flow)# dlclsf-rulename <num_of_rule_names (1-6)> <rulename> [<rulename>] [...]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<num_of_rule_names (1-6)>Indicates the number of uplink/downlink classification rules to be createdMandatory N/A 1-6](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-252.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 349 System Manual4.3.10.15.3.3.5Deleting Uplink/Downlink Classification Rule NamesAfter enabling the service flow configuration mode, run the following commands to delete uplink/downlink classification rules:npu(config-srvcprfl-flow)# no ulclsf-rulename [<num_of_rulenames (1-6)> <rulename> [<rulename>] ...]npu(config-srvcprfl-flow)# no dlclsf-rulename [<num_of_rulenames (1-6)> <rulename> [<rulename>] ...]After you have executed these commands, you can terminate the service flow configuration mode, and return to the service profile configuration mode (refer to Section 4.3.10.15.3.3.6)<rulename> Indicates the name of the uplink/downlink classification rule to be linked to this service flow. Use the classification rule name to reference the appropriate classification rule.For VLANCS service flows the linked uplink and downlink classification rules should be the same. This is because the VLANCS classificaion rules define the CVID (Customer VLAN ID), that should be the same for uplink and downlink flows.The number of rule name entries must match the number defined in num_of_rule_names.For more information about creating classification rules, refer to Section 4.3.10.15.4.1.Mandatory N/A Valid classification rule nameCommand ModesService profile-service flow configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-253.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 350 System Manual4.3.10.15.3.3.6Terminating the Service Flow Configuration ModeRun the following command to terminate the service flow configuration mode:npu(config-srvcprfl-flow)# exitCommand Syntaxnpu(config-srvcprfl-flow)# no ulclsf-rulename [<num_of_rulenames (1-6)> <rulename> [<rulename>] ...]npu(config-srvcprfl-flow)# no dlclsf-rulename [<num_of_rulenames (1-6)> <rulename> [<rulename>] ...]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<num_of_rulenames (1-6)>Indicates the number of uplink/downlink classification rules to be deleted.Mandatory N/A 1-6<rulename> Indicates the name of the uplink/downlink classification rule to be deleted from to this service flow. Use the classification rule name to reference the appropriate classification rule.The number of rule name entries must match the number defined in num_of_rule_names.Mandatory N/A Valid classification rule nameCommand ModesService profile-service flow configuration modeCommand Syntaxnpu(config-srvcprfl-flow)# exit](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-254.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 351 System Manual4.3.10.15.3.3.7Deleting Service FlowsYou can, at any time, run the following command to delete one or all service flows:npu(config-srvcprfl)# no flow [<flow-id>]4.3.10.15.3.4 Terminating the Service Profile Configuration ModeRun the following command to terminate the service profile configuration mode:Privilege Level10Command ModesService profile-service flow configuration modeCAUTIONSpecify the flow ID if you want to delete a specific service flow. Otherwise all the configured service flows are deleted.Command Syntaxnpu(config-srvcprfl)# no flow [<flow-id>]Privilege Level10Command Syntaxnpu(config-srvcprfl)# no flow [<flow-id>]Syntax Description Parameter Description Presence Default ValuePossible Values[<flow-id>] Denotes the flow ID of the service flow to be deleted. If you do nort specify a value for this parameter, all the service flows are deleted.Optional N/A 0-232Command ModesService profile configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-255.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 352 System Manualnpu(config-srvcprfl)# exit4.3.10.15.3.5 Displaying Configuration Information for Service Profiles To display all or specific service profiles, run the following command:npu# show srvc-profile [<profile-name>]Specify the profile name if you want to display configuration information for a particular service profile. Do not specify a value for this parameter if you want to view configuration information for all service profile.Command Syntaxnpu(config-srvcprfl)# exitPrivilege Level10Command ModesService profile configuration modeIMPORTANTAn error may occur if you provide an invalid service profile name. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu# show srvc-profile [<profile-name>]Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-256.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 353 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values[<profile-name>]Indicates the name of the service profile for which configuration information is to be displayed. If you do not specify a value for this parameter, configuration information is displayed for all service profiles.Optional N/A String](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-257.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 354 System ManualDisplay FormatSrvc Profile <value>status <value>flow-id <value>flow-type <value>srvc-grp <value>Service-If <value or null>CS-type <value>Media-Type <value>UL-flowDataDeliveryType <value>UL-flowQosMaxSustainedRate <value>UL-flowQosTrafficPrority <value>DL-flowDataDeliveryType <value>DL-flowQosMaxSustainedRate <value>DL-flowQosTrafficPrority <value>UL-MinReservedTrafficRate <value>UL-MaxLatencey <value>UL-ToleratedJitter <value>UL-UnsolicitedGrantInterval <value>UL-SduSize <value>DL-MinReservedTrafficRate <value>DL-MaxLatencey <value>DL-ToleratedJitter <value>DL-UnsolicitedGrantInterval <value>DL-SduSize <value>UL-Rulenames :<value>, <value>.....DL-Rulenames :<value>, <value>....flow-id <value>............ Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-258.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 355 System Manual4.3.10.15.3.6 Deleting Service ProfilesRun the following command to delete one or all service profiles:npu(config)# no srvc-profile [<profile-name>]4.3.10.15.4 Configuring Classification RulesClassification rules are user-configurable rules that are used to classify packets transmitted on the bearer plane. You can associate one or more classification rules with a particular service profile (For details, refer to Section 4.3.10.15.3.3.4). You can define an L3 classification rule with respect to the following criteria:IP ToS/DSCPIP protocol (such as UDP or TCP)NOTEThe Default Service Profile cannot be deleted.CAUTIONSpecify the profile name if you want to delete a specific service profile. Otherwise all the configured service profiles (excluding the Default Service Profile) are deleted.Command Syntaxnpu(config)# no srvc-profile [<profile-name>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<profile-name>]Denotes the name of the service profile you want to delete. Specify this parameter only if you want to delete a specific service profile.Optional N/A StringCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-259.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 356 System ManualIP source address (an address mask can be used to define a range of addresses or subnet)IP destination address (an address mask can be used to define a range of addresses or subnet)Source port rangeDestination port range You can define an L2 classification rule based on the Customer VLAN ID (CVID).Classification rules can be specified for:Downlink data is classified by the ASN-GW into GRE tunnels, which, in turn, are mapped into 802.16e connections in the air interfaceUplink data is classified by the MS into 802.16e connections, and with respect to classification rules defined in the service profile provisioned in the ASN-GW and downloaded to the MS when establishing a connection.For instance, you can define an L3 downlink classification rule that will classify traffic to a certain MS with a DSCP value of 46 into a UGS connection, and all other traffic to the MS into a best effort connection. In addition, an uplink L3 classification rule can be defined that will classify traffic from this MS with a UDP destination port higher than 5000 into a UGS connection, and all other traffic from the MS into a best effort connection. Up to a maximum of 100 classification rules can be created.1Enable the L3 classification rules configuration mode (refer to Section 4.3.10.15.4.1)To configure one or more L3 classification rules:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-260.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 357 System Manual2You can now execute any of the following tasks:»Configure the parameters for this classification rule (refer to Section 4.3.10.15.4.2)»Restore the default parameters for this classification rule (refer to Section 4.3.10.15.4.3)»Manage protocol configuration (refer to Section 4.3.10.15.4.4)»Manage source address configuration (seeSection 4.3.10.15.4.5)»Manage destination address configuration (refer to Section 4.3.10.15.4.6)»Manage source port configuration (refer to Section 4.3.10.15.4.7)»Manage destination port configuration (refer to Section 4.3.10.15.4.8)3Terminate the L3 classification rules configuration mode (refer to Section 4.3.10.15.4.9)You can, at any time, display configuration information (refer to Section 4.3.10.15.4.13) or delete an existing classification rule (refer to Section 4.3.10.15.4.14), protocol lists (refer to Section 4.3.10.15.4.4.5), source addresses (refer to Section 4.3.10.15.4.5.5), destination addresses (refer to Section 4.3.10.15.4.6.5), source ports (refer to Section 4.3.10.15.4.7.5), or destination ports (refer to Section 4.3.10.15.4.8.5) configured for this classification rule.1Enable the L2 classification rules configuration mode (refer to Section 4.3.10.15.4.1)2You can now execute any of the following tasks:»Configure the parameters for this classification rule (refer to Section 4.3.10.15.4.10)»Clear the configuration of this classification rule (refer to Section 4.3.10.15.4.11)»Terminate the L2 classification rules configuration mode (refer to Section 4.3.10.15.4.12)To configure one or more L2 classification rules:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-261.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 358 System ManualYou can, at any time, display configuration information (refer to Section 4.3.10.15.4.13) or delete an existing classification rule (refer to Section 4.3.10.15.4.14).4.3.10.15.4.1 Enabling the Classification Rule Configuration Mode\ Creating a New Classification RuleTo configure the parameters for a classification rule, first enable the classification rule configuration mode. Run the following command to enable the classification rule configuration mode. You can also use this command to create a new classification rule.npu(config)# clsf-rule <rulename> [clsfRuleType {L2 | L3}]If you use this command to create a new classification rule, the configuration mode for this rule is automatically enabled.After enabling the classification rule configuration mode for an L3 rule you can execute any of the following tasks:Configure the parameters for this classification rule (refer to Section 4.3.10.15.4.2).Restore the default parameters for this classification rule (refer to Section 4.3.10.15.4.3)Manage protocol configuration (refer to Section 4.3.10.15.4.4)Manage source address configuration (refer to Section 4.3.10.15.4.5)Manage destination address configuration (refer to Section 4.3.10.15.4.6)Manage source port configuration (refer to Section 4.3.10.15.4.7)Manage destination port configuration (refer to Section 4.3.10.15.4.8)After you have executed these tasks, you can terminate the classification rules configuration mode (refer to Section 4.3.10.15.4.9).After enabling the classification rule configuration mode for an L2 rule you can execute any of the following tasks:Configure the parameters for this classification rule (refer to Section 4.3.10.15.4.10).](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-262.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 359 System ManualClear the current configuration of this classification rule (refer to Section 4.3.10.15.4.11)After you have executed these tasks, you can terminate the classification rules configuration mode (refer to Section 4.3.10.15.4.12).4.3.10.15.4.2 Specifying Configuration Parameters for the L3 Classification RuleAfter enabling the classification rules configuration mode for an L3 classification rule, run the following command to configure the parameters for this classification rule:npu(config-clsfrule)# config [priority <priority(0-255)>] [phs-rulename <rulename>] [iptos-low <value(0-63)>] [iptos-high <value(0-63)>] [iptos-mask <value(0-63)>] [iptos-enable]Command Syntaxnpu(config)# clsf-rule <rulename> [clsfRuleType {L2 | L3}]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<rulename> Denotes the name of the classification rule. Mandatory N/A String (1 to 11 characters)[clsfRuleType {L2 | L3}]The type of classifier: L2 or L3.Optional when creating a new rule.L3 L2L3Command ModesGlobal configuration modeNOTEYou can display configuration information for specific or all classification rules. For details, refer to Section 4.3.10.15.4.13.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-263.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 360 System ManualCommand Syntaxnpu(config-clsfrule)# config [priority <priority(0-255)>] [phs-rulename <rulename>] [iptos-low <value(0-63)>] [iptos-high <value(0-63)>] [iptos-mask <value(0-63)>] [iptos-enable]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values [priority <priority(0-255)>] Denotes the priority level to be assigned to the classification rule.Optional 0 0-255[phs-rulename <rulename>] Indicates the Packet Header Suppression (PHS) rule name to be associated with the classification rule. Specify the PHS rulename if you want to perform PHS for this flow. For more information about configuring PHS rules, refer Section 4.3.10.16.Optional None StringAn existing PHS rule name.[iptos-low <value(0-63)>] Denotes the value of the lowest IP TOS field to define the lowest value where the range can begin.Optional 0 0-63[iptos-high <value(0-63)>] Denotes the value of highest IP TOS field to define the highest value where the range can end.Optional 0 0-63[iptos-mask <value(0-63)>] Denotes the mask for IP TOS value.This mask is applied to the TOS field received in the IP header to be matched within the TOS range configured.Optional 0 0-63](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-264.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 361 System Manual4.3.10.15.4.3 Restoring the Default Parameters for the L3 Classification RuleRun the following command to restore the default configuration for this classification rule.npu(config-clsfrule)# no [priority] [iptos-low] [iptos-high] [iptos-mask] [iptos-enable][phs-rulename]4.3.10.15.4.4 Managing Protocol Configuration for the L3 Classification RuleL3 classification rules can classify the packet, based on the value of IP protocol field. You can configure the value of IP protocol for a given classification rule.1Enable the IP protocol configuration mode (refer to Section 4.3.10.15.4.4.1)[iptos-enable] Indicates whether the use of TOS-based classification is to be enabled.Optional By default, the use of TOS-based classification is disabled.The presence/absence of this flag indicates that the use of TOS-based classification should be enabled/disabled. Command ModesL3 Classification rules configuration modeNOTERefer to Section 4.3.10.15.4.3 for a description and default values of these parameters. Command Syntaxnpu(config-clsfrule)# no [priority] [iptos-low] [iptos-high] [iptos-mask] [iptos-enable] [phs-rulename]Privilege Level10Command ModesL3 Classification rules configuration modeTo configure one or more IP protocols:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-265.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 362 System Manual2Enable/disable protocol lists (refer to Section 4.3.10.15.4.4.2 and Section 4.3.10.15.4.4.3)3Terminate the protocol configuration mode (refer to Section 4.3.10.15.4.4.4)In addition, you can, at any time, delete an existing protocol list (refer to Section 4.3.10.15.4.4.5). The following example illustrates the (sequence of) commands for enabling the IP protocol configuration mode, enabling IP protocol 100, and then terminating the protocol lists configuration mode:npu(config-clsfrule)# ip-protocolnpu(config-clsfrule-protocol)# protocol-enable 1 100npu(config-clsfrule-protocol)# exit4.3.10.15.4.4.1Enabling the IP Protocol Configuration ModeRun the following command to enable the IP protocol configuration mode. npu(config-clsfrule)# ip-protocolYou can now enable or disable a protocol list (refer to Section 4.3.10.15.4.4.2 and Section 4.3.10.15.4.4.3).4.3.10.15.4.4.2Enabling Protocol ListsAfter enabling the protocol configuration mode, run the following command to enable one or more IP protocol lists:npu(config-clsfrule-protocol)# protocol-enable <number of protocols(1-6)> <protocol1> [<protocol2>] [...]Command Syntaxnpu(config-clsfrule)# ip-protocolPrivilege Level10Command ModesL3 Classification rules configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-266.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 363 System Manual4.3.10.15.4.4.3Disabling Protocol ListsAfter enabling the protocol configuration mode, run the following command to disable one or more IP protocol lists:npu(config-clsfrule-protocol)# no protocol-enable <number of protocols(1-6)> <protocol1> [<protocol2>] [...]Command Syntaxnpu(config-clsfrule-protocol)# protocol-enable <number of protocols(1-6)> <protocol1> [<protocol2>] [...]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<number of protocols(1)>Indicates the number of protocol lists to be enabled. In the current release, only one protocol can be enabled per classification rule. Mandatory N/A 1<protocol1> [<protocol2>] [...]Indicates the IP protocols to be enabled. In the current release, only one protocol can be enabled per classification rule. Mandatory N/A 0-255 (Using standard IANA protocol values)Command ModesL3 Classification rules-IP protocol configuration modeCommand Syntaxnpu(config-clsfrule-protocol)# no protocol-enable <number of protocols(1-6)> <protocol1> [<protocol2>] [...]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-267.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 364 System Manual4.3.10.15.4.4.4Terminating the Protocol Configuration ModeRun the following command to terminate the IP protocol configuration mode:npu(config-clsfrule-protocol)# exit4.3.10.15.4.4.5Deleting Protocol Lists You can, at any time, run the following command to delete all protocol lists:npu(config-clsfrule)# no ip-protocol Syntax Description Parameter Description Presence Default ValuePossible Values<number of protocols(1-6)>Indicates the number of protocol lists to be disabled.In the current release, only one protocol can be enabled per classification rule. Mandatory N/A 1<protocol1> [<protocol2>] [...]Indicates the protocols to be disabled. You are required to specify at least one protocol that is to be disabled.In the current release, the single previously enabled protocol should be defined. Mandatory N/A 0-255Command ModesL3 Classification rules-IP protocol configuration modeCommand Syntaxnpu(config-clsfrule-protocol)# exitPrivilege Level10Command ModesL3 Classfication rule-IP protocol configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-268.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 365 System Manual4.3.10.15.4.5 Managing Source Address Configuration for the L3 Classification RuleClassification rules can classify the packet, based on the source address of the packet. You can configure the value of source address for a given classification rule.1Enable the source address configuration mode (refer to Section 4.3.10.15.4.5.1)2You can now execute any of the following tasks:»Configure the address mask (refer to Section 4.3.10.15.4.5.2)»Disable the source address (refer to Section 4.3.10.15.4.5.3)3Terminate the source address configuration mode (refer to Section 4.3.10.15.4.5.4)You can, at any time, delete an existing source address (refer to Section 4.3.10.15.4.5.5). The following example illustrates the (sequence of) commands for enabling the source address configuration mode, configuring the address mask, and then terminating the source address configuration mode:npu(config-clsfrule)# srcaddr 10.203.155.20npu(config-clsfrule-srcaddr)# config addr-enable addr-mask 255.255.0.0npu(config-clsfrule-srcaddr)# exitCommand Syntaxnpu(config-clsfrule)# no ip-protocolPrivilege Level10Command ModesL3 Classfication rule-IP protocol configuration modeTo configure one or more source addresses:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-269.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 366 System Manual4.3.10.15.4.5.1Enabling the Source Address Configuration Mode\ Creating a New Source AddressTo configure the parameters for a source address, first enable the source address configuration mode. Run the following command to enable the source address configuration mode. You can also use this command to create a new source address.npu(config-clsfrule)# srcaddr <ipv4addr>If you use this command to specify a new source address, the configuration mode for the newly created source address is automatically enabled, after which you can execute any of the following tasks:Configure the address mask (refer to Section 4.3.10.15.4.5.2)Disable the source address (refer to Section 4.3.10.15.4.5.3)After you have executed these tasks, terminate the source address configuration mode to return to the service classification rule configuration mode (refer to Section 4.3.10.15.4.5.4).IMPORTANTAn error may occur if you provide an invalid source IP address. Refer the syntax description for more information about the appropriate value and format for configuring this parameter.Command Syntaxnpu(config-clsfrule)# srcaddr <ipv4addr>Syntax Description Parameter Description Presence Default ValuePossible Values<ipv4addr> Denotes the IPv4 address of the source address for which the configuration mode is to be enabled. If you want to create a new source address, specify the value for the new source address. The source address configuration mode is automatically enabled. Mandatory N/A Valid IP Address](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-270.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 367 System Manual4.3.10.15.4.5.2Configuring the Address MaskAfter enabling the source address configuration mode, run the following command to configure the address mask for the source address. npu(config-clsfrule-srcaddr)# config [addr-enable] [addr-mask <value>]You can also run this command to enable a source address that is currently disabled. For details, refer to “Disabling the Source Address” on page 368.Command ModesL3 Classification rules configuration modeIMPORTANTAn error may occur if you provide an invalid address mask for the source address. Refer the syntax description for more information about the appropriate value and format for this parameter.Command Syntaxnpu(config-clsfrule-srcaddr)# config [addr-enable] [addr-mask <value>]Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values[addr-enable] Indiactes that the use of the associated source address is enabled for the classification rule that you are configuring. If the use of this address is disabled, the associated source address is ignored while classifying the packet. Optional By default, the use of the associated source address is disabled.The presence/absence of this flag indicates that the use of the associated source address is enabled/disabled.[addr-mask <value>]Denotes the mask field that is used to specify a range of source addresses.Optional 255.255.255.255Valid address mask](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-271.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 368 System Manual4.3.10.15.4.5.3Disabling the Source AddressYou can run the following command to disable the source address that is currently enabled:npu(config-clsfrule-srcaddr)# no addr-enable4.3.10.15.4.5.4Terminating the Source Address Configuration ModeRun the following command to terminate the source address configuration mode:npu(config-clsfrule-srcaddr)# exitCommand ModesL3 Classification rules-source address configuration modeIMPORTANTTo enable this source address, run the following command: npu(config-clsfrule-srcaddr)# config [addr-enable] [addr-mask <value>]For details, refer to “Configuring the Address Mask” on page 367.Command Syntaxnpu(config-clsfrule-srcaddr)# no addr-enablePrivilege Level10Command ModesL3 Classification rules-source address configuration modeCommand Syntaxnpu(config-clsfrule-srcaddr)# exitPrivilege Level10Command ModesL3 Classfication rule-source address configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-272.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 369 System Manual4.3.10.15.4.5.5Deleting Source Addresses You can, at any time, run the following command to delete one or all source addressesnpu(config-clsfrule)# no srcaddr [<ipv4addr>]CAUTIONSpecify the IP address if you want to delete a specific source address. Otherwise all the configured source addresses are deleted.IMPORTANTAn error may occur if you provide an invalid IP address. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu(config-clsfrule)# no srcaddr [<ipv4addr>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<ipv4addr>] Denotes the IPv4 address of the source address that you want to delete from a classification rule. Specify this parameter only if you want to delete a specific source address. If you do not specify a value for this parameter, all the configured source addresses of the classification rule will be deleted.Optional N/A Valid IP AddressCommand ModesL3 Classification rules configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-273.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 370 System Manual4.3.10.15.4.6 Managing Destination Address Configuration for the L3 Classification RuleClassification rules can classify the packet, based on the destination address of the packet. You can configure the value of destination address for a given classification rule.1Enable the destination address configuration mode (refer to Section 4.3.10.15.4.6.1)2You can now execute any of the following tasks:»Configure the address mask (refer to Section 4.3.10.15.4.6.2)»Disable the destination address (refer to Section 4.3.10.15.4.6.3)3Terminate the destination address configuration mode (refer to Section 4.3.10.15.4.6.4)In addition, you can, at any time, delete an existing destination address (refer to Section 4.3.10.15.4.6.5). The following example illustrates the (sequence of) commands for enabling the source address configuration mode, configuring the address mask, and then terminating the destination address configuration mode:npu(config-clsfrule)# dstaddr 10.203.155.22npu(config-clsfrule-dstaddr)# config addr-enable addr-mask 0.0.255.255npu(config-clsfrule-srcaddr)# exit4.3.10.15.4.6.1Enabling the Destination Address Configuration Mode\ Creating a New Destination AddressTo configure the parameters for a destination address, first enable the destination address configuration mode. Run the following command to enable the destination address configuration mode. You can also use this command to create a new destination address.npu(config-clsfrule)# dstaddr <ipv4addr>If you use this command to specify a new destination address, the configuration mode for the newly created destination address is automatically enabled, after which you can execute any of the following tasks:To configure one or more destination addresses:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-274.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 371 System ManualConfigure the address mask (refer to Section 4.3.10.15.4.6.2)kDisable the destination address (refer to Section 4.3.10.15.4.6.3)After you execute these tasks, you can terminate the destination address configuration mode (refer to Section 4.3.10.15.4.6.4) and return to the classification rules configuration mode.4.3.10.15.4.6.2Configuring the Address MaskRun the following command to configure the address mask for the destination address. npu(config-clsfrule-dstaddr)# config [addr-enable] [addr-mask <value>]IMPORTANTAn error may occur if you provide an invalid destination IP address. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu(config-clsfrule)# dstaddr <ipv4addr>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ipv4addr> Denotes the IPv4 address of the destination address for which the configuration mode is to be enabled. If you want to create a new destination address, specify the value for the new destination address. The destination address configuration mode is automatically enabled.Mandatory N/A Valid IP AddressCommand ModesL3 Classification rules configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-275.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 372 System ManualYou can also run this command to enable a destination address that is currently disabled. For details, refer to “Disabling the Destination Address” on page 372.4.3.10.15.4.6.3Disabling the Destination AddressRun the following command to disable the destination address that is currently enabled:npu(config-clsfrule-dstaddr)# no addr-enableIMPORTANTAn error may occur if you provide an invalid address mask. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu(config-clsfrule-dstaddr)# config [addr-enable] [addr-mask <value>]Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values[addr-enable] Indicates that the use of the associated destination address is enabled for the classification rule that you are configuring. If the use of this address is disabled, the associated destination address is ignored while classifying the packet. Optional By default, the use of the associated destination address is disabled.The presence/absence of this flag indicates that the use of the associated destination address is enabled/disabled.[addr-mask <value>]Denotes the mask field that is used to specify a range of destination addresses.Optional 255.255.255.255 Valid address maskCommand ModesL3 Classification rules-destination address configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-276.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 373 System Manual4.3.10.15.4.6.4Terminating the Destination Address Configuration ModeRun the following command to terminate the destination address configuration mode:npu(config-clsfrule-dstaddr)# exit4.3.10.15.4.6.5Deleting Destination Addresses You can, at any time, run the following command to delete one or all destination addressesnpu(config-clsfrule)# no dstaddr [<ipv4addr>]Command Syntaxnpu(config-clsfrule-dstaddr)# no addr-enablePrivilege Level10Command ModesL3 Classification rules-destination address configuration modeCommand Syntaxnpu(config-clsfrule-dstaddr)# exitPrivilege Level10Command ModesL3 Classfication rule-destination address configuration modeCAUTIONSpecify the IP address if you want to delete a specific destination address. Otherwise all the configured destination addresses are deleted.IMPORTANTAn error may occur if you provide an invalid IP address. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-277.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 374 System Manual4.3.10.15.4.7 Managing Source Port Configuration for the L3 Classification RuleClassification can be based on the source port of the packet. You can configure the value of a source port for a given classification rule.1Enable the source port configuration mode (refer to Section 4.3.10.15.4.7.1)2Enable/disable the source port range (refer to Section 4.3.10.15.4.7.2/Section 4.3.10.15.4.7.3)3Terminate the source port configuration mode (refer to Section 4.3.10.15.4.7.4)In addition, you can, at any time, delete an existing source port configuration (refer to Section 4.3.10.15.4.7.5).The following example illustrates the (sequence of) commands for enabling the source port configuration mode, enabling the source port range, and then terminating the source port configuration mode:Command Syntaxnpu(config-clsfrule)# no dstaddr [<ipv4addr>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<ipv4addr>] Denotes the IPv4 address of the destination address that you want to delete from a classification rule. Specify this parameter only if you want to delete a specific destination address.Optional N/A Valid IP AddressCommand ModesL3 Classification rules configuration modeTo configure one or more source ports:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-278.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 375 System Manualnpu(config-clsfrule)# srcport 20 50npu(config-clsfrule-srcport)# port-enablenpu(config-clsfrule-srcport)# exit4.3.10.15.4.7.1Enabling the Source Port Configuration Mode\ Creating a New Source PortTo configure the parameters for a source port, first enable the source port configuration mode. Run the following command to enable the source port configuration mode. You can also use this command to create a new source port.npu(config-clsfrule)# srcport <start-port> <end-port>If you use this command to specify a new source port, the configuration mode for the newly created source port is automatically enabled, after which you can enable/disable the source port range (refer to Section 4.3.10.15.4.7.2/Section 4.3.10.15.4.7.3).You can then terminate the source port configuration mode (refer to Section 4.3.10.15.4.7.4) and return to the classification rules configuration mode.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-clsfrule)# srcport <start-port> <end-port>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<start-port> Denotes the starting value of port range to be configured.Mandatory N/A 1-65535<end-port> Denotes the end value of port range to be configured.Mandatory N/A 1-65535](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-279.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 376 System Manual4.3.10.15.4.7.2Enabling the Source Port RangeRun the following command to enable the source port range:npu(config-clsfrule-srcport)# port-enableYou can also run this command to enable a source port range that is currently disabled. For details, refer to “Disabling the Source Port Range” on page 376.4.3.10.15.4.7.3Disabling the Source Port RangeRun the following command to disable the source port range that is currently enabled:npu(config-clsfrule-srcport)# no port-enableCommand ModesL3 Classification rules configuration modeCommand Syntaxnpu(config-clsfrule-srcport)# port-enablePrivilege Level10Command ModesL3 Classification rules-source port configuration modeIMPORTANTTo enable this source port range, run the following command: npu(config-clsfrule-srcport)# port-enableFor details, refer to “Enabling the Source Port Range” on page 376.Command Syntaxnpu(config-clsfrule-srcport)# no port-enablePrivilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-280.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 377 System Manual4.3.10.15.4.7.4Terminating the Source Port Configuration ModeRun the following command to terminate the source port configuration mode:npu(config-clsfrule-srcport)# exit4.3.10.15.4.7.5Deleting Source Ports Run the following command to delete one or all source portsnpu(config-clsfrule)# no srcport [<start-port> <end-port>]Command ModesL3 Classification rules-source port configuration modeCommand Syntaxnpu(config-clsfrule-srcport)# exitPrivilege Level10Command ModesL3 Classfication rule-source port configuration modeCAUTIONSpecify the start and end port numbers if you want to delete a specific souce port. Otherwise all the configured source ports are deleted.IMPORTANTAn error may occur if you provide an invalid value for the start-port and end-port parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-clsfrule)# no srcport [<start-port> <end-port>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-281.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 378 System Manual4.3.10.15.4.8 Managing Destination Port Configuration for the L3 Classification RuleClassification can be based on the destination port of the packet. You can configure the value of a destination port for a given classification rule.1Enable the destination port configuration mode (refer to Section 4.3.10.15.4.8.1)2Enable/disable the destination port range (refer to Section 4.3.10.15.4.8.2/Section 4.3.10.15.4.8.3)3Terminate the destination port configuration mode (refer to Section 4.3.10.15.4.8.4)In addition, you can, at any time, delete an existing destination port configuration (refer to Section 4.3.10.15.4.8.5).The following example illustrates the (sequence of) commands for enabling the destination port configuration mode, enabling the destination port range, and then terminating the destination port configuration mode:npu(config-clsfrule)# dstport 50 400npu(config-clsfrule-dstport)# port-enablenpu(config-clsfrule-dstport)# exitSyntax Description Parameter Description Presence Default ValuePossible Values<start-port> Denotes the starting value of port range to be deleted.Optional N/A 1-65535<end-port> Denotes the end value of port range to be deleted.Optional N/A 1-65535Command ModesL3 Classification rules configuration modeTo configure one or more destination ports:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-282.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 379 System Manual4.3.10.15.4.8.1Enabling the Destination Port Configuration Mode\ Creating a New Destination PortTo configure the parameters for a destination port, first enable the destination port configuration mode. Run the following command to enable the destination port configuration mode. You can also use this command to create a new destination port.npu(config-clsfrule)# dstport <start-port> <end-port>If you use this command to specify a new destination port, the configuration mode for the newly created destination port is automatically enabled, after which you can enable/disable the destination port range (refer to Section 4.3.10.15.4.8.2/Section 4.3.10.15.4.8.3). After executing these tasks, you can terminate the destination port configuration mode (refer to Section 4.3.10.15.4.8.4). 4.3.10.15.4.8.2Enabling the Destination Port RangeYou can run the following command to enable the destination port range:IMPORTANTAn error may occur if you provide an invalid value for the start-port and end-port parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-clsfrule)# dstport <start-port> <end-port>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<start-port> Denotes the starting value of port range to be configured.Mandatory N/A 1-65535<end-port> Denotes the end value of port range to be configured.Mandatory N/A 1-65535Command ModesL3 Classification rules configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-283.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 380 System Manualnpu(config-clsfrule-dstport)# port-enableYou can also run this command to enable a destination port range that is currently disabled. For details, refer to “Disabling the Destination Port Range” on page 380.4.3.10.15.4.8.3Disabling the Destination Port RangeYou can run the following command to disable the destination port range that is currently enabled:npu(config-clsfrule-dstport)# no port-enable4.3.10.15.4.8.4Terminating the Destination Port Configuration ModeRun the following command to terminate the destination port configuration mode:npu(config-clsfrule-dstport)# exitCommand Syntaxnpu(config-clsfrule-dstport)# port-enablePrivilege Level10Command ModesL3 Classification rules-destination port configuration modeIMPORTANTTo enable this destination port range, run the following command: npu(config-clsfrule-dstport)# port-enableFor details, refer to “Enabling the Destination Port Range” on page 379.Command Syntaxnpu(config-clsfrule-srcport)# no port-enablePrivilege Level10Command ModesL3 Classification rules-destination port configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-284.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 381 System Manual4.3.10.15.4.8.5Deleting Destination Ports Run the following command to delete one or all destination portsnpu(config-clsfrule)# no dstport [<start-port> <end-port>]Command Syntaxnpu(config-clsfrule-dstport)# exitPrivilege Level10Command ModesL3 Classfication rule-destination port configuration modeCAUTIONSpecify the start and end port numbers if you want to delete a specific destination port. Otherwise all the configured destination ports are deleted.IMPORTANTAn error may occur if you provide an invalid value for the start-port and end-port parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-clsfrule)# no dstport [<start-port> <end-port>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<start-port> Denotes the starting value of port range to be deleted.Optional N/A 1-65535<end-port> Denotes the end value of port range to be deleted.Optional N/A 1-65535](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-285.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 382 System Manual4.3.10.15.4.9 Terminating the L3 Classification Rule Configuration ModeRun the following command to terminate the L3 classification rules configuration mode:npu(config-clsfrule)# exit4.3.10.15.4.10Specifying Configuration Parameters for the L2 Classification RuleAfter enabling the classification rules configuration mode for an L2 classification rule, run the following command to configure the parameters for this classification rule:npu(config-clsfrule-L2)# cvid <value(1-4094)>Command ModesL3 Classification rules configuration modeCommand Syntaxnpu(config-clsfrule)# exitCommand ModesL3 Classification rules configuration modeNOTEYou can display configuration information for specific or all classification rules. For details, refer to Section 4.3.10.15.4.13.Command Syntaxnpu(config-clsfrule-L2)# cvid <value(1-4094)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuescvid <value(1-4094)>Denotes the Customer VLAN ID value to be assigned to the classification rule.Mandatory N/A 1-4094](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-286.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 383 System Manual4.3.10.15.4.11Clearing the configuration of the L3 Classification RuleRun the following command to clear the configuration of this classification rule (removing the configured cvid):npu(config-clsfrule-L2)# no cvidAfter clearing the configuration you can define a new cvid for this classification rule.4.3.10.15.4.12Terminating the L2 Classification Rule Configuration ModeRun the following command to terminate the L2 classification rules configuration mode:npu(config-clsfrule-L2)# exit4.3.10.15.4.13Displaying Configuration Information for Classification Rules To display all or specific classification rules, run the following command:npu# show clsf-rule [<rulename>]Specify the classification rule name if you want to display configuration information for a particular rule. Do not specify a value for this parameter if you want to view configuration information for all classification rules.Command ModesL2 Classification rules configuration modeCommand Syntaxnpu(config-clsfrule-L2)# no cvidPrivilege Level10Command ModesL2 Classification rules configuration modeCommand Syntaxnpu(config-clsfrule-L2)# exitCommand ModesL2 Classification rules configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-287.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 384 System ManualIMPORTANTAn error may occur if you provide an invalid value for the rulename parameter. Refer the syntax description for more information about the appropriate values and format for configuring this parameters.Command Syntaxnpu# show clsf-rule [<rulename>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<rulename>] Denotes the name of the classification rule that you want to display. Specify this parameter only if you want to display a specific classification rule. If you do not specify a rule name, it displays all configured classification rules.Optional N/A StringDisplay Format for each L3 rule Classification Rule Configuration : ClsfRulename <value> clsfRuleType: L3 Priority <value> Phs rulename <value> IpTosLow <value> IpTosHigh <value> IpTosMask <value> IpTosEnable <0/1> clsfRuleSrcAddr <value> clsfRuleMask <value> SrcAddrEnable <0/1> clsfRuleDstAddr <value> clsfRuleAddrMask <value> DstAddrenable <0/1> clsfRuleSrcPort Start <value> clsfRuleSrcPort End <value> clsfRulePortEnable <0/1> clsfRuleDstPort Start <value> clsfRuleDstPort End <value> clsfRulePortEnable <0/1>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-288.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 385 System Manual4.3.10.15.4.14Deleting Classification RulesRun the following command to delete one or all classification rules:npu(config)# no clsf-rule [<rulename>]Display Format for each L2 ruleClsfRulename <value>clsfRuleType: L2Cvid <value>Command ModesGlobal command modeCAUTIONSpecify the rule name if you want to delete a specific classification. Otherwise all the configured classification rules are deleted.Command Syntaxnpu(config)# no clsf-rule [<rulename>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<rulename>] Denotes the name of the classification rule that you want to delete. Specify this parameter only if you want to delete a specific classification rule, otherwise all configured classification rules are deleted.Optional N/A StringCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-289.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 386 System Manual4.3.10.16 Configuring PHS RulesPacket Header Suppression (PHS) is a mechanism that conserves air-interface bandwidth by removing parts of the packet header that remain constant along the traffic session. PHS operates by allowing the MS and ASN-GW to associate PHS rules to each service flow. When PHS is enabled, a repetitive portion of the payload headers of higher layers is suppressed in the MAC SDU by the sending entity and restored by the receiving entity. At the uplink, the sending entity is the MS and the receiving entity is the NPU. At the downlink, the sending entity is the NPU, and the receiving entity is the MS. If PHS is enabled at the MAC connection, each MAC SDU is prefixed with a PHSI, which references the Payload Header Suppression Field (PHSF).For instance, the ASN-GW will associate a PHS rule to each provisioned service flow intended for VoIP traffic that will suppress the IP address field from the IP header and other unvarying fields (e.g. protocol version) from the IP and RTP headers. The PHS rules are provisioned on a per-service profile name basis. (For details, refer Section 4.3.10.15.4.)PHS rules define:Header fields that need to be suppressedStatic values that can be configured for the suppressed header fields1Enable the PHS rules configuration mode (refer to Section 4.3.10.16.1)2Configure the parameters for the PHS rule (refer to Section 4.3.10.16.2)3Terminate the PHS rules configuration mode (refer to Section 4.3.10.16.3)You can, at any time, display configuration information (refer to Section 4.3.10.16.5) or delete an existing PHS rules (refer to Section 4.3.10.16.4). The following example illustrates the (sequence of) commands for enabling the PHS rules configuration mode, configuring the parameters of a PHS rule, and then terminating the PHS configuration mode, should be executed as shown in the example below:npu(config)# phs-rule phs-rule1To configure one or more PHS rules:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-290.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 387 System Manualnpu(config-phsrule)# config field 000000000000000000000000FFFFFFFF00000000 mask 000F00 verify 0 size 20npu(config-phsrule)# exit4.3.10.16.1 Enabling the PHS Rules Configuration Mode /Creating a New PHS RuleTo configure the parameters for a PHS rule, first enable the PHS rules configuration mode. Run the following command to enable the PHS rules configuration mode. You can also use this command to create a new PHS rule.npu(config)# phs-rule <rulename>If you use this command to create a new PHS rule, the configuration mode for this PHS rule is automatically enabled, after which you can configure the parameters for the PHS rule (refer to Section 4.3.10.16.2). You can then terminate the PHS rules configuration mode (refer to Section 4.3.10.16.3) and return to the global configuration mode.4.3.10.16.2 Configuring Parameters for the PHS RuleRun the following command to configure the parameters of the PHS rule:npu(config-phsrule)# config <[field <value>] [mask <value>] [verify <value>] [size <value>]>Command Syntaxnpu(config)# phs-rule <rulename>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<rulename> Denotes the PHS rule for which the PHS configuration mode is to be enabled.Mandatory N/A String (1 to 11 characters)Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-291.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 388 System ManualNOTEYou can display configuration information for specific or all PHS rules. For details, refer Section 4.3.10.16.5.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-phsrule)# config <[field <value>] [mask <value>] [verify <value>] [size <value>]>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[field <value>] Denotes the PHSF value, that is, the header string to be suppressed. Mandatory N/A String. This parameter is of format "0x0000000000000000000000000000000000000000". Here Octet(x), x=20 bytes, each Byte will represent two characters when used as string like in xml file.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-292.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 389 System Manual4.3.10.16.3 Terminating the PHS Rules Configuration ModeRun the following command to terminate the PHS rules configuration mode:npu(config-phsrule)# exit[mask <value>] Indicates the PHSM, which contains the bit-mask of the PHSF with the bits set that is to be suppressed.Mandatory N/A String This parameter is of format "0x000000". Here Octet(x), x=3 bytes, each Byte will represent two characters when used as string like in xml file.[verify <value>] Indicates whether the PHS header is to be verified.Optional 0 (No) 0: Indicates that the PHS header should be verified.1: Indicates that the PHS header should not be verified.[size <value>]Indicates the size in bytes of the header to be suppressed.Mandatory N/A 0-20Command ModesPHS rules configuration modeCommand Syntaxnpu(config-phsrule)# exitPrivilege Level10Command ModesPHS rulesconfiguration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-293.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 390 System Manual4.3.10.16.4 Deleting PHS RulesRun the following command to delete one or all PHS rules:npu(config)# no phs-rule [<rulename>]4.3.10.16.5 Displaying Configuration Information for PHS Rules To display all or specific PHS rules, run the following command:npu# show phs-rule [<rulename>]Specify the rule name if you want to display configuration information for a particular PHS rule. Do not specify a value for this parameter if you want to view configuration information for all PHS rule.CAUTIONSpecify the rule name if you want to delete a specific PHS rule. Otherwise all the configured PHS rules are deleted.Command Syntaxnpu(config)# no phs-rule [<rulename>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[<rulename>] Denotes the rule name of the PHS rule that you want to delete. Specify a value for this parameter if you want to delete a specific PHS rule. Do not specify a value for this parameter, if you want to delete all PHS rules. Optional N/A StringCommand ModesClassfication rule-IP protocol configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-294.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 391 System Manual4.3.10.17 Managing the ASN-GW Keep-Alive FunctionalityOnce an MS enters the network, its context is stored in ASN entities (BS, ASN-GW). Dynamically, MS context could be transferred/updated (during HO and re-authentication) to other entities or duplicated to other entities (separation between anchor functions such as Authenticator, Data Path and Relay Data Path).IMPORTANTAn error may occur if you provide an invalid value for the rulename parameter. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu# show phs-rule [<rulename>]]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<rulename>] Denotes the rule name of the PHS rule that you want to delete. Specify a value for this parameter if you want to delete a specific PHS rule. Do not specify a value for this parameter, if you want to delete all PHS rules. Optional N/A StringDisplay FormatPHS Configuration :rulename field mask verify size<value> <value> <value> <value> <value>…….Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-295.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 392 System ManualIn certain cases, such as entity reset, other entities are not aware of service termination of an MS in that entity, and keep maintaining the MS context. This may result in service failure, excessive consumption of memory resources and accounting mistakes. The keep-alive mechanism should be used to clear MS context from all network entities when it is de-attached from the BS, and de-register MS from the network when its context becomes unavailable in one of its serving function locations.When the keep-alive mechanism is enabled the ASN-GW periodically polls other ASN entities-of-interest (BSs and other ASN-GW) and waits for their responses. In case of no keep-alive response, the ASN-GW shall make further actions, such as clearing the applicable MS(s) context.The ASN-GW builds a list of BS-of-interest and ASN-GW-of-interest which it must poll. ASN-GW shall poll other ASN-GW in case data-path was established over R4 during inter-ASN HO (hierarchical data-path establishment).The list shall be dynamically updated; the ASN-GW tracks all BSID(s) in all MS(s) contexts it holds, and dynamically updates the list of BSs-of-interest. When a new MS is attached to a BS that does not exist in the list, it will be added it to the list. When the last MS(s) with specific BSID makes network exit, the ASN-GW shall remove the BS from the list.The same dynamic behavior applies also to ASN-GW-of-interest list. When hierarchical data-path is established, the Data Path Function ASN-GW updates its ASN-GW-of-Interest list with Relay Data Path ASN-GW and vice-versa. The trigger is R4 data-path creation.The ASN-GW periodically polls the BS(s) and ASN-GW(s) for keep-alive. The polling mechanism is independent and unrelated for every BS-of-interest or ASN-GW-of-interest the ASN-GW polls. The keep-alive mechanism uses configurable retry timer and retries counter. Upon expiration of the retry timer, the ASN-GW resends the ASN Keep-Alive request message. Upon expiration of the retries counter, the ASN-GW assumes failure of the polled BS/ASN-GW and clears the contexts of all MS(s) served by that BS/ASN-GW. In addition, the ASN-GW verifies that for each polled entity that the "Last-Reset-Time" UTC value of poll N+1 is equal to the value of poll N. If the "Last-Reset-Time" UTC value of poll N+1 is higher than the value of poll N, this mean that the BS/ASN-GW went through reset state during the interval between two consecutive polls. In this case, the ASN-GW shall clear all MS(s) contexts, served by that specific BS/ASN-GW that are "older" than BS/ASN-GW life after](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-296.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 393 System Manualreset (through calculation of difference between polled entity "Last-Reset-Time" received on poll N+1 and self UTC).If the ASN-GW is the authenticator for the MS(s) the failing BS served, then in addition to context clearance it also sends R3 Accounting-Request (Stop) message including a release indication to AAA.If ASN-GW is the Data Path Function for the MS(s) that the failing BS/Relay Data Path ASN-GW served, then in addition to context clearance it also sends R4 NetExit_MS_State_Change_Req (or equivalent - according to R6 IOT spec procedure) message to the Authenticator which in turn sends R3 Accounting-Request (Stop) message including a release indication to AAAWhen keep-alive fails, ASN-GW generates an alarm and log the event.Regardless of the enable/disable status of the keep-alive mechanism in the ASN-GW, it replies to ASN_Keep_Alive_Req received from other ASN-GWs/BSs with ASN_Keep_Alive_Rsp. that includes also its "Last-Reset-Time". It responds only if all its functions operate properly. In case one of the functions fails, the ASN-GW shall not respond to the keep-alive poll.4.3.10.17.1 Configuring ASN-GW Keep-Alive ParametersTo configure one or several keep-alive parameters, run the following command:npu(config)# set keep-alive ([asnGwKeepAliveTmr <integer (10-1000)>] [asnGwKeepAliveRtxLmt <integer (1-10)>] [asnGwKeepAliveRespTmr <integer (100-10000)>] [asnKeepAliveEnable <enable|disable>])Command Syntaxnpu(config)# set keep-alive ([asnGwKeepAliveTmr <integer (10-1000)>] [asnGwKeepAliveRtxLmt <integer (1-10)>] [asnGwKeepAliveRespTmr <integer (100-10000)>] [asnKeepAliveEnable <enable|disable>]) Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-297.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 394 System Manual4.3.10.17.2 Displaying Configuration Information for ASN-GW Keep-Alive Parameters To display the ASN-GW keep-alive parameters, run the following command:npu# show keep-aliveSyntax Description Parameter Description Presence Default ValuePossible Values[asnGwKeepAliveTmr <integer (10-1000)>]The period ln seconds between polling sessions.asnGwKeepAliveTmr x 1000 (value in milliseconds) cannot be lower than asnGwKeepAliveRespTmr x (asnGwKeepAliveRtxLmt +1).Optional 60 10-1000[asnGwKeepAliveRtxLmt <integer (1-10)>]Maximum number of retries if asnGwKeepAliveRespTmr has expired without getting a response.Optional 3 1-10[asnGwKeepAliveRespTmr <integer (100-10000)>]Time in milliseconds to wait for a response before initiating another polling attempt or reaching a decision that the polled entity has failed (if the maximum number of retries set by asnGwKeepAliveRtxLmt has been reached).Optional 500 100-10000[asnKeepAliveEnable <enable|disable>]Enable/Disable the ASN-GW keep-alive mechanism.Optional disable enabledisableCommand ModesGlobal configuration modeCommand Syntaxnpu# show keep-alive](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-298.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 395 System Manual4.3.11 Configuring LoggingLogs can be generated to record events that occur with respect to the following system modules:System startup procedures: Refers to all procedures/events that occur during system startup.NPU/AU upgrade procedures: Refers to all the procedures executed while upgrading the NPU/AU.Fault management procedures: Refers to internal processes that are executed for monitoring erroneous conditions or fault conditions. System performance procedures: Refers to internal processes that are executed for monitoring system performance. Shelf management procedures: Refers to internal processes that are executed for monitoring the health and temperature of all hardware components (other than the NPU) such as the AU, PIU and PSU.WiMAX signaling protocols: Refers to all the protocols that implement the ASN-GW functionality.User interface: Refers to the command line or remote management interface used for executing all user-initiated events such as system shut down or reset.Privilege Level1Display Format% Asn-gateway Keep Alive ConfigurationasnGwKeepAliveEnable : <enable/disable>asnGwKeepAliveTmr : <value>asnGwKeepAliveRtxLmt : <value>asnGwKeepAliveRespTmr : <value>Command ModesGlobal cpmmand mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-299.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 396 System ManualAU Manager: Refers to all internal processes used for fault, configuration, and performance management for AU.You can specify the severity level for which log messages are to be generated for each module. Logs are generated for events for which the severity level is equal to or higher than the configured level. The following are the severity levels that you can configure for each module:EmergencyAlertCriticalErrorWarningNoticeInformationBy default, system-level logging is enabled. The system stores a maximum of 1000 log and trace messages. The system stores log and trace messages using the cyclic buffer method. That is, when there are more than 1000 messages, the system overwrites the oldest log and trace messages. To configure logging, first specify system-level logging that is applicable across the entire system. You can then configure logging, individually for each system module. This section describes the commands to be used for:“Managing System-level Logging” on page 397“Configuring Module-level Logging” on page 406IMPORTANTThe Syslog utility is used to implement the logging feature for 4Motion. IMPORTANTIt is recommended that you periodically make backups of log messages before these are overwritten. For details, refer to “Making a Backup of Log Files on the NPU Flash” on page 403.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-300.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 397 System Manual4.3.11.1 Managing System-level LoggingSystem-level logging refers to all the procedures to be executed for managing logging for the entire system. To manage system-level logging:Enable/disable logging across the entire system, and specify the destination (a file on the local system or on an external server) where logs are to be maintained.Make periodic backups of log files.You can, at any time, view the current log destination or delete log files from the NPU flash. After you have enabled/disabled system-level logging and specified the destination for storing log messages, you can configure logging separately for each module. This section describes the commands to be used for:“Enabling System-level Logging” on page 397“Disabling Logging to File or Server” on page 399“Displaying System-level Logs” on page 401“Displaying the Current Log Destination” on page 402“Making a Backup of Log Files on the NPU Flash” on page 403“Deleting Backup Log Files from the NPU Flash” on page 4054.3.11.1.1 Enabling System-level LoggingYou can enable logging for the entire system and specify the destination where logs should be written. The destination can be either written to:FileExternal server (Log files are sent to the external server in the Syslog log format. The Syslog daemon on the external server can save these log messages in the appropriate format depending upon the server configuration.)By default, system-level logging is enabled. To view whether the system-level logging is enabled/disabled for logging to file or server. For details, refer Section 4.3.11.1.4.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-301.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 398 System ManualThe system maintains a maximum of 1000 log and trace messages. The system stores log and trace messages using the cyclic buffer method. That is, when there are more than 1000 messages, the system overwrites the oldest log and trace messages. To enable system-level logging, run the following command:npu(config)# log destination {file | server <IP address>}IMPORTANTIf you have enabled writing of log messages to file, it is recommended that you periodically make a backup of this log file. This is because log messages that are written to file are deleted after system reset. For more information about making backups of log files on the NPU flash, refer to Section 4.3.11.1.5.NOTEAfter you execute this command, logging is enabled for the entire system. You may also configure logging separately for each system module. For details, refer to Section 4.3.11.2.IMPORTANTAn error may occur if:Logging is already enabled for the requested destination (file or server). Logging is enabled to a server with a different IP address. Because logging can be enabled to only one external server, you can specify another server IP address after you disable logging to the existing server IP address. For more information about disabling logging to server, refer “Disabling Logging to File or Server” on page 399.An internal error has occurred.You have specified the IP address in an invalid format. Specify the IP address in the format, XXX.XXX.XXX.XXX.Command Syntaxnpu(config)# log destination {file | server <IP address>}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-302.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 399 System Manual4.3.11.1.2 Disabling Logging to File or ServerTo disable logging to file or server, run the following command:npu(config)# no log destination {file | server <IP address>}Syntax Description Parameter Description Presence Default ValuePossible Values{file|server <IP address>}Indicates whether logs are to be written to a file or server.Mandatory N/A file: Indicates that logs are to be written to a file. (Logs written to file are not maintained after system reset; periodically save the log file to flash.) For details, refer to Section 4.3.11.1.5.server: Indicates that logs are to be written to an external server. Specify the server IP address of the server in the format, XXX.XXX.XXX.XXX.Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-303.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 400 System ManualIMPORTANTAn error may occur if:Logging is already disabled for the requested destination (file or server).An internal error has occurred.The server IP address that you have specified does not exist.Command Syntaxnpu(config)# no log destination {file | server <IP address>}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-304.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 401 System Manual4.3.11.1.3 Displaying System-level LogsTo display system-level logs, run the following command:npu# show logsSyntax Description Parameter Description Presence Default ValuePossible Values{file|server <IP address>}Indicates whether the system-level logs are to be disabled for a file or server.Mandatory N/A file: Indicates that system-level logging to a file is to be disabled.server<ipaddress>: Indicates that system-level logging to a server is to be disabled. Specify the IP address if you want to disable logging to a specific server. Otherwise logging is disabled for the server that was last enabled for logging. Provide the IP address in the format, XXX.XXX.XXX.XXX.Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-305.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 402 System ManualWhen you run this command, all the log messages are displayed. (4Motion maintains a maximum of 1000 log and trace messages.) If you want to filter log messages to be displayed, run the following command to specify the filter criteria:npu# show logs [filter | grep <string>]For example, if you want to view log messages pertaining to only Error logs, run the following command:npu# show logs filter|grep ERROR4.3.11.1.4 Displaying the Current Log DestinationTo view the current log destination, that is, whether logs are written to file or an external server, run the following command:npu# show log destinationIMPORTANTAn error may occur if:There are no logs to be displayed.The log files are inaccessible or an internal error occurred while processing the result.Command Syntaxnpu# show logs [filter | grep <string>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[filter | grep <string>]Indicates the criteria for filtering the log messages to be displayed.Optional N/A StringCommand ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-306.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 403 System Manual4.3.11.1.5 Making a Backup of Log Files on the NPU FlashThe system stores a maximum of 1000 log and trace messages in the log file, after which the oldest messages are overwritten. This log file resides in the TFTP boot directory (/tftpboot/management/system_log/) of the NPU. You can TFTP this file from the NPU flash. You can display the list of log files residing on the NPU flash. For details, refer Section 4.3.11.1.7. In addition, logs written to file are not maintained after system reset. If you have enabled writing of logs to file, it is recommended that you periodically make a backup of log messages on the NPU flash.When you make a backup of log files on the NPU flash, the last 1000 log and trace messages are stored in a compressed file, which is saved on the NPU flash. There is no limit on the number of log files that can be saved unless there is inadequate space on the NPU flash.IMPORTANTAn error may occur if an internal error occurs when you execute this command.Command Syntaxnpu# show log destinationPrivilege Level1Display FormatLogfile(<file name>) : Enabled/DisabledLog Server(<IP address>) : Enabled/DisabledCommand ModesGlobal command modeIMPORTANTYou can display a list of log files that are currently residing on the NPU flash. For details, refer Section 4.3.11.1.7.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-307.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 404 System ManualRun the following command to make a backup of the log and trace messages (written to file), on the NPU flash:npu(config)# save log file <file name.gz>When you run this command, the last 1000 log and trace messages are stored in the compressed file, which is saved on the NPU flash.IMPORTANTTrace messages are also written to the same file as log messages (provided you have enabled writing of trace messages to file.) When you make a backup of log files written to file, the backup file also contains trace messages (provided you have enabled writing of trace messages to file). For more information about configuring traces, refer Section 4.11.1.1.IMPORTANTAn error may occur if: You have specified the file name in an invalid format. Because the backup log file is a compressed file, always suffix the file name with .gz.The length of the file name has exceeded 255 characters.The system was unable to compress the file or save the compressed file to flash. A processing error has occurred.Command Syntaxnpu(config)# save log file <file name>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<file name> Indicates the name of the compressed file that contains the last 1000 log and trace messages. Always suffix the file name with .gz.Mandatory N/A <file name>.gz](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-308.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 405 System Manual4.3.11.1.6 Deleting Backup Log Files from the NPU FlashYou can delete the backup log files from the NPU flash. It is recommended that you periodically make a backup of these log files, and delete these from the NPU flash.To delete log and trace backup files from the NPU flash, run the following command:npu(config)# erase log file [<file name>]Command ModesGlobal configuration modeIMPORTANTTrace and log messages are stored in the same backup file on the NPU flash. When you execute this procedure, trace messages are also deleted from the NPU flash. For details, refer to “Managing System-level Tracing” on page 822.CAUTIONSpecify the file name if you want to delete a specific backup file. Otherwise all the backup files residing in the NPU flash are deleted.IMPORTANTAn error may occur if:The file name that you have specified does not exist.A processing error has occurred.Command Syntaxnpu(config)# erase log file [<file name>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-309.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 406 System Manual4.3.11.1.7 Displaying Log Files Residing on the NPU FlashYou can display a list of log files that are residing on the NPU flash. For details, refer Section 4.10.4.4.3.11.2 Configuring Module-level LoggingYou can configure logging (enable/disable) separately for the following modules, and define the severity level for which logging is required:System startup proceduresNPU/AU upgrade proceduresFault management proceduresSystem performance proceduresShelf management proceduresWiMAX signaling protocolsUser interfaceAU management proceduresThis section describes the commands to be used for:Syntax Description Parameter Description Presence Default ValuePossible Values[<file name>] Indicates the name of the compressed log file to be deleted. If you do not specify the file name, all the log files residing in the NPU flash are deleted.Always suffix the file name with .gz.Optional N/A <file name>.gzCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-310.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 407 System Manual“Configuring the Log Severity Level” on page 407“Displaying Configuration Information for Module-level Logging” on page 409“Disabling Module-level Logging” on page 4104.3.11.2.1 Configuring the Log Severity LevelYou can configure the severity level for logs to be generated for each module. This means that if an event occurs for a module for which the severity level is equal to or higher than the configured level, a log is generated. The following are the severity levels (highest to lowest) that can be configured for each module:EmergencyAlertCriticalErrorWarningNotice InformationTo specify the severity level for each module for which logs are to be created, run the following command:npu(config)# log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}] {EMERG|ALERT|CRIT|ERROR|WARN|NOTICE|INFO}The parameters in this command correspond to the system modules/procedures listed in the following table:IMPORTANTBy default, logging is enabled for all modules, and the severity level is Error. The severity levels recorded in 4Motion log messages are defined in RFC 3164.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-311.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 408 System ManualSpecify 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 Warning or higher:npu(config)# log level SIGASN WARNOr run the following command to set the severity level to Error for all modules:npu(config)# log level ERRORTable 4-21: Modules for which Logging can be EnabledParameter Refers to...StartupMgr System startup proceduresSWDownload Software upgrade proceduresFaultMgr Fault management proceduresShelfMgr Shelf management proceduresSIGASN WiMAX signaling protocolsUserIF User-initiated proceduresAUMgr Internal processes used for managing AUPerfMgr Performance management proceduresNOTEYou can display the currently configured severity levels for each module. For details, refer Section 4.3.11.2.2.Command Syntaxnpu(config)# log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}] {EMERG|ALERT|CRIT|ERROR|WARN|NOTICE|INFO}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-312.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 409 System Manual4.3.11.2.2 Displaying Configuration Information for Module-level LoggingTo 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|AUMgr}]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 Parameter Description Presence Default ValuePossible Values[{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]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 4-21.Optional N/A StartupMgrSWDownloadFaultMgrPerfMgrShelfMgrSIGASNUserIFAUMgr{EMERG|ALERT|CRIT|ERROR|WARN|NOTICE|INFO}Indicates the severity level to be applied to a particular or all modules. Mandatory Error EMERGALERTCRITERRORWARNNOTICEINFOCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-313.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 410 System Manual4.3.11.2.3 Disabling Module-level LoggingTo disable logging for one or all system modules, run the following command:npu(config)# no log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]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.Command Syntaxnpu(config)# show log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]Indicates the name of the module for which you want to view the configured severity level. For more information about these parameters, refer Table 4-21.If you do not specify any value for this parameter, the severity level is displayed for all modules.Optional N/A StartupMgrSWDownloadFaultMgrPerfMgrShelfMgrSIGASNUserIFAUMgrDisplay FormatModule Name : Log level<Module Name> : <Log Level>Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-314.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 411 System Manual4.3.12 Configuring Performance Data CollectionYou can configure 4Motion to periodically collect and store performance counters with respect to the following groups:Command Syntaxnpu(config)# no log level [{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values[{StartupMgr|SWDownload|FaultMgr|PerfMgr|ShelfMgr|SIGASN|UserIF|AUMgr}]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 4-21.Optional N/A StartupMgrSWDownloadFaultMgrPerfMgrShelfMgrSIGASNUserIFAUMgrCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-315.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 412 System ManualNPU Counters Groups (per-NPU counters):»NPU DATA port»NPU MGMT port»NPU CASCADE port»AU ports»NPU internal-management interface»NPU external-management interface»NPU local-management interface»NPU bearer interface»Service Flow Authorization functionality»Data path functionality»AAA client functionality»Authenticator function»Context function»DHCP proxy functionality»DHCP relay functionality»DHCP server functionality»MS state change functionality](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-316.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 413 System ManualAU Counters Groups (per-BS counters)»De-Registration»Integrity»Mobility»Network Entry (NE)»Traffic»Utilization»General»All MS Basic Mode»Specific MS Advanced Mode (not supported in current release)For details on the performance data counters collected for each group refer to the relevant 4Motion Performance Monitoring document.You can specify the group for which performance data is to be stored and collected, and the interval after which this data should be fetched.The data is stored in an XML file called, prf_yyyymmddhhmm.xml.gz in the path, TFTP/boot/Management/Performance Manager. 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. In addition, you can specify the interval after which this data should be obtained from each group. This section describes:“Enabling Collection and Storage of Historical Performance Data” on page 414“Disabling Collection and Storage of Performance Data” on page 417“Displaying the Status of Performance Data Collection” on page 419](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-317.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 414 System Manual4.3.12.1 Enabling Collection and Storage of Historical Performance Data4Motion collects and stores performance data for the a number of system groups (refer to Section 4.3.12). 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)# group enable {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}To enable collection and storage of performance data for an AU counters group:npu(config)# group enable au { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}You can display whether performance data collection is currently enabled or disabled for a particular group. For details, refer Section 4.3.12.3.The parameters in this command correspond to the groups listed in the following tables:NOTENOTEUsing this command, you can enable collection of performance data for only one group at a time. For example, run the following command if you want to enable performance data collection and storage for the data path function:npu(config)# group enable pmDatapathFnTable 4-22: NPU Counters Groups for which Performance Data can be CollectedParameter Name Refers to...pmNpuBckhlPort NPU DATA portpmNpuMgmtPort NPU MGMT portpmNpuCascPort NPU CASCADE portpmAuPort AU portspmNpuIntMgmtIf NPU internal-management interfacepmNpuExtMgmtIf NPU external-management interfacepmNpuLclMgmtIf NPU local-management interface](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-318.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 415 System ManualFor example, run the following command if you want to enable performance data collection for the NPU DATA port:npu(config)# group enable pmNpuBckhlPortWhen you run this command, collection and storage of performance data is enabled for the DATA port counters.pmNpuBearerIf NPU bearer interfacepmSfa Service flow authorizationpmDatapathFn Data path functionalitypmAaaClient AAA client functionalitypmAuthenticator Authenticator functionpmContextFn Context functionpmDhcpProxy DHCP proxy functionalitypmDhcpRelay DHCP relay functionalitypmDhcpServer DHCP server functionalitypmMsStateChangeFn MS state change functionalityTable 4-23: AU Counters Groups for which Performance Data can be CollectedParameter Name Refers to...pmBsDeRegistration De-RegistrationpmBsIntegrity IntegritypmBsMobility MobilitypmBsNetworkEntry Network EntrypmBsTraffic TrafficpmBsUtilization UtilizationpmBsGeneral Generalpmbsallmsbasicmode All MS Basi Modecpmbsspecificmsadvancedmode Specific MS Advanced Mode (not supported in current release)Table 4-22: NPU Counters Groups for which Performance Data can be CollectedParameter Name Refers to...](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-319.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 416 System ManualAfter you have enabled collection and storage of performance data is fetched every quarter of an hour. NOTENOTEWhen you enable collection of performance data collection, the data is stored in a file called, prf_yyyymmddhhmm.xml.gz in the path, TFTP/boot/Management/Performance Manager. It is recommended that you periodically make a backup of these files on an external server.IMPORTANTAn error may occur if run this command when you are operating the NPU in the Transparent mode and want to enable performance data storage and collection for the following WiMAX signaling protocol groups:Service Flow Authorization functionalityData path functionalityAAA client functionalityAuthenticator functionContext functionDHCP proxy functionalityDHCP relay functionalityDHCP server functionalityMS state change functionalityCommand Syntaxnpu(config)# group enable {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}npu(config)# group enable au { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-320.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 417 System Manual4.3.12.2 Disabling Collection and Storage of Performance DataTo disable collection and storage of performance data for one group, run the following command:To disable collection and storage of performance data for an NPU counters group:Syntax Description Parameter Description Presence Default ValuePossible Values{pmNpuBckhlPort|pmNpuMgmtPort|pmNpuCascPort|pmAuPort | pmNpuIntMgmtIf pmNpuExtMgmtIf|pmNpuLclMgmtIf|pmNpuBearerIf|pmSfa|pmDatapathFn|pmAaaClient|pmAuthenticator|pmContextFn|pmDhcpProxy|pmDhcpRelay|pmDhcpServer|pmMsStateChangeFn}For a description of each parameter in this command, refer to Table 4-22.Mandatory N/A Refer to Table 4-22.For NPU groups:For AU groups{pmBsDeRegistration | pmBsIntegrity|pmBsMobility|pmBsNetworkEntry|pmBsTraffic|pmBsUtilization|pmBsGeneral|pmbsallmsbasicmode|pmbsspecificmsadvancedmode}For a description of each parameter in this command, refer to Table 4-23Mandatory N/A Refer to Table 4-23.Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-321.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 418 System Manualnpu(config)# no group enable {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}To disable collection and storage of performance data for an NPU counters group:npu(config)# no group enable au { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}For example, run the following command if you want to disable performance data collection and storage for the data path function:npu(config)# no group enable pmDatapathFnNOTENOTEUsing this command, you can disable collection of performance data for only one group at a time. For more information about the group names in this command, refer to Table 4-22.Command Syntaxnpu(config)# no group enable {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}npu(config)# no group enable au { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-322.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 419 System Manual4.3.12.3 Displaying the Status of Performance Data CollectionTo display whether collection and storage of performance data is enabled/disabled for a group, run the following command:To display the status for an NPU counters group:npu# show group status {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | Syntax Description Parameter Description Presence Default ValuePossible Values{pmNpuBckhlPort|pmNpuMgmtPort|pmNpuCascPort|pmAuPort | pmNpuIntMgmtIf pmNpuExtMgmtIf|pmNpuLclMgmtIf|pmNpuBearerIf|pmSfa|pmDatapathFn|pmAaaClient|pmAuthenticator|pmContextFn|pmDhcpProxy|pmDhcpRelay|pmDhcpServer|pmIgmp|pmMsStateChangeFn}For a description of each parameter in this command, refer Table 4-22.Mandatory N/A Refer to Table 4-22For NPU groupsFor AU groups{pmBsDeRegistration | pmBsIntegrity|pmBsMobility|pmBsNetworkEntry|pmBsTraffic|pmBsUtilization|pmBsGeneral|pmbsallmsbasicmode|pmbsspecificmsadvancedmode}For a description of each parameter in this command, refer to Table 4-23Mandatory N/A Refer to Table 4-23.Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-323.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 420 System ManualpmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}To display the status for an AU counters group:npu# show au group status { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}IMPORTANTAn error may occur if run this command when you are operating the NPU in the Transparent mode and want to display performance data collection for the following WiMAX signaling protocol groups:Service Flow Authorization functionalityData path functionalityAAA client functionalityAuthenticator functionContext functionDHCP proxy functionalityDHCP relay functionalityDHCP server functionalityMS state change functionalityCommand Syntaxnpu# show group status {pmNpuBckhlPort | pmNpuMgmtPort | pmNpuCascPort | pmAuPort | pmNpuIntMgmtIf | pmNpuExtMgmtIf | pmNpuLclMgmtIf | pmNpuBearerIf | pmSfa | pmDatapathFn | pmAaaClient | pmAuthenticator | pmContextFn | pmDhcpProxy | pmDhcpRelay | pmDhcpServer | pmMsStateChangeFn}npu# show au group status { pmBsDeRegistration | pmBsIntegrity | pmBsMobility | pmBsNetworkEntry | pmBsTraffic | pmBsUtilization | pmBsGeneral | pmbsallmsbasicmode | pmbsspecificmsadvancedmode}Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-324.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 421 System Manual4.3.13 Configuring the SNMP/Trap ManagerThis section describes the commands for:Syntax Description Parameter Description Presence Default ValuePossible Values{pmNpuBckhlPort|pmNpuMgmtPort|pmNpuCascPort|pmAuPort | pmNpuIntMgmtIf pmNpuExtMgmtIf|pmNpuLclMgmtIf|pmNpuBearerIf|pmSfa|pmDatapathFn|pmAaaClient|pmAuthenticator|pmContextFn|pmDhcpProxy|pmDhcpRelay|pmDhcpServer|pmIgmp|pmMsStateChangeFn}For a description of each parameter in this command, refer Table 4-22.Mandatory N/A Refer to Table 4-22For NPU groupsFor AU groups{pmBsDeRegistration | pmBsIntegrity|pmBsMobility|pmBsNetworkEntry|pmBsTraffic|pmBsUtilization|pmBsGeneral|pmbsallmsbasicmode|pmbsspecificmsadvancedmode}For a description of each parameter in this command, refer to Table 4-23Mandatory N/A Refer to Table 4-23.Display Format<Group Name> <Status>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-325.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 422 System Manual“Configuring the SNMP Manager” on page 422“Configuring the Trap Manager” on page 4244.3.13.1 Configuring the SNMP ManagerTo enable 4Motion configuration over SNMP, you are required to first configure the SNMP Manager. You can configure up to five SNMP Managers for the 4Motion system. This section describes the commands to be executed for:“Adding an SNMP Manager” on page 422“Deleting an Entry for the SNMP Manager” on page 423“Displaying Configuration Information for SNMP Managers” on page 4244.3.13.1.1 Adding an SNMP ManagerYou can configure upto five SNMP Managers. To add an SNMP Manager, run the following command:npu(config)# snmp-mgr [ReadCommunity <string>] [ReadWriteCommunity <string>]You can display configuration information for existing SNMP Managers. For details, refer Section 4.3.13.1.3.NOTEAn existing SNMP Manager entry cannot be modify. To modify the parameters of an SNMP Manager, delete the entry and add a new entry with the required parameters.IMPORTANTAn error may occur if you have specified:More than five entries for the SNMP Manager Duplicate entriesCommand Syntaxnpu(config)# snmp-mgr [ReadCommunity <string>] [ReadWriteCommunity <string>]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-326.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 423 System Manual4.3.13.1.2 Deleting an Entry for the SNMP ManagerTo delete an SNMP Manager entry, run the following command:npu(config)# no snmp-mgr index <integer>Syntax Description Parameter Description Presence Default ValuePossible Values[ReadCommunity <string>]IThe SNMP Read Community string allowing execution of SNMP Get operations.Optional public String (up to 10 characters and case-sensitive)[ReadWriteCommunity <string>]The SNMP Read/Write Community string allowing execution of SNMP Set and Get operations.Optional private String (up to 10 characters and case-sensitive)Command ModesGlobal configuration modeIMPORTANTAn error may occur if you provide an incorrect index number for the SNMP Manager to be deleted. To display the index numbers for configured SNMP Managers, refer Section 4.3.13.1.3.Command Syntaxnpu(config)# no snmp-mgr index <integer>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<integer> Indicates the index number of the SNMP Manager to be deleted. Should be an index of an existing SNMP Manager.Mandatory N/A 1-5](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-327.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 424 System Manual4.3.13.1.3 Displaying Configuration Information for SNMP ManagersTo display configuration information for all SNMP Managers, run the following command:npu# show snmp-mgr4.3.13.2 Configuring the Trap ManagerThe SNMP Agent can send traps to multiple Trap Managers, for which an entry exists in the 4Motion system. After you have created an entry for a Trap Manager, you are required to enable the Trap Manager. You can, at any time, disable a Trap Manager for the 4Motion system.This section describes the commands for:“Adding/Modifying a Trap Manager entry” on page 425“Deleting an Entry for the Trap Manager” on page 426“Enabling/Disabling the Trap Manager” on page 427Command ModesGlobal configuration modeIMPORTANTAn error may occur if there is no existing SMNP Manager entry.Command Syntaxnpu# show snmp-mgrPrivilege Level1Display Format Snmp Manager Table --------------------------------Manager Index:(1) Read Only Community:(<value>) Read WriteCommunity: (<value>)Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-328.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 425 System Manual“Displaying Configuration Information for Trap Managers” on page 427“Displaying the Trap Rate Limit” on page 4284.3.13.2.1 Adding/Modifying a Trap Manager entryYou can configure up to five Trap Manager entries for the 4Motion system. To add a Trap Manager entry, or to modify an existing entry, run the following command:npu(config)# trap-mgr ip-source <ip_addr> [Port <(0-65535)>] [TrapCommunity <string>] [EnableFlag <integer(1 for enable, 2 for disable)>]You can view configuration information for existing Trap Managers. For details, refer Section 4.3.13.2.4.IMPORTANTAn error may occur if :You have specified invalid values for the IP address, Trap Community or port.The IP address is already configured for another Trap Manager.You are trying to create more than five Trap Managers. (You can configure up to five Trap Managers for the 4Motion system.Command Syntaxnpu(config)# trap-mgr ip-source <ip_addr> [Port <(0-65535)>] [TrapCommunity <string>] [EnableFlag <integer(1 for enable, 2 for disable)>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ip_addr> Indicates the IP address of the Trap Manager to be added or modified.Must be unique (the same IP address cannot be assigned to more than one Manager)Mandatory N/A Valid IP address](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-329.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 426 System Manual4.3.13.2.2 Deleting an Entry for the Trap ManagerTo delete a Trap Manager, run the following command:npu(config)# no trap-mgr ip-source <ip_addr>[Port <(0-65535)>]Indicates the port number on which the Trap Manager will listen for messages from the Agent.Optional 162 0-65535[TrapCommunity <string>] Indicates the name of the community of the Trap Manager. Optional public String (up to 10 characters and case-sensitive)[EnableFlag<integer(1 for enable, 2 for disable)>] Indicates whether traps sending to the Trap Manager is to be enabled. or disabledOptional 1 1: Indicates enable2 Indicates disableCommand ModesGlobal configuration modeIMPORTANTAn error may occur if the IP address you have specifed does not exist.Command Syntaxnpu(config)# no trap-mgr ip-source <ip_addr>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ip_addr> Indicates the IP address of the Trap Manager to be deleted.Mandatory N/A Valid IP addressCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-330.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 427 System Manual4.3.13.2.3 Enabling/Disabling the Trap ManagerTraps are sent to a particular Trap Manager only if it is enabled. Run the following commands to enable/disable the Trap Manager that you have created.npu(config)# trap-mgr enable ip-source <ip_addr>npu (config)# trap-mgr disable ip-source <ip_addr>4.3.13.2.4 Displaying Configuration Information for Trap ManagersTo display configuration information for the configured Trap Managers, run the following command:NOTEBy default, all Trap Managers are enabled. NOTEThese enable/disable commands have functionality that is identical to the EnableFlag parameter (see “Adding/Modifying a Trap Manager entry” on page 425).IMPORTANTAn error may occur if the IP address that you ave specified does not exist in the Trap Manager index.Command Syntaxnpu(config)# trap-mgr enable ip-source <ip_addr>npu (config)# trap-mgr disable ip-source <ip_addr>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<ip_addr> Indicates the IP address of the Trap Manager to be enabled/disabled.Mandatory N/A Valid IP AddressCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-331.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 428 System Manualnpu# show trap-mgr4.3.13.2.5 Displaying the Trap Rate LimitTo display the trap rate limit, run the following command:npu# show trap-rate-limitIMPORTANTAn error may occur if no Trap Manager has been configured.Command Syntaxnpu# show trap-mgrPrivilege Level1Display Format Trap Manager Table --------------------------------Trap Manager Ip:(10.203.153.149) Port:(162) Community:(public) Control Register: (Enable)Command ModesGlobal command modeCommand Syntaxnpu# show trap-rate-limitPrivilege Level1Display FormatMaximum number of traps sent is 20 traps per second.Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-332.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 429 System Manual4.3.14 Configuring the 4Motion ShelfThe 4Motion shelf comprises the following components:NPU card: Serves as the shelf controller that manages and monitors all the shelf components. In addition, it provides backbone Ethernet connectivity via a 10/100/1000 Base-T network interface. The shelf contains one active and one redundant NPU card.AU: Is responsible for wireless network connection establishment and for bandwidth management. The shelf contains six active and one redundant AU.PSU: Accepts 48V DC input and provides 5, 3.3, +/-12V DC output. There are four PSUs in the shelf and work in load-sharing mode.PIU: Serves as a 48V power source for PSU. One active and one redundant PIU are provided in the shelf.GPS: An external GPS receiver is used to synchronizes the air link frames of Intra-site and Inter-site located sectors to ensure that in all sectors the air frame will start at the same time, and that all sectors will switch from transmit (downlink) to receive (uplink) at the same time. In addition, the GPS synchronizes frame numbers that are transmitted by the AU.AVU: Includes a 1U high integral chamber for inlet airflow and a 1U high fan tray with an internal alarm module. The AVU comprises 10 brush-less fans, where 9 fans are sufficient for cooling a fully loaded chassis.Power Feeder: The PIU can support a maximum current of 58 A (@-40.5 VDC). In certain installations with a relatively high number of ODUs this current may not be sufficient to power the shelf and all the ODUs. In such installations the ODU Power Feeder is used as an additional power source providing power (-48 VDC) to ODUs. It transfers transparently all signals between the AU and the ODU, while injecting DC power received from an external source. Each ODU Power Feeder unit can serve up to four ODUs.This section describes the commands to be used for:IMPORTANTNPU redundancy is not supported in the current release.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-333.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 430 System Manual“Configuring the PSU/PIU Modules” on page 430“Configuring the GPS” on page 433“Managing Power Feeders Configuration” on page 447“Managing Dry-contact Input Alarms” on page 450“Managing Dry-contact Output Alarms” on page 455“Configuring the Location Information for the 4Motion Shelf” on page 460“Configuring the Unique Identifier for the 4Motion Shelf” on page 4624.3.14.1 Configuring the PSU/PIU ModulesThis section describes the commands to be used for:“Enabling/Disabling the PSU, and PIU Modules” on page 430“Configuring the PIU Hardware Version” on page 4324.3.14.1.1 Enabling/Disabling the PSU, and PIU ModulesYou can use the CLI to configure the administrative status of the PSU/PIU modules to enable or disable.Run the following command to enable/disable the PSU/PIU modules:npu(config)# enable {PSU | PIU} <slot id>npu(config)# disable {PSU | PIU} <slot id>Specify the slot ID of the PSU or PIU to be enabled. The following figure depicts the slot ID of the 4Motion shelf components:IMPORTANTAn alarm is raised if you enable a PSU or PIU that is already powered down, or you disable a PSU or PIU that is already powered up.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-334.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 431 System ManualFigure 4-1: Slot IDs of Shelf ComponentsFor example, if you want to enable PSU, slot# 3, and disable the PIU, slot# 1, run the following command:npu(config)# enable PSU 3npu(config)# disable PIU 1Remember that a minimum AU-to-PSU/PIU ratio should always be maintained. The following table lists the required active AU-to-PSU ratio. Before disabling the PSU module, ensure that this ratio is maintained.IMPORTANTAn error may occur if you specify a PSU slot ID that is not in the range, 1-4, or a PIU slot ID that is not in the range 1-2.IMPORTANTEnsure that the NPU to PSU/PIU ratio is also maintained. At least one PSU and PIU should always be active to support the NPU.Table 4-24: Active AU-to-PSU RatioIf the number of Active AUs is... Number of active PSUs should be... Number of Active PIU1-4 2 15-7 3 1Command Syntaxnpu(config)# enable {PSU | PIU} <slot id>npu(config)# disable {PSU | PIU} <slot id>](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-335.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 432 System Manual4.3.14.1.2 Configuring the PIU Hardware VersionYou need to manually configure the PIU hardware version that is currently in use. The system periodically checks whether the configured and actual hardware versions are identical. If there is a difference in the configured and actual versions, an alarm is raised. To configure the PIU hardware version, run the following command:npu(config)# PIU <slot id (1-2)> hw_version <version (0-7)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values{PSU | PIU} Indicates whether the PSU or PIU slot is to be enabled or disabled.Mandatory N/A PSUPIU<slot id> Indicates the slot ID of the PSU/PIU that you want to enable or disable. Refer Figure 4-1 for more information about the slot ID assigned to each PIU/PSU module on the 4Motion chassis.Mandatory N/A 1-4 for PSU slot1-2 for PIU slotCommand ModesGlobal configuration modeCommand Syntaxnpu(config)# PIU <slot id (1-2)> hw_version <version (0-7)>Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-336.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 433 System Manual4.3.14.2 Configuring the GPSThe GPS is used to synchronize the air link frames of Intra-site and Inter-site located sectors to ensure that in all sectors the air frame will start at the same time, and that all sectors will switch from transmit (downlink) to receive (uplink) at the same time. This synchronization is necessary to prevent Intra-site and Inter-site sectors interference. In addition, the GPS synchronizes frame numbers that are transmitted by the AU.The GPS clock generates a 1PPS signal with accuracy of 10-11 and maximum jitter of 100ns, and is connected to the 4Motion shelf via the GPS SYNC IN connector on the front panel of the NPU. The GPS clock requirements can be reached by an outdoor installed GPS unit when it is synchronized to a minimum number of (user-configurable) satellites. This section describes the commands to be used for:“Configuring the GPS Clocks” on page 434“Configuring General Configuration Parameters for the GPS” on page 437“Configuring the Date and Time” on page 439“Configuring the Position” on page 440Syntax Description Parameter Description Presence Default ValuePossible Values<slot id (1-2)>Indicates the PIU slot ID for which the hardware version is to be configured.Mandatory N/A 1-2hw_version <version (0-7)>Indicates the hardware version to be configured for the PIU slot.Mandatory N/A 0-7Command ModesGlobal configuration modeIMPORTANTImplementation of GPS synchronization is based on the assumption that all sectors are operating with the same frame size and with the same DL/UL ratio.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-337.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 434 System Manual“Configuring the Clock Mode” on page 441“Configuring the Required Number of Satellites” on page 442“Displaying GPS Clocks Parameters” on page 443“Displaying GPS General Configuration Parameters” on page 444“Displaying the Date and Time Parameters” on page 445“Displaying the Position Parameters” on page 446“Displaying the Clock Mode Parameter” on page 446“Displaying the Number of Satellite Parameters” on page 4474.3.14.2.1 Configuring the GPS ClocksThe GPS clock parameters determines the source for the main clocks in the system. To configure the GPS clock, you are required to enable/disable:External 1PPS: Determines the air-frame start time. Assuming that all systems use the same air-frame size and DL/UL Ratio, then, when the 1PPS clock is received from a GPS system, this mechanism ensures inter-site and intra-site synchronization among all sectors, preventing cross interference and saturation problems. When using the internal 1PPS clock (derived from the selected 16 MHz clock source), only intra-site synchronization among sectors can be achieved. You can either enable the external 1PPS clock source or use the internal 1PPS clock source derived from the selected 16 MHz clock. By default, the External IPPS clock is enabled. When using a GPS for synchronization, the 1PPS clock is received from the GPS receiver and must be enabled for proper operation.IMPORTANTReset the system for changes in the GPS clock configuration to be applied to the entire system.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-338.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 435 System ManualExternal 16MHz: Generates all the main clocking signals in the system, including the internal 1PPS clock. Using an external, accurate 16 MHz clock source will enable better hold-over of the 1PPS clock upon temporary loss (or reduced reliability when receiving less than 4 satellites) of the external 1PPS clock. This will allow a longer time of continued operation before appearance of interferences due to clock drifts among BSs. You can either enable the external 16 MHz clock source or use the internal 16 MHz clock source. By default, the external 16MHz clock is disabled. In the current release MHz clock must be disabled.To configure the GPS clock, run the following command:npu(config)# set clock ([ External1PPS {Enable | Disable} ] [ External16MHz {Enable | Disable} ])For example, to configure the internal 1PPS clock at the NPU to synchronize the air frames for inter-site and intra-site sectors:npu(config)# set clock External1PPS DisableNOTEIf the external 1PPS GPS clock is enabled:The concatenated slave NPU 16Mhz created from local 16MHz TCXO/OCXO at the NPU provides holdover when the GPS loses synchronization with its satellites.Configure the GPS parameters listed in section, Section 4.3.14.2.2.Command Syntaxnpu(config)# set clock ([External1PPS {Enable | Disable}] [External16MHz {Enable | Disable}])Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-339.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 436 System ManualSyntax Description Parameter Description Presence Default ValuePossible ValuesExternal1PPS {Enable | Disable}Indicates whether the external 1PPS clock is enabled or disabled.If the External 1PPs clock is enabled, synchronization of air frames for inter-site and intra-site sectors should be managed by the external 1PPS GPS clock. If the External 1PPS clock is disabled, it indicates that the internal 1PPS at the NPU is used to synchronize air frames for inter-site and intra-site sectors.When using a GPS, External 1PPS clock must be enabled for proper operation of the system.Optional Enable EnableDisableExternal16MHz {Enable | Disable}Indicates whether the External 16Mhz clock is enabled or disabled.If the external 16 MHz is enabled, the NPU should receive 16Mhz signal from the master NPU. This parameter should be enabled only if the NPU clock mode is slave. If the NPU clock mode is master, the MPU drives the 16Mhz signal towards the slave NPUs.In the current release External 16MHz clock must be disabled.Optional Disable EnableDisableCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-340.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 437 System Manual4.3.14.2.2 Configuring General Configuration Parameters for the GPSThe GPS general configuration parameters determine how the GPS should function with respect to the 4Motion system. Depending upon the values defined for these parameters, you can configure the GPS clock (external 1PPS and 16MHz), and the UTC time. Run the following command to configure the global configuration parameters for the GPS:npu(config)# gps config ( [Type {Trimble | None}] [AdaptorRequired {Yes | No}][HoldoverPassedTout <expiry_interval(0-2880)>] [HoldoverPassTxOperationStop {True | False}][AlmanacUsableTime <expiry_interval(0-4320)>] [EphemerisUsableTime <expiry_interval(0-168)>] [IntervalToReadGPSTime{Hourly | Daily | Monthly | Yearly}] [TimeToReadGPSTime <HH:MM:SS,DD/MM>]))IMPORTANTSkip this section if you have selected the internal 1PPS clock. For more information about configuring the GPS clock, refer Section 4.3.14.2.1.IMPORTANTAn error may occur if:Time to read GPS time is not in valid format. Correct format is hh:mm:ss, dd/mm: Minute and Second should be within range of 0 to 60, Hour should be within the range of 0 to 23, days should be in the range 1 to 31 and Month should be within the range of 1 to 12, also day should be valid in accodance with month.Command Syntaxnpu(config)# gps config gps config ( [Type {Trimble | None}] [AdaptorRequired {Yes | No}][HoldoverPassedTout <expiry_interval(0-2880)>] [HoldoverPassTxOperationStop {True | False}][AlmanacUsableTime <expiry_interval(0-4320)>] [EphemerisUsableTime <expiry_interval(0-168)>] [IntervalToReadGPSTime{Hourly | Daily | Monthly | Yearly}] [TimeToReadGPSTime <HH:MM:SS,DD/MM>]))Privilege Level10Syntax DescriptionParameter Description Presence Default ValuePossible Values](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-341.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 438 System ManualType {Trimble | None}]Indicates the type of GPS connected to 4Motion.Optional Trimble TrimbleNone[AdaptorRequired {Yes | No}]Indicates whether a GPS adaptor is required. The NPU can be connected to an extenal GPS adaptor that allows the NPU to connect to multiple GPS interfaces/1PPS /16Mhz clocks. In the current release a GPS adapter is not supported.Optional No YesNo[HoldoverTimeout <expiry_interval (0-2880)>]Indicates the period, in minutes, for which the NPU provides holdover when the GPS loses synchronization with its satellites. Optional 720 0 - 2880[HoldoverPassTxOperationStop{True | False}]Indicates whether the AU modules should stop data transmission if the GPS loses synchronization with its satellites and the holdover timeout has occurred.Optional True TrueFalse[AlmanacUsableTime <expiry-interval(0-4320)>]Indicates the maximum period, in hours, for which the Almanac time is valid when the GPS is reset.Optional 720 0-4320[EphemerisUsableTime <expiry-interval(0-168)>]Indicates the maximum period, in hours, for which the Ephemeris time is valid when the GPS is reset.Optional 4 0-168[IntervalToReadGPSTime {Hourly | Daily | Monthly | Yearly}]Indicates the interval after which the NPU should obtain the GPS time for frame synchronization, and send it to the AU.Optional Daily HourlyDailyMonthlyYearly[TimeToReadGPSTime <HH:MM:SS,DD/MM>]Indicates the time when the NPU should obtain the GPS time for frame synchronization. .Optional 04:05 HH:MM:SS,DD/MM](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-342.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 439 System Manual4.3.14.2.3 Configuring the Date and TimeThe UTC time is used to configure the following:Local time: Differs from the UTC time with respect to the value you have specified for the localUTCDiff and DST parameters. The local time is equal to the sum of the UTC time, the value of the localUTCDiff parameter (local offset from UTC time) and DST (daylight saving time offset). For more information about configuring this parameter, “Configuring the GPS Clocks” on page 434. You can use the CLI to display the current local time. For details, refer the section, “Displaying the Date and Time Parameters” on page 445.System time: Refers to the operating system (kernel) time that is identical to the UTC time when the system boots up. The system time is updated every hour with the time received from the GPS receiver.Real Time Clock (RTC) time: Refers to the time maintained by the board’s hardware clock. By default, the RTC time is set to 1st January, 1970. The RTC time is updated every hour with the UTC time that is received from the GPS receiver or that you have configured from the CLI. The RTC time is used for creating the timestamp for log and trace messages, performance data collection files, and for managing the interval after which a backup of the configuration file should be maintained and performance data should be collected.Execute the following command to configure the date and time parameters. If the GPS is synchronized to its satellites and is connected to 4Motion, the UTC time is provided by the GPS. Otherwise the UTC time that you configure is used instead.To configure the date and time parameters, run the following command:npu(config)# set date [UTC <HH:MM:SS,DD/MM/YYYY>] [LocalUTCDiff <+/-HH:MM>] [DST <(0-2)>]Command ModesGlobal configuration modeIMPORTANTAn error may occur if :1) UTC time is not in the valid format i.e. hh: mm: ss, dd/mm/yyyy. 2) Local UTCDiff is not valid format i.e. +/-hh:mm3) Local UTC Diff is out of the range between -12 to +13 or it is not in steps of 30 minutes.4) DST is out of range i.e between 0 to 2](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-343.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 440 System Manual4.3.14.2.4 Configuring the PositionThe position configuration enables setting the location’s parameters when GPS is not used (Type=None).To configure the position parameters, run the following command:npu(config)# set position ([Latitude <xxx.xxx,N/S>] [Longitude <xxx.xxx,E/W>] [Altitude (-300.0 - 9000.0)])Command Syntaxnpu(config)# set date [UTC <HH:MM:SS,DD/MM/YYYY>] [LocalUTCDiff <+/-HH:MM>] [DST <(0-2)>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible ValuesUTC <HH:MM:SS,DD/MM/YYYY>Indicates the UTC time to be used for 4Motion if not available from GPS.Mandatory N/A Use the format:HH:MM: SS, DD/MM/YYYYLocalUTCDiff <+/-HH:MM>The local offset from UTC Optional +00:00 +/-HH:MMHH: -12 to +13MM: 00 or 30DST <(0-2)> Daylight Saving Time offset of the local clockOptional 0 0-2Command ModesGlobal configuration modeIMPORTANTAn error may occur if :1) Latitude, longitude and altitude are configured while GPS type is not "None".2) Latitude is not in valid format i.e. lll.mmm,a where a is either N or S3) Longitude is not in valid format i.e. lll.mmm,a where a is either E or W.4) Altitude is not in valid range i.e. +-300.0 to 9000.0.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-344.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 441 System Manual4.3.14.2.5 Configuring the Clock ModeThe Clock Mode parameter enables defining the functionality of the NPU when GPS chaining is used. In the current release GPS chaining is not supported and the clock mode must be set to Master.To configure the clock mode parameter, run the following command:npu(config)# set npu ClockMode {Master | Redundant | Slave}Command Syntaxnpu(config)# set position ([Latitude <xxx.xxx,N/S>] [Longitude <xxx.xxx,E/W>] [Altitude (-300.0 - 9000.0)])Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible ValuesLatitude <xxx.xxx,N/S>Indicates the latitude where the 4Motion shelf is currently positioned. Configure only if GPS Type is None.Optional 000.000.N Use the format, Ill.mmm.a (where lll.mmm is in degrees and the value of a is either N or S)Longitude <xxx.xxx,E/W>Indicates the longitude where the 4Motion shelf is currently positioned. Configure only if GPS Type is None.Optional 000.000.E Use the format, Ill.mmm.a (where ll.mmm is in degrees and the value of a is either E or W)Altitude (-300.0 - 9000.0)])Indicates the altitude (in meters) where the 4Motion shelf is currently positioned. Configure only if GPS Type is None.Optional 0.0 -300.0 to 9000.0Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-345.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 442 System Manual4.3.14.2.6 Configuring the Required Number of SatellitesThe satellite parameter enables configured the minimum number of satellites required for maintaining synchronization and for renewing synchronization after synchronization loss.To configure the satellite parameters, run the following command:npu(config)# set satellite ([MinNumOfSatForHoldoverReturn <range (1-12)>] [MaxNumOfSatBeforeSyncLoss <range (0-11)>])IMPORTANTAn error may occur if setting to any option other than Master because current release supports only the Master option.Command Syntaxnpu(config)# set npu ClockMode {Master | Redundant | Slave}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesnpu ClockMode {Master | Redundant | Slave}Indicates the clocks functionality of the NPU when GPS chaining is used. GPS chaining is not supportyed in current release and this parameter must be set to its default value of Master.Optional Master Master(other options not supported in current release)Command ModesGlobal configuration modeIMPORTANT1) An error can occur while configuring MinNumOfSatForHoldoverReturn if Minimum number of satellite for holdover return is less than Maximum number of satellite before synchronization loss.2) An error can occur while configuring MaxNumOfSatBeforeSyncLoss if Maximum number of satellite before synchronization is more than Minimum number of satellite for holdover return.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-346.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 443 System Manual4.3.14.2.7 Displaying GPS Clocks ParametersTo display the GPS clock configuration parameters, run the following command:npu# show clock status [{CurrentExternal1PPS | ConfiguredExternal1PPS | CurrentExtrnal16MHz | ConfiguredExternal16MHz}]Command Syntaxnpu(config)# set satellite ([MinNumOfSatForHoldoverReturn <range (1-12)>] [MaxNumOfSatBeforeSyncLoss <range (0-11)>]Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible ValuesMinNumOfSatForHoldoverReturn <range (1-12)>Indicates the minimum number of satellites that should be received for resuming synchronization (exiting holdover status) after loss of synchronization.Optional 2 1-12MaxNumOfSatBeforeSyncLoss <range (0-11)>Indicates the minimum number of satellites required for maintaining synchronization.Optional 1 0-11Command ModesGlobal configuration modeCommand Syntaxnpu# show clock status [{CurrentExternal1PPS | ConfiguredExternal1PPS | CurrentExtrnal16MHz | ConfiguredExternal16MHz}Privilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-347.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 444 System Manual4.3.14.2.8 Displaying GPS General Configuration ParametersTo display the GPS general configuration parameters, run the following command:npu# show gps config [{ Type | SoftwareVersion [{ Navigation | Signal }] | AdaptorRequired | HoldoverPassedTout | HoldoverPassTxOperationStop | AlmanacUsableTime | EphemerisUsableTime | IntervalToReadGPSTime | TimeToReadGPSTime} ]Syntax DescriptionFor a detailed description of each parameter in this command, refer the section, “Configuring the GPS Clocks” on page 434.Both Current and Configured values for each clock are provided (the parameters are applied after reset)Display FormatConfigured External 1PPS Status :Enable/ DisableCurrent External 1PPS Status :Enable/ DisableConfigured External 16MHz Status :Enable/ DisableCurrent External 16MHz Status :Enable/ DisableCommand ModesGlobal command modeCommand Syntaxnpu# show gps config [{ Type | SoftwareVersion [{ Navigation | Signal }] | AdaptorRequired | HoldoverPassedTout | HoldoverPassTxOperationStop | AlmanacUsableTime | EphemerisUsableTime | IntervalToReadGPSTime | TimeToReadGPSTime} ]Privilege Level1Syntax DescriptionFor a detailed description of each parameter in this command, refer the section, “Configuring General Configuration Parameters for the GPS” on page 437.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-348.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 445 System ManualIn addition to the configuration parameters, the SW Versions of the GPS Navigation and Signal Processors are also displayed (if available).4.3.14.2.9 Displaying the Date and Time ParametersTo display the current date parameters, run the following command:npu# show date [{Local | UTC | LocalUTCDiff | DST}]Display FormatConfigured GPS Type :GPS Navigation Processor SW Version :GPS Signal Processor SW version :Adaptor Required :Holdover Timeout :HoldoverPassedTxOperationStop :Almanac Usable Time :Ephemeris Usable Time :Interval To Read Gps Time :Time To Read Gps Time :Command ModesGlobal command modeCommand Syntaxnpu# show date [{Local | UTC | LocalUTCDiff | DST}]Privilege Level1Syntax DescriptionFor a detailed description of each parameter in this command, refer the section, “Configuring the Date and Time” on page 439.Display FormatLocal Time :UTC Time :Local UTC Offset :Daylight Saving Time :](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-349.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 446 System ManualIn addition to the configurable parameters, the calculated Local Time is also displayed.4.3.14.2.10 Displaying the Position ParametersTo display the current position parameters, run the following command:npu# show position [{Latitude | Longitude | Altitude}]4.3.14.2.11 Displaying the Clock Mode ParameterTo display the current clock mode parameter, run the following command:npu# show npu clock modeCommand ModesGlobal command modeCommand Syntaxnpu# show position [{Latitude | Longitude | Altitude}]Privilege Level1Syntax DescriptionFor a detailed description of each parameter in this command, refer the section, “Configuring the Position” on page 440.Display FormatLatitude :Longitude :Altitude :Command ModesGlobal command modeCommand Syntaxnpu# show npu clock modePrivilege Level1](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-350.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 447 System Manual4.3.14.2.12 Displaying the Number of Satellite ParametersTo display the current satellite parameters, run the following command:npu# show satellite [{MinNumOfSatForHoldoverReturn | MaxNumOfSatBeforeSyncLoss | NumOfSatelliteAvailable}]In addition to the configurable parameters, the current number of satellites acquired by the GPS receiver is also displayed.4.3.14.3 Managing Power Feeders ConfigurationThe Power Feeder configuration enables specifying the AU port connected to each Power Feeder port.Syntax DescriptionFor a detailed description of the parameter in this command, refer the section, “Configuring the Clock Mode” on page 441.Display FormatNPU Clock Mode : MasterCommand ModesGlobal command modeCommand Syntaxnpu# show satellite [{MinNumOfSatForHoldoverReturn | MaxNumOfSatBeforeSyncLoss | NumOfSatelliteAvailable}]Privilege Level1Syntax DescriptionFor a detailed description of each parameter in this command, refer the section, “Configuring the Required Number of Satellites” on page 442.Display FormatMax Satellites Before Sync Loss :Min Satellites For Holdover Return :Number of Satellites Acquired :Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-351.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 448 System Manual4.3.14.3.1 Configuring Power FeedersTo configure the AU ports connected to the ports of a specific Power Feeder, run the following command:npu(config)# config pfUnitNo <pfunit no (1-4)> pfPortNo <pfport no (1-4)> pfAuSlotNoDestination <AuslotNoDestination (-1,1-4,7-9)> pfAuPortNoDestination <pfAuPortNoDestination (-1,1-4)>Command Syntaxnpu(config)# config pfUnitNo <pfunit no (1-4)> pfPortNo <pfport no (1-4)> pfAuSlotNoDestination <AuslotNoDestination (-1,1-4,7-9)> pfAuPortNoDestination <pfAuPortNoDestination (-1,1-4)>Privilege Level10Syntax Description Parameter Description PresenceDefault ValuePossible ValuespfUnitNo <pfunit no (1-4)>The Power Feeder unit number.Mandatory N/A 1-4pfPortNo <pfport no (1-4)>Each combination of Power Feeder Unit Number and Port Number can appear in a maximum of one Power Feeder instanceThe Power Feeder port numberMandatory N/A 1-4pfAuSlotNoDestination <AuslotNoDestination (-1,1-4,7-9)>The AU Slot number.-1 means none.Mandatory -1 (none) -1 (none), 1-4, 7-9](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-352.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 449 System Manual4.3.14.3.2 Displaying Configuration Information for Power FeedersTo display configuration information for all defined Power Feeders, run the following command:npu# show power-feeder configurationpfAuPortNoDestination <pfAuPortNoDestination (-1,1-4)>Each combination of AU Slot Number and Port Number can appear in a maximum of one Power Feeder instance (excluding combinations with a none value).The AU Port number.-1 means none.Mandatory -1 (none) -1 (none), 1-4Command ModesGlobal configuration modeCommand Syntaxnpu# show power-feeder configurationPrivilege Level1Display Format (for each configured instance)PfUnitNo : <value>, PfPortNo : <value>, AuPortNo : <value>, AuSlotNo : <value>........Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-353.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 450 System Manual4.3.14.4 Managing Dry-contact Input AlarmsDry-contact input alarms are external devices that are connected to the 4Motion unit, and notify the system when there is a change in external conditions. When the system receives this notification, an SNMP trap is sent to the EMS. For example, a device such as a temperature sensor that is connected to the 4Motion unit, and configured to function as a dry-contact input alarm, can raise an alarm to the system when there is a sudden change in the room temperature. The system then sends an SNMP trap to the EMS, notifying the administrator of the change indicated by the external device.Dry contact input alarms are connected to the 4Motion system via a 25-pin micro D-Type ALRM-IN/OUT connector on the NPU front panel. The following figure depicts the ALRM-IN/OUT connector, and the pin numbers assigned to each pin:Figure 4-2: 25-pin Micro D-Type ALRM-IN/OUT ConnectorYou can configure upto eight dry contact input alarms, each mapping to a different pin number. This section describes the commands to be executed for:“Mapping a Dry-contact Input Alarm to an Alarm Condition” on page 450“Disabling Dry-contact Input Alarms” on page 4544.3.14.4.1 Mapping a Dry-contact Input Alarm to an Alarm ConditionDry contact alarms are connected to the 4Motion unit via the 25-pin micro D-Type ALRM-IN/OUT connector on the front panel of the NPU. You can configure upto eight dry contact input alarms, each connected to a different pin on the ALRM-IN/OUT connector. Each alarm can then map to any of the following alarm conditions. If the external dry-contact alarm detects that any of these conditions is fulfilled, an alarm is raised, and a corresponding trap is sent to the EMS.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-354.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 451 System ManualCommercial power failure FireEnclosure door openHigh temperatureFloodLow fuelLow battery thresholdGenerator failureIntrusion detectionExternal equipment failureTo map the a dry contact alarm to an alarm condition, run the following command:npu(config)# dry-contact IN <alarm_num (1-8)> alarm {CommercialPowerFailure | Fire | EnclosueDoorOpen | HighTemperature | Flood | LowFuel | LowBatteryThreshold | GeneratorFailure | IntrusionDetection | ExternalEquipmentFailure} In this command, the alarm_num parameter maps to a pin on the ALRM IN-OUT connector. The following table lists the pin numbers of the 25-pin micro D-Type ALRM-IN/OUT connector corresponding to the alarm number you are configuring:IMPORTANTDry-contact input alarms are a means to raise a trap to the EMS when a change in conditions is notified by the external device. However, the trap may not reach the EMS because of trap rate limiting, network congestion or for reasons relating to the external equipment. Alvarion does not assume responsiblity for traps that are lost.](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-355.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 452 System ManualRefer Figure 4-2 for a diagrammatic representation of the 25-pin micro D-Type ALRM-IN/OUT connector and the numbers assigned to each pin.Table 4-25: Pin Numbers Corresponding to Dry Contact Input Alarm NumbersPin Number Alarm Number3 and 15 14 and 16 25 and 17 36 and 18 47 and 19 58 and 20 69 and 21 710 and 22 8NOTEFor more information about displaying the alarm conditions currently mapped to the micro D-Type ALRM-IN/OUT connector pins, refer Section 4.3.14.6.Command Syntaxnpu(config)# dry-contact IN <alarm_num (1-8)> alarm {CommercialPowerFailure | Fire | EnclosueDoorOpen | HighTemperature | Flood | LowFuel | LowBatteryThreshold | GeneratorFailure | IntrusionDetection | ExternalEquipmentFailure} Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-356.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 453 System ManualSyntax Description Parameter Description Presence Default ValuePossible Values<alarm_num (1-8)>Indicates the alarm number of the dry contact input alarm that is to be mapped to an alarm condition. This alarm number corresponds to a pin on the 25-pin micro D-Type jack . For more information about the pin numbers that correspond to the alarm number, refer Table 4-25.Mandatory N/A 1-8](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-357.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 454 System Manual4.3.14.4.2 Disabling Dry-contact Input AlarmsTo disable a dry contact input alarm mapped to a specific alarm condition, run the following command:npu(config)# no dry-contact IN <alarm_num (1-8)>alarm {CommercialPowerFailure | Fire | EnclosueDoorOpen | HighTemperature | Flood | LowFuel | LowBatteryThreshold | GeneratorFailure | IntrusionDetection | ExternalEquipmentFailureIndicates the alarm condition to be mapped to a pin number. Mandatory N/A CommercialPowerFailure FireEnclosueDoorOpenHighTemperatureFloodLowFuelLowBatteryThresholdGeneratorFailureIntrusionDetection ExternalExternalEquipmentFailure (can be used for defining a condition other than the ones specified by the other parameters in this command)Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-358.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 455 System Manual4.3.14.5 Managing Dry-contact Output AlarmsDry-contact output alarms are raised by the system to notify an external device connected to the 4Motion unit about a change in the system state. The external monitoring entity may take the appropriate action after receiving the notification from the 4Motion system.You can use the CLI to raise an alarm to the external entity that is connected to the dry contact output pin. After the system returns to its normal state, you can clear the dry contact output alarm that you had raised.Dry contact output alarms are connected to the 4Motion system via a 25-pin micro D-Type ALRM-IN/OUT connector on the NPU front panel. The following NOTEFor more information about mapping dry contact alarms to an alarm condition, refer to “Mapping a Dry-contact Input Alarm to an Alarm Condition” on page 450. For more information about displaying the alarm condition currently mapped to an alarm, refer to “Displaying Configuration Information for Dry-contact Input/Output Alarms” on page 458.Command Syntaxnpu(config)# no dry-contact IN <alarm_num (1-8)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<alarm_num (1-8)>Indicates the alarm number of the dry contact input alarm alarm that is to be disabled. The value of this parameter should be between 1 and 8.For more information about the pin numbers that correspond to the alarm number, refer Table 4-25.Mandatory N/A 1-8Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-359.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 456 System Manualfigure depicts the ALRM-IN/OUT connector, and the pin numbers assigned to each pin:Figure 4-3: 25-pin Micro D-Type ALRM-IN/OUT ConnectorYou can configure upto three dry contact output alarms, each mapping to a different pin number. This section describes the commands used for:“Raising Dry-contact Output Alarms” on page 456“Clearing Dry-contact Output Alarms” on page 4574.3.14.5.1 Raising Dry-contact Output AlarmsYou can raise a dry contact output alarm to any external entity that is connected to the 4Motion unit via the 25-pin micro D-Type jack on the NPU front panel. To raise a dry contact output alarm, run the following command:npu(config)# dry-contact OUT <alarm_num (1-3)> alarm <alarm name >In this command, the alarm_num parameter maps to a specific pin of the micro D-Type ALRM-IN/OUT connector. The following table lists the pin numbers of the 25-pin micro D-Type ALRM-IN/OUT connector corresponding to the alarm number you are configuring:In this table, N.C denotes Not Closed, and N.O denotes Not Open.Table 4-26: Pin Numbers Corresponding to Dry Contact Output Alarm NumbersPin Number Corresponding Alarm Number1(FIX) - 2(N.C) - 14(N.O) 111(FIX)- 12(N.C) - 13(N.O) 223(FIX) - 24(N.C) - 25(N.O) 3](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-360.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 457 System ManualRefer Figure 4-3 for a diagrammatic representation of the 25-pin micro D-Type ALRM-IN/OUT connector and the numbers assigned to each pin.4.3.14.5.2 Clearing Dry-contact Output AlarmsAfter the system returns to its normal state, run the following command to clear the dry-contact output alarm that you had raised:npu(config)# no dry-contact OUT <alarm_num (1-3)>NOTEAfter you have raised an alarm, clear this alarm when the system state returns to its normal condition. For information, refer to, “Clearing Dry-contact Output Alarms” on page 457. For more information about displaying configuration information about a dry contact output alarm, refer to “Displaying Configuration Information for Dry-contact Input/Output Alarms” on page 458.Command Syntaxnpu(config)# dry-contact OUT <alarm_num (1-3)> alarm <alarm name >Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<alarm_num (1-3)>Indicates the alarm number of the dry contact output alarm that is to be configured. This alarm number corresponds to a pin on the 25-pin micro D-Type jack . For more information about pin numbers that correspond to the alarm number, refer Table 4-26.Mandatory N/A 1-3alarm <alarm name>Indicates the name of the dry-contact alarm to be raised.Mandatory N/A Up to 256 charactersCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-361.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 458 System ManualAfter you run this command, the alarm that you had raised is cleared. 4.3.14.6 Displaying Configuration Information for Dry-contact Input/Output AlarmsTo display configuration information for dry-contact input/output alarms, run the following command:npu# show dry-contact {IN | OUT} [<alarm_num>]If you want to display configuration information for input or output alarms, specify IN or OUT. You can also specify the pin number if you want to view configuration information for particular pin used for connecting an external device to the 4Motion unit.NOTENOTEFor more information about raising a dry contact ouput alarm, refer to “Raising Dry-contact Output Alarms” on page 456.Command Syntaxnpu(config)# no dry-contact OUT <alarm_num (1-3)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<alarm_num (1-3)>Indicates the alarm number of the dry contact output alarm alarm that is to be disabled. For more information about the pin numbers that correspond to the alarm number, refer Table 4-26.Mandatory N/A 1-3Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-362.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 459 System ManualFor example, run the following command if you want to display configuration information for the dry contact input alarm connected to the 4Motion unit via pin# 8 on the NPU panel:npu# show dry-contact IN 8If you want to display configuration information for all dry contact alarms, run the following command:npu# show dry-contactNOTEAn error may occur if you have specified an incorrect pin number for a particular input/output alarm. For more information about the correct pin-to-alarm number mapping, refer Table 4-25 and Table 4-26.Command Syntaxnpu# show dry-contact {IN | OUT} [<alarm_num>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values{IN|OUT} Indicates whether configuration information is to be displayed for input or output alarms. If you do not specify this value, configuration information is displayed for all input and output alarms.Optional N/A INOUT](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-363.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 460 System Manual4.3.14.7 Configuring the Location Information for the 4Motion ShelfThe site location parameters provide general information on the site. Run the following command to configure the 4Motion shelf location information, such as the rack number and location:npu(config)# site {Name <name (32)> | Address <address(32)> | RackLocation <rack no. + position in rack (32)> | ContactPerson <name (32)> | AsnName <name (32)> |Region <area (32)> |ProductType BMAX_4M_Macro}For example, run the following command if you want to specify the site name:npu(config)# site name Site 12[<alarm_num>] Denotes the alarm number of the input or output alarm for which configuration information is to be displayed.Refer Figure 4-2 and Figure 4-3 for more information about the numbers assigned to the pins used for connecting dry contact alarms.Optional N/A 1-8 for input alarms1-3 for output alarmsDisplay FormatDry-Contact Input Alarm:AlarmNumber AlarmName InputBlocking<alarm num> <alarm name> <Yes or No>Dry-Contact Output Alarm:AlarmNumber AlarmStatus AlarmName<alarm num> <On or Off> <name>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-364.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 461 System ManualIMPORTANTAn error may occur if the length of any of these parameters exceeds the specified range. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config)# site (Name <name (32)> | Address <address(32)> | RackLocation <rack no. + position in rack (32)> | ContactPerson <name (32)> |AsnName <name (32)> |Region <area (32)> |ProductType BMAX_4M_Macro)Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible ValuesName <name (256)>}Indicates the name of the 4Motion shelf.Optional N/A String (up to 32 characters)Address <address (256)>}Indicates the address of the 4Motion site. Optional N/A String (up to 32 characters)RackLocation <rack no. + position in rack (256)>}Indicates the rack number and location of the 4Motion shelf.Optional N/A String (up to 32 characters)ContactPerson <name (256)>Indicates the name of person who is administering the 4Motion shelf.Optional String (up to 32 characters)AsnName <name (256)>Indicates the name of the Access Service Network for which 4Motion is serving as the ASN gateway.Optional N/A String (up to 32 characters)Region <area (256)>Indicates the region where the site is located. Optional N/A String (up to 32 characters)ProductType BMAX_4M_Macro Indicates the product type. In the current release it cannot be changed from the default of BMAX_4M_MacroOptional BMAX_4M_MacroBMAX_4M_Macro](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-365.png)
![Chapter 4 - Operation and Administration Using the CLI NPU Configuration4Motion 462 System Manual4.3.14.8 Configuring the Unique Identifier for the 4Motion ShelfThe Site Identifier (Site ID) is used by the management system as identifier of the site and must be unique in the managed network.The default value 0 is not a valid Site Identifier: it indicates that the Site Identifier was not configured and a valid Site Identifier must be configured. A BTS with Site Identifier 0 will not be discovered by AlvariSTAR.Since the Site Identifier is used by AlvariSTAR to identify the site, it is highly recommended not to modify it. If necessary, you must follow the Site Number Change process described in the AlvariSTAR Device Manager User Manual.To configure a unique identifier for the 4Motion shelf, run the following command:npu(config)# site identifier <site id <0-999999>>Command ModesGlobal configuration modeNOTETo display the 4Motion shelf identifer, refer to “Displaying the Unique Identifier for the 4Motion Shelf” on page 783.Command Syntaxnpu(config)# site identifier <site id <0-999999>>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values<site id <0-999999>>Indicates the ID of the 4Motion shelf.Mandatory N/A 0-999999Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-366.png)
![Chapter 4 - Operation and Administration Using the CLI Managing MS in ASN-GW4Motion 463 System Manual4.4 Managing MS in ASN-GWThis section describes the MS level commands.“Manual MS De-registration”“Displaying MS Information”4.4.1 Manual MS De-registrationRun the following command to initiate the de-registration process of the MS with the specified NAI value or of all MSs.npu(config)# de-reg ms {nai <nai-string> | all}IMPORTANTAn error may occur if NAI value is not specified. Refer to the syntax description for more information about the appropriate values and format for configuring this parameter.An error may occur also for “MS not found", in case no MS with the specified NAI is registered at ASNGW.Command Syntaxnpu(config)# de-reg ms {nai <nai-string> | all}Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Valuesde-reg ms {nai <nai-string> | all}Initiates the de-registration of the MS with the specified NAI value.If “all” is specified then, deregister all the MSs.Mandatory N/A StringCommand ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-367.png)
![Chapter 4 - Operation and Administration Using the CLI Managing MS in ASN-GW4Motion 464 System Manual4.4.2 Displaying MS InformationRun the following command to view the MS context information of the specified NAI/MSID. npu# show ms info [{nai|msid}<nai/msid string>]IMPORTANTAn error may occur if invalid NAI or invalid MSID is provided. Refer the syntax description for more information about the appropriate values and format for configuring this parameter.Command Syntaxnpu# show ms info [{nai|msid}<nai/msid string>]Privilege Level1Display FormatMS context Info: NAI = <value>MS ID = <value>Serving BS ID = Serving Flow ID1 = <value>Serving Flow GRE key = <value>Serving Flow Direction = <Uplink | Downlink>MS Flow Service Group IP = <value>|Serving Flow IDn = <value>Serving Flow GRE key = <value>Serving Flow Direction = <Uplink | Downlink>MS Flow Service Group IP = <value>Command ModesGlobal command mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-368.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 465 System Manual4.5 Managing AUsUp to seven AU objects can be created and configured, corresponding to the AU cards that can be installed in slots 1-4, 7-9 of the shelf.1Enable the AU configuration mode for the selected AU (refer to Section 4.5.1)2You can now execute any of the following tasks:»Configure one or more of the parameters tables of the AU (refer to Section 4.5.2)»Restore the default values of parameters in one or more of the parameters tables of the AU (refer to Section 4.5.3)3Terminate the AU configuration mode (refer to Section 4.5.4)In addition, you can, at any time, display configuration and status information for each of the parameters tables of the AU (refer to Section 4.5.6) or delete an existing AU object (refer to Section 4.3.10.11.5). 4.5.1 Enabling the AU Configuration Mode\Creating an AU ObjectTo configure the parameters of an AU, first enable the AU configuration mode for the specific AU. Run the following command to enable the AU configuration mode. You can also use this command to create a new AU object. A new AU object is created with default values for all parameters.npu (config)# au <(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>Specify the slot ID of the AU to be configured/created. See Figure 4-1 for slot assignment in the shelf.For example, to configure the AU in slot# 1, run the following command:npu (config)# au 1NOTEIn Release 2.0 up to 3 AUs may be used for service provisioning.To configure an AU:](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-369.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 466 System ManualIf you use this command to create a new AU, the configuration mode for this AU is automatically enabled, after which you can execute any of the following tasks:Configure one or more of the parameters tables of the AU (refer to Section 4.5.2)Restore the default values of parameters in one or more of the parameters tables of the AU (refer to Section 4.5.3)After executing the above tasks, you can terminate the AU configuration mode (refer to Section 4.5.4) and return to the global configuration mode.4.5.2 Configuring AU ParametersAfter enabling the AU configuration mode you can configure the following parameters tables:IMPORTANTAn error occurs if you specify an AU slot ID that is not in the range, 1-4, or 7-9.Command Syntaxnpu (config)# au <(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>The slot ID of the AU to be configuredMandatory N/A 1-47-9Command ModesGlobal configuration modeNOTEThe following examples are for au configuration mode for au-1 .](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-370.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 467 System ManualProperties (refer to Section 4.5.2.1)Control (refer to Section 4.5.2.2)Connectivity (refer to Section 4.5.2.3)Reserved (refer to Section 4.5.2.4)4.5.2.1 Configuring PropertiesThe properties table enables configuring the main properties of the required AU card and controlling the power on each of the AU’s ODU ports.To configure the properties parameters, run the following command:npu(config-au-1)# properties [required-type {typeThree | typeTwo}] [required-ports {four}] [required-bandwidth {fourteen | twenty | notrequired}] [port-1-power {shutDown | noShutDown}] [port-2-power {shutDown | noShutDown}] [port-3-power {shutDown | noShutDown | NA}] [port-4-power {shutDown | noShutDown | NA}]NOTEYou can display configuration information for the AU properties. For details, refer to Section 4.5.6.1.IMPORTANTAn error may occur if you provide an invalid value for any of these parameters. Refer the syntax description for more information about the appropriate values and format for configuring these parameters.Command Syntaxnpu(config-au-1)# properties [required-type {typeThree | typeTwo} ] [required-ports {four} ] [required-bandwidth {fourteen | twenty | notrequired} ] [port-1-power {shutDown | noShutDown} ] [port-2-power {shutDown | noShutDown} ] [port-3-power {shutDown | noShutDown | NA} ] [port-4-power {shutDown | noShutDown | NA} ]Privilege Level10](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-371.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 468 System ManualSyntax Description Parameter Description Presence Default Value Possible Values[required-type {typeThree | ttypeTwo} ]Defines the AU card configuration required.In the current release only typeTwo AU is available.Optional typeThree typeThreetypeTwo[required-ports {two | four} ]Defines the No of AU card ODU ports required.In the current release only four-ports AU is available.Optional Four Four[required-bandwidth {fourteen | twenty | notrequired} ]Defines the AU card Bandwidth (in MHz) required.In the current release all cards can support up to 20 MHz, except to previous generation cards that can support up to 14 MHz.Optional Twenty FourteenTwentynotrequired[port-1-power {shutDown | noShutDown} ]Controls power from AU card port 1 to ODUOptional No ShutdownshutDownnoShutDown[port-2-power {shutDown | noShutDown} ]Controls power from AU card port 2 to ODU.Optional No ShutdownshutDownnoShutDown[port-3-power {shutDown | noShutDown | NA} ]Controls power from AU card port 3 to ODU.The NA (Not Applicable) option is not relevant for a four-ports AU.Optional No ShutdownshutDownnoShutDownNA[port-4-power {shutDown | noShutDown | NA} ]Controls power from AU card port 4 to ODU.The NA (Not Applicable) option is not relevant for a four-ports AU.Optional No ShutdownshutDownnoShutDownNACommand Modesau configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-372.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 469 System Manual4.5.2.2 Configuring the Control ParameterThe control parameters enables controlling the operation of the AU.To configure the control parameter, run the following command:npu(config-au-1)# control shutdown-operation {normalOperation | reset | shutdown} 4.5.2.3 Configuring ConnectivityThe connectivity tables enables configuring the connectivity parameters for the Ethernet interface of the AU. In the current release the interface operates in 802.1q mode: In this mode, the interface accepts only VLAN-tagged packets. All packets received without VLAN tags are dropped.To configure the connectivity parameters, run the following command:npu(config-au-1)# connectivity [maxframesize <(1518 to 9000 StepSize 1)>] [bearervlanid <(0 to 4092 StepSize 1)>]Command Syntaxnpu(config-au-1)# control shutdown-operation {normalOperation | reset | shutdown}Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Valuesshutdown-operation {normalOperation | reset | shutdown}Controls the operation of the AU card: Normal Operation, Shutdown (disable power to card) or Reset.Mandatory normal OperationnormalOperationresetshutdownCommand Modesau configuration modeCommand Syntaxnpu (config-au-1)# connectivity [maxframesize <(1518 to 9000 StepSize 1)>] [bearervlanid <(0 to 4092 StepSize 1)>]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-373.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 470 System Manual4.5.2.4 Configuring AU Reserved ParametersAs the name implies, the reserved parameters table enables configuring up to 9 parameters that are reserved for possible future use. In the current release none of the reserved parameters is being used. To configure the AU reserved parameters, run the following command:Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values[maxframesize <(1518 to 9000 StepSize 1)>]The maximum frame size (in Bytes) that can be accepted on the Ethernet interface of the AU. Larger packets will be dropped.In 802.1q encapsulation mode the actual minimal frame size (including VLAN tag) is 1522 bytes, which is also the default.Must be configured to the same value as the mtu parameter for this interface in the NPU.Optional 1522 1518 to 9000[bearervlanid <(0 to 4092 StepSize 1)>]The VLAN ID of packets on the Ethernet interface of the AU. It must be configured to the same value as the if_vlan parameter of the bearer interface in the NPU.Note that VLAN 10 is used for internal management and cannot be used the bearer VLAN.Optional 11 0-4092Command Modesau-1 configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-374.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 471 System Manualnpu(config-au-1)# au-reserved [reserved-1 <string (32)>] [reserved-2 <string (32)>] [reserved-3 <string (32)>] [reserved-4 <string (32)>] [reserved-5 <string (32)>] [reserved-6 <string (32)>] [reserved-7 <string (32)>] [reserved-8 <string (32)>] [reserved-9 <string (32)>]4.5.3 Restoring Default Values for AU Configuration ParametersAfter enabling the AU configuration mode you can restore the default values for parameters in the following parameters tables:Properties (refer to Section 4.5.3.1)Control (refer to Section 4.5.3.2)Connectivity (refer to Section 4.5.3.3)Reserved (refer to Section 4.5.3.4)Command Syntaxnpu (config-au-1)# au-reserved [reserved-1 <string (32)>] [reserved-2 <string (32)>] [reserved-3 <string (32)>] [reserved-4 <string (32)>] [reserved-5 <string (32)>] [reserved-6 <string (32)>] [reserved-7 <string (32)>] [reserved-8 <string (32)>] [reserved-9 <string (32)>]Privilege Level10Syntax Description Parameter Description Presence Default Value Possible Values[reserved-N <string (32)>] (N=1-9)Reserved parameter number NOptional null (an empty string)A string of 32 printable characters.Command Modesau configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-375.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 472 System Manual4.5.3.1 Restoring the Default Values of Properties ParametersTo restore the some or all of the Properties parameters to their default value, run the following command:npu(config-au-1)# no properties [required-type] [required-ports] [required-bandwidth] [port-1-power] [port-2-power] [port-3-power] [port-4-power]You can restore only selected parameters to their default value by specifying only those parameter. For example, to restore only the required type to the default value (threeDSP), run the following command:npu(config-au-1)# no properties required-typeThe parameter will be restored to its default value, while the other parameters will remain unchanged.To restore all properties parameters to their default value, run the following command:npu(config-au-1)# no properties4.5.3.2 Restoring the Default Value of the Control ParameterTo restore the Control parameter to the default value (normalOperation), run the following command:npu(config-au-1)# no controlNOTERefer to Section 4.5.2.1 for a description and default values of these parameters.Command Syntaxnpu(config-au-1)# no properties [required-type] [required-ports] [required-bandwidth] [port-1-power] [port-2-power] [port-3-power] [port-4-power]Privilege Level10Command Modesau configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-376.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 473 System Manual4.5.3.3 Restoring the Default Values of Connectivity ParametersTo restore Connectivity parameters do their default value, run the following command:npu(config-au-1)# no connectivity [maxframesize] [bearervlanid]You can restore only one of the parameters to its default value by specifying only that parameter. For example, to restore only the maximum frame size to the default (1522), run the following command:npu(config-au-1)# no connectivity maxframesizeThe maximum frame size will be restored to its default value, while the bearervlanid parameter will remain unchanged.To restore both parameters to their default value, run the following command:npu(config-au-1)# no connectivityCommand Syntaxnpu(config-au-1)# no controlPrivilege Level10Command ModesGlobal configuration modeNOTERefer to Section 4.5.2.3 for a description and default values of these parameters.Command Syntaxnpu(config-au-1)# no connectivity [maxframesize] [bearervlanid]Privilege Level10Command Modesau configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-377.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 474 System Manual4.5.3.4 Restoring the Default Values of AU Reserved ParametersTo restore the AU Reserved parameters to their default value, run the following command:npu(config-au-1)# no au-reserved [reserved-1] [reserved-2] [reserved-3] [reserved-4] [reserved-5] [reserved-6] [reserved-7] [reserved-8] [reserved-9]You can restore only selected parameters to their default value by specifying only those parameter. For example, to restore only the reserved-1 parameter to its default values, run the following command:npu(config-au-1)# no au-reserved reserved-1This parameter will be restored to the default value, while the other parameters will remain unchanged.To restore all parameters to their default value, run the following command:npu(config-au-1)# no au-reserved4.5.4 Terminating the AU Configuration ModeRun the following command to terminate the au configuration mode:npu(config-au-1)# exitNOTERefer to Section 4.5.2.4 for a description and default values of these parameters.Command Syntaxnpu(config-au-1)# no au-reserved [reserved-1] [reserved-2] [reserved-3] [reserved-4] [reserved-5] [reserved-6] [reserved-7] [reserved-8] [reserved-9]Privilege Level10Command ModesGlobal configuration modeCommand Syntaxnpu(config-au-1)# exit](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-378.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 475 System Manual4.5.5 Deleting an AU ObjectRun the following command to delete an AU object:npu(config)# no au <(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>4.5.6 Displaying Configuration and Status Information for AU ParametersYou can display the current configuration and (where applicable) additional status information for the following parameters tables:Properties (refer to Section 4.5.6.1)Privilege Level10Command Modesau-1 configuration modeIMPORTANTAn associated AU (specified in a Sector Association) cannot be deleted.Command Syntaxnpu(config)# no au <(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>Privilege Level10Syntax Description Parameter Description Presence Default ValuePossible Values <(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>The slot ID of the AU card Mandatory N/A 1-4, 7-9Command ModesGlobal configuration mode](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-379.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 476 System ManualControl (refer to Section 4.5.6.2)Connectivity (refer to Section 4.5.6.3)Reserved (refer to Section 4.5.6.4)4.5.6.1 Displaying Configuration and Status Information for AU PropertiesTo display configuration and status information for the properties of a specific or all AU objects, run the following command: npu# show properties au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Specify the au slot ID (1-4, 7-9) if you want to display configuration and status information for a particular AU. Do not specify a value for this parameter if you want to view configuration and status information for all existing AU objects.Command Syntaxnpu# show properties au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]The slot ID of the AU Specify a value for this parameter if you want to display the properties of a specific AU. Do not specify a value for this parameter if you want to display the properties of all AUs.Optional N/A 1-4, 7-9](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-380.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 477 System ManualIn addition to the configurable parameters, the following status parameters are also displayed:Display Format(for each existing AU object if requested for all AUs)SlotNo. :<value>RequiredType :<value>RequiredPorts :<value>RequiredBandwidth(MHz) :<value>InstalledStatus :<value>InstalledType :<value> (0 for notinstalled AU)InstalledPorts :<value> (0 for notinstalled AU)InstalledBandwidth(MHz) :<value> (0 for notinstalled AU)HWVersion :<value> (null for notinstalled AU)HWRevision :<value> (null for notinstalled AU)SerialNo. :<value> (null for notinstalled AU)BootVersion :<value> (null for notinstalled AU)IFVersion :<value> (null for notinstalled AU)IFRevision :<value> (null for notinstalled AU)Port1PowertoODU :<value>Port2PowertoODU :<value>Port3PowertoODU :<value>Port4PowertoODU :<value>Command ModesGlobal command modeParameter Description Possible ValuesInstalledStatus Indicates whether an AU card is installed in the slot.Following parameters are applicable only for installed AU.installed (1)notinstalled (0)](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-381.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 478 System Manual4.5.6.2 Displaying Configuration for AU ControlTo display configuration for the Control parameter of a specific or all AU objects, run the following command: npu# show control au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Specify the au slot ID (1-4, 7-9) if you want to display configuration information for a particular AU. Do not specify a value for this parameter if you want to view configuration information for all existing AU objects.InstalledType The AU Type. threeDSP (1)twoDSP (2)other (3)auNotDetected (4)InstalledPorts The number of ODU ports. two (1)four (2)other (3)auNotDetected (4)InstalledBandwidth(MHz) The bandwidth supported by the AU.fourteen (1)twenty (2)other (3)auNotDetected (4)HWVersion AU HW Version number <number>HWRevision AU HW Revision number <number>SerialNo. AU Serial number <number>BootVersion AU Boot SW Version number <string>IFVersion AU IF Version number <number>IFRevision AU HW Revision number <number>Command Syntaxnpu# show control au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Privilege Level1Parameter Description Possible Values](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-382.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 479 System Manual4.5.6.3 Displaying Configuration Information for AU Connectivity ParametersTo display configuration information for the connectivity parameters of a specific or all AU objects, run the following command: npu# show connectivity au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Specify the au slot ID (1-4, 7-9) if you want to display configuration for a particular AU. Do not specify a value for this parameter if you want to view configuration for all existing AU objects.The displayed information includes also configured values for relevant parameters that are configured for the internal management interface of the NPU.Syntax Description Parameter Description Presence Default ValuePossible Values[<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]The slot ID of the AU Specify a value for this parameter if you want to display the control parameter of a specific AU. Do not specify a value for this parameter if you want to display the control parameters of all AUs.Optional N/A 1-4, 7-9Display Format(for each existing AU object if requested for all AUs)SlotNo. :<value>AUPowerControl :<value>Command ModesGlobal command modeCommand Syntaxnpu# show connectivity au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-383.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 480 System ManualIn addition to the configurable parameters, the following status parameters are also displayed:Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]The slot ID of the AU Specify a value for this parameter if you want to display the connectivity parameters of a specific AU. Do not specify a value for this parameter if you want to display the connectivity parameters of all AUs.Optional N/A 1-4, 7-9Display Format(for each existing AU object if requested for all AUs)SlotNo. :<value>EncapsulationMode :vlanAwareBridging(0)MaxFrameSize(Bytes) :<value>InternalManagementVLANID :<value>BearerVLANID :<value>InternalManagementIPAddress :<value>InternalManagementIPSubnetMask :<value>Command ModesGlobal command modeParameter Description Possible ValuesEncapsulationMode The Ethernet encapsulation mode of the card’s Ethernet port (hard coded in production).vlanAwareBridging(0)InternalManagementVLANID The VLAN ID Management of the shelf.(hard coded in production)0-4092](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-384.png)
![Chapter 4 - Operation and Administration Using the CLI Managing AUs4Motion 481 System Manual4.5.6.4 Displaying Configuration Information for AU Reserved ParametersTo display configuration information for the reserved parameters of a specific or all AU objects, run the following command: npu# show au-reserved au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Specify the au slot ID (1-4, 7-9) if you want to display configuration for a particular AU. Do not specify a value for this parameter if you want to view configuration for all existing AU objects.InternalManagementIPAddress IP Address of the internainterface of the AU. Acquired via DHCP.IP addressInternalManagementIPSubnetMask Subnet Mask of the internainterface of the AU. Acquired via DHCP.Subnet maskCommand Syntaxnpu# show au-reserved au [<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]Privilege Level1Syntax Description Parameter Description Presence Default ValuePossible Values[<(1 to 4 StepSize 1) | (7 to 9 StepSize 1)>]The slot ID of the AU Specify a value for this parameter if you want to display the reserved parameters of a specific AU. Do not specify a value for this parameter if you want to display the reserved parameters of all AUs.Optional N/A 1-4, 7-9](https://usermanual.wiki/Alvarion-Technologies/BMAX-OR-25.Manual-2/User-Guide-1114030-Page-385.png)