Switching

Hi, 

Do you see any mac-addresses on the switch or arp on both sides

show ethernet-switching table [vlan VLAN100]
show arp

Also with a ping running from ASR1 to 10.10.100.3, do you see any traffic on ge-0/0/30:

monitor traffic interface ge-0/0/30

Cheers,

Ashvin

Even after initiating pings from both routers, this is the MAC table output from the Juniper Switch:

Ethernet-switching table: 0 unicast entries
  VLAN              MAC address       Type         Age Interfaces
  VLAN100           *                 Flood          - All-members
  VLAN100           dc:38:e1:a1:5c:41 Static         - Router

That MAC address is associated with the VLAN IP I assigned.

The following is the monitor output during a ping:

verbose output suppressed, use <detail> or <extensive> for full protocol decode
Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on ge-0/0/30, capture size 96 bytes

12:05:54.567470 Out LLDP, name ****JUNIPER6, length 60
        [|LLDP]
12:06:21.061375 Out LLDP, name ****JUNIPER6, length 60
        [|LLDP]
12:06:49.689345 Out LLDP, name ****JUNIPER6, length 60
        [|LLDP]
12:07:15.323307 Out LLDP, name ****JUNIPER6, length 60
        [|LLDP]
^C
4 packets received by filter
0 packets dropped by kernel

I have also replaced both the cable and the optics for both (Cisco branded in Cisco and Juniper in Juniper), with no luck. 

Hello,

---

@albatross wrote:

I have also replaced both the cable and the optics for both (Cisco branded in Cisco and Juniper in Juniper), with no luck. 

---

Make sure You are not using single-mode cable with multimode optics, and vice versa.

HTH

Thx

Alex

Here is the transciever information for the ASR1 Gig0/0/5 to Juniper6 ge-0/0/30 link.

Juniper:

                       Fiber                    Xcvr vendor       Wave-    Xcvr
Port Cable type        type  Xcvr vendor        part number       length   Firmware
30   GIGE 1000SX       MM    AVAGO              AFBR-5715PZ-JU1   850 nm   0.0

ASR1:

IDPROM for transceiver GigabitEthernet0/0/5:
  Description                               = SFP or SFP+ optics (type 3)
  Transceiver Type:                         = GE SX (19)
  Product Identifier (PID)                  = GLC-SX-MMD          
  Vendor Revision                           = A   
  Serial Number (SN)                        = FNS18272505     
  Vendor Name                               = CISCO           
  Vendor OUI (IEEE company ID)              = 00.90.65 (36965)
  CLEI code                                 = WOTRB9VBAA
  Cisco part number                         = 10-2626-01
  Device State                              = Enabled.
  Date code (yy/mm/dd)                      = 14/07/03
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              NRZ
  Nominal bitrate                           = GE (1300 Mbits/s)
  Minimum bit rate as % of nominal bit rate = not specified
  Maximum bit rate as % of nominal bit rate = not specified

I am using a (teal) multi-mode fiber cable for both connections. 

Hello,

What are Your optical power levels? Are You overdriving the receive side, perhaps?

HTH

Thx

Alex

Here is the diagnostic output for the Juniper6 port ge-0/0/30:

Physical interface: ge-0/0/30
    Laser bias current                        :  6.320 mA
    Laser output power                        :  0.2850 mW / -5.45 dBm
    Module temperature                        :  29 degrees C / 83 degrees F
    Module voltage                            :  3.2980 V
    Receiver signal average optical power     :  0.3273 mW / -4.85 dBm
    Laser bias current high alarm             :  Off
    Laser bias current low alarm              :  Off
    Laser bias current high warning           :  Off
    Laser bias current low warning            :  Off
    Laser output power high alarm             :  Off
    Laser output power low alarm              :  Off
    Laser output power high warning           :  Off
    Laser output power low warning            :  Off
    Module temperature high alarm             :  Off
    Module temperature low alarm              :  Off
    Module temperature high warning           :  Off
    Module temperature low warning            :  Off
    Module voltage high alarm                 :  Off
    Module voltage low alarm                  :  Off
    Module voltage high warning               :  Off
    Module voltage low warning                :  Off
    Laser rx power high alarm                 :  Off
    Laser rx power low alarm                  :  Off
    Laser rx power high warning               :  Off
    Laser rx power low warning                :  Off
    Laser bias current high alarm threshold   :  12.000 mA
    Laser bias current low alarm threshold    :  2.000 mA
    Laser bias current high warning threshold :  10.000 mA
    Laser bias current low warning threshold  :  2.000 mA
    Laser output power high alarm threshold   :  1.1000 mW / 0.41 dBm
    Laser output power low alarm threshold    :  0.0600 mW / -12.22 dBm
    Laser output power high warning threshold :  1.0000 mW / 0.00 dBm
    Laser output power low warning threshold  :  0.0850 mW / -10.71 dBm
    Module temperature high alarm threshold   :  100 degrees C / 212 degrees F
    Module temperature low alarm threshold    :  -40 degrees C / -40 degrees F
    Module temperature high warning threshold :  85 degrees C / 185 degrees F
    Module temperature low warning threshold  :  -10 degrees C / 14 degrees F
    Module voltage high alarm threshold       :  3.630 V
    Module voltage low alarm threshold        :  2.970 V
    Module voltage high warning threshold     :  3.465 V
    Module voltage low warning threshold      :  3.134 V
    Laser rx power high alarm threshold       :  1.8000 mW / 2.55 dBm
    Laser rx power low alarm threshold        :  0.0000 mW / - Inf dBm
    Laser rx power high warning threshold     :  1.0000 mW / 0.00 dBm
    Laser rx power low warning threshold      :  0.0200 mW / -16.99 dBm

And here is what I can find for the other end (ASR1 Gig0/0/5):

The Transceiver in slot 0 subslot 0 port 5 is enabled.
  Module temperature                        = +23.464 C
  Transceiver Tx supply voltage             = 3281.0 mVolts
  Transceiver Tx bias current               = 5906 uAmps
  Transceiver Tx power                      = -4.9 dBm
  Transceiver Rx optical power              = -5.5 dBm

IDPROM for transceiver GigabitEthernet0/0/5:
  Description                               = SFP or SFP+ optics (type 3)
  Transceiver Type:                         = GE SX (19)
  Product Identifier (PID)                  = GLC-SX-MMD          
  Vendor Revision                           = A   
  Serial Number (SN)                        = FNS18272505     
  Vendor Name                               = CISCO           
  Vendor OUI (IEEE company ID)              = 00.90.65 (36965)
  CLEI code                                 = WOTRB9VBAA
  Cisco part number                         = 10-2626-01
  Device State                              = Enabled.
  Date code (yy/mm/dd)                      = 14/07/03
  Connector type                            = LC.
  Encoding                                  = 8B10B
                                              NRZ
  Nominal bitrate                           = GE (1300 Mbits/s)
  Minimum bit rate as % of nominal bit rate = not specified
  Maximum bit rate as % of nominal bit rate = not specified
  The transceiver type is 19 
  Link reach for 9u fiber (km)              = SX(550/270m) (0)
                                              1xFC-MM(500/300m) (0)
                                              2xFC-MM(300/150m) (0)
                                              ESCON-MM(2km) (0)
  Link reach for 9u fiber (m)               = SX(550/270m) (0)
                                              1xFC-MM(500/300m) (0)
                                              2xFC-MM(300/150m) (0)
                                              ESCON-MM(2km) (0)
  Link reach for 50u fiber (m)              = SX(550/270m) (55)
                                              LX(5km/550m) (55)
                                              LX(10km/550m) (55)
  Nominal laser wavelength                  = 850 nm.
  DWDM wavelength fraction                  = 850.0  nm.
  Supported options                         = Tx disable
                                              Loss of signal (standard implementation)
  Diagnostic monitoring                     = Digital diagnostics supported
                                              Diagnostics are internally calibrated
                                              Rx power measured is "Average power"
  Transceiver temperature operating range   = -5 C to 85 C (extended)
  Minimum operating temperature             = -5 C
  Maximum operating temperature             = 85 C
  High temperature alarm threshold          = +90.000 C
  High temperature warning threshold        = +85.000 C
  Low temperature warning threshold         =  -5.000 C
  Low temperature alarm threshold           =  -10.000 C
  High voltage alarm threshold              = 3600.0 mVolts
  High voltage warning threshold            = 3500.0 mVolts
  Low voltage warning threshold             = 3100.0 mVolts
  Low voltage alarm threshold               = 3000.0 mVolts
  High laser bias current alarm threshold   = 15.000 mAmps
  High laser bias current warning threshold = 12.000 mAmps
  Low laser bias current warning threshold  = 2.000 mAmps
  Low laser bias current alarm threshold    = 1.000 mAmps
  High transmit power alarm threshold       =  0.0 dBm
  High transmit power warning threshold     = -3.0 dBm
  Low transmit power warning threshold      = -9.5 dBm
  Low transmit power alarm threshold        = -13.5 dBm
  High receive power alarm threshold        =  3.0 dBm
  High receive power warning threshold      =  0.0 dBm
  Low receive power warning threshold       = -17.0 dBm
  Low receive power alarm threshold         = -21.0 dBm
  External Calibration: bias current slope  = 1.000
  External Calibration: bias current offset = 0

Are you already tried to turn off autonegotiation on the cisco side?
"no negotiation auto"

Hi,

Maybe worth checking the mode [speed / duplex] on both side and any errors on the interfaces.

Could you also check the interface statistics on each end.

show interfaces extensive x/x/x
show interfaces x/x/x extensive | match "Link|neg

Cheers,

Ashvin

Turning off auto-negotiation did not make a difference.

Here are the show interface outputs from both sides...

Juniper

Physical interface: ge-0/0/30, Enabled, Physical link is Up
  Interface index: 239, SNMP ifIndex: 590, Generation: 256
  Description: ASR1 0/0/5
  Link-level type: Ethernet, MTU: 9216, Speed: 1000mbps, Duplex: Full-Duplex, BPDU Error: None,
  MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled,
  Auto-negotiation: Enabled, Remote fault: Online, Media type: Fiber
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x0
  Link flags     : None
  CoS queues     : 8 supported, 8 maximum usable queues
  Hold-times     : Up 0 ms, Down 0 ms
  Current address: dc:38:e1:a1:5c:61, Hardware address: dc:38:e1:a1:5c:61
  Last flapped   : 2016-08-15 15:11:28 EDT (18:12:14 ago)
  Statistics last cleared: Never
  Traffic statistics:
   Input  bytes  :              1736241                    0 bps
   Output bytes  :                17568                    0 bps
   Input  packets:                 5238                    0 pps
   Output packets:                  274                    0 pps
   IPv6 transit statistics:
    Input  bytes  :                   0
    Output bytes  :                   0
    Input  packets:                   0
    Output packets:                   0
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0,
    L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
  Output errors:
    Carrier transitions: 9, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0,
    HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
  Egress queues: 8 supported, 4 in use
  Queue counters:       Queued packets  Transmitted packets      Dropped packets
    0 best-effort                    0                  918                    0
    1 assured-forw                   0                    0                    0
    5 expedited-fo                   0                    0                    0
    7 network-cont                   0                    0                    0
  Queue number:         Mapped forwarding classes
    0                   best-effort
    1                   assured-forwarding
    5                   expedited-forwarding
    7                   network-control

Physical interface: ge-0/0/30, Enabled, Physical link is Up
  Link-level type: Ethernet, MTU: 9216, Speed: 1000mbps, Duplex: Full-Duplex, BPDU Error: None,
  Auto-negotiation: Enabled, Remote fault: Online, Media type: Fiber
  Link flags     : None
    HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
  Autonegotiation information:
    Negotiation status: Complete
    Link partner:
        Link mode: Full-duplex, Flow control: Symmetric, Remote fault: OK, Link partner Speed: 1000 Mbps
        Flow control: Symmetric, Remote fault: Link OK

Cisco

GigabitEthernet0/0/5 is up, line protocol is up 
  Hardware is 6XGE-BUILT-IN, address is f44e.0588.2d05 (bia f44e.0588.2d05)
  MTU 9216 bytes, BW 1000000 Kbit/sec, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation 802.1Q Virtual LAN, Vlan ID  1., loopback not set
  Keepalive not supported 
  Full Duplex, 1000Mbps, link type is auto, media type is SX
  output flow-control is on, input flow-control is on
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 18:13:43, output 00:00:13, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/375/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
     926 packets input, 58833 bytes, 0 no buffer
     Received 908 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 0 throttles 
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 13 multicast, 0 pause input
     6541 packets output, 1825630 bytes, 0 underruns
     0 output errors, 0 collisions, 16 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

Speed and duplex both match up. The stats show some input/output but no errors.

...and couple outputs please .... 🙂

show ethernet-switching interfaces ge-0/0/30 detail

show spanning-tree interface ge-0/0/30

is lldp enabled on cisco devices?

Hello,

GigabitEthernet0/0/5 is up, line protocol is up 
  Hardware is 6XGE-BUILT-IN, address is f44e.0588.2d05 (bia f44e.0588.2d05)
  MTU 9216 bytes, BW 1000000 Kbit/sec, DLY 10 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation 802.1Q Virtual LAN, Vlan ID  1.

looks like Your VLAN IDs do not match. That would explain all Your troubles.

Please double-check, make them the same, then re-test and report back.

HTH

Thx

Alex

But this is default vlan-id of physical interface. It always equal "1" for parental interfaces.

Hi, 

Could you perhaps reset the config on the interfaces and apply a P2P IP config to verify the connectivity. You could apply the inet address on the facing ge-0/0/30.0 interface to test.

Once the connectivity is verified, then you could move to the vlan config.

Cheers,

Ashvin

So, I got in today and noticed that the ASR2 link to to Juniper6 is now working, pings between ASR2's IP and Juniper6's IP is successful. I don't think that there is any difference in configuration here...

Here is the output EssentialRoot requested:

Interface: ge-0/0/30.0, Index: 91, State: up, Port mode: Trunk
Native vlan: VLAN999
Ether type for the interface: 0x8100
VLAN membership:
    VLAN999, 802.1Q Tag: 999, untagged, msti-id: 0, unblocked
    VLAN100, 802.1Q Tag: 100, tagged, msti-id: 0, unblocked
Number of MACs learned on IFL: 0

Spanning tree interface parameters for instance 0

Interface    Port ID    Designated      Designated         Port    State  Role
                         port ID        bridge ID          Cost
ge-0/0/30.0    128:543      128:543  32768.dc38e1a15c41     20000  FWD    DESG 

Both routers have lldp enabled, ASR1 shows no neighbors while ASR2 shows Juniper6 now that that link is working.

Ashvin0, I'm not exactly sure what you mean by "P2P IP Config". I have connected the router ports directly and the pings work then.

I'm going to compare outputs between the two routers so I can try and see why ASR2 is working now (at least partially based on lldp neighbor output).

Hi, 

"P2P IP Config" - I meant using a /30 point to point on the ASR Gi0/0/5 and Juniper ge-0/0/30.0 without any vlan configs.

From the previous monitor traffic, we could see EX sending LLDP

Cheers,

Ashvin

AshvinO,

What you are asking me to do is not possible on the EX4500. The only way to create a routable interface is to create a routed VLAN interface (RVI) which is a logical interface associated with the VLAN rather than any physical port specifically. This is not a Layer 3 switch with routed port capabilities (like the Cisco Nexus 7000).

The fact that the ASR2 connection, with identical optical hardware is now working while the ASR1 connection (and incidentally other ports on both routers) are still not working equally puzzles me. 

Hi, 

I thought family inet on an interface was possible on EX4500:

"Note: Access interfaces on EX2200, EX3200, EX3300, EX4200, and EX4500 switches are set to family ethernet-switching by default. You might have to delete this or another user-configured family setting before changing the setting to family inet or family inet6."

http://www.juniper.net/documentation/en_US/junos15.1/topics/task/configuration/ex-series-gigabit-interfaces-cli.html

Cheers,

Ashvin

Look at this... https://kb.juniper.net/InfoCenter/index?page=content&id=KB23996&smlogin=true&actp=search

maybe native vlans are different for ge-0/0/30 and ge-1/0/34? And this is a cause of LLDP neighbor absence for ASR1.

That does make sense. Though, I did add VLAN 1 to the member list of ge-0/0/30 and that didn't make a difference.

If this is true with lldp, why can Juniper6 and ASR2 see eachother on the ge-1/0/34 gig0/0/5 link while VLAN 1 is not allowed? As you can see in my original post, the native vlan is the same for both links. This just adds in more questions. Here is the detailed lldp neighbor output from he ASR2 side:

Local Intf: Gi0/0/5
Chassis id: dc38.e1a1.5c40
Port id: 616
Port Description: ASR2 0/0/5
System Name: ****JUNIPER6

System Description: 
Juniper Networks, Inc. ex4500-40f , version 12.3R4.6 Build date: 2013-09-13 04:12:57 UTC 

Time remaining: 109 seconds
System Capabilities: B,R
Enabled Capabilities: B,R
Management Addresses:
    IP: ****
    OID:
        *******
Auto Negotiation - supported, enabled
Physical media capabilities:
    1000baseX(FD)
Media Attachment Unit type - not advertised
Vlan ID: 999

And on the Juniper6 side:

LLDP Neighbor Information:
Local Information:
Index: 24 Time to live: 120 Time mark: Wed Aug 17 15:01:55 2016 Age: 8 secs 
Local Interface    : ge-1/0/34.0
Parent Interface   : -
Local Port ID      : 616
Ageout Count       : 0

Neighbour Information:
Chassis type       : Mac address
Chassis ID         : 00:62:ec:52:45:00
Port type          : Interface name
Port ID            : Gi0/0/5.100
Port description   : GigabitEthernet0/0/5.100
System name        : ****-ASR2
  
System Description : Cisco IOS Software, ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S2, RELEASE SOFTWARE (fc2)
                     Technical Support: http://www.cisco.com/techsupport
                     Copyright (c) 1986-2016 by Cisco Systems, Inc.
                     Compiled Thu 11-Feb-16 07:18 by mcpre

System capabilities 
        Supported  : Bridge Router 
        Enabled    : Router 

Management Info 
        Type              : IPv4
        Address           : 10.10.100.2
        Port ID           : 23
        Subtype           : 1
        Interface Subtype : ifIndex(2)
        OID               : 1.3.6.1.2.1.31.1.1.1.1.23

LLDP Neighbor Information:
Local Information:
Index: 23 Time to live: 120 Time mark: Wed Aug 17 15:01:59 2016 Age: 4 secs 
Local Interface    : ge-1/0/34.0
Parent Interface   : -
Local Port ID      : 616
Ageout Count       : 0
                                        
Neighbour Information:
Chassis type       : Mac address
Chassis ID         : 00:62:ec:52:45:00
Port type          : Interface name
Port ID            : Gi0/0/5
Port description   : GigabitEthernet0/0/5
System name        : ****-ASR2
  
System Description : Cisco IOS Software, ASR1000 Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(3)S2, RELEASE SOFTWARE (fc2)
                     Technical Support: http://www.cisco.com/techsupport
                     Copyright (c) 1986-2016 by Cisco Systems, Inc.
                     Compiled Thu 11-Feb-16 07:18 by mcpre

System capabilities 
        Supported  : Bridge Router 
        Enabled    : Router 

Management Info 
        Type              : IPv4
        Address           : ****
        Port ID           : 10
        Subtype           : 1
        Interface Subtype : ifIndex(2)
        OID               : ****

Listen, cisco lldp frames are sent as 802.1Q tagged with VLAN ID 1; even if the VLAN is not configured on the trunk.

try to configure both of ge-0/0/30 and ge-1/0/34 like these:

set interfaces ge-0/0/30 unit 0 family ethernet-switching port-mode trunk
set interfaces ge-0/0/30 unit 0 family ethernet-switching vlan members 100

set interfaces ge-1/0/34 unit 0 family ethernet-switching port-mode trunk
set interfaces ge-1/0/34 unit 0 family ethernet-switching vlan members 100

without any native vlans and without vlanid=1 as member of trunk.

Alright, I deleted the native vlan statements from both ports on the Juniper6 side. They now both look like this:

mtu 9216;
unit 0 {
    family ethernet-switching {
        port-mode trunk;
        vlan {
            members VLAN100;
        }
    }
}

This hasn't made any difference. 

I had thought to restart the switch at some point, I'm going to do that now. I doubt it will make any difference.

You can also swap ASR1 and ASR2 between 0/0/30 and 1/0/34 ports 😄 to make sure that's not a VC problem.

Hey guys,

It looks like cutting power and letting the switch restart has solved the issues....

I'm resisting the urge to take a hammer to this thing. 

Still need to confirm some connectivity.

Wow... it was like a detective story... the butler is the murderer... I always knew that! 😄

Well,

Thanks to everyone who helped me, shame we never figured out the actual root of the problem. Really hope this doesn't pop up again.

Thanks.