Dell Compellent FS8600 最优实践

Dell Compellent FS8600 最优实践
Dell Compellent FS8600 最优实践

THIS BEST PRACTICES 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.

? 2012 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. Trademarks used in this text: Dell TM, the DELL TM logo, and Compellent TM are trademarks of Dell Inc. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

June 2012

Contents

Document Revision (3)

Audience (3)

Purpose (3)

Customer Support (3)

Introduction (4)

Connectivity (4)

Ethernet connectivity (4)

Client Connectivity (5)

Interconnect Connectivity (8)

Fibre Channel Connectivity (9)

Network Services (11)

Domain Name System (11)

Round Robin DNS (11)

Cluster Quorum (11)

Active Directory (12)

Network Lock Manager (12)

Network Time Protocol (12)

Cluster Quorum (12)

Client Identification Services (12)

LDAP/NIS (12)

Active Directory (13)

FS8600 User Access Settings (13)

NAS volumes (13)

Thin Provisioning (13)

Exports and Shares (14)

NFS Exports (14)

CIFS Shares (14)

Quotas (18)

FS8600 Data Protection (19)

Snapshots (19)

Replication (19)

NDMP Backups (20)

Storage Center best practices for the FS8600 (21)

Data Progression (21)

Data Instant Replay, Remote Instant Replay and Live Volume (21)

Solid state disks (21)

Managing FS8600 Storage Center Volumes (22)

VMware (22)

Tables

Table 1.Revision History (3)

Figures

Figure 1.Example of User Based Share View for “bob” (15)

Figure 2.Example of User Based Share View for “jane” (15)

Figure 3.CIFS Share View Example (15)

Figure 4.Example View Within the “users” Share (16)

Figure 5.Establishing a Hidden Share (17)

Figure 6.Hidden Share No Longer Visible to Users (17)

Figure 7.Hidden Share Accessed Using UNC Path (18)

Figure https://www.360docs.net/doc/009187804.html,ing FS8600 NFS Export as Datastore to VMware ESX/ESXi (22)

Figure 9.Creating Symlink to Expose .snapthots (23)

Figure 10.View of the snapshots Symlink Created (23)

Figure 11.Viewing Contents of the .snapshots Using the Symlink (23)

Document Revision

Table 1. Revision History

Preface

Audience

The audience for this document is intended to be systems, networking, storage or backup administrators who are responsible for the day-to-day management responsibilities of a Dell Compellent FS8600 environment. Proper management of a FS8600 requires administrators or teams of administrators capable of managing and configuring enterprise-grade Fibre Channel SAN and Ethernet networks, any enterprise-grade backup software intended to be used, the Dell Compellent Storage Center itself as well as general purpose NAS administration.

Purpose

The purpose of this document is to cover specific implementation concepts or specifics related to the management of a Dell Compellent FS8600 environment. It is not intended to be a primer or introductory resource for any of the subject matters involved, and it assumes at least introductory knowledge of many of the subjects covered in this document. This document should be used in conjunction with other Dell Compellent resources, such as the Dell Compellent Storage Center Connectivity Guide, FS8600 Admin Guide and Hardware Manual, Enterprise Manager 6 User Guide, or any other available documentation resources.

Customer Support

Dell Compellent provides live support 1-866-EZSTORE (866.397.8673), 24 hours a day, 7 days a week, 365 days a year. For additional support, email Dell Compellent at support@https://www.360docs.net/doc/009187804.html,. Dell Compellent responds to emails during normal business hours.

Introduction

As unstructured file data continues to grow at challenging rates, IT file server infrastructure supporting business and mission critical systems can easily become strained and fragmented. This can manifest in a variety of painful forms such as rising management costs, lost storage efficiencies, complicated or fickle backup architectures and challenges to overall system availability.

The Dell Compellent FS8600 is uniquely suited to overcome the challenges presented by explosive file data growth and file sprawl. With the combination of the Dell Fluid File System’s (FluidFS) s cale-out single namespace and Compellent Storage Center’s Data Progression and Dynamic Capacity, IT teams can reduce management overhead as well as leverage the platform’s unique storage efficiencies and cost of ownership attributes while providing class-leading availability and data protection.

It should be noted that the FS8600 is a member of the Dell FluidFS NAS product family. It is in many ways conceptually similar to the FluidFS products available on the Dell PowerVault product line as well as the Dell EqualLogic product line. While many of the concepts, particularly front-end NAS concepts are similar or even identical, other subjects, such as management of interaction with backend storage, may be radically different. Relevant resources for each FluidFS platform should be leveraged for the appropriate product.

Connectivity

The Dell Compellent FS8600 leverages industry-standard connectivity protocols and concepts, namely Ethernet and Fibre Channel connectivity, and the proper implementation and configuration of the systems involved is a paramount concern. Particularly in large-scale or otherwise complex deployments, considerable care and planning of the connectivity systems involved is required.

An FS8600 environment is dependent on several conceptually isolated networks, each of which may contain other subdivisions of logically independent networks. While each logically independent network may meet its own requirements, each network can have a substantial impact on the requirements or overall behavior of the other networks involved. Therefore, each individual network as well as the network configuration as a whole must be carefully understood.

Ethernet connectivity

FS8600 Ethernet connectivity is the connectivity medium that is used to carry client or interconnect traffic. Client network connectivity is used to expose file resources, backup protocols and management interfaces to users, administrators and other systems. Interconnect Ethernet connectivity is used in

FS8600 clusters of two or more FS8600 appliances to carry cluster traffic between NAS controllers.

As stated in the “Purpose” section of this document, it is assumed that the reader has already consulted the FS8600 Admin Guide and Hardware Manual.

For environments with networks living on multiple switch vendors/models (Cisco Catalyst<->Brocade Foundry), and particularly environments adopting a new vendor switch as part of the FS8600 deployment (for example Dell Force10 into an established Cisco network), all network features should be thoroughly tested before entering the deployment into production.

Monitoring

It is also strongly suggested that a system for monitoring and trending all ports on all switches in an environment be preemptively set up prior to the production implementation of an FS8600 environment, as this can be a substantial resource in detecting potential bottlenecks or protecting against future performance or availability issues.

Each FS8600 interface can also be monitored through both SNMP traps and SNMP polling after SNMP has been configured through either the “Start Configuration Wizard” or through the appropriate configuring interfaces in the web interface or CLI. The interfaces are exposed to SNMP polling through the standard net-snmp OIDs.

Client Connectivity

The FS8600 client network connectivity is responsible for exposing and carrying NAS resource traffic to clients and other systems. In any FS8600 deployment, the client connectivity Ethernet ports are reserved to the left most network interfaces on each Ethernet card when observing the rear of the

FS8600 appliance.

Separate Networks/Subnets

The FS8600 is capable of supporting or living on large numbers of separate or distinct networks, also referred to as subnets. This can be beneficial for reasons such as consolidating established or legacy file servers, as well as following best practices for providing dedicated resources to specific client groups or environments. NDMP backups should also be isolated to a dedicated network, and it is also suggested that where possible, networks should be isolated in a one to one fashion with VLANs (see below).

The scale-out architecture of FluidFS ensures that each host or client that accesses NAS resources is evenly distributed across all interfaces in an FS8600 cluster. Generally, this means only one IP address is needed per network. The FluidFS platform balances clients across interfaces in the following way: Client-A tries to access NAS resources with the DNS provided hostname of cl0-fs8600.local, which is a DNS A record to 10.10.30.5. Not having any previous network information for 10.10.30.5, Client-A will issue an ARP request on its available interfaces. Seeing the request, the FS8600 will respond saying it owns 10.10.30.5 through its first NIC, and the client and FS8600 will proceed to communicate over that interface. Client-B then tries to access NAS resources through the cl0-fs8600.local hostname, and following DNS, similarly reaches out to the network with an ARP request for 10.10.30.5. In order to balance the connection from Client-B, the FS8600 will respond to Client-B through its second NIC, and communication between Client-B and the FS8600 will continue through that interface. Going forward, the FS8600 will continue to answer new ARP requests through all of the interfaces available in the cluster.

There are reasons why multiple IP addresses per network may be needed, such as supporting IP addresses or legacy hostnames from consolidated legacy file servers. In some environments, there may also be performance reasons for maintaining multiple IP addresses per network. Take, for example, an NFS client that accesses NFS exports “cl0-fs8600.local:/vol1/mail cl0-fs8600:/vol1/htdocs/ and cl0-

fs8600:/export/ora1”. The first time the client requests NAS resources (for example for /vol1/mail), it

will reach out with an ARP, just as any other client. However, the second time it requests NAS resources (for example /vol1/htdocs), the client already knows which MAC address it needs to reach the NAS resources, and it will simply use that established lane of communication, meaning that going forward, the client will only communicate through one NIC on the FS8600. For high performance clients, this may not be ideal. In these cases, mechanisms such as round robin DNS or the use of a hosts file can specify multiple hostnames for multiple IPs, such that “cl0-fs8600-1” resolves to 10.10.30.5 and “cl0-fs8600-2” resolves to 10.10.30.6. Then each time a client attempts to access both “cl0-

fs8600-1:/vol1/mail” and “cl0-fs8600-2:/export/ora1”, the client will ARP for each resource, and hence be distributed across NICs for each resource.

Similarly, some network devices, such as VPNs or routers, may cache ARP/MAC addresses in such a way as to only distribute traffic for a destination IP through one FS8600 NIC. For resources that are heavily accessed through such devices, mechanisms such as round robin DNS should be used in order for clients to request multiple destinations through the VPN or router. This will balance traffic across the FS8600 NICs.

When adding subnets, it is suggested to set aside sufficient IP address per subnet to accommodate the addition of more FS8600 appliances as part of the cluster at a later point in time.

It should be noted that any client connectivity, including NDMP, should always target a client VIP, and client traffic should never target the management IP.

VLANs

The FS8600 is VLAN-aware, meaning it is capable of understanding and communicating with VLAN tagged Ethernet frames, allowing it to address multiple networks across multiple VLANs at a time. The management network is not VLAN-aware and must be an untagged VLAN network to the FS8600 NICs. Similarly, any installation of Enterprise Manager must be in a VLAN capable of reaching the FS8600 management network. Similarly, the network gateway for the FS8600 must be reachable, preferably through the management/untagged network, because reaching the gateway is used as part of the FluidFS cluster quorum logic.

It is generally suggested to use and isolate networks to a VLAN and network per purpose where possible (for example, a certain data is only accessed by isolated group of clients). This is also true for functions such as replication or NDMP backup traffic.

The management network cannot be VLAN-isolated, and it requires that the switch ports “untag” the VLAN associated with the management network to the FS8600 interfaces.

MTU

The FS8600 is Ethernet Jumbo Frames (MTU 9000+) capable, and environments can expect a degree a performance improvement, particularly where throughput is concerned, by enabling Jumbo Frames on the FS8600 platform as well as the client connectivity network topology and clients. It must be noted that the MTU setting for client connectivity on the FS8600 is a global variable for all networks, so environments with mixed MTU topologies need to determine whether they can enable Jumbo Frames on the FS8600 and associated network infrastructure without impacting the non-Jumbo Frames network infrastructure. It is also worth noting that not all vendors agree on the exact definition of Jumbo Frames, and as such, documentation from each vendor should be consulted.

Spanning Tree

The FS8600 requires that spanning tree on all switch ports connected to client connectivity ports must be disabled. For many network vendor implementations, this will be called “portfast” or “edge” mode within the switch configuration semantics.

For networks with sprawled network topologies or otherwise complicated/collapsed/converged topologies, it is strongly recommended that a modern implementation of rapid spanning tree protocol, multiple spanning tree protocol or other similar technology be deployed, as the impact to client connectivity in the event of a failure will be determined by network convergence delays. In many environments, the time required for spanning tree to detect and react to a topology change will be the primary source of observed time for a client to recover from a network or NAS controller failure.

For networks that make use of VLANs, it is suggested that the spanning tree implementation support a mechanism for an instance of spanning tree per VLAN.

Load Balancing and ALB vs. LACP

There are few or no technical or rational reasons why LACP should be chosen over ALB, and ALB should be the assumed connectivity mode for all FS8600 environments.

FluidFS actively monitors client connectivity across the cluster and maintains a policy list for what NAS protocols to migrate in the event that the cluster experiences a failover event that causes lopsided client connectivity across the cluster. It is strongly suggested that the default policies be left intact unless a known client connectivity issue requires a change.

Flow Control

It is recommended but not required that all switch ports connected to the FS8600 client side interfaces have flow control enabled. Outside of the switch ports directly connected to the FS8600, Flow Control can be enabled or disabled as required.

Note this in contrast to the Dell Compellent Storage Center, for which it is strongly suggested to disable flow control on switch ports connected to iSCSI I/O cards. For more information regarding Flow Control and Storage Center, consult any Co-Pilot Support Tech Alerts for the Storage Center configuration in question.

Switch Topology

An FS8600 appliance or cluster can only be as highly available or high-performance as the switch infrastructure supporting it. Architecturally, three guiding principles can be used to construct a best practice switch connectivity topology:

?Avoid any single points of failure

?Ensure sufficient inter-switch throughput

?Make every client connectivity port in an FS8600 cluster available to any potential client

It is also important to remember that the client network is responsible for all traffic of exposed NAS resources, including general client connectivity, management, replication and backups. Accordingly, the throughput and impact of backup traffic between the FS8600 and the backup server should be accounted for.

The FS8600 and the FluidFS architecture are fundamentally Ethernet/Switch topology agnostic as long as the topology meets the stated best practice requirements. This means that technologies such as switch stacking or other vendor proprietary switch trunking technologies are valid topologies, so long as they behave as open standards Ethernet to the FS8600 interfaces.

Understanding failure scenarios

This section assumes that an FS8600 is being supported by a correctly configured highly available switch topology. In a correctly configured, highly available environment, a failure of any individual system, including an FS8600 controller, should be able to be survived while maintaining data availability.

In the event of a switch failure, clients who had a connected session to an FS8600 interface connected through that switch will begin their TCP/IP timeout/ARP cache counter and expire the now invalid ARP cache for that FS8600. At that point, the client will issue another ARP request, which will be answered to by one of the FS8600 interfaces available through another switch. In these scenarios, the performance of the spanning tree implementation in question is likely to be the primary concern for recovery times.

In the event of an FS8600 controller failure, the surviving controller will issue a gratuitous arp to the clients of the failed controller. This gratuitous arp instructs those clients to renegotiate their arp cache, which will be answered by one of the interfaces on another controller in the cluster.

It should be noted that clients who lose connectivity to an FS8600 controller during the middle of a CIFs data operation will error out and will have to re-establish a CIFs session with the surviving controller.

Interconnect Connectivity

The FS8600 is dependent on the ability of each NAS controller in an FS8600 cluster to communicate through a dedicated network, called the interconnect network, to any other controller in the cluster. The interconnect network is used both for inter-node communication to satisfy client I/O across FS8600 appliances, as well as cluster quorum and availability communication. The interconnect network reserves the rightmost ports on a NAS controller.

An example of a client side I/0 that generates interconnect traffic would be a client read request that is best resolved by querying another controller’s cache or file system allocation than satisfying the I/O with an expensive operation to disk. This type of behavior can cause the overall FluidFS architecture to be relatively “chatty” over its interconnect network, particularly in high-performance environments.

For single appliance deployments, the interconnect ports on each controller are cross connected directly to each other, bypassing any switch. For deployments with multiple FS8600 appliances in a single NAS cluster, the interconnect ports must be connected to a switch infrastructure. For more information, please consult the FS8600 Hardware Manual.

VLANs

The interconnect network must live on a dedicated VLAN that is isolated from all other traffic and solely purposed for an individual cluster’s interconnect traffic. Similarly to the management network, this VLAN must be untagged on all switch ports connected to FS8600 interconnect connectivity ports.

MTU

All switch ports connected to FS8600 interconnect connectivity ports must be enabled for Jumbo Frames (MTU equal to or greater than 9000).

Spanning Tree

Spanning tree must be disabled for all FS8600 interconnect ports. For many network vendor implementations, this will be called “portfast” or “edge” in the switch configuration semantics.

Flow Control

The FS8600 requires that all switch ports connected to the FS8600 interconnect interfaces have flow control enabled.

Note this is in contrast to the Dell Compellent Storage Center, for which it is strongly suggested to disable flow control on switch ports connected to iSCSI I/O cards. For more information regarding Flow Control and Storage Center, consult any Co-Pilot Support Tech Alerts for the Storage Center configuration in question.

Switch Topology

An FS8600 appliance or cluster can only be as highly available or high-performance as the switch infrastructure in supporting of it. Architecturally, three guiding principles can be used to construct a best practice switch connectivity topology:

?Avoid any single points of failure

?Sufficient inter-switch throughput

?All controller interconnect ports must be able to reach all other controller interconnect ports

Because of the chatty nature of the Interconnect network, throughput between switches responsible for the Interconnect network may require sufficient inter-switch throughput as to match the aggregate client connectivity throughput.

Through the use of VLANs, the interconnect network can reside on the same physical switch infrastructure as the client connectivity network. The interconnect network can also reside on dedicated switch infrastructure solely purposed for the interconnect network, which may be ideal for larger or higher performance deployments, so long as all controller interconnect ports are be able to reach all other controller interconnect ports.

Fibre Channel Connectivity

The FS8600 is unique in the FluidFS family for its usage of Fibre Channel based connectivity to provide access to its backend supporting storage, a Dell Compellent Storage Center or in some cases two Storage Centers. Similarly to the front end Ethernet connectivity, the FS8600 is only as highly available and high performance as the supporting backend SAN switch environment and topology. Architecturally, the following guiding principles can be used to construct a best practice Fibre Channel connectivity topology:

?Avoid any single points of failure

?Ensure sufficient ISL throughput

?Make all NAS controller Fibre Channel ports able to reach all Storage Center ports per fault domain

?Avoid or minimize impact to other hosts in the SAN

?Adhere to established Dell Compellent Storage Center best practices such as those outlined in the Dell Compellent Storage Center Connectivity Guide.

Logically isolated fabrics

Not all environments or deployments warrant the implementation of a Fibre Channel infrastructure

that avoids any single point of failure for the SAN. For these environments, it is suggested that a virtual fabric technology (Cisco’s VSANs or Brocade’s logical switch features) be implemented in order to logically isolate port and zoneset configurations into two separate logical fabrics. While this may introduce conceptual complexity, it provides the benefit of isolating one logical fabric from administrative errors in the other. This allows for the survival of the FS8600 environment even if there is a critical configuration error in one of the logical fabrics.

Each individual port in an FS8600 controller should be associated with a unique, logically isolated fabric, and the same logically isolated fabrics should be used for each FS8600 controller in a cluster.

Storage Center Fault Domains

As stated previously, it is strongly suggested that the relevant Dell Compellent Storage Center documentation be consulted when implementing a Fibre Channel architecture that involves the FS8600.

A Storage Center fault domain should be created per logically isolated fabric, physical or virtual. In the event that a logically isolated fabric is being introduced to an established architecture as part of an

FS8600 implementation, the Storage Center connectivity into that fabric and its relevant Fibre Channel fault domain configuration should be adjusted accordingly.

It should be noted that the Storage Center logically links Fibre Channel over Ethernet with Fibre Channel fault domains. As the FS8600 is not currently supported on FCoE-based connectivity, the proper configuration of FCoE vs. FC fault domains needs to be considered.

Legacy vs. Virtual Port Mode

As stated previously, it is strongly suggested that the relevant Dell Compellent Storage Center documentation be consulted when implementing a Fibre Channel architecture that involves the FS8600.

The Dell Compellent Storage Center has two modes of front-end Fibre Channel connectivity configuration - Legacy Port Mode and Virtual Port Mode, each of which has its own rationale for implementation. Both Legacy Port Mode and Virtual Port Mode are supported by the FS8600. Generally speaking, the primary concern that drives any Storage Center to Legacy Port Mode is the existence of legacy HP-UX and Solaris systems or current AIX systems. Legacy Port Mode can become conceptually complex very quickly, and in-depth coverage of Storage Center Fibre Channel connectivity falls outside the scope of this document.

It should be noted that converting from Legacy Port Mode to Virtual Port Mode is a “one way” move. While a Storage Center in Legacy Port Mode can be converted to Virtual Port Mode, a Storage Center in Virtual port Mode cannot be converted back to Legacy Port Mode.

Zoning

Traditionally, Dell Compellent recommends implementing WWN-based zoning policies for Storage Center SANs but also supports port-base zoning out of recognition that some customers may prefer this method. However, with the FS8600, the recommendation is reversed. Dell Compellent recommends zoning the FS8600 controllers using port-based zoning but also supports WWN-based zoning out of recognition that some customers may prefer this method. The rationale for suggesting port-based zoning is that in the rare event that an FS8600 controller or Fibre Channel card needs to be replaced, the use of port zoning avoids the need to change the relevant zone set.

For large SANs, it may be advantageous to group the front-end Storage Center Fibre Channel ports into a Fibre Channel alias on the fabric and create zones by using the FC Alias for the appropriate Storage Center. For Legacy Mode Storage Centers, both the Front-End Primary and Front-End Reserve can be included in a single zone.

A zone should be created per NAS controller port to the respective Storage Center front-end ports. No zone should be created that allows a NAS controller port to see any other NAS controller port. No more than one Storage Center should be included per zone. No zone should be created that allows a NAS controller port to see anything other than a Storage Center front-end port.

Network Services

All FS8600 environments will be dependent on various network services that, while providing crucial services, also introduce complexity that needs to be accounted for.

Domain Name System

Round Robin DNS

Route-aware devices (routers/gateways, VPNs etc) may cache IP to MAC Address destination relationships, which could cause uneven distribution of clients on a limited number of FS8600 interfaces. Because of this, some environments may benefit from the use of Round Robin DNS systems. For a pool of clients, this will iteratively alter the IP address that is returned to the clients, causing the clients to connect through the route-aware device to the FS8600 in a balanced way. When implementing a Round Robin DNS system, it is important to understand the caching relationships of all subsequent DNS systems between the Round Robin DNS server and the clients. For example, if ns0.local and ns1.local are configured for Round Robin DNS but clients use ns0.office.local as their primary DNS target, ns0.office.local could possibly poll ns0.local to satisfy the request but then cache the request and return the same value to the next client, hence removing the benefit of implementing Round Robin DNS. Some environments may see a benefit in keeping a short TTL value for the relevant DNS records for added overall flexibility.

When allocating IPs and creating A record pools for Round Robin DNS, there should be at a minimum as many IPs and associated A records as there are interfaces in the FS8600 cluster.

Cluster Quorum

In the absence of a reachable gateway, the ability to reach the configured DNS hosts is used as a cluster quorum voting mechanism. As such, DNS must be similarly highly available and reachable by the FS8600.

Active Directory

For FS8600 environments that will be integrated with Active Directory, all relevant DNS entries must be up to date and valid prior to attempting to bind the FS8600 into that Active Directory domain. The DNS servers configured on the FS8600 must include DNS servers responsible for the DNS of the Active Directory domain in question, and one of the configured DNS suffix entries configured on the FS8600 must be the Active Directory domain in question.

Network Lock Manager

The specific configuration for NFS NLM is highly platform dependent. However, as a rule of thumb, most client implementations are highly dependent on a valid alignment of:

?The client’s perceived hostname for itself (this is because the hostname can be included as part of the NLM request)

?The matching of the client’s perceived hostname to visible DNS forwards

?The matching of DNS forwards to the IP address of the client

?The matching of DNS forwards to proper DNS reverse lookups

In many environments and platforms, troubleshooting of NLM will be difficult or impossible without a valid end-to-end DNS configuration.

Network Time Protocol

The FS8600 can use the NTP to poll time information from authoritative outside sources. Generally, it is recommended that a minimum of two sources be used. Three or more sources is the suggested ideal configuration.

For FS8600 environments that will be integrated with Active Directory, the NTP sources should be the Active Directory Domain Controllers for the domain in question.

Cluster Quorum

In the event that both the configured gateway and DNS hosts are unreachable, the ability to reach the configured NTP hosts is used as a cluster quorum voting mechanism. Because this mechanism is used in the event that DNS is unreachable, at least one of the time servers should be configured by IP as opposed to DNS.

Client Identification Services

LDAP/NIS

As both LDAP and NIS are acknowledged to be unsecure authentication protocols, all NIS and LDAP traffic should be confined to secured or otherwise untrusted networks and VLANs. As NFSv3 is also understood to be unsecure, it may be possible that authentication traffic may be able to reside in the same network or VLAN as NFS traffic.

The FS8600 should be pointed to name services that are logically close to the FS8600 in the overall network topology. While the FS8600 will cache some name information for short periods of time, name lookups can introduce unexpected latency in performance or latency-sensitive environments.

As with networking, the FS8600 can only be as highly available as the systems on which it depends. As such, LDAP and NIS services should be configured in such a way as to be highly available.

Both LDAP and NIS are covered in more depth in the Dell Compellent FS8600: NFS File Server Consolidation Guide.

Active Directory

As detailed in the Network Time Protocol section, accurate time resolution is required for an FS8600 to participate as part of a cluster.

Active Directory is covered in more depth in the Dell Compellent FS8600: CIFs File Server Consolidation Guide.

FS8600 User Access Settings

NAS volumes

NAS volumes represent one of the primary building blocks in the creation of isolated data sets, and are isolated containers within the overall Fluid File System. NAS volumes should be created per data set requirements (for example, CIFs vs NFS data sets) and also to meet other requirements (for example, data protection RPO & RTO requirements as met by snapshot and replication). It should be noted that unlike some other platforms, NAS volumes are a purely logical level of abstraction within the single namespace of the Fluid File System, and there are no performance benefits of spreading data sets across multiple NAS volumes.

Thin Provisioning

While it is possible to oversubscribe the capacity of storage presented to a FS8600 cluster using Storage Center’s Dynamic Capacity thin provisioning technology, it is not possible to oversubscribe space allocated from the FluidFS file system. The FluidFS file system can only allocate as much storage to NAS volumes as has been allocated from Storage Center to the FS8600.

It should be noted that, while all Storage Center volumes are thinly provisioned by default, as data is written over time to the FS8600, the storage allocated and consumed on the Storage Center for that data cannot be reclaimed. If the overall storage capacity of the Storage Center is oversubscribed, extreme care should be taken to monitor the available capacity in the Storage Center to ensure the system always has sufficient free space available.

Data sets with extremely high change rates that also leverage FluidFS snapshots can threaten to consume their allocated storage very quickly and hence should never be oversubscribed.

Access time granularity

The access time granularity setting governs how FluidFS will manage access time request updates to files. Traditionally, very few applications or use cases are dependent on file access time, which in and of itself generates a significant metadata performance burden on both a client and on the NAS platform. By default, tracking of access time is disabled for NAS volumes, but this can be changed both at NAS volume creation time as well as at any time in the future after the initial NAS volume creation. File access security style

The file access security style setting controls which permission schemes are authoritative for that volume. It is generally suggested that data sets that will be exclusively shared through NFS or CIFs reside on different NAS volumes. For NAS volumes that will be exported via NFS, this setting should be set to “UNIX”. For NAS volume s that will be shared via CIFs, it should be set to “NTFS”. In the cas e that

a NAS volume may contain data sets that need to be exposed through both protocols, the setting can be set to “MIXED”.

NAS volumes in UNIX mode will always conform to POSIX style permissions for the data set. A NAS volume in NTFS mode will conform to the NTFS ACL scheme for a given data set. As a rule of thumb, a NAS volume in MIXED mode will enforce the permissions of a file from the perspective of the last protocol to manage the permissions of a file. Take, for example, a file that is stored in UNIX permissions scheme, but the permissions allow a CIFs user to edit and manage the permissions of the file. After the CIFs user has managed the file and the file permission data is committed from the CIFs connection, that file will now have the permissions scheme of an NTFS ACL, as was committed by the client. If configured, user mapping will allow for file permissions interaction between LDAP/NIS and Active Directory user data, allowing for the translation of permissions across protocols.

Exports and Shares

Exports and Shares represent points of isolated visibility into the overall single namespace Fluid File System.

It is suggested that shares do not expose the “/” or root of any individual NAS volume. The “/” folder contains a folder called “.clusterConfig”, which is a stored backup of the cluster configuration and can be used to access backups of the cluster configuration through the file protocols. However, it also contains sensitive information that should not be exposed to unprivileged users.

NFS Exports

Most classical Unix NFS export concepts can be carried over into an FS8600 environment. It is worth noting that exports can be created below export, and the same directory structure of the file system can be exposed through multiple exports.

Limit reported size

The size available and announced through an NFS share will by default be the overall size of the NAS volume. For NAS volumes with many exports, this may be undesirable. Using the “Limit reported size” function under the advanced section of an NFS export, the size reported to the client can be arbitrarily limited at any time. Note that setting a limited size below what the export is already consuming can have disastrous consequences for clients already accessing that export.

Secure Port

There are certain platforms with interpretations of the NFS RFC that cause them to request NFS mount negotiation over what are deemed insecure or unprivileged ports. In order to allow those platforms to access FS8600 exports, the Secure Port setting may need to be enabled. This should not have any impact on other platforms already accessing that export.

CIFS Shares

CIFS shares names must be unique throughout the FS8600. For environments leveraging replication between FS8600s, shares must be unique for each FS8600 environment so that in the event that the NAS volume and associated shares need to be brought online, there is no conflict with established shares.

User-based directory tree

For shares that are intended to provide user home folder data sets, FluidFS does have the capability to emulate a share per CIFS user authenticated against the FS8600 that is limited to that user/work station. For example, when user-based directory trees has been configured and Active Directory user

“bob” connects to the FS8600, the user will be presented with any available general shares, as well as with a share labeled “bob” that is visible to only that workstation.

Figure 1. Example of User Based Share View for “bob”

When the Active Directory user “jane” connects to the FS8600, that user will be presented with the “jane” share.

Figure 2. Example of User Based Share View for “jane”

The folder for that user must exist in the file system before the share can be accessed. This is because shares represent points of visibility into the file system, not folders or file systems themselves.

Consequently, some administrators may want to first create a dedicated “/users/” share within the NAS volume and modify the permissions of that share so that only administrators can manage the share or the contents of that share. This administrator-only share can also be provisioned as a hidden share (see below). The “homes” share can then be created using the user-based directory tree option, which will automatically live inside of “/users”.

Figure 3. CIFS Share View Example

As part of a new user creation process, an administrator can then proceed to create the directory in the user’s share for that user.

Figure 4. Example View Within the “users” Share

It should be noted that only one share per FS8600 cluster can have user-based directory trees enabled at a time.

Hidden files and folders

In the advanced configuration page for any CIFS share, the share can be configured to hide certain files or folders based on matching string names as configured. For NAS volumes that must expose the root of the NAS volume as a share, it is strongly suggested to add “/.clusterConfig/” to obfuscate the cluster configuration directory away from unprivileged users.

Hidden shares

When creating a share, a “$” character can be added to the end of the share name, which will hide or obfuscate away the existence of the share from end-user visibility.

Figure 5. Establishing a Hidden Share

From an end-user perspective, the share will no longer be exposed by default. Figure 6. Hidden Share No Longer Visible to Users

However, the share can still be accessed by entering the specific UNC for the share.

Figure 7. Hidden Share Accessed Using UNC Path

Share creation and permissions

When a share is created, it assumes the default permissions are inherited from the file system.

Consequently, an administrator will need to manage the permissions of the share before it can be accessed by users. As part of the initial permissions construction, appropriate users/groups should be given access to the share by managing the shares permissions directly. Some clients may also require that the “owner” of the share be altered from the default to a user present within the Active Directory domain before users can traverse into the share.

Users in the Active Directory grou p “Domain Admins” are granted root-like permissions over every share. When first provisioning a share, a user in this group should be used to easily build share schemas for a share.

Individual users can also b e granted “Full Access Rights” through the FluidFS CLI. Because an account that has been granted “Full Access Rights” does have super user privileges over all data sets, it is

generally only suggested for accounts used for backups or other maintenance tasks, but it can also be useful for initial share permission schema creation.

Through the CLI, a user can be granted through:

system authentication full-access-account set DOMAIN+username

To print a list of users with Full Access Rights:

system authentication full-access-account view

To remove Full Access Rights from an account:

system authentication full-access-account delete

Previous Versions

Windows clients can access the “previous versions” user level file protection feature built into the Windows platform. The items listed in previous versions will return a list of versions as associated with FS8600 file system-level snapshots.

Quotas

The security style selected for the volume will also determine which user database is used for quota assignments to user objects. NAS volumes configured for NTFS security will look to the configured Active Directory domain as well as to the locally configured accounts for user objects. UNIX will look to

传媒公司社会实践报告

传媒公司社会实践报告 实践,这是一段辛苦劳作的青春时光,也是一段收获颇丰的精彩年华,即使这段经历不是我毕生引以为傲、受益无穷的精神和物质财富,无论如何,它也必将成为我的人生画卷上不可忽略的真实一笔,以下是由XX为大家整理的相关 内容,欢迎阅读参考。 一、实习目的 重点参与和信文化传媒有限责任公司影视包后期的制作。了解了影视的性质,为毕业设计做了个定位,为更好的做出这个毕业设计去学习了promire等软件,解决了毕业设 计的技术问题。实习期间我参与了宣传片剪辑的制作,和这使得我离影视后期这个行业又迈出了更大的一步,因此我更坚定了自己做影视后期这个行业的决心。 二、实习单位及岗位情况介绍 本人XXXX年7月10日到8月10日在山西和信文化传媒有限责任公司实习,通过实习对影视后期的制作这方面市场的总体竞争环境有了更加具体的认识。通过面试我进入了山西和信文化有限责任公司成为了一名实习生。刚开始我就主动要求,接触多方面的工作。想借此来提高自己的实战经验,来弥补在大学期间所欠缺的。山西和信文化传媒有限责任公司,是专业从事影视制作、电视栏目运营、品牌策

划与推广、广告设计制作与发布、大型文化活动策划组织的新兴文化创意企业,而这方面恰好是我的兴趣所好。把自己的一些设计观念溶入到社会实践中去,是我的设计理念与实践所追求的。 三、实习内容及过程: 实习的第一项任务就是为一个企业的推广宣传片做剪辑。对于影片的剪辑从开始的强劲斗志到后来的丧失信心,让我明白更多的关于专业的知识。作为企业形象宣传片,更多的是体现企业的经营理念,以及企业的总体特征。而不是完全的体现个性化设计理念。接下来就是芦芽山景区推广的策划,我是第一次参与策划这方面的活动。在策划中,感受最多的是“品牌”两个字。 对于品牌的认识程度并不高的我,在设计时没有考虑更多整个行业的各个环节。提出确实可以给商家带来巨大的利益,只单纯依靠概念的偶然性太大,容易抄袭,并缺少系统性与连续性。如果企业是品牌驱动型的,就可以依靠系统、科学的品牌管理,将概念转化的品牌核心价值在消费者心目中广泛传播,建立起强有力的品牌联想与品牌个性,取得差异化的竞争优势。在设计之前,就应该把“品牌”完善,在整体的品牌战略指导下整合宣传文案。在文案的大体方针下,设计动画。只有这样才能准确高效的完成对外的品牌宣传。 品牌的竞争定位:认清自己在市场中的品牌地位,才能确定自己在市场中的品牌走向。清晰而准确的定性分析对 于制订营销宣传策略、确定音视频设计风格等营销行为都有着指导性的意义。

Dell服务器安装操作系统四种方法

Dell服务器安装操作系统四种方法 PowerEdge服务器手动安装操作系统.....................(适合有软驱软盘,硬盘有数据要保留的用户) Dell PowerEdge 1950 服务器Windows 2003安装手册 本文档介绍了在不使用Dell Open Manage Server Assistant (DOSA) 光盘引导的情况下,如何安装Windows 2003 Server 到您的Dell PowerEdge 1950 上。这个过程需要大约45 到60 分钟。 *通常不使用Dell Open Manage Installition 光盘引导安装主要是基于以下一些原因: 1. 原有的硬盘分区里有重要的数据, 倘若使用OMSA光盘安装, 将会删去硬盘上的原有分区; 2. 原有硬盘上有动态磁盘分区,DOSA光盘引导将导致系统自动重启, 而进入不了安装界面。 索引 步骤1. 识别您的Power Edge 服务器的系统配置 步骤2. 安装前的准备 步骤3. win2003安装步骤 步骤4. 驱动程序的安装 步骤1. 识别您的PowerEdge 服务器的系统配置 Note:具体信息随配置不同,请根据自己的配置正确安装。 常见1950 服务器集成的设备: ·集成两块网络适配器BroadCom 5708以太网卡; ·ATI Radeon(TM) ES1000显示卡; ·DRAC 5 远程控制卡(可选) ·常见使用的硬盘控制卡: - SAS5i控制器(安装内置磁盘) https://www.360docs.net/doc/009187804.html,/SAS-Non-RAID/R122665.exe (32bit) https://www.360docs.net/doc/009187804.html,/SAS-Non-RAID/R122666.exe (EMT64/x64) - SAS5E控制器(安装外置磁盘柜) - PERC 5I控制器(安装内置磁盘阵列) https://www.360docs.net/doc/009187804.html,/SAS-RAID/R120960.EXE (32bit) https://www.360docs.net/doc/009187804.html,/SAS-RAID/R120962.EXE (EMT64/x64) - PERC 5E控制器(安装外置磁盘阵列柜) 步骤2. 安装前的准备

DELL服务器错误代码

12G DELL服务器LCD信息代码 DELL服务器LCD信息代码的意思: E1114 Temp Ambient 系统周围环境温度超出允许范围。 E1116 Temp Memory 内存已超过允许温度,系统已将其禁用以防止损坏组件。E1210 CMOS Batt 缺少 CMOS 电池,或电压超出允许范围。 E1211 ROMB Batt RAID 电池丢失、损坏或因温度问题而无法再充电。 E12nn XX PwrGd 指定的稳压器出现故障。 E1229 CPU # VCORE 处理器 # VCORE 稳压器出现故障。 E122B 0.9V Over Voltage 0.9 V 稳压器电压已超过电压允许范围 E122C CPU Power Fault 启动处理器稳压器之后,检测到稳压器故障 E1310 RPM Fan ## 指定的冷却风扇的 RPM 超出允许的运行范围。 E1410 CPU # IERR 指定的微处理器正在报告系统错误。 E1414 CPU # Thermtrip 指定的微处理器超出了允许的温度范围并已停止运行。E1418 CPU # Presence 指定的处理器丢失或损坏,系统的配置不受支持。 E141C CPU Mismatch 处理器的配置不受 Dell 支持。 E141F CPU Protocol

系统 BIOS 已报告处理器协议错误。 E1420 CPU Bus PERR 系统 BIOS 已报告处理器总线奇偶校验错误。 E1421 CPU Init 系统 BIOS 已报告处理器初始化错误。 E1422 CPU Machine Chk 系统 BIOS 已报告机器检查错误。 E1618 PS # Predictive 电源设备电压超出允许范围;指定的电源设备安装错误或出现故障。 E161C PS # Input Lost 指定的电源设备的电源不可用,或超出了允许范围。 E1620 PS # Input Range 指定的电源设备的电源不可用,或超出了允许范围。 E1710 I/O Channel Chk 系统 BIOS 已报告 I/O 通道检查错误。 E1711 PCI PERR B## D## F## PCI PERR Slot # 系统 BIOS 已报告组件的 PCI 奇偶校验错误,该组件所在的 PCI 配置空间位于总线 ##,设备 ##,功能##。 系统 BIOS 已报告组件的 PCI 奇偶校验错误,该组件位于 PCI 插槽 #。 E1712 PCI SERR B## D## F## PCI SERR Slot # 系统 BIOS 已报告组件的 PCI 系统错误,该组件所在的 PCI 配置空间位于总线 ##,设备 ##,功能 ##。系统 BIOS 已报告组件的 PCI 系统错误,该组件位于插槽 #。 E1714 Unknown Err 系统 BIOS 已确定系统中存在错误,但无法确定错误来源。 E171F PCIE Fatal Err B## D## F## PCIE Fatal Err Slot # 系统 BIOS 已报告组件的 PCIe 致命错误,该组件所在的 PCI 配置空间位于总线 ##,设备 ##,功能 ##。系统 BIOS 已报告组件的 PCIe 致命错误,该组件位于插槽 #。 卸下并重置 PCI 扩充卡。如果问题仍然存在,请参阅排除扩充卡故障。 E1913 CPU & Firmware Mismatch

传媒公司实习报告

传媒公司实习报告范文 传媒公司实习报告(一) 转眼间。大一结束了。经过短暂的传媒公司实习。更加坚定了我作为一个传媒人的理想。 20xx年8月4号。我来到徐州矿务集团庞庄矿宣传科电台交通部开始了实习。职务是记者。我先是参观了电台的直播间。观看了节目的直播过程。也了解了录播节目的流程。我的实习老师吴罕对我说:“给你一星期的时间去熟悉工作内容和环境。有什么不明白的地方可以直接来问我。”起先我简单的认为怎么会需要那么长的时间呢?记者不也就是每天跑跑新闻写写稿件嘛。随后的一星期彻底改变了我的想法。 首先。每天早上九点钟。交通部的记者们要召开例会。每个人都要总结前一天的工作并阐述当天工作安排。如果接到活动通知。那么每个记者还要为活动出谋划策。说出自己的看法。遇到交通突发事件。工作安排也会重新计划。我发现。每天的例会。从来不会有人迟到。而且大家都会在会前10分钟就到达会议室。这种敬业精神让我钦佩不已。 会议结束后。我就坐在指定的办公区域阅读老师每天给我规定的新闻稿。了解交通部节目的风格。总结稿件的内容、方向。还要熟知平时和交通部往来密切的部门的联系方式。经过一星期近300篇稿件的阅读。我已经基本把握了节目的特色。但是我还是更期待第二个星期的真实的记者生活。 第二个星期开始了。在例会结束后。我跟着吴老师来到新闻发生地。用录音笔记录采访对象的每一句话。我发现。当记者必须要反应灵敏。在最快的时间内想出

有针对性有内涵的问题。并且需要和受访者进行有效的沟通。 一般采访都是在上午。下午就会在办公室里将受访者的音频整理成文字版。用专业的音频剪辑软件将音频剪辑出适合电台播出的声音稿。在整理音频的时候是对记者速记和听力的一大卡宴。然后写一篇当天采访新闻的稿件。因为我并不是新闻学专业的学生。所以写出的稿件往往存在较大的问题。这时老师总会耐心的指导。并帮助我把稿件修改到满意为止。如果第二天需要口播稿。那么记者当天还要在录音室自己录音。从这我看出记者并不是简单的写稿采访。现代社会需要一个编播导一体化高素质的人才了。当记者的另一大必备素质就是要有十足的耐心。比如去采访某些会议,是要等到会议结束后才会给记者采访的时间。而等待的过程中就成了各家媒体结识人脉的好机会。所以。做一个好记者并不是孤军奋战。团体的力量也是成功的关键。 两个星期实习使我深深体会到,要想取得较好的成绩,以下几点是我们必须做到的: 1、真诚待人。 作为一个新闻人。而我自己本身是个相对比较内向的。不太擅长主动和别人交流打交道。在此次实习过程中我也发现了自己的不足。比如在刚开始实习的几天内。我比较怯生。面对沉默不语的尴尬。自己有责任和义务去与别人主动交流。在工作的时候同样也要积极主动地与老师交流。在今后的社会工作中。工作不再是一个人所能完成的。那是几个人或是一个团队的工作。而且你还必须去帮助别人或是接受别人的帮助已完成工作。因此你不能期望你自己一个人就能完成任务。或是看到别人有困难也不去帮。虽然此次我是来实习的。

文化传媒公司暑期社会实践报告

文化传媒公司暑期社会实践报告 正式工作是在7月中旬,那时是夏天最热的时段。冒着蒸笼的暑气,开始自己进入社会的又一程。 一进公司才发现很多实习生,经了解有两个是早于我进来的,朱茜茜和张凯琳;也有和我一起进来的,陆驿、孟文、朱洁彦。第一天,我们的工作就是在网上搜寻关于各个省份的文化产业、文化项目、文化市场以及相关的文化艺术等信息,然后刚传到中国文化产业网的地方频道上。工作简单却也是极其枯燥烦闷的,机械化比较严重,不过通过对这些资料的搜集,了解了更多自己不知道的东西,这未尝不是一种获得呢。第三天,孙秋静让我搜集有关萧县书画的相关信息、南京市廊、书画之乡以及书画名人等资料。所以我从枯燥中提前跳了出来,剩下陆驿、孟文、洁彦、凯琳她们还在枯燥中纠结着。这些资料花费了我整整两天时间,看看自己的成果不禁惊讶:中国书画之乡那么多啊? 第二周一开始得到的是我们公司与安徽省宿州市萧县书画项目的协议书拟定的工作,这件工作看起来比较适合我,因为自认为在文字上还是有点造诣的。于是很兴奋,从资料的准备到文字的组织都很认真地做着,然而得到是不合格,还需要修改。结果修改来修改去还是不可以,一篇协议我搞了两天才搞定。当然期间也负责了河南省各市、地方宣传部的信息搜集工作。 第三周主要是拟定协议的年度详案,不知是不是自己笨,终究还是用来很长的时间搞懂上面领导的意思,因为我知道不要怀疑上级的表达能力及其他。这份工作在我和孙秋静之间来回转了好几回,最终让经理满意的就是在我走之前的一天。或许这算是我的功德圆满了吧。当案子孙做的时候我就帮网站找资料什么的,虽然枯燥无味,但是了解的东西还是不少的。有句话说的好:女人因为优秀而寂寞,男人因为寂寞而优秀。这个暑假就是寂寞中求生的历练。点点滴滴很多,本想细述,但很多东西无以表达。 整个社会实践过程中,我的确得到了一定的锻炼,并从其间学会了不少东西——这不仅是交流问题,同样了解了人们工作的心理状态,通过人的语言、表情、动作分析人的内心世界,公司管理的要领在这里给我以生动的展现。社会实践是活教材或许就是这样一种说法。我想这次实践对我进入未来的公司是有很大的帮助的。 三、实践结果: 经过三周的实习,我明白了很多,这些东西都是无形的资产。本次实践基本达到我预期的目的,就个人能力提升以及关系拓展方面不是做得很好,关键在于公司领导认为短期兼职生不固定,所以很多关系资源不会给我疏通的。就此我认识到,不论以后做什么,一定要有长期的打算,就算是会退出那个市场,但是关系资源是可以结合利用的。 自己暑假了解的管理学知识在现实中找到了验证,尤其是霍桑实验尤为明显。孙秋静的积极态度以及工作能力是大家有目共睹的,但也是因为能力的问题,使大家的工作态度显得非常消极。尽管她已经获得现任经理的认可,有很大可能

广告传媒公司实习报告范文

实习报告是指各种人员实习期间需要撰写的对实习期间的工作学习经历进行描述的文本。它是应用写作的重要文体之一。今天为大家精心准备了广告传媒公司实习报告,希望对大家有所帮助! 广告传媒公司实习报告 一、实习目的 重点参与嘉禾有限责任公司影视包后期的制作。了解了影视的性质,为毕业设计做了个定位,为更好的做出这个毕业设计去学习了promire等软件,解决了毕业设计的技术问题。实习期间我参与了宣传片剪辑的制作,这使得我离影视后期这个行业迈出了更大的一步,因此我更坚定了自己做影视后期这个行业的决心。 二、实习单位及岗位情况介绍 本人xxxx年7月10日到7月31日在嘉禾文化传媒有限责任公司实习,通过实习对影视后期的制作这方面市场的总体竞争环境有了更加具体的认识。通过面试我进入了嘉禾文化有限责任公司成为了一名实习生。刚开始我就主动要求,接触多方面的工作。想借此来提高自己的实战经验,来弥补在大学期间所欠缺的。嘉禾文化传媒有限责任公司,是专业从事影视制作、电视栏目运营、品牌策划与推广、广告设计制作与发布、大型文化活动策划组织的新兴文化创意企业,而这方面恰好是我的兴趣所好。把自己的一些设计观念溶入到社会实践中去,是我的设计理念与实践所追求的。 三、实习内容及过程 实习期间,我利用此次难得的机会,努力工作,严格要求自己,虚心向老员工求教,认真学习政治理论,党和国家的政策,学习构思、采访技巧、剪片操作等知识,利用空余时间认真学习一些课本内容以外的相关知识,掌握了一些基本的电视制作技能。并自己闲暇时间自己揣摩揣摩,又为以后在学习的过程中将这种在实践学习到的东西来帮助理论知识的学习。为以后真正走上工作岗位打下及坚实的基础。 “纸上得来终觉浅,绝知此事要躬行。”在短暂的实习过程中,我深深的感觉到自己所学知识的肤浅和在实际运用中的专业知识的匮乏,刚开始的一段时间里,对一些工作感到无从下手,茫然不知所措,这让我感到非常的难过。甚至开始有些怀疑自己是不是真的不行。在学校总以为自己学的不错,一旦接触到实际,才发现自己知道的是多么少,这时才真正领悟到“学无止境”的含义。这也许是我一个人的感觉。我认为新闻传播学是一门实践性很强而且综合性也是很强的学科,需要理论的指导,同时需要学习大量的不同领域的学科知识。熟话说新闻学就是无学嘛。但是其发展还是在实践中来完成的。所以,我们的新闻传播学教育应当与实践结合起来,采用理论与实际相结合的办学模式,具体说就是要处理好“三个关系”即课堂教育与社会实践的关系,以课堂为主题,通过实践将理论深化;假期实践与平时实践的关系,以假期实践为主要时间段;社会实践广度与深度的关系,力求实践内容与实践规模同步调进展。把这三个关系处理好,是我们学好新闻学的一个重要的方式。以后接触新的学科我

戴尔+DELL服务器的操作系统安装方法

戴尔DELL服务器的操作系统安装方法 注意:采用DOSA光盘引导和安装服务器系统,将使您服务器硬盘上的所有数据丢失,因此此方法仅供全新的服务器和确认数据有备份前提下的服务器安装 此安装方式仅支持零售版操作系统,如果是盗版光盘,如市面上常见的WINDOWS2003 3IN1版本则无法使用(DELL强烈建议您采用正版软件)安装前请确认您的服务器光驱为DVD 首先,将随机配送的Systems Management Tools and Documentation version6.0光盘放入服务器光驱,将服务器设置为光驱引导。 注:此版本dosa支持相应系统为: 1、Server 2003 sp2 ; 2、Server 2003 sp2 64 bit ; 3、windows 2003 SBS sp2; 4、Server 2008; 5、windows 2008 SBS\EBS x64; 6、Red hat Linux4.7 32bit; 7、Red hat Linux 4.7 64bit; 8、Red hat Linux5.2 32bit; 9、Red hat Linux 5.2 64bit; 10、Suse Linux10 sp2 64bit;11、ESX 3.5 U4 操作系统光盘版本一定要和DOSA 安装时选择的版本一致,否则DOSA会报告插入无效光盘。 支持的服务器类型: PowerEdge M610 PowerEdge M710 PowerEdge R610 PowerEdge R710 PowerEdge T610 PowerEdge T710 PowerEdge R410 PowerEdge T410 DOSA6.0 下载地址: pport/downloads/download.aspx?c=us&l=en&s=gen&releaseid=R215376&Syste mID=pwe_r710&servicetag=CLQRN2X&os=WNET&osl=en&deviceid=17861&devlib=0

Dell戴尔PowerEdgeR720服务器错误代码二

Dell/戴尔PowerEdge R720 服务器错误代码二 本空间免费为已购买客户提供终身售前以及售后技术支持 140 错误代码消息信息 MEM0701消息 Correctable memory error rate exceeded for .( 的可纠正内存错误比率超限。)详细信息内存可能无法操作。这是未来可能发生的不可纠正错误的早期迹象。操作重新安装内存模块。如果问题仍然存在,请参阅“获得帮助”。 MEM0702消息 Correctable memory error rate exceeded for .( 的可纠正内存错误比率超限。) LCD 消息 Correctable memory error rate exceeded for . Re-seat memory.( 的可纠正内存错误比率超限。重新安装内存。)详细信息内存可能无法操作。这是未来可能发生的不可纠正错误的早期迹象。操作重新安装内存模块。如果问题仍然存在,请参阅“获得帮助”。 MEM1205消息 Memory mirror redundancy is lost. Check memory device at location(s) .(内存镜像冗余已丢失。检查位置 的内存设备。)LCD 消息 Memory mirror lost on . Power cycle system.( 的内存镜像丢失。将系统关闭后再打开。)详细信息内存可能安装不正确,配置错误,或者发生故障。操作检查内存配置。重新安装内存模块。如果问题仍然存在,请参阅“获得帮助”。 MEM1208消息 Memory spare redundancy is lost. Check memory device at location .(内存备用冗余已丢失。检查位置 的内存设备。)LCD 消息 Memory spare lost on . Power cycle system.( 内存备份丢失。将系统关闭后再打开。)详细信息内存备份不再可用。操作重新安装内存模块。如果问题仍然存在,请参阅“获得帮助”。 MEM8000消息 Correctable memory error logging disabled for a memory device at location .(位置 的内存设备上可纠正内存错误日志已禁用。) LCD 消息 SBE log disabled on . Re-seat memory.( 上SBE 日志已禁用。重新安装内存。)详细信息错误将被纠正但不再记录。操作检查系统日志排查内存异常。重新安装位于 处的内存。 PCI1302消息 A bus time-out was detected on a component at bus device function .(总线 设备 功能 的组件上检测

戴尔公司供应链管理案例分析

戴尔公司供应链管理案例分析 戴尔公司供应链管理案例分析 在网络和信息技术迅速发展的今天,面对电子商务的出现和兴起,企业最关心的是如何通过电子商务解决供应链管理问题. 戴尔计算机公司于1984年创立,戴尔是目前全球领先的计算机系统直销商,同时也是电子商务基础建设的主要领导厂商.戴尔公司能够有如此成就离不开他日渐完善的供应链管理模式与销售模式. 戴尔公司的供应链管理策略主要是: 一是零库存.零库存的关键是按定单生产.这样就要求对用户的需求把握要很准.零库存也能最大限度地降低成本.戴尔在全球有6座工厂,包含马来西亚的槟城和中国的厦门.它将原本下给200多家供货商的订单集中,交给其中50家,但条件是他们在戴尔工厂旁边盖仓库,就近供货,不愿配合的就从供应链剔除.戴尔本身的零件库存不到2小时,接到订单后,再通知供货商送零件来,从进料到组装完出货只要4小时.从而达到了零库存,降低库存成本,不用为库存堆积而蒙受损失. 二是强化供应链上的信息流通速度和透明度.和戴尔做生意的供货商,等于是帮它管理库存,必须很清楚戴尔未来的出货计划,以免库存过多自己赔本、库存不够被戴尔撤换.对戴尔来说,也必须随时掌握整条供应链上的库存情形,确保上头每一家公司的运作都正常.这牵涉双向的信息流通和信任.它必须确保这一整条神经活得好好的,一小段出问题,整条神经就会瘫痪,在供应链的运作上,换供货商的成本很高,因为学习曲线是效率的损失.戴尔高度运用信息科技,架构连结客户、管理生产线和联络供货商的基本骨干,并要求供货商配合. 三是找到最短的到达客户路径,也就是说,用户对DELL直接提出需求.这种最短的途径最好的办法就是直销.直销可以直接获得客户的需求,最“懂”市场.戴尔计算机因采取直销方式,库存量低于同业,可将成本下降迅速回馈给消费者. 四是低成本.DELL采用的直接模式、生产方法和对供应链的管理有助于降低成本,包括DELL对办公地点的选择和对新技术的研发,也是着眼于不降低质量为前提的降低成本.这些削减的成本最后会反映到用户身上.他们买产品的价格就会趋于更加合

传媒公司实习日记20篇

传媒公司实习日记20篇 11月20日星期日晴 因为之前自己已经有两年的传媒兼职经验,所以这次学校安排的实习期我仍然选择了自己较为了解的有关广告、公关、传播、媒介、会展等行业的实习工作。只不过,鉴于两年的兼职经历,我决定改变自己的角色,挑战比之间的工作高一层次的公关活动策划文案,从配合各种活动传媒的舞蹈队队长转换到领导者,希望自己可以把这么长一段时间所学到的听到的看到的可以很好的利用起来。 这次我所实习的单位是隶属于太原市杏花岭青年就业创业服务中心的太原市美丽家族文化传媒有限公司。这家公司是一支具有专业水准、营运规范化的综合性演艺团队机构,公司自2010年9月1日成立至今,主要从事营业性演出的经营与经纪活动;大型赛事承接承办,展览展示服务;市场信息调研;设计、制作、代理、发布各类广告;企业文化发展、营销策划;企业管理及形象策划等。我相信,这段实习生涯一定可以为我的生活增添一些知识和色彩。 11月21日星期一晴 今天太原的天气已经有点阴冷,第一天正式去单位,有点兴奋也有点紧张,以前都只是双休日或者节假日工作,这样有规律的在一个单位工作还是第一次。一到公司就迎面遇上了当时面试我的韩经理,他是个很热情也很精明干练的人,他先带我到了我的办公地点,然后为我详细介绍了公司的流程和业务,还有我的工作任务。当然,更多的细节还需要我去花时间花精力去认真的了解。这家传媒公司和所有的传媒公司都有一样的通性,不是大公司,但是每个人的价值都很高,能感觉到都很忙,但正是这样,学到的东西一应也会很多,我会加油的。 韩经理也安排了我这明天的工作,他觉得我对广告、公关、传播、媒介、会展这些活动领域虽然了解,但是都很肤浅,他希望我可以结合之前的工作经验再花些时间细致深入的领悟这些活动的真正意义和策划重点。 11月22日星期二晴 公关活动策划虽然不是我大学所学的专业,但是也与工商管理有着千丝万缕的联系,尤其是在这两天我学习基础理论的过程中深深意识到原来我大学里学到的很多专业知识在其中都可以的好很好地运用。但是我也明白,理论归理论,应用归应用,虽然应用肯定是建立在理论之上,但是真正实践时往往需要结合客户的实际需要和大众的审美以及接受程度,所以很多活动往往需要策划人灵活运用,根据现场的情况来决定活动的具体进行。所以,我要面临的挑战真的很大。 学习了一天的理论并写好了学习心得交给了韩经理之后,从明天开始我就要接受公司的基本训练,也就是一些基本的礼仪和职员注意事项。和我一起学习的都是一些新加入公司的,大家都很积极也很优秀,实习一个月之后,之后就是例行的考核,竞争很激烈呀。 说实话,这几天感觉自己很茫然,可能是跨入一个新领域的原因,还不是太习惯,觉得自己没什么事干,只是在不停的看一些相关资料,不过我想一切会好的。 11月23日星期三晴 从早上开始我们一天都在学习和实践,训练的李老师还蛮严格的。上午的时间李老师在公司的会议室给我们进行教学,他为我们细致的介绍了公司的文化和发展,以及作为一名文化传媒公司的职员应该具备的基本情操和素质,也是一些比较理论的东西,感觉就像又回到了学校上课,但是大家都在很积极地进行笔迹和讨论,比起我前几天一个人苦闷的学习有趣了不少而且接受的更快了。 下午则换了一位张老师,他负责我们的实践,比上午那位老师幽默风趣了很多,他带我们很详细的参观了公司各部门并对其进行了解说,让我们对公司有了深入的了解,对以后的工作开展有了一定的帮助。 今天一天还算充实,明天将进行礼仪的学习,很是期待。 11月24日星期四晴 今天我们全体实习员工要进行了基本的礼仪教学,教我们礼仪的是一位既漂亮又有气质的女老师,大家的兴致一下子就上来了,据说这位礼仪老师在这个圈子里很有名呢。老师为我们每个人都印了有关员工礼仪的资料,上面介绍的很清楚,老师又为我们进行了真实的示范表演,比如看到客户会怎么样表现等等。介绍了一会老师就要求我们每个人都要上台来为大家实践表演,有的同事很大方,当然也有部分有点扭捏,万事开头难,我的表现还算适中,我相信,慢慢都会好的。

传媒公司实习报告范文

实习能帮助大学生树立市场意识,端正就业态度。大学生通过实习才能认知社会中的优胜劣汰,培养竞争意识,才能在实习中了解用人单位的需求和要求。今天为大家精心准备了传媒公司实习报告,希望对大家有所帮助! 传媒公司实习报告 本人自xxxx年6月28日至2012年1月20日在上海桦安电子有限公司实习,担任制片人、导演、演员等多职。 在完成徐汇区政府团委与天平街道“两新”团建小助理为期三个月的实习之后,经团区委老师介绍,我成为电信广告翼支付广告片的女主角,并于六月底参与该片的拍摄。在拍摄过程中,我熟知所有拍摄与制作流程,所以在拍摄完广告之后,我的角色便由演员转换至导演兼制片,并加入该公司,我的实习生涯开始了。 虽然做好了虚心学习,吃苦耐劳的准备,但我觉得我面前摆着的难题实在太多了。战战兢兢,忧心重重,毕竟我与该行业的专业人士相比,实际操作经验不足。但我自信满满,一切顺其自然,我相信都会变好的。 在公司期间,我先后完成了上海法液空公司的宣传片、上海徐汇区新进公务员汇报片、上海团市委创新创业大赛的广告片以及上海市新收犯监狱庆建监十五周年的专题片。在制作过程中,我担当导演一职,兼制片人的一角,从与客户接洽、创意设计、脚本确立、团队构建、实地拍摄、现场调度、后期设计与制作、与领导协商修改事宜。我参与每一个环节,尽心尽力完成每一个任务,尽管其中我有迷茫彷徨,不知所措,处事不得当等失败教训,但从中得到的经验就是我实习生涯中难能可贵的。 实习生活对我来说异常充实,我不但尝试并担任了各个职位(公务员、制片、导演、演员、创意设计、文案、后期剪辑、特效、配音、配乐),也在工作的过程中,专业能力也从充满学生气的稚嫩逐渐提升至初备专业气息的精通,也深谙许多商业规则。与领导们沟通,也是我在实习阶段学习的要点之一,如何揣摩领导的心思,做出既能让其满意又不失艺术水准,既能投其所好也在创作允许范围内,如何把握好这个度,什么话说到什么程度,都是我在实习过程中逐渐摸索学习的。 作为制片与导演,大局观很是重要,如何在繁琐的诸多事务中把握明确的方向,便是需要我不断加强大局观,当然同时也需要加强领导力。可以说,完成第一部片子是打下专业的基础,第二部片子是稳固与拓展,第三、四部片子便是达到熟练掌握的程度,对自我要求也更高,特别是我接触的都是政府机构部门的片子,其影响力,严肃性都是毋庸置疑的,这对我工作的细致性,考虑问题的周到性都是前所未有的挑战。 在实习期间,我正巧接触的是四类不同的影片,有广告、宣传片、汇报片、专题片,难度一点一点提升,对我专业技能方面的要求也越来越高,工作强度也越来越大,但我从中汲取的经验也成几何倍数递增。

DELL服务器BIOS设置

D E L L服务器B I O S设 置 集团标准化小组:[VVOPPT-JOPP28-JPPTL98-LOPPNN]

系统设置程序是一种BIOS程序,使您可以管理系统硬件和指定BIOS级的选项。通过系统设置程序,您可以: 在添加或删除硬件后更改NVRAM设置 查看系统硬件配置 启用或禁用集成设备 设置性能和电源管理阈值 管理系统安全 选择系统引导模式 系统设置程序也能供您指定引导模式,以便于安装操作系统: BIOS引导模式(默认)是标准的BIOS级引导接口。 UEFI引导模式是一种基于一体化可扩展固件接口规格(UEFI)(高于系统BIOS)的增强64位引导接口。有关此接口的详情,请参阅。 在系统设置程序BootSettings(引导设置)屏幕的?BootMode(引导模式)字段中选择引导模式。请参阅。指定引导模式后,系统将以该模式引导,然后即可通过该模式继续安装操作系统。然后,您必须将系统引导为同一引导模式(BIOS或UEFI)以访问安装的操作系统。试图从其它引导模式引导操作系统将导致系统在启动时立即停机。 注:操作系统必须兼容UEFI(例如,Microsoft??WindowsServer??2008x64版)才能通过UEFI 引导模式进行安装。DOS和32位操作系统不支持UEFI,只能通过BIOS引导模式进行安装。 进入系统设置程序 1.打开或重新启动系统。 2.系统显示以下信息时按键: =SystemSetup(=系统设置) 注:系统会在激活USB键盘后才响应。 如果按键之前已开始载入操作系统,请让系统完成引导过程,然后重新启动系统并再试一次。 响应错误信息

DELL服务器报警信息

DELL服务器LCD信息代码 DELL服务器LCD信息代码的意思: E1114 Temp Ambient 系统周围环境温度超出允许范围。 E1116 Temp Memory 内存已超过允许温度,系统已将其禁用以防止损坏组件。 E1210 CMOS Batt 缺少 CMOS 电池,或电压超出允许范围。 E1211 ROMB Batt RAID 电池丢失、损坏或因温度问题而无法再充电。 E12nn XX PwrGd 指定的稳压器出现故障。 E1229 CPU # VCORE 处理器 # VCORE 稳压器出现故障。 E122B 0.9V Over Voltage 0.9 V 稳压器电压已超过电压允许范围 E122C CPU Power Fault 启动处理器稳压器之后,检测到稳压器故障 E1310 RPM Fan ## 指定的冷却风扇的 RPM 超出允许的运行范围。 E1410 CPU # IERR 指定的微处理器正在报告系统错误。 E1414 CPU # Thermtrip 指定的微处理器超出了允许的温度范围并已停止运行。

E1418 CPU # Presence 指定的处理器丢失或损坏,系统的配置不受支持。 E141C CPU Mismatch 处理器的配置不受 Dell 支持。 E141F CPU Protocol 系统 BIOS 已报告处理器协议错误。 E1420 CPU Bus PERR 系统 BIOS 已报告处理器总线奇偶校验错误。 E1421 CPU Init 系统 BIOS 已报告处理器初始化错误。 E1422 CPU Machine Chk 系统 BIOS 已报告机器检查错误。 E1618 PS # Predictive 电源设备电压超出允许范围;指定的电源设备安装错误或出现故障。 E161C PS # Input Lost 指定的电源设备的电源不可用,或超出了允许范围。 E1620 PS # Input Range 指定的电源设备的电源不可用,或超出了允许范围。 E1710 I/O Channel Chk 系统 BIOS 已报告 I/O 通道检查错误。 E1711 PCI PERR B## D## F## PCI PERR Slot # 系统 BIOS 已报告组件的 PCI 奇偶校验错误,该组件所在的 PCI 配置空间位于总线 ##,设备 ##,功能 ##。系统 BIOS 已报告组件的 PCI 奇偶校验错误,该组件位于 PCI 插槽 #。

传媒公司实习报告

传媒公司实习报告 本人自xxxx年6月28日至2012年1月20日在上海桦安电子有限公司实习,担任制片人、导演、演员等多职。 在完成徐汇区政府团委与天平街道两新团建小助理为期三个月的实习之后,经团区委老师介绍,我成为电信广告翼支付广告片的女主角,并于六月底参与该片的拍摄。在拍摄过程中,我熟知所有拍摄与制作流程,所以在拍摄完广告之后,我的角色便由演员转换至导演兼制片,并加入该公司,我的实习生涯开始了。 虽然做好了虚心学习,吃苦耐劳的准备,但我觉得我面前摆着的难题实在太多了。战战兢兢,忧心重重,毕竟我与该行业的专业人士相比,实际操作经验不足。但我自信满满,一切顺其自然,我相信都会变好的。 在公司期间,我先后完成了上海法液空公司的宣传片、上海徐汇区新进公务员汇报片、上海团市委创新创业大赛的广告片以及上海市新收犯监狱庆建监十五周年的专题片。在制作过程中,我担当导演一职,兼制片人的一角,从与客户接洽、创意设计、脚本确立、团队构建、实地拍摄、现场调度、后期设计与制作、与领导协商修改事宜。我参与每一个环节,尽心尽力完成每一个任务,尽管其中我有迷茫彷徨,不知所措,处事不得当等失败教训,但从中得到的经验就是我实习生涯中难能可贵的。 实习生活对我来说异常充实,我不但尝试并担任了各个职位(公

务员、制片、导演、演员、创意设计、文案、后期剪辑、特效、配音、配乐),也在工作的过程中,专业能力也从充满学生气的稚嫩逐渐提升至初备专业气息的精通,也深谙许多商业规则。与领导们沟通,也是我在实习阶段学习的要点之一,如何揣摩领导的心思,做出既能让其满意又不失艺术水准,既能投其所好也在创作允许范围内,如何把握好这个度,什么话说到什么程度,都是我在实习过程中逐渐摸索学习的。 作为制片与导演,大局观很是重要,如何在繁琐的诸多事务中把握明确的方向,便是需要我不断加强大局观,当然同时也需要加强领导力。可以说,完成第一部片子是打下专业的基础,第二部片子是稳固与拓展,第三、四部片子便是达到熟练掌握的程度,对自我要求也更高,特别是我接触的都是政府机构部门的片子,其影响力,严肃性都是毋庸置疑的,这对我工作的细致性,考虑问题的周到性都是前所未有的挑战。 在实习期间,我正巧接触的是四类不同的影片,有广告、宣传片、汇报片、专题片,难度一点一点提升,对我专业技能方面的要求也越来越高,工作强度也越来越大,但我从中汲取的经验也成几何倍数递增。 可以说,我在有限实习的时间里面,涉足了诸多不同的工作环境,进行了各方面的锻炼,充分利用实习这一接触社会的机会,从各方面提升自我,使自己成为能适应社会融入社会并具有综合素质的专业人才,为后续就业打下了扎实的基础。

DELL双路服务器图解安装全过程

DELL双路服务器图解安装全过程 不管企业规模如何一般来说企业内部都会有自己的网络服务,任何网络服务的运行都离不开服务器。那么对于企业网络管理员来说如何安装服务器呢?相比普通计算机来说服务器在设置上又有哪些不同呢?安装服务器操作系统前要有哪些值得注意的地方呢?相比这些问题是中小企业网络管理员所关心的话题,那么今天就请各位IT168读者跟随笔者一起零距离体验DELL服务器安装全过程。 一、设备简介: 笔者使用的是DELL公司出品的机架式服务器PowerEdge 2950,他属于双插槽、四核2U机架式服务器,处理类型为Intel Xeon 5310,速度是1.6GHz,内存容量是2G。(如图1) 图1 正面能够看到电源按钮以及设备型号标识信息,在正面板有一个显示屏可以随时显示系统和设备运行状态。同时在前面板依次提供了光驱和VGA接口,还有两个USB接口,下面则是硬盘架。(如图2)

图2 在实际使用过程中我们点正面“i”按钮可以让显示屏在不同状态下进行切换,从而显示不同信息。(如 图3) 图3 PowerEdge 2950后面板提供的接口更多,从左向右依次是VGA接口,USB接口和两个千M以太网卡接口,同时在右边提供了双电源接口,保证设备具备双路供电系统让PowerEdge 2950可以更稳定的运行,电源的冗余也是服务器有别于普通计算机的一大特点。(如图4)

图4 除了常规接口外在下排接口上方提供了扩展插槽,我们可以从图中看到写有PCI 2,PCI 3的字样,在日后运行过程中我们可以通过这些插槽针对PowerEdge 2950服务器进行升级。(如图5) 图5 在PowerEdge 2950上部有一个锁扣,通过他可以将前面板锁死,同时PowerEdge 2950提供了三个SAS 接口的硬盘,这些硬盘都支持热插拔。(如图6)

戴尔公司客户关系管理

合肥工业大学 戴 尔 公 司 客 户 关 系 管 理 案 例 分 析 2013年10月31日

目录 摘要 (3) 引言 (3) 一.公司简介 (3) 二. 戴尔客户关系的背景 (4) 三、戴尔公司成功之道 (4) 四、戴尔公司客户关系管理实施战略 (4) 4.1、客户识别 (4) 4.2、客户忠诚 (4) 4、3 戴尔客户关系管理的相关技术 (5) 五、戴尔客户关系管理的分析 (6) 5.1 戴尔对客户的管理制度和策略 (6) 5.2戴尔客户关系管理的优势 (6) 六、与案例相关的理论 (7) 6.1 客户价值识别理论 (7) 6.2 客户忠诚理论 (7) 七、结论 (7) 八、总结 (8) 参考文献: (9)

【摘要】 随着中国企业信息化程度的提高和市场化进程的加速,利用客户关系管理量化和流程化客户管理,已成为中国企业提升自己竞争力的一大选择。越来越多的中国企业认为,能否建立一个具有弹性和高效的客户关系管理系统,成为增强客户忠诚度、提升自身核心竞争力的关键。客户信息是客户关系管理的基础。数据仓库、商业智能、知识发现等技术的发展,使得收集、整理、加工和利用客户信息的质量大大提高。在可以预期的将来,我国企业的信息交换成本将会降低,这将进一步推动互联网、电信业的发展,进而推动呼叫中心的发展。网络和电信的结合,使得企业以统一的平台面对客户。20世纪90年代提出的客户关系管理理论,经过十多年的发展,逐渐成熟起来,开始被越来越多的企业所关注。随着经济一体化的加快和竞争的加剧,企业已经逐步由传统的,以产品和规模为中心的粗放式经营管理模式,向以客户为中心、实现客户价值和达到企业利润最大化的集约式经营管理模式转变。 【引言】 现代市场竞争日趋激烈,企业管理不得不从过去的“产品”导向转变为“客户”导向,只有快速响应并满足客户个性化正瞬息万变的需求,企业才能在激烈的市场竞争中得以生存和发展。客户关系管理也就显得尤为重要。客户关系管理是现代电子商务活动的核心部分,对客户关系管理的重视是现代市场营销理念和商业运作方式转变的结果。客户关系管理具有广泛的市场价值和研究价值。而数据挖掘的出现,让决策者可以有效的总结规律,提高效率。只有企业能真正懂得利用客户关系管理,才可以指导企业高层决策者制定最优的企业营销策略,降低企业运营成本,增加利润,加速企业的发展。客户关系管理是一个不断加强与客户交流,不断了解客户需求,并不断对服务进行改进和提高以满足客户需求的连续过程,而戴尔作为生产电脑这一行业来说,市场竞争日趋激烈,在这种情况下增加企业销售额就成为首要问题,通过把握客户消费心理,重点培养客户忠诚度满足客户个性化需求来增加企业销售额。 一.公司简介 戴尔计算机公司于1984年由迈克尔·戴尔创立.戴尔电脑总部设在美国德克萨斯州奥丝登(Austin),戴尔公司是世界排名第一的计算机系统公司、计算机产品及服务的首要提供商,其业务包括帮助客户建立自己的信息技术及互联网基础架构。全球领先的IT产品及服务提供商戴尔公司,致力于倾听客户需求,提供客户所信赖和注重的创新技术与服务。戴尔在全球的产品销量高于任何一家计算机厂商主要是受益于独特的直接经营模式,戴尔也因此在财富500强中名列第25位。戴尔之所以能够不断巩固其市场领先地位,是因其一贯坚持直接销售基于标准的计算产品和服务。 二、戴尔客户关系的背景 在当今竞争如此激烈的计算机电脑市场,像外国的戴尔,惠普,三星,索尼东芝等以及中国的电脑巨商联想,早已入住中国多年,在中国市场也早已分得自己的一杯羹。而年轻的戴尔作为后入住中国市场的电脑生产商,又是如何能在这

相关文档
最新文档