No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Service Provisioning on the uPortal Occasionally Fails

Service Provisioning on the uPortal Occasionally Fails

Symptom

During service provisioning on the uPortal, the BMU fails to be connected occasionally.

Possible Causes

The MAC address segments configured in different OMU systems during CGP installation conflict. As a result, MAC addresses of VM network ports in different OMU systems conflict. MAC address conflict will cause abnormal packet sending and receiving through service IP addresses of the corresponding network ports.

Troubleshooting Method

  1. Run the DSP IPINFO command under the CGP on the LMT to query the VM network port corresponding to the faulty IP address.
    DSP IPINFO: DEPLOYTYPE=VM, VMNAME="ec_ecs_oracle_m-1", IPITERM=IP;
    +++    CGP/*MEID:0 MENAME:Enhanced site management*/         2018-01-02 21:19:09+08:00
    O&M    #341
    %%DSP IPINFO: DEPLOYTYPE=VM, VMNAME="ec_ecs_oracle_m-1", IPITERM=IP;%%
    RETCODE = 0   Operation succeeded
    
    IP address is as follows
    ------------------------
     Local IP address             Mask/Prefix-length  Device interface
    
     172.16.191.96                  255.255.0.0         BASE1  
     172.17.191.96                  255.255.0.0         BASE2 
     172.18.191.96                  255.255.0.0         FABRIC1 
     172.19.191.96                  255.255.0.0         FABRIC2 
     10.102.20.31                   255.255.0.0         VNIC1  
     127.0.0.254                    255.255.255.255     vn0   
     fe80:0000:0000:0000:0ae8:4fff:fe7d:1fca  64        BASE1   
     fe80:0000:0000:0000:0ae8:4fff:fe7d:1fcb  64        BASE2   
     fe80:0000:0000:0000:0ae8:4fff:fe7d:1fcc  64        FABRIC1 
     fe80:0000:0000:0000:0ae8:4fff:fe7d:1fcd  64        FABRIC2 
     fe80:0000:0000:0000:4ef9:5dff:fe00:1916  64        VNIC1   
     fe80:0000:0000:0000:4ef9:5dff:fe00:1917  64        VNIC2   
     fe80:0000:0000:0000:0200:00ff:fe00:0000  64        vn0     
    (Number of results = 13)
    
    ---    END

    In the preceding information, the value of Device interface corresponding to 10.102.20.31 is the VM network port corresponding to the faulty IP address.

  2. Run the LST VNET command under the CGP to query the MAC address of the faulty network port based on the VM network port found in the previous step
    LST VNET: VMNAME="ec_ecs_oracle_m-1", VMPORTNAME=VNIC1;
    +++    CGP/*MEID:0 MENAME:Enhanced site management*/         2018-01-02 08:25:30+00:00
    O&M    #596
    %%LST VNET: VMNAME="ec_ecs_oracle_m-1", VMPORTNAME=VNIC1;%%
    RETCODE = 0   Operation succeeded
    
    The result is as follows
    ------------
                       ME ID  =  301
        Virtual machine name  =  ec_ecs_oracle_m-1
    Virtual machine port name =  VNIC1
                 MAC address  =  4C:F9:5D:00:18:E9
        Location description  =  Host-ECS_ALLINONE/IP-10.102.20.202
              Host port name  =  Port2
                Network name  =  NULL
                     VLAN ID  =  0
    (Number of results = 1)
    
    ---    END
  3. Run the LST VNET command on the LMT of another OMU system on the same layer-2 switching network, enter the MAC address found in step 2, and check whether there is any result. If there is any result, MAC address conflict exists.
    +++    CGP/*MEID:0 MENAME:Enhanced site management*/         2018-01-02 07:42:09+00:00
    O&M    #443
    %%LST VNET: MACADDR="4C:F9:5D:00:18:E9";%%
    RETCODE = 0   Operation succeeded
    
    The result is as follows
    ------------
                       ME ID   =  5
         Virtual machine name  =  VM_CLOUDMCU
    Virtual machine port name  =  VNIC2
                 MAC address   =  4C:F9:5D:00:18:E9
         Location description  = Host-CloudMCU_Server/IP-10.102.23.204
               Host port name  =  Port2
                 Network name  =  NULL
                      VLAN ID  =  0
    (Number of results = 1)
    
    
    ---    END

Solution

  1. Run the LST MACPOOL command under the CGPs of two OMU systems and check whether the MAC address segment (specified by Start MAC and End MAC) of one OMU system conflicts with that of the other OMU system.

    LST MACPOOL:;

    +++    CGP/*MEID:0 MENAME:Enhanced site management*/         2018-01-02 20:13:19+08:00
    O&M    #67
    %%LST MACPOOL:;%%
    RETCODE = 0   Operation succeeded
    
    The result is as follows
    ------------
      Start MAC  =  4C:F9:5D:00:18:DA
        End MAC  =  4C:F9:5D:00:28:79
            Sum  =  4000
           Free  =  3924
    (Number of results = 1)
    
    ---    END

    LST MACPOOL:;

    +++    CGP/*MEID:0 MENAME:Enhanced site management*/          2018-01-02 20:13:19+08:00
    O&M    #99
    %%LST MACPOOL:;%%
    RETCODE = 0   Operation succeeded
    
    The result is as follows
    ------------
      Start MAC  =  4C:F9:5D:00:18:DA
        End MAC  =  4C:F9:5D:00:28:79
            Sum  =  4000
           Free  =  3900
    (Number of results = 1)
    
    ---    END

    The query result indicates that the MAC address segments configured in the two OMU systems conflict.

  2. Adjust the MAC address segments based on the network data plan. To adjust the MAC address segments, you need to re-deploy the OMU system and service NEs. Deploy the OMU system by referring to section Installing the OMU in the corresponding product documentation and then deploy related service NEs.

    NOTE:

    OMU system re-deployment will cause reinstallation of all service NEs based on the OMU system and interruption of services on all service NEs of the OMU system. Therefore, re-deploy the OMU system during off-peak hours.

Translation
Download
Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 21902

Downloads: 12

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next