how do I fully delete an endpoint?

[Guest_imported]

Hi,

Simple question, (I hope) How dod I delete an endpoiint? I've yanked the endpoint from the gateways in the "Endpoint Manger" in the TME desktop, and issued a "wep sync_gateways" on the TMR, but I'm still getting "host not responding" messages on the TEC.

The man page for wep says the following:

wep del ep_oid gw_label
Deletes the endpoint from an epmgr.bdb file.
Because there are separate .bdb files for each
gateway, it is necessary to specify the
endpoint's assigned gateway. The gw_label can be
found by issuing the wep ls command. The wep del
command does not completely delete all refer-
ences to the endpoint.

So how do I delete it completely?

TME 10
Framework 3.7
Solaris environment

Any help greatly appreciated

later
jb

(praxis22@hotmail.com)

 

[txtxcowboy]

In our enviroment we have a file created on each TMR that has a full list of all Endpoints on the TMR which our allow install policy uses to determine which EP are already in the object repository so DUPES are not created.

After issueing the wdelep >label< we then run a wlookup -ar Endpoint >filename (filename being the file that lists all Endpoints on that TMR) This will allow it to come in again because the update of the file takes out that EP and the allow install policy will see it is not there... I assume you are running into a problem with the allow install policy which is preventing your EP from coming back in because it has reminance of the EP somewhere (probably on the TMR it logged into before)

After we do the wdelep and the redirection of wlookup to the file. We are able to reisntall the EP software and the EP will come in instantly (even withotu a reboot!!)

Hope this helps..

Dave

 

[Guest_imported]

jb, it's simple
wdelep -d eplabel
This deletes it entirely from DB and removes the code from the EP (that's the -d flag)
Good luck!

 

[Guest_imported]

Hi,

Well, it's like this....

I want to delete the endpoint, I don't want it back, the machines are toast, and I've trashed the endpoints via the gui, edited the files that issue the ping, and then redistributed the profiles, (which contain the ping script) to the outlying machines, gateways, etc.

In the mean time, the Enterprise server on the TEC has been restarted 3 times and the whole Tivoli installation, (bar the gateways) has been restarted. by taking down the TEC, then the TMR and then restarting them both, TMR first to allow the DB to stabilise, then the TEC.

After all this I'm still getting &quot;host down&quot; (ping) messages and &quot;tivoli heartbeat failed&quot; messages for the machines in question, (of which there are three) still no joy...

Ideas?

later
jb
(praxis22@hotmail.com)

 

[Guest_imported]

Hi,

The answer would appear to be thus:

if a machine is down for a bit and you don't want messages then wpostemsg -r HARMLESS -m &quot;start of Maintenance Mode&quot; sub_origin=<name of the endpoint> hostname=<name of the endpoint> Tivoli_Heartbeat TIV_DISABLE

and this will stop messages until a new heartbeat message is received from the machine.

If you have deleted the endpoint then
wpostemsg -r HARMLESS -m &quot;start of Maintenance Mode&quot; sub_origin=<name of the endpoint> hostname=<name of the endpoint> Tivoli_Heartbeat TIV_DELETE

later
jb