System vlan an port-profile

I have a profile uplink which include a system vlan of 50, 60, 220
thne i also have a port profile for vlan 50 and 60
but when i connect a vm to this port group, i do not get any connection.
however other vlans that are not set as system vlan on the uplink are working fine on their own port group.
any idea why?

here is an example from my configs I use.
port-profile type ethernet system-uplink-03
vmware port-group
switchport mode trunk
switchport trunk native vlan 1034
switchport trunk allowed vlan 1031-1034
channel-group auto mode on mac-pinning
no shutdown
system vlan 1031-1033
description Development system profile for critical ports and vm traffic
state enabled
1031-1034 are vmware mgmt, ip storage and vmotion in this instance vcenter was in a different environment I have I think about 12 different system uplink port profiles
here is a port-profile:
port-profile type vethernet 03-development-vmsc
capability l3control
vmware port-group
switchport mode access
switchport access vlan 1031
no shutdown
system vlan 1031
max-ports 32
description 03 Development ESXi Management
state enabled
hope this helps.

Similar Messages

The Use of Port Profiles

My understanding of the uses of port profiles includes the implementation of Nexus 1K/5K etc. and the implementation of VM-FEX correct? These port profiles are then pushed to vCenter to be used by the VM's offloading the networking portion back to UCSM and not the VM admin... Is this correct?

N1k/N5k/UCS VM-FEX port-profiles are used by both the network & VMware administrator. The network administrator creates the port-profile & assigns properties (VLAN, QoS, ACL, etc) - available features differ on each product with N1k offering the most features. After the the port-profile is create it is automatically advertised in vCenter. The vCenter admin then assigns port-profiles to VM interfaces and vmnics. This essentially separates the network & system admin roles so that each person concentrates on their area of expertise.
Port-profiles are also available on standalone N5k/N7k to be used at interface templates when not integrating with VMware.

Only system vlans forward traffic on 1000v

I am trying to migrate to a Nexus 1000v vDS but only VM's in the system VLAN can forward traffic. I do not want to make my voice vlan a system VLAN but that is the only way I can get a VM in that VLAN to work properly. I have a host with its vmk in the L3Control port group. From the VSM, a show module shows the VEM 3 with an "ok" status. I currently only have 1 NIC under the vDS control. My VM's using the VM_Network port group work fine and can forward traffic normally. When I put a VM in the Voice_Network port group I lose communication with it. If I add vlan 5 as a system vlan to my Uplink port profile then the VM's in the Voice_Network work properly. I thought you shouldn't create system vlans for each vlan and only use it for critical management functions so I would rather not make it a system vlan. Below is my n1k config. The upstream switch is a 2960X with the "switchport mode trunk" command. Am I missing something that is not allowing VLAN 5 to communicate over the Uplink port profile?
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 vethernet VM_Network
vmware port-group
switchport mode access
switchport access vlan 1
no shutdown
system vlan 1
max-ports 256
description VLAN 1
state enabled
port-profile type vethernet L3-control-vlan1
capability l3control
vmware port-group L3Control
switchport mode access
switchport access vlan 1
no shutdown
system vlan 1
state enabled
port-profile type ethernet iSCSI-50
vmware port-group "iSCSI Uplink"
switchport mode trunk
switchport trunk allowed vlan 50
switchport trunk native vlan 50
mtu 9000
channel-group auto mode active
no shutdown
system vlan 50
state enabled
port-profile type vethernet iSCSI-A
vmware port-group
switchport access vlan 50
switchport mode access
capability iscsi-multipath
no shutdown
system vlan 50
state enabled
port-profile type vethernet iSCSI-B
vmware port-group
switchport access vlan 50
switchport mode access
capability iscsi-multipath
no shutdown
system vlan 50
state enabled
port-profile type ethernet Uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1,5
no shutdown
system vlan 1
state enabled
port-profile type vethernet Voice_Network
vmware port-group
switchport mode access
switchport access vlan 5
no shutdown
max-ports 256
description VLAN 5
state enabled

Below is the output you requested. Thank you.
~ # vemcmd show card
Card UUID type 2: 4c4c4544-004c-5110-804a-b9c04f564831
Card name: synergvm5
Switch name: synergVSM
Switch alias: DvsPortset-0
Switch uuid: 7d e9 0d 50 b3 3b 25 47-64 14 61 c0 3f c0 7b d9
Card domain: 4094
Card slot: 3
VEM Tunnel Mode: L3 Mode
L3 Ctrl Index: 49
L3 Ctrl VLAN: 1
VEM Control (AIPC) MAC: 00:02:3d:1f:fe:02
VEM Packet (Inband) MAC: 00:02:3d:2f:fe:02
VEM Control Agent (DPA) MAC: 00:02:3d:4f:fe:02
VEM SPAN MAC: 00:02:3d:3f:fe:02
Primary VSM MAC : 00:50:56:aa:70:b9
Primary VSM PKT MAC : 00:50:56:aa:70:bb
Primary VSM MGMT MAC : 00:50:56:aa:70:ba
Standby VSM CTRL MAC : 00:50:56:aa:70:b6
Management IPv4 address: 172.30.2.64
Management IPv6 address: 0000:0000:0000:0000:0000:0000:0000:0000
Primary L3 Control IPv4 address: 172.30.100.1
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: 1
Card packet VLAN: 1
Control type multicast: No
Card Headless Mode : No
       Processors: 16
Processor Cores: 8
Processor Sockets: 2
Kernel Memory:   62904468
Port link-up delay: 5s
Global UUFB: DISABLED
Heartbeat Set: True
PC LB Algo: source-mac
Datapath portset event in progress : no
Licensed: Yes
~ # vemcmd show port
LTL   VSM Port Admin Link State PC-LTL SGID Vem Port Type
   24     Eth3/8     UP   UP    FWD       0          vmnic7
   49      Veth1     UP   UP    FWD       0            vmk1
   50      Veth2     UP   UP    FWD       0        XP-Voice.eth0
   51      Veth3     UP   UP    FWD       0        synergPresence.eth0
~ # vemcmd show port vlans
                          Native VLAN   Allowed
LTL   VSM Port Mode    VLAN    State* Vlans
   24     Eth3/8   T          1   FWD    1
   49      Veth1   A          1   FWD    1
   50      Veth2   A          1   FWD    1
   51      Veth3   A          5   FWD    5
* VLAN State: VLAN State represents the state of allowed vlans.
~ # vemcmd show bd
Number of valid BDS: 10
BD 1, vdc 1, vlan 1, swbd 1, 5 ports, ""
Portlist:
BD 2, vdc 1, vlan 3972, swbd 3972, 0 ports, ""
Portlist:
BD 3, vdc 1, vlan 3970, swbd 3970, 0 ports, ""
Portlist:
BD 4, vdc 1, vlan 3969, swbd 3969, 2 ports, ""
Portlist:
      8
      9
BD 5, vdc 1, vlan 3968, swbd 3968, 3 ports, ""
Portlist:
      1 inban
      5 inband port securit
     11
BD 6, vdc 1, vlan 3971, swbd 3971, 2 ports, ""
Portlist:
     14
     15
BD 7, vdc 1, vlan 5, swbd 5, 1 ports, ""
Portlist:
     51 synergPresence.eth0
BD 8, vdc 1, vlan 50, swbd 50, 0 ports, ""
Portlist:
BD 9, vdc 1, vlan 77, swbd 77, 0 ports, ""
Portlist:
BD 10, vdc 1, vlan 199, swbd 199, 0 ports, ""
Portlist:
~ #

System VLANs for AD, vCentre...

Hi All,
In the event that my entire data centre were to shut-down, is it recommended that the VLANs for AD, vCentre, vCentre DB be configured as System VLANs so that when everything powers up the VEM modules can actually communicate with these systems in order to get their configs? I am aware that the system vlans pretty much negate any security applied to them however was looking to see the best practice.
thanks,

Yeah it wouldn't be a bad idea. Just make sure to add the system vlan to the eth and veth port-profiles.
And remember you can only have 32 port-profiles with the system vlan command in them.
Also understand that when the VSM is not available to program the VEMs and a system vlan is present on the port-profiles that it is only basic connectivity that is allowed. No higher level features like ACLs or QOS will be working.
Let us know if you need more classification. You can also play with the concept if you want by building a small lab environment. The great thing about the N1KV is it does work on a nested ESXi environment so you can build an entire lab on one host.
louis

Input packet drops on uplink port-profile

Hi,
I'm using Nexus 1000v and vSphere 5.1;
I just migrated some physical servers to VM, and I have some weird reporting issues;
Just to make sure it wasn't a network issue they asked me to verify if anything was overlooked on the Nexus side of things;
Everything checked out, but I'm seeing a lot of input packet drops on the physical ports of the system uplink port-profile; I doubled checked the configs on the VSM and the Catalyst stack and all is configured properly;
should I be concerned about these Input packet drops that I'm seeing on the VSM on the physical interfaces of my uplink port-profile? If so, could it be the NICS in the ESX host that could be the issue?
Any feed back would be appreciated;
Thanks.

I have the same symptomps on 3 different Nexus 1000v. All 3 run the same version - 4.2(1)SV2(1.1) VMware is 5.0 sp1 and the hardware for ESXi hosts is more or less the same (At least server blade model and CNA).
We have tried to use vempkt to capture traffic but no traffic is captured if we filter on drops even though the counter on the port-channel and member Ethernet interfaces increase. On the hosts we tried vempkt we see about 20 drops per second. Here is some info. I have removed some irrellevant stuff.
NRK-VSM-001# show int po 14
port-channel14 is up
Members in this channel: Eth6/3, Eth6/4
6172 input packet drops <- Increases
NRK-VSM-001# show mod 6
Mod Sw                  Hw
6    4.2(1)SV2(1.1)      VMware ESXi 5.0.0 Releasebuild-1024429 (3.0)
Mod Server-IP        Server-UUID                           Server-Name
6    10.16.1.12       4c4c4544-0034-3010-8036-b4c04f33354a nrk-vi01-h07.nt.se
FROM The ESXi
~ # vemcmd show port
LTL   VSM Port Admin Link State PC-LTL SGID Vem Port Type
   19     Eth6/3     UP   UP    F/B*    305     0    vmnic2
   20     Eth6/4     UP   UP    F/B*    305     0    vmnic3
~ # vempkt show capture info
Stage : Drop
     LTL : 305
    VLAN : Unspecified
    Filter : Unspecified
Even if we let the capture run for several minutes we see no drops. I set it to capture 31 packets.
~ # vempkt show info
                 Enabled : Yes
    Total Packet Entries : 0       <- Never increases even if the capture is running filtered like above
Wrapped Packet Entries : 0
     Lost Packet Entries : 0
Skipped Packet Entries : 560145
Available Packet Entries : 14169
     Packet Capture Size : 88
     Packet Capture Mode : Un Reliable
Stop After Packet Entry : 31
In our case, could the input drops depend on that we allow vlans from the upstream hardware switch to the VEM that do not exist on the N1000v and that this is the reason we can not capture the dropped packets?
Any ideas?
PS: We see drops on uplinks on all VEMs

Nexus 1000V - port-profile for VSM and VEM on same host

Hello,
I'm trying to run the VSM and VEM on the same host. At first I connected the VSM to the vSwitch. This works fine. Then I tried to move the VSM behind its own VEM.
I have 3 different VLANs for management, control and packet traffic. Is it possible to connect the three VSM interfaces (management, control and packet) to only one port-profile, in which these three different VLANs are configured in a trunk? Or do I have to configure for each interface a separate port-profile, if I am using three different VLANs?
Thanks
Tobias

Hello,
The VSM does not emit VLAN-tagged frames. Therefore, its ports need to be configured in access mode. If your Control and Packet VLANs are the same, you could use the same port profile for both.
Please make sure that the access VLAN is a system VLAN for all three ports.
On a related note, if the VSM's storage is on NFS or iSCSI, the storage vmknic needs a system port profile as well. More info at:
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/getting_started/configuration/guide/n1000v_gsg_5vsm_behind_vem.html

System VLAN's on n1000v

Hi all
when deploying the VSM on a Standard Switch, is it a requirement to include System VLAN's for my the packet and control VLAN's in the Port-Profiles on the dvs?
Many thanks

Correct. You only want system VLANs on the VLANs that are needed to bootstrap the 1000v.
The normal port-profiles that would be used with your VMs typically don't require a system VLAN.
In fact, if you enable a system VLAN on an interface that is going to implement access lists or QoS and there is a problem programming the interface, the port will still forward on that system VLAN, but none of the access lists or QoS settings will be in place.

Physical computer profile "Error 21505" setting management vNic port profile

Hi
Versions: WS2012R2, VMM 2012R2 CU4.
I am creating a Physical computer profile for bare metal deployment of hosts that will eventually form a Hyper-V cluster. I have 4 pNics and have configured 2 pNics as a switch for the VMs (guest traffic). The last two pNics are form a logical
switch with three vNics for host comms (management, heartbeat and Live Migration). The problem I am facing is that when I set the port classification for the management vNic to "Host management" the job returns the following
error:
Error 21505
The specified network adapter profile cannot be removed because it is associated with another network adapter profile as a transient management network adapter.
Recommended Action
To remove this network adapter profile, first remove the associated network adapter profile.
As indicated by the error I do have a pNic set as a transient management network adapter, and this has an uplink port profile set (as it is used to create the switch required for host comms). I don't get why this isn't working and I can't find anything
online regarding the error. Does anyone have any ideas on how to get this to work?
I should mention that I created the (almost) excact profile pre CU4 and this produced no error in the jods view.
/Trond

Hi Sir,
>>I should mention that I created the (almost) excact profile pre CU4 and this produced no error in the jods view.
Please try to keep it up-to-date .
The latest UR is 5 :
http://blogs.technet.com/b/scvmm/archive/2013/04/10/update-rollup-5-for-system-center-2012-vmm-2012-fixes.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

SCVMM2012r2 UR3 : Even with no Virtual switch assigned, an uplink port profile remains

Hi,
What I'm tryng to do, is to unassign an uplink set on my host, set to the wrong NIC (actually, on 3 NIC, event if I specified 2 when I added the logical switch...).
To proceed, I deleted the Logical Switch assigned in the host properties on Virtual Switches tab.
On my host, the teaming has been deleted, but unfortunately, on one of my NIC, the subnet set in my Logical Network subsit in "Logical Network Connectivity" and is greyed out.
It's said "The subnet an VLAN information is set by an uplink port profile set 'tVMNet' associated to this host an cannot be changed here".
But, if I removed the virtual switch, how can it be?
Thanks for any advice, I'm stuck

Hi all,
I did finaly remove the cluster from SCVMM and added it back, and it's working now. No more ghost config remaining.
I'm working on SCVMM from 3 days now, and I'm really not sure that's the easy to use tool we need to manage our small private cloud... It's buggy, slow, oposite of ergonomic and far too much cloud provider oriented...

Nexus 6004: Question about port-profile type port-channel

I'm setting up a new deployment of Nexus 6004 switches and want to utilize port-profiles as much as possible to simplify management down the road.
All uplinks to other switches, routers and firewalls will be connected using VPC:s. On the port-channels (vpc) the only thing that will change over time is the allowed vlans.
It seems that port-profiles of the type port-channel does not behave in the same way as those with type ethernet, at least not when adding vlans.
If I modify the port-profile using "switchport trunk allowed vlan add XXX" it will delete the previous config and only retain "switchport trunk allowed vlan add XXX", and not merge it with the previous config as is expected.
Question: Is this a bug or is it working as intended?
RH_N6K4_01(config-sync)# switch-profile rh
Switch-Profile started, Profile ID is 1
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan 3
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
assigned interfaces:
===================================
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan add 84
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
assigned interfaces:
Expected behavior here would be "switchport trunk allowed vlan 3,84". This only occurs when using "port-profile type port-channel" not when using "port-profile type ethernet"

<> is template syntax and is generally the type of object a container holds.. So it is defining that the MSGQUEUE type is a deque holding struct_buffer*'s.

No Service for System SAPECC(Sender Port), Client800(R/3 system client 800)

Hi friends,
I am new to XI/PI I am working with IDOC to Flat file scenario I am facing the folllowing error.
No Service for System SAPECC(Sender Port), Client800(R/3 system client 800) in integration Directory.
can any one tell what was the reason for this error.
Thanks in Advance,
Ravi Yasoda.

Hi Ravi,
Have you imported the Business System in Integration Directory?
Check whether you see the logical system name in adapter specific identifiers or not...
Also check from integration directory that cache notification was done and also check SXI_CACHE in the abap stack.
See this thread...
No service for system SAP***, client 001 in Integration Directory
Please go through below content from sap note for your issue...
Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc,the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the
type (business-system/business-service):
Business system
-> Activities in the System Landscape Directory (SLD)(Create technical
system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client. For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the
"Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with Transaction SLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical
system under "Objects"->"Adapter-specific identifiers". Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
-> Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD. In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific
identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
Regds,
Pinangshuk.

Is it better to use router port versus vlan member port?

Hi CSC,
This is more of a philosophical or "best practices" question.
I have a Cisco 3550 at the home office. Connected to the 3550 is a number of branch offices by way of T1 circuits or VDSL modems. They all come to the home office, where we have a central internet connection and server farm for our entire organization.
Except for one special case branch office, we don't forsee the need for appearances of the home office vlan at the branch office sites. In that case, we bring it into a trunk port at the home office, and at the special case branch office we have a dell 3024 switch and tag some ports as vlan 18 (the home office) or vlan 27 (the special case branch office).
We also do not forsee a need for the vlan from one branch office to appear at another branch office.
They are all (except for the special case mentioned above) currently configured something like this:
interface FastEthernet0/1
description home office
switchport access vlan 18
switchport mode access
interface FastEthernet0/2
description t1 to branch office 1
switchport access vlan 19
switchport mode access
interface Vlan18
description subnet for home office
ip address 192.168.18.1 255.255.255.0
interface Vlan19
description subnet for branch office 1
ip address 192.168.19.1 255.255.255.0
Is it better, in terms of reduced network complexity or performance on my 3550, to do something like this instead?
That is, to make the interfaces router ports as opposed to vlan member ports?
Of course, if we ever DID need to have appearances of the home office vlan at branch office sites, or appearances of one branch office's vlan at another branch office, we would lose that flexibility.
interface FastEthernet0/1
description home office
switchport access vlan 18
switchport mode access
interface FastEthernet0/2
description t1 to branch office 1
ip address 192.168.19.1 255.255.255.0
interface Vlan18
description subnet for home office
ip address 192.168.18.1 255.255.255.0
no vlan 19

Hello,
In my opinion there is no 100% right answer here. I think it depends also about network forecast. I'll try to add here some thoughts:
- if you use trunk interfaces from home to branch and SVI for L3 connection, in terms of scalability is much easier to expand (you have now only one p2p L3 link, but in future you'll need another one; if the port is a trunk one, you just configure another SVI interface, allow vlan on trunk and your good to go)
- trunk interfaces involve more configuration (L2 interface and SVI L3 interface)
- if you add in the home office another switch to existing one, and for some reason you have misconfiguration in STP / VTP, then you can run into problems like loops, vlan database modification (e.g. VTP server mode and the new added switch has a higher revision number than existing one)
- L3 physical interfaces are easier to configure and less complex, but in case you want to scale to additional p2p link will be harder
- L3 configuration is easier to troubleshoot as you avoid the L2 complexity
- in terms of packet exchange a L3 interface will exchange less packets than a L2 trunk with SVI (I'm talking here about control traffic, not user traffic)
- with L2 trunk you can have other problems like if somebody is "smart enough" to add a new switch into the existing switch (if you have a switch there) at the branch location; imagine that the new switch due to misconfigurated STP became root bridge; you have a large STP domain.
As I said, there is no good or bad approach. You have to guide yourself about forecasts in your network. For example if you know that a branch location will not be extended in the next 2 years, then go ahead with L3 interface and that's it. On the other hands if you have doubts you can add for another location L2 trunk with SVI. You can mix this two solution to obtain the best results for your network characteristics.
Cheers,
Calin

Serial Port Profile (SPP) and Object Push Profile (OPP)

I just bought a new Blackberry Curve 8320. And am having several difficulties with it which I will list separately.
With other phones (like the Motorola RAZR V3t) I could send contacts from my Pocket PC HP iPaq via Bluetooth. When I try to do this with the Blackberry, the Pocket PC says that it cannot connect to the Object Push Profile (OPP) in the remote device (which is the Blackberry).
With other phones (like the Motorola RAZR V3t) I could dial contact from my Pocket PC HP iPaq via Bluetooth. When I try to do this with the Blackberry, the Pocket PC says that it cannot connect to the Serial Port Profile (OPP) in the remote device (which is the Blackberry).
Please and Thanks in advance for your help.
Kudos! Thanks!

Luisfigueredo,
Please do not post the same thread twice.
See my response in relation to your bluetooth question on ur previous thread.
http://supportforums.blackberry.com/rim/board/message?board.id=8300&message.id=9228#M9228
If your issue is resolved, put a checkmark in the green box that contains the resolution.
OR
If it was just/or also really helpful - Give it a Kudos.. Go on Mate.. Help the rest of the clueless blackberry user world find their answer too..
~Gday from Down Under~

Proxy Host and Proxy Port Profiles

Hi Hussein,
Could you let me know when we use Proxy Host and Proxy Port profiles. Where it will be used.
Regards,
Satya.

Hi Satya,
Are you referring to the following variables? If yes, then it is whenever you need the application to connect to the internet and a proxy server is required (an example is when you want to access Metalink from OAM to download application patches).
- Applications Server-Side Proxy Host And Domain (s_proxyhost)
- Applications Proxy Port (s_proxyport)
Note: 297689.1 - Unable to update MetaLink credentials from OAM
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=297689.1
Regards,
Hussein

SCVMM 2012R2 - change port profiles and logical Switches

Dear all,
we are runnings a few clusters with Hyper-V 2012R2, managed by SCVMM 2012R2.
I have configurad a Logical switch "Cluster-Default" with the necessary Logical networks, Port Pofiles etc., everything works fine.
Now I have to make an additional network available to some of our VMs that is currently not configured in the Switch and the Uplink Port profile.
Can I add Logical and VM Networks to a port profile that is "in use"?
If Yes, how will these changes be applied to the hosts that are using the switches?
(I have searched through technet and have found a lot about creating switches and profiles, but not about changing them)
If No - how can I proceed?
best regards
Markus

Yes, Network Sites can be added to Uplink Port Profiles that are in use. The VM Networks for the associated Logical Networks will then be available for use by vNics connected to the Logical Switch using the updated Uplink Port Profile.

System vlan an port-profile

Similar Messages

Maybe you are looking for