C210 ESXI Port Group

Hi,
I had an issue where traffic on one of my ESXI port groups stopped passing traffic.
Port Group name :UCM vnic 1&2 - Catalyst 4500 Etherchannel Mode on, access vlan 100
Port Group name :Unity/Uccx vnic 3&4 - Catalyst 4500 Etherchannel Mode on, access vlan 100
My setup was in my UC environment was configured with 2 x vNics for my UCM VMs and 2 x vNics for my Unity/IUCCX VMs.
I am not trunking over the Etherchanels, and my Cisco switches are configured with mode on, and are access ports in Vlan 100.
Traffic stopped passing over Port Group Unity/UCCX and I was unable to access the VMs from the switch side of the network. As all VMs are in the same vlan, I moved my Unity and UCCX VMs into Port Group UCM and then they were reachable from the network. Only Port Group Unity/Uccx had failed.
The only way I could resolve the issue was to power down all VMs and reboot the C210 server.
They had been operational for a period of time before the fault appeared. Any ideas why this may have happed or how to resolve without a complete server reboot would be appreciated.
thanks
Ian.

Ian,
I would suggest you to open a TAC service request with following information
ESXi logs ( vm-support command output )
CIMC show tech
Upstream Switch show tech
Approx date & time of the problem event
So it worked when we moved the VMs to other port group on the vSwitch, right ?
We need to look into VMware messages log file for this event.
Padma

Similar Messages

Static nat and service port groups

I need some help with opening ports on my ASA using firmware 9.1.2.
I read earlier today that I can create service groups and tie ports to those. But how do I use those instead of using 'object network obj-ExchangeSever-smtp' ?
I have the ACL -
access-list incoming extended permit tcp any object-group Permit-1.1.1.1 interface outside
Can this statement
object network obj-ExchangeSever-smtp
nat (inside,outside) static interface service tcp smtp smtp
reference the service port groups instead?
Thanks,
Andrew

Hi,
Are you looking a way to group all the ports/services you need to allow from the external network to a specific server/servers?
Well you can for example configure this kind of "object-group"
object-group service SERVER-PORTS
service-object tcp destination eq www
service-object tcp destination eq ftp
service-object tcp destination eq https
service-object icmp echo
access-list OUTSIDE-IN permit object-group SERVER-PORTS any object
The above would essentially let you use a single ACL rule to allow multiple ports to a server or a group of servers. (Depending if you use an "object" or "object-group" to tell the destination address/addresses)
I am not sure how you have configured your NAT. Are they all Static PAT (Port Forward) configurations like the one you have posted above or perhaps Static NAT configurations?
You can use the "object network " created for the NAT configuration in the above ACL rule destination field to specify the host to which traffic will be allowed to. Using the "object" in the ACL doesnt tell the ASA the ports however. That needs to be configured in the above way or in your typical way.
Hope this helps
- Jouni

Port groups in NX7000 F2 48-port 1G/10G Ethernet module in regard to VDC?

Have couple of questions about assigning ports on the F2 1G/10G Ethernet module to VDC. Thanks for any help.
1) The older 32-port 10G Ethernet module has port groups. When assigning ports to VDC, ports in the same port group should be assigned to the same VDC. Is it the same scenario with the newer F2 1G/10G Ethernet module? If so, where can I find information about mapping between ports and port groups?
2) The older 32-port 10G module has ports in dedicated mode or shared mode due to its 80G bandwidth to the switching fabrid. Is each port of the newer F2 10G module at 10G line rate? If that's the case, I can then assigned any ports to be vPC peer link, as oppsed to the older 32 port module where only one port from a port group can be in dedicated mode to be vPC peer link.
Thanks again

1) F2 has the same limitation. The port-group is grouped by the SoC. Meaning 1-4 is port-group 1, 5-8 is port-group 2, etc.
2) F2 is line rate if you have 5x Fab-2 module. Yes you can assign any port as vPC peer-link but you should consider the MAC limitation when designing such solution.
HTH,
jerry

Prime Infrastructure (2.0) utilization report on port group possible?

Hello
I want to create an interface utilization report for a specific port group in PI, but can't see how to do that in the report setting. You only seem to be able to select a specific device or site rather than port group. Is it possible? Also, is it possible to put that on a dashlet?
thanks for your help

Thanks for that Mahavir
Yes, I worked that out a little while ago, and can now see interface utilization by port group on the Performance > Network Interface page. I do have another question however (well two)....
I wanted to add graph over time for the utilization to the detail dashboard, but nothing shows up, even though I see the utilization in the network interface page, so I'm sure the monitoring is deployed. Why is the data missing from the graphs?
Also, I wanted to see interface packets per second graphs, but see that is not part of any default template, so I created a customer SNMP template from the IF-MIB to do this, but I can only deploy that against sites/devices or a list of interfaces, and not port groups. Why can't I deploy a customer SNMP template against a port group?
thanks for your help

NX7K VDC: port groups in F2 48-port 1G/10G Ethernet module?

Have couple of questions about assigning ports on the F2 1G/10G Ethernet module to VDC. Thanks for any help.
1) Does the newer F2 1G/10G 48-port Ethernet module have port groups as the older 32-port 10G Ethernet module? If so, where can I find information about mapping between ports and port groups?
2) The older 32-port 10G module has ports in dedicated mode or shared mode due to its 80G bandwidth to the switching fabrid. Is each port of the newer F2 10G module at 10G line rate or still the same as the older 32-port module? I want to make sure the 10G ports for vPC peer link are in line rate.
Thanks again

Hi there
The F2 line card use the SOC (Switch On Chip) architecture where each SOC manages a group of 4 contiguous ports called “Port-Group”
the port groups on the F2 are broken up into groups of four, 1, 2, 3, 4 are part of port-group1, and then so on down the line in groups of 12 groups
"12x4= 48 ports "
For changing the bandwidth and VDC allocation it is highly recommended to use the entire port group using same attribute/VDC
“N7K-F248 Requires allocation in port groups of four to align ASIC resources”
http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/virtual_device_context/configuration/guide/vdc_mgmt.html#wp1170127
the each interface of the F2 is a "10G line rate" which can provide you with up to 480G per line card
however you need to make sure that you have enough Fabric moduls to support the required bandwidth in the backbend/fabric
for example example each FAB2 can provide up to 110G per slot so to run the F2 with its full capacity you need 5x FAB2
hope this helps
If helpful rate

VMware ESX Cluster Port Groups not Replicated as Network Sites in SCVMM 2012 Logical Switch

To whom it may concern,
We have added our ESX 4.1 Update 2 Cluster that's being managed by VMware vCenter to SCVMM 2012 because we want to create a private cloud and use the resources of the ESX cluster. SCVMM is replicating all the vSwitch from the ESX cluster as a logical network
but it's not replicating the port groups on the vSwitch as Network Sites associated to the Logical Network.
May you please advise or confirm that this is the normal behaviour of SCVMM? Or is there any way that SCVMM would be able to recognize the port groups associated to the ESX vSwitch and replicate it a a Networks Sites associated to Logical Switches?
Your prompt response will be greatly appreciated.
Thanks in advance!

Hi Graham,
Thanks for your reply.
I understand that we need to configure the port groups in the vCenter server but SCVMM is only replicating the vSwitch as a Logical Network but not the port groups. It should also replicate the port group as a network site associated to the logical network.
On our VMware environment, we have port groups on different VLANs and being mapped to one physical NIC. When creating a VMware VM in a private cloud with a self-service user role we can't select the option to connect the port group that we've created from
the vCenter server. The only option it gives is the logical network (vSwitch) not the port groups within that logical network (vSwitch). Even if we create network site within the logical network (with assigned VLAN) in SCVMM, it randomly selects the port group
within the VMware vSwitch when we create a VM. We need the users with a self-service role to be able to select the port group from our vSwitch to assign the virtual NIC of the VM to a specific port group. In this way, they don't have to call or email us to
assign the VM to a port group.
I still don't understand why SCVMM does not map the port groups we've created from VMware vCenter server with user that has a self-service role. Is there any other way so that we can map the port group automatically to SCVMM?
Please advise. Thanks!

Port Groups on Multiple switches

Is it possible to create a port group that contains ports from multiple physical switches. We are using Catalyst 3500 series switches that are connected to a Catalyst 6509 running layer 3.

The Etherchannel do not HAVE to be on the same switch.
You may configure an etherchannel between 3 physical switches :
cf http://www.cisco.com/en/US/products/hw/switches/ps5023/products_configuration_example09186a00806cb982.shtml
a document called "Cross-Stack EtherChannel on a Catalyst 3750 Switch Configuration Example"

Prime Infrastructure port grouping

Hi,
I have question regarding the port groups.
Is it possible to create a port group based on port type where the port type is a dot1q trunk?
In the drop down menu, I can only find Cisco ISL.
My goal is to apply the interface/port monitoring only on trunk interfaces/ports.
Regards
Joerg

This discussion will be of your help:
https://supportforums.cisco.com/thread/2239478
You can select the interfaces of your interest for port groups manually. Check the user guide here:
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/2.0/user/guide/setup_groups.html#wp1055433
P.S : In CSC it is always good to share the device and Cisco PI platform and version details. Many times you'll find features are supported in one release and not in others.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **

Prime 2.2 : Deploy template to port group

Dear Cisco guys,
We managed to make a port group, we managed to make a template, but how do you couple both ?
For example : Change description on fa0/1 & fa0/2 in switchA ?
Many thanks,
Lieven Stubbe
Belgian railways

Thanks for that Mahavir
Yes, I worked that out a little while ago, and can now see interface utilization by port group on the Performance > Network Interface page. I do have another question however (well two)....
I wanted to add graph over time for the utilization to the detail dashboard, but nothing shows up, even though I see the utilization in the network interface page, so I'm sure the monitoring is deployed. Why is the data missing from the graphs?
Also, I wanted to see interface packets per second graphs, but see that is not part of any default template, so I created a customer SNMP template from the IF-MIB to do this, but I can only deploy that against sites/devices or a list of interfaces, and not port groups. Why can't I deploy a customer SNMP template against a port group?
thanks for your help

Migrate physical adapter to Nexus 1000v's specific uplink port Group

When I run the below script in vmware powercli, the physical adapters get added to N1K's "Unused_Or_Quarantine_Uplink" port group. I got "sys-uplink" PortGroup in my N1K (VSM-DVS-SCALE), and I want the physical adapters to get added to this "sys-uplink".
Issue is Add-VDSwitchPhysicalNetworkAdapter does not have a option to specify which Port-Group the adapter should be added to. Any workarounds to solve this issue. Looks like customers are facing similar issue and moving away from N1k to vmware's dvs (see
https://communities.vmware.com/thread/442897?start=0&tstart=0)
$vmhost = Get-Datacenter Dao | Get-VMHost "192.100.12.16"
$myVDSwitch = Get-VDSwitch -Name "VSM-DVS-SCALE" -Location Dao
$hostsphysicalnic = $vmhost | Get-VMHostNetworkAdapter -name vmnic2,vmnic1
$myVDPortGroup = get-vdportgroup -name $myVDPortGroup -vdswitch $myVDSwitch
Add-VDSwitchPhysicalNetworkAdapter -VMHostNetworkAdapter $hostsPhysicalNic -DistributedSwitch "VSM-DVS-SCALE"

When I run the below script in vmware powercli, the physical adapters get added to N1K's "Unused_Or_Quarantine_Uplink" port group. I got "sys-uplink" PortGroup in my N1K (VSM-DVS-SCALE), and I want the physical adapters to get added to this "sys-uplink".
Issue is Add-VDSwitchPhysicalNetworkAdapter does not have a option to specify which Port-Group the adapter should be added to. Any workarounds to solve this issue. Looks like customers are facing similar issue and moving away from N1k to vmware's dvs (see
https://communities.vmware.com/thread/442897?start=0&tstart=0)
$vmhost = Get-Datacenter Dao | Get-VMHost "192.100.12.16"
$myVDSwitch = Get-VDSwitch -Name "VSM-DVS-SCALE" -Location Dao
$hostsphysicalnic = $vmhost | Get-VMHostNetworkAdapter -name vmnic2,vmnic1
$myVDPortGroup = get-vdportgroup -name $myVDPortGroup -vdswitch $myVDSwitch
Add-VDSwitchPhysicalNetworkAdapter -VMHostNetworkAdapter $hostsPhysicalNic -DistributedSwitch "VSM-DVS-SCALE"

Port Groups in RME 4.3

The new port and module groups for RME have attributes that require data from Campus Manager. The disclaimer states, "NOTE: The attributes that begin with "CM." return data only if CiscoWorks Campus Manager is installed on the CiscoWorks Server."
Does this indicate that RME and CM need to be installed on the same server in a multi-server setup or is something missing for these two apps to communicate?

Yes, Campus and RME must be installed on the same server in order for these attributes to work.

Default ports groups for iptv and iptv control server

is there a default group for iptv and default ports for different types of communication

I was able to take a look at the system here at work:
Under "Preferences" in the Content Manager, the first category of configurable parameters are for Multicast Addresses.
If you keep the default (Global)it uses 224.2.X.Y, and allows you to set the TTL's to set the multicast diameter.
The Administratively Scoped multicast addresses are 239.255.0.0 - 239.255.255.255. You can also set a TTL.
Global SSM addresses are 232.0.0.0-232.255.255.255
Admin Scoped SSM addresses are 239.232.0.0-239.232.255.255
Near the end of that section, you can choose which address range will be the default, and I believe "Global" (224.2.X.Y) is the "default" default.
The only ports listed are for Multicast Announcement (9874) and RTSP (8554) both are UDP.
Good Luck
Scott

Does ACI support a VXLAN Tunnel between Leaf(Leaves) and VMware-vDS, and MS-vSwtich?

Hi Experts,
I have a quick question about Normalized Forwarding of ACI Fabric.
Does ACI support a VXLAN Tunnel between Leaf(Leaves) and VMware-vDS, and MS-vSwtich? Otherwise any plan to provide that function in the future?
If there is no function and plan How is Normalized Forwarding possible with VXLAN headers that are generated by each Hypervisor? Of course I know it's possible for a VM on ESXi to communicate with another VMs on Hper-V without VXLAN but I just focus on Normalized Forwarding between Multi-Hypervisor.
Or If AVSs are implemented on ESXi and Hyper-V repectively, is it possible to make a VXLAN Tunnel between Leaf(Leaves) and AVSs on ESXi and Hyper-V? And what is a example of that usage?
Thanks in advance.
Paul

Hi Paul,
As I understand, ACI Leaf to the VMware-vDS is still vlan so no tunnel for VXLAN. When we integrate Vcenter with the ACI, We define the vlan range for the traffic from VM-ware-vDS to map EPG to a VMware ESXi port group.
For the MS-vSwitch, As It support OpFlex agent could act as VTEP but not part of the fabric. But I am not sure about this.
As AVS is part of the fabric so It will act as a VTEP (VXLAN Tunnel between Leaf(Leaves) and AVSs)
But what is the benefit are you looking? Traffic normalization is still there because Traffic within the fabric is encapsulated as VXLAN. External VLAN/VXLAN/NVGRE tags are mapped at ingress to an internal VXLAN tag.
Note:the VLAN ID has local significance for the leaf node
Regards,
Anser

Port quarantined due to Cmd Failure, Failure applying command channel-group mac-pinning

Hi,
we run an UCS domain with several server, having two FIs. Each blade has 18 vNICs, 9 to Fabric-A and 9 to Fabric-B. Now for some weird reason we get the error for our management vlan (5), which has two dedicated vNICs, inteface x/y has been quarantined... --> failure when enabling PC mac-pinning
sh logging logfile | grep INTER:
2014 May 21 07:28:14 be-egt-sw-p8 %ETH_PORT_CHANNEL-5-PCM_CHANNEL_ID_ASSIGNED: Assigning port channel number 81 for member ports Ethernet3/1
2014 May 21 07:28:14 be-egt-sw-p8 %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/1 has been quarantined due to Cmd Failure
2014 May 21 07:28:15 be-egt-sw-p8 %ETH_PORT_CHANNEL-5-PCM_CHANNEL_ID_ASSIGNED: Assigning port channel number 81 for member ports Ethernet3/10
2014 May 21 07:28:15 be-egt-sw-p8 %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/10 has been quarantined due to Cmd Failure
sh accounting log:
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 ; no switchport trunk allowed vlan (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 ; no switchport mode trunk (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; switchport mode trunk (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; switchport trunk allowed vlan 5 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; channel-group auto mode on mac-pinning (FAILURE)
Wed May 21 07:28:14 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 ; no switchport trunk allowed vlan (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 ; no switchport mode trunk (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; switchport mode trunk (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; switchport trunk allowed vlan 5 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; channel-group auto mode on mac-pinning (FAILURE)
We tried wich port-channel based on cdp information, but same errrors occured. The weird thing is that it only applies to mgmt port-profile...
Can someone help me what I'm doing wrong here... thanks a lot :)
Uplink Config:
port-profile type ethernet ESX_MGMT
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 5
channel-group auto mode on mac-pinning
no shutdown
system vlan 5
state enabled
vEth Config:
port-profile type vethernet VLANname
capability l3control
vmware port-group
switchport mode access
switchport access vlan 5
no shutdown
system vlan 5
max-ports 64
state enabled
Kind regards,
Yan

Hi,
we run an UCS domain with several server, having two FIs. Each blade has 18 vNICs, 9 to Fabric-A and 9 to Fabric-B. Now for some weird reason we get the error for our management vlan (5), which has two dedicated vNICs, inteface x/y has been quarantined... --> failure when enabling PC mac-pinning
sh logging logfile | grep INTER:
2014 May 21 07:28:14 be-egt-sw-p8 %ETH_PORT_CHANNEL-5-PCM_CHANNEL_ID_ASSIGNED: Assigning port channel number 81 for member ports Ethernet3/1
2014 May 21 07:28:14 be-egt-sw-p8 %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/1 has been quarantined due to Cmd Failure
2014 May 21 07:28:15 be-egt-sw-p8 %ETH_PORT_CHANNEL-5-PCM_CHANNEL_ID_ASSIGNED: Assigning port channel number 81 for member ports Ethernet3/10
2014 May 21 07:28:15 be-egt-sw-p8 %PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/10 has been quarantined due to Cmd Failure
sh accounting log:
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 ; no switchport trunk allowed vlan (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14356:admin:configure terminal ; interface Ethernet3/1 ; no switchport mode trunk (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; switchport mode trunk (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; switchport trunk allowed vlan 5 (SUCCESS)
Wed May 21 07:28:14 2014:update:ppm.14364:admin:configure terminal ; interface Ethernet3/1 ; channel-group auto mode on mac-pinning (FAILURE)
Wed May 21 07:28:14 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 ; no switchport trunk allowed vlan (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14379:admin:configure terminal ; interface Ethernet3/10 ; no switchport mode trunk (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; switchport mode trunk (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; switchport trunk allowed vlan 5 (SUCCESS)
Wed May 21 07:28:15 2014:update:ppm.14393:admin:configure terminal ; interface Ethernet3/10 ; channel-group auto mode on mac-pinning (FAILURE)
We tried wich port-channel based on cdp information, but same errrors occured. The weird thing is that it only applies to mgmt port-profile...
Can someone help me what I'm doing wrong here... thanks a lot :)
Uplink Config:
port-profile type ethernet ESX_MGMT
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 5
channel-group auto mode on mac-pinning
no shutdown
system vlan 5
state enabled
vEth Config:
port-profile type vethernet VLANname
capability l3control
vmware port-group
switchport mode access
switchport access vlan 5
no shutdown
system vlan 5
max-ports 64
state enabled
Kind regards,
Yan

Nexus1000v: Mgmt Port on different VLAN than host

I am setting up a pair of Nexus 1000v switches. As per the Cisco
documentation, I have the management port in the system-uplink
port-profile. However, currently, this management port is in the same
production VLAN as most of our servers. I would rather have the
management in an separate VLAN for security and reliability reasons.
Also, as I cannot assign a VLAN to both the system-uplink and the
data-uplink port-group, this means all of the server traffic will be
using the system-uplink port-group. This does not sound logical.
My question is:
1. Does the management port have to be in the same VLAN as the VM Host
server?
2. If is does, what are the implications of putting the management port
on the data-uplink port-group?
3. OR, if (1) is YES, then what do you think about putting the VM Hosts
(ESXI) on a separate VLAN than the virtual servers?
Note: I have been playing with svs domain mode l3. But as I cannot even
ping the gateway, I haven't had much success.

I would say you should seperate it.
One VLAN Management (mabye in ESX Managemt or Switchmanagement VLAN)
One VLAN for Packet & Contrl.
Others for Data (server, user traffic)
Seperate Management ist just for security reasons
The others should be seperated, because the are very important to let the nexus Work, If packets are lost, the hole nexus will get trouble to work.
Additional you should think about QoS if you don't use a seperate NIC for that traffic. I would suggest to use a bundle of NIC's for evetyhing and work with QoS to be High Available.
Thats my point of view after discussion in a nexus training and with a cisco technician.
regards,
Sebastain

C210 ESXI Port Group

Similar Messages

Maybe you are looking for