Case 6:20-cv-00272-ADA Document 65-4 Filed 03/14/22 Page 1 of 6
`
`Exhibit 2
`
`

`

`Case 6:20-cv-00272-ADA Document 65-4 Filed 03/14/22 Page 2 of 6
`
`I I I I I I I I •
`CISCO .
`
`Network Management Fundamentals
`
`A guide to understanding how network management
`I works
`techfl<>I~
`
`clM:Ol)rost.eom
`
`Alexander Clemm. Ph.D.
`
`

`

`Case 6:20-cv-00272-ADA Document 65-4 Filed 03/14/22 Page 3 of 6
`
`ii
`
`Network Management Fundamentals
`Alexander Clemm, Ph.D.
`Copyright© 2007 Cisco Systems, Inc.
`Published by:
`Cisco Press
`800 East 96th Street
`Indianapolis, IN 46240 USA
`All rights reserved. No part of this book may be reproduced or transmitted in any form or by any means, electronic or mechanical,
`including photocopying, recording, or by any information storage and retrieval system, without written permission from the pub-
`lisher, except for the inclusion of brief quotations in a review.
`Printed in the United States of America 1 2 3 4 5 6 7 8 9 0
`First Printing November 2006
`LIBRARY OF CONGRESS CATALOG CARD NUMBER: 2004110268
`ISBN: 1-58720-137-2
`
`Warning and Disclaimer
`This book is designed to provide information about network management. Every effort has been made to make this book as complete
`and as accurate as possible, but no warranty or fitness is implied.
`The information is provided on an “as is” basis. The authors, Cisco Press, and Cisco Systems, Inc., shall have neither liability nor
`responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book or from
`the use of the discs or programs that may accompany it.
`The opinions expressed in this book belong to the author and are not necessarily those of Cisco Systems, Inc.
`
`Corporate and Government Sales
`Cisco Press offers excellent discounts on this book when ordered in quantity for bulk purchases or special sales. For more informa-
`tion, please contact: U.S. Corporate and Government Sales
`1-800-382-3419 corpsales@pearsontechgroup.com
`International Sales
`For sales outside of the U.S. please contact:
`1-317-581-3793 international@pearsontechgroup.com
`
`Feedback Information
`At Cisco Press, our goal is to create in-depth technical books of the highest quality and value. Each book is crafted with care and pre-
`cision, undergoing rigorous development that involves the unique expertise of members from the professional technical community.
`Readers’ feedback is a natural continuation of this process. If you have any comments regarding how we could improve the quality
`of this book or otherwise alter it to better suit your needs, you can contact us through e-mail at feedback@ciscopress.com. Please
`make sure to include the book title and ISBN in your message.
`We greatly appreciate your assistance.
`
`Trademark Acknowledgments
`All terms mentioned in this book that are known to be trademarks or service marks have been appropriately capitalized. Cisco Press
`or Cisco Systems, Inc., cannot attest to the accuracy of this information. Use of a term in this book should not be regarded as affect-
`ing the validity of any trademark or service mark.
`
`

`

`

`

`Case 6:20-cv-00272-ADA Document 65-4 Filed 03/14/22 Page 5 of 6
`
`iv
`
`About the Author
`Dr. Alexander Clemm, Ph.D. is a Senior Architect with Cisco Systems. He has been involved
`with integrated management of networked systems and services since 1990. Alex has provided
`technical leadership for many network management development and engineering efforts from
`original conception to delivery to the customer. They include management instrumentation of
`network devices, turnkey management solutions for packet telephony and managed services, and
`management systems for Voice over IP networks, broadband access networks, and provisioning of
`residential subscriber services. Alex has approximately 30 publications related to network
`management and 15 patents pending. He is on the Organizing Committee or Technical Program
`Committee of the major technical conferences in the field, including IM, NOMS, DSOM, IPOM,
`and MMNS, and he served as Technical Program Co-chair of the 2005 IFIP/IEEE International
`Symposium on Integrated Network Management. He holds a Ph.D. degree from the University of
`Munich and a Master’s degree from Stanford University.
`
`

`

`Case 6:20-cv-00272-ADA Document 65-4 Filed 03/14/22 Page 6 of 6
`
`Network Management Complexities: From Afterthought to Key Topic 23
`
`Application Characteristics
`Typically, management systems have to support many different functions. As it turns out, many of
`those functions really need to be supported through their mvn (sub )applications. Many of these
`applications have characteristics with certain architectural implications.
`
`We discuss management applications and tools in greater detail in the next chapter. However, let
`us preview some typical and important types of network management applications to illustrate the
`wide range of application characteristics that are involved. Each of them is associated with its own
`set of challenges. In addition, many of these applications impose different requirements on the
`supporting management systems, which, from a software engineering point of view, sometimes
`can be difficult to reconcile. In particular, this concerns characteristics that management
`applications share with transaction-based systems, interrupt-driven systems, and number(cid:173)
`crunching applications.
`
`Transaction-Based System Characteristics
`Provisioning applications are concerned with driving desired configurations down to network
`devices; for example, to turn up a service for a customer in the network. Using network
`management parlance, we also refer to network devices as network elements, as depicted in Figure
`1-8. To perform provisioning, a management system typically sends a request, or a number of
`requests, to a network element, or a set of network elements, and processes the responses returned
`from the network to make sure everything is in order. These interactions with the network devices
`constitute transactions that are conducted with the network.
`
`Figure 1-8 Network and Network Elements
`
`Network
`Elements
`
`Network
`
`This means that a provisioning application shares many characteristics with transaction-based
`systems in other areas, such as banking. As with a transaction-based system in those other areas,
`a provisioning application must be good at dispatching requests, processing responses, managing
`
`