DAG Replication Network Isolation from MAPI
Hi,
Recently We have implemented Exchange 2010 SP2 DR setup.
We have two sites Prod and DR. We are facing some issue in DAG replication Network (Replication Adapter).
We are using 10.10.10.x for Mapi Networks and 192.168.1.x for Replication Network for Prod and 10.11.10.x for MAPI and 192.168.2.x for Replications.
As per Microsoft recommended, We configured replication adapters and added static routes for Replication Network.
We understand, Replicarion adapter is used for DAG Replication (Log Shipping and Seeding) and configured forewall to allow tonly DAG port 64327 for replication Vlans between sites.
Now, When we check the replication network hit in firewall. Its still using MAPI Network (MAPI Nic) to communication with DR sites. Replication Nics is not working properly.
Please let me know, How to isolate the MAPI and Replication Networks. Do we need configure Replication Port in DAG properties.
How to check whether Replication Network is working between the sites.
Regards
M
My Problem is, While seeding is happening between Primary Site to DR Site. Connections are going only via MAPI Networks. It is not using Replication Netowork. I have added the static route in all the prod and DR Mailbox Servers. But I have not
configured Replication Port in DAG properties. And also, I allowed only Port 64327 for Replication Vlan in both Primary and DR. Please let me know if you have any solutions. Regards M
That's expected if you are just using the EMC, or using standard options via EMS
What happens if you use
http://technet.microsoft.com/en-us/library/dd335201(v=exchg.141).aspx
Update-MailboxDatabaseCopy -Network
and
http://technet.microsoft.com/en-us/library/dd335158.aspx
Managing Mailbox Database Copies
To specify the networks you want to use for seeding, use the Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use. If you don't use the
Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:
http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
Note: My posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Similar Messages
-
Changing a Network Interface in DAG Replication Network after going P2V
I have a DAG member suffering severe hardware failure so I have gone P2V with it. It's functioning fine, except that the DAG Network Interfaces have changed - The MAPI Interface was on "Local Area Network" on the physical server, and is now
on Local Area Connection 7 on the VM. However, the DAG settings still point to "Local Area Network" and will not let me change it. Same thing for the replication network.
I have lost redundancy due to this, so I need to get it repaired pretty promptly.
Removing and re-adding the subnet in the DAG network has no effect - it still references the old physical NIC instead of the new virtual NIC, despite the new virtual NIC having the same IP as the old physical NIC.Try to change the network binding on the server
http://technet.microsoft.com/en-us/library/cc732472(WS.10).aspx
Try to delete the hidden network adapters as well.
Open Device Manager, from the File menu, expand the View and select the Show Hidden Devices option. This will enable and show any old un-used devices in the window
http://www.gfi.com/blog/how-to-remove-hidden-network-adapters-from-virtual-machines/
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Good afternoon
I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
site and I would like to keep that traffic to the replication network I have configured.
Any insight would be helpful.Hi,
If you want to specify the networks for seeding, you can use the
Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
So please use the Update-MailboxDatabaseCopy cmdlet with
NetWork parameter to specify which DAG network should be used for seeding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support -
Map network drive from windows 98 to server 2008 R2
Guys I have some old Windows 98 systems these 98 systems are attached to pieces of equipment on the warehouse floor. So with that said there is no way to upgrade them. I would like to map a network drive from these 98 systems to a 2008 R2 file server.
I have played around with LM compatibility mode but I'm not having much luck. Still when I try to access a share on a 2008 R2 box I'm being asked to entire a password. On the old 2003 server all I had to do was create a local account with the same username
and password on the 2003 server. So if anyone's done this I would be curious in knowing more. BTW the member server I'm trying to connect to is in a domain and the 98 box is in a workgroup.Hi,
As Windows 98 is such an old system, I may make mistake on suggestions I provided so please just have a try.
For old client system like Windows XP, in a workgroup environment we have 2 mentions to share folders.
1. As you said, create local account with same password on each computers so they can access each other with that account.
2. Share folders to Everyone (including Guest) and enable Guest account on computers which going to access.
You can try to enable Guest account and set a same password on each computer as a test.
Also in Windows XP we need to modify "Simple File Sharing" option. I cannot confirm if it exists on Windows 98 system but if it does, enable it when trying suggestion 2 and disable it when trying suggestion 1.
http://support.microsoft.com/kb/304040/en-us
If you have any feedback on our support, please send to [email protected] -
Mapping Network Drives From Mac to Windows
I'm wondering if anyone else has had any success with this. I am mapping a network drive from my Mac to my PC (Windows 7). I moved all of my photos to the Mac so I want my laptop to look there for the files. I have no problem with other PC's in the house but when I try to map to the Mac I receive the following error:
"The folder you entered does not appear to be valid. Please enter another."
I copy and paste the address into Windows Explorer and it opens no problem. I click start and paste it into the search area, same thing, no problem. Any ideas?If you search within this forum (search block, upper right), you will see that PAHU has answered this several times. For example, search for "UFRII windows."
Printing on OS X isn't quite as simple as on Windows - quite often, manufacturers provide drivers that are limited to the comm protocol "they want you to use," and Windows Printing (SMB) is usually not one of those. In fact, most USB printers get USB-only drivers. -
Multiple Airports with private and isolated guest wireless networks available from both
Hi,
I've been searching online for some equipment that can do what i want to do without going into the enterprise grade and spending $5000 on Cisco gear.
Consider two locations approx 80m apart - Primary is a house, and secondary location is a garage. A Cat6 run exists between the two.
The goal would be to have a wireless primary router in the house for wired and private wireless internet access, with an additional Guest wireless that is isolated from the private network that I can turn on and off if guests are coming over.
In addition, the second location should also support both wired and wireless connections.
It seems simple to me, one device in each location. The WAN port on the garage device would connect back to the house device. The two devices should be smart enough to know that one is extending the other. Someone on the guest wireless that is connected via the garage AP would not be able to see the wired devices even though it's traffic is going across the same wire back to the primary router.
Can I do this without spending a fortune?
ThanksTwo Apple AirPorts would do most....but not all...of what you want.
A few notes.....
In order for the guest network feature to work correctly on an AirPort router, the "main" AirPort in the house must connect to a simple modem......not a modem/router or gateway device. That is a deal killer for some users right there.
When the guest network is activated in the garage, it must be activated for both AirPorts....house and garage.
You could actiivate the guest network for the house and leave the guest network off in the garage if you wanted, no problem there.....but.....you could not activate the guest network in the garage without also activating it in the house first.
"Guests" can only connect to the guest network using wireless. Up to you to decide if you want to leave the guest network open or use a password that would need to be used to connect to the network.
But.....If "guests" had physical access to the AirPort in the garage....and they connected to one of the Ethernet ports on the AirPort in the garage, they would be connecting to your main or private network.
So, if something like this was a concern, you would have to either hide the AirPort in the garage and trust that users would not find it....or....find some way to limit access to the back panel of the AirPort so that users could not connect to it using an Ethernet cable.
If the features and installation limitations are acceptable, you could spend as little as $100 for each AirPort Express.
If you wanted better performance from the AirPort in the house, you could use an AirPort Extreme there...about $200 and an AirPort Express in the garage.
The deluxe option would be to use two AirPort Extremes.
Finally, you would want to make sure that you understood the store's return policy before you buy.....in case something unexpected crops up, as can sometimes be the case. -
Site Link Flooded By DAG Replication Traffic
Hi everyone,
I have a quick question regarding DAG replication. We have a DAG that stretches two sites (one site is the primary site and the other site is strictly DR). The WAN link is 150 Mbps, and we have
encoutered some issues with the network being over-saturated by bursts from the Exchange servers on the replication networks.
The manager of the Engineering team informed me of this today. Apparently this has been going on for a while, but they just discovered the cause recently. He asked about policing/rate-limiting
on traffic destined to the IP at the DR site to 100 Mbps. My understanding is that this would cause packets to drop if they go over 100 Mbps.
Now, I understand how TCP fundamentally works, and that the DAG utilizes TCP (default port 64327), so I would
like to think this wouldn't be an issue, but I wanted to open a dialog here anyway to see if anyone else has encountered anything like this, and if so, if problems arose.
As an aside, I am running Exchange 2010 SP2 (yeah, I know...hopefully going to SP3 next month). There are four total mailbox servers (three at the main site and one at the DR site). And yes,
I have collapsed my DAG networks (MAPI, Replication, Backup).
Any insight is welcome.
Thanks in advance!Thank you, Jared and Jim.
Yes, I figured that at worst my databases at my DR site may simply fall behind a bit, but I don't think it will be by too much, as it doesn't run that high all the time.
The manager of the engineering team is scheduling up a change for Tuesday morning to effectively limit the traffic on Tuesday morning. I'll monitor it for a few days and let you guys know how it is behaving.
Thanks again and have a great weekend! -
Hi All,
Please have a look in to the below mentioned environment.
primary site :SITE 1
server 1
server 2
secondary site :SITE 2
server 3
Note : All the above three servers are in single DAG .All the database are mounted on the server (server 1) which is located in the primary site (I.E SITE 1).
On that 5 databases we are having 3500 users .Based on the user designation we have allocated the mailbox size.
Query : Each and every day we are having the large no copy queue length for all the five databases to the server located in SITE 2.
Please help me out on this and also tell me is there any tool available to exactly get the required bandwidth for the exchange servers located between the active directory sites.
Thanks & Regards S.NithyanandhamI don't know of any tool that can calculate things for you but latency is the biggest thing you have to worry about. The other issues is looking at the network gear between the 2 sites. I have seen many times were switches get maxed out if they are set to
1 GB or even ports getting maxed out and need to bonded for more throughput. Test your latency from the edge of each site then test it within to see if there is a difference.
Regardless of their geographic location relative to other DAG members, each member of the DAG must have round trip network latency no greater than 500 milliseconds between each other member.
As the round trip latency between two Mailbox servers hosting copies of a database increases, the potential for replication not being up to date also increases. Regardless of the latency of the solution, customers should validate that the networks between
all DAG members is capable of satisfying the data protection and availability goals of the deployment. Configurations with higher latency values may require special tuning of DAG, replication, and network parameters, such as increasing the number of databases
or decreasing the number of mailboxes per database, to achieve the desired goals.
Round trip latency requirements may not be the most stringent network bandwidth and latency requirement for a multi-datacenter configuration. You must evaluate the total network load, which
includes client access, Active Directory, transport, continuous replication, and other application traffic, to determine the necessary network requirements for your environment.
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com -
Exchange DAG Replication Data Rate
i need some information regarding DAG replication issue. In my environment there is two mailbox server. One DC and another in DR site. The connectivity between DC and DR site is VPN. Bandwidth is one MB. But in VPN connection have ping loss. The ping loss rate
1-2%. In my environment twodatabase.
one is single and another is under the dag member. when i move mailbox from single to dag database the move rate is so slow and sometimes database going to dismount. I think its happened as because connectivity issue.
Can you please suggest the details about dag replication. I need to know that: what is dag replication
data rate? also the acceptable rate of ping loss and How much rate connectivity between DAG Heartbeat connection.
Please suggest as soon as possible.
Thanks,
ParvezHi Parvez,
From your description, I would like to clarify the following things:
1. It is not recommended to install Exchange server on DC.
2. The witness server is needed when there's an even number of members in the DAG. Based on your case, you need a file share witness server.
3. The DAG replication rate depends on the replication traffic.
4. By default, heartbeat frequency (subnet delay) is 1000ms for both local and remote subnets. When a node misses 5 heartbeats (subnet threshold) another nod within your DAG cluster will initiate a failover.
What's more, here are some helpful threads for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Exchange 2010: Collapsing DAG Networks
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
Hope my clarification is helpful.
Best regards,
Amy
Amy Wang
TechNet Community Support -
HI
I have one exchange 2013 SP1 server holding both Mailbox and CAS roles,
I want to come up with DAG, so i am going to setup a witness server.
SRV1- Exchange 2013 SP1(MB,CAS)
SRV2 -Witness Server
Do i need replication NICS (As i have only one member i.e one server holding both MB,CAS).
I dont have any issue configuring replication NICS but is it recommended in my scenario?
I am aware it is recommended when you want to add two members to DAG.If you are only going to have one server then you definitely don't need any replication NICs.
I typically only use dedicated replication NICs when the following are true:
I have dedicated NICs on the physical Server that are connected to a completely separate switch (not just vLAN)
I have a dedicated WAN for replication traffic to other sites. (if DAG stretches multiple sites)
In order to get the benefits of a replication network, these need to be met (atleast in my opinion)
Are you planning on setting up a second DAG member in the future? If not, I would hold off on even setting up and configuring the DAG, since you're not going to get any of the replication benefits from the DAG. You can always configure it again later
if you ever add the second server. Just my 2 cents. -
question on DAG replication
basic scenario DB will replicate on MAPI port and log will replicate on Replication port.
if replication port get disconnected than then replication will start on MAPI network that is by default senerio.
My Question
1) Some network outage happened but after some time network is restored and found that indexing get failed and both MAPI and REPlication are up then how the replication will work ?
2) And in the same senerio if database get unhealthy or corrupted then how it will work and which port it will use.Hi,
During the seeding process, the use of network depends on situations. If you want to specify the network that you want to use for seeding, you can use the Network parameter when running the
Update-MailboxDatabaseCopy cmdlet. If you don't use the
Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
Best regards,
Belinda Ma
TechNet Community Support -
Auto Deploy and VCD Network Isolation - Not Working
Hello,
I have opened a support case about this issue, but the case is moving a lot slower than I would like to see. I thought I'd post here to see if anyone has ran into anything similar.
We recently switched our 24-host vCloud cluster (more info about this cluster below) over to Auto-Deploy (was using boot from USB). After the switch, we had a few complaints from customers that use isolated networks. It turns out that only 4 of our 24 hosts were working properly with isolated networks. All 24-hosts are using the same auto-deploy image.
When the hosts boot up, the vCloud Director web interface shows the following with green check marks: "Status", "Enabled", "Ready", "Available", and "VCD Network Isolation Capable".
To get my other 20 hosts working, I disabled all 20 hosts in the vCloud interface, unprepared them, and prepared them. After this, network isolation worked for those 20 hosts. When I reboot one of the hosts, the host still looks like it's good in the interface, but network isolation doesn't work until I disable, unprepare, and prepare.
Here is some more information about our environment:
vCenter build 2001466
ESXi Host Build 2702864
VCD Build 5.5.2.2000523
vShield Build 5.5.3
Here is the Deploy Rule that the hosts are using:
Name : UCS-2.2.1-pcloud.5.5.aln
PatternList : {oemstring=$SPT:ESX_PublicCloud_autod.2.2.x}
ItemList : {ESXi-5.5.0-autod-2.2.1.vshield}
I have confirmed that this is indeed the profile being used by looking at the Summary tab for the hosts and seeing the listed Image Profile.
And here is what's in that item:
PowerCLI D:\ImageBuild> Get-EsxSoftwarePackage
Name Version Vendor Creation Date
misc-cnic-register 1.72.1.v50.1i-1vmw.550.0.0.... VMware 9/19/2013 6:0...
scsi-lpfc820 8.2.3.1-129vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-megaraid-mbox 2.20.5.1-6vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
esx-xlibs 5.5.0-0.0.1331820 VMware 9/19/2013 6:0...
lpfc 10.0.100.1-1vmw.550.0.0.133... VMware 9/19/2013 6:0...
mtip32xx-native 3.3.4-1vmw.550.1.15.1623387 VMware 2/22/2014 1:1...
net-nx-nic 5.0.621-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
block-cciss 3.6.14-10vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-fnic 1.6.0.5-1OEM.500.0.0.472560 cisco 9/30/2013 11:...
net-enic 2.1.2.42-1OEM.500.0.0.472560 Cisco 9/5/2013 8:30...
sata-sata-sil24 1.1-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
rste 2.0.2.0088-4vmw.550.1.15.16... VMware 2/22/2014 1:1...
elxnet 10.0.100.0v-1vmw.550.0.0.13... VMware 9/19/2013 6:0...
scsi-aacraid 1.1.5.1-9vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-cmd64x 0.2.5-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
net-cnic 1.72.52.v55.1-1vmw.550.0.0.... VMware 9/19/2013 6:0...
scsi-adp94xx 1.0.8.12-6vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
net-be2net 4.6.100.0v-1vmw.550.0.0.133... VMware 9/19/2013 6:0...
net-ixgbe 3.7.13.7.14iov-12vmw.550.2.... VMware 4/29/2015 6:4...
net-igb 5.0.5.1.1-1vmw.550.2.54.240... VMware 1/1/2015 8:00...
epsec-mux 5.1.0-01814505 VMware 5/13/2014 4:3...
esx-base 5.5.0-2.62.2702864 VMware 4/29/2015 6:4...
ata-pata-sil680 0.4.8-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ipmi-ipmi-msghandler 39.1-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-hpt3x2n 0.3.4-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-megaraid-sas 5.34-9vmw.550.2.33.2068190 VMware 8/23/2014 1:5...
scsi-mptsas 4.23.01.00-9vmw.550.0.0.133... VMware 9/19/2013 6:0...
net-bnx2 2.2.3d.v55.2-1vmw.550.0.0.1... VMware 9/19/2013 6:0...
ata-pata-via 0.3.3-2vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ima-qla4xxx 2.01.31-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-amd 0.3.10-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-serverworks 0.4.3-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-sata-promise 2.12-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-sata-nv 3.5-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ipmi-ipmi-devintf 39.1-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-ips 7.12.05-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-sata-svw 2.3-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-mptspi 4.23.01.00-9vmw.550.0.0.133... VMware 9/19/2013 6:0...
net-e1000e 1.1.2-4vmw.550.1.15.1623387 VMware 2/22/2014 1:1...
esx-xserver 5.5.0-0.0.1331820 VMware 9/19/2013 6:0...
net-tg3 3.123c.v55.5-1vmw.550.2.33.... VMware 8/23/2014 1:5...
net-forcedeth 0.61-2vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-aic79xx 3.1-5vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-ata-piix 2.12-10vmw.550.2.33.2068190 VMware 8/23/2014 1:5...
scsi-bnx2i 2.72.11.v55.4-1vmw.550.0.0.... VMware 9/19/2013 6:0...
ohci-usb-ohci 1.0-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-qla4xxx 5.01.03.2-6vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
scsi-qla2xxx 902.k1.1-9vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
net-mlx4-core 1.9.7.0-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-atiixp 0.4.6-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
misc-drivers 5.5.0-2.62.2702864 VMware 4/29/2015 6:4...
esx-dvfilter-generic-... 5.5.0-0.0.1331820 VMware 9/19/2013 6:0...
ata-pata-pdc2027x 1.0-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
qlnativefc 1.0.12.0-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
lsi-mr3 0.255.03.01-2vmw.550.1.16.1... VMware 4/15/2014 9:0...
vshield 5.5.3-2172759 VMware 9/30/2014 2:3...
net-vmxnet3 1.1.3.0-3vmw.550.2.39.2143827 VMware 9/18/2014 11:...
scsi-hpsa 5.5.0-44vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
tools-light 5.5.0-2.62.2702864 VMware 4/29/2015 6:4...
scsi-mpt2sas 14.00.00.00-3vmw.550.1.15.1... VMware 2/22/2014 1:1...
scsi-bnx2fc 1.72.53.v55.1-1vmw.550.0.0.... VMware 9/19/2013 6:0...
lsi-msgpt3 00.255.03.03-1vmw.550.1.15.... VMware 2/22/2014 1:1...
net-e1000 8.0.3.1-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
xhci-xhci 1.0-2vmw.550.2.39.2143827 VMware 9/18/2014 11:...
ipmi-ipmi-si-drv 39.1-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-ahci 3.0-21vmw.550.2.54.2403361 VMware 1/1/2015 8:00...
net-bnx2x 1.72.56.v55.2-1vmw.550.0.0.... VMware 9/19/2013 6:0...
scsi-megaraid2 2.00.4-9vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
ehci-ehci-hcd 1.0-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
esx-tboot 5.5.0-2.33.2068190 VMware 8/23/2014 1:5...
uhci-usb-uhci 1.0-3vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
sata-sata-sil 2.3-4vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
vcloud-agent 5.5.0-1280396 VMware 8/17/2013 4:0...
net-mlx4-en 1.9.7.0-1vmw.550.0.0.1331820 VMware 9/19/2013 6:0...
And here is the output of testing the deploy rule compliance:
PowerCLI D:\ImageBuild> Get-Cluster 0000000-ESXVCLOUDCL1.ALN | Get-VMHost |Test-
DeployRuleSetCompliance
VMHost ItemList
esx142269.vm.seo.... {}
esx140622.vm.seo.... {}
esx139784.vm.seo.... {}
esx140617.vm.seo.... {}
esx138793.vm.seo.... {}
esx135523.vm.seo.... {}
esx138945.vm.seo.... {}
esx138794.vm.seo.... {}
esx139783.vm.seo.... {}
esx140309.vm.seo.... {}
esx140310.vm.seo.... {}
esx140311.vm.seo.... {}
esx140313.vm.seo.... {}
esx140339.vm.seo.... {}
esx140614.vm.seo.... {}
esx140615.vm.seo.... {}
esx140616.vm.seo.... {}
esx140618.vm.seo.... {}
esx140619.vm.seo.... {}
esx140621.vm.seo.... {}
esx141947.vm.seo.... {}
esx141945.vm.seo.... {}
esx142271.vm.seo.... {}
esx142270.vm.seo.... {}
Here is another vib list from a host:
~ # esxcli software vib list
Name Version Vendor Acceptance Level Install Date
net-enic 2.1.2.42-1OEM.500.0.0.472560 Cisco VMwareCertified -
ata-pata-amd 0.3.10-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-atiixp 0.4.6-4vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-cmd64x 0.2.5-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-hpt3x2n 0.3.4-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-pdc2027x 1.0-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-serverworks 0.4.3-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-sil680 0.4.8-3vmw.550.0.0.1331820 VMware VMwareCertified -
ata-pata-via 0.3.3-2vmw.550.0.0.1331820 VMware VMwareCertified -
block-cciss 3.6.14-10vmw.550.0.0.1331820 VMware VMwareCertified -
ehci-ehci-hcd 1.0-3vmw.550.0.0.1331820 VMware VMwareCertified -
elxnet 10.0.100.0v-1vmw.550.0.0.1331820 VMware VMwareCertified -
epsec-mux 5.1.0-01814505 VMware VMwareCertified -
esx-base 5.5.0-2.62.2702864 VMware VMwareCertified -
esx-dvfilter-generic-fastpath 5.5.0-0.0.1331820 VMware VMwareCertified -
esx-tboot 5.5.0-2.33.2068190 VMware VMwareCertified -
esx-xlibs 5.5.0-0.0.1331820 VMware VMwareCertified -
esx-xserver 5.5.0-0.0.1331820 VMware VMwareCertified -
ima-qla4xxx 2.01.31-1vmw.550.0.0.1331820 VMware VMwareCertified -
ipmi-ipmi-devintf 39.1-4vmw.550.0.0.1331820 VMware VMwareCertified -
ipmi-ipmi-msghandler 39.1-4vmw.550.0.0.1331820 VMware VMwareCertified -
ipmi-ipmi-si-drv 39.1-4vmw.550.0.0.1331820 VMware VMwareCertified -
lpfc 10.0.100.1-1vmw.550.0.0.1331820 VMware VMwareCertified -
lsi-mr3 0.255.03.01-2vmw.550.1.16.1746018 VMware VMwareCertified -
lsi-msgpt3 00.255.03.03-1vmw.550.1.15.1623387 VMware VMwareCertified -
misc-cnic-register 1.72.1.v50.1i-1vmw.550.0.0.1331820 VMware VMwareCertified -
misc-drivers 5.5.0-2.62.2702864 VMware VMwareCertified -
mtip32xx-native 3.3.4-1vmw.550.1.15.1623387 VMware VMwareCertified -
net-be2net 4.6.100.0v-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-bnx2 2.2.3d.v55.2-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-bnx2x 1.72.56.v55.2-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-cnic 1.72.52.v55.1-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-e1000 8.0.3.1-3vmw.550.0.0.1331820 VMware VMwareCertified -
net-e1000e 1.1.2-4vmw.550.1.15.1623387 VMware VMwareCertified -
net-forcedeth 0.61-2vmw.550.0.0.1331820 VMware VMwareCertified -
net-igb 5.0.5.1.1-1vmw.550.2.54.2403361 VMware VMwareCertified -
net-ixgbe 3.7.13.7.14iov-12vmw.550.2.62.2702864 VMware VMwareCertified -
net-mlx4-core 1.9.7.0-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-mlx4-en 1.9.7.0-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-nx-nic 5.0.621-1vmw.550.0.0.1331820 VMware VMwareCertified -
net-tg3 3.123c.v55.5-1vmw.550.2.33.2068190 VMware VMwareCertified -
net-vmxnet3 1.1.3.0-3vmw.550.2.39.2143827 VMware VMwareCertified -
ohci-usb-ohci 1.0-3vmw.550.0.0.1331820 VMware VMwareCertified -
qlnativefc 1.0.12.0-1vmw.550.0.0.1331820 VMware VMwareCertified -
rste 2.0.2.0088-4vmw.550.1.15.1623387 VMware VMwareCertified -
sata-ahci 3.0-21vmw.550.2.54.2403361 VMware VMwareCertified -
sata-ata-piix 2.12-10vmw.550.2.33.2068190 VMware VMwareCertified -
sata-sata-nv 3.5-4vmw.550.0.0.1331820 VMware VMwareCertified -
sata-sata-promise 2.12-3vmw.550.0.0.1331820 VMware VMwareCertified -
sata-sata-sil24 1.1-1vmw.550.0.0.1331820 VMware VMwareCertified -
sata-sata-sil 2.3-4vmw.550.0.0.1331820 VMware VMwareCertified -
sata-sata-svw 2.3-3vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-aacraid 1.1.5.1-9vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-adp94xx 1.0.8.12-6vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-aic79xx 3.1-5vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-bnx2fc 1.72.53.v55.1-1vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-bnx2i 2.72.11.v55.4-1vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-hpsa 5.5.0-44vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-ips 7.12.05-4vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-lpfc820 8.2.3.1-129vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-megaraid-mbox 2.20.5.1-6vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-megaraid-sas 5.34-9vmw.550.2.33.2068190 VMware VMwareCertified -
scsi-megaraid2 2.00.4-9vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-mpt2sas 14.00.00.00-3vmw.550.1.15.1623387 VMware VMwareCertified -
scsi-mptsas 4.23.01.00-9vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-mptspi 4.23.01.00-9vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-qla2xxx 902.k1.1-9vmw.550.0.0.1331820 VMware VMwareCertified -
scsi-qla4xxx 5.01.03.2-6vmw.550.0.0.1331820 VMware VMwareCertified -
uhci-usb-uhci 1.0-3vmw.550.0.0.1331820 VMware VMwareCertified -
vcloud-agent 5.5.0-1280396 VMware VMwareCertified -
vmware-fdm 5.5.0-2001466 VMware VMwareCertified -
vshield 5.5.3-2172759 VMware VMwareCertified -
xhci-xhci 1.0-2vmw.550.2.39.2143827 VMware VMwareCertified -
tools-light 5.5.0-2.62.2702864 VMware VMwareCertified -
scsi-fnic 1.6.0.5-1OEM.500.0.0.472560 cisco VMwareCertified -
Any help is appreciated. Thanks.Right now, on my test host (that is not working), I have two VMs, one named "Test 1" and the other "Test 2" They only have an isolated network on them (named "Test Isolated Network") that is in my VDC, and pings do not work between them. If I move them to any other host (that have been unprepared and prepared), pings work. I can move both to the same host, or different hosts.
Here is the fence info on this host, I'm not really sure how to interpret this:
~ # esxcli vcloud fence getfenceinfo
Module Parameters:
Host Key: 0x104b0
Configured LAN MTUs:
+------------------------------------------------------------------------------------------+
| LAN ID | 1 2 3 4 5 6 7 8 9 10 - - - - - - |
| MTU | 1500 1500 1500 1500 1500 1500 1500 1500 1500 1500 - - - - - - |
+------------------------------------------------------------------------------------------+
Active Ports:
+-----------------------------------------+
| ID | OPI | LanID | MTU |
+-----------------------------------------+
| 410b1d4ce7d0 | 01,0001a2 | 4 | 1500 |
| 410b1d4cfde0 | 01,0001a2 | 4 | 1500 |
+-----------------------------------------+
Switch State:
+-----------------------------------------------------+
| Inner MAC | Outer MAC | used | age | seen |
+-----------------------------------------------------+
+ ............................... Port:0x410b1d4ce7d0 +
+-----------------------------------------------------+
+ ............................... Port:0x410b1d4cfde0 +
| 00:50:56:01:06:16 | 00:13:F5:01:04:B4 | 1 | 1 | 1 |
+-----------------------------------------------------+
Port Statistics Summary:
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Identity | To VM dropped | To VM passed | From VM dropped | From VM passed | Reflect |
| Port ID | Fence ID | total | misunf | misfen | stored | frag | other | fenced | join | unfen | csum | frag | GVT | other | fenced | tso | frag | csum | GVT | ufport | pass | error |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 410b1d4ce7d0 | 01,0001a2 | 3991 | 2 | 3976 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 679 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 410b1d4cfde0 | 01,0001a2 | 4478 | 2 | 3860 | 0 | 0 | 0 | 616 | 0 | 0 | 0 | 0 | 0 | 0 | 626 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
And here is the output of the command a little while later on the same host (while my test pings are going)
~ # esxcli vcloud fence getfenceinfo
Module Parameters:
Host Key: 0x104b0
Configured LAN MTUs:
+------------------------------------------------------------------------------------------+
| LAN ID | 1 2 3 4 5 6 7 8 9 10 - - - - - - |
| MTU | 1500 1500 1500 1500 1500 1500 1500 1500 1500 1500 - - - - - - |
+------------------------------------------------------------------------------------------+
Active Ports:
+-----------------------------------------+
| ID | OPI | LanID | MTU |
+-----------------------------------------+
| 410b1d4ce7d0 | 01,0001a2 | 4 | 1500 |
| 410b1d4cfde0 | 01,0001a2 | 4 | 1500 |
+-----------------------------------------+
Switch State:
+-----------------------------------------------------+
| Inner MAC | Outer MAC | used | age | seen |
+-----------------------------------------------------+
+ ............................... Port:0x410b1d4ce7d0 +
+-----------------------------------------------------+
+ ............................... Port:0x410b1d4cfde0 +
| 00:50:56:01:06:16 | 00:13:F5:01:04:B4 | 1 | 1 | 1 |
+-----------------------------------------------------+
Port Statistics Summary:
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Identity | To VM dropped | To VM passed | From VM dropped | From VM passed | Reflect |
| Port ID | Fence ID | total | misunf | misfen | stored | frag | other | fenced | join | unfen | csum | frag | GVT | other | fenced | tso | frag | csum | GVT | ufport | pass | error |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 410b1d4ce7d0 | 01,0001a2 | 4696 | 2 | 4681 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 796 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 410b1d4cfde0 | 01,0001a2 | 5300 | 2 | 4565 | 0 | 0 | 0 | 733 | 0 | 0 | 0 | 0 | 0 | 0 | 743 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Looking at the VDS, the Maximum MTU is set to 1500. Looking at dvs.VCDVSTest Isolated Network-ca9a45c9-1dec-4f95-8b96-68d9c05b2a5d, I see it's VLAN is set to 2535 (which matches the network pool settings) and number of ports is 16 -
Hello,
I have imported a 2.x VM to a 3.0.3 server, using 3.1.1 manager as a template. I removed network entries from the vm.cfg file before the import. Now I need to configure this VM to have network access, but I'm having a hard time putting all the different pieces together.
What is the procedure to do this? I am going through the user's guide, but any other sources are much appreciated.
Thanks.Well i was used to using VM Server 2.1.1 without the Manager, which I found too buggy to use and grew accustomed to just using the server itself. Now I went for VM Server 3.0.3 to check out the new manager which looks promising :-)
I figured out my network issues so I'll mark this thread as answered, thanks.
My problem was very very simple, no bond mapped to a network :-D I couldn't figure it out for a while, because I was trying to create a new network and that, of course, couldn't assign the already assigned bond. I was shocked how many people blog about Oracle VM installation only posting screenshots and text output of the actual installation, just seems pointless.
The official User Manual is a great resource, but it's a bit harder to read for someone who only needs the simplest network to manage sandbox environments. I'm also using separate servers, each having their own (internal) repository and individual network. -
How to prevent a rdp user from mapping drives on the server ?
Hi,
User A from Domain A (using Win7 pro) is able to rdp to Server Z (Windows Server 2008) which is in Domain Z and is able to map drive.
My question is : How do I prevent User A from mapping any drive in Server Z ?
Please advise. TIA !Hi,
if a user has access to the other share there is no way to prevent that user from mapping a drive.
However, you can remove the "map Network drive" functionality via policy, please see
http://msdn.microsoft.com/en-us/library/ms812045.aspx
That does not prevent users from mapping their drive manually using the "net use ..." command from a shell. While it is possible to restrict running of the net command, I do not recommend that (see
http://social.technet.microsoft.com/Forums/windowsserver/en-US/b5012142-cfe9-4b24-99b9-d7ff3b84f0f4/what-security-policy-blocks-use-of-the-net-command-for-nonadmin-users?forum=winserverGP).
( What you may consider when having Shares cross-forest, you can remove that authorized users permission from the share replacing it by DOMAIN\Domain users groups, etc. So access to the share is limited instead of using a share that a user has access to.
Please Keep in mind that even when you remove the Network drives a user can still Access the resource via UNC. )
Regards,
Martin -
Background: For work I routinely need to connect to a secure VPN that is completely isolated from the internet. When using it, I can only connect to the servers that reside within the network and the VPN software (Cisco AnyConnect + NAC Agent) seems to automatically redirect all http requests to external sites to a catch-all 'sorry you can't do that' page.
So while connected to the VPN, Firefox Sync doesn't work and nor do I expect it to. However, my issue is that every time I connect to the VPN, Firefox silently pops up a "sync encountered an error while syncing" error message bar at the bottom of the browser, which I have to manually close. This obviously isn't the end of the world, but having to do it all the time gets annoying so I was wondering if there was a way of suppressing that particular error message or maybe getting Sync to handle the secure VPN more gracefully.I don't know about blocking that message, but my suggestion is to turn Sync autoconnect off, and use Sync manually.
Type '''about:config''' in the URL bar and hit Enter. <br />
Then type '''''autoconnect''''' in the Search bar at the top. <br />
'''services.sync.autoconnect''' = double-click that pref to toggle it to '''false'''.
Then to trigger a Sync manually, hit '''Sync Now''' in the Firefox menu ''(or the File menu)''.
Maybe you are looking for
-
My phone was doing system update. will not turn on now gives me a startup error and turns off
my phone did a system update to lollipop now it will not turn on and gives me an error message 1740 and 1790 then turns off
-
STAD Report generation takes too Much time
Dear Experts, In our Production system if we execute the STAD report for10 minutes to get the business transaction data for a single user or multiple users. Its taking too much time upto 500 sec sometimes throwing DUMP due to time out. We have the is
-
Please let me how to store images in the Oracle 9i database and how to retrieve.
-
SC workflow - "set status to released" step tRFC error
Hi All, We have a "Shopping Cart without approval" workflow defined in our SRM system. The workflow is working fine in Develpoment scenario however in Production it is stuck at "set status to released" step. Checked that step and its a backgroung ste
-
HP Pavillion 23 freezing after startup
As soon as I turn on the computer, the hp logo shows and usually, these colors start showing. This just started after the 8.1 update. I don't think it's graphics because you see the hp logo, and the prompt to restart my computer. You can somewhat see