× 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.



My Last 4 HMC/Virtual Ethernet issues were all due to VLAN id mismatches.
I'm looking for some good notes , tips for HMC VLAN id management.

First, confirming all the various uses for Virtual Ethernet, VLAN id, and which can / cannot be shared.
1)Virtual Line Descpitions for LPAR to LPAR comm (shared)
2)Virtual Line for Ethernet Bridge (shared)
3) SST LAN adapter for HMC network installs (not shared)
4) SST LAN adapter for remote virtual optical (not shared)
5) others?
Second, you cannot see the VLAN id from iSeries partition, so I'm thinking of making the VLAN id match the adapter id.
Do think IBM will ever add so you can see the VLAN id from i5/OS?
If this works, then if your displaying a CMN resource, adapter id equal VLAN id.
By default, virtual adapters 1 and 2 are usually serial.
Virtual Ethernet numbers usually will start at 3, 4, 5 etc.
So VLAN ID will be set to match the adapter number, 3,4,5,etc.

Third, I had a mismatch between the HMC profile VLAN id and the actual VLAN id, viewing through properties or DLPAR.
IPLing to fix the above did not correct the difference. Partition needed to be shutdown, activated via HMC.

Any thoughts from the group.



Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.