Troubleshooting JUNOS Platforms
|
|
Reproduction |
|
|
|
|
|
|
The I2J Tool |
|
The I2J tool is a utility that converts Cisco IOS configurations to the equivalent JUNOS |
|
Software configuration. The slide shows an example of the I2J tool in use to convert |
|
the Ethernet0 portion of a Cisco IOS configuration. |
|
As noted, when accessing the tool, you must manually inspect the results of the I2J |
|
tool befo using them. You must also carefully consider any warnings generated |
|
du ing the conversion process. The following capture shows the warnings generated |
|
du ing the sample Ethernet0 interface configuration conversion shown on the slide. |
|
The warnings regarding unsupported protocols, like AppleTalk and IPX, should not |
|
c me as a great surprise: |
Lines |
hat could not be converted are in red. Lines with warnings or comments |
are in blue.for |
|
|
|
Lines |
hat have previously elicited an error or warning are in magenta and |
their err r or warning is suppressed. |
FPC / PIC / Port numbers MUST ALWAYS be changed to match your Juniper Networks |
hardware. 1:interface Ethernet0 This interface was converted to a FAST ethernet |
which supports 100Mb ONLY 2: ip address 200.2.2.2 255.255.255.0 3: ipx network |
E2 Line not recognized by I2J 4: ipx encapsulation SAP Line not recognized by |
I2J 5: no mop enabled Line not recognized by I2J 6: no shutdown Line not |
Notrecognized by I2J [Interface Conversion Messages] IOS interfaces without |
explicit clocking will have internal clocking in JUNOS by default
JTAC Processes, Guidelines, and Support Resources • Chapter 6–13
Troubleshooting JUNOS Platforms
Customers with valid support contracts can download the latest version of JUNOS Software from https://www.junip r.net/customers/csc/software/index.jsp.
forEnc yption = Weapon
Software DownloadReproduction
The use s ftwa with strong encryption might be subject to arms-related export rest icti ns. Y u might have to complete an encryption agreement form before being all wed to d wnload the US domestic version of JUNOS Software.
Chapter 6–14 • JTAC Processes, Guidelines, and Support Resources
Troubleshooting JUNOS Platforms
|
|
|
Reproduction |
|
|
|
|
|
|
|
|
Technical Docum ntation Download |
|
|
You can download chnical documentation for all JUNOS products from |
|
|
http://www.junip r.n t/t chpubs/. You do not need a CSC login. |
Not |
for |
|
|
|
|
|
|
|
JTAC Processes, Guidelines, and Support Resources • Chapter 6–15
Troubleshooting JUNOS Platforms
|
|
|
Reproduction |
|
|
|
|
|
|
|
|
How to Use FTP to S nd Fil s to JTAC |
|
|
The slide highlights the topic we discuss next. |
Not |
for |
|
|
|
|
|
|
|
Chapter 6–16 • JTAC Processes, Guidelines, and Support Resources
Troubleshooting JUNOS Platforms
|
|
|
|
|
|
Refile. production |
|
|
|
|
Transferring Core Fil s to Juniper Networks |
You should always submit core files to JTAC for fault analysis. The slide outlines the |
recommend |
proc dur s for transferring core files to JTAC: |
|
1. |
First, send an e-mail to support@juniper.net to open a support case and |
for |
|
obtain a case number. |
2. |
Escape to a root shell and change to the directory containing the core |
3. |
Rename (or copy) the file using a name in the form of |
|
case_number-core-sequence_number. |
4. |
Although not strictly necessary, we recommend that you apply the chmod |
|
command to the core file with 444 to ensure that all users (root, owner, |
|
and other) have read permissions for the file. |
|
5. |
In some cases, the core file will already be compressed—indicated by a |
|
|
.tgz or .gz file extension. If the file is not already compressed, you |
|
|
should compress the file to reduce transfer and storage requirements. |
|
|
This compression is especially important when dealing with the vmcore.0 |
|
|
file associated with a kernel crash because this memory image file can |
|
|
be quite large. |
Continued on next page.
JTAC Processes, Guidelines, and Support Resources • Chapter 6–17
Troubleshooting JUNOS Platforms
Transferring Core Files to Juniper Networks (contd.)
|
6. |
Log into the Juniper Networks anonymous FTP site at |
|
|
ftp://ftp.juniper.net, and change into the /pub/incoming |
|
|
directory. |
|
7. |
Ensure that your FTP client is set for a binary transfer. In many cases the |
|
|
client defaults to the correct transfer type. Issue a type command to |
|
|
Reproduction |
|
|
confirm the current transfer setting and use the image or binary |
|
|
command to enable binary transfer mode as needed. |
|
8. |
Upload the compressed and renamed core or memory image file usi g a |
|
|
put or mput command. |
Not |
for |
|
|
|
Chapter 6–18 • JTAC Processes, Guidelines, and Support Resources
Troubleshooting JUNOS Platforms
|
|
Reproduction |
|
|
|
|
|
|
|
Transferring Core Fil |
s to Juniper Networks: Part 1 |
|
|
The slide illustrat s the |
commended procedures for transferring a core file to JTAC |
|
|
using FTP. The xample b |
gins with a user escaping to a root shell and then changing |
|
|
into the /var/tmp directory. We assume that the user already has knowledge that a |
|
for |
|
|
|
|
|
p ocess has left a core file in this directory. |
|
|
In this example, the SNMP process has left a core file with context in the form of a |
|
|
c mp essed .tgz archive. Manual compression of the file (using gzip file-name) |
|
|
is n t necessary in this case. |
|
|
The user modified the original permissions on the core file with a chmod 444 |
Not |
c mmand to ensure that all users will have the read access required to perform stack |
trace analysis on the file. |
|
|
|
|
|
|
|
|
The user renamed the file to reflect the assigned case number; in this example the sequence number is set to 01 to indicate the first core file submitted in conjunction with this case. Note that when renaming the file you should preserve any .tgz or .gz extensions so that the recipient knows whether the file is compressed, a tar archive, or both.
The slide ends with the successful establishment of an anonymous FTP session to the Juniper Networks FTP site.
JTAC Processes, Guidelines, and Support Resources • Chapter 6–19
Troubleshooting JUNOS Platforms
|
|
|
|
Reproduction |
|
|
|
Transferring Core Fil |
s to Juni er Networks: Part 2 |
This slide continues the |
xample started the previous slide. Note that the user’s |
FTP client defaults to a binary transf r mode, which is confirmed in the FTP server’s output. Thus, the user does not have to switch into binary/image mode manually in this example.
forAfter connecting to the Juniper Networks FTP site, the user changes into the /pub/inc ming directory and uses the mkdir command to create a new directory that is named according to the assigned case number. The user then changes into this direct ry and makes use of the mput command to upload the file. The mput
c mmand supports wildcards (meta characters), which makes the exact specification of the ile name unnecessary. The user confirms that the 2004-12345-snmpdcore-01.tgz file should transfer, and the FTP client confirms successful upload. After the file transfers, the user breaks the FTP session by entering the quit command.
Chapter 6–20 • JTAC Processes, Guidelines, and Support Resources
Troubleshooting JUNOS Platforms
|
|
|
Reproduction |
|
|
|
|
|
|
|
|
This Chapt |
Discuss |
d: |
|
|
|
• |
Support ntitl |
ment and opening a support case; |
|
|
|
• |
Support resources; |
|
|
for |
• |
The Customer Support Center; |
|
|
• |
Case management; |
|
|
|
|
|
|
• |
JTAC KB and PRs search tools; |
|
|
|
• |
The I2J tool; |
|
|
|
Not |
|
• |
Downloading software and technical documentation; and |
|
• |
Transferring files to JTAC using FTP. |
|
|
|
JTAC Processes, Guidelines, and Support Resources • Chapter 6–21
Troubleshooting JUNOS Platforms
3. |
Reproduction |
|
|
|
Review Questions |
1. |
|
|
|
2. |
|
|
|
for |
|
|
|
4. |
|
|
|
Chapter 6–22 • JTAC Processes, Guidelines, and Support Resources
