A reboot of the re and cards is required after the change.
For minimum time I successfully used the following process
- remove re redundancy configuration
delete routing-options nonstop-routing
delete chassis redundancy graceful-switchover
delete protocols layer2-control nonstop-bridging
commit synchronize
- Make the mode change configuration and commit synchronize
- Prep system for upgrade by saving rescue config and snapshot
- Upgrade backup RE1 & reboot backup RE1
- Verify backup RE is in new forwarding mode
in junos:
show chassis network-services
from shell:
user@router> start shell
% sysctl -a | grep netsvc
net.netsvc: 2
The variable net.netsvc can be one the following values:
0 : IP
1 : ethernet
2 : enhanced IP
3 : enhanced Ethernet
4 : all IP
5 : all Ethernet
6 : enhanced mode
7 : lan
- Switch master to backup RE1 (this is where the cards reboot and downtime occurs)
- Upgrade RE0 & reboot
- Restore redundancy configuration
- Confirm sync & redundancy is good then graceful switch back to RE0
master
show task replication
backup
show system switchover
------------------------------
Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
http://puluka.com/home------------------------------
Original Message:
Sent: 03-16-2021 11:59
From: Cel Mai
Subject: Change from network-services ip to enhanced-ip
Hi,
When changing from ip to enhanced-ip network-services, on the below link, this is required: System reboot is required (PFE/FPCs)
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/chassis-guide-tm-config-ntwrk-srvics-mode.html
Which is different than the other network-services changes, at least in term of words.
As a matter of fact, what exactly is required when changed from ip to enhanced-ip? Full system reboot (all REs and FPCs in the same time) or we can reboot, one by one ?