Issues with printer on different VLAN

[Stacey Hummer]

So, been banging away at this for a while. Not sure what is going on tried lots of different things. 

Issues, moving away from everything being on VLAN 1, however when I move machines into a vlan (lets say 323). The printer is left in vlan 1 for now. Each switch has vlan 1 and vlan 323 with ip addresses.

So

  1                                                               2                                             3

3560 ---------- ----------------------------------2960 -------------------------------- 2960

Core                                                        Dist                                        Dist

Vlan 1 10.2.x.2                                  10.2.x.3                                        10.x.x.4

Vlan 323 10.1.x.1                               10.1.x.2                                         10.1.x.3

Printer is on vlan 1 10.2.x.66

Pc is @ 10.1.x.55

Cannot ping printer from vlan 323 on third switch.

Default-gateway set to 10.1.x.1

Tried pinging from VLAN 323 to core 10.2.x.1 and it couldn't find it.

From core to third switch on vlan 323 works as well.

Any ideas

More info...

On the core I can ping from vlan 1 to printer so, 10.2.0.2 to 10.2.0.66

However when I do a source of vlan 19 which is configured and up it fails so from 10.1.9.1 to 10.2.0.66 it fails.

As well from the core I do an extended ping and it's very slow and sporadic. 

Protocol [ip]: 
Target IP address: 10.2.0.66
Repeat count [5]: 1500
Datagram size [100]: 
Timeout in seconds [2]: 
Extended commands [n]: 
Sweep range of sizes [n]: 
Type escape sequence to abort.
Sending 1500, 100-byte ICMP Echos to 10.2.0.66, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 99 percent (1499/1500), round-trip min/avg/max = 1/104/864 ms

Error message on the core

Jul 16 13:03:49.735 MNT: NTP Core (NOTICE): Spike event  s

Jul 16 13:03:30.937 MNT: ICMP: dst (10.2.0.2) port unreachable rcv from 10.2.0.162

162 is reachable and 2 is the Core this is from....

Never mind it was a printer config issue... :)

[Mark Mc Nicholas · Accepted solution]

My first though is have you ip routing enabled on the 3560?

If from the switches you have configured you can ping the default gateway addresses in each vlan (Assuming they are svi's on the 3560) then this is most likely a simple routing issue there.

The  other question and sorry for asking but have you verified the default gateway config on the printer. since up to now you have all been on vlan 1 there was never a need for the printer to have a gateway!! I have seen many sites where people never configure a gateway on the printer. 

[Sanjith47]

Please check the trunk status on the switches and the gateway for the printer.
 

[paul driver]

Hello

"Each switch has vlan 1 and vlan 323 with ip addresses."

this should not be th case

The core should have th SVI interfces for all vlans and ip roiting enabled

The access switches should be "host" switches - meaning a management interface only
and a default-gateway pointing to the core svi of that vlan with no ip routing enabled.

lastly the L2 vlans should be defined in the vtp database.

example:

core
int vlan 5
description Management- vlan
ip address 5.5.5.254 255.255.255.0


int vlan 10
description data-vlan10
ip address 10.10.10.254 255.255.255.0

int vlan20
description data-vlan20
ip address 20.20.20.254 255.255.255.0

int x/x
description downlink- port -to-access-switches
swithport trunk encap dotq
swithport mode trunk

ip routing

vtp domain IAMBOSS
vtp mode server


vlan 5 name Management- vlan
vlan 10 name data-vlan1
vlan 20 name data-vlan2



access-switches

int vlan 5
description Management- vlan
ip address 5.5.5..1 255.255.255.0

ip default-gateway 5.5.5.254

vtp mode transparent
vtp domain IAMBOSS
vtp mode client

int x/x
description uplink port
swithport trunk encap dotq
swithport mode trunk
 

int fax/x
description access port
switchport host
switchport acess vlan 5


int fax/x
description access port
switchport host
switchport acess vlan 10

int fax/x
description access port
switchport host
switchport acess vlan 20



res

Paul
 

[Stacey Hummer]

Sorry everyone, my bad, I've been so busy and this was resolved quickly when our tech went to the site to see how the printer was configured. The default-gateway was wrong. Thanks for all the help.