Cannot run program "C:\\Program": CreateProcess error=2, The system cannot find the file specified

We often find this issue when we login to the UCSM and Click on KVM manager, we see the following error –

Cannot run program "C:\\Program": CreateProcess error=2, The system cannot find the file specified

Even if you try to setup the path file for Java in options given on the top of UCSM but nothing works.

This error happens when you upgrade the latest version of Java from what you had installed earlier – jre-6u45-windows-i586. So the best option is to uninstall the Java from your PC completely and install it the older version given above again. This time when installing it, just change the destination folder while installing Java and that’s it.

For e.g  - Install Java in C:\Java\

Once you do the above step and retry opening KVM via UCSM tool you will see that starts working. 

Cisco Prime infrastructure upgrade procedure from 2.0 to 2.1

Step 1. Check the Version of code already running and please read the release notes carefully.

CPI20/admin# show ver Cisco Application Deployment Engine OS Release: 2.0 ADE-OS Build Version: 2.0.6.003-px-build ADE-OS System Architecture: x86_64 Copyright (c) 2005-2010 by Cisco Systems, Inc. All rights reserved. Hostname: CPI20 Version information of installed applications --------------------------------------------- Cisco Prime Infrastructure ------------------------------------------ Version : 2.0.0.0.294  --------------------------<<< Current version

Step 3. Transfer Patch file into the CPI defaultRepo.

CPI20/admin#  copy tftp://10.x.x.x/PI-Upgrade-2.1.0.0.87.tar.gz disk:/defaultRepo

Step 4. Check the defaultRepo.

CPI20/admin# show repository defaultRepo CPI20-140806-0330.tar.gpg CPI20-140813-0330.tar.gpg PI-Upgrade-2.1.0.0.87.tar.gz  -------------------<<< This file should be present in the defaulRepo before starting the Upgrade

Step 5. Stoping NCS Services before upgrade. 

CPI20/admin# ncs stop Stopping Network Control System... This may take a few minutes... Network Control System successfully shutdown. Plug and Play Gateway is being shut down..... Please wait!!! Stop of Plug and Play Gateway Completed!! SAM daemon process id does not exist DA daemon process id does not exist DA syslog daemon process id does not exist

Step 7. Initiate the upgrade.

  

CPI20/admin# application upgrade PI-Upgrade-2.1.0.0.87.tar.gz defaultRepo Save the current ADE-OS running configuration? (yes/no) [yes] ? Generating configuration... Saved the ADE-OS running configuration to startup successfully Please ensure you have a backup of the system before proceeding. Proceed with the application upgrade ? (yes/no) [yes] ? DO NOT press ^C while the upgrade is in progress Aborting upgrade with a ^C may leave the system in a unrecoverable state Initiating Application Upgrade...   Stage 1 of 7: Transferring file ...   -- complete.   Stage 2 of 7: Unpacking file ...   -- complete. *** System will reboot after a successful installation of this package *** After reboot, please login again into the server to check status   Stage 3 of 7: Executing pre-install ... [WARNING] System will reboot after a successful installation of this package (after Stage 7). After reboot, please login again into the server to check status. No action required at this time. Continuing with Stage 3. % Repository not found  -- complete.   Stage 4 of 7: Upgrading binaries ...   -- complete.   Prime Infrastructure Application installation completed             Stage 5 of 7: Retrieving system version ...   -- complete.   Stage 6 of 7: Updating Database Schema ...               : This could take long time based on the existing data size.                   Stage 1 of 5: Pre Migration Schema Upgrade ...                                         -- completed at: 2014-08-15 00:21:25.162, Time Taken : 0 hr, 0 min, 17 sec                   Stage 2 of 5: Schema Upgrade ...                                 : This could take long time based on the existing data size.                                         -- completed at: 2014-08-15 00:24:56.716, Time Taken : 0 hr, 3 min, 31 sec                   Stage 3 of 5: Post Migration Schema Upgrade ...                                         -- completed at: 2014-08-15 00:26:34.534, Time Taken : 0 hr, 1 min, 37 sec                   Stage 4 of 5: Enabling DB Constraints ...                                         -- completed at: 2014-08-15 00:34:31.834, Time Taken : 0 hr, 7 min, 56 sec                   Stage 5 of 5: Finishing Up ...                                         -- completed at: 2014-08-15 00:34:44.867, Time Taken : 0 hr, 0 min, 13 sec   -- complete.   Stage 7 of 7: Re-enabling Database Settings ...   -- complete. Upgrade Finished. Server is  restarting . Please wait .. % This application Install or Upgrade requires reboot, rebooting now... Broadcast message from root (pts/0) (Fri Aug 15 00:38:13 2014): The system is going down for reboot NOW! Application upgrade successful Checking the Code after upgrading

Step 8. Verify the OS after reboot.

  

CPI20/admin# show version Cisco Application Deployment Engine OS Release: 2.0 ADE-OS Build Version: 2.0.6.003-px-build ADE-OS System Architecture: x86_64 Copyright (c) 2005-2010 by Cisco Systems, Inc. All rights reserved. Hostname: CPI20 Version information of installed applications --------------------------------------------- Cisco Prime Infrastructure ------------------------------------------ Version : 2.1.0.0.87   -----------------------------<<<<< Upgraded Version

mac-address bpdu source command

Mac-address bpdu source version 2 is used to use 00:26:0b:xx:xx:x mac address as the source in BPDU by VPC peer.

Default Spanning tree mode in nexus switches

Use show spanning tree command to check the current STP mode. As you can see, RSTP-PVST+ is the default spanning tree mode on nexus switches.

N7k (config-if-range)# show spanning-tree vlan 30 VLAN0030   Spanning tree enabled protocol rstp ---------<<<<<<<<<<<<<   Root ID    Priority    32798              Address     0005.73bc.067c              This bridge is the root              Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32798  (priority 32768 sys-id-ext 30)              Address     0005.73bc.067c              Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- ------------------------------- - Eth1/1           Desg FWD 2         128.129  P2p Eth1/2           Desg FWD 2         128.130  P2p

MST configuration on Cisco Nexus 7k switches

Step 1. Check the current STP mode.

N7k (config-if-range)# show spanning-tree vlan 30 VLAN0030   Spanning tree enabled protocol rstp ---------<<<<<<<<<<<<<   Root ID    Priority    32798              Address     0005.73bc.067c              This bridge is the root              Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec   Bridge ID  Priority    32798  (priority 32768 sys-id-ext 30)              Address     0005.73bc.067c              Hello Time  2  sec  Max Age 20 sec  Forward Delay 15 sec Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- ------------------------------- - Eth1/1           Desg FWD 2         128.129  P2p Eth1/2           Desg FWD 2         128.130  P2p

Step 2 .  Enable MST mode. By default RSTP-PVST+ is enabled.

N7k (config)# spanning-tree mode mst

Step 3.  Enter in MST configuration mode

N7k (config)# spanning-tree mst configuration

Step 4.  Give the name to MST process. It should be same on all the switches otherwise switch will not recognize each other.

N7k(config-mst)#  name MST1

Step 4. Give the revision number. Similar to the name, it must be same on all switches in L2 domain.

N7k (config-mst)#  revision 1

Step 5. Create instance as per your requirement and map the vlan to it. Make sure you don’t create unnecessary large number of instance.

N7k (config-mst)# instance 1 vlan 30,40

Step 6. This is an optional step to configure the MST root. We can elect different switch as root for different MST instance.

N7k (config)# spanning-tree mst 1 root primary  N7k # show spanning-tree mst 1 ##### MST2    vlans mapped:   50,60 Bridge        address 001b.54c2.67c2  priority      24578 (24576 sysid 2) Root          this switch for MST1  ----------------<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Interface        Role Sts Cost      Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------- Eth1/1           Desg FWD 2000      128.129  P2p Eth1/2           Desg FWD 2000      128.130  P2p

MTU in EIGRP Metric

In Eigrp, Metric is calculated by using below formula.

metric = {K1*BW + [(K2*BW)/(256-load)]+(K3*delay)}*{K5/(reliability+K4)}

As we can see MTU is not present in it. So how it is impacting the EIGRP calculation?

The answer is it will not take part in route election till the time maxixmum path is not crossed. Changing MTu will not initiate the routing recalculation.

MTU is only in use when router has many routes for the destination and due to the maximum path restriction ( default or configured) it has to reject few routes then it will reject the routes with lowest MTU .

Let’s suppose if router has 16 routes for same destination and we have configured the maximum path to 4. 

So the question is how the router will select the 4 routes out of 16 best available routes. Router rejects the routes which  have the lowest MTU values. MTU is checked only on the incoming interfaces rather than outgoing interfaces.

EIGRP Metric calculation

Eigrp metric is calculated by using the below formula:-

metric = {K1*BW + [(K2*BW)/(256-load)]+(K3*delay)}*{K5/(reliability+K4)}

By default, value of only K1 and K3 are 1 and all other K values are 0 which makes the formula as shown below:-

Note: - Mismatch in K values prevents the neighbor formation.

Metric = 256 * ( Bandwidth + delay)

Bandwidth is calculated by using below expression where BWmin is in Kbps.

bandwidth= (256 x 107)/BWmin

Delay is sum of all the outgoing interface delays which comes in the path. Delay will be taken in microseconds.

delay = [sum of delays] x 256