How to assemble a 24×7 team
Team 24×7 is a team that works 24 hours a day and 7 days a week, that is, a team that is always on standby so that the customer never runs out of support. For this reason, it is so common for companies in the IT area and networks to seek to have this team within their organizations, because that way they can deliver more quality in their service. At Made, we went through the process of putting together a 24×7 team when we went to structure our monitoring service. First, we had to adjust the schedules of the attendants, the scale was divided into morning, afternoon, night and dawn. This way we have 4 shifts with fixed attendants in each of these shifts. Each shift is monitored periodically by the supervisor to detect possible failures and difficulties that the attendants face in their schedules An example of the NOC scales follows: Another important point was finding ways to keep communication aligned when changing shifts, in our “passing the baton” we always prioritize the exchange of important information and we have some steps that the team follows as soon as they take over the shift. The idea of passing the baton is basically passing on information in such a way that the next shift can understand all the demands that are still pending from the previous shift, so that the employees of that shift can continue the activities that have not yet been completed by the attendants of the shift. previous. It’s called “passing the baton” because it follows the principle of relay races, in which a teammate waits at the end of the stretch you’ve just run. As you approach your teammate, they start running to match your speed, and the baton is passed. The idea is that the next shift won’t be completely in the dark (otherwise, the person would be at a standstill), but rather that they’ll be following the events from the previous shift so they don’t get lost when information is handed off. In other words, the staff for the next shift begin catching up on the events of the day a little before their shift begins. The employees from the previous shift then hand over the information (passing the baton), making sure they’ve been clear and that there are no questions about pending issues. By following this approach—staying up to date on the day’s key events at and receiving updates on pending issues and open tickets at in the NOC—we’ve been able to run an effective and dynamic team. Keep in mind that team chemistry is extremely important; if the team members don’t know each other, it will be difficult to ensure that the flow of information is effective, because a team that understands its challenges and weaknesses can work together to correct mistakes, allowing the members to grow and evolve together. In addition to the previous steps, we reviewed tools to help us with monitoring. All support agents receive a list of videos and content about networks and how the internet works so that they can fully understand the customer’s environment as soon as they finish analyzing incidents. At , we are always exploring new ways to improve our service and streamline our processes while maintaining precision in everything we do. We explore new possibilities and always put ourselves in our customers’ shoes, understanding their pain points and seeking new ways to help them. Did we help you understand a little more about how a 24×7 team works? Share this post, and if you don’t want to go through the entire process of setting up a 24×7 team, consider outsourcing this work. At Made4it, we offer our monitoring services to internet service providers—Made4NOC is our 24/7 monitoring solution for providers.
Partial drop triggers
Understand how partial drop triggers can help you and how you can create 30% and 60% partial drop triggers
zabbix Installation Guide
If you have an infrastructure, whether large or small, it is extremely important to have a monitoring system that can sound alarms when something goes wrong.
Made4Graph Updates – May 2020
Check out the latest from Made4Graph—this May, we’ve updated the system with new features and improvements
Made4Flow Updates – May 2020
Check out the latest news from Made4Flow for May—lots of new things for you 🙂
Creating VPN using PFSense and OpenVPN
Basically, VPN stands for Virtual Private Network, and it serves as a tunnel between two connection points. When you set up a VPN between a computer at your home and a PFsense at your company, for example, the tunnel created allows your computer to act as if it were “inside” your company’s local network, granting access to servers and equipment, provided that the PFsense is reachable from your home computer. Now that we understand what VPN is all about, let’s learn how to set it up using PFSense to establish the connection between your different networks. Configuring the VPN We’ll use PFSense’s built-in “Wizard” for this configuration. To do this, go to the VPN > OpenVPN. Then, click the Wizardstab: So, that’s it, folks. This was our guide to setting up OpenVPN using pfSense and configuring a connection to it using the OpenVPN Client, with the files provided by pfSense itself.If you need help or support with pfSense maintenance, please contact us —we’re here to help!Thanks, and see you next time!
Installation of PFSense as your network’s Gateway.
At the end of the Wizard, we have our PFSense ready to use! In upcoming posts. We will teach you how to create a VPN using PFSense, so you can access your Internal Network from your home. Thank you and see you in the next posts. Adriano Elias de SouzaIT ConsultantMade4it
Custom Dashboard and CDN Charts by Time – Made4Flow News 02/24/2020
See what’s new in Made4Flow, our new custom dashboard and CDN charts by period.
Interconnecting two Virtual Systems (VS) on Huawei NE platform (Interconnecting 2 virtual routers on Huawei NE)
The other way to link… Interconnecting two VS via VPN VPWS CCC # Admin-VS ! Side L2 Admin-VS Virtual-Ethernet0/2/100 interface ve-group 100 l2-terminate Virtual-Ethernet0/2/100,100 interface vlan-type dot1q 100 ! Side L2 VS1 Virtual-Ethernet0/2/200 interface ve-group 200 l2-terminate Virtual-Ethernet0/2/200.100 interface vlan-type dot1q 100 ! MPLS CCC VPWS interconnectionccc test interface Virtual-Ethernet0/2/100.100 tagged out-interface Virtual-Ethernet0/2/200.100 tagged # Admin-VS ! Side L3 Admin-VS Virtual-Ethernet0/2/101 interface mac-address c4b8-b434-ab45 ve-group 100 l3-access interface Virtual-Ethernet0/2/101.100 vlan-type dot1q 100 ip address 10.1.1.1 255.255.255.252 ! Side L3 VS1 interface Virtual-Ethernet0/2/201 ve-group 200 l3-access interface Virtual-Ethernet0/2/201.100 vlan-type dot1q 100 # Admin-VSadmin virtual-system vs1 pvmb slot 3 port-mode port assign interface Virtual-Ethernet0/2/201.100 # VS1 ! VS1 L3 Sideinterface Virtual-Ethernet0/2/201.100 vlan-type dot1q 100 ip address 10.1.1.2 255.255.255.252 Scenario Considerations Validations <HUAWEI>display vll ccctotal ccc vc : 1local ccc vc : 1, 1 upremote ccc vc : 0, 0 up name: teste, type: local, state: up,intf1: Virtual-Ethernet0/2/100.100 (up), access-port: false intf2: Virtual-Ethernet0/2/200.100 (up), access-port: false VC last up time: 2020/02/17 14:40:58VC total up time: 0 days, 0 hours, 16 minutes, 37 seconds Admin-VS:<HUAWEI>ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=1 msd Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=1 ms — 10.1.1.2 ping statistics — 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 ms VS1:<HUAWEI-vs1>ping 10.1.1.1 PING 10.1.1.1: 56 data bytes, press CTRL_C to break Reply from 10.1.1.1: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 10.1.1.1: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.1.1: bytes=56 Sequence=3 ttl=255 time=1 ms Reply from 10.1.1.1: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.1.1: bytes=56 Sequence=5 ttl=255 time=1 ms — 10.1.1.1 ping statistics — 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 ms<HUAWEI>ping 10.1.1.2 PING 10.1.1.2: 56 data bytes, press CTRL_C to break Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=255 time=1 msd Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=255 time=1 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=255 time=1 ms — 10.1.1.2 ping statistics — 5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 1/1/1 ms <HUAWEI>display bgp peer BGP local router ID: 192.168.88.100 Local AS number: 11111 Total number of peers: 1 Peers in established state: 1 Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv 10.1.1.2 4 22222 25 25 0 00:19:38 Established 0<HUAWEI>displ ospf peer brief (M) Indicates MADJ neighbor OSPF Process 1 with Router ID 10.0.0.1 Peer Statistics InformationTotal number of peers: 1 Peers in full state: 1—————————————————————————– Area Id Interface Neighbor id State 0.0.0.0 VE0/2/101.100 10.0.0.2 Full<HUAWEI> displ ospfv3 peer OSPFv3 Process (1) OSPFv3 Area (0.0.0.0) Neighbor ID Pri State Dead Time Interface Instance ID 10.0.0.1 1 Full/DR 00:00:38 VE0/2/201.100 0 Finally that’s it folks, we don’t know the performance or impact on the box, but the basic services worked normally. If you test it with traffic, let us know! Share your results with us. If you need assistance, please contact us! Hugs, Rafael Ganascim, Gabriel Henrique and Kevin Walters IT Consulting Team – Made4it
Virtual-System on Huawei NE: The Power of Virtual Routers
See how to better explore your Huawei NE line router through the VS (Virtual-System) feature.
