Español dropdown-ico

Blue Coat Systems SGOS 4.x manual

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34

Ir a la página of

manuales de instrucciones parecidos

Buen manual de instrucciones

Las leyes obligan al vendedor a entregarle al comprador, junto con el producto, el manual de instrucciones Blue Coat Systems SGOS 4.x. La falta del manual o facilitar información incorrecta al consumidor constituyen una base de reclamación por no estar de acuerdo el producto con el contrato. Según la ley, está permitido adjuntar un manual de otra forma que no sea en papel, lo cual últimamente es bastante común y los fabricantes nos facilitan un manual gráfico, su versión electrónica Blue Coat Systems SGOS 4.x o vídeos de instrucciones para usuarios. La condición es que tenga una forma legible y entendible.

¿Qué es un manual de instrucciones?

El nombre proviene de la palabra latina “instructio”, es decir, ordenar. Por lo tanto, en un manual Blue Coat Systems SGOS 4.x se puede encontrar la descripción de las etapas de actuación. El propósito de un manual es enseñar, facilitar el encendido o el uso de un dispositivo o la realización de acciones concretas. Un manual de instrucciones también es una fuente de información acerca de un objeto o un servicio, es una pista.

Desafortunadamente pocos usuarios destinan su tiempo a leer manuales Blue Coat Systems SGOS 4.x, sin embargo, un buen manual nos permite, no solo conocer una cantidad de funcionalidades adicionales del dispositivo comprado, sino también evitar la mayoría de fallos.

Entonces, ¿qué debe contener el manual de instrucciones perfecto?

Sobre todo, un manual de instrucciones Blue Coat Systems SGOS 4.x debe contener:
- información acerca de las especificaciones técnicas del dispositivo Blue Coat Systems SGOS 4.x
- nombre de fabricante y año de fabricación del dispositivo Blue Coat Systems SGOS 4.x
- condiciones de uso, configuración y mantenimiento del dispositivo Blue Coat Systems SGOS 4.x
- marcas de seguridad y certificados que confirmen su concordancia con determinadas normativas

¿Por qué no leemos los manuales de instrucciones?

Normalmente es por la falta de tiempo y seguridad acerca de las funcionalidades determinadas de los dispositivos comprados. Desafortunadamente la conexión y el encendido de Blue Coat Systems SGOS 4.x no es suficiente. El manual de instrucciones siempre contiene una serie de indicaciones acerca de determinadas funcionalidades, normas de seguridad, consejos de mantenimiento (incluso qué productos usar), fallos eventuales de Blue Coat Systems SGOS 4.x y maneras de solucionar los problemas que puedan ocurrir durante su uso. Al final, en un manual se pueden encontrar los detalles de servicio técnico Blue Coat Systems en caso de que las soluciones propuestas no hayan funcionado. Actualmente gozan de éxito manuales de instrucciones en forma de animaciones interesantes o vídeo manuales que llegan al usuario mucho mejor que en forma de un folleto. Este tipo de manual ayuda a que el usuario vea el vídeo entero sin saltarse las especificaciones y las descripciones técnicas complicadas de Blue Coat Systems SGOS 4.x, como se suele hacer teniendo una versión en papel.

¿Por qué vale la pena leer los manuales de instrucciones?

Sobre todo es en ellos donde encontraremos las respuestas acerca de la construcción, las posibilidades del dispositivo Blue Coat Systems SGOS 4.x, el uso de determinados accesorios y una serie de informaciones que permiten aprovechar completamente sus funciones y comodidades.

Tras una compra exitosa de un equipo o un dispositivo, vale la pena dedicar un momento para familiarizarse con cada parte del manual Blue Coat Systems SGOS 4.x. Actualmente se preparan y traducen con dedicación, para que no solo sean comprensibles para los usuarios, sino que también cumplan su función básica de información y ayuda.

Índice de manuales de instrucciones

  • Página 1

    Blue Coat ® Systems Pro xy SG ™ SGOS 4.x Upgr ade Guide[...]

  • Página 2

    Blue Coat SGOS 4.x Upgrade Guide ii Contact Inf or mation Blue Coat Syst ems Inc. 650 Almanor A venue Sunnyvale, California 94085 North America (USA) T oll Fr ee: 1.866.362.2628 (86 6.36.BCOA T) North America Direct (USA): 1.408.220.2270 Asia Pacific Rim (Japan): 81.3.5425.8492 Europe, Mid dle East, and Africa (U nited Kingdom): +44 (0) 1276 854 10[...]

  • Página 3

    iii Contents Contact Information Chapter 1: Upgrading—Ove rview Changes Between SGOS 3. x and SGOS 4.x ....................... ................. ................ ............... ................ ... ............ 5 About the Document Organization ............ ................. ................. .............. ................. ................. ..[...]

  • Página 4

    Blue Coat SGOS 4.x Upgrade Guide iv[...]

  • Página 5

    5 Chapter 1: Upgr ading—Ov er view Blue Coat ® stro n g l y re c om m en d s t h at yo u rea d th i s d o cu m e n t b e fo re at te m p t i ng t o u p gr ad e to S GO S 4.x from pr evious Proxy SG operating systems. Existing features and policies might not perform as with previous versions, and upgrading to this version might require some addit[...]

  • Página 6

    Blue Coat SGOS 4.x Upgrade Guide 6 • Blue Coat ProxySG Configuration and Management Guide • Blue Coat Pr oxySG Content Policy Language Guide • Blue Coat Pr oxySG Command Line Interface Ref erence Document Con v entions The following section li sts the typographical and Command Line Interface (CLI) syntax conventions used in this manual. T abl[...]

  • Página 7

    7 Chapter 2: Upgr ade Beha vior , General Upgrading When upgrading to SGOS 4.x from SGOS 3.2.4 or higher , the Pr oxy SG saves a copy of the original configurations. Th ese confi gurations remain unaf fected when configuring featur es going forward . If you downgrade to the previous SGOS version, th e saved configuration is us ed and the Pr oxy SG [...]

  • Página 8

    Blue Coat SGOS 4.x Upgrade Guide 8 Summar y of Changes to the Upgrade Process • The upgrade path must include a sy stem that shows all possible depr ecation warnin gs, so that these can be corr ected in advance of the upgrad e, to avoid policy compilation failu res after upgrading. Migrating through SGOS 3.2.4 or greater satisfies th is requireme[...]

  • Página 9

    Chapter 2: Upgrade Beh avior, General 9 Redoing an Upgr ade from SGOS 3.2.4 When the initial SGOS 4.x upgrade occurs, any comp atible config urations are converted. This only happens the first time you upgrade; i f you later downgrade to a pr e-SGOS 4.x version by selecti ng an earlier image on your system, make configuration changes, and re-instal[...]

  • Página 10

    Blue Coat SGOS 4.x Upgrade Guide 10 Changing Between SGOS 4.x V ersions When moving fr om one SGOS 4.x r elease to anot her SGOS 4.x release, the system maintains all settings. Changes made after an upgrade continue to be available after a subsequent downgrade as long as the setting is re levant to the downgraded release. Note: When upgrading or do[...]

  • Página 11

    Chapter 2: Upgrade Beh avior, General 11 Included W ebsense Offbo x Content Filtering For W ebsense of f-box support only . Included ICAP Services External virus and content scanning with ICAP servers. Included Bandwidth Management Allows you to classify , control, and, if requir ed, limit the amount of bandwidth used by differ ent classes of netwo[...]

  • Página 12

    Blue Coat SGOS 4.x Upgrade Guide 12 Hardware Suppor ted W ith SGOS v4.x, support for the Proxy SG Series 600 and 700 systems has been dr opped. Users with these systems must either upgrade their hardwar e or stay with SGOS v3.x. Blue Coat supports the following hardware: • Proxy SG Series 200 • Proxy SG Series 400 • Proxy SG Series 800 • Pr[...]

  • Página 13

    13 Chapter 3: F eature-Specific Upgrade Beha vior This chapter provides critical information concerning how specific features are affected by upgrading to SGOS 4.x (and i f relevant do wngrading fr om) and provides actions admi nistrators must or are recommended to take as a result of upgrading. This chapter contains the foll owing sections:. • &[...]

  • Página 14

    Blue Coat SGOS 4.x Upgrade Guide 14 Global Enab le/Disable Switch In SGOS 4.x, you can enable or disable access loggi ng on a global basis, both through the Management Console ( Access Logging>General>Global Settings) and the CLI. When logging is disabled , that setting overrides bo th policy and logging configuration. When access logging is [...]

  • Página 15

    Chapter 3: Feature-Specific Upgrade Beh avior 15 P eer-to-P eer The Proxy SG recognizes peer -to-peer (P2P) activity rela tin g to P2P file sharing applications. By constructing policy , you can control, block, and lo g P2P activity and limit th e band width consumed by P2P traffi c. Upgrade Beha vior • A new default format and a log called p2p i[...]

  • Página 16

    Blue Coat SGOS 4.x Upgrade Guide 16 A new substituti on modifier—label(N)— has been added. It is used in conjunction with the client.host substituti on variable in defi ning Policy Substi tution Realms. For exa mple, $(client.host:label(2)) could be used in the definiti on of a Policy Substitution Realm to set the user name from the results of [...]

  • Página 17

    Chapter 3: Feature-Specific Upgrade Beh avior 17 A uthentication T wo new r ealms—policy substitution and Ob lix COREid—have been added in SGOS 4.x. • COREid Realm—The Pr oxy SG can be configur ed to consul t an Oblix COREid (f ormerly known as Oblix NetPoint) Access Server for authentica tion and session manage ment decisions. This req u i[...]

  • Página 18

    Blue Coat SGOS 4.x Upgrade Guide 18 Upgrade Beha vior As BWM is a new feature, upgrade issues are restricted to pr eviously existing bandwidth configuration that will now be subs um ed into the BWM configuration. BWM does not r eplace the older bandwidth limiting featur es currently available in Streaming (max streaming, max Real and ma x MMS). It [...]

  • Página 19

    Chapter 3: Feature-Specific Upgrade Beh avior 19 On an upgrade, cached HTTP objects ar e usable. On a downgrade, cached H TTP objects fetched after the upgrad e are re-fetched. Documentation Ref erences • Chapter 6, “Confi guring Pr oxies,” in the Blue Coat Pr oxySG Configuration and Management Guide • The Blue Coat Content Pol icy Language[...]

  • Página 20

    Blue Coat SGOS 4.x Upgrade Guide 20 Endpoint Mapper and SOCKS Compression The Endpoint Mapper proxy accelerates Microsoft RPC traffic between branch and main of fices, automatically creating TCP tunnels to p orts wher e RPC services ar e r unning. The Endpoint Mapper proxy can be used in both explicit and transpar ent mode. Using SOCKS compr ession[...]

  • Página 21

    Chapter 3: Feature-Specific Upgrade Beh avior 21 • SGOS#(config external-services) view htt p icap-patience details • SGOS#(config external-services) view htt p icap-patience header • SGOS#(config external-services) view htt p icap-patience help • SGOS#(config external-services) view htt p icap-patience summary Documentation Ref erences Cha[...]

  • Página 22

    Blue Coat SGOS 4.x Upgrade Guide 22 • user= • user .domain= • user .x509.issuer= • user .x509.serialNumber= • user .x509.subject= The authenticated= condition can be used to test whether or not the user information is available. Forward layer r ules contai ning the ot her new authentication conditions wi ll fail to match if ther e is no a[...]

  • Página 23

    Chapter 3: Feature-Specific Upgrade Beh avior 23 CPL Syntax that was deprecated in SGOS 3.x has been abandoned in SGOS 4.x. Policy that includes abandoned syntax should be cor rected befor e yo u attempt to upgrade the system. The standard upgrade path and process are designed to ensur e the integrity of policy and the securi ty of your network. Bl[...]

  • Página 24

    Blue Coat SGOS 4.x Upgrade Guide 24 protocol= url.scheme= proxy_address= proxy.address proxy_card= proxy.card proxy_port= proxy.port release_id= release.id= release_version= release.version= request_header.<name>= request.header.<name>= request_header_address.<name>= request.header.<n ame>.address= request_x_header.<name&[...]

  • Página 25

    Chapter 3: Feature-Specific Upgrade Beh avior 25 prefetch() pipeline() proxy_authentication() authenticate() reflect_vip() reflect_ip() service() allow or deny trace_destination() trace.destination() trace_level() trace.level() trace_request() trace.request() trace_rules() trace.rules() T able 3.10: Abandoned P olicy Actions Abandoned Synta x Repla[...]

  • Página 26

    Blue Coat SGOS 4.x Upgrade Guide 26 request_header.Content-Language request.h eader.Content-Language request_header.Content-Length request.h eader.Content-Length request_header.Content-Location request.h eader.Content-Location request_header.Content-MD5 request.h eader.Content-MD5 request_header.Content-Range request.h eader.Content-Range request_h[...]

  • Página 27

    Chapter 3: Feature-Specific Upgrade Beh avior 27 request_header.User-Agent request.h eader.User-Agent request_header.Vary request.header.Va ry request_header.Via request.header.Vi a request_header.WWW-Authenticate request.h eader.WWW-Authenticate request_header.Warning request.header.Wa rning request_header.X-BlueCoat-Error request.h eader.X-BlueCo[...]

  • Página 28

    Blue Coat SGOS 4.x Upgrade Guide 28 Documentation Ref erences Appendix D, “Substitutions,” in the B lue Coat Cont ent Policy Language Gu ide Exception P ages A number of built-in exception pages have been a dded to SGOS 4.x to send information back to the user under operational contexts that ar e known to occur . New exception pages include: re[...]

  • Página 29

    Chapter 3: Feature-Specific Upgrade Beh avior 29 • HTML Notificati on ❐ notify ❐ notify_missing_cookie • Compression ❐ transformation_err or ❐ unsupported_encoding ❐ invalid_res ponse • ICAP ❐ icap_error (should be used in place of the existing icap_communications_err or exception page) On a downgrade to SGOS 3.2.4, the ProxySG r [...]

  • Página 30

    Blue Coat SGOS 4.x Upgrade Guide 30 On an upgrade, objects that cannot be named by the user are automatically updated to have the underscore character pr efix the object name. Documentation Ref erence Chapter 14, “VPM,” in the Blue Coat ProxySG Configuration and Management Guide Securing the Ser ial P or t When the secur e serial port is enable[...]

  • Página 31

    Chapter 3: Feature-Specific Upgrade Beh avior 31 SGOS#(config ssl)import keyring show|no-show keyring_id SGOS#(config ssl)import certificate keyr ing_id SGOS#(config ssl)import signing-request keyring_id SGOS#(config ssl)import ca-certificate k eyring_id SGOS#(config ssl)import external-certifi cate keyring_id Documentation Ref erences Chapter 7, ?[...]

  • Página 32

    Blue Coat SGOS 4.x Upgrade Guide 32[...]

  • Página 33

    33 Inde x A access logging default logs, protocols 14 global enable/disable switch, CLI commands 14 global enable/disable switch, ov ervi ew 14 new features in 13 P2P log, format 15 P2P upgrade behavior 15 substitutions, new 15 authentication BCAAA, installing 17 COREid realm, added 17 Policy Substitution realm, added 17 upgrade behavior 17 B bandw[...]

  • Página 34

    Blue Coat SGOS 4.x Upgrade Guide 34 substitutions abandoned 25 additional 15 substitution syntax, abandoned 23 U upgrading changes betwee n SGOS 3.2.3 and SGOS 4.x 5 paths, required 7 restore-cacheos4-config command, upgrading 9 restore-sgos2-config command, using 9 restore-sgos3-config command, using 9 V VPM object naming 29 UTF-8 encoding 29[...]