I'm working on deploying a tried and tested xcat database that was successful 
on Cisco Catalyst switches. The MN is now hooked up to a Cisco Nexus 5672U 
running Nexus 6000 IOS and manages a ToR fex switch attached to IMM on the 
nodes and a partnered 5624Q connected to the mellanox 10gb ports on the nodes.
                                                                         RACK 1
xCAT MN -->5672U (mstrswitch)  --> 5624Q (switch 1 )
                                                                  --> 2248TP-E 
(FEX 101)

I've tried lots of configurations and have attached the configurations I have 
right now to this e-mail. I'm getting extremely slow discoveries. One node is 
discovered every 10-15 minutes. The nodes sometimes do not discover at all and 
sit in a limbo where they are in genesis kernel with the correct hostname but 
xCAT does not see them. Similar happens with nodes that show the blue discover 
beacon, they have their hostname and correct static IP but xCAT does not see 
the device as discovered and rpower, rbeacon and rinv time out. I can ping and 
do a name resolution on the node but it does not respond to rpower commands.

These are some of the messages worth noting that I receive on journal

Apr 30 14:37:30 serverx.cluster xcat[1813]: xcatd: Processing discovery request 
from 172.16.1.4
Apr 30 14:37:31 serverx.cluster xcat[1813]: Discover info: configure static BMC 
ip:r1c1n1p1i1-bmc for host_node:r1c1n1p1i1.
Apr 30 14:37:31 serverx.cluster xcat[8003]: xCAT: Allowing rspconfig to 
r1c1n1p1i1 ip=r1c1n1p1i1-bmc for root from localhost
Apr 30 14:37:45 serverx.cluster xcatd[1813]: Discovery worker: switch instance: 
nodediscover instance: Failed to notify 172.16.1.4 that it's actually r1c1n1p1i1



Apr 30 14:37:46 serverx.cluster xcat[1813]: Discover info: configure static BMC 
ip:r1c1n1p1i1-bmc for host_node:r1c1n1p1i1.
Apr 30 14:37:46 serverx.cluster xcat[8029]: xCAT: Allowing rspconfig to 
r1c1n1p1i1 ip=r1c1n1p1i1-bmc for root from localhost
Apr 30 14:38:01 serverx.cluster xcatd[1813]: Discovery worker: fsp instance: 
nodediscover instance: Failed to notify 172.16.1.4 that it's actually 
r1c1n1p1i1.



I'm able to run snmpwalk on these switches and it returns with the interface 
information. I've narrowed down a lot of this to the nexus switch and things 
work entirely different on these switches. Can someone chime in on what I could 
be missing from my switch configuration?


Thank you,
Edward Nunez
Lead Integration Network Engineer| Certified : CCNA R&S
SHI International Corp.| [email protected]<mailto:[email protected]> | Tel: 
1(732)564-8188

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to