80 likes | 188 Views
NUSA Overview. Mike Rykowski IT-TNS. The old days…. Complaint or event would get TNS’s attention TNS would track down user port and shut it off TNS would try to contact user After host gets fixed, user would try to contact TNS TNS would then turn port back on when they can.
E N D
NUSA Overview Mike Rykowski IT-TNS
The old days… • Complaint or event would get TNS’s attention • TNS would track down user port and shut it off • TNS would try to contact user • After host gets fixed, user would try to contact TNS • TNS would then turn port back on when they can
Barely Treading Water • The process was highly labor intensive • TNS personnel spent lots of time per event • Useful information to fix problem was not getting to the users • Just as long as the number of events was small, TNS was getting by…
Then Came Welchia/Blaster • About 900 ports were shutoff in August 2003, all manually • Most of TNS’s resources were used for this one event • We were not treading water any more, something had to change
Here comes NUSA • Network User Status Agent • Main goals of NUSA: • Notify system administrators of events via a contact DB • Apply actions to events automatically • Give system administrators the power to resolve events (turn ports on, etc.)
Possible Future Enhancements to NUSA • Self scanning • Expand to more than security related information • Port level information (port speed, duplex, location, etc.) • Network Statistics/Status • Any network information that system admins might find useful
How to access NUSA • Web based utility • Send email to: nsg-net@northwestern.edu • Provide: • Subnet(s) • Mailing list/email address • Netid(s) of contacts