Re: [j-nsp] Juniper support offline?
I just messaged some local at Juniper NZ and they advised that +80025864737 is working for support. Seems to work from my 2D mobile here too. Cheers Liam On Sun, 26 Jan 2020 at 8:16 PM, Nathan Ward wrote: > Hi, > > Looks to me and colleagues of mine like Juniper support is offline. > > Last night, I was able to log in but trying to download an image got to > some stage of the redirect process and hung, then a please try again later > message. It persisted for the next few hours of me trying every now and > then. > > Today, I can’t log in at all - Invalid user/password. > Password reset process works, but, still doesn’t let me in. Different > browsers, cleared cache, all the usual “is it on at the wall sir” debugging. > > Hearing the same story for others. > > I’ve called both the NZ 00800 (international 800) and the US +1888 number. > The former says “call cannot be completed”. The US number says “high volume > of calls please leave a message”. > > We’re in New Zealand - unsure if that’s relevant. > > > Are others having these same issues? > > Any insight in to what’s going on? > It’s a long weekend here, so the local sales/SE/etc. folks I usually deal > with are likely not anywhere near their phones. > > -- > Nathan Ward > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Kind Regards Liam Farr Maxum Data +64-9-950-5302 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Juniper support offline?
Hi, Looks to me and colleagues of mine like Juniper support is offline. Last night, I was able to log in but trying to download an image got to some stage of the redirect process and hung, then a please try again later message. It persisted for the next few hours of me trying every now and then. Today, I can’t log in at all - Invalid user/password. Password reset process works, but, still doesn’t let me in. Different browsers, cleared cache, all the usual “is it on at the wall sir” debugging. Hearing the same story for others. I’ve called both the NZ 00800 (international 800) and the US +1888 number. The former says “call cannot be completed”. The US number says “high volume of calls please leave a message”. We’re in New Zealand - unsure if that’s relevant. Are others having these same issues? Any insight in to what’s going on? It’s a long weekend here, so the local sales/SE/etc. folks I usually deal with are likely not anywhere near their phones. -- Nathan Ward ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] ACX5448 & ACX710
On 24/Jan/20 19:24, Colton Conor wrote: > Mark, > > So which box is best to just get customers a simple IP, but has all > the management and metro-e requirements you need? Well, anything sold for a Metro-E application nowadays, whether it supports MPLS or not, will always have some kind of OAM capability. This is just vendors building what the industry asked for years ago, and thinks the industry still needs today. For us, 98% of the customers on our Metro-E network are simple IP customers, i.e., DIA or IP Transit. They don't care about OAM. They just want a connection they can use to access their cloud services. Of the remaining 2% who buy only EoMPLS services, 0.5% of those ask about OAM. To put it another way - if vendors could build boxes and price them cheaper because they had little or no OAM features (either by design or via licenses), I'd buy them in an African minute. Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] arp from correct IP address
Hello I have a problem where some customer routers refuse to reply to arp from our juniper mx204. The arp will look like this: 11:57:46.934484 Out arp who-has 185.24.169.60 tell 185.24.168.248 The problem is that this should have been "tell 185.24.169.1" because the client is in the 185.24.169.0/24 subnet. The interface is "unnumbered-address lo0.1" with lo0.1 having both 185.24.168.248 and 185.24.169.1 among many others. A Linux box would select the nearest address but apparently junos does not know how to do this. Tried adding in "preferred-source-address $junos-preferred-source-address" but this just results in "preferred-source-address NONE" and does nothing. Also there is zero documentation on how junos will fill in that variable. Is there a solution to this? Is there a radius variable I can set with the preferred source address? Regards, Baldur ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
