Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[SRX/J-series] Unable to see the physical interface in 'show interface terse' on Chassis Cluster (after upgrade or in initial installation)

0

0

Article ID: KB23033 KB Last Updated: 18 Apr 2013Version: 3.0
Summary:
This article describes the issue of being unable to see any physical interface in show interface terse.

Additionally, the cluster status is shown as hold; even after all the requirements of high-availability are fulfilled (for more information, refer to KB16141 - What are the minimum hardware and software requirements for a Chassis Cluster (JSRP) on SRX?).
Symptoms:
Output of show interfaces terse:

root> show interfaces terse
Interface Admin Link Proto Local Remote
fxp0 up up
fxp1 up up
gre up up
ipip up up
lo0 down up
lo0.32768 up down
lsi up up
mtun up up
pimd up up
pime up up
tap down up

{hold:node0}
root> show chassis cluster status
Cluster ID: 1
Node Priority Status Preempt Manual failover

Redundancy group: 0 , Failover count: 0
node0 1 hold no no
node1 0 lost n/a n/a

{hold:node0}
root> show version
error: Could not connect to node0 : No route to host



Cause:
This is caused when the management or control interfaces are configured on the device.

{hold:node0}
root> edit
warning: Clustering enabled; using private edit
error: shared configuration database modified

Please temporarily use 'configure shared' to commit
outstanding changes in the shared database, exit,
and return to configuration mode using 'configure'

{hold:node0}
root> configure shared
Entering configuration mode
The configuration has been changed but not committed

{hold:node0}[edit]
root# show interfaces | display set
set interfaces fe-0/0/1 fastether-options redundant-parent reth0
set interfaces fe-0/0/2 fastether-options redundant-parent reth1
set interfaces fe-0/0/7 unit 0 family inet address 192.168.0.1/24 < (Control interface on SRX100)
set interfaces fe-1/0/1 fastether-options redundant-parent reth0
set interfaces fe-1/0/2 fastether-options redundant-parent reth1
set interfaces fab0 fabric-options member-interfaces fe-0/0/5
set interfaces fab1 fabric-options member-interfaces fe-1/0/5
set interfaces reth0 redundant-ether-options redundancy-group 1
set interfaces reth0 unit 0 family inet address 192.168.100.1/24
set interfaces reth1 redundant-ether-options redundancy-group 1
set interfaces reth1 unit 0 family inet address 172.16.1.1/24
Solution:
Delete the configured management and control interface on the device and their related configuration and commit the changes. This will help to resolve the issue.

{hold:node0}[edit]
root# delete interfaces fe-0/0/7

{hold:node0}[edit]
root# delete security zones security-zone trust interfaces fe-0/0/7.0

{hold:node0}[edit]
root# commit
node0:
commit complete

{primary:node0}[edit]
root@Node_0# run show interfaces terse
Interface Admin Link Proto Local Remote
fe-0/0/0 up down
fe-0/0/1 up down
fe-0/0/1.0 up down aenet --> reth0.0
fe-0/0/2 up down
fe-0/0/2.0 up down aenet --> reth1.0
fe-0/0/3 up down
fe-0/0/4 up down
fe-0/0/5 up down
fe-0/0/5.0 up down aenet --> fab0.0
fe-0/0/6 up down
fe-0/0/7 up up
fab0 up down
fab0.0 up down inet 30.17.0.200/24
fxp0 up up
fxp0.0 up up inet 10.20.30.1/24
fxp1 up up
fxp1.0 up up inet 129.16.0.1/2
tnp 0x1100001
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
reth0 up down
reth0.0 up down inet 192.168.100.1/24
reth1 up down
reth1.0 up down inet 172.16.1.1/24
st0 up up
tap up up

{primary:node0}[edit]
root@Node_0# run show chassis cluster status
Cluster ID: 1
Node Priority Status Preempt Manual failover

Redundancy group: 0 , Failover count: 0
node0 200 primary no no
node1 1 secondary no no

Redundancy group: 1 , Failover count: 0
node0 200 primary no no
node1 1 secondary no no

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search