1587051532Index.Pdf

1587051532Index.Pdf

1532xix.fm Page 344 Monday, October 18, 2004 4:38 PM 1532xix.fm Page 345 Monday, October 18, 2004 4:38 PM I N D E X RSVP, 99–101 Numerics TE, 89–90 traffic-handing mechanisms, 81–83 802.11 networks, QoS, 276 work-conserving queuing, 93–96 agents, 146–147, 192 capture, 234 A embedded, 72 enabling, 148 ABR (available bit rate), 294 profiling, 39 Abstract Syntax Notation One (ASN.1), 147 SAA, 72, 158, 199 access. See also security agreements (SLAs) storage-area networks, 269 Cisco NetFlow, 73–74 transactions, 232 defining, 65–66 access control lists (ACLs), 81, 95 delivery, 66–67 accountability, delivery of service, 133 management, 67–68 accounting, 143 monitoring, 76–77 accounts, transactions, 230 profiling, 74–76 acknowledgments (ACKs), 60, 254 requirements, 68–73 ACLs (access control lists), 81, 95 alarms, 142 active agents, 192 algorithms Address Resolution Protocol (ARP), 236 queuing, 82, 91. See also queuing administration. See also management queue-servicing, 81 APM, 5 alignment, business/technical methodologies, 30–32 benefits of, 16 allocation end-to-end systems, 7 ports, 243 isolation, 7–8 QoS, 297 lifecycles, 9 resources, 80–81, 108–109 monitoring SLAs, 9 amalgamation, 62 overview of, 6 analysis sharing information, 8 business-impact, 124 CRM systems, 74 capacity planning, 183–186 oversight, 26 failure, 181 QPM, 109 modeling, 51 SLAs, 67–68 predictive performance, 15 system, 13 queries, 257–258 TCO, 25 root-cause, 142, 150 tools, 79 SLA compliance, 180 configuration, 83–84 systems, 77 DiffServ, 101–102 TCO, 25–27 FIFO, 92–93 thresholds, 49 IntServ, 98–99 triggers, 14 MPLS, 85–88 virtual environments, 176 networks resource allocation, 80–81 analyzers non-work–conserving queuing, 96–98 data, 204 provisioning, 83–84 network, 234 queuing, 91–92 profiling, 38 1532xix.fm Page 346 Monday, October 18, 2004 4:38 PM 346 any-to-any communication any-to-any communication, 270 assessment APIs (application programming interfaces), 190 applications, 14 APMs (application performance management), demarcation points, 128–130 5, 127 new application impact, 52 benefits of, 16 assignment end-to-end systems, 7 associated applications, 24 isolation, 7–8 demarcation points, 128–130 lifecycles, 9 QoS, 134–137 monitoring SLAs, 9 ATM (Asynchronous Transfer Mode), 86 overview of, 6 authentication, 110 services, 132–134 authorized transactions, 230 sharing information, 8 automation application programming interfaces (APIs), 190 capacity planning, 185 application-aware probes, 158 polling, 146 application-development teams, 13 availability, 157 applications, 13, 29 defining, 65–66 analyzers, 38 delivery, 66–67 architecture, 217–219, 256 available bit rate (ABR), 294 assessment, 14 average bytes per frame, viewing, 241 bandwidth-bounded, 42, 59–61 baselining, 48 business-critical, 29 B capture points, 55 characterizing, 45 background classification, 40–42, 289–290 data, 177 coexisting, 28 traffic, 118, 177. See also traffic data flow, 49 backplane utilization, 160 delivery, 11, 61–63 balancing metrics, 154 deployment, 50 bandwidth, 42 end-to-end models, 284–297 application consumption of, 7 interactive, 217 increasing, 61 latency-bounded, 40, 58–59 optimizing, 59–61 mission-critical, 291 priority, 29 monitoring, 198, 205 profiling, 36 probes, 72 windows, 254 status, 43 base networks, building, 118 storage solutions, 272 base transactions, defining, 43, 230. See also threads, 40 transactions turns, 37, 243 baselining, 47–50, 155 web-based, 291 businesses, 122 workloads, 10 collection, 185 architecture environments, 43 applications, 217–219, 256 establishing, 287 delivery requirements, 221–222 infrastructure, 107–108 hub-and-spoke, 135 performance, 173–174 policy management, 109–112 technical baselines, 121 ARP (Address Resolution Protocol), 236 BC (committed burst), 135 ASN.1 (Abstract Syntax Notation One), 147 Be (excess burst), 135 1532xix.fm Page 347 Monday, October 18, 2004 4:38 PM CLEC (competitive local exchange carrier) 347 benchmarking, 121 TCO, 25 benefits of TE, 90 APM, 16 validating, 179 TCO, 27 capacity Berkeley Standard Distribution (BSD), 204 increasing, 61 BGP (Border Gateway Protocol), 83 planning, 66, 174, 183–186 big bang deployments, 119–120 capturing big-picture view, 216 capture points, 55 bits, DE, 135 data, 54 Border Gateway Protocol (BGP), 83 traces, 218–219, 234–235 bottlenecks, identifying, 289 traffic, 218 boundaries, defining transactions, 248 transactions, 236 BPDU (bridge protocol data unit), 204 CAR (committed access rate), 81 branches, transactions, 232 case studies bridge protocol data unit (BPDU), 204 QoS, 259–265 broadcast traffic (etherStatsBroadcastPkts), 161 SLAs, 246–253 BSD (Berkeley Standard Distribution), 204 transactions BSM (business service management), 133 optimizing, 253–259 building profiling, 229–246 baseline environments, 43 categorizing business transactions, 230 baselines, 48 CBR (constant bit rate), 294 business applications, 7 CBWFQ (class-based weighted fair queuing), 81, 95 business baselines, 122 CDP (Cisco Discovery Protocol), 149 business criteria category (SLAs), 68–69 Cell Loss Priority (CLP), 135 business management, 150 cell switching, ATM, 86 business objectives, 132–134 central site (hub), 135 business requirements, 127 channel service unit/data service unit business service management (BSM), 133 (CSU/DSU), 295 business transactions characterizing applications, 45 optimizing, 253–259 CIFS (Common Internet File System), 271 profiling, 229–246 CIR (committed information rate), 135 business-critical applications Cisco Discovery Protocol (CDP), 149 defining, 22–24 Cisco IOS priority, 29–30 show commands, 201 requirements, 27–29 traffic-conditioning mechanisms, 136 TCO, 25–27 Cisco NetFlow, 31, 73–74 technical alignment, 30–32 Cisco Networking Service (CNS), 148, 213 business-impact analysis, 124 Cisco Tag Switching implementations, 86 bytes Cisco Works, 31 transfers, 245 class-based weighted fair queuing (CBWFQ), viewing, 241 81, 95 classification, 81, 84, 135–136 applications, 40–42, 289–290 C devices, 112 management systems, 141–151 calculations clean transactions, 235 measurements, 72 cleaning traces, 236 SPF, 90 CLEC (competitive local exchange carrier), 291 1532xix.fm Page 348 Monday, October 18, 2004 4:38 PM 348 CLI (command-line interface) CLI (command-line interface), 109, 147, metrics, 250 199–204 QoS, 109, 297 client, network, and server (CNS), 148, 213 RSPAN, 164 clients SPAN, 163 overloading, 220 storage-area networks, 269–276 processing time, 252 TCO, 25–27 CLP (Cell Loss Priority), 135 thresholds, 49 CNS (Cisco Networking Service), 148, 213 validation, 180 CNS (client, network, and server), 148, 213 conflict-prevention tools, SLAs, 67 coexisting applications, 28 congestion, troubleshooting, 176 collection congestion-avoidance (WRED) procedures, 135 baselining, 185 connections key date points, 70 any-to-any communication, 270 methods, 72 bandwidth-bounded applications, 42 metrics, 157–165 critical switched ports, 71 points, 246–253 latency, 35 collisions, Ethernet, 161 WLANs, 276–284 command-line interface (CLI), 109, 147 consistency commands APM, 6 debug, 202–203 transaction captures, 236 frame-relay ip rtp header-compression, 263 constant bit rate (CBR), 294 get, 245 constraint-based routing, 90 ip rtp compression-connections, 264 consumption, monitoring, 10 ip rtp header-compression, 263 contingency plans, deployment, 121–124 show, 201 control consoles, reporting to, 192 show processes cpu, 204 conversation, 38 snmpwalk, 49 capture points, 235 committed access rate (CAR), 81 paths, 157, 247 committed burst (Bc), 135 conversational maps, 240 committed information rate (CIR), 135 COPS (Common Open Policy Service), 110 Common Internet File System (CIFS), 271 core devices, QoS, 113 Common Open Policy Service (COPS), 110 core networks, CPE measurements, 72 common sense, 179 correlation of events, 142 communication CPE (customer premises equipment), 72, 295 deployment, 124 CQ (custom queuing), 81, 94 directory systems, 110 credit, SLAs, 66 SLAs, 67 critical switched port connections, 71 comparing trace files, 237–246 CRM (customer relationship management), 74 competitive local exchange carrier (CLEC), 291 cRTP (Real-Time Transport Protocol header complex transactions, 230 compression), 263 compliance, SLA analysis of, 180 CSU/DSU (channel service unit/data service computing resources, forecasting, 10 unit), 295 Compuware Application Vantage, 234 custom queuing (CQ), 81, 94 configuration customer premises equipment (CPE), baselining, 48 72, 295 CLI, 109 customer relationship management (CRM), 74 management, 143 customer service, SLAs, 66 1532xix.fm Page 349 Monday, October 18, 2004 4:38 PM development of application-development teams 349 pyramid model, 139–141 D responsibilities, 12 traffic, 274 data analyzers, 204 troubleshooting, 221–222 data collection, 108. See also baselining verifying, 61–63 data flow, application, 49 demarcation points, assigning, 128–130 data link connection identifier (DLCI), 88 dense wavelength-division multiplexing Data Link Switching (DLSw), 75 (DWDM), 88 data transfers, 290 dependency failures, 220 database administrator (DBA), 211 deployment database management system (DBMS), 160 application-deployment teams, 13 data-collection method, 159 applications, 50, 57 DBA (database administrator), 211 baselining, 155 DBMS (database management system), 160 big bang, 119–120 DE (Discard Eligible) bits, 135 contingency plans, 121–124 debug commands, 202–203 domains, 112–113 defining infrastructure, 107–108 base transactions, 43, 230 NetFlow, 165 business-critical applications,

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    20 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us