Configuring Subnet Addressing | Paradyne 8510 RADSL, 8310 MVLt

Configuring the Hotwire DSLAM

Configuring Subnet Addressing

To define a subnet entry, the IP address has to be entered as the lower boundary address of the subnet. Otherwise, only a host entry can be configured.

For example, a subnet with a mask of 255.255.255.192 requires one of the following IP addresses:

H255.255.255.0

H255.255.255.64

H255.255.255.128

H255.255.255.192

NOTE:

For more information about the fields listed above, see Table 4-6, Filters

Options, in Chapter 4, 8310 MVL and 8510 RADSL Card Configuration.

Configuring Subnet Masks

After the IP address is entered, a default subnet mask is displayed. The default subnet mask is based on the IP address entered and can be changed.

If the IP Address entered is . . .	Then the Default Subnet Mask is . . .

xxx.xxx.xxx.0	255.255.255.0

xxx.xxx.0.0	255.255.0.0

xxx.0.0.0	255.0.0.0

xxx.xxx.xxx.xxx	255.255.255.255

To configure the DSL card, a valid subnet must be used. When a Host entry is input, any valid IP address results in a subnet mask of 255.255.255.255.

When a Subnet entry is entered, the valid subnet mask is based on the IP address entered. A valid subnet mask must be in one of the following formats:

H255.0.0.0

H255.nnn.0.0

H255.255.nnn.0

H255.255.255.nnn

Where nnn must be: 0, 128, 192, 224, 240, 248, 252, 254.

NOTE:

For more information about the fields listed above, see Table 4-4, Bridge

Options, in Chapter 4, 8310 MVL and 8510 RADSL Card Configuration.

3-6

January 1999

8000-A2-GB26-10

Image 36

Paradyne 8510 RADSL, 8310 MVLt manual Configuring Subnet Addressing, Configuring Subnet Masks

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 About This Guide Document Purpose and Intended Audience Document Summary Section Description Product-Related Documents Document Number Document Title Viii Hotwire Dslam System Description What is the Hotwire DSLAM? Hotwire Dslam Components Central Office COOptional Hotwire Dslam Chassis Input 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 Hotwire Menus and Screens Overview Components of a Hotwire Menu Menu and Screen Formats Components of a Hotwire Screen Commonly Used Navigation Keys Keys Definition Hotwire Menu Hierarchy Hotwire Chassis Main MenuHotwire ± MCC Menu Hotwire Chassis Hotwire ± DSL Menu Hotwire DSLDiagnostics Applications DSL Card Configuration Menu Logging In to the System DSL Card Monitoring Menu Reviewing the Levels of Access User Login Screen Card Selection Screen Column Position Display Description Heading D U X X Accessing the Hotwire ± DSL Menu Exiting from the SystemManually Logging Out Automatically Logging Out Configuring the Hotwire Dslam Service DomainDomain Types Management Domain Configuring the DSL Cards For each DSL card, to See Configuring VNIDs on a DSL Card Configuring the Active Vnid on each DSL Port Configuring Static Users Addressing a Location Using Dhcp Configuring Subnet Addressing Configuring Subnet Masks Configuring IP Filter Rules Configuring the Hotwire Dslam MVL and 8510 Radsl Card Configuration DSL Configuration Card Status Screens Card Status Options 1 Card Info Card InformationTime/Date Nvram Clear Nvram Cfg Loader Nvram Configuration Loader Card ResetCard Status Options 2 DOS Machine Card Status Options 3 Download Code Download Code and Apply Download F a and BDownload Code a or Apply Download B Apply Download B DSL Configuration Ports Screens Ports Options 1Ethernet Port Ports Options 2 DSL Ports Radsl Parameters 8510 Radsl Card Ports Options 3 DSL Ports MVL Parameters 8310 MVL Card DSL Configuration Interfaces Screens Interfaces Options General General InterfacesControl Control Interfaces DSL Configuration Users Screens DSL Configuration Bridge Screens Bridge Options 1 General General Bridge ParametersCard Vnid Port Vnid Bridge Options 2 Client Vnid Bridge Options 3 ARP Entry Add ARP Entry B DSL Configuration Service Node Screens Service Node Options SN Configuration 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 Monitoring the Hotwire Dslam DSL Monitoring Card Status Screens 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 Physical Layer Options 2 Ethernet Stats Ethernet Statistics Physical Layer Options 3 EtherHDLC Stats EtherHDLC StatisticsInitialized EtherHDLC Ports ± s1c, s1d, s1e, or s1f Physical Layer Options 4 DSL Link Perf DSL Link Performance Summary 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 Network Protocol Options 2 TCP Statistics TCP Data Statistics Network Protocol Options 3 TCP Connection StatisticsIP Statistics Network Protocol Options 4 Icmp Statistics Icmp Packet StatisticsSnmp Statistics Snmp Authentication Statistics Network Protocol Options 5 DSL Bridge Screens Bridge Table MAC Table ClientItem to Display ± Entry number Vnid ARP Table DSL SN Information Screen Default filter action ± Forward/discard DSL Monitoring IP Filters ScreenIP Filters Filter Table Diagnostics and Troubleshooting Diagnostic Screens Diagnostics Options Alarms Card AlarmsSelftest DSL Packet Echo Test Troubleshooting Checking AlarmsMajor Alarms 1 Action No Response at Startup Major Alarms 2 Action Minor Alarms 1 Action Margin Threshold Minor Alarms 2 Action Link DownThreshold Network Problems High-Level Troubleshooting Client-to-Service Node Segment Client Cannot Ping the Gateway RouterIf the Client cannot Ping the Gateway Router Then Client Cannot Reach Service Node Client-to-Service Node Segment Layer SolutionLayer 1 ± Physical 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 DSLAM-to-IPC Segment Layer Solution Movefromdef=1 IPC-to-Router Segment Layer Solution Client Cannot Reach Router Cannot Upload Configurations to a Unix Server Router-to-IPC Segment Layer Solution Performance Issues ± Viewing Network Statistics Examining Performance Issues Go To Download Code Download Code Download Only System Automatic Immediate Apply Traps DSL Card TrapsEvent Severity Comment Trap # Traps MIB Traps Glossary Default route Dhcp Relay AgentDhcp Server Domain Host Host routesHub Internet Service Node OpenLane DCEManager Packet Static route Subnet addressSubnet mask Telnet GL-6 Index IN-1 IN-2