StorageGRIDは、制限されたIPの重複によりストレージ接続が低下していると報告しています
環境
- NetApp StorageGRID
- NetApp SG6160およびSG5812/SG5860
問題
- StorageGRID GRID Managerから以下の警告が報告されました：
Storage appliance storage connectivity degradedThere is a problem with one or more connections between the compute controller and storage controller.
- EシリーズポートにI/Oが表示されません：
STATE-CAPTURE-DATA -> ionShow(99,0,0,0,0,0,0,0,0,0)
-> chall 0
chAll (Tick 0021928819) ==> 03/26/26-13:07:36
4000-A 08.90.09.00.....Channels.....:...........Target...........:............Initiator..........: Link :ITN :..........IOs..........:ITN :............IOs...........:.........Busy.........Idle. Ch H/D STP Down :cnt : Open Completed Errs :cnt : Qd Open Completed Errs: Ms Ms---- --- --- ---- :--- :----- ---------- ----- :--- :--- ----- ---------- -----: ------------ ------------- 0 Drv SAS 0 : 0 : 0 0 0 : 13 : 0 9 4048487 0: 4763199 152128 1 Drv SAS 0 : 0 : 0 0 0 : 13 : 0 0 4198117 0: 4774977 140351 2 Hst iSC 0 : 4 : 0 0 0 : 0 : 0 0 0 0: 0 4915329 3 Hst iSC 0 : 8 : 5 4864197 0 : 0 : 0 0 0 0: 4804213 111116 4 Drv iSA 0 : 0 : 0 0 0 : 1 : 0 0 1 0: 0 4915329
- StorageGRID
ifconfig接続不良のためインターフェースIPを表示しない：
e0a: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::d239:eaff:febc:ed8a prefixlen 64 scopeid 0x20<link> ether d0:39:ea:bc:ed:8a txqueuelen 1000 (Ethernet) RX packets 14071 bytes 1407100 (1.3 MiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 65309 bytes 6467863 (6.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0e0b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.x.x.x netmask 255.255.255.255 broadcast 0.0.0.0 inet6 fe80::d239:eaff:febc:ed89 prefixlen 64 scopeid 0x20<link> ether d0:39:ea:bc:ed:89 txqueuelen 1000 (Ethernet) RX packets 2780450573 bytes 3631616715793 (3.3 TiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 4972444852 bytes 6799848032561 (6.1 TiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0- StorageGRIDの
var/local/log/syslog.logで接続に失敗しました：
2026-03-03T12:22:53.800603+00:00 localhost sga-san-conn-manager: No candidate network configurations were able to connect to on interface e0a2026-03-03T12:22:53.800633+00:00 localhost sga-san-conn-manager: Writing status file /run/sga-san-conn-manager-status.json2026-03-03T12:23:23.793628+00:00 localhost sga-san-conn-manager: Interface e0a needs configuration2026-03-03T12:23:23.794905+00:00 localhost sga-san-conn-manager: Applied Candidate CIDR x.x.x.x/32 to interface e0a for connction to remote x.x.x.x2026-03-03T12:23:23.794967+00:00 localhost sga-san-conn-manager: Attempting to connect iSCSI path to x.x.x.x2026-03-03T12:23:26.852103+00:00 localhost sga-san-conn-manager: Connection to candidate address for 192.168.130.101 failed. Errno 113: No route to host2026-03-03T12:23:26.864490+00:00 localhost sga-san-conn-manager: Unable to create any connection to x.x.x.x2026-03-03T12:23:26.871651+00:00 localhost sga-san-conn-manager: Failed to connect to iSCSI target 192.168.130.101:3260 Errno 107: Transport endpoint is not connected2026-03-03T12:23:26.871709+00:00 localhost sga-san-conn-manager: Error while performing discovery on x.x.x.x2026-03-03T12:23:26.887347+00:00 localhost sga-san-conn-manager: Candidate CIDR x.x.x.x/x on interface e0a did not successfully connect to remote x.x.x.x2026-03-03T12:23:26.887437+00:00 localhost sga-san-conn-manager: Removing all IPs from interface e0a2026-03-03T12:23:26.887491+00:00 localhost sga-san-conn-manager: No candidate network configurations were able to connect to on interface e0a