Device Manager. Device Provisioning. Preparing to Register a Device

Transcription

1 You access the device manager by clicking the tab in the DCC UI. The device manager provides a consolidated interface to perform various tasks on an individual Customer Premises Equipment (CPE). Specifically it allows you to perform the functions: Device Provisioning, page 1 Log Uploads and Triggers, page 28 View Information about a Device, page 29 Device Operations, page 31 Status Messages, page 39 Updating Device Configuration, page 47 Device Provisioning You can register and activate a new device at a time using the Register screen in the DCC UI. Alternatively, you can activate an already registered device using update button in the DCC UI. Preparing to Register a Device The device ID is a combination of the Organizationally Unique Identifier (OUI) number (for example, 001B67) of the manufacturer and the 15 digit serial number, which is the International Mobile Equipment Identity (IMEI) number of the FAP (for example, ). When you enter the first few characters of the device ID, the performs an automatic lookup to find all device IDs beginning with that string instead of having to scroll down the entire list to find the device ID. Also, as you start entering a new device ID, a tooltip is displayed indicating that the device is not registered and the Register option is enabled to allow for registering the device. To provide specific cell ID (CID) and Service Access Code (SAC) ID for the AP instead of the RMS automatic assignment, register the FAP or update the already registered FAP by providing the CID and SAC ID from the OSS. The provided SAC ID and CID should be defined within the SAI and Cell pool defined and the new CID value should belong to same FemtoGateway. This functionality is not supported from the DCC UI. 1

2 Preparing to Register a Device Before You Begin Before registering a device you should verify the following: Latest version of RMS is installed. Appropriate network connectivity is established between the RDU and the DPE, and between the DPE and the FAPs. PMGDB if installed should be up and running. You can create groups from the DCC-UI Groups and IDs tab. The register button is activated when you enter in an identifier for a device in the. Default groups and pools are created only for reference. Create your own Groups and Pools before registration. Before registering an Enterprise device, you must create all of the following: Area group FemtoGateway group UMTSSecGateway group LTESecGateway group HeNBGW group Region group Site group Sub-Site group (Optional) Enterprise group SAI pool CELL pool LTE-CELL pool (Optional) Alarms profile Before registering a Residential device, you must create all of the following: Area group Femto gateway group HeNBGW group UMTSSecGateway group LTESecGateway group Region group Cell pool 2

3 Registering a Device in Enterprise Mode SAI pool LTE-CELL pool Registering a Device in Enterprise Mode Use this task to register a device in Enterprise mode after the Device Registration screen is displayed. Only open mode is supported for enterprise devices. This means that no whitelist is supported and all access control is determined at the HNB-GW. Before You Begin You should have completed all prerequisites for registering an Enterprise device, including creating any required groups and pools. Refer to Preparing to Register a Device, on page 1. While registering an enterprise inner device, multicell active entry device or multicell idle entry device, the grid should be enabled for the selected site. The grid should be disabled for standalone active entry and idle entry devices. The grid can be enabled or disabled at Site group level. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 If you are registering an LTE device, verify that the LTE radio button is checked. For UMTS device, verify that the UMTS radio button is checked. Uncheck the Residential mode check box. Optionally, add the Subscriber ID and Secondary ID to be associated with the device. Select the Enterprise to be assigned to the device from the Enterprise drop-down list. Select the Site to be used from the Site drop-down list. Optionally select the Sub Site to be used from the Sub Site drop-down list. Optionally select the group name from the RF Profile drop-down list. RF profile is used for RF tuning and configuration (power settings, handover rules, and so on). Select the AP role to be assigned to the device from the AP Role drop-down list. The drop-down list provides you with these three options: Active Entry AP AP in this role offers full idle and connected mode mobility on par with macrocell to macrocell handover. The number of APs is strictly limited by macro constraints (32 Inter RAT and Inter Frequency neighbors total), because it requires configuration of unique AP primary scrambling code (PSC) and Cell ID in macro neighbor list. Inner AP AP in this role does not offer active macrocell to femtocell mobility in idle or connected mode, and has constrained or disabled femtocell to macrocell mobility. This concept is unique to multicell deployments. The APs in this role support mobility with other APs in the multicell grid. The advantage of this role over Idle Entry AP is that Inner APs can use a larger set of PSCs that are unknown to the 3

4 Registering a Device in Residential Mode macrocell, thereby reducing PSC conflicts among those APs. Disable Inner AP role for Standalone Enterprise AP. Idle Entry AP AP in this role offers full mobility with macrocell in idle and connected mode, with the exception of macrocell to femtocell handover which is disabled in macrocell. The advantage of such deployment is high scaling because of the reuse of AP PSCs in the macro neighbor list. Primarily, residential APs are deployed in this role due to large quantities. Step 9 Step 10 Step 11 Step 12 The AP usage role is assigned by the administrator. Select the AP Purpose for the device: Coverage or Capacity. APs are classified by their intended purpose to provide capacity or coverage. Selecting Coverage or Capacity purpose has no functional effect if the AP being registered is an Inner AP. This field can be left as is. Coverage provides network connectivity at all desired locations. Capacity provides sufficient bandwidth to satisfy the communication requirements of the client. APs classified for capacity are assumed to be deployed in areas of sufficient macro coverage. The default AP Purpose is Coverage. Check the Activated check box. This option controls whether the device is allowed to activate its radio. If you do not select the Activated check box while registering the device, you can activate the registered device later by clicking Provision and selecting Update. Provide a valid Tracking Area Code (TAC) ID value for the LTE device. The TAC ID value should be from the list set at the associated HeNB-GW group Tracking Area Identity (TAI) list. Click Register in the Device Registration dialog box. After registering the device, the successfully registered device message is displayed at the top left corner of the screen along with the dashboard. Registering a Device in Residential Mode Use this task to register a device in Residential mode after the Device Registration screen is displayed. UMTS residential devices can be registered in either closed or open mode. Once the device is operational you can verify whether it is in open or closed mode by using this command from the HNB gateway: show hnbgw sessions full LTE residential devices can be registered in open mode only. Before You Begin You should have completed all prerequisites for registering an Residential device, including creating any required groups and pools. Refer to Preparing to Register a Device, on page 1. 4

5 Register a Device with a New Group Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 If you are registering an LTE device, verify that the LTE radio button is checked. Check the Residential Deployment check box. The Residential mode check box is checked by default. Optionally, add the Subscriber ID and Secondary ID to be associated with the device. Select the area to be assigned to the device from the Area drop-down list box. Specify the Latitude and Longitude value to get the area. To do this configure the PMG DB and connect it to the Central Node. Refer to the RMS Installation Guide, Configuration of PMGDB with Central Node for more details. Optionally select the group name from the RF Profile drop-down list. RF profile is used for RF tuning and configuration (power settings, handover rules, and so on). Check the Activated check box. The Activated check box is checked by default. This option controls whether the device is allowed to activate its radio. If you do not select the Activated check box while registering the device, you can activate the registered device later by clicking Provision and selecting Update. Select the Closed mode check box to register a device in closed mode access. Step 9 Update the details such as White list, ACL. ACL is the access control list which holds IMSI of the UE of 14 to 15 digits. Step 10 Step 11 Step 12 Step 13 Click Remove selected to remove the added White lists/ ACL. Provide a valid TAC ID value for the LTE device. The TAC ID value should be from the list set at the associated HeNB-GW group TAI list. Optionally, click the Assign Geographical Identifier checkbox and add the Geographical Identifier Code or add the IU SAC ID to be associated with the device. Click Register in the Device Registration dialog box. After registering the device, the successfully registered device message is displayed at the top left corner of the screen along with the dashboard. To provide specific cell ID (CID) and Service Access Code (SAC) ID for the AP instead of the RMS automatic assignment, register the FAP or update the already registered FAP by providing the CID and SAC ID from the OSS. The provided SAC ID and CID should be defined within the SAI and Cell pool defined and the new CID value should belong to same FemtoGateway. This functionality is not supported from the DCC UI. Register a Device with a New Group If a device is registered to an existing group, and you need to associate it with a new group, follow this procedure to change the group with which the device is registered. Procedure Step 1 Step 2 Select the device that you need to provision with the new group from the Select Device drop-down list in the screen. Select Delete Device from the Provision drop-down list. Refer to Deleting a Device, on page 38 for more information. 5

6 Assigning a Device to a New Site Step 3 Step 4 Enter a the device ID in the Select Device text box in the screen and click Register. Select the new group for which the device needs to be provisioned and register the device as described in Preparing to Register a Device, on page 1, Registering a Device in Enterprise Mode, on page 3 and Registering a Device in Residential Mode, on page 4 For enterprise registration a direct group association with the device is not possible. Therefore, pair the site associated with the device and the new group. Assigning a Device to a New Site Use this task to associate a device with a different site than the site used when the device was originally provisioned. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 From the Group and ID tab in the DCC UI, select Groups from the left navigation pane. Click the Site tab and click Add. Refer to Adding a Group Instance to add a new site group using the same enterprise that was previously associated with the site. Select a device that needs to be reassigned using the device identifier fields at the top of the screen. Select Update from the Provision drop-down list. Change the Site to be the new site to which you are registering the device. Refer to Adding a Group Instance. The above device assignment can be accomplished through the OSS using the PMG NB API. For more information on the PMG NB API usage, see the Cisco RAN Management System API Guide. The TAC ID value should be from the list set at the associated HeNB-GW group TAI list. Reassign a Site to a Different Area Use this task to assign a site to a different area. Procedure Step 1 Step 2 Step 3 Step 4 From the Group and ID tab in the DCC UI, select Groups from the left navigation pane. Click the Site tab and select an existing site. Click Update. Do one of these: 6

7 Updating a Device Click Area Association and change the Area to which the site or device needs to be associated. Unclick Area Association and specify the latitude and longitude coordinates of the area. Reassignment of a site to a different area can be accomplished through the OSS using PMG NB API. For more information on the PMG NB API usage, see the Cisco RAN Management System API Guide. After reassigning the site to new assigned area, run the reassign.sh script to move the already registered FAPs under the given site to the newly assigned area and FemtoGateway (for UMTS device) and HeNB-GW (for LTE device). This might also change the CID, SAC ID, and TAI list depending on the cell pool, SAI pool, and HeNB-GW associated with the new area. Updating a Device Use this task to activate a registered device or to manipulate the values such as RF Profile, AP Role, AP Purpose (for Enterprise mode), TACID (for LTE device), and white list, ACL (for Residential mode) specified during registration. The dialog box displayed for updating a device depends on whether the device is registered in Residential or Enterprise mode. If the device is associated with an Enterprise and Site group, the Enterprise update screen is displayed, otherwise the Residential update screen is displayed. You can customize the Enterprise and Residential update dialog boxes using dynamic configurations. Refer to Configuring DCC Dialog Boxes. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Select a registered Device ID from the Select Device drop-down list box in the screen. The latest ten AP EIDs are displayed in the drop down configuration. Providing the first few characters of the device EID displays all the relevant EIDs. Select the Provision tab, and select Update from the drop-down list. The Update Device Registration dialog box is displayed with the selected Device ID value automatically populated in the Device ID text box. The dialog box displayed for updating a device depends on whether the device is registered in Residential or Enterprise mode. Select Activated. Select this option only if the device was not activated during registration. (Optional) Update the required information regarding the device. For more information regarding the specific fields, refer to Registering a Device in Residential Mode, on page 4 or Registering a Device in Enterprise Mode. You have an option to clear in the tampered state of the device in case the device reports as, tampered. Click Update. After updating a device, the dashboard is displayed together with the successfully updated message at the top left corner of the screen. 7

8 Enabling Location Verification Changing the TAC ID associates the HeNB-GW based on the TAI list. Enabling Location Verification Location Verification (LV) is part of provisioning flow in which before unlocking the HNB for Radio On, its location is verified to ensure that the HNB is still in the same location where it was registered. RMS supports the following types of Location Verification: Global Positioning System (GPS) Expected Detected Neighbors (EDN) Detected Neighbor Location (DNL) Detected Neighbor MCC/MNC (DNM) IP address Subnet Match (ISM) IP based LV (IPL) Chained Intra Grid (CIG) Detected Neighbor Benchmark (DNB) Chained Intra Chassis (CIC) All the above LV methods are configurable from the RMS. Configuration to Control Location Verification Here are a number of options to control how location verification is configured: 1 Location Verification can be skipped by setting the property present at the Area group level, FC-NO-LV to true By default the property exists at Area and Region level in DCC UI. The property can be set at any group level or device level from the BAC UI. 2 To ignore REM-based LV (DNM, EDN, DNL, DNB) and bring up the AP in a situation where there are no macrocells in the area, set the FC-NO-NEIGHBOR-LV-BYPASS custom property to "true" at the device or group level in the BAC UI. If the FC-NO-NEIGHBOR-LV-BYPASS property is set to true and macrocells are not detected as part of a REM scan then all REM-based LV attempts return "valid location" and pass the location check. By default, the property is present at the Region level in the DCC UI. 3 To ensure that neighbor location verification is performed on macrocells only and not femtocells, the power threshold can be set using the custom property FC-TRANSMISSION-POWER-THRESHOLD in the BAC UI. The default value is 25dBm. The value of this threshold is compared to the PCPICHTxPower property value of any detected neighbors and only those neighbors whose PCPICHTxPower value is greater than the FC-TRANSMISSION-POWER-THRESHOLD are considered as valid neighbors for performing location verification. By default, the property is present at the Region level in the DCC UI. 8

9 Enabling Location Verification The BAC custom properties for controlling location verification are listed here: Property Name Property Type Description FC-NO-LV Boolean LV is skipped. FC-NO-NEIGHBOR-LV-BYPASS FC-TRANSMISSION-POWER- THRESHOLD Boolean Integer REM-based LV is passed if there are no macrocells in the area. The default value is "true." To filter the detected neighbors based on power threshold comparison with PCPICHTxPower of the detected neighbor The default value is "25". To configure how often NWL scans are performed, use this custom property: Property Name FC-PERIODIC-NWL -SCAN-INTERVAL Format Integer, number of seconds Description This custom property is configured by BAC during runtime based on the NWL location verification results. If GPS is out of tolerance, this property is not affected. The default is 20 minutes (1200 seconds) for a failed NWL scan interval and 24 hours for a successful NWL scan interval. Global Positioning System Global Positioning System (GPS) location verification (LV) verifies the location of the HNB based on the comparison between Reported Latitude/Longitude by HNB during GPS scan and the expected latitude/longitude of the HNB provided during HNB Registration. If the distance between Expected Latitude/Longitude and Reported Latitude/Longitude is within the GPS tolerance, then the GPS LV will pass. During the initial boot, if GPS and NWL-based LV are enabled, GPS may take longer to acquire the GPS lock than the NWL scan. The UMTS provisioning flow ensures that the GPS location verification check is the first location verification check. The NWL location verification check is performed only after receiving the GPS scan status as success or timeout during the initial boot. Use the FC-GPS-TIME-OUT parameter to configure the timeout value. 9

10 Enabling Location Verification If the PMG DB is installed in the RMS system with Area to Latitude/Longitude mapping, then create the Area with the unique identifier that defines the mapping of the Area key with the Latitude/Longitude stored in the PMG DB. After creating the Area, then create the Site group by selecting Latitude/Longitude instead of Area, so that the Area is automatically selected from the mapped Latitude/Longitude from PMG DB. After creating the Site, select the Latitude/Longitude when registering the Residential FAP and similarly, select the Site when registering the Enterprise FAP. All the created and registered Area, Site, and Residential FAP with Latitude/Longitude, these Latitude/Longitude will be treated as the Expected Latitude/Longitude for the FAP. In this case, there is no need to define the Expected Lat/Long for GPS LV. In case PMG DB does not exist and there is no mapping of Latitude/Longitude to the Area, then after registering the AP (Residential or Enterprise), select the Custom property (FC-EXP-LAT and FC-EXP-LONG) from BAC UI and provide the Expected Latitude/Longitude of the AP at the Device or Group level for GPS LV. Property Format Expected Value Comments FC-GPS-ENABLED Boolean true or false Enables the GPS LV methods during the provisioning flow FC-EXP-LAT Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI to if configured from the DCC UI; to if configured from the BAC UI. Expected latitude of the HNB. Refer to section to understand more on this parameter and for the input of this parameter. FC-EXP-LONG Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI to if configured from the DCC UI; to if configured from the BAC UI Expected longitude of the HNB. Refer to previous section to understand more on this parameter and for the input of this parameter. 10

11 Enabling Location Verification FC-GPS-TOLERANCE Integer value in meters GPS Tolerance in meters The distance between the expected latitude or longitude and the reported latitude or longitude is calculated using the Haversine formula and is then compared with the GPS tolerance. If the actual distance is less than or equal to the GPS tolerance then the GPS passes, otherwise the GPS fails. FC-GPS-LAT Actual/Reported GPS Latitude Actual/Reported GPS Latitude Read-only parameter and should not be configured. Once the HNB completes the GPS scan, it reports the actual latitude which is populated automatically at the device level. FC-GPS-LONG Actual/Reported GPS Longitude Actual/Reported GPS Longitude Read-only parameter and should not be configured. Once the HNB completes the GPS scan, it reports the actual longitude which is populated automatically at the device level. FC-GPS-TIME-OUT Integer Number of seconds Timeout value in seconds from when the scan started to when it times out. A timed out scan is reported as Error_TIMEOUT with error details indicating "Timed out". The default value is 1200 (seconds). The above properties are available at the Region level in the DCC UI. Once the LV method is verified, then at device level, below two properties will automatically get configured displaying the GPS status. FC-GPS-STATUS= This will be either Valid Location, Wrong Location, Missing expected location, or Error: <cause> FC-GPS-STATUS-TS =This is a timestamp when the above state of the GPS status is changed. 11

12 Enabling Location Verification GPS Status Valid Location Wrong Location Missing Expected Location Error: <cause> Comments GPS Success GPS Failure Expected Latitude and Longitude are missing There is some issue in GPS scan or GPS scan could not locate the satellite and got timed Out Expected Detected Neighbor Expected Detected Neighbor (EDN) location verification (LV) verifies the neighbors based on reported neighbors discovered during 2G and 3G REM scan. Following are the properties required for enabling and configuring EDN LV. Property Format Expected Value Comments FC-EDN-ENABLED Boolean True or false Enables the verification of EDN LV methods during the provisioning flow FC-EDN-LIST Comma separated value where each value defines the neighbor ID Neighbor ID For example, 3G , 2G List of expected neighbors. If the list is not provided then the LV returns the status as unknown. FC-EDN-TOLERANCE Single value integer Integer This property defines the tolerance, or threshold to pass the LV. The default value is 1. If the value is not configured then by default, the tolerance will be considered as 1. For example, if the value of this property is 3 then a minimum of three neighbors are expected to match to pass EDN LV, else the result of the LV methods is decided based on the next 2 properties (FC-EDN-NO-MATCH-STATUS and FC-EDN-NO-NEIGHBOR-STATUS). 12

13 Enabling Location Verification FC-EDN-NO-MATCH-STATUS String "unknown"/ "failure" If none of the valid neighbors match and the detected neighbor count is not zero then the result of the method is determined by the configured value, either "unknown" or "failure." The default value is "unknown". Hence if the property is not defined, then LV returns "unknown." FC-EDN-NO-NEIGHBOR-STATUS String "unknown"/ "failure" If none of the valid neighbors match and the detected neighbor count is zero, the result of the method is determined by the configured value, either "unknown" or "failure". The default value is "unknown." Hence if the property is not defined, then LV returns "unknown." The above properties are available at the Region level in the DCC UI. After the LV method is verified, at the device level the following two properties are automatically configured displaying the EDN status. FC-EDN-STATUS = This is either Valid Location, Wrong Location, Ignoring Wrong Location, Missing expected neighbors or Error: <cause>. FC-EDN-STATUS-TS = This is a timestamp when the above state of the EDN status is changed. See Additional Location Verification Tasks for more information on how to configure the Neighbor ID. Below is the status and description of all the EDN: EDN Status Description Valid Location Wrong Location Ignoring Wrong Location Missing expected neighbors Error: <cause> EDN Success or "FC-NO-NEIGHBORS-LV-BYPASS" is set as true and macrocells are not detected EDN Failure No matching neighbor, or no neighbors detected and "unknown" is returned EDN List is missing or not configured and "unknown" is returned There is some issue in 2G or 3G REM scan 13

14 Enabling Location Verification Detected Neighbor Location Detected Neighbor Location (DNL) location verification (LV) verifies the detected neighbor's ID and then compares the location configured in the file with that reported by the HNB. If the distance between latitude/longitude of the HNB and that configured in file is within the tolerance then the LV method passes. Following are the properties required for enabling and configuring the DNL LV: Property Format Expected Value Comments FC-DNL-ENABLED Boolean True or false Enables the verification of DNL LV methods during the provisioning flow FC-CELL-LOC-FILE Filename Filename which contains the expected neighbor ID along with the latitude and longitude for location verification. The file is added to RDU through BAC. See Appendix for more details on this process. FC-EXP-LAT Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI to if configured from the DCC UI; to if configured from the BAC UI. FC-EXP-LONG Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI to if configured from the DCC UI; to if configured from the BAC UI FC-DNL-TOLERANCE Integer Great Circle Distance (GCD) (in meters) Defines the tolerance or threshold value in distance to pass the LV. The default value is 5000 m. 14

15 Enabling Location Verification FC-DNL-NO-MATCH-STATUS String "unknown"/ "failure" Used only when macro is detected and the macro matches the cell ID configured in DNL file. The result of out of tolerance when a neighbor is matched is decided by this property. Either unknown or failure. Default value is unknown. so if this property is not defined, by default the flow considers it as failure. FC-DNL-NO-NEIGHBOR-STATUS String "unknown"/ "failure" If none of the valid neighbors match and the detected neighbor count is zero, then the result of the method is determined by the configured value, either unknown or failure. The default value is unknown. Hence if the property is not defined, then LV will return unknown. The above properties are available at the Region level in the DCC UI. The file entry for the DNL is as follows: The cell location file is a text file comprised one entry per line. Each entry is comma separated and consists of: <neighbor identifier>, <neighbor latitude>, <neighbor longitude>. Where, <neighbor identifier> is as per mentioned in REM Neighbor Identifier <neighbor latitude> is the latitude of the neighbor <neighbor longitude> is the longitude of the neighbor For example: 2G , , G , ,

16 Enabling Location Verification Once the LV method is verified then at device level below two properties will automatically get configured displaying the DNL status. FC-DNL-STATUS= this will be either Valid Location, Wrong Location, Ignoring Wrong Location, Missing cell location file, Detected neighbors missing from cell location file, Missing expected location or Error: <cause> FC-DNL-STATUS-TS= The timestamp when the above state of the DNL status is changed. Refer to the appendix to understand how to configure the Neighbor ID. Below is the status and description of the DNL: DNL Status Valid Location Wrong Location Ignoring Wrong Location Missing cell location file Detected neighbors missing from cell location file Missing expected location Error: <cause> Description DNL Success or "FC-NO-NEIGHBORS-LV-BYPASS" is set as true and macrocells are not detected DNL Failure Detected macros that are part of the DNL file but are out of tolerance and FC-DNL-NO-MATCH-STATUS is configured as "Unknown." No neighbors are detected and FC-DNL-NO-NEIGHBOR-STATUS is configured as "Unknown." DNL expected neighbor file is missing and "Unknown" is returned. File does not have expected latitude or longitude or neighbor ID, or detected macro is not present in file HNB latitude or longitude is not configured Issue in 2G or 3G REM scan Detected Neighbor MCC/MNC Detected Neighbor Mobile Country Code (MCC) or Mobile Network Code (MNC) [DNM] location verification (LV) verifies the location by the location of the HNB by validating the reported Public Land Mobile Network Identifier (PLMN ID) of the detected neighbor. The PLMNID is comprised of the MCC and the MNC. Following are the properties required for enabling and configuring this LV method. Property Format Expected Value Comments FC-DNM-ENABLED Boolean True or false Enables the verification of DNM LV methods during the provisioning flow 16

17 Enabling Location Verification FC-DNM-LIST Comma separated value where each value defines the MCC or PLMNID of the neighbor MCC and MNC of the expected neighbor. E.g , where 116 = MCC and 113 = MNC List of expected neighbors. If the list is not provided then the LV returns the status as unknown. FC-DNM-NO-MATCH-STATUS String "unknown" or "failure" If none of the valid neighbors are matching and the detected neighbor count is not zero, then the result of the method is determined by the configured value, either unknown or failure. The default value is "unknown," hence if the property is not defined, then LV returns "unknown". FC-DNM-NO-NEIGHBOR-STATUS String "unknown" or "failure" If none of the valid neighbors match and the detected neighbor count is zero, then the result of the method is determined by the configured value, either unknown or failure. The default value is "unknown," hence if the property is not defined, then LV will return unknown. The above properties are available at the Region level in the DCC UI. Once the LV method is verified then at device level, below two properties will automatically get configured displaying the DNM status. FC-DNM-STATUS = This is either Valid Location, Wrong Location, Ignoring Wrong Location and Missing valid MCC/MNCs FC-DNM-STATUS-TS = This is a timestamp when the above state of the DNM status is changed. See Additional Location Verification Tasks for more information on how to configure the Neighbor ID. Below is the status and description of all the DNM: DNM Status Comments Valid Location DNM Success or "FC-NO-NEIGHBORS-LV-BYPASS" is set as true and macrocells are not detected 17

18 Enabling Location Verification Wrong Location Ignoring Wrong Location Missing valid MCC/MNCs Error: <cause> DNM Failure No Matching neighbor or no neighbors detected and "unknown" is returned DNM List is missing or not configured and "unknown" is returned. There is some issue in 2G or 3G REM scan IP Address Subnet Match The IP Address Subnet Match (ISM) location verification (LV) method uses the source IP address subnet match defined in CIDR format of the sessions to verify if the HNB is communicating with the allowed subnet. Following are the properties required for enabling and configuring the ISM LV. Property Format Expected Value Comments FC-ISM-ENABLED Boolean True or false Enables the verification of ISM LV methods during the provisioning flow FC-ISM-File Filename Filename Filename which contains the allowed IPv4 address subnets FC-ISM-REJECT-UNKNOWN Boolean True or false If the property is true or not present or not configured, and the HNB IP address does not match the configured IP address in the file, then the LV method returns "Failure". If the parameter is False and HNB IP address does not match with the IP address configured in the File then the LV method returns "Unknown" and logs the correct subnet as a warning message in the troubleshooting logs for you to configure the correct value in the file, if required. The above properties are available at the Region level in the DCC UI. The IP address subnet match (ISM) file is a text file comprised of one entry per line. Each entry is a IPv4 subnet defined as CIDR notation (<network address>/<mask bits>). For example, /24, /24. Save the file with some name, for example ISM.txt and give the same name for the property FC-ISM-FILE. Once the LV method is verified then at device level, below two properties will automatically get configured displaying the ISM status. FC-ISM-STATUS = This is either Valid Location, Wrong Location, Missing ISM file or Unknown subnet 18

19 Enabling Location Verification FC-ISM-STATUS-TS = This is a timestamp when the above state of the ISM status is changed. See Additional Location Verification Tasks for more information on how to configure the Neighbor ID. Below is the status and description of all the ISM: ISM Status Comments Valid Location Wrong Location Missing ISM file Unknown subnet ISM Success ISM Failure When the file is missing If <FC-ISM-REJECT-UNKNOWN> is False, and HNB IP does not match with the one's configured in the File, then the LV method returns Unknown and logs the correct subnet as warning message for the operator to configure the correct value in the file, if required. IP Based Location Verification The IP based Location Verification feature uses the IP address of the AP (the public IP address which it uses to communicate with RMS) to verify if the location of the AP is within the expected distance or not. The IP based location verification file is a text or CSV file comprised of one entry per line. Each entry is comma separated and consists of: <IP address>, <Expected Latitude of IP>, <Expected Longitude of IP> Where, <IP Address> is the public/nat IP of the AP which the AP uses to communicate with RMS. < Expected Latitude of IP> is the latitude of the IP. < Expected Longitude of IP> is the longitude of the IP. For example: , , , , When the AP communicates with RMS, RMS retrieves the source IP of the AP (this is the public IP/outer IP of the AP which the AP uses to communicate with RMS) from the existing tr069 session and then looks for the IP in the file provided. Depending on the deployment and installation scenarios, the public IP visible by RMS may or may not be assigned to the AP directly. In a residential deployment, this public IP/outer IP address is typically the one that is assigned to the fixed broadband modem/router to which the AP is attached. In this deployment, the AP is typically assigned with a private IP address and the broadband router/modem performs a network address translation (NAT) to communicate with the public network. When the IP is located in the file, distance is calculated using the haversine formula between the latitude and longitude defined for the IP in the file and the expected latitude and longitude defined for the AP in RMS. 19

20 Enabling Location Verification The calculated distance is compared with the tolerance provided in RMS. If the distance is within tolerance then the location of the AP is s "Valid Location" and the AP admin state is unlocked (considering only IP based location verification is enabled. If any other location verification is also enabled then the admin state is dependent on those other enabled location verifications). If the distance is out of the configured tolerance, the IP based location verification will either fail and lock the AP or will return unknown and keep the AP in previous state, depending on the configuration. By default the behavior is "unknown". The following should be configured for the IP based Location Verification feature in RMS: Enable IPL LV Provide the file name for IPL LV Configure the tolerance for IPL LV (if this tolerance is not provided then a default of 5000 m is used as tolerance) Configure the IPL LV failure behavior as either failure or unknown Use the Region group in the DCC UI to implement the above-mentioned configurations. Property Format Expected Value Comment FC-IPL-ENABLED Boolean true or false This property is enabled in the Region group in the DCC UI. Setting this value as "true" or checking the check box for this method enables the IPL location verification. FC-IPL-FILE String filename (example, ipl_file1.txt or ipl_file1.csv) This property refers to the filename that contains IP to latitude/longitude mapping. The file can be in.txt or.csv format. The file is added to the RDU from BAC UI. The filename can be configured through DCC UI. For more details on this, see Additional Location Verification Tasks. 20

21 Enabling Location Verification Property Format Expected Value Comment FC-IPL-NO-MATCH-STATUS String unknown or failure This property refers to the result when the IP of the AP is found in the file and the distance is out-of-tolerance. The values are either "unknown" or "failure". Default value is "unknown". The value of this property can be configured using the DCC UI. FC-IPL-TOLERANCE Integer Great Circle Distance (GCD) (in meters); for example, 5000 (here 5000 defines 5000m=5Km) This property refers to the tolerance or threshold value in distance to pass the location verification. The default value is 5000 m. The value of this property can be configured using the DCC UI. FC-IPL-TRIGGER-EVENT-CODE-LIST String TR069 informs. Example, "2 PERIODIC INFORM,6 CONNECTION REQUEST, 1BOOT, 4 VALUE CHANGE" This property defines the TR069 event code on which the IPL LV is checked. By default, the IPL LV is checked or triggered on 0 Bootstrap and 1 Boot. This property can be configured from the BAC UI. It is recommended that this value is not changed and the default value is maintained. 21

22 Enabling Location Verification Property FC-EXP-LAT Format Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI. Expected Value to if configured from the DCC UI; to if configured from the BAC UI. Comment Expected latitude of the HNB. FC-EXP-LONG Decimal format if configured from the DCC UI with six decimal places; integer format if configured from the BAC UI to if configured from the DCC UI; to if configured from the BAC UI Expected longitude of the HNB. The above properties are available at the Region level in the DCC UI. The file upload for IPL LV verification has to be done from the BAC UI and the file should be uploaded in Generic tab in the BAC UI, that is, Configuration > Files > Generic (File Type). Ensure that the filename is the same as that provided for the IPL LV configuration along with file extension. When the location verification method is verified, the following two properties are automatically configured at the device level displaying the IPL status. FC-IPL-STATUS This will be "Valid Location", "Wrong Location", "Ignoring Wrong Location", "Missing IPL file", "Reported IP missing from IPL file", or "Missing expected location" FC-IPL-STATUS-TS This is the timestamp when the above state of the IPL status is changed. The descriptions for the various statuses of the IPL LV are as follows: IPL Status Valid Location Description IPL location verification is successful. 22

23 Enabling Location Verification Wrong Location Ignoring Wrong Location Missing IPL file Reported IP missing from IPL file Missing expected location Distance is out-of-tolerance and FC-IPL-NO-MATCH-STATUS is configured as "failure". Distance is out-of-tolerance and FC-IPL-NO-MATCH-STATUS is configured as "unknown". IP address to Latitude/Longitude mapping file is missing from RDU database. IP of the AP is not present in IPL file. Expected latitude and longitude of the AP is missing. Chained Intra Grid (CIG) The Chained Intra Grid (CIG) LV method is used for enterprise deployment for a grid concept. For example, if there are three APs in the Grid with two APs located inside the premises and one AP is planned outside or edge of premises, since one of the APs (edge AP/Active entry AP) get GPS lock, the LV for other APs will be passed since they are part of the same grid even though the two inner APs did not get GPS satellite lock or macro neighbors during NWL. Below are the properties relevant for CIG LV: Property Format Expected Value Comments FC-CIG-ENABLED Boolean true or false This property enables the CIG LV methods during Provisioning Flow. FC-CIG-GROUP-TYPE Single Value String Group Type name (Site, Area, FemtoGateway) The value of this property states that on which group the details of anchor AP has to be populated after the Anchor AP is formed. For enterprise Deployment, the suggested value is Site group type. Only one group type name has to be given as input for this parameter. Only the group type name has to be entered, not the group name. 23

24 Enabling Location Verification FC-CIG-LV-METHOD-LIST String GPS This parameter states which all LV methods need to be considered for passing the CIG LV. Only GPS is supported, hence GPS is the only value supported for this parameter. FC-CIG-TOLERANCE Integer value in meters CIG Tolerance in meters The Anchor AP details (Latitude/Longitude) for a grid will be updated only if the (actual GPS distance reported by anchor AP) > (FC-CIG-TOLERANCE + FC-CIG-GPS-DISTANCE) FC-ANCHOR-AP-LV-LIST String GPS This parameter state which all LV methods need to be considered for creating an anchor AP. Only GPS is supported, hence GPS is the only value supported for this parameter. The above properties are available at the Region level in the DCC UI. The above mentioned properties are for the configuration of CIG. Below are the properties which are used by CIG for the CIG verification. The below mentioned properties gets automatically populated on the required Group type (as defined in the property (FC-CIG-GROUP-TYPE). The user do not need to configure any of the below properties as they are configured automatically once the GPS scan is completed for any one of the AP in the grid. Property Format Expected Value Comments FC-CIG-ANCHOR-AP-EID string EID of Anchor AP First AP in a grid passing GPS becomes anchor AP and its details will be populated at group level for other APs to do CIG LV FC-CIG-GPS-LAT Latitude Latitude of Anchor AP Latitude of Anchor AP FC-CIG-GPS-LONG Longitude Longitude of the AP Longitude of the AP 24

25 Enabling Location Verification FC-CIG-GPS-DISTANCE Integer Distance in meters GPS distance reported between expect and actual co-ordinates of the anchor AP The CIG status can be either Valid Location (if CIG is passed) or Unknown (if CIG is failed). Detected Neighbor Benchmark (DNB) Detected Neighbor Benchmark (DNB) location verification (LV) stores the benchmark when there is a first successful LV and after which it verifies the benchmark on the subsequent flow. If the benchmark fails, but other LV methods configured for DNB passes, then the DNB updates its benchmark. This method is enabled by default as part of RMS installation. Radio environment measurement (REM)-based location verification capabilities include: Storing a configurable number of neighbors in NWL benchmark. Storing RSSI information in NWL benchmark. Using RSSI for 3G neighbor power comparison for BAC location check. Using the property FC-DNB-FREQ-MATCH to decide comparison of neighbor identities using GUID regardless of frequency signature. Configuring periodic NWL scan duration. Refer to Enabling Location Verification, on page 8 Following are the properties defined for DNB LV: Property FC-DNB-ENABLED FC-DNB FC-DNB-FREQ-MATCH Format Boolean Comma separated value where each value is a combination of Neighbor ID Frequency Signature Power, for example, 3G Boolean Description Enables the verification of DNB LV methods during the provisioning flow List of benchmark entries for DNB. The list is automatically populated once any one of the LV methods (configured in FC-DNB-LV-METHOD-LIST) passes and none fails. Defines whether to match the frequency signature of the neighboring HNB, or to skip the verification of frequency signature. 25

26 Enabling Location Verification Property FC-DNB-LV-METHOD- LIST FC-DNB-POWER- TOLERANCE FC-DNM-BENCHMARK- UPDATE FC-DNB-FAIL-ACTION FC-DNB-CONFIG-NWL -LIST-COUNT FC-DNB-FREQ-MATCH Format String, can include any or all of GPS,CIG, EDN, DNL, ISM, DNM, IPL Integer - Power in dbm Boolean String: "Unknown" or "Error" Integer Boolean Description Defines which of the LV methods should be used for DNB list population or DNB verification in case DNB is not passed. If the configured LV method is enabled then that is used to populate/update the DNB. This is a comma separated value. Defines the threshold for matching the power of neighboring HNB's to the power of defined HNB in the DNB list. If power is within this tolerance, then the neighbor is valid for DNB. Specifies to update the benchmark if DNM LV is successful. The default value is "true". To revert to RMS 4.0 flow so that the benchmark is not updated on DNM LV success, configure the 'FC-DNM-BENCHMARK-UPDATE' as "false". Used to check if the DNB LV method fails. If the value is "unknown", set the LV method status as "Unknown"; otherwise set the LV method status as "Failure". The default value is "Unknown". To revert to RMS 4.0 flow, configure the 'FC-DNB-FAIL-ACTION' as "Error". Configures the number of neighbors in NWL benchmark. Default value is 12. Used to decide the power comparison using GUID or frequency. Valid values are "true" or "false"; default is "false". The above properties are available at the Region level in the DCC UI. After the LV method is verified, at device level the following two properties are automatically configured displaying the DNB status. FC-DNB-STATUS = This will be either "Valid Location", "Wrong Location", "Not executed, no verification methods configured", "Not Running, Not ready", or it will not be updated if the DNB LV is "Unknown". FC-DNB-STATUS-TS = This will be a timestamp when the above state of the DNB status is changed. See Additional Location Verification Tasks for more information. Below is the status and description of the DNB: 26

27 Enabling Location Verification DNB Status Valid Location Wrong Location Not executed, no verification methods configured Not Running, Not ready Description DNB Success or "FC-NO-NEIGHBORS-LV-BYPASS" is set as true and macrocells are not detected DNB Failure Indicates that the DNB LV is enabled but "FC-DNB-LV-METHOD-LIST" property is not configured with any LV methods Indicates that the DNB LV is enabled but none of the LV methods defined in "FC-DNB-LV-METHOD-LIST" is enabled Additionally, if the DNB list is not present in the device, then it will get populated if the DNB LV is passed. If the DNB list is present, and if in the next scan the AP does not detect any macrocells, then the DNB list (Benchmark list) is deleted from the device. Chained Intra Chassis Chained intra chassis (CIC) location verification allows you to skip location verification on a technology type (either 2G, 3G or 4G) within the same chassis, if another technology type in the chassis has already completed the location verification process. These properties are applicable to CIC LV: Property Format Expected Value Comments FC-CIC-ENABLED Boolean true or false This property enables the CIC LV methods during Provisioning Flow. The remaining properties are automatically updated at the device level if CIC is enabled and LV passes for any technology AP on the chassis. FC-CIC-ANCHOR-AP-EID String EID of Anchor AP When FC-CIC-ENABLED set as true and location verification is passed for the first AP from a chassis then mark EID of that AP (Either 3G or 4G) FC-CIC-STATUS String Status of the CIC LV Property gets updated to show the status of CIC LV 27

28 Log Uploads and Triggers FC-CIC-STATUS-TS String Time stamp of the CIC LV update Time stamp at which the CIC LV has got updated FC-CHASSIS-ID String Chassis ID of the AP This property gives the chassis ID on which both technology AP s are mapped FC-PEER-RAT-ID String Peer RAT ID of the AP This property gives the device EID of the other RAT in the FC-CHASSIS-ID The above properties are available at the Region level in the DCC UI. Log Uploads and Triggers Uploading a Log You can configure log uploads depending on event triggers. You can also request an on-demand log upload. Use this task to upload of a log file on-demand from a device. This is in addition to any logs that are uploaded according to configured triggers. Procedure Step 1 Step 2 Step 3 Step 4 Select a Device ID from the Select Device drop-down list in the screen. Click Perform and select On-Demand Log Upload from the drop-down list. After the device acknowledges the upload request, you are prompted to select the destination server to which to upload the log. Select a valid destination server from the Server drop-down list. Select the appropriate Log Type, if available, and click Submit. If the devices support more than one type of on-demand log uploads, for example, an Ubiquisys device supporting both Diagnostic and Performance logs, the screen is configurable to include multiple log types. Refer to Configuring DCC Dialog Boxes for more information. The result of the upload is displayed as a page message with the appropriate icon and the URL to the uploaded file is also displayed. To access the link from the machine, there should be a static route added for the network of the machines with a gateway pointing to the core router. If the request to upload the file fails, the data manager displays an error message. 28

29 Setting Triggers to Upload the Logs Setting Triggers to Upload the Logs Use this task to specify triggers to cause a log to be uploaded to the Log Upload Server (LUS). Procedure Step 1 Step 2 Step 3 Step 4 Select a Device ID from the Select Device ID drop-down list in the screen. Click Provision and select Log Upload Triggers from the drop-down list. After the device has acknowledged the request, the Update Log Upload Triggers screen is displayed with the various triggers that can be selected. By default, Triggers managed by RMS is selected. To upload the logs periodically, uncheck the Triggers managed by RMS option. A tooltip is displayed to describe each trigger. Click Update to update the triggers. After the update process is complete, a message is displayed. View Information about a Device The device manager provides a device dashboard where you can view varied detailed information about the device. Displaying the Device Dashboard The Device Dashboard displays device details in a combined view. The data displayed are fetched from the Regional Distribution Unit (RDU) when the operation is performed. The exact fields displayed depend on whether the device supports UMTS or LTE. The RDU data is divided into these parts: Registration Data Displays the device registered area and activation status. Assigned Data Displays the HNB GW info and MCC.MNC, LAC, RNC & SAC ID values. Activation Status Displays the device service and location valid status with Timestamp values, and tampered status of the device. Discovered Data Displays the manufacturer information. Live Data Displays details regarding the device admin, operational, RFTx status and firmware version. 29

30 Displaying the Neighbor List in Use Procedure Step 1 Step 2 Step 3 Select a device identifier type in the Device Search drop-down list. For Device ID and Secondary ID: a) Select the device identifier from the Select Device drop-down list, or type in your device identifier if your device does not appear in the list. b) Click View and select Dashboard from the drop-down list. The device data is displayed. For device types other than Device ID and Secondary ID: a) Type your device identifier into the Search field and click Search. b) Click the device identifier link in Identifier pane. The device data is displayed on the dashboard. Displaying the Neighbor List in Use Within the you can view the neighbors for a device. For LTE devices, these categories of neighbors are displayed: LTE Inter-RAT GSM Neighbors LTE Inter-RAT UMTS Neighbors LTE Cell Neighbors (Inter and Intra) For UMTS devices, these categories of neighbors are displayed: Inter-Frequency Neighbors Intra-Frequency Neighbors Inter-RAT Neighbors Procedure Step 1 Step 2 Step 3 Select Device ID in the Device Search drop-down list. Select the device identifier from the Select Device drop-down list, or type in your device identifier if your device does not appear in the list. Click View and select Neighbor List in Use from the drop-down list. The neighbor data for the device is displayed. 30

31 Device Operations Device Operations You can request to connect to a device. Alternatively, you can reboot, factory reset or shutdown a device. You can also configure any static neighbors for the device. Configuring Static Neighbors Use these tasks to add, update, or delete the static neighbors for a particular device post device registration from DCC UI. Adding or Updating Static Neighbors Use this task to add or update static neighbors for a device from the DCC UI. Procedure Step 1 Step 2 Step 3 Select a device from the Select Device drop-down list in the screen. Select Static Neighbors from the Provision drop-down list. Select one of the Static Neighbor tabs and click either Add or Update to add or update a static neighbor of that type. Based on the selection of Static Neighbor type, one of two possible dialog boxes are displayed to add or update static neighbors. The content of these dialog boxes are based on the dynamic screen configuration files: sdm-inter-rat-static-neighbors.xml sdm-inter-freq-static-neighbors.xml lte-inter-rat-gsm-static-neighbors.xml lte-inter-rat-umts-static-neighbors.xml lte-cell-static-neighbors.xml Refer to Configuring DCC Dialog Boxes for information on customizing these files. Before adding LTE Inter Static Neighbor, add the INTER FREQUENCY CARRIER. Set the parameters for the FC-LTE-IDLEMODE-INTERFREQ-CARRIER-1, FC-LTE-IDLEMODE-INTERFREQ-CARRIER-2, FC-LTE-IDLEMODE-INTERFREQ-CARRIER-3, and FC-LTE-IDLEMODE-INTERFREQ-CARRIER-4 that is present in the Area Group with the appropriate Inter-frequency carrier value. An example is provided in the Default Area. Step 4 Step 5 Step 6 Enter valid values in all the fields according to the tooltips provided. The Save and Submit buttons are enabled only after entering appropriate values in all fields. Click Save. The update operation is recorded locally, and the Submit Saved Changes button is enabled with a warning. Click Submit. 31

32 Configuring Static Neighbors The values are submitted for processing. If you add a static neighbor with the primary key value the same as an already existing static neighbor, then an error message is displayed. The primary key for Inter-RAT is the BCCH-ARFCN parameter. For Inter-Frequency, the primary key is a combination of the UARFCNDL and Primary Scrambling Code parameters. For LTE, the Primary keys are as follows for each LTE object: LTE Object Device.Services.FAPService.1.CellConfig.LTE.RAN.NeighborList.LTECell Device.Services.FAPService.1.CellConfig.LTE.RAN.NeighborList.InterRATCell.UMTS Device.Services.FAPService.1.CellConfig.LTE.RAN.NeighborList.InterRATCell.GSM Primary Keys PLMNID, CID PLMNID, CID PLMNID, LAC, CI To add Intra-Frequency neighbors, add the neighbor with the same UARFCN values (UL and DL) along with other valid values. Ensure that you note the UARFCN assigned before adding the neighbor as intra-frequency. Step 7 Click Cancel to cancel the request. Updating Static Neighbor Filtering Select Update Static Neighbor Filtering to edit additional settings related to static neighbors for the respective device from DCC UI. This feature is not available for LTE FAPs. Procedure Step 1 Step 2 Step 3 Step 4 Step 5 Select a device using the device identifier fields at the top of the screen. Select Static Neighbors from the Provision drop-down list. Click Update Static Neighbor Filtering. The Update Static Neighbor Filter dialog box opens. Check the desired option: FEMTO-NEIGHBORING-FILTERING-ENABLE enables automatic Femto neighbor filtering. STATIC-NEIGHBORING-FILTERING-ENABLE enables the classification of static neighbors. Do one of these: Click Submit to submit the request immediately. 32

33 Replacing a Device Click Cancel to cancel the request. Deleting Static Neighbors Use this task to delete static neighbors for a Device from the DCC UI. Procedure Step 1 Step 2 Step 3 Step 4 Select a Device using the device identifier fields at the top of the screen. Select Static Neighbors from the Provision drop-down list. A Static Neighbor provisioning tab is displayed for each available static neighbor type. Select the desired Static Neighbor tab and click Delete. Based on the selection of Static Neighbor type, a delete Static Neighbor confirmation box for a single instance is displayed. Click Save. The delete operation is recorded locally, and the Submit Saved Changes button is enabled with a warning. Click Submit to send a request to the BAC to delete the selected Static Neighbor. Click Cancel to close the dialog box without doing anything. Replacing a Device Use this task to replace a faulty 3G or LTE device from DCC UI. An operational device cannot be replaced. You can replace a device if the device is not functioning as expected and cannot be corrected by software/firmware upgrade, or if the device has malfunctioning hardware. Deactivate the faulty device from DCCUI before replacing with new device. Ensure that the new device is not available (registered) in RMS. Device replacement can replace devices of different flavors of AP. For example, USC 5310 for wifi+3g, USC 7330 for Enterprise, USC 3331 for Residential. If you are replacing a 3.7 software version FAP with a 3.5 software version FAP and if you encounter a config-sync failure then after replacing the device, perform a firmware upgrade on the replaced device to software version

34 Requesting a Connection to a Device Procedure Step 1 Step 2 Select a Device ID from the Select Device drop-down list in the screen. Select Device Replacement from the Provision drop-down list. A Device Replacement screen is displayed with two fields: Old Device ID - Populated with the existing EID with the text box disabled. New Device ID - To enter the new valid EID as validated in PMG to replace the existing ID. Figure 1: Device Replacement Screen for New Device ID The Replace button will be enabled only after a valid New Device ID is entered. Step 3 Step 4 To replace the device, enter the new device ID and select Replace. The successful device replacement message is displayed with an appropriate page error message depending on the PMG response. After successful device replacement, the successful device replacement message is displayed; in case of error, the appropriate error message is displayed. If the device replacement fails, the SDM list of EIDs is unaffected. You will be forwarded to the dashboard of old Device ID. The old device ID configuration will be unaffected. Requesting a Connection to a Device Use this task to send a connection request to a device. Procedure Step 1 Step 2 Step 3 Select a Device ID from the Select Device drop-down list. Click Perform, and select Connection Request from the drop-down list. A confirmation dialog box is displayed. Click Confirm to confirm the connection request. 34

35 Rebooting a Device If the connection request to the device is successful, the successful message is displayed. If the request fails, the data manager displays an error message. Rebooting a Device Use this task to reboot on a device. Procedure Step 1 Step 2 Step 3 Step 4 Select a Device ID from the Select Device ID drop-down list in the screen. Click Perform and select Reboot from the drop-down list. For LTE device, additionally the Reboot Option dialog box is displayed specifying the available reboot options for the LTE device. Specify the Reboot Option. If Reboot is selected, a Reboot TR-069 message is sent to the device. If Forced, Immediate or Delayed are selected, the parameter Device.Services.FAPService.1.FAPControl.LTE.X_CISCO_COM.RebootMethod is set accordingly and a Reboot TR-069 message is sent to the device. A confirmation dialog box is displayed. Click Confirm to continue to reboot the device. Click Cancel to cancel the reboot operation. The LTE Reboot options in the drop-down list are currently not supported on the Ubiquisys 6732 FAP. Resetting a Device Use this task to perform a factory recovery of a device or reset it. These recovery options are available for supported devices: No Recovery Immediate recovery Recovery in least busy hour Recovery on next power up Factory Reset The default option is Factory Reset. When chosen, a FactoryReset TR-069 message is set to the device. 35

36 View and Update Live Data Procedure Step 1 Step 2 Step 3 Step 4 Select a Device ID from the Select Device ID drop-down list in the Device Manger screen. Click Perform and select Factory Recovery/Reset from the drop-down list. A Select Recovery Option dialog box is displayed. Select the desired recovery option. A confirmation dialog box is displayed. Click Confirm. The success/failure message of the operation is displayed. View and Update Live Data The device manager provides you the ability to view and update live data from a device. Additionally, you can modify previously updated live data. Displaying Live Data The live data view of the device allows you to navigate through the data model (by object), querying the device for its values on demand. Procedure Step 1 Step 2 Step 3 Select a registered Device ID from the Select Device drop-down list in the screen. Click View and select Live Data from the drop-down list. After the device acknowledges the request, the object name of the specified device is displayed. You can navigate through the data model (by object). Check any of the check boxes and click Load/Refresh Selected Objects to refresh the view. A list of parameters set for the particular object and the device data is displayed, Updating Live Data for a Device Use this task to update the live data for a device. These parameters are values that are configured on the BAC and updated using the Data Manager user interface. Do not use this functionality for adding new instances in case of multi instance tables. 36

37 View and Update Live Data Procedure Step 1 Step 2 Select a Device ID from the Select Device drop-down list in the Data Manager screen. Click Perform and select Set Live Data from the drop-down list. After the device has acknowledged the request, the live device details are displayed. Figure 2: Set Live Data Display for 3G FAP Step 3 Step 4 Step 5 Step 6 Select the desired properties check boxes and click Load/Refresh Selected Objects. Any selected properties are refreshed and a list of parameters set for the particular object and the device data is displayed. Alternatively, you can expand the tree structure to view the device data. Make any desired changes. Only fields that are not grayed out can be edited. Click Submit to make the requested changes. The Submit button is enabled only after editing the parameters. After the updated values are validated in the data model, a confirmation dialog box is displayed. Click OK to confirm the changes. The parameters are updated with the new values and a successful message is displayed. The Parameters are set on the device on the next contact. Updating Modified Live Data The Set Modified Live Data feature allows you to write values and set the live data for a specified device. Specifically, this includes all the live parameters that have been modified previously. 37