"inactive" port status

Hogan.BrendanT1 · ‎09-30-2015

I am trying to update my local 6509, our network TFTP is timing out when I try to copy the OS from it. What I have done is created a vlan on the 6509 (Vlan 102) gave it an IP and a broadcast address as well (10.10.10.1 netmask 255.255.255.0 broadcast 10.10.10.255) I waited for VTP to distribute out vlan 102 before configuring the FEX ports below.

I have a laptop that I put a TFTP server on and I set its IP to 10.10.10.2.

I have configured my FEX for port 104/1/20 and 105/1/20 (dual-homed FEX) to access vlan 102.

Simple port configuration, both are configured like this :

switchport mode access

switchport access vlan 102

description iOS_Configuration_VLAN

no shut

When I have one FEX interface set to shutdown it shows "link not connected" on the other, as soon as I enable the other then it goes to "inactive"

Can someone please help me with why the port is switching to inactive? Is there something Ive missed or is this not going to work? I even tried to configure another port the same and had the exact same thing happen to that port as well so there has to be something that Ive either missed, or not configured right.

EDIT: I am going through the FEX to my 5548 to reach the 6509, not directly connecting to the 6509.

Thank you in advance

Mark Malone · ‎09-30-2015

Hi I don't think you can connect a FEX 2K DC switch to a standard 6509

They will work with 6880s but as far as im aware they will not work with 6509s

They need the 5k or 7k connected to them as there controlled by them , there not standalone devices like 2960s

https://supportforums.cisco.com/discussion/11480776/nexus-2248-6509

Hogan.BrendanT1 · ‎09-30-2015

The 6509 is my core, I go through a 5548 which is what the FEX's are connected to.

Mark Malone · ‎09-30-2015

If I have this right what your trying to do is basically create a dual homed server/pc to 2 2ks 104 and 105 , if your doing this you need to use an enhanced vpc which is basically a port-channel as vpc is already part of 2k and if you do show vpc brief your 2k ports will be there

so you need to have a port-channel on each 5k like below , and the config must be identical on each 5k, heres an example below I just built this for a server the other week that's dual homed to 2 fexs 118 & 117 using lacp

5k1# sh run int e117/1/2

interface Ethernet117/1/2
switchport access vlan 37
channel-group 177 mode active

5k1# sh run int e118/1/2

interface Ethernet118/1/2
switchport access vlan 37
channel-group 177 mode active

5k1# sh run int po177

interface port-channel177
switchport access vlan 37

Hogan.BrendanT1 · ‎09-30-2015

Mark,

Thank you for the help. I think that cleared up the "inactive" part now I am seeing the ports as up, with a "none" description. I am still not able to ping through the network though I get timed out when trying to do so.

As you did above here is my current config:

5k#1 sh run int e104/1/20

switchport access vlan 102

channel-group 133 mode active

5k#1 sh run int e105/1/20

switchport access vlan 102

channel-group 133 mode active

5k#1 sh run int po133

interface port-channel133
switchport access vlan 102

5k#2 is configured exactly the same as above.

Any further assistance or suggestions you can give me are greatly appreciated.

EDIT: After posting this I went and did a tracert and it looks like I am not even getting past my 5k's and have no idea why as Vlan 102 is there and assigned to these ports.

Mark Malone · ‎10-01-2015

Ah that's good vpc is working links are up,on the uplink trunk ports connected to the 6509 check that the vlan 102 is allowed on it on both 5ks, check the show int trunk status nothings being pruned or dropped for that vlan on 65 & 5ks , make sure vlan 102 is up/up on 65 and check the vlan database for 102 has the exact same name on both 6509 and 5k any discrepancy might black hole the traffic at the 5 as it cant be switched up, these are just things I would check myself as this is layer 2 , check STP is not blocking the vlan anywhere on uplinks