[j-nsp] Fwd: logical router with physical Interco
juniper light
juniperlight at gmail.com
Wed Dec 22 03:24:28 EST 2010
thanks Nilesh and Cristian ,
I checked the autoneg and it seems ok ( show interface extensive) :
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link mode: Full-duplex, Flow control: None, Remote fault: OK
I lunch 2 pings :
ping 10.0.24.1 count 1000
ping logical-router PE2 10.0.123.2 count 1000
and I have been collecting info from FEB but nothing happen always same
result before and during and after the pings :
admin at M10> start shell pfe network feb
SBR platform (266Mhz PPC 603e processor, 64MB memory, 512KB flash)
SBR(M10 vty)# bringup bchip 0 read 0x3002
B0 0x00003002: 0x00000000
SBR(M10 vty)#
any idea Nilesh?
Cristian :
information in log chassid seems correct and also there no reject on the
"show route ..." command :
log chassid
Dec 21 18:21:01 FPC 0 PIC 3, attaching clean
Dec 21 18:21:01 create_pic_entry: pic i2c 0x214, hw qs 4 supported qs 4,
flags 0x0, pic port 0
Dec 21 18:21:01 create_pic_entry: pic i2c 0x214, hw qs 4 supported qs 4,
flags 0x0, pic port 1
Dec 21 18:21:01 create_pic_entry: pic i2c 0x214, hw qs 4 supported qs 4,
flags 0x0, pic port 2
Dec 21 18:21:01 create_pic_entry: pic i2c 0x214, hw qs 4 supported qs 4,
flags 0x0, pic port 3
Dec 21 18:21:01 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface
device for fe-0/3/0
Dec 21 18:21:01 fe-0/3/0: large delay buffer cleared
Dec 21 18:21:01 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface
device for fe-0/3/1
Dec 21 18:21:01 fe-0/3/1: large delay buffer cleared
Dec 21 18:21:01 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface
device for fe-0/3/2
Dec 21 18:21:01 fe-0/3/2: large delay buffer cleared
Dec 21 18:21:01 CHASSISD_IFDEV_CREATE_NOTICE: create_pics: created interface
device for fe-0/3/3
Dec 21 18:21:01 fe-0/3/3: large delay buffer cleared
Dec 21 18:21:01 hwdb: entry for pic 532 at slot 3 in fpc 0 inserted
Dec 21 18:21:01 PIC message op 1
Dec 21 18:21:06 send: slot_info request for slot 0
Dec 21 18:21:06 send: slot_info request for slot 1
Dec 21 18:21:06 rcv reply: Slot Info 0 State 3
Dec 21 18:21:06 CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on
(jnxFruContentsIndex 7, jnxFruL1Index 1, jnxFruL2Index 0, jnxFruL3Index 0,
jnxFruName FPC: @ 0/*/*, jnxFruType 3, jnxFruSlot 1, jnxFruOfflineReason 2,
jnxFruLastPowerOff 0, jnxFruLastPowerOn 10585)
Dec 21 18:21:06 hwdb: entry for pic at slot 0 in fpc 0 updated
Dec 21 18:21:06 rcv: Set Slot Info fpc 0, pic 0 valid
Dec 21 18:21:06 hwdb: entry for pic at slot 1 in fpc 0 updated
Dec 21 18:21:06 rcv: Set Slot Info fpc 0, pic 1 valid
Dec 21 18:21:06 hwdb: entry for pic at slot 2 in fpc 0 updated
Dec 21 18:21:06 rcv: Set Slot Info fpc 0, pic 2 valid
Dec 21 18:21:06 hwdb: entry for pic at slot 3 in fpc 0 updated
Dec 21 18:21:06 rcv: Set Slot Info fpc 0, pic 3 valid
Dec 21 18:21:06 rcv reply: Slot Info 1 State 3
Dec 21 18:21:06 CHASSISD_SNMP_TRAP10: SNMP trap generated: FRU power on
(jnxFruContentsIndex 7, jnxFruL1Index 2, jnxFruL2Index 0, jnxFruL3Index 0,
jnxFruName FPC: @ 1/*/*, jnxFruType 3, jnxFruSlot 2, jnxFruOfflineReason 2,
jnxFruLastPowerOff 0, jnxFruLastPowerOn 10585)
Dec 21 19:44:23
show route logical-router PE2
inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.123.0/30 *[Direct/0] 12:12:45
> via fe-0/3/0.123
10.0.123.1/32 *[Local/0] 12:12:48
Local via fe-0/3/0.123
show route logical-router PE3
inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.0.123.0/30 *[Direct/0] 10:47:51
> via fe-0/3/1.123
10.0.123.2/32 *[Local/0] 12:20:04
Local via fe-0/3/1.123
here is the configuration again :
fe-0/3/0 and fe-0/3/1 back to back connection ( crossover cable )
fe-0/3/2 =>> connected to annother router
set logical-routers PE2 interfaces fe-0/3/0 unit 123 vlan-id 123
set logical-routers PE2 interfaces fe-0/3/0 unit 123 family inet address
10.0.123.1/30
set logical-routers PE3 interfaces fe-0/3/1 unit 123 vlan-id 123
set logical-routers PE3 interfaces fe-0/3/1 unit 123 family inet address
10.0.123.2/30
set chassis aggregated-devices ethernet device-count 1
set interfaces fe-0/3/0 vlan-tagging
set interfaces fe-0/3/1 vlan-tagging
set interfaces fe-0/3/2 unit 0 family inet address 10.0.24.2/30
set interfaces fxp0 unit 0 family inet address 172.31.16.35/25
set interfaces fxp1 disable
any idea
thanks guys
On Tue, Dec 21, 2010 at 11:01 PM, Nilesh Khambal <nkhambal at juniper.net>wrote:
> One thing to check would be auto negotiation on the ports. 4xFE port does
> not work in half-duplex mode. If the AN fails we would fall back to
> half-duplex mode and the pic would basically not forward anything out of
> the
> port. From the FEB colllect this command output by running a ping across
> the
> port in background. Take multiple snapshots.
>
> To log into the FEB, do "start shell pfe network feb0|cfeb0" depending on
> whether its M10 or M10i.
>
> - bringup bchip 0 read 0x3002
>
> Thanks,
> Nilesh.
>
> On 12/21/10 1:46 PM, "Cristian Frizziero" <cristian.frizziero at iquall.net>
> wrote:
>
> > Ok,
> >
> > It looks like a hardware problem (at PIC or EFEB level, may be).
> > I´d be a good idea to change the cable too.... just in case....
> >
> > Check with show log chassid , may be you can find some log related to a
> > physical problem.
> >
> > Also check with a show route logical-router PE2 or PE3. You must find
> > your subnets and physical addresses of your interfaces. If you find some
> > route marked as rejected you could think in some problem of connectivity
> > in L1.
> >
> > Good luck
> >
> > logo impre
> > Ing. Cristian Frizziero
> > Honorio Pueyrredon 1475 -- Buenos Aires
> > Tel+54.11.4855.6041 (Ext.517)
> > Cel+54.9.11.6249.1303
> > cristian.frizziero at iquall.net <mailto:cristian.frizziero at iquall.net>
> > www.iquall.net <http://www.iquall.net>
> >
> >
> >
> > El 21/12/2010 18:34, juniper light escribió:
> >> I didn't change cabling, but I connected a new interface to annother
> >> router and I'm having the same problem, the new interface is in the
> >> default configuration :
> >> set interfaces fe-0/3/2 unit 0 family inet address 10.0.24.2/30
> >> <http://10.0.24.2/30>
> >> admin at M10 <mailto:admin at M10>> show interfaces terse
> >> Interface Admin Link Proto Local Remote
> >> ...
> >> fe-0/3/0 up up
> >> fe-0/3/0.123 up up inet 10.0.123.1/30
> >> <http://10.0.123.1/30>
> >> fe-0/3/0.32767 up up
> >> fe-0/3/1 up up
> >> fe-0/3/1.123 up up inet 10.0.123.2/30
> >> <http://10.0.123.2/30>
> >> fe-0/3/1.32767 up up
> >> fe-0/3/2 up up
> >> fe-0/3/2.0 up up inet 10.0.24.2/30 <
> http://10.0.24.2/30>
> >> fe-0/3/3 up up
> >> any idea guys ?
> >> BR // Mounir
> >>
> >>
> >> On Tue, Dec 21, 2010 at 7:25 PM, Cristian Frizziero
> >> cristian.frizziero at iquall.net <mailto:cristian.frizziero at iquall.net>
> >> wrote:
> >>
> >> Hi!!
> >>
> >> I'd try to change ports pairs, and to switch the PIC to a
> >> different fpc slot, just to be sure that there is no hardware
> >> issue....
> >>
> >> The configuration looks fine....
> >>
> >> Cristian
> >>
> >>
> >> El 21/12/2010 15:07, juniper light escribió:
> >>> Hi guys, I would like to use M10 to simulate 3 PE, using
> >>> logical-routers ( Junos 8.4R4.2 ) I connected 2 fastethernet
> >>> back-to-back, link are UP. but when I tried configuring vlan-id ,
> >>> I cannot ping from one Logical router to the other : first
> >>> scenario using Vlan-tagging : set logical-routers PE2 interfaces
> >>> fe-0/3/0 unit 23 vlan-id 123 set logical-routers PE2 interfaces
> >>> fe-0/3/0 unit 23 family inet address 10.0.123.1/30
> >>> <http://10.0.123.1/30> set logical-routers PE3 interfaces
> >>> fe-0/3/1 unit 23 vlan-id 123 set logical-routers PE3 interfaces
> >>> fe-0/3/1 unit 23 family inet address 10.0.123.2/30
> >>> <http://10.0.123.2/30> set interfaces fe-0/3/0 vlan-tagging set
> >>> interfaces fe-0/3/1 vlan-tagging admin at M10> show interfaces terse
> >>> Interface Admin Link Proto Local Remote ... fe-0/3/0 up up
> >>> fe-0/3/0.123 up up inet 10.0.123.1/30 fe-0/3/0.32767
> >>> <http://10.0.123.1/30fe-0/3/0.32767> up up fe-0/3/1 up up
> >>> fe-0/3/1.123 up up inet 10.0.123.2/30 fe-0/3/1.32767
> >>> <http://10.0.123.2/30fe-0/3/1.32767> up up fe-0/3/2 up up
> >>> fe-0/3/3 up up Second scenario without Vlan-tagging : set
> >>> logical-routers PE2 interfaces fe-0/3/0 unit 0 family inet
> >>> address 10.0.123.1/30 <http://10.0.123.1/30> set logical-routers
> >>> PE3 interfaces fe-0/3/1 unit 0 family inet address 10.0.123.2/30
> >>> <http://10.0.123.2/30> admin at M10> ping logical-router PE2
> >>> 10.0.123.2 source 10.0.123.1 PING 10.0.123.2 (10.0.123.2): 56
> >>> data bytes nothing happen ...... admin at M10> show interfaces terse
> >>> Interface Admin Link Proto Local Remote ... fe-0/3/0 up up
> >>> fe-0/3/0.0 up up inet 10.0.123.1/30 fe-0/3/1
> >>> <http://10.0.123.1/30fe-0/3/1> up up fe-0/3/1.0 up up inet
> >>> 10.0.123.2/30 fe-0/3/2 <http://10.0.123.2/30fe-0/3/2> up up
> >>> fe-0/3/3 up up admin at M10
> >>>> show chassis hardware
> >>> Hardware inventory:
> >>> Item Version Part number Serial number
> Description
> >>> Chassis xxxx M10
> >>> Midplane REV 03 710-001950 xxx M10 Backplane
> >>> Power Supply A Rev 05 740-002497 xxx AC Power Supply
> >>> Display REV 04 710-001995 xxx M10 Display
> Board
> >>> Routing Engine REV 07 740-007603 xxx RE-3.0
> >>> FEB REV 08 710-003310 xx E-FEB
> >>> FPC 0 E-FPC
> >>> PIC 1 REV 05 750-003163 xxx 1x G/E, 1000
> >>> BASE-SX
> >>> PIC 3 REV 06 750-002992 xxx 4x F/E, 100
> >>> BASE-TX
> >>> FPC 1 E-FPC
> >>> Fan Tray Rear Left
> Fan
> >>> Tray
> >>>
> >>> Any idea about that ?
> >>>
> >>> Thanks for your help,
> >>>
> >>> Kind Regards
> >>> // Mounir
> >>> _______________________________________________
> >>> juniper-nsp mailing listjuniper-nsp at puck.nether.net
> >>> <mailto:juniper-nsp at puck.nether.net>
> >>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >>
> >>
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
More information about the juniper-nsp
mailing list