How to Factory Default Telepresence ISDN 3241 from Console?

[gthaliwal]

Hi there,

We have a 3241 ISDN which has all forms of remote access and file transfer (appart from https) disabled.

We then set https client verification to required.  We can now no longer access the unit on https or http.  There is obviously something wrong with the certificate or the verification process.

We are left with a 3241 which I have tried to reset via the console using procedure outlined here

http://www.cisco.com/en/US/docs/telepresence/infrastructure/articles/cisco_telepresence_resetting_password_restoring_factory_settings_kb_13.shtml

However after running the

reset_config

Command the unit is still not accessable leading us to believe that this is not a FULL factory default (i.e. wipes all settings/certificates files etc)

Please can someone advise how to perform this operation?  I'm trying to aviod raising a TAC request on this

Thank you

Gurp

[Paulo Souza]

After trying factory reset, are you able to ping MCU? How do you know that the reset process went sucessfully?

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[gthaliwal]

Hi Paulo,

The reset works as we get a warning and after the box reeboots it is on DHCP (factory default network settings).  We then configure the IP address in the usual way (static A x.x.x.x y.y.y.y z.z.z.z) and after a second reeboot I am able to ping it ... but still no http or https access.  This leads me to believe it is still using old settings as described above?

[Paulo Souza]

Hi,

I really believe that the factory reset should remove the client certification configuration. But you can validate it by yourself: Open the XML backup file that you have taken from MCU, check the content of the file and see if you can find the parameters related to the configurations that you have changed. If the configuration that you changed is not listed into this backup file, so you can come to conclusion that this configuration may be totally independent from the reset process, but I am not sure.

Can you you try to telnet MCU on ports 80 and 443? Can you try to use another browser or PC?

Well, anyhow, I would suggest you to go ahead and open a TAC case.

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[gthaliwal]

Hi Paulo

Thanks for your feedback. It's an isdn gateway, but yes, I suppose the access options are exactly the same as an MCU. Unfortunately no, ssh and telnet are not responding and as part of the initial configuration they were infact disabled. I'm beginning to think that the reset hasn't worked too so I will get my guy to try again. Slight problem in that the gateway is in an entirely different country to me! I will also request a permanent serial connection. I'm also going to go ahead and speak to TAC.

Will post back any findings. Thanks again.

Sent from Cisco Technical Support iPad App

[gthaliwal]

The fix was to start the http service via the console, cant remember the exact syntax but it was something along the lines of 'service start http'. Once http was enabled I was able to browse into the unit and disable https cert authentication.

Sent from Cisco Technical Support iPhone App