[gpfsug-discuss] How do I add a new IP to the configuration?

[KG]

Hi

The CES service on protocol nodes binds to all available addresses
including fixed IP addresses.

You would need to add a virtual interface on existing interface (or setup a
new interface) and assign IP to it (from the new subnet that you wish to
add).
After that add IPs to CES pool.
The CES pool will then attach to newly added interface. You may have to
restart the CES service/protocol node daemon.

On Sat, Jan 22, 2022 at 5:32 AM Alec <anacreo at gmail.com> wrote:

> It sounds like you are attempting to add multiple networks to the same
> interface.
>
> So if your existing ESS is not on a network that is routed to your new
> clients then you'll need to do one of the following:
>
> 1) Establish routing between the new ESS client IP's and your existing ESS
> servers.
> 2) Add a Virtual Interface with that network's VLAN on it (or the VLAN of
> a network that is routed to the new client).
> 3) Configure new interfaces on the ESS with the new network.
>
> No one else answered, and unfortunately I don't own an ESS so I can't tell
> you had to do step #2.
>
> But typically a scenario would look like this:
>
> ESS
>   1st interface IP is 192.168.1.150 subnetmask 255.255.0.0 and default
> gateway 192.168.0.1
>
>   With this anything in the 192.168.x.x address space could be added to
> the 1st interface as they are all local to that address.
>
>   Now you're presented with needing to offer data to something on IP
> 10.1.20.30, and 192.168.0.1 doesn't know how to reach that interface, or we
> don't want that data flowing across routes.
>
>   If we don't want to add another physical interface to ESS we have to get
> into VLAN configuration (Virtual LAN)...
>
>   Now we say VLAN 0 is going to be 192.168.0.0 network and it's the
> default network (anything not tagged goes there)...
>   And the network team has 10.0.0.0 network on VLAN 10...  So we ask the
> network team to add VLAN 10 to our 1st interface.  It should now have VLAN
> 0 and VLAN 10.
>
>   I don't know how but somehow in the ESS you're now going to have to add
> a new virtual adapter that is bound to VLAN 10... and since the first
> interface didn't have VLAN's it will continue to use the now default VLAN 0.
>
>   Once we have that 2nd virtual adaptor on VLAN 10 we can define it as...
>     2nd interface (still on the 1st physical interface, but a virtual
> adapter) IP is 10.240.1.150 (let's say 10.240 is going to be the ESS's
> portion of the 10 network)..  and we define the subnetmask 255.0.0.0 and
> maybe no route...
>
> It really needs for your network team to define how they want you to
> proceed and then figure out how the ESS can be configured to consume that
> network design.
>
> What you can't do is straight up put two IP's from different subnets on
> the same interface.  Essentially the logical interface will look at it's
> IP, it's Subnet combine the values with your new IP and say, hey wrong
> network.
>
> Alec
>
> On Fri, Jan 21, 2022, 7:17 AM Jesus Mora Luna <jesus.mora at 4ks.mx> wrote:
>
>> Good day
>>
>>
>>
>> Please can you help me to solve a problem that I have with the
>> modification of an ESS to add a new IP to share the volumes in a new
>> network.
>>
>>
>>
>> The issue is that I already tried to add the IP with the corresponding
>> commands and what it tells me is that it does not find the network, I also
>> tried to add the IP directly to one of the Ethernet interfaces and it does
>> not let me do it.
>>
>>
>>
>> Where can I find or can you share the procedure if it is available to add
>> a new IP
>>
>>
>>
>> Thanking you in advance for your attention to my request, I look forward
>> to your response and comments.
>>
>>
>>
>> Greetings and thanks
>>
>>
>>
>>  *Jesús Mora Luna  *
>>
>> Servicios Continuos
>>
>> System Engineer
>>
>> Jesus.mora at 4ks.mx
>>
>> Oficina  55 41636541
>>
>> Móvil  55 14853753
>>
>> Ignacio Allende N° 21
>>
>> Ampliación Torre Blanca Miguel Hidalgo, CDMX  11289
>>
>> www.4ks.mx
>>
>>
>>
>> [image: Descripción: Descripción: Descripción:
>> https://docs.google.com/uc?export=download&id=11HlTv0TDj5BTu4hVCM-2rNkHWnmxAH5E&revid=0ByZwGRTUTp29c0VQdWVKWVRaT0dkUEVDK3hRckc4MCtJWVZnPQ]
>>
>>
>>
>> [image: Descripción: Descripción: Descripción:
>> https://docs.google.com/uc?export=download&id=1NomENnxEOLpSFfGyStQMonSuz83p33aL&revid=0ByZwGRTUTp29NTlqVzMyMEVhQnNnNUt5eGpzY3M3MGNGeXZ3PQ]
>>
>>
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at spectrumscale.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20220122/2a6b2aec/attachment-0002.htm>