Hmm, maybe it was a vlan thing. Maybe there was some confusion as to whether or not the SAN supported vlan, or whomever set up the SAN didn't know what a vlan was. We had an issue with an earlier security card package. We initially underspecified it and it didn't support vlans.
Basically there's always two sides to every story. "seek first to understand"
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jim Oberholtzer
Sent: Tuesday, May 28, 2019 1:54 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Why adulterate ports vs using an additional IP address? Was: Ports IP specific?
Now that is hilarious, the network won't support a SAN graphical interface?
Which by the way, any way you cut it is a requirement since you can't even create LUNs or Hosts without the ethernet attachment. (graphical or character based)
I'm thinking jealousy is the root cause.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin Taylor
Sent: Tuesday, May 28, 2019 12:40 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Why adulterate ports vs using an additional IP address? Was:
Ports IP specific?
That's the way everything is, and why I keep everything I can within IBMi.
For the SAN, they didn't want to give me the IP address because they said their network couldn't support my SAN.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Tuesday, May 28, 2019 12:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Why adulterate ports vs using an additional IP address? Was:
Ports IP specific?
Basically that came down to my last question: drudgery with the network people.
Did the Windows people object to the address because they wanted the SAN only for themselves or are they just that <word for a tight opening normally reserved for passing waste> on IP addresses?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
