UNSOLVED

kevinnguyen

updated

9 years ago

0

3119

May 5th, 2017 12:00

issue on remove RP-Splitter

I am testing Recover Point for VM and getting issue to remove it.

. Query if having RP splitter installed

esxcli software vib list | grep RP

RP-Splitter                    RPESX-00.5.1.0.0.0.c.65.000           EMC_Recoverpoint  VMwareCertified   2017-05-05

. Try to remove and got error

esxcli software vib remove -n RP-Splitter --maintenance mode

[NoMatchError]

No VIB matching VIB search specification 'RP-Splitter'.

Please refer to the log file for more details.

Does anyone have same issue and resolution?

Thanks.

Kevin

  • forshr

    2 Intern

    1126 Posts

    2362

    0

    Posted May 5th, 2017 12:00

    Hi Kevin,

    Put quotes around the vib name, "RP-Splitter".

    Regards,

    Rich

  • Idan

    4 Apprentice

    675 Posts

    2362

    0

    Posted May 5th, 2017 13:00

    Hi Kevin,

    The removal should be done without --maintenance-mode while the ESX is in maintenance mode.

    Can you try and let me know via email how it went ?

    Thanks,

    Idan Kentor

    idan.kentor@emc.com

  • forshr

    2 Intern

    1126 Posts

    2362

    0

    Posted May 5th, 2017 13:00

    Hi Kevin,

    Two points of note.

    Firstly, this isn't a supported method of removing the splitter. Secondly, this is the 5.1 splitter?

    Regards,

    Rich

  • 2362

    0

    Posted May 5th, 2017 13:00

    esxcli software vib remove -n "RP-Splitter" --maintenance-mode

    [NoMatchError]

    No VIB matching VIB search specification 'RP-Splitter'.

    Please refer to the log file for more details.

    Also tried

    esxcli software vib remove --vibname=EMC_Recoverpoint:RP-Splitter:RPESX-00.5.1.0.0.0.c.65.000

    Still no go.

    Thanks.

    Kevin

  • 2365

    0

    Posted May 5th, 2017 16:00

    yes, this is 5.1 and above command is valid from 5.0 Recover Point for VM.

  • Idan

    4 Apprentice

    675 Posts

    2365

    0

    Posted May 5th, 2017 23:00

    5.1 is not out yet, let's continue this via email.

    Thanks,

    Idan