Hi, hopefully i am not the very first one in the work to have this issue. So the issue is as follows. I am busy with a project where the client is moving from cisco to juniper on core and access. They have several ex2300 VC stacks on each floor, each floor have a few printers, there are two brands, Xerox and Bizhubb. The network is currently pretty straight forward, one VLAN for servers, one for users and one spare for other. This is VLAN2 for servers, VLAN1 (ciscos default) for users and then VLAN8. There is still the old cisco core and the new juniper core, each with their repective access switches attached to it, all the users have been moved to new network points which is now on the EX2300, still VLAN1 for now. So remember that everything on the access level is pretty much a flat vlan, all users and printers are in the same L2 domain. Users are setup to print to the printers directly, all users are using windows. So there is obviously no firewall between printers and users, no proxy or isolation etc.
Back to the core both cisco and Juniper are connected using a trunk to extend VLAN1, 2 and 8 between them. So as it is currently now all users are on VLAN1 on the juniper side and all Bizhubb printers are on the Cisco side. Xerox on the Juniper side. The reason for this is as soon as i move the cable that goes from the Bizhubb on the cisco in VLAN1 and i move to the Juniper on VLAN1, the printer ceases to print, it goes offline on windows and i can't access the built in webgui of the printer, however the printer does respond to pings no matter what switch it is plug into. People print jobs gets qeued and nothing happens, soon as i move it back to the cisco ports, it starts printing etc. I have disabled RSTP, POE, stormcontrol, LLDP and pretty much any protocal that migh operate on the juniper switchport, still same result. I have configured the physcial settings on both printers like speed and duplex, issue still the same. There is no duplicate IP addresses. This issue is occruing among all Bizhubb printers, where the Xerox is fine. It seems to indicate that the issue is the brand then, but as soon as move it back to the cisco it works. To make it more crazier there is one Bizhubb printer that seems to have worked from the very first time it was moved and it still is working on the Juniper switch. I had the printer techs install the same version firmware on the all the non working printers which are the same model, but they are still not working. Also the same model printers, running the same software are plugged into the same physcial Juniper switch into the same configured interface range, but the one works and the other one doesn't. I dont know much on how printers work exactly but it shouldnt matter really, as it uses IP, i am not sure of it is doing some sort of multicast etc. but surely i should just be able to access it on the webgui using the IP, so i cant figure out what on a switching level is defrent between the cisco and juniper and why it will work on the cisco but not juniper. I can see the MAC address etc. and as i said i can ping it always, it is just print services that stops working.
Thanks for the repsonse. No they dont work after a reboot. Also keep in mind that there is now routing on the juniper done as comms are direclty between client and printer on the same vlan so there is not gateway required.
Strange issue... a couple of thoughts/questions which could potentially bring us closer.
The bizzhub printer which is working and the others which aren't... are they close to being the same (same OUI?).
Any differences between output of 'show ethernet-switching table interface X/X/X' for the working bizzhub and non-working printer? Does 'show ethernet-switching mac-learning-log' indicate any non-expected behaviour?
When pinging a non-working printer does the arp entry match the expected mac address of the bizzhub printer?
Any MTU differences between the Cisco and Juniper enviroment? Can you ping with large packets from your client(s)
Again - these are more brain storm like questions but I hope they can help making progress :-)
Please also check if there's any MAC limit config or firewall filter at the interface or VLAN level sitting on the Juniper inadvertently.
show configuration vlans | display set | display inheritance show interfaces | display set | display inheritance show configuration ethernet-switching-options (Non-ELS) or show configuration switch-options (ELS/post Junos 12.3)
Hi, i did a comparison between the setup of the working printer and the one's not working. Only disparity was on the working printer ipv6 was disabled. Did the same on the others and now they seems to work. Other models however is still doing the same but they havent been upgraded to the latest software, so waiting on that.