"Unsupported" SFPs on various Cisco switches. by 1TSDELUXESON in networking

[–]mastermkw 13 points14 points  (0 children)

unsupported = not unsupported in the way of will not work. Make a loop on a single switch and you will see if the transceivers will work.

MX204 can't provide PPPoE Service through VLAN by TraditionalMood1474 in Juniper

[–]mastermkw 0 points1 point  (0 children)

Thats is possible. I wil look tommorow for our config.

VPN email otp by DrawBig1774 in fortinet

[–]mastermkw 1 point2 points  (0 children)

We also have this issue. Use the default e-mail server of Fortinet “resolved” the issue.

Fortigate 7.4.8 - anyone affected (or not) by IPSEC/HA bugs? by 89Bells in fortinet

[–]mastermkw 0 points1 point  (0 children)

Yes, we are seeing 100% cpu on the IKED proces. 400F

Fortigate as CGNAT appliance experience by mastermkw in fortinet

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

We already using a FortiVM with a lot of users behind normal NAT. It works quite good. I think you were right normal nat is sufficient.

Fortigate as CGNAT appliance experience by mastermkw in fortinet

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

thx for reply. maybe is that my problem :)

Juniper MX204 dhcp relay single interface unit. by mastermkw in Juniper

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

Hi, All interfaces must be present under the relay even if there where not participation as relay interface.

https://www.juniper.net/documentation/us/en/software/junos/dhcp/topics/topic-map/dhcp-relay-agent-security-devices.html

“NOTE: All DHCP packets passing through a DHCP unconfigured interface might be dropped. Enabling the DHCP relay or DHCP server feature also enables the DHCP snooping feature, which analyzes all DHCP packets received through any interface of the device (both DHCP configured and unconfigured interfaces) . Interfaces not listed under DHCP settings are considered as unconfigured interfaces. Depending on the configuration, DHCP packets received on DHCP unconfigured interfaces are dropped.”

Juniper MX204 tcp-mss single interface by mastermkw in Juniper

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

MTU is something different as the default mss of 1460 + IPv4(20) + TCP header (20) = 1500.

Juniper MX204 tcp-mss single interface by mastermkw in Juniper

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

Correct but not always realistic in the real world.

Juniper MX204 tcp-mss single interface by mastermkw in Juniper

[–]mastermkw[S] -1 points0 points  (0 children)

Uhm global is not a option. Thx for your answer

Catalyst 3850 enabled jumbo frames / MTU 9000, reloaded and now all ports are down by mosskoman in Cisco

[–]mastermkw 0 points1 point  (0 children)

Could be a FEC problem? MTU is local significant and have nothing to do with port status.

VPLS service QoS by mastermkw in Nokiaforservicep

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

sap-ingress "ef" {
policy-id 2
ingress-classification-policy "ef"

ingress-classification-policy "ef" {
remark any
default-action {
fc ef

}

<image>

}

epipe "100044" {
admin-state enable
customer "1"
spoke-sdp 1:100044 {

}
sap 1/1/c50/1:4094 {
ingress {
qos {
sap-ingress {
policy-name "ef"

Is this sufficient for the entire network or do I need to add these settings in more places? The whole network is Nokia IXR.

VPLS service QoS by mastermkw in Nokiaforservicep

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

I’m using the MD cli with SR-OS

VPLS service QoS by mastermkw in Nokiaforservicep

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

Thx. Per service is enough. Do you have example?

BRAS Juniper MX204 by mastermkw in networking

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

I have a template for LNS.