Send redback-nsp mailing list submissions to
redback-nsp@puck.nether.net
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/redback-nsp
or, via email, send a message with subject or body 'help' to
redback-nsp-requ...@puck.nether.net
You can reach the person managing the list at
redback-nsp-ow...@puck.nether.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of redback-nsp digest..."
Today's Topics:
1. Re: se800 ge-4-port card not working (Marcin Kuczera)
2. L2TP - Multiple Remote IPs, One Remote Name (Blake Willis)
----------------------------------------------------------------------
Message: 1
Date: Thu, 22 Sep 2016 11:28:14 +0200
From: Marcin Kuczera <mar...@leon.pl>
To: redback-nsp@puck.nether.net
Subject: Re: [rbak-nsp] se800 ge-4-port card not working
Message-ID: <57e3a42e.1000...@leon.pl>
Content-Type: text/plain; charset="utf-8"
On 2016-09-22 09:57, Eng.Nawras Chahbandar wrote:
>
> Hi There,
>
>
>
> I have a similar problem at se800 for ge-4-port card. Card isn?t
> working. I saw the log ?Chass Entitlement : SE400 (0x4)? what does mean?
>
>
>
> I know se400 and se800 same chassies. But the card not working. I can
> try to ?reload fpga 5? see the log ?FPGA programming verification
> failure? What does mean?
>
>
>
> What can I do?
>
show diag pod card 5 detail
or sth like that.
Marcin
>
>
> PS: I haven?t got a services contract at the ericsson.
>
>
>
> [local]Redback#sh hardware card 5 detail
>
>
>
> Slot : 5 Type : ge-4-port
>
> Serial No : 8K50xxxxxxxxxx Hardware Rev : 50
>
> EEPROM id/ver : 0x5a/4 Mfg Date : 13-APR-2005
>
> SysFpga rev : 0x0 SysFpga file rev : N/A
>
> LimFpga rev : 0x0 LimFpga file rev : N/A
>
> FlipFpga rev : 0x0 FlipFpga file rev : N/A
>
> IPPA memory : N/A EPPA memory : N/A
>
> Voltage : N/A Temperature : N/A
>
> Card Status : HW failure POD Status : Success
>
> Card State : FPGA programming verification failure
>
> ODD Status : Not Available
>
> Fail LED : Invalid Active LED : Invalid
>
> Standby LED : Invalid
>
> Chass Entitlement : SE400 (0x4)
>
> Ports Entitled : 1, 3
>
> Active Alarms : N/A
>
>
>
> [local]Redback#
>
>
>
> Other logs are below.
>
>
>
> [local]Redback#sh ver
>
>
>
> Redback Networks SmartEdge OS Version SEOS-6.1.5.7-Release
>
> Built by sysbuild@SWB-node13 Fri Nov 19 10:30:08 PST 2010
>
> Copyright (C) 1998-2010, Redback Networks Inc. All rights reserved.
>
> System Bootstrap version is PowerPC,1.0b1272
>
> Installed minikernel version is 23
>
> Router Up Time - 4 days, 10 hours 43 minutes 31 secs
>
> [local]Redback#
>
>
>
> [local]Redback#sh hardware card 5
>
>
>
> Slot Type Serial No Rev Ver Mfg Date Voltage
> Temp
>
> ---- -------------------- -------------- ---- --- ----------- --------
> -------
>
> 5 ge-4-port 8K50xxxxxxxxxx 50 4 13-APR-2005
> N/A N/A
>
>
>
> [local]Redback#sh hardware card 5 detail
>
>
>
> Slot : 5 Type : ge-4-port
>
> Serial No : 8K50xxxxxxxxxx Hardware Rev : 50
>
> EEPROM id/ver : 0x5a/4 Mfg Date : 13-APR-2005
>
> SysFpga rev : 0x0 SysFpga file rev : N/A
>
> LimFpga rev : 0x0 LimFpga file rev : N/A
>
> FlipFpga rev : 0x0 FlipFpga file rev : N/A
>
> IPPA memory : N/A EPPA memory : N/A
>
> Voltage : N/A Temperature : N/A
>
> Card Status : HW detected POD Status : Success
>
> ODD Status : Not Available
>
> Fail LED : Invalid Active LED : Invalid
>
> Standby LED : Invalid
>
> Chass Entitlement : SE400 (0x4)
>
> Ports Entitled : 1, 3
>
> Active Alarms : N/A
>
>
>
> [local]Redback#
>
>
>
> [local]Redback#sh hardware card 4
>
>
>
> Slot Type Serial No Rev Ver Mfg Date Voltage
> Temp
>
> ---- -------------------- -------------- ---- --- ----------- --------
> -------
>
> 4 ge-4-port 8K03xxxxxxxxxxx 03 4 06-MAY-2003
> OK NORMAL
>
>
>
> [local]Redback#sh hardware card 4 detail
>
>
>
> Slot : 4 Type : ge-4-port
>
> Serial No : 8K03xxxxxxxxxxx Hardware Rev : 03
>
> EEPROM id/ver : 0x5a/4 Mfg Date : 06-MAY-2003
>
> SysFpga rev : 0x7 SysFpga file rev : N/A
>
> LimFpga rev : 0x5 LimFpga file rev : 0x5
>
> FlipFpga rev : 0xc FlipFpga file rev : 0xc
>
> IPPA memory : 256 MB EPPA memory : 256 MB
>
> Voltage 1.500V : 1.514 (+1%) Voltage 1.800V : 1.770 (-2%)
>
> Voltage 2.625V : 2.627 (+0%) Voltage 3.400V : 3.394 (-0%)
>
> Temperature : NORMAL (41 C)
>
> Card Status : HW initialized POD Status : Success
>
> ODD Status : Not Available
>
> Fail LED : Off Active LED : On
>
> Standby LED : Invalid
>
> Chass Entitlement : All (0x0)
>
> Ports Entitled : All
>
> Active Alarms : NONE
>
>
>
> [local]Redback#
>
>
> Best regards
>
> Eng. Nawras Chahbandar
>
>
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
--
Marcin Kuczera / Wiceprezes Zarz?du / CTO
+48 32 440 80 71/ marcin.kucz...@leon.pl <mailto:marcin.kucz...@leon.pl>
Leon Sp. z o.o.
ul. Kili?skiego 33d, 44-200 Rybnik
http://www.leon.pl/
INTERNET | TELEWIZJA | TELEFON
KRS 0000223101 S?d Rejonowy w Gliwicach
Kapita? zak?adowy 282.500 z?
NIP: 6332068698
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/redback-nsp/attachments/20160922/9a6a70c4/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 22 Sep 2016 11:32:36 +0200
From: Blake Willis <bl...@ibrowse.com>
To: redback-nsp@puck.nether.net
Subject: [rbak-nsp] L2TP - Multiple Remote IPs, One Remote Name
Message-ID: <5b5019889bf6efb8981d01483f042...@ibrowse.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
On 22.09.2016 08:26, redback-nsp-requ...@puck.nether.net wrote:
>
> I need to terminate L2TP sessions from multiple remote LACs, each of
> which
> uses the same hostname in its L2TP tunnel setup. Unfortunately these
> belong
> to a third-party, so I can't do anything about the hostnames.
>
> According to the docs the 'name' parameter to l2tp-peer must be unique
> so
> it sounds like I can't do what I need with the SE but I was hoping one
> of
> you had come across this scenario and had found a solution.
Hi Dermot,
Just as Sam said, for every l2tp peer where we can't control the name
&/or they have more than a couple LACs, we dedicate a context &
configure an unnamed peer for them (you can only have 1 per context...).
Something to watch out for when doing this: to my recollection, SEOS
(at least the 6.1 that we [still] use) can't handle encapsulating L2TP
and MPLS on the same packet, so e.g. you need to design your L2TP
contexts so that the tunnels don't come in over L3VPN. (perhaps someone
has experience to the contrary?)
HtH,
---
Blake Willis
Network Architect
iBrowse
------------------------------
Subject: Digest Footer
_______________________________________________
redback-nsp mailing list
redback-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp
------------------------------
End of redback-nsp Digest, Vol 103, Issue 5
*******************************************
