Network Upgrade: Global Manufacturing Corp

1
Network Upgrade Global Manufacturing Corp

• Team Alpha

2
Problem Description

• The project is the replacement of dated and
  struggling but reliable technology (x.25) with a
  contemporary implementation (ATM or MPLS) with
  provisions for the accomplishment of centralized
  integrated network management as soon as
  possible.

3
Requirements

• Investigate feasibility of replacing x.25 network
• Investigate Enterprise Management Center
  construction
• Provide analytical support of a trade between ATM
  and MPLS
• Consider Turnkey Solution
• Plan for Integrated Network Management capability

4
Requirements (Cont)

• Current Environment
• Six major nodes connected by leased lines
  (intra-company WAN at up to 64kbps)
• Each node connects LANs with 26,000 workstations
  smaller number of file, print, and database
  servers.
• Existing x.25 links are struggling with the
  introduction of high speed data requirements,
  Unified Communications advances and VoIP.

5
Requirements

• CIO Concerns
• Centralized Network Management must be available
  100 (backup mgmt node)
• Redundant links considered to headquarters in San
  Francisco vs. having another node serve as backup
  network management center
• While redundant links operating (MPLS and x.25)
  how can monitor and control be done for both
  types of traffic?

6
Requirements (CIO Concerns)

• 1500 trouble calls daily with no traceability
• No early indication of problem in formation
• Node C reliability only 85
• Integrated Network Mgmt Solution may solve
  problems
• Candidate - Unicenter Network System Mgmt(NSM)
• Solution may add traffic to network
• No increase in delay more than 3 due to
• Removal of x.25
• Addition of NMC function
• Volume and flow of NM info during recovery of a
  link or node does not cause a ripple or
  saturation effect on the other links in the
  network.

7
Approach

• Analyze Existing (X.25) WAN
• Analyze Emerging Network Requirements
• Provide Upgrade Alternatives As Required
• Analyze Suitability Of Alternatives To Current
  and Emerging Needs
• Analyze LAN and Relationship (Current and
  Emerging) To WAN
• Recommend LAN Alternatives If Necessary
• Provide Recommendation For Network Monitoring
  System / Center
• Analyze Security Requirements and Solutions
• Provide Reasonable Upgrade Plan

8
Traffic Analysis

• Existing Information Regarding Network Traffic Is
  Minimal
• Bandwidth Link Averages (Mean)
• Utilize Stochastic Models Of Network Traffic
  Demands for Network Analysis
• Gaussian Distribution Model
• Most Network Traffic Models Converge To A
  Gaussian Model
• The Discrete Gaussian Distribution Model Offers
  An Excellent Description Of Network Traffic Over
  Time and Bandwidth Allocations
• More Complex, and Accurate, Models Are Possible
• Require More Detailed Empirical Sampling Of
  Existing Network Traffic

IEEE Communications Magazine, August 1998
Broadband Traffic Modeling Simple Solutions to
Hard Problems Ronald G. Addie, University of
Southern Queensland Moshe Zukerman and Timothy
D. Neame, University of Melbourne
9
Existing Network Analysis
10
Link Load Means (kb/s)

• AB 19(AB) 14(ABC) 10(ABFD) 43kb/s
  of 56kb/s 77
• AE 17(AE) 4(AEF)
  22kb/s of 56kb/s 39
• BA 19(BA) 4(CBA) 10(DFBA)
  43kb/s of 56kb/s 77
• BC 18(BC) 14(ABC) 32kb/s of
  56kb/s 57
• BF 4(BF) 2(BFE) 3 (BFD) 10(ABFD)
  9kb/s of 56kb/s 16
• CB 4(CBA) 8(CB)
  12kb/s of 56kb/s 21
• CD 13(CD) 13(ECD) 26kb/s of
  56kb/s 46
• CE 13(CE) 20 (CEF) 3(DCE) 36kb/s
  of 56kb/s 64
• DC 3(DC) 3(DCE) 6kb/s of
  56kb/s 11
• DF 4(DF) 3(DFB) 10(DFBA)
  17kb/s of 56kb/s 30
• EA 7(EA) 14(FEA) 21kb/s of
  56kb/s 37
• EC 20(FEC) 3(EC) 13(ECD) 36kb/s
  of 56kb/s 64
• EF 20(CEF) 4(AEF) 5(EF) 20(EFB) 49kb/s
  of 64kb/s 76
• FB 14(FB) 20(EFB) 10(DFBA) 3(DFB) 47kb/s
  of 56kb/s 84
• FD 4(FD) 10(ABFD) 3(BFD) 17kb/s
  of 56kb/s 30
• FE 5(FE) 14(FEA) 20(FEC) 2(BFE) 41kb/s
  of 56kb/s 73

11
Traffic Model

• Graph Depicts Gaussian PDF of Traffic Presented
  to One Link
• Assumes Data Presented To Network Is
  (Stochastically) Time Invariant
• Saturation Is Defined As The Percentage Of Time
  That Traffic Presented To Link, Exceeds Link
  Capacity.

12
Link Analysis Summary
See Appendix A for complete link analysis
13
New IP Traffic Data Requirements

• Internet
• The mean internet page size remains at 60.48KB
  and has since the mid 1990s
• Nominal Assumed Rate Is Based On 25 Web Page
  Visits Per Workstation Per Day
• For 26,000 Workstation Node Over an 8 Hour Day
  10.92Mb/sec

http//www.pantos.org/atw/35654-a.html
14
New IP Traffic Data Requirements

• VOIP
• A G.723.1 5.6kbps compressed audio path will
  require 18kbps of bandwidth based on standard
  sampling rates.
• The difference between the 5.6kbps and 18kbps is
  packet headers.
• Silence suppression and header compression can
  typically save 35 on bandwidth used.
• VoIP off shoots such as TDMoIP take advantage of
  the concept of bundling conversations that are
  heading to the same destination and wrapping them
  up inside the same packets. These can offer near
  toll quality audio in a 6-7kbps data stream.
• For analysis, a 7kb/s data rate is assumed, with
  15, 3-minute calls per employee per day
• For 26,000 Employee / Node 11.4Mb/Sec

15
New IP Traffic Data Requirements

• Online Collaboration Software
• Net Meeting, RainDance, WebAsyst, WorkZone
• Primary bandwidth utilization is dependent on
  media file type (Video CAD, MSWord etc.)
• Assume typical usage based on Medium Quality
  Video (130kb/s, Netmeeting)
• Assuming a 1 Workstation Utilization 33.8Mb/s
  For 26,000 Workstation Node

http//www.microsoft.com/windows/NetMeeting/Corp/r
eskit/Chapter7/
16
Predicted Network Utilization

• Per Node Assuming 26,000 Workstations and 25
  Growth.

17
Predicted Growth Of Bandwidth Requirements Per
Node
18
Upgrade Alternatives

• MPLS
• ATM
• L2TP

19
What Is MPLS?

• Multiprotocol Label Switching (MPLS)
• Emulates some properties of a circuit-switched
  network over a packet-switched network.
• Operates between Layer 2 (data link layer) and
  Layer 3 (network layer)
• Referred to as a "Layer 2.5" protocol.

20
What Is MPLS?

• Designed to provide a unified data-carrying
  service for both circuit-based clients and
  packet-switching clients
• Can be used to carry many different kinds of
  traffic, including
• IP packets,
• ATM
• SONET
• Ethernet frames.

21
MPLS ATM / Frame Relay

• A number of different technologies were
  previously deployed with essentially identical
  goals, such as frame relay and ATM. MPLS is now
  replacing these technologies in the marketplace,
  mostly because it is better aligned with current
  and future technology and needs.

22
MPLS ATM / Frame Relay

• MPLS dispenses with the cell-switching and
  signaling-protocol baggage of ATM.
• MPLS recognizes that small ATM cells are not
  needed in the core of modern networks, since
  modern optical networks (as of 2001) are so fast
  (at 10 Gbit/s and well beyond) that even
  full-length 1500 byte packets do not incur
  significant real-time queuing delays (the need to
  reduce such delays, to support voice traffic,
  having been the motivation for the cell nature of
  ATM).

23
MPLS ATM / Frame Relay

• Attempts to preserve the traffic engineering and
  out-of-band control that made frame relay and ATM
  attractive for deploying large scale networks.
• Originally proposed by a group of engineers from
  Cisco Systems, Inc. it was called "Tag
  Switching" when it was a Cisco proprietary
  proposal, and was renamed "Label Switching" when
  it was handed over to the IETF for open
  standardization.

24
MPLS ATM / Frame Relay

• One original motivation was to allow the creation
  of simple high-speed switches, since it was at
  one point thought to be impossible to forward IP
  packets entirely in hardware. However, advances
  in VLSI have made such devices possible. The
  systemic advantages of MPLS, such as the ability
  to support multiple service models, do traffic
  management, etc, remain.

25
MPLS ATM (continued)

• MPLS can not be compared directly to ATM as they
  are totally different technologies with different
  goals.
• MPLS allows a very smooth migration for IP only
  services on ATM networks, without the need to
  support of complex signalling and routing
  protocols like PNNI.
• A large proportion of the data transported over
  ATM networks in the late 1990s was IP
• Cheaper to upgrade some switches to support MPLS
  instead of PNNI.

26
MPLS ATM (continued)

• MPLS packets can be much larger than ATM cells
  (with the difference that they have variable
  length, ATM cells have fixed size of 53 bytes).
• Today's networks usually must be able to
  transport packets at least 1500 bytes long
  (because this is the ubiquitous maximum size for
  Ethernet)
• Any MPLS payload size (being the size of the
  encapsulated payload plus the size required for
  all the labels) that the network interfaces in
  use will allow, can be transported.
• Requires the use of "baby jumbo packets" if
  Ethernet is used as the transport for MPLS).
• Compares well with the 48-byte cell of ATM, and
  reduces encapsulation overheads, particularly in
  the case of small packets for example, it allows
  a minimum-length TCP packet to reside in a single
  MPLS packet, rather than two cells as in ATM.

27
MPLS ATM (continued)

• The 16 bits of VCI and 8 bits of VPI in the ATM
  cell are replaced by a single label field of 20
  bits, packed into a 32 bit label header.
• The 32 bit MPLS label field also contains an 8
  bit time-to-live field, a "top of stack" bit, and
  three spare bits for expansion.
• Although fewer bits are available for the label,
  labels can be stacked to create arbitrarily
  complex MPLS label stacks.
• This makes addressing and trunking in MPLS vastly
  more flexible than in ATM, as there is no need to
  impose an arbitrary boundary between VP and VC
  switching.

28
L2TP

• Layer 2 Tunneling Protocol Version 3 is a draft
  version of L2TP that is proposed as an
  alternative protocol to MPLS for encapsulation of
  multiprotocol Layer 2 communications traffic over
  IP networks. Like L2TP, L2TPv3 provides a
  pseudo-wire service, but scaled to fit carrier
  requirements.
• L2TPv3 can be regarded as being to IP what MPLS
  is to ATM a simplified version of the same
  concept, with much of the goodness achieved with
  a fraction of the effort, at the cost of losing
  some technical features considered less important
  in the market. In the case of L2TPv3, the
  features lost are traffic engineering features
  considered important in MPLS. The protocol
  overhead of L2TPv3 is also significantly bigger
  than MPLS. However, there is no reason why these
  features could not be re-engineered in or on top
  of L2TPv3 in later products.

29
Considered Solutions

• Connectivity
• VPN Over Internet
• Leased Line WAN Using Optical Networks At 1Gb/s
• ATM
• Theoretically Lower Latency for Real Time Traffic
  (Voice, Video Conferencing)
• Scalable
• Merges with ATM-25 Concept (Being Considered For
  LAN)

30
WAN Option 1

• VPN over the internet to individual sites
• Advantages
• Most Robust In Terms Of Node Failure
• Disadvantages
• Each Site Must Maintain Own Internet
  Accessibility
• Firewall
• External Tunneling Access (User Access for entire
  enterprise)
• Must Tunnel In To Individual Sites To Access
  Equipment on those sites.
• Completely reliant on service providers network
  (manageable through SLA)

31
WAN Option 1
32
WAN Option 2

• Leased Lines to individual sites
• Internet Access Via NOC (San Francisco) and
  Backup NOC (Dallas)
• Advantages
• Single point of entry (egress) to/from the
  internet
• Single database of user access for tunnel-in
  capability
• Single firewall
• Single point to tunnel in for employees on
  travel, etc. for entire network access
• Single point to upgrade for IPv6 migration, and
  other upgrades
• Leased line bandwidth is 100 devoted to
  corporate needs
• Disadvantages
• Compromising single point of entry compromises
  entire network
• Single point of failure for internet access

33
WAN Option 2
34
Proposed Solution

• Leased Line IP WAN Over 1Gb/Sec
• Optical Links
• Minimum 100Mb/Sec To Carry Needs Through To Next
  Tech Refresh
• Recommend 1Gb/Sec To Carry Needs Through Next 10
  Years
• MPLS
• Initially Implement X.25 Over IP Tunneling
• Lower Risk During Hand Over
• Quicker Implementation Of IP Network Without
  Perturbing Existing Network Requirements.
• COTS Hardware
• Upgrade LAN To Better Handle New Traffic
  Requirements
• Add Internet Connectivity
• Include Internet Access Redundancy
• Include Web Site Capability
• Add Security At Internet And Remote Dial-Up
  Access Points
• Migrate Legacy Servers Off X.25 To IP
• Allows For Scalability
• Add Network Management System
• Include High Availability Failover Capability

35
MPLS

• Allow Us To Carry Multiple Traffic Types
• Particularly IP Packets, ATM, SONET, and Ethernet
  frames
• Easier Addressing and Trunking To Support
  Upgrades Sub Node Additions
• More Mature Than L2TPv3
• Cheaper Support Hardware (Switches) Than ATM
• Avoids Complex Signaling and Routing Protocols
  Like PNNI

36
X.25 Tunneling Over IP Implementation

• Commercial Hardware Solutions
• Encore Bandit
• Anchor X.O.T. Gateway
• Genuity (L-Com)
• Others
• Seamless Switchover From The Current Low
  Bandwidth Data Links, to the New Fast IP Data
  Links
• Without Interrupting Access To Legacy Servers
• Implement Server Crossover To IP As Convienent

37
Local Area Network Bandwidth Requirements
38
LAN Latency and Efficiency
39
LAN Case Study
Source http//www.networking.ibm.com/nhd/webnav.n
sf/pages/atmatm25fe.html
40
LAN Case Study 2
41
LAN Case Study 2 contd.

• Ethernet could not span the wide area components
  of Chrysler's network as well or as seamlessly as
  ATM.
• When they evaluated cost, desktop ATM compared
  favorably with Fast Ethernet.

Source Chrysler Corporation, Engineering
Department.
42
LAN Hardware
43
Internet Access and Security

• Provide Corporate Internet Access At Two Nodes
• Minimizes Potential Points Of Intrusion
• Provides Redundancy
• Minimizes Points Requiring Security Hardware /
  Software Upgrades
• Choose Network Operations Center (San Francisco)
  and Backup (Dallas)
• Include Bastion (DMZ) To Secure Web Server WAN
  Access and LAN
• Provide Secure Remote (Dial Up) Access Through
  Bastion Server To Secure LAN / WAN
• Contivity (Nortel)
• VPN Appliance with RSA One Time Password
  Generators

44
NOC Topology
Legacy Mainframes
Web Server
WAN
Internet
X.25 To IP
LAN
Dial In Access
Bastion
NMS
45
Network Management Systems Considered

• Spirent
• CenterOp Suite
• Computer Associates
• Network Monitoring And Traffic Reporting.
• Opnet
• IT Guru
• Rendition Networks
• TrueControl 3.0

46
CenterOp

• Spirent Communications CenterOp
• Perform Performance Monitoring
• Test Throughput Testing and Network Modeling
• Gateway Tunnel Capability Through VPN
• Ticket Trouble Ticketing and Asset
• Management
• SNMP, CMISE, and Other Legacy Protocols
• Auto Discovery of Hardware
• Security / Password Management
• IBM High Availability Failover

47
Network Monitoring And Traffic Reporting

• Computer Associates Network Monitoring And
  Traffic Reporting.
• Polling interval configurable
• Automated failover database duplication
• Gateway capability for Cross-VPN Monitoring

48
IT Guru 11 - OpNet

• Network Modeling and Management Tool supports
  predictive planning of networks
• Allows designers to test changes to network
  topology before implementing on a production
  network
• Scales well to production networks
• Models link failures, changes, device failures
  load changes, route changes and link overloading.
• Models OSPF link costs and timer mods
• Supports third party integrations
• Enables capacity planning for distributed systems
  and mainframe environments
• Claims accepts workload inputs from BMC Software,
  Concord Communications, HP, IBM, NetIQ, and XML.

49
TrueControl(Opsware)-Rendition

• Provides network topology search, auditing and
  reporting.
• Devices, modules, configurations, tasks,
  sessions, and events are all checkable against
  limit criteria.
• Allows changes to both startup and running device
  configurations.
• Supports grouping of equipment for ease of
  management and monitoring

50
TrueControl(Opsware)-Rendition-2

• Deploys user and SNMP passwords
• Real time change detection vs polling
• Supports scripting of configuration changes
• Provides SecurID and TACACS two-factor
  authentication
• Compliance Center Sarbanes-Oxley and best IT
  practices
• Adding workflow and approvals procedures in Ver.
  4.0
• Singleview and Singlesearch for centralized
  configuration

51
Schedule

• Review high-level schedule milestones here

FOR MORE INFO...
List location or contact for detailed schedule
(or other related documents) here
52
Appendix (A) Link Analysis
53
Link AB Analysis
54
Link AE Analysis
55
Link BA Analysis
56
Link BC Analysis
57
Link BF Analysis
58
Link CB Analysis
59
Link CD Analysis
60
Link CE Analysis
61
Link DC Analysis
62
Link DF Analysis
63
Link EA Analysis
64
Link EC Analysis
65
Link EF Analysis
66
Link FB Analysis
67
Link FD Analysis
68
Link FE Analysis
69
Appendix (B) 12 Requirements for NW Mgmt
70
12 Requirements for NW Mgmt

• Today's diverse networking technologies and the
  clients that use them mean there are possibly
  thousands of factors that have to be considered
  in the selection of any technology or solution.
• However, enterprises of all types and sizes find
  that the best solutions share at least 12
  essential qualities

Computer Associates Literature Extract
71
12 Requirements for NW Mgmt

• 1. Business Focus
• 2. Application Service Delivery Context
• 3. Integral Availability, Access Performance
  Management
• 4. End-to-end Management Capability
• 5. Scalability Resource Efficiency
• 6. Cost Effectiveness
• 7. Ease-of-use Interface Consistency
• 8. Standards Support
• 9. Legacy Support
• 10. Protocol Independence Vendor Neutrality
• 11. Integration
• 12. Flexibility

72
1. Business Focus

• Lifeline of the business
• Serve needs of business, not require it to adapt
  to the network limitations
• Be proactive, not just reactive to network
  difficulties, based on policies.
• Quickly show what areas of business are
  potentially affected

73
2. Application and Service Delivery Context

• Provide the type of services required of the
  business (e.g. high rate - low latency, low rate
  high integrity)
• Provide meaningful metrics meeting
  requirements?
• Provide tools that simulate real loads not just
  verify connectivity

74
3. Integral Availablility, Access and Performance
Management

• Alive and online no longer sufficient
• Meeting the needs without timing out
• Measurement of availability, device status,
  loading, and topology are required knowledge for
  proactive management.

75
4. End-to-end Management

• Virtual seamless operations required
• Entire extent of the network must be available to
  all users
• Observation of all steps end-to-end required to
  maintain usability

76
5. Scalability and Resource Efficiency

• 250 node group limitations no longer acceptable
• Beware of flat files and databases which arent
  scalable or become unmanageable as networks grow.
• A scalable, n-tier, object oriented database will
  prevent the solution from overwhelming the
  network its intended to support.

77
6. Cost Effectiveness

• Conflicting requirements
• Guarantee uptime reduce staff
• Ensure high performance reduce hardware
  additions
• A cost effective solution must provide high
  leverage to limited staffing, minimize staff
  training requirements and installation/setup
  loads.

78
7. Ease of Use / Interface Consistent

• Single face for all features of an integrated
  network management solution.
• Intuitive and easy to use GUIs
• Beware of patched together solutions from
  acquired providers (e.g. different and sometimes
  contradictory user interfaces)

79
8. Standards Support

• Current and emerging standards built into or
  planned into the tools architecture.
• In addition to SNMP, supports
• DHCP and DNS, DMI and CIM

80
9. Legacy Support

• In addition to commonly found Unix and NT
  servers.
• Accounting Mainframe processes
• Etc.

81
10. Protocol Independence Vendor Neutrality

• In addition to TCP/IP.
• Supports SNA and DECnet IPX/SPX, Frame Relay, and
  ATM
• Runs on various hardware and OSs WinNT, Unix,
  AS/400, NetWare as well as mainframe
  environments.

82
11. Integration

• Supports integration of third party solution when
  one is required
• Launches third party tools from within its own
  network maps
• Provides for information exchange

83
12. Flexibility

• Adaptable to enterprise requirements
• Regional
• By Business Unit
• By Platform
• Adaptable to sudden configuration changes
• Acquisition of another business
• Surges in network utilization e.g. streaming
  video
• Discovery of newly added resources

84
Obsolete Slides
85
Project Goals

• Ultimate goal of project
• Analyze x.25 removal feasibility
• Investigate Enterprise Mgmt Center Construction
• Relationship to other projects
• Turnkey Solution desired
• Integrated Network Mgmt desired
• High-level timing goals- ASAP

86
Propose a Solution

• Build credibility with CIO by
• analyzing existing and proposed network
  performance
• laying out a plan to move to MPLS
• Provide analyses to demonstrate what you consider
  best approach
• Compare and contrast analyses in 2 with those of
  1.

87
Current Data Requirements
88
ATM Option

• Theoretically Lower Latency for Real Time Traffic
  (Voice, Video Conferencing)
• Scalable
• Merges with ATM-25 Concept

89
LAN Options

• Replace With Fast Ethernet
• Fast Token Ring
• ATM-25

90
Remote Access

• Dial In
• Contivity (Nortel)
• VPN Appliance with RSA One Time Password
  Generators
• Bastion Server - DMZ

91
Project - Network Management

• Network Upgrade
• Global Manufacturing Corp
• Team Alpha

92
Offered Traffic to x.25 (kb/s) from attached LANs
and current x.25 routing (Given )
93
Trades Analysis

• Alternatives
• The two alternatives are the well understood (by
  the CIO) ATM approach or a latest thinking MPLS
  approach that is well thought of by the technical
  community.
• Strengths
• Weaknesses

94
Technology

• New technology being used
• Benefits
• Standards being adopted
• Benefits
• Standards specifically being ignored
• Drawbacks benefits
• DYA define your acronyms!

95
Team/Resources

• State assumptions about resources allocated to
  this project
• People
• Equipment
• Locations
• Support outside services
• Manufacturing
• Sales

96
Procedures

• Highlight any procedural differences from regular
  projects of this type
• Discuss requirements, benefits, and issues of
  using new procedures

FOR MORE INFO...
List location or contact for procedures document
(or other related documents) here
97
Trades Study from Network World

• Network Modeling and Management Tools Considered
• Opnets IT Guru best1
• Rendition Networks TrueControl 3.0 best2
• AlterPoints DeviceAuthority Suite
• Dorado Softwares RedCell
• Peribit Networks SR-100
• Shunra Softwares Shunra/Storm Ver.3.1
• Sourcefires Real-time Network Awareness Sensor
  2000
• Tripwires Tripwire for Network Devices
• Voyences VoyenceControl
• Developed from Network World 2/28/05 by Chris
  Burns Ken Shaw update

98
DeviceAuthority Suite - AlterPoint

• DeviceAuthority Server
• User credential management
• Device version control backup
• Scheduling
• Autodiscovery
• Identifies and backs up Cisco hardware

99
Other Notables

• RedCell Dorado Software
• Integrated Suite of Products
• Network Discovery and Configuration Management
• Easy start/stop
• Full of features
• SR-100 Peribit Networks
• WAN link compression appliance

100
Shunra/Storm Ver.3.1 Shunra SW

• Network Modeling
• Real time simulator
• Models WAN links
• Uses MS Visio for user interface
• Models bandwidth throttling, link limitations,
  packet delays and jitter.

101
Real-time Network Awareness Sensor 2000 -
Sourcefire

• Visibility into all events on the network
• Combines passive network analysis with Web-based
  management system
• Provides IT extensive network activity monitoring
• Provides application ID, (e.g. mail servers on
  non-standard ports), without affecting hosts or
  network

102
Tripwire for Network Devices - Tripwire

• File integrity assurance product extended to
  network devices
• Built-in log viewer for error isolation
• Direct hooks to major network management
  frameworks CA Unicenter, HP Openview, and IBM
  Tivoli
• Claims support for 100,000 devices

103
VoyenceControl - Voyence

• Network configuration product
• Sends customer proof-of-concept document before
  shipping installing product
• Voyence then will provide hardware preconfigured
  or install on customer provided hardware
• Easy GUI discovery and management
• Easy data view from devices
• Integrated with Mapquest for real topology

104
Current Status

• High-level overview of progress against schedule
• On-track in what areas
• Behind in what areas
• Ahead in what areas
• Unexpected delays or issues

105
Related Documents

• Marketing plan
• Location or contact name/phone
• Budget
• Location or contact name/phone
• Post mortem
• Location or contact name/phone
• Submit questions
• Location or contact name/phone