Ethernet Switching
Ethernet Switching

Fluking Ports

05.09.14   |  
‎05-09-2014 06:29 AM

We have some demo switches at our location and I've been playing around with one in anticipation of our infrastructure upgrade.  We use Fluke LinkRunner AT 1000's and when I fluke a port on these switches I get a number instead of the port id that I get when I fluke a Cisco switch.  An example would be port ge-0/0/0 returns 505 for the port.

 

Does anyone else have this issue or is there something misconfigured on our Fluke or switches.

18 REPLIES
Ethernet Switching

Re: Fluking Ports

05.09.14   |  
‎05-09-2014 06:36 AM

You are getting the SNMP index:

 

{master:0}
root@EX>                               

{master:0}
root@EX> show snmp mib walk ifDescr | grep ge-0/0/0    
ifDescr.504   = ge-0/0/0

{master:0}
root@EX> show snmp mib walk ifIndex | grep 504         
ifIndex.504   = 504

{master:0}
root@EX>

 

I don't know if there is actually something wrong as I never used any Fluke devices.

 

 

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Ethernet Switching

Re: Fluking Ports

05.09.14   |  
‎05-09-2014 09:24 AM

I'm pretty sure that Fluke is defaulting to CDP (Cisco Discovery Protocol) to gather this information. 

 

See if it supports LLDP which is the open standard then enable LLDP on the access ports.

Steve Puluka BSEET
Juniper Ambassador
Senior IP Engineer - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
JNCIA-Junos JNCIS-SEC JNCIP-SEC JNCSP-SEC
JNCIS-FWV
JNCDA JNCDS-DC JNCDS-SEC
JNCIS-SP
ACE PanOS 6 ACE PanOS 7
http://puluka.com/home
Ethernet Switching

Re: Fluking Ports

01.12.17   |  
‎01-12-2017 10:55 AM

have You ever figure it out the problem?

Ethernet Switching

Re: Fluking Ports

01.15.17   |  
‎01-15-2017 10:42 AM

I'm pretty sure if you enable LLDP on the ports in question you will get the desired behavior

 

https://www.juniper.net/documentation/en_US/junos13.3/topics/task/configuration/802-1x-lldp-cli.html

 

 

Steve Puluka BSEET
Juniper Ambassador
Senior IP Engineer - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
JNCIA-Junos JNCIS-SEC JNCIP-SEC JNCSP-SEC
JNCIS-FWV
JNCDA JNCDS-DC JNCDS-SEC
JNCIS-SP
ACE PanOS 6 ACE PanOS 7
http://puluka.com/home
Ethernet Switching

Re: Fluking Ports

[ Edited ]
01.15.17   |  
‎01-15-2017 07:25 PM

Hi Folks,

As per my understanding the tester gets the post information by CDP/LLDP/EDP from your managed switches. Based on the switch [cisco/juniper/hp/etc] basically default deployed on standard or proprietary protocol that switch handles we need to tweak the tester to detect the port.

 

 

Datasheet: LinkRunner™ AT
Nearest switch and VLAN information — uses IEEE Link Layer Discovery Protocol (LLDP) plus the Cisco® and Extreme Discovery Protocols (CDP and EDP) to display the VLAN and nearest switch model, slot and port.

-Python JNCIP-DC|ENT|SP CCIP JNCDA ITIL
#Please mark my solution as accepted if it helped, Kudos are appreciated as well.
Ethernet Switching

Re: Fluking Ports

09.06.17   |  
‎09-06-2017 01:00 PM

Has this been resolved? I am having issue with this. 

Ethernet Switching

Re: Fluking Ports

09.06.17   |  
‎09-06-2017 02:46 PM

For this to work you need to have lldp enabled on the ports that connect to the Fluke.  This is in the default confiugration for most juniper access switches

 

set protocols lldp interface all

 

But can be removed or restricted to just listed ports.

 

And the Fluke has to be looking for LLDP and not CDP (the cisco propritary method).

Steve Puluka BSEET
Juniper Ambassador
Senior IP Engineer - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
JNCIA-Junos JNCIS-SEC JNCIP-SEC JNCSP-SEC
JNCIS-FWV
JNCDA JNCDS-DC JNCDS-SEC
JNCIS-SP
ACE PanOS 6 ACE PanOS 7
http://puluka.com/home
Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 04:55 AM

I have all configured correctly on Juniper and Fluke. When Upgraded to 15.X on Juniper now I see only port description, no VLAN information, and sometimes I see VMWARE ESX port with mac or phone MAC and phone IP when connect to VOICE port which has data & voice vlan configured - this is totally cray now. Never seen these info before with old Juniper OS. 

 

 

Something must have had chnaged. 

 

I have a case opened with Fluke but should I open one with Juniper? 

 

P.S there is not much I can change on Fluke since this tool is pretty simple to use. 

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 05:37 AM

Which exact EX model are you using? If legacy (non-ELS based) EX switch I might suggest going back to some (latest?) 12.3 instead of 15.1.  I believe LLDP works as expected in 12.3, not so sure about 15.1.  If using 15.1, which exact version - R6-S2?

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 05:41 AM

I use some 2200C 3300 & 4300, but the wired bahavoiur noticed on 2200C :

 

Hostname: 
Model: ex2200-c-12p-2g
Junos: 15.1R5.5
JUNOS EX Software Suite [15.1R5.5]
JUNOS FIPS mode utilities [15.1R5.5]
JUNOS Online Documentation [15.1R5.5]
JUNOS EX 2200 Software Suite [15.1R5.5]
JUNOS Web Management Platform Package [15.1R5.5]
JUNOS Web Management Application package [15.1A3]

 

This is on all 3300 and 2200, 4300 has different OS. 

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 06:20 AM

There is a KB out there to NOT run 15.1 on EX2200/EX2200-C - TSB 17138

 

https://kb.juniper.net/InfoCenter/index?page=content&id=S:TSB17138&IQ_SESSION_ID=ffc22345-66bd-4bdf-...

 

FYI.

 

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 07:19 AM

ahhhhhh ok this is for 2200C 

 

what about 3300 ?   

 

I have 2200C installed in small IDFs so this should not be a big deal to donwgrade the OS.

 

Thank You so much for help here. 

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 07:35 AM

I'd suggest 12.3 for EX3300 as well, but that is your call.  For 4300 14.1X53 is my best recommendation, today.

Ethernet Switching

Re: Fluking Ports

09.07.17   |  
‎09-07-2017 07:41 AM

I have found these:

 

 

https://kb.juniper.net/InfoCenter/index?page=content&id=KB21476

 

3300 15R.1 should be ok

Ethernet Switching

Re: Fluking Ports

09.08.17   |  
‎09-08-2017 02:29 AM

What was your previous version of code?

 

There was a major change in the handling of layer 2 vlans recently.  You may need to convert from old style vlans to the ELS system as part of your upgrade process.

 

https://www.juniper.net/documentation/en_US/junos/topics/task/configuration/getting-started-els.html

Steve Puluka BSEET
Juniper Ambassador
Senior IP Engineer - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
JNCIA-Junos JNCIS-SEC JNCIP-SEC JNCSP-SEC
JNCIS-FWV
JNCDA JNCDS-DC JNCDS-SEC
JNCIS-SP
ACE PanOS 6 ACE PanOS 7
http://puluka.com/home
Ethernet Switching

Re: Fluking Ports

09.08.17   |  
‎09-08-2017 04:37 AM

before we had 12.3 now 15.1R5

Highlighted
Ethernet Switching

Re: Fluking Ports

09.08.17   |  
‎09-08-2017 09:04 AM

"There was a major change in the handling of layer 2 vlans recently.  You may need to convert from old style vlans to the ELS system as part of your upgrade process."

 

This statement is inaccurate.  SW does NOT change CLI style between old [non-ELS] and newer ELS.  This is determined 100% by hardware platform.  Legacy EX use non-ELS always.  Newer EX use ELS always.  You can not take an EX product and move from format to the other via SW.

 

FYI

Ethernet Switching

Re: Fluking Ports

09.09.17   |  
‎09-09-2017 05:19 AM

Thanks, I didn't notice that the change was only occuring per hardware platform.

 

I have all configured correctly on Juniper and Fluke. When Upgraded to 15.X on 
Juniper now I see only port description, no VLAN information, and sometimes I see
VMWARE ESX port with mac or phone MAC and phone IP when connect to VOICE port which
has data & voice vlan configured - this is totally cray now. Never seen these info
before with old Juniper OS.

In this case then you seem to have encounter a bug know as PR (problem reports).  Searching the public db I see a number of lldp issues but none of these seem to match your description exactly.

 

https://prsearch.juniper.net/InfoCenter/index?page=prsearch#qt=lldp&bv=12.3R1&uv=15.1R5&sid=ex&dt=0&...

 

If you also don't see a match here, you will need to open a JTAC ticket to get the data collected and the PR into the system for correction.

Steve Puluka BSEET
Juniper Ambassador
Senior IP Engineer - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
JNCIA-Junos JNCIS-SEC JNCIP-SEC JNCSP-SEC
JNCIS-FWV
JNCDA JNCDS-DC JNCDS-SEC
JNCIS-SP
ACE PanOS 6 ACE PanOS 7
http://puluka.com/home