Enthusiast
Enthusiast

ESX 5.1 Hosts disconnected from HA/DRS Cluster

Hello,

Can someone please help me...

ESX 5.1 hosts got disconnect from HA/DRS enabled cluster, but hosts is up and able access via ILO

after some time, i am able to connect host, not sure what is issue here

I can see this error in my vmkwarning.log file.

2013-09-25T15:26:03.953Z cpu19:16435)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T15:26:27.076Z cpu15:3988854)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015c62200 (ID=0x2326): Unknown VSCSI filter

2013-09-25T15:26:27.076Z cpu15:3988854)WARNING: VSCSI: vm 3988855: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-25T15:26:27.373Z cpu14:3988864)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T15:26:27.373Z cpu14:3988864)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T15:42:04.976Z cpu16:16436)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T15:42:04.976Z cpu16:16436)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:04:20.135Z cpu19:4004414)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015c62200 (ID=0x2329): Unknown VSCSI filter

2013-09-25T22:04:20.135Z cpu19:4004414)WARNING: VSCSI: vm 4004415: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-25T22:04:20.521Z cpu12:3611207)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:04:20.521Z cpu12:3611207)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:19:07.308Z cpu15:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:19:07.308Z cpu15:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:19:35.482Z cpu12:4004939)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015c62200 (ID=0x232c): Unknown VSCSI filter

2013-09-25T22:19:35.482Z cpu12:4004939)WARNING: VSCSI: vm 4004940: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-25T22:19:36.045Z cpu12:4004975)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:19:36.045Z cpu12:4004975)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:34:07.752Z cpu12:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:34:07.752Z cpu12:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:49:34.971Z cpu12:4006022)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015c62200 (ID=0x232f): Unknown VSCSI filter

2013-09-25T22:49:34.971Z cpu12:4006022)WARNING: VSCSI: vm 4006023: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-25T22:49:35.252Z cpu18:4006031)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T22:49:35.252Z cpu18:4006031)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T23:05:37.316Z cpu12:16435)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T23:05:37.316Z cpu12:16435)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-25T23:07:43.015Z cpu15:16399)WARNING: ScsiDeviceIO: 1224: Device naa.60060160f8cc2e00107986f044dfe211 performance has deteriorated. I/O latency increased from average value of 1056 microseconds to 26785 microseconds.

2013-09-26T03:08:58.942Z cpu20:4016348)WARNING: UserLinux: 1331: unsupported: (void)

2013-09-26T03:26:09.452Z cpu16:3115785)WARNING: VisorFS: 2176: Refusing write to read-only visorfs file /etc/localtime by process vi.

2013-09-26T04:03:33.104Z cpu12:16436)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T04:03:33.104Z cpu12:16436)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:37:58.449Z cpu14:4027215)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015cb31c0 (ID=0x2332): Unknown VSCSI filter

2013-09-26T07:37:58.449Z cpu14:4027215)WARNING: VSCSI: vm 4027216: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-26T07:37:58.787Z cpu19:4027224)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:37:58.787Z cpu19:4027224)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:53:32.097Z cpu22:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:53:32.097Z cpu22:16434)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:54:01.284Z cpu20:4027797)WARNING: VSCSIFilter: 299: Couldn't add filter 'cbrc_filter' to VSCSI_Handle 0x410015c71c80 (ID=0x2335): Unknown VSCSI filter

2013-09-26T07:54:01.284Z cpu20:4027797)WARNING: VSCSI: vm 4027798: 3876: Attaching filter 'cbrc_filter' on scsi0:0 failed: Not found (195887107)

2013-09-26T07:54:01.553Z cpu18:4027806)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T07:54:01.553Z cpu18:4027806)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T08:08:56.868Z cpu16:16435)WARNING: Uplink: 3075: releasing cap 0x0!

2013-09-26T08:08:56.868Z cpu16:16435)WARNING: Uplink: 3075: releasing cap 0x0!

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
4 Replies
Immortal
Immortal

Have you looked at the physical network - particulalry the ports the physical NICs or the physical NICs on the host?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
Enthusiast
Enthusiast

Hello,

Our network team confirmed that everything looks good from Network Port side, as they physically checked and confirmed.

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Enthusiast
Enthusiast

is this issue solved ? Looks like spanning tree issue.

you know nothing..
0 Kudos
Enthusiast
Enthusiast

Issue has been resolved after upgrading b2net drivers (544 FLB adapter) on all ESXi hosts.

Thank you.

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos