I am running into another problem with the .map files truncating the output. In this instance, the interfaces are getting cut from the searches:
Search results
Days MAC IP DNS Name
Switch Name Port VLAN Inactive Speed Duplex Port Label Address Address (if known)
Plano-NDC-7613 Gi10/1 10 13 auto auto * Agilent *
Plano-NDC-7613 Gi10/2 22 1G full Blade6 Agilent 0015c5f78b39
Plano-NDC-7613 Gi10/4 10 1G full * AgilentMUS Service 00151720aee0 x.x.x.x
Plano-NDC-7613 Gi11/1
If I have a port that is Gig and in slot 10 or higher, and port 10 or higher the seacrch gets skewed. Is there a way to make each of these fields longer? The issue also crops up with DNS names that are over a certain number of characters.
You had mentioned that searching the HTML files may resolve this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does it look right on the HTML page? If so then the .map files can be made to show the correct info as well. If the HTML do now show the correc info then we have a little work to do....when ever the time permits.
-Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you show me an example of one that is broken. The only thing that looks wrong here is the Port Label is getting truncated because it is longer than 20 characters.
Please show me a valid HTML, .map, and search result example. That will help me identify what you want.
-Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I don't believe that it is broken. It is only truncated. I am trying to get the search results (and the description, DNS name) for IP PLAN, etc. to be complete instead of truncated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You should be able to add more "<" symbols to the fields you need and the map file should then contain more characters to that field. If that doesn't work then there might be more work. My descriptions are very short so I don't run into that issue.
-Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Careful. You can add "<" to get the .text files to have wider fields, but the headers in the text files
won't be correct. More important, it will break the FindOffice.pl script (the "search the portlist web
pages" feature). FindOffice.pl hard-codes the offsets of the columns in the .text files.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Correct. I think you saw one of the earlier conversations between nolajc2000 and I regarding this type of thing. I told him how to adjust FindOffice.pl
None the less caution needs to be done.
Maybe there is a way we can put this in a variable and call it from Constants.pm or something and that way we won't be changing things in multiple places. Who knows.
-Lance
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running into another problem with the .map files truncating the output. In this instance, the interfaces are getting cut from the searches:
Search results
Switch Name Port VLAN Inactive Speed Duplex Port Label Address Address (if known)
Plano-NDC-7613 Gi10/1 10 13 auto auto * Agilent *
Plano-NDC-7613 Gi10/2 22 1G full Blade6 Agilent 0015c5f78b39
Plano-NDC-7613 Gi10/4 10 1G full * AgilentMUS Service 00151720aee0 x.x.x.x
Plano-NDC-7613 Gi11/1
If I have a port that is Gig and in slot 10 or higher, and port 10 or higher the seacrch gets skewed. Is there a way to make each of these fields longer? The issue also crops up with DNS names that are over a certain number of characters.
You had mentioned that searching the HTML files may resolve this.
Does it look right on the HTML page? If so then the .map files can be made to show the correct info as well. If the HTML do now show the correc info then we have a little work to do....when ever the time permits.
-Lance
Yes, it is correct in the HTML which is the odd thing. I just couldn't find the delimiter.
[jcash@vsrvr-ipplan01 text]$ more Plano-7613A.map
Gi1/8 10 100M full *Juniper EVDO "A" OA 0080421831eb 10.222.9.53 juniper-m40e-re0
Actual HTML:
Gi1/8 10 Active 100M full Juniper EVDO "A" OA&M 0080421831eb Force Computers 10.222.9.53 juniper-m40e-re0
Can you show me an example of one that is broken. The only thing that looks wrong here is the Port Label is getting truncated because it is longer than 20 characters.
Please show me a valid HTML, .map, and search result example. That will help me identify what you want.
-Lance
Well, I don't believe that it is broken. It is only truncated. I am trying to get the search results (and the description, DNS name) for IP PLAN, etc. to be complete instead of truncated.
Ok, You can most likely do this fairly easy.
File "WriteTextDirectory.pm"
Line 102
You should be able to add more "<" symbols to the fields you need and the map file should then contain more characters to that field. If that doesn't work then there might be more work. My descriptions are very short so I don't run into that issue.
-Lance
Careful. You can add "<" to get the .text files to have wider fields, but the headers in the text files
won't be correct. More important, it will break the FindOffice.pl script (the "search the portlist web
pages" feature). FindOffice.pl hard-codes the offsets of the columns in the .text files.
Pete,
Correct. I think you saw one of the earlier conversations between nolajc2000 and I regarding this type of thing. I told him how to adjust FindOffice.pl
None the less caution needs to be done.
Maybe there is a way we can put this in a variable and call it from Constants.pm or something and that way we won't be changing things in multiple places. Who knows.
-Lance