09-12-2011 08:10 AM
Greetings All,
I am having a heck of a time getting these 1010's running. I am tring to create a virtual services blade and I am using a Cisco guide and when I attempt to enable the new VSB I get an error. I verified that the file that I am using is in the repolitory directory on the unit. Any thoughts or assistance would be appreciated.
1010-01(config-vsb-config)# enable pr
primary properties
1010-01(config-vsb-config)# enable primary
Enter vsb image: [nexus-1000v.4.2.1.SV1.4.iso]
Enter domain id[1-4095]: 700
Management IP version [V4/V6]: [V4]
Enter Management IP address: 10.xxx.xxx.15
Enter Management subnet mask: 255.255.255.0
IPv4 address of the default gateway: 10.xxx.xxx.1
Enter HostName: VSM-1
Enter the password for 'admin': ***********
1010-01(config-vsb-config)# 2011 Sep 16 15:51:09 1010-01 %KERN-3-SYSTEM_MSG: redun_platform_ioctl : Not a VSM - kernel
2011 Sep 16 15:51:09 1010-01 %CPPA_MGR-3-ENABLE_VB_FAILURE: Virtual service blade 2 could not be enabled. Error: success
1010-01(config-vsb-config)# enable pr
primary properties
1010-01(config-vsb-config)# enable primary
Enter vsb image: [nexus-1000v.4.2.1.SV1.4.iso]
Enter domain id[1-4095]: 700
Management IP version [V4/V6]: [V4]
Enter Management IP address: 10.xxx.xxx.15
Enter Management subnet mask: 255.255.255.0
IPv4 address of the default gateway: 10.xxx.xxx.1
Enter HostName: VSM-1
Enter the password for 'admin': ***********
1010-01(config-vsb-config)# 2011 Sep 16 15:51:09 1010-01 %KERN-3-SYSTEM_MSG: redun_platform_ioctl : Not a VSM - kernel
2011 Sep 16 15:51:09 1010-01 %CPPA_MGR-3-ENABLE_VB_FAILURE: Virtual service blade 2 could not be enabled. Error: success
Solved! Go to Solution.
09-12-2011 06:47 PM
Please send me the following:
dir bootflash:repository
sh ver
sh run
sh sys red status
sh logging
09-12-2011 06:47 PM
Please send me the following:
dir bootflash:repository
sh ver
sh run
sh sys red status
sh logging
10-03-2011 05:47 AM
Greetings,
Sorry for the long delay. I did want to pass along the solution to my problem and maybe it will help someone else.
Working with TAC it was discovered that the issue was a combination or missing configurations, not having ports 3-6 configured for the Control and Packet VLAN along with the VSM file being present on one unit but not the other. Not sure how that happened but it did. Also accourding to TAC there is some kind of BUG that can raise its ugly head in the newest version of software for the 1010 that causes this "split brain" issue.
Ultimatly I reinstalled the OS to the constant rebooting node and made sure that the configurations on the unit that was active were correct. Once that was done it booted and came right up.
10-03-2011 08:25 AM
I believe there was a misunderstanding in what was communicated. There are no known issues in N1010 SP1(3) which would result in split-brain situation or corruption of the HA Standby system. There are several documentation defects open to clarify cabling and upstream switch configuration. It was these defects referred to in the TAC case. Sorry for the confusion. Glasco
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide