cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3318
Views
0
Helpful
28
Replies

Cannot manage one switch via network

wn1kbates
Level 1
Level 1

I have three 4506 switches with vlan 4 set as the management vlan. Switch 1 is connected to switch 2 and switch 3.

I can access switch 1 and 2 using telnet from the management vlan and both switches reply to pings. But from switch 1 or 2 I cannot ping or telnet switch 3. If I plug into switch 3 and I can ping and telnet switch 3 but not switches 1 or 2.

It is as if the management vlan 4 is not being passed to/from switch 1 and 3. The configs for the uplinks from switch 1 to 2 and 3 are the same. And the configs for switches 2 and 3 look the same apart from the port settings.

I have over 40 vlans running all that work fine between all the switches.

any ideas??

28 Replies 28

If I show the trunk settings I get the following, which if I'm correct shows vlan 4 in the allowed but not on the spanning tree.

4507_Dare_03#sh int trunk

Port        Mode             Encapsulation  Status        Native vlan
Po10        on               802.1q         trunking      1

Port        Vlans allowed on trunk
Po10        1-500

Port        Vlans allowed and active in management domain
Po10        1-110,210-279,300-400,410-465

Port        Vlans in spanning tree forwarding state and not pruned
Po10        8-11,16,19-110,210-279,300-400,410-465

Are there any ports in vlan4 besides the vlan interface if there is on on Switch 3?

It's allowed on the trunk, it's just not going to go across the trunk, because there are no ports with vlan 4 assigned to it.

Switch 3 will not get broadcasts or multicats for vlan4.

Yes, as I thought at first it was an tcp/ip issue, so I set a port on vlan 4 and I can ping/telnet the switch from this port, if I manually set an ip address on the pc.

If I do a show int I get, is this correct ?

Vlan4 is down, line protocol is down

  Hardware is Ethernet SVI, address is 001a.a1d6.45ff (bia 001a.a1d6.45ff)

  Description: Management_VLAN

  Internet address is 172.25.254.3/24

  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 2w5d, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

  L3 in Switched: ucast: 55 pkt, 2359 bytes - mcast: 0 pkt, 0 bytes

  L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes

     587 packets input, 56563 bytes, 0 no buffer

     Received 532 broadcasts (48 IP multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     77 packets output, 5538 bytes, 0 underruns

     0 output errors, 1 interface resets

     0 output buffer failures, 0 output buffers swapped out

But on switch 2 that is working I get

Vlan4 is up, line protocol is up

  Hardware is Ethernet SVI, address is 001a.a18b.ce7f (bia 001a.a18b.ce7f)

  Description: Management_VLAN

  Internet address is 172.25.254.2/24

  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA, loopback not set

  ARP type: ARPA, ARP Timeout 04:00:00

  Last input 00:00:00, output never, output hang never

  Last clearing of "show interface" counters never

  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

  Queueing strategy: fifo

  Output queue: 0/40 (size/max)

  5 minute input rate 0 bits/sec, 0 packets/sec

  5 minute output rate 0 bits/sec, 0 packets/sec

  L3 in Switched: ucast: 837226 pkt, 61024700 bytes - mcast: 0 pkt, 0 bytes

  L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes

     5265830 packets input, 694497826 bytes, 0 no buffer

     Received 4428604 broadcasts (597 IP multicasts)

     0 runts, 0 giants, 0 throttles

     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

     831605 packets output, 78038957 bytes, 0 underruns

     0 output errors, 0 interface resets

     0 output buffer failures, 0 output buffers swapped out

Try to do a 'no shut' on vlan 4. As long as vlan 4 is actually created locally or discovered via VTP, then that should be good.

just tried no shut on vlan 4 and no joy.

Is vlan4 still shown as down? Can u verify that vlan 4 is created again and a port is assigned to it.

Does the vlan4 int have an ip assign?

Yes vlan 4 is still down and down (note there is nothing in int 6/1)

Below parts of the config

vlan 2-9

!

vlan 10

  private-vlan primary

  private-vlan association 11-110

!

interface GigabitEthernet6/1

description MgtNetwork

switchport access vlan 4

switchport mode access

spanning-tree portfast

spanning-tree bpduguard enable

!

interface Vlan4

description Management_VLAN

ip address 172.25.254.3 255.255.255.0

!

ip route 0.0.0.0 0.0.0.0 172.25.254.1

ip http server

ip http access-class 10

ip http authentication local

no ip http secure-server

!

Well, I'm almost 99.999% sure once that vlan interface comes up, you should be good to go.

What happens if you kill the vlan4 interfac and recreate it and do a 'no shut' ?

I'm not sure what is the best way to kill a vlan ?

Found the commands.

And the vlan has come back up/up and has been added to the trunk. All is well. Thanks you very much this one has been a pain for ages.

Kevin

So I am curious, what fixed it (if the sh/no sh didnt)?

I did (or there abouts)

conf t

no vlan 4

end

wr mem

conf t

vlan 4

no shut

end

wr mem

then pinged the switch from switch 1 and it replied.

Kevin