Routing

Hi Everyone,

     Maybe you guys can help me out. I am trying to bring up and interface between a J2300 and SRX100 however I am unsucessfull. Below is the configuration interface output for both the J2300 and SRX100 router. What I find weird is that I cannot see the interface Fe-0/0/0 and Fe-0/0/1 when I execute the "show interface terse" command but when I do for example "show configuration interface" I see the interfaces in the config. Thank you

Physical Layout:

J2300(Juniper3) Port 1 --->>>>  SRX100(Juniper1)

J2300(Juniper3) Port 0 --->>>>  SRX100(Juniper2)

Juniper3 Output:

root@Juniper3> show interfaces terse
Interface Admin Link Proto Local Remote
dsc up up
gre up up
ipip up up
lo0 up up
lsi up up
mtun up up
pimd up up
pime up up
tap up up

root@Juniper3> show configuration interfaces
fe-0/0/0 {
enable;
unit 0 {
family inet {
address 200.10.240.1/24;
address 20.0.0.1/24;
address 192.168.23.3/24;
}
}
}
fe-0/0/1 {
speed 100m;
link-mode full-duplex;
unit 0 {
family inet {
address 192.168.26.1/31;
}
}
}

root@Juniper3>

Juniper2 Output:

root@Juniper2> show interfaces terse
Interface Admin Link Proto Local Remote
fe-0/0/0 up up
fe-0/0/0.0 up up
gr-0/0/0 up up
ip-0/0/0 up up
lt-0/0/0 up up
mt-0/0/0 up up
sp-0/0/0 up up
sp-0/0/0.0 up up inet
sp-0/0/0.16383 up up inet 10.0.0.1 --> 10.0.0.16
10.0.0.6 --> 0/0
128.0.0.1 --> 128.0.1.16
128.0.0.6 --> 0/0
fe-0/0/1 up up
fe-0/0/1.0 up up eth-switch
fe-0/0/2 up down
fe-0/0/2.0 up down eth-switch
fe-0/0/3 up down
fe-0/0/3.0 up down eth-switch
fe-0/0/4 up up
fe-0/0/4.0 up up eth-switch
fe-0/0/5 up down
fe-0/0/5.0 up down eth-switch
fe-0/0/6 up down
fe-0/0/6.0 up down eth-switch
fe-0/0/7 up down
fe-0/0/7.0 up down eth-switch
gre up up
ipip up up
irb up up
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet 10.0.0.1 --> 0/0
10.0.0.16 --> 0/0
128.0.0.1 --> 0/0
128.0.1.16 --> 0/0
lo0.32768 up up
lsi up up
mtun up up
pimd up up
pime up up
pp0 up up
ppd0 up up
ppe0 up up
st0 up up
tap up up
vlan up up
vlan.0 up up inet 192.168.1.1/24

root@Juniper2> show configuration interfaces
fe-0/0/0 {
unit 0;
}
fe-0/0/1 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/2 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/3 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/4 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/5 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/6 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/7 {
speed 100m;
link-mode full-duplex;
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
vlan {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}

root@Juniper2>

Juniper1 Output:

root@Juniper1> show interfaces terse
Interface Admin Link Proto Local Remote
fe-0/0/0 up up
fe-0/0/0.0 up up
gr-0/0/0 up up
ip-0/0/0 up up
lt-0/0/0 up up
mt-0/0/0 up up
sp-0/0/0 up up
sp-0/0/0.0 up up inet
sp-0/0/0.16383 up up inet 10.0.0.1 --> 10.0.0.16
10.0.0.6 --> 0/0
128.0.0.1 --> 128.0.1.16
128.0.0.6 --> 0/0
fe-0/0/1 up up
fe-0/0/1.0 up up eth-switch
fe-0/0/2 up down
fe-0/0/2.0 up down eth-switch
fe-0/0/3 up down
fe-0/0/3.0 up down eth-switch
fe-0/0/4 up up
fe-0/0/4.0 up up eth-switch
fe-0/0/5 up down
fe-0/0/5.0 up down eth-switch
fe-0/0/6 up down
fe-0/0/6.0 up down eth-switch
fe-0/0/7 up down
fe-0/0/7.0 up down eth-switch
gre up up
ipip up up
irb up up
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet 10.0.0.1 --> 0/0
10.0.0.16 --> 0/0
128.0.0.1 --> 0/0
128.0.0.4 --> 0/0
128.0.1.16 --> 0/0
lo0.32768 up up
lsi up up
mtun up up
pimd up up
pime up up
pp0 up up
ppd0 up up
ppe0 up up
st0 up up
tap up up
vlan up up
vlan.0 up up inet 192.168.1.1/24

root@Juniper1> show configuration interfaces
fe-0/0/0 {
unit 0;
}
fe-0/0/1 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/2 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/3 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/4 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/5 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/6 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
fe-0/0/7 {
unit 0 {
family ethernet-switching {
vlan {
members vlan-trust;
}
}
}
}
vlan {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}

root@Juniper1>

Hello there,

---

victor.reyes.ii@citi.com wrote:

Hi Everyone,

 

     What I find weird is that I cannot see the interface Fe-0/0/0 and Fe-0/0/1 when I execute the "show interface terse" command but when I do for example "show configuration interface" I see the interfaces in the config. Thank you

 

 

 

 

---

It is well-known JUNOS feature that You can configure non-existing interfaces, then plug in the linecard+cables and it starts to work/pass traffic.

On the topic - what is the J2300 exact model and JUNOS version?

Please post the following printouts, You may wat to conceal serial numbers:

show chassis hardware extensive | no-more
show version detail | no-more

 HTH

Thanks
Alex

Hi, When I try the first command "show chassis hardware detail | no-more" I get the message you see below. Regarding the second command below is the output. Thank you

root@Juniper3> show chassis hardware extensive | no-more error: the chassis-control subsystem is not running

root@Juniper3

> show version detail | no-more Hostname: Juniper3 Model: j2300 JUNOS Software Release [7.1R1.3] (Export edition) KERNEL 7.1R1.3 #0 built by builder on 2005-02-11 04:47:41 UTC MGD release 7.1R1.3 built by builder on 2005-02-11 04:34:51 UTC CLI release 7.1R1.3 built by builder on 2005-02-11 04:34:36 UTC CHASSISD release 7.1R1.3 built by builder on 2005-02-11 04:19:15 UTC DFWD release 7.1R1.3 built by builder on 2005-02-11 04:21:38 UTC DCD release 7.1R1.3 built by builder on 2005-02-11 04:17:04 UTC RPD release 7.1R1.3 built by builder on 2005-02-11 04:35:03 UTC SNMPD release 7.1R1.3 built by builder on 2005-02-11 04:26:03 UTC MIB2D release 7.1R1.3 built by builder on 2005-02-11 04:23:45 UTC VRRPD release 7.1R1.3 built by builder on 2005-02-11 04:26:47 UTC ALARMD release 7.1R1.3 built by builder on 2005-02-11 04:18:56 UTC PFED release 7.1R1.3 built by builder on 2005-02-11 04:25:04 UTC CRAFTD release 7.1R1.3 built by builder on 2005-02-11 04:21:25 UTC SAMPLED release 7.1R1.3 built by builder on 2005-02-11 04:25:43 UTC RMOPD release 7.1R1.3 built by builder on 2005-02-11 04:25:25 UTC COSD release 7.1R1.3 built by builder on 2005-02-11 04:21:09 UTC KMD release 7.1R1.3 built by builder on 2005-02-11 04:51:42 UTC NASD release 7.1R1.3 built by builder on 2005-02-11 04:24:58 UTC FUD release 7.1R1.3 built by builder on 2005-02-11 04:21:56 UTC PPMD release 7.1R1.3 built by builder on 2005-02-11 04:35:00 UTC SPD release 7.1R1.3 built by builder on 2005-02-11 04:26:27 UTC PGMD release 7.1R1.3 built by builder on 2005-02-11 04:34:57 UTC BFDD release 7.1R1.3 built by builder on 2005-02-11 04:34:33 UTC HTTPD release 7.1R1.3 built by builder on 2005-02-11 04:51:40 UTC AUTOD release 7.1R1.3 built by builder on 2005-02-11 04:47:45 UTC FWDD release 7.1R1.3 built by builder on 2005-02-11 04:52:29 UTC SDXD release 7.1R1.3 built by builder on 2005-02-11 04:39:50 UTC DHCPD release 7.1R1.3 built by builder on 2005-02-11 04:47:56 UTC USBD release 7.1R1.3 built by builder on 2005-02-11 04:48:05 UTC PPPOED release 7.1R1.3 built by builder on 2005-02-11 04:25:19 UTC jkernel-dd release 7.1R1.3 built by builder on 2005-02-11 04:08:53 UTC jroute-dd release 7.1R1.3 built by builder on 2005-02-11 04:09:28 UTC jcrypto-dd release 7.1R1.3 built by builder on 2005-02-11 04:10:05 UTC

root@Juniper3

>

Hello,

The issue is with Chassisd:

root@Juniper3> show chassis hardware extensive | no-more error: the chassis-control subsystem is not running

 You may wish to try:

restart chassis-control

 Failing that, a reboot. 

If the issue persists after reboot, upgrade Your JUNOS - You may get older J2300-compatible code through JTAC if You have a support contract.

HTH

Thanks

Alex

Thank you I rebooted the router again the and chassis control daemon started again. Thank you