Nexus 1000v vsm secondary not recognized
I deployed the seondary vsm but when it came up the primary vsm still does not recognize that there is a standby.
I went through the ovf and selected seondary and only entered the vsm domain id and the admin password.
after the power on the master did not see the secondary
any idea?
Hi Tony,
In order for this VSM to see its peer, you need to configure it for system redundancy role Primary.
As shown in the output, it is currently running in standalone mode.
Once we reconfigure the first deployed VSM as primary, the two VSMs should see each other (given they have L2 connectivity)
Nexus1000v# show system redundancy status
Redundancy role
administrative: standalone
operational: standalone
Redundancy mode
administrative: HA
operational: None
This supervisor (sup-1)
Redundancy state: Active
Supervisor state: Active
Internal state: Active with no standby
Other supervisor (sup-2)
Redundancy state: Not present
Nexus1000v# con
Nexus1000v(config)# system redundancy role primary
After this change, the VSMs will negotiate and the secondary will reboot. When the secondary comes back up, we should see that they have paired.
Nexus1000v(config)# show redundancy status
Redundancy role
administrative: primary
operational: primary
Redundancy mode
administrative: HA
operational: HA
This supervisor (sup-1)
Redundancy state: Active
Supervisor state: Active
Internal state: Active with HA standby
HTH,
Joe
Similar Messages
-
Nexus 1000v repo is not available
Hi everyone.
Cisco Yum repo for nexus 1000v is not available at the moment. I am wondering, is it Ok and Cisco finished it experiment with free Nexus1k or I need to contact someon (who?) to ask him to fix this problem.
PS Link to the repo: https://cnsg-yum-server.cisco.com/yumrepoLet's set the record straight here - to avoid confusion.
1. VEMs will continue to forward traffic in the event one or both VSM are unavailable - this requires the VEM to remain online and not reboot while both VSMs are offline. VSM communication is only required for config changes (and LACP negociation prior to 1.4)
2. If there is no VSM reachable, and a VEM is reboot, only then will the System VLANs go into a forwarding state. All other non-system VLANs will remain down. This is to faciliate the Chicken & Egg theory of a VEM being able to initially communicate with a VSM to obtain its programming.
The ONLY VLANs & vEth Profiles that should be set as system vlans are:
1000v-Control
1000v-Packet
Service Console/VMkernel for Mgmt
IP Storage (iSCSI or NFS)
Everything else should not be defined as a system VLAN including VMotion - which is a common Mistake.
**Remember that for a vEth port profile to behave like a system profile, it must be define on BOTH the vEth and Eth port profiles. Two factor check. This allows port profiles that maybe are not critical, yet share the same VLAN ID to behave differently.
There are a total of 16 profiles that can include system VLANs. If you exceed this, you can potentially run into issues with the Opaque data pushed from vCenter is truncated causing programming errors on your VEMs. Adhering to the limitations above should never lead to this situation.
Regards,
Robert -
Nexus 1000v VSM can't comunicate with the VEM
This is the configuration I have on my vsm
!Command: show running-config
!Time: Thu Dec 20 02:15:30 2012
version 4.2(1)SV2(1.1)
svs switch edition essential
no feature telnet
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip host Nexus-1000v 172.16.0.69
hostname Nexus-1000v
errdisable recovery cause failed-port-state
vem 3
host vmware id 78201fe5-cc43-e211-0000-00000000000c
vem 4
host vmware id e51f2078-43cc-11e2-0000-000000000009
priv 0xa2cb98ffa3f2bc53380d54d63b6752db localizedkey
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1-2
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet vmware-uplinks
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1-3967,4048-4093
channel-group auto mode on
no shutdown
system vlan 2
state enabled
port-profile type vethernet Management
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet vMotion
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet ServidoresGestion
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet L3-VSM
capability l3control
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
system vlan 2
state enabled
port-profile type vethernet VSG-Data
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
port-profile type vethernet VSG-HA
vmware port-group
switchport mode access
switchport access vlan 2
no shutdown
state enabled
vdc Nexus-1000v id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 1 maximum 1
limit-resource u6route-mem minimum 1 maximum 1
interface mgmt0
ip address 172.16.0.69/25
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-1
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-2
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-2
svs-domain
domain id 1
control vlan 1
packet vlan 1
svs mode L3 interface mgmt0
svs connection vcenter
protocol vmware-vim
remote ip address 172.16.0.66 port 80
vmware dvs uuid "ae 31 14 50 cf b2 e7 3a-5c 48 65 0f 01 9b b5 b1" datacenter-n
ame DTIC Datacenter
admin user n1kUser
max-ports 8192
connect
vservice global type vsg
tcp state-checks invalid-ack
tcp state-checks seq-past-window
no tcp state-checks window-variation
no bypass asa-traffic
vnm-policy-agent
registration-ip 172.16.0.70
shared-secret **********
policy-agent-image bootflash:/vnmc-vsmpa.2.0.0.38.bin
log-level
for some reason my vsm can't the the vem. I could before, but then my server crashed without doing a copy run start and when it booted up all my config but the uplinks was lost.
When I tried to configure the connection again it wasn't working.
I'm also attaching a screen capture of the vds
and a capture of the regular switch.
I will appreciate very much any help you could give me and will provide any configuration details that you might need.
Thank you so much.Carlos,
Looking at vds.jpg, you do not have any VEM vmkernel interface attached to port-profile L3-VSM. So fix VSM-VEM communication problem, you either migrate your VEM management vmkernel interface to L3-VSM port-profile of the vds, or create new VMkernel port on your VEM/host and attach it to L3-VSM port-profile. -
Nexus 1000v Layer3 Control not coming up
For info, I run 4.2(1)SV1(4) as a VM and not the appliance.
I tried this morning to migrate a small environment to the Nexus L3 control instead of L2 for a certain requirement. We have two ESX in the with the Nexus 1000v running sucessfully for months on L2.
I tried to follow the procedure that is in this document. I followed this script:
Created a layer3 control0 interface with an IP in vlan951.
So I had my VMWare guy move a VMKernel interface of each ESX host to this profile:
port-profile type vethernet VLAN951
vmware port-group VLAN951
capability l3control
switchport mode access
switchport access vlan 951
system vlan 951
no shutdown
state enabled
Then modified the svs domain like such:
svs-domain
no control vlan
no packet vlan
svs mode 13 interface control0
I made sure that I have layer-2 connectivity between the VSM host and the rest ESX hosts is OK, but I am not certain how you actually assign a layer 2 vlan to the control0 interface... Is it supposed to broadcast on all the VLANs? Or is it a correlation of the port-profile config and svs-domain that does that?
In any case, my two VEM go down and do not come back up once I am in l3 mode. I had to revert back to L2.
Any help would be appreciated.
Regards,
Simon T.Hi Simon,
Since you are using ctrl0 as the layer 3 interface, you need to assign the IP address under the ctrl0 interface (interface ctrl0). This IP address should be able to communicate with the vmk interface's IP address.
Regards,
Shankar -
Firewall between Nexus 1000V VSM and vCenter
Hi,
Customer has multiple security zones in environment, and VMware vCenter is located in a Management Security Zone. VSMs in security zones have dedicated management interface facing Management Security Zone with firewall in between. What ports do we need to open for the communication between VSMs and vCenter? The Nexus 1000V troubleshooting guide only mentioned TCP/80 and TCP/443. Are these outbound from VSM to vCenter? Is there any requirements from vCenter to VSM? What's the best practice for VSM management interface configuration in multiple security zones environment? Thanks.Avi -
You need the connection between vCenter and the VSM anytime you want to add or make any changes to the existing port-profiles. This is how the port-profiles become available to the virtual machines that reside on your ESX hosts.
One problem when the vCenter is down is what you pointed out - configuration changes cannot be pushed
The VEM/VSM relationship is independent of the VSM/vCenter connection. There are separate VLANs or L3 interfaces that are used to pass information and heartbeats between the VSM and its VEMs.
Jen -
VN-Link Hardware require Nexus 1000v yes or not?
I have a problem about VN-Link Hardware. When i create port profile on UCS Manager and Create Port Profile Client then vCenter will create Port Group too. But when i apply network in Virtual Machine by select Port Group in vCenter i can't see Virtual Maching Guest in VM tab on UCS Manager.
Finally question VN-Link Hardware require Nexus 1000v install on ESX yes or not? in UCS Manager GUI document say need require DVS Switch.Thank you for reply. I have successfully turn on VN-Link hardware by follow this video --> http://tinyurl.com/23p896k
and i have install Nexus 1000v VEM in ESX for turn on VN-Link hardware.
I need test performance of CNA Card (palo) and report to my CEO.
- How to test it?
- What is tool for test?
PS.Sorry for English language -
Nexus 1010 VSM does not see VEM (DPA service not running....)
Hi all,
I have the attached topology. All the conf outputs and device details are attached. The problem is "vemcmd show card info" output shows that VEM correctly receives the control, packet VLAN information from the VSM. However I couldnt make vempda service to run. I got the same output all the sayins that : "VEM Agent (vemdpa) is not running". I checked the control and packet vlan end to end connectivity by creating VMs and etc. there werent any problems....One thing is that, VEM AIPC MAC never showed up in the upstream switch which is connected to ESX host.
I would be glad if someone can help me out with any configuration errors or anything like that...
[root@sahaesx1 ~]# vem status -v
Package vssnet-esx5.5.0-00000-release
Version 4.0.4.1.3.0.0-2.0.21
Build 21
Date Sat May 22 16:25:36 PDT 2010
Number of PassThru NICs are 0
VEM modules are loaded
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 128 4 128 1500 vmnic0
DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
vsm1yeni 256 51 256 1500 vmnic2,vmnic1
Number of PassThru NICs are 0
VEM Agent (vemdpa) is not running
[root@sahaesx1 ~]# vemcmd show version
VEM Version: 4.0.4.1.3.0.0-2.0.21
VSM Version: 4.0(4)SV1(3)
System Version: VMware ESX 4.1.0 Releasebuild-235786
[root@sahaesx1 ~]#Ok. Now VEM and VSM speaks to each other. However I can not see VEM on "show module vem mapping" ? Is there any specific reason to that ?
[root@iacm-1 tmp]# vem-health check 00:02:3d:70:01:03
VSM Control MAC address: 00:02:3d:70:01:03
Control VLAN: 444
DPA MAC: 00:02:3d:40:02:00
The VEM-VSM connectivity seems to be fine.
vsm1yeni# show module uptime
------ Module 1 -----
Module Start Time: Thu Oct 14 16:49:45 2010
Up Time: 3 day(s), 23 hour(s), 45 minute(s), 6 second(s)
vsm1yeni# show module vem mapping
Mod Status UUID License Status
vsm1yeni# show module vem counters
Mod InNR OutMI InMI OutHBeats InHBeats InAipcMsgs OutTO OutTOC InsCnt RemCnt
vsm1yeni# -
Nexus 1000v 4.2.1 - Interface Ethernet3/5 has been quarantined due to Cmd Failure
Hello,
i get the error message "Interface Ethernet3/5 has been quarantined due to Cmd Failure" when i try to activate the System Uplink ports on the Nexus 1000v VSM. The symptom occurs under 4.2.1.SV1.4 (has been fresh setup, did before tests with 4.0.4). Unfortunately, the link to the 4.2.1 troubleshooting guide does not work (seems it hasn't been released yet).
Has anyone an idea what the root cause could be?
The VSM and VEM run on a GP DL3xxG7 with 2 x Dual Port 10Gbit CNA Adapters.
Nexus 1k config:
vlan 1
vlan 260
name Servers
vlan 340
name NfsA
vlan 357
name vMotion
vlan 920
name Packet_Control
port-profile type ethernet SYSTEM-UPLINK
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,260,301,303,305,307,357,544,920
spanning-tree port type edge trunk
switchport trunk native vlan 1
channel-group auto mode active
no shutdown
system vlan 1,357,920
state enabled
port-profile type ethernet STORAGE-UPLINK
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 340
channel-group auto mode active
no shutdown
system vlan 340
state enabled
When i do a no shut on the physical ports i get:
switch(config-if)# no shut
2011 Feb 24 11:43:55 switch %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/7 has been quarantined due to Cmd Failure
2011 Feb 24 11:43:55 switch %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/5 has been quarantined due to Cmd Failure
The other etherchannel (Port Profile STORAGE-UPLINK) does work pretty well...
The peer switches are two Nexus 5k with VPC.
config:
port-profile type port-channel VMWare-LAN
switchport mode trunk
switchport trunk allowed vlan 260, 301, 303, 305, 307, 357, 544, 920
spanning-tree port type edge trunk
switchport trunk native vlan 1
state enabled!
interface port-channel18
inherit port-profile VMWare-LAN
description CHA vshpvm001 LAN
vpc 18
speed 10000!
interface Ethernet1/18
description CHA vshpvm001 LAN
switchport mode trunk
switchport trunk allowed vlan 260,301,303,305,307,357,544,920
channel-group 18 mode active
switch# show port-profile sync-status
Ethernet3/5
port-profile: SYSTEM-UPLINK
interface status: quarantine
sync status: out of sync
cached commands:
errors:
cached command failed
recovery steps:
unshut interface
Ethernet3/7
port-profile: SYSTEM-UPLINK
interface status: quarantine
sync status: out of sync
cached commands:
errors:
cached command failed
recovery steps:
unshut interface
kind regards,
andySean,
thank you !
"show accounting log" helped me - i had the command spanning-tree port type edge trunk in the config which i somehow didn't realize that we hadn't this command in the 4.0.4 lab setup...so it was a copy/paste error (i copied the port-profile config from the N5k down to the N1k).
Fri Feb 25 07:20:32 2011:update:ppm.13880:admin:configure terminal ; interface Ethernet3/5 ; spanning-tree port type edge trunk (FAILURE)
Fri Feb 25 07:20:32 2011:update:ppm.13890:admin:configure terminal ; interface Ethernet3/5 ; shutdown (FAILURE)
As the N1k doesn't do STP at all (or does it? ) it's no wonder that the cli was complaining ...
Maybe this command should get more attention in the tshoot guide as it seems to be a very helpful one.
Cheers & Thanks,
Andy -
Cisco Nexus 1000v VXLAN don't work
Hi to all,
I configured VXLAN configuration by the book (Cisco Nexus 1000V VXLAN Configuration Guide, Release 4.2(1)SV1(5.1)), but there is some problem.
There are two ESXs with four VMs (two VMs on each ESX). Each VM has one NIC and that NIC is assigned to a port-profile configured for same VXLAN bridge-domain access. There is connectivity between VMs on same ESX but there is no connectivity between VMs hosted on different ESXs. In other words, L2 connectivity works between VMs on same ESX but not between VMs on different ESXs.
Nexus 1000V VSM is installed on Nexus 1010 Appliance and manages two VEMs through L3 control interfaces.
VSM version is 4.2(1)SV1(5.1) and VEM feature level is 4.2(1)SV1(5.1).
Bridge-domain is VXLAN-5001 with segment id 5001 and group address 239.1.1.1
Port-profile for VMK VXLAN interface is properly configured for access to VLAN 588 ("transport" VLAN for VXLAN) and capability vxlan.
VLAN 588 is allowed on all uplinks on both sides (Nexus and physical switch).
Port profile for VMs if properly configured for access to bridge-domain.
I was create a monitor session for VLAN 588 on upstrean switch (Cisco 6513 with 12.2(18)SXF14 IOS) and did't see any multicast, unicast or any other traffic. According to documentation, first I shuld to see IGMP join, after that multicast and after that unicast traffic between two VMK interfaces.
Here is MAC address table for bridge-domain VXLAN-5001:
Nexus1000V-VSM-1# sh mac address-table bridge-domain VXLAN-5001
Bridge-domain: VXLAN-5001
MAC Address Type Age Port IP Address Mod
--------------------------+-------+---------+---------------+---------------+---
0050.56a3.0009 static 0 Veth6 0.0.0.0 3
0050.56a3.000a static 0 Veth7 0.0.0.0 3
0050.56a3.0007 static 0 Veth4 0.0.0.0 4
0050.56a3.0008 static 0 Veth5 0.0.0.0 4
Total MAC Addresses: 4
As you can see, there is no proper destination IP addresses.
Can somebody help me?Good hint, but it seems that is not the problem...
Cat ports connecting VEMs support jumbo frames and their MTU is set to 9216B.
I saw that MTU on Ethernet interfaces of VEMs is set to 1500B, I changed uplink port-profile and set MTU to first to 1550B, and after that to 9000B (max), but thing still isn't working.
I'm not using vCloud director, just VMware vSphere 4.1 (vCenter Server with VUM, vCenter Client and two ESX hosts).
Message was edited by: Mate Grbavac
After little research I found something strange... I setted up SVI on Cat in Vlan 588 ("transport" VLAN for VXLAN) and when I ping VMKernel interface (with capabilitiy vxlan) with packet size more than 1500B and df bit set I have no reply. My Cat ports and UpLink port profiles are configured for jumbo frames. Is it possible to change MTU of VMKernel interface? -
[Nexus 1000v] VEM can't be add into VSM
hi all,
following my lab, i have some problems with Nexus 1000V when VEM can't be add into VSM.
+ on VSM has already installed on ESX 1 (standalone or ha) and you can see:
Cisco_N1KV# show module
Mod Ports Module-Type Model Status
1 0 Virtual Supervisor Module Nexus1000V active *
Mod Sw Hw
1 4.2(1)SV1(4a) 0.0
Mod MAC-Address(es) Serial-Num
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP Server-UUID Server-Name
1 10.4.110.123 NA NA
+ on ESX2 that 's installed VEM
[root@esxhoadq ~]# vem status
VEM modules are loaded
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 128 3 128 1500 vmnic0
VEM Agent (vemdpa) is running
[root@esxhoadq ~]#
any advices for this,
thanks so muchHi,
i'm having similar issue: the VEM insatlled on the ESXi is not showing up on the VSM.
please check from the following what can be wrong?
This is the VEM status:
~ # vem status -v
Package vssnet-esx5.5.0-00000-release
Version 4.2.1.1.4.1.0-2.0.1
Build 1
Date Wed Jul 27 04:42:14 PDT 2011
Number of PassThru NICs are 0
VEM modules are loaded
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 128 4 128 1500 vmnic0
DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
VSM11 256 40 256 1500 vmnic2,vmnic1
Number of PassThru NICs are 0
VEM Agent (vemdpa) is running
~ # vemcmd show port
LTL VSM Port Admin Link State PC-LTL SGID Vem Port
18 UP UP F/B* 0 vmnic1
19 DOWN UP BLK 0 vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show trunk
Trunk port 6 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 16 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 18 native_vlan 1 CBL 0
vlan(111) cbl 1, vlan(112) cbl 1,
~ # vemcmd show port
LTL VSM Port Admin Link State PC-LTL SGID Vem Port
18 UP UP F/B* 0 vmnic1
19 DOWN UP BLK 0 vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show port vlans
Native VLAN Allowed
LTL VSM Port Mode VLAN State Vlans
18 T 1 FWD 111-112
19 A 1 BLK 1
~ # vemcmd show port
LTL VSM Port Admin Link State PC-LTL SGID Vem Port
18 UP UP F/B* 0 vmnic1
19 DOWN UP BLK 0 vmnic2
* F/B: Port is BLOCKED on some of the vlans.
Please run "vemcmd show port vlans" to see the details.
~ # vemcmd show port vlans
Native VLAN Allowed
LTL VSM Port Mode VLAN State Vlans
18 T 1 FWD 111-112
19 A 1 BLK 1
~ # vemcmd show trunk
Trunk port 6 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 16 native_vlan 1 CBL 1
vlan(1) cbl 1, vlan(111) cbl 1, vlan(112) cbl 1, vlan(3968) cbl 1, vlan(3969) cbl 1, vlan(3970) cbl 1, vlan(3971) cbl 1,
Trunk port 18 native_vlan 1 CBL 0
vlan(111) cbl 1, vlan(112) cbl 1,
~ # vemcmd show card
Card UUID type 2: ebd44e72-456b-11e0-0610-00000000108f
Card name: esx
Switch name: VSM11
Switch alias: DvsPortset-0
Switch uuid: c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78
Card domain: 1
Card slot: 1
VEM Tunnel Mode: L2 Mode
VEM Control (AIPC) MAC: 00:02:3d:10:01:00
VEM Packet (Inband) MAC: 00:02:3d:20:01:00
VEM Control Agent (DPA) MAC: 00:02:3d:40:01:00
VEM SPAN MAC: 00:02:3d:30:01:00
Primary VSM MAC : 00:50:56:ac:00:42
Primary VSM PKT MAC : 00:50:56:ac:00:44
Primary VSM MGMT MAC : 00:50:56:ac:00:43
Standby VSM CTRL MAC : ff:ff:ff:ff:ff:ff
Management IPv4 address: 10.1.240.30
Management IPv6 address: 0000:0000:0000:0000:0000:0000:0000:0000
Secondary VSM MAC : 00:00:00:00:00:00
Secondary L3 Control IPv4 address: 0.0.0.0
Upgrade : Default
Max physical ports: 32
Max virtual ports: 216
Card control VLAN: 111
Card packet VLAN: 112
Card Headless Mode : Yes
Processors: 8
Processor Cores: 4
Processor Sockets: 1
Kernel Memory: 16712336
Port link-up delay: 5s
Global UUFB: DISABLED
Heartbeat Set: False
PC LB Algo: source-mac
Datapath portset event in progress : no
~ #
On VSM
VSM11# sh svs conn
connection vcenter:
ip address: 10.1.240.38
remote port: 80
protocol: vmware-vim https
certificate: default
datacenter name: New Datacenter
admin:
max-ports: 8192
DVS uuid: c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78
config status: Enabled
operational status: Connected
sync status: Complete
version: VMware vCenter Server 4.1.0 build-345043
VSM11# sh svs ?
connections Show connection information
domain Domain Configuration
neighbors Svs neighbors information
upgrade Svs upgrade information
VSM11# sh svs dom
SVS domain config:
Domain id: 1
Control vlan: 111
Packet vlan: 112
L2/L3 Control mode: L2
L3 control interface: NA
Status: Config push to VC successful.
VSM11# sh port
^
% Invalid command at '^' marker.
VSM11# sh run
!Command: show running-config
!Time: Sun Nov 20 11:35:52 2011
version 4.2(1)SV1(4a)
feature telnet
username admin password 5 $1$QhO77JvX$A8ykNUSxMRgqZ0DUUIn381 role network-admin
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip domain-lookup
hostname VSM11
snmp-server user admin network-admin auth md5 0x389a68db6dcbd7f7887542ea6f8effa1
priv 0x389a68db6dcbd7f7887542ea6f8effa1 localizedkey
vrf context management
ip route 0.0.0.0/0 10.1.240.254
vlan 1,111-112
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet system-uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 111-112
no shutdown
system vlan 111-112
description "System profile"
state enabled
port-profile type vethernet servers11
vmware port-group
switchport mode access
switchport access vlan 11
no shutdown
description "Data Profile for VM Traffic"
port-profile type ethernet vm-uplink
vmware port-group
switchport mode access
switchport access vlan 11
no shutdown
description "Uplink profile for VM traffic"
state enabled
vdc VSM11 id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 32 maximum 32
limit-resource u6route-mem minimum 16 maximum 16
limit-resource m4route-mem minimum 58 maximum 58
limit-resource m6route-mem minimum 8 maximum 8
interface mgmt0
ip address 10.1.240.124/24
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-2
svs-domain
domain id 1
control vlan 111
packet vlan 112
svs mode L2
svs connection vcenter
protocol vmware-vim
remote ip address 10.1.240.38 port 80
vmware dvs uuid "c4 be 2c 50 36 c5 71 97-44 41 1f c0 43 8e 45 78" datacenter-n
ame New Datacenter
max-ports 8192
connect
vsn type vsg global
tcp state-checks
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level
thank you
Michel -
DVD Drive not recognized in secondary IDE slot
PLease help. I removed my DVD player from the primary IDE slot and plugged into the secondary IDE slot and now it is not recognized by either the BIOS or XP. I installed a new ATA hard drive into the primary IDE slot. The ATA drive is recognized and works fine.
Please help!!!For 865PE/875 boards using WinXP
Bios>>Integrated Peripherals>>On-Chip IDE Config.>>
Native Mode
SATA Only (can also try PATA only here if required)
Keep PATA enabled - Yes
Both Channels
SATA as Raid - NO unless you are using Raid
Legacy mode is for old OS's that only support 2 IDE channels
1 channel reserved for IDE, other for SATA1&2 to share. Remaining IDE channel disabled
Native Mode is for newer OS's and supported by XP.
Both IDE channels enabled, both SATA channels enabled. -
Can a Nexus 1000v be configured to NOT do local switching in an ESX host?
Before the big YES, use an external Nexus switch and use VN-Tag. The question is when there is a 3120 in a blade chassis that connects to the ESX hosts that have a 1000v installed on the ESX host. So, first hop outside the ESX host is not a Nexus box.
Looking for if this is possible, if so how, and if not, where that might be documented. I have a client who's security policy prohibits switching (yes, even on the same VLAN) within a host (in this case blade server). Oh and there is an insistance to use 3120s inside the blade chassis.
Has to be the strangest request I have had in a while.
Any data would be GREATY appreciated!Thanks for the follow up.
So by private VLANs, are you referring to "PVLAN":
"PVLANs: PVLANs are a new feature available with the VMware vDS and the Cisco Nexus
1000V Series. PVLANs provide a simple mechanism for isolating virtual machines in the
same VLAN from each other. The VMware vDS implements PVLAN enforcement at the
destination host. The Cisco Nexus 1000V Series supports a highly efficient enforcement
mechanism that filters packets at the source rather than at the destination, helping ensure
that no unwanted traffic traverses the physical network and so increasing the network
bandwidth available to other virtual machines" -
FEX 2232TM not recognized by Nexus 5010P
Hi there,
I don't have any clue what this problem might be so please help.
I have a brandnew FEX 2232TM which is connected to a NEXUS 5010P running the following firmware:
oftware
BIOS: version 1.5.0
loader: version N/A
kickstart: version 5.2(1)N1(1)
system: version 5.2(1)N1(1)
power-seq: Module 1: version v1.2
BIOS compile time: 11/30/10
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.2.1.N1.1.bin
kickstart compile time: 7/12/2012 19:00:00 [07/13/2012 02:08:13]
system image file is: bootflash:///n5000-uk9.5.2.1.N1.1.bin
system compile time: 7/12/2012 19:00:00 [07/13/2012 03:23:16]
According to the Cisco download page it is the latest version and should definitely support the 2232TM.
The problem is that the FEX is completely not recognized by the parent Nexus.
It is connected via 8 FET modules. But when ich check the light on both sides I only have light on the NEXUS side never on the FEX side on all modules.
From my understanding this should be the root cause of the issue because no light = no link.
I tried standard 10GBase-SR and Twinax cables as well. Same behavior - the FEX is not recognized.
The status LED if of course orange on the FEX.
This is the FEX related config ont he NEXUS:
feature fex
fex 101
pinning max-links 8
description "FEX0101"
interface Ethernet1/1
switchport mode fex-fabric
fex associate 101
interface Ethernet1/2
switchport mode fex-fabric
fex associate 101
interface Ethernet1/3
switchport mode fex-fabric
fex associate 101
interface Ethernet1/4
switchport mode fex-fabric
fex associate 101
interface Ethernet1/5
switchport mode fex-fabric
fex associate 101
interface Ethernet1/6
switchport mode fex-fabric
fex associate 101
interface Ethernet1/7
switchport mode fex-fabric
fex associate 101
interface Ethernet1/8
switchport mode fex-fabric
fex associate 101
Can anyone give me a hint what I am missing here??
Any help is really appreciated.
Thanks a lot!I have a two lab switches running 5.2.1.N1.1 and connected in vpc with 2232TM and I am able to see the fex online without any problems. One side I have SFP-10G-SR and other side I have 3M Cisco Twinax cable.
here is the output from my lab,
5010-1# show fex
FEX FEX FEX FEX
Number Description State Model Serial
100 FEX0100 Online N2K-C2232TM-10GE SSI15380CPM
5010-1# show fex 100 detail
FEX: 100 Description: FEX0100 state: Online
FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
FEX Interim version: 5.2(1)N1(1)
Switch Interim version: 5.2(1)N1(1)
Extender Serial: SSI15380CPM
Extender Model: N2K-C2232TM-10GE, Part No: 73-13626-03
Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po100 - Interface Up. State: Active
Eth1/1 - Interface Up. State: Active
Fex Port State Fabric Port
5010-1# show interface e1/1 transceiver details
Ethernet1/1
transceiver is present
type is SFP-H10GB-CU3M rev A
name is CISCO-MOLEX INC
part number is 74752-9026
revision is A
serial number is MOL12240343
nominal bitrate is 12000 MBit/sec
Link length supported for copper is 3 m
cisco id is --
cisco extended id number is 4
DOM is not supported
5010-2# show fex
FEX FEX FEX FEX
Number Description State Model Serial
100 FEX0100 Online N2K-C2232TM-10GE SSI15380CPM
5010-2# show fex 100 detail
FEX: 100 Description: FEX0100 state: Online
FEX version: 5.2(1)N1(1) [Switch version: 5.2(1)N1(1)]
FEX Interim version: 5.2(1)N1(1)
Switch Interim version: 5.2(1)N1(1)
Extender Serial: SSI15380CPM
Extender Model: N2K-C2232TM-10GE, Part No: 73-13626-03
Card Id: 164, Mac Addr: 28:94:0f:2e:12:82, Num Macs: 64
Module Sw Gen: 21 [Switch Sw Gen: 21]
post level: complete
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po100 - Interface Up. State: Active
Eth1/1 - Interface Up. State: Active
Fex Port State Fabric Port
5010-2# show interface e1/1 transceiver details
Ethernet1/1
transceiver is present
type is 10Gbase-SR
name is CISCO-AVAGO
part number is SFBR-7700SDZ-CS2
revision is B5
serial number is AGD133133S4
nominal bitrate is 10300 MBit/sec
Link length supported for 50/125um OM2 fiber is 82 m
Link length supported for 50/125um OM3 fiber is 300 m
Link length supported for 62.5/125um fiber is 26 m
cisco id is --
cisco extended id number is 4
SFP Detail Diagnostics Information (internal calibration)
Current Alarms Warnings
Measurement High Low High Low
Temperature 44.18 C 75.00 C -5.00 C 70.00 C 0.00 C
Voltage 3.26 V 3.63 V 2.97 V 3.46 V 3.13 V
Current 6.48 mA 10.50 mA 2.50 mA 10.50 mA 2.50 mA
Tx Power -2.62 dBm 1.69 dBm -11.30 dBm -1.30 dBm -7.30 dBm
Rx Power -2.80 dBm -- 1.99 dBm -13.97 dBm -1.00 dBm -9.91 dBm
Note: ++ high-alarm; + high-warning; -- low-alarm; - low-warning
So dont believe we have any interoperability issue with 5010 and 2232TM here. Before we swap out this fex, can you please open a case with Cisco support or let me know when you are available and I can do a webex to look at this switch to see if there is something more to this problem than what we already know ?
Thanks,
Vinayak -
Hi,
We are planning to install Cisco Nexus 1000v in our environment. Before we want to install we want to explore little bit about Cisco Nexus 1000v
• I know there is 2 elements for Cisco 1k, VEM and VSM. Does VSM is required? Can we configure VEM individually?
• How does Nexus 1k integrated with vCenter. Can we do all Nexus 1000v configuration from vCenter without going to VEM or VSM?
• In term of alarming and reporting, does we need to get SNMP trap and get from individual VEM or can be use VSM to do that. OR can we get Cisco Nexus 1000v alarming and reporting form VMware vCenter.
• Apart from using Nexus 1010 can what’s the recommended hosting location for VSM, (same Host as VEM, different VM, and different physical server)
Foyez AhammedHi Foyez,
Here is a brief on the Nexus1000v and I'll answer some of your questions in that:
The Nexus1000v is a Virtual Distributed Switch (software based) from Cisco which integrated with the vSphere environment to provide uniform networking across your vmware environment for the host as well as the VMs. There are two components to the N1K infrastructure 1) VSM 2) VEM.
VSM - Virtual supervisor module is the one which controls the entire N1K setup and is from where the configuration is done for the VEM modules, interfaces, security, monitoring etc. VSM is the one which interacts with the VC.
VEM - Virtual ethernet module are simply the module or virtual linecards which provide the connectivity option or virtual ports for the VMs and other virtaul interfaces. Each ESX host today can only have one VEM. These VEMs recieve their configuration / programing from the VSM.
If you are aware of any other switching products from Cisco like the Cat 6k switches, the n1k behaves the same way but in a software / virtual environment. Where the VSM are equal of a SUPs and the VEM are similar to the line cards. The control and the packet VLANs in the n1k provide the same kind of AIPC and Inband connectivity as the 6k backplane would for the communication between the modules and the SUP (VSM in this case).
*The n1k configuration is done only from the VSM and is visible in the VC.However the port-profiles created from the VSM are pushed from the VSM to the VC and have to be assigned to the virtual / physical ports from the VC.
*You can run the VSM either on the Nexus1010 as a Virtual service blade (VSB) or as a normal VM on any of the ESX/ESXi server. The VSM and the VEM on the same server are fully supported.
You can refer the following deployment guide for some more details: http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/guide_c07-556626.html
Hope this answers your queries!
./Abhinav -
Trying to install original drive into secondary bay, but drive is not recognized
I have a DV7 QE, and replaced the hard drive that came with it with an SSD. So far, so good. But then I installed the original drive into the secondary bay, and it is not recognized. Are there some kind of jumper settings I need to set to make it recognizable as an additional disk drive?
David34234 wrote:
I have a DV7 QE, and replaced the hard drive that came with it with an SSD. So far, so good. But then I installed the original drive into the secondary bay, and it is not recognized. Are there some kind of jumper settings I need to set to make it recognizable as an additional disk drive?
I think so. I have never had a laptop with two SATA hard drives but I had to set jumpers on a desktop. The first hard drive was set as primary and the other drive had the jumper on slave. That was a long time ago but you can't go wrong with that. I have noticed that some laptops had disabled the second SATA slot. Make sure that the slot is not disabled in the BIOS.
Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
Testing - HP 15-p000
HP Touchpad provided by HP
Currently on Debian Wheeze
*Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*
Maybe you are looking for
-
Print to two printers with one command?
Is there a way to print the same document to two printers with one command? I'd like to have every document I print automatically saved as a PDF at the same time. Thanks, Mark. MacBook Pro (and 5 others) Mac OS X (10.4.9)
-
Applet TAB navigation not working with 1.4.1_01
I recently upgraded to Java version 1.4.1_01. Now, when I load my applets, the TAB key cannot be used for navigation until I open the Java console and then close it again. To ensure that my the threads in my specific Applet are not the problem, I cam
-
A Separte contact lists was created on BB when I tried to synch with Outlook 2010
Device: BB Style 9670 Carrier: Sprint OS: 6.0 Bundle 3049 (v6.0.0.706) I am not using an enterprise server. I had used an enterprise server over a year ago, but I removed the IT policy when I stopped using the enterprise server. I have been synching
-
Apple TV 2 isn't recognizing that I have a season pass after update.
I recently updated to the latest update on Apple TV. I have a season pass to a show, but now my Apple TV 2 does not allow me to download episodes without paying for them again. I am logged in with my apple ID, so that's not the problem. I received
-
How do i make a web object scrollable on a tablet?
i put a web object on a slide and i used the folder icon in the property panel to target a pdf file. when i run the course in my laptop browser, locally or from a web server, the web object scrolls as it should and i can read the entire pdf. but when