Hi, I have just had a to revert a customer due to a failed install. Hoping someone can help.
Replacing an HP core with Cisco 3750's configured up all the vlan s and IP addresses. Created two port channels, 11 and 12 to take 10gig uplinks from cisco fabric interconnects (Currently they have 1gig connections into the HP). Plugged the 10 gigs, vlans cane up.. Dang switch wont ping the UCS manager on vlan 220 from either default vlan or using vlan 220 as a source. all VM's lost connections within the UCS (they are supposed to switch inside the FI's). Must be something wrong with my config pasted below... Had a laptop plugged into a port I configures as an access port on VLAN 220, could ping the ip address of the vlan 220 interface but not the interface of vlan 1 or the ucs manager. ANy help or pointers appreciated and apologies for the long post.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.05.30 08:24:31 =~=~=~=~=~=~=~=~=~=~=~= sh run Building configuration...
Current configuration : 13110 bytes ! version 12.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname vvvv ! boot-start-marker boot-end-marker ! enable secret 5 vvv ! username root privilege 15 secret 5 vvvv ! ! no aaa new-model switch 1 provision ws-c3750x-48 switch 2 provision ws-c3750x-48 system mtu routing 1500 ip routing ! ! ip domain-name vvv ip name-server 192.168.220.31 ip name-server 192.168.220.59 ! ! crypto pki trustpoint TP-self-signed-2806828672 enrollment selfsigned subject-name cn=IOS-Self-Signed-Certificate-2806828672 revocation-check none rsakeypair TP-self-signed-2806828672 ! ! crypto pki certificate chain TP-self-signed-2806828672 truncated
Hmm. Did you create those VLANs on the switch? :) Also, check spanning-tree and check the trunk ports and make sure that the VLANs are allowed across. Also, make sure you allow the VLANs on the trunk from the FIC/UCS side as well.
About the native VLAN: You should definitely have it matching on both sides. Otherwise, it can definitely cause issues. For instance, if it is native 220 on the UCS but 1 on the switch then traffic from the UCS on VLAN 220 would come untagged across the trunk. Since the traffic does not have a VLAN tag the switch would assume that it should be riding on VLAN 1 (the local native VLAN) and vice-versa
You should issue show interface trunk and show CDP neighbor detail on the switch and post the output here.
About the port-channeling protocol: I have not worked much with UCS but even if it did support channel-group on, I would still recommend that you use LACP
A couple of other things to test:
1. From your test machine on VLAN 220, can you ping another host on that switch that is in a different VLAN?
2. From the same test machine can you ping another upstream device/IP. For instance, the default gateway or an upstream router/L3 switch...basically something other than UCS and hosts behind it
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...