Getting Started: Network Configuration

461 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
461
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Slide Highlights: Spell out details of the three components of the Visual UpTime System: ASE, PAM, PAC Visual UpTime system is a client/server architecture Emphasis on Complete TURN-KEY SYSTEM from a SINGLE VENDOR! Slide Script: There are 3 components to the Visual UpTime system. The intelligent management agent deployed throughout your network is called the Analysis Service Element or “ASE”. The ASEs gather over 60 statistics on every frame going in and out of each site in the network. The data is stored in the ASE for up to 48 hours and is download typically once per day to the Performance Archive Manager or “PAM”. The PAM is the central application/database of the system. 2 dbases - ST/LT 53 week default for reporting. Auto DB maint/sync Partitioning It is a turn key solution running Windows 2003 Standard Server and MS SQL 2000 database. Communication between the ASEs and the PAM is via standard SNMP and TFTP. The UpTime system is a client server architecture, with the Select Server being the server. The client is the Platform Applicable Client or “PAC”, or a Web interface. The PAC (platform applicable client) is software client loaded onto an existing workstation that allows the workstation to become the presentation device for the system. Communication between the PAM and PAC is via standard RPC. The PAC is provided in windows versions to support a wide variety of workstation environments.
  • Here is the deployment model diagram showing our ASE/DSUs at each location, bringing data back to the centrally located server. In the enterprise, the server is located in an enterprise NOC or data center. Among service providers, the provider hosts the server and owns the data, and provides views to the customer as part of a monthly service fee. Cisco WAPMS can be deployed in tandem with the UpTime Select system – in a mixed WAPMS and ASE environment.
  • ASEs collect and store second-by-second application and network performance data in memory in 15-minute increments for two days, with new data overwriting the oldest so that the most recent data is always available. This historical data is downloaded to a Visual UpTime Select server when it initiates ASE data collection. ASEs also communicate current and real-time network performance data through the server to be available for display by client applications. The short-term database on the Visual UpTime Select server stores 14 days of application and network performance data in 15-minute increments. This data is downloaded from the ASE each time ASE data collection occurs (daily by default at 1:00 a.m.). Each time database maintenance occurs (daily by default at 2:00 a.m.), data is copied from the short-term database to the long-term database and any data more than 14 days old is purged from the short-term database. The short-term database also stores network configuration and statistical event data for performance monitoring (entered from a PAC), and access control settings (entered from the server). This information remains in the short-term database and is updated when new information is entered through the PAC or server user interfaces. The long-term database on the server stores up to n weeks (52 by default) of network performance data in 1-hour increments for use with the Planning and Reporting toolset. The long-term database capacity is determined for the server at the time of purchase. ASE data collection and database maintenance, which trigger this data transfer, can be scheduled and performed on demand from the PAC. You can also modify the number of weeks of data stored in the long-term database from the PAC. ASEs collect and store second-by-second application and network performance data in memory in 15-minute increments for two days, with new data overwriting the oldest so that the most recent data is always available. This historical data is downloaded to a Visual UpTime Select server when it initiates ASE data collection. ASEs also communicate current and real-time network performance data through the server to be available for display by client applications. The short-term database on the Visual UpTime Select server stores 14 days of application and network performance data in 15-minute increments. This data is downloaded from the ASE each time ASE data collection occurs (daily by default at 1:00 a.m.). Each time database maintenance occurs (daily by default at 2:00 a.m.), data is copied from the short-term database to the long-term database and any data more than 14 days old is purged from the short-term database. The short-term database also stores network configuration and statistical event data for performance monitoring (entered from a PAC), and access control settings (entered from the server). This information remains in the short-term database and is updated when new information is entered through the PAC or server user interfaces. The long-term database on the server stores up to n weeks (52 by default) of network performance data in 1-hour increments for use with the Planning and Reporting toolset. The long-term database capacity is determined for the server at the time of purchase. ASE data collection and database maintenance, which trigger this data transfer, can be scheduled and performed on demand from the PAC. You can also modify the number of weeks of data stored in the long-term database from the PAC.
  • Getting Started: Network Configuration

    1. 1. Visual Select Webinar Training Session 6: Network Configuration Kirk O’Connor [email_address] 301 296 2300
    2. 2. Introduction <ul><li>Welcome! </li></ul>Kirk O’Connor 301 296 2744 [email_address] Office Headquarters: Visual Networks, Inc. 2092 Gaither Road Rockville, MD 20901 www.visualnetworks.com <ul><ul><li>For troubleshooting or questions related to this training, please contact: [email_address] . </li></ul></ul><ul><ul><li>For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative. </li></ul></ul>
    3. 3. Agenda <ul><li>Housekeeping </li></ul><ul><li>System Overview </li></ul><ul><li>Network Configuration </li></ul><ul><li>System Demonstration </li></ul>
    4. 4. Housekeeping <ul><li>Training webinars are one hour or less. </li></ul><ul><ul><li>System Overview </li></ul></ul><ul><ul><li>Getting Started </li></ul></ul><ul><ul><li>Application Troubleshooting </li></ul></ul><ul><ul><li>Network Troubleshooting </li></ul></ul><ul><ul><li>Traffic Capture </li></ul></ul><ul><ul><li>Network Configuration </li></ul></ul><ul><ul><li>Planning and Reporting </li></ul></ul><ul><ul><li>ASE Installation </li></ul></ul><ul><ul><li>Network Configuration </li></ul></ul><ul><ul><li>Managing the ASEs </li></ul></ul><ul><ul><li>Total Time: 10 hours </li></ul></ul><ul><ul><li>For troubleshooting or questions related to this training, please contact: [email_address] . </li></ul></ul><ul><ul><li>For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative. </li></ul></ul>
    5. 5. Training Webinar Courses <ul><li>System Overview : A demonstration of all the Tools. </li></ul><ul><li>Getting Started: Logging in, Service Summary, Events, Performance Monitoring. (1 hour) </li></ul><ul><li>Application Troubleshooting: Using the Application Integrity toolset including Application Summary and Application Flows. (1 hour) </li></ul><ul><li>Network Troubleshooting: Using the Troubleshooting Toolset on the Physical and Port views of the Local Loop and end-to-end SLAs on the Circuit. (1 hour) </li></ul><ul><li>Traffic Capture: Using the Traffic Capture Toolset for advanced level troubleshooting. (1 hour) </li></ul>
    6. 6. Training Webinar Courses <ul><li>Network Configuration: Adding Networks, Sites, ASEs and Circuits to be monitored by the Server. (1 hour) </li></ul><ul><li>Planning and Reporting : Creating and analyzing Executive Reports and Site-Specific Reports for trending and problem analysis. (1 hour) </li></ul><ul><li>ASE Installation: Installing the ASE and commands. (1 hour) </li></ul><ul><li>Network Configuration: Adding, Networks, Sites, ASEs and Circuits to be monitored by the Server. (1 hour) </li></ul><ul><li>Managing the ASEs : Getting the data home. (1 hour) </li></ul>
    7. 7. Course Objectives <ul><ul><li>Network Configuration: Logging in, Service Summary, Events, Performance Monitoring. </li></ul></ul><ul><ul><li>By the end of the session, participants will be able to: </li></ul></ul><ul><ul><li>Log into the Platform Applicable Client. </li></ul></ul><ul><ul><li>Navigate to a Customer. </li></ul></ul><ul><ul><li>Use Network Configuration to Move, Add, Change, Delete a Network, Site, Access Line, and/or Circuit. </li></ul></ul><ul><ul><li>Add Applications to be monitored. </li></ul></ul><ul><ul><li>Add the Committed Access Rate (CAR) value. </li></ul></ul><ul><ul><li>Add a Local Subnet for mapping to a Remote Subnet to create an IP Circuit. </li></ul></ul><ul><ul><li>Total Time: 1 hour </li></ul></ul>
    8. 8. Visual UpTime Select – 2005 - 2006 Visual UpTime Select Server Probe ASE/DSU Ethernet Instrumentation Third-Party Integration Interfaces Software Modules Service Summary Core System Software Select AppSummary Select AppFlows Select Traffic Capture Select Class-of-Service Select Network Troubleshooting Select Back-in-Time Select VoIP MRI Select Citrix Intelligence Select Enhanced VoIP Select LAN/WLAN SELECT SELECT Select Remote Control Select Router Polling
    9. 9. The Visual System SQL SQL SQL SNMP/TFTP Servers come in two sizes Single Processor: 1,000 ASEs or 1-15 Domains or 5,000 objects* Dual Processor: 8,000 ASEs or 1-250 Domains or 28,000 objects * Objects are the total number of ASEs, partner devices, and defined VPI/VCI’s or IP circuits supported on the server. Events, Real Time and 48 hours worth of data in 1 second granularity 1 years’ worth of data via Planning and Reporting Toolset Traps, Real Time View, 2 weeks “back in time” data plus 1 year of Reports Data Collection: Analysis Service Element “ ASE” Data Interpretation: Performance Archive Manager Select Server Data Presentation: Platform Applicable Clients “ PAC” or Web Client
    10. 10. Deployment Model T1 T1 WIC 56k T1 DS3 Remote Locations Headquarters Data Center Management Data Customer Web-Based GUI Operations Center WAN PAC Tool for NOC Mgmt PVC for Nightly Data Collection Ethernet LAN based ASE * Images Best Practice: Probe at every location.
    11. 11. System Communication Service Providers use multiple servers that point to a single Web server. A back up server can be deployed as well.
    12. 12. Select Server RPC PAC initiated transfer of database information UDP Unacknowledged status notifications: new events, data collection progress NOTE: Arrows indicate direction of information transfer. SNMP SET Modify ASE configuration VIA the Select Server SNMP GET/GETNEXT PAC initiated retrieval of real-time stats and configuration VIA the Select Server TFTP PUT PAC initiated transfer of a new software image to the ASE VIA the Select Server SNMP TRAPS Unacknowledged exception reports. The only ASE initiated communications. TFTP GET PAM initiated bulk transfer of historical statistics SNMP GET/GETNEXT PAM initiated transfer of lost traps (events) Visual API TCP/IP based access to configuration, historical statistics, and events ASE PAC P&R API PAC initiated Report generation control and data Visual Communication Firewall ports will need to be configured correctly .
    13. 13. Data Movement One Second Granularity in 15 minutes buckets, or 900 seconds for a total of 192 buckets. Data really collected nightly (1x) each night because of the nightly collection. Removes unnecessary polling. 1 years’ worth of data <ul><ul><li>Data is organized as follows: Domain = Customer Network Network Site Access Line = Port = ASE Circuits PVC IP HDLC ATM </li></ul></ul>Application Summary Data (4 weeks of AppFlows)** **Application Alarms are generated nightly during the Daily Database Maintenance. SNMP Traps in Real Time or by hourly or On-Demand Or On-Demand Select Server
    14. 14. Service Summary Polling <ul><li>Service Summary data includes: </li></ul><ul><li>Updates of layer 2 up/down status on ASE-monitored ports polled from ASEs every 15 minutes and circuit up/down status polled every hour. </li></ul><ul><li>Port history (link up/down status) stored in 1-hour intervals for the most recent three days. </li></ul><ul><li>The five most recent port and circuit events uploaded by ASEs, updated every 15 minutes or when you refresh the Port and Circuit Details page in Service Summary. An ASE uploads recorded events as they occur to the Service Summary process in the Visual UpTime Select server and to the network performance database. To view all events for the previous two weeks, use the PAC Event Processor. </li></ul>On the Visual UpTime Select server, the Service Summary process polls ASEs for status data every 15 minutes (this setting can be changed in Server Administration on the server). A Service Summary middleware component in the server requests updates from the poller every 15 minutes and interfaces with the Web Server to make detected ASE status changes available to Web Clients. Server polls ASE every 15 minutes (default) for up/down status. Useful for HARD OUTAGES or cuts on the circuit. Web Client automatically refreshes, globally, every 300 seconds (default), or a manually with the REFRESH button. Select Server
    15. 15. Network Configuration Requirements <ul><li>User must have the Platform Applicable Client (PAC) loaded on their PC or access via Remote Terminal Services. </li></ul><ul><li>User must have connectivity from the PAC to the Select Server. </li></ul><ul><ul><li>Note : Firewall configuration for PAC <-> Server communication necessary. </li></ul></ul><ul><li>User must have Network Configuration user access on the Domain, i.e. Customer. </li></ul><ul><li>The ASE probe must be installed at the customer’s premise. </li></ul><ul><li>The Select Server must have connectivity to the ASE probe. </li></ul><ul><ul><li>Note : Firewall configuration for ASE <-> Server communication necessary. </li></ul></ul><ul><li>Proper licensing must be deployed on the Server (or the Domain) in order for the ASE probe to be added for monitoring. </li></ul><ul><li>DOMAIN: </li></ul><ul><li>A logical partitioning of all networks configured on a Visual UpTime Select server. A user can have access to more than one domain, and a domain can be accessed by multiple users. The Visual UpTime Select administrator configures which toolsets and functions a given user can access by domain. </li></ul>
    16. 16. Decisions to be made: * The only fun part <ul><li>The Customer Data is segmented by the following: </li></ul><ul><ul><li>SERVER: (the highest level, encompasses the server and all the Domains/Customers within the Server) </li></ul></ul><ul><ul><li>DOMAIN: This is typically the Customers’ Name. </li></ul></ul><ul><ul><ul><li>example: GlobalFinacials </li></ul></ul></ul><ul><ul><li>NETWORK: This can be a single Network or multiple Networks </li></ul></ul><ul><ul><ul><li>example: GlobalFinacials </li></ul></ul></ul><ul><ul><ul><ul><li>Or </li></ul></ul></ul></ul><ul><ul><ul><li>example: Asia Network, US Network, South America Network, Europe Network </li></ul></ul></ul><ul><ul><li>SITES: This can be the Physical Location of the ASE, or LEC Circuit ID. </li></ul></ul><ul><ul><ul><li>example: Rockville MD </li></ul></ul></ul><ul><ul><li>ACCESS LINES: This is also equal to PORT. The actual IP Address of the ASE is provisioned here. </li></ul></ul><ul><ul><li>CIRCUITS : Mapping of two ASEs to each other to create an IP Circuit, PVC, HDLC, or ATM circuit. </li></ul></ul>
    17. 17. Example and Notes <ul><li>Server : 192.168.236.46 </li></ul><ul><li>Domain: </li></ul><ul><li>GlobalFinancials </li></ul><ul><li>Network: </li></ul><ul><li>Global Financials </li></ul><ul><li>Site: </li></ul><ul><li>Rockville MD </li></ul><ul><li>Access Line: </li></ul><ul><li>RTR123CKTid </li></ul><ul><li>Circuit: </li></ul><ul><li>RockvilleMD<->EverettWA </li></ul><ul><li>NOTES : </li></ul><ul><li>User Access is controlled at the Domain Level, not the Network. </li></ul><ul><li>WAN Planning and Reporting has the option to generate Reports on ‘All Networks’, or specific Networks like ‘ASIA Network’ or ‘US Network’. </li></ul><ul><li>Sites can have more than one ASE, in the case of multiple Access Lines. </li></ul><ul><li>Access Lines is where the ASE IP address lives. </li></ul><ul><li>Circuits must be mapped correctly and MACD’ed if changed in reality on the network. </li></ul>
    18. 18. PAC: Log in <ul><li>1. Navigate to: START  Program  Visual Networks  Visual UpTime Select Client  PAC </li></ul>3 . Name* Server and input IP address : 4. Highlight Server and click CLOSE : 5 . Login with provided User name and Password : 2. Click ADD Successful  PAC attempts to contact server. *Any name will work. It is local to the Client. *Steps 1-4 will be skipped next time you log in.
    19. 19. To switch customers: 4 clicks <ul><li>*Once log in’ed it is very easy to change customers for a MACD within the Network Configuration toolset. </li></ul>A . Login  Setup  Domain Selection B. All Servers and Domains that the USER has access to is populated in the Domain Selection screen. 1 2 3. 4.
    20. 20. Network Configuration <ul><li>Click Network Configuration </li></ul><ul><li>Click Add Networks </li></ul><ul><li>Click Add Sites </li></ul><ul><li>Click Access Lines = Port = ASE: more work needed </li></ul><ul><li>Click Auto Add must be correct </li></ul><ul><li>Click Close </li></ul>1. 2. 3. 4. See next screen 5. See Creating IP Circuits 6. Best Practice: Print...to file and save the Domain Configuration for backup.
    21. 21. Add Access Line = Port = ASE <ul><li>Add the Access Line Name </li></ul><ul><li>Decide on Data Collection </li></ul><ul><li>Add the LAN IP or INBAND IP address of the ASE. </li></ul><ul><li>Click ASE Setup* </li></ul><ul><li>*This will cause the Select Server to contact the ASE to confirm communication and license for monitoring. </li></ul><ul><ul><li>*Best Practice: Fat fingering the IP address of the ASE will cause failure, as will, no IP route between ASE and Select Server, as will, the wrong SNMP Community string in the CLI of the ASE. </li></ul></ul><ul><li>* Best Practice: Collect Data more often than once a day for locations with known power outages or generators. </li></ul>1 . 3 . 2 . 4 . Best Practice#1: Set the Data Collection to the ASE Local Time based upon the Server Time. Best Practice#2: If ASE is not installed or down, make the ASE Active checkbox inactive (grey). * Always, Always do a Data Collection prior to rebooting or updating an ASE.
    22. 22. ASE Configuration <ul><li>IP...: Lots’ of Action Here </li></ul><ul><li>Frame Relay...: hmm, interesting </li></ul><ul><li>T1 Interface...: DO NOT MESS WITH. *This is the T1 command on the ASE. Not applicable on probes. </li></ul><ul><li>________________________________________________ </li></ul><ul><li>Software Version: </li></ul><ul><li>IP Transport ASE = MPLS IP VPN Networks </li></ul><ul><li>Multi-Protocol ASE = Traditional Frame, ATM, HDLC Networks </li></ul><ul><li>Same Hardware, different Firmware </li></ul>Buttons depends on the type of ASE T1 Interface The most dangerous button The ID command on the ASE * Do Data Collection first, requires a reboot. = Same as Serial # = Good info or Multi-Protocol Best Practice: Always confirm the latest Software Version during installation by checking Visual Customer Care (VTAC). or Multi-Protocol
    23. 23. T1 Interface The PAC ASE Setup T1 button allows for editing the CSU/DSU configurations. Best Practice: On circuit upgrades, change the CSU/DSU via command or PAC prior to upgrading the circuit. Communication will be lost with the ASE until the circuit is upgraded and the CSU/DSU becomes synchronized. The T1 Command on the ASE is used to configure the CSU/DSU. This information is provided by the local Telco and must match in order to work, otherwise truck roll. NOTE : Any T1 Command Line or PAC changes are instantaneous. Double check. =
    24. 24. Frame Relay <ul><li>Frame length > than 4096 can be viewed under PORT  STATISTICS </li></ul><ul><li>Enscapulation Protocols are for those tricky moments </li></ul><ul><li>Link Management is standard LMI between the CER and the PER. </li></ul>
    25. 25. IP...Applications <ul><li>Top 10 Applications will be rotated every 7 days unless LOCKED. </li></ul><ul><li>Use LOCK for your favorite protocols. </li></ul><ul><li>Auto Select should be used initially for every install. </li></ul>Very cool feature: Auto discovery and monitoring of the top 10 Protocols for the week.
    26. 26. IP...Subnets <ul><li>Subnet Guidance List is a “suggested discovered subnets” that the ASE automatically discovers. </li></ul><ul><li>If BGP is being used, the Local Subnet List will be automatically populated. </li></ul><ul><li>The subnets related to the Customers Routers Serial interface should be used. </li></ul>Customize your local subnets THE LOCAL SUBNET LIST MUST BE CORRECT IN ORDER TO MAP AN IP CIRCUIT AND GAIN PROPER COS SLA METRICS. These Local Subnets will be mapped to another Remote Local Subnet to create an IP CIRCUIT.
    27. 27. IP...Class of Service <ul><li>The CoS Configurations default configuration is set on the Select Server for each Domain. </li></ul><ul><li>Getting it right in the Select Server will get it right on every ASE. </li></ul><ul><li>Each field is configurable on the server. </li></ul><ul><li>Only Policing Threshold settings for each CoS is configurable here. </li></ul><ul><li>Reminder: All traffic is “tagged” in the ToS on the Customer Edge Router, the ASE is only “monitoring” the ToS field. </li></ul><ul><ul><li>If the Web Client shows “Unknown” then the CER is typically mis-configured because all traffic is tagged as “best effort.” </li></ul></ul>Up to 8 CoS settings can be configured. Jitter on CoS only available once.
    28. 28. IP...Committed Access Rate (CAR) <ul><li>CAR values are represented at the PORT  BURST tab. </li></ul><ul><li>In some ASEs, like the Ethernet ASE, the CAR value is also used in the PORT  Summary tab for PORT Utilization graphing and reporting. </li></ul><ul><li>This value is only used for calculations and reporting. </li></ul><ul><li>This values does NOT affect traffic. </li></ul><ul><li>Setting to ‘zero’ will default to ASE Port Speed. </li></ul>The GREAT DEBATE: In some cases, CAR = PORT speed, in other cases CAR = the value “guaranteed” by the Service Provider on the Local Loop. Also known as the “policed value” as related to the Port NOT CoS.
    29. 29. IP...IP Circuit Clean Up <ul><li>IP Circuit Clean Up: an easy way to delete non-functional, or mis-configured IP Subnet to IP Subnet mapping. </li></ul>
    30. 30. Creating IP Circuits <ul><li>AUTO ADD SHOULD NOT BE USED ON REMOTE SITES and only on LIMITED HUB SITES </li></ul><ul><li>This creates a fully meshed environment that may not be accurate with the routing statements. </li></ul><ul><li>BE VERY CAUTIOUS HERE. </li></ul>
    31. 31. IP Circuit Properties <ul><li>This screen is useful when BGP is running on the network. If you see red, check the square and close. Click “OK”, close, and re-open. </li></ul><ul><li>IF BGP is not running, much more consideration needs to takes place in creating an IP Circuit. </li></ul>Best Practice: Use the ADD button in the Circuit Network Configuration to make an educated IP Circuit; mapping proper subnet to subnets
    32. 32. PAC: Identify ASE IP Class of Service settings are configured on the Customer Domain by the Server Administrator. Identify ASE only available on the PAC. 1. Log into PAC and go to: File > Identify ASE 2 . 3 . 4 . **By getting it right in one place, the ASE’s will track COS and thresholds for all Sites.**
    33. 33. PAC: System Management <ul><li>Run Identify ASE… often, especially after upgrading an ASE, or the Select Server. </li></ul><ul><li>Run ASE Inventory… to better understand your connection status. </li></ul><ul><li>Run Collect Data Now… on individual sites, especially if Data Collection Poll Failure Event. </li></ul><ul><li>Search for DATA COLLECTION POLL FAILURES : Partial Data Collection in the Event Processor means mis-mapped circuits and are not good. Fix these ASAP in Network Configuration, or open a ticket. This effects SLA metrics. </li></ul>Log into PAC and go to File… * Best Practice:
    34. 34. Review: <ul><li>Use the PAC to run Identify ASE and Data Collection to quickly assess the monitoring of your Visual Select system. </li></ul><ul><li>Search for Data Collection Poll Failures and fix these immediately on the Circuit in Network Configuration or by opening a ticket. </li></ul><ul><li>Sort the Events by Site or Priority for quick site analysis. </li></ul><ul><li>Use the Acknowledge Displayed to remove Events from the Event Processor and keep the Events manageable. </li></ul><ul><li>Use the context sensitive HELP system. </li></ul>
    35. 35. Introduction <ul><li>Thank you! Any questions? </li></ul>Kirk O’Connor 301 296 2744 [email_address] Office Headquarters: Visual Networks, Inc. 2092 Gaither Road Rockville, MD 20901 www.visualnetworks.com <ul><ul><li>For troubleshooting or questions related to this training, please contact: [email_address] . </li></ul></ul><ul><ul><li>For troubleshooting or questions related to your Visual Select system, contact your Service Provider or Sales Representative. </li></ul></ul>

    ×