DOCSLIB.ORG

USM Anywhere Deployment Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

USM Anywhere™ Deployment Guide Copyright © 2020 AT&T Intellectual Property. All rights reserved. AT&T, the AT&T logo and all other AT&T marks contained herein are trademarks of AT&T Intellectual Property and/or affiliated companies. All other marks are the property of their respective owners. Updated November 24, 2020 2 USM Anywhere™ Deployment Guide Contents About USM Anywhere Deployment 6 USM Anywhere Deployment Overview 7 USM Anywhere Architecture 7 USM Anywhere Data Security 10 USM Anywhere Log Data Enhancement 12 USM Anywhere Deployment Types and Scalability 17 USM Anywhere Deployment Requirements 19 USM Anywhere Deployment Process 20 USM Anywhere Updates 21 USM Anywhere Sensor Deployment on VMware 23 About VMware Sensor Deployment 24 Requirements for VMware Sensor Deployment 25 Creating the VMware Virtual Machine 29 The OVF Package Is Invalid and Cannot Be Deployed - SHA256 Error 37 USM Anywhere Setup on the VMware Virtual Machine 38 VMware Sensor Connection to USM Anywhere 40 Completing the VMware Sensor Setup 43 USM Anywhere Sensor Deployment on Microsoft Hyper-V 56 About Hyper-V Sensor Deployment 57 Requirements for Hyper-V Sensor Deployment 57 Create the Hyper-V Virtual Machine 60 USM Anywhere Setup on the Hyper-V Virtual Machine 70 Hyper-V Sensor Connection to USM Anywhere 72 Completing the Hyper-V Sensor Setup 75 USM Anywhere Sensor Deployment on AWS 88 About AWS Sensor Deployment 89 USM Anywhere™ Deployment Guide 3 Requirements for AWS Sensor Deployment 90 Deploying the AWS Sensor 96 Setting the AWS Sensor Connection to USM Anywhere 99 Completing the AWS Sensor Setup 103 Enabling Connections in an AWS VPC 110 Mirroring VPC Traffic with an AWS Sensor 111 Adding an Additional Sensor for Other AWS Accounts 114 Configure Amazon GuardDuty for the AWS Sensor 117 AWS Log Discovery and Collection in USM Anywhere 118 USM Anywhere Sensor Deployment on Microsoft Azure 131 About Azure Sensor Deployment 132 Requirements for Azure Sensor Deployment 134 Deploying the USM Anywhere Sensor from the Azure Marketplace 138 Setting the Azure Sensor Connection to USM Anywhere 141 Completing the Azure Sensor Setup 145 Creating an Application and Obtaining Azure Credentials 159 Adding Another Sensor for Other Azure Subscriptions 162 Azure Log Discovery and Collection in USM Anywhere 165 USM Anywhere Sensor Deployment on Google Cloud Platform 180 About GCP Sensor Deployment 181 Requirements for GCP Sensor Deployment 183 Preparing Your GCP Environment for Sensor Deployment 186 Deploying the GCP Sensor 190 Setting the GCP Sensor Connection to USM Anywhere 191 Completing the GCP Sensor Setup 195 Adding Another Sensor for Other GCP Subscriptions 205 GCP Log Discovery and Collection in USM Anywhere 207 Network Setup and Configuration 216 Configure Network Interfaces for On-Premises Sensors 217 Configure USM Anywhere to Receive ERSPAN Traffic 227 Port Mirroring Configuration on Network Devices 228 Granting Access to Active Directory for USM Anywhere 239 4 USM Anywhere™ Deployment Guide Data Sources and Log Processing 251 Log Collection from Your Data Sources 252 File Integrity Monitoring 297 Running Active Directory Scans 306 Alarm and Event Notifications 309 Sending USM Anywhere Notifications to Slack 310 Sending USM Anywhere Notifications to Datadog 320 Sending USM Anywhere Notifications to PagerDuty 327 Sending Notifications Through Amazon SNS 334 Troubleshooting and Remote Sensor Support 343 Checking Connectivity to the Remote Server 344 Creating a Remote Support Session 346 Collecting Debug Information 349 View Network Testing Information 351 Retrieve Unique Identifier Information 355 USM Anywhere™ Deployment Guide 5 About USM Anywhere Deployment USM Anywhere is a software as a service (SaaS) security monitoring solution that centralizes threat detection, incident response, and compliance management across your on-premises, cloud, or hybrid environments. Data collection, security analysis, and threat detection are centralized in the AlienVault Secure Cloud and provide you with a single view into all of your critical infrastructure. This section includes the following topics. USM Anywhere Deployment Overview 7 USM Anywhere Architecture 7 USM Anywhere Data Security 10 USM Anywhere Log Data Enhancement 12 USM Anywhere Deployment Types and Scalability 17 USM Anywhere Deployment Requirements 19 USM Anywhere Deployment Process 20 USM Anywhere Updates 21 USM Anywhere™ Deployment Guide 6 USM Anywhere™ USM Anywhere Deployment Overview USM Anywhere consists of a modular, scalable, two-tier architecture to manage and monitor every aspect of cloud security. Software sensors collect and normalize data from all of your on-premises and cloud environments, while USM Anywhere provides centralized cloud security management, analysis, correlation, detection, alerting, log management, and reporting. Purpose-built USM Anywhere Sensors deploy natively into each environment and help you gain visibility into all of your on-premises and cloud environments. These sensors collect and normalize logs, monitor networks, and collect information about the environments and assets deployed in your hybrid environments. USM Anywhere™ USM Anywhere Architecture USM Anywhere has a modular and scalable two-tier architecture. 7 USM Anywhere™ Deployment Guide USM Anywhere Architecture Diagram Tier 1 — USM Anywhere Sensors and Agents USM Anywhere Sensors deploy natively into each environment and help you gain visibility into all of your on-premises and cloud environments. Sensors collect and normalize logs, monitor networks and collect information about the environments and assets deployed in your hybrid environments. Sensors are a key component of the USM Anywhere solution. They operate either on-premises or in the cloud, performing the following tasks: l Discovering your assets. l Scanning assets for vulnerabilities. l Monitoring packets on your networks and collecting data. l Collecting log data and normalizing it before securely sending it to USM Anywhere. USM Anywhere Agents deploy on your network host and provide the following: l Endpoint detection and response l Network asset monitoring l File integrity monitoring (FIM) l Log collection USM Anywhere™ Deployment Guide 8 Tier 2 — USM Anywhere Cloud USM Anywhere receives the previously described data sent to it by the USM Anywhere Sensor and uses it to provide essential security capabilities in a single SaaS platform: l Centralized system security management l Log data analysis and correlation l Detection l Alerting l Log management l Reporting USM Anywhere also integrates log management and securely retains raw logs long-term for forensic investigations and compliance mandates. AWS Deployment Regions The USM Anywhere cloud instance will be deployed in one of the following AWS endpoint regions based on your location. The following table lists the code and name of each region: Supported AWS Regions Code Name Reserved Static IP Address Blocks ap-northeast-1 Asia Pacific (Tokyo) 18.177.156.144/28 ap-south-1 Asia Pacific (Mumbai) 3.7.161.32/28 ap-southeast-2 Asia Pacific (Sydney) 3.25.47.48/28 ca-central-1 Canada (Central) 3.96.2.80/28 eu-central-1 Europe (Frankfurt) 18.156.18.32/28 eu-west-1 Europe (Ireland) 3.250.207.0/28 eu-west-2 Europe (London) 18.130.91.160/28 sa-east-1 South America (São Paulo) 18.230.160.128/28 us-east-1 US East (N. Virginia) 3.235.189.112/28 us-west-2 US West (Oregon) 44.234.73.192/28 us-gov-west-1 AWS GovCloud (US-West) 3.32.43.32, 3.32.43.33, 3.32.43.34, 3.32.43.35 9 USM Anywhere™ Deployment Guide USM Anywhere™ USM Anywhere Data Security As a security-first organization, AT&T Cybersecurity makes your data protection and privacy a top priority. USM Anywhere architecture and processes are designed to protect your data in transit and at rest. Data Collection All data sent from the USM Anywhere Sensor deployed in your on-premises or cloud environment to the USM Anywhere service in the AlienVault Secure Cloud is encrypted and transferred over a secure TLS 1.2 connection. Each sensor generates a certificate to communicate with the USM Anywhere service. This means that all communication is uniquely encrypted between each sensor and USM Anywhere. All forensic data (raw logs) is backed up on an hourly basis. The data collected in USM Anywhere is secured using AES-256 encryption for both hot (online) storage and cold (offline) storage. Data Access Your data in USM Anywhere is treated as highly confidential, and only a select few AT&T Cybersecurity staff members have access. This group of employees uses multi-factor authentication (MFA) to access the AlienVault Secure Cloud. Strict internal controls and automation enable support for the service while minimizing administrative access. AT&T Cybersecurity also has a formal information security program that implements various security controls to the National Institute of Standards Technology (NIST) Cyber Security Framework. Key controls include: Inventory of Devices, Inventory of Software, Secure Configurations, Vulnerability Assessment, and Controlled Use of Administrative Privileges. Additionally, AT&T Cybersecurity conducts security self-assessments on a regular basis. Single-Tenant Data Store Unlike other SaaS solutions that use a multi-tenant architecture, AT&T Cybersecurity uses a single- tenant data store architecture to securely store your data. With USM Anywhere, your data is stored in its own dedicated data store, which is completely isolated from other customers’ data. Unlike multi-tenancy, which is prone to data leakage and breakage that can affect multiple customer accounts, single-tenancy ensures that all customers’ data is kept separate and leak-proof. USM Anywhere™ Deployment Guide 10 Cold Storage Data Integrity USM Anywhere offers secure long-term log retention, known as cold storage. By default, USM Anywhere stores all data associated with a customer’s subdomain in cold storage for the life of the active USM Anywhere subscription at no additional charge. USM Anywhere uses a write once, read many (WORM) approach to log storage to prevent log data from being modified or otherwise tampered with. You can download your raw logs at any time.
Recommended publications
  • Dell Local Government Solutions

    Dell Local Government Solutions

    Dell local government solutions The Dell difference Delivering an agile, efficient and scalable architecture which is enabling local authorities to transform their services and drive down costs. Dell local government solutions - meet the other Dell Mobilising the workforce As a professional working in local government you will be aware of the role of technology in the Empowering a more mobile and agile workforce with anytime, anywhere, successful delivery of services to users, efficient processes, cost-saving opportunities and the any device access. transformation of services and working practices. What you may not know is that Dell has partnered with councils and local government organisations across the UK for over 25 years to deliver solutions and services that empower local government staff and citizens, connect communities and improve service delivery. With a dedicated team of local government specialists, our solutions have tackled just about every IT operational issue faced in local government, from the modernisation of data centres to the setting-up of shared infrastructure services, such as the one recently deployed for the Scottish Fire and Rescue Service. Government cloud computing With dedicated local government account teams and specialists across the country, we Helping organisations understand if, and how, they can take advantage understand both the challenges facing leadership teams within local government and the of cloud technologies. technology needed to overcome them. In recent years, Dell has undertaken an extensive strategic acquisition programme designed to help customers to: • Reduce CapEx through the commoditisation and standardisation of everything in their infrastructures. • Reduce OpEx by driving automation and manageability across not only Dell solutions but those of other vendors too.
  • Implementation of Centralized Logging and Log Analysis in Cloud Transition

    Implementation of Centralized Logging and Log Analysis in Cloud Transition

    Implementation of Centralized Logging and Log Analysis in Cloud Transition Antti Vainio School of Science Thesis submitted for examination for the degree of Master of Science in Technology. Espoo 3.7.2018 Supervisor Prof. Jukka Suomela Advisor MSc Cyril de Vaumas Copyright ⃝c 2018 Antti Vainio Aalto University, P.O. BOX 11000, 00076 AALTO www.aalto.fi Abstract of the master’s thesis Author Antti Vainio Title Implementation of Centralized Logging and Log Analysis in Cloud Transition Degree programme Computer, Communication and Information Sciences Major Computer Science Code of major SCI3042 Supervisor Prof. Jukka Suomela Advisor MSc Cyril de Vaumas Date 3.7.2018 Number of pages 84 Language English Abstract Centralized logging can be used to collect log data from multiple log files on multiple separate server machines and transmit the data to a single centralized location. Log analysis on top of that can automatically process large amounts of logs for various different purposes including problem detection, troubleshooting, monitoring system performance, identifying security incidents, and understanding user behavior. As the volume of log data is growing when software systems, networks, and services grow in size, the log data located on multiple separate server machines can be difficult to manage. The traditional way of manually inspecting logs hasalso become too labor-intensive and error-prone when large amounts of log data need to be analyzed. Setting up centralized logging and automatic log analysis systems can be used to solve this problem. This thesis explains the concepts of log data, centralized logging, and log analysis, and also takes a look at existing software solutions to implement such a system.
  • D1.5 Final Business Models

    D1.5 Final Business Models

    ITEA 2 Project 10014 EASI-CLOUDS - Extended Architecture and Service Infrastructure for Cloud-Aware Software Deliverable D1.5 – Final Business Models for EASI-CLOUDS Task 1.3: Business model(s) for the EASI-CLOUDS eco-system Editor: Atos, Gearshift Security public Version 1.0 Melanie Jekal, Alexander Krebs, Markku Authors Nurmela, Juhana Peltonen, Florian Röhr, Jan-Frédéric Plogmeier, Jörn Altmann, (alphabetically) Maurice Gagnaire, Mario Lopez-Ramos Pages 95 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Abstract The purpose of the business working group within the EASI-CLOUDS project is to investigate the commercial potential of the EASI-CLOUDS platform, and the brokerage and federation- based business models that it would help to enable. Our described approach is both ‘top down’ and ‘bottom up’; we begin by summarizing existing studies on the cloud market, and review how the EASI-CLOUDS project partners are positioned on the cloud value chain. We review emerging trends, concepts, business models and value drivers in the cloud market, and present results from a survey targeted at top cloud bloggers and cloud professionals. We then review how the EASI-CLOUDS infrastructure components create value both directly and by facilitating brokerage and federation. We then examine how cloud market opportunities can be grasped through different business models. Specifically, we examine value creation and value capture in different generic business models that may benefit from the EASI-CLOUDS infrastructure. We conclude by providing recommendations on how the different EASI-CLOUDS demonstrators may be commercialized through different business models. © EASI-CLOUDS Consortium. 2 Deliverable 1.5 – Final Business Models for EASI-CLOUDS v1.0 Table of contents Table of contents ...........................................................................................................................
  • Why the Dell / EMC Combination Makes Sense for Customers

    Why the Dell / EMC Combination Makes Sense for Customers

    Why the Dell / EMC Combination Makes Sense for Customers Synergistic product portfolio and go-to-market strategies have potential to set IT customers up for success in the digital economy Executive Summary One of the biggest technology deals in history at over $60 billion is about to unfold as Dell prepares to buy EMC. At EMC World in May 2016, Michael Dell made this acquisition more real than ever when he announced the new entity’s name, Dell Technologies, which will be an umbrella brand for the collection of companies that will include enterprise and client solutions and services, and other strategic assets including VMware, Pivotal, RSA, Virtustream, and SecureWorks. With just a few major milestones to go, it appears that all is on track for the companies to merge the enterprise organizations as Dell EMC under the umbrella brand and to begin operating as one by around mid-year. Dell and EMC are positioning themselves as the path to the cloud for IT customers. Moor Insights & Strategy (MI&S) believes Dell’s leadership in compute and EMC’s leadership in storage and converged infrastructure have the potential to become building blocks for a one-stop shop for enterprise datacenter customers. Other assets such as security, virtualization software, and cloud solutions can help round out the portfolio. Moreover, Dell’s client computing business and IoT practices can bring insight into client computing and IoT models that will be key drivers for future datacenter requirements. Dell EMC should focus on continuing to build up their networking business and making it a more cohesive part of their end-to-end datacenter story.
  • NXLOG Community Edition Reference Manual for V2.9.1716 I

    NXLOG Community Edition Reference Manual for V2.9.1716 I

    Ed. v2.9.1716 NXLOG Community Edition Reference Manual for v2.9.1716 i NXLOG Community Edition Reference Manual for v2.9.1716 Ed. v2.9.1716 Ed. v2.9.1716 NXLOG Community Edition Reference Manual for v2.9.1716 ii Copyright © 2009-2014 NXLog Ltd. Ed. v2.9.1716 NXLOG Community Edition Reference Manual for v2.9.1716 iii Contents 1 Introduction 1 1.1 Overview . .1 1.2 Features . .1 1.2.1 Multiplatform . .1 1.2.2 Modular architecture . .1 1.2.3 Client-server mode . .2 1.2.4 Log message sources and destinations . .2 1.2.5 Importance of security . .2 1.2.6 Scalable multi-threaded architecture . .2 1.2.7 High performance I/O . .2 1.2.8 Message buffering . .2 1.2.9 Prioritized processing . .3 1.2.10 Avoiding lost messages . .3 1.2.11 Apache-style configuration syntax . .3 1.2.12 Built-in config language . .3 1.2.13 Scheduled tasks . .3 1.2.14 Log rotation . .3 1.2.15 Different log message formats . .4 1.2.16 Advanced message processing capabilites . .4 1.2.17 Offline processing mode . .4 1.2.18 Character set and i18n support . .4 2 Installation and quickstart 5 2.1 Microsoft Windows . .5 2.2 GNU/Linux . .6 2.2.1 Installing from DEB packages (Debian, Ubuntu) . .6 2.2.2 Installing from RPM packages (CentOS, RedHat) . .6 2.2.3 Configuring nxlog on GNU/Linux . .6 Ed. v2.9.1716 NXLOG Community Edition Reference Manual for v2.9.1716 iv 3 Architecture and concepts 7 3.1 History .
  • Nxlog Community Edition Reference Manual

    Nxlog Community Edition Reference Manual

    NXLog Community Edition Reference Manual NXLog Ltd. Version 2.10.2150, November 2018 Table of Contents 1. Man Pages. 1 1.1. nxlog(8) . 1 1.2. nxlog-processor(8) . 3 2. Configuration . 5 2.1. General Directives . 5 2.2. Global Directives . 6 2.3. Common Module Directives. 7 2.4. Route Directives. 12 3. Language. 15 3.1. Types . 15 3.2. Expressions. 15 3.3. Statements . 24 3.4. Variables . 26 3.5. Statistical Counters . 26 3.6. Functions. 28 3.7. Procedures . 31 4. Extension Modules . 34 4.1. Character Set Conversion (xm_charconv) . 34 4.2. Delimiter-Separated Values (xm_csv) . 35 4.3. External Programs (xm_exec) . 39 4.4. File Operations (xm_fileop) . 41 4.5. GELF (xm_gelf) . 44 4.6. JSON (xm_json). 48 4.7. Key-Value Pairs (xm_kvp) . 51 4.8. Multi-Line Parser (xm_multiline) . 60 4.9. Perl (xm_perl) . 68 4.10. Syslog (xm_syslog) . 71 4.11. WTMP (xm_wtmp) . 83 4.12. XML (xm_xml). 84 5. Input Modules . 88 5.1. Fields . 88 5.2. DBI (im_dbi) . 88 5.3. External Programs (im_exec) . 89 5.4. Files (im_file) . 90 5.5. Internal (im_internal). 93 5.6. Kernel (im_kernel) . 95 5.7. Mark (im_mark) . 96 5.8. EventLog for Windows XP/2000/2003 (im_mseventlog). 97 5.9. EventLog for Windows 2008/Vista and Later (im_msvistalog) . 100 5.10. Null (im_null) . 105 5.11. TLS/SSL (im_ssl) . 105 5.12. TCP (im_tcp) . 107 5.13. UDP (im_udp) . 108 5.14. Unix Domain Sockets (im_uds) . 109 6. Processor Modules . 111 6.1. Blocker (pm_blocker) . ..
  • Facing the Challenge(S) of Windows Logs Collection to Leverage Valuable Iocs

    Facing the Challenge(S) of Windows Logs Collection to Leverage Valuable Iocs

    Facing the challenge(s) of Windows logs collection to leverage valuable IOCs . Michel de Crevoisier Security Analyst, Radar Cyber Security 15.10.2019, Berne © RadarServices // Classification: Public The five challenges © RadarServices // Classification: Public #1 High diversity of log sources Server Microsoft 3rd party Built-in roles software software Advanced Threat ADFS Application Analytics (ATA) Ivanti software Certification authority Exchange PowerShell Kaspersky DHCP server Skype Security DNS server SQL Server Veeam Backup System IIS web server SYSMON […] […] NPS Radius Defender © RadarServices // Classification: Public 3 #2 Different log extensions EVTX ETL TXT (standard Windows logs (analytical logs, like DNS (IIS, NPS, DHCP, in XML format) Server or PowerShell) PowerShell Transcript, former DNS logs) © RadarServices // Classification: Public 4 #3 Multiple architectural approaches Access method / Protocol (MS-EVEN6, RPC, WMI,…) Push vs Pull Agent vs Agentless Intermediate collector VS Direct sending to receiver Central file store vs Shared folder Managed agent VS Unmanaged agent © RadarServices // Classification: Public 5 #4 Disabled and restrictive event logs • Protected users (if configured, on DCs only) Valuable event • LSA (Local Security Authority) logs disabled • IIS web server • DNS client Event logs with • SMB server restrictive • SMB client access • IIS web server © RadarServices // Classification: Public 6 6 #5 Operational constraints Security Data exchange Performance Configuration Environment • Avoid usage of • Data
  • Using Nxlog with Elasticsearch and Kibana I

    Using Nxlog with Elasticsearch and Kibana I

    Using NXLog with Elasticsearch and Kibana i Using NXLog with Elasticsearch and Kibana Using NXLog with Elasticsearch and Kibana ii Contents 1 Setting up Elasticsearch and Kibana 1 1.1 Installing Elasticsearch . .1 1.2 Installing Kibana . .1 2 Loading data into Elasticsearch with NXLog2 2.1 Loading data with om_elasticsearch . .2 2.2 Loading data with om_http . .4 2.3 Using Logstash . .5 Using NXLog with Elasticsearch and Kibana 1 / 6 Elasticsearch coupled with the Kibana frontend has become quite popular recently as a low-cost centralized log monitoring solution. This is commonly referred to as the ELK stack comprised of Elasticsearch, Logstash and Kibana. While Logstash is a great piece of software it has some disadvantages compared to NXLog: • Logstash is written in ruby and requires Java to run. Besides being a lot more hungry on system resources, many system administrators would rather not take the hassle of deploying the Java runtime onto their production servers and needing take care of the Java security updates. • The Eventlog plugin in Logstash pulls the eventlog data through the Windows WMI interface which incurs a significant performance penalty. NXLog hooks directly into the Windows EventLog API natively and can collect logs from our highly loaded Domain Controllers also. • It’s just one more piece of software to take care about. NXLog is a small and efficient log collector that can be set up to securely and reliably centralize event data from Windows and Unix platforms. As such, NXLog is recommended by many ELK users as the log collector of choice for Windows and Linux.
  • Dell Technologies1 Partner Program Incentive Terms and Conditions LATAM

    Dell Technologies1 Partner Program Incentive Terms and Conditions LATAM

    Dell Confidential Dell Technologies1 Partner Program Incentive Terms and Conditions LATAM As a member in good standing in the Dell Technologies Partner Program certain resellers (“Partner” or “Partners”) may be eligible to participate in incentive programs (“Program” or Incentive Program”) including but not limited to, special discounts, rebates, sales spiffs, promotions or contests, and marketing development funds (MDF) programs (“Incentive” or collectively “Incentives”). The following Dell Technologies Partner Program Incentive Terms and Conditions (“Incentive Terms”), unless otherwise agreed to in writing by Dell Technologies, apply to a Partner’s participation in any and all Dell Technologies Partner Program Incentives. Unless otherwise specified in these Incentive Terms, any terms and definitions used herein have the meanings ascribed to them in the Dell Technologies Partner Program Agreement. These Incentive Terms are supplemental and subject to the Dell Technologies Partner Program Agreement, and together with the Benefits and Requirements documents for the applicable Partner Track, set forth the terms and conditions governing Partner eligibility, type, structure, and amount of any Incentive and constitute the entire agreement (“Agreement”) between Dell Technologies and Partner with respect to all Incentives. The Benefits and Requirements document may be found on the Dell Technologies Partner Portal located here: https://www.delltechnologies.com/partner/es-mx/partner/partner.htm This Agreement supersedes any and all prior agreements and understandings regarding any Incentives, whether established by custom, practice, procedure or precedent, including without limitation all prior incentive program terms and conditions or business rules offered to a certain class of Partner in the current Dell Technologies Partner Program, the former Dell PartnerDirect Program, or EMC Business Partner Program.
  • Stacking Dell Networking Switches: N4032, N4032F, N4064, N4064F

    Stacking Dell Networking Switches: N4032, N4032F, N4064, N4064F

    Stacking Dell Networking Switches: N4032, N4032F, N4064, N4064F Dell Engineering February 2014 A Dell Deployment and Configuration Guide Revisions Date Description Author(s) February 2014 Initial Release Victor Teeter THIS PAPER IS FOR INFORMATIONAL PURPOSES ONLY, AND MAY CONTAIN TYPOGRAPHICAL ERRORS AND TECHNICAL INACCURACIES. THE CONTENT IS PROVIDED AS IS, WITHOUT EXPRESS OR IMPLIED WARRANTIES OF ANY KIND. © 2014 Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. PRODUCT WARRANTIES APPLICABLE TO THE DELL PRODUCTS DESCRIBED IN THIS DOCUMENT MAY BE FOUND AT: http://www.dell.com/learn/us/en/19/terms-of-sale-commercial-and-public-sector Performance of network reference architectures discussed in this document may vary with differing deployment conditions, network loads, and the like. Third party products may be included in reference architectures for the convenience of the reader. Inclusion of such third party products does not necessarily constitute Dell’s recommendation of those products. Please consult your Dell representative for additional information. Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ ,OptiPlex™, Latitude™, PowerEdge™, PowerVault™, PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc. Other Dell trademarks may be used in this document. Cisco Nexus®, Cisco MDS®, Cisco NX-0S®, and other Cisco Catalyst® are registered trademarks of Cisco System Inc. EMC VNX®, and EMC Unisphere® are registered trademarks of EMC Corporation. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S.
  • An Exploratory Semantic Analysis of Logging Questions

    An Exploratory Semantic Analysis of Logging Questions

    Received: Added at production Revised: Added at production Accepted: Added at production DOI: xxx/xxxx An Exploratory Semantic Analysis of Logging Questions Harshit Gujral*1 | Sangeeta Lal2 | Heng Li3 1Department of Computer Science Engineering and Information Abstract Technology, Jaypee Institute of Information Technology, Noida, India. Logging is an integral part of software development. Software practitioners often face issues Email: [email protected] in software logging, and they post these issues on Q&A websites to take suggestions from 2Lecture Data Science, School of Computing and Mathematics, Keele the experts. In this study, we perform a three-level empirical analysis of logging questions University, Keele, United Kingdom. posted on six popular technical Q&A websites, namely Stack Overflow (SO), Serverfault Email: [email protected] 3Department of Computer and Software (SF), Superuser (SU), Database Administrators (DB), Software Engineering (SE), and Engineering, Polytechnique Montréal, Android Enthusiasts (AE). The findings show that logging issues are prevalent across var- Montréal, Canada. Email: [email protected] ious domains, e.g., database, networks, and mobile computing, and software practitioners from different domains face different logging issues. The semantic analysis of logging ques- Correspondence *Corresponding author. tions using Latent Dirichlet Allocation (LDA) reveals trends of several existing and new logging topics, such as logging conversion pattern, android device logging, and database logging. In addition, we observe specific logging topics for each website: DB (Log shipping, Log file growing/shrinking), SU (Event Log, Syslog configuration), SF (Log analysis, Sys- log configuration), AE (App Install, Usage tracking), SE (Client server logging, Exception logging), and SO (Log file creation/deletion, Android Emulator Logging, Logger class of log4j).
  • SLED Plan 1H FY20

    SLED Plan 1H FY20

    The Essentials of Esports for K12 Agenda • Speaker Introductions • What is Esports? • Panel Discussion • Dell Esports Solutions for Education • Q&A 2 of 25 Dell – Internal Use – Confidential Presenters Kyle Berger Chief Technology Officer Grapevine-Colleyville ISD @edtechcto John McCarthy Education Technology Consultant, Advanced Learning Partnerships @JMcCarthyEdS Juan “hungrybox” DeBiedma Pro-gamer for Team Liquid Super Smash Bros world champion Ranked #1 @LiquidHbox Omar Ali HS Educator 2019 Lindback Foundation Distinguished Teaching Award Reciepient 3 of 25 Dell – Internal Use – ConfidentialPhiladelphia School District Esports in Education 4 of 25 Dell – Internal Use – Confidential What is esports? Multiplayer video games played competitively for spectators 5 of 25 Dell – Internal Use – Confidential Esport tournament viewers Esports as an Industry 7 of 25 Dell – Internal Use – Confidential Why esports in education? • Following student interests - 70% of students are gaming • Engaging students who have not participated in other campus activities • Students are forming their own clubs • Minimum GPA standards for participation in varsity and club programs • Potential to offset tuition and education expenses • STEAM and esports are a great fit together 8 of 25 Dell – Internal Use – Confidential The rise of high school esports High schools are creating esports programs to engage students, build school culture and promote career and college readiness. High School Organizations Website High School eSports League https://www.highschoolesportsleague.com/