NETSCOUT Handheld Network Test

for Enterprise Access

Networks

Christian Drost

How do you manage your access network?

Cisco ISR with Integrated Agent

Access

Internet

Wireless Access Point

Core Network Gateway

Computer

VOIP Phone

Camera

Link Sprinter

Link Runner

AirCheck One Touch AirMagnet Mobile

OneTouch

Handheld Network Test – Portfolio

AirCheck AirMagnet Mobile

LinkSprinter LinkRunner

Wireless

Wireline

Link-Live

For Proactive Projects and Reactive Troubleshooting

LinkSprinter

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.

Test

More skilled techs want details:

LinkSprinter deliver them on your phone via the built in Wi-Fi access point

LinkRunner

LinkRunner AT Network Auto-Tester

Graphical, color wiremap and cable details

Comprehensive, one button AutoTest

Critical Switch Port Details

Flexible reporting to Link-Live Cloud Service or LinkRunner Manager

AirCheck G2 Wireless

AIRCHECK G2 WIRELESS TESTER

NEW

• 802.11abgn & ac 3x3 Radio

• 5” Touch screen

• Simplified workflow

• Link-Live Cloud Repository

AIRCHECK G2 WIRELESS TESTER

Complete Visibility

• Discovery of SSIDs, APs, clients,

channels

• Intuitive interface

• Locate APs and Clients - Rogue

detection!

• SSID Log in option

AirMagnet Mobile

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

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

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

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

OneTouch

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

Copper

Fiber

Wi-Fi

Performance Tests

Packet Capture

Services Tests

Discovery

Application Tests

Test profiles generated with Pass/Fail assessment

Autotest Profile

A full sets of validation criteria can be included

Test profiles generated for MS Outlook.com

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 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.

 TCP 3268 Global catalog. The Windows Active Directory global catalog (which is really a domain controller "role") listens on TCP port 3268. When you are troubleshooting issues that may be related to a global catalog, connect to port 3268 in LDP.

LDAP/SSL TCP 636 LDAP over Secure Sockets Layer (SSL). When SSL is enabled, LDAP data that is transmitted and received is encrypted.

 TCP 3269 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.

IMAP TCP 143

Internet Message Access Protocol (IMAP), may be used by "standards-based" clients such as Microsoft Outlook Express, Live Mail, Mobile Devices to access the e-mail server. IMAP4 runs on top of the Microsoft Internet Information Service (IIS) Admin Service and enables client access to the Exchange Information Store.

IMAP/SSL TCP 993 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

POP3 TCP 110

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 e-mail server. As with IMAP4, POP3 runs on top of the IIS Admin Service, and enables client access to the Exchange Information store.

POP3/SSL TCP 995 POP3 over SSL uses TCP port 995.

NNTP TCP 119 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.

NNTP/SSL TCP 563 NNTPS over SSL uses TCP port 563.

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

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/SSL TCP 465

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

SMTP/LSA TCP 691

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.

X.400 TCP 102 TCP port 102 is the port that the Exchange message transfer agent (MTA) uses to communicate with other X.400-capable MTAs.

MS-RPC TCP 135

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.

ULS TCP 522

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).

DNS UDP/TCP 53 Domain Name System (DNS) is at the heart of all of the services and functions of Windows Active Directory and Exchange Server.

Thank You