On 2/17/21 5:00 PM, Jarrod Johnson wrote:
Sorry, my control button was stuck and I sent bad messages.
The confsion would be hostA, hostA needs ot have fully qualified interface name.
Yes. Thanks! It works indeed when fully qualifying both ports:
port=Ethernet1
port=Ethernet49/1
Seems obvious now ;-)
Thanks again
--
TH
-----Original Message-----
From: Jarrod Johnson
Sent: Wednesday, February 17, 2021 10:59 AM
To: xcat-user@lists.sourceforge.net
Subject: RE: [xcat-user] [External] Switch based discovery with mix of splitted
and non splitted ports
-----Original Message-----
From: Thomas HUMMEL <thomas.hum...@pasteur.fr>
Sent: Wednesday, February 17, 2021 10:32 AM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] [External] Switch based discovery with mix of splitted
and non splitted ports
On 2/17/21 3:47 PM, Thomas HUMMEL wrote:
On 2/17/21 3:23 PM, Christian Caruthers wrote:
Long ago (>10years) I had a similar issue, w/ SMC switches I believe.
Putting the exact output from snmpwalk (e.g. "Ethernet49/1")fixed it
for me then.
Thanks. I'm trying it.
Well this has not worked, at least stating
1 for hostA
Ethernet49/1 for HostS
Maybe I should try Ethernet1 for hostA as well (though I never had to do so).
--
TH
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872
-----Original Message-----
From: Thomas HUMMEL <thomas.hum...@pasteur.fr>
Sent: Wednesday, February 17, 2021 08:56
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] [External] Switch based discovery with mix
of splitted and non splitted ports
On 2/17/21 2:41 PM, Christian Caruthers wrote:
What do you see if you run (assumes you're using SNMPv1 & "public"
community string):
snmpwalk -v 1 -c public {SWITCH_NAME} .1.3.6.1.2.1.31.1.1.1.1
This should show how the switch reports the ports.
As a matter of fact, it reports (please see attachement) as Ethernetn/p.
Still the / or dotted syntax worked previously (granted not on the
same switch model nor the same xCAT version)
Thanks
--
TH
Regards,
Christian Caruthers
Lenovo Professional Services
Mobile: 757-289-9872
-----Original Message-----
From: Thomas HUMMEL <thomas.hum...@pasteur.fr>
Sent: Wednesday, February 17, 2021 08:35
To: xcat-user@lists.sourceforge.net
Subject: [External] [xcat-user] Switch based discovery with mix of
splitted and non splitted ports
Hello,
Currently, I'm using xCAT 2.16.1 on CentOS 8.2 to provision CentOS
8.3 stateless nodes using switch based discovery.
I've been doing this for many years with success.
I always did that in either one of the 2 following cases :
a) no switch port were using splitters
b) all switch ports were using splitter
For b) I did successfully use either the n/x or the n.x syntax
Today, I encountered what may seem an xCAT issue (not sure though,
it could be a switch configuration issue) for it is the first time
I've got a switch where I mix direct and split port attachement.
The actual switch is an Arista 7050TX-72Q: 48x 1/10GbE (RJ 45) and
6x 40GbE, where all nodes are rj45 attached except one which is
connected using one of the 4 link of a 40G port using a splitter
What happens is the following :
a) nodeA on port 1 was previously provisionned using switch-based
discovery without any problem
b) I set up the node definition for nodeS which is connected to port
49.1 (I used this dot-based syntax)
-> nodeS is discovered with the name of nodeA and nodeA is assigned
nodeS mac adress
so things get mixed up.
Can you help me figure out
- what syntax is the canonical one for split ports
- if this is an xCAT problem or a switch problem
?
Thanks for your help
--
Thomas HUMMEL
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/list
in
fo/xcat-user__;!!JFdNOqOXpB6UZW0!7dZN6eQ_2yzAFzPWZ34yOdGlqCWFB4iCVf7
6j
SJL0nECAzYU9o_0J_VEBrr8ZTP_IWunXQ$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/list
in
fo/xcat-user__;!!JFdNOqOXpB6UZW0!7dZN6eQ_2yzAFzPWZ34yOdGlqCWFB4iCVf7
6j
SJL0nECAzYU9o_0J_VEBrr8ZTP_IWunXQ$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listi
nfo/xcat-user__;!!JFdNOqOXpB6UZW0!4L860p0BxToiFqFrQSusQlMBcyO1TKI6a1U
cHmfl0WbvnDx0rd4v36NRFmdy1CgQHvozdA$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listin
fo/xcat-user__;!!JFdNOqOXpB6UZW0!82Oner-rnYhRatWr5T7faTINlaY-ExAlNFnmY
igaIOrdTUWJlzQ7l2D7uue5ZZWXcJSa1w$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/xcat-user__;!!JFdNOqOXpB6UZW0!4BDQQOQTT7ttjlPw4eDqrE25BdsQr6Slgipmt5TDMCQUK2pdNlcOuyMtwim5AFZBhcGe8A$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/xcat-user__;!!JFdNOqOXpB6UZW0!4BDQQOQTT7ttjlPw4eDqrE25BdsQr6Slgipmt5TDMCQUK2pdNlcOuyMtwim5AFZBhcGe8A$
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
