Data Collection can help with issue investigation as well as in reducing time to resolve. Each problem/issue could require a different set of data to collect. This article contains a list of data to collect for NorthStar Controller issues. If your problem needs to be sent to JTAC for Root Cause Analysis (RCA), this data is required.

What information should I collect to assist in troubleshooting prior to opening a case?

The goal of this document is to reduce the time spent on initial data collection and reduce time to resolve by providing a comprehensive list of what to collect or gather to troubleshoot an issue.

Collect the following for NorthStar Controller issues:

1. Check the size of disk storage and size of each partition:

df -h
free -h

2. Check the NorthStar Controller version:

/u/wandl/bin/.bbdsgn -V

3. Check the NorthStar Controller's health status, including the IP address of all the VMs in NorthStar Controller:

service northstar status 

4. Collect the JunosVM configuration and iptables :

   1. Launch the  net_setup.py  script:

[root@hostname~]# /opt/northstar/utils/net_setup.py

2. Type D and press Enter to select Maintenance and Troubleshooting.

3. Type 1 and press Enter to select Backup JunosVM Configuration.

4. Confirm the backup JunosVM configuration is stored at ' /opt/northstar/data/junosvm/junosvm.conf '.

5. Save the iptables .

iptables-save > /opt/northstar/data/iptables.conf

5. Collect the NorthStar Controller logs:

tar -czvf /tmp/nslog-YYYY-MM-DD.tgz --exclude=junosvm.* /opt/northstar/logs/

2021-10-11: Changed "-exclude" to "--exclude" while collecting logs