To configure a cellular domain with single SIM deployment
Steps
1 |
Choose Manage→Cellular Domains from the NFM-P main menu. The Cellular Domain Manager form opens. |
2 |
Click Create. The Cellular Domain [Create | Edit] form opens. |
3 |
Configure the Name parameter. |
4 |
Configure the Sim Layout parameter to Single SIM. For dual SIM, see To configure a cellular domain with dual SIM deployment. |
5 |
Configure the Operation Mode parameter. See Cellular domain operation modes for information about operation modes. |
6 |
Configure the ADP Process parameter to specify one-step or two-step discovery. |
7 |
Configure the ADP System IP Address parameter. |
8 |
If the cellular domain includes any older NEs that are factory-shipped with a default administrator password, configure the Default ADP-Hm admin Password parameter using the administrator password that is common to the NEs. |
9 |
Specify one or more head-end nodes for the cellular domain, as required.
|
10 |
Click Select in the Mediation Security panel and choose the required SNMPv3 mediation security policy. |
11 |
Click Select in the PDN Profile panel and choose the required PDN Profile policy. |
12 |
Click Select in the Software panel and choose the required software and firmware upgrade policy. During software upgrade, if the 7705 SAR-Hm has a later image than that mentioned in the domain, the node software is not changed with the version mentioned in the domain since it is already running a latest image. Unlike software upgrade, there is no version check of the current 7705 SAR-Hm firmware. The firmware image mentioned in the domain is pushed down to the node even if it is an older image. Leave the firmware image empty if you want to skip the firmware upgrade. |
13 |
If required, configure the Firmware Version parameter. For the 7705 SAR-Hm, use a format that is aligned with the Sierra Wireless web portal, [VENDOR NAME]<space>[FIRMWARE_SUFFIX]<space>[PRI]. For example: GENERIC 02.24.03.00 002.026_000 For the 7705 SAR-Hmc, use a format such as this example: CAT4_GS_BYPASS_0.3.3.9_V1.9 |
14 |
Configure the Software Version parameter using the string that identifies the software release to which the devices are to be upgraded; for example, TiMOS-B-RR.r Rn. |
15 |
If NGE is to be used, click Select in the NGE Domain panel and choose the required NGE domain. |
16 |
Configure the parameters in the PIN Security panel. |
17 |
Configure the parameters in the BGP Configuration panel. |
18 |
If required, use the Select button in the Post Discovery Action panel to choose a post-discovery action for NEs in the cellular domain. Note: The post-discovery action is performed on the NEs only when the ADP process for each NE in the cellular domain is complete. |
19 |
If the Operation Mode parameter is set to Static Cellular Interface or Dynamic Cellular Interface, perform the following steps. |
20 |
Click Apply. |
21 |
Click OK. The Cellular Domain [Edit] form refreshes and displays additional tabs. |
22 |
If the Operation Mode is set to Static Cellular System, add new devices to the cellular domain, as required.
|
23 |
Add subnets to the domain, as required. |
24 |
If any NEs in the cellular domain have unique administrator passwords, click on the Serial Number Data tab. Otherwise, go to Step 26. |
25 |
Perform one of the following.
|
26 |
If any head-end node in the domain is a 7705 SAR, configure BGP peers on the head-end node BGP group; see To configure peer-level BGP. |
27 |
If the Operation Mode is set to Static Cellular Interface or Dynamic Cellular Interface, or the Operation Mode is set to Static Cellular System and the ADP System IP Address parameter is set to Use XML, import a list of devices.
|
28 |
If the Operation Mode is set to Static Cellular Interface or Dynamic Cellular Interface, and the ADP System IP Address parameter is set to Verify and Allocate from Pool, define one or more System IP address pools to provide a sufficient number of IP addresses for all devices that are to be discovered in the cellular domain subnets. Note: The NFM-P does not reuse any IP address in a pool. Ensure that the System Prefix value that you specify allocates a sufficient range of addresses for the subnet. |
29 |
Click OK to save your changes and close the open forms, as required. End of steps |