Reset Data Networks/Client Networks DB 2.5.1.18 DSM Skip to end of metadata

Disclaimer:  Reset_db does not work, don't try

cd /elastifile/emanage/
./reset_db.sh


1. Reset the data NICs (so emanage can see the interfaces again)

   

  
[root@emanage ~(elfs_admin)]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: eno16777984: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP qlen 1000
    link/ether 00:50:56:82:2e:19 brd ff:ff:ff:ff:ff:ff
3: eno33557248: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP qlen 1000
    link/ether 00:50:56:82:7d:80 brd ff:ff:ff:ff:ff:ff
4: eno50336512: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:50:56:82:2c:ea brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.100/24 scope global eno50336512
       valid_lft forever preferred_lft forever
    inet 192.168.0.101/24 scope global secondary eno50336512
       valid_lft forever preferred_lft forever
11: v150.cbe60c68@eno16777984: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP
    link/ether 00:50:56:82:2e:19 brd ff:ff:ff:ff:ff:ff
    inet 10.15.0.101/16 scope global v150.cbe60c68
       valid_lft forever preferred_lft forever
12: v250.194cd7d7@eno33557248: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP
    link/ether 00:50:56:82:7d:80 brd ff:ff:ff:ff:ff:ff
    inet 10.25.128.99/16 scope global v250.194cd7d7
       valid_lft forever preferred_lft forever

[root@emanage ~(elfs_admin)]# epa-cli nic set 00:50:56:82:2e:19 1500
{
    "errstr": "",
    "status": 0
}
[root@emanage ~(elfs_admin)]# epa-cli nic set 00:50:56:82:7d:80 1500
{
    "errstr": "",
    "status": 0
}



2. Run installer again

Use /root/install_emanage.sh instead:

   

  
root@emanage emanage(elfs_admin)]# cd /root/
[root@emanage ~(elfs_admin)]# ./install_emanage.sh

******************************

Installation mode (vCenter/physical): physical

******************************

Select EMS Role (Primary/Secondary)
[1] Primary
[2] Secondary

1
You chose Primary, are you sure? [Y/n]

******************************

Select Management Network IP Type (DHCP/Static)
[1] DHCP
[2] Static

2
You chose Static, are you sure? [Y/n]

******************************

Enter EMS physical IP address: 192.168.0.100
You chose 192.168.0.100, are you sure? [Y/n]

******************************

Enter EMS physical network mask: 255.255.255.0
You chose 255.255.255.0, are you sure? [Y/n]

******************************

Enter Static IP Management Network Gateway: 192.168.0.1
You chose 192.168.0.1, are you sure? [Y/n]

******************************

Select do you want to add name server
[1] No
[2] Yes

1
You chose No, are you sure? [Y/n]

******************************

Enter the EMS Virtual IP address: 192.168.0.101
You chose 192.168.0.101, are you sure? [Y/n]

******************************

Setting up external network
The EMS virtual IP is 192.168.0.101
The EMS IP is 192.168.0.100

******************************

Enter Enter the Common Names separated by commas (default empty): [None]
You chose None, are you sure? [Y/n]
Enter the Common Names separated by commas (default empty): None
you can reuse the parameters by running the install script with @emanage_install_args_20180327-133625

******************************

EMS deployed successfully



3. Go back to EMS server, refresh, and start configuration wizard over again


4. Reset the vhead(s) data network interfaces, then log in to emanage again

epa-cli nic set <mac_address> 1500

epa-cli sys register-physical-host --emanage-ip 192.168.0.100 --user admin --password changeme


Troubleshooting

“too many interfaces configured” after epa-cli register --- remove the NIC

D
Dadee is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.