SNA » Rconfig

Meeting was scheduled for wednesday 28th August at 10 am est

MOM are here as follows:

Project Introduction and Status

• Peter introduced the config project, started 9 months ago
• Initial attempt with expensive Windows server software failed
• Switched to Arconfig for better performance
• Peter building scripts to automate device import
• Discovered connectivity issues with only 10% of devices reachable
• Issues fixed two weeks ago by Dan

📚 Learning Rconfig

• Peter advised team to research Arconfig before next meeting
• Emphasis on learning Arconfig CLI
• Peter suggested watching YouTube videos and visiting arconfig.com
• Meeting rescheduled for the next day to discuss in more detail

🤔 Miscommunication and Expectations

• Team expected Peter to explain the project and provide a demo
• Peter expressed frustration over team's lack of preparation
• Discussion about CLI knowledge and Arconfig-specific CLI
• Peter emphasized difficulty in explaining without basic knowledge

📅 Meeting Rescheduling

• Peter suggested rescheduling for next week
• Stacy to discuss with Tony and Shelley before rescheduling
• Peter to contact Tony regarding meeting preparation issues

=================================================================

Awaiting directions from sir tony/shelly on this

Rconfig Project Plan

1. Project Initiation

• Objective Definition: Implement rConfig for network device configuration management for SNA infrastructure

• Stakeholder Identification: Identify key stakeholders, including operations Manager, Account Manager , Customer Success, Program Managers, IT Net , IT Dev

OM: Yanni

AM: Alexis

Peter : Rconfig Implementation engineer

Chase: NOC Supervisor, Will provide assistance to access equipment configurations and help oversee Rconfig rollout and administration

2. Planning

• Requirements Gathering: Collect specific needs, such as the types of network devices to be managed, configuration backup frequency, and automation requirements.

• Resource Allocation: Assign roles, including a project manager, network engineers, and system administrators.

Grey: Level four engineer: Will provide assistance to access configuration across all infrastructure of SNA

• Timeline and Milestones: Set key milestones, such as installation, configuration, testing, and go-live, with clear deadlines.

• Risk Management: Identify risks, such as potential integration issues or security concerns, and plan mitigation strategies.

3. Design

• System Architecture: Design the rConfig setup, including server specifications, network architecture, and integration points with existing systems.

• Interface Design: Plan the user interface layout, considering ease of use for network engineers.

• Documentation: Prepare documentation outlining the rConfig architecture, workflows, and user roles.

4. Development

• System Configuration: Install rConfig on the designated server, configure necessary dependencies, and set up the initial environment.

• Customization: Customize rConfig to include necessary plugins, scripts, and templates for the specific network devices in use.

• Testing: Perform unit testing, integration testing with existing systems, and user acceptance testing (UAT) to ensure rConfig meets all requirements.

5. Implementation

• Deployment: Gradually roll out rConfig in a phased approach, starting with a pilot group of network devices before full deployment.

• Data Migration: If applicable, migrate existing network device configurations to rConfig for centralized management.

• Training: Conduct training sessions for network engineers and administrators to ensure proficiency in using rConfig.

• Go-Live: Officially transition to rConfig for managing network device configurations, with close monitoring for any issues.

6. Post-Implementation

• Monitoring and Support: Continuously monitor rConfig’s performance and provide ongoing support to address any issues.

• Evaluation: Gather feedback from users to assess the effectiveness of rConfig and identify any areas for improvement.

• Optimization: Implement any necessary optimizations based on feedback and system performance to enhance efficiency.

7. Project Closure

• Final Review: Conduct a comprehensive review of the rConfig implementation project, documenting successes and lessons learned.

• Handover: Transition ownership of rConfig to the operational team, ensuring all documentation and training materials are up to date.

• Sign-Off: Obtain final approval from stakeholders and formally close the Rconfig implementation project..

Project call is scheduled at 2nd Sep 5 pm est

Notes on sep 2

🔧 Project Overview and Rconfig Introduction (00:19 - 14:10)

• Peter explained the Rconfig project for SNA infrastructure
• Rconfig will backup device configurations automatically
• Integration with Zabbix for data pulling
• Peter sent documentation and work plan to Lenny and Shelley
• Meeting with Alex from SNA needed to move forward

📅 Project Timeline and Tasks (14:13 - 25:08)

• Stacy went through project milestones and tasks
• Peter emphasized not to send the document to Lenny before the meeting with SNA
• Discussed stakeholders and their roles
• Alexis assigned as the main point of contact for coordination with Lenny

🛠️ System Design and Documentation (25:08 - 36:15)

• System architecture design is complete
• Interface design is using Rconfig's default UI
• Documentation needed for workflows and user roles
• Peter needs help from SNA management for user roles and workflow documentation
• Timeline for documentation set to 4-6 weeks

💻 Rconfig Functionality and Integration (36:16 - 45:44)

• Rconfig will be used to backup and restore device configurations
• Integration with Zabbix for device information
• Can push configurations to new or replacement devices
• Discussed how Rconfig communicates with new switches

🔄 Configuration Management and Updates (45:44 - 54:11)

• Rconfig will automatically update when changes are made in Zabbix
• Will store multiple versions of configurations, including the original
• Discussed the process of config changes and backups

🎓 UI Demo and Next Steps (54:15 - 01:03:28)

• Peter offered to show the Rconfig UI
• Discussed scheduling a meeting with Lenny and Alex
• Stacy to upload project plan to SharePoint for team access and updates

Action items

Alexis Ybanez

• Schedule a meeting with Lenny, Peter, and Alex for late this week or early next week (59:56)
• Reach out to Lenny tomorrow for meeting availability (59:36)

Peter Degn

• Prepare and send a video explaining Rconfig functionality to the team (57:33)

Stacy Kinkar

• Upload the project plan to SharePoint and share with the team (02:10)
• Take follow-ups and update the SharePoint document as needed (02:53)

Grey Erespe

• Review Rconfig documentation on rconfig.com (40:30)