EqualLogic - connection load balancing

grpparams conn-balancing disable

Other settings having impact

TCP Offload Engine v nastavení karet – OFF

Flow Control – On resp. Auto

Ze sitovek odstraneny nepotrebne bindy a protokoly: Client MS Network, QOS, File&Print a IPV6

Nastaveny JUMBO frames

Instalace MS KB974909 (The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer)

Switche               – STP off (can cause port off up to 50sec)

                               – RSTP on (can cause port off up to 12sec), je akceptovatelne to se tusim nechalo ON

Restore Point Simulator

http://rps.dewin.me/

Backup/Restore 

Force10 Scheduling the script

Below is the example how to use scheduler in Force10 FTOS 9.7+

FTOS 9.7

411: Release-To-Web of Dell Networking OS 9.7 for Data Center Switches Dell Confidential – For Internal Use Only Overview Dell Networking OS 9.7(0.0) delivers many new features such as support for Open Networking platforms including S6000-ON, S6000 Stacking, new automation features like Puppet, increased scale, VRF and VLT enhancements, and support for new hardware (future launches such as the 10GBaseT module for S5000 and new optics). Note: for RTS actual shipping time will vary as 9.6 stock exhausts. Features and Updates This release adds the following new features: VRF Enhancement: ü  VRF aware IPv4 multicast protocols ü  Support for IPv6 unicast routing protocols per VRF ü  Support for IS-IS for v4 and v6 VRF ü  Route leaking across VRF instance using dynamic protocol routes ü  Introduce VRF support on Z9500 VLT Enhancement: ü  Support PVST+ protocol in VLT context to interop with existing ü  PVST enabled networks ü  Support for Q-in-Q (aka VLAN stacking) in VLT context to provide multi-tenancy in hosted service provider networks Scaling Improvements: ü  OS 9.7 supports a new Forwarding table mode which increases the number ü  of IPv4 routes to 128K. This feature is applicable on S6000 and Z9500 ü  Increase in number of VRF from 64 (current) to 510 ü  2500 L3 vLANs ü  Network Load Balancing (NLB) cluster increased from 8 (current) to 64 clusters. Enhancements to MXL/IOA ü  F port support on FC Flex IO - Enables direct connectivity to FC equipment through Fibre channel ports provided by FC Flex IO optional module rather than through a FC switch ü  Secure management mode support on MXL to enable Federal certifications ü  like UCR and CC for MXL ü  New Hardware Support ü  Dell Networking OS 9.7 supports S6000-ON platform. With this support, customers have the option of choosing one of the supported alternate operating systems or Dell Networking OS. ü  Dell Networking OS 9.7 supports 12x10GBase-T module on S5000. Z9500 Enhancement: This features enables customers to deploy Z9500 with predictable end-to-end RRoCE performance and DCB lossless Ethernet support RRoCE Support ü  ECN Enhancement ü  Dynamic Load Balancing ü  VLT scaling – Up to 512 LAG interfaces supported in a VLT config Open Automation Enhancement ü  BMP: Supported on IOA, Best practices upgrades: Automated failback to previous image and configuration if the SW upgrade is not committed ü  Scripting and CLI automation: Ruby, Support for NFS, CLI command to copy OS images between partitions, TCL script on IOA ü  DevOps: Puppet with support for NetdevOps model (Hostname, Physical Interface, VLAN, Layer 2 Interface, Link Aggregation (static)) ü  REST: Support for: Static Routes, ACL, IPv6, WECMP, IP tunnel Other Features: ü  S6000 stacking (up to 6 members) ü  Dynamic config for Fan-out of 40G ports to 4x10G – Supported on S6000 and Z9500 ü  LACP Link fallback on IOA ü  BGP Link bandwidth and Weighted ECMP support for unequal cost load sharing ü  OpenFlow 1.3 Compliance ü  IPv6 RA Guard ü  DHCPv6 Snooping ü  Ingress SFLOW ü  MIB support per VLAN ü  Optics support – SFP+ ZR, QSFP+ LM4 support on S4810, S4820T, S5000 (ZR optic launch pending) How to Download Dell Networking OS 9.7(0.0) software is currently available for download to customers with an active Support Contract at the following Dell Networking Data Center iSupport download site. URL (requires login credentials): S-Series: https://www.force10networks.com/CSPortal20/Software/SSeriesDownloads.aspx ZSeries: https://www.force10networks.com/CSPortal20/Software/ZSeriesDownloads.aspx MXL/IOA: https://www.force10networks.com/CSPortal20/Software/MSeriesDownloads.aspx Shipping Timeline The factory will begin cutting in 9.7 in the coming months, however stock in the hubs will still be 9.6 for some time.  Please expect your customers to receive 9.6 in the near future. Exception Dell Networking Z9000 NOT supported

Same MAC address on DNOS9 switches for switch-internal and OOB/management interfaces

Many times in this group questions came up why the S-Series and MXL/MIOA switches do use the same burnt in MAC addresses for the switch internal (data plane) and management interface interfaces and the problem that causes; especially on the MIOA/MXL switches.

Many different examples have been given when this gives problems for customers, especially the people who have used PowerConnect M-series switches earlier and suddenly have huge packet-loss when they try to connect to the switch management – all being caused by the same MAC address being used by vlan-interfaces and OOB/management interfaces.

Also on rack switches like S4810 or S4820 people run in same problem even if they have a dedicated OOB LAN but that does terminate on same core and the VLAN is also available on the core.

That it might be hard to change on S-series I can follow as there might be only 1 burnt-in MAC address available per switch; but on MXL and MIOA there are at least 3 MAC addresses available/reserved: so changing the address used by the physical management interfaces should be pretty simple and straightforward and the impact of the change for installed base should be minimal: only if they would use static ARP’s or similar a very small number of users might have issues: but that can be avoided by making it configurable via CLI command like:

!

config

!

interface ma0/0

mac-address  alternative    #this would use next available burnt-in MAC address or

no mac-address  alternative   # this would use same MAC on ma0/0 as on any SVI inside the switch  

mac-address user nn:nn:nn:nn:nn   #this would make it user-configurable, which could be used on older hardware that only has one burnt in MAC address available

end

!

I’m really surprised that all these discussions here in the past only led to one single Feature Request from Harvey Lang for the S4810: after reading all the communication in these groups I would have expected many more FR’s on this subject and for sure also on MIOA/MXL.

As I –as tech-support- can’t open FR’s I have to rely on commercial colleagues to open FR’s: so if you do think it would greatly help your customer if we can change the MAC address used for the management interfaces please do open Feature requests for your customers situation. Without requests from sales it will never be changed.

Regards,

Jan Tonkens

Enterprise Technical Support Advisor

Brocade Certified FCoE Professional

Dell | EMEA Solutions Support Team

phone: +353 12792295

mail: jan_peter_tonkens@dell.com

Dell Inc. Innovation House, Cherrywood Science & Technology Park, Dublin, Rep of Ireland

Recovering a Locked Administrator Account in Storage Center OS v6.5

Tech Tip: Recovering a Locked Administrator Account in Compellent Storage Center OS v6.5
If all accounts are inaccessible because they have been disabled or locked‐out, use this procedure to reestablish a local Administrator account and reset passwords.

Prerequisites
This procedure requires a USB device that contains a partition table with one partition formatted with an MSDOS/FAT32 filesystem. USB devices vary by vendor as to whether they are formatted with or without partitions. Use Windows disk management or other third‐party tools to create a partition if the USB device does not have an MSDOS/FAT32 partition.

Steps
1 Create a text file containing the following line of text:
unlock <username>
where <username> is typically the Admin username. The Admin account is always on the system and it has the required Administrator privileges to reset passwords.

2 Save the file and name it:
unlock.phy

3 Copy the file to a MSDOS/FAT32 formatted USB drive.

4 Insert the USB drive into a port on the lead controller. When the media is recognized, System Manager allows the specified account to log on.

5 Log on to System Manager using the account specified on the USB drive. The password cannot be blank, but any text entered will be ignored.

6 Unlock locked accounts.

7 Reset passwords on accounts.

8 Remove the USB drive from the port.

Oracle licensing

Gerry is correct, Oracle *explicitly* does NOT support BIOS core disabling for the purposes of Oracle core licensing, since the cores can easily be re-enabled after initial installation config.  Likewise, core restriction via VMware/Hyper-V/KVM are also NOT recognized for licensing purposes, for the same reason.   There are some customers  who have struck one-off side-deals with their Oracle reps to recognize BIOS core disabling, but there is not an official lic. policy allowing this.  To avoid future audits = *extremely* expensive Oracle lic. "true-ups" I wouldn't even suggest this option for customers to pursue unless they can get that side deal in writing from their Oracle reps.

To restrict cores for Oracle lic. purposes, one must either:

* use fixed lower core count/higher clockspeed processor models e.g. E5-2637v3 4C@3.5GHz
* use OracleVM, ie. Oracle's Xen-based hypervisor.  OracleVM implements a feature called "core binding" aka "core pinning", which locks specific CPU core serial #'s to VMs, so one can create e.g. 2C VMs which cannot be modified, i.e. cannot add CPU's without destroying/recreating the VM from scratch, and therefore are recognized for Oracle lic. purposes.

From a market best practice perspective, many customers who've already standardized on VMware/Hyper-V etc. simply opt to pay the full core count cost for the system, then load as many Oracle workloads as possible onto the system/cluster, however for customers with smaller Oracle installs, OracleVM is a quite useful to control core costs, and has quite low compute perf overhead.

Peter Bailey
ET- Linux/Solaris/Oracle
512.800.9792
________________________________________
From: Gonzalez, Gerry
Sent: Friday, February 13, 2015 7:47 AM
To: Drunen, Marcel van; Sharma10, Ashish; Akkalyoncu, Serhat; Blades-Tech; BladeMasters
Subject: RE: Is it possible for Dell to disable cores?

Dell - Internal Use - Confidential
All,

From my experience within my set of US Global accounts, Oracle does NOT sanction disabling cores on X86 systems to forego licensing cores…Yes, once the cores are disabled they are electrically isolated and can NOT be seen by the OS until the next reboot but Oracle ONLY allows certain x86 systems that support hard partitioning  as well as RISC and SPARC systems leveraging LPARs to support disabling cores…

That said, I do have an account that worked a deal with their Oracle rep but that is on an account by account basis…Speaking from experience, I attempted to leverage this arrangement at another account and they were audited and were told they would have to entitle ALL cores in their Dell servers whether they were turned on or off…Moral of the story…Let your account take the fight to Oracle and NOT you…Dell will NOT officially support this due to our relationship with Oracle and they advise to move the customer to OVM and OEL to mitigate licensing costs…however, most customers will NOT want to stand up another virtualized environment to satisfy Oracle licensing…

Attached is the Oracle document explaining how Oracle defines core partitioning as Soft or Hard…Dell would fall under the ‘Soft’ definition according to Oracle although Intel would support that when cores are turned off in our systems, they are electrically isolated and cannot be used until they are turned back on in the bios on a subsequent reboot…

This is one of the reasons Intel continues to build and provide low core count processors, so your approach of using 4C procs is the way to go…

Don’t want to ramble here (as this brings up OLD scars) but if you would like more information just let me know…

Thanks…

Gerry Gonzalez
Enterprise Domain Specialist - Global - SouthEast
Dell Enterprise Products and Solutions
305-274-8982 Office
305-987-4395 Cell
305-274-0503 Fax


How am I doing? Please contact my manager, Richard Schultze at Richard_Schultze@Dell.com<mailto:Richard_Schultze@Dell.com> with any feedback.



From: Drunen, Marcel van
Sent: Friday, February 13, 2015 7:14 AM
To: Sharma10, Ashish; Akkalyoncu, Serhat; Blades-Tech; BladeMasters
Subject: RE: Is it possible for Dell to disable cores?


Dell - Internal Use - Confidential
Hi Ashish,

This is news to me. Can we get an official statement from Oracle about that?

Using one of the frequency optimized CPU’s will be a better choice most of the time because of the higher frequency. If disabling cores is not allowed, than the CPU’s with the lowest amount of cores are the E5-2637v3 (@3.5 GHz) and E5-2623v3 (@3.0 GHz). Both have four cores, so if the customer has a 8-core license these will be the CPU’s of choice in a dual socket Intel system.

Kind regards,

Marcel van Drunen
Senior Manager EMEA HPC
Dell ESG
+31-206744313

From: Sharma10, Ashish
Sent: Friday, February 13, 2015 12:26 PM
To: Akkalyoncu, Serhat; Blades-Tech; BladeMasters
Subject: RE: Is it possible for Dell to disable cores?

Hi Serhat,

You can go and disable the cores in the bios and OS will see only the enabled cores.

One of my customer had taken a letter from Oracle that their licensing will be only for active cores and he was able to leverage this feature.



Thanks & Regards

Ashish Sharma
Enterprise Technologist
Dell |Enterprise Solution Organisation
+919833630569
Ashish_sharma10@dell.com<mailto:Ashish_sharma10@dell.com>



From: Akkalyoncu, Serhat
Sent: Friday, February 13, 2015 4:30 PM
To: Blades-Tech; BladeMasters
Subject: Is it possible for Dell to disable cores?


Dell - Internal Use - Confidential
Hi,

I have a RFP and in one of the requirements it says “There should be a possibility to disable physical cores in server”. Is it possible? Our customer will use these systems in Oracle deployment and so because of the core licensing they want to disable cores.

Best Regards,

Serhat Akkalyoncu
CSE (Customer Sales Engineer)
Dell | EMEA Emerging Markets / Turkey
Office : +90 216 570 8700, mobile : +90 532 426 2386, faks : +90 216 570 8798
e-mail :  serhat_akkalyoncu@dell.com<mailto:serhat_akkalyoncu@dell.com>
adress:  Icerenkoy mah. Askent sok. no:3/A Atasehir / Istanbul PK:34752 Turkey