Visibility issue of the RTN-910 through different clouds (UBR).

Issue Description

In a network we have iManager U2000 NMS & the MW NEs are RTN 900 & some of the UBR links which need to visible on the NMS. Now when we are going to visible the RTN 910 which are behind the UBR links, getting problem for the visibility.

Please find the picture, as per the actual network.

Alarm Information

N/A

Handling Process

Since the DCC was flowing through HW-ECC protocol we could not make E and F visible. Now we give IP in A,BC,D,E,F in such a way that the IP of A becomes the gateway of B, IP of B becomes the gateway of C and so on.

Then we try to search for E and F and easily got E and F visible in NMS.

Root Cause

In case of huawei internal visibility the equipments we use HW-ECC protocol for DCC flow. But whenever we have to consider third party equipements, we need other protocols like TCP/IP. Here we have some 910 IDUs that are behind the cloud of UBR links. For making these 910 IDUs visible in NMS, we have to use TCP/IP in an appropriate way as described in the handling process. Let us consider:-

Huawei 910 IDUs- A,B where E,F are the far end IDU that need to be visible.

UBR IDUs- C,D where the chain is linke A-B-C-D-E-F.

When we search for E and F in NMS, we find nothing is comming although A and B are visible in NMS.

Suggestions

This is different from giving IP in normal IDUs running in TCP/IP protocol as normally we give the IP of the router as the gateway of NEs, but here we have to give the IP of the preceeding NE as the G/W of the succeeding NE due to UBR presence in between the NEs.

Issue Description

In a network we have iManager U2000 NMS & the MW NEs are RTN 900 & some of the UBR links which need to visible on the NMS. Now when we are going to visible the RTN 910 which are behind the UBR links, getting problem for the visibility.

Please find the picture, as per the actual network.

Alarm Information

N/A

Handling Process

Since the DCC was flowing through HW-ECC protocol we could not make E and F visible. Now we give IP in A,BC,D,E,F in such a way that the IP of A becomes the gateway of B, IP of B becomes the gateway of C and so on.

Then we try to search for E and F and easily got E and F visible in NMS.

Root Cause

In case of huawei internal visibility the equipments we use HW-ECC protocol for DCC flow. But whenever we have to consider third party equipements, we need other protocols like TCP/IP. Here we have some 910 IDUs that are behind the cloud of UBR links. For making these 910 IDUs visible in NMS, we have to use TCP/IP in an appropriate way as described in the handling process. Let us consider:-

Huawei 910 IDUs- A,B where E,F are the far end IDU that need to be visible.

UBR IDUs- C,D where the chain is linke A-B-C-D-E-F.

When we search for E and F in NMS, we find nothing is comming although A and B are visible in NMS.

Suggestions

This is different from giving IP in normal IDUs running in TCP/IP protocol as normally we give the IP of the router as the gateway of NEs, but here we have to give the IP of the preceeding NE as the G/W of the succeeding NE due to UBR presence in between the NEs.

Issue Description

In a network we have iManager U2000 NMS & the MW NEs are RTN 900 & some of the UBR links which need to visible on the NMS. Now when we are going to visible the RTN 910 which are behind the UBR links, getting problem for the visibility.

Please find the picture, as per the actual network.

Alarm Information

N/A

Handling Process

Since the DCC was flowing through HW-ECC protocol we could not make E and F visible. Now we give IP in A,BC,D,E,F in such a way that the IP of A becomes the gateway of B, IP of B becomes the gateway of C and so on.

Then we try to search for E and F and easily got E and F visible in NMS.

Root Cause

In case of huawei internal visibility the equipments we use HW-ECC protocol for DCC flow. But whenever we have to consider third party equipements, we need other protocols like TCP/IP. Here we have some 910 IDUs that are behind the cloud of UBR links. For making these 910 IDUs visible in NMS, we have to use TCP/IP in an appropriate way as described in the handling process. Let us consider:-

Huawei 910 IDUs- A,B where E,F are the far end IDU that need to be visible.

UBR IDUs- C,D where the chain is linke A-B-C-D-E-F.

When we search for E and F in NMS, we find nothing is comming although A and B are visible in NMS.

Suggestions

This is different from giving IP in normal IDUs running in TCP/IP protocol as normally we give the IP of the router as the gateway of NEs, but here we have to give the IP of the preceeding NE as the G/W of the succeeding NE due to UBR presence in between the NEs.

Issue Description

In a network we have iManager U2000 NMS & the MW NEs are RTN 900 & some of the UBR links which need to visible on the NMS. Now when we are going to visible the RTN 910 which are behind the UBR links, getting problem for the visibility.

Please find the picture, as per the actual network.

Alarm Information

N/A

Handling Process

Since the DCC was flowing through HW-ECC protocol we could not make E and F visible. Now we give IP in A,BC,D,E,F in such a way that the IP of A becomes the gateway of B, IP of B becomes the gateway of C and so on.

Then we try to search for E and F and easily got E and F visible in NMS.

Root Cause

In case of huawei internal visibility the equipments we use HW-ECC protocol for DCC flow. But whenever we have to consider third party equipements, we need other protocols like TCP/IP. Here we have some 910 IDUs that are behind the cloud of UBR links. For making these 910 IDUs visible in NMS, we have to use TCP/IP in an appropriate way as described in the handling process. Let us consider:-

Huawei 910 IDUs- A,B where E,F are the far end IDU that need to be visible.

UBR IDUs- C,D where the chain is linke A-B-C-D-E-F.

When we search for E and F in NMS, we find nothing is comming although A and B are visible in NMS.

Suggestions

This is different from giving IP in normal IDUs running in TCP/IP protocol as normally we give the IP of the router as the gateway of NEs, but here we have to give the IP of the preceeding NE as the G/W of the succeeding NE due to UBR presence in between the NEs.