Talk:Part Numbers

From Juniper Clue

Jump to: navigation, search

Contents

Multiple Part IDs

If we have multiple part numbers for the same part should we be entering it as:

CHAS-BP-M40e       710-005071
CHAS-BP-M40e       710-008502

or

CHAS-BP-M40e       710-005071 710-008502

Clinton 10:21, 16 September 2005 (CDT)


Question marks

Why are question marks being put behind some of the part numbers? Hopefully people are only adding part numbers that they have confirmed.

PB-1GE-LH          750-003629?

Clinton 10:21, 16 September 2005 (CDT)


Formatting

Should we use tables instead of literal text formatting?

Instead of:

CHAS-BP-M40e       710-005071
CHAS-BP-M40e       710-008502

Use:

CHAS-BP-M40e 710-005071
CHAS-BP-M40e 710-008502

Clinton 10:21, 16 September 2005 (CDT)

How to collect and enter data

The problem with using the output of "show chassis hardware" to obtain the part number is that it doesn't directly map to a part name. I've caught several instances where people entered the record for a P-whatever because they had it installed in an M20, but it turns out that the PIC is a PE- and is inserted into the wrong chassis. There are also a few other issues with the description, for example the part numbers for the 4-port OC3 card and the 4-port STM1 card are the same, but the description changes depending on how the card is configured.

As for the question marks, I've been trying to put those in when we aren't 100% certain about the data. So far I haven't actually seen a confirmed and undisputed case where 2 pieces of hardware are sold as exactly the same (not a -E, -B, etc) but have two different part numbers. I'm not sure if they actually exist or not, but until I see that they do I am inclined to be suspect of anyone who has entered two different numbers for the same PIC.

Ultimately I would like to put this all directly into a database, but I'm waiting to see if we can determine if we're dealing with a one-to-one or one-to-many relationship before doing so. Maybe a better solution would be to make a webpage where users just paste the entire contents of their show chassis hardware and we parse it out either manually or through a script, using the number of occurances of a particular part number to try and look for flukes? It might cut down on the number of errors we're encountering. Unfortunately it doesn't seem like even Juniper people have a complete database of the part numbers available.

ras 02:56:56, 2005-09-22 (CDT)


Juniper has a spreadsheet of part numbers that I obtained from my CSE, but your right in that it seems outdated. It has all of the old PICs / FPCs, but is missing many of the newer parts. I can assure you that Juniper has more than one 710-NNNNNN part number for some cards. I have captured the "show chassis hardware" on a number of M40e routers and a simple grep shows multiple part numbers for the same FPC Type 2 card.

FPC 1            REV 03   710-003950   xxxxxx            E-FPC Type 2
FPC 4            REV 02   710-009007   xxxxxx            M40e-FPC Type 2
FPC 5            REV 02   710-009007   xxxxxx            M40e-FPC Type 2
FPC 6            REV 02   710-009007   xxxxxx            M40e-FPC Type 2
FPC 7            REV 02   710-009007   xxxxxx            M40e-FPC Type 2
FPC 1            REV 01   710-011163   xxxxxx            M40e-FPC Type 2
FPC 2            REV 01   710-011163   xxxxxx            M40e-FPC Type 2
FPC 4            REV 04   710-005197   xxxxxx            M40e-FPC Type 2
FPC 5            REV 01   710-011163   xxxxxx            M40e-FPC Type 2
FPC 6            REV 01   710-011163   xxxxxx            M40e-FPC Type 2
FPC 7            REV 01   710-011163   xxxxxx            M40e-FPC Type 2

I agree that I have never seen more than part number for a PIC. Only FPCs and other chassis parts seem to have multiple part numbers. I have written perl scripts to parse the show chassis hardware command, lookup the part numbers in a table to get the part, and then import the data into a database. Creating a site where people can submit show chassis hardware output and generate a part list would be great. I would like to see the part data in a database as well (better data integrity).

--Clinton 18:48, 22 September 2005 (CDT)

Personal tools