NETSCOUT Handheld Network Test. Enterprise Access Networks

Transcription

1 NETSCOUT Handheld Network Test for Enterprise Access Networks Christian Drost

2 How do you manage your access network? Wireless Access Point Computer Internet VOIP Phone Access Core Network Gateway Camera Cisco ISR with Integrated Agent Link Sprinter Link Runner AirCheck One Touch AirMagnet Mobile

3 Handheld Network Test Portfolio For Proactive Projects and Reactive Troubleshooting Wireless AirCheck Link-Live AirMagnet Mobile Wireline LinkSprinter LinkRunner OneTouch

4 LinkSprinter

5 Test Can I reach my critical cloud or internal service? Verify DNS lookup and application port connectivity Can I get to the edge of my premise? Verifying the router/gateway address and reachability. Is the DHCP server running and responsive? Request an IP address, or use your own static IP. Does this cable go anywhere? Quickly verify links including gigabit Ethernet connectivity. Can I use a phone, camera or AP here? LinkSprinter even runs without batteries on Power over Ethernet.

6 More skilled techs want details: LinkSprinter deliver them on your phone via the built in Wi-Fi access point

7 LinkRunner

8 LinkRunner AT Network Auto-Tester Critical Switch Port Details Graphical, color wiremap and cable details Comprehensive, one button AutoTest Flexible reporting to Link-Live Cloud Service or LinkRunner Manager

9 AirCheck G2 Wireless

10 AIRCHECK G2 WIRELESS TESTER NEW abgn & ac 3x3 Radio 5 Touch screen Simplified workflow Link-Live Cloud Repository

11 AIRCHECK G2 WIRELESS TESTER Complete Visibility Discovery of SSIDs, APs, clients, channels Intuitive interface Locate APs and Clients - Rogue detection! SSID Log in option

12 AirMagnet Mobile

13 HOW IT S USED: PLANNER Basic workflow: Load site details Define attenuation areas Define coverage / deployment limitations Place APs Verify requirements are met Document work done

14 HOW IT S USED: SURVEY Basic workflow: Load map Determine and configure survey types Walk site Verify requirements for deployment are met Document work done

15 HOW IT S USED: WIFI ANALYZER Basic workflow: Look for low hanging fruit in AirWISE Clean up known issues Use specific screens to analyze more in-depth issues Document work done

16 HOW IT S USED: SPECTRUM XT Basic workflow: Look for identified interferers Validate that interferers are impacting Wi-Fi network Use Find as needed to track down unexpected devices Document work done

17 OneTouch

18 What is OneTouch AT? Wired & Wi-Fi Analysis Standardized, Automated Testing Application Network Performance Troubleshooting tools Inline VoIP Analysis Capture Reporting Remote Control Cloud Services

19 Test profiles generated with Pass/Fail assessment Copper Fiber Discovery Performance Tests Autotest Profile Services Tests Application Tests Wi-Fi Packet Capture A full sets of validation criteria can be included

20 Test profiles generated for MS Outlook.com

21 All MS Outlook.com ports Protocol Packet Type Port Description LDAP TCP 389 Lightweight Directory Access Protocol (LDAP), used by Active Directory, Active Directory Connector, and the Microsoft Exchange Server 5.5 directory. Â TCP 379 The Site Replication Service (SRS) uses TCP port 379. Â TCP 390 Â TCP 3268 LDAP/SSL TCP 636 Â TCP 3269 IMAP TCP 143 IMAP/SSL TCP 993 POP3 TCP 110 POP3/SSL TCP 995 POP3 over SSL uses TCP port 995. NNTP TCP 119 NNTP/SSL TCP 563 NNTPS over SSL uses TCP port 563. While not a standard LDAP port, TCP port 390 is the recommended alternate port to configure the Exchange Server 5.5 LDAP protocol when Exchange Server 5.5 is running on a Microsoft Windows Active Directory domain controller. Global catalog. The Windows Active Directory global catalog (which is really a domain controller "role") listens on TCP port When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP. LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted. Global catalog over SSL. Applications that connect to TCP port 3269 of a global catalog server can transmit and receive SSL encrypted data. To configure a global catalog to support SSL, you must install a Computer certificate on the global catalog. Internet Message Access Protocol (IMAP), may be used by "standards-based" clients such as Microsoft Outlook Express, Live Mail, Mobile Devices to access the server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service and enables client access to the Exchange Information Store. IMAP4 over SSL uses TCP port 993. Before an Exchange server supports IMAP4 (or any other protocol) over SSL, you must install a Computer certificate on the Exchange 2000 server. This can be a self-signed certificate or a purchased signed certificate Post Office Protocol (POP3), enables "standards-based" clients such as Outlook Express, Windows Mail, Live Mail and other POP3 enabled mail clients to access the server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange Information store. Network News Transport Protocol (NNTP), sometimes called Usenet protocol, enables client access to public folders in the Information store. As with IMAP4 and POP3, NNTP runs on top of the IIS Admin Service. HTTP TCP 80 Hyper-Text Transfer Protocol is the protocol used primarily by Microsoft Outlook Web Access (OWA) HTTP/SSL TCP 443 HTTPS over SSL SMTP TCP 25 SMTP/SSL TCP 465 SMTP/LSA TCP 691 X.400 TCP 102 MS-RPC TCP 135 ULS TCP 522 DNS UDP/TCP 53 Simple Mail Transfer Protocol (SMTP) is the foundation for all e- mail transport in Exchange. The SMTP Service (SMTPSvc) runs on top of the IIS Admin Service. Unlike IMAP4, POP3, NNTP, and HTTP, SMTP in Exchange does not use a separate port for secure communication (SSL), but uses a security sub-system called Transport Layer Security (TLS). SMTP over SSL. TCP port 465 is reserved by common industry practice for secure SMTP communication using the SSL protocol. However SMTP typically still uses port 25 and use TLS for its security layer The Microsoft Exchange Routing Engine (RESvc) listens for routing link state information on TCP port 691. Exchange uses routing link state information to route messages and the routing table is constantly updated. TCP port 102 is the port that the Exchange message transfer agent (MTA) uses to communicate with other X.400-capable MTAs. Microsoft Remote Procedure Call is a Microsoft implementation of remote procedure calls (RPCs). TCP port 135 is actually only the RPC Locator Service, which is like the registrar for all RPC-enabled services that run on a particular server. In Exchange 2000, the Routing Group Connector uses RPC instead of SMTP when the target bridgehead server is running Exchange 5.5. Also, some administrative operations require RPC. To configure a firewall to enable RPC traffic, many more ports than just 135 must be enabled. User Locator Service (ULS) is a type of Internet directory service for conferencing clients, such as NetMeeting. Exchange 2000 Server and Exchange 2000 Conferencing Server do not implement a ULS, but rather take advantage of Active Directory for directory services (by TCP port 389). Domain Name System (DNS) is at the heart of all of the services and functions of Windows Active Directory and Exchange Server.

22 Thank You