Re: Renaming a LIND -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Doug:

You should be able to rename the line descriptions without too much trouble, you _*will*_ have to vary them off first.

Procedure:
wrkcfgsts *lin
Option 2 Vary Off
Option 8 Work with Description
Option 7 Rename
F12 back to wrkcfgsts *lin
Option 1 Vary on.

You don't mention any iASP so there should not be any intrigue there, nor do you mention any load balancing. If there is load balancing you may have to get into the graphical interface and reset it. If there is load balancing I would suspect that you might need to restart TCP/IP so some care should be used.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC

On 11/16/2010 1:11 PM, Hart, Doug - EI wrote:

I want to rename the line descriptions for the Ethernet lines on my LPARs. The names are old and meaningless and I would like to set a new standard. My question is can anyone think of anything that might break if I do this? I can't. I have checked and no code is referencing the names. Any newer code uses the Alias name. Any use of these lines by *ANYNET or *HPRIP (EE) should be OK. Since these are all 1G 5706 NICs no native SNA should be in use over them.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.