IPDR Configuration(ipdr parameter keepalive)

ipdr parameter keepalive

Function

The ipdr parameter keepalive command is used to set keepalive intervals for Internet Protocol Detail Record (IPDR) protocol.
The undo ipdr parameter keepalive command is used to reset the keepalive interval to the default value 300s.

Format

ipdr parameter keepalive time
undo ipdr parameter keepalive

Parameters

Parameter	Description	Value
time	Indicates the keepalive interval for the IPDR protocol.	Numeral type. Range: 5-300. Unit: second. Default value: 300. NOTE: The shorter the keepalive interval is, the higher frequency at which the CMTS device detects whether the IPDR collector is faulty will be. The shorter the keepalive interval is, more keepalive packets between the CMTS device and IPDR collector will be generated, which heavies the load on the IPDR collector.

Modes

Global config mode,MA5683T,MA5680T,MA5608T

Level

Administrator level

Usage Guidelines

The keepalive interval for the IPDR protocol can be modified only when all sessions are in the deactivated state.

Example

To set the keepalive interval for IPDR messages to 200s, do as follows:

huawei(config)#ipdr parameter keepalive
{ time<U><5,300> }:200

  Command:
          ipdr parameter keepalive 200

To reset the keepalive interval for IPDR messages to the default value, do as follows:

huawei(config)#undo ipdr parameter keepalive

System Response

• The system does not display any message after the command is executed successfully.

MORE BLOG:

When you cannot find 10GE port on S7700?

How to Install SLQ4 board on slot 1 to slot 4 in OSN 3500?

What’s the Ethernet features in terms of function of the OptiX OSN 1500 V1R2?

IPDR Configuration---ipdr collector

ipdr collector

Function

The ipdr collector name command is used to create an Internet Protocol Detail Record (IPDR) collector. After the IPDR collector is created, it cannot be modified.
The undo ipdr collector command is used to delete an IPDR collector. IPDR collectors associated with sessions cannot be deleted. Before deleting an IPDR collector, ensure that its association with a session has been deleted by using the undo ipdr session collector command.
The ipdr collector type command is used to configure the IPDR collector's connection mode. active mode is the collector initiating a connection, passive mode is the collector receiving a connection. The default mode is active.

Format

ipdr collector name name ip ip-address [ port port ]
undo ipdr collector name
ipdr collector type { active | passive }

Parameters

Parameter	Description	Value
name name	Indicates a IPDR collector name.	Character string type, a string of 1-20 characters.
ip ip-address	Indicates the IP address of the IPDR collector.	IPv4 address format. Dotted decimal notation.
port port	Indicates the socket port number of the IPDR collector.	Numeral type. Range: 1-65535. Default value: 4737. When the connection mode of the IPDR collector is active, this port is invalid. This port is used only when the IPDR collector's connection mode is passive.
type	Indicates the IPDR collector connection type.	-
active	IPDR collector initiating a connection.	-
passive	IPDR collector receiving a connection.	-

Modes

Global config mode, MA5683T,MA5680T,MA5608T

Level

Administrator level

Usage Guidelines

• IP address identify an IPDR collector.
• A maximum of 10 IPDR collectors can be configured in the system.

Example

To create an IPDR collector whose name is huawei, IP address is 10.10.10.10, and port number is 1, do as follows:

huawei(config)#ipdr collector
{ name<K>|type<K> }:name
{ name<S><Length 1-20> }:huawei
{ ip<K> }:ip
{ ip-address<I><X.X.X.X> }:10.10.10.10
{ <cr>|port<K> }:port
{ port<U><1,65535> }:1

  Command:
          ipdr collector name huawei ip 10.10.10.10 port 1

To create an IPDR collector whose name is huawei, IP address is 10.10.10.11, and default port number is 4737, do as follows:

huawei(config)#ipdr collector
{ name<K>|type<K> }:name
{ name<S><Length 1-20> }:huawei
{ ip<K> }:ip
{ ip-address<I><X.X.X.X> }:10.10.10.11
{ <cr>|port<K> }:

  Command:
          ipdr collector name huawei ip 10.10.10.11

To delete an IPDR collector named huawei, do as follows:

huawei(config)#undo ipdr collector
{ name<S><Length 1-20> }:huawei

  Command:
          undo ipdr collector huawei

To configure the IPDR collector's connection mode is active, do as follows:

huawei(config)#ipdr collector type
{ active<K>|passive<K> }:active

  Command:
          ipdr collector type active

To configure the IPDR collector's connection mode is passive, do as follows:

huawei(config)#ipdr collector type
{ active<K>|passive<K> }:passive

  Command:
          ipdr collector type passive

System Response

• The system does not display any message after the command is executed successfully.

MORE BLOG:

What Is the Calculation Method for Load Balancing of the Upstream Aggregation Ports of the MA5680T?

When the NMS Failing to Synchronize ONUs?

How to Bootrom password for X7 switch

Incorrect Client-Side Service Type Causes Failure of Interconnection With a Router

Incorrect client-side service type causes a failure of interconnection with a router.

Product

OptiX BWS 1600G, OSN 6800, OSN 8800

Fault Type

Equipment Interconnection

Client Equipment

Symptom

On a network, an ETMX board on the OptiX BWS 1600G is used to receive a 2.5 Gbit/s service from a router on the client side. Client-side channels run properly after an expansion is performed on the network.

When the ETMX board on the OptiX BWS 1600G receives the 2.5 Gbit/s service, interconnections with ports on the router are successful but exchanges of protocols fail. After an outloop is configured on the ETMX board at the local end by using the NMS to loopback the service to the router, port interconnections and protocol exchanges are successful. After an inloop is configured on the WDM-side optical port on the ETMX board at the remote end by using a fiber patch cord to loopback the service to the router, port interconnections are successful but protocol exchanges fail. This indicates that the fault lies on the WDM-side link or interconnected ports.

Cause Analysis

The analysis of the problem is as follows:

1. An SDH analyzer is used to test the WDM-side channel after the expansion is performed. No exception is found.
2. After the outloop on the ETMX board at the local end is performed, port interconnections and protocol exchanges are successful. This indicates that the router is running properly.
3. After the inloop on the ETMX board at the remote end through a fiber patch cord is performed, protocol exchanges fail. This indicates that protocol configuration is incorrect after signals are transmitted from the router to the ETMX board.

The preceding information shows that the problem is due to incorrect configurations of the ETMX board.

Procedure

1. Check the WDM-side configurations of the board. Service Type for services received from the client side of the ETMX board can beSDH, SONET, or ODU1.. By default, Service Type is set to SDH and J0 byte in the SDH interface overhead is set to Null.
2. Check the interconnected ports and no alarm is generated. This indicates that the no error is generated in the J0 byte.
3. Confirm that on the client side of the OptiX BWS 1600G, the service type interconnected with the router is OC48, which is different from the service type of the ETMX board. This is why the problem occurs.
4. Change Service Type of the ETMX board to SONET. Then, protocol exchanges are successful and services are normal.

Result

The problem is resolved.

Reference Information

None.

MORE BLOG:

How to do when Abnormal Optical Power Reporting Caused by the Coupling Exception

How to do when the Occasional Failure to Go Online for TN11HSC1 Boards

Incorrect Configuration of the ZL80018 Chip on OptiX OSN 1800

Inconsistency of Fiber Jumper Model and Fiber Connector Type of a Board

The receive optical power of a board is lower than the specified threshold because the fiber connector mismatches the port connector on the board, the connected OAU board at the downstream station reports MUT_LOS and R_LOS alarms.

Product

OptiX BWS 1600G, OSN 6800, OSN 8800

Fault Type

Optical Power Abnormality

Fiber

MUT_LOS

R_LOS

Symptom

At an OptiX BWS 1600G station, a fiber connector on the RPC board is damaged and the fiber jumper must be replaced. After the fiber jumper is replaced, the receive optical power on the WDM side is low (-53 dBm).

The connected OAU board at the downstream station reports MUT_LOS and R_LOS alarms.

Cause Analysis

After a detailed check, it is found that:

1. The transmit optical power of the FIU board at the downstream station is within the permitted range.
2. The receive optical power of the ODF connected to the local station is within the permitted range. That is, the line attenuation is within the permitted range.
3. The receive optical power of the OAU at the local station is low.
4. The receive optical power at the IN port on the FIU board at the local station is low.
5. The fiber jumper between the IN port on the FIU board and the SYS port on the RPC board is normal.

The preceding information shows that the fault is located between the ODF and the FIU board. Possible causes of the problem are as follows:

• The fiber jumper between the ODF and the RPC board is damaged.
• The RPC board is malfunctioning.

Procedure

1. Check the fiber jumper between the ODF and the RPC board. The fiber jumper uses an FC/PC connector at one end and an LHS/UPC connector at the other end, while the LINE port connector on the RPC is LSH/APC. The end faces of the FC/PC and LSH/UPC connectors of the fiber jumper is flat while the end face of the LSH/APC connector is tilted. Therefore, air exists between the LINE port on the RPC board and the fiber jumper connector. As a result, the transmit optical power of the pump laser on the RPC board is abnormal and the receive optical power on the WDM side is low. Change connectors of the fiber jumper on the RPC board so that the fiber jumper uses an FC/PC connector at one end and an LSH/APC connector at the other end. Then, the system operates properly.

Result

The problem is resolved.

Reference Information

None.

MORE BLOG:

How to Use the Ethernet Test Frames on the OptiX OSN 6800?

TD Alarms Falsely Reported by Some Boards Using Pluggable Optical Modules in WDM Products

When the Software Version Compatibility Issue on the TNF2LQM and TNF2LDGF2 Boards in OptiX OSN 1800

The Spectrum Analyzer Cannot Scan a Wavelength of the LWC Board Due to the Drift of This Wavelength

The spectrum analyzer cannot scan a wavelength of the LWC board due to the drift of this wavelength.

Product

OptiX Metro 6100, OSN 6800,Metro 3000

Fault Type

Optical Transponder Unit

Symptom

After one LWC board that operates at 192.9 THz is added to the OptiX Metro 6100 equipment on a network for capacity expansion, the MON port on the WBA board detects neither the 192.9 THz wavelength nor one more wavelength.

Cause Analysis

The possible causes of the problem are as follows:

• The LWC board is faulty.
• The WBA board is faulty.

Procedure

1. Query the optical power at the IN optical port on the WBA board. The query result shows that the optical power at the IN optical interface after the expansion is the same as that before the expansion. This indicates that the added wavelength does not reach the WBA board.
2. Use an optical power meter to test the LWC board. The test result shows that the output frequency of the board is 193.09 Hz. The WDM-side wavelength drift of the LWC board is large. Therefore, the wavelength of the LWC board does not match that of the M40 board interconnected with the LWC board.
3. Replace the faulty LWC board and then test the output frequency at the MON interface on the new LWC board. The test result shows that the output frequency is within the normal range.

Result

After the faulty LWC board, the problem is solved.

Reference Information

Wavelength drift on the OTU board will cause low output optical power on the M40 board. Therefore, ensure that center frequency of each output wavelength on the WDM side of the OTU board is within the range of ±10 GHz from its nominal center frequency.

MORE BLOG:

When customized for North America unable to configure OSN1800.

How to Use the LDMD Board to Configure Intra-Board 1+1 Protection Fails?

When OptiX OSN 1800 Database Recovery Failures

IPDR Configuration----ipdr session statistic reset

ipdr session statistic reset

Function

This command is used to clear debugging statistic about Internet Protocol Detail Record (IPDR) sessions. After rectifying a collector or the current device network environment, if you want to check whether packets can be correctly transmitted, run this command to clear debugging statistics. Then, check whether the device is recovered to normal with the help of the display ipdr session statistic command output.

NOTE:

After this command is successfully executed, all debugging statistics are cleared. Exercise caution when running this command.

Format

ipdr session id statistic reset

Parameters

Parameter	Description	Value
id	Indicates a session uniquely.	Numeral type. Range: 1-255.

Modes

Diagnose mode, MA5683T, MA5608T, MA5680T

Level

Super level

Usage Guidelines

In the privilege mode or global config mode, run the diagnose command to enter the Diagnose mode.

Example

To clear the debugging statistic about an IPDR session whose ID is 1, do as follows:

huawei(diagnose)#ipdr session
{ id<U><1,255> }:1
{ statistic<K> }:statistic
{ reset<K> }:reset

  Command:
          ipdr session 1 statistic reset

System Response

• The system does not display any message after the command is executed successfully.

MORE BLOG:

Interconnection Between the OLT and the Switch Fails

How to precaution the using problem of Huawei MA5603T product?

Some Abnormal OLT GPON CLASS B+ Optical Modules at High Temperature

IPDR Configuration----ipdr session name

ipdr session name

Function

The ipdr session command is used to create an Internet Protocol Detail Record (IPDR) session or modify the existing session's name and description information. The created session is in the deactivated state.
The undo ipdr session is used to delete an IPDR session. After a session is deleted, its associated template and the association between the session type and collector are also deleted.
To activate a session, run the ipdr session activate command. To deactivate an activated session, run the ipdr session deactivate command. Only the session in the deactivated state can be modified (session name and description information) or deleted.

Format

ipdr session id name name desc description
undo ipdr session id

Parameters

Parameter	Description	Value
id	Indicates a session uniquely.	Numeral type. Range: 1-255.
name name	Indicates the session name.	Character string type, a string of 1-20 characters.
desc description	Indicates the description of the session.	Character string type, a string of 1-64 characters.

Modes

Global config mode, MA5683T, MA5608T, MA5680T

Level

Administrator level

Usage Guidelines

A maximum of 30 sessions can be created.

Example

Assume that:

• Session ID: 1
• Session name: huawei
• Description: huawei

To create such an IPDR, do as follows:

huawei(config)#ipdr session
{ activate<K>|deactivate<K>|id<U><1,255> }:1
{ collector<K>|name<K>|template<K> }:name
{ name<S><Length 1-20> }:huawei
{ desc<K> }:desc
{ description<S><Length 1-64> }:huawei
  Command:
          ipdr session 1 name huawei desc huawei

Assume that:

• Session ID: 1
• Session name: huawei
• Session description: huawei

To change the name and description for test of the IPDR session, do as follows:

huawei(config)#ipdr session
{ activate<K>|deactivate<K>|id<U><1,255> }:1
{ collector<K>|name<K>|template<K> }:name
{ name<S><Length 1-20> }:test
{ desc<K> }:desc
{ description<S><Length 1-64> }:test
  Command:
          ipdr session 1 name test desc test

Assume that:

• Session ID: 1
• Session name: test
• Description: test

To delete such a session, do as follows:

huawei(config)#undo ipdr session
{ id<U><1,255> }:1
{ <cr>|collector<K> }:

  Command:
          undo ipdr session 1

System Response

• The system does not display any message after the command is executed successfully.

MORE BLOG:

How to Assemble an IMPI on the MA5620G?

What is the command lines that we can use on the OLT to detect PRTE board status

How to check service board detail information?

---

Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.