cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2185
Views
0
Helpful
3
Replies
Highlighted
Beginner

Default login name and password for CPS-MSP ?

My boss handed me a CPS MSP 1 RU appliance yesterday to setup along with two cameras.  It is running RHEL 5.  I have downloaded every available piece of documentation and the login name/password mentioned doesnt let me login to RHEL 5.  This is a brand new box and as I understand it, I may still need to install a Video Surveillance Manager.  Since this may have been pre-installed based on what I see on the quote but I cant verify that since when I tried to get into the WEB GUI, I get a page cannot be displayed error.

Does anyone know what the default credentials are for this system ?  The root password specified in all the doc's wont let me in.  I have tried the various Cisco default accounts I have come across over the years to no avail.

Trying not to call TAC but running out of options.

Thanks,

Ron                         

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Beginner

Hi Ronald,

You might want to do some quick research on your end to see how the part was sourced, ask your accounting folks to dig up a Sales Order or Purchase Order based on the Serial Number of the server.  Some 2-tier distributors and a handful of other vendors ship appliances in such a way that they may not have been factory configured.  Assuming this came from the factory configured as a VSOM 7.0.x appliance, the server should present a logon GUI when you access the server as either

https://serverIPorHostname  (https://171.69.15.4 for example)

if you do not get a GUI page, you can try

https://serverIPorHostname/vsmc/  (https://172.16.7.57/vsmc/ for example, and note the ending slash.)

If you are not getting a GUI at all, reboot the server and retry.  If you have a GUI login screen, try the following logins

USER          PASS

localadmin  secur4u

admin          admin

operator     operator

root               secur4u

New servers ordered directly from Cisco through the ordering tools or through Cisco account teams come preconfigured from the factory, though a CPS-MSP-1RU appliance could have been configured with CPAM, VSM or IPICS installed.  The Sales Order would show you.  If this is not a new server but one being 'repurposed' from another installation (by the partner, installer or end customer,) you can try loging into the console to the linux prompt (or use ssh) and use root and secur4u, or localadmin and secur4u or admin and admin.  If in either case your authentication succeeds but the prompt returned is the non-privileged prompt ($ instead of the #), you can execute the command

sudo su -  (return)  and when prompted for the password, use whatever password got you into the system to the # prompt.

I hope that helps,

Jim

View solution in original post

3 REPLIES 3
Highlighted
Beginner

Hi Ronald,

You might want to do some quick research on your end to see how the part was sourced, ask your accounting folks to dig up a Sales Order or Purchase Order based on the Serial Number of the server.  Some 2-tier distributors and a handful of other vendors ship appliances in such a way that they may not have been factory configured.  Assuming this came from the factory configured as a VSOM 7.0.x appliance, the server should present a logon GUI when you access the server as either

https://serverIPorHostname  (https://171.69.15.4 for example)

if you do not get a GUI page, you can try

https://serverIPorHostname/vsmc/  (https://172.16.7.57/vsmc/ for example, and note the ending slash.)

If you are not getting a GUI at all, reboot the server and retry.  If you have a GUI login screen, try the following logins

USER          PASS

localadmin  secur4u

admin          admin

operator     operator

root               secur4u

New servers ordered directly from Cisco through the ordering tools or through Cisco account teams come preconfigured from the factory, though a CPS-MSP-1RU appliance could have been configured with CPAM, VSM or IPICS installed.  The Sales Order would show you.  If this is not a new server but one being 'repurposed' from another installation (by the partner, installer or end customer,) you can try loging into the console to the linux prompt (or use ssh) and use root and secur4u, or localadmin and secur4u or admin and admin.  If in either case your authentication succeeds but the prompt returned is the non-privileged prompt ($ instead of the #), you can execute the command

sudo su -  (return)  and when prompted for the password, use whatever password got you into the system to the # prompt.

I hope that helps,

Jim

View solution in original post

Highlighted

This is a brand new box that came from Cisco.  I attached a monitor/keyboard/mouse and saw the box appear to startup normally.  I did see a service named "cisco" start up during the boot up process.

I see a RHEL5 screen appear on the server.  I get a gui to come up when I try to login to the server over the network but it isnt a Cisco branded screen.  The server is in the lab but I remember the name on the gui screen when access from the workstation is the same as the vendor name I saw when BIOS came up when the server firsts boots up.

Will take a look at this and get back with you.

Thanks,

Ron

Highlighted

Lessons learned on this for others who are implementing this -

1) Eth0 which I was connected to is hard coded for an ip address that wasnt in use on the vlan the server was connected to

2) The account I had to use to access the server wasnt the one listed in what little documentation I could find on this appliance

3) had to do a sudo su - in order to be able to run ifconfig which is what told me that the interface I was using on the server was part of the problem I was experiencing

4) for those not fluent in linux (I am a bit but not a hardcore gearhead (a term used with all respect for those fluent in Linux), doing a service network restart allowed me to use eth1 without rebooting the box.

Now if I can just find how to rerun the initial setup script that ran in case I want to document the setup process for other boxes of this flavor that we may be implementing for others.

Thanks,

Ron

This widget could not be displayed.