juniperlab

Our goal is to configure routing instances on all devices and provide routing between all instances with ospf protocol. Configure routing instances on SRX1: We will be using a tagged interface ge-0/0/1 where vlan 10 is for vr10.10 routing instance and vlan 20 is for vr20.20: set interfaces ge-0/0/1 vlan-tagging set interfaces ge-0/0/1 unit 10 vlan-id 10 set interfaces ge-0/0/1 unit 10 family inet address 172.16.10.1/24 set interfaces ge-0/0/1 unit 20 vlan-id 20 set interfaces ge-0/0/1 unit 20 family inet address 172.16.20.1/24 Now create routing instances and assign interfaces to them: set routing-instances vr10.10 instance-type virtual-router set routing-instances vr10.10 interface ge-0/0/1.10 set routing-instances vr20.20 instance-type virtual-router set routing-instances vr20.20 interface ge-0/0/1.20 Configure rib-groups to import routes from one routing instance to another (Another alternative is to configure policy-options for importing): set routing-instances vr10.10 routing-opti

In the following topology we have two companies: East Company (routers WR1,WR2,WR3), and West Company (router ER1). Some employees of EastCompany reside on WR3 router of West Company (subnet 192.168.10./24). As we can see between West and East Companies there is an uplink which connects routers WR3 and ER1 with OSPF protocol Area 0. As matter of fact we have very odd scenario with two OSPF Backbone Areas. And one more thing, router ER1 should not maintain/see the routes in Backbone Area 0 of WR1 and WR2 routers but users in East Company should be able to get access to all subnets in West Company.   The approach described violates one of the concepts of OSPF which is that the area 0 backbone should be contiguous. It may work or things may break depending on some details of how it gets implemented. Some of the things that can cause black holing of traffic or other problems can include: - if you have configured stub areas, the stub area will have a default r

Patching vmware 14.0 for kernel headers 4.14.2: sudo su cd /tmp cp /usr/lib/vmware/modules/source/vmmon.tar . tar xf vmmon.tar rm vmmon.tar wget https://raw.githubusercontent.com/mkubecek/vmware-host-modules/fadedd9c8a4dd23f74da2b448572df95666dfe12/vmmon-only/linux/hostif.c mv -f hostif.c vmmon-only/linux/hostif.c tar cf vmmon.tar vmmon-only rm -fr vmmon-only mv -f vmmon.tar /usr/lib/vmware/modules/source/vmmon.tar vmware-modconfig –console –install-all

This configuration review written based on official HP Advanced Traffic Management Guide with some scenarios added to clearify topics not fuly covered in the official guide. In this review you can find various configuration scenarios on QoS deployment for HP 2530 Series switches with detailed explanations how to deploy one or another QoS method/technique to achieve required results. This switch software review is intended for network administrators and support personnel who wants to depoly QoS service in low-price HP configurable switches. Download Full Review  >>GET<<  Inside this review (one of scenarios): Let's consider another example when central Core switch connects Edge switches with running services on them. On edge switches SW1, SW2, SW3 we will be prioritizing the services traffic using DSCP policy prioritization and on core switch CoreSW the traffic will be prioritized using QoS VLAN-ID Priority with 802.1p prioritization on tagge

Mikrotik Router OS CAPsMAN Configuration only bridge mode with external DHCP server and NAT service You can deploy CAPsMAN wireless controller on any Mikrotik RouterOS hardware (for instance Haplite series routers) 1st step is to check our RouterOS image version, it should include wiressless package (check System>Packages). OS version on CAPsman controller should the same as in Access Point. You can upgrade the version manual. Go to the System>Packages , then simply drag and drop your previously downloaded imge. After I would recomend to reboot it from CLI / system reboot and then just run / system routerboard upgrade and again reboot it. Then we can check the version / sys rou print . 2nd step is to create bridge interface which should include our physycal interface or several interfaces, so we create bridging between our physycal interfaces or if it's only one interfaces then it will be put into bridge mode. Let's check our interfaces:

1. NAT Configuration    1.1. Define Access List [Router] acl basic 2001  [Router] step 1 [Router] rule 0 permit [Router] rule 10 deny 2. Interfaces Configuration    2.1. External (WAN) interface configuration [Router] interface GigabitEthernet 0/0/0 [Router] ip address 10.163.195.2 255.255.255.0 [Router] nat outbound 2001     2.2. Internal (LAN) sub-interfaces configuration [Router] interface GigabitEthernet 0/0/1.2 [Router] ip address 192.168.1.2 255.255.255.0 [Router] vlan-type dot1q vid 2 [Router] interface GigabitEthernet 0/0/1.3 [Router] ip address 192.168.2.2 255.255.255.0 [Router] vlan-type dot1q vid 3 [Router] interface GigabitEthernet 0/0/1.4 [Router] ip address 192.168.3.2 255.255.255.0 [Router] vlan-type dot1q vid 4 3. DHCP Server Configuration     3.1. Enable DHCP service on router [Router] dhcp enable     3.2. Define dhcp settings for vlan 2 [Router] dhcp server ip-pool vlan 2 [Router] ne

GET YOUR JNCIA LAB manual