Hi, Regarding choosing the IS-IS routes over the redist routers, so you can use the following commands to change the AD of the redist routes to whatever you need to prefer IS-IS over External, or the opoosit,    Router(config)#router ospf 1 Starts the OSPF routing process Router(config-router)#distance ospf intra-area 105 inter-area 105 external 125 Changes the AD to 105 for intra-area and interarea routes, and changes the AD to 125 for external routes ... View more

Hi Dak, Your question is very basic, but very important at the same time. So, we have 2x situations to explain, both will be based the following scenario, PC1  ----- SW1  ---- R1  ---- R2  ---- R3  ---- SW2 ---- PC08 PC2  ----- SW1 PC3  ----- SW1   So, this simple topology saying that 3x PCs connected to SW1, which this switch is connected to R1. Then, R1 connected to R2, which again connected to R3. Finally, this R3 is connected to SW2 which has PC08 attached to.   Assuming PC1 IP = 10.0.0.1/24 PC1 MAC = AAA PC2 IP = 10.0.0.2/24 PC2 MAC = BBB R1 IP = 10.0.0.10/24 (the gateway of the PCs) R1 MAC = CCC ################# PC8 IP = 80.0.0.8/24 PC1 MAC = AA88 R3 IP = 80.0.0.10/24 (the gateway of the PCs) R3 MAC = CC33 So, We will have to cases to study, 1- PC1 communicating with PC2 (Called Switched / or  Local Communication) The packet/traffic goes out for PC1 will have this in the header, SRC MAC : AAA DST MAC : BBB SRC IP :10.0.0.1 DST IP :10.0.0.2 TCP Header (as per the application or traffic type), and will never get changed at any stage. So, since both source and destination are in the same network/subnet, so the switch will handle this traffic and do switching which is processing the headers by checking the DST MAC and decide which port to send the traffic out (without anything change in the header).     2- PC1 Communicating with PC08 (Called Routing / or Remote Communication) The packet/traffic goes out for PC1 will have this in the header, SRC MAC : AAA DST MAC : CCC SRC IP :10.0.0.1 DST IP :80.0.0.8 TCP Header (as per the application or traffic type), and will never get changed at any stage.   This time is different, the source and destination are in different network/subnet, so the PC decide to send this traffic to its gateway which is the router (bcz from PC perspective, the gateway is only device in the network who should know about the way/path to reach any unknown networks) that's why you see that DST MAC includes the Mac of the gateway, by sending such packet with such header, the switch receives it and knows where to send it, out of the ports connected to the router (switch can't understand the IP header, only deals with MACs). So far, no changes in the header at all.  But, once the R receives the packet, it will consult its routing table and figure the path/route to network 80.0.0.0 which should be through R2. Here you are, R1 change the SRC MAC R1-Mac and DST and R2-MAC, and keep the rest of the header as the same. Then, R2 will do the same, change the SRC MAC to R2-MAC and DST MAC to R3-MAC...an d so on. In conclusion, IP headers remains the same throughout the whole journey from source to destination, but the MAC addresses changes hop-by-hop.   **** Please rate this post as helpful if it helped you, and as a correct answer if it solved your problem. ****     ... View more

Hi, I see for the show output that vlan 100 is not forwarding on spanning tree. ####   Port Vlans in spanning tree forwarding state and not pruned Po1 45-46 #### So, could you please share the output of the following commands: Show spanning-tree vlan 100 Show interface trunk Show interface status.   My doubts here are: 1- You might not having spanning tree instance for vlan 100, if so, do this : SW(config)# spanning-tree vlan 100 2- Go to under vlan 100, and make no shutdown. 3- Make sure you have 1x access port in vlan 100 and the test again. 4- Is this switch part of VSS or VPC, or just standalone switch?   ## Anyway, the show commands I requested will help to identify the problem.##       ... View more

looks like your router is booting ROMMON, check the IOS if exist on flash or not, if yes, make sure you're pointing to it properly.   ... View more

Yea, the problem is caused by HDD capacity, so it will be very good start then share with us the result if solved the problem or not.   ... View more

Hello, once you configured interface vlan 1, then you were able to ping 192.168.1.10 from the switch, where is this .10 is connected to ? It should be connected to one of switch ports, so assuming that this host .10 is connected to Gi1/0/12 so, instead of sharing your config and we investigate then reply back, do the follwoing, 1- show run interface Gi1/0/12 2- copy the output. 3- config t interface range g 1/0/1 - 48 no shutdown ### past the copied configs ### end copy run start   that's it, you should have it working smoothly.   *** Please rate this as helpful and correct answer if it helped you and solved your problem *** ... View more

Hello, once you configured interface vlan 1, then you were able to ping 192.168.1.10 from the switch, where is this .10 is connected to ? It should be connected to one of switch ports, so assuming that this host .10 is connected to Gi1/0/12 so, instead of sharing your config and we investigate then reply back, do the follwoing, 1- show run interface Gi1/0/12 2- copy the output. 3- config t interface range g 1/0/1 - 48 no shutdown ### past the copied configs ### end copy run start   that's it, you should have it working smoothly.   *** Please rate this as helpful and correct answer if it helped you and solved your problem ***   ... View more

Great, this eliminates the firmware issue. If I were in your place, I would do this: 1- Hard Reset the AP manually, 2- Update/Change the firmware on these 5x APs manually, by downloading the new firmware and upload it to the AP by tftp. 3- if problem still exist, ( i doubt), bring a virtual controller in your lab, and join these APs to this lab controller), if joined, so this means that issue is with controller.   ... View more

Hi, 1- MTU wouldn't your biggest problem, becz the overhead is affordable unless you having a critical apps which considering the fragmentation is the first enemy.   2- if you have such amount of traffic, this means you're not running ISR routers, ASR at minimum, if so, drop the GRE tunnel option and go with VXLAN.   3- to deal with the issue of using interior or redist routes, you can use filtering easily and rely only on one of routes either the local or redist.     ... View more

as they mentioned, configuration is straight forward, it's all about static nat with ports, wither to do it from CLI or using ASDM. ... View more

I will not add much on this, as the gentlemen mentioned the important points. However, in healthcare domain, I saw many architectures that were suffering congestion and high utilization while they were using 10G and 40G, but the golden question is, what was that platform or architecture required that very high bandwidth? The answer is, the architecture were relying on core block which is responsible for all Campus and DC traffic routing, especially the Video traffic (a lot of sources / divisions) had video capability along with huge CCTV network. so, simply, go to your customer, get insight on the current setup, collect statistics (mostly will be from the NMS app) and do the analysis required on that.   ... View more

Hi, Good question, Unfortunately, you can't. But, there is a workaround to have the partitioned Area 0 get connected, which by doing the following:  1- Create Interface Loopback on R1 and R2, then advertise them in OSPF 2- Enable OSPF to IS-IS and IS-IS redistribution (Mutual redistribution) on R1 and R2. By doing so, you would have Loopback reachability on both R1 and R2 3- Create GRE tunnel interface on both R1 and R2 using those loopbacks created in step 1 as a source-interface. 4- Assign those tunnel interfaces to OSPF area 0. So, finally you will have full OSPF running on top of IS-IS which will be considered as an Underlay (just a carrier) and the OSPF area 0 will be the Overlay.     *** Please rate this as "Answer" if it solved your problem.*** ... View more