Announcements

News about the SCC offer: Service News
Report malfunction: via ITB or the SCC ticketing system.
 In case of failure of this website: scc.fail
Please note! To view all incidents, planned maintenance, or internal KIT notices at the SCC, you must be logged into the KIT intranet. If you are a KIT member, log into the KIT intranet via remote access (VPN).
Stand: 13.10.2025 03:20:04

Incidents

 2025-08-11 20:00

Performance Issues Firewall Stufe-2 and Extranet


DescriptionPerformance issues have been observed since the firewall software upgrade on August 11, 2025.

Individual connections require too many resources, which disadvantages other users.
These users experience higher latencies, which can lead to slow websites, file transfers, etc.

As a first step, the software update suggested by the manufacturer was installed on September 16. This has not yet led to any actual improvement. Troubleshooting together with the manufacturer is ongoing.
Affected usersUsers of Firewall Stufe 2 (Area D) und Extranet (Area B)
Exists since2025-08-11 20:00

Maintenance

  2025-06-24 10:00 - 2025-10-21 13:00

KIT-AD: Migration of DC to Windows Server 2025 - Old DC will be shut down on October 21, 2025 (UPDATE, 08.10.25)


UPDATE, 08.10.25, 2pm
The old DC will not be shut down until October 21, 2025.

_ _ _ _ _ _ _ _ _ _
Step 3:
Monday, 21.10.2025, 10:00-13:00
Switching off old domain controllers
_ _ _ _ _ _ _ _ _ _

DESCRIPTION
The domain controllers kit-dc-20, kit-dc-21, kit-dc-22 and kit-dc-23 are no longer in operation.

IMPACT / IMPORTANT
If you address one of these DCs directly by name, you must adapt your configuration!

NOTE / RECOMMENDATION
To use the KIT-AD via LDAP, we recommend the dedicated LDAP access, see "LDAP access to KIT-AD" at https://www.scc.kit.edu/dienste/9224.php



_ _ _ _ _ _ _ _ _ _
Original message dated June 11, 2025
_ _ _ _ _ _ _ _ _ _
The domain controllers of the Active Directory at KIT (KIT-AD) will be successively converted to Windows Server 2025. The migration will take place gradually and is expected to be completed by the end of September 2025:

1. Installation of additional domain controllers (kit-dc-24.kit.edu, kit-dc-25.kit.edu, kit-dc-26.kit.edu und kit-dc-27.kit.edu)

2. Switching the BigIP F5 (kit-ad.scc.kit.edu) to new DCs

3. Switching off the old domain controllers (kit-dc-20.kit.edu, kit-dc-21.kit.edu, kit-dc-22.kit.edu, kit-dc-23.kit.edu)



P L A N N I N G
_ _ _ _ _ _ _ _ _ _
Step 1:
Monday, 24.06.2025, 10:00-13:00
Starting up new domain controllers
_ _ _ _ _ _ _ _ _ _

DESCRIPTION
Initially, three new domain controllers will be put into operation:

IMPACT
No interruptions to the ongoing operation of the KIT-AD are expected.
No changes or adjustments by service providers or users are required.

_ _ _ _ _ _ _ _ _ _
Step 2:
Monday, 01.07.2025, 10:00-13:00
Switching the BigIP F5 (kit-ad.scc.kit.edu) to new DCs
_ _ _ _ _ _ _ _ _ _

DESCRIPTION
The new domain controllers are addressed for LDAP access to kit-ad.scc.kit.edu.

IMPACT
No interruptions to the ongoing operation of the KIT-AD are expected.
No changes or adjustments by service providers or users are required.

_ _ _ _ _ _ _ _ _ _
Step 3:
Monday, 30.09.2025, 10:00-13:00
Switching off old domain controllers
_ _ _ _ _ _ _ _ _ _

DESCRIPTION
The domain controllers kit-dc-20, kit-dc-21, kit-dc-22 and kit-dc-23 are no longer in operation.

IMPACT
If you address one of these DCs directly by name, you must adapt your configuration!

NOTE
To use the KIT-AD via LDAP, we recommend the dedicated LDAP access, see https://www.scc.kit.edu/dienste/9224.php.
  2025-10-10 20:00 - 2025-10-13 08:00

Power outage at SCC - South Campus: IT services partially available


CAUSE
In accordance with DGUV Regulation 3 – Accident Prevention Regulations for Electrical Systems and Equipment – Facility Management (FM) is carrying out maintenance and testing of the electrical systems in the SCC building (South Campus, Building 20.20/21).

AFFECTED by the power outage
South Campus buildings: 20.20 & 20.21 (entire buildings)
The SCC offices and computer rooms on the South Campus will be completely affected. The power supply will be completely shut off in the affected buildings.

MEASURES
Shutting down the power supply requires connecting selected systems to a backup power supply so that basic IT services can be ensured.
This measure and the redundancy of IT services mean that many central IT services will remain available.

However, a few systems will have to be shut down, meaning that the following IT services will be unavailable.

AFFECTED IT services
IMPACT on affected IT services
  • Fri, Oct. 10, 2025, evening until Mon, Oct. 13, 2025, morning: License server scclic7.scc.kit.edu
    • License server scclic7.scc.kit.edu for providing technical scientific applications is unavailable.
    • Affected software packages: Abaqus, COMSOL, Creo / ProEngineer, and Star-CD/Star-CCM+.


* Fri, Oct 10, 2025, evening until Mon, Oct 13, 2025, morning: Backup with IBM SP on the South Campus
  • During the specified period, the backup service with IBM SP (formerly TSM) on the South Campus will NOT be available. Backups and restores of data cannot be performed on the South Campus.
* Affected users will be informed separately by the backup team.
  • Fri, Oct. 10, 2025, evening until Mon, Oct. 13, 2025, morning: Parts of bwUniCluster
    • bwUniCluster 2.0 Level 2 is affected
    • Affected HPC users will be informed in more detail by the HPC team about the effects during the power outage
    • Details for HPC users
      • The Ice Lake partitions of bwUniCluster 3.0 will not be available
      • Workspace on Flash (full flash pfs) will not be available
      • The x86 servers of the Future Technology Partition (FTP) will not be available
      • JobMon will not be available

  • Fri, Oct. 10, 2025, evening to Mon, Oct. 13, 2025, morning: Server housing
    • Affected institutions whose server systems we host on Campus South have already been informed about the shutdown.
    Stand: 13.10.2025 05:06:18

    Announcements

     2025-10-06 08:03

    Note: Problems with encryption after Office update


    After the Office update to Office 2024, problems may occur when encrypting emails.
    This may be because the personal certificate is incorrectly integrated and therefore the personal S/MIME certificate is not used for encryption after the update. You can fix the problem by reintegrating your personal certificate.
    Instructions:
    * https://docs.ca.kit.edu/geant-tcs/de/user/#install-certificate
    * https://docs.ca.kit.edu/guides/de/configure_outlook/

     2025-01-07 11:14

    Note: Misbehavior between Windows 11 Update 22H2 in conjunction with specific network switch type


    UPDATE, 07.01.25
    In 2024, some components could be replaced, but there are still components in use where the malfunction could occur.
    _ _ _

    A misbehavior has been detected between a network switch type used at KIT South Campus and a Windows 11 update (version 22H2). Due to this misbehavior, the network port on the switch is automatically switched off.
    As a result, the network connection or network access for the connected device is no longer available.
    To enable network access, the data socket used must be communicated to the IT representative / IT admin of the OU so that he can apply for enabling via the SCC network team.

    WORKAROUND
    To prevent the network port from being switched off, the LLDP service can be disabled under Windows. This can be done manually (computer-specific) under "Network adapter properties". Furthermore, the SCC provides the group policy "SCC-FMC-LLDP_disable", which can be linked to the computer accounts and automatically disables LLDP under Windows. Unlocking of already blocked ports can be requested from the network team via the IT representative/IT admin of the OU.

    AFFECTED
    Windows 11 Nutzer mit Updatestand 22H2 (und voraussichtlich höher) in Verbindung mit spezifischem Netzwerk-Switchtyp

    TECHNICAL DETAILS
    As of Windows 11 update level 22H2, sending Link Layer Discovery Protocol (LLDP for short) packets on a specific type of switching causes a network loop detection service to trigger on the switch, automatically blocking the network port.

    (translated with DeepL.com)