Data center failure Australia

Similar Questions

• Does anyone use this switches in a data center?

  I have an interest in the switches of SG-300 or SG-500 small businesses for small and moderate use.

  These are rack switches, but my question is if someone is actually using them in a rack of data center with public servers rather than catalysts?

  I understand that they are small business units, but they would hold the heat, vibration in a rack? How do they practice?

  I have an older catalyst, it costs less than new now that some of this small business ones, but I really need gigabit for internal LAN traffic ports and my DC tells me none has this unit to small businesses in their DC, it is not normal to use because they are not high-performance switches. IM worried to go small businesses who are actually Linksys device and not Cisco. I have some Linksys devices for personal use and at home and they are still in years. But I Don t know how they perform outside of this environment. I need to stay under $ 1000 per switch.

  They would fail in a few months? Can be clustered (2 switches) so if one fails the other take the network up until I have replace the failure? If so, I could take the risk, but one dying switch would be a disaster.

  My needs are low speed gigabit between the servers for backup and storage, but usually less 50 Mbit on the public Wan. These switches are really only for small office use or if they work very well with the servers in an institution? If so, I'd love to hear some real experiences, everyone I ask most of them said not to go with the switches, but then why are they still rack? They can´t be this bad or that they are not really designed for 24/7 usage?

  I'd appreciate some experiences with the amount of traffic you are passing on them and for how long (months) because I Don t know anyone use so far in a remote installation.

  Catalyst has shared backplanes and ASICS. SX300 and SX500 series does not work. If you do not need things like the protocols of the road (BPG, OSPF, IS - IS), VTP, CEF then these switches are very good.

  The switch has generally not hardware failure unless it is due to external voltage problems. A real failure, the MTBF is probably 4 or 5 years old, and I say this because the SX300 was not of the most and I've honestly never seen a die with the exception of power problems (storms, power surges, etc.). I saw ports to die only once and a while but that does not matter much because the switches are hardware to life with replacement free advanace...

  If you plan to use these switches as a Ridge with high throughput, especially in layer 2, I seriously doubt you'll break this thing.

  I am not yet sold on the robustness in environments of layer 3 but as a core for sub 300 people is a good switch. In response to another concept, the SX500X switches supports VRRP.

  -Tom
  Please mark replied messages useful

• FabricPath or OTV between two data center using Direct fiber cable

  Hello

  I have two data center both of them has the same equipment N7k, N5k and N2k, and we want the dataCenter being active/active, I'm really confused to use OTV or FabricPath characteristic, if someone can help me with my scenario and explain to me what is the best solution and advantage and disadvantage between OTV and PabrcPath.

  Many thanks in advance

  Hi Steven,

  No problem, I'll go through your points as completely as possible. I advise you to read more about these protocols, maybe if you have access to INE or similar, see their videos on this. I would also like to say again that I have not seen all documentation Cisco indicating that FabricPath to be used as a DCI.

  With regard to the way fabric you ask what follows...

   1. only can use it between two datacenters of you have more we can't, please correct me?

  No, you can use the path of fabric with more than two data centers, but even with OTV, you can use it with more than two data centers.

   2. HSRP localization can not be implemented as OTV. However You can have two differnet Gateways at the Data Center 1 and 2 using two different HSRP groups. If server is moved dynamically from, (i didn't understand this point can you please explain with example?

  OK, so this is a GREAT topic. Location of HSRP CAN be implemented with OTV, but cannot be implemented with fabric path. First hop redundancy protocols can be localized and is supported by Cisco with OTV, this basically allows the same default gateway to reside in two of your data centers providing the ACTIVE/ACTIVE configuration. So no matter where your VM is, they did not change their default, even if gateway your servers to move to the other datacenter.

  If we didn't have this, we would have only an active member of HSRP divided between DC and things would be extremely troublesome in regard to traffic flows. A virtual machine in DC2 VLAN needs to talk to host in VLAN B. But the default gateway is completely in DC1. So frame is sent to the ICD in DC1, then the gateway by default, routes packets VLAN B. This VLAN B lies in fact in DC2, so now it has to go all the way back to DC2. You get my point...? :)

  With localization happen only local to the domain controller. If all servers / VMS in the domain controller can speak locally to its "own" default gateway.

   3. unknown unicast flooding (can you give me an example?)

  Unknown unicast traffic is unicast packets/images with unknown destination mac address. By default, switches are flooding this type of traffic to all ports in the VLAN. With path of fabric that would take place during your DCI, but with OTV, it is all taken care locally, so massive savings on bandwidth here and it is much more effective.

   4. ARP optimization between Data Center (can you give an example regarding ARP optimization?)

  There is another function of OTV, which makes it far superior on the way of tissue. Essentially, we are reducing the volume of traffic passing through the transport infrastructure (i.e. ICD)

  When ARP, host in DC1 to host that responds in DC2, we use links and there is travel time of package that might be minimal, but is not the most optimal. OTV AED - or edge device spy ARP response and subsequently knows that this mapping exists from there. ARP takes place after the first Protocol, the EDA almost proxy ARP to DC1 so the ARP request locally does not have to travel to DC2.

   5. Typically two flows (Odd VLANs by OTV-VDC-1 and even vlans by OTV-VDC-2) carry the entire layer 2 traffic flow between the two Data Centes. Hence the load balancing the links is not efficient. ( (can you explain compare with FabricPath if you have example?)

  IMHO, it's bad and good. Balance the workload of the OTV if you have more than an AED on site. VLAN strange appointment via an AED, even numbered VLAN go through the other. Depending on traffic on VLANs, this could become unbalanced. Fabric used by all its links to mac addresses 'route' to the respective SID - ID switch she needs to do. So perhaps a better uniformity of split here.

   6. VLAN scalability for OTV is lower than FabricPath as of this content writing. (can you explain what this mean i didn't understand it)

  I completely disagree with this comment. I too do not understand.

   7. Resiliency of FabricPath network is better than OTV in some failure scenarios.(can me an example ?)

  I also disagree with that. Resilience of path of fabric could be same as OTV or perhaps better. However, my personal experience is that OTV fine tuning with things like BFD failover is much faster!

  Fabric is good because the control of aircraft ISIS and its operation is admirable, but could say the same for the OTV.

  Lets say one of the DCI links had to die, the transmission of the tissue path would continue through the other links, then perhaps for low latency, high frequency, environments that would be beneficial. OTV will change the EDA and re - learn mac, announced by other AEDS, addresses, but as I said, the time could be extremely minimal and tuning. This isn't a big deal, unless you need under second time convergence!

  I hope that I have answered your questions, I recommend use for your DCI OTV, use the path of fabric for your inside of local switching in your DC. This has been implemented repeatedly and the links I sent you the models validated Cisco also point out.

  Remember - fabric has been built to be a step towards TRILL, and replacement of protocols spanning-tree, OTV was built especially for the dci. They are both built and examples of specific design. It makes no sense to get these confused or mixed up, unless there is a real and pressing the case.

  Joel conclusion is right, use the right tools for the job. If the use case is good for the FP then OK, if not, OTV.

  Rcmnd - reading http://www.packetmischief.ca/2013/04/23/DCI-series-overlay-transport-vir...

  These are just my thoughts.

  Bilal (CCIE #45032)

• Need to create a report across data center that summarizes each cluster

  I created a few reports of various kinds, layers to multiple views and used filters for will only display me specific data.  However, I don't find a way to summarize or failure, a report by a resource of the child.

  To be precise, I'm looking to get information about the data at the data center or vCenter level stores, grouped by cluster.  Currently, I can obviously pull 53 different reports and getting these data on a per-cluster basis, but I want to be able to do is have a summary of each cluster in a single report.  Currently, the report is perfectly functional vcenter down to a host, but it displays each individual data store and the summary only I can give is all grouped together, and is not an indication that data warehouses are in clusters.

  Is there a way to do this?

  I would like that the report looks simply:

  Data Center

  Group 1

  Data warehouses

  Summary

  Group 2

  Data warehouses

  Summary

  and so on...

  I am currently on vROps 6.1.

  You can do things with the summary views and the bubble to the top a few statistics by using Supermetrics in some cases, but the possibilities for nesting are today a bit limited in terms of nesting of data visually in views. Of data are what kind of data from the warehouses you trying to show?

• Data Center shutdown Complete weekend activity...

  Dear team,

  In our environment, we have 22 esx host 4 storage san, 4 fabric switches, network switches 4. every weekend, there is problem of complete power failure will be there, so each client weekend for full on stop data center, so we install full stop that I just want to know what will be recommended for this bee and as precaustion to take before making this kind of activity, so need your help on the same

  Will it work this way, if we turned off the entire infrastructure,

  (1) fist take the glance of each virtual machine power on each host
  (2) then take snap of all the SAN data store that r connected on each host are
  (3) make the snap of networking architecture
  (4) stop each virtual machines on an esx host,.
  (5) stop ESX host
  (6) stop SAN storage
  7-stop Fabric Switches
  (8) stop all network switches

  While switch on/off the infrastructure unit will it work that way,

  (1) power on network switches, after 5 minutes
  (2) after 5 minutes on the fabric power switches
  (3) power storage SAN, after 10 minutes
  (4) power on all ESX hosts after 45 minutes
  (5) power on all the virtual machines on all ESX hosts
  (6) cross check all works very well.

  Correct if I'm wrong, please help me on the same.

  Concerning

  Mr. VMware

  every weekend he comes from complete power failure

  The steps you mentioned certainly works, but I don't see a reason for snapshots. Better make sure that you have a good backup in place. I guess you also have an exact plan on the order in which the power and off the virtual machine.

  On the other side, it may be interesting to find out the reason for the failure and eliminate it or think of a suitable UPS system to avoid this procedure.

  André

• Best practices installation CARS in two areas of data center?

  Data Center has two distinct areas.
  In each area, we have a storage system and a rac node.
  
  We will install RAC 11 GR 2 ASM.
  
  For data, we want to use diskgroup + DATA, normal redundancy mirrored on two storage systems.
  
  CRS + vote, we want to use diskgroup + CRS, normal redundancy.
  But for diskgroup CRS + vote with normal redundancy, there are 3 LUNS and we have only 2 storage systems.
  In my view, that the third logical unit number is necessary to avoid situations of split brain.
  
  If we put two LUNS to storage lun #1 and the other for storage #2, what will happen when storage faills #1 - it means that two of the three disks for diskgroup + CRS are inaccessible?
  What will happen when all the material in the #1 box fails?
  Is the human intervention: at the time of the failure, which #1 area rises again?
  
  Is there a best practice for configuration 2-zone 2-storage cars?
  
  Joachim

  Hello

  With regard to the vote of the files are concerned, that a node must be able to access more than half of the files with the right to vote at any time (simple majority). In order to be able to tolerate failure of n files in vote, need at least 2n + 1 configured. (n = number of files with voting rights) for the cluster.
  The problem in a stretch cluster configuration, is that most of the facilities use only two storage systems (one on each site), which means that the site that hosts the majority of voting records is a potential single point of failure for the entire cluster. If the storage or the site where the files of n + 1 vote is configured fails, the entire cluster will go down, because Oracle Clusterware will lose the majority of the files.
  To avoid a complete cluster failure, Oracle will support a third vote file on a cheap lowend, standard NFS mounted device somewhere in the network. Oracle recommends the file NFS vote on a dedicated server, which belongs to a production environment.

  The white paper below allows you to accomplish:
  http://www.Oracle.com/technetwork/database/Clusterware/overview/grid-infra-thirdvoteonnfs-131158.PDF

  Also with regard to the configuration of the vote and OCR (11.2), when you use ASM. How they should be stored?
  I recommend that you read:
  {message: id = 10028550}

  Kind regards
  Levi Pereira

• In another data center replication sites

  Hello...

  I have a few excellent hot press web templates - residing in the data center in the United States.

  It is - I'm in Australia and want the template applied to the Australian data center, and it seems that it's not possible.

  When you replicate a site (in partnership), it of great, takes about 3 seconds.

  BUT.

  It is automatically default to the location of the new the same site where the model.

  Is there a way to get around this?

  The creators of model that load in the system have an option to download to a defined data center?

  See you soon

  Dave

  Hi again, Dave ;-)

  Yes, they can. TribeVita offers a menu to select the data center when you order your model. Not sure why gurus don't. Maybe in the notes where you enter your partner info note you want AUS Datacenter.

  In the meantime, you should be able to contact support, and they can probably fly over it for you.

• I would take my existing Server 2008 and upgrade to Server 2012 and the purchase of a virtual server in a data center

  Original title:

  Virtualization server 2012

  I got too many answers to this question. I need the correct answer before buying any CALs galore.

  I would take my existing Server 2008 and upgrade to Server 2012 and the purchase of a virtual server in a data center. I have 25 computers that need to communicate with the server throughout the day, all the different machines. I want to know the best option without breaking the Bank. I permit the data center included in the package to my server.

  Try asking in the Windows Server forum:
  http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

• I have windows xp. The fix for microsoft data center could not scan my computer because it says that an error has occurred

  I just installed the fix for microsoft data center and I couldn't run a check on the various problems because they said and the error has occurred.

  Hi Carroll,

  If the problem is just related to the execution of the Microsoft Fixit tool, I suggest that you post your question on the Forums of Microsoft Fixit.

  Microsoft Fix it Center Forums

• Number of dashboards for managing a data center: how?

  Some time ago we had a number as the average data center uses 37 dashboards and a management console.  But I have no idea where this came from, ir even if it's a real number.  Anyone of you have any ideas or sources?

  How about an average of 20?

• Deliver the addition of new set of switches stacked as an extension to the network in another data center building

  Hello

  I was wondering if someone can help me, I am a humble sysadmin with no real network admin training.

  I have the following Setup to work in a rack in our data center.

  2 x Dell Sonicwall NSA2400
  2 x stacked switches Dell Powerconnect N5524

  A Sonicwall is connected to each switch (active-passive)

  Every Dell server has 2 x nics in servile failover mode, one of each network card connected to each switch

  This is done to allow a full redundancy for network, cable, switches and Firewall interface cards. It works well.

  The above mentioned rack is now full and we ordered a new rack that is in a different datacenter of construction on the same site. We decided to buy another set of stacked switches and _extend_ (no battery) these via optical SPF on the rack on the other.

  The idea is that we still have the switch fault tolerance but link to two grids through 10 GB. The new switches are 2 x Dell Powerconnect N2048 and have been implemented stacked with any connected devices.

  I have implemented SPF ports on both switches to be a junction ports and connected the two sets of switches, unfortunately our site went offline, our alert went ballistic and no servers could not talk to each other!

  Quickly, I unplugged the new switches and after a worrisome 10 alerts deleted seconds and the site is back online.

  I don't know why this has happened and reflected on the STP parameters that my googleing seem well. I don't know I'm missing something basic.

  I'll post a framework and a diagram in a follow-up post

  Which is no doubt tree covering the shot weight. It is a good idea to assign lower priority to the main switch. Generally, your root switch will be the one that plugs into the firewall. Definition of priority on the main switch to 4096, it will make the root switch. So as you work your way through different layers of the network, increase the priority. Access layer switches can be left by default.

  I would also check the physical connections for loops. In situations where you have multiple connections switch, make sure that these ports are configured in a SHIFT.

  Keep us informed.

• Mini Data Center design

  Hello

  I have a few doubts about the best solution for the design of a mini data center.

  In the data center, there is a 6500 with FWSM module installed, there are a few created vlans, each of them in the fwsm module. For example, a back-end to communicate with a server in the front end server must always go through the firewall. My question is, these flows through the firewall that does not reduce the speed of communication?

  What is the best practice, just to pass the communications with the Wan in the firewall, and the communication of vlan between front-end and back-end is only set up to 6500?

  Thank you

  Although security is a subject with many facets. How to fix you can do things depends on part on your needs to provide the functionality for the application to work.

  If the database servers do not need to Internet, just keep on a VLAN internal only and do not allow to be routed even initialized requests internally by. If the database servers have need to talk to the Internet (why is this really necessary would be a good question to ask - a bastion host could be used instead?), then lock the rules in the FWSM with an access list that allows only addresses and ports as necessary for the minimum necessary service work.

  In any scenario, your should analyse your servers (for example with Nessus) and harden to reduce their exposed attack surface. Additional measures could include things like Tripwire on the servers to block further down. Audit of system access - and actually looking at the newspapers! -also helps. Tools such as iptables on Linux or Windows Firewall servers must be a lever to allow only the communications in and out of the box as necessary so that it can perform its designated function.

• Branch 5505, 1 circuit ISP, Dual - peer VPN Configuration for Data Center & Track Options

  Hi all

  I have a data center with two lines of ISP redundancy and two ASA 5520 for redundancy VPN to my branches.  Each of my branches has 1 ASA 5505 with a base license and 1 ISP circuit. Currently all my VPN tunnels are built for data center main circuit ISP only, so if one goes down, I'm toast.  I need to fix this. Problem is, I don't know how I can control failover on 5505 with 1 single line branch.  Please see my picture for an example of how he looks at it right now.

  So the problem is that the data center LAN my branch has to go to is identical regardless of which circuit of data center is in the. And I know the ASA rules say only 1 VPN tunnel can be active at a time if flow are the same.  So in this case, I know you usually do:

  card crypto outside_map 1 set 12.x.xxx.20 50.xxx.xx.190 counterpart

  and then configure route followed to control when cut down the primary counterpart and turn back up by peers. But where I have only 1 ISP on the side of the branch, I'll only have 1 default route: route outside 0.0.0.0 0.0.0.0 3.3.3.2 1, will be used that the active end counterpart is the primary or the secondary data center. Also, since I did not have a second track, I can't configure followed on the main road with an SLA that defines the trigger conditions, because there is nothing to ensure the follow-up of the routing.

  How is - a would handle a situation like this? Are there other features that can be taken off the roads?  I really need to be able to define "num-package 5 ' in ALS so my sites are not beat all day, but once again, without something to follow, I can't really set up a meaningful SLAS.  Any help is appreciated.

  Thanks for the additional explanation. It helps to clarify your environment. EIGRP running on the Remote would be a nice option, but I'm not sure that it is supported on the SAA. I ran EIGRP to remote peers using IOS routers (using the two ACCORD with IPsec and VTI tunnels tunnels) and it was very effective. But on the SAA, I believe that we must seek an alternative.

  It seems to me that using reverse road Injection as part of your VPN site-to-site should work. With IPP the ASA inserts a static route to remote resources when the VPN tunnel is negotiated and traffic can flow. If you redistribute the static in EIGRP EIGRP then must learn the ways of any ASA a currently active tunnel. And who should provide the dynamic rollover you need.

  HTH

  Rick

• IPS in data center

  4270 IPS connected to the distribution in the data center, each with each 6509, now the question is how to be redundancy/failover works in inline and out-of-use of the band.

  Yes, and especially any configuration change you need to do (such as signature tuning) must be made each individual sensor unless you have the CSM. This is quite annoying, your signature, it seems you work for a gold partner, message to Cisco, to stop the lame marketing stuff "we don't need regular tipping STP/ECLB enough" and ask them to provide an adequate failover.

  Cordially :)

  Farrukh

• Evolution of the data center: N7k or C6500

  Hello

  I am curretnly studying how our data centers evolve.

  For physical physical architecture:

  -We have 2 data centers, L2 interconnected at 10 Gbps.

  -On each data center, 2 x C6500 serve basic and distribution at the same time.

  -The access layer is to C3750G, connected to the chassis base with 3x1Gbps etherchannels.

  -No server rack blade for the moment.

  For the logical aspect:

  -L2: we use STP lying on the 2 DC

  -L3: Core are connected directly to the MPLS cloud. We use the VRF.

  The next evolution of the server would be to replace the stand-alone servers by blade, connected with 10 Gbps.

  I was hesitant on how to improve the current design, and I'm not sure the + and - 2 (except that Nexus need investment)

  (1) keep the C6500 and:

  -Add maps to 10 Gbps on the C6500 (16-port cards)

  -use VSS on the two site to simplify the design STP (even though we have had no problems with it so far)

  (2) replace C6500 by Nexus7K for greater flexibility with 10 Gbps

  (3) as an option, add a distribution layer N5K which would simplify the wiring and allow a possible evolution FCoE (in this solution, I would keep C6500 as base or evolve N7k).

  What do you think?

  Thank you

  P.

  This is going to be a very controversial topic.

  Let's not talk about budget here because it could become very dark.

  The 6500 Sup720 or Sup2T (I still prefer the latter), is very good when you aggregate a significant amount of some 10 Gbps and 1 Gbps and a handful of 40 Gbit/s.

  The Nexus family is very good when you want to consider a few 100 Gbit/s, but a significant amount of 10 Gbps.  NEXUS is also the way to go if you want to connect your Fibre Channel switch DC as Nexus will support 1, 2, 4 - and 8 Gbps FC.

  Nexus 7 K can support 100 Gbps (two per card online), 40 Gbps (six per card online) and of course 10 Gbit/s (up to 48 by card online).

  Very quickly, the will be some service modules that will be introduced for the Nexus 7 K.  They are WAAS, ASA and a NAM.

  There will be life with the 6500?  In some cases, Yes.  It is still is not clear if ALL the 6500 service modules will evolve into the Nexus.  In my view, the three modules, I have just mentioned is to "test" the waters.  Once the momentum has been achieved, the others could follow.

  There are rumours abound that there could be a possibility of Nexus 2 K which will support the PoE.

  Attached something for your perusal.