Votos - 5, Puntuación media: 4.8
(
)
)
|
Resumen del manual
Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel. Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy network down time and/or permanent damage to hardware. • Use the command udprelay_do_systrace = 0 to disable systrace and enable console output. • Use the command C = x (where x=1 to 9.) This increases the levels of udprelay debug. A level of 5 will display the source, destination IP, and MAC lines seen below. A level of 8 will include the hex dump of the packet. In addition, this level is very CPU intensive and will delay the UDP function. A level of 9 displays all packets as well as IPC messages. At this time running a level of 9 uses up so much of the UDP function that the relay agent can not pass traffic. A level of 9 is not recommended. • And to turn it off use the udprelayDebugLevelCMM = -1 command. The following is a sample UDP relay debug session: enqueue_to_ip_using_ipc: Packet sent to IP using IPC handle_event_udprelay_cmm(): Received on bsd socket handle_event_bsd_udprelay_cmm: Recieved message from the bsd socket Received 284 bytes from bsdsocket 0x1a We got in a tweaked zero IP address packet on bsd socketRecvd on bsd socket pkt from 0.0.0.0, rtr-port addr=192.168.20.254, 0x-1062726402Received short packet from bsd socket from 192.168.20.254, len=284 bytesReceived request packetfor the bootp service on bsd socket BOOTP REQ: secs=0 hops=0x0 BOOTP REQ: Haven't waited long enough: secs=0 s/b >= 3 handle_event_udprelay_cmm(): received on ipc socket handle_event_ipc_udprelay_cmm: num of bytes received = 352 handle_event_ni_udprelay_cmm: Recieved message from the NI handle_event_ni_udprelay_cmm: Recieved message from the NI for regular UDP packet hex_dump_udprelay_cmm: Printing the buffer at address = 0x60c3b10 00 03 00 01 01 5d 0e 70 50 -- 31 20 30 01 4a 00 00 00 14 60 14 41 00 ff ff ff -- ff ff ff 00 0b 85 03 07 f0 81 00 00 14 08 00 45 -- 00 01 38 4d cb 40 00 20 11 0b eb 00 00 00 00 ff -- ff ff ff 00 44 00 43 01 24 9e a6 01 01 06 00 73 -- 02 3f 32 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 0b 85 03 07 f0 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 00 page 5-6 OmniSwitch Troubleshooting Guide September 2005 Troubleshooting BOOTP/DHCP/UDP Relay Preliminary Dshell 6/5/06 00 00 00 00 00 00 00 00 -- 00 00 00 00 00 00 00 63 82 53 63 35 01 03 32 04 -- c0 a8 14 9a 36 04 c0 a8 1e 05 39 02 02 4e 37 04 -- 01 1c 03 2b 3c 10 41 69 72 65 73 70 61 63 65 2e -- 41 50 31 32 30 30 ff In the example above, the BOOTP request was dropped because the number of seconds elapsed since the start of the process was not incremented (secs=0), and the forward delay was set to 3 seconds. We got in a tweaked zero IP address packet on BSD socket shown below: Recvd on bsd socket pkt from 0.0.0.0, rtr-port addr=20.20.20.200, 0x336860360Received request packet for the bootp service on bsd socket BOOTP REQ: secs=0 hops=0x0 The BOOTP REQ field shows that we haven’t waited long enough. (The seconds shown is 0, when it should be greater than or equal to 3.) handle_uevent_udprelay_cmm(d): received on ipcp socket relayDebughandle_event_ipc_Ludprelay_cmm: num oef bytes received = v368elCMM =-1handle_event_ni_udprelay_cmm: Recieved message from the NI handle_event_ni_udprelay_cmm: Recieved message from the NI for regular UDP pack Finally, the Dshell command bootpSizeCheck turns on/off the bootpSizeCheck function. (By default it is off.) To turn it on enter the following: Working: [Kernel]-> bootpSizeCheck = 1 To turn it on enter the following: Working: [Kernel]-> bootpSixeCheck = 0 Note. OS-6600 supports minimum of 64 byte size packets. OmniSwitch Troubleshooting Guide September 2005 page 5-7 Dshell Troubleshooting BOOTP/DHCP/UDP Relay page 5-8 OmniSwitch Troubleshooting Guide September 2005 6 Troubleshooting DNS In order to troubleshoot a DNS problem, a basic understanding of the protocol/feature is required. Some basic concepts are covered below. Reading the “Enabling the DNS Resolver” section in the “Logging Into the Switch” chapter in the appropriate OmniSwitch Switch Management Guide is highly recommended. In This Chapter “Introduction” on page 6-1 “Troubleshooting a DNS Failure” on page 6-2 “DNS Configuration Considerations” on page 6-3 Introduction The primary function of Domain Name Service or DNS enables the user to enter a pre-configured name rather than an IP address to reach...
Otros modelos de este manual:Equipo de red - 6624 (2.24 mb)
Equipo de red - 6800 (2.24 mb)
Equipo de red - 8800 (2.24 mb)