We swapped in a different switch and see the same errors. The opensm logfile does not show any errors:
------------------------------------------------- OpenSM 3.3.5 Command Line Arguments: Daemon mode Log File: /var/log/opensm.log ------------------------------------------------- OpenSM 3.3.5 Sep 02 05:56:29 933684 [B53B8700] 0x80 -> OpenSM 3.3.5 Entering DISCOVERING state Sep 02 05:56:29 934931 [B53B8700] 0x02 -> osm_vendor_init: 1000 pending umads specified Sep 02 05:56:29 935079 [B53B8700] 0x80 -> Entering DISCOVERING state Using default GUID 0x2c90300032de1 Entering MASTER state Sep 02 05:56:29 953763 [B53B8700] 0x02 -> osm_vendor_bind: Binding to port 0x2c90300032de1 Sep 02 05:56:29 990146 [B53B8700] 0x02 -> osm_vendor_bind: Binding to port 0x2c90300032de1 Sep 02 05:56:29 990240 [B53B8700] 0x02 -> osm_opensm_bind: Setting IS_SM on port 0x0002c90300032de1 Sep 02 05:56:30 009040 [AF1DB710] 0x80 -> Entering MASTER state SUBNET UP Sep 02 05:56:30 009885 [AF1DB710] 0x02 -> osm_ucast_mgr_process: minhop tables configured on all switches Sep 02 05:56:30 014593 [AF1DB710] 0x80 -> SUBNET UP On Thu, Sep 2, 2010 at 8:56 AM, Hal Rosenstock <[email protected]> wrote: > On Thu, Sep 2, 2010 at 8:34 AM, Chuck Hartley <[email protected]> wrote: >> Hello, >> >> We installed 1.5.1 and are having problems getting the IB fabric >> working. ibv_devinfo shows the HCAs ports are ok and ibdiagnet reports >> no errors. However, ibchecknet shows that the switch ports are not >> being configured. We have never seen this before and are at a loss as >> to where the problem might be - would someone please point us in the >> right direction to look? Could it be a problem with the switch >> itself? Output from ibchecknet below. >> >> >> # ibchecknet >> Error check on lid 3 (Infiniscale-IV Mellanox Technologies) port all: FAILED >> ibwarn: [26732] dump_perfcounters: PortXmitWait not indicated so >> ignore this counter >> #warn: Lid is not configured lid 3 port 7 >> #warn: SM Lid is not configured > > Is there an SM running on your subnet ? If so, I think that the lack > of an SM could account for all of the issues mentioned here. > > -- Hal > -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
