User Guide
Table Of Contents
- Nortel WLAN Security Switch 2300 Series Configuration Guide
- Contents
- How to get Help
- Introducing the Nortel WLAN 2300 System
- Using the Command-Line Interface
- Configuring AAA for Administrative and Local Access
- Configuring and Managing Ports and VLANs
- Configuring and Managing Ports
- Configuring and Managing VLANs
- Managing the Layer 2 Forwarding Database
- Port and VLAN Configuration Scenario
- Configuring and Managing IP Interfaces and Services
- MTU Support
- Configuring and Managing IP Interfaces
- Configuring the System IP Address
- Configuring and Managing IP Routes
- Managing the Management Services
- Configuring and Managing DNS
- Configuring and Managing Aliases
- Configuring and Managing Time Parameters
- Setting the Time Zone
- Configuring the Summertime Period
- Statically Configuring the System Time and Date
- Displaying the Time and Date
- Configuring and Managing NTP
- Adding an NTP Server
- Removing an NTP Server
- Changing the NTP Update Interval
- Resetting the Update Interval to the Default
- Enabling the NTP Client
- Displaying NTP Information
- Managing the ARP Table
- Pinging Another Device
- Logging In to a Remote Device
- Tracing a Route
- IP Interfaces and Services Configuration Scenario
- Configuring SNMP
- Overview
- Configuring SNMP
- Displaying SNMP Information
- Configuring and Managing Mobility Domain Roaming
- Configuring User Encryption
- Configuring AP access points
- AP Overview
- Configuring AP access points
- Specifying the Country of Operation
- Configuring a Template for Automatic AP Configuration
- Configuring AP Port Parameters
- Configuring AP-WSS Security
- Configuring a Service Profile
- Configuring a Radio Profile
- Configuring Radio-Specific Parameters
- Mapping the Radio Profile to Service Profiles
- Assigning a Radio Profile and Enabling Radios
- Disabling or Reenabling Radios
- Displaying AP Information
- Displaying AP Configuration Information
- Displaying a List of Distributed APs
- Displaying a List of Distributed APs that Are Not Configured
- Displaying Connection Information for Distributed APs
- Displaying Service Profile Information
- Displaying Radio Profile Information
- Displaying AP Status Information
- Displaying AP Statistics Counters
- Configuring RF Auto-Tuning
- Wi-Fi Multimedia
- Configuring and Managing Spanning Tree Protocol
- Configuring and Managing IGMP Snooping
- Configuring and Managing Security ACLs
- About Security Access Control Lists
- Creating and Committing a Security ACL
- Mapping Security ACLs
- Modifying a Security ACL
- Using ACLs to Change CoS
- Enabling Prioritization for Legacy Voice over IP
- Security ACL Configuration Scenario
- Managing Keys and Certificates
- Why Use Keys and Certificates?
- About Keys and Certificates
- Creating Keys and Certificates
- Choosing the Appropriate Certificate Installation Method for Your Network
- Creating Public-Private Key Pairs
- Generating Self-Signed Certificates
- Installing a Key Pair and Certificate from a PKCS #12 Object File
- Creating a CSR and Installing a Certificate from a PKCS #7 Object File
- Installing a CA’s Own Certificate
- Displaying Certificate and Key Information
- Key and Certificate Configuration Scenarios
- Configuring AAA for Network Users
- About AAA for Network Users
- AAA Tools for Network Users
- Configuring 802.1X Authentication
- Configuring Authentication and Authorization by MAC Address
- Configuring Web-based AAA
- Configuring Last-Resort Access
- Configuring AAA for Users of Third-Party APs
- Assigning Authorization Attributes
- Overriding or Adding Attributes Locally with a Location Policy
- Configuring Accounting for Wireless Network Users
- Displaying the AAA Configuration
- Avoiding AAA Problems in Configuration Order
- Configuring a Mobility Profile
- Network User Configuration Scenarios
- Configuring Communication with RADIUS
- Managing 802.1X on the WSS Switch
- Managing Sessions
- Managing System Files
- Rogue Detection and Countermeasures
- About Rogues and RF Detection
- Summary of Rogue Detection Features
- Configuring Rogue Detection Lists
- Enabling Countermeasures
- Disabling or Reenabling Active Scan
- Enabling AP Signatures
- Disabling or Reenabling Logging of Rogues
- Enabling Rogue and Countermeasures Notifications
- IDS and DoS Alerts
- Displaying RF Detection Information
- Appendix A: Troubleshooting a WS Switch
- Fixing Common WSS Setup Problems
- Recovering the System Password
- Configuring and Managing the System Log
- Running Traces
- Using Show Commands
- Remotely Monitoring Traffic
- Capturing System Information for Technical Support
- Appendix B: Supported RADIUS Attributes
- Appendix C: Mobility Domain Traffic Ports
- Appendix D: DHCP Server
- Glossary
- Index
- Command Index
152 Configuring and Managing IP Interfaces and Services
320657-A
Tracing a Route
You can trace the router hops necessary to reach an IP host.
The traceroute facility uses the TTL (Time to Live) field in the IP header to cause routers and servers to generate specific
return messages. Traceroute starts by sending a UDP datagram to the destination host with the TTL field set to 1. If a
router finds a TTL value of 1 or 0, it drops the datagram and sends back an ICMP Time Exceeded message to the sender.
The traceroute facility determines the address of the first hop by examining the source address field of the ICMP
time-exceeded message.
To identify the next hop, traceroute again sends a UDP packet, but this time with a TTL value of 2. The first router
decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL value of 1,
discards the datagram, and returns the Time Exceeded message to the source. This process continues until the TTL is
incremented to a value large enough for the datagram to reach the destination host (or until the maximum TTL is
reached).
To determine when a datagram has reached its destination, traceroute sets the UDP destination port in the datagram to a
very large value, one that the destination host is unlikely to be using. In addition, when a host receives a datagram with
an unrecognized port number, it sends an ICMP Port Unreachable error to the source. This message indicates to the trac-
eroute facility that it has reached the destination.
To trace a route to a destination subnet, use the following command:
traceroute host [dnf] [no-dns] [port port-num] [queries num] [size size] [ttl hops]
[wait ms]
To trace the route to host server1, type the following command:
23x0# traceroute server1
traceroute to server1.example.com (192.168.22.7), 30 hops max, 38 byte packets
1 engineering-1.example.com (192.168.192.206) 2 ms 1 ms 1 ms
2 engineering-2.example.com (192.168.196.204) 2 ms 3 ms 2 ms
3 gateway_a.example.com (192.168.1.201) 6 ms 3 ms 3 ms
4 server1.example.com (192.168.22.7) 3 ms * 2 ms
In this example, server1 is four hops away. The hops are listed in order, beginning with the hop that is closest to the
WSS and ending with the route’s destination. (For information about the command options, see the Nortel WLAN
Security Switch 2300 Software Command Reference.)
IP Interfaces and Services Configuration Scenario
This scenario configures IP interfaces, assigns one of the interfaces to be the system IP address, and configures a default
route, DNS parameters, and time and date parameters.
1 Configure IP interfaces on the WSS_mgmt and roaming VLANs, and verify the configuration changes.
Type the following commands:
23x0# set interface WSS_mgmt ip 10.10.10.10/24
success: change accepted.
23x0# set interface roaming ip 10.20.10.10/24
success: change accepted.