Pipenv

Install pipenv Testing venv itsdangerous token...

Set your own custom venv Python Path

Find current Path for python site-packages Find and highlight Add your own Python Path Confirm the new PATH You may want to use alias Check using which path...

Ubuntu Python Flask

For production server Create required folder structure config file for apache sudo nano flaskapp.wsgi sudo nano __init__.py from flask import Flask app = Flask(name) @app.route("/") def hello(): return "Hello Kim! 1 2" if name == "main": app.run(host='0.0.0.0', debug=True) Give proper permissions to wsgi.py Enable the file with a2ensite (if you are using separate conf)...

Tshoot 300-135 (Infrastructure service) Policy-based routing and VRF

Ticket #8Traffic from the R9 is getting sub-optimally routed to R1 (10.12.12.1)Ensure it takes the optimal path. #### Fix by removing RM_PBR R8(config-if)#no ip policy route-map RM_PBR #### Verify fix R9#traceroute 10.12.12.12 source 10.9.9.9 probe 1 timeout 1 ttl 1 11 R9#traceroute 10.12.12.12 source 192.0.2.9 probe 1 timeout 1 ttl 1 11 Ticket #9Your...

Tshoot 300-135 (Infrastructure service) NAT

Ticket #6R9 is translating 192.0.2.100 to the Server’s 10.9.9.100 address. PC1 can’t ping the server at 192.0.2.100Diagnose and resolve.Don’t modify any NAT rules. #### Why this crazy NAT setting? R7#show ip nat statistics #### Discovered R7 has two NAT Ticket #7PC2 (192.168.200.100) can’t reach the server at 10.9.9.100Diagnose and resolve. Even when meticulously follow...

Tshoot 300-135 (Infrastructure service) First Hope Redundancy Protocols

Ticket #1PC1 is not getting an IP address from SW5.Ensure PC1 receives an IP address between 192.168.100.100-249 Use the command ifconfig eth1 to view its IP address.Use the command sudo reboot to request an ip address Ticket #2PC1 and PC2 can’t ping each other.Diagnose and resolve. Ensure each PC’s default gateway is set to...

Tshoot 300-135 (BGP & GRE)

Ticket #1The eBGP neighborship is broken between R1 and R5.Diagnose and resolve Ticket #2R9’s loopback interface (9.9.9.9) can’t ping R2 (198.51.100.12)Diagnose and resolve.Do not modify or unassign any ACLs Ticket #3R2’s interface (198.51.100.12) is unable to ping R4’s interface (203.0.113.4) Diagnose and resolveDo not modify and IGP configurationDo not remove any route map entries...

Tshoot 300-135 (Routing IPv6 OSPF)

Ticket #5 R5 and R7 aren’t forming an OSPF3 adjacency with R1 and R4 on the 2001:1457::/64 segment. R5 and R7 are also not forming an adjacency with each other over this segment Ensure that all four routers form an adjacency Fixing the static MAC address entry Things to check if OSPF adjacency does...

Tshoot 300-135 (Routing IPv6 EIGRP)

Ticket #1 R1 (RID 1.1.1.1) and R2 (RID 2.2.2.2) are not forming an EIGRPv6 adjacency Ensure that both routers form an adjacency in AS 10 using multicast. Ticket #2 R1 and R3 aren’t forming an adjacency. Diagnose and resolve Ticket #3 R1, R2 and R3 do not have a route to R4’s loopback 0...

Scroll to top