NEC Network Hardware IP8800 S2400 User Manual

3.7.1 No RIP Routing Information Exists

Download from Www.Somanuals.com. All Manuals Search And Download.

1. Overview

Item

Subitem

No RIP information

Reference

IPv4 unicast routing

communication failure

3.7.2 No OSPF Routing Information Exists

3.7.3 No BGP4 Routing Information Exists

3.7.4 No Routing Information Exist [OP-NPAR]

No OSPF information

No BGP4 information

No VRF information

IPv4 multicast routing

communication failure

Communication disabled on PIM-SM

network

3.8.1 Communication on IPv4 PIM-SM Network Is

3.8.2 Multicast Data Is Double-relayed on IPv4

Data double-relayed on PIM-SM network

PIM-SM Network

Communication disabled on PIM-SSM

network

3.8.3 Communication on IPv4 PIM-SSM Network Is

3.8.5 IPv4 Multicast Communication Failure In VRF

Data double-relayed on PIM-SSM network 3.8.4 Multicast Data Is Double-relayed on IPv4

PIM-SSM Network

Communication failure of VRF

[OP-NPAR]

IPv6 network communication

failure

Communication disabled

DHCP trouble

3.9.1 Communication Is Disabled or Is Disconnected

3.9.2 IPv6 DHCP Troubleshooting

IPv6 multicast routing

communication failure

No RIPng information

No OSPFv3 information

No BGP4+ information

3.10.1 No RIPng Routing Information Exists

3.10.2 No OSPFv3 Routing Information Exists

3.10.3 No BGP4+ Routing Information Exists

IPv6 multicast routing

communication failure

Communication disabled on PIM-SM

network

3.11.1 Communication on IPv6 PIM-SM Network Is

3.11.2 Multicast Data Is Double-relayed on IPv6

Data double-relayed on PIM-SM network

PIM-SM Network

Communication disabled on PIM-SSM

network

3.11.3 Communication on IPv6 PIM-SSM Network Is

3.12.1 Communication Failure on Using IEEE 802.1X

Data double-relayed on PIM-SSM network 3.11.4 Multicast Data Is Double-relayed on IPv6

PIM-SSM Network

Layer 2 authentication

communication failure

Authentication failed in IEEE802.1X

Authentication failed in Web

authentication

3.12.2 Communication Failure on Using Web

Authentication

Authentication failed in MAC

authentication

3.12.3 Communication Failure on Using MAC

Authentication

Authentication failed in authentication

VLAN

3.12.4 Communication Failure on Using

Authentication VLAN [OP-VAA]

GSRP failure

3.13.1 GSRP Communication Failures

IPv4 VRRP failure

3.13.2 Communication with VRRP Configuration in

IPv4 Network Is Disabled

IPv6 VRRP failure

3.13.3 Communication with VRRP Configuration in

IPv6 Network Is Disabled

SNMP communication failure

MIB acquisition disabled

3.14.1 MIBs Cannot Be Obtained from SNMP

Manager

Trap receiving disabled

3.14.2 Traps Cannot Be Received by SNMP Manager

3.15.1 sFlow Packets Do Not Reach Collector

3.15.2 Flow Sample Does Not Reach Collector

3.15.3 Counter Sample Does Not Reach Collector

sFlow statistics failure

sFlow packet does not reach

Flow sample does not reach

Counter sample does not reach

Download from Www.Somanuals.com. All Manuals Search And Download.

1. Overview

Item

Subitem

Reference

Neighboring system information

cannot be acquired by LLDP

function

3.16.1 Unable to Obtain Neighboring System

Information via LLDP Function

Neighboring system information

cannot be acquired by OADP

function

3.16.2 Unable to Obtain Neighboring System

Information via OADP Function

Communication failure in NTP

3.17.1 Time Synchronization by NTP Is Disabled

Failure when using IEEE802.3ah/

UDLD function

Port becomes inactive

3.18.1 Port Becomes Inactive Due to IEEE802.3ah/

UDLD Function

Problems on redundant

3.19.1 Active System Switchover Is Disabled

configuration of basic control unit

(BCU)/control and switching unit

(CSU)/management and switching

unit (MSU)

[IP8800/S6700] [IP8800/

S6600] [IP8800/S6300]

Problems on redundant

BSU switchover disabled

3.20.1 Active BSU Switchover Is Disabled

configuration of basic switching

unit (BSU) [IP8800/S6700]

Problem on using power saving

function

Schedule is disabled

3.21.1 Schedule Is Disabled [IP8800/S6700]

[IP8800/S6600]

[IP8800/S6700] [IP8800/S6600]

Communication failure due to

discard of packets

3.23.1 Checking Filtering/QoS Setting Information

4.1 MAC Address Table Resource Shortage

Communication failure due to

resource shortage

The volume of MAC address table used

exceeds the accommodating condition.

[IP8800/S6700] [IP8800/

S6600] [IP8800/S6300]

The volume of VLAN identification table

used exceeds the accommodating

condition.

4.2 When Resource Shortage of VLAN Identification

Table Occurs

Resource shortage of shared memory

4.3 When Resource Shortage Occurs in Shared

Memory

Others

Re-check the setting according to "Configuration

Settings."

Download from Www.Somanuals.com. All Manuals Search And Download.

Troubleshooting System Failures

This chapter explains how to deal with the problems on the system.

2.1 Troubleshooting for IP8800/S6700, IP8800/S6600, and IP8800/S6300

2.2 Troubleshooting for IP8800/S3600 and IP8800/S2400

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

2.1 Troubleshooting for IP8800/S6700, IP8800/S6600,

and IP8800/S6300

2.1.1

Troubleshooting Procedure on System Failures

Follow the procedure below when the system failed.

Table 2-1: Troubleshooting System Failures

Failure

No.

Action

Execute the steps below immediately.

•

Fume generated from the system

1. Power off the system.

Unusual odor occurs from the system

Unusual sound occurs from the system

2. When the power cable is fastened by the slip-off preventive clamp,

remove it from the power cable.

3. For AC power supply, unplug the power cable.

4. For DC power supply, turn off the breaker of power distribution panel

connected to the system.

Shut down operation as described above and then contact the local sales

office.

1. When MC is inserted, first remove the MC then reboot the system by

turning it off and on.

2. When MC is not inserted, reboot the system by turning it off and on.

3. If the same problem still persists after system reboot, replace BCU/CSU/

MSU.

All LEDs on BCU/MSU are OFF

1. Check LED on the power supply and follow the steps below.

(1) If ALARM LED is lit in red on the power supply, replace the power

supply with a new one.

(2) If both POWER LED and ALARM LED are OFF on the power

supply, implement "Table 2-2: Power Failure Check Items." If the

problem is not settled, replace the power supply with LED turned off.

2. If all power supplies are running normally, replace BCU/CSU/MSU.

BCU/CSU/MSU SYSTEM1 LED lit in red or

orange

1. If an error message is output to the system operation panel, take the

action against the corresponding error message in manual "Message Log

Reference."

2. If no error message is output, replace BCU, BSU, CSU, MSU or NIF on

which STATUS LED is lit in red.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

No.

Failure

Action

Error message output to the system operation

panel

Take the action against the corresponding error message in the manual

"Message Log Reference."

STATUS LED on BCU/CSU/MSU is lit in red,

other LEDs are OFF, and no message on the

system operation panel

1. Check the single/redundant configuration of BCU/CSU/MSU.

(1) For the single configuration, follow the step 3 and later.

(2) For the redundant configuration, follow the step 2 and later.

2. Check the active/standby state of BCU/CSU/MSU.

(1) If the failure occurs only in one system, replace the BCU/CSU/MSU.

You do not have to follow the step 3 and later.

(2) If the failure occurs in both systems, follow the step 3 and later.

3. Check the LED on the power supply.

(1) If ALARM LED is lit in red on the power supply, replace the power

supply with a new one.

(2) If both POWER LED and ALARM LED are OFF on the power

supply, implement "Table 2-2: Power Failure Check Items" If the

problem is not settled, replace the power supply with LED turned off.

(3) If all power supplies are running normally, leave those power supplies

as is.

4. Turn off all power supplies installed on the system.

5. At least two seconds elapse, turn on all power supplies installed on the

system.

(1) If this failure occurs on BCU/CSU/MSU, replace the BCU/CSU/

MSU.

Table 2-2: Power Failure Check Items

Failure

No.

Action

Power switch on the power supply is OFF

Turn on the power switch.

Follow the steps below.

•

Power cable is unplugged

1. Turn off the power switch.

Power cable is not firmly connected to the system

Power cable is not securely fastened by the slip-off

preventive clamp

2. For DC power supply, turn off the breaker of power distribution

panel connected to the system.

3. Connect the power cable correctly.

4. If the power cable can be fastened by the slip-off preventive clamp,

fasten the power cable using it.

5. For DC power supply, turn on the breaker of power distribution

panel connected to the system.

6. Turn on the power switch.

Power supply is not securely mounted but loose

Follow the steps below.

1. Turn off the power switch.

2. For DC power supply, turn off the breaker of power distribution

panel connected to the system.

3. When the power cable is fastened by the slip-off preventive clamp,

remove it from the power cable.

4. Remove the power cable.

5. Remove the power supply and insert it securely.

6. Attach the power cable.

7. If the power cable can be fastened by the slip-off preventive clamp,

fasten the power cable using it.

8. For DC power supply, turn on the breaker of power distribution

panel connected to the system.

9. Turn on the power switch.

Measured input power is out of the range below.

100VAC: 90 to 132VAC

Contact the person in charge of the power facility and ask him/her to

take the action for input power.

200VAC: 180 to 264VAC

-48VDC: -40.5 to -57VDC

Note: Implement this matter only if input power can

be measured.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

2.1.2

Replacement Method of Optional Components

The optional component replacement procedures are described in "Hardware Installation Guide." Follow the

procedures described in the manual.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

2.2 Troubleshooting for IP8800/S3600 and IP8800/

S2400

2.2.1

Troubleshooting Procedure on System Failures

Follow the procedure below when the system failed.

Table 2-3: Troubleshooting System Failures

Failure

No.

Action

Execute the steps below immediately.

•

Fume generated from the system

1. Power off the system.

Unusual odor occurs from the system

Unusual sound occurs from the system

2. Remove the power cable of the system.

After the above steps, replace the system.

1. When MC is inserted, first remove the MC then reboot the system by

turning it off and on.

2. When MC is not inserted, reboot the system by turning it off and on.

3. If the same problem still persists after system reboot, replace the

system.

PWR LED on the system is OFF

Follow the steps below to take the action.

1. Follow the steps in "Table 2-4: Isolating Power Supply Failure"

2. For the redundant power model, replace the power supply that has

failed. The faulty power supply is in one of the states below.

(a) POWER LED is off.

(b) ALM1 LED is lit in red.

3. If 1 and 2 are not applicable, restart the system and confirm that the

environment is free from troubles.

(1) Turn off the power switch on the system (or power supply for the

redundant power model) and turn it on again to restart the system.

(2) If the system can be restarted, execute the show logging

command to view the failure information.

>show logging | grep ERR

(3) If a message "Caution, High temperature" exists in the retrieved

failure information, the operating environment may have caused the

failure. Request the system administrator to improve the

environment.

(4) If the system cannot be restarted by procedure (1) above and no

failure information exists in procedure (3) above or message

"Caution, High temperature" does not exist, the system may have

failed. Replace the system.

ST1 LED on the system is lit in red

A failure occurred or the system was powered on after it had remained

powered off for a long time (at least one month).

1. If you do not turn on the power of the system for a long time (one month

or more), reboot the system by turning it off and on.

2. In the case of other than the previous case, a failure might occur in the

system. Replace the system.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

No.

Failure

Action

System or line has failed.

•

ST1 LED on the system is blinking in red

LINK LED (10GBASE-R port and

1000BASE-X port) and 1-48 LED (10/100/

1000BASE-T port) on each port of the system

are lit in orange or OFF

1. For the redundant power supply model, check the states of the power

supplies and fan unit. Replace them if they have failed.

- If ALM LED on the fan unit is lit in red, replace the fan unit.

- If ALM1 LED or ALM2 LED or the power supply is lit in red, replace

the power supply.

- If POWER LED on the power supply is off, take the action against

power failure according to "Table 2-4: Isolating Power Supply

Failure." If POWER LED is still off after the action is taken, replace

the power supply.

2. For cases other than 1 above, refer to the error message and take the

action against the failure. Execute the show loggingcommand to

check the failure information and take the action.

>show logging | grep ERR

3. For the failure on the external power unit, refer to "2.2.2 Isolating

Failures on External Power Unit" to isolate the failure.

"EPU:Disconnect" is displayed for the system

management command although LEDs on the

system and external power unit are normal

Check the cable interconnecting the system and EPU. If the cable has

slipped off, restart the system as described below.

1. Power off the system.

2. Reconnect the cable that has slipped off.

3. Power off the system.

Table 2-4: Isolating Power Supply Failure

Failure

No.

Action

Power switch on the system (or power supply for the

redundant power model) is OFF

Turn on the power switch.

Power cable has slipped off or is loose

Follow the steps below.

1. Turn off the power switch.

2. Connect the power cable correctly.

3. Turn on the power switch.

For the redundant power supply model, the power

supply is not securely mounted but loose

Follow the steps below.

1. Turn off the power switch.

2. Insert the power supply correctly.

3. Turn on the power switch.

Measured input power is out of the range below.

100VAC: 90 to 127VAC

Contact the person in charge of the power facility and ask him/her to

take the action for input power.

200VAC: 180 to 254VAC

-48VDC: -40.5 to -57VDC

Note: Implement this matter only if input power can be

measured.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

2.2.2

Isolating Failures on External Power Unit

If the external power unit fails, follow the steps below to isolate the failure.

Table 2-5: Isolating Failures on External Power Unit

Failure

No.

Action

POWER LED on the external power unit is lit in

green

Check LED on the power module mounted on the external power unit

and identify the power module that is not normally running. If the power

module is normally running, the states below are provided.

•

EPU-A:

DC-OK: Lit in green, DC-ALM: OFF

EPU-B:

•

DC-OK: Lit in green, DC-FAIL: OFF, AC-OK: Lit in green

For the power module that is not normally running, implement "Table

2-7: Isolating Failures on Power Module."

POWER LED on the external power unit is OFF

Follow the steps in "Table 2-6: Isolating Failures on External Power

Unit (Main Body)."

Table 2-6: Isolating Failures on External Power Unit (Main Body)

Failure

No.

Action

Power switch on the external power unit is OFF

Turn on the power switch.

1. Turn off the power switch.

Power cable of the external power unit is not

correctly connected to the system

2. Connect the power cable correctly.

3. Turn on the power switch.

Input power to the external power unit is out of the

range below

(AC power supply: 90 to 132V)

Ask the system administrator to take the action because of the failure on

the power supply facility (i.e. not the failure on this system).

Other than 1 to 3 above

Replace the external power unit.

Table 2-7: Isolating Failures on Power Module

Failure

No.

Action

Power switch on the power module is OFF

Turn on the power switch on the power module.

Power cable of the power module is not correctly

connected to the system

1. Turn off the power switch on the power module.

2. Connect the power cable correctly.

3. Turn on the power switch on the power module.

Power module is not correctly mounted on the

external power unit

1. Turn off the power switch.

2. Mount the power module correctly.

3. Turn on the power switch.

Other than 1 to 3 above

Replace the power module.

Download from Www.Somanuals.com. All Manuals Search And Download.

2. Troubleshooting System Failures

2.2.3

Replacement Method of System and Optional Components

The replacement procedures for optional components are described in "Hardware Installation Guide." Follow the

procedures described in the manual.

Download from Www.Somanuals.com. All Manuals Search And Download.

Troubleshooting Functional Failures

in Operation

This chapter describes actions to be taken when the system does not operate normally

or the communication is not possible.

3.1 Problems on Login Password

3.2 Problems on MC

3.3 Problems on Operation T e rminal

3.4 Network Interface Communication Failure

3.5 Layer 2 Network Communication Failure

3.6 IPv4 Network Communication Failure

3.7 IPv4 Unicast Routing Communication Failure

3.8 IPv4 Multicast Routing Communication Failure

3.9 IPv6 Network Communication Failure

3.10 IPv6 Unicast Routing Communication Failure

3.11 IPv6 Multicast Routing Communication Failure

3.12 Layer 2 Authentication Communication Failure

3.13 Communication Failure on High-reliability Function

3.14 SNMP Communication Failure

3.15 Troubleshooting of sFlow Statistics (Flow Statistics) Function

3.16 Communication Failures on Neighboring System Managing Function

3.17 NTP Communication Failure

3.18 Communication Failure on IEEE802.3ah/UDLD Function

3.19 Problems on Redundant Configuration of Basic Control Unit (BCU)/Control and Switching

Unit (CSU)/Management and Switching Unit (MSU) [IP8800/S6700] [IP8800/S6600]

[IP8800/S6300]

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.20 Problems on Redundant Configuration of Basic Switching Unit (BSU) [IP8800/S6700]

3.23 Communication Failure Caused by Settings of Filtering/QoS

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.1 Problems on Login Password

3.1.1

Forgot the Login User Password

If you forgot the login user password and cannot login to the system during operation, follow the procedure below.

1. Reporting to the system administrator

First, consult the system administrator. However, if there is no login user eligible for the administrator (e.g., there is

no other login user), perform a default restart and set a password again.

Default restart

Press and hold the reset switch on the system for five or more seconds.

Since security check using a password is not performed, special care must be taken when doing default restart.

The password setting is enabled after starting the system.

2. Changing the password

When a password change is requested, the system administrator must change it and inform all the target login users

of the change (use the passwordcommand to change a password, or the clear passwordcommand to simply

delete it).

Figure 3-1: Changing Login User Password by System Administrator

# password user1

Changing local password for user1.

New password:

Retype new password:

3.1.2

Forgot the System Administrator Password

If all the login users with the system administrator privilege forgot the system administrator password and they cannot

enter the system administrator mode, perform the default restart to set up a password again.

Default restart

Press and hold the reset switch on the system for five or more seconds.

Since security check using a password is not performed, special care must be taken when doing default restart. The

password setting is valid after restarting the system.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.2 Problems on MC

3.2.1

"MC:--------" is displayed by entering the show system command

or the show mc command

When "MC:--------" is displayed by entering the show systemcommand or the show mccommand, follow the

instruction in "Table 3-1: Problems and Actions When "MC:--------" is displayed"

Table 3-1: Problems and Actions When "MC:--------" is displayed

No.

Failure

Troubleshooting Steps

Check to see ACC LED.

When ACC LED is lit in green, it indicates other process might be accessing to MC. After

the ACC LED lights off, execute the command again. If the ACC LED is not lit in green,

follow the instructions on No.2 and later.

Remove the MC then insert it.

Replace the MC with a new one.

After removing and inserting MC, execute the command again.

Confirm that no dust is attached on the MC or the memory card. If dust is adhere to them,

clean it with a dry cloth then insert the MC.

If a symptom still occurs after you have removed and inserted the MC for several times,

follow the instructions on No.3.

Replace the MC then execute the command again.

If a fault still occurs after the MC has been replaced, memory slot card might be broken. In

this case, replace the BCU [IP8800/S6700], the CSU [IP8800/S6600], the MSU

[IP8800/S6300], the system [IP8800/S3600], or the system [IP8800/S2400].

3.2.2

"MC not found" is displayed when MC is accessed

When "MC not found" is displayed after the command for accessing to MC has been executed, follow the instruction in

"Table 3-2: Problems and Actions When "MC not found" is displayed."

Table 3-2: Problems and Actions When "MC not found" is displayed

No.

Failure

Troubleshooting Steps

Check to see ACC LED.

When ACC LED is lit in green, it indicates other process might be accessing to MC. After

the ACC LED lights off, execute the command again. If ACC LED is not lit in green, follow

the instructions on No.2 and later.

Remove the MC then insert it.

Replace the MC with a new one.

After removing and inserting MC, execute the command again.

Check to see that any dust is not attached on the MC or the memory card. If dust is adhere

to them, clean it with a dry cloth then insert the MC.

If a symptom still occurs after you have removed and inserted the MC for several times,

follow the instructions on No.3.

Replace the MC then execute the command again. If a fault still occurs after the MC has

been replaced, memory slot card might be broken. In this case, replace the BCU [IP8800/

S6700], the CSU [IP8800/S6600], the MSU [IP8800/S6300], or the system [IP8800/

S3600] [IP8800/S2400].

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.3 Problems on Operation Terminal

3.3.1

Unable to Input/Display from the Console Correctly

When there is a problem connecting to the console, follow the instruction in "Table 3-3: Problems and Actions When

Connecting to Console."

When there is a problem connecting to the modem, follow the instruction in "Table 3-4: Problems and Actions When

Connecting to Modem." Also, see the manual provided with the modem.

Table 3-3: Problems and Actions When Connecting to Console

No.

Failure

Troubleshooting Steps

Nothing is displayed on the

screen.

Determine the cause by following the steps below:

1. Check if the ST1 LED on the front panel of the system lights in green. If it is not, see

"1.2 System and Partial Failure Analysis Overview."

2. Check to see if the cable is connected correctly.

3. Confirm that RS232C cross cable is used.

4. Confirm that communication software settings, including port number, communication

rate, data length, parity bit, stop bit, flow control are set as follows:

Communication rate: 9600 bps (or a custom value)

Data length: 8 bits

Parity bit: None

Stop bit: 1 bit

Flow control: None

You cannot enter any key.

Determine the cause by following the steps below:

1. Data sending/receiving may be interrupted by the XON/XOFF flow control. Restart the

data sending/receiving (press [Q] key with the [Ctrl] key pressed). If the problem

continues, follow the instructions on No.2 and later.

2. Check to see if the communication software is configured properly.

3. The screen may be suspended by [Ctrl]+[S]. Press any key.

Abnormal characters are

displayed upon login.

Negotiation with the communication software may have failed. Check the communication

rate of the communication software as described below.

1. If the communication rate for the CONSOLE (RS232C) has not been set up using

configuration command line console 0, check to see if the communication rate is

set to 9600 bps in the communication software.

2. If the communication rate for the CONSOLE (RS232C) is set to 1200, 2400, 4800, 9600

or 19200 bps using configuration command line console 0, confirm that the

communication rate in the communication software has been correctly set.

Abnormal characters appears

while entering user name.

Communication rate for the CONSOLE (RS232C) may have been changed. See No. 3.

Confirm that the login prompt appears on the screen. If it is not the case, starting up the

system is on the way. Wait for a while.

Abnormal characters appear and

command entry is rejected when

the communication rate of the

communication software is

changed after login.

If the communication rate of the communication software is changed after login, normal

display is not achieved. Reset the communication rate of the communication software to the

original setting.

Abnormal characters appear

upon login with HyperTerminal.

Negotiation with the communication software may have failed. See No. 3. Issue a break

signal using [Alt]+[B]. Depending on the communication rate in HyperTerminal, login

screen may not appear until you issue several break signals.

Item names and contents are not

displayed in line.

The size of information might be too large to display within one line. Change the screen size

by setting the communication software and increase the number of characters that can be

displayed in one line.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-4: Problems and Actions When Connecting to Modem

No.

Failure

Troubleshooting Steps

Automatic termination to the modem is

disabled.

Check the following.

•

Cable is connected properly.

Modem is powered on.

Telephone number is correct.

Settings of the modem are correct.

Line can be connected by connecting the modem to two terminals and

dialing.

Abnormal characters are displayed upon

Determine the cause by following the steps below:

1. Set the baud rate of the modem to 9600 bps.

2. If the modem supports communication standard V90, K56flex, x2, or later,

set the modem so that it is connected via V.34 communication method or

below.

Line is busy and cannot be connected by

redialing after disconnection.

Termination may be disabled for several seconds after disconnection of the line.

See the manual provided with the modem.

Line cannot be reconnected after line failure.

When the line is disconnected due to a failure, reconnection may be disabled

for up to 120 seconds. If you want to connect the line immediately, login via

another method, and use the killusercommand to apply forced logout to the

user who connected AUX by dial-up IP connection.

Line cannot be reconnected after

disconnection.

When dial-up IP connection is disconnected, it might take time to reconnect the

line. In this case, wait for approximately 30 seconds then reconnect the line.

3.3.2

When connecting to the remote operation terminal fails, take actions in the following table.

Table 3-5: Problems and Actions When Connecting Remote Operation Terminal

No.

Symptom

Action to Be Taken or Reference

Remote connection rejected.

Determine the cause by following the steps below:

1. To make sure the route for the remote connection has been established, execute the

pingcommand from a PC or workstation.

2. After the message indicating the connection has been established is displayed, if it needs

much time to display the prompt, communication with the DNS server may possibly be

disabled. (If this is the case, it takes approximately five minutes until the prompt is

displayed, which is a typical value and usually depends on network conditions.)

Determine the cause by following the steps below:

1. Check to see if the terminal used has the IP or IPv6 address allowed by the access list

for the configuration command line vtymode. Furthermore, confirm that denyhas

not been set for the IP or IPv6 address on the access list in the configuration command

(for details, see the manual "Configuration Commands, Vol. 1").

2. Confirm that maximum number of login users has not been exceeded (for details, see

the manual "Configuration Settings").

If reachability from the remote operation terminal to this system is lost when the

maximum number of users have logged in and then the reachability is recovered, a

remote operation terminal cannot log in to the system until the time of TCP protocol

timeout elapses to clear the session. The time of TCP protocol timeout is approximately

10 minutes although it depends on the states of the remote operation terminal and

network.

3. Check to see if protocols restricted by the configuration command transport

input in line vty mode are not being used. For more details, see the manual

"Configuration Commands."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Symptom

Action to Be Taken or Reference

Determine the cause by following the steps below:

Key entry rejected.

1. Data sending/receiving may be interrupted by the XON/XOFF flow control. Restart the

data sending/receiving (press [Q] key with the [Ctrl] key pressed). If key entry is still

disabled, check No. 2 or later.

2. Check to see if the communication software is configured properly.

3. The screen may be suspended by [Ctrl]+[S]. Press any key.

Some users remain in the login

state.

Wait for automatic logout or log in again and use the killusercommand to delete users

in the login state. If editing the configuration is on the way, the possibly changed

configuration information has not been saved. Log in again and enter the configuration mode

to save the change and exit from the editing.

3.3.3

If login authentication using RADIUS/TACACS+ is failed, check the following:

1. Communication with the RADIUS/TACACS+ server

Use the pingcommand to see if communication from this system to the RADIUS/TACACS+ server is achieved. If it

is not possible to communicate with the server, see "3.6.1 Communication Is Disabled or Is Disconnected." If a local

address has been defined in configuration, check the connectivity between this system and RADIUS/ TACACS+

servers by issuing pingfrom the local address.

2. Setting timeout value and retry count

For the RADIUS authentication, you can use configuration commands radius-server host,

radius-server retransmit, and radius-server timeoutto determine the maximum value of the

timeout, which determines that communication between this system and the RADIUS server is faulty. This value is

calculated by <set timeout value (sec.)> × <set retry count> × <set number of RADIUS servers>.

For the TACACS+ authentication, you can use configuration commands tacacs-server hostand

tacacs-servertimeoutto determine the mazimum value of the timeout, which determines that

communication between this system and TACACS+ server is faulty. This value is calculated by <set timeout value

(sec.)> × <set number of TACACS+ servers>. If this time is extremely long, applications such as telnet on the remote

operation terminal may be terminated as a result of timeout. If this is the case, edit the value on the RADIUS/

TACACS+ configuration or the timeout value on the application running on the remote operation terminal. If telnet

or ftp fails despite the "RADIUS/TACACS+ authentication successful" message appears in the operation log, the

application on the remote operation terminal may have timed out until it can connect to the running RADIUS/

TACACS+ server out of multiple RADIUS server specified in the configuration. In this case, make sure you set up

that the running RADIUS/TACACS+ server will take precedence or decrease the <Timeout value (in seconds)> ×

<Number of retries> value.

3.3.4

Command Authorization Using RADIUS/TACACS+ Is Disabled

If command authorization fails even when login to this system through RADIUS/TACACS+ authentication was

successful, or if an authorization error message is displayed and command cannot be executed, check the following:

1. Check using the show whoamicommand

Using the show whoamicommand on this system, the list of operation commands permitted/limited for the current

user can be displayed and checked. Confirm that the command list has been acquired according to the setting on the

RADIUS or TACACS+ server.

2. Check for server settings

Confirm that setting on command authorization on this system is correct on the RADIUS/TACACS+ server. For

RADIUS, beware the settings for vendor-specific attributes. For TACACS+, beware service and attribute name. For

detail on the RADIUS/TACACS+ server settings, see the manual "Configuration Settings."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3. Notes on writing command list

Care must be taken about the handling of spaces when you describe the command list for the command authorization

on this system on the RADIUS/TACACS+ server. For example, if show ip(show ipfollowed by a space) is set

in the permitted command list, the show ip interfacecommand is permitted but the show ipv6

interfacecommand is prohibited.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.4 Network Interface Communication Failure

3.4.1

Ethernet Port Cannot Be Connected

If the Ethernet port has possibly caused the communication failure, check for the NIF [IP8800/S6700] [IP8800/

S6600] [IP8800/S6300] and port statuses as follows.

(1) Checking NIF status [IP8800/S6700] [IP8800/S6600] [IP8800/S6300]

1. Checking log

For the log, see the manual "Message Log Reference."

2. Isolating the problem according to the NIF status.

Check the NIF status by using the show interfacescommand, and isolate the problem according to the table

below.

Table 3-6: Check and Action for NIF Status

No.

NIF Status

Problem

Action

active

The NIF is operating normally.

Check the port status according to "Table 3-7: Check and Action for

Port Status."

notconnect

inactive

The NIF is not installed.

Install the NIF board.

The inactivatecommand is set.

The NIF is not fully inserted.

NIF is not activated.

Use the activatecommand to activate the NIF.

Install the NIF board correctly.

Use the show systemcommand to check the BSU operation status

and set the operation status to "active." [IP8800/S6700]

Use the show system command to check the PSP operation status and

set the operation status to "active." [IP8800/S6600] [IP8800/S6300]

NIF not supported by the software

version is installed.

Check the NIF board type and software version. Replace the NIF board

or update the software.

NIF not supported by this system is

installed.

Replace the NIF board.

fault

The NIF is faulty.

According to the log of the NIF displayed by the show logging

command, see the corresponding part in the manual "Message Log

Reference" and follow the descriptions in [Action].

initialize

disable

The NIF is being initialized.

Wait until initialization completes.

no power enableis set by

Confirm that the NIF board to be used is installed and enter

configuration command.

configuration command power enableto activate the NIF.

(2) Checking port status

1. Checking log

For the log, see the manual "Message Log Reference."

2. Isolating the problem according to the port status.

Check the port status by using the show interfacescommand, and isolate the problem according to the table

below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-7: Check and Action for Port Status

No.

Port Status

Problem

Action

active up

The port is operating normally.

Line failure occurred in the port.

None

active down

According to the log of the port displayed by the show logging

command, see the corresponding part in manual "Message Log

Reference" and follow [Action] described.

inactive

The inactive state is set by one of the

following:

•

If the inactive state is set by standby link function of link

aggregation, it is a normal operation and therefore do not set the

active state using the activatecommand. Check standby link

function using the show channel-groupcommand with

"detail" parameter specified.

•

The inactivatecommand

Standby link of link aggregation

BPDU guard function of a spanning

tree

•

If the inactive state is set by the BPDU guard function of a

spanning tree, review the configuration of the opposite system.

Set up the configuration so that this system will not receive

BPDU. Using the activatecommand, set the port to the active

state. Check BPDU guard function using the show

spanning-treecommand with "detail" parameter specified.

If the inactive state is set by the port reset function of GSRP, the

active state automatically restores. Since this is a normal

operation, do not set to the active state using the activate

command.

•

GSRP port-reset function

Failure detected by the IEEE802.3ah/

UDLD function

•

Port blocked by L2 loop detection

function

•

Port blocked by the storm control

function

If the inactive state is set by detection of one-way link failure or

L2 loop by IEEE802.3ah/UDLD function, see

"3.18 Communication Failure on IEEE802.3ah/UDLD Function."

After recovery from failure, use the activatecommand to

activate the port.

•

When ports blocked by L2 loop detection function are in inactive

status, change the configuration, which causes the loop. And then

enable the inactive port by using the activatecommand. At

this time, if loop-detection auto-restore-timehas

been set by the configuration command, the ports will change

status to active status automatically.

•

If the inactive state is set by the storm control function, use the

activatecommand to activate the port after LAN recovered

from the storm.

If you want to set the active in any other case, confirm that the

cable is connected to the port to be used and use the activate

command to activate the port.

test

The port is in the line test by the test

interfacescommand.

To restart communication, execute the no test interfaces

command to stop the line test and activate the port with the

activatecommand.

fault

Hardware of the port is faulty.

According to the log of the port displayed by the show logging

command, see the corresponding part in manual "Message Log

Reference" and follow [Action] described.

initialize

The port is being initialized.

Wait until initialization completes.

disable or

locked

Configuration command shutdownis

set.

Confirm that the cable is connected to the port to be used and enter

configuration command no shutdownto activate the port.

(3) Checking statistical information

Enter the show port statisticscommand to check the number of sent/received packets and the number of

discarded packets on all ports installed on this system.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Figure 3-2: Example of "Checking Port Operation Status" [IP8800/S6700] [IP8800/S6600] [IP8800/S6300]

> show port statistics

2006/03/23 12:00:00

Port Counts:48

Port Name

Status T/R Unicast Multicast Broadcast

Discard

1/ 1 geth1/1 up

1/ 2 geth1/2 down Tx

1/ 3 geth1/3 down Tx

(Omitted hereafter)

Figure 3-3: Example of "Checking Port Operation Status" [IP8800/S3600] [IP8800/S2400]

> show port statistics

2006/03/23 12:00:00

Port Counts:48

Port Name

Status T/R All packets Multicast Broadcast

Discard

0/ 1 geth0/1 up

0/ 2 geth0/2 down Tx

0/ 3 geth0/3 down Tx

(Omitted hereafter)

If display item "Discard" is larger than 0 when this command is executed, a failure discarding packets has occurred. Use

the show interfacescommand to retrieve detail information of the port.

3.4.2

Communication Failure in Basic Switching Unit BSU/PSP

If BSU/PSP has possibly caused the communication failure, check for the BSU/PSP status as follows.

(1) Checking BSU/PSP operation status

1. Checking log

For the log, see the manual "Message Log Reference."

2. Isolating the problem according to the BSU/PSP operation status

Check the BSU/PSP operation status by using the show systemcommand, and isolate the problem according to

the table below.

Table 3-8: Check and Action for BSU/PSP Operation Status

No.

BSU Operation

Status

Problem

Action

active

The BSU/PSP is operating as active system.

See "3.4.1 Ethernet Port Cannot Be Connected."

standby hot

The BSU/PSP is operating as standby system

in hot standby mode.

standby cold

[IP8800/S6700]

The BSU/PSP is operating as standby system

in cold standby mode.

See "3.4.1 Ethernet Port Cannot Be Connected."

standby cold2

[IP8800/S6700]

[IP8800/S6600]

The BSU/PSP is operating as standby system

in cold standby 2 mode.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

BSU Operation

Status

Problem

Action

fault

Unavailable configuration has been set.

Use configuration command fldm preferto

correctly set flow distribution pattern of the filter

and QoS function.

Use configuration command fwdm preferto

correctly set the distribution pattern of the

maximum number of entries per device.

The BSU/PSP is faulty.

According to the log of the BSU displayed by the

show loggingcommand, see the corresponding

part in manual "Message Log Reference" and

follow [Action] described.

inactive

[IP8800/S6700]

The inactivate bsucommand is set.

Use the activate bsucommand to make the

BSU active, standby hot, or standby cold status. If

it does not become standby hot or standby cold

status, see "3.20 Problems on Redundant

Configuration of Basic Switching Unit (BSU)

[IP8800/S6700]."

The BSU is not fully inserted.

Install the BSU board correctly.

Different type of BSUs are installed together. Unify the type of all BSU boards.

BSU not supported by the software version is

installed.

Check the BSU board type and software version.

Replace the BSU board or update the software.

BSU not supported by this device is installed. Replace the BSU board.

notconnect

The BSU is not installed.

Check if as many BSU boards as required for active

[IP8800/S6700]

BSU + standby BSU (if standby BSU is not

required, only active BSU) are installed. If so, no

action is required. If not so, install the required

number of BSU boards.

initialize

The BSU/PSP is being initialized.

Wait until initialization completes.

disable

[IP8800/S6700]

no power enableis set by configuration

command.

After checking that the BSU board to be used is

installed, use configuration command power

enableto make the BSU active, standby hot, or

standby cold status. If it does not become standby

hot or standby cold status, see "3.20 Problems on

Redundant Configuration of Basic Switching Unit

(BSU) [IP8800/S6700]."

3.4.3

Actions against Troubles on 10BASE-T/100BASE-TX/

1000BASE-T

If a trouble occurs on 10BASE-T/100BASE-TX/1000BASE-T, follow the procedure below to isolate the problem.

1. Checking log

For the log, see the manual "Message Log Reference."

2. Isolating the problem according to the failure analysis method

Isolate the problem according to the failure analysis method listed below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-9: Troubleshooting for Failed 10BASE-T/100BASE-TX/1000BASE-T

No.

Troubleshooting Steps

Problem

Action

According to the failure

statistical information

displayed by the show

interfacescommand,

check to see if the statistical

information below is

counted for the port. If

counted, see "Problem" and

"Action" columns.

Line quality is

degraded.

Check to see if the cable type is correct. For the fiber optics type, see

"Hardware Installation Guide."

Check to see if MDI-X is selected for pin mapping in the case of the

following:

•

The port setting is fixed.

The port setting is auto negations and auto MDIX function is

disabled.

Check the cable length. For the cable length, see "Hardware Installation

Guide."

•

Link down

Check to see if the cable is connected correctly.

Replace with the connection interface supported by this system. For the

connection interfaces supported by this system, see "Configuration

Settings."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfaces(Ethernet) command and follow the indicated actions.

For the test type to be specified, see "6.1 Testing Line."

According to the receiving

error statistical information

displayed by the show

interfacescommand,

check to see if the statistical

information below is

counted for the port. If

counted, see "Problem" and

"Action" columns.

Line quality is

degraded.

Check to see if the cable type is correct. For the fiber optics type, see

"Hardware Installation Guide."

Check to see if MDI-X is selected for pin mapping in the case of the

following:

•

The port setting is fixed.

The port setting is auto negations, and auto MDIX function is

disabled.

Check the cable length. For the cable length, see "Hardware Installation

Guide."

•

CRC errors

Symbol errors

Check to see if the cable is connected correctly.

Replace with the connection interface supported by this system. For the

connection interfaces supported by this system, see "Configuration

Settings."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfacescommand and follow the indicated actions. For the test

type to be specified, see "6.1 Testing Line."

According to the failure

statistical information

displayed by the show

interfaces command,

check to see if the statistical

information below is

Pin mapping of the

cable is not correct.

Correct the pin mapping. For pin mapping, see the manual

"Configuration Settings."

counted for the port. If

counted, see "Problem" and

"Action" columns.

•

MDI cross over changed

Check the line type/line

speed for the port according

to the "Port detail"

information generated by the

show interfaces

command.

If the line type/line speed is

not correct, see the

"Problem" and "Action"

columns.

An incompatible

cable is used.

Check to see if the cable type is correct. For the fiber optics type, see

"Hardware Installation Guide."

The values set for

configuration

commands speed

and duplexare

incompatible with

the target system.

Use the same values as the remote system in configuration commands

speedand duplex.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps

Problem

Action

According to the failure

statistical information

displayed by the show

interfacescommand,

check to see if the statistical

information below is

Packets with

invalid frame

length are received.

Follow the jumbo frame setting on the remote system.

counted for the port.

If counted, see "Problem"

and "Action" columns.

•

Long frames

Check to see if statistics in

the following is not counted

by the show qos

Packets are being

discarded.

Review the system maintenance using discard control and shaper.

queueingcommand. If it

is counted, see "Problem"

and "Action" columns.

•

discard_pkt

3.4.4

Actions against Troubles on 1000BASE-X

If a trouble occurs on 1000BASE-X, follow the procedure below to isolate the problem.

1. Checking log

For the log, see the manual "Message Log Reference."

2. Isolating the problem according to the failure analysis method

Isolate the problem according to the failure analysis method listed below.

Table 3-10: Failure Analysis Method for Troubles on 1000BASE-X

No.

Troubleshooting Steps

Problem

Action

According to the failure

Line quality on

receiving side is

degraded.

Check the type of fiber optics. For the fiber optics type, see "Hardware

Installation Guide."

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port. If counted,

see "Problem" and "Action"

columns.

Check the attenuation value if an optical attenuator is used. For the

optical level, see "Hardware Installation Guide."

Check the cable length. For the cable length, see "Hardware Installation

Guide."

Check to see if the cable is connected correctly. Check to see if end

surfaces of the cable are dirty. If they are dirty, remove the dirt.

•

Link down

Signal detect errors

Check to see if the transceiver is connected correctly.

Use the same values as the remote system in configuration commands

speedand duplex.

Follow the segment standard on the remote system.

Check to see if the optical level is correct. For the optical level, see

"Hardware Installation Guide."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfacescommand and follow the indicated actions.

For the test type to be specified, see "6.1 Testing Line."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps

Problem

Action

According to the receiving error

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

Line quality on

receiving side is

degraded.

Check the type of fiber optics. For the mode, see "Hardware Installation

Guide."

Check the attenuation value if an optical attenuator is used. For the

optical level, see "Hardware Installation Guide."

Check the cable length. For the cable length, see "Hardware Installation

Guide."

If counted, see "Problem" and

"Action" columns.

Check to see if the cable is connected correctly. Check to see if end

surfaces of the cable are dirty. If they are dirty, remove the dirt.

•

CRC errors

Symbol errors

Check to see if the transceiver is connected correctly.

Use the same values as the remote system in configuration commands

speedand duplex.

Follow the segment standard on the remote system.

Check to see if the optical level is correct. For the optical level, see

"Hardware Installation Guide."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfacescommand and follow the indicated actions. For the test

type to be specified, see "6.1 Testing Line."

According to the failure

Transceiver is

faulty.

Replace the transceiver.

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

If counted, see "Problem" and

"Action" columns. [IP8800/

S3600] [IP8800/S2400]

•

TX fault

Check to see if the combination

of transceivers is valid when

using the 1 core optical cable

such as 1000BASE-BX.

Combination of

transceivers is

invalid.

For 1000BASE-BX, use U type and D type transceivers in pairs. Check

to see if the transceiver type is correct.

According to the failure

Packets with

Follow the jumbo frame setting on the remote system.

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

invalid frame

length are received.

If counted, see "Problem" and

"Action" columns.

•

Long frames

Check to see if statistics in the

following is not counted by the

show qos queueing

command. If it is counted, see

"Problem" and "Action"

columns.

Packets are being

discarded.

Review the system maintenance using discard control and shaper.

•

discard_pkt

3.4.5

Actions against Troubles on 10GBASE-R

If a trouble occurs on 10GBASE-R, follow the procedure below to isolate the problem.

1. Checking log

For the log, see the manual "Message Log Reference."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

2. Isolating the problem according to the failure analysis method

Isolate the problem according to the failure analysis method listed below.

Table 3-11: Failure Analysis Method for Troubles on 10GBASE-R

No.

Troubleshooting Steps

Problem

Action

According to the failure

Line quality on

receiving side is

degraded.

Check the type of fiber optics. For the fiber optics type, see "Hardware

Installation Guide."

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

Check the attenuation value if an optical attenuator is used. For the

optical level, see "Hardware Installation Guide."

Check the cable length. For the cable length, see "Hardware Installation

Guide."

If counted, see "Problem" and

"Action" columns.

Check to see if the cable is connected correctly. Check to see if end

surfaces of the cable are dirty. If they are dirty, remove the dirt.

•

Signal detect errors

LOS of sync

[IP8800/S6700]

[IP8800/S6600]

[IP8800/S6300]

HI_BER

[IP8800/S6700]

[IP8800/S6600]

[IP8800/S6300]

Check to see if the transceiver is connected correctly.

For the transceiver, follow the segment standard on the remote system.

•

Check to see if the optical level is correct. For the optical level, see

"Hardware Installation Guide."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfaces command and follow the indicated actions. For the test

type to be specified, see "6.1 Testing Line."

[IP8800/S6700]

[IP8800/S6600]

[IP8800/S6300]

According to the receiving error

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

Line quality on

receiving side is

degraded.

Check the type of fiber optics. For the fiber optics type, see "Hardware

Installation Guide."

Check the attenuation value if an optical attenuator is used. For the

optical level, see "Hardware Installation Guide."

Check the cable length. For the cable length, see "Hardware Installation

Guide."

If counted, see "Problem" and

"Action" columns.

Check to see if the cable is connected correctly. Check to see if end

surfaces of the cable are dirty. If they are dirty, remove the dirt.

•

CRC errors

•

Symbol errors

Check to see if the transceiver is connected correctly.

For the transceiver, follow the segment standard on the remote system.

Check to see if the optical level is correct. For the optical level, see

"Hardware Installation Guide."

Perform the line test on this system and confirm that there is no problem

in the receiving function. See the execution results of the no test

interfacescommand and follow the indicated actions. For the test

type to be specified, see "6.1 Testing Line."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps

Problem

Action

According to the failure

Line quality on

sending side is

degraded.

Check the type of fiber optics. For the fiber optics type, see "Hardware

Installation Guide."

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port. If counted,

see "Problem" and "Action"

columns. [IP8800/S6700]

[IP8800/S6600] [IP8800/

S6300]

Check the attenuation value if an optical attenuator is used. For the

optical level, see "Hardware Installation Guide."

Check the cable length. For the cable length, see "Hardware Installation

Guide."

Check to see if the cable is connected correctly. Check to see if end

surfaces of the cable are dirty. If they are dirty, remove the dirt.

•

Check to see if the transceiver is connected correctly.

For the transceiver, follow the segment standard on the remote system.

Check to see if the optical level is correct. For the optical level, see

"Hardware Installation Guide."

Perform the line test on this system and confirm that there is no problem

in the sending function. See the execution results of the no test

interfacescommand and follow the indicated actions. For the test

type to be specified, see "6.1 Testing Line."

According to the failure

Packets with

Follow the jumbo frame setting on the remote system.

statistical information displayed

by the show interfaces

command, check to see if the

statistical information below is

counted for the port.

invalid frame

length are received.

If counted, see "Problem" and

"Action" columns.

•

Long frames

Check to see if statistics in the

following is not counted by the

show qos queueing

command. If it is counted, see

"Problem" and "Action"

columns.

Packets are being

discarded.

Review the system maintenance using discard control and shaper.

•

discard_pkt

3.4.6

Communication Failure on Using PoE

If electricity is not provided when PoE is in use, isolate the problem using the failure analysis methods listed in the

following table.

Table 3-12: Communication Failure Analysis Methods When PoE Is in Use

No.

Troubleshooting Steps and Command

Action

Check to see PoEStatus display on the port by

the show power inlinecommand.

•

PoEStatus indicates off

Electricity is not provided. Go to No.2.

PoEStatus indicates denied

A shortage of electricity to the whole equipment occurs. Go to No.3.

PoEStatus indicates faulty

Electricity is unable to be provided to the connected equipment. Go to No.4.

Check to see if the port is shutdown.

•

The port is shutdown

Use the no shutdowncommand.

The port is not showdown

Check to see if Power receiving equipment is connected properly.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Check to see Threshold(W) and Allocate(W)

by the show power inlinecommand.

Because a value in Allocate(W) is larger than one in Threshold(W), electricity is

not able to be provided. First, check to see the amount of power supply provided

to the whole system, the amount of electrical power allocation to the ports, and

power consumption of the ports. And then configure these items to adjust

allocations.

Check to see if a fault occurs by the show

Power receiving equipment or connection cable might be faulty.

loggingcommand.

•

When "0/x Supplying power was stopped by the overload detection." is

indicated.

Because overload is detected, electricity is not able to be provided. Check to see

the power receiving equipment or the connection cables. If it is not recovered,

change the type and length of the cables by seeing "Hardware Installation

Guide."

If devices providing PoE are connected with each other, disable the PoE

function of the port by the power inlinecommand.

3.4.7

Communication Failure on Using Link Aggregation

If communication is disabled or if degenerated operation is performed when link aggregation is in use, isolate the

problem using the failure analysis methods listed in the following table.

Table 3-13: Communication Failure Analysis Methods When Link Aggregation Is in Use

No.

Troubleshooting Steps and Command

Action

Check the setting of failed link aggregation

using the show channel-group

command with "detail" parameter specified.

Check to see if the link aggregation mode matches that of the remote system. If the

mode is different from that of the remote system, change the mode so that it will

match that of the remote system.

If the link aggregation mode matches that of the remote system, check to see if the

LACP starting methods for both ports are set to "passive." If they are set to

"passive," change the setting on either one of the ports to "active."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Check the setting of failed port status using

the show channel-groupcommand

with "detail" parameter specified.

Check the status of each port. If all ports in a link aggregation group are Down, the

link aggregation group is also Down.

Take the action below for the Down port depending on the Reason displayed.

•

CH Disabled

The link aggregation group is Disabled and Down.

Port Down

The link is down. See "3.4 Network Interface Communication Failure."

Port Speed Unmatch

Due to mismatch of the line speed on other ports in the link aggregation group,

a degeneration has occurred. To avoid degeneration, match the speed on all

ports in the link aggregation group.

•

Duplex Half

The mode is Half and the degenerated status has occurred. To avoid degenera-

tion, set the Duplex mode to Full.

Port Selecting

Because the port aggregation conditions are being checked, the degeneration

has occurred. Wait until the check completes. If the degeneration is not recov-

ered though you wait for a while, check to see the operation status and settings

of the remote system.

•

Waiting Partner Synchronization

The system has finished the port aggregation condition check and is waiting for

the synchronization of the connected port, so the degeneration has occurred. If

recovery does not occur after a while, check the remote system operation status

and settings.

•

Partner System ID Unmatch

Partner System ID received from the connected port does not match the Partner

System ID of the group. As a result, the degeneration has occurred. To avoid de-

generation, check the remote system operation and wiring.

LACPDU Expired

Since the valid LACPDU time from the connected port has expired, the port has

degenerated. Check the LACPDU statistics using the show chan-

nel-groupstatisticscommand with "lacp" parameter specified. Also,

check the remote system operation status.

•

Partner Key Unmatch

Since Key received from the connected port does not match Partner Key of the

group, the degeneration has occurred. To avoid degeneration, check the remote

system operation and wiring.

Partner Aggregation Individual

Since link aggregation disabled is received from the connected port, the degen-

eration has occurred. To avoid degeneration, check the remote system operation

and settings.

Partner Synchronization OUT_OF_SYNC

Since synchronization disabled is received from the connected port, the degen-

eration has occurred. (This occurs if configuration is changed on this system or

the line is blocked on the remote system.)

•

Port Moved

The connected port was connected with another port. Check the wiring.

Operation of Detach Port Limit

Since the detached port limiting function is activated, the link aggregation group

is Down.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.5 Layer 2 Network Communication Failure

3.5.1

Layer 2 Communication by VLAN Is Disabled

If layer 2 communication is disabled when using VLAN, isolate the problem using failure analysis method listed in the

following table.

(1) Checking VLAN status

Execute the show vlancommand or execute the show vlancommand with "detail" parameter specified and check

the VLAN status. Check items for each VLAN function are listed below.

(a) Check items common to all VLAN functions

•

Confirm that the VLAN setting for the port is correct.

Confirm that the port has been set up with the compatible mode. If the expected port does not belong to

the default VLAN (VLAN ID 1), check the setting below.

• Confirm that a port VLAN other than VLAN ID 1 is not assigned for the access VLAN or native VLAN.

• Confirm that the default VLAN setting is assigned for "allowed vlan" in the trunk port.

• Confirm that a mirror port is not assigned for.

•

Confirm that VLANs with the function enabled (such as VLAN authentication [static] of IEEE802.1X

function, Web authentication [fixed VLAN mode], and MAC authentication) and VLANs with the function

disabled are not in the same trunk port.

(b) Check items for protocol VLAN

If protocol VLAN is in use, execute showvlanand confirm that the protocol is set correctly.

# show vlan

VLAN ID:100 Type:Protocol based Status:Up

Protocol VLAN Information Name:ipv4

EtherType:0800,0806 LLC: Snap-EtherType:

Learning:On Uplink-VLAN:

Uplink-Block:

Tag-Translation:

•

When using the MAC VLAN, execute the show vlan mac-vlancommand to confirm that the MAC

address that is allowed the VLAN communication is set up correctly. The value in the parentheses indicates

the function that registers a MAC address.

[Function]

static: MAC address that is set with configuration.

dot1x: MAC address that is set with IEEE802.1X.

wa: MAC address that is set with Web authentication.

vaa: MAC address that is set with authentication VLAN.

# show vlan mac-vlan

VLAN ID:100

MAC Counts:4

0012.e200.0001 (static)

0012.e200.0003 (static)

0012.e200.00:02 (static)

0012.e200.00:04 (dot1x)

•

Execute the show vlan mac-vlan command to confirm that the same MAC address on the layer 2

authentication has not been set up for different VLAN configuration. A MAC address with * (asterisk) means

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

that the identical MAC address is set in the configuration and is disabled.

# show vlan mac-vlan

VLAN ID:500

MAC Counts:4

0012.e200.aa01 (static)

0012.e200.aa02 (static)

0012.e200.aa04 (dot1x)

0012.e200.aa03 (static)

VLAN ID:600

MAC Counts:1

* 0012.e200.aa01 (dot1x)

(2) Checking port status

•

Execute the show vlancommand with "detail" parameter specified, and confirm that the port is Up. If the

port is Down, see "3.4 Network Interface Communication Failure."

•

Confirm that the port is in the Forwarding status. If the port is in the Blocking status, the reason is shown

in parentheses. Check the operation status of the function causing the problem.

[Cause]

VLAN: VLAN is specified to suspended.

CH: Forwarding is suspended by link aggregation.

STP: Forwarding is suspended by spanning tree.

GSRP: Forwarding is suspended by GSRP.

dot1x: Forwarding is suspended by IEEE802.1X.

CNF: Forwarding is suspended due to inability of configuration setting.

AXRP: Forwarding is suspended by Ring Protocol.

# show vlan detail

VLAN ID:100 Type:Protocol based Status:Up

Port Information

0/1

0/2

Up Forwarding

Untagged

Tagged

(3) Checking MAC address table

(a) Checking MAC address learning status

•

Execute the show mac-address-tablecommand to retrieve the information of the failed destination

MAC address.

# show mac-address-table

MAC address

VLAN

Type

Port-list

0012.e22c.650c

0012.e22c.650b

Dynamic 0/1

Dynamic 0/2

•

Take the action below according to the Type displayed.

[When Type displayed is Dynamic]

MAC address learning information may not be updated. Execute the clear mac-address-table

command to clear old information. The old information can be also cleared by sending frames from the

destination system.

[When Type displayed is Static]

Check the forwarding destination port configured using configuration command mac-address-table

static.

[When Type displayed is Snoop]

See "3.5.4 Multicast Relay by IGMP snooping Is Disabled" and "3.5.5 Multicast Relay by MLD snooping Is

Disabled."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

[When Type displayed is Dot1x]

See "3.12.1 Communication Failure on Using IEEE 802.1X."

[When Type displayed is Wa]

See "3.12.2 Communication Failure on Using Web Authentication."

[When Type displayed is Macauth]

See "3.12.3 Communication Failure on Using MAC Authentication."

•

Flooding is executed if the MAC address is not displayed.

• IP8800/S6700, IP8800/S6600, and IP8800/S6300:

If the communication still has been blocked despite no display appears, check to see if learning is suspended by

MAC address learning limitation. In addition, check to see if the threshold in the Storm Control function is not too

low.

• IP8800/S3600 and IP8800/S2400:

If the communication still has been blocked despite no display appears, check to see if the Suppress Port-to-Port

Forwarding has been enabled. In addition, check to see if the threshold in the Storm Control function is not too low.

(b) Checking MAC address learning limitation [IP8800/S6700] [IP8800/S6600] [IP8800/S6300]

Execute the show mac-address-tablecommand with "learning-counter" parameter specified to check the

information of MAC address learning limitation for the port and the VLAN to be checked.

>show mac-address-table learning-counter port 1/1-6

Date 2005/09/21 20:00:57 UTC

Port counts:6

Port

1/1

1/2

1/3

1/4

1/5

1/6

Count Maximum Threshold Status

1000

- -

800 Learning

- -

40 Stop learning <---1

40 Learning

>show mac-address-table learning-counter vlan

Date 2005/09/21 20:00:57 UTC

VLAN counts:4

Count Maximum Threshold Status

1000

- -

100

200

4095

800 Stop learning <---1

- No learning

100 Learning

<---2

100

1. MAC address learning is suspended according to the MAC address learning limitation value. Frames from the

unlearned source address are discarded without learning the MAC address. However, flooding is executed for frames

of VLAN for which MAC address learning is suppressed.

2. Suppression of MAC address learning is set. Flooding is executed for received frames.

(4) Checking filtering/QoS

Certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth

monitoring, discarding control, or shaper of the QoS control. Check to see if the conditions of filtering and QoS control

in the configuration have been set up correctly and if bandwidth monitoring, discarding control, or shaper has been set

up appropriately for system operation. For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

3.5.2

Failures on Using Spanning Tree

If the spanning tree function is in use and a layer 2 communication failure occurs or the spanning tree operation status

does not comply with the network configuration, isolate the problem according to the analysis method listed below. For

the multiple spanning trees, check for each CIST or MST instance. For example, read the CIST route bridge or the route

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

bridge for each MST instance for route bridge, when checking the route bridge.

Table 3-14: Spanning Tree Failure Analysis Method

Troubleshooting Steps and Command

No.

Action

Execute the show spanning-tree

command for the failed spanning tree and

check the protocol status of the spanning tree.

If shown as Enable, go to No. 2.

When tree information is not displayed while Ring Protocol and PVST+ both are

in use, go to No.7.

If shown as Disable, the spanning tree is suspended. Check the configuration.

Ring Protocol and multiple spanning tree both are used, go to No.8.

Check to see if the number of PVST+s is within the conditions of accommodation.

Execute the show spanning-tree

command for the failed spanning tree and

check the bridge identifier of the route bridge

for the spanning tree.

Go to No. 3 if the bridge identifier of the route bridge complies with the network

configuration.

Check the network configuration and configuration if the bridge identifier of the

route bridge does not comply with the network configuration.

Execute the show spanning-tree

command for the failed spanning tree and

check the port status and the port role of the

spanning tree.

Go to No. 4 if the spanning tree port status and port role comply with the network

configuration.

When the systems before Ver10.6 is used:

If the port status of the port for which the loop guard function is defined is

Blocking or Discarding, check to see if the port is a designated port. If the port is

a designated port, delete the setting of the loop guard function.

If the spanning tree port status and port role do not comply with the network

configuration, check the neighboring system status and configuration.

Execute the show spanning-tree

statistics command for the failed

spanning tree and check BPDU sending and

receiving on the failed port.

Check the BPDU sending/receiving counter.

[Root port]

Go to No. 5 if the BPDU receiving counter has been incremented.

If not so, BPDU may have been discarded by filtering, or BPDU may have

been discarded through bandwidth monitoring, discarding control, or shaper

of the QoS control. See "3.23.1 Checking Filtering/QoS Setting Information"

to check for it. If no problem is found, check the neighboring system.

[Designated port]

Go to No. 5 if the BPDU sending counter has been incremented. Otherwise,

see "3.4 Network Interface Communication Failure."

Execute the show spanning-tree

command for the failed spanning tree with

"detail" parameter specified, and check the

received BPDU bridge identifier.

Confirm that the received BPDU route bridge identifier and sending bridge

identifier comply with the network configuration. Otherwise, check the

neighboring system status.

Check to see if the maximum number of

failed spanning trees is within the

accommodating conditions.

Set up the number within the range of the accommodating conditions. For the

accommodating conditions, see "Configuration Settings."

Check to see if vlan-mapping is applied to

the single VLAN that is to operate with

PVST+.

If vlan-mapping of Ring Protocol is not applied to the target VLAN, configure it.

In addition, if multiple VLANs are applied to the vlan-mapping, review the

vlan-mapping and change it to a single VLAN.

Check to see if the vlan-mapping of VLANs

to be operated with MST instances is the

same as that of Ring Protocol.

If vlan-mapping of Ring Protocol is not applied to the target VLAN, adjust it to

match the configuration of VLANs with multiple spanning tree enabled.

3.5.3

Failures on Using Ring Protocol

This subsection describes Autonomous Extensible Ring Protocol failure.

The Autonomous Extensible Ring Protocol is redundant protocol on the layer 2 network for ring topology, refer to it as

"Ring Protocol" hereafter.

When the communication is disabled during Ring Protocol operation, follow the analysis flow to identify the symptom

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

and isolate the problem.

Figure 3-4: Analysis Flow

Analysis Flow

Any failure on node

constituting ring network or

port as ring port?

Any failure on cable

or hardware?

Any failure on software?

Execute the dump

command and collect

the failure information.

Correct the problem

on settings.

Replace the faulty

parts.

on hardware

configuration.

When the Ring Protocol is not running normally or the ring network failure is detected, isolate the problem by

following the failure analysis methods shown in the table below for all the nodes configuring the ring network.

Table 3-15: Ring Protocol Failure Analysis Method

No.

Troubleshooting Steps and

Command

Action

Execute the show axrpcommand to

Go to No. 3 if "enable" is displayed on "Oper State."

check the Ring Protocol operation state.

If "-" is displayed on "Oper State," the setting necessary for operating Ring Protocol

is not set in the configuration.

Check the configuration.

If "disable" is displayed on "Oper State," Ring Protocol is disabled. Check the

configuration.

If "Not Operating" is displayed on "Oper State," Ring Protocol is inoperative.

Check to see if any inconsistency (such as combination of operation mode, attribute

and ring port of the system is invalid) exists in configuration. Go to No. 2 if

configuration is valid. [IP8800/S6700] [IP8800/S6600] [IP8800/S6300]

Execute the show logging

command to check the normality of the

entry registration to MAC address table

as the default operation of Ring

Protocol

Go to No. 3 if the message "The MAC address entry can't be registered at hardware

tables." is not output.

If the message "The MAC address entry can't be registered at hardware tables." is

output, the entry setting for MAC address table necessary for Ring Protocol operation

is failed.

See the corresponding part in the manual "Message Log Reference" and follow

descriptions in [Action]. Also, see "4.1.2 Action to Be Taken When MAC Address

Table Resource Shortage Occurs."

[IP8800/S6700] [IP8800/S6600]

[IP8800/S6300]

Execute the show axrpcommand to

check the operation mode and attribute.

Go to No. 4 if "Mode" and "Attribute" correspond to the operation mode and attribute

of network configuration.

Otherwise, check the configuration.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and

Command

Action

Execute the show axrpcommand to

check the ring port for each VLAN

group and its operation state.

Go to No. 5 if "Ring Port" and "Role/State" correspond to the port state of network

configuration.

Otherwise, check the configuration.

Execute the show axrp detail

command to check the control VLAN

ID.

Go to No. 6 if "Control VLAN ID" corresponds to the VLAN ID of network

configuration.

Otherwise, check the configuration.

Execute the show axrp detail

command to check the VLAN ID which

belongs to the VLAN group.

Go to No. 7 if "VLAN ID" corresponds to the VLAN ID of network configuration.

Otherwise, check the configuration.

Execute the show axrp detail

command to check timer values for

transmission interval and hold time of

the health check frame.

Go to No. 8 if the timer value "Health Check Hold Time" of the health check frame

hold time is larger than the timer value "Health Check Interval" of the health check

frame transmission interval (i.e. transmission delay is considered).

Check and review the configuration if the timer value of the health check frame hold

time is equivalent or smaller than the that of health check frame transmission interval

(i.e. transmission delay is not considered).

Execute the show vlan detail

command to check the VLAN which is

used in Ring Protocol and its port state.

Go to No. 9 and 10 if there is no failure on the VLAN and its port state.

Check the configuration and restore the state if there is any failure.

Check settings of the filtering and QoS

control.

Ring Protocol control frames may have been discarded by filtering or QoS control.

See "3.23.1 Checking Filtering/QoS Setting Information" to check the setting. Also

see the manual "Configuration Guide."

Check the settings of the virtual link if

spanning tree or GSRP is used at the

same time.

Check to see if virtual link has been correctly configured for the network

configurations.

•

Check to see if the virtual link settings of devices that Ring Protocol and either one

of spanning tree or GSRP are used together are correct.

•

As for equipment in the whole ring network, confirm the VLAN used as a virtual

link belongs to the VLAN group of Ring Protocol.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.5.4

Multicast Relay by IGMP snooping Is Disabled

If multicast relay is disabled when using IGMP snooping, follow the analysis flow to identify the symptom using steps

shown in the table below and isolate the problem.

Figure 3-5: Analysis Flow

Analysis Flow

see the manual "Message Log

Reference" and perform the

actions described in [Action]

associated with each log

message.

Is there log information?

Verify that the settings of

filter and QoS Control are

correct.

Is filter setting correct?

Verify that the settings for

using IPv4 multicast at the

same time are correct.

Is IPv4 multicast used?

Set IP address on VLAN,

and add the querier

function in IGMP snooping.

Is there IGMP querier?

This system may be the

IGMP querier.

Unresolve

Is the device that relays

multicast data connected

Set the connecting port as

a multicast router port.

to the same

VLAN?

Unresolved

Is the data relayed within

the same VLAN?

Is it a relay within

the same VLAN?

Verify that the configuration of

IGMP snooping is properly set in

the corresponding VLAN.

Refer to "3.8 IPv4 Multicast

Routing Communication

Failure."

Verify that other systems

are set to relay the

multicast data.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-16: Troubleshooting on Multicast Relay

No.

Troubleshooting Steps and

Command

Action

Use the show loggingcommand to

check if any failure occurs.

Check the following:

- Check the log information for physical failures.

Check if filtering and QoS are set

correctly.

Certain packets may have been discarded by filtering, or packets may have been

discarded through bandwidth monitoring, discarding control, or shaper of the QoS

control. Check to see if the conditions of filtering and QoS control in the configuration

have been set up correctly and if bandwidth monitoring, discarding control, or shaper

has been set up appropriately for system operation.

For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

Check the settings of IPv4 multicasts if

you want to use IPv4 multicast at the

same time.

Check the following:

•

Check to see that the settings by configuration command

swrt_multicast_tableare applied to the system. [IP8800/S3600]

[IP8800/S3600] [IP8800/S6700]

[IP8800/S6600] [IP8800/S6300]

When the settings by configuration command swrt_multicast_table are

applied, "On" is indicated on "Current selected swrt_multicast_table:" by entering

the show systemcommand.

Current selected swrt_multicast_table: On

When

"Off"

indicated

after

the

configuration

command

swrt_multicast_tablehas been executed, restart the system.

•

When IPv4 multicast and IGMP snooping are used at the same time, configure IPv4

multicast in the VLAN. [IP8800/S3600]

When IPv4 multicast is used in the VLAN, "On" is indicated in "IPv4 Multicast

routing:" by entering the igmp-snoopingcommand.

IPv4 Multicast routing: On

•

When static group entry function of IPv4 multicast is used in the VLAN, set

multicast router port to the ports that are necessary for multicast communication.

When the number of entries registered in IGMP snooping exceeds the

accommodation conditions, the excess multicast relay entries of IPv4 multicast can

communicate only between multicast router ports. Therefore, set up the network

configuration so as not to exceed the registered entries of IGMP snooping.

When the registered entries of IGMP snooping exceeds the accommodation

conditions, log information is displayed in the following:

IGMP snooping: The number of the IGMP snooping entry

exceeded the capacity of this system.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and

Command

Action

Check the IGMP snooping configuration

using the show igmp-snooping

command.

Check the following:

- Check that the message below is displayed to confirm the existence of the IGMP

querier which monitors group members. [IP8800/S3600]

(1) If the IGMP querier exists, the IGMP querier IP address is displayed.

IGMP querying system: 192.168.11.20^*

(2) If the IGMP querier does not exist, nothing is displayed in "IGMP querying

system:".

IGMP querying system:

- If this system is the IGMP querier, confirm that an IP address is set for the VLAN.

(1) If an IP address is set for the VLAN, a message is displayed.

IP Address: 192.168.11.20^*

(2) If no IP address is set for the VLAN, nothing is displayed in "IP Address:".

IP Address:

- If a multicast router is connected, check mrouter-port.

> show igmp-snooping 100

Date 2005/05/15 15:20:00

VLAN 100:

IP Address:192.168.11.20

Querier : enable

IGMP querying system : 192.168.11.20

Port (2): 0/1,0/3

Mrouter-port:0/1

Group Counts: 3

Execute the show igmp-snooping

command with "group" parameter

specified, and check IPv4 multicast

group address.

Check the following:

- Confirm that the joined IPv4 multicast group address is displayed by the show

igmp-snooping groupcommand.

> show igmp-snooping group 100

Date 2005/05/15 15:20:00

VLAN 100 Group counts:3

Group Address

224.10.10.10

MAC Address

0100.5e0a.0a0a

Port-list 0/1-3

225.10.10.10

0100.5e0a.0a0a

Port-list 0/1-2

239.192.1.1

0100.5e40.1606

Port-list 0/1

* If this system is the IGMP querier, the address displayed in "IGMP querying system" matches the address displayed

in "IP Address"; however, if a different system is the IGMP querier, the address displayed in "IGMP querying system"

does not match the address displayed in "IP Address."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.5.5

Multicast Relay by MLD snooping Is Disabled

If multicast relay is disabled when using MLD snooping, follow the analysis flow to identify the symptom using steps

shown in the table below and isolate the problem.

Figure 3-6: Analysis Flow

Analysis Flow

See the manual "Message Log

Reference" and perform the

action described in [Action]

associated with each log

message.

Is there log information?

Verify that the settings of

Is filter setting correct?

filter and QoS Control are

correct.

Verify that the settings for

using IPv6 multicast at the

same time are correct.

Is IPv6 multicast used?

Set IP address on VLAN,

and add the querier

function in MLD snooping.

Is there MLD querier?

This system may be the

MLD querier.

Unresolved

Set the connecting port as

a multicast router port.

Is the device that relays

multicast data connected

to the same

VLAN?

Is it a relay within

the same VLAN?

Unresolved

Is the data relayed

within the same

VLAN?

Refer to "3.11 IPv6 Multicast

Routing Communication

Failure."

Verify that other devices

are set to relay the

multicast data.

Verify that the MLD snooping

configuration is properly set up in

the corresponding VLAN.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-17: Troubleshooting on Multicast Relay

No.

Troubleshooting Steps and

Command

Action

Use the show loggingcommand to

check if any failure occurs.

Check the log information for physical failures.

Check if filtering and QoS are set

correctly.

Certain packets may have been discarded by filtering, or packets may have been

discarded through bandwidth monitoring, discarding control, or shaper of the QoS

control. Check to see if the conditions of filtering and QoS control in the configuration

have been set up correctly and if bandwidth monitoring, discarding control, or shaper

has been set up appropriately for system operation.

For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

Check the settings of IPv6 multicasts if

you want to use IPv6 multicast at the

same time.

Check the following:

•

Check to see that the settings by configuration command are applied to the system

[IP8800/S3600]

[IP8800/S3600] [IP8800/S6700]

[IP8800/S6600] [IP8800/S6300]

When the settings by configuration command swrt_multicast_table are

applied, "On" is indicated on "Current selected swrt_multicast_table:" by entering

the show systemcommand.

Current selected swrt_multicast_table: On

When

"Off"

indicated

after

the

configuration

command

swrt_multicast_tablehas been executed, restart the system.

•

When IPv6 multicast and MLD snooping are used at the same time, configure IPv4

multicast in the VLAN. [IP8800/S3600]

When IPv6 multicast is used in the VLAN, "On" is displayed in "IPv4 Multicast

routing:" by entering the igmp-snoopingcommand.

IPv6 Multicast routing: On

•

When static group entry function of IPv6 multicast is used in the VLAN, set

multicast router port to the ports that are necessary for multicast communication.

When the number of entries registered in MLD snooping exceeds the

accommodation conditions, the excess multicast relay entries of IPv6 multicast can

communicate only between multicast router ports. Therefore, set up network

configuration so as not to exceed the registered entries of MLD snooping.

When the registered entries of MLD snooping exceeds the accommodation

conditions, log information is displayed in the following:

MLD snooping: The number of the MLD snooping entry

exceeded the capacity of this system.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and

Command

Action

Check the MLD snooping configuration

using the show mld-snooping

command.

Check the following:

- Check that the message below is displayed to confirm the existence of the MLD

querier which monitors group members.

(1) If the MLD querier exists, the MLD querier IP address is displayed.

MLD querying system: fe80::200:87ff:fe10:1959*

(2) If the MLD querier does not exist, nothing is displayed in "MLD querying system:".

MLD querying system:

- If this system is the MLD querier, confirm that an IP address is set for the VLAN.

(1) If an IP address is set for the VLAN, the following message is displayed.

IP Address: fe80::200:87ff:fe10:1959*

(2) If no IP address is set for the VLAN, nothing is displayed in "IP Address:".

IP Address:

- If a multicast router is connected, check mrouter-port.

>show mld-snooping 100

Date 2005/05/15 15:20:00

VLAN 100:

IP Address:fe80::200:87ff:fe10:1959 Querier : enable

MLD querying system: fe80::200:87ff:fe10:1959

Port(2): 0/1,0/3

Mrouter-port: 0/1

Group Count :3

Execute the show mld-snooping

command with "group" parameter

specified, and check IPv6 multicast

group address.

Check the following:

- Confirm that the joined IPv6 multicast group address is displayed by the show

mld-snooping groupcommand.

> show mld-snooping group 100

Date 2005/05/15 15:20:00

VLAN 100 Group count:2

Group Address

MAC Address

ff0e::0e0a:0a01 3333.0e0a.0a01

Port-list 0/1-3

ff0e::0102:0c11 3333.0102.0c11

Port-list 0/1-2

* If this system is the MLD querier, the address displayed in "MLD querying system" matches the address displayed in

"IP Address"; however, if a different system is the MLD querier, the address displayed in "MLD querying system" does

not match the address displayed in "IP Address."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.6 IPv4 Network Communication Failure

3.6.1

Communication Is Disabled or Is Disconnected

There are three possible causes that result in communication failure on the IPv4 network using this system.

1. Configuration on IP communication has changed

2. Network configuration has changed

3. Network component failures

For 1 and 2 above, check for the differences in the configuration and network configuration provided before and after

the change. Check for any difference disabling communication.

This section describes procedure to identify the failed part and to isolate the problem, mainly for the cases of "IP

communication is disabled although the configuration and network configuration are correct." and "IP communication

had been normally running but it is disabled now." as in above case 3.

To locate the faulty part and cause, follow the flow below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Figure 3-7: Failure Analysis Procedure When IPv4 Communication Disabled

Verify if there is a line failure log message.

A line failure log message exists.

No line failure log message exists.

See the manual"Message Log Reference"and

perform the action described in [Action]

associated with each log message.

Check the Up/Down status of the interface.

VRF interface is not displayed

Confirm Option License OP-NPAR.

down

Go to "3.4 Network Interface Communication

Failure."

Identify the extent of the failure using the ping

command.

Communication between the neighboring host and router is disabled.

Verify the status of address resolution using the show ip arp command.

Communication

between remote

host and router is

disabled.

Solved

Unresolved

Verify the route information using the

show ip route command.

Verify the IP network of remote system.

Otherwise, go to "3.4 Network Interface

No route information

exists or the next hop

address is invalid.

The route

information exists.

Go to "3.6.2 IP Addresses Cannot Be Assigned

Using DHCP Function" and "3.23.1 Checking

Filtering/QoS Setting Information."

Go to "3.7 IPv4 Unicast Routing Communication

Failure"

(1) Checking log

Communication may be interrupted by a line failure (or damage). The following procedure displays hardware error

messages among this system's log messages.

For details about the log, see the manual "Message Log Reference."

1. Log in to the system.

2. Display the log using the show loggingcommand.

3. The date and time when an error occurred are displayed in the log. Check to see if a log was displayed at the date/

time when communication was disabled.

4. For detailed information about the failure in the log displayed at the time and date of the communication interruption

and the actions for failures, see the manual "Message Log Reference." Follow the instruction.

5. If there is no log recorded at the time and date when communication was disabled, go to "(2)Checking interface

status."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

(2) Checking interface status

It is also possible that a failure has occurred on the hardware of the neighboring system connected to this system even if

the hardware on this system is running properly.

The procedure for checking the status of interface between this system and the neighboring system is described below.

1. Log in to the system.

2. Check the Up/Down status of the interface between the systems using the show ip interfacecommand.

3. When the interface is not displayed as VRF interface, see "(9)Checking option license OP-N P A R [OP-NPAR]."

[OP-NPAR]

4. If the interface is in the "Down" status, see "3.4 Network Interface Communication Failure."

5. If the interface is in the "Up" status, go to "(3)Identifying the extent of the failure (performed from this system)"

(3) Identifying the extent of the failure (performed from this system)

If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote

system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:

1. Log in to the system.

2. Use the pingcommand to check communication between both parties. For an example of issuing pingand how

to interpret the result, see the manual "Configuration Settings."

3. If communication to the other party cannot be verified with the pingcommand, use the pingcommand to check

communication to remote systems starting from the system closest to this system.

4. If the result of the pingcommand shows that the neighboring system has failed, go to "(5)Checking ARP resolution

information with neighboring system." If the result shows that the remote system has failed, go to "(6)Checking

unicast routing information."

(4) Identifying the extent of failure (performed from the customer's terminal equipment)

If login to this system is not possible, follow the procedure below to identify the extent of failure to see the failure

location in the route between the customer's terminal equipment and the other party.

1. Confirm that the customer's terminal equipment has the ping function.

2. Use the ping function to check communication between the customer's terminal equipment and the remote system.

3. If communication to the remote system cannot be verified with the pingcommand, use pingagain to check

communication to systems starting from the system closest to the customer's terminal equipment.

4. After the extent of failure has been identified using the ping command, log in to this system if it is considered to have

failed and follow the failure analysis flow to check for the failure cause.

(5) Checking ARP resolution information with neighboring system

If communication to a neighboring system is not possible as a result of the pingcommand execution, address

resolution by ARP may not have been achieved. The procedure for checking the status of address resolution between

this system and the neighboring system is described below.

1. Log in to the system.

2. Use the show ip arpcommand to check the status of address resolution status with the neighboring system

(presence/ absence of ARP entry information).

3. If the address resolution with the neighboring system is achieved (ARP entry information is provided), go to

"(6)Checking unicast routing information."

4. Confirm that the IP network setting on the neighboring system matches that of this system if the address resolution

with the neighboring system is not achieved (ARP entry information is not provided).

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

(6) Checking unicast routing information

Check the route information acquired by this system if communication is not possible even when the address resolution

with the neighboring system is achieved, or if communication is disabled in the midway to the other party during IPv4

unicast communication, or if the route to the other party is abnormal. Use the following procedure:

1. Log in to the system.

2. Execute the show ip route command to check the route information acquired by this system.

3. For IP8800/S6700, IP8800/S6600, and IP8800/S6300, check to see if packets are discarded because of the Null

interface. If the route information sending interface resulting a communication failure is null0, packets are discarded

because of the Null interface. Review the setting conditions for the static routing function in the configuration.

4. Go to "3.7 IPv4 Unicast Routing Communication Failure" if the route information on the failed interface is missing

in the route information acquired by this system or if the next hop address is invalid.

5. If the route information acquired by this system contains the route information on the failed interface, the following

functions set for the interface may have problem. Check these functions.

• DHCP/BOOTP function

Go to "(7)Checking DHCP/BOOTP setting information."

• Filtering/QoS function

Go to "(8)Checking filtering/QoS setting information."

(7) Checking DHCP/BOOTP setting information

When the relay function or the server function of DHCP/BOOTP on this system provides IP addresses to the

neighboring system, there is possibility that IP addresses are not correctly assigned to the neighboring system.

Check to see the settings of the relay function or the server function. For the procedure, see "3.23.1 Checking Filtering/

QoS Setting Information."

(8) Checking filtering/QoS setting information

Certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth

monitoring, discarding control, or shaper of the QoS control. Review if the conditions of filtering and QoS control in

the configuration have been set up correctly and if bandwidth monitoring, discarding control, or shaper has been set up

appropriately for system operation. For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

(9) Checking option license OP-NPAR [OP-NPAR]

If no information is displayed by the show ip interfacecommand though the interface is set to VRF interface

and configured, there is possibility that option license OP-NPAR is unregistered or invalid. Check the status of option

license on this system by using the show licensecommand.

1. Log in to the system.

2. Check to see the license software and the enabled options by using the show licensecommand.

3. If OP-NPAR does not appear in the license software, it indicates any license key for OP-NPAR has not been

registered yet. Register the license key for OP-NPAR.

4. When OP-NAPR is displayed in license software but it is not displayed as an enabled option, the hardware

configuration of this system might not support OP-NPAR. Review the hardware configuration. For more information

about the hardware configuration, see the manual "Configuration Settings, Vol. 1."

5. When this system hardware configuration supports OP-NPAR but the OP-NPAR is not displayed as an enabled

option, use the reloadcommand to restart the system, which will enable the option license.

6. When OP-NPAR appears as an enabled option, see step 4 or later in "(2)Checking interface status."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.6.2

IP Addresses Cannot Be Assigned Using DHCP Function

(1) DHCP/BOOTP relay communication failure

There are three possible causes for DHCP/BOOTP relay communication failures:

1. Configuration relating to DHCP/BOOTP relay has changed

2. Network configuration has changed

3. DHCP/BOOTP server failures

For 2 above, check for the differences in the network configuration provided before and after the change. Check for any

difference disabling communication.

Assuming that client settings (network card setting, cable connection, etc.) have been verified, this section describes the

procedure for locating the faulty part and cause in the cases described such as "IP addresses are not assigned from the

DHCP/BOOTP server as a result of changing the configuration." and "Although the configuration and network

configuration are correct, IP addresses are not assigned and IP communication is disabled" as in above No. 1 and 3.

To locate the faulty part and cause, follow the flow below.

Figure 3-8: Troubleshooting on DHCP/BOOTP Relay

< IP addresses cannot be assigned to clients.>

Verify if there is a failure occurrence using the show logging command or the show ip

interface command.

No failure

exists.

A failure exists.

See the manuals "Message Log

Reference" and "3.6.1 Communication Is

Disabled or Is Disconnected" and perform

the actions described in [Action]

Identify the extent of failure using the

ping command.

associated with each log message.

Communication between

the neighboring host and

router is disabled.

Communication between

remote host and router is

disabled.

The route

information

exists.

Solved

Verify the status of address

resolution using the show ip arp

command.

Verify the route information using

the show ip route command.

No route

information

exists.

The next-hop

address is invalid.

Unresolved

Verify the IP network of remote

system. Otherwise, go to

"3.4 Network Interface

Analyze the failure on each

routing protocol.

(RIP, BGP, etc.)

Verify the setting

information of DHCP and

BOOTP.

Verify the setting

information of filter and

QoS.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

(a) Checking the log and interface

On possible cause for the server not assigning IP addresses to clients, communication between client and server may

have been disabled. Check the log displayed on this system or the interface up/down status using the show ip

interfacecommand. For the procedure, see "3.6.1 Communication Is Disabled or Is Disconnected."

(b) Identifying the extent of the failure (performed from this system)

If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote

system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:

1. Log in to the system.

2. Use the pingcommand to check communication between both parties. For an example of issuing pingand how

to interpret the result, see the manual "Configuration Settings."

3. If communication to the other party cannot be verified with the pingcommand, use the pingcommand to check

communication to remote systems starting from the system closest to this system.

4. If the result of the pingcommand shows that the neighboring system has failed, go to "(d)Checking ARP resolution

information with neighboring system." If the result shows that the remote system has failed, go to "(e)Checking route

information."

If login to this system is not possible, follow the procedure below to identify the extent of failure to see the failure

location in the route between the customer's terminal equipment and the other party.

1. Confirm that the customer's terminal equipment has the ping function.

2. Use the ping function to check communication between the customer's terminal equipment and the remote system.

3. If communication to the remote system cannot be verified with the pingcommand, use pingagain to check

communication to systems starting from the system closest to the customer's terminal equipment.

4. After the extent of failure has been identified using the pingcommand, log in to this system if it is considered to

have failed and follow the failure analysis flow to check for the failure cause.

(d) Checking ARP resolution information with neighboring system

If communication with a neighboring system is not possible as a result of pingexecution, address resolution by ARP

may not have been achieved. The procedure for checking the status of address resolution between this system and the

neighboring system is described below.

1. Log in to the system.

2. Use the show ip arpcommand to check the status of address resolution status with the neighboring system

(presence/ absence of ARP entry information).

3. If the address resolution with the neighboring system is achieved (ARP entry information is provided), go to

"(e)Checking route information."

4. Confirm that the IP network setting can be exchanged between the neighboring system and this system if the address

resolution with the neighboring system is not achieved (ARP entry information is not provided).

(e) Checking route information

Check the route information acquired by this system if the following happens: Communication is not possible even

when the address resolution with the neighboring system is achieved, communication is disabled in the midway to the

other party, or the route to the other party is abnormal.

Take the following procedure.

1. Log in to the system.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

2. Execute the show ip routecommand to check the route information acquired by this system.

3. Go to "3.7 IPv4 Unicast Routing Communication Failure" if the route information on the failed interface is missing

in the route information acquired by this system or if the next hop address is invalid.

4. If the route information acquired by this system contains the route information on the failed interface, the following

functions set for the interface may have problem. Check these functions.

• Filtering/QoS function

Go to "(f)Checking filtering/QoS setting information."

• DHCP/BOOTP function

Go to "(g)Checking DHCP/BOOTP setting information."

(f) Checking filtering/QoS setting information

It may have been set to discard only certain packets by filtering, or packets may have been discarded through

bandwidth monitoring, discarding control, or shaper of the QoS control.

Check to see if the conditions of filtering and QoS control in the configuration have been set up correctly and if

bandwidth monitoring, discarding control, or shaper has been set up appropriately for system operation. For the

procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

(g) Checking DHCP/BOOTP setting information

If there are sufficient lease IP addresses remaining in the DHCP/BOOTP server, IP addresses may not be assigned to

clients due to configuration setting errors for the DHCP/BOOTP relay. The followings are the steps to check the

configuration:

1. Confirm that the IP address of the DHCP/BOOTP server or that of a neighboring router with the DHCP/BOOTP

relay agent function has been assigned for ip helper-address.

2. Confirm that iphelper-addresshas been assigned for the client interface.

3. Confirm that ipbootp-hopsis set to a correct "bootp hops" value for the client.

4. For multi-homed configuration, confirm that the "ip relay-agent-address" value matches the IP address subnet

distributed by the DHCP/BOOTP server.

(h) Checking when the DCCP relay and VRRP are operated on the same interface

If the DHCP/BOOTP relay and VRRP are operated on the same interface, the DHCP/BOOTP client gateway address

(router option) must be set to the virtual router address specified in the VRRP configuration on the DHCP/BOOTP

server. Otherwise, communication of the DHCP/BOOTP client may be disabled after master/standby router switching

by VRRP. Follow the checking method for each DHCP/BOOTP server.

(2) DHCP server communication trouble

The following are three possible causes for DHCP server communication failures (address not distributed to clients).

1. Configuration error

2. Network configuration has changed

3. DHCP server failure

First, check 1 above. This section describes configurations that are easily misconfigured. For 2 above, check for the

differences in the network configuration provided before and after the change. Check for any difference disabling

communication. If the configuration and network configuration are correct but IP communications are unavailable

because IP addresses cannot be assigned to clients, described in 3 above, see "(b)Checking the log message and

interface" through "(e)Checking filtering/QoS setting information" for details.

To locate the failed part and cause, follow the flow below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Figure 3-9: DHCP Server Failure Analysis Procedure

Check the configuration.

Verify the failure occurrence using the show logging

command and the show ip interface command.

No failure on this

system

(Connected directly)(

No failure on this system

(Connected via relay

agent)

A failure occurred on

this system

Refer to

"(1)DHCP/BOOTP relay communication failure."

see the manuals "Message Log

Reference" and "3.6.1 Communication Is

Disabled or Is Disconnected" and

Verify the setting information of filter

and QoS.

perform the actions described in [Action]

associated with each log message.

(a) Checking configuration

IP addresses may not be assigned to clients due to configuration setting errors for resources on the DHCP server. The

followings are the steps to check the configuration:

1. Confirm that the configuration has the "ip dhcp pool" setting including the network setup of the IP address to be

assigned to DHCP clients.

2. Using configuration command ip dhcp excluded-address, confirm that the number of pooled IP addresses

in the configuration to be assigned to the DHCP clients is not fewer than the number of clients to be used

concurrently.

3. If communication between a client and another system is disabled after an address is assigned by this system to the

client, the default router may not have been set. Execute configuration command default-routerto confirm

that the router address (default router) of the network to which the client is connected has been set up (see the manual

"Configuration Commands").

4. Check the setting of the system as the DHCP relay agent. If this system is also used as the relay agent, see "(1)DHCP/

BOOTP relay communication failure."

(b) Checking the log message and interface

On possible cause for the server not assigning IP addresses to clients, the communication client between cliant and

server may have been disabled. Check the log message displayed on this system or the interface up/down status using

the show ip interfacecommand. For the procedure, see "3.6.1 Communication Is Disabled or Is Disconnected."

If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote

system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:

1. Log in to the system.

2. If a router is provided between the server and the client, use the pingcommand to verify communication of the

system (router) between the server and the other system (DHCP client) to which communication is disabled. If

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

communication to the other party cannot be verified with the pingcommand, use pingto check communication

toward clients starting from the system closest to this system. For an example of issuing pingand how to interpret

the result, see the manual "Configuration Settings."

3. If the server and the client are directly connected, check the HUB and cable connections.

4. Depending on the extent of failure detected by the pingcommand, that is the neighboring system or remote system,

proceed to the next step in the failure analysis flow.

(d) Checking route information

Check the route information acquired by this system if communication is not possible even when the address resolution

with the neighboring system is achieved, or if communication is disabled in the midway to the other party, or if the

route to the other party is abnormal. Use the following procedure:

1. Log in to the system.

2. Execute the show ip route command to check the route information acquired by this system.

(e) Checking filtering/QoS setting information

Only certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth

monitoring, discarding control, or shaper of the QoS control.

Check to see if the conditions of filtering and QoS control in the configuration have been set up correctly and if

bandwidth monitoring, discarding control, or shaper has been set up appropriately for system operation in system

configuration, on this system and on the relay equipment located between the client and server. For the procedure, see

"3.23.1 Checking Filtering/QoS Setting Information."

(f) Checking layer 2 network

If no setting error or failure is found in steps (a) to (e), the layer 2 network may have problem. Check the layer 2

network, referring to "3.5 Layer 2 Network Communication Failure"

3.6.3

DynamicDNS Cooperation in DHCP Function Is Disabled

(1) DHCP server communication trouble

Following are three possible causes for DHCP server communication failures.

1. Configuration error

2. Network configuration has changed

3. DHCP server failure

First, check 1 above. This section describes configurations that are easily misconfigured. For 2 above, check for the

differences in the network configuration provided before and after the change. Check for any difference disabling

communication. If the DNS server/DHCP server settings (network card setting, cable connection, etc.) have been

confirmed to be normal, and if the configuration and network configuration are correct but IP communications are

unavailable because IP addresses cannot be assigned to clients, as described in 3 above, see "(b)Checking time

information" through "(f)Checking filtering/QoS setting information" for details.

To locate the failed part and cause, follow the flow below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Figure 3-10: Troubleshooting for DHCP Server Failure with DNS Cooperation

Check the configuration.

Verify if there is a failure occurrence using the show logging

command and the show ip interface command.

No failure on this

system

(Connected directly)

No failure on this system

(Multiple devices exist

between DNS server and

DHCP server.)

A failure occurred on

this system

Verify the failure occurrence on other devices.

No failure on other devices

See the manuals "Message Log Reference"

and "3.6.1 Communication Is Disabled or Is

Disconnected" and perform the actions

described in [Action] associated with each log

message.

Verify the setting information of filter

and QoS.

(a) Checking configuration

This failure may be caused by the incorrect DNS update on Dynamic DNS due to the DHCP server errors or the conflict

with the settings on the DNS server. The followings are the steps to check the configuration:

1. First, check the method for permitting DNS update on the DNS server. For access permission with an IP address/

network, see No. 3 and later. For permission with an authentication key, see No. 2 and later.

2. Confirm that the key information and authentication key specified on the DNS server are equivalent to the key

information set in the DHCP server configuration (see the manual "Configuration Commands").

3. Confirm that the zone information specified on the DNS server is equivalent to the zone information in the DHCP

server configuration (see the manual "Configuration Commands"). In this case, confirm that both forward lookup

and reverse lookup are set.

4. Confirm that DNS update is defined (see the manual "Configuration Commands"). Since the DNS update is disabled

by default, this setting is required to update DNS.

5. Confirm that the domain name used by the client matches the domain name registered on the DNS server. When

distributing the domain name by DHCP, confirm that it is correctly set in the configuration (see "Configuration

Commands" and "Operation Commands").

(b) Checking time information

When the authentication key is being used for DNS update, the difference in time between this system and the DNS

server should be within 5 minutes as the UTC time in most cases. Use the show clock command to check the time

information on this system and synchronize the time information referring to "Configuration Commands" and

"Operation Commands," as required.

As one of the causes for disabled communication to the DNS server, communication between the DNS server and

DHCP server has been disabled. Check the log message displayed on this system or the interface up/down status using

the show ip interfacecommand. For the procedure, see "3.6.1 Communication Is Disabled or Is Disconnected."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

(d) Identifying the extent of the failure (performed from this system)

If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote

system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:

1. Log in to the system.

2. If a router is provided between the DNS server and DHCP server, use the pingcommand to verify communication

of the system (router) between the DHCP server and the other system (DNS server) to which communication is

disabled. If communication to the other party cannot be verified with the pingcommand, use pingto check

communication toward clients starting from the system closest to this system. For an example of issuing ping and

how to interpret the result, see the manual "Configuration Settings."

3. If the DNS server and DHCP server are directly connected, check the HUB and cable connections.

4. Depending on the extent of failure detected by the pingcommand, that is the neighboring system or remote system,

proceed to the next step in the failure analysis flow.

(e) Checking route information

Check the route information acquired by this system if communication is not possible even when the address resolution

with the neighboring system is achieved, or if communication is disabled in the midway to the other party, or if the

route to the other party is abnormal. Use the following procedure:

1. Log in to the system.

2. Execute the show ip routecommand to check the route information acquired by this system.

(f) Checking filtering/QoS setting information

Only certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth

monitoring, discarding control, or shaper of the QoS control.

Check to see if the conditions of filtering and QoS control in the configuration have been set up correctly and if

bandwidth monitoring, discarding control, or shaper has been set up appropriately for system operation in system

configuration, on this system and on the relay equipment located between the DNS server and DHCP server. For the

procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

(g) Checking layer 2 network

If no setting error or failure is found in steps (a) to (f), the layer 2 network may have problem. Check the layer 2

network, referring to "3.5 Layer 2 Network Communication Failure."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.7 IPv4 Unicast Routing Communication Failure

3.7.1

No RIP Routing Information Exists

Isolate the problem according to the failure analysis method listed below if RIP route information does not exist in the

displayed route information acquired by this system.

Besides, when the upper limit of routing is set by configuration command maximum routes, see "3.7.4 No Routing

Information Exist [OP-NPAR]." [OP-NPAR]

Table 3-18: RIP Failure Analysis Method

No.

Troubleshooting Steps and Command

Action

RIP neighboring information is displayed.

show ip rip neighbor

Go to No. 2 if the interface of a neighboring router is not displayed.

Go to No. 3 if the interface of a neighboring router is displayed.

Go to No. 3 if the configuration is correct.

Check to see if the RIP setting is correct in the

configuration.

Correct the configuration if it is not correct.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the RIP route.

Correct the configuration if it is not correct.

3.7.2

No OSPF Routing Information Exists

Isolate the problem according to the failure analysis method listed below if OSPF route information does not exist in

the displayed route information acquired by this system.

Besides, when the upper limit of routing is set by configuration command maximum routes, see "3.7.4 No Routing

Information Exist [OP-NPAR]." [OP-NPAR]

Table 3-19: OSPF Failure Analysis Method

No.

Troubleshooting Steps and Command

Action

Check the interface status of OSPF.

Go to No. 3 if the interface status is DR.

showipospfinterface<IP Address>

Go to No. 2 if the interface status is BackupDR or DR Other.

Execute the command again after a certain period if the interface status is

"Waiting." Go to No. 1.

Check the status of a neighboring router of DR

from Neighbor List.

Go to No. 4 if the status of the neighboring router of DR is other than Full.

Go to No. 5 if the status of the neighboring router of DR is Full.

Go to No. 4 if the status of some neighboring routers is other than Full.

Go to No. 5 if the status of all neighboring routers is Full.

Go to No. 5 if the configuration is correct.

Check the status of all neighboring routers from

Neighbor List.

Check to see if the OSPF setting is correct in

configuration.

Correct the configuration if it is not correct.

Check the OSPF routes that have been learned.

Go to No. 6 if the route is set to "InActive."

show ip route all-routes

If no route exists, check to see if the neighboring router advertises the OSPF

route.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the OSPF route.

Correct the configuration if it is not correct.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.7.3

No BGP4 Routing Information Exists

Isolate the problem according to the failure analysis method listed below if BGP4 route information does not exist in

the displayed route information acquired by this system.

Besides, when the upper limit of routing is set by configuration command mazimum routes, see "3.7.4 No Routing

Information Exist [OP-NPAR]." [OP-NPAR]

Table 3-20: BGP4 Failure Analysis Method

No.

Troubleshooting Steps and Command

Action

Check the BGP4 peer status.

show ip bgp neighbors

Go to No. 2 if the peer status is other than Established.

Go to No. 3 if the peer status is Established.

Go to No. 3 if the configuration is correct.

Correct the configuration if it is not correct.

Go to No. 4 if the route does not exist.

Check to see if the BGP4 setting is correct in

configuration.

Check to see if the BGP4 route is learned.

show ip bgp received-routes

If the route exists, execute the show ip routecommand to confirm the

learned route is active.

Check to see if the routing information exists to

solve the next hop address.

show ip route

If routing information exists to solve the next hop address, go to No.5.

If no routing information exist to solve the next hop address, perform protocol

fault analysis to learn the routing information.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the BGP4 route.

Correct the configuration if it is not correct.

3.7.4

No Routing Information Exist [OP-NPAR]

If no routing information for each protocol exist in the information this system acquired, isolate the cause according to

the failure analysis method below.

Table 3-21: VRF Failure Analysis Method

No.

Troubleshooting Steps and Command

Action

Check to see if the number of routes in VRF

exceeds the upper limit configured.

show ip vrf

If the number of routes exceeds the upper limit, go to No.2.

The number of routes is less than upper limit, perform protocol failure

analysis against protocols that no routing information exists.

RIP: "3.7.1 No RIP Routing Information Exists"

OSPF: "3.7.2 No OSPF Routing Information Exists"

BGP4: "3.7.3 No BGP4 Routing Information Exists"

Check to see the value set in the upper limit for

the number of routes in VRF in the

configuration.

Increase the upper limit or aggregate the routing in order to decrease the

routing number.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.8 IPv4 Multicast Routing Communication Failure

Actions to be taken if IPv4 multicast communication failures occur on this system are described below.

3.8.1

Communication on IPv4 PIM-SM Network Is Disabled

If multicast relay is disabled in the IPv4 PIN-SM network configuration, isolate the cause according to the failure

analysis method below.

The figure below illustrates a network example of IPv4 PIM-SM.

Figure 3-11: Example of IPv4 PIM-SM Network

Multicast

receiver

BSR and rendezvous point

router

Participation in

the IGMP group

Multicast

sender

first-hop-router

last-hop-router

Multicast

data

Participation in

the IGMP group

Multicast

sender

Note

• BSR: This router delivers rendezvous point information (for details, see the manual "Configuration Settings").

• Rendezvous point router: This router relays the packets, for which the relay destination is not determined, toward

the multicast receiver (for details, see the manual "Configuration Settings").

• first-hop-router: This router is directly connected to the multicast sender.

• last-hop-router: This router is directly connected to the multicast receiver.

(1) Common check items

The table below shows the common check items for all system in the IPv4 PIM-SM network configuration.

Table 3-22: Common Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that the use of multicast function is designated (ip

multicast routing) in the configuration.

show running-config

If the use of multicast function is not designated, correct the

configuration.

Confirm that PIM is running on one or more interfaces.

show ip pim interface

If PIM is not running, check the configuration. Set PIM to run

on one or more interfaces. If the interface set in the

configuration to run PIM is not displayed by the show ip

pim interfacecommand, confirm that multi-homing is

not set on the interface.

Check to see if IGMP snooping is applied to the interfaces

with PIM enabled.

show igmp-snooping

If IGMP snooping is applied, confirm the following:

•

Confirm the port to which the neighboring router connected

is set as multicast router port of IGMP snooping.

Disabled."

•

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Confirm in the configuration that suppression of protocol

packet and multicast packet relay through filtering, etc. is not

provided on the interface that allows PIM and IGMP to run.

show running-config

If suppression of protocol packet and multicast packet relay is

provided, correct the configuration.

Check the PIM neighboring information.

If the neighboring router is not displayed, check the following:

show ip pim neighbor

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ip pim

interfacecommand.

•

Verify the settings of the neighboring router.

Check to see if the unicast route to the multicast data sender

exists.

show ip route

If the unicast route does not exist, see "3.7 IPv4 Unicast

Confirm that PIM is running on the interface to the next hop

address for the multicast data sender.

show ip pim interface

If PIM is not running, check the configuration. Set PIM to run

on the interface connected to the next hop address for the

multicast data sender.

Confirm that the PIM-SSM group addresses do not contain the If the PIM-SSM group addresses contain the relay target group

relay target group address, referring to the configuration.

show running-config

address, correct the configuration.

Confirm that BSR is determined. However, this confirmation

is not required if the rendezvous point for the relay target

group address is a static rendezvous point.

show ip pim bsr

If BSR is not determined, check to see if the unicast route to

BSR exists. If the unicast route does not exist, see "3.7 IPv4

Unicast Routing Communication Failure."

If the unicast route exists, check the BSR setting. If the BSR is

this system, see "(2)BSR check items."

Confirm that the rendezvous point is determined.

show ip pim rp-mapping

If the rendezvous point is not determined, check to see if the

unicast route to the rendezvous point exists. If the unicast

route does not exist, see "3.7 IPv4 Unicast Routing

If the unicast route exists, check the rendezvous point setting.

If the rendezvous point is this system, see "(3)Rendezvous

point router check items."

Confirm that the rendezvous point group addresses contain the

relay target group address.

show ip pim rp-mapping

If the relay target group address is not contained, check the

rendezvous point setting. If the rendezvous point is this

system, see "(3)Rendezvous point router check items."

Confirm that the multicast relay entry exists.

show ip mcache

If the multicast relay entry does not exist, confirm that

multicast data has arrived at the upstream port. If multicast

data has not arrived, check the setting of the multicast sender

or upstream router.

Confirm that the multicast relay routing information exists.

show ip mroute

If the multicast routing information does not exist, check the

setting of the downstream router.

Check to see if multicast routing information or multicast

forwarding entry exceeds the upper limit.

Multicast routing information:

show ip mroute

When warning is output, confirm that unexpected multicast

routing information or unexpected multicast forwarding entry

has not been created. If much of the negative cache exists in

multicast forwarding entry, confirm that there is no terminal

transmitting unnecessary packets.

Multicast forwarding entry:

show ip mcache

netstat multicast

(2) BSR check items

The table below shows the items to be checked when this system is BSR in the IPv4 PIM-SM network configuration.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-23: BSR Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is a candidate for BSR.

show ip pim bsr

If this system is not a candidate for BSR, check the

configuration and set the configuration to run this system as a

candidate for BSR. Since this system does not run as a

candidate for BSR if no address is set for the loopback

interface, confirm that an address is set for the loopback

interface.

Confirm that this system is BSR.

show ip pim bsr

If this system is not BSR, check the priority of other BSR

candidates. The larger the value, the higher the priority. If the

same priority is provided, the BSR candidate with the largest

BSR address becomes BSR.

(3) Rendezvous point router check items

The table below shows the items to be checked when this system is the rendezvous point router in the IPv4 PIM-SM

network configuration.

Table 3-24: Rendezvous Point Router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is a candidate of rendezvous point for

the relay target group address.

show ip pim rp-mapping

If this system is not a candidate of rendezvous point for the

relay target group address, check the configuration and set the

configuration to run this system as a candidate of rendezvous

point for the relay target group address. Since this system does

not run as a candidate of rendezvous point if no address is set

for the loopback interface, confirm that an address is set for

the loopback interface.

Confirm that this system is the rendezvous point for the relay

target group address.

show ip pim rp-hash<Group Address>

If this system is not the rendezvous point, check the priority of

other candidates of rendezvous point. The smaller the value,

the higher the priority. If the priority of another candidate of

rendezvous point is higher, this system does not run as the

rendezvous point. If the same priority is provided, the

rendezvous point is distributed for each group address

according to the protocol specifications and this system may

not run as the rendezvous point. To run this system

preferentially as the rendezvous point, set the priority higher

than those of other rendezvous point candidates.

(4) last-hop-router check items

The table below shows the items to be checked when this system is the last-hop-router in the IPv4 PIM-SM network

configuration.

Table 3-25: last-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that IGMP is running on the interface connected to

the multicast receiver.

If IGMP is not running, check the configuration and set the

configuration to run IGMP.

show ip igmp interface

Confirm that the multicast receiver participates in the relay

target group via IGMP.

show ip igmp group

If the multicast receiver does not participate in the relay target

group, check the setting of the multicast receiver.

If there is an interface in which the relay target group

participates, confirm that this system is DR.

show ip pim interface

If this system is not DR, check DR of the relay target interface.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Check to see if IGMP snooping is set to the port in which static

group join function is working.

When IGMP snooping is set, confirm the following:

•

Confirm that relay port is set as multicast port for IGMP

show igmp-snooping

snooping

•

Disabled."

Confirm that no interface in abnormal state is detected.

show ip igmp interface

See notices and confirm that warning information is not

output. When warning information is output, check the

following:

•

L: The number of join request exceeded the maximum

number expected. Check to see the number of connected

users.

•

Q: The IGMP version of neighboring router is different.

Adjust it to the same IGMP version.

R: A user who transmitted reports unreceivable at the

present settings exists. Change the IGMP version of this

system or confirm the settings of the participant.

S: Some of the participant information are being discarded

because the number of source exceeded the upper limit

defined to store source per message in IGMPv3. Check the

settings of the participant.

•

(5) first-hop-router check items

The table below shows the items to be checked when this system is the first-hop-router in the IPv4 PIM-SM network

configuration.

Table 3-26: first-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is directly connected to the multicast

sender.

If not, check the network configuration.

Confirm that PIM or IGMP is running on the interface

connected to the multicast sender.

show ip pim interface

If PIM or IGMP is not running, check the configuration and

set the configuration to run PIM or IGMP.

show ip igmp interface

Confirm that the multicast relay routing information exists.

show ip mroute

If the multicast routing information does not exist, confirm

that multicast data source address is the network address of

the interface directly connected to the multicast sender.

3.8.2

Multicast Data Is Double-relayed on IPv4 PIM-SM Network

If multicast data is double-relayed in the IPv4 PIM-SM network configuration, check the settings of each router and set

the configuration to run PIM on the interface for a network having multiple routers.

If double-relay still continues, check the following:

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-27: Check Items When Double-relay Continues

Troubleshooting Steps and Command

No.

Action

Check the PIM neighboring information on the interface of the

network having multiple routers.

If the neighboring router is not displayed, check the

following:

show ip pim neighbor

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ip pim

interfacecommand.

•

Confirm in the configuration that suppression of protocol

packet relay by filtering, etc. is not provided.

Verify the settings of the neighboring router.

3.8.3

Communication on IPv4 PIM-SSM Network Is Disabled

If multicast relay on the IPv4 PIN-SSM network configuration is disabled, isolate the cause according to the failure

analysis method below.

The figure below illustrates a network example of IPv4 PIM-SSM.

Figure 3-12: Example of IPv4 PIM-SSM Network

Multicast

receiver

Participation in

the IGMP group

Multicast

sender

first-hop-router

last-hop-router

Multicast

data

Participation in

the IGMP group

Multicast

receiver

Note

• first-hop-router: This router is directly connected to the multicast sender.

• last-hop-router: This router is directly connected to the multicast receiver.

(1) Common check items

The table below shows the common check items for all system in the IPv4 PIM-SSM network configuration.

Table 3-28: Common Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that the use of multicast function is specified (ip

multicast routing) in the configuration.

show running-config

If the use of multicast function is not designated, correct the

configuration.

Confirm that PIM is running on one or more interfaces.

show ip pim interface

If PIM is not running, check the configuration. Set PIM to run

on one or more interfaces. If the interface set in the

configuration to run PIM is not displayed by the show ip

pimcommand with "interface" parameter specified, confirm

that multi-homing is not set on the interface.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Confirm that IGMP snooping is set to the interface with PIM

When the IGMP snooping is set, confirm the following:

enabled.

show igmp-snooping

•

The port to which neighboring router connected is set as a

multicast router port for IGMP snooping.

Disabled."

•

Confirm in the configuration that suppression of protocol

packet and multicast packet relay through filtering, etc. is not

provided on the interface that allows PIM and IGMP to run.

show running-config

If suppression of protocol packet and multicast packet relay is

provided, correct the configuration.

Check the PIM neighboring information.

show ip pim neighbor

If the neighboring router is not displayed, check the

following:

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ip pimcommand

with "interface" parameter specified.

•

Verify the settings of the neighboring router.

Check to see if the unicast route to the multicast data sender

exists.

show ip route

If the unicast route does not exist, see "3.7 IPv4 Unicast

Confirm that PIM is running on the sending interface for the

unicast route to the multicast data sender.

show ip pim interface

If IGMP is not running, check the configuration and set the

configuration to run PIM on the sending interface for the

unicast route.

Confirm that the PIM-SSM group addresses contain the relay

target group address, referring to the configuration.

show running-config

If the PIM-SSM group addresses do not contain the relay

target group address, correct the configuration.

Confirm that the multicast relay routing information exists.

show ip mroute

If the multicast routing information does not exist, check the

setting of the downstream router.

Confirm that multicast routing information or multicast

forwarding entry does not exceed the upper limit.

Multicast routing information:

show ip mroute

multicast forwarding entry:

When warning is output, confirm that unexpected multicast

routing information or unexpected multicast forwarding entry

has not been created. If much of the negative cache exists in

multicast forwarding entry, confirm that there is no terminal

transmitting unnecessary packets.

show ip mcache

netstat multicast

(2) last-hop-router check items

The table below shows the items to be checked when this system is the last-hop-router in the IPv4 PIM-SSM network

configuration.

Table 3-29: last-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that the use of PIM-SSM cooperation in IGMPv1/

IGMPv2 is designated (ip igmp ssm-map enable) in the

configuration.

If the use of PIM-SSM cooperation in IGMPv1/IGMPv2 is

not designated, correct the configuration.

show running-config

Confirm in the configuration that PIM-SSM cooperation in

IGMPv1/IGMPv2 is set (ip igmp ssm-map static) for the group

address and source address to be relayed by PIM-SSM.

show running-config

If PIM-SSM cooperation in IGMPv1/IGMPv2 is not set,

correct the configuration.

Confirm that IGMP is running on the interface connected to

the multicast receiver.

show ip igmp interface

If IGMP is not running, check the configuration and set the

configuration to run IGMP.

Confirm that the multicast receiver participates in the relay

target group via IGMP.

If the group does not participate in the relay target group,

check the setting of the multicast receiver.

show ip igmp group

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

If there is an interface in which the relay target group

participates, confirm that this system is DR.

show ip pim interface

If this system is not DR, check DR of the relay target interface.

Confirm that IGMP snooping is set to the interface with static When the IGMP snooping is set, confirm the following:

group join function enabled.

show igmp-snooping

•

Confirm that the relay port is set as a multicast router port

for IGMP snooping.

•

IPv4 PIM-SM Network Is Disabled" to "3.8.4 Multicast Data

Disabled."

Confirm that no interface in abnormal state is detected.

show ip igmp interface

See notices and confirm that warning information is not

output. When warning information is output, check the

following:

•

L: The number of join request exceeded expected

maximum number. Check to see the number of connected

users.

•

Q: The IGMP version of neighboring router is different.

Adjust it to the version of IGMP.

R: A user who transmitted reports unreceivable at the

present settings exists. Change the IGMP version of this

system or confirm the setting of the participant.

S: Some of the participant information are being discarded

because the number of source exceeded the upper limit

defined to store source per message in IGMPv3. Check the

settings of the participant.

•

(3) first-hop-router check items

The table below shows the items to be checked when this system is the first-hop-router in the IPv4 PIM-SSM network

configuration.

Table 3-30: first-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is directly connected to the multicast

sender.

If not, check the network configuration.

Confirm that PIM or IGMP is running on the interface

connected to the multicast sender.

If PIM or IGMP is not running, check the configuration and

set the configuration to run PIM or IGMP.

show ip pim interface

show ip igmp interface

Check to see if multicast data arrives at this system.

If multicast data has not arrived, check the setting of the

multicast sender.

Check to see if the group address and source address in

multicast data match those in the multicast routing

information.

If the group address and source address do not match, check

the settings of the multicast sender and last-hop-router.

show ip mroute

show netstat multicast

3.8.4

Multicast Data Is Double-relayed on IPv4 PIM-SSM Network

If multicast data is double-relayed in the IPv4 PIM-SSM network configuration, check the settings of each router and

set the configuration to run PIM on the interface for a network having multiple routers.

If double-relay still continues, check the following:

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-31: Check Items When Double-relay Continues

No.

Troubleshooting Steps and Command

Action

Check the PIM neighboring information on the interface of the

network having multiple routers.

If the neighboring router is not displayed, check the

following:

show ip pim neighbor

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ip pimcommand

with "interface" parameter specified.

•

Confirm in the configuration that suppression of protocol

packet relay by filtering, etc. is not provided.

Verify the settings of the neighboring router.

3.8.5

IPv4 Multicast Communication Failure In VRF [OP-NPAR]

If IPv4 multicast communication failure still continues, check the following:

Table 3-32: Check Items for VRF

Troubleshooting Steps and Command

No.

Action

Check to see the VRF interface, port number, VLAN ID.

If the setting is not correct, modify the configuration or the

connections.

show ip vrf

show vlan

show ip pim interface

When this system operates as rendezvous point or BSR,

confirm that loopback interface is set to the VRF or the

configuration.

show ip vrf

show running-config

Specify the same loopback interface number between

rendezvous point/BSR and the VRF.

Besides, If IPv4 address is not set to the loopback interface,

assign IPv4 address.

When multiple VRFs are operating, confirm that global

network or a specific VRF does not occupy more multicast

forwarding entries than expected.

If you find a specific global network or VRF that occupied

more multicast forwarding entries than expected, check to see

if unexpected multicast relay entry has not been created.

If much of the negative cache exist in multicast forwarding

entry, check to see if no terminal transmitting unnecessary

packets exist. In addition, keep a global network or a specific

VRF from occupying the forwarding entry.

show ip mcache vrf all

Corresponding Configuration:

ip pim vrf <vrf id> mchache-limit <number>

For each VRF, check the items from "3.8.1 Communication on To confirm technical information by using commands, you

Is Double-relayed on IPv4 PIM-SSM Network."

need to specify VRF. For more information on how to specify

VRF, see the manual "Operation Commands."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.9 IPv6 Network Communication Failure

3.9.1

Communication Is Disabled or Is Disconnected

There are three possible causes that result in communication failure on the IPv6 network using this system.

1. Configuration on IPv6 communication has changed

2. Network configuration has changed

3. Network component failures

For 1 and 2 above, check for the differences in the configuration and network configuration provided before and after

the change. Check for any difference disabling communication.

This section describes procedure to identify the failed part and to isolate the problem, mainly for the cases of "IPv6

communication is disabled although the configuration and network configuration are correct." and "IPv6

communication had been normally running but it is disabled now." as described in 3 above.

To locate the faulty part and cause, follow the flow below.

Figure 3-13: Failure Analysis Procedure When IPv6 Communication Disabled

Verify if there is an occurrence of line failure using the show

logging command.

A physical failure

message exists.

No physical failure

message exists.

see the manual "Message Log Reference"and

perform the action described in [Action]

associated with each log message.

Check the Up/Down status of the interface

using the show ipv6 interface command.

Identify the extent of failure using the

ping ipv6 command.

Go to "3.4 Network Interface

Communication between the

neighboring host and router

is disabled.

Communication between the

remote host and router is

disabled.

Unicast communication

The route

information

exists.

Verify the route

information using the

show ipv6 route

command.

Verify the status of

Solved

Verify RA address

distribution.

address resolution

using the show ipv6

neighbors command.

Unresolve

Not

distributed

Distributed

No route information exists or the

next hop address is invalid.

Verify the IP network of

remote system. Otherwise, go

to "3.4 Network Interface

"3.9.1 Communication Is Disabled or Is Disconnected"

Verify the filter

settings.

Analyze the failure on each

routing protocol. (RIPng,

BGP4+, etc.)

Verify the RA

settings.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

(1) Checking the log and interface

Communication may be interrupted by a line failure (or damage) or a neighboring system failure. Check the log

displayed on this system or the interface up/down status using the show ipv6 interface command. For the

procedure, see "3.6.1 Communication Is Disabled or Is Disconnected."

(2) Identifying the extent of the failure (performed from this system)

If no failure is found on this system, a failure may exist somewhere in the route between this system and the remote

system. The procedure to locate the failure in the route to the remote system and identify the failure range is as follows:

1. Log in to the system.

2. Use the ping ipv6 command to check communication between both parties. For an example of issuing ping

ipv6and how to interpret the result, see the manual "Configuration Settings."

3. If communication to the other party cannot be verified with the pingcommand, use pingto check communication

to remote systems starting from the system closest to this system.

4. If the result of the ping ipv6command shows that the neighboring system has failed, go to "(4)Checking NDP

resolution information with neighboring system." If the result shows that the remote system has failed, go to

"(5)Checking unicast interface information."

(3) Identifying the extent of failure (performed from the customer's terminal equipment)

If login to this system is not possible, follow the procedure below to identify the extent of failure to see the failure

location in the route between the customer's terminal equipment and the other party.

1. Confirm that the customer's terminal equipment has the ping ipv6 function.

2. Use the ping ipv6 function to check communication between the customer's terminal equipment and the remote

system.

3. If communication to the remote system cannot be verified with the ping ipv6command, use ping ipv6again

to check communication to systems starting from the system closest to the customer's terminal equipment.

4. After the extent of failure has been identified using the ping ipv6command log in to this system if it is considered

to have failed and follow the failure analysis flow to check for the failure cause.

(4) Checking NDP resolution information with neighboring system

If communication to a neighboring system is not possible as a result of ping ipv6execution, address resolution by

NDP may not have been achieved. The procedure for checking the status of address resolution between this system and

the neighboring system is described below.

1. Log in to the system.

2. Use show ipv6 neighborscommand to check the status of address resolution with the neighboring system

(presence/absence of NDP entry information).

3. If the address resolution with the neighboring system is achieved (NDP entry information is provided), go to

"(5)Checking unicast interface information."

4. Confirm that the IP network setting on the neighboring system matches that of this system if the address resolution

with the neighboring system is not achieved (NDP entry information is not provided).

(5) Checking unicast interface information

Check the route information acquired by this system if communication is not possible even when the address resolution

with the neighboring system is achieved, or if communication is disabled in the midway to the other party during IPv6

unicast communication, or if the route to the other party is abnormal. Use the following procedure:

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

1. Log in to the system.

2. Execute show ipv6 routecommand to check the route information acquired by this system.

3. For IP8800/S6700, IP8800/S6600, and IP8800/S6300, check to see if packets are discarded because of the Null

interface. If the route information sending interface resulting a communication failure is null0, packets are discarded

because of the Null interface. Review the setting conditions for the static routing function in the configuration.

4. Go to "3.9 IPv6 Network Communication Failure" if the route information on the failed interface is missing in the

route information acquired by this system or if the next hop address is invalid.

5. If the route information acquired by this system contains the route information on the failed interface, the following

functions set for the interface may have problem. Check these functions.

• RA function

Go to "(7)Checking RA setting information."

(6) Checking filtering/QoS setting information

Certain packets may have been discarded by filtering, or packets may have been discarded through bandwidth

monitoring, discarding control, or shaper of the QoS control.

Review if the conditions of filtering and QoS control in the configuration have been set up correctly and if bandwidth

monitoring, discarding control, or shaper has been set up appropriately for system operation in system configuration.

For the procedure, see "3.23.1 Checking Filtering/QoS Setting Information."

(7) Checking RA setting information

If communication is not possible between this system and the terminal directly connected to this system, address

information is not properly distributed by RA. Confirm that the RA function is set correctly in the configuration. Use

the following procedure:

1. Log in to the system.

2. Execute the command show ipv6 routeand check the RA information of this system.

3. If IPv6 address information is distributed properly, following function that is configured on the failed interface may

have problem. Check these functions.

• Filtering/QoS function

See "(8)Checking filtering/QoS setting information."

3.9.2

IPv6 DHCP Troubleshooting

(1) Configuration is not distributed

When using the prefix distribution feature of IPv6DHCP server in this system, the following five items are possible

causes of service malfunction.

1. The client count is greater than the number of prefix that can be distributed.

2. The client DUID (DHCP Unique Identifier) is not correctly specified.

3. The "ipv6 dhcp server" setting is not correct.

4. Failure during IPv6DHCP operation

5. Other failures

The above problems can be isolated by determining the location of the failure using the following procedure.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Figure 3-14: IPv6DHCP Server Failure Analysis Procedure

Verify the operation log using the show logging command.

No physical failure message exists.

A physical failure message exists.

Check the Up/Down status of the interface using the

see the manuals "Message Log Reference" and

and perform the actions described in [Action] associated

with each log message.

show ipv6interfacecommand.

Go to "3.4 Network Interface Communication Failure."

Check the status of IPv6DHCP server.

The settings of this system

are correct.

The settings of this system

are incorrect.

Check if the prefix has been distributed

redundantly using the show ipv6 dhcp binding

command.

Follow the configuration procedure described in this

chapter.

Redundantly distributed.

Not redundantly distributed.

Follow the procedure for restoring from duplicate

distribution described in this chapter.

Verify if the status and the settings of client.

(a) Checking the log and interface

Communication may be interrupted by NIM or interface failure (or damage) or failure in the neighboring system.

Check the log displayed by this system and the up/down status of interfaces using the show inpv6 interface

command. For the procedure, see "3.9.1 Communication Is Disabled or Is Disconnected."

(b) Checking the status of the IPv6 DHCP server in this system

1. Checking if the IPv6DHCP server service is running

Confirm that information can be retrieved from the IPv6DHCP server daemon using the show ipv6 dhcp

server

statisticscommand. If the show ipv6 dhcp server statistics command produces the following

output, reset

IPv6DHCP server using configuration command service ipv6 dhcp.

[Execution results]

> show ipv6 dhcp server statistics

> < show statistics >: dhcp6_server doesn't seem to be running.

2. Checking the remaining distributable prefixes

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Check the number of remaining prefixes that can be distributed from the IPv6DHCP server using the show ipv6 dhcp

server statistics command. For the instructions, see "Configuration Settings." If the distributable number of prefixes

is 0, increase the number of prefixes to be distributed. The prefixes can be distributed up to 1024.

1. Confirm that IPv6DHCP server functions is enabled.

Execute configuration command show serviceto confirm that the "IPv6 DHCP" server is enabled. If the

underlined part in the following results is not displayed, the "IPv6 DHCP" server is enabled.

[Execution results]

(config)# show service

no service ipv6 dhcp

(config)#

2. Checking "ipv6 dhcp server" setting.

Execute configuration command showto confirm that the "ipv6 dhcp server" setting presents. If not configured, add

the configuration. If the setting presents, confirm that the specified interface supports the network on which clients

are connected.

[Execution results]

(config)# show

interface vlan 10

ipv6 address 3ffe:1:2:: linklocal

ipv6 enable

ipv6 dhcp server Tokyo preference 100

(config)#

3. Check the setting of ipv6 dhcp pool/ipv6 local pool/prefix-delegation/prefix-delegation pool.

Execute configuration command show ipv6 dhcpto confirm that the prefix distribution from the "IPv6DHCP"

server is configured. If not configured, add the configuration. If this feature is configured, confirm that the value

specified in "prefix-delegation/ipv6 local pool," which determine the prefix to be distributed, and presence/absence

of "duid" configuration, which determine the target clients for the distribution, and the client DUID value defined in

"duid" are correct.

[Execution results]

(config)# show ipv6 dhcp

ipv6 dhcp pool Tokyo

prefix-delegation 3ffe:1:2::/48 00:03:00:01:11:22:33:44:55

(config)#

(d) Duplicate acquisition by the client

1. Checking binding information

Execute the show ipv6 dhcp bindingcommand with "detail" parameter specified to confirm that only one

prefix is distributed for each DUID. An example is as follows.

[Execution results]

> show ipv6 dhcp binding detail

Total: 2 prefixes

<DUID>

3ffe:1234:5678::/48

05/04/01 11:29:00 Automatic

00:01:00:01:55:55:55:55:00:11:22:33:44:55

3ffe:aaaa:1234::/48

05/04/01 11:29:00 Automatic

00:01:00:01:55:55:55:55:00:11:22:33:44:55

As displayed in the underlined portion, if the same DUID appears two or more times, it may be a client that is

improperly acquiring prefix information. Check each client and confirm the distributed prefixes value.

2. Matching distributed prefixes and clients

If no client is found that is acquiring duplicated prefixes as the results of the show ipv6 dhcp binding

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

detailcommand, it is necessary to match the displayed DUIDs and client systems. To do that, compare the value

of distributed prefixes displayed in the binding information and the information of prefixes distributed to client

system.

(e) Checking client setting

Check the client setting referring manuals provided with client.

(f) Procedure for restoring from duplicate distribution

If it is determined that duplicated prefixes were distributed to the same client by the IPv6DHCP server in this system,

examine currently unused prefixes from the matching of displayed DUIDs and clients. Delete binding information for

currently unused prefixes using the clear ipv6 dhcp binding<unused prefixes> command.

[Execution results]

> show ipv6 dhcp binding detail

Total: 2 prefixes

<DUID>

3ffe:1234:5678::/48

05/04/01 11:29:00 Automatic

00:01:00:01:55:55:55:55:00:11:22:33:44:55

3ffe:aaaa:1234::/48

05/04/01 11:29:00 Automatic

00:01:00:01:55:55:55:55:00:11:22:33:44:55

> clear ipv6 dhcp binding 3ffe:1234:5678::/48

> show ipv6 dhcp binding detail

<DUID>

3ffe:aaaa:1234::/48

05/04/01 11:29:00 Automatic

00:01:00:01:55:55:55:55:00:11:22:33:44:55

(2) Communication with the target of the prefix distribution is disabled

The following two possible causes of route information are not set when using the automatic route information setting

feature for the route to prefix distribution target of the DHCP server in this system.

1. Information is configured but not distributed.

2. Operations or events have occurred that have an effect on functions relating to automatic route information setting.

It is possible to isolate the above reasons by comparing the results of the show ipv6 route -scommand which

checks route information and distributed prefix information displayed by the show ipv6 dhcp server

bindingcommand.

Table 3-33: Isolating Problems Relate Routing Information to Prefix Distribution Target

Condition

Cause

Binding Information

Route Information

Yes

Route exists

No route

Not applicable. active state.

Cause 2

None

Route exists

No route

Cause 2

Causes 1, 2

There are limits to the retention of route information to prefix distribution target, as indicated in the table below.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-34: Retention of Route Information to Prefix Distribution Target

Retention Information

Concerning Prefix

Event and Retention

Server Function Restart

Routing Manager Restart

This System Restart

Command

Execution

Server

Failure

Route information to client

Y/N

(Legend)

Y: Guaranteed

Y/N: Not guaranteed (each status information may be retained)

N: Not guaranteed (re-setting required because of initialization)

Note

Route management functions required when setting route information to prefix distribution target.

For other failures, see "3.9.1 Communication Is Disabled or Is Disconnected."

(a) Checking route information

When using the automatic route setting feature to the prefix distribution targets from the IPv6DHCP server, the route

information after prefix distribution can be checked using the show ipv6 routecommand with "-s" parameter

specified.

Figure 3-15: Check for Routing Information Using Operation Command

> show ipv6 route -s

Total: 10routes

Destination

Next Hop

::1

Interface

tokyo

Metric Protocol Age

3ffe:1234:5678::/48

0/0

Static 45m

3ffe:aaaa:1234::/48

::1

osaka

0/0

Static 23m

(b) Reconfiguring route information

When using automatic route information setting feature of the IPv6DHCP server of this system to prefix distribution

target, if an event occurs that deletes route information due to a failure, etc., restoration requires the redistribution of

prefixes. Execute operations for the re-acquisition of prefix information by the client system.

(3) If DUID of this system conflicts with other system

If DUID conflicts in the configurations with 2 or more IPv6DHCP servers including this system in the same network,

reconfigure the DUID in this system according to the following procedure.

(a) Deleting the file containing DUID information

The DUID of this system is stored in /usr/var/dhcp6/dhcp6s_duid. Explicitly delete the file from the operation

command line using rm.

(b) Reproducing the DUID

After deleting the DUID file, restart the server using the restartipv6 dhcpservercommand or add an

IPv6DHCP server setting to the configuration information. The IPv6DHCP server acquires the MAC address of the

IPv6 interface used as IPv6DHCP server interface when restarted and generates new DUID based on that information

and time information.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

You can check the DUID in the "< Server DUID >" section of the output of the show ipv6 dhcp server

statisticscommand. For details, see "Configuration Settings."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.10 IPv6 Unicast Routing Communication Failure

3.10.1 No RIPng Routing Information Exists

Isolate the problem according to the failure analysis method listed below if RIPng route information does not exist in

the displayed route information acquired by this system.

Table 3-35: Failure Analysis of RIPng

No.

Troubleshooting Steps and Command

Action

RIPng neighboring information is displayed.

show ipv6 rip neighbor

Go to No. 2 if the interface of a neighboring router is not displayed.

Go to No. 3 if the interface of a neighboring router is displayed.

Go to No. 3 if the configuration is correct.

Check to see if the RIPng setting is correct in

configuration.

Correct the configuration if it is not correct.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the RIPng route.

Correct the configuration if it is not correct.

3.10.2 No OSPFv3 Routing Information Exists

Isolate the problem according to the failure analysis method listed below if OSPFv3 route information does not exist in

the displayed route information acquired by this system.

Table 3-36: Failure Analysis of OSPFv3

No.

Troubleshooting Steps and Command

Action

Check the interface status of OSPFv3.

show ipv6 ospf interface<Interface

Name>

Go to No. 3 if the interface status is DR.

Go to No. 2 if the interface status is BackupDR or DR Other.

Execute the command again after a certain period if the interface status is

"Waiting." Go to No. 1.

Check the status of a neighboring router of DR

from Neighbor List.

Go to No. 4 if the status of the neighboring router of DR is other than Full.

Go to No. 5 if the status of the neighboring router of DR is Full.

Go to No. 4 if the status of some neighboring routers is other than Full.

Go to No. 5 if the status of all neighboring routers is Full.

Go to No. 5 if the configuration is correct.

Check the status of all neighboring routers from

Neighbor List.

Check to see if the OSPFv3 setting is correct in

configuration.

Correct the configuration if it is not correct.

Check the OSPFv3 routes that have been

learned.

show ipv6 route all-routes

Go to No. 6 if the route is set to "InActive."

If no route exists, check to see if the neighboring router advertises the

OSPFv3 route.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the OSPFv3 route.

Correct the configuration if it is not correct.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.10.3 No BGP4+ Routing Information Exists

Isolate the problem according to the failure analysis method listed below if BGP4+ route information does not exist in

the displayed route information acquired by this system.

Table 3-37: BGP4+ Failure Analysis Method

No.

Troubleshooting Steps and Command

Action

Check the BGP4+ peer status.

show ipv6 bgp neighbors

Go to No. 2 if the peer status is other than Established.

Go to No. 3 if the peer status is Established.

Go to No. 3 if the configuration is correct.

Correct the configuration if it is not correct.

Go to No. 4 if the route exist but it is not in active status.

Go to No.5 if no route exist.

Check to see if the BGP4+ setting is correct in

configuration.

Check to see if the BGP4+ route is learned.

show ipv6 bgp received-routes

Check to see if routing information for the next Go to No.5 if the route information for the next hop address resolution

hop address resolution in BGP4+ exist.

exists.

show ipv6 route

When no routing information for the next hop address resolution exist,

perform the protocol failure analysis to learn the routing information.

Confirm that the routing are not filtered by

referring to the configuration.

Check to see if the neighboring router advertises the BGP4+ route.

Correct the configuration if it is not correct.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.11 IPv6 Multicast Routing Communication Failure

Actions to be taken if IPv6 multicast communication failures occur on this system are described below.

3.11.1

Communication on IPv6 PIM-SM Network Is Disabled

If multicast relay on the IPv6 PIN-SM network configuration is disabled, isolate the cause according to the failure

analysis method below.

The figure below illustrates a network example of IPv6 PIM-SM.

Figure 3-16: Example of IPv6 PIM-SM Network

Multicast

Receiver

BSR and

rendezvous point router

Participation in

the MLD group

Multicast

Sender

first-hop-router

last-hop-router

Multicast

data

Participation in

the MLD group

Multicast

Receiver

Note

• BSR: This router delivers rendezvous point information (for details, see the manual "Configuration Settings").

• Rendezvous point router: This router relays the packets, for which the relay destination is not determined, toward

the multicast receiver (for details, see the manual "Configuration Settings").

• first-hop-router: This router is directly connected to the multicast sender.

• last-hop-router: This router is directly connected to the multicast receiver.

(1) Common check items

The table below shows the common check items for all system in the IPv6 PIM-SM network configuration.

Table 3-38: Common Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that the use of multicast function is designated (ipv6

multicast routing) in the configuration.

If the use of multicast function is not designated, correct the

configuration.

show running-config

Confirm that the address of the loopback interface is set in the

configuration.

If the address of the loopback interface is not set, correct the

configuration.

show running-config

Confirm that PIM is running on one or more interfaces.

show ipv6 pim interface

If PIM is not running, check the configuration. Set PIM to run

on one or more interfaces.

Confirm that MLD snooping is set to the interface with PIM When MLD snooping is set, confirm the following:

enabled.

show mld-snooping

•

Confirm that multicast router port for MLD snooping is set

to the port to which neighboring router connects.

•

See "3.5.5 Multicast Relay by MLD snooping Is Disabled."

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Confirm in the configuration that suppression of protocol

packet and multicast packet relay through filtering, etc. is not

provided on the interface that allows PIM and MLD to run.

show running-config

If suppression of protocol packet and multicast packet relay is

provided, correct the configuration.

Check the PIM neighboring information.

show ipv6 pim neighbor

If the neighboring router is not displayed, check the

following:

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ipv6 pim

command with "interface" parameter specified.

Verify the settings of the neighboring router.

•

Check to see if the unicast route to the multicast data sender

exists.

show ipv6 route

If the unicast route does not exist, see "3.10 IPv6 Unicast

Confirm that PIM is running on the interface to the next hop

address for the multicast data sender.

show ipv6 pim interface

If PIM is not running, check the configuration. Set PIM to run

on the interface connected to the next hop address for the

multicast data sender.

Confirm that the PIM-SSM group addresses do not contain the

relay target group address, referring to the configuration.

show running-config

If the PIM-SSM group addresses contain the relay target

group address, correct the configuration.

Confirm that BSR is determined. However, this confirmation

If BSR is not determined, check to see if the unicast route to

is not required if the rendezvous point for the relay target group BSR exists. If the unicast route does not exist, see "3.10 IPv6

address is a static rendezvous point.

Unicast Routing Communication Failure."

show ipv6 pim bsr

If the unicast route exists, check the BSR setting. If the BSR

is this system, see "(2)BSR check items."

Confirm that the rendezvous point is determined.

show ipv6 pim rp-mapping

If the rendezvous point is not determined, check to see if the

unicast route to the rendezvous point exists. If the unicast

route does not exist, see "3.10 IPv6 Unicast Routing

If the unicast route exists, check the rendezvous point setting.

If the rendezvous point is this system, see "(3)Rendezvous

point router check items."

Confirm that the rendezvous point group addresses contain the

relay target group address.

show ipv6 pim rp-mapping

If the relay target group address is not contained, check the

rendezvous point setting.

Confirm that the multicast relay entry exists.

show ipv6 mcache

If the multicast relay entry does not exist, confirm that

multicast data has arrived at the upstream port. If multicast

data has not arrived, check the setting of the multicast sender

or upstream router.

Confirm that the multicast routing information exists.

show ipv6 mroute

If the multicast routing information does not exist, check the

setting of the downstream router.

Confirm that multicast routing information or multicast

forwarding entry does not exceed the upper limit.

Multicast routing information:

show ip mroute

Multicast forwarding entry:

When warning is output, confirm that unexpected multicast

routing information or unexpected multicast forwarding entry

has not been created. If much of the negative cache exists in

multicast forwarding entry, check to see if no terminal

transmitting unnecessary packets exist.

show ip mcache

netstat multicast

(2) BSR check items

The table below shows the items to be checked when this system is BSR in the IPv6 PIM-SM network configuration.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

Table 3-39: BSR Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is a candidate for BSR.

show ipv6 pim bsr

If this system is not a candidate for BSR, check the

configuration and set the configuration to run this system as a

candidate for BSR. Since this system does not run as a

candidate for BSR if no address is set for the loopback

interface, confirm that an address is set for the loopback

interface.

Confirm that this system is BSR.

show ipv6 pim bsr

If this system is not BSR, check the priority of other BSR

candidates. The larger the value, the higher the priority. If the

same priority is provided, the BSR candidate with the largest

BSR address becomes BSR.

(3) Rendezvous point router check items

The table below shows the items to be checked when this system is the rendezvous point router in the IPv6 PIM-SM

network configuration.

Table 3-40: Rendezvous Point Router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is a candidate of rendezvous point for

the relay target group address.

show ipv6 pim rp-mapping

If this system is not a candidate of rendezvous point for the

relay target group address, check the configuration and set the

configuration to run this system as a candidate of rendezvous

point for the relay target group address. Since this system does

not run as a candidate of rendezvous point if no address is set

for the loopback interface, confirm that an address is set for

the loopback interface.

Confirm that this system is the rendezvous point for the relay

target group address.

show ipv6 pim rp-hash<Group Address>

If this system is not the rendezvous point, check the priority of

other candidates of rendezvous point. The smaller the value,

the higher the priority. If the priority of another candidate of

rendezvous point is higher, this system does not run as the

rendezvous point. If the same priority is provided, the

rendezvous point is distributed for each group address

according to the protocol specifications and this system may

not run as the rendezvous point. To run this system

preferentially as the rendezvous point, set the priority higher

than those of other rendezvous point candidates.

(4) last-hop-router check items

The table below shows the items to be checked when this system is the last-hop-router in the IPv6 PIM-SM network

configuration.

Table 3-41: last-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that MLD is running on the interface connected to the

multicast receiver.

If MLD is not running, check the configuration and set the

configuration to run MLD.

show ipv6 mld interface

Confirm that the multicast receiver participates in the relay

target group via MLD.

show ipv6 mld group

If the multicast receiver does not participate in the relay target

group, check the setting of the multicast receiver.

participates and PIM is running, confirm that this system is

If this system is not DR, check DR of the relay target interface.

DR.

show ipv6 pim interface

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Confirm that MLD snooping is set to the interface with PIM

When MLD snooping is set, confirm the following:

enabled.

show mld-snooping

•

Confirm that multicast router port for MLD snooping is set

to the forwarding port.

•

See "3.5.5 Multicast Relay by MLD snooping Is Disabled."

Confirm that no interface in abnormal state is detected.

show ipv6 mld interface

See notices and confirm that warning information is not

output. When warning infromation is output, check the

following:

•

L: The number of join request exceeded expected

maximum number. Check to see the number of connected

users.

•

Q: The MLD version of neighboring router is different.

Adjust it to the MLD version.

R: A user who transmitted reports unreceivable at the

present settings exists. Change the MLD version of this

system or confirm the setting of the participant.

S: Some of the participant information are being discarded

because the number of source exceeded the upper limit

defined to store source per message in MLDv2. Check the

settings of the participant.

•

(5) first-hop-router check items

The table below shows the items to be checked when this system is the first-hop-router in the IPv6 PIM-SM network

configuration.

Table 3-42: first-hop-router Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that this system is directly connected to the multicast

sender.

If not, check the network configuration.

Confirm that PIM or MLD is running on the interface

connected to the multicast sender.

show ipv6 pim interface

If not running, check the configuration and set the

configuration to run PIM or MLD.

show ipv6 mld interface

Confirm that the multicast relay routing information exists.

show ipv6 mroute

If the multicast routing information does not exist, confirm

that multicast data source address is the network address of

the interface directly connected to the multicast sender.

3.11.2

Multicast Data Is Double-relayed on IPv6 PIM-SM Network

If multicast data is double-relayed in the IPv6 PIM-SM network configuration, check the settings of each router and set

the configuration to run PIM on the interface for a network having multiple routers.

If double-relay still continues, check the following:

Table 3-43: Check Items When Double-relay Continues

No.

Troubleshooting Steps and Command

Action

Check the PIM neighboring information on the interface of the

network having multiple routers.

If the neighboring router is not displayed, check the

following:

show ipv6 pim neighbor

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ipv6 pim

command with "interface" parameter specified.

Confirm in the configuration that suppression of protocol

packet relay by filtering, etc. is not provided.

•

Verify the settings of the neighboring router.

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

3.11.3

Communication on IPv6 PIM-SSM Network Is Disabled

If multicast relay on the IPv6 PIN-SSM network configuration is disabled, isolate the cause according to the failure

analysis method below.

The figure below illustrates a network example of IPv6 PIM-SSM.

Figure 3-17: Example of IPv6 PIM-SSM Network

Multicast

receiver

Participation in

the MLD group

Multicast

sender

first-hop-router

last-hop-router

Multicast

data

Participation in

the MLD group

Multicast

receiver

Note

• first-hop-router: This router is directly connected to the multicast sender.

• last-hop-router: This router is directly connected to the multicast receiver.

(1) Common check items

The table below shows the common check items for all system in the IPv6 PIM-SSM network configuration.

Table 3-44: Common Check Items

No.

Troubleshooting Steps and Command

Action

Confirm that the use of multicast function is designated (ipv6

multicast routing) in the configuration.

If the use of multicast function is not designated, correct the

configuration.

show running-config

Confirm that the address of the loopback interface is set in the

configuration.

If the address of the loopback interface is not set, correct the

configuration.

show running-config

Confirm that PIM is running on one or more interfaces.

show ipv6 pim interface

If PIM is not running, check the configuration. Set PIM to run

on one or more interfaces.

Confirm that MLD snooping is set to the interface with PIM When MLD snooping is set, confirm the following:

enabled.

show mld-snooping

•

Confirm that multicast router port for MLD snooping is set

to the ports to which neighboring routers connect.

•

See "3.5.5 Multicast Relay by MLD snooping Is Disabled."

Confirm in the configuration that suppression of protocol

packet and multicast packet relay through filtering, etc. is not

provided on the interface that allows PIM and MLD to run.

show running-config

If suppression of protocol packet and multicast packet relay is

provided, correct the configuration.

Check the PIM neighboring information.

show ipv6 pim neighbor

If the neighboring router is not displayed, check the

following:

•

Confirm that PIM is running on the interface connected to

the neighboring router using the show ipv6 pim

command with "interface" parameter specified.

Verify the settings of the neighboring router.

•

Download from Www.Somanuals.com. All Manuals Search And Download.

3. Troubleshooting Functional Failures in Operation

No.

Troubleshooting Steps and Command

Action

Check to see if the unicast route to the multicast data sender

exists.

If the unicast route does not exist, see "3.10 IPv6 Unicast