Configure Route for IPWorks PL Node

Contents

1Introduction
1.1Prerequisites

2

Procedure
2.1Add Route for IPWorks PL Node
2.2Remove Route from PL Node
2.3Remove eVIP Command from Command List

1   Introduction

This document describes how to add or remove route for a remote network through traffic interface (ipw_sig_sp and ipw_data_sp) in PL node. For example, if the operator wants to connect PL to a remote CUDB server (10.0.50.30/32), and the traffic goes through PL interface ipw_data_sp instead of other interfaces, the operator can add a new route in PL to achieve this functionality.

The configuration is performed by using ECLI, and it takes effect after the related PL reboot.

For more information about these traffic interfaces, refer to IPWorks Network Connectivity Overview.

1.1   Prerequisites

This section describes the prerequisites, which must be fulfilled before using the procedure.

1.1.1   Conditions

The following conditions must apply:

2   Procedure

This section provides the following topics:

2.1   Add Route for IPWorks PL Node

To add a new route for IPWorks PL node, do the following:

This example guides the user to add a route for 10.0.50.30/32 (from remote network) to use the route interface ipw_sig_sp as the default route for PL-3. In this example, the startup command name is set_new_route_ipv4.

The configuration is different depending on whether the PL-3 is fixed PL or floating PL.

  1. Log on to an SC node:

    #ssh <UserName>@<SC IP Address>

  2. Start an ECLI session:

    #/opt/com/bin/cliss

  3. Navigate to the MO EvipCommandDefinition:

    >dn ManagedElement=<Node Name>,Transport=1,Evip=1,EvipDeclarations=1,EvipCommandDefinition=1

  4. Enter configuration mode:

    (EvipCommandDefinition=1)>configure

  5. Add the startup command to add a new route:

    (config-EvipCommandDefinition=1)>EvipCommand=set_new_route_ipv4

    (config-EvipCommand=set_new_route_ipv4)>command="ip route add 10.0.50.30/32 dev ipw_sig_sp"

    (config-EvipCommand=set_new_route_ipv4)>commit

  6. Add a command to the attribute commandsForAllUndesignated of the MO EvipCluster:

    (EvipNode=3)>dn ManagedElement=<Node Name>,Transport=1,Evip=1,EvipDeclarations=1,EvipCluster=1

    (EvipCluster=1)>configure

    (configEvipCluster=1)>commandsForAllUndesignated="4:set_new_route_ipv4"

    (config-EvipCluster=1)>commit

    (EvipCluster=1)>show -v commandsForAllUndesignated

    commandsForAllUndesignated
    "4:set_new_route_ipv4"
    

    (EvipCluster=1)>exit

  7. Log on to each PL, and then reboot the them to make the change take effect:

    Take PL-3 as an example:

    #ssh pl-3

    #shutdown -r now

2.2   Remove Route from PL Node

This example guides the user to remove the route for the PL-3 node.

  1. Navigate to the MO EvipCluster:

    >dn ManagedElement=<Node Name>,Transport=1,Evip=1,EvipDeclarations=1,EvipCluster=1

  2. Enter the configuration mode:

    (EvipCluster=1)>configure

  3. Remove the command (for example, "4:set_new_route_ipv4") from the attribute commandsForAllUndesignated of the MO.

    (config-EvipCluster=1)>no commandsForAllUndesignated="4:set_new_route_ipv4"

    (config-EvipCluster=1)>commit

    (EvipCluster=1)>show -v commandsForAllUndesignated

    commandsForAllUndesignated
     "0:flush_route_cache"
     "1:flush_ipv6_default"
     "2:set_default_route_ipv4_sig"
     "3:set_local_port_range"

  4. Log on to each PL, and then reboot them to make the change take effect.

    Take PL-3 as an example:

    #ssh pl-3

    #shutdown -r now

2.3   Remove eVIP Command from Command List

To remove a command from command list, do the following:

Note:  
Make sure that the command to be removed is not used by any other PL.

  1. Navigate to the MO EvipCommandDefinition:

    >ManagedElement=<Node Name>,Transport=1,Evip=1,EvipDeclarations=1,EvipCommandDefinition=1

  2. Check the configuration:

    (EvipCommandDefinition=1)>show

    For example:

    EvipCommandDefinition=1
       evipCommandDefinitionId="1"
       EvipCommand=flush_route_cache
       EvipCommand=flush_ipv6_default
       EvipCommand=set_local_port_range
       EvipCommand=set_default_route_ipv4_sig
    
    

  3. Enter configuration mode:

    (EvipCommandDefinition=1)>configure

  4. Remove a startup command:

    For example:

    (config-EvipCommandDefinition=1)>no EvipCommand=set_new_route_ipv4

    (config-EvipCommandDefinition=1)>commit -s

    (config-EvipCommandDefinition=1)>end

    Note:  
    If the command is used by EvipCluster, an error message will be prompted to indicate that the command is in use:

    (config-EvipCommandDefinition=1)>commit

    ERROR: Transaction validation failed with error code: ComFailure

    [evipCommandId=set_new_route_ipv4,evipCommandDefinitionId=1,evipDeclarationsId=1,evipId=1] Command definition is in use

    To fix this problem, the operator needs to first remove the command definition from EvipCluster .


  5. Exit the ECLI session:

    (EvipCommandDefinition=1)>exit



Copyright

© Ericsson AB 2017, 2018. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    Configure Route for IPWorks PL Node