| Add_workflow_for_techpubs |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7edf811e000e, userName='null'} |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a0c85f4199b1015f7ea6e836000d, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a0c86d32712b016d406f77af0008, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc4207c6, userName='null'} |
|---|
|
| Available_since |
|---|
| Type | Modified For |
|---|
| Release | 16.0.1 |
|---|
|
This section describes how to use the
to replace older model
devices to newer model devices using the
Swap (ESWAP) feature.
Overview
ESWAP, the
replacement solution, is a method of migration from legacy
devices and
14 to newer model
devices and the new
.
| Info |
|---|
|
Before proceeding, install and make sure that the legacy and public Zero Touch Provisioning (ZTP) server are reachable. Refer to Installing and Upgrading EdgeView SCC for more details on how to install . |
During the
installation, the administrator registers the
using a registration key received from
and sets up the
evadmin and
tenantadmin user profiles. Use the
evadmin credentials and set a valid email address in
General Settings >
Notification Sender Email to allow
to send emails for password resets or first-time password creation when adding new users.
ZTP allows you to redirect factory defaulted or out-of-the-box, newer model
devices to the
using auto-provisioning and ESWAP. When an order is placed for a new
device,
's order management system assigns this
device's LAN MAC address to an
identifier. This identifier references the device's registration when
is first installed. The identifier and the device's LAN MAC address are used by the ZTP server to provide redirection to this
when it is placed in the network for service deployment. The
contacts the ZTP server and provides it its LAN MAC address and the ZTP server provides the
the URL to contact the
which then claims this device using auto-provisioning or ESWAP.
for
14 Integration
This section describes how to configure
and
14, so as to allow the ESWAP feature to extract the legacy device's active running configuration and apply it to the newer model
replacement device.
The ESWAP feature requests the configuration of a legacy
device to the
14 managing it, when the device is online and in service.
14 contacts the legacy device using its management protocol methods and performs a full system backup.
| Anchor |
|---|
| Create a collection |
|---|
| Create a collection |
|---|
|
Create a Collection for
14 Integration
To integrate
with
14, create a collection. The integration process synchronizes all
14 groups and
devices to this collection. You can create this collection with the
tenantadmin or a named user with
tenantadmin rights. In all examples of this section, the
tenantadmin user is used.
To create a collection:
Choose Devices > Collections. The Collections page appears.
Choose ADD COLLECTION. The Add Collection page appears.
Enter the following details:
Name – Enter a name for your collection.
Description – Enter a description for the collection.
- External API Key – To integrate a top-level collection with Phonism, specify the Phonism API key. For more details on integrating Phonism with the , refer to Integrate Phonism with EdgeView.
Firmware Repository – Choose the Firmware Repository to associate with the collection.
- Select ADD COLLECTION once you are done. The collection is added successfully. For more details on how to create a collection, refer to Create Collections in EdgeView.
The created collection now appears under Devices > Collection. Select the created collection and click the Edit icon in the Policy pane.
Click Add.
| Info |
|---|
|
It is not necessary to make any changes to the policy before clicking Add. |
Go to Devices > Collection and select the Unassigned Collection.
Add a policy to the unassigned collection by selecting the Unassigned Collection and clicking the Edit icon in the Policy pane.
Click Add.
| Info |
|---|
|
It is not necessary to make any changes to the policy before clicking Add. |
| Anchor |
|---|
| Create an external admin |
|---|
| Create an external admin |
|---|
|
Create an External Admin Collection User for EdgeView 14 Integration
requires a specific user type for
14 integration. This section explains how to create this user and to assign this user to the newly created collection.
The integration process synchronizes all 14 groups and devices to the collection using this username and password for authentication to .
To create a user:
- Choose Users > List. The users List page appears.
Choose ADD USER. The Add User page appears.
- Enter the following details:
- Full Name
- User Name
- Email
Phone Number (Optional)
| Info |
|---|
|
Make sure that the email address you provide is one that you have access to, as you will receive the reset password function for the externaladmin user on this email address. |
- Choose the collection that you created to get access to the collection.
- Choose the Role type as externaladmin. This role is specific to 14 integration and cannot be used for login and management.
Configure the Collection Access by selecting the collection created for 14 integration.
The following notification appears. Click OK.
- Select ADD USER to save changes and to add the new user.
If required, reset your password by selecting Reset Password.
| Info |
|---|
|
New user creation automatically sends a reset password email to the user's configured email address. The reset password function is required if the password is forgotten or a new operations person is managing the system. |
For more details on how to create a user, refer to User Management in EdgeView.
Prerequisites
- TCP port 443 – For HTTPS REST request for synchronization - allow inbound to the IP.
- TCP port 5671 – For status reporting after synchronization - allow inbound to the IP.
- TCP port 9142 – For legacy support data syncing Outbound (Cassandra connection for legacy support).
This section describes how to configure 14, so as to connect to to allow the ESWAP feature to extract the legacy device's active running configuration and apply it to the newer model replacement device.
To configure the
14:
- Go to the 14 server and log in as a user with administrator role.
Choose EV SYSTEM > System Settings > 15. The
15 tab appears.
- Enter the following details:
Enable EV15 Synchronization: Select the check-box.
EV15 Address: Enter the EdgeView 15 IP address.
EV15 Username: Enter the user-name of the user created in Create an External Admin Collection User for EdgeView 14 Integration.
EV15 User Password: Enter the user's password.
EdgeView14 External Address: Configure the IP or FQDN of this 14 system. By default populates the IP address of logged-in EdgeView 14.x.x.
| Info |
|---|
|
The field description asks you to include 'http://' or 'https://' in the address. Do not include these in the address string. |
Click Save and then select Test EV15 Connection to test the connection.
If the connection is successful, select Sync with EV15.
You are prompted to confirm the sync. Click OK.
If the sync is successful, the following screen appears.
- On the , select the collection created. All the collections and devices in the 14.x.x are populated here.
For more details on the 15 synchronization, refer to Manage EdgeMarc Legacy Devices.
Verify 14 – Integration
The time required to complete the synchronization depends on the number of
14 groups and
nodes. As an example, if the
14 has two groups with one
in each group, the synchronization is completed within a few seconds.
The synchronization time depends on:
- Compute resources on both 14 and .
- The speed of your network connection.
- The number of groups and devices being synchronized.
| Info |
|---|
|
Any IDS/IPS system inspecting the TCP 443 connection can introduce delays. |
To verify the synchronization:
- Log in to .
Go to Devices > Collections.
- Select the collection created in Create a Collection for EdgeView 14 Integration that now appears with a blue highlight and the label Legacy.
The external admin user created in Create an External Admin Collection User for EdgeView 14 Integration and assigned to this collection, gives 14 the permission to connect to the
and copy all groups and devices on 14 to this specific collection.
The Relationship pane contains the synchronized grouping structure and sub-groups from 14.
| Info |
|---|
|
The initial synchronization may take a while to complete. |
Synchronization from 14 to is an ongoing process. When a group or is created on 14, they are synchronized with in real-time. Test this by adding a new 14 group and verifying that this group is available on .
Verify the availability and connectivity of legacy devices by selecting the required group.
Select the Devices tab. The following screen appears with all the devices in the 14 group. The replacement feature is now functional.
Replacement Feature
Replace the Legacy Device
ESWAP provides a way to easily convert a legacy model
SBC to a newer model
SBC.
The legacy management and SBC solution used a multi-protocol management method to provide operators with the toolsets required to provide end-users a quick analysis of the problem they are experiencing or help with additional service configuration requirements. As networks began to grow, security surrounding VoIP solutions became a topic of concern. The new
devices and the
provides better security to protect device data, new connection methods to ensure strong encryption, all the while maintaining ease of deployment.
The
along with newer
firmware provides this added security element with methods for transitioning older legacy devices that are in service, quickly and securely. The ZTP process provides redirection of newer
devices to the
server. The
to/from ZTP uses TCP port 443 with HTTP REST based API’s. The
that contacts ZTP also uses TCP port 443 and when redirected to the
server, creates a new TCP 443 connection for provisioning.
uses the ESWAP feature to identify legacy devices to be replaced with newer model
devices that use a single port TCP 443 encrypted connection for provisioning and
management. The legacy devices multi-protocol management method required certain service ports to be opened inbound to the legacy
, but the new
devices connect outbound to the
for management.
This section explains how to replace a legacy device managed by
14 with a newer device completely managed by
. The new device once replaced, runs the legacy device's latest configuration to reduce service outage at the end-user's location.
To replace legacy device:
- Go to the 14 server and log in as a user with administrator role.
Go to Devices > Collections and select the collection used for 14 synchronization.
Select the legacy group populated by the 14 synchronization.
Select Devices tab and choose the legacy device to replace.
On the device overview page, go to Actions > Replace Device. A Replace Device dialog box appears.
| Info |
|---|
|
If you select Manage Device from the Actions drop-down menu, a new browser instance of the 14 appears as the selected device is not yet fully managed by . The browser that opens is not a direct connection to the , but a proxy connection to the 14. |
In the Replace Device dialog box, enter the MAC address of the new replacement device and click REPLACE.
| Info |
|---|
|
One method to obtain the replacement device's MAC address is by logging into it and copying it from the Admin page. |
You are prompted to confirm the action. Click Confirm.
You are redirected to the Action Log page. You are most likely to see a pending status. During this process, the
is waiting for the 14 to create a backup of the legacy device. This may take up to 10 minutes.| Info |
|---|
|
Hovering over the status indicator shows a message when the device is ready for replacement. |
Go to Provisioning > Status. The current state of the
during replacement is displayed. Awaiting Contact signifies that the is waiting for the replacement device to connect and request provisioning.
Power on the replacement device for provisioning. It may take a few minutes for the replacement device to boot up and connect to the
. The status changes when the replacement device is configured. Select the Finished check-box to verify the status.
The Action Log also displays a Completed status.
The new device is now ready for
management.
For more details on how to replace devices, refer to Replace EdgeMarc Legacy Devices.
| Info |
|---|
|
By default, the new device lands in the same collection as that of the device it replaces. You can move it to any other collection. For more information on how to move an device to a different collection, refer to Perform Actions on SBC Edge. |
Verify Replacement
To verify that the replacement is successful:
- Go to Devices > Collections.
Select the Unassigned collection. The new
device is now visible in the collection and ready for management. | Info |
|---|
|
In this example, the full legacy configuration is applied to the replacement device – this includes the hostname and all IP configurations. |
Select the new device for a list of full management parameters.
| Info |
|---|
|
The legacy hostname configuration is applied to the replacement device due to the policy but the replacement MAC, model, and firmware correctly reflect the replacement device. |