Paradyne 8310 MVLt, 8510 RADSL Service Node-to-DSLAM Segment 2 Layer Solution, Layer 2 ±, Network

Page 89

Diagnostics and Troubleshooting

Table 6-5. Service Node-to-DSLAM Segment (2 of 2)

Layer

Solution

 

 

Layer 1 ±

5. Make sure the LINE LED on the Service Node is lit. This verifies a

Physical

 

DSL connection to the DSLAM.

(continued)

6.

On the Access Node, make sure the LINE STATUS is up.

 

 

7.

Make sure the CO splitter is connected correctly. The DSL line goes

 

 

to the 50-pin amphenol jack on the DSLAM and the other line goes to

 

 

the PSTN switch in the central office.

 

8.

Make sure the 50-pin amphenol jack is firmly attached to the correct

 

 

interface on the DSLAM. For the 20-slot chassis, the ports are labeled

 

 

1±6, 7±12, and 13±18.

 

9.

Make sure the loop characteristics are within MVL/RADSL

 

 

specifications.

 

 

Layer 2 ±

1. On the DSLAM, if using static IP addressing, make sure the address

Network

 

is correctly configured (screen A-E-D).

 

2.

On the DSLAM, make sure all configured ports are in use (screen

 

 

B-B-A). If ports are not in use, properly configure them.

 

3.

On the DSLAM, check the status of the port (screen A-C-B). If the

 

 

status is not active, restart the port.

 

4.

If dynamic addressing is being used and the clients cannot get an

 

 

IP address from the DHCP server, statically configure an IP address

 

 

and then verify that the client can Ping the DHCP server. After the

 

 

client reaches the server, remove the IP address and return the

 

 

system to dynamic (DHCP) addressing.

 

5.

An ARP table may have invalid entries if a recent configuration

 

 

change took place anywhere on the network and enough time has not

 

 

passed for the entry to expire. Check the ARP tables on the client,

 

 

DSLAM, and router.

 

6.

To ensure connection between the DSLAM and the Service Node,

 

 

perform a packet echo test (screen D-C). Make sure the number of

 

 

packets sent is the same as the number of packets received. If fewer

 

 

packets are being received than sent, the Service Node may not be

 

 

functioning correctly.

 

7.

If the DSLAM fails to connect to the Service Node, attempt to connect

 

 

upstream and downstream at lower speeds or configure the card to

 

 

rate adaptive mode (screen A-B-B). When a speed is changed, the

 

 

port must be restarted (screen A-C-B) for the change to take effect.

 

 

 

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

8000-A2-GB26-10

January 1999

6-11

Image 89
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 GuideSection Description Document SummaryDocument Number Document Title Product-Related DocumentsViii What is the Hotwire DSLAM? Hotwire Dslam System DescriptionOptional Hotwire Dslam ComponentsCentral Office CO Input Hotwire Dslam ChassisFront View of a Hotwire 8800 or 8810 Dslam Chassis Radsl or MVL Card Hotwire Dslam FeaturesMCC Card Software Functionality Levels of AccessConfiguring the DSL Cards Monitoring the DSL Cards Troubleshooting and Diagnostics Overview Hotwire Menus and ScreensMenu and Screen Formats Components of a Hotwire MenuComponents of a Hotwire Screen Keys Definition Commonly Used Navigation KeysHotwire Chassis Main Menu Hotwire Menu HierarchyHotwire ± MCC Menu Hotwire ChassisHotwire DSL Hotwire ± DSL MenuDiagnostics ApplicationsDSL Card Configuration Menu DSL Card Monitoring Menu Logging In to the SystemUser Login Screen Reviewing the Levels of AccessCard Selection Screen D U X X Column Position Display Description HeadingExiting from the System Accessing the Hotwire ± DSL MenuManually Logging Out Automatically Logging OutService Domain Configuring the Hotwire DslamDomain Types Management DomainFor each DSL card, to See Configuring the DSL CardsConfiguring VNIDs on a DSL Card Configuring the Active Vnid on each DSL Port Addressing a Location Using Dhcp Configuring Static UsersConfiguring Subnet Masks Configuring Subnet AddressingConfiguring IP Filter Rules Configuring the Hotwire Dslam DSL Configuration Card Status Screens MVL and 8510 Radsl Card ConfigurationCard Info Card Information Card Status Options 1Time/Date Nvram ClearCard Reset Nvram Cfg Loader Nvram Configuration LoaderCard Status Options 2 DOS MachineDownload Code Download Code and Apply Download F a and B Card Status Options 3Download Code a or Apply Download B Apply Download BEthernet Port DSL Configuration Ports ScreensPorts Options 1 DSL Ports Radsl Parameters 8510 Radsl Card Ports Options 2DSL Ports MVL Parameters 8310 MVL Card Ports Options 3DSL Configuration Interfaces Screens Control Control Interfaces Interfaces OptionsGeneral General Interfaces DSL Configuration Bridge Screens DSL Configuration Users ScreensGeneral General Bridge Parameters Bridge Options 1Card Vnid Port VnidClient Vnid Bridge Options 2ARP Entry Add ARP Entry B Bridge Options 3DSL Configuration Service Node Screens SN Configuration Service Node OptionsDSL Configuration Filters Screen IP Filters IP Filter Table IP Filters IP Filter Configuration screenFilters Options 1 Destination Address ± nnn.nnn.nnn.nnn format IP Filters IP Filter ConfigurationFilters Options 2 DSL Monitoring Card Status Screens Monitoring the Hotwire DslamCard Info General Card Information Login HistoryCard Status Options Syslog Screen Example Active List Active Ports List DSL Monitoring Physical Layer ScreensPhysical Layer Options 1 Ethernet Stats Ethernet Statistics Physical Layer Options 2Initialized EtherHDLC Ports ± s1c, s1d, s1e, or s1f Physical Layer Options 3EtherHDLC Stats EtherHDLC Statistics DSL Link Perf DSL Link Performance Summary Physical Layer Options 4Customer Data Physical Layer Options 5DSL Perf Stats DSL Performance Stats DSL Xmit Status DSL Transmit Stats DSL Error StatsPhysical Layer Options 6 DSL Monitoring Interfaces Screens Status Interface Status Monitor Interfaces OptionsActive List Active Interfaces List DSL Network Protocol Screens UDP Statistics Network Protocol Options 1Socket Statistics TCP Statistics TCP Data Statistics Network Protocol Options 2IP Statistics Network Protocol Options 3TCP Connection Statistics Snmp Statistics Network Protocol Options 4Icmp Statistics Icmp Packet Statistics Network Protocol Options 5 Snmp Authentication StatisticsBridge Table DSL Bridge ScreensItem to Display ± Entry number MAC TableClient ARP Table VnidDSL SN Information Screen DSL Monitoring IP Filters Screen Default filter action ± Forward/discardIP Filters Filter TableDiagnostic Screens Diagnostics and TroubleshootingAlarms Card Alarms Diagnostics OptionsSelftest DSL Packet Echo TestChecking Alarms TroubleshootingMajor Alarms 1 Action No Response at StartupMajor Alarms 2 Action Margin Threshold Minor Alarms 1 ActionThreshold Minor Alarms 2 ActionLink Down High-Level Troubleshooting Network ProblemsIf the Client cannot Ping the Gateway Router Then Client-to-Service Node SegmentClient Cannot Ping the Gateway Router Client-to-Service Node Segment Layer Solution Client Cannot Reach Service NodeLayer 1 ± PhysicalLayer 1 ± Physical Service Node-to-DSLAM Segment 1 Layer SolutionClient Cannot Reach Dslam Network Service Node-to-DSLAM Segment 2 Layer SolutionLayer 2 ± Client Cannot Reach IPC Movefromdef=1 DSLAM-to-IPC Segment Layer SolutionClient Cannot Reach Router IPC-to-Router Segment Layer SolutionRouter-to-IPC Segment Layer Solution Cannot Upload Configurations to a Unix ServerExamining Performance Issues Go To Performance Issues ± Viewing Network StatisticsDownload Code Download Only System Automatic Immediate Apply Download CodeEvent Severity Comment Trap # TrapsDSL Card Traps Traps MIB Traps Glossary Dhcp Relay Agent Default routeDhcp Server DomainHost routes HostHub InternetOpenLane DCE Service NodeManager PacketSubnet address Static routeSubnet mask TelnetGL-6 IN-1 IndexIN-2