SRX Junos enable IPv6 and reload procedure chassis cluster

26.04 2023 | by massimiliano

SRX Junos enable IPv6 and reload procedure chassis cluster STEP-1: verifica collegamento interface user@junosfwsrx>; show configuration interfaces reth1 […]

STEP-1: verifica collegamento interface

user@junosfwsrx>; show configuration interfaces reth1 | display set

set interfaces reth1 vlan-tagging

set interfaces reth1 redundant-ether-options redundancy-group 1

user@junosfwsrx>; show configuration interfaces reth2 | display set

set interfaces reth2 vlan-tagging

set interfaces reth2 redundant-ether-options redundancy-group 2

user@junosfwsrx>; show configuration interfaces | display set

set interfaces ge-0/0/4 gigether-options redundant-parent reth1

set interfaces ge-0/0/5 gigether-options redundant-parent reth2

set interfaces ge-5/0/4 gigether-options redundant-parent reth1

set interfaces ge-5/0/5 gigether-options redundant-parent reth2

set interfaces fab0 fabric-options member-interfaces ge-0/0/12

set interfaces fab1 fabric-options member-interfaces ge-5/0/12

STEP-2: monitor interface

user@junosfwsrx>; monitor interface reth1

Delay: 56/0/56

Interface: reth1, Enabled, Link is Up

Encapsulation: Ethernet, Speed: 1000mbps

Traffic statistics: Current delta

Input bytes: 52856956383174 (8608552 bps) [99402373]

Output bytes: 15780046141918 (5497712 bps) [28663469]

Input packets: 43827723644 (1157 pps) [83634]

Output packets: 22337753679 (889 pps) [41252]

Error statistics:

Input errors: 0 [0]

Input drops: 0 [0]

Input framing errors: 0 [0]

Carrier transitions: 0 [0]

Output errors: 0 [0]

Output drops: 0 [0]

user@junosfwsrx>; monitor interface reth2

onafw01c2 Seconds: 18 Time: 15:59:01

Delay: 0/0/60

Interface: reth2, Enabled, Link is Up

Encapsulation: Ethernet, Speed: 1000mbps

Traffic statistics: Current delta

Input bytes: 15886402600408 (8611200 bps) [16136444]

Output bytes: 52924597095604 (29282240 bps) [43048804]

Input packets: 22881492232 (1510 pps) [21890]

Output packets: 43903844650 (3011 pps) [38422]

Error statistics:

Input errors: 0 [0]

Input drops: 0 [0]

Input framing errors: 0 [0]

Carrier transitions: 0 [0]

Output errors: 0 [0]

Output drops: 0 [0]

STEP-3: verifica chassis cluster

user@junosfwsrx>; show chassis cluster status

Monitor Failure codes:

CS Cold Sync monitoring FL Fabric Connection monitoring

GR GRES monitoring HW Hardware monitoring

IF Interface monitoring IP IP monitoring

LB Loopback monitoring MB Mbuf monitoring

NH Nexthop monitoring NP NPC monitoring

SP SPU monitoring SM Schedule monitoring

CF Config Sync monitoring

Cluster ID: 1

Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1

node0 200 primary no no None

node1 100 secondary no no None

Redundancy group: 1 , Failover count: 5

node0 200 primary yes no None

node1 100 secondary yes no None

{primary:node0}

STEP-4: enable ipv6 protocol

L’abilitazione della feature ipv6 richiede i reload dei nodi SRX e pertanto questo comporta azioni di cluster failover

- - Dal nodo secondario abilitare ipv6
  - Dal nodo secondario fare reboot (request system reboot)
  - Switchare il traffic con il failover cluster
  - Dal nodo primario, diventato secondario, abilitare ipv6
  - Dal nodo primario, diventato secondario fare reboot
  - Rimettere il cluster chassis nella posizione originale

Passi 1 e 2:

{secondary:node1}

user@junosfwsrx>edit

{secondary:node1}

user@junosfwsrx# set security forwarding-option family inet6 mode flow-based

{secondary:node1}

user@onafw01c2# commit and-quit

{secondary:node1}

user@junosfwsrx>

VERIFICA

{secondary:node1}

user@junosfwsrx>; show configuration security forwarding-option

family {

inet6 {

mode flow-based;

}

{secondary:node1}

user@junosfwsrx>; show security flow status

Flow forwarding mode:

Inet forwarding mode: flow based

Inet6 forwarding mode: flow based

…. output omitted

{secondary:node1}

user@junosfwsrx>; request system reboot

Passo 3:

{primary:node0}

user@junosfwsrx>; request chassis cluster failover redundancy-group 0 node 1

—————————————————————————–

Initiated manual failover for redundancy group 0

{primary:node0}

zzmsb09@onafw01c2>; request chassis cluster failover redundancy-group 1 node 1

—————————————————————————–

Initiated manual failover for redundancy group 1

VERIFICA

Appena eseguito il failover:

user@junosfwsrx> show chassis cluster status

Cluster ID: 1

Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1

node0 200 secondary-hold no no None

node1 255 primary no no None

Redundancy group: 1 , Failover count: 3

node0 200 secondary no no None

node1 255 primary no no None

Dopo pochi minuti:

user@junosfwsrx>; show chassis cluster status

Cluster ID: 1

Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1

node0 200 secondary no no None

node1 255 primary no no None

Redundancy group: 1 , Failover count: 3

node0 200 secondary no no None

node1 255 primary no no None

Passi 4 e 5:

{secondary:node0}

user@junosfwsrx>edit

{secondary:node0}

user@junosfwsrx# set security forwarding-option family inet6 mode flow-based

{secondary:node0}

user@junosfwsrx# commit and-quit

{secondary:node0}

user@junosfwsrx>

VERIFICA

{secondary:node0}

user@junosfwsrx>; show configuration security forwarding-option

family {

inet6 {

mode flow-based;

}

{secondary:node0}

user@junosfwsrx>; show security flow status

Flow forwarding mode:

Inet forwarding mode: flow based

Inet6 forwarding mode: flow based

…. output omitted

{secondary:node1}

user@junosfwsrx>; request system reboot

Passo 6:

{secondary:node0}

user@junosfwsrx> request chassis cluster failover reset redundancy-group 0

—————————————————————————–

No reset required for redundancy group 0

node1:

—————————————————————————–

Successfully reset manual failover for redundancy group 0

{secondary:node0}

user@junosfwsrx>; request chassis cluster failover reset redundancy-group 1

—————————————————————————–

No reset required for redundancy group 1

node1:

—————————————————————————–

Successfully reset manual failover for redundancy group 0

Successivamente:

{secondary:node0}

user@junosfwsrx>; request chassis cluster failover redundancy-group 0 node 0

—————————————————————————–

Node0:

—————————————————————————–

Initiated manual failover for redundancy group 0

{secondary:node0}

user@junosfwsrx>; request chassis cluster failover reset redundancy-group 1

—————————————————————————–

Node0:

—————————————————————————–

Initiated manual failover for redundancy group 0

VERIFICA:

{primary:node0}

user@junosfwsrx>; show chassis cluster status

Cluster ID: 1

Node Priority Status Preempt Manual Monitor-failures

Redundancy group: 0 , Failover count: 1

node0 255 primary no no None

node1 100 secondary no no None

Redundancy group: 1 , Failover count: 3

node0 255 primary no no None

node1 100 secondary no no None

STEP-5: configurazione IPv6 interface

user@junosfwsrx>;

set interfaces reth2 unit 100 family inet6 address <ipv6_address>

set interfaces reth2 unit 50 family inet6 address <ipv6_address>

set interfaces reth1 unit 3109 family inet6 address <ipv6_address>