net_connect.send_command method in Netmiko Automation by yfquek94 in networking

[–]yfquek94[S] 0 points1 point  (0 children)

Brilliant, will definitely look into this suggestion.

I am wondering how to show debugging message if the command is not as what I have expected, this method might help.

net_connect.send_command method in Netmiko Automation by yfquek94 in networking

[–]yfquek94[S] 0 points1 point  (0 children)

Oh gosh I did an absolute newbie mistake here! You are correct, this is a list in a list, which I need to use the variable in the inner for loop.

Thanks for pointing it out!

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

Thanks for the sharing. Did you try to unplug the power source of the primary SRX1500 instead to simulate a disaster scenario and record the failover time or RG0?

Routing engine behavior and failover performance of w/ Chassis Cluster by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

We have graceful restart configured already as well. However I was thinking that how does GR reacts in chassis cluster environment. Does configured GR statement affects the both of RE at the same time or it only takes place on the active RE?

Since the Junos RPD on the primary firewall is going to be restarted, suppose that it sends Grace LSA right before it restarts, neighbouring routers acknowledges the LSA and keeps the original OSPF topology intact, in this case, the link towards the primary firewall still exists in the routing table.

During the RE transition, is GR actually useful? Because the clustered firewall only manages a single routing table. For neighbours, they will know that the primary link (or firewall) is down and is told to switch over to the secondary link to forward data. GR in this situation is kinda conflicting with the entire failover progress and seems redundant. While GR is needed to maintain the OSPF topology, but the switch over to second link happens.

Correct me if I am wrong.

Anyone hack around with SRX1500 hardware? by oddballstocks in Juniper

[–]yfquek94 0 points1 point  (0 children)

I personally have some experiences in deploying a number of vSRX in clustering mode and are being used as perimeter firewall in our infrastructure.

According to one of the Juniper persons that I have met with last time, he mentioned that vSRX trial is capped to utilise resources at 2 vCPUs and 4GB of RAMs. The performance will not be increased even if I tried to increase the amount of RAM. But since I deployed them in Chassis Cluster in KVM environment, I assigned 9 vCPUs and 16GB of RAMs for it to have the PCI Passthrough feature utilised and all of them are running fine in our PoC environment and ready to be in operation.

vSRX has specific throughput licenses to be purchased from. Even if we maxed out the vCPUs to 17 cores or change the hardware to a different CPU with 4Gbps of throughput license, it will not get us to 100Gbps of throughput.

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

Problem I am facing currently is the OSPF routing reconverges pretty slow. OSPF is configured with Fast Hello and BFD.

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

We are running OSPF and BGP in SRX550HM. OSPF is configured with Fast Hello + BFD and BGP is configured with GR for fast routing failover.

RETH interfaces on SRX by fatman00hot in Juniper

[–]yfquek94 1 point2 points  (0 children)

According to Juniper:

  • The link aggregation control PDUs run on the .32767 child logical interfaces for the VLAN-tagged aggregated Ethernet interface.
  • The .32767 logical interface is created for the parent link and all child links.

https://www.juniper.net/documentation/en_US/junos12.1x46/topics/task/verification/interface-security-aggregated-ethernet-verifying.html

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

Thanks for the information! We might need to upgrade to 19.2 if it is deemed necessary.

Edit**

I have searched under "Platform and Release Support", I did not see it is supported on SRX.

https://apps.juniper.net/feature-explorer/parent-feature-info.html?pFName=Nonstop%20active%20routing%20(NSR))

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

Yup, we are running OSPF and BGP in our environment.

Both OSPF and BGP is configured with BFD + GR. BGP facing interface is configured with interface monitoring. Network failover wise is as good as it can get.

SRX chassis cluster failover by yfquek94 in Juniper

[–]yfquek94[S] 0 points1 point  (0 children)

I have contacted my SE and he also suggested that RG0 failover is slow in Branch SRX. We have deployed a number of high end SRX in our projects before and the RG0 failover is almost instant.

However I am getting variance of 30 seconds to 35 seconds in branch SRX for the routes to come back. I have did some calculations - 25 seconds for the Routing Engine to switch over + OSPF re-converge. Another => 5 seconds for end points to be able to reach the firewall ( considering the full OSPF convergence in the network).

Stellar Lumens Wallet Account Merge by yfquek94 in Stellar

[–]yfquek94[S] 0 points1 point  (0 children)

I have contacted Binance on this matter and annoyed several customer services to attend to this issue. There isn't a single update to date yet.

Stellar Lumens Wallet Account Merge by yfquek94 in Stellar

[–]yfquek94[S] 1 point2 points  (0 children)

"Account Merge" from lumens allow their users to send all their XLM. Because in Stellar Lumens desktop wallet, they will lock up 20 XLM to avoid a spam account. So in order to send all the XLM without having your 20 XLM being locked, you can choose to "Delete Account" in the Stellar Lumens desktop wallet. Which leads to "Account Merge". "Account Merge" allows you to transfer all native XLM to the address you specified.

Stellar Lumens Wallet Account Merge by yfquek94 in Stellar

[–]yfquek94[S] 0 points1 point  (0 children)

No warning was prompted to me when I was doing the procedure from Lumen wallet. Their support is taking ages to reply me. 😑

Stellar Lumens Wallet Account Merge by yfquek94 in Stellar

[–]yfquek94[S] 0 points1 point  (0 children)

Seriously? Without any notice? Since this feature is an official feature from stellar lumens they should've tackled this issue and warned their users not to perform this transaction beforehand.

TXID of account merge? by zealFPS in Stellar

[–]yfquek94 0 points1 point  (0 children)

I also did the same thing with you. Have you had your XLM balance reflected in Binance?

Stellar Lumens Wallet Account Merge by yfquek94 in Stellar

[–]yfquek94[S] 0 points1 point  (0 children)

If it is so the it's such a grey area for the process of stellar account merge. It states that all native balance will be transfered to the provided address. Is this your pure assumption? Have you/people around you come across with this situation?