Cisco VMfex port-profile manager HyperV 2.2 UCS 2012R2

Could not locate the files of instalation for Cisco VMfex Manager of port-profile for Windows Server 2012 R2 Hyper-V. Without it, we were able to use VMFEX/SRIOV vNIC on our UCS system. UCS Firmware is 2.2

W2012 R2 does not appear on the support matrix

http://www.Cisco.com/c/dam/en/us/TD/docs/unified_computing/UCS/interoperability/matrix/r_hcl_B_rel2-21.PDF

Tags: Cisco DataCenter

Similar Questions

  • VMFEX / ports VMK / QoS

    When you use (non-performing) vmfex how would you define the ports for vmotion vmk, nfs, etc. and are also using vmfex...? Is it just a case of creating a profile of port for vmotion etc, then creating a vmotion interface and attach it to the port with vcentre group?

    In addition, using this mode where you attached the qos policy? And finally, when you use UCS qos is policy applied to the FIs, as well as the adapter or just the adapter?

    Concerning

    Hello

    Yes, you can use VM - FEX vmkernel ports for vmotion, NFS trafffic. You can use existing port profile or create separate port profile and associate with the vmk appropriate interfaces.

    Each port-profile can have a QoS policy. CoS marking is done according to the QoS configuration and corresponding traffic is placed in queues in FI.

    http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/vm_fex/VMware/GUI/config_guide/GUI_VMware_VM-FEX_UCSM_Configuration_Guide_chapter7.html

    More info

    http://www.Cisco.com/en/us/NetSol/ns1124/index.html

    Padma

  • Remove the ' system VLAN "Nexus 1000V port-profile

    We have a Dell M1000e blade chassis with a number of Server Blade M605 ESXi 5.0 using the Nexus 1000V for networking.  We use 10 G Ethernet fabric B and C, for a total of 4 10 cards per server.  We do not use the NIC 1 G on A fabric.  We currently use a NIC of B and C fabrics for the traffic of the virtual machine and the other card NETWORK in each fabric for traffic management/vMotion/iSCSI VM.  We currently use iSCSI EqualLogic PS6010 arrays and have two configuration of port-groups with iSCSI connections (a physical NIC vmnic3 and a vmnic5 of NIC physical).

    We have added a unified EMC VNX 5300 table at our facility and we have configured three VLANs extra on our network - two for iSCSI and other for NFS configuration.  We've added added vEthernet port-profiles for the VLAN of new three, but when we added the new vmk # ports on some of the ESXi servers, they couldn't ping anything.   We got a deal of TAC with Cisco and it was determined that only a single port group with iSCSI connections can be bound to a physical uplink both.

    We decided that we would temporarily add the VLAN again to the list of VLANS allowed on the ports of trunk of physical switch currently only used for the traffic of the VM. We need to delete the new VLAN port ethernet-profile current but facing a problem.

    The Nexus 1000V current profile port that must be changed is:

    The DenverMgmtSanUplinks type ethernet port profile

    VMware-port group

    switchport mode trunk

    switchport trunk allowed vlan 2308-2306, 2311-2315

    passive auto channel-group mode

    no downtime

    System vlan 2308-2306, 2311-2315

    MGMT RISING SAN description

    enabled state

    We must remove the list ' system vlan "vlan 2313-2315 in order to remove them from the list" trunk switchport allowed vlan.

    However, when we try to do, we get an error about the port-profile is currently in use:

    vsm21a # conf t

    Enter configuration commands, one per line.  End with CNTL/Z.

    vsm21a (config) #-port ethernet type DenverMgmtSanUplinks profile

    vsm21a(config-port-Prof) # system vlan 2308-2306, 2311-2312

    ERROR: Cannot delete system VLAN, port-profile in use by Po2 interface

    We have 6 ESXi servers connected to this Nexus 1000V.  Originally they were MEC 3-8 but apparently when we made an update of the firmware, they had re - VEM 9-14 and the old 6 VEM and associates of the Channel ports, are orphans.

    By example, if we look at the port-channel 2 more in detail, we see orphans 3 VEM-related sound and it has no ports associated with it:

    Sho vsm21a(config-port-Prof) # run int port-channel 2

    ! Command: show running-config interface port-canal2

    ! Time: Thu Apr 26 18:59:06 2013

    version 4.2 (1) SV2 (1.1)

    interface port-canal2

    inherit port-profile DenverMgmtSanUplinks

    MEC 3

    vsm21a(config-port-Prof) # sho int port-channel 2

    port-canal2 is stopped (no operational member)

    Material: Port Channel, address: 0000.0000.0000 (bia 0000.0000.0000)

    MTU 1500 bytes, BW 100000 Kbit, DLY 10 usec,

    reliability 255/255, txload 1/255, rxload 1/255

    Encapsulation ARPA

    Port mode is trunk

    Auto-duplex, 10 Gb/s

    Lighthouse is off

    Input stream control is turned off, output flow control is disabled

    Switchport monitor is off

    Members in this channel: Eth3/4, Eth3/6

    Final cleaning of "show interface" counters never

    102 interface resets

    We can probably remove the port-channel 2, but assumed that the error message on the port-profile in use is cascading on the other channel ports.  We can delete the other port-channel 4,6,8,10 orphans and 12 as they are associated with the orphan VEM, but we expect wil then also get errors on the channels of port 13,15,17,19,21 and 23 who are associated with the MEC assets.

    We are looking to see if there is an easy way to fix this on the MSM, or if we need to break one of the rising physical on each server, connect to a vSS or vDS and migrate all off us so the Nexus 1000V vmkernel ports can clean number VLAN.

    You will not be able to remove the VLAN from the system until nothing by using this port-profile. We are very protective of any vlan that is designated on the system command line vlan.

    You must clean the canals of old port and the old MEC. You can safely do 'no port-channel int' and "no vem" on devices which are no longer used.

    What you can do is to create a new port to link rising profile with the settings you want. Then invert the interfaces in the new port-profile. It is generally easier to create a new one then to attempt to clean and the old port-profile with control panel vlan.

    I would like to make the following steps.

    Create a new port-profile with the settings you want to

    Put the host in if possible maintenance mode

    Pick a network of former N1Kv eth port-profile card

    Add the network adapter in the new N1Kv eth port-profile

    Pull on the second NIC on the old port-profile of eth

    Add the second network card in the new port-profile

    You will get some duplicated packages, error messages, but it should work.

    The other option is to remove the N1Kv host and add it by using the new profile port eth.

    Another option is to leave it. Unless it's really bother you no VMs will be able to use these ports-profile unless you create a port veth profile on this VLAN.

    Louis

  • Profile Manager - failed to install the remote access profile in the domain environment & multi-Active Network Directory

    Hi all

    I am a COMPUTER administrator for a college and I am trying to fix what seems to be the last hurdle in getting the Profile Manager works correctly.

    I worked for a while now trying to get the Profile Manager capable of pushing the device and profiles for Mac in our group network environment. I was able to operate intermittently, but not often. Most of the time I'm unable to install the remote management profile.

    When you try to install the remote management profile, I give myself one of the two errors-

    The first error is:

    The Installation of the profile failed.

    The «TeleManagement (com.apple.config. » profile (Server.FQDN.mdm:GUID) "could not be installed because of an unexpected error < MDMResponseStatus:500 >

    (Obviously server.fqdn and GUID are placeholders for their actual values)

    The second mistake is:

    The Installation of the profile failed.

    Failed to contact the Protocol SCEP server to ""http://server.fqdn: 1640/CEP / "."

    The server Mac OS X 10.11.4 works

    OS X Server is version 5.1

    Client Mac is for most running 10.10.4

    Here's a quick run down on the environment and the steps I have already taken to solve the problem.

    • The network is an Active Directory with several networks multi-domain environment. I mainly work with two different networks, each associated with one of the two areas.
    • The Mac server hosting the Profile Manager is a Mac Pro. The two network cards is used, each on one of the two networks. The Mac server is joined to the domain in the primary forest.
    • I opened all the ports and IP ranges for Apple's Push Notification service for two on our firewall and tested networks between the two networks to ensure that the AFN is accessible.
    • I created a static DNS entry for the server in the DNS zone for the main domain. I also have a separate DNS zone for the DNS record for the interface on the secondary network. I also confirmed that Macs see the correct IP address of the Mac server for their network.
    • I tried to change the settings for network access for the Profile Manager. The first error seems to happen when the Profile Manager are restricted to the network the Mac client is not connected. This same error also occurs if I open Manager profile access to "all networks".
    • I have experiemented with the different certificate types. In general, I use the self-signed certificates that are generated automatically. In this scenario, I install the profile Trust first (which works seamlessly regardless of network or domain). I also tried to use a certificate for Code signing signed with our own CA to sign the profile of remote management. The same errors will occur no matter what certificates are used.
    • The second error occurs when the access profile manager is limited to the same network that is connected to the Mac client
    • I ran Wireshark captures on several client computers, as well as on the Mac server interfaces and haven't seen any traffic blocked or rejected that seemed related to the Profile Manager
    • I've deleted and rebuilt my OD master
    • I also scoured newspapers for clues Profile Manager and haven't found much
    • In addition, I have also studied the problem and error codes/etc widely and have not found a lot of useful information
    • I don't know there are any other troubleshooting steps I took as well, but I've been question bout this for awhile and I don't remember everyone.

    That's a strange thing - I had it working for Mac on the main network and the domain. However, I discovered that the Mac on the secondary network and the field was unable to download the profile of remote management. This is when I started to change the Profile Manager, access network, which eventually introduce the problem on Macs connected to the primary/field of experimentation network. Change access return settings in Profile Manager does not restore functionality for pimps who worked.

    Another thing odd in this test scenario all - Mac on the network high school/area would not install remote profile unless management I temporarily moved it to the main network (I do not untie / reassign to one the main domain on these Macs) I could get the profile of remote management to install and then pushing profiles has worked. Even more strange, it's the Mac that I had to move temporarily secondary network to the main network to allow remote management profile install only works always as long as the Profile Manager are restricted to the secondary network and 'the Mac'. However, Macs in the same room, on the same network in the same field, using the exact image even get the errors described above.

    The only thing I have not yet done is delete/reconstruction Profile Manager. I would really like to avoid this if possible. Solutions that involve something like Casper or other software integration AD for Macs are also a non-starter.

    I'm happy to elaborate if necessary. I appreciate the help.

    Okay, I think I can find the root cause.

    Before this discovery, I had completely rebuilt Profile Manager. Now, I managed by pushing the management profile remote for Mac in the two fields/networks. However, many of them still refuse to install remote management profile.

    Macs who encounter the problem are all were imaged using NetRestore using an image captured from an another similar iMac. IMac even that was used to build the image has now been reassigned in a test of Mac. I found that when you attempt to register one of the Mac who had received this image it shows already as "registered" when you go to "mydevices" on my Mac server. I also noticed that they all have the serial number of the test Mac when viewing their "register". Among the issues of Macs, I activated the lock of the device from the page "mydevices" for the so-called problematic Mac registered (showing the serial number of the iMac used to create the image) and it locked the iMac used to create the image - not the Mac issue.

    This tells me that the CID (or Mac equivalent) is set on the Mac CID used to create the image for all of the Mac said image was deployed to. If it's a Windows box I have a sysprep prior to deployment or could perform a rearm after the fact. I am unaware of how to perform similar functions in OS X.

    I tested also since on some Macs that do not have this image, and they are able to register and install the profile of Managing remotely with success.

    If anyone has any suggestions on how to reset the CID (the computer ID) under OS X, I'd appreciate it. Thank you.

  • profilemanger 404 not found (Profile Manager)

    Today, we finally managed to activate our account VPP! The token in charge and was able to access the Profile Manager Page for a short time, but now do not have access to the Profile Manager page using any browser.

    I ran a listening thingy [sudo lsof Pei - n - PICT - sTCP: LISTEN | grep httpd] and its throwing up a couple of odd port 34543 and 34580 when I thought it is recommended to use: 80

    I rebooted the server [hardware] and restarted the server [App] and earlier it anyway displays a message saying that the Profile Manager was not yet ready, please try again later, then he returned to the Apache page shown in the image above.

    If anyone has had any dealing with this, please let me know as I tried to figure it out for the last 3 hours!

    All files appear to be in the right directory:

    /Server/Library/Web/data/sites/default/default.html.en (alias)

    Server.app/Contents/ServerRoot/usr/share/web/locales/en.lproj/profilemanager.htm l

    So I guess it's the good ol' ' Open Source ApacheWare which is to blame...

    I'll look forward to reading your contributions.

    You tried to access it via localhost on the server?

  • Profile Manager - will not communicate with devices

    Hello

    The profile manager worked until January 26, but he has not worked since. I tried to re-adding devices (it won't register their), and pushing the settings does not work either. I did 2 full reset of the particles, but the two did nothing to solve the problem.

    I am on a network with an AirPort Extreme 192.168. 80, 1640, 5223, 2195-2196 ports are open.

    Thanks in advance!

    David

    Check expired certificates and see if the console connects - available through Console.app - show anything relevant to the Profile Manager and related errors.

  • Quest Desktop Virtualization (vWorkspace) user profile management issues

    Hi, I work on the configuration of the user profile with (Win 7 VDI) virtual desktop management service following the guide of vworkspace administrator 7.6 and any other docs, I found on quest.com and I have a problem with it, there is nothing in the file metaprofiles\global. It doesn't seem to work. I have a file (vdi-storage1) server with action c:\vdiuserprofiles\ created folder where the profile will be stored. I also installed the role of vWorkspace on this file server user profile management and the service is running. 5206 port is open. All the virtual desktops have pntools installed with all the options and I can see that the user profile agent is running. I can reach the storage server (vdi-storage1) using telnet on port 5206 and ping. I even gave domain user full ntfs permissions to the c:\vdiuserprofiles folder, but I don't think that this is necessary.

    -In the Managment Console > resources > (right click 'properties') user profiles

    -General: Compression: low, log level: detailed, Refresh: 5 minutes

    -Storage servers: server name: vdi-storage1, Basic file: c:\vdiuserprofiles\metaprofiles, Folder Global: Global, The TCP Port: 5206

    -Silos: name: VirtualDesktopSilo, storage for the user profile server: vdi-storage1

    -Properties VirtualDesktopSilo

    -Members: name: desktop Windows 7, Type: computer group

    - Storage for the user profile server: vdi-storage1

    - Automatic backup: 30 minutes

    The MC did create the folder metaprofiles\global automatically when I applied the settings. I use supplied with vworkspace default registry keys, and I attributed them to the domain users group. I recorded several times power on and off on the virtual desktop. I noticed 5 second delay on the virtual machine after that I typed the information identification, and before she really connects me since I activated the profile management. A I forgot something or is misconfigured it?

    OK, after having received assistance from Dell (Quest) suppor, t the issue happens to be with me remoting (via RDP) for VM directly instead of by the intermediary of the broker vWorkspace, therefore the profile could not be created because I had not the closed valid session so it never created the profile. Once I've tested it using vWorkspace connector this worked.

  • UCSM VM - FEX create when port-profile name cannot be used. (dot)

    UCSM q with 6120XP 2.01

    I can create using port-profile. (dot) for example "VLAN30 - 192.168.1", but it causes a warning message (pictured below)

    so I try to change the name of VLAN30-192-168-1 it can work very well

    My question is can I use. (point) in my profile of the port name?

    PS. I checked the manual of cisco

    This name can be between 1 and 31 ASCII alphanumeric. You can not

    Use spaces or other special characters as - (dash) _

    (underscore character). (period), and: (colon), and you cannot change this name

    Once the object has been saved.

    Thank you

    We have logged a bug for this CSCtw50228 - thanks to Yasmin!

    Our developers have confirmed that while other objects have name validation, virtual computer Port profiles are not, who raises the error you see because NXOS cannot process ".» (periods).  The names of service profiles are another matter that NXOS has no knowledge of these objects.

    The solution is to avoid using periods in the VM profile names.  Use a dashboard.

    Kind regards

    Robert

  • How to export the list of devices in the Profile Manager?

    Hello

    is there a way to export the list of devices in the Profile Manager on a mini mac running OS Server 5.3?

    Thank you

    How to export data from device in the Profile Manager

    How to export a list of devices and their info?

  • Run Profile Manager

    Hello

    I found the article how to register a certificate using Windows CA.

    as I found the article presents the Profile Manager in OS X 10.11.

    But how can I run it on OS X 10.11?

    Thank you!

    Isn't the profile one manager part of the OS X Server?

    https://www.Apple.com/OSX/Server/features/#Profile-Manager

  • Firefox does not start, the Profile Manager is not available

    Firefox worked, then update it does not start. I tried all the fixes; However, the Profile Manager is not accessible or even present in the execution file. I unintalled and reinstalled several times, but I still can't get it to work. There is no Windows or Norton firewall block so I do not understand. What can I do? I want to use Firefox because it's the best browser; but now I'm forced to use Oscar. It's not terrible, but I prefer the features I've had with Firefox

    I had upgraded to the latest version; but the thought of demotion to the version which worked perfectly. In the end, I had to defrag, do a registry clean and optimization of performance of PC, but for the upgrade launched. So, I'm happy to say that I reply to this post with my Firefox browser. Thank you very much for your help. If all goes well, I won't have problems.
    DoubleD52

  • I can not get to start Profile Manager.

    I go to ~/.thunderbird and run

       ./thunderbird -ProfileManager
    

    Instead of giving me a Profile Manager window it gives me just an instance of the envelope to thunderbird.

    I have a problem with the email thunderbird at the moment and it was suggested to me that I change my
    Profile (using the command above).

    I'm running (the very older) Fedora 17.

    In fact I realized the problem: the instructions that I was told to go in the profile directory

       ~/.thunderbird/********.default
    

    and run. / thunderbird - ProfileManager.

    But there was no thunderbird executable in this directory! So I went to a directory in which there * was * a thunderbird executable and issued the command. With the unsatisfactory results tht I described.

    I *finally* found that if I went to /.thunderbird/********.default
    and issued the command "thunderbird -ProfileManager" (*not* preceded   by "./" --- so that I got the "system" thunderbird command) then the  result was as desired.
    

    So my problem is solved. But he had nothing to do with letting thunderbird running.

  • When the Profile Manager stores data profiles created?

    I have several profiles of Firefox that I created with the Profile Manager, but I find no where the Profile Manager stores data for profiles created because even if I delete all the firefox location of C:\Users\user\AppData\Local\Mozilla user data files and all the data in the registry though Firefox I start the Profile Manager still lists all created profiles.

    Then, where the data for profiles created is stored?

    Hello, these data are stored in subfolders of \Mozilla\Firefox\Profiles\ C:\Users\user\AppData\Roaming- profiles - where Firefox stores your bookmarks, passwords and other user data

  • Profile Manager fot portable applications

    I need to import my backup in my portable thunderbird and I read in the documentation that I have use the "Profile Manager" or edit the "profiles.ini". I can't find them both.

    This line: ["L:\PortableApps\ThunderbirdPortable\ThunderbirdPortable.exe" - p] just open the usual program

    How may I access the profile with the mobile application manager?

    Thank you

    OK I have neen searching around on portableapps.com for Thunderbird.

    You see you do not actually use Mozilla Thunderbird desktop, you use a product that has been modified by a third party and really should ask in this forum of products.

    http://PortableApps.com/node/23603
    The Profile Manager is not portable. It is just not supported by Thunderbird Portable because it will break things.

    http://PortableApps.com/node/11191

    http://PortableApps.com/support/thunderbird_portable#local_profile

  • I created my firefox shortcut to go directly to the Profile Manager. I got it for years. All of a sudden it has stopped working

    Hello

    I can't get my firefox shortcuts to go directly on the Profile Manager. I don't know why. I know I have the target correctly configured in the properties, but he still won't be going to the nursery to profile. Help, please.

    Here is what is the location of the target in the properties:

    "C:\Program Files (x 86) \Mozilla"-profilemanger

    I have not had a problem yet. Did that for about two years. This most recent update erased the "profilemanager" - no-remote-p. I added it waala and back in! Out of service again.

    But duly noted. Thanks for the tips.

Maybe you are looking for