https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081264#M49654 Deleting the NIC in YAST solved the problem - confusing was that the deleted NIC didn't disappear in YAST it changed the status to "no configured" Mon, 26 Nov 2007 01:23:52 GMT cscherb 2007-11-26T01:23:52Z https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081262#M49652 How to prevent Systems Management Homepage / Agents running on Suse Linux Enterprise Server to issue an alarm for a link failure on a ethernet nic which is intentionaly no used ? Sat, 24 Nov 2007 13:00:45 GMT https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081262#M49652 cscherb 2007-11-24T13:00:45Z https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081263#M49653 If you disable the NIC (presumably through YaST) then you will no longer have a link failure... Sat, 24 Nov 2007 20:12:14 GMT https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081263#M49653 David Claypool 2007-11-24T20:12:14Z https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081264#M49654 Deleting the NIC in YAST solved the problem - confusing was that the deleted NIC didn't disappear in YAST it changed the status to "no configured" Mon, 26 Nov 2007 01:23:52 GMT https://community.hpe.com/t5/server-management-systems/smh-sles-nic/m-p/5081264#M49654 cscherb 2007-11-26T01:23:52Z