Simplest Data Center Interconnect?

Hi all,
What's a simple way to implement a L2 network across 2 L3 DCs connected by 2x1Gig links using a 6504-E with SUP720-3C?! The DCs are only a few kilometres apart and our local service provider can only provide 1Gig fiber links between DCs (which I can then configure as L2 or L3). I do not want to simply configure flat L2 across both DCs - I would like to keep each DC as a separate L3 site and run OSPF for fast convergence and therefore avoid spanning-tree altogether.
At the moment each DC uses 3750 switches connected by L3 links and runs EIGRP. We then use separate hardware (7200) and L2TPv3 to create some shared L2 networks across that. We're moving to the 6500 platform and so it's a good opportunity to redesign things - and hopefully I can minimise the amount of hardware needed and consolidate using only the 6500 platform in each DC.
I also have a Cisco ACE appliance to fit at each site and to have redundancy for these they need to live in a shared network! That's what happens when the design process starts after the kit has already been brought (not my choice btw!).
Any ideas?

Howdy,
The 2x1Gig links are to connect the 2 DCs together - but the question is what's the best way to do this? For example, best practice dictates that sites should be L3 only. However, I also need some kind of L2 connectivity for certain clustered services which require L2.
What I've ended up doing is a bit of both L2 and L3. Basically I created a L2 etherchannel which only allows 2 things - a VLAN which is used to provide a small /30 link so that I can create SVIs on each end and run L3 on top; and VLANs which are used as pure L2 which run HSRP. Here's the config:
DC1 switch
interface Port-channel1
description Link to DC2 - Po1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 2
switchport trunk allowed vlan 2,120
switchport mode trunk
interface Vlan2
ip address 10.x.x.9 255.255.255.252
ip ospf network point-to-point
interface Vlan120
description Shared VLAN
ip address 10.120.0.253 255.255.255.0
standby 120 ip 10.120.0.254
standby 120 priority 150
standby 120 preempt
DC2 switch
interface Port-channel1
description Link to DC1 - Po1
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 2
switchport trunk allowed vlan 2,120
switchport mode trunk
interface Vlan2
ip address 10.x.x.10 255.255.255.252
ip ospf network point-to-point
ip ospf priority 0
interface Vlan120
description Shared VLAN
ip address 10.120.0.252 255.255.255.0
standby 120 ip 10.120.0.254
standby 120 preempt
It does seem to work ok - for example I have different networks at each DC which I can reach independently and I have a couple of VLANs which stretch across sites. The only problem that I can see is that there would be serious problems if the 2 Gig links went down between the 2 switches - each would then be HSRP master. Also there's a trombone effect with traffic from DC2 using DC1 as its default gateway but there's no way around this unless we use OTV or similar!
Any thoughts are very welcome! Thank you.

Similar Messages

Data Center Interconnect - Layer 2 Extension using vPC

Hi, I wanna if possible try to validate the design to connect 4 nexus 7010 to permit data center interconnect and layer 2 extension using the same vpc and the same port channel number and only 2 links between them as showed in the attach ppt
Is anybody using a design like that ??

this will work if it is *only* layer2 between the two pairs of N7K. You cannot create a L3 SVI and attempt to route it via the vpc port channel. It won't work. If you need both L3 and L2, one option will be to use OTV. Rgds Eng Wee

Data Center InterConnect with Dark Fibre

Dear all,
We are designing a Data Center InterConnection for our two Data Centers on top of a 10G Dark Fibre.
Our primary goal is to:-
extend a few vlans between the two DCs;
Support VMware vMotion betwen the two DCs;
asymmetric SAN synchronization;
FCoE for SAN connectivity between the two DCs;
So may I ask if we could run both LAN and SAN connections on this DF connection? We have NX5K on one DC and NX7K on the other, are there specific devices required to enable both LAN and SAN connections?
It would be really appreciated if anyone could shed any lights on this. Any suggestions are welcome!
Best Regards,
James Ren

Hello.
If you are running Active/Backup DC scenario, I would suggest to make network design and configuration exactly the same. This includes platforms, interconnectivity types and etc.
Do you know what is the latency on the fiber between these two DCs?
Another question: why do you run 6880 in VSS, do you really need this?
Q about the diagram: are you going to utilize 4 fibers for DC interconnection?
PS: did you think about OTV+LISP instead of MPLS?

Data Center Interconnect using MPLS/VPLS

We are deploying a backup data center and need to extend couple of Vlans over the backup data center.These two DC's which are interconnected by a fibre link which we manage and terminates on the ODC2MAN and ODCXMAN.We run MPLS on these devices ODC2MAN and ODCXMAN(Cisco 6880) as PE routers. I configured OSPF between these devices and advertised their loopbacks.
I need configuration assistance on my PE (odcxman and odc2man) to run the VFI and the VPLS instances.The vlans on the ODCXAGG need to extend to the ODC2AGG.
Also, I am looking for the configuration assistance such that each core devices should have 3 eigrp neighbors.
For example:
ODC2COR1 should have Eigrp neighbors with ODCXCOR1, ODCXCOR2 and ODC2COR2 and my VPLS Cloud should be emulated as a transparent bridge to my core devices such that it appears that ODC2COR1 is directly connected to ODCXCOR1 and ODCXCOR2 and have cdp neighbor relation. I have attached the diagram.Please let me know your inputs.

Hello.
If you are running Active/Backup DC scenario, I would suggest to make network design and configuration exactly the same. This includes platforms, interconnectivity types and etc.
Do you know what is the latency on the fiber between these two DCs?
Another question: why do you run 6880 in VSS, do you really need this?
Q about the diagram: are you going to utilize 4 fibers for DC interconnection?
PS: did you think about OTV+LISP instead of MPLS?

Data Center to Data Center Layer 2 connectivity

What would be the best way
to provide layer 2 connectivity between 2 data centers? Sample router configs?
Thanks!!
Gary

What would be the best way
to provide layer 2 connectivity between 2 data centers? Sample router configs?
Thanks!!
Gary
Hi Gary,
Data Center to Data Center can be conencted in diffterent ways like point to point link,over the MPLS or some other means and cofniguration all depend on the connectivity what exactly is with your current network setup.
Check out the below link on Data Center interconnect consideration.
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11_493718.html
Hope to Help !!
Remember to rate the helpful post
Ganesh.H

Data Center Redundancy

Hi, dear experts!
I) My Input data is (read please, or see attach):
- I have one active data center (main office), one backup data center (backup office), and several branch offices and many corporate internet users
- Each of the offices has redundant internet connection: Main office via ISP1 and ISP2, backup office via ISP3 and ISP4.
- Standby data center duplicates corporates services (such as Exchange, Sharepoint, FileStorage).
- Main office and backup office are long-distanced from each other (about 800 km), and interconnected via 1Gb fiberoptic.
II) My tasks are:
1. Provide redundant network connection for local ofiice users to corporate services.
2. Provide redundant network connection for branch offices and internet users to corporate services.
III) My ideas are:
1. Accordingly to the 1-st task. Here I suppose to use load balancers in redundant configuration.
2. Accordingly to the 2-nd task. To my mind there are two scenarios.
2.1 First scenario. To built a DMVPN topology using main and backup offices as a hubs, and branch offices as a spokes.
2.2 Second scenario. To by provider independet IPv4-adress block and ASN, to advertise main and backup office networks in internet.
IV) My questions are:
-What scenario according to the 2-nd task is better: using a DMVPN-topology or using an ASN-redundancy?
-Is it possible to avoid assymetric routing problems in case of using a an ASN-redundancy?
Thank you!

I think Global loadblancer device will solve your both issue or there is an other solution for 2nd question,
to use BGP confedration, that means use two private ASN internaly one in each DC, and put them both DC in one confedration, use one public ASN with all your ISP's.
Regards,

Nexus 5K - Data Center to Data Center

Hi All,
A scenario was recently presented to me that involved connecting two SANs between two Data Centers. One of the Data Centers is existing and utilizes Nexus 5K switches while the other Data Center will be greenfield and is currently just a shell.
From what I've been reading the Nexus 5K does not support FCIP and I have some concerns regarding the feasibility to perform SAN to SAN over a Service Providers WDM infrastructure; mainly due to cost. More reading suggested that this could not be done with FCoE.
Just wanted to pick everyones brain regarding what solutions are available to interconnect two SANs between Data Centers. The solution would involve using a Service Provider, Ethernet and WDM services are available to both locations.

You can add a pair of MDS9222i in the middle. This will take care of FCIP, DWDM traffic.

Data Center Connection using ONS 15530

Hi!
1. I am connecting 2 Data Center using DWDM on ONS 15530. The client is GE and planning on running Gigabit Etherchannel.
2. My question is, whish one is better? Using the multirate transponder or GE aggregation card to connect to GE client?
3. Either way, how does client and ONS component interconnect?
- If transponder is used, how does the OADM, OSC, trunk card and transponder connect to each other?
- If muxponder is used, what component is needed ad how does it connect?
4. FYI, I come from ONS 15540 ESPx background where everything connect externally. Apreciate you guys expert response. Thanks.
Rgds
Helme

You have three options:
1/ Use 8 port aggregation card (15530-FCGE-8P) together with 10G ITU card (4 port aggregation card is not cost effective if you are carrying only GE traffic). 10G ITU is the expensive part.
This 8 port aggregation module is connected to 10G ITU module via ONS15530 electrical backplane (not optical); 10G ITU and 8 port module both have 4x 2,5G backplane connections. 10G ITU is connected OADM using external MU-MU optical patch cords.
You can also use 2,5G ITU card but then you can only use 2 ports of the 8 port module card.
2/ Use 8 port multiservice muxponder (15530-MSMP-xxxx), this card has 2,5G capacity and card is SDH/SONET based. DWDM laser is embedded in the card, so this card is connected directly to OADM using external MU-MU optical patch cords (no backplane connections). Remember that this card is 2,5G so if you plan to use only GE you can utilize only 2 ports from the module.
3/ Use Transponders (15530-TSP1-XXX2) as you do in ONS15540. One Transponder - one client signal - one lambda. Transponder is connected directly to OADM using external MU-MU optical patch cords (no backplane connections).
What solution fits best for you depends on how many GE connections you need, what are future needs for more ports, what is your optical power budget, do you need high availability (no single point of failure) etc. Cheapest way to run only 2x GE is using option 2 above.
rgds,
Jp

Data center vs mdf?

Hello,
My question is,
What is the difference between a data center and an MDF. I know the ISP line always drops into the MDF. Is that the same with a data center? If so, to me it seem like a data center is just a very large mdf that needs alot of cooling, and space.

MDF
Short for main distribution frame, a cable rack that interconnects and manages the telecommunications wiring between itself and any number of
IDFs. Unlike an IDF, which connects internal lines to the MDF, the MDF connects private or public lines coming into a building with the internal network. For example, an enterprise that encompasses a building with several floors may have one centralized MDF on the first floor and one IDF on each of the floors that is connected to the MDF
http://www.webopedia.com/TERM/M/MDF.html
data center is a term that refer to the entire physical location that host multiple physical and logical technologies such as MDF, Racks, servers , Network equipments ..etc where an MDF could be used to interconnect the building floors IDFs to the building Data center
hope this help

Welcome to the Solutions and Architectures Data Center & Virtualization Community

Welcome to the Solutions and Architectures Data Center & Virtualization Community. We encourage everyone to share their knowledge and start conversations related to Data Center and Virtualization Solutions and architectures.All topics are welcome, including Servers – Unified Computing, Data Center Security, Data Center Switching, Data Center Management and Automation, Storage Networking, Application Networking Services and solutions to solve business problems.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
Cheers,
Dan Bruhn

Hi,
I have a question...
I going to install two Nexus 7009 with three N7K-F248XP-25 modules on each one, I am planning to create 3 VDC, but at the initial configuration the system does not show the ethernets ports of these modules, even with the show inventory and show module I can see tah the modules are recognized and its status is OK. There is something that I have to do before start to configure these modules...? enable some feature or license in order to see the ports with show running CLI...?

Welcome to the Enterprise Data Center Networking Discussion

Welcome to the Cisco Networking Professionals Connection Network Infrastructure Forum. This conversation will provide you the opportunity to discuss general issues surrounding Enterprise Data Center Networking. We encourage everyone to share their knowledge and start conversations on issues such as Mainframe connectivity, SNA Switching Services, DLSw+, managing SNA/IP and any other topic concerning Enterprise Data Center Networking.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
We encourage you to tell your fellow networking professionals about the site!
If you would like us to send them a personal invitation simply send their names and e-mail addresses along with your name to us at [email protected]

Hi together,
Since the release of SAP NetWeaver 2004s to 'Unrestricted Shipment' as of 6th of June 2006, we have renamed the forum 'SAP NetWeaver2004s Ramp-Up' to 'BI in SAP NetWeaver2004s'.
The forum should continue to adress BI issues particular to the release SAP NetWeaver 2004s. Please post general BI, project, etc. question to the other existing BI forums.
The SAP NetWeaver BI organisation will also use this forum to communicate / roll-out information particular to the release of SAP NetWeaver 2004s (in addtion to the FAQs and other material on the SAP Service Marketplace and information in other areas of the SDN).
Cheers
SAP NetWeaver BI Organisation

Deploying Cisco Overlay Transport Virtualization (OTV) in Data Center Networks

Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to plan, design, and implement Cisco Overlay Transport Virtualization (OTV) in your Data Center Network with Cisco experts Anees Mohamed Abdulla and Pranav Doshi.
Anees Mohamed Abdulla is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. He has 10 years of experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching content engineer and LAN switching TAC engineer. He holds a bachelor's degree in electronics and communications and has a CCIE certification 18764 in routing and switching.
Pranav Doshi is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. Pranav has experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching TAC engineer and now network consulting engineer. He holds a bachelor's degree in electronics and communications and a master's degree in electrical engineering from the University of Southern California.
Remember to use the rating system to let Anees and Pranav know if you have received an adequate response.
Because of the volume expected during this event, Anees and Pranav might not be able to answer each question. Remember that you can continue the conversation on the Data Center, sub-community forum shortly after the event. This event lasts through August 23, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Dennis,
    All those Layer 2 extension technologies require STP to be extended between Data Centers if you need to have multiple paths between Data Centers. OTV does not extend STP rather it has its own mechanism (AED election) to avoid loop when multiple paths are enabled. It means any STP control plane issue, we don't carry to the other Data Center.
    OTV natively suppresses Unknown Unicast Flooding across the OTV overlay. Unknown unicast flooding is a painful problem in layer 2 network and difficult to troubleshoot to identify the root cause if you don't have proper network monitoring tool.
   It has ARP optimization which eliminates flooding ARP packets across Data Center by responding locally with cached ARP messages. One of the common issues I have seen in Data Center is some server or device in the network sends continuous ARP packets which hits Control plane in the Aggregation layer which in turn causes network connectivity issue.
The above three points proves the Layer 2 domain isolation between data centers. If you have redundant Data Centers with Layer 2 extended without OTV, the above explained layer 2 issue which happens in one Data Center carries the same failure to the second data center which creates the question of what is the point of having two different Data Centers if we can not isolate the failure domain.
OTV natively supports HSRP localization with few command lines. This is a very important requirement in building Active/Active Data Center.
Even though your question is related to L2TP, OTV deserves the comparison with VPLS and those comparison will also be applicable for L2TP. The below link explains in detail...
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-574984.html
Thanks,
Anees.

Windows server 2012 Data Center with VDI configuration error message ( The remote session was disconnected because there are no remote desktop license servers available)

Dears,
I have two windows server 2012 Data Center and I configured (Virtual Desktop Interface)VDI on it's.
All my clients connected on both of servers by used Remote Desktop sessions ,5 months since.
Currently,when the clients is connected on the both of servers they received the following error:
"The remote session was disconnected because there are no remote desktop license servers available to provide license"
Kindly note, I installed windows Licenses Server Data Center on the both of servers.
Regards.

Hi,
Please let us know if you have purchased RDS CALs and install it in your RD licensing server.
Also, on RD Session host servers, please make sure that you have specified the license mode and point them to the RD licensing server.
Remote Desktop Services Client Access Licenses (RDS CALs)
http://technet.microsoft.com/en-us/library/cc753650.aspx
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
Hope this helps.
Jeremy Wu
TechNet Community Support

Ask the Expert: Scaling Data Center Networks with Cisco FabricPath

With Hatim Badr and Iqbal Syed
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco FabricPath with Cisco technical support experts Hatim Badr and Iqbal Syed. Cisco FabricPath is a Cisco NX-OS Software innovation combining the plug-and-play simplicity of Ethernet with the reliability and scalability of Layer 3 routing. Cisco FabricPath uses many of the best characteristics of traditional Layer 2 and Layer 3 technologies, combining them into a new control-plane and data-plane implementation that combines the immediately operational "plug-and-play" deployment model of a bridged spanning-tree environment with the stability, re-convergence characteristics, and ability to use multiple parallel paths typical of a Layer 3 routed environment. The result is a scalable, flexible, and highly available Ethernet fabric suitable for even the most demanding data center environments. Using FabricPath, you can build highly scalable Layer 2 multipath networks without the Spanning Tree Protocol. Such networks are particularly suitable for large virtualization deployments, private clouds, and high-performance computing (HPC) environments.
This event will focus on technical support questions related to the benefits of Cisco FabricPath over STP or VPC based architectures, design options with FabricPath, migration to FabricPath from STP/VPC based networks and FabricPath design and implementation best practices.
Hatim Badr is a Solutions Architect for Cisco Advanced Services in Toronto, where he supports Cisco customers across Canada as a specialist in Data Center architecture, design, and optimization projects. He has more than 12 years of experience in the networking industry. He holds CCIE (#14847) in Routing & Switching, CCDP and Cisco Data Center certifications.
Iqbal Syed is a Technical Marketing Engineer for the Cisco Nexus 7000 Series of switches. He is responsible for product road-mapping and marketing the Nexus 7000 line of products with a focus on L2 technologies such as VPC & Cisco FabricPath and also helps customers with DC design and training. He also focuses on SP customers worldwide and helps promote N7K business within different SP segments. Syed has been with Cisco for more than 10 years, which includes experience in Cisco Advanced Services and the Cisco Technical Assistance Center. His experience ranges from reactive technical support to proactive engineering, design, and optimization. He holds CCIE (#24192) in Routing & Switching, CCDP, Cisco Data Center, and TOGAF (v9) certifications.
Remember to use the rating system to let Hatim and Iqbal know if you have received an adequate response.
They might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community Unified Computing discussion forum shortly after the event. This event lasts through Dec 7, 2012.. Visit this support forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Sarah,
Thank you for your question.
Spanning Tree Protocol is used to build a loop-free topology. Although Spanning Tree Protocol serves a critical function in these Layer 2 networks, it is also frequently the cause of a variety of problems, both operational and architectural.
One important aspect of Spanning Tree Protocol behavior is its inability to use parallel forwarding paths. Spanning Tree Protocol forms a forwarding tree, rooted at a single device, along which all data-plane traffic must flow. The addition of parallel paths serves as a redundancy mechanism, but adding more than one such path has little benefit because Spanning Tree Protocol blocks any additional paths
In addition, rooting the forwarding path at a single device results in suboptimal forwarding paths, as shown below, Although a direct connection may exist, it cannot be used because only one active forwarding path is allowed.
Virtual PortChannel (vPC) technology partially mitigates the limitations of Spanning Tree Protocol. vPC allows a single Ethernet device to connect simultaneously to two discrete Cisco Nexus switches while treating these parallel connections as a single logical PortChannel interface. The result is active-active forwarding paths and the removal of Spanning Tree Protocol blocked links, delivering an effective way to use two parallel paths in the typical Layer 2 topologies used with Spanning Tree Protocol.
vPC provides several benefits over a standard Spanning Tree Protocol such as elimination of blocker ports and both vPC switches can behave as active default gateway for first-hop redundancy protocols such as Hot Standby Router Protocol (HSRP): that is, traffic can be routed by either vPC peer switch.
At the same time, however, many of the overall design constraints of a Spanning Tree Protocol network remain even when you deploy vPC such as
1.     Although vPC provides active-active forwarding, only two active parallel paths are possible.
2.     vPC offers no means by which VLANs can be extended, a critical limitation of traditional Spanning Tree Protocol designs.
With Cisco FabricPath, you can create a flexible Ethernet fabric that eliminates many of the constraints of Spanning Tree Protocol. At the control plane, Cisco FabricPath uses a Shortest-Path First (SPF) routing protocol to determine reachability and selects the best path or paths to any given destination in the Cisco FabricPath domain. In addition, the Cisco FabricPath data plane introduces capabilities that help ensure that the network remains stable, and it provides scalable, hardware-based learning and forwarding capabilities not bound by software or CPU capacity.
Benefits of deploying an Ethernet fabric based on Cisco FabricPath include:
• Simplicity, reducing operating expenses
– Cisco FabricPath is extremely simple to configure. In fact, the only necessary configuration consists of distinguishing the core ports, which link the switches, from the edge ports, where end devices are attached. There is no need to tune any parameter to get an optimal configuration, and switch addresses are assigned automatically.
– A single control protocol is used for unicast forwarding, multicast forwarding, and VLAN pruning. The Cisco FabricPath solution requires less combined configuration than an equivalent Spanning Tree Protocol-based network, further reducing the overall management cost.
– A device that does not support Cisco FabricPath can be attached redundantly to two separate Cisco FabricPath bridges with enhanced virtual PortChannel (vPC+) technology, providing an easy migration path. Just like vPC, vPC+ relies on PortChannel technology to provide multipathing and redundancy without resorting to Spanning Tree Protocol.
Scalability based on proven technology
– Cisco FabricPath uses a control protocol built on top of the powerful Intermediate System-to-Intermediate System (IS-IS) routing protocol, an industry standard that provides fast convergence and that has been proven to scale up to the largest service provider environments. Nevertheless, no specific knowledge of IS-IS is required in order to operate a Cisco FabricPath network.
– Loop prevention and mitigation is available in the data plane, helping ensure safe forwarding that cannot be matched by any transparent bridging technology. The Cisco FabricPath frames include a time-to-live (TTL) field similar to the one used in IP, and a Reverse Path Forwarding (RPF) check is also applied.
• Efficiency and high performance
– Because equal-cost multipath (ECMP) can be used the data plane, the network can use all the links available between any two devices. The first-generation hardware supporting Cisco FabricPath can perform 16-way ECMP, which, when combined with 16-port 10-Gbps port channels, represents a potential bandwidth of 2.56 terabits per second (Tbps) between switches.
– Frames are forwarded along the shortest path to their destination, reducing the latency of the exchanges between end stations compared to a spanning tree-based solution.
    – MAC addresses are learned selectively at the edge, allowing to scale the network beyond the limits of the MAC addr

When trying to start my Windows server 2008 R2 Data Center, I am getting "ramdisk device creation failed due to insufficient memory",

I have the following:-
VMWare workstation version 9 , with windows server 2008 R2 data center installed.
- I have installed the windows 2008 R2 inside the VM using an iso image.
- The host is windows 7.
I use to work well with the VM, but after adding a new VM to the same workstation . I start getting the following error when starting my old VM
ramdisk device creation failed sue to insufficient memory.
And on the windows boot manger screen they mentioned to :-
inset my windows installation dis and restart my PC.
click “repair your computer”
but not sure if this will fix the problem , baring in mind that the RAM assigned to the VM
is 24 GB & 80 GB hard disk.
The error is
Link.
so can any one advice what is causing this error?
Thanks

You might start by checking the RAM.
http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Simplest Data Center Interconnect?

Similar Messages

Maybe you are looking for