date:20171120

[swinog] Selling Cisco 7206 VXR NPEG1 - new price

2017-11-20 Diskussionsfäden Hofer Ruedi

Dear all

I am selling 3 x Cisco 7206 VXR / NPEG1 / dual power supply
They were bought in 2003 and used until recently. They are in good condition 
and clean.

See tech spec below for details.

Price: CHF33.30/piece (bid >0 welcome;)

-   No guarantee
  No Support
-   No Lasers
-   No Cables
-   No Shipping, pickup at our premises only, see address below
-   Cash-only payment

First come first served.

Please contact me offlist if interestet. mailto:ruedi.ho...@ewb.ch

Freundliche Grüsse

Ruedi Hofer
Leiter Telecom Center

Energie Wasser Bern
Monbijoustrasse 11, Postfach, 3001 Bern
ruedi.ho...@ewb.ch, ewb.ch


Summary :
-   Cisco 7206VXR, 6-slot chassis
-   NPE-G1 / 512MB RAM / 64MB Flash Card
-   3x1GB Interface

Web Refrence : 
https://www.cisco.com/c/en/us/td/docs/routers/7200/install_and_upgrade/network_process_engine_install_config/npense/4448o5.html

### RAW DATA 
##
ewb-ch-emc-brn01-rm-01#sh inventory raw
NAME: "Chassis", DESCR: "Cisco 7206VXR, 6-slot chassis"
PID: CISCO7206VXR  , VID:, SN: 30827013

NAME: "I/O and CPU Slot 0", DESCR: "I/O and Processor Slot Container"
PID:   , VID:, SN:

NAME: "NPE-G1 0", DESCR: "Cisco 7200 Series Network Processing Engine NPE-G1"
PID: NPE-G1, VID:, SN: 31248843

NAME: "GBIC Port Container 0/1", DESCR: "GBIC Port Container"
PID:   , VID:, SN:

NAME: "GigabitEthernet0/1", DESCR: "BCM1250 Internal MAC"
PID:   , VID:, SN:

NAME: "GBIC Port Container 0/2", DESCR: "GBIC Port Container"
PID:   , VID:, SN:

NAME: "GigabitEthernet0/2", DESCR: "BCM1250 Internal MAC"
PID:   , VID:, SN:

NAME: "GBIC Port Container 0/3", DESCR: "GBIC Port Container"
PID:   , VID:, SN:

NAME: "GigabitEthernet0/3", DESCR: "BCM1250 Internal MAC"
PID:   , VID:, SN:

NAME: "Flash Card Slot Container CPU", DESCR: "Flash Card Slot Container CPU"
PID:   , VID:, SN:

NAME: "disk2", DESCR: "64MB Compact Flash Disk for NPE-G1"
PID: MEM-NPE-G1-FLD64  , VID:, SN:

NAME: "NPE Inlet Temperature 0", DESCR: "NPE Inlet Temperature Sensor"
PID:   , VID:, SN:

NAME: "NPE Outlet Temperature 0", DESCR: "NPE Outlet Temperature Sensor"
PID:   , VID:, SN:

NAME: "+3.45 V Voltage 0", DESCR: "+3.45 V  Voltage Sensor"
PID:   , VID:, SN:

NAME: "+5.15 V Voltage 0", DESCR: "+5.15 V  Voltage Sensor"
PID:   , VID:, SN:

NAME: "+12.15 V Voltage 0", DESCR: "+12.15 V  Voltage Sensor"
PID:   , VID:, SN:

NAME: "-11.95 V Voltage 0", DESCR: "-11.95 V  Voltage Sensor"
PID:   , VID:, SN:

NAME: "Gi0/1", DESCR: "BCM1250 Internal MAC RJ45"
PID:   , VID:, SN:

NAME: "Gi0/2", DESCR: "BCM1250 Internal MAC RJ45"
PID:   , VID:, SN:

NAME: "Gi0/3", DESCR: "BCM1250 Internal MAC RJ45"
PID:   , VID:, SN:

NAME: "PA Slot 1", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PA Slot 2", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PA Slot 3", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PA Slot 4", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PA Slot 5", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PA Slot 6", DESCR: "PA Slot Container"
PID:   , VID:, SN:

NAME: "PEM 0", DESCR: "Power Supply Container"
PID:   , VID:, SN:

NAME: "Power Supply 0", DESCR: "Cisco 7200 AC Power Supply"
PID: PWR-7200-AC   , VID:, SN:

NAME: "PEM 1", DESCR: "Power Supply Container"
PID:   , VID:, SN:

NAME: "Power Supply 1", DESCR: "Cisco 7200 AC Power Supply"
PID: PWR-7200-AC   , VID:, SN:


ewb-ch-emc-brn01-rm-01#sh ver
ewb-ch-emc-brn01-rm-01#sh version
Cisco IOS Software, 7200 Software (C7200-JK9O3S-M), Version 12.4(8c), RELEASE 
SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2006 by Cisco Systems, Inc.
Compiled Tue 12-Dec-06 03:30 by prod_rel_team

ROM: System Bootstrap, Version 12.2(8r)B, RELEASE SOFTWARE (fc1)
BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.2(15)B, EARLY DEPLOYMENT 
RELEASE SOFTWARE (fc1)

System image file is "disk2:c7200-jk9o3s-mz.124-8c.bin"
Last reload reason: Reload Command

This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this

Re: [swinog] RIPE database and more specific routes

2017-11-20 Diskussionsfäden Bernd Spiess

Hi Vincent,

I´d suggest to create each route object for each announced prefix...
If you did it right, you should see irrexplorer for your ASN in green only:
http://irrexplorer.nlnog.net/search/61098 (looks excellent)
IMHO you are very right - there are for sure networks out there, which will 
filter 
your prefixes, when you do not have a matching route object entry ...

Bernd

-Original Message-
From: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] On 
Behalf Of Vincent Bernat
Sent: Montag, 20. November 2017 11:03
To: swi...@swinog.ch
Subject: [swinog] RIPE database and more specific routes

Hey!

I am updating the route/inetnum objects in the RIPE database and I am wondering 
if I have to create more specific route objects. For example, I have the 
following routes announced:

 - 89.145.160.0/21
 - 89.145.160.0/22 (FR7)
 - 89.145.164.0/23 (DK2)
 - 89.145.166.0/23 (GV2)

Each more specific route is announced in a different location. Should I create 
only the top route object or should I create a route object for each announce?

If I look at bgpq3, I see by default, it uses exact matches:

$ bgpq3 -4 -J -E AS61098 | grep 89.145
route-filter 89.145.160.0/21 exact;
route-filter 89.145.160.0/22 exact;
route-filter 89.145.164.0/23 exact;
route-filter 89.145.166.0/23 exact;

However, I use it this way:

$ bgpq3 -R 24 -4 -J -E AS61098 | grep 89.145
route-filter 89.145.160.0/21 upto /24;

But I am concerned some people may build filters using only exact matches, so 
it seems safer to have route objects for more specifics.
--
If more of us valued food and cheer and song above hoarded gold, it would be a 
merrier world.
-- J.R.R. Tolkien


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

Re: [swinog] RIPE database and more specific routes

2017-11-20 Diskussionsfäden Gert Doering

Hi,

On Mon, Nov 20, 2017 at 11:03:18AM +0100, Vincent Bernat wrote:
> But I am concerned some people may build filters using only exact
> matches, so it seems safer to have route objects for more specifics.

Generally speaking, you should have route objects for what you intend
to announce.

*Some* upstreams might be libral and accept everything up to a /24 from
the blocks you define, but others are very strict.

Gert Doering
-- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AGVorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14  Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444   USt-IdNr.: DE813185279


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

[swinog] RIPE database and more specific routes

2017-11-20 Diskussionsfäden Vincent Bernat

Hey!

I am updating the route/inetnum objects in the RIPE database and I am
wondering if I have to create more specific route objects. For example,
I have the following routes announced:

 - 89.145.160.0/21
 - 89.145.160.0/22 (FR7)
 - 89.145.164.0/23 (DK2)
 - 89.145.166.0/23 (GV2)

Each more specific route is announced in a different location. Should I
create only the top route object or should I create a route object for
each announce?

If I look at bgpq3, I see by default, it uses exact matches:

$ bgpq3 -4 -J -E AS61098 | grep 89.145
route-filter 89.145.160.0/21 exact;
route-filter 89.145.160.0/22 exact;
route-filter 89.145.164.0/23 exact;
route-filter 89.145.166.0/23 exact;

However, I use it this way:

$ bgpq3 -R 24 -4 -J -E AS61098 | grep 89.145
route-filter 89.145.160.0/21 upto /24;

But I am concerned some people may build filters using only exact
matches, so it seems safer to have route objects for more specifics.
-- 
If more of us valued food and cheer and song above hoarded gold, it would
be a merrier world.
-- J.R.R. Tolkien


___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog

[swinog] Selling Cisco 7206 VXR NPEG1 - new price

Re: [swinog] RIPE database and more specific routes

Re: [swinog] RIPE database and more specific routes

[swinog] RIPE database and more specific routes

4 matches

Site Navigation

Mail list logo

Footer information