- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Initializing nettl.LOG000
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2004 08:01 PM
09-19-2004 08:01 PM
I suspect my nettl.LOG000 is corrupted, causing netfmt -f /var/adm/nettl.LOG000 to core dump. This is what I did to initialize nettl.LOG00:
====================================
/sbin/init.d/nettl stop
mv nettl.LOG000 nettl.LOG000.bk
touch nettl.LOG000
/sbin/init.d/nettl start
====================================
The nettl.LOG000 is 128Byte size after restart, but netfmt -f cmd produce nothing now probably no logs has be entered.
Is my steps correct ?
thanks
Lai
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2004 08:11 PM
09-19-2004 08:11 PM
Re: Initializing nettl.LOG000
what are the entries in /etc/nettlgen.conf ?
Maybe you they are not correct and you should check them
Regards
Franky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2004 08:17 PM
09-19-2004 08:17 PM
Re: Initializing nettl.LOG000
Pardon me for asking. How do I determine if the entires are correct ?
I cut out the nettlgen.conf, remove all lines with "#",this is what I have :
=======================================
LOG:1:8:1000:/var/adm/nettl:/var/adm/conslog.opts
KL:1000:5000:1M:/var/adm/kl:0
SS:127:FORMATTER:12:u:libfmtutil.sl:netfmt:subsys_GENERIC_format:subsys_127_get_options:FORMATTER
SS:512:KL_FORMATTER:12:u:libfmtutil.sl:netfmt:subsys_GENERIC_format:subsys_512_get_options:FORMATTER
SS:0:NS_LS_LOGGING:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:1:NS_LS_NFT:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:2:NS_LS_LOOPBACK:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:3:NS_LS_NI:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:4:NS_LS_IPC:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:5:NS_LS_SOCKREGD:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:6:NS_LS_TCP:12:s:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:7:NS_LS_PXP:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:8:NS_LS_UDP:12:s:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:9:NS_LS_IP:12:s:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:10:NS_LS_PROBE:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:11:NS_LS_DRIVER:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:LAN/9000 NETWORKING
SS:12:NS_LS_RLBD:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:13:NS_LS_BUFS:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:14:NS_LS_CASE21:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:15:NS_LS_ROUTER21:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:16:NS_LS_NFS:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:17:NS_LS_NETISR:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:19:NS_LS_NSE:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:20:NS_LS_STRLOG:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:21:NS_LS_TIRDWR:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:22:NS_LS_TIMOD:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:23:NS_LS_ICMP:12:s:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:26:FILTER:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:27:NAME:12:k:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:29:NS_LS_IGMP:12:s:libnsfmt.sl:nsfmt:subsys_ns_format:subsys_ns_get_options:ARPA/9000 NETWORKING
SS:513:KL_VM:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:514:KL_PKM:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:515:KL_DLKM:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:516:KL_PM:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:517:KL_VFS:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:518:KL_VXFS:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:519:KL_UFS:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:520:KL_NFS:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:521:KL_FSVM:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:522:KL_WSIO:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:523:KL_SIO:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:524:KL_NET:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:525:KL_MC:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:526:KL_DYNTUNE:8:k:NULL:klfmt:NULL:NULL:Kernel Logging
SS:210:btlan:12:k:libfmtbtlan.sl:fmtbtlan:subsys_btlan_format::100 Mb/s LAN/9000 Networking
SS:129:STREAMS:12:k:libstrfmt.sl:strfmt:subsys_streams_format:subsys_streams_get_options:STREAMS/UX
SS:176:PCI_FDDI:12:k:libfddifmt4.sl:fddi4:subsys_176_format::PCI_FDDI
SS:185:GELAN:12:k:libfmgelan.sl:fmgelan:subsys_gelan_format::Gigabit Ethernet LAN/9000 Networking
SS:253:IETHER:12:k:libfmiether.sl:fmiether:subsys_iether_format::Gigabit Ethernet LAN/9000 Networking
SS:252:IGELAN:12:k:libfmigelan.sl:fmigelan:subsys_igelan_format::Gigabit Ethernet LAN/9000 Networking
SS:247:VLAN:12:k:libfmtvlan.sl:fmtvlan:subsys_vlan_format::VLAN Subsystem
=======================================
Thanks.
Lai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2004 11:40 PM
09-19-2004 11:40 PM
Re: Initializing nettl.LOG000
the nettlgen.conf file looks good to me.
Two more thoughts: is the NETTL=1 enty set in /etc/rc.config.d/nettl and is the nettl proc up and running ?
On the other site it can take some time until the nettl.LOG000 file is filled up, because it needs certain circumstances to make entries in there
Just my thoughts
Regards
Franky
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2004 12:43 PM
09-20-2004 12:43 PM
Re: Initializing nettl.LOG000
Thanks. I guess I'll have to simulate some network problems to generate errors to assertain if the nettl is working fine.
Thanks Franky, for your response and reading thru the conf file.
Lai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2004 12:10 AM
09-21-2004 12:10 AM
SolutionTo answer your first question, I've used that procedure before to clear up a corrupt nettl.LOGXXX trace file. When you recreate the log file it will be 128 byte size since no logging has occured.
To test your logging you can increase the log level to informative, you should see data written to the nettl.LOGXXX file.
To view logging:
# nettl -status |pg
Notice the default log level per subsystem is set to error and disaster.
Increase log level for ICMP
# nettl -log i w e d -entity ns_ls_icmp
Check status:
# nettl -status
NS_LS_ICMP INFORMATIVE WARNING ERROR DISASTER
Now create some ICMP trafic, ping the broadcast address etc.
You can increase nettl logging for all entities which should definately produce some log messages.
# nettl -log i w e d -entity all
To set it back to default do this.
# nettl -log e d -e all
Verify by checking the status again.
# nettl -status
You should be able to format your log file now.
# netfmt -Nnlf /var/adm/nettl.LOG000
Hope this helps,
Todd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2004 02:06 PM
09-21-2004 02:06 PM
Re: Initializing nettl.LOG000
Thanks Todd,
That's brilliant. I'm able to generate enuf logs to assertain that the nettl.LOG000 is fine and netfmt -f gives no more core dump.
Proble solved...
Thanks again man !!
Lai
[A happy Sys Admin]