Client Cannot Reach Service Node, Layer 1 ± | Paradyne 8310 MVLt

Diagnostics and Troubleshooting

Client Cannot Reach Service Node

Table 6-4. Client-to-Service Node Segment

Layer	Solution

Layer 1 ±	1. Make sure the PWR LED on the front of the Service Node is lit. Use only
Physical		the power adapter shipped with the unit.
	2.	To verify connection to the client, make sure the ETHERNET LED on the
		front of the Service Node is lit.
	3.	Make sure there is a physical connection between the Service Node and
		the Network Interface Card (NIC). If there is a LINK LED on the NIC
		card, make sure it is lit.
	4.	If there is a hub, check its cables and LEDs.
	5.	Make sure the correct type of cable is being used between the client and
		the Service Node. A crossover cable should be used if the client is not
		connected to a LAN hub.
	6.	Make sure the NIC and drivers are correctly installed.
	7.	Make sure the correct Service Node firmware is being used.

Layer 2 ± Network

1.If static addressing is used, make sure the client has its correct IP address and subnet mask by entering the following:

±Windows 95: winipcfg

±Windows NT: ipconfig/all

For other operating systems, use help or see the appropriate manual.

2.Restart the client after a static IP address has been added or changed.

3.Make sure the client can Ping its own IP address. This confirms the IP address was successfully accepted by the computer.

4.Check the PC's default gateway to make sure it is functioning properly.

1.If dynamic addressing is being used and the client cannot get an IP address from the Dynamic Host Configuration Protocol (DHCP) server, statically configure an IP address and then verify that the client can Ping the DHCP server.

2.After the client reaches the server, remove the IP address and return the system to dynamic (DHCP) addressing.

Make sure there are 32 or fewer DHCP users active on the port at any given time. Only 32 users are entered into the host table.

If the problem persists after the above items are checked, the client-to-service node segment of the network is functional.

8000-A2-GB26-10

January 1999

6-9

Image 87

Paradyne 8310 MVLt Client Cannot Reach Service Node, Client-to-Service Node Segment Layer Solution, Layer 1 ±, Physical

Contents

HOTWIRE Dslam for 8310 MVL and 8510 Radsl Cards Copyright E 1999 Paradyne Corporation All rights reserved Contents Configuring the Hotwire Dslam Traps Contents Document Purpose and Intended Audience About This Guide Section Description Document Summary Document Number Document Title Product-Related Documents Viii What is the Hotwire DSLAM? Hotwire Dslam System Description Hotwire Dslam Components Central Office COOptional Input Hotwire Dslam Chassis Front View of a Hotwire 8800 or 8810 Dslam Chassis Hotwire Dslam Features MCC CardRadsl or MVL Card Levels of Access Configuring the DSL CardsSoftware Functionality Monitoring the DSL Cards Troubleshooting and Diagnostics Overview Hotwire Menus and Screens Menu and Screen Formats Components of a Hotwire Menu Components of a Hotwire Screen Keys Definition Commonly Used Navigation Keys Hotwire Chassis Hotwire Menu HierarchyHotwire Chassis Main Menu Hotwire ± MCC Menu Applications Hotwire ± DSL MenuHotwire DSL Diagnostics DSL Card Configuration Menu DSL Card Monitoring Menu Logging In to the System User Login Screen Reviewing the Levels of Access Card Selection Screen D U X X Column Position Display Description Heading Automatically Logging Out Accessing the Hotwire ± DSL MenuExiting from the System Manually Logging Out Management Domain Configuring the Hotwire DslamService Domain Domain Types For each DSL card, to See Configuring the DSL Cards Configuring VNIDs on a DSL Card Configuring the Active Vnid on each DSL Port Addressing a Location Using Dhcp Configuring Static Users Configuring Subnet Masks Configuring Subnet Addressing Configuring IP Filter Rules Configuring the Hotwire Dslam DSL Configuration Card Status Screens MVL and 8510 Radsl Card Configuration Nvram Clear Card Status Options 1Card Info Card Information Time/Date DOS Machine Nvram Cfg Loader Nvram Configuration LoaderCard Reset Card Status Options 2 Apply Download B Card Status Options 3Download Code Download Code and Apply Download F a and B Download Code a or Apply Download B DSL Configuration Ports Screens Ports Options 1Ethernet Port DSL Ports Radsl Parameters 8510 Radsl Card Ports Options 2 DSL Ports MVL Parameters 8310 MVL Card Ports Options 3 DSL Configuration Interfaces Screens Interfaces Options General General InterfacesControl Control Interfaces DSL Configuration Bridge Screens DSL Configuration Users Screens Port Vnid Bridge Options 1General General Bridge Parameters Card Vnid Client Vnid Bridge Options 2 ARP Entry Add ARP Entry B Bridge Options 3 DSL Configuration Service Node Screens SN Configuration Service Node Options DSL Configuration Filters Screen IP Filters IP Filter Configuration screen Filters Options 1IP Filters IP Filter Table IP Filters IP Filter Configuration Filters Options 2Destination Address ± nnn.nnn.nnn.nnn format DSL Monitoring Card Status Screens Monitoring the Hotwire Dslam Login History Card Status OptionsCard Info General Card Information Syslog Screen Example DSL Monitoring Physical Layer Screens Physical Layer Options 1Active List Active Ports List Ethernet Stats Ethernet Statistics Physical Layer Options 2 Physical Layer Options 3 EtherHDLC Stats EtherHDLC StatisticsInitialized EtherHDLC Ports ± s1c, s1d, s1e, or s1f DSL Link Perf DSL Link Performance Summary Physical Layer Options 4 Physical Layer Options 5 DSL Perf Stats DSL Performance StatsCustomer Data DSL Error Stats Physical Layer Options 6DSL Xmit Status DSL Transmit Stats DSL Monitoring Interfaces Screens Monitor Interfaces Options Active List Active Interfaces ListStatus Interface Status DSL Network Protocol Screens Network Protocol Options 1 Socket StatisticsUDP Statistics TCP Statistics TCP Data Statistics Network Protocol Options 2 Network Protocol Options 3 TCP Connection StatisticsIP Statistics Network Protocol Options 4 Icmp Statistics Icmp Packet StatisticsSnmp Statistics Network Protocol Options 5 Snmp Authentication Statistics Bridge Table DSL Bridge Screens MAC Table ClientItem to Display ± Entry number ARP Table Vnid DSL SN Information Screen Filter Table Default filter action ± Forward/discardDSL Monitoring IP Filters Screen IP Filters Diagnostic Screens Diagnostics and Troubleshooting DSL Packet Echo Test Diagnostics OptionsAlarms Card Alarms Selftest No Response at Startup TroubleshootingChecking Alarms Major Alarms 1 Action Major Alarms 2 Action Margin Threshold Minor Alarms 1 Action Minor Alarms 2 Action Link DownThreshold High-Level Troubleshooting Network Problems Client-to-Service Node Segment Client Cannot Ping the Gateway RouterIf the Client cannot Ping the Gateway Router Then Physical Client Cannot Reach Service NodeClient-to-Service Node Segment Layer Solution Layer 1 ± Service Node-to-DSLAM Segment 1 Layer Solution Client Cannot Reach DslamLayer 1 ± Physical Service Node-to-DSLAM Segment 2 Layer Solution Layer 2 ±Network Client Cannot Reach IPC Movefromdef=1 DSLAM-to-IPC Segment Layer Solution Client Cannot Reach Router IPC-to-Router Segment Layer Solution Router-to-IPC Segment Layer Solution Cannot Upload Configurations to a Unix Server Examining Performance Issues Go To Performance Issues ± Viewing Network Statistics Download Code Download Only System Automatic Immediate Apply Download Code Traps DSL Card TrapsEvent Severity Comment Trap # Traps MIB Traps Glossary Domain Default routeDhcp Relay Agent Dhcp Server Internet HostHost routes Hub Packet Service NodeOpenLane DCE Manager Telnet Static routeSubnet address Subnet mask GL-6 IN-1 Index IN-2