We have ATT help for tomorrow Aug 1st to activate VSS on the two core 6509 switches.
The affects should be minimal, none during the day, with only a very small impact late when the final configuration command is entered.
Only systems that may be affected are those connected directly to one of these switches and there are few services connected that way.
Jamie Voyles
HSB 119
217 206-7840
|
|
|
Email/Voicemail Maintenance – 2:30pm |
|
In response to reported issues with voicemail, we will be rebooting one of our mailbox servers at 2:30pm. Users may be disconnected from email during this reboot; however, no data will be lost. Users may restart Outlook or Webmail immediately to be reconnected. If you have any questions or concerns, please contact The Technology Support Center at 217/206-6000 or techsupport@uis.edu. |
|
|
The Camtasia Relay service is not working. The service is responding with a:
HTTP Error 503. The service is unavailable.
The Relay Manager service was stopped. Starting it or restarting IIS did not fix the problem.
I will reboot the server to see if that fixes the problem.
We have a tentative date set with the engineer from ATT to assist in virtualizing our two core switches. The date is next Wednesday July 24. We will reconfigure the two switches to act as one, this will make the network more redundant in that there won’t be any delay if we one of the two switch should fail. Additionally since we have most of the edge switches connected to both of the core switches the VSS will double the bandwidth to the edge switch. This will also allow us to configure the HA WISM2 blade so we will have redundant controllers for the wireless.
Jamie Voyles
HSB 119
217 206-7840
We have noticed that the power output on some of the Access Points is lower than it was with the old controllers. There is a setting that allows us to determine the max and min power settings, we are planning to adjust the minimum up slightly to see if that resolves the issues. The challenge is that to make this adjustment we must disable the 802.11b/g network, make the adjustment and then re-enable the network, then do the same with the 802.11a/n network. The process should only take a minute.
Jamie Voyles
HSB 119
217 206-7840
Begin forwarded message:
From: "Nye, Mark Allen" <marknye@ILLINOIS.EDU>
Date: July 11, 2013, 1:35:49 PM CDT
To: <UOFI-BOX@LISTSERV.ILLINOIS.EDU>
Subject: [UOFI-BOX] report on yesterday’s Shibboleth outage
Reply-To: U of I Box.net Staff <UOFI-BOX@LISTSERV.ILLINOIS.EDU>, "Nye, Mark Allen" <marknye@ILLINOIS.EDU>
Box’rs,
Yesterday’s UIUC Shibboleth outage was caused by a problem with the terracotta cluster engine, which is used by Shibboleth to share live session data across our Shibboleth IDP nodes. From Keith Wessel:
The standby node lost contact with the active node a couple times during the DC network work yesterday morning. The last time it did, it was half way through a re-initialization of its database. This left it in a hung and uninitialized state. We’ve only seen this once before.
By early afternoon unstable terracotta has consumed enough memory to disrupt Tomcat service on the lead Shibboleth node. The problem was reported to the ID Management group at 2:30pm, and the service was restored ~2:50pm. (Unfortunately response from service management was somewhat delayed due to a fire drill going on in DCL.)
In the short term, Keith will setup a monitor script to watch the terracotta logs and alert on this problem, so next time it can be fixed before it causes a service disruption. In the longer term, the plan is to reconfigure Shibboleth such that terracotta is not required.
best,
Mark
—–
Mark Nye (marknye@illinois.edu)
Collaborative Services Team, CITES AS
University of Illinois at Urbana-Champaign
The Authentication issues with Urbana’s Shiboleth have been resolved. We can now access Box and Webstore.
We are experiencing some problems authenticating with Urbana’s Shiboleth environment this impacts users accessing Box and Webstore. Urbana is working on resolving this issue.
The trouble has been resolved thanks to Kevin and Brian.
What appeared to have been a faulty patch, multiple certificates were loaded to all servers including the email servers. The number of Certs. caused the servers to fail to communicate with each other. We are not sure why it happened now, since the patch was released in Dec of 2012.
Jamie Voyles
HSB 119
217 206-7840
We are having issues with the VM messages being sent to the appropriate email accounts exchange is queuing them. We will keep you posted.
Jamie Voyles
HSB 119
217 206-7840
