Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY ISSUE OF JANUARY 21, 2012 FBO #3710
SPECIAL NOTICE

70 -- Enterprise Network Monitoring and Event Correlation System

Notice Date
1/19/2012
 
Notice Type
Special Notice
 
NAICS
511210 — Software Publishers
 
Contracting Office
Social Security Administration, Office of Budget, Finance, and Management, Office of Acquisition and Grants, 1st Floor, Rear Entrance, 7111 Security Blvd., Baltimore, Maryland, 21244
 
ZIP Code
21244
 
Solicitation Number
SSA-RFI-12-1013
 
Archive Date
2/24/2012
 
Point of Contact
Deborah R Wilson, Phone: (410) 966-2818, Jane W Quinn, Phone: 4109659588
 
E-Mail Address
debbie.r.wilson@ssa.gov, jane.quinn@ssa.gov
(debbie.r.wilson@ssa.gov, jane.quinn@ssa.gov)
 
Small Business Set-Aside
N/A
 
Description
1.0 OVERVIEW AND PURPOSE This is a REQUEST FOR INFORMATION (RFI). Please Reference Number-SSA-RFI-12- 1013 when responding to this announcement. The Social Security Administration (SSA) is currently seeking to identify responsible Vendors capable of an enterprise network monitoring and event correlation system. SSA currently employs EMC IONIX (formerly SMARTS) as its primary network-monitoring platform to alert operations personnel of problems affecting SSA enterprise network (SSANet) services. Vendors with the ability to meet the requirements listed below should submit complete details. The responses must clearly state how their product provides the ability to meet the requirements. 2.0 REQUIREMENTS ( Note: ALL Listed Requirements Are Essential) 2.1 DISCOVERY & REPRESENTATION REQUIREMENTS - Perform an automated discovery to identify devices, device components, relationships and services within the enterprise using a variety of protocols and methods including: Cisco Discovery Protocol (CDP), Link-Layer Discovery Protocol (LLDP), Simple Network Management Protocol (SNMP), Secure Shell (SSH) Command line, Internet Protocol (IP), Address Resolution Protocol (ARP), Windows Management Interface (WMI). - Automatically discover the SSA enterprise network and update previously collected data in less than 4 hours. - Support discovery over IPv4 and IPv6 networks and be capable of monitoring devices using both versions. - Discovery must use Border Gateway Protocol (BGP) routing information to identify remote SSA locations across the multiple Multiprotocol Label Switching (MPLS) provider networks. - Automatically group devices at remote SSA locations and support-customized group naming using SSA business data including, but not limited to: city, state, and segment id and site code - Provide dynamic grouping of discovered devices based on configurable criteria including SSA site & business data. - Automatically update all attributes & relationships of discovered elements in successive discoveries. - Provide the ability to exclude IP addresses and address ranges from discovery and monitoring. - Perform discovery without the use of network ping sweeping. - Provide the ability to include or exclude discovered devices using configurable criteria including, but not limited to: model, snmp syscontact, device type, hostname, processes, vendor. - Automatically discover the identity and asset information of devices including, but not limited to: vendor, operation system (OS) version and image name, SNMP system information, hostname, serial numbers, hardware and software components. - Automatically discover the attributes of devices including, but not limited to: SNMP system information, hostname, ports and interfaces, ip addressing, mac addressing, installed software, enabled features, processes and services. - Automatically discover the relationships between discovered objects including, but not limited to: vlans, trunks, aggregated links, containment relationships, neighbor relationships. - Automatically discover state information including, but not limited to: interface admin and operational status, interface err-disable, routing protocol session status, system up time, host process and service status. - Automatically discover redundancy and aggregation relationships including, but not limited to: redundancy groups, network interface card (NIC) teaming, clusters, hot standby routing protocol (HSRP), gateway load balancing protocol (GLBP), virtual router redundancy protocol (VRRP), aggregated links and ether-channel. - Automatically discover VMware environment components including, but not limited to: ESX hosts and clusters, vCenter, virtual machines (VMs), virtual applications (vApps), virtual NICs, Cisco 1000v, Ethernet interfaces, host bus adapter (HBA) cards, storage paths, datastores and datacenters. - Automatically discover virtual entities including, but not limited to: virtual routers, Solaris logical domains (LDOMs), Microsoft (MS) Hyper-V VMs, Citrix XEN VMs. - Automatically discover IP layer-2 protocol entities including, but not limited to: virtual local area networks (VLANs), spanning tree protocol (STP), per-vlan spanning tree protocol (PVST), rapid per-vlan spanning tree protocol (R- PVST), vlan spanning tree protocol (VSTP), multiple vlan spanning tree protocol (MSTP), vlan trunking protocol (VTP) domains - Automatically discover and manage Cisco Virtual Switching System (VSS) devices including: ports and interfaces, inter-switch links (ISL), chassis, cards, cpu, memory, file systems. 2.2 MONITORING REQUIREMENTS - Provide agentless availability and performance monitoring of discovered devices, hardware and services. - Provide continuous availability monitoring of 20,000 devices polling each device every 4 minutes or less. - Monitor at least 700,000 network adapters for availability every 4 minutes and for performance problems every 15 minutes or less. - Provide automated root-cause analysis and event suppression without requiring rule creation by administrators. - Provide a list of related events and non-root-cause alarms within a root-cause alarm. - Provide count and a listing of impacted devices and services for any given alarm for instance: the switches and host affected when a router shuts down. - Perform monitoring using management protocols and access methods including, but not limited to: SNMP (all versions), Asynchronous SNMP, WMI, extensible mark-up language (XML), simple object acces protocol (SOAP), web services (WS)-Management, Java management extensions (JMX), telnet, SSHv2, PowerShell, transmission control protocol (TCP), hyper text transfer protocol (HTTP), internet control message protocol (ICMP). - Support monitoring the following types of devices and systems: Cisco Routers and Switches, Cisco Wireless, Cisco Nexus, Cisco VSS, F5 & Alteon Load balancers, Bluecoat proxies, Juniper JunOS devices, ScreenOS devices, Brocade switches, Microsoft servers & Hyper-V, Microsoft Clusters, Unix (Solaris & AIX) and Linux servers, Vmware vSphere, Citrix XEN, IBM AS400. - Monitor VMware vSphere for problems including, but not limited to: health, performance, capacity, vMotion, loss of storage paths, vm restarts. - Monitor for performance problems including, but not limited to: errors, drops, collisions, discards, excessive broadcasts, icmp latency. - Monitor network protocols and entities including, but not limited to: - border gateway protocol (BGP), enhanced interior gateway routing protocol (EIGRP), intermediate system to intermediate system (IS-IS), generic routing encapsulation (GRE) Tunnels, point-to-point (PPP) links, GLBP, HSRP, VRRP. - Monitor redundancy and switch-over events including, but not limited to: HSRP failover, Backup links, vMotion events, Load balancer failover, server cluster events. - Monitor aggregated links as a bundle as well as member links. - Create an alert when a remote SSA location becomes unreachable through the carrier links. - Create alerts when carrier connections to remote sites experience errors or lose link members. - Monitor the connections between switches and routers as Trunk Cables. - Monitor and record configuration changes on routers and switches including the user initiating the change. - Monitor and record hardware changes to network devices. - Monitor switch access ports only when the attached device is monitored unless configured otherwise. - Provide the ability to create custom polling and instrumentation methods for monitoring. - Process SNMP Traps and Syslog messages for event creation, root-cause analysis and to trigger automation. - Provide utilities to import and compile vendor management information base (MIBs) for polling and SNMP processing. - Provide the ability to define and process custom SNMP traps and Syslog messages. - Provide the ability to process Syslog messages using pattern matching and regular expressions. - Suppress alerts due to administrative changes including, but not limited to: BGP & EIGRP session disconnects, down network adapters. - Support the suppression of alerts at a given location, device or group of devices for a period of time. - Support the scheduling of recurring maintenance on a daily and weekly basis where alerts are suppressed. - Provide a method to users to suspend monitoring of a device, group of devices or service in real time. 2.3 USER INTERFACE & PRESENTATION REQUIREMENTS - Provide a multi-threaded web browser-based client interface. - Provide the ability to configure system behaviors using the web browser-based client interface including, but not limited to: polling intervals, device authentication, polling intervals and performance thresholds. - Support the creation of read-only dashboard consoles for un-authenticated users. - Require users to authenticate a single time per session to access all features. - Provide a configurable event console to view alerts and initiate actions by SSA network operations center (NOC) personnel. - Support event console configuration to allow personalized user views including, but not limited to: filtering out alerts, creating column headings, hiding columns, sorting and ordering, splitting the console into tiles. - Provide a set of event filters to control what alerts are visible within the event console. - Event filters must support filtering on alert attributes, device attributes and SSA business data. - Provide the ability for users to acknowledge and take ownership of alerts in the event console. - Automatically clear events using: polling events, inbound events, automation policies, hysteresis modeling. - Provide within the alert a text field to store the SSA ticket id string. - Display within the alert any SSA business data associated including, but not limited to: site code, segment id, site type, workstation count. - Enrich alerts to include historical events and trends at both a device and site level. - Display neighboring devices, group memberships, system components and services within an alert. - Provide a record of changes and actions taken on each alert in the system. - Distinguish alerts resulting from scheduled outages. - Provide network visualization of remote SSA sites diagramming site devices and how they are connected. - Provide the ability to export network visualizations to file formats such as: MS Visio, portable network graphics (PNG), portable document format (PDF), tagged image file format (TIFF), joint photographic experts group (JPEG). - Provide the ability to export console alerts to a file format such as: comma separate values (CSV), Excel, PDF 2.4 CONFIGURATION & SYSTEM ADMINISTRATION REQUIREMENTS - Provide the ability to change and apply system settings in real time. - Provide a way to configure the amount of time inactive events remain in the system. - Support dynamically grouping devices, services and sites based on discovered data and external systems. -Provide the ability to automatically synchronize settings within the system for things including, but not limited to: logical groupings of devices and services, polling and threshold settings, user account and profile information. - Provide the ability to import and export settings using XML files for things including, but not limited to: system configuration, user profiles, logical device grouping, event console settings. - Provide an XML Schema (XSD) file to check the validity of any XML files used in the system. - Provide a syntax checking utility for all text-based system configuration files. - Provide centralized logging of system events and user actions including, but not limited to: user log on, device delete, manual discovery initiation, discovery completion. - Support user account creation, configuration and management using the web browser-based client interface. - limit access to system features and functions using role-based access control (RBAC). - Provide the ability for users to reset and recover their passwords. - Provide the ability to view all users connected to the system at any given time. - Provide the ability to view licenses purchased, used and remaining. 2.5 DATA ACCESSIBILITY & AUTOMATION REQUIREMENTS - Provide a command-line interface to access system data and resources. - Provide a representational state transfer (REST)-ful web service application program interface (API) and web services description language (WSDL) file to access to system data and resources. - Provide a scripting API in an industry standard language such as: PERL (preferred), PYTHON, RUBY. - Support open database connection (ODBC) connections and structure query language (SQL) queries to any system database. - Provide the ability to create alert workflows or escalations based on the alert and underlying devices. - Support custom tool creation for users to execute against an alert including, but not limited to: ssh to a device terminal, ping a device, run a script, reduce the alert severity. - Provide the ability to trigger actions against alerts including, but not limited to: sending an email, executing a script. - Provide alert information via environment variables to any scripts triggered by or executed against an alert. - Support passing command line options to scripts when triggered. - Provide a way for users to visually define for what alerts they are notified for and how including, but not limited to: email and short message service (SMS). - Provide a way for users to subscribe to pre-defined alert lists. 2.6 DEPLOYMENT REQUIREMENTS - Support a centrally-located configuration where all parts of the solution are located within SSA datacenters. - Require no significant modifications to the agency's existing network architecture. - Support x86-64 processors with hardware virtualization assistance (VT-x). - All applications must be certified by VMware as "VMware-ready." - Support VMware vSphere 4.1 or later environment including ESX and ESXi hosts. - Support deployment as a VMware VM open virtualization format (OVF) package (preferred) or installed on Red Hat Enterprise Linux 5 or later. 2.7 CONTINUITY OF OPERATIONS REQUIREMENTS - Support an architecture that will maintain a presence in all SSA datacenters simultaneously. - Support a recovery time objective of 2 minutes and recovery point objective of 1 minute in the event of a failure. - Provide automatic synchronization of primary and redundant systems. - Redundant or secondary systems must automatically assume workloads upon primary system failure. - Redundant or secondary systems must not duplicate polling activities or traffic on the network. - Provide the ability to manually initiate or schedule failover between data centers. - Support VMware vMotion within a datacenter cluster of ESX hosts. 2.8 SECURITY REQUIREMENTS - Authenticate users against the agency's Microsoft Active Directory services using approved protocol versions. - Provide role-based user management. - Support the encryption of client sessions and server-to-server communications. - Installed applications must run without being root user. - Provide the ability to log all user activities and changes to the system. 2.9. REPORTING REQUIREMENTS - Provide historical reporting and trending of device availability and performance for the past 12 months. - Provide historical reporting and trending by SSA office location (site). - Provide a web browser-based client interface to query in real time for historical alerts. - Provide the ability to export/save report query results to CSV, Excel, PDF. - Provide the ability to schedule reports to run at a specified date and time and email results. - Provide reporting on system activities and health. - Provide reporting for system license usage. - Provide reporting on end of life (EOL) and end of service (EOS) for managed systems and components. 2.9.1 VENDOR SUPPORT REQUIREMENTS - Provide 24x7x365 online and telephone support with a response time of less than 1 hour. - Included software upgrades in maintenance and support. - Provide current manuals, documentation and release note with all software upgrades and patches. - Provide monthly site visits by advanced technical personnel to provide assistance and support. - Provide for a bi-weekly project meeting to track project issues and support items. - Provide a product roadmap for the next 2 years. - Provide solution design and architecture review support. - Notify SSA via email when problems or bugs affect the software deployed at the agency. - Provide a listing of identified problems and bugs and what versions of software are affected. 3.0 SUBMITTAL INSTRUCTIONS Suggested solutions shall be compliant with Section 508 Electronic and Information Technology (EIT) Accessibility Standards. V endors having the capability to provide the above requirements are invited to submit complete details. Interested parties shall respond to this notice within 21 days from date of this publication. Vendors responding shall indicate whether the products are available on the GSA Federal Supply Schedules. Vendors may submit pricing data. This is not a request for proposal or quote and the Government does not intend to pay for information received. The government will not notify respondents of the results of the evaluation of the data received. The government will not issue a contract award based on responses received; however, the agency will use this information in SSA's assessment of products available on the market. The agency will not accept Faxed responses. The agency will not honor or acknowledge requests for copies of a solicitation. SSA will not be issuing a solicitation at this time. Please submit electronic responses via email only to the Contracting Officer identified herein. NOTE: There is a size limit for e-mail; no submission shall be greater than 5 MB. The Agency will not accept phone calls.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/spg/SSA/DCFIAM/OAG/SSA-RFI-12-1013/listing.html)
 
Place of Performance
Address: Social Security Administration, 6401 Security Boulevard, Baltimore, Maryland, 21235, United States
Zip Code: 21235
 
Record
SN02657678-W 20120121/120119234925-28fc3a13d1328f59b6a81a7a4c27de38 (fbodaily.com)
 
Source
FedBizOpps Link to This Notice
(may not be valid after Archive Date)

FSG Index  |  This Issue's Index  |  Today's FBO Daily Index Page |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  © 1994-2020, Loren Data Corp.